Virtual Router Redundancy Protocol (Vrrp); Ip Multicast; Ipx; Qos - 3Com 4007 Release Note

84 C 6: R I M S M
HAPTER ELEASE SSUES FOR ULTILAYER WITCHING ODULES
Virtual Router You can remove a Virtual Router (VR) through the Web Management
Redundancy Protocol interface without disabling VRRP. The system does not recognize the
(VRRP) change for a few polling intervals. For most networks, the system
recognizes the change in only a few seconds. Any possible network
outage should last only a few seconds. (29940)
In rare instances VRRP routers transfer between backup and master,
and then back to the Backup state. There is no adverse effect on the
original Master VRRP router; and after the state changes of the
Backup, the original Master continues to function as expected. This
has occurred in test environments only where heavy levels of traffic in
a continuous stream are injected. (30410, 30665, 30438)

IP Multicast

IP Multicast traceRoute does not work if one router hop further
downstream of the router with tunnels defined. (29564)
3Com recommends that you use VLAN-based IP interfaces with STP
enabled rather than port-based IP interfaces in IP networks that use
DVMRP as the multicast routing protocol when these networks have
physical loops in them. Because port-based IP interfaces ignore the
STP state, a port-based IP interface that appears to be blocking traffic
is really forwarding traffic. Using DVMRP and STP ensures that the
physical loops in the network are removed from the IP Multicast traffic
flow.

IPX

The screen shows only up to 19 characters of an
ipx server display
IPX server's name. Novell specifies that a server name can be up to 48
characters. (28021)

QoS

The QoS control with 802.1p tag on flow class is not used in
forwarded frames. A nonflow classifier must be used for this option.
For cyclical QoS control timers, the output edit displays the start time
for the next time period that the control becomes active. (27272)
If you classify traffic as IPX non-custom (for example, classifier 460) or
as custom, then adding a drop control has no effect unless an
underlying IPX-II VLAN is present. (27678)
In the display, one-way-flow dropped
qos statistics receive
packets appear in the dropped field, but they also appear erroneously
in the NonFlowReserved field. (29297)