3Com Router 5000 and Router 6000 Family Release Notes v2.41 • Page 6
2.1 Software Issues Resolved Since v2.30/2.31 The following issues have been resolved since the v2.30/2.31 release of this software.
• VCX calls fail across a NAT network.
• NBX phones fail to load across a NAT network.
• IPX is now supported on Frame Relay, Ethernet and PPP. IPX is not supported on, HDLC, and
X25.
• When setting the main/backup images, the file pointer does not point to flash:/ by default;
the flash device must be included in the path; for example, bootfile main flash:/main.bin
rather than just bootfile main main.bin.
• When there is a high traffic load on the router, and the CLI response time slows, the CPU
usage information is not accurately displayed.
• Gigabit Ethernet and POS interfaces do not support auto-install.
• SYS MGMT — Router 5000 series routers report that the system returned to service via
“power-on” even if the router is warm booted.
• IPSEC policy with a deny rule before a more general permit rule will not enforce the deny
rule.
• Resetting the IKE SA does not reset the tunnel completely; Resetting both sides at the same
time is currently required to completely reset the tunnel.
• IPSec tunnel resets (resetting IKE SA/IPSec SA) may result in router reboot.
• CBR traffic approaching PCR on a PVC will experience packet loss when UBR traffic on a
separate PVC is introduced on the ATM link
• Service classes on IMA group interfaces have cell rate limits of just one T1/E1 Link regardless
of how many links are in the bundle.
2.2 Software Issues Resolved from v2.11 The following issues have been resolved since the v2.11 release of this software.
• In some specific circumstances, displaying virtual-access on a router with MLPPP may cause a
reboot. To resolve this, use the command, Display Virtual Template instead.
• A virtual baud rate setting of 786000 is not available on a serial interface.
• The state of Promiscuous mode on an Ethernet interface is not shown in the “display
current” command. To view the state of Promiscuous mode, use the “display interface
Ethernet x/x” command.
• Gigabit Ethernet interfaces will not forward traffic if they are assigned to a bridge-set.
Gigabit interfaces should only be assigned to routed interfaces.
• When a bridge-set is removed from an Ethernet interface the message “Promiscuous
operation mode was removed automatically” is displayed. However, promiscuous mode may
not have been disabled on that interface. Manually verify that Promiscuous mode has been
reset using the “display interface Ethernet x/x” command. If it has not been disabled, use
the “undo promiscuous” command in the interface view.
• There is no support for ISDN switch type DMS100.
• Frame Relay sub-interface definition types (P2MP, P2P) are not displayed. To determine the
interface type, display the interface as follows: “Display fr pvc interface <interface> <dlci>.”