User guide

Open Problem Reports and Feature Exceptions
page 104 OmniSwitch 6600/7000/8800—Release 5.1.5.R04
PR 72271
When building a new stack using up and running standalone units on an OS6624/OS6648, they system my
experience multiple unit reboots and takeovers which might leave the stack in an unstable state.
Workaround: Never connect together or add running standalone units to a stack. Always turn the standal-
ones off, connect them to the stack, and then turn them on.
PR 72648
The 5.1.4 boot.cfg file may not be compatible with earlier versions of code.
Workaround: Use the boot.cfg file of the earlier version of code.
PR 73037
If a port on the OS7000 is disconnected and reconnected while sending traffic from a traffic generator at a
high rate, the port does not become active until the traffic rate decreases.
Workaround: Stop the traffic for a moment before restarting the traffic generator.
PR 74724
The CPU utilization of the system remains high while the system is flushing a big number of IP addresses.
The CPU utilization returns to normal once the entire process is completed.
Workaround: There is no known workaround at this time.
PR 75615
On an OS6600, a "continuous Flash synchro" process may occur if the local "working" and "certified"
directories are not "Certified".
Workaround: When connecting stacks to other stacks, make sure individual stacks are synchronized
between themselves. That is, locally (Working and Certified) and within each module within current stack
environment.
PR 76349
On the OS7000, admin down on a port cannot bring down the link on the link partner. As a result, the link
partner can detect LINK UP or toggling UP and DOWN.
Workaround: There is no known workaround at this time.
PR 76500
Flash File System May be corrupted after Certify, Restore or Flash Synchro process.
Workaround: There is no known workaround at this time.