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

    Configuring Interface DPCs or MPCs for User Mobility Traffic

    The MobileNext Broadband Gateway chassis has a number of open slots for cards (also called boards). Once installed, the cards must be configured. This topic describes the configuration process for the interface Modular Port Concentrators (MPCs) or Dense Port Concentrators (DPCs) used for user mobile traffic.

    Before you begin, you should have done the following:

    • Installed the MobileNext Broadband Gateway
    • Installed the cards of the broadband gateway
    • Decided which DPCs or MPCs will be used for user mobility traffic

    To configure an interface DPC or MPC for user mobility traffic, you configure the DPC or MPC to run the mobility forwarding package. You can configure this capability at the card (FPC) or Packet Forwarding Engine level. To configure the DPC or MPC:

    1. Configure the forwarding package at the FPC level (so that all Packet Forwarding Engines understand what to do with mobility packets) by configuring the mobility ggsn-pgw forwarding package at the FPC level.
      [edit chassis]user@host# set fpc 0 forwarding-packages mobility ggsn-pgw

      In this example, all Packet Forwarding Engines on the DPC or MPC in FPC slot 0 are configured for mobility traffic.

    2. Optionally, configure the forwarding package at the PIC level, so that only this PIC understands what to do with mobility packets by configuring the mobility ggsn-pgw forwarding package at the PIC level:
      [edit chassis]user@host# set fpc 0 pfe 0 forwarding-packages mobility ggsn-pgw

      In this example, only Packet Forwarding Engine 0 on the DPC or MPC in FPC slot 0 is configured for mobility traffic.

    Note: You must include every Packet Forwarding Engine configured with the ggsn-pgw forwarding package at the [edit unified-edge gateways ggsn-pgw gateway-name system anchor-pfes] hierarchy level on the broadband gateway. If you do not specify the Packet Forwarding Engine as an anchor, then the Packet Forwarding Engine will not be used by the broadband gateway.

    Published: 2011-11-22