3com Router 6040 Release note

Brand: 3com

Model: Router 6040

Category: Networking

Type: Release note

This manual is also suitable for

http://www.3com.com/

Router 6000 and 3000 DSL

Family Release Notes

Software V 2.01

Router 6040 (3C13840)

Router 6080 (3C13880)

Router 3030 (3C13630)

Router 3031 (3C13631)

Router 3032 (3C13632)

Router 3033 (3C13633)

Router 3034 (3C13634)

Router 3035 (3C13635)

Part No. 10014363

Published August 2004

3COM ROUTER 6000/3000 DSL

FAMILY RELEASE NOTES

Software V 2.01

Introduction These release notes address the following:

■ V2.0 to V 2.01 Software Upgrade

■ Hardware Accessories Installation

■ System Access

■ SNMP

■ System Management

■ Interface Management

■ Link Layer Protocol

■ Network Protocol

■ Routing Protocol

■ Multicast Protocol

■ Security

■ Quality of Service (QoS)

■ MPLS

■ Documentation Errors

IMPORTANT NOTE The following features are supported in the Extended Release only:

■ IPSec

■ SNMP v3

■ SSH

V2.0 to V 2.01

Software Upgrade

Please verify the software version running on your router. You can verify the

software version by issuing a

display version command on your router. If the

display output shows 3Com Router Software V2.00, please upgrade your router

software to version 2.01. You can obtain the latest version of router software from

the 3Com support web site.

IMPORTANT: For 3Com Router 3000 DSL Family running V2.00 router software. If

you upgrade your router software via tftp, it will always fail on the first attempt

with the following output:

<3Com>tftp <server ip address> get <filename> system

The file system currently exists. Overwrite it?[Y/N]:y

File will be transferred in binary mode.

Downloading file from remote tftp server, please wait...\

2 CHAPTER 1: 3COM ROUTER 6000/3000 DSL FAMILY RELEASE NOTES SOFTWARE V 2.01

Incorrect packet received

It is necessary to wait 3 minutes and then repeat the command.

IMPORTANT: For 3Com 6000 Router Family running V2.00 router software. If you

upgrade your router software via tftp and set the destination filename to

secure.bin then tftp will always fail on the first attempt with the following output:

<3Com>tftp <server ip address> get <filename> secure.bin

The file system currently exists. Overwrite it?[Y/N]:y

File will be transferred in binary mode.

Downloading file from remote tftp server, please wait...\

Incorrect packet received

DO NOT use secure.bin as the destination file. Issue the following command

instead

<3Com>tftp <server ip address> get <filename> r6x02_01e.bin

Issue boot main r6x02_01e.bin from the system view to set r6x02_01e.bin as

the main image then reboot the router.

Hardware Accessories

Installation

For Router 3032/3035 ADSL over ISDN products, standard RJ-11 to RJ-11 cable is

provided for an external splitter with RJ-11 connection. This cable can also be used

for RJ-45 connection if the external device has this type of interface available only.

System Access ■ Issuing the display current-configuration command on the Router 3000

DSL Family will result in some packet loss during heavy traffic times. Please

refrain from issuing the current configuration command during peak usage

periods.

■ The following command does not work: Undo Local-user user-name

ftp-directory

. Change the FTP directory to the default: Local-user

user-name ftp-directory flash:

■ Router does not allow the configuration of FTP server with Radius

Authentication None option. FTP Anonymous login is not supported. A

username and password is required for FTP access.

■ The FTP server does not support filenames containing spaces. Use underscores

instead of spaces for character separation.

SNMP ■ snmp-agent trap enable entity command missing

■ To enable RFC 2737 (Entity MIB) traps use snmp-agent trap enable

command, then undo any unwanted traps types individually.

■ To disable Entity MIB traps, use undo snmp-agent trap enable command,

then enable any other wanted traps types individually.

System Management 3

System Management ■ The Display PVC command from User View is not supported.

■ The system clock on the Router 6000 may reset after reboot. The system clock

on the Router 3000 DSL Family resets after reboot. Configure NTP protocol or

check system clock and set clock manually.

■ Cannot undo snmp trap target created using SNMP. 3Com Network Director

automatically configures the router to send SNMP traps by default. The entry

cannot be deleted using the CLI. De-select this option in the Monitoring tab in

the

