User guide

Open Problem Reports and Feature Exceptions
page 115
Hot Swap Time Limitations for OmniSwitch 7000/8800
• All removals of NI modules must have a 30 second interval before initiating another hot swap activity.
• All insertions of NI modules must have a 3 minute interval before initiating another hot swap activity.
• All hot swaps of CMM modules must have a 10 minute interval before initiating another hot swap,
reload or takeover activity.
• All takeovers must have a 10 minute interval before following with another hot swap, reload or take-
over activity.
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 the OS7000 CMM to fail.
Workaround: There is no known workaround at this time.
PR 62355
The Feni.img image is not listed as loaded microcode on the secondary CMM, nor will it be on the
primary CMM after takeover on OS7000’s. This should not affect the functionality of the switch.
Workaround: There is no known workaround at this time.
PR 62403
Voice conversation drops and IP phones directly connected to OS7000 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 into the working directory, the reload working no
rollback-timeout command has to be issued. This insures that the NIs are properly reloaded and the new
configurations are sent to the NIs.