User guide
Open Problem Reports and Feature Exceptions
page 84 OmniSwitch 6600/7000/8800—Release 5.1.6.R02
PR 67882
The show qos queue command does not display Xmit or Drop Packets for any port queue on an OS6624/
6648 switch.
Workaround: There is no known workaround at this time.
PR 68472
OS6624 and OS6648 switches do not prioritize traffic on saturated half-duplex links, possibly allowing
data traffic through the phone to cause drops of voice traffic or signaling to the PCX. This happens only
when we have a PC connected through the phone, and have heavy PC traffic going through the IP phone.
Link is acting in accordance with CSMA/CD standards.
Workaround: There is no known workaround at this time.
PR 68550
When using link aggregation, one cannot use QoS with destination port slot/port or destination inter-
face type to match the traffic going through the link aggregation on the OS7000/8800. QoS only knows
the virtual port of the link aggregation, but does not know anything about the physical port that is used to
forward traffic.
Workaround: There is no known workaround at this time.
PR 68555
Every time one does a qos apply when the QoS configuration has changed, all traffic on an OS7000/8800
switch is disturbed. Basically, all hardware entries are flushed and all traffic goes to source learning again.
The switch throughput will drop for a short time (software speed instead of wire speed). This means that
some packets may be lost depending on the amount of traffic when the qos apply command is issued.
Workaround: There is no known workaround at this time.
PR 69252
Mibwalk fails in QoS mib at alaQoSPortGroups and alaQoSAppliedPortGroups because of lexicographic
failure on an OS6624/6648 switch.
Workaround: There is no known workaround at this time.
PR 72325
On an OS6624/6648 switch, if the TOS bit is set to 1, when the traffic comes into an untrusted port it does
not set the bit to 0. Packets coming in on untrusted ports will not be dropped. TOS bits will be set to 0 only
on L3 traffic. 802.1p bits will be set to 0 on L2 traffic.
Workaround: There is no known workaround at this time.