Tools -> Options dialog in 3Com Network Director to avoid.

■ A "configuration change" trap is generated whenever a CLI user enters the

system-view instead of when an actual configuration change has been made.

To resolve this, disable the configuration traps using the

undo snmp-agent

trap enable configuration

trap.

Interface

Management

■ The Virtual Template interface remains up when the associated physical

interface is down. As a result, the router advertises the Virtual Template.

There are multiple areas that can apply a Virtual Template (MLPPP, ISDN, IPSec,

PPPoE server, etc.) There is no solution for these areas using Virtual Template,

except for MLPPP. Use MP-group if you want to use MLPPP.

■ Interface statistics set with a flow-interval under 10 seconds are not accurate.

Do NOT use a flow-interval setting under 10 seconds.

■ Dialer interface statistics are NOT accurate for flow intervals under 300

seconds. For flow intervals between 10 and 300 seconds, check the associated

physical interface for accurate statistics.

■ The Router 3000 DSL Family Ethernet interface displays physical and protocol

states as up/up even when there is no cable connection. The interface responds

to pings even with no cable connection. The Router 3000 DSL Family Ethernet

ports will be in the up/up state as soon as an ip address is configured. No cable

connection is required. The LED indicator is a more accurate indicator of a valid

link.

■ The virtual-ethernet interface's protocol state is always down. Issue a ping

command to verify that the interface is actually up and working properly.

Link Layer Protocol ■ Frame Relay PVCs can be modified while they are a part of PVC switching

endpoints. You must verify that the interface is not a PVC endpoint before

making any changes.

■ The Line Protocol state displays as up when no cable is attached to the port on

an ISDN interface. Observe the interface's physical Current State. It will be

down if no cable is attached to the interface.

■ FRF.9 Compression displays when viewing PVC statistics even after PVC is

re-mapped without FRF.9. After re-mapping a PVC to exclude FRF.9

Compression, you need to reset the interface in order to clear any reference to

FRF.9.

Network Protocol ■ Packets with an internal address will appear outside the NAT boundary. NAT

does not translate any IP protocols other than ICMP, TCP, UDP, and GRE (with

respect to PPTP)

4 CHAPTER 1: 3COM ROUTER 6000/3000 DSL FAMILY RELEASE NOTES SOFTWARE V 2.01

■ A router running DHCP client cannot obtain the default gateway address.

Auto configuring the Default gateway is not supported in this release. You

must manually configure this setting.

■ You cannot access certain web sites from DSL routers. To resolve this, set the

tcp maximum segment size to 1410 on the DSL router's outgoing (WAN)

physical or virtual interface.

■ IPX is not supported on Frame Relay, HDLC, and X25. IPX is only supported on

Ethernet and PPP.

■ The DHCP Server fails to remember the DHCP clients after a reboot.

Routing Protocol ■ OSPF interface costs are not the same on peer DCE/ DTE Frame Relay Serial

interfaces. If a Frame Relay DTE Serial interface is configured for OSPF, and the

DCE has a different baud rate, the interface must be configured with the

virtualbaudrate command. Configure this command using the same baud

rate as the DCE. After configuration, shut down and restart the interface.

■ BGP Auto-summary does not work for networks originated using the Network

command. Only imported routes will be auto-summarized.

■ An undo RIP from interface view removes RIP globally. To remove RIP from

interface view use the

Undo rip work command.

■ BGP route dampening does not work for IBGP routes. BGP dampening works

for EBGP routes only.

Multicast Protocol ■ The default value for the IGMP query interval does not match the

recommended value in RFC 2236. Set the query interval to match the query

interval of other routers in your network.

■ PIM is not supported with IP unnumbered FR interfaces. An IP address must be

assigned to the FR interface.

Security ■ NAT traversal does not work in IKE Main Mode. IKE Aggressive Mode is

required for NAT traversal to function properly

■ IPsec tunnel will not get established with Cisco routers when a NAT device is in

the communications path. NAT traversal is not compatible with Cisco routers

■ Only one security association is used for all traffic flows. IPsec SAs originated

from 3Com routers will be ACL based. To obtain flow-based functionality,

create multiple ACLs with one rule each.

■ The firewall drops FTP connections when ASPF is configured to filter TCP.

Configure ASPF with TCP and FTP together

