Filter
Top Products
Open Problem Reports and Feature Exceptions
page 54 OmniSwitch 6800/6850/9000—Release 6.1.3.R01
Bridging
Problem Reports
PR 86261
On an OS6800, Ethernet SNAP packets with non-zero Organizationally Unique Identifiers (OUI) will not
be classified using port-protocol rule.
Workaround: If applicable, other rules should be used to classify such packets.
PR 94269
The OmniSwitch 9000 counts all error packets as unicast packets in the packets received and error
counters, regardless of whether the packet is a unicast packet or a multicast packet. An oversized packet is
defined as a packet longer than 9216 bytes. This causes the following behavior in the switch:
1) Received packets longer than 9216 bytes are counted as unicast packets AND as error packets even if
the packet is a broadcast or multicast packet.
2) For ports operating at speeds of 10 Mbps or 100 Mbps, a packet is not counted as an error packet unless
it is longer than 9216 bytes.
Workaround: There is no known workaround at this time.
PR 94866
Invalid Packets with SA or DA set to all 0's continue to get bridged by the system.
Workaround: There is no known workaround at this time.
PR 99331
On an OS6800, when protocol or subnet based mobility rules are deleted and created after a VLAN delete,
the traffic coming in after this is not classified correctly.
Workaround: Delete the rule first before deleting the VLAN.
PR 99899
On an OS6800/OS6850, binding rules that require a port number to be specified as part of the rule can no
longer be deleted if the port is not set to be mobile.
Workaround: Make the port mobile before deleting the rule.