Router 3000/5000 Series

Release Notes for V1.10

http://www.3com.com/ Part No. 10014223 Published October 2003

Contents
Chapter 1 Introduction ............................................................................................................................. 3

1.1. Scope ................................................................................................................................................................... 3 1.2. Cable Connections ............................................................................................................................................... 3 1.3. Online Resources................................................................................................................................................. 3
Chapter 2 Release Notes for the Router 3000 and Router 5000 Series V1.10 ....................................... 4

2.1. System Access..................................................................................................................................................... 4 2.2. System Management ........................................................................................................................................... 4 2.3. Interface Management ......................................................................................................................................... 5 2.4. Link Layer Protocol............................................................................................................................................... 5 2.5. Network Protocol .................................................................................................................................................. 5 2.6. Routing Protocol................................................................................................................................................... 6 2.7. Multicast Protocol ................................................................................................................................................. 6 2.8. Security ................................................................................................................................................................ 7 2.9. VPN ...................................................................................................................................................................... 7 2.10. QoS .................................................................................................................................................................... 7 2.11. Dial-Up ............................................................................................................................................................... 7

Chapter 1 Introduction
1.1. Scope
These release notes summarize operational requirements and issues for the following Router 3000 and Router 5000 modules and software release V1.10. Read these release notes before installing your router. Table 1 Router Model Numbers
Description 3C Number

3Com Router 3012 3Com Router 3013 3Com Router 3016 3Com Router 5009 3Com Router 5231 3Com Router 5640 3Com Router 5680

3C13612 3C13613 3C13616 3C13700 3C13750 3C13754 3C13758

1.2. Cable Connections

3Com recommends that you power off the router before connecting any cable. Do not connect and disconnect synchronous or asynchronous serial WAN cables, console cables, Ethernet cables, ISDN BRI cables, and 4-port serial WAN adapters while power to the router is on. Connnecting cables while power to the router is on can crash the router or damage the serial port.

1.3. Online Resources

3Com routers contain a software agent that can be upgraded using the command line interface. The software agent that is initially provided with the routers does not fully support GRE, L2TP, IPSec, or SNMPv3. To download a software agent that adds full support for these features, visit the 3Com support website at http://support.3com.com to register your product. Note that this download agent contains encryption capabilities that are restricted to certain users and countries so approval for these downloads can take up to 48 hours. To upgrade to future software agents that contain additional features, you must purchase a service contract. Details are provided on the Service and Warranty pages of the 3Com support website http://support.3com.com . See the Router 3000 Installation Guide or Router 5000 Installation Guide for software download instructions. Download the Router 3000 Installation Guide from: http://support.3com.com/infodeli/tools/routers/R3000Install.pdf Download the Router 5000 Installation Guide from: http://support.3com.com/infodeli/tools/routers/5000Install.pdf Download the 3Com Router Command Reference Guide from: http://support.3com.com/infodeli/tools/routers/3ComRouterComRef.pdf Download other current software updates and release notes from: http://www.3com.com/

Chapter 2 Release Notes for the Router 3000 and Router 5000 Series V1.10
This chapter offers updates on Router 3000 and Router 5000 features in the following areas:

System Access System Management Interface Management Link Layer Protocol Network Protocol

Routing Protocol Multicast Protocol Security VPN QoS

Dial-Up

2.1. System Access

Symptom Solution

A user, logging in as an operator, can see administrator passwords.

Use encrypted passwords instead of simple passwords.

2.2. System Management

Symptom Solution

If you add or remove a module, the configuration may be altered.

The router reboots if an invalid agent software file is used to upgrade the device.

RMON MIB tables can be created on an Ethernet interface on which RMON is disabled, but no data is collected. RMON history bucket allocation fails if more than 50 buckets are requested. RMON Matrix DS table has src and dst addresses reversed. Routers are not recognized by Network Management applications, such as 3Com Network Supervisor, unless SNMP V1 is enabled.

Save the configuration file and edit it with the new interface numbers so that the file corresponds with the new physical configuration. Insure that the correct agent file has been used before writing to flash memory. Use Xmodem or TFTP to upgrade and recover the device. Enable RMON on interfaces being used for monitoring. Insure no more than 50 buckets are requested when creating an RMON history table. Use the SD table instead. Enable SNMP V1 on the device, as described in the Installation Guide, and then discover the network using Network Supervisor.

R E L E A S E

N O T E S

F O R

T H E

R O U T E R 3 0 0 0 V 1 . 1 0

A N D

R O U T E R

5 0 0 0

S E R I E S

2.3. Interface Management

Symptom Solution

Interface changes may require a reset of the interface for changes to take effect. The error message for deleting a PRI is incorrect. Dialer interfaces do not support IP Unnumbered. When initially configuring a virtual template, a reboot of the router may be necessary.

If you make a configuration change to an interface, reset the interface. Use the undo pri-set command instead. Assign an IP address to dialer interfaces. Save the configuration and reboot the router.

2.4. Link Layer Protocol

Symptom Solution

LMI Encapsulation type has been renamed. Router 3000 series routers do not autonegotiate with the 3Com SSII Dual Speed Hub 500. Routers only support switch type dss1 BRI S/T (European ISDN).

