User guide

Open Problem Reports and Feature Exceptions
OmniSwitch 6600/7000/8800—Release 5.1.5.R04 page 73
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.
PR 75002
There is no provision to configure per Vlan IP MTU on an OS6624/6648. As a result, once the flow is
setup on the OS6624/6648 (meaning both the Src/Dest addresses are learned), if a packet violating the IP
MTU is received, it will still be forwarded by the hardware. IP MTU checking is done in software, so it
will work for the first packet (that comes to software), i.e. for the first packet, the switch will send back an
appropriate ICMP response.
Workaround: There is no known workaround at this time.
PR 75244
When OS6624/6648 is configured for layer 3 routing, the servers with "teamed" or load balanced ports is
currently only supported with the 802.3ad service configured on the switch.
Workaround: There is no known workaround at this time.
PR 79799
On OS6600 series switches, an OSPF route cannot be redistributed into Rip when there exists a Static
route in the IP Routing Table for the same destination, same metric and same next-hop as the Ospf route.
Workaround: There is no workaround for this issue. Only one of the two routes - Ospf route and Static
route - may be used in the IP Routing Table. Hence, the configuration of the network should be such that
routes of only one protocol - static or dynamic - exist at exist at any time in the IP Routing Table for the
same destination and with the same next-hop.
PR 79931
On OS6600 series switches, when a Static and an OSPF route exist for the same destination and with the
same next-hop and metric and if both the Static and OSPF routes are redistributed into Rip with the order
being Static config specified first and then OSPF (as specified in the config file), then Static routes are
redistributed into Rip.
Workaround: There is no workaround for this issue. The limitation is that at a time, there should be only
one kind of route existing for a destination in the OS6600 series IP Routing Table.