User guide

Open Problem Reports and Feature Exceptions
OmniSwitch 6600/7000/8800—Release 5.1.5.R04 page 85
PR 72325
On the OS6624/6648, 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.
PR 73767
On an OS7000/8800, when setting a permanent MAC address to filtering, traffic going to this MAC will
always be dropped regardless of the qos rules (even if one permit rule match this mac). When setting a
permanent MAC address to bridging, traffic going to this MAC will always be accepted at best effort,
regardless of the qos rules. Therefore it becomes impossible to set any priority, stamping/mapping or
bandwidth shaping actions for traffic going to this MAC address.
Workaround: There is no known workaround at this time.
PR 74062
On an OS6624/6648 system, it is not possible to create an L3 ACL on a source and another on a destina-
tion because currently the it cannot link up source and destination.
Workaround: There is no known workaround at this time.
PR 76509
In some cases a bogus "time change detected" message is displayed in the policy server event log.
Workaround: There is no known workaround at this time.
PR 76901
The OmniSwitch 6624/6648 5.1.4.R01 configuration file is not compatible with 5.1.5.R01 and 5.1.5.R03.
Workaround: Edit the boot.cfg file.
PR 80707
QoS rules have no "matches" after 2 takeovers
Workaround: The match count shown from the CLI currently reflects only newly created flows/matches.
On a takeover, if the flows aren't flushed and re-learned, the match counts will remain 0 on the secondary
until new flows are matched (or the old ones time out and are re-learned).
PR 81351
Layer 2 P-Stamping rules are not supported on OS6600 series Link Aggregation ports.
Workaround: There is no known workaround at this time.