RBFS Redundancy Configurations

Configure RBFS Redundancy

To deploy RBFS in redundancy mode, you must complete the following configuration on both Multiservice Edge nodes which are paired for redundancy.

  • Redundancy Profile

  • Redundancy Session

  • Link Aggregation Group for the Redundancy Session

  • Access for the Redundancy Session

The following steps provide the commands to configure RBFS Redundancy on both devices, which comprise the redundancy pair. For more detailed information about RBFS Redundancy Deployment, see RBFS Redundancy Solution Guide.

Redundancy Profile Configuration

Run the following commands to configure the redundancy profile on both devices (CBNG1 and CBNG2). Redundancy profile configuration is required to enable the devices to identify the peer in the network.

CBNG1 configuration:

set redundancy profile rd_ipoe1
set redundancy profile rd_ipoe1 switchover-hold-timer 0
set redundancy profile rd_ipoe1 peer ipv4 remote-address 198.51.100.200
set redundancy profile rd_ipoe1 peer ipv4 update-source 198.51.100.100
set redundancy profile rd_ipoe1 peer ipv4 instance default
set redundancy profile rd_ipoe2
set redundancy profile rd_ipoe2 switchover-hold-timer 0
set redundancy profile rd_ipoe2 peer ipv4 remote-address 198.51.100.210
set redundancy profile rd_ipoe2 peer ipv4 update-source 198.51.100.110
set redundancy profile rd_ipoe2 peer ipv4 instance default
commit
supervisor@rtbrick: op> show config redundancy
{
  "rtbrick-config:redundancy": {
    "profile": [
      {
        "name": "rd_ipoe1",
        "switchover-hold-timer": 0,
        "peer": {
          "ipv4": {
            "remote-address": "198.51.100.200",
            "update-source": "198.51.100.100",
            "instance": "default"
          }
        }
      },
      {
        "name": "rd_ipoe2",
        "switchover-hold-timer": 0,
        "peer": {
          "ipv4": {
            "remote-address": "198.51.100.210",
            "update-source": "198.51.100.110",
            "instance": "default"
          }
        }
      }
    ],
    "session": [
      {
        "session-id": 100,
        "priority": 20,
        "profile": "rd_ipoe1"
      },
      {
        "session-id": 200,
        "priority": 15,
        "profile": "rd_ipoe2"
      }
    ]
  }
}

CBNG2 Configuration:

set redundancy profile rd_ipoe1
set redundancy profile rd_ipoe1 switchover-hold-timer 0
set redundancy profile rd_ipoe1 peer ipv4 remote-address 198.51.100.100
set redundancy profile rd_ipoe1 peer ipv4 update-source 198.51.100.200
set redundancy profile rd_ipoe1 peer ipv4 instance default
set redundancy profile rd_ipoe2
set redundancy profile rd_ipoe2 switchover-hold-timer 0
set redundancy profile rd_ipoe2 peer ipv4 remote-address 198.51.100.110
set redundancy profile rd_ipoe2 peer ipv4 update-source 198.51.100.210
set redundancy profile rd_ipoe2 peer ipv4 instance default
supervisor@rtbrick: op> show config redundancy
{
  "rtbrick-config:redundancy": {
    "profile": [
      {
        "name": "rd_ipoe1",
        "switchover-hold-timer": 0,
        "peer": {
          "ipv4": {
            "remote-address": "198.51.100.100",
            "update-source": "198.51.100.200",
            "instance": "default"
          }
        }
      },
      {
        "name": "rd_ipoe2",
        "switchover-hold-timer": 0,
        "peer": {
          "ipv4": {
            "remote-address": "198.51.100.110",
            "update-source": "198.51.100.210",
            "instance": "default"
          }
        }
      }
    ],
    "session": [
      {
        "session-id": 100,
        "priority": 10,
        "profile": "rd_ipoe1"
      },
      {
        "session-id": 200,
        "priority": 30,
        "profile": "rd_ipoe2"
      }
    ]
  }
}

