Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Example: Configuring Broadband Gateway Redundancy

    This example shows how to configure redundancy for a MobileNext Broadband Gateway chassis containing session Dense Port Concentrators (DPCs) and interface DPCs and Module Port Concentrators (MPCs) (housing Packet Forwarding Engines). Routing Engine redundancy is not unique to mobility and is not discussed in this example. This topic describes only the unique mobile redundancy portion of the configuration.

    Requirements

    This example uses the following hardware and software components:

    • An MX chassis equipped with four session DPCs and three interface DPCs or MPCs.
    • Junos OS Mobility package

    Before you begin:

    • Install the chassis hardware.
    • Configure the chassis.

    Overview

    Figure 1 shows a broadband gateway chassis with multiple Routing Engines (not discussed further in this example), session DPCs, and interfaces Packet Forwarding Engines (housed in DPCs or MPCs).

    Figure 1: Redundancy Example for the Broadband Gateway

    Redundancy Example for the Broadband
Gateway

    In this example, the chassis has session DPCs in Packet Forwarding Engines slots 4 and 5 featuring 1:1 redundancy. Group ams0 will backup PIC mams-4/1/0 with mams-5/1/0 and redistribute all traffic with the rejoin option. Group ams1 will back up PIC mams-4/0/0 with mams-5/0/0. Both groups have two logical units for authentication, authorization, and accounting (AAA) and charging. The chassis also has interface DPCs or MPCs in Packet Forwarding Engines slots 7, 8, and 9, featuring N:1 redundancy, in this case, 2:1. This example backs up Packet Forwarding Engines pfe-7/0/0 and pfe-8/0/0 with warm standby pfe-9/0/0.

    Configuration

    Redundancy for the above is configured by:

    Configuration

    CLI Quick Configuration

    [edit interfaces]user@host# set ams0 load-balancing-options member-interface mams-4/1/0 user@host# set ams0 load-balancing-options member-interface mams-5/1/0 user@host# set ams0 load-balancing-options high-availability-options many-to-one preferred-backup mams-5/1/0 user@host# set ams0 load-balancing-options member-interface-options redistirbute-all-traffic enable-rejoin user@host# set ams0 unit 1 family inet user@host# set ams0 unit 2 family inet user@host# set ams1 load-balancing-options member-interface mams-4/0/0 user@host# set ams1 load-balancing-options member-interface mams-5/0/0 user@host# set ams1 load-balancing-options high-availability-options many-to-one preferred-backup mams-5/0/0 user@host# set ams1 unit 1 family inet user@host# set ams1 unit 2 family inet user@host#set apfe0 anchoring-options primary-list pfe-7/0/0 user@host#set apfe0 anchoring-options primary-list pfe-8/0/0 user@host#set apfe0 anchoring-options secomdary pfe-9/0/0 warm-standby

    Step-by-Step Procedure

    Results

    From configuration mode, confirm your configuration by entering the show interfaces command. If the output does not display the intended configuration, repeat the configuration instructions in this example to correct it.

    For brevity, this show command output includes only the configuration statements that are relevant to this example.

    ams0 {load-balancing-options {member-interface mams-4/1/0;member-interface mams-5/1/0;member-failure–options {redistribute-all-traffic {enable-rejoin;}}high-availability-options {many-to-one {preferred-backup mams-5/1/0;}}}unit 1 {family inet;}unit 2 {family inet;}}ams1 {load-balancing-options {member-interface mams-4/0/0;member-interface mams-5/0/0;member-failure–options {drop-member-traffic {rejoin-timeout 10000;}}high-availability-options {many-to-one {preferred-backup mams-5/1/0;}}}unit 1 {family inet;}unit 2 {family inet;}}apfe0 {anchoring-options {primary-list {fpc-7/0/0;fpc-8/0/0;}secondary pfe-9/0/0;warm-standby;}}

    If you are done configuring the device, enter commit from configuration mode.

    Verification

    Verifying Redundancy

    Purpose

    Verify that redundancy is enabled or not.

    Action

    From operational mode, enter the show unified-edge ggsn-pgw interfaces redundancy command.

    Note: To view failover statistics, enter the show unified-edge ggsn-pgw exception-handling statistics failover command.

    Meaning

    The output shows the redundancy parameters or failover statistics configured on the gateway

    Published: 2011-11-22