3Com Router 3000 Series Manuel utilisateur

Router 3000/5000

Series

Release Notes for V1.20

http://www.3com.com/

Part No. 10014296

Published January 2004

Introduction

1.1. Scope

These release notes summarize operational requirements and issues for the following

Router 3000 and Router 5000 hardware and software release V1.20:

 Router 3015

 Router 5009 smart interface card (SIC):

2-Port ISDN BRI U

 Router 5231, 5640, and 5680 multifunctional interface cards (MIMs):

4-Port Enhanced Synchronous/Asynchronous MIM with X.21

4-Port E1/CE1/PRI MIM

1-Port T3 MIM

1-Port E3 MIM

Read these release notes before installing your router, software, or component hardware.

1.2. Cable Connections

3Com recommends that you power off the router before connecting any cable.

Do not connect and disconnect synchronous or asynchronous physical WAN cables, console

cables, Ethernet cables, ISDN BRI cables, and 4-port physical WAN adapters while power to the

router is on. Connecting cables while the router is powered on can crash the router or damage the

interface 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,

SSH, 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:

3Com Router Release Notes for V1.20

http://support.3com.com/infodeli/tools/routers/3ComRouterComRef.pdf

Download the 3Com Router Configuration Guide from:

http://support.3com.com/infodeli/tools/routers/3com_configuration_guide.pdf

Download other current software updates and release notes from:

http://www.3com.com/

3Com Router Release Notes for V1.20

1.1. V1.20 Release Notes

This chapter offers updates on Router 3000 and Router 5000 features in the following

areas:

System Access Network Protocol QoS

SNMP Routing Protocol Dial-Up

System Management Multicast Protocol Documentation

Interface Management Security Resolved Issues

Link Layer Protocol VPN

1.1.1. System Access

Symptom Solution

The following commands will not be available

after an upgrade from V1.10:

undo login pad

terminal telnet refuse-negotiation

terminal telnet break-on-ip

Those commands are now undo login-

method authentication-mode pad, reverse-

telnet no-negotiation, and reverse-telnet

break-on-ip, respectively

1.1.2. SNMP

Symptom Solution

Routers are not recognized by Network

Management applications, such as 3Com

Network Supervisor, unless SNMP V1 is

enabled.

Enable SNMP V1 on the device, as described

in the Installation Guide, then discover the

network using 3Com Network Supervisor.

Adding a row to the RMON2 trapDest table

does not automatically enable traps. Use the snmp-agent trap enable command.

In the RMON2 trapDest table, the RowStatus

value of CreateAndGo(4) is not correctly

implemented.

Use CreateAndWait(5) and set the row Valid(1)

using a second PDU.

SNMPv3 traps are not being generated. SNMPv3 traps are not supported in this

release.

3Com Router Release Notes for V1.20

1.1.3. System Management

Symptom Solution

Upgrading from V1.10 will result in denied

access to the router via telnet if local users or

RADIUS was not configured and saved

beforehand

Configure a local user with administrative rights

and save the configuration before upgrading to

V1.20 remotely

System file cannot be accessed for upgrade if

remote upgrade process was not completed

(answer to query about writing to flash was not

received) before the telnet session is

terminated

A reboot of the router is necessary if a second

attempt at upgrading is to be successful

Do not power cycle the router until after the

upgrade is complete.

The basic version of this release does not

support SSH Use the extended version of this release for

SSH support.

If you add or remove a module, the

configuration may be altered. Save the configuration file and edit it with the

new interface numbers so that the file

corresponds with the new physical

configuration.

The router reboots if an invalid agent software

file is used to upgrade the device. Insure that the correct agent file has been used

before writing to flash memory.

When a router reboots, the system clock is

reset to GMT. Set the time zone if using NTP. If the Master

Clock router is rebooted, reset the time on the

Master Clock router. All other routers will

synchronize with the Master Clock if they are

defined as peers.

On the Router 5680, the T3/E3 MIMs may

sometimes not be recognized by the system

upon DISPLAY VERSION.

Do not place the T3 or E3 card in slot 2. Use

another available slot

X.21 does not work on the 4-Port Synchronous/

Asynchronous MIM (3C13763) or 1-Port

Synchronous/Asynchronous SIC (3C13714).

To support X.21 on 3Com routers, you must

use the embedded serial interface or the 4-Port

Synchronous/Asynchronous MIM with X.21

support (3C13764)

The E1 controller does not inter-operate with