Redundancy Session Configuration

Run the following commands to configure the session for redundancy. Redundancy sessions can be uniquely identified by session IDs, which are used to store subscriber-specific data between active and standby devices.

set redundancy session 100
set redundancy session 100 priority 20
set redundancy session 100 profile rd_ipoe1
set redundancy session 200
set redundancy session 200 priority 15
set redundancy session 200 profile rd_ipoe2

Redundancy configuration from the node CBNG1 is shown below:

supervisor@rtbrick: op> show config redundancy session
{
  "rtbrick-config:redundancy": {
    "session": [
      {
        "session-id": 100,
        "priority": 20,
        "profile": "rd_ipoe1"
      },
      {
        "session-id": 200,
        "priority": 15,
        "profile": "rd_ipoe2"
      }
    ]
  }
}

The redundancy configuration from the node CBNG2 is shown below:

set redundancy session 100
set redundancy session 100 priority 10
set redundancy session 100 profile rd_ipoe1
set redundancy session 200
set redundancy session 200 priority 30
set redundancy session 200 profile rd_ipoe2
supervisor@rtbrick: op> show config redundancy session
{
  "rtbrick-config:redundancy": {
    "session": [
      {
        "session-id": 100,
        "priority": 10,
        "profile": "rd_ipoe1"
      },
      {
        "session-id": 200,
        "priority": 30,
        "profile": "rd_ipoe2"
      }
    ]
  }
}
The session priority value determines the active/standby nodes for a session.

LAG Configuration for Redundancy

Run the following commands to configure LAG on both devices (CBNG1 and CBNG2) for redundancy. This configuration is required to associate the redundancy session with LAG.

Run the following commands to configure LAG on CBNG1 for redundancy.

set link-aggregation interface lag-1
set link-aggregation interface lag-1 mode lacp
set link-aggregation interface lag-1 minimum-link-count 3
set link-aggregation interface lag-1 redundancy-session-id 100
set link-aggregation interface lag-1 system-id 10:aa:aa:aa:aa:aa
set link-aggregation interface lag-1 member-interface ifp-0/1/26
set link-aggregation interface lag-1 member-interface ifp-0/1/27
set link-aggregation interface lag-1 member-interface ifp-0/1/28
set link-aggregation interface lag-11
set link-aggregation interface lag-11 mode lacp
set link-aggregation interface lag-11 minimum-link-count 3
set link-aggregation interface lag-11 redundancy-session-id 200
set link-aggregation interface lag-11 system-id 10:aa:aa:aa:aa:a1
set link-aggregation interface lag-11 member-interface ifp-0/1/31
set link-aggregation interface lag-11 member-interface ifp-0/1/33
set link-aggregation interface lag-11 member-interface ifp-0/1/35
set link-aggregation interface lag-2
set link-aggregation interface lag-2 mode lacp
set link-aggregation interface lag-2 minimum-link-count 2
set link-aggregation interface lag-2 member-interface ifp-0/1/14
set link-aggregation interface lag-2 member-interface ifp-0/1/15
set link-aggregation interface lag-3
set link-aggregation interface lag-3 mode lacp
set link-aggregation interface lag-3 minimum-link-count 2
set link-aggregation interface lag-3 member-interface ifp-0/1/23
set link-aggregation interface lag-3 member-interface ifp-0/1/24

LAG configuration for redundancy on CBNG1 is shown below:

