User guide

Open Problem Reports and Feature Exceptions
OmniSwitch 6600/7000/8800—Release 5.1.6.R02 page 45
PR 89608
On an OS6600 series switch, as per the design of the group mobility rule structure, creation of a DSAP-
SSAP rule is expected only for the non standard or custom defined DSAP SSAP values. For well known
DSAP SSAP values like IPX-SNAP, an IPX-SNAP rule should be configured.
Workaround: There is no known workaround at this time.
PR 89827
Network rule conflicts are not resolved or prevented at the CLI level. Conflicts are resolved only at run-
time on an OS6600 series switch.
Workaround: There is no known workaround at this time.
PR 90044
On an OS6600 series switch, it is possible to see a brief interruption in traffic flows once you add rules.
This is because all MACs are flushed in the anticipation that rule precedence change may potentially
affect the classification status of the learned MACs.
Workaround: There is no known workaround at this time.
PR 90081
On an OS6600 series switch, a runtime change in the IP address for a given MAC may result in the flow
being put in filtering for non-matching IP addresses. The MAC is learned on the right VLAN once the
filtering entry gets aged out.
Workaround: There is no known workaround at this time.
PR 90995
On an OS8800 switch, sometimes an error message "admin conf in NI for slot/port failed” may be
displayed after issuing the admin up or down command.
Workaround: Re-enter the admin up or down command.
PR 91437
Certain user defined rules end up classifying non-matching traffic patterns on the user defined VLAN
instead of the default VLAN on an OS6600 series switch.
Workaround: There is no known workaround at this time.