the Adtran Atlas 830 in PRI or CE1 using AMI

line code.

Use HDB3 line code to operate correctly with

the Adtran switch.

TACACS+ appears in the CLI as HWTACACS Use the HWTACACS commands for TACACS+

configuration.

1.1.4. Interface Management

Symptom Solution

Interface changes may require a reset of the

interface for changes to take effect. If you make a configuration change to an

interface, use the shutdown and undo

shutdown commands on the interface..

The error message for deleting a PRI is

incorrect. Use the undo pri-set command instead.

Dialer interfaces do not support IP

Unnumbered. Assign an IP address to dialer interfaces.

When initially configuring a virtual template, a

reset of all physical interfaces may be

necessary.

To correct any abnormalities in operations, all

physical interfaces related to the virtual

template must be shut down together before

being brought back up.

3Com Router Release Notes for V1.20

Removing the firewall-packet filter command

from the interface does not work The command must be completed with the

“inbound” or “outbound” keyword

1.1.5. Link Layer Protocol

Symptom Solution

North American ISDN protocol types cannot be

configured on a PRI interface. DSS1 is the only supported protocol type.

The LMI Encapsulation type on the 3Com

routers is called Non-Standard. If the frame relay peer is set to LMI, set the

Local Interface to Non-Standard.

Router 3000 series routers do not auto-

negotiate with the 3Com SSII Dual Speed Hub

500.

Adjust the speed and duplex manually on both

devices so they match. Disable negotiation

mode.

The dialer disconnect B-channel command

uses a timeslot numbering scheme. The dialer disconnect B-channel command

takes a timeslot as an argument. Timeslot 16 is

the D channel; the timeslot numbering for the

B-channels is 1-15 and 17-31. To disconnect

B-channel 30 the user must specify timeslot 31.

Defining an SDLC controller address preceded

by the hexadecimal designator, ‘0x’ results in

‘Invalid Address’ message.

Omit the hexadecimal ‘0x’ when defining an

SDLC address.

Changing a link from MFR to MP can result in a

router reboot When changing from an MFR configuration to a

MP configuration, shut down all the physical

interfaces used by the Virtual-Template.

Save the configuration, reboot the router and

undo shutdown on the physical interfaces.

1.1.6. Network Protocol

Symptom Solution

IGMP query timer defaults to 60. Set the query timer, manually, to 125.

Naming inconsistency with interface and IPX

static routes. When configuring a static route for a network

that begins with an alpha character, preface

the network with 0x.

IPX RIP entries are not aged-out at the user-

defined interval. 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 services’ timer and multiplier value

configurations are ignored. IPX SAP updates are received once a minute

regardless of configuration settings.

NAT translates the global interface IP address

as well as all internal addresses. Thus, all

traffic going out of the NAT interface is

translated, including all local interface IP

addresses on the router.

Any IP address (especially that of the global

NAT interface) that was not intended for NAT,

should be denied translation in an access list.

Deny the NAT outbound interface address with

an Access List.

Refer to 3Com Knowledgebase solution

3KB9241 for more details.

RTP header compression is not fully supported

in this release. RTP header compression is not fully supported

in this release.

Load balancing does not work through

recursive lookup. Use MP or OSPF to support load balancing.

3Com Router Release Notes for V1.20

When trying to configure a second IPX sub-

interface with the same IPX frame type, the

following error message is displayed:

"Same frame type has exist, you can change to

another frame type in order to config ipx"

To configure multiple IPX networks with the

same IPX frame type, you must use separate

physical interfaces for each network.

1.1.7. Routing Protocol

Symptom Solution

Any route policy that uses ACLs defaults to

permit all. Add an explicit deny all or permit all rule at

the end of all ACL statements.

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.

If necessary, configure an ACL to filter the

route.

Changing the OSPF Area on an interface will

delete the OSPF configuration on that

interface.

Save the OSPF configuration file before the

change.

Changes to an access list are not applied until

the route policy is reapplied. Reapply the route policy immediately after

making changes to the access list.

The display bgp route command only shows

one route even if multiple (backup) routes are

available.

The display only shows detail information for

the best route.

RIP MD5 Authentication types are ambiguous. For RIP MD5 Authentication, use the default

non-standard value. This is the most common.

Routing does not function correctly, in a virtual

template with MP and OSPF configuration. When using MP with OSPF, you must

configure OSPF peer ip address.

When using a serial DTE interface, the OSPF

