Filter
Top Products
Open Problem Reports and Feature Exceptions
page 64 OmniSwitch 6800/6850/9000—Release 6.1.3.R01
PR 105788
Some STP entries in the 802.1D standard mib may return out of range or undefined values on an OS9000.
This is because we are returning the true values of a newer version of STP (802.1Q 2005), not 802.1D
1998 that the MIB is based on. When a new standard MIB is defined, we can obsolete the old version.
Workaround: There is no known workaround at this time.
PR 106106
STP may return a hello time of 0 on SNMP queries on disabled instances after an OS9000 has been
running for some time.
Workaround: There is no known workaround at this time.
PR 106513
On an OS9000, STP can display the wrong port as the next best port. The next best port is not actually
used in topology calculation and has no effect on the network.
Workaround: There is no known workaround at this time.
VLAN Stacking
Problem Reports
PR 102958
On an OS9000, setting SVLAN priority using "vlan svlan priority" command may not work properly.
Workaround: Use the QoS command to trust all VLAN Stacking ports, and use QoS policy to configure
SVLAN priority.
PR 106514
Deleting a large range of SVLANs will sometimes result in an STP error message about the SVLAN status
on an OS9000.
Workaround: Delete the SVLANs in a smaller range of VLANs.
PR 107054
An error message is received on an OS6850 console after assigning a range of tagged vlans to an aggre-
gate from CLI.
Workaround: This message can be ignored since it does not affect the actual assignment of the VLANs in
the range.