User guide

Open Problem Reports and Feature Exceptions
OmniSwitch 6600/7000/8800—Release 5.1.6.R02 page 71
PR 59599
The number of TCP reset does not match the number of SYN Request packets after doing a show tcp
statistics command on an OS7000 series switch.
Workaround: There is no known workaround at this time.
PR 67799
Performance may drop slightly below wire rate while routing small-sized packets on an OS6624/6648
switch.
Workaround: There is no known workaround at this time.
PR 71573
An OS6624/6648 switch does not support multiple router MAC address mode.
Workaround: If connecting an OS6624/6648 to an XOS box, make sure that only one port per IP VLAN
is physically connected between the two boxes. Otherwise, routing will not work.
PR 72943
The protocol processing on the OS6600 family of switches, includes the IP-SNAP protocol in the IP
Ethernet protocol set. That means, if a protocol rule for ip-e2 exists with an ip-snap protocol rule on the
same switch, the ip-snap rule will be disregarded.
The OS7000 series switches do process ip-e2 and ip-snap protocols separately.
Workaround: Use an IP network address rule instead of an IP protocol rule in conjunction with an ip-
snap protocol rule, if possible.
PR 73015
The IP ETHERNET 2 protocol and the IPX ETHERNET 2 protocols cannot be associated with the same
MAC address in two separate mac-port-protocol rules (using the same port is assumed). Either one or the
other protocol's traffic will flow, but not both on an OS7000 series switch.
Workaround: Use only a mac-port-protocol rule with either IP or IPX, or go to a less restricted rule like
port-protocol or protocol rule.
PR 74184
Router-ID does not respond to ping. This feature is frequently referred to as a loopback interface and is
not available in the current release. The "router-id" and "primary-address" configuration commands are
strictly used by the routing protocols for unique router identification.
Workaround: There is no known workaround at this time.