Users Guide

redundancy auto-failover-limit
• Re-Enable the auto-failover-limit with its default parameters.
CONFIGURATION mode
redundancy auto-failover-limit
(no parameters)
Disabling Auto-Reboot
To disable auto-reboot, use the following command.
• Prevent a failed stack unit from rebooting after a failover.
CONFIGURATION mode
redundancy disable-auto-reboot
Manually Synchronizing Management and Standby Units
To manually synchronize Management and Standby units at any time, use the following command.
• Manually synchronize Management and Standby units.
EXEC Privilege mode
redundancy synchronize full
Pre-Configuring a Stack Unit Slot
You may also pre-configure an empty stack unit slot with a logical stack unit.
To pre-configure an empty stack unit slot, use the following command.
• Pre-configure an empty stack unit slot with a logical stack unit.
CONFIGURATION mode
stack-unit unit_id provisionS4048–ON
After creating the logical stack unit, you can configure the interfaces on the stack unit as if it is present.
Removing a Provisioned Logical Stack Unit
To remove the line card configuration, use the following command.
• To remove a logical stack-unit configuration, use the following command:
CONFIGURATION mode
no stack-unit unit_id provision
Hitless Behavior
Hitless is a protocol-based system behavior that makes a stack unit failover on the local system transparent to remote systems. The
system synchronizes protocol information on the Management and Standby stack units such that, in the event of a stack unit failover, it is
not necessary to notify the remote systems of a local state change.
Hitless behavior is defined in the context of a stack unit failover only.
• Only failovers via the CLI are hitless. The system is not hitless in any other scenario.
Hitless protocols are compatible with other hitless and graceful restart protocols. For example, if hitless open shortest path first (OSPF) is
configured over hitless the link aggregation control protocol (LACP) link aggregation groups (LAGs), both features work seamlessly to
deliver a hitless OSPF-LACP result. However, to achieve a hitless end result, if the hitless behavior involves multiple protocols, all protocols
must be hitless. For example, if OSPF is hitless but bidirectional forwarding detection (BFD) is not, OSPF operates hitlessly and BFD flaps
upon an RPM failover.
The following protocols are hitless:
304
High Availability (HA)