User guide

Open Problem Reports and Feature Exceptions
page 84 OmniSwitch 6600/7000/8800—Release 5.1.5.R04
PR 68472
OS6624 and OS6648 does not prioritize traffic on saturated half-duplex links, possibly allowing data traf-
fic through the phone to cause drops of voice traffic or signaling to the PCX. This happens only when we
have PC connected through 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 the OS7000/8800
will be 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 68849
Policy->Groups->Ports does not display all built-in port groups.
Workaround: There is no known workaround at this time
PR 68906
Sometimes, all the policies do not flush. This applies on all platforms.
Workaround: Issue the policy server flush command from the command line to delete all the policies.
PR 69252
Mibwalk fails in QOS mib at alaQoSPortGroups and alaQoSAppliedPortGroups because of lexicographic
failure on an OS6624/6648.
Workaround: There is no known workaround at this time.