supervisor@rtbrick: op> show config link-aggregation
{
  "rtbrick-config:link-aggregation": {
    "interface": [
      {
        "interface-name": "lag-1",
        "mode": "lacp",
        "minimum-link-count": 3,
        "redundancy-session-id": 100,
        "system-id": "10:aa:aa:aa:aa:aa",
        "member-interface": [
          {
            "member-interface-name": "ifp-0/1/26"
          },
          {
            "member-interface-name": "ifp-0/1/27"
          },
          {
            "member-interface-name": "ifp-0/1/28"
          }
        ]
      },
      {
        "interface-name": "lag-11",
        "mode": "lacp",
        "minimum-link-count": 3,
        "redundancy-session-id": 200,
        "system-id": "10:aa:aa:aa:aa:a1",
        "member-interface": [
          {
            "member-interface-name": "ifp-0/1/31"
          },
          {
            "member-interface-name": "ifp-0/1/33"
          },
          {
            "member-interface-name": "ifp-0/1/35"
          }
        ]
      },
      {
        "interface-name": "lag-2",
        "mode": "lacp",
        "minimum-link-count": 2,
        "member-interface": [
          {
            "member-interface-name": "ifp-0/1/14"
          },
          {
            "member-interface-name": "ifp-0/1/15"
          }
        ]
      },
      {
        "interface-name": "lag-3",
        "mode": "lacp",
        "minimum-link-count": 2,
        "member-interface": [
          {
            "member-interface-name": "ifp-0/1/23"
          },
          {
            "member-interface-name": "ifp-0/1/24"
          }
        ]
      }
    ]
  }
}

Run the following commands to configure LAG on CBNG2 for redundancy.

set link-aggregation interface lag-1
set link-aggregation interface lag-1 mode lacp
set link-aggregation interface lag-1 minimum-link-count 3
set link-aggregation interface lag-1 redundancy-session-id 100
set link-aggregation interface lag-1 system-id 10:aa:aa:aa:aa:aa
set link-aggregation interface lag-1 member-interface ifp-0/1/30
set link-aggregation interface lag-1 member-interface ifp-0/1/32
set link-aggregation interface lag-1 member-interface ifp-0/1/33
set link-aggregation interface lag-11
set link-aggregation interface lag-11 mode lacp
set link-aggregation interface lag-11 minimum-link-count 3
set link-aggregation interface lag-11 redundancy-session-id 200
set link-aggregation interface lag-11 system-id 10:aa:aa:aa:aa:a1
set link-aggregation interface lag-11 member-interface ifp-0/1/34
set link-aggregation interface lag-11 member-interface ifp-0/1/35
set link-aggregation interface lag-11 member-interface ifp-0/1/47
set link-aggregation interface lag-2
set link-aggregation interface lag-2 mode lacp
set link-aggregation interface lag-2 minimum-link-count 2
set link-aggregation interface lag-2 member-interface ifp-0/1/14
set link-aggregation interface lag-2 member-interface ifp-0/1/15
set link-aggregation interface lag-3
set link-aggregation interface lag-3 mode lacp
set link-aggregation interface lag-3 minimum-link-count 2
set link-aggregation interface lag-3 member-interface ifp-0/1/25
set link-aggregation interface lag-3 member-interface ifp-0/1/26

LAG configuration for redundancy on CBNG2 is shown below:

supervisor@rtbrick: op> show config link-aggregation
{
  "rtbrick-config:link-aggregation": {
    "interface": [
      {
        "interface-name": "lag-1",
        "mode": "lacp",
        "minimum-link-count": 3,
        "redundancy-session-id": 100,
        "system-id": "10:aa:aa:aa:aa:aa",
        "member-interface": [
          {
            "member-interface-name": "ifp-0/1/30"
          },
          {
            "member-interface-name": "ifp-0/1/32"
          },
          {
            "member-interface-name": "ifp-0/1/33"
          }
        ]
      },
      {
        "interface-name": "lag-11",
        "mode": "lacp",
        "minimum-link-count": 3,
        "redundancy-session-id": 200,
        "system-id": "10:aa:aa:aa:aa:a1",
        "member-interface": [
          {
            "member-interface-name": "ifp-0/1/34"
          },
          {
            "member-interface-name": "ifp-0/1/35"
          },
          {
            "member-interface-name": "ifp-0/1/47"
          }
        ]
      },
      {
        "interface-name": "lag-2",
        "mode": "lacp",
        "minimum-link-count": 2,
        "member-interface": [
          {
            "member-interface-name": "ifp-0/1/14"
          },
          {
            "member-interface-name": "ifp-0/1/15"
          }
        ]
      },
      {
        "interface-name": "lag-3",
        "mode": "lacp",
        "minimum-link-count": 2,
        "member-interface": [
          {
            "member-interface-name": "ifp-0/1/25"
          },
          {
            "member-interface-name": "ifp-0/1/26"
          }
        ]
      }
    ]
  }
}

