Configuring Redundancy for PPPoE Subscribers

Configuration Overview

Configuring Redundancy for PPPoE Subscribers

You must perform the following tasks to deploy the RBFS devices in redundancy mode. These configurations must be performed on both of the devices.

  1. Set up the Redundancy Mode on the Platform Profile

  2. Configure Redundancy Profile

  3. Configure Session for Redundancy

  4. Configure Link Aggregation Group for Redundancy

Configuration Syntax and Commands

The following sections describe syntax and commands for various configurations.

Configure the Redundancy Mode

You must select the standby-non-forwarding option under the platform profile.

This setup is a one-time activity and system reboot is required the changes to take effect.

To set the desired redundancy mode, use the command.

Syntax:

set system platform profile <profile-name> redundancy-mode standby-non-forwarding

Attribute Description

<profile-name>

Name of the platform profile.

standby-non-forwarding

Active-Standby Redundancy mode. Standby node and LAG does not forward traffic unless a failover occurs.

Example:

This configuration defines a platform profile named '4q' and enables 'standby-non-forwarding' mode.

set system platform profile 4q
set system platform profile 4q redundancy-mode standby-non-forwarding
supervisor@rtbrick.net: cfg> show config system platform profile
{
  "rtbrick-config:profile": [
    {
      "profile_name": "4q",
      "redundancy-mode": "standby-non-forwarding"
    }
  ]
}

Configuring Redundancy Profile

Redundancy profile is used to provide peer node identity in redundancy. While configuring the redundancy profile on the nodes, you need to specify IP addresses of both the peer nodes. Based on the priority value that you specify for the session ID, the peers take the roles of active and standby for the subscriber session.

Syntax:

set redundancy profile <name> peer ipv4 instance <instance>
set redundancy profile <name> peer ipv4 remote-address <remote-address>
set redundancy profile <name> peer ipv4 update-source <update-source>
set redundancy profile <name> switchover-hold-timer <0-600>

Attribute Description

name

Name of the redundancy profile.

instance

Name of the instance.

remote-address

Specifies the IPv4 address of the peer BNG.

update-source

Specifies the source IPv4 address used by the local node.

switchover-hold-timer

Minimum interval time between consecutive switch-overs in seconds. Supported range: 0 - 600.

Example:

This configuration sets up a redundancy profile called 'rd_pppoe' and details the essential parameters for establishing peer connectivity. The remote-address specifies the peer BNG, the update-source designates the local address for the redundancy session, and the instance parameter defines the routing instance that manages the peer connection.

set redundancy profile rd_pppoe
set redundancy profile rd_pppoe peer ipv4 remote-address 198.51.100.2
set redundancy profile rd_pppoe peer ipv4 update-source 198.51.100.1
set redundancy profile rd_pppoe peer ipv4 instance default
supervisor@rtbrick.net: cfg> show config redundancy profile
{
    "rtbrick-config:profile": [
      {
        "name": "rd_pppoe",
        "peer": {
          "ipv4": {
            "remote-address": "198.51.100.2",
            "update-source": "198.51.100.1",
            "instance": "default"
          }
        }
      }
    ]
  }

api  To access the RESTCONF API that corresponds to this CLI, click here.

Configuring Session for Redundancy

You can configure Redundancy session with a unique session ID. You can define the system priority value (which determines active and standby roles) and the associate Redundancy profile configuration in the Redundancy Session configuration.

Syntax:

set redundancy session <id> keepalive-interval <value>
set redundancy session <id> priority <priority>
set redundancy session <id> profile <profile>

Attribute Description

keepalive-interval

Keepalive message transmission interval in seconds. Supported range is 1 - 30. Default is 3 seconds.

id

Session ID supported value range is 1 - 255.

priority

The node with the higher priority value becomes the active node.

profile

Redundancy profile name.

Example for configuring session for redundancy.

The following configuration creates a redundancy session (session ID 100) and links it to the 'rd_pppoe' redundancy profile. The priority value determines the node’s preference for acting as the active unit.

set redundancy session 100
set redundancy session 100 priority 10
set redundancy session 100 profile rd_pppoe

Configuration Example:

supervisor@rtbrick.net: cfg> show config redundancy session
{
    "rtbrick-config:session": [
      {
        "session-id": 100,
        "priority": 10,
        "profile": "rd_pppoe"
      }
    ]
  }

api  To access the RESTCONF API that corresponds to this CLI, click here.

Configuring LAG for Redundancy

You must associate the Redundancy session ID with the LAG. While configuring LAG for redundancy, you must specify the session ID to associate the LAG with the Redundancy Session. LAG can identify its Redundancy session with this mapping.

For information on how to configure LAG for Redundancy, see Configuring LAG for Redundancy.

Switchover Manually

In the Active-Standby redundancy mode, administrators can perform a manual switchover from an active node to a standby node. Use the following command to perform switchover:

switch-over session <id> confirm