Configuring High Availability for the Services SDK

You can pair two Multiservices PICs in high availability mode using the virtual rms interface. As part of the configuration, one of the PICs is set as the primary and the other as the secondary PIC. When the rms interface comes up, the primary PIC comes up as active and the secondary PIC as standby.

On failure of the active PIC, the standby PIC becomes active and traffic is switched over to the new active PIC. When the failed primary PIC is restored, it comes up as standby. The network administrator must explicitly request a reversion to the primary PIC to make it active again. Otherwise, it continues in standby mode until the active PIC fails.

To create the rms interface, include the redundancy-options statement at the [edit interfaces interface-name] hierarchy level:

For the interface-name variable, specify the value rmsnumber, where number is in the range from 0 through 127.

Note: To bring up the rms interface, you must include the unit logical-unit-number family inet statement.

When a new rms interface is created, PICs designated as primary and secondary reboot automatically. When either the primary or secondary PIC, or both, are changed, the corresponding old and new ms- interfaces reboot automatically.

Note: The rms interface is also supported for service sets, class of service (CoS), and routes.

Related Topics

• Commands Supporting High Availability for Multiservices PICs