User guide

Open Problem Reports and Feature Exceptions
OmniSwitch 6600/7000/8800—Release 5.1.6.R02 page 113
PR 77206
On an OS7000 series switch, during a takeover or failover, due to the IP Stack transition, some of the
messages may not be able to log to a remote device if one enables the syslog mechanism. This period may
be in the boundary of a second.
Workaround: There is no known workaround at this time.
PR 79063
Flash Synchronization is successful, but show running shows CMMs NOT SYNC when a new folder is
created in /working on an OS7000 series switch.
Workaround: Do not create other folders in the Working directory.
PR 79991
On OS6600 series switches, inserting an element with a different release may result in rendering some
elements unoperational.
Workaround: Only inserting the same version of software is supported. Upgrade the element(s) running
on a different release to the same release level of the stack in which the element(s) will be inserted.
PR 80356
On OS6600 series switches, flash synchronization may fail when a certified stack is connected to a non-
certified stack (Primary).
Workaround: Make sure both (working and certified) directories are certified before connecting them to
any stacks.
PR 84317
Do not reload the NIs on an OS6600 series switch, in case of takeovers with unsaved configurations due to
some limitations. The unsaved running configuration is still applied on the NIs, even though the new
primary cannot see that portion of the configuration update. Since the takeover did not reload this NI, the
applied group mobility rules are still in effect.
Workaround: Reboot the stack.
PR 85838
5.1.5.R03 releases and later are not backward compatible in terms of flash synchro with 5.1.5.R02 and
earlier releases.
Workaround: On dual CMM systems (7000 & 8800 series), once users have upgraded existing releases
to 5.1.5.R03 or later, they will have to downgrade each CMM individually if there is a need to downgrade
to 5.1.5.R02 or earlier. The individual CMMs will then need to be plugged together.