Skip to main content
jensthms
New Member
Jul 14, 2019 12:42 PM UTC
Solved

SD WAN issue

I was trying to do SD WAN cofiguration in fortinet VM(6.0) in gns3 before going live in production. But i cant add members to SDWAN, it shows error FAILED DEPENDENCY. What could be the reason?. I also checked whether the interface adding is there in any policy. I can add one interface to SDWAN,when adding second one it shows failed dependency error.

    Dave_Hall
    Dave_HallAnswer
    New Member
    Jul 18, 2019 2:43 PM UTC

    Possible suggestion:

    Add port2 to the SDWAN by itself and save that cfg then load an unencrypted backup copy into a text editor and add port3 to the SDWAN members.  Load that back into the fgt vm - try to monitor the console output while it is booting and/or perform diagnose debug config-error-log read at the CLI after you gain access the console.

     

    The above method is ugly in my opinion, but may work.  I recall an old bug from the 4.3/5.0 days where just doing something in the GUI causes certain interfaces to "become dependence".  That said, as a suggestion it maybe remotely possible that this problem is browser related - try using a different browser.

     

     

     

    14 replies

    hubertzw
    New Member
    Jul 15, 2019 11:24 AM UTC

    Check routing and firewall policies, VPN, etc.

    Translate
    jensthms
    jensthmsAuthor
    New Member
    Jul 15, 2019 12:49 PM UTC

    i checked that..interfaces are not linked in any of those sections(ipv4 policy,vpn,routing etc) Iam configuring it from scratch..

    Translate
    Toshi_Esumi
    SuperUser
    SuperUser
    Jul 15, 2019 4:05 PM UTC

    Get in CLI and "show | grep -f INTERFACE_NAME"

    If it doesn't show anything other than the interface config, you might need to reboot it.

    Translate
    jensthms
    jensthmsAuthor
    New Member
    Jul 18, 2019 8:12 AM UTC

    I also checked whether it is referenced anywhere but cant find anything.

    Translate
    Leen
    New Member
    Jul 18, 2019 11:49 AM UTC

    backup your fortigate and use a text editor to scan through the backup text file.

    items to look for

    - port 9 HA enabled

    - ntp setup on interface

    - user that has the interface on it's gui defined

    Translate
    Dave_Hall
    Dave_HallAnswer
    New Member
    Jul 18, 2019 2:43 PM UTC

    Possible suggestion:

    Add port2 to the SDWAN by itself and save that cfg then load an unencrypted backup copy into a text editor and add port3 to the SDWAN members.  Load that back into the fgt vm - try to monitor the console output while it is booting and/or perform diagnose debug config-error-log read at the CLI after you gain access the console.

     

    The above method is ugly in my opinion, but may work.  I recall an old bug from the 4.3/5.0 days where just doing something in the GUI causes certain interfaces to "become dependence".  That said, as a suggestion it maybe remotely possible that this problem is browser related - try using a different browser.

     

     

     

    Translate
    jensthms
    jensthmsAuthor
    New Member
    Jul 18, 2019 1:38 PM UTC

    I also checked the above things. But same issue. Attaching the config file below.

    Translate
    Risk and Resilience in the Age of AI. An OT Thought Leadership Summit for Houston's Critical Infrastructure Leaders. Date: Thursday, December 3, 2026. Time: 8:30 am - 1:30 pm (CT). Location: The Westin Houston, Memorial City | 945 Gessner Road, Houston, TX 77024