Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Configuring AS or Multiservices PIC Redundancy

You can configure AS or Multiservices PIC redundancy on M Series and T Series routers, except TX Matrix routers, that have multiple AS or Multiservices PICs. To configure redundancy, you specify a redundancy services PIC (rsp) interface in which the primary PIC is active and a secondary PIC is on standby. If the primary PIC fails, the secondary PIC becomes active, and all service processing is transferred to it. If the primary AS or Multiservices PIC is restored, it remains on standby and does not preempt the secondary PIC; you need to manually restore the services to the primary PIC. To determine which PIC is currently active, issue the show interfaces redundancy command.

Failover to the secondary PIC occurs under the following conditions:

  • The primary PIC, FPC, or Packet Forwarding Engine goes down, resets, or is physically removed from the router.

  • The PIC or FPC is taken offline using the request chassis pic fpc-slot slot-number pic-slot slot-number offline or request chassis fpc slot slot-number offline command. For more information, see the CLI Explorer.

  • The driver watchdog timer expires.

  • The request interface switchover command is issued. For more information, see the CLI Explorer.


Adaptive Services and Multiservices PICs in Layer-2 mode (running Layer 2 services) are not rebooted when a MAC flow-control situation is detected.


When you perform a switchover from a primary PIC to a secondary or standby PIC or a revert operation by issuing request interfaces (revert | switchover) command for redundancy services PICs (rsp), the PIC that was previously the active PIC before the switchover or reversion is automatically rebooted. The reboot of the PIC that was previously active and functioning as the primary PIC does not disrupt traffic forwarding.

The physical interface type rsp specifies the pairings between primary and secondary sp interfaces to enable redundancy. To configure an AS or Multiservices PIC as the backup, include the redundancy-options statement at the [edit interfaces rspnumber] hierarchy level:

For the rsp interface, number can be from 0 through 15.


You can include a similar redundancy configuration for Link Services IQ (LSQ) PICs at the [edit interfaces rlsqnumber] hierarchy level. For more information, see Configuring LSQ Interface Redundancy in a Single Router Using Virtual Interfaces.

The following constraints apply to redundant AS or Multiservices PIC configurations:

  • The services supported in redundancy configurations include stateful firewall, NAT, IDS, and IPsec. Services mounted on the AS or Multiservices PIC that use interface types other than sp- interfaces, such as tunneling and voice services, are not supported. For information on flow monitoring redundancy, see Configuring Services Interface Redundancy with Flow Monitoring.


    For IPsec functionality, the router no longer needs to renegotiate security associations (SAs) during warm standby PIC switchover. Instead, the warm standby feature has been made stateful by periodically setting a checkpoint between the working state of the PIC and the Routing Engine, which should lessen the downtime during switchover. If you prefer to retain the earlier behavior, you can include the clear-ipsec-sas-on-pic-restart statement at the [edit services ipsec-vpn] hierarchy level. If you enable this capability, the router renegotiates the IPsec SAs on warm standby PIC switchover. For more information, see Configuring Security Associations.

  • We recommend that you pair the same model type in RSP configurations, such as two ASMs or two AS2 PICs. If you pair unlike models, the two PICs may perform differently.

  • You can specify an AS or Multiservices PIC (sp interface) as the primary for only one rsp interface.

  • An sp interface can be a secondary for multiple rsp interfaces. However, the same sp interface cannot be configured as a primary interface in one rsp configuration and as a secondary in another configuration.

  • When the secondary PIC is active, if another primary PIC that is paired with it in an rsp configuration fails, no failover takes place.

  • When you configure an AS or Multiservices PIC within a redundant configuration, the sp interface cannot have any configured services. Apply the configurations at the [edit interfaces rspnumber] hierarchy level, using, for example, the unit and services-options statements. Exceptions include the multiservice-options statement used in flow monitoring configurations, which can be configured separately for the primary and secondary sp interfaces, and the traceoptions statement.

  • All the operational mode commands that apply to sp interfaces also apply to rsp interfaces. You can issue show commands for the rsp interface or the primary and secondary sp interfaces.

  • If a secondary PIC fails while it is in use, the rsp interface returns to the “ not present” state. If the primary PIC comes up later, service is restored to it.

  • For redundant Multiservices (rms-) interfaces, similar to the configuration of other bundle interfaces, the properties of the Multiservices (ms-) member interfaces, such as the logical unit and the address family, are inherited from the underlying rms- interface. If you previously configured the member ms- interface properties separately, and attempt to configure the rms- interface properties by using the relevant statements at the [edit interfaces rmsnumber] hierarchy level, an error occurs when you perform a commit check operation. You must configure the properties of interfaces that are part of the rms- interface only by using the statements at the [edit interfaces rmsnumber] hierarchy level.