User guide

Open Problem Reports and Feature Exceptions
OmniSwitch 6600/7000/8800—Release 5.1.5.R04 page 65
PR 76688
Path cost of 0 is mistakenly allowed to configure a port on the OS7000.
Workaround: Do not use path cost 0.
PR 76951
'Show Spantree' command still displays some values in the 'Path Cost', 'Op Cnx', and 'Designated Bridge
ID' columns for a port when it is down.
Workaround: If the port's 'Operating Status' Column shows DIS (for disabled), just ignore the values for
the rest of other columns. These values are being displayed to show the past connection history of the path
cost, connection type and Bridge ID etc.
PR 77228
When running scripts using automation tools to configure an OS7000 from 1d protocol to 1w, the STP
seems to be stuck in blocking state for a certain VLAN in 1w protocol.
Workaround: Executing commands manually or from the boot.cfg file to switch protocols works OK. In
case this problem occurs, try switching STP modes: bridge mode flat and then bridge mode 1x1 to see if
this problem goes away.
PR 77262
When running scripts using automation tools to configure STP on a stand-alone OS6600 stack, it's
observed that the CPU Utilization could go up to 100% after changing the bridge protocol from 1d to 1w.
The STP task seems to be stuck in a loop forever, causing the CPU utilization to go up.
Workaround: Manually typing in the commands to switch protocols and configure STP works OK. In
addition, executing the same commands in boot.cfg file also work OK.
PR 81949
On the OS8800, in flat mode, the default path cost value for a link agg port is being used instead of the
new path cost value in the configuration file after the switch as booted up. (It seems like any new path cost
value in the thousand range is more likely to experience this problem).
Workaround: Manually re-configure the path cost again for the link agg port after the switch has booted
up.
PR 84258
When Spanning Tree bridge parameters are changed for a group of VLANs at the same time repeatedly, it
might lead to Spanning Tree loop for some VLANs on an OS8800.
Workaround: There is no known workaround at this time.