3Com Router 3012 Release Note - Page 3

Browse online or download pdf Release Note for Network Router 3Com Router 3012. 3Com Router 3012 7 pages. Router 3000 series, router 5000 series
Also for 3Com Router 3012: Release Note (7 pages)

Print Page

• Previously, the LAN Ethernet port would hang if you used the bridged

configuration at approximately 80% load. The user would need to manually shut

down and restart the port, or reboot the router, in order to fix this problem.

• It was observed that a 5680 device routing to five remote 3016 devices would

reboot spontaneously. The router experienced PCI write error under heavy traffic

load when the router was fully populated with E1 interface modules.

• In previous releases, the router 5231 was unable to route IP, and bridge other

protocols.

• Previously, the 5009 routers would not answer incoming BRI calls with switches

that required channel ID to be present in a setup message.

• In earlier releases, the ISDN BRI U interface did not interoperate with the DMS-

100 National ISDN configuration in the 3015 router.

• Previously, the router would sometimes reboot when you changed a link from

MFR to MP.

• In the past, the DHCP 'option' commands were not saved with the 'save'

command. Therefore, it was not maintained after a reboot and would need to be

re-entered. The 'option' command now supports values up to 64 bytes.

Routing Protocol:

• Previously, the router would reboot when the user tried to use more than 15,000

BGP routes. In the current release, the router limits the number of BGP routes to a

maximum of 15,000 routes.

• In previous releases, if you used 'the default-local-pref' command with a value

other than 100, the router would convert this value back to 100 after a reboot

operation.

Security:

• This release contains a fix for the NISCC Vul/236929 TCP vulnerability, which

was released on April 20th, 2004. For more information on this vulnerability,

refer to the NISCC-CERT advisory link at:

http://www.uniras.gov.uk/vuls/2004/236929/index.htm

• In previous releases, the TACAS+ authentication scheme would not attempt the

secondary authentication method (LOCAL) after the first defined authentication

method failed.

http://www.3com.com/

Part No.

10014533

Published August 2004