Download Print this page

3Com Router 3012 Release Note page 2

Router 3000 series, router 5000 series
Hide thumbs Also See for Router 3012:

Advertisement

4. The 'info-center logbuffer filter' command supports four new filter parameters,
L2TP, EC (encryption card), IPSEC, and IKE.
Bugs Fixed in this Release
System/Interface:
• Previously, the router would forward packets with a field length set to zero across
the T1 WAN interface. This would cause the router receiving these packets to
reboot. In the current release, the router checks the field length of outbound
packets and drops any with a field length of zero.
• In the past, a user would not be able to access the system file if a remote upgrade
operation did not complete successfully. For example, if the user did not respond
to the 'writing to flash' query before the telnet session timed out, no user at any
location would be able to access the system file. The only way around this was to
reboot the router.
• In earlier releases, it is possible for the 301x router to run out of memory. The
system would fail to login via telnet and the 'display current' command would fail
with insufficient memory error.
• Previously, if a combination of eight MIM cards were installed in the 5680 device
simultaneously, the device would be unable to boot up.
• In earlier releases, the system clock would revert back to GMT settings when the
router underwent a reboot operation.
Link Layer/Network Protocol:
• In earlier releases, the router 5680 would corrupt UDP packets from the LAN
Bridge-set 2 to the WAN bridge-set1. The corrupted packets were layer 3
broadcast packets, including DHCP requests.
• In previous releases, the router would not place ARP responses in the ARP cache
when it was configured in bridge mode and IP routing mode. An ARP request
from the router to the client would be entered in the cache as all zeros. Therefore,
it was not possible to manage the router until the client pinged the router. In this
release, the router creates the correct ARP entry in the ARP cache.
• In earlier releases, ISDN would not work with Lucent 5 (AT&T 5ESS), or
National ISDN. This was because there was no support for North American
switch types for T1 PRI interfaces.
http://www.3com.com/
Part No.
10014533
Published August 2004
2

Advertisement

loading