■ IPsec renegotiates SAs too early with heavy traffic. This may lead to traffic

disruptions. Set ISAKMP traffic (destination UDP port 500) as high priority in

QoS to avoid any disruption in communications through the IPsec tunnel

Quality of Service

(QoS)

■ Frame Relay Classes that contain Frame Relay QoS parameters can be applied

to PVC's even if Frame Relay Traffic Shaping is not enabled. Frame Relay Traffic

Shaping must be enabled for PVC queues.

MPLS 5

■ Frame Relay Congestion Control BECN/FECN does not function. Disable IP Fast

Forwarding on the interface if Frame Relay Traffic Shaping is selected.

■ Frame Relay Traffic Shaping is Inactive on interfaces that use Frame Relay Traffic

Shaping. Disable IP Fast Forwarding on the interface if Frame Relay Traffic

Shaping is selected.

■ QoS with ip fast forwarding doesn't work properly. Disable ip fast forwarding.

MPLS ■ If you ping a CE Router from a PE Router within an MPLS/BGP L3 network there

will be no response. Use the command

ping -vpn -a xxx.xxx.xxx.xxx

xxx.xxx.xxx.xxx

, using the source address of the PE interface that is in the

VPN of the intended target.

■ If Loopback0 and LSR ID ip addresses are different, MPLS LDP will not work

properly. Match Loopback0 and LSR ID ip addresses

Documentation Errors ■ Command Reference Manual' IS-IS section text is:

“When the cost type is “narrow”, its range is 1 through 63; when the cost type

is wide, its range is 1 to 16777215.”

Text Correction: “When the cost type is “narrow”, its range is 0 through 63;

when the cost type is wide, its range is 0 to 16777215.”

■ The Router 6000 Family uses the frame relay terminology Cir Allow and Cir,

instead of Cir and MinCir respectively. Please refer to the following documents:

'3Com Router Command Reference Manual' page 1033. '3Com Router

Configuration Guide' page 1019

Text Correction: Use CIR Allow when configuring the maximum Committed

Information Rate for the DTE when no network congestion exists. Use CIR as

the value to which the DTE will adjust when network congestion exists

■ Command manual example results in an error: “snmp-agent local-engineid

12345”

Text Correction: The command requires the user to enter a string of 5 to 32

octets of hexadecimal characters for the SNMP engine ID. Ex: 0102030405

■ The virtualbaudrate command is non-existent in the Command Index.

Use the “virtualbaudrate” command in the CLI.

[6080-3-Serial2/0/4]virtualbaudrate?

300 only for async mode

600 only for async mode

1200 for syn & asyn mode

2400 for syn & asyn mode

4800 for syn & asyn mode

9600 for syn & asyn mode

19200 for syn & asyn mode

38400 for syn & asyn mode

56000 only for syn mode

57600 for syn & asyn mode

64000 only for syn mode

72000 only for syn mode

115200 for syn & asyn mode

128000 only for syn mode

384000 only for syn mode

2048000 only for syn mode

6 CHAPTER 1: 3COM ROUTER 6000/3000 DSL FAMILY RELEASE NOTES SOFTWARE V 2.01

■ The SNMP Trap enable default is incorrectly documented. All traps are enabled

when the snmp-agent command is executed

■ Firewall ASPF UDP detection does not support the following UDP based

applications: TFTP, SSH, DHCP.

■ Named access list is documented but not supported. Named access list is not

supported in this release

■ ACL numbering scheme is different from that documented. The following is

the corrected numbering scheme:

1000-1099(Interface-based ACL)

2000-2099(Basic ACL)

3000-3099(Advanced ACL)

4000-4999(Ethernet Frame Header ACL)

■ The Command Reference Manual states that reset ike sa will clear both

phase 1 and phase 2 security associations.

reset ike sa will only clear phase 1 security associations; “reset ipsec sa” will

clear phase 2 security associations

■ MPLS LDP loop detect cannot be configured after LDP is enabled on interface.

An error is reported. Enable LDP loop detect under system view before enabling

LDP on the interface.

3com Router 6040 Release note

Brand: 3com

Model: Router 6040

Category: Networking

Type: Release note

This manual is also suitable for

Download PDF

report

3com Router 6040 Release note

This manual is also suitable for

3com Router 6040 Release note

Related papers

Other documents