cost may not be set correctly. Set the OSPF cost for the DTE manually.

BGP places all internal peers into one peer

group by default To configure different policies for one peer,

place that peer in a separate peer group and

define policies for that peer group.

The router supports only 15,000 entries.

Receiving over 15,000 BGP routes may cause

the router to hang.

Arrange with the local ISP to filter routes before

updates can reach the router.

With Routing Policies, matching next-hop

based on IP prefix list does not actually match

the BGP next-hop.

Use ACL instead of prefix-list.

Poison Reverse is not supported in this

release. Poison Reverse is not supported in this

release.

With IBGP, importing direct routes will have

origin attribute of IGP locally. However, when

advertised to a peer, the peer will log the route

as incomplete. This is only a problem with

IBGP peers.

Correct the issue with an export policy if

necessary.

When the default-local-pref command is used

with a value other than 100, the value is

reverted back to 100 after a reboot.

Re-configure the default-local-pref value after

a reboot.

BGP advertises routes when it is out of

synchronization with the interior routing

protocol

BGP synchronization is not supported.

3Com Router Release Notes for V1.20

1.1.8. Multicast Protocol

Symptom Solution

The router does not support IP multicast

forwarding on an IGMP interface without the

multicast routing protocol enabled.

Keep PIM-SM or PIM-DM enabled on the

IGMP interface to insure multicast runs

correctly.

Enabling ip unnumbered on a PIM-SM

interface disables PIM-SM routing. Do not configure ip unnumbered on a PIM-SM

interface.

1.1.9. Security

Symptom Solution

ACL match counts are not logged. ACL match counting is only supported with the

firewall feature.

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.

Use Tunnel mode if you are configuring the

router to be an IPSec gateway.

IPSec nesting (i.e. the encrypting of already

encrypted packets) is not supported in this

release.

IPSec nesting is not supported in this release.

The Encryption card status message,

Byte

Order: Not consistent with host

can be misleading.

Disregard this status message.

Only one security association is used for each

ACL-incompatible with per-rule implementation.

Create one separate ACL for each permit

statement in the third-party access list.

To telnet or SSH to a 3Com Router there must

be a local user defined on that 3Com router.

Configure a local-user on the router for telnet

or SSH access

Routers that are defined within a Server ACL

on the Master Clock router will not sync to the

Master

From the Master Clock router, define each

router as a Peer of the clock source router

within a Peer ACL if these routers are to be

synchronized by the Master.

In addition, direct NTP messages to the master

using the unicast server command on the

routers.

The encryption card in combination with some

features may cause ping responses or traffic to

be slowed. Example: Encryption card with

GRE, MP, IPSec.

If problems occur with securely managing or

pinging the router via an IPSec tunnel, use a

software encryption policy instead of an

encryption card policy.

It is difficult to exit from the SSH public key

configuration without a valid key Enter another view, such as interface view,

using the command interface Ethernet 0, then

quit.

3Com Router Release Notes for V1.20

1.1.10. 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.

A Windows 2000 or Windows XP client cannot

connect to a 3Com router using L2TP over

IPSec.

L2TP over IPSec support on Windows 2000 or

Windows XP clients requires modification of

the Windows Registry and a static IP address.

Refer to 3Com Knowledgebase solution

3KB9023 for more details.

1.1.11. QoS

Symptom Solution

NBX Layer 2 traffic cannot be classified for

QoS. Use Layer 3 prioritization.

QoS is not supported with the Encryption card In order to use QoS with IPSec, use a software

encryption policy instead of a hardware

encryption card policy.

After configuring QoS Policies on a Virtual

interface, QoS does not take effect The virtual interface must be shut down by

shutting down all of the physical interfaces

before the new QoS policy will take effect

The undo wred weighting-constant

command will not execute To restore the weighting constant to its default,

use the wred weighting-constant 9

command.

The undo wred ip-precedence value

command will not execute To restore the wred ip-precedence parameters

to the default, use the following command:

wred ip-precedence value low-limit 10 high-

limit 30 discard-probability 10

1.1.12. Dial-Up

Symptom Solution

The router reboots after a HyperTerminal

session is disconnected from the

1-Port Synchronous/Asynchronous SIC, 4-Port

Synchronous/Asynchronous MIM, or 4-Port

Synchronous/Asynchronous MIM with X.21

support.

HyperTerminal is not supported on these

modules.

Remote console administration can be

achieved by dialing into a modem connected to

