SD-WAN

 View Only
last person joined: 3 days ago 

Ask questions and share experiences with SD-WAN and Session Smart Router (formerly 128T).
  • 1.  HA Not quite working

    Posted 05-01-2019 07:32
    I have a simple setup, as follows;

    Users ---10.1.8.1/24-- LAN1 (Node1RTR1) ---WAN1 ----- 172.16.95.0/16 ---- Internet
                                                         |
                                                     Fabric
                                                         |
    Users ---10.1.8.1/24-- LAN1 (Node2RTR1)

    If LAN1 is active on Node1, traffic to/from Internet flows.
    If LAN1 is active on Node2, traffic is blocked but I can ping the def gw on LAN1

    Conductor CFG follows:
    node leedsedge1
    name leedsedge1
    asset-id leedsedge1
    role combo

    device-interface LAN1
    name LAN1
    description "Link to Switch 1"
    pci-address 0000:00:14.2
    enabled true
    shared-phys-address 00:00:5e:00:00:01

    network-interface LEEDSLAN1
    name LEEDSLAN1
    global-id 7
    type external
    tenant LeedsLan1

    address 10.1.8.1
    ip-address 10.1.8.1
    prefix-length 24
    exit
    exit
    exit

    device-interface Fabric
    name Fabric
    pci-address 0000:00:14.1

    network-interface Fabric
    name Fabric
    global-id 3

    address 100.64.0.16
    ip-address 100.64.0.16
    prefix-length 31
    exit
    exit
    exit

    device-interface WAN
    name WAN
    pci-address 0000:04:00.0
    capture-filter "ip host 172.16.95.50"

    network-interface FakeWAN
    name FakeWAN
    global-id 4
    source-nat true

    address 172.16.95.50
    ip-address 172.16.95.50
    prefix-length 16
    gateway 172.16.0.1
    exit
    exit
    exit

    device-interface Mgmt
    name Mgmt
    pci-address 0000:00:14.3

    network-interface Mgmt
    name Mgmt
    global-id 6
    conductor true
    tenant Mgmt
    source-nat true

    address 10.1.2.61
    ip-address 10.1.2.61
    prefix-length 24

    host-service ssh
    service-type ssh
    exit
    exit
    exit
    exit
    exit

    node leedsedge2
    name leedsedge2
    asset-id leedsedge2
    role combo

    device-interface Fabric
    name Fabric
    pci-address 0000:00:14.1

    network-interface Fabric
    name Fabric
    global-id 2

    address 100.64.0.17
    ip-address 100.64.0.17
    prefix-length 31
    exit
    exit
    exit

    device-interface Mgmt
    name Mgmt
    pci-address 0000:00:14.3

    network-interface Mgmt
    name Mgmt
    global-id 5
    conductor true
    tenant Mgmt
    source-nat true

    address 10.1.2.62
    ip-address 10.1.2.62
    prefix-length 24

    host-service ssh
    service-type ssh
    exit
    exit
    exit
    exit

    device-interface LAN1
    name LAN1
    pci-address 0000:00:14.2
    shared-phys-address 00:00:5e:00:00:01

    network-interface LAN1
    name LAN1
    global-id 7
    tenant LeedsLan1

    address 10.1.8.1
    ip-address 10.1.8.1
    prefix-length 24
    exit
    exit
    exit
    exit

    service-route Internet
    name Internet
    service-name Internet

    next-hop leedsedge1 FakeWAN
    node-name leedsedge1
    interface FakeWAN
    gateway-ip 172.16.0.1
    exit
    exit

    ------------------------------
    Alan Wright
    LEATHERHEAD
    +44 (0) 20 7043 6127
    ------------------------------


  • 2.  RE: HA Not quite working
    Best Answer

     
    Posted 05-02-2019 09:37
    Hi, did you set your Fabric network interface to type "fabric" in the config?

    ------------------------------
    Gene Shtirmer
    Sales Engineer
    Randolph NJ
    (973) 610-5676
    ------------------------------



  • 3.  RE: HA Not quite working

    Posted 05-03-2019 04:43

    Well spotted Gene. I now have

    0.0.0.0/0 <any> <any> OfficeUser Internet 100.64.0.16
    :)



    ------------------------------
    Alan Wright
    LEATHERHEAD
    +44 (0) 20 7043 6127
    ------------------------------



  • 4.  RE: HA Not quite working

     
    Posted 05-03-2019 00:11
    At face value this config looks good to me. Check the output of "show fib" on both nodes. On the A node, the FIB for your internet service will have the egress gateway. On the B node it should show the 100.64.0.16 address as a next hop.

    ------------------------------
    pt.
    ------------------------------