LSQ Failure Conditions and Constraints

Link Services IQ PIC failure occurs under the following conditions:

• The primary PIC fails to boot. In this case, the rlsq interface does not come up and manual intervention is necessary to reboot or replace the PIC, or to rename the primary PIC to the secondary one in the rlsq configuration.
• The primary PIC becomes active and then fails. The secondary PIC automatically takes over processing.
• A failover to the secondary PIC takes place. The secondary PIC then fails. If the primary PIC has been restored to active state, processing switches to it.
• The FPC that contains the Link Services IQ PIC fails.

The following constraints apply to redundant LSQ configurations:

• We recommend that primary and secondary PICs be configured in two different FPCs (in chassis other than M10i routers).
• You cannot configure a Link Services IQ PIC with explicit bundle configurations and as a constituent of an rlsq interface.
• Redundant LSQ configurations provide full GRES support. (You must configure GRES at the [edit chassis] hierarchy level; see the JUNOS System Basics Configuration Guide.
• If you configure the redundancy-options statement with the hot-standby option, the configuration must include one primary interface value and one secondary interface value. If you configure the warm-standby option, you can include multiple instances of the primary interface.
• Since the same interface name is used for hot-standby and warm-standby, if you modify the configuration to change this attribute, it is recommended that you first deactivate the interface, commit the new configuration, and then reactivate the interface.
• You cannot make changes to an active redundancy-options configuration. You must deactivate the rlsqnumber interface configuration, change it, and reactivate it.
• The rlsqnumber configuration becomes active only if the primary interface is active. When the configuration is first activated, the primary interface must be active; if not, the rlsq interface waits until the primary interface comes up.
• You cannot modify the configuration of lsq interfaces after they have been included in an active rlsq interface.
• All the operational mode commands that apply to rsp interfaces also apply to rlsq interfaces. You can issue show commands for the rlsq interface or the primary and secondary lsq interfaces. However, statistics on the link interfaces are not carried over following a Routing Engine switchover.
• The rlsq interfaces also support the lsq-failure-options configuration, discussed in Interchassis LSQ Failover. If the primary and secondary Link Services IQ PICs fail and the lsq-failure-options statement is configured, the configuration triggers a SONET APS switchover.
• Redundant LSQ configurations that require MLPPP Multilink Frame Relay (FRF.15 and FRF.16) are supported only with the warm-standby option.
• Redundant LSQ support is extended to ATM network interfaces.
• Channelized interfaces are used with FRF-16 bundles, for example rlsq0:0. The rlsq number and its constituents, the primary and secondary interfaces, must match for the configuration to be valid: either all must be channelized, or none. For an example of an FRF.16 configuration, see FRF-16 Configuration.

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

Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice.