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 Anchor Session DPCs and PFEs

    Even with redundancy configured, a separate step is required to make a session Dense Port Concentrator (DPC) or Packet Forwarding Engine (Packet Forwarding Engines are part of an interface DPC or Modular Port Concentrator [MPC]) a mobility anchor. An anchor acts as a tunnel endpoint for control and data GPRS tunneling protocol (GTP) packets.

    Before you begin configuring anchors on a broadband gateway, you should have done the following:

    • Configured the chassis of the MobileNext Broadband Gateway
    • Configured the interfaces of the broadband gateway
    • (Optional) Configured the general redundancy parameters for the broadband gateway

    To determine the anchor session DPCs (PICs) and Packet Forwarding Engines, you configure the components as anchors.

    To configure anchor session DPCs (PICs):

    1. Add the PIC to the list of anchor-spics.
      [edit unified-edge gateway ggsn-pgw MBG1 system]user@host# set anchor-spics interface ams0

      Note: You can set the anchor PICs individually if you do not have redundancy configured. For example, you can use ms-1/1/0 instead of ams0.

    2. Add the Packet Forwarding Engine to the list of anchor-pfes.
      [edit unified-edge gateway ggsn-pgw MBG1 system]user@host# set anchor-pfes interface apfe0user@host# set anchor-pfes interface apfe1

      Note: You can set the anchor Packet Forwarding Engines individually if you do not have redundancy configured. For example, you can use pfe-4/1/0 and pfe-4/2/0.

    Published: 2011-11-22