the AUX port configured in flow mode.

1.1.13. Documentation

Symptom Solution

There is no support for NTP Broadcast Delay,

or NTP Synchronization Period in the CLI, yet

they remain in the user documents.

Disregard documentation on these features

within the user documents.

The setup command is documented but

missing.

Use CLI commands for your initial

configuration.

The synchronization command is listed in the

documentation but cannot be used. This command is no longer supported. BGP

synchronization is always disabled.

3Com Router Release Notes for V1.20

1.1.14. Resolved Issues

The following issues have been resolved since the release of V1.10:

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

• RMON MIB tables cannot be created on an Ethernet interface on which RMON is

disabled.

• The RMON history bucket allocation does not fail if more than 50 buckets are

requested.

• The src and dst addresses are no longer reversed on RMON Matrix DS tables.

• BRI interfaces support ISDN protocol types National ISDN and AT&T 5ESS

(Lucent 5E).

• MTU size can now be changed from the default of 1500.

• Toggling route-reflection with a connection established no longer causes the router to

reboot.

• A route policy specified in a peer group now takes effect after a reboot.

• When using automatic matching order with ACLs, similar rules with different

qualifiers are added as separate rules.

• Routers no longer reboot after an NBX page is completed.

3Com Router Release Notes for V1.20

Ce manuel convient aux modèles suivants

Table des matières

Autres manuels 3Com Routeur réseau

3Com

3Com 3C8S400 - SuperStack II PathBuilder S400... Manuel utilisateur

3Com

3Com 400 Family Manuel utilisateur

3Com

3Com OfficeConnect 3CRWDR200A-75 Manuel utilisateur

3Com

3Com OfficeConnect WL-537 Manuel utilisateur

3Com

3Com OfficeConnect 3CR858-91 Manuel utilisateur

3Com

3Com OfficeConnect 3CR414492 Manuel utilisateur

3Com

3Com OfficeConnect Ethernet Hub 16C Manuel utilisateur

3Com

3Com 3C13701 Manuel utilisateur

3Com

3Com Router 6000 Series Manuel utilisateur

3Com

3Com Switch 4800G 24-Port Manuel utilisateur

3Com

3Com MSR 50-40 Manuel utilisateur

3Com

3Com 3C13751 Manuel utilisateur

3Com

3Com OfficeConnect Remote 812 Manuel utilisateur

3Com

3Com Router 3012 Mode d’emploi

3Com

3Com 3C6090 - NETBuilder II Dual Processor Engine... Manuel utilisateur

3Com

3Com OfficeConnect 3C840 Instructions d'installation et d'utilisation

3Com

3Com OfficeConnect WX4400 Manuel d'installation

3Com

3Com MSR 50 Series Feuille d'instructions

3Com

3Com NETBuilder SI Mode d’emploi

3Com

3Com Router 3031 Manuel d'utilisation

3Com

3Com OfficeConnect 3C840 Manuel utilisateur

3Com

3Com 3C13886 - Router OC-3 ATM SML Flexible Interface... Manuel utilisateur

3Com

3Com MSR 50 Series Instructions originales

3Com

3Com 3CBLUF26 Manuel utilisateur

Manuels Routeur réseau populaires d'autres marques

Allnet

Allnet ALL0333AU Manuel utilisateur

HomeSeer

HomeSeer HT-SEL Manuel utilisateur

Sercomm

Sercomm Genesis OC3505D Manuel utilisateur

Billion

Billion BIPAC 5102 Series Manuel utilisateur

TP-Link

TP-Link TD-8817 Manuel utilisateur

Motorola

Motorola MR1900 Manuel utilisateur

Digi

Digi IX14 Manuel utilisateur

Cisco

Cisco NCS 540 Manuel

XAVi

XAVi X8821e Manuel utilisateur

BEC

BEC 6200WZL Manuel utilisateur

MikroTik

MikroTik hAP ac3 Series Manuel utilisateur

Korenix

Korenix JetNet 5428G Series Manuel utilisateur

NETGEAR

NETGEAR FS526T - Switch Manuel utilisateur

Korenix

Korenix JetNet 5710G Series Manuel utilisateur

Automated Logic

Automated Logic ZN551 Manuel du propriétaire

Cisco

Cisco ASR 1000 Series Manuel de l'opérateur

EnGenius

EnGenius ESR-9710 Manuel utilisateur

Cisco

Cisco 805 Series Instructions d'utilisation et de sécurité