SD-WAN

  • 1.  Router stuck at "Starting"

    Posted 09-18-2020 09:01

    Hi,

    After creating a router from the conductor and selecting the correct asset-id, the status is stuck at "starting".
    Below are the steps performed :
    1. Conductor is up and running
    2. Router is configured with conductor IP address.
    3. On the conductor we can see the "Pending" request, as well as the correct asset-id
    4. A new router is created on the Conductor :
    - A new node is created with a device interface (Named WAN with correct PCI Address)
    - Role combo is selected
    - Network Interface with static IP, Source NAT and "Conductor : true" is created
    5. The conductor communicates with the router and applies the config  :
    - the status is changed from Connected to Reinitializing, then to Starting (retrieve version 4.3.6, which is also the version of the Conductor)

    6. on the router, we can see eth0 interface is removed, kni254 interface is created.
    There is an error message
    "Failed to add device interface WAN, disabling the resource due to :Device attach failure: Error (1: Operation not permitted) cannot finde device 0000:00:0a:0"
    The bus address matches however the one from eth0.


    Running a tcpdump, we can see the router sends multiple TCP retransmits (dport 4505 and 4506)


    The status on the conductor is then stuck at Starting for about 20 minutes, finally it changes to "Disconnected"


    On the router itself, the device-interface is configured but appears as "down"


    EDIT : Added show system connectivity internal output (According to Tyler Carroll's Blo)

    ------------------------------
    Mirco El-Nomany
    Head of IT
    01721037634
    ------------------------------


  • 2.  RE: Router stuck at "Starting"

    Posted 09-22-2020 03:14
    The error "Failed to add device interface WAN, disabling the resource due to :Device attach failure: Error (1: Operation not permitted) cannot find device 0000:00:0a:0" seems to be linked to legacy hyper-V network adapters. Even if the PCI address is correct, the conductor cannot change the config.

    Solution was to use normal Hyper-V network adapter :
    - Choosing VM generation 2
    - Selecting blue network card
    - Since no PCI address is found when using modern NIC, create a bridge for the network interface on the conductor ( Ethernet bridge, destination interface eth0)

    Now the router can be installed

    ------------------------------
    Mirco El-Nomany
    Head of IT
    01721037634
    ------------------------------



  • 3.  RE: Router stuck at "Starting"

    Posted 09-23-2020 06:58
    The workaround works fine for normal interfaces (type external), but we cannot configure HA interfaces :
    "Cannot configure a non-forwarding host or bridged interface"
    "Only non-forwarding fabric or shared interfaces of type "ethernet" are allowed"

    ------------------------------
    Mirco El-Nomany
    ------------------------------