User guide

Open Problem Reports and Feature Exceptions
OmniSwitch 6600/7000/8800—Release 5.1.6.R02 page 111
CMM Redundancy / Hot Swap Feature Exceptions
• If you do a write memory, and do not do a certify (copy working certified) before doing a takeover or
reload primary, you will lose the boot.cfg contents because the secondary will do an automatic
restore (copy certified working) when it comes up as the secondary. This allows it to be ready for
failovers.
Redundancy / Hot Swap
Problem Reports
PR 54530
An uncontrolled power down could potentially cause an OS7000 CMM to fail.
Workaround: There is no known workaround at this time.
PR 62403
Voice conversation drops and IP phones directly connected to an OS7000 series switch may reboot when a
takeover of CMM is issued.
Workaround: Wait until the NI is not busy before hot swapping to avoid this situation.
PR 62534
If a takeover is done after uploading a new boot.cfg file, both the OS7000 CMMs could end up trying to
be the primary CMM upon doing reloads.
Workaround: Whenever a new boot.cfg file is loaded in the working directory, the reload working no
rollback-timeout command has to be issued. This ensures that the NIs are properly reloaded and the new
configurations are sent to the NIs.
PR 66098
The user may see the following message on bootup: "CSM_P1_4 - csCsmCmmCtx.cmmState = 9" on an
OS7000 series switch. This is an informational message indicating that a timeout has occurred during
system bootup.
Workaround: There is no known workaround at this time.
PR 67150
If modules are in the middle of a Flash Synchronization, and a takeover process is issued (both from the
user or from SM detection), stacks will get into an unstable condition.
Workaround: DO NOT perform (manually) a takeover while Flash Synchronization is in progress.