Access Configuration for Redundancy

Run the following commands to configure access interface of CBNG1 device for enabling redundancy.

set access interface double-tagged lag-1 1001 1100 1001 1100 redundancy-session-id 100
set access interface double-tagged lag-11 1101 1200 1001 1100 redundancy-session-id 200

Access Configuration for Redundancy on CBNG-1 is shown below:

{
  "rtbrick-config:access": {
    "interface": {
      "double-tagged": [
        {
          "interface-name": "lag-1",
          "outer-vlan-min": 1001,
          "outer-vlan-max": 1100,
          "inner-vlan-min": 1001,
          "inner-vlan-max": 1100,
          "redundancy-session-id": 100
        },
        {
          "interface-name": "lag-11",
          "outer-vlan-min": 1101,
          "outer-vlan-max": 1200,
          "inner-vlan-min": 1001,
          "inner-vlan-max": 1100,
          "redundancy-session-id": 200
        }
      ]
    }
  }
}

Run the following commands to configure access interface of CBNG2 device for enabling redundancy.

set access interface double-tagged lag-1 1001 1100 1001 1100 redundancy-session-id 100
set access interface double-tagged lag-11 1101 1200 1001 1100 redundancy-session-id 200

Access Configuration for Redundancy on CBNG2 is shown below:

{
  "rtbrick-config:access": {
    "interface": {
      "double-tagged": [
        {
          "interface-name": "lag-1",
          "outer-vlan-min": 1001,
          "outer-vlan-max": 1100,
          "inner-vlan-min": 1001,
          "inner-vlan-max": 1100,
          "redundancy-session-id": 100
        },
        {
          "interface-name": "lag-11",
          "outer-vlan-min": 1101,
          "outer-vlan-max": 1200,
          "inner-vlan-min": 1001,
          "inner-vlan-max": 1100,
          "redundancy-session-id": 200
        }
      ]
    }
  }
}

BNG Blaster Configuration

BNG Blaster is an open-source network testing platform for access and routing protocols. It can emulate massive PPPoE and IPoE (DHCP) subscribers, including IPTV, and L2TP (LNS). One can use this platform for end-to-end BNG and non-BNG router testing. For more information about BNG Blaster, see https://github.com/rtbrick/bngblaster

Configure LAG on BNG Blaster for Redundancy Validation

With BNG blaster, you can validate the Multiservice Edge - IPoE with Redundancy solution implementation and the traffic streams. BNG Blaster uses the following configuration file to validate Multiservice Edge - IPoE with Redundancy.

