Q-NOTE QN-7000HX User's Guide Page 72

  • Download
  • Add to my manuals
  • Print
  • Page
    / 115
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 71
Open Problem Reports and Feature Exceptions
page 72 OmniSwitch 6600/7000/8800—Release 5.1.6.R02
PR 75002
There is no provision to configure per VLAN IP MTU on an OS6624/6648 switch. 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 an OS6624/6648 switch is configured for layer 3 routing, the servers with "teamed" or load
balanced ports are currently only supported with the 802.3ad service configured on the switch.
Workaround: There is no known workaround at this time.
PR 79799
On the OS6600 series switches, an OSPF route cannot be redistributed into RIP when a Static route exists
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. Therefore, the configuration of the network should be such
that routes of only one protocol - static or dynamic - 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, with the same
next-hop and metric; and, if both the Static and OSPF routes are redistributed into RIP with the order
being Static configuration specified first, OSPF (as specified in the configuration file), and 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.
PR 80049
When a RIP v1 interface on one OS6600 series router connects to a RIP v2 interface on another OS6600
router, then RIP v1-based host-routes will be created by the RIP v1 router for each of the existing RIP v2
routes and added to the IP Routing Table. These will then be aged out after reaching metric 16 and then
removed. This is done periodically once in every 4 or 5 minutes. This happens since host-route support is
not disabled by default on the RIP v1 or RIP v2 routers.
Workaround: The host-route support should be disabled on each of the RIP v1 or v2 routers. The host-
routes will no longer be generated.
Page view 71
1 2 ... 67 68 69 70 71 72 73 74 75 76 77 ... 114 115

Comments to this Manuals

No comments