If the frame relay peer is set to LMI, set the Local Interface to Non-Standard. Adjust the speed and duplex manually on both devices so they match. Disable auto mode. Routers only support switch type dss1 in this release.

2.5. Network Protocol

Symptom Solution

IGMP query timer defaults to 60. Naming inconsistency with interface and IPX static routes. IPX RIP entries are not aged-out at the userdefined interval.

IPX SAP services timer and multiplier value configurations are ignored. MTU size cannot be dynamically changed from the default of 1500. When you configure NAT outbound on an interface, that interface is not immune to the NAT translation. RTP header compression is not fully supported in this release. Load balancing does not work through recursive lookup. IPX WAN encapsulation is configurable over HDLC.

Set the query timer, manually, to 125. When configuring a static route for a network that begins with an alpha character, preface the network with 0x. The IPX RIP table entries are removed from the table if updates for those entries are not received within the default interval of 180 seconds. This value is based upon a default RIP update timer of 60 seconds and a default multiplier of 3. IPX SAP updates are received once a minute regardless of configuration settings. If making a change to the MTU size, reboot the router afterwards. Deny the NAT outbound interface address with an Access List. RTP header compression is not fully supported in this release. Use MLPPP or OSPF to support load balancing. IPX WAN encapsulation is configurable over HDLC.

R E L E A S E

N O T E S

F O R

T H E

R O U T E R 3 0 0 0 V 1 . 1 0

A N D

R O U T E R

5 0 0 0

S E R I E S

2.6. Routing Protocol

Symptom Solution

Any route policy that uses ACLs defaults to permit all. The OSPF command, abr-summary not advertise is not working correctly. The abr-summary not advertise command does not filter the initial route in a summary update. For example, 128.213.64.0/19 filters the routes 128.213.65.0 to 128.213.95.0 but does not filter 128.213.64.0. Changing the OSPF Area on an interface will delete the OSPF configuration on that interface. Changes to an access list are not applied until the route policy is reapplied. The display bgp route command only shows one route even if multiple (backup) routes are available. RIP MD5 Authentication types are ambiguous. Routing does not function correctly, in a virtual template with multilink PPP and OSPF configuration. When using a serial DTE interface, the OSPF cost may not be set correctly. BGP places all internal peers into one peer group by default, The router supports only 15,000 entries. Receiving over 15,000 BGP routes may cause the router to hang. With Routing Policies, matching next-hop based on IP prefix list does not actually match the next BGP hop. Toggling route-reflection with a connection established causes the router to reboot. A route policy specified in a peer group does not take effect after a reboot, Poison Reverse is not supported in this release.

Add an explicit deny all or permit all rule at the end of all ACL statements. If necessary, configure an ACL to filter the route.

Save the OSPF configuration file before the change. Reapply the route policy immediately after making changes to the access list. The display only shows detail information for the best route. For RIP MD5 Authentication, use the default non-standard value. This is the most common. When using MP with OSPF, you must configure OSPF peer ipaddress. Set the OSPF cost for the DTE manually. To configure different policies for one peer, place that peer in a separate peer group and define policies for that peer group. Arrange with the local ISP to filter routes before updates can reach the router. Use ACL instead of prefix-list.

Shut down the interface before toggling routereflection. Reenter the route-policy after the router has returned to service. Poison Reverse is not supported in this release.

2.7. Multicast Protocol

Symptom Solution

The router does not support IP multicast forwarding without the multicast routing protocol. Enabling ip unnumbered on a PIM-SM interface disables PIM-SM routing.

Keep PIM-SM or PIM-DM enabled on the interface to insure multicast runs correctly. Do not configure ip unnumbered on a PIM-SM interface.

R E L E A S E

N O T E S

F O R

T H E

R O U T E R 3 0 0 0 V 1 . 1 0

A N D

R O U T E R

5 0 0 0

S E R I E S

2.8. Security
Symptom Solution

ACL match counts are not logged. If you are using automatic matching order with ACLs, a rule that is similar to an existing rule, even if they have different qualifiers, is not added as a separate rule. IPSec in transport mode will transmit transit traffic with no security headers. IPSec in transport mode is designed for direct communications between two peers running IPSec. IPSec nesting is not supported in this release. The Encryption card status message, Byte Order: Not consistent with host, can be misleading. Only one security association is used for each ACL-incompatible with per-rule implementation.

ACL match counting is only supported with the firewall feature. Remove the existing rule before applying the new rule.

Use Tunnel mode if you are configuring the router to be an IPSec gateway.

IPSec nesting is not supported in this release. Disregard this status message.

Create one separate ACL for each permit statement in the third-party access list.

2.9. VPN
Symptom Solution

The basic version of this release does not support GRE or L2TP.

Use the extended version of this release for GRE and L2TP tunneling support.

2.10. QoS
Symptom Solution

NBX Layer 2 traffic cannot be classified for QoS.

Use Layer 3 prioritization.

2.11. Dial-Up
Symptom Solution

The ppp chap user command is not supported in dialer interfaces.

When using Resource DCC and using chap authentication, ppp chap user should be configured only on the router that is dialing out.