{
  "interfaces": {
    "tx-interval": 1,
    "rx-interval": 1,
    "lag": [
      {
        "interface": "lag1",
        "lacp": true,
        "lacp-timeout-short": true
      },
      {
        "interface": "lag11",
        "lacp": true,
        "lacp-timeout-short": true
      }
    ],
    "links": [
      {
        "interface": "SN-5-C1",
        "lag-interface": "lag1"
      },
      {
        "interface": "SN-6-C1",
        "lag-interface": "lag1"
      },
      {
        "interface": "SN-7-C1",
        "lag-interface": "lag1"
      },
      {
        "interface": "SN-11-C2",
        "lag-interface": "lag1"
      },
      {
        "interface": "SN-12-C2",
        "lag-interface": "lag1"
      },
      {
        "interface": "SN-13-C2",
        "lag-interface": "lag1"
      },
      {
        "interface": "SN-20-C1",
        "lag-interface": "lag11"
      },
      {
        "interface": "SN-21-C1",
        "lag-interface": "lag11"
      },
      {
        "interface": "SN-22-C1",
        "lag-interface": "lag11"
      },
      {
        "interface": "SN-23-C2",
        "lag-interface": "lag11"
      },
      {
        "interface": "SN-24-C2",
        "lag-interface": "lag11"
      },
      {
        "interface": "SN-25-C2",
        "lag-interface": "lag11"
      }
    ],
    "network": [
      {
        "interface": "SN-15-R1",
        "address": "192.0.2.45/30",
        "gateway": "192.0.2.46",
        "isis-instance-id": 1,
        "isis-level": 1
      },
      {
        "interface": "SN-17-R2",
        "address": "192.0.2.50/30",
        "gateway": "192.0.2.49",
        "isis-instance-id": 2,
        "isis-level": 1
      },
      {
        "interface": "SN-19-RR",
        "address": "192.0.2.54/30",
        "gateway": "192.0.2.53",
        "address-ipv6": "2001:db8:1:1::2",
        "gateway-ipv6": "2001:db8:1:1::1",
        "isis-instance-id": 3,
        "isis-level": 1
      }
    ],
    "access": [
      {
        "interface": "lag1",
        "type": "ipoe",
        "stream-group-id": 1,
        "agent-remote-id": "CBNG1.RTBRICK.{session-global}",
        "outer-vlan-min": 1001,
        "outer-vlan-max": 1100,
        "inner-vlan-min": 1001,
        "inner-vlan-max": 1100
      },
      {
        "interface": "lag11",
        "type": "ipoe",
        "stream-group-id": 1,
        "agent-remote-id": "CBNG2.RTBRICK.{session-global}",
        "outer-vlan-min": 1101,
        "outer-vlan-max": 1200,
        "inner-vlan-min": 1001,
        "inner-vlan-max": 1100
      }
    ]
  },
  "sessions": {
    "count": 10,
    "max-outstanding": 800,
    "start-rate": 400,
    "stop-rate": 100
  },
  "access-line": {
    "agent-remote-id": "DEU.RTBRICK.{session-global}",
    "agent-circuit-id": "0.0.0.0/0.0.0.0 eth 0:{session-global}",
    "rate-up": 2000,
    "rate-down": 16384,
    "dsl-type": 5
  },
  "dhcp": {
    "enable": true
  },
  "dhcpv6": {
    "ldra": true,
    "enable": true
  },
  "streams": [
    {
        "name": "BE",
        "stream-group-id": 1,
        "type": "ipv4",
        "direction": "both",
        "network-ipv4-address": "192.0.2.54",
        "network-interface": "SN-19-RR",
        "vlan-priority": 1,
        "priority": 128,
        "length": 1000,
        "pps": 2000
    },
    {
        "name": "LowDelay",
        "stream-group-id": 1,
        "type": "ipv4",
        "direction": "both",
        "network-ipv4-address": "192.0.2.54",
        "network-interface": "SN-19-RR",
        "vlan-priority": 2,
        "priority": 160,
        "length": 1000,
        "pps": 2000
    },
    {
        "name": "LowLoss",
        "stream-group-id": 1,
        "type": "ipv4",
        "direction": "both",
        "network-ipv4-address": "192.0.2.54",
        "network-interface": "SN-19-RR",
        "vlan-priority": 3,
        "priority": 192,
        "length": 1000,
        "pps": 2000
    },
    {
        "name": "VoIP",
        "stream-group-id": 1,
        "type": "ipv4",
        "direction": "both",
        "network-ipv4-address": "192.0.2.54",
        "network-interface": "SN-19-RR",
        "vlan-priority": 4,
        "priority": 224,
        "length": 1000,
        "pps": 2000
    }
  ],
  "isis": [
    {
      "instance-id": 1,
      "area": [
        "49.0002/24"
      ],
      "system-id": "1920.0000.2036",
      "router-id": "192.0.2.36",
      "hostname": "BBL-LSR1",
      "hello-padding": true,
      "teardown-time": 30,
      "external": {
        "mrt-file": "/home/supervisor/isis.mrt",
        "connections": [
          {
            "system-id": "1980.5110.0061",
            "l1-metric": 10
          }
        ]
      }
    },
    {
      "instance-id": 2,
      "area": [
        "49.0002/24"
      ],
      "system-id": "1920.0000.2046",
      "router-id": "192.0.2.46",
      "hostname": "BBL-LSR2",
      "hello-padding": true,
      "teardown-time": 30,
      "external": {
        "mrt-file": "/home/supervisor/isis.mrt",
        "connections": [
          {
            "system-id": "1980.5110.0062",
            "l1-metric": 10
          }
        ]
      }
    },
    {
      "instance-id": 3,
      "area": [
        "49.0002/24"
      ],
      "system-id": "1980.5110.0056",
      "router-id": "198.51.100.56",
      "hostname": "BBL-RR",
      "hello-padding": true,
      "teardown-time": 30,
      "sr-base": 1000,
      "sr-range": 100,
      "sr-node-sid": 56,
      "external": {
        "mrt-file": "/home/supervisor/isis.mrt",
        "connections": [
          {
            "system-id": "1980.5110.0063",
            "l1-metric": 10
          }
        ]
      }
    }
  ],
  "bgp": [
    {
      "__comment__": "RR-IPv4",
      "network-interface": "SN-19-RR",
      "local-ipv4-address": "192.0.2.54",
      "peer-ipv4-address": "198.51.100.51",
      "raw-update-file": "/home/supervisor/ipv4_nlri.bgp",
      "local-as": 65002,
      "peer-as": 65002
    },
    {
      "__comment__": "RR-IPv6",
      "network-interface": "SN-19-RR",
      "local-ipv4-address": "192.0.2.54",
      "peer-ipv4-address": "198.51.100.52",
      "raw-update-file": "/home/supervisor/ipv6_nlri.bgp",
      "local-as": 65002,
      "peer-as": 65002
    }
  ]
}

