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

    member-failure-options (Aggregated Multiservices)

    Syntax

    member-failure-options {drop-member-traffic {rejoin-timeout rejoin-timeout;}redistribute-all-traffic {enable-rejoin;}}

    Hierarchy Level

    [edit interfaces interface-name load-balancing-options]

    Release Information

    Statement introduced in Junos OS Mobility Release 11.2W.

    Description

    Configure the possible behavior for the aggregated multiservices (AMS) interface in case of failure of more than one active member.

    Note: The drop-member-traffic configuration and the redistribute-all-traffic configuration are mutually exclusive.

    Table 1 displays the behavior of the member interface after the failure of the first multiservices PIC. Table 2 displays the behavior of the member interface after the failure of two multiservices PICs.

    Note: The AMS infrastructure has been designed to handle one failure automatically. However, in the unlikely event that more than one multiservices PIC fails, the AMS infrastructure provides configuration options to minimize the impact on existing traffic flows.

    Table 1: Behavior of Member Interface After One Multiservices PIC Fails

    High Availability Mode

    Member Interface Behavior

    One-to-one (1:1) mobile control plane redundancy

    Automatically handled by the AMS infrastructure

    Many-to-one (N:1) high availability support for service applications

    Automatically handled by the AMS infrastructure

    Table 2: Behavior of Member Interface After Two Multiservices PICs Fail

    High Availability Mode

    Configuration

    rejoin-timeout

    Behavior when member rejoins before rejoin-timeout expires

    Behavior when member rejoins after rejoin-timeout expires

    One-to-one (1:1) mobile control plane redundancy

    drop-member-traffic

    Configured

    The traffic is dropped since both members are down.

    The first member to rejoin becomes the active member. The second member to rejoin becomes the backup. This behavior is handled automatically by the AMS infrastructure.

    The traffic is dropped since both members are down.

    The first member to rejoin becomes the active member, and the second member to rejoin is moved to the discard state. An explicit request interface load-balancing revert command is required to make the second member rejoin the AMS.

    One-to-one (1:1) mobile control plane redundancy

    redistribute-all-traffic

    Not applicable

    The traffic is dropped since both members are down.

    The first member to rejoin becomes the active member. The second member to rejoin becomes the backup. This behavior is handled automatically by the AMS infrastructure.

    Many-to-one (N:1) high availability support for service applications

    drop-member-traffic

    Configured

    The existing traffic for the second failed member will not be redistributed to the other members.

    The first member to rejoin becomes an active member. The second member to rejoin becomes the backup. This behavior is handled automatically by the AMS infrastructure.

    The existing traffic for the second failed member will not be redistributed to the other members.

    The first member will rejoin the AMS automatically. However, the other members who are rejoining will be moved to the discard state. An explicit request interface load-balancing revert command is required to make these members rejoin the AMS.

    Many-to-one (N:1) high availability support for service applications

    redistribute-all-traffic

    Not applicable

    Before rejoin, the traffic is redistributed to existing active members.

    After a failed member rejoins, the traffic is load-balanced afresh. This may impact existing traffic flows.

    The remaining statements are explained separately.

    Default

    If member-failure-options are not configured, then the default behavior is to drop member traffic with a rejoin timeout of 120 seconds. If the member does not come back online within this time, then it must be manually brought back into the AMS interface, using the request interface load-balancing revert command.

    Required Privilege Level

    interface—To view this statement in the configuration.

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

    Published: 2011-11-22