3Com 4007 Release Note

Also see for 4007: Getting started guide Important notice Command reference guide Implementation guide Product guide

Contents

3Com 4007 Release Note Manual pdf 84 page image

84 CHAPTER 6: RELEASE ISSUES FOR M ULTILAYER S WITCHING MODULESVirtual RouterRedundancy Protocol(VRRP)n You can remove a Virtual Router (VR) through the Web Managementinterface without disabling VRRP. The system does not recognize thechange for a few polling intervals. For most networks, the systemrecognizes the change in only a few seconds. Any possible networkoutage should last only a few seconds. (29940)n In rare instances VRRP routers transfer between backup and master,and then back to the Backup state. There is no adverse effect on theoriginal Master VRRP router; and after the state changes of theBackup, the original Master continues to function as expected. Thishas occurred in test environments only where heavy levels of traffic ina continuous stream are injected. (30410, 30665, 30438)IP Multicast n IP Multicast traceRoute does not work if one router hop furtherdownstream of the router with tunnels defined. (29564)n 3Com recommends that you use VLAN-based IP interfaces with STPenabled rather than port-based IP interfaces in IP networks that useDVMRP as the multicast routing protocol when these networks havephysical loops in them. Because port-based IP interfaces ignore theSTP state, a port-based IP interface that appears to be blocking trafficis really forwarding traffic. Using DVMRP and STP ensures that thephysical loops in the network are removed from the IP Multicast trafficflow.IPX n The ipx server display screen shows only up to 19 characters of anIPX server’s name. Novell specifies that a server name can be up to 48characters. (28021)QoS n The QoS control with 802.1p tag on flow class is not used inforwarded frames. A nonflow classifier must be used for this option.n For cyclical QoS control timers, the output edit displays the start timefor the next time period that the control becomes active. (27272)n If you classify traffic as IPX non-custom (for example, classifier 460) oras custom, then adding a drop control has no effect unless anunderlying IPX-II VLAN is present. (27678)n In the qos statistics receive display, one-way-flow droppedpackets appear in the dropped field, but they also appear erroneouslyin the NonFlowReserved field. (29297)