Validating Multiservice Edge Redundancy and Reachability

The following command line string shows how to start a BNG Blaster instance:

sudo bngblaster -C <filename> -I -c10

Redundancy Session Data and Subscriber States on Active and Standby Nodes

CBNG-1: Before switchover, which is the actual state

supervisor@rtbrick: op> show redundancy session
Instance: default
  Session ID     Interface      Peer           Source         State          Peer state     Keepalive rcvd    Keepalive sent    Mode
  100            lag-1          198.51.100.200 198.51.100.100 active         standby        46                46                standby-non-forwarding
  200            lag-11         198.51.100.210 198.51.100.110 standby        active         46                45                standby-non-forwarding
supervisor@rtbrick: op> show subscriber
Subscriber-Id           Interface           VLAN     Type    State
1369375761697341441     lag-1             1001:1001  IPoE    ESTABLISHED
1369375761697341442     lag-1             1001:1002  IPoE    ESTABLISHED
1369375761697341443     lag-1             1001:1003  IPoE    ESTABLISHED
1369375761697341444     lag-1             1001:1004  IPoE    ESTABLISHED
1369375761697341445     lag-1             1001:1005  IPoE    ESTABLISHED
2522297266304188417     lag-11            1101:1001  IPoE    STANDBY
2522297266304188418     lag-11            1101:1002  IPoE    STANDBY
2522297266304188419     lag-11            1101:1003  IPoE    STANDBY
2522297266304188420     lag-11            1101:1004  IPoE    STANDBY
2522297266304188421     lag-11            1101:1005  IPoE    STANDBY

CBNG-2: Before switchover, which is the actual state

supervisor@rtbrick: op> show redundancy session
Instance: default
  Session ID     Interface      Peer           Source         State          Peer state     Keepalive rcvd    Keepalive sent    Mode
  100            lag-1          198.51.100.100 198.51.100.200 stand-alone    down           48                48                standby-non-forwarding
  200            lag-11         198.51.100.110 198.51.100.210 active         standby        47                47                standby-non-forwarding
