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

    interfaces (Aggregated Packet Forwarding Engine)

    Syntax

    interfaces interface-name {anchoring-options {apfe-group-set apfe-group-set;primary-list {[anchoring-device-name];}secondary anchoring-device-name;warm-standby;}}

    Hierarchy Level

    [edit]

    Release Information

    Statement introduced in Junos OS Mobility Release 11.2W.

    Description

    Configure the aggregated Packet Forwarding Engine interface (apfe) used for anchor Packet Forwarding Engine redundancy on the mobile broadband gateway.

    The type of redundancy supported is many-to-one (N:1), which means that one Packet Forwarding Engine acts as the backup for one or more (N) Packet Forwarding Engines. When you configure Flexible PIC Concentrators (FPCs) for anchor Packet Forwarding Engine redundancy, the corresponding anchor Packet Forwarding Engines in each FPC are configured for N:1 redundancy. The first Packet Forwarding Engine of each primary FPC is backed up by the first Packet Forwarding Engine of the backup FPC, the second Packet Forwarding Engine of each primary FPC is backed up by the second Packet Forwarding Engine of the backup FPC, and so on.

    Note: The interfaces must be valid apfe interfaces; for example, apfe0 or apfe1.

    The remaining statements are explained separately.

    Options

    interface-name

    Name of the aggregated Packet Forwarding Engine interface (ams); for example, apfe0 or apfe1, and so on.

    Required Privilege Level

    interface—To view this statement in the configuration.

    interface-control—To add this statement to the configuration.

    Published: 2011-06-28