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]
Description
Configure the possible behavior for the aggregated Multiservices (AMS) interface in case of failure of more than one active member.
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 services PIC. Table 2 displays the behavior of the member interface after the failure of two services PICs.
The AMS infrastructure has been designed to handle one failure automatically. However, in the unlikely event that more than one services PIC fails, the AMS infrastructure provides configuration options to minimize the impact on existing traffic flows.
High Availability Mode |
Member Interface Behavior |
|---|---|
Many-to-one (N:1) high availability support for service applications |
Automatically handled by the AMS infrastructure |
High Availability Mode |
Configuration |
|
Behavior when member rejoins before |
Behavior when member rejoins after |
|---|---|---|---|---|
Many-to-one (N:1) high availability support for service applications |
|
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. |
Many-to-one (N:1) high availability support for service applications |
|
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. See CLI Explorer.
Default
If member-failure-options are not configured,
then the default behavior is to drop member traffic with a rejoin
timeout of 120 seconds.
Required Privilege Level
interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration.
Release Information
Statement introduced in Junos OS Release 11.4.
Support added in Junos OS Release 19.3R2 for Next Gen Services on MX Series routers MX240, MX480 and MX960 with the MX-SPC3 services card.