supervisor@rtbrick: op> show subscriber
Subscriber-Id           Interface           VLAN     Type    State
1369375761697341441     lag-1             1001:1001  IPoE    ESTABLISHED
1369375761697341442     lag-1             1001:1002  IPoE    ESTABLISHED
1369375761697341443     lag-1             1001:1003  IPoE    ESTABLISHED
1369375761697341444     lag-1             1001:1004  IPoE    ESTABLISHED
1369375761697341445     lag-1             1001:1005  IPoE    ESTABLISHED
2522297266304188417     lag-11            1101:1001  IPoE    ESTABLISHED
2522297266304188418     lag-11            1101:1002  IPoE    ESTABLISHED
2522297266304188419     lag-11            1101:1003  IPoE    ESTABLISHED
2522297266304188420     lag-11            1101:1004  IPoE    ESTABLISHED
2522297266304188421     lag-11            1101:1005  IPoE    ESTABLISHED

After link (connecting OLT1 to CBNG1) is brought down, the state becomes down for the RD session 100 and for the same session, the other CBNG becomes stand-alone.

CBNG-1:

supervisor@rtbrick: op> show redundancy session
Instance: default
  Session ID     Interface      Peer           Source         State          Peer state     Keepalive rcvd    Keepalive sent    Mode
  100            lag-1          198.51.100.200 198.51.100.100 active         standby        47                47                standby-non-forwarding
  200            lag-11         198.51.100.210 198.51.100.110 standby        active         47                46                standby-non-forwarding
supervisor@rtbrick: op> show subscriber
Subscriber-Id           Interface           VLAN     Type    State
1369375761697341441     lag-1             1001:1001  IPoE    ESTABLISHED
1369375761697341442     lag-1             1001:1002  IPoE    ESTABLISHED
1369375761697341443     lag-1             1001:1003  IPoE    ESTABLISHED
1369375761697341444     lag-1             1001:1004  IPoE    ESTABLISHED
1369375761697341445     lag-1             1001:1005  IPoE    ESTABLISHED
2522297266304188417     lag-11            1101:1001  IPoE    STANDBY
2522297266304188418     lag-11            1101:1002  IPoE    STANDBY
2522297266304188419     lag-11            1101:1003  IPoE    STANDBY
2522297266304188420     lag-11            1101:1004  IPoE    STANDBY
2522297266304188421     lag-11            1101:1005  IPoE    STANDBY

CBNG-2:

supervisor@rtbrick: op> show redundancy session
Instance: default
  Session ID     Interface      Peer           Source         State          Peer state     Keepalive rcvd    Keepalive sent    Mode
  100            lag-1          198.51.100.100 198.51.100.200 stand-alone    down           48                48                standby-non-forwarding
  200            lag-11         198.51.100.110 198.51.100.210 active         standby        47                47                standby-non-forwarding
supervisor@rtbrick: op> show subscriber
Subscriber-Id           Interface           VLAN     Type    State
1369375761697341441     lag-1             1001:1001  IPoE    ESTABLISHED
1369375761697341442     lag-1             1001:1002  IPoE    ESTABLISHED
1369375761697341443     lag-1             1001:1003  IPoE    ESTABLISHED
1369375761697341444     lag-1             1001:1004  IPoE    ESTABLISHED
1369375761697341445     lag-1             1001:1005  IPoE    ESTABLISHED
2522297266304188417     lag-11            1101:1001  IPoE    ESTABLISHED
2522297266304188418     lag-11            1101:1002  IPoE    ESTABLISHED
2522297266304188419     lag-11            1101:1003  IPoE    ESTABLISHED
2522297266304188420     lag-11            1101:1004  IPoE    ESTABLISHED
2522297266304188421     lag-11            1101:1005  IPoE    ESTABLISHED

CBNG-1:

supervisor@rtbrick: op> show redundancy session
Instance: default
  Session ID     Interface      Peer           Source         State          Peer state     Keepalive rcvd    Keepalive sent    Mode
  100            lag-1          198.51.100.200 198.51.100.100 connect        stand-alone    48                49                standby-non-forwarding
  200            lag-11         198.51.100.210 198.51.100.110 standby        active         48                47                standby-non-forwarding
