User guide

Open Problem Reports and Feature Exceptions
page 114
Redundancy / Hot Swap
CMM Redundancy Feature Exceptions for OmniSwitch 7000/8800
• Manual invocation of failover (by user command or Primary pull) should only be done during times
when traffic loads are minimal.
• Hot standby redundancy or failover to a secondary OS7000/8800 CMM without significant loss of traf-
fic is only supported if the secondary is fully flash synchronized with the contents of the primary’s
flash.
• Hot standby redundancy or failover to a secondary module without significant loss of traffic is only
supported if all the remaining units in the stack are fully flash synchronized with the contents of the
primary’s flash.
• Failover/Redundancy is not supported when the primary and secondary CMMs are not synchronized
(i.e. unsaved configs, different images etc.). In this case, upon failover, all the NIs will reset and might
go to "down" state and to recover need to power down the switch and power it back up.
Hot Swap Feature Exceptions for OmniSwitch 7000/8800
• Hot swap of NIs needs to be preceded by the removal of all cables connected to the NI.
• Hot insertion of unlike modules is not supported in this release. Support is planned in next mainte-
nance release.
• The Reload NI command is not supported in this release. Please use No Power NI/Power NI as an
alternative.
• All insertions of NI modules cannot be followed by another hot swap activity until the OK2 LED on
the inserted NI blinks green.
Hot Swap Feature Exceptions for OmniSwitch 6600
• When removing modules from the stack (powering off the module and/or pulling out its stacking
cables), the loop back stacking cable must be present at all times to guarantee redundancy. If a module
is removed from the stack rearrange the stacking cables to establish the loopback before attempting to
remove a second unit.
• When inserting a new module in the stack, the loop back has to be broken. Full redundancy is not guar-
anteed until the loop back is restored.
• When inserting a new module in the stack, make sure that the new element is synchronized by itself.