supervisor@rtbrick: op> show subscriber
Subscriber-Id           Interface           VLAN     Type    State
1369375761697341441     lag-1             1001:1001  IPoE    STANDBY
1369375761697341442     lag-1             1001:1002  IPoE    STANDBY
1369375761697341443     lag-1             1001:1003  IPoE    STANDBY
1369375761697341444     lag-1             1001:1004  IPoE    STANDBY
1369375761697341445     lag-1             1001:1005  IPoE    STANDBY
2522297266304188417     lag-11            1101:1001  IPoE    STANDBY
2522297266304188418     lag-11            1101:1002  IPoE    STANDBY
2522297266304188419     lag-11            1101:1003  IPoE    STANDBY
2522297266304188420     lag-11            1101:1004  IPoE    STANDBY
2522297266304188421     lag-11            1101:1005  IPoE    STANDBY

CBNG-2:

supervisor@rtbrick: op> show redundancy session
Instance: default
  Session ID     Interface      Peer           Source         State          Peer state     Keepalive rcvd    Keepalive sent    Mode
  100            lag-1          198.51.100.100 198.51.100.200 stand-alone    connect        49                48                standby-non-forwarding
  200            lag-11         198.51.100.110 198.51.100.210 active         standby        47                48                standby-non-forwarding
supervisor@rtbrick: op> show subscriber
Subscriber-Id           Interface           VLAN     Type    State
1369375761697341441     lag-1             1001:1001  IPoE    ESTABLISHED
1369375761697341442     lag-1             1001:1002  IPoE    ESTABLISHED
1369375761697341443     lag-1             1001:1003  IPoE    ESTABLISHED
1369375761697341444     lag-1             1001:1004  IPoE    ESTABLISHED
1369375761697341445     lag-1             1001:1005  IPoE    ESTABLISHED
2522297266304188417     lag-11            1101:1001  IPoE    ESTABLISHED
2522297266304188418     lag-11            1101:1002  IPoE    ESTABLISHED
2522297266304188419     lag-11            1101:1003  IPoE    ESTABLISHED
2522297266304188420     lag-11            1101:1004  IPoE    ESTABLISHED
2522297266304188421     lag-11            1101:1005  IPoE    ESTABLISHED
To revert to the original active-standby mode based on the priority, a manual switchover can be performed using the switch-over session 100 confirm command.

Switchover Scenario for Active Multiservice Edge Node Failure

CBNG-2’s Session State and Subscriber State After node failure

supervisor@rtbrick: op> show redundancy session
Instance: default
  Session ID     Interface      Peer           Source         State          Peer state     Keepalive rcvd    Keepalive sent    Mode
  100            lag-1          198.51.100.100 198.51.100.200 stand-alone    down           51                51                standby-non-forwarding
  200            lag-11         198.51.100.110 198.51.100.210 stand-alone    down           49                50                standby-non-forwarding
supervisor@rtbrick: op> show subscriber
Subscriber-Id           Interface           VLAN     Type    State
1369375761697341441     lag-1             1001:1001  IPoE    ESTABLISHED
1369375761697341442     lag-1             1001:1002  IPoE    ESTABLISHED
1369375761697341443     lag-1             1001:1003  IPoE    ESTABLISHED
1369375761697341444     lag-1             1001:1004  IPoE    ESTABLISHED
1369375761697341445     lag-1             1001:1005  IPoE    ESTABLISHED
2522297266304188417     lag-11            1101:1001  IPoE    ESTABLISHED
2522297266304188418     lag-11            1101:1002  IPoE    ESTABLISHED
2522297266304188419     lag-11            1101:1003  IPoE    ESTABLISHED
2522297266304188420     lag-11            1101:1004  IPoE    ESTABLISHED
2522297266304188421     lag-11            1101:1005  IPoE    ESTABLISHED