3com Router 5000 and Router 6000 Release Notes: Part Number: 10016400 Rev AA Published October 2007

3Com Router 5000 and Router 6000 Release Notes
Software version 3.11 Part Number: 10016400 Rev AA Published October 2007
3Com Router 5000 and Router 6000 Family Release Notes Software v3.11
Contents
1. Introduction ..................................................................................................................................................3 1.1 Scope .....................................................................................................................................................3 1.2 Supported Routers ..................................................................................................................................3 1.3 Online Resources.....................................................................................................................................3 1.4 New Software Features for V3.11............................................................................................................4 1.5 New Bug Fixes for V3.11 .......................................................................................................................11 1.6 New Software Support for FIC Modules in V3.11...................................................................................11 2. Software Issues Resolved in Previous Releases ..............................................................................................12 2.1 Issues Resolved in Router 5000 Bootrom ...............................................................................................12 2.2 Software Issues Resolved in v3.00..........................................................................................................12 2.3 Documentation Issues Resolved in v3.00................................................................................................13 2.4 Software Issues Resolved in v2.41..........................................................................................................13 2.5 Software Issues Resolved in v2.21..........................................................................................................14 2.6 Software Issues Resolved in v2.21..........................................................................................................15 2.7 User Documentation Issues resolved in v2.21.........................................................................................16 2.8 Software Issues Resolved in v2.30/31.....................................................................................................16 2.9 Documentation Issues Resolved in v2.30/31...........................................................................................17 3. Known Issues in Release v3.01.....................................................................................................................17 3.1 System Access.......................................................................................................................................17 3.2 SNMP ...................................................................................................................................................18 3.3 System Management ............................................................................................................................18 3.4 Interface Management..........................................................................................................................18 3.5 Link Layer Protocol ................................................................................................................................19 3.6 Network Protocol ..................................................................................................................................20 3.7 Routing Protocol ...................................................................................................................................20 3.8 Multicast Protocol .................................................................................................................................21 3.9 Security/VPN .........................................................................................................................................21 3.10 Quality of Service (QoS).......................................................................................................................22 3.11 MPLS ..................................................................................................................................................22 3.12 Voice and Router Interoperability 3Com VCX and NBX issues ..........................................................23 3.13 Documentation Errors .........................................................................................................................24 4. Known Issues in Release v3.11.....................................................................................................................24 4.1 System Management ............................................................................................................................24 4.2 Security/VPN .........................................................................................................................................24 4.3 Voice and Router Interoperability 3Com VCX and NBX issues ............................................................24 5. Upgrading Software ....................................................................................................................................24 5.1 Upgrading the Router 5000 Software....................................................................................................24 5.2 Upgrading the Software for the Router 6000/RPU .................................................................................32 5.3 Software Upgrade for the Router 6000/RPU2 ........................................................................................44 5.4 Maintaining Application Program and Configurations Using the Command Line ....................................52
1. Introduction
1.1 Scope
This document contains the release notes for the Router 5000 and Router 6000 v3.01 software listed in Table 1. This software release provides an update to the Router 5000 and Router 6000. Please note that the software for the Router 6000 RPU2 will not load on the Router 6000 RPU. Table 1: Software Release v3.11 Software Filenames R6y03_11e.bin R6y03_11v.bin R6x03_11e.bin R6x03_11v.bin R5y03_11v.bin R5y03_11e.bin Description Encrypted software agent for the Router 6040 and 6080 RPU2 (including bootrom) Basic software agent for the Router 6040 and 6080 RPU2 (including bootrom) Encrypted software agent for the Router 6040 and 6080 RPU (including bootrom) Basic software agent for Router 6040 and 6080 RPU (including bootrom) Basic software agent for the 5012, 5232, 5642, 5842 Routers Encrypted software agent for the 5012, 5232, 5642, 5842 Routers
bootromfull9-23.bin Router 5000 Boot ROM file for 5012, 5232, 5642, 5842 Routers
1.2 Supported Routers

These release notes summarize the operational requirements and issues for the following routers: Router 5012 3-Slot (3C13701) Router 5232 3-Slot (3C13751) Router 5642 4-Slot (3C13755) Router 5682 8-Slot (3C13759) Router 6040 4-Slot (3C13840) Router 6080 8-Slot (3C13880)
1.3 Online Resources

Visit the 3Com web site for the latest documentation and software updates: www.3Com.com Obtain a copy of the Router 5000 or Router 6000 Installation Guide, Command Reference Guide, or Configuration Guide. Obtain current software updates (maintenance releases) and associated release notes for the Router 5000 and Router 6000 and other 3Com products.
1.4 New Software Features for V3.11

The following software support has been added for V3.11
1.4.1 SIP Server Registration using a DNS Name

V3.11 accepts DNS names as well as IP addresses for the 'sip-server' command. This makes it easy for Service Providers to change the SIP Server address.
1.4.2 SIP Early-Media Parameter

V3.11 sends a SIP message 183 Session Progress Response with SDP instead of SIP message 180 Ringing. This allows the media stream to be set up prior to the call being answered.
1.4.3 Management Protocol IP Address Parameter

V3.11 allows defining an IP address or the loopback interface as the source address for administrative protocols including NTP, FTP, TFTP, and SCEP. This ensures that the Router remains reachable by management traffic even when it's on a different AS to the management station and the Router's management traffic is using a physical interface.
1.4.4 Enhanced 'show ppp mp' Command

The output of the 'show ppp mp' command is enhanced to include load information (x/255). This helps with identification of problems.
1.4.5 Source Specific Multicast (SSM) Mapping

V3.11 supports Source Specific Multicast (SSM) Mapping. This enables efficient handling of one-to-many multicast streams.
1.4.6 SNMP v3 USM-User Passwords

(RFC 3414 User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)) This supports proper password copying when taking a configuration including a password, from one router and loading it onto another router.
1.4.7 OSM | CA MIB

OSN|CA MIB Support The OSM|CA MIB is supported. This enables applications running on an installed OSM module to communicate with the Router. The prime purpose of this is to allow an application running on the OSM to request specific traffic flows to be forwarded, copied or re-directed to it.
1.4.8 IGMP version3 (RFC 3376 Internet Group Multicast Protocol, Version 3)
IGMP Version 3 adds support for "source filtering," which enables a multicast receiver host to signal to a router which groups it wants to receive multicast traffic from, and from which source(s) this traffic is expected
1.4.9 PIM SSM (RFC 4607 Source-Specific Multicast for IP)

PIM-SSM supports one-to-many model. Initial commercial multicast Internet applications are likely to be available to subscribers (that is, receivers that issue join messages) from only a
single source (a special case of SSM covers the need for a backup source). PIM-SSM builds shortest path trees (SPT) rooted at the source immediately because in SSM, the router closest to the interested receiver host is informed of the unicast IP address of the source for the multicast traffic. That is, PIM-SSM goes directly to the source-based distribution tree instead of the RP through shared distribution trees. PIM-SSM operation is guaranteed only in the 232/8 range (232.0.0/24 is reserved).
1.4.10 Kentrox T3/E3 subrate support

The T3/E3 interface offers the new feature of interoperating with Kentrox DataSMART T3/E3 IDSU.
1.4.11 CLI command to specify the source address of PKI communication

The system administrator now can specify the source address used during PKI communication.
1.4.12 Fast forwarding with Policy Routing Support

After policy routing is enabled on an interface, packets on the interface are fast forwarded to enhance the IP forwarding efficiency.
1.4.13 QoS in GRE Tunnel Fast Forwarding

The GRE Tunnel fast forwarding process supports QoS as in the normal forwarding process.
1.4.14 OSPF Fast-Hello Function

OSPF fast hello packets refer to hello packets being sent at intervals of less than 1 second as compare to 10 seconds for an Ethernet link and 30 seconds for a non broadcast link.
1.4.15 SIP supports all standard 18x Temporary Response

This feature implements standard handling for 18x temporary responses in the case of SIP calls, and the ringback tone can be correctly played upon internetworking with devices from other vendors
1.4.16 HWPing Enhancement

I.
Enhanced HWPing Functions
This version enhances the routers HWPing functions, including: Support NQA MIB and expand SNMPs manageability for HWPing. Support NQA MIB display of multiple test results of a single test instance. Support storage and search for test groups in alphabetic order of the references. A single test instance can send over 3000 packets continuously. Support concurrent scheduling of test instances. Support the increase of sub-test instances from 150 to 1000. The test types supported include ICMP, UDP, Jitter, DNS, HTTP and FTP. Of them, the number of concurrent FTP tests can reach 50, and the number of concurrent tests on ICMP to the same IP address can reach 5. Support the removal of all test instances (supporting CLI and NMS configuration).
Support classifying HTTP statistics based on DNS resolution, TCP connection and transaction time. FTP statistics can include the measurement of the file downloading rate. Support the configuration of the file path and the uploaded file size during FTP testing (supporting CLI and NMS configuration). Add DNS measurement. Support the DNS test configuration count.
II.
HWPing Threshold Statistics Requirement
Based on the existing threshold alarm function, HWPing supports a new function that counts the number of monitored objects (including jitterrtt, jitterowd-sd, and jitterowd-ds) in a jitter test whose thresholds are exceeded, and this information can be displayed through a command.
III.
Jitter Test through ICMP
The original HWPing uses UDP packets for jitter tests to analyze the network performance. Now HWPing supports the use of timestamped ICMP packets for jitter tests to obtain network performance metrics.
IV.
HWPing Supports Unidirectional Performance Test
This version can test the unidirectional delay in the performance asymmetrical network. This feature needs the enabling of NTP. This feature does not involve new configuration commands. You can refer to the HWPing jitter test configuration and NTP configuration. It does not matter whether NTP or HWPING is configured. However, the unidirectional delay test result makes sense only when NTP synchronization has finished before the test.
1.4.17 Filtering of command logs to be sent to TACACS Server

Administrators can configure not to send command logs that contain certain keywords or match specific rules to the TACACS server.
1.4.18 Switchover between HWTACACS Server

Administrators can configure three HWTACACS servers as the authentication/Authorization/Accounting (AAA) server, including a primary server and two backup servers. The user can send AAA requests to the device (HWTACACS client), and the device then selects a server from the above three servers to send AAA packets
1.4.19 Switching over to local authentication in the case of incorrect TACACS configuration
Local authentication is used in the case of incorrect TACACS configuration: You can switch over to local authentication only when authentication fails. You can switch over to local authentication when the IP address of the server is incorrectly configured (servers unreachable). You can switch over to local authentication in the case of incorrect key configuration. The only option is to calculate the length of packets returned by servers and compare it
with the length of packets calculated through local key. If the lengths are not the same, you can tell that it is a key error. You can switch over to local authentication in the case of incorrect NAS-IP configuration, including errors that occurred before the socket was connected.
1.4.20 RADIUS and TACACS supports VRF Applications

This feature extends the applications of RADIUS and HWTACACS in MPLS/VPN networking environments, including: You can use commands to configure the VPN to which the RADIUS and HWTACACS schemes belong. The VPN name configured in the RADIUS and HWTACACS schemes can be displayed. The RADIUS and HWTACACS modules can receive and handle packets from private networks correctly. The RADIUS and HWTACACS modules can send packets to a specified server in a private network correctly. You can configure the nas-ip in RADIUS and HWTACACS schemes as a private network IP address. You can configure a global private network nas-ip. You can display the global private and public network nas-ip information.
1.4.21 SIP responses to options requests of Softswitch

Upon receiving an options request from the Softswich, the SIP protocol stack sends a response, so that the Softswtich can obtain the following information without waiting for the ringing of the opposite side: methods supported, content type, extension name and encoding/decoding method. In addition, the Softswitch can use options for heartbeat detection with SIP.
1.4.22 Supporting the RFC2833-Defined Packet Format for Carrying DTMF Signals
This feature uses the RTP packets to transmit DTMF numbers by using the RFC2833-defined packet format.
1.4.23 Supporting the VRRP Virtual Address Serving as the Voice Gateway Address
By using the VRRP virtual address as the voice gateway address, backup of the voice gateway can be implemented through the backup capability of VRRP.
1.4.24 Global Configuration of the QoS Module Supports Hot Swapping

This feature enables the global configuration of the QoS module to support hot swapping: After an interface board is pulled out, the match rules turn invalid. You can view the validity of rules by displaying the rule information. After an interface board is inserted, the rules referencing that interface should be valid. After an interface board is deleted, the rules referencing that interface are deleted as well.
1.4.25 Increase MTU of E1/T1 interface to 1620 1.4.26 CBWFQ Supports the Configuration of Remaining Bandwidth Percentage
In the original implementation, bandwidth configuration of LLQ and BQ involves the percentage configuration mode and the absolute value configuration mode. The two modes cannot be used for hybrid configuration. This feature allows the EF queue on the same interface to support the hybrid configuration mode of percentage bandwidth and absolute value bandwidth. Moreover, it offers the remaining bandwidth percentage configuration mode for AF queues. In this way, users networking requirements are satisfied in a better way, meeting the demand for handling different types of EF services on the same interface. Moreover, through the configuration of remaining bandwidth percentage for AF queues, the bandwidth requirements for AF queues are met. This feature removes the restriction from the original CBWFQ feature: if the percentage configuration mode is adopted for LR in the main policy, that configuration mode must be used for queues in the sub-policies.
1.4.27 Using QoS CAR to Implement Address-by-Address Rate Limitation Based on Network Segments
QoS CAR is a solution to traffic policing. To limit the rate of a host at a certain IP address, you need to configure the IP address-based CAR policy. However, one such policy can limit the rate of one host only. To address this issue, this feature can use simple commands to configure a network segment-based CAR ACL, and to apply that ACL in the CAR policy, thus restricting the rate of the entire network segment. Meanwhile, when configuring the network segment-based CAR ACL, you can use parameters to restrict the rate of each host or the rate of the entire network segment.
1.4.28 QoS extension

Support CAR in FRTS classes Support to remark DSCP in CAR behavior
1.4.29 X2T Supports Carrying the Called Number

The feature implements the routers function that X2T carries the called X.121 address. After this function is enabled, the packets sent by X.25 terminals can be relayed multiple times by means of X2T.
1.4.30 XOT Supports DNSBased X.121 Address Resolution

The DNSbased X.121 address resolution function is used to support XOT of the SVC application. This function takes the idea of DNS, putting the mapping relations between X.121 addresses and IP addresses in a network on the same DNS server for unified maintenance. The mapping relations between X.121 addresses and IP addresses are similar to those between domain names and IP addresses. When sending packets, XOT sends resolution requests to the DNS Server based on the current X.25 route configuration. Upon receiving the requests, the DNS Server responds with the resolution replies. According to the replies, the destination IP addresses of the X.25 packets can be determined. Centralized maintenance of the mapping between X.121 addresses and IP addresses reduces the complexity, improves the maintenance efficiency, better adapts to the changes of mapping relations, and simplifies the XOT switching configuration.
1.4.31 X25 CLI commands enhancement

I.
Adding the Command for Deleting X.25 Facility
This feature offers the function of deleting the windows size and packet size parameters from the X.25 facility field, meeting the requirements for internetworking with different devices.
II.
X25 Switching Supports Packet Fragmentation and Reassembly
This feature adds the function of disabling X.25 from using the windows size and packet size parameters in the facility field to conduct flow negotiation. Instead, flow control is conducted solely based on the local user configuration. Moreover, the packet reassembly and fragmentation functions are added when the device is undergoing X.25 switching.
III.
T4 Parameter Is Supported
The T4 parameter is added based on LAPB (Link Access Procedure on B-Channel). Moreover, after N2 RR is sent upon T4 switching over to T1, T1 sends SABM messages continuously.
IV.
X.25 Many-to-Many Address Translation Is Implemented
It is implemented that a command with the regular expression can replace multiple x25 switch svc commands.
1.4.32 HoPE Supports the Sending of Detailed Routes

In the SPE/UPE networking environment, SPE not only can send default routes to UPE, but can send detailed routes. Meanwhile, you can control which detailed routes are sent to which UPE by extending the community attributes, thus isolating the mutual access of some Sites via UPE in the same VPN.
1.4.33 Policy-Based Routing Supports Auto-Detect

By configuring the association between policy-based routing (PBR) and the auto-detect function, collaboration between the two can be implemented. That is, when the autodetect function finds a route currently used by PBR fails, PBR will be notified of this. Then, PBR can conduct link switchover by either selecting another route automatically or using the route determined by the dynamic routing protocol.
1.4.34 RIP Supports Modifying the COST Value of Particular Routes

This feature allows routing policies to filter certain receiving/sending RIP routes and to change their cost values to a specified one. Before this function is implemented, the metric-in and metric-out commands can be used on an interface to configure the cost values of RIP routes advertised by that interface. The problem with the old method is that, the cost values of routes advertised by that interface all changed and precise control cannot be conducted, for example, you cannot modify the cost value of routes in a specified network segment.
1.4.35 Displaying the Device Manufacturing Information

You can use the display device manuinfo command to view the device manufacturing information, including: DEVICE_NAME
10
DEVICE_SERIAL_NUMBER MAC_ADDRESS MANUFACTURING_DATE VENDOR_NAME
1.4.36 Supporting Levellized Logging of Commands

You can use the new command record { log | accounting } level INTEGER<0-3> to configure levellized logging of commands or levellized accounting of commands. After this command is configured, the system starts to log the commands or count the commands only after the command at or higher than the specified is executed.
1.4.37 Telnet Server Supports Displaying or Hiding the Copyright Notice upon User Login
The new command [undo] vty copyright-info enable applies to all the login users. The vty copyright-info enable command restores the default. That is, the copyright notice is shown when any telnet users logs in. The undo vty copyright-info enable command hides the copyright notice when any telnet user logs in.
1.4.38 Supporting SNMP Query of ADSL/G.SHDSL Uplink/Downlink Rate

After the ADSL interface and G.SHDSL interface are connected on a physical link, a work rate is obtained through link negotiation. Such rate is inconsistent with the baud rate of the interfaces. Normally, the uplink rate and downlink rate of these two interfaces are different. This feature adds two read-only MIB tables, and the table index is the index of the ADSL interface and G.SHDSL interface used to read the actual work rate of these two interfaces through SNMP.
1.4.39 Supporting the Statistics of Traffic Within the Last Five Minutes
Using the private MIB, you can view the statistics of traffic within the last five minutes on interfaces via the SNMP NMS.
1.4.40 IP Host Command Supports Telnet Port Configuration

The ip host command is used to configure the correspondence between host names and IP addresses. This feature adds the option of specifying a port number to that command, recording the correspondence between IP addresses and ports simply through the domain names. This configuration applies to the telnet command only, and is mainly used to support reverse telnet.
1.4.41 NAT Server Supports Load Balancing Among Servers in the Same Server Group on the Internal Network
This feature uses NAT Server to implement load balancing among servers in the same server group on the internal network. Each type of users sees only one server, while multiple internal servers are working for them. NAT Server allocates users access based on the current load status of respective servers, implementing load sharing.
11
To implement load sharing, you need to define a server group on the NAT device and add the internal network servers offering the same service to that server group. Moreover, you need to set the right of each internal network server based on its handling capacity. Apply that server group to the public network interface on the NAT device and specify a public network address and port, that is, configure a server group-style NAT Server. When an external access reaches the NAT device, the NAT Server selects an appropriate internal network server based on the load and right of each internal network server, directing that access to that internal network server, and thus implementing load sharing in the server group.
1.4.42 PBR Supports Modifying the DF Value of IP Headers

In special networking environments like GRE, etc, the DF bit of a packet can be set to 1 while the packet size might exceed 1500 bytes. In that case, if fragmentation is needed, this configuration can be used.
1.5 New Bug Fixes for V3.11

The following bugs were fixed in this release.
1.5.1 Backup IPSec on Loopback Interface

A backup IPSec Tunnel created between two loopback interfaces does not work when the main interface is down.
1.5.2 Outputing debugging messages to logbuffer

Debugging messages cannot be output to logbuffer
1.5.3 CLI command display ft1 displays the main physical FT1 interface and all the subinterfaces that are assocated with it.
Executing CLI command display ft1 display the main physical interface as well as all the sub-interfaces that are associated with it.
1.5.4 Frame Relay statistics are not computed correctly

The incoming and outgoing packets are not counted properly in the Frame Relay circuit
1.5.5 5012/FT1 module: No message indicating FT1 is in BERT test mode

When BERT test is executed on a FT1 module on a 5012 router, there is no message indicating the interface is in BERT test mode.
1.6 New Software Support for FIC Modules in V3.11

3C# 3C14832 3C14833 3C14834 3C14836A Description ROUTER 4-Port CE1/PRI FIC ROUTER 8-Port CE1/PRI 120 FIC ROUTER 4-Port Fractional E1 FIC ROUTER 4-Port Fractional T1 FIC
12
3C14850 3C14851A
ROUTER 1-Port CE3 FIC ROUTER 1-Port FT3/CT3 FIC
2. Software Issues Resolved in Previous Releases

2.1 Issues Resolved in Router 5000 Bootrom
V9.21 corrects an issue with the use of RoHS-compliant memory chips in which the clash memory sometimes cause software upgrade to fail. V9.23 improves compatibility with Transend, Kingston, and Ramaxel memory chips.
2.2 Software Issues Resolved in v3.00

The following issues have been resolved since the last release, v2.41, of this software. VCX V7000 Inter-Operability Issue with Router 5000/6000: Removal of the Master SIP server from a voice configuration will remove the following from the configuration: Slave SIP server if one exists address sip proxy for SIP VoIP entities When saving a configuration to a non-existing directory the following message displays: Cannot open the configuration file, this may be caused by insufficient memory space. This is an incorrect message and is displayed when the user is trying to save a file to a non-existent directory. To solve the problem, create the directory first. When rebooting the router, the Current Configuration change detection sometimes detects changes when there were none, and a warning message is displayed. Display interface for an ATM interface with sub-interfaces will display the same cumulative statistical information - no individual statistics are provided; Instead use, display atm interface to show more individualized statistics. ACL matches for IPSec only count the first packet used to open the tunnel - subsequent packets will be logged in the IPSec SA. A frame relay link will not come up if the IP Address is changed, because the fr inarp table is not refreshed. The user must reset the fr inarp table manually. The select-rule type-first command under the voice/dial view includes an option for VoFR. VoFR is not supported in this release. Make it the last choice in the select list. Voice is barely audible when an NBX T1 is attached to the router configured running QSIG master (network side). Voice quality is poor over a T1 link when the T1VI module is configured for QSIG master (configured for ISDN network side.). QSIG master functions correctly over E1 using the E1VI module. CLI doesnt support pre-defined ringing tones for the following countries: Egypt, South Africa, and Australia.
13
MIB object isdnBearerOperStatus (OID 1.3.6.1.2.1.10.20.1.2.1.1.2) will report the status of ISDN B channel The standby timer delay 0 0 command will activate standby interface immediately once the cable on the main interface is disconnected DHCP relay agent will recognize BOOTP and DHCP protocol messages and process (relay) them appropriately.
2.3 Documentation Issues Resolved in v3.00

User Documentation issues resolved since the last release, v2.41, of this software. Spanning Tree is listed as not supported in Router 5000-6000 Configuration Guide. Spanning Tree is supported. Ike peer-name does not seem to work as documented in the NAT-Traversal Example; In order to get name authentication to work, both sides must have id-type name configured. Both sides must have remote-names configured, and one side must have remote-ip configured (the initiator). Changing MLPPP parameters will not take effect until the Virtual-Template or Mp-group is reset via bringing down all the physical interfaces and bringing them back up again. A Router running DHCP client cannot obtain the default gateway address automatically. This parameter must be manually configured. Where Static Routes point to Ethernet interfaces, ARP responses are ignored. The nexthop must be specified for static routes on Ethernet interfaces. The router will continuously reboot if the MSDP configuration references an interface that is not available; this would most likely occur when a module is removed or replaced and the saved configuration still has a reference to the old interface. IPSec card-proposal does not have an option for ESP encapsulation. Those options do not show up until the use command is issued to specify which encryption module to use. All busy signals on voice cards are the same type: fast-busy signal.

The following issues have been resolved since the v2.30/2.31 release of this software. VCX calls fail across a NAT network. NBX phones fail to load across a NAT network. IPX is now supported on Frame Relay, Ethernet and PPP. IPX is not supported on, HDLC, and X25. When setting the main/backup images, the file pointer does not point to flash:/ by default; the flash device must be included in the path; for example, bootfile main flash:/main.bin rather than just bootfile main main.bin. When there is a high traffic load on the router, and the CLI response time slows, the CPU usage information is not accurately displayed. Gigabit Ethernet and POS interfaces do not support auto-install.
14
SYS MGMT Router 5000 series routers report that the system returned to service via power-on even if the router is warm booted. IPSEC policy with a deny rule before a more general permit rule will not enforce the deny rule. Resetting the IKE SA does not reset the tunnel completely; Resetting both sides at the same time is currently required to completely reset the tunnel. IPSec tunnel resets (resetting IKE SA/IPSec SA) may result in router reboot. CBR traffic approaching PCR on a PVC will experience packet loss when UBR traffic on a separate PVC is introduced on the ATM link Service classes on IMA group interfaces have cell rate limits of just one T1/E1 Link regardless of how many links are in the bundle.

The following issues have been resolved since the v2.11 release of this software. In some specific circumstances, displaying virtual-access on a router with MLPPP may cause a reboot. To resolve this, use the command, Display Virtual Template instead. A virtual baud rate setting of 786000 is not available on a serial interface. The state of Promiscuous mode on an Ethernet interface is not shown in the display current command. To view the state, use the display interface Ethernet x/x command. Gigabit Ethernet interfaces will not forward traffic if they are assigned to a bridge-set. Gigabit interfaces should only be assigned to routed interfaces. When a bridge-set is removed from an Ethernet interface the message Promiscuous operation mode was removed automatically is displayed. However, promiscuous mode may not have been disabled on that interface. Manually verify that Promiscuous mode has been reset using the display interface Ethernet x/x command. If it has not been disabled, use the undo promiscuous command in the interface view. There is no support for ISDN switch type DMS100. Frame Relay sub-interface definition types (P2MP, P2P) are not displayed. To determine the interface type, display the interface as follows: Display fr pvc interface <interface> <dlci>. Frame Relay Classes that contain Frame Relay QoS parameters can be applied to PVCs even though Frame Relay Traffic Shaping is not enabled. Frame Relay Traffic Shaping must be enabled for PVC queues to be functional. When IPSec policies are configured on both the incoming and outgoing interfaces, one of the interfaces needs to have IPSec over GRE configured to allow multicast IP fragments to pass through the router without problems. The ability to add inline comments to describe an ACL as a whole is available; however the ability to add a specific description to a rule is not available. Example: if an ACL is long and complicated, inline comments for the rule cannot be added. Save the current configuration and then edit in descriptive comments to that configuration. FDL and remote loop back issues. B8ZS and ESF issues.
15
LBO range issues. Alarm Threshold Settings issues. Issues with viewing current alarms and error registers. Various issues with local, payload, and remote loopbacks. DEBUG commands on the serial interface and physical layer characteristics of the router modules. UNDO of the DEBUG function. Constant DEBUG output issues on the FT1 SIC module. No indication of resetting (zeroing) traffic statistics. Lack of input and output rates displayed in bits per second as part of traffic statistics output. A logging error where VPN information is logged erroneously, when there was no actual VPN configuration. Only one system user at a time able to access the console. With the display interface command, packet flow shows double that of the Ethernet interfaces. Inaccurate display information with ACL statistics, not properly incrementing for permit statements. Frame Relay statistics discrepancies on the sub-interface packet counts. Statistics on the FT1 and T1 interfaces not properly zeroed upon reset command, reset counter interface. Banner information is lost upon FTP or TFTP while obtaining router information. A packet loss problem with small packet sizes configured. No display of trap settings with status. NAT traversal is not compatible with Cisco routers. IPsec tunnel is not established with Cisco routers when a NAT device is in the path. Only one security association is used for all traffic flows. IPsec SA is not flow based. IPSec SAs originated from 3COM routers will be ACL based. To obtain flow-based functionality, create multiple ACLs with one rule each.

The following issues have been resolved since the v2.20 release of this software. Changing the speed and duplex on the Gigabit Ethernet Module does not take effect without resetting the interface manually. A manual shutdown and then undo shutdown is required to have the changes take effect. Loopback LED remains lit solid after remote side sends the loop down code. No Loopback LED indicator Banners edited offline in the proper format will be discarded when loaded into the system via ftp/tftp
16
D4, D4/AMI and ones density are not supported. FDL AT&T payload option issues. No fdl-att-plb-up and fdl-att-plb-down are available. Alarm LED No Alarm LED indicator BERT issues Bits received since test started and Bits received since latest sync do not match on a perfect loop NAT display issues NAT sessions do not display NO-PAT
2.7 User Documentation Issues resolved in v2.20

The following user Documentation issues have been resolved since the v2.20 release of this software. ACL numbering scheme is different from those documented in the Command Reference Manual. Use the following 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. The virtualbaudrate command is non-existent in the Command Index. Use the virtualbaudrate command in the Command Line Interface (CLI).
[XXXX-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
2.8 Software Issues Resolved in v2.30/31

The following issues have been resolved since the last release, v2.21, of this software.
17
If the user cut and pastes within the BootRom menu to fill in fields (such as filenames for TFTP downloads) the display will only show a maximum of 8 characters. If the filename is longer it will be accepted by the system, but will not display characters beyond the initial 8. The more command truncates large config files(>17KB) on the 5012 routers. If the file needing to be read is not the saved configuration, transfer the file to a PC disk, and read it from there. If it is the saved configuration, read it with the display savedconfiguration command. Display ft1 will display the same statistics multiple times, once for each Frame Relay interface/sub-interface configured. The current IMA aggregate baud rate does not change when links are added or removed, when using the display interface command. This is a display problem only. The Gigabit Ethernet module does not support half duplex mode at 100 Mb setting. Display fr pvc statistics do not account for the outbound packets. The bridge <x> mac-address command for setting a static MAC entry for a gigabit Ethernet interface is not supported. The bridge <x> mac-address <xxxx-xxxx-xxxx> permit interface command is not an option for a Gigabit type interface. This command is not supported for Gigabit interfaces. CRC and PAD errors on the 1-Port ADSL Module interfere with even the lowest traffic loads, of expected normal operation Example 256K traffic on 8Mb link. PIM is not supported over an IPsec tunnel. PIM hellos are rejected over an IPSec Tunnel. The first IKE peer with local-address defined will have its address be used for all IKE peers in the policy. ATM VBR service classes will fail to be set at Peak Cell Rates higher than 124492 kbps (for OC3-ATM), 41923 kbps (for T3-ATM) and 33340 kbps (for E3-ATM).
2.9 Documentation Issues Resolved in v2.30/31

User Documentation issues resolved since the last release, v2.21, of this software. Named access list is documented but not supported. Name based ACLs, as listed in the command reference manual, are not supported.
3. Known Issues in Release v3.01

3.1 System Access
The router does not allow configuring of an 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. 3Com recommends using underscores instead of spaces as separation delimiters. To get ftp mputs to work properly from a client, ftp update normal must be set on the router.
18
3.2 SNMP
The router does not respond to SNMP when the user is logged into the System View. This causes Network Management Systems such as 3Com Router Manager and 3Com Network Director to generate errors. To resolve this, exit the System View. The Frame Relay MIB does not use the latest version of the RFC 2115. As a result, public MIB variables for troubleshooting Frame Relay performance problems are not supported; (e.g. frCircuitLogicalIfIndex) from the current FRAME_RELAY-DTE-MIB (RFC 2115) The router will send an initial invalid trap packet upon link down/up event, followed by the correct Trap packet. Ignore the first trap packet, the second packet is correct.
3.3 System Management

On RPU2s when booting from the compact flash, it is possible to get the following error on boot up: Error encountered during checking disk, format the disk! and the boot will not complete. Power down the router and power it back up to clear the problem. Analog Modem debugging shows internal activity when no cable is connected. This indicates that the modem is active and ready to receive or make calls. There is no way to recover if both the Bootrom password and the console password are lost. If both passwords are lost, the router must be returned to 3Com for repair (RMA). FTP user cannot be cleared; set the ftp time-out to 1 minute to clear an inactive session rather than waiting the 30 minutes set by default. The display current-configuration command with a filter will not recognize the underscore character(_) alone. Use the backslash character (\) in front of the underscore to get the desired result. For example, display current-configuration | begin bgp\_peer will display the configuration starting with the line containing bgp_peer CPU Usage history graph has the time scale backwards; the right side is the most recent history. A 1-Port Channelized E3 MIM card will not operate if inserted in slot 0 on the 5642 or slot 1 on the 5232. Select a different slot for the E3.
3.4 Interface Management

When the Dialer interfaces toggles state (up or down), minor packet loss will occur for any packet passing through the router. Interface statistics with a flow-interval of under 10 seconds are not accurate. Do not enter flow- interval values under 10 seconds. The Virtual-Ethernet interface protocol state displays as being down when running PPPoE. This is the normal operating state of the Virtual-Ethernet interface. On an ISDN interface, the Line Protocol state is up when no cable is attached to the port on the interface. It is best to observe the interfaces Current State. The Current State will be down if no cable is attached to the interface even though the Line Protocol will show it as up. A Frame Relay sub-interface that has been configured as Down transmits packets.
19
Displaying a Fractional E1 interface displays a Frame Format equal to NONE. The actual Frame Format is no-crc. Frame Relay Payload Compression is displayed for PVC even after it is removed. Reset the interface to resolve. An ATM PVC that is set with rate limiting and is heavily oversubscribed with data, will fail to pass traffic. Other PVCs continue to work on the link. Changing the speed on a modem interface resets the interface. Do not change the modem interface speed while a dialup session is active. The activity LED on the T3 ATM Module indicates heavy activity regardless of the amount of traffic passing through it. Regardless of actual traffic running or not, T3 and E3 activity LEDs blink constantly. The Bridge-Template interface does not give flow / load interval statistics. When load is over 4500 active streams, netstream takes an extra few minutes to send all export data after a flow has expired.
3.5 Link Layer Protocol

Alarm-threshold values are not configurable when a T1-line is configured within a T3 link. Level-4 alarm-threshold is not supported for T1 links setup for SF frame format. The CLI will not report an error. ATM AIS/RDI statistics are inaccurate. ATM OAM Segment Loop cells are not supported. Frame Relay PVCs can be modified when they are part of a PVC switching endpoint. Verify first that the interface is not a PVC endpoint before making any changes, else traffic may be disrupted. There is no DEBUG support for Multilink Fragmentation (FRF.16.1). Status and statistics for Multilink Fragmentation (FRF.16.1) cannot be viewed There is no support for ISDN switch type AT&T for BRI U interfaces. The router Command Line Interface and the documentation specifically states that AT&T is only supported on PRI interfaces. The default isdn protocol-type dss1 will connect to switches using AT&T switch type on a BRI interface. This was tested with Lucent 5E, otherwise known as AT&T 5ess. Bridge-set traffic cannot be routed even though a bridge-set can be configured with an IP address. FRF.9 Compression is still displayed upon viewing of PVC statistics, after the PVC is remapped without FRF.9. After re-mapping a PVC to exclude FRF.9 compression, reset the interface in order to clear any reference to FRF.9 When removing FRF.9 compression settings from a frame relay static address mapping, the interface needs to be reset (shutdown/undo shutdown) for the configuration to take place.
20
When the ATM OAM and PVC states are all down, the ATM interface is still showing state:UP and Line:UP; Use display atm pvc-info to see the true state of the individual PVCs. ATM statistics may be wrong if the traffic rate exceeds the Class of Service settings configured. PPP STAC compression is not supported on the POS interface. ATM OAM up/down timers for transitioning the PVC State are not accurate. ATM T3/E3 Modules require all cables to be connected before link LEDs will be lit.
3.6 Network Protocol

PPP, Frame relay, HDLC, and E1 interfaces do not support DHCP Global subaddress mode. Certain web sites cannot be accessed when using DSL interfaces. To resolve this, set the outgoing router (WAN) physical or virtual interface to 1410 as the maximum segment size for TCP. The DHCP Server does not remember the DHCP clients after a reboot. The DHCP lease expiration, client reboot or client renew request will repopulate the DHCP clients table transparent to the user. ICMP type 3 messages are generated for some but not all instances in RFC 1812 (Section 5.2.7.1). DHCP option 14 cannot be configured. There are no CLI commands for option 14.
3.7 Routing Protocol

When BGP changes states, minor packet loss will occur at the instance of the change, for any packet passing through the router. 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 differing baud rate, the interface has to be configured with the virtualbaudrate command. Configure this command using the same baud rate as the DCE. After configuring, shut down and restart the interface. Undo RIP from interface view removes RIP globally. To remove RIP from interface view use the command, Undo RIP work. BGP route dampening does not work for IBGP routes. BGP dampening is designed to work only for EBGP routes The 3Com router will not exchange RIP Updates with various 3rd Party vendors equipment when MD5 usual implementation is configured. The 3Com router will only exchange RIP Updates with a 3rd Party vendors equipment when MD5 NonStandard implementation is configured. Use Usual to exchange RIP Updates between 3Com routers. The BGP route is not advertised if the IGP route is present in the forwarding table. Import the route into BGP from the protocol which owns the route in the forwarding table. RIP Poison Reverse is not supported.
21
IPX does not support X25. IPX is supported on HDLC, Frame Relay, Ethernet, and PPP. The BGP received and advertised routes for a particular peer (display bgp routing-table peer <x.x.x.x> received|advertised) are not displayed in numerical order. With OAM and PVC states both down, the interface is still considered up and the directly connected route is not withdrawn from the routing table; Along the same line, with OAM active, a PVCs going down does not have its learned routes deleted from the routing table. The router will need to rely on the individual routing protocols timeout feature to initiate route removal. Load Sharing statistics are not accurate when more than one next-hop router is reachable via the same physical interface. BGP Auto-summary does not work with the BGP Network command; Auto-Summary works in all other cases. Redistribution of IGP routes into IBGP will not have the IGP next-hop. Instead, the next hop will always be the router doing the redistribution.
3.8 Multicast Protocol

The default value for the IGMP query interval (60 seconds) does not match the recommended value in RFC 2236 (125 seconds). Set the query interval to match the query interval of other routers in the network. PIM is not supported with IP unnumbered FR interfaces. An IP address must be assigned to the FR interface.
3.9 Security/VPN
The encryption card does not perform as well when passing large byte data (e.g. anything over 1464 bytes for 3DES/SHA1). Display firewall ethernet-frame-filter all does not work. Specify the exact interface to get the desired information. NAT traversal does not work in IKE Main Mode. IKE Aggressive Mode is required for NAT traversal to function properly. Packets with internal addresses appear outside the NAT boundary. NAT does not translate ESP or IGMP packets. NAT does not translate any IP protocols other than ICMP, TCP, UDP, and GRE (with respect to PPTP) The firewall drops FTP connections when ASPF is configured to filter TCP. ASPF must be configured with TCP and FTP together. With CRL checking enabled by default, certificate enrollment cannot be performed and an IPsec tunnel cannot be established without the CRL on the router. CRL checking must be disabled for certificate enrollment and the IPsec tunnel if the CRL is not on the router. If an undefined ACL is used in a configuration, a warning message is not displayed. In X.509 the CRL URL format determines which protocol is used to retrieve CRL from the CA server. Use one of the following CLI commands depending on specific Server support:
HTTP: LDAP: crl url http://<CA Server IP>/<CRL DP> crl url ldap://<CA Server IP>/<CRL DP>
22
SCEP:
crl url "scep"
Manual Ipsec only protects the first match in an ACL with multiple rules; Recommendation: make only one rule per ACL to protect all desired traffic. IPSec transform negotiation is not compatible with Cisco; configure only one transform for any policy interacting with a Cisco router. IKE Keepalive is not accepted by a Cisco router and tears down the tunnel. Do not use the ike sa keepalive-timer timeout command (default). Junipers IPSec implementation does not interoperate with the 3Com Router 5000 Family with respect to IPSec Fragmentation. If possible, set the MTU to 1438 or lower on devices that will be using the tunnel to avoid having to fragment IPSec packets. DvPN is not supported Debug firewall packet (denied/permitted) no longer works; Use debug firewall all instead.
3.10 Quality of Service (QoS)

CBR miscalculates the remaining Bandwidth available after multiple PVCs oversubscribe the link. An undo service will recover all but 32kbps of the available bandwidth. A router reboot will recover the rest. Once a QOS policy is applied use the CLI command reset IP Fast Cache to re-apply the QoS functions properly. An under provisioned ATM service class results in link failure for that PVC only. DAR doesn't detect TFTP traffic fully. FTP data is not correctly detected by DAR if there is a pause in user activity with the FTP server for over 5 minutes. DAR reports application packets going out an interface even if it's just ARPs being sent to find the destination MACs in order to forward those application packets. QoS CBQ incorrectly drops packets when the guaranteed rate is equal to the traffic rate on the Serial interfaces. This is not a problem on Ethernet/GigabitEthernet interfaces Hostname support for target host in HWPing is good only if it can be resolved immediately; the hostname is only used for ease of use; the saved configuration will have the resolved ip address.
3.11 MPLS
If there is no response, from pinging a CE Router from a PE Router within an MPLS/BGP L3 network 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. In an interface view, the undo mpls ldp command will provide the warning WARNING: Executing this command will remove MPLS LDP on all interfaces on this router. Use MPLS LDP DISABLE to remove MPLS LDP on this interface only. Do you wish to continue? [Y/N] Regardless of what the user responds here, yes or no, the CLI will return to the system view instead of the interface view. JK
23
3.12 Voice and Router Interoperability 3Com VCX and NBX issues
SIP compatibility mode is required for calls between 3Com Convergence Center Clients to router 5000/6000 analog phones. Execute the sip-comp server command from the voice view on the router. The undo command does not work for the mode command in the controller/cas view. To reset the mode to the default value use the mode itu-t command. By default, voice entities with the same match criteria are chosen at random. To prioritize VOIP entities use the command select-rule type-first 213 command in the voice/dial view. Voice activity detection (VAD) is only supported when the G.723 codec is used. CAS is not supported on the T1VI module. RADIUS authentication and accounting is not supported for H.323. Only voice traffic is supported on E1 and T1 voice cards. This applies to Router 5000 & 6000 platforms. Data traffic is not supported over Router 5000 and 6000 Voice cards. FIC Voice Cards are not hot-swappable; they must be inserted/removed with the power off. A short static noise at the tail-end of the audio transmission is experienced when calls are placed across Router 5000 and Router 6000 FXS cards. FXS ports do not support modem operations. One-Stage dialing through POTS may take up to 5 rings before rings are heard on the remote side. Local ringing occurs before the remote side actually hears the rings. While accessing an outside line (two-stage dialing) the second dial tone takes a little longer than normal to be heard; wait for the second dial tone before proceeding. Caller-ID Name is not supported; the router does not generate the names tied to a local phone line. Analog voice quality is reduced when using analog lines across three or more routers. The users call forwarding option is not retained after a router reboot; the user must reprogram call forwarding after a router reboot to ensure proper forwarding operation. The router cannot detect when its own E&M, FXO/FXS, or E1 CAS E&M connections are down. Therefore, if a voice entity using one of these interfaces is routing calls, and the interface goes down, the router will not check for a voice entity with equivalent match criteria to use. The router will continue to attempt to send calls through the down interface. CLI doesnt support pre-defined ringing tones for the following countries: Colombia, EU, Dubai. FXO ports on the 5000 series routers might not pick up when receiving a call from a device other than a 3COM router 3Com VCX 7000 phones do not support SIP outband mode. DTMF digits sent from router 5000/6000 to VCX phones will be disregarded.
24
3.13 Documentation Errors

The steps to bind the voice MAX-CALL function to a voice entity described in the user guide, is not clear. When configuring voice MAX-CALL you must apply this function inside the voice entity view. Bridging over Frame Relay is not listed as being supported in the Router 5000-6000 Configuration Guide. Bridging over Frame Relay is supported. DVPN service is not enabled by default as stated in the user documentation. The user must enable it if needed. Firewall ASPF UDP detection does not support the following UDP based applications: TFTP, SSH, DHCP The documentation incorrectly states that a VLAN port link type can be set to access, hybT operations for HWPing will always send a 50 byte file which does not have to exist on the router; FTP GET operations will timeout if the file is large; just increase the timeout until "Operation timeout" no longer registers a non-zero value.
4. Known Issues in Release v3.11

4.1 System Management
Application download via NET will not prompt to overwrite a file if the target name matches a name already on the flash.
4.2 Security/VPN
IPSec SA renegotiation happens much earlier than the SA byte duration and before the SA time duration when load on the tunnel is low (under 50%). The "undo ips policy" command if typed as stated will not return an error. This command does nothing. Use "undo ipsec policy" in interface view to remove the ipsec policy.
4.3 Voice and Router Interoperability 3Com VCX and NBX issues
When multiple subscriber lines could be used for an outgoing call, if a line happens to be down for some reason (cable disconnect, etc), the router will still try to use that line as an option just because it was configured. Do not configure lines that are not ready for use (not cabled up).
5. Upgrading Software
This section describes how to upgrade the software in your 3Com Router.
5.1 Upgrading the Router 5000 Software

The following diagram shows the process to upgrade the Boot ROM and Comware images under the Comware V3 environment
25
Start Check Boot ROM and software versions Upgrade Boot ROM? Y Choose correct Boot ROM Upgrade N
Upgrade software? Y Choose correct software Choose upgrade mode Via netwrok interface XModem upgrade TFTP upgrade Upgrade End
Note: The entire Boot ROM image file in this section includes two segments: extended and basic. You can separately upgrade and back up the extended segment.
5.1.1 Understanding the Boot Menu

To view the routers boot menu: 1 Start the router; when the message Press Ctrl-B to enter Boot Menu .......... appears, press <Ctrl+B>. The console screen displays:
Please input bootrom password:
FTP upgrade
Enter the correct password (there is no password by default). The Boot menu is displayed, as shown below: (Note that the menu may be slightly different depending on the bootrom version)
Boot Menu: 1: Download application program with XMODEM
26
2: Download application program with NET 3: Set application file type 4: Display applications in Flash 5: Clear application super password 6: Reset console authentication 7: Start up and ignore configuration 8: Enter debugging environment 9: Boot Rom Operation Menu a: Do not check the version of the software b: Exit and reboot Enter your choice(1-b):
These options are described in sequence as follows:

I.
Boot Menu 1: Download the application image with XMODEM
Refer to the subsection Upgrading Software through XMODEM in this section.

II.
Boot Menu 2: Download the application image with NET
Refer to the subsection Upgrading the application image through Ethernet in this section. If you select this option, the following Net Port Download Menu appears:
Net Port Download Menu: 1: Change Net Parameter 2: Download From Net To Flash 3: Download From Net To SDRAM And Run 4: Upload the current config file to PC 5: Exit to Main Menu Enter your choice(1-5):1
III.
Boot Menu 3: Set application file type
Routers with more than 8 Mb of Flash provide a dual-image function. The system defines three default application files for booting the router (see below). If you want to change the order or the boot file, you can select this option from the Boot ROM menu and make modifications. The default names, types, and selected sequence of main, backup, and secure application files are described as follows: Main application file: default name is main.bin, file type M. This is the default file the system uses to boot. Backup application file: default name is backup.bin, file type B. This file will be used to boot system when the main file fails. Secure application file: default name is secure.bin, file type S. This file will be used to boot the router when the main and backup file fails. The system will display a booting failure message if the secure application file also fails. Table 1 Default names and types of the boot files Boot file Main boot file Backup boot file Secure boot file File name main.bin backup.bin secure.bin File type M B S
27
Notes: Only the application file types M, B, and S can be used to boot the system. Applications marked as N/A cannot be used to boot the router. The names of the applications in Flash can be modified using CLI commands after the router has started. Refer to the System Management document for more information on the CLI commands. The application file types M, B, and N/A can be modified in either the Boot ROM menu or by the CLI commands after the application is started. Modifications to the file type of applications with type S are not allowed. Because the secure boot file is the last file the system uses to boot properly, the file type of secure boot file is not allowed to be changed, nor is it derived from any other type of file. It can only be downloaded via the Boot ROM menu, and its name must be specified as secure.bin. If you change the file name of the secure file using rename command after the system has started, there is no secure boot file in Flash and you need to download it again. Only one file of each type (M, B, and S) can exist in Flash. For example, if a file of type M and a file of type B exist in Flash, it is impossible to have a second file type of M or B. If the file type of another application is to be changed to B, the existing file of type B will be changed to N/A. The name (including the extension) assigned to a boot file is recommended to be less than 16 characters.
Select <3> from the Boot menu. The console screen displays the following menu, provided four application image files exist in Flash memory:
M=MAIN B=BACKUP S=SECURE ************************************************************************* NO. Name Size Type Time 1 main.bin 5988025 M Jan/10/2006 10:10:10 2 backup.bin 5985198 B Jan/10/2006 10:10:10 3 a.bin 987491 N/A Jan/10/2006 10:10:10 4 secure.bin 5988022 S Jan/10/2006 10:10:10 ************************************************************************* 5 Exit to main menu Enter your choice(1-5): 3
In this menu select <3> to change the file type of a.bin. The console screen displays:
Set this file as: 1. Main 2. Backup 3. Exit Enter your choice(1-3):
To use a.bin as the main boot file, select <1> in this menu. When the modification is validated, the type of the original main file is changed to N/A., and a.bin will be used to boot the router
IV.
Boot Menu 4: Display applications in Flash.
This option is to display the existing applications (and their types) in Flash. The following information appears when you select option 4 in the Boot ROM menu (suppose that the above modification is validated).
M=MAIN B=BACKUP S=SECURE **************************************************************************
3Com Router 5000 and Router 6000 Family Release Notes Software v3.11 NO. Name Size Type Time 1 main.bin 5988025 N/A Jan/10/2006 10:10:10 2 backup.bin 5985198 B Jan/10/2006 10:10:10 3 a.bin 5987491 M Jan/10/2006 10:10:10 4 s_system.bin 5988022 S Jan/10/2006 10:10:10 ************************************************************************** There are <4> application files. Press <Enter> key to continue
28
Press <Enter> to return to Boot Menu.

V.
Boot Menu 5: Clear application super password.
Selecting this option allows users without system view privileges to access system view after a reboot. This, however, is a one-time operation. You must provide the super password at subsequent reboots.
VI.
Boot Menu 6: Reset console authentication.
This option allows you to log in from the console port without authentication and reset a password if needed Note that if not saved, the modified configuration will not survive a reboot, Select the option; exit and then restart the router. The screen displays Login authentication ignored, allowing you to log in from the console port without authentication. Note: This is a one-time operation. It takes effect at the first reboot. Console authentication is required however at subsequent reboots.
VII.
Boot Menu 7: Start up and ignore configuration.
Select <7> in the Boot Menu. The system sets an Ignore flag to Flash memory and displays:
Flag set successfully.
Thus, a default factory configuration will be used for booting. The system removes the Ignore flag after the reboot completes.
VIII.
Boot Menu 8: Enter debugging environment.
Enter the debugging environment to help resolve problems.

IX.
Boot Menu 9: Enter the Boot ROM operation menu.
Select <9> to enter Boot ROM Download Menu as follows for upgrade, backup, or recovery of the Boot ROM program:
Boot ROM Download Menu: 1: Download Boot ROM with XModem 2: Download Extended Segment of Boot ROM with XModem 3: Restore Extended Segment of Boot ROM from FLASH 4: Backup Extended Segment of Boot ROM to FLASH 5: Exit to Main Menu Enter your choice(1-5):
X.
Boot Menu a: Do not check the version of the software
Ignore software version check for backward compatibility. The likelihood exists that your upgrade attempt fails even when you select the correct software version. If the system prompts invalid version in this case, you can select <a> from the Main Menu to have the system skip version check during upgrade. This option applies only once when selected. When the router is rebooted, version checking is restored.
XI.
29
Boot Menu b: Exit and reboot
Select <b> to exit and reboot the router. Note: To enter Boot Menu, you must press <Ctrl+B> within three seconds after the information Press Ctrl-B to enter Boot Menu... appears. Otherwise, the system starts decompressing images. To re-enter the menu after that, you must reboot the router.
5.1.2 Upgrading Software through XMODEM

You can use the console port to upgrade the software using Xmodem without the need to set up a network environment.
I.
Upgrading the application image
Enter Boot Menu (refer back to the subsection Boot Menu in this section), press <1> to select the XMODEM protocol for downloading the application image. The router supports the following downloading speeds:
Please choose your download speed: 1: 9600 bps 2: 19200 bps 3: 38400 bps 4: 57600 bps 5: 115200 bps 6: Exit and reboot Enter your choice(1-6):
Select an appropriate download speed, <5> for 115200 bps for example. The console screen displays:
Download speed is 115200 bps. Change the terminal's speed to 115200 bps, and select XModem protocol. Press ENTER key when ready.
Change the baud rate on the console terminal (see Figure 5-4) to the software download speed, 115200 bps in this example. After that, select [Dial-in/Disconnect] and then [Dial-in/Dialing] to disconnect and reconnect the terminal. Press <Enter> to start downloading. The console screen displays:
Please Select Program File Downloading ... CCCCC
Note: To validate the new baud rate set on the console terminal, you must disconnect and then reconnect the terminal emulation program. 4 Select [Transfer/Send file] in the HyperTerminal window. The Send File dialog box is displayed:
30
Click Browse to select the application image file to be downloaded, select XMODEM from the Protocol drop down list, then click Send. The following dialog box appears:
After completing download, the system begins writing to Flash memory and upon its completion displays the following message:
Download completed.
For the R5000 series router, the system also prompts you to select the file type upon completion of the download.
please select file to be saved as 1. main application file 2. backup application file 3. secure application file 4. cancel downloading Enter your choice(1-4):
The system starts writing to Flash memory after you enter your choice and displays:
Writing to flash memory... Please wait,it needs a long time .Please wait... ######################################################## Writing FLASH Success. Please use 9600 bps.Press <ENTER> key to reboot the system.
Restore the baud rate of the console terminal to 9600 bps as prompted, disconnect the terminal and dial again. Then, you can see the system boot banner.
II.
Upgrading the entire Boot ROM image
Enter Boot Menu, and select <9> to enter Boot ROM Download Menu as follows:
31
Select <1> in Boot ROM Download Menu to download the Boot ROM image through XMODEM. Multiple download speeds are available. The subsequent steps are the same as those described in the Upgrading the application image section.
Caution: 3Com recommends that you upgrade the entire Boot ROM program only when necessary and with the guidance of technical staff, because no means is available for on-field recovery in case of an upgrade failure.
III.
Upgrading the extended segment of the Boot ROM image
1 2
Enter Boot Menu, select <9> to enter Boot ROM Download Menu. Select <2> in the menu to upgrade the extended segment of the Boot ROM image through XMODEM. Multiple speed options are available. The subsequent steps are the same as those described in the Upgrading the application image section.
Caution: This upgrade approach upgrades only a portion of the Boot ROM image, so you can make a second attempt if errors occur.
5.1.3 Backing up and Restoring the Extended Segment of the Boot ROM Image
I.
Back up the extended segment of the Boot ROM image to Flash memory
1 2
Enter Boot Menu, select <9> to enter Boot ROM Download Menu. In Boot ROM Download Menu, select <4> to copy the current extended segment to Flash memory.
Backup Extended Segment, are you sure?[Y/N]
Enter <Y>. For a successful backup, the console screen displays:

Writing to FLASH.Please wait...#### Backuping Boot ROM program to FLASH successed!
4
II.
When Boot ROM Download Menu appears again, select <5> to and reboot the router.
Restore the extended segment of the Boot ROM image from Flash memory
In case faults occur to the extended segment or the upgrade is done inadvertently, take these steps to restore the extended segment of the Boot ROM image from Flash memory to the Boot ROM: 1 2 Enter Boot Menu, select <9> to enter Boot ROM Download Menu. In Boot ROM Download Menu, select <3> to restore the extended segment from Flash memory.
Restore Extended Segment, are you sure?[Y/N]
Enter <Y>. The system starts restoring and if successful displays:

Writing to Boot ROM.Please wait...###### Restoring Boot ROM program successed!
When Boot ROM Download Menu appears again, select <5> to exit and reboot the router.
32
5.2 Upgrading the Software for the Router 6000/RPU

5.2.1 Boot Menu
Software maintenance uses the main Boot ROM menu and the small Boot ROM menu, for downloading and booting the application image and the main Boot ROM system respectively. Build up a configuration environment according to the section Setting up a Configuration Environment in the chapter Starting and Configuring the Router. Start the router. The console screen displays:
Do you want to go on checking the sdram? Yes or no(Y/N): Enter <N>. The screen displays: Press CTRL+A to Stop AutoBoot! Starting...
Press <Ctrl+A> within five seconds after the message Starting... appears. Then the system enters the small Boot ROM menu. Notes: To enter the small Boot ROM menu, you must press <Ctrl+A> within five seconds after the message Starting appears. Otherwise, the system enters the main Boot ROM menu if the system passes its system check. If you do not press <Ctrl+A> then, the system checks the code of the main system after the small system boots. If an error occurs during the system check or for some other reason, the system enters the small Boot ROM menu rather than the main Boot ROM menu.
5.2.2 Small Boot ROM Menu

After the system enters the small Boot ROM menu, the console screen displays:
============<SMALL-BOOTROM MENU(Ver 1.07)>============== | <1> Modify Serial Interface Parameter | | <2> Update LargeBootrom | | <3> Boot main system ========================================================= Enter your choice(1-3):
I.
Option 1: Modify Serial Interface Parameter
To modify the serial interface parameters: 1 Enter <1> in the small Boot ROM menu. The screen displays:
========================<BAUDRATE SET>========================= |Note: Change The HyperTerminal's Baudrate Accordingly. | |-----------------------<Baudrate Avaliable>-----------------| | <1> 9600(Default) | | <2> 19200 | | <3> 38400 | | <4> 57600 | | <5> 115200 |
33
================================================================ Enter Your Choice(1-5):
The default baud rate of the serial port is 9600 bps. By changing it to a higher baud rate, you can save the file downloading time. 2 Select a higher baud rate, <5> for 115200 bps for example, and press <Enter>. The screen displays:
Enter your choice(1-5): 5 Change The BaudRate On PC Side First!
In the HyperTerminal window, select File > Properties then click <Configure>. Set the baud rate, to 115200 for example, and click <OK>. For more information, refer to the subsection Setting terminal parameters in the section Setting up a Configuration Environment in the chapter Starting and Configuring the Router. Disconnect and redial to validate new parameters: a. Disconnect from the system:
b. Redial to validate serial interface parameters:
Note: The baud rate on the router is automatically reset to the default value of 9600 after the router reboot. Restore the baud rate in the HyperTerminal to 9600 bps (the default) after upgrading the Boot ROM. This is to ensure that information can be displayed on the console screen after system boot or reboot.
II.
Option 2: Update LargeBootrom
To upgrade the large Boot ROM system (the large Boot ROM) through the serial port, enter <2> in the small Boot ROM menu and choose to upgrade the large Boot ROM through Xmodem. Refer to the subsection Upgrading the main Boot ROM system in the section Upgrading Image Files Using Xmodem.
III.
Optoin 3: Boot main system
To boot the main Boot ROM system enter <3> in the small Boot ROM menu. The system copies the files from the main Boot ROM system to the SDRAM, and then
34
decompresses the boot file in the SDRAM and reboots them. After that, the system starts the main Boot ROM menu.
5.2.3 Main Boot ROM menu

During the boot process, the console screen displays:
******************************************************* * * * 3Com Routers BOOTROM, Version 5.25 * * * ******************************************************* Copyright (c) 2004-2007 3Com Corporation and its licensors. CPU type : IBM750FX CPU L2 Cache : 512KB CPU Clock Speed : 733MHz Memory Size : 256MB Press Ctrl+B to enter Boot Menu... 0
To enter the main Boot ROM menu, press <Ctrl+B> as prompted.
Note: To enter the main Boot ROM menu, press <Ctrl+B> within four seconds after startup; otherwise the system boots with the default mode. The system displays the following prompt:
Main Bootrom password:
Enter the Boot ROM password.
Note: You have three chances to provide the correct Boot ROM password (the initial setting is void). If you fail to do that, you need to reboot the system. After you enter the correct password, the console screen displays:
MAIN MENU =====================<MAIN-BOOTROM MENU>==================== | <1> Boot With Default Mode | <2> Boot From Flash | <3> Enter Serial SubMenu | <4> Enter Ethernet SubMenu | <5> Boot File Control | <6> Modify Bootrom Password | <7> Reset Console Authentication | <8> Ignore System Configuration | <9> Enter Debugging Environment | <a> Reboot ============================================================ Enter your choice(1-a): _
| | | | | | | | | |
Note: If Flash memory is used the first time, the Flash file system formats it when reading or writing the Flash file and displays the following information:
Formatting Flash, please waiting several minutes...done
I.
35
Option 1: Boot With Default Mode
To boot the main image with the default mode enter <1> in the main Boot ROM menu. The system downloads the main image to the SDRAM, and theN decompresses and runs it. The console screen displays:
Boot with default mode Booting from flash... The main boot file is <flash:/main.bin>
Note: Currently the RPU only supports to boot from Flash memory.
II.
Option 2: Boot From Flash
Enter <2> in the main Boot ROM menu to boot from Flash memory. The system downloads the application image to the SDRAM, and decompresses and runs it. The console screen displays:
Booting from flash The main boot file is <flash:/main.bin> Decompressing..................................done! Booting from main boot file!
III.
Option 3: Enter Serial SubMenu
Enter <3> in the main Boot ROM menu to enter the serial sub-menu. The console screen displays:
Boot from serial port. ======================<SERIAL SUB-MENU>======================== | <1> Download Program To SDRAM And Run | | <2> Download Main Boot File To Flash | | <3> Change Boot Parameter | | <4> Exit To Main Menu | =============================================================== Enter your choice(1-4): _
Enter <1> to have the system download the application image to the SDRAM through the serial interface using Xmodem, decompress, and run it.
Caution: An application loaded this way runs directly without being saved to Flash memory. When the router reboots, the loaded application is still the old version. Therefore, use this upgrade method with caution. Enter <2> to have the system download the main boot file to Flash memory using Xmodem. Enter <3> to modify the baud rate of the serial port on the RPU. The console screen displays:
Change serial port parameter. ========================<BAUDRATE SET>==================== |Note: Change The HyperTerminal's Baudrate Accordingly. | | Press Enter to exit with things untouched | |-------------------<Baudrate Avaliable>------------------| | <1> 9600(Default) | | <2> 19200 | | <3> 38400 | | <4> 57600 |
36
| <5> 115200 | ===========================================+============== Enter Your Choice(1-5):
The default baud rate of the serial port is 9600 bps. You can change it to a higher baud rate, 115200 for example by entering <5>. The console screen displays:
Enter your choice(1-5): 5 Change The BaudRate On PC Side First!
Change the baud rate of the console terminal. Disconnect the system and redial to validate the new baud rate. Refer back to the item Modify the serial interface parameters in the subsection Small Boot ROM menu in this section.
IV.
Enter <4> in the serial sub-menu to return to the main Boot ROM menu.
Option 4: Enter Ethernet SubMenu
Enter <4> in the main Boot ROM menu to access the Ethernet sub-menu. The console screen displays:
Boot from net port. =======================<ETHERNET SUB-MENU>====================== | <1> Download Program To SDRAM And Run | | <2> Download Main Boot File To Flash | | <3> Download Backup Boot File To Flash | | <4> Download Secure Boot File To Flash | | <5> Change Boot Parameter | | <6> Upload config file to PC | | <7> Exit To Main Menu | | <Ensure The Parameter Be Modified Before Downloading! > | =============================================================== Enter your choice(1-7):
Enter <1>to have the system download the application image directly to the SDRAM and run it there. The file is not written to Flash memory however and as a result cannot survive a reboot.
Caution: An application loaded this way runs directly without being saved to Flash memory. When the router reboots, the loaded application is still the old version. Therefore, use this upgrade method with caution. Enter <2>, <3>, or <4> to have the system download the main boot file, backup boot file, or secure boot file from the connected host to Flash memory through the Ethernet port. The system attempts booting with the three files in the order of main, backup, and secure. If it fails to boot with the secure boot file, it prompts the boot failure. The following table gives default names and types of the boot files Table 2. Default names and types of the boot files Boot file Main boot file Backup boot file Secure boot file File name main.bin backup.bin secure.bin File type M B S
37
Enter <5> to change the boot parameters. The console terminal displays:
Change boot parameter through net port Note: Two protocols for download, tftp & ftp. You can modify the flags following the menu. tftp--0x80, ftp--0x0. Available Boot Device: [wancom] '.' = clear field; '-' = go to previous field; ^D = quit boot device :wancom Ethernet device name processor number : 0 host name : host file name : c:/share/vxWorks Host file name inet on ethernet (e) : 192.168.0.90 IP address of the Ethernet port on the main control board inet on backplane (b) : host inet (h) : 192.168.0.91 Host IP address gateway inet (g) : user (u) : user FTP username ftp password (pw) (blank = use rsh): password FTP user password flags (f) : 0x0(FTP)/0x80(TFTP) File transfer type target name (tn) :main.bin startup script (s) : other (o) :
Enter a name behind the target name (tn) prompt for the file to be saved on Flash memory. Alternatively, you may choose not to enter any name and use the file name used for the last upgrade instead. If the file name already exists on Flash memory, the following message appears after the file is downloaded asking whether you need to overwrite the original file:
Loading...done 11162108 bytes downloaded. flash:/main.bin already exist. Overwrite it?(Y/N):
Enter <Y> to overwrite the original file or <N> to return to the Ethernet submenu. Enter <6> in the Ethernet sub-menu to upload the router config file to a PC. The console terminal displays:
Upload config file to PC through net port boot device unit number processor number file name inet on ethernet (e) host inet (h) user (u) ftp password (pw) flags (f) : : : : : : : : : wancom 0 0 R46XX-V3.30-0002.BIN 169.254.75.1 169.254.75.166 1 1 0x0
Attached TCP/IP interface to wancom0. Attaching network interface lo0... done. Invalid targetname, target file is set to be default.cfg
38
Upload fails!
V.
Enter <7> in the Ethernet sub-menu to return to the main Boot ROM menu.
Option 5: Boot File Control
To enter the boot file control sub-menu enter <5> in the main Boot ROM menu. The console screen displays:
Boot file control. =====================<BOOT FILE CONTROL>=============== | <1> Display Available Boot File | | <2> Set Main Boot File | | <3> Set Backup Boot File | | <4> Exit To Main Menu | ======================================================= Enter your choice(1-4):
Enter <1> to view the available boot files:

Available boot file(s): 'M' = MAIN, 'B' = BACKUP, 'S' = SECURE ------------------------------------------------------------[No.] [Type] [Date] [Time] [Size] [Name] 1 M Jan/12/2006 00:38:29 5534020 main.bin 2 B Jan/17/2006 11:27:43 5865492 backup.bin 3 S Jan/04/2006 23:09:24 5749340 secure.bin 4 N/A Jan/04/2006 23:09:24 5749340 router.bin ------------------------------------------------------------Press <Enter> to continue.
Press any key to return to the boot file control sub-menu. Notes: The application images for system boot can be type M, B and S, but not type N/A. You can store them in Flash memory, but only one for each. For example, if an M+B file exists, it is impossible to have another M or B file. If you change the file type of another file to B, the M+B file becomes a type M file. You can modify the file name of an application image in Flash memory using the command after it boots. For more information, refer to Comware V3 Operation Manual System Management. You cannot modify the file type of the type S application image file, but you can modify the file type of type M/B and N/A application image files in the Boot ROM menu or using commands after the application image boots. Secure boot file is the last system boot resort. You can download it in the Boot ROM menu and must name it secure.bin. However, you cannot modify this file or change the type of another file to S. If you change the name of the secure boot file with the rename command after the system boots, the file is removed from Flash memory. To use the secure boot file after that, you need to download it again.
39
Enter <2> in the boot file control sub-menu to set the main boot file. The console screen displays:
Input main boot file name -> router.bin Set main boot file successfully!
Enter <3> in the boot file control sub-menu to set the backup boot file. The console screen displays:
Input backup boot file name -> router.bin Set backup boot file successfully!
VI.
Enter <4> in the boot file control sub-menu to return to the main Boot ROM menu.
Option 6: Modify Bootrom Password
To modify the Boot ROM password enter <6> in the main Boot ROM menu. The console screen displays:
Change password. Old password: New password: Verify: Password set successfully.
Note: Either failure to provide the correct old password or new password inconsistency can fail a password modification attempt. The system then exits from this operation.
VII.
Option 7: Reset Console Authentication
To reset console authentication enter <7> in the main Boot ROM menu. The console displays:
Exit and then restart the router. The screen displays Login authentication ignored, allowing you to log in from the console port without authentication. Note: This is a one-time operation. It takes effect only at the first reboot after resetting console authentication is selected. At subsequent reboots, console authentication is required.
VIII.
Option 8: Ignore System Configuration
To ignore the system configuration enter <8> in the main Boot ROM menu. The system sets an Ignore flag to Flash memory and displays:
Thus, an empty configuration applies at reboot. The system removes the Ignore flag after its boot is completed. If you forget the password, you may select this option to have the system boot with the configuration file ignored. After the system boots up, you may change or delete the password. Note that if not saved, the modified configuration cannot survive a reboot. To have the router reboot with the new configuration, you must perform the save operation after completing configuration.
IX.
40
Option 9: Enter Debugging Environment
To enter the Debugging Environment enter <9> in the main Boot ROM menu. The console screen displays:
Enter debugging environment: Press any key to stop auto-boot... 0 auto-booting...
boot device unit number processor number file name inet on ethernet (e) host inet (h) user (u) ftp password (pw) flags (f)
: : : : : : : : :
wancom 0 0 R46XX-V3.30-0002.BIN 169.254.75.1 169.254.75.166 1 1 0x0
Attached TCP/IP interface to wancom0. Attaching network interface lo0... done. Loading... Error loading file: errno = 0xd0003. Can't load boot file!!
X.
Option a: Reboot
To reboot the system enter <a> in the main Boot ROM menu. The console screen displays:
Rebooting...
5.2.4 Upgrading Image Files Using Xmodem

I.
Upgrading the main Boot ROM system
To upgrade the main Boot ROM system, perform the following steps: 1 2 3 Connect the console terminal as shown in Figure 4-1. Start the router and press <Ctrl+A> within five seconds after the message "Starting" appears to enter the small Boot ROM menu. Change the baud rate of the serial port on the RPU to a higher value. Refer back to Modify Serial Interface Parameters in the subsection Small Boot ROM menu in the section Boot Menu.
Note: The default baud rate of the serial port on the RPU is 9600 bps. Skip this step if you do not want to modify it; but if you change it, note to reset it to 9600 bps after file transfer is completed. 4 Enter <2> in the small Boot ROM menu to have the system download the image file from the console terminal to the SDRAM using Xmodem. If system check is passed, the system begins to upgrade the Boot Rom image. The console screen displays:
Select Program File Please. Waiting...CC
41
Select Transfer > Send file in the HyperTerminal window.
The Send File dialog box is displayed:
6 7
Select Xmodem for the Protocol field and type the path and name of the image file in the Filename field Click <Send> (If the terminal is not ready yet, press <Ctrl+X> to quit downloading). The HyperTerminal window displays the following information:
When the load is completed, the system displays:

Waiting ...CC download successfully! Update Bootrom...done!
Note: Upgrading may fail if an erroneous file is downloaded. Excluding the time to download the file, it takes about 10 seconds upgrading the main Boot ROM system.
II.
Downloading application image through a serial port is easy, but at low speed. To upgrade the application image, perform the following steps: 1 Connect the console terminal:
42
Start the router and enter the main system. Press <Ctrl+B> when the system prompts Press Ctrl+B to enter Boot Menu... 3. Input the correct password to enter the main Boot ROM menu. Select <3> in the main Boot ROM menu to enter the serial sub-menu. Change the baud rate of the serial port on the RPU to a higher value using option 3 (Change Boot Parameter) in the serial sub-menu.
3 4
Note: The default baud rate of the serial port on the RPU is 9600 bps. Skip this step if you do not want to modify it; but if you change it, note to reset it to 9600 bps after file transfer is completed. 5 In the serial sub-menu, select <1> to download and run the application image (note that this does not save the application image to Flash memory), or select <2> to download it to Flash memory. Select the application image file and the Xmodem protocol in the Send File window in the HyperTerminal. See Step 5 in the previous subsection. Send the file. See Step 6 in the previous subsection. If you select <1> in the serial port sub-menu, the application image runs immediately after it is loaded; if you select <2>, the system returns to Main Menu and boots from Flash memory after the write to Flash operation is done.
6 7 8
Note: Upon completion of application image upgrade, the router reboots and checks Boot ROM version for consistency before starting the Comware software. If the version of the current extended Boot ROM image segment is not the same as that of the extended segment to be started, the system automatically updates the Boot ROM image, and displays Update main bootrom. Updating...done. System will reboot Then, it reboots again.
5.2.5 Upgrading the Application Image through an Ethernet Port

Through an Ethernet port, you can upgrade the application image at high speed using FTP or TFTP, but you need to prepare an FTP Server or TFTP Server. The following subsections describe the upgrading procedures:
I.
Setting up an upgrade environment
Set up an FTP/TFTP upgrade environment as shown in the diagram below.
LAN/WAN
3Com 6040
(FTP/TFTP Client)
PC(FTP/TFTP Server )
Follow these steps to set up an application image upgrading environment: 1 2 Connect Ethernet port 0/0/0 on the RPU to a PC by using a crossover cable. Connect the console port on the router to an external console terminal (it can be the PC connected to the Ethernet port), and configure the HyperTerminal with Caution: Only Ethernet port 0/0/0 is available for upgrading.
43
reference to the subsection Connecting the router to a console terminal in the section Setting up a Configuration Environment. 3
II.
Copy the new application image file to the designated directory and configure the IP address of the Ethernet port on the PC.
Runing TFTP Server or FTP Server
Start the TFTP or FTP Server and set a path for the target file. For FTP, you should also set up a user name and password for use.
III.
Configuring the router
Follow these steps to configure your router: 1 2 3 Start the router and press <Ctrl+B> to enter the main Boot ROM menu. Refer to the subsection Main Boot ROM menu in the section Boot Menu. Select <4> in the main Boot ROM menu to enter the Ethernet sub-menu. Select <5> in the Ethernet sub-menu to set parameters of the Ethernet port. For upgrading using TFTP , set the following parameters:
file name: Name of the file to be downloaded inet on ethernet (e): IP address of the downloading port on the router, which is userdefined and cannot conflict with the addresses of the connected network devices. host inet (h): IP address of TFTP Server flags (f): 0x80.
For FTP upgrading, set the following parameters:

file name: Name of the file to be downloaded inet on ethernet (e): IP address of the downloading port on the router, which is userdefined and cannot conflict with addresses of the connected network devices. host inet (h): IP address of FTP Server user (u): username, same as the one configured at FTP Server. ftp password (pw) (blank = use rsh); password, which should be consistent with that at FTP Server. flags (f): 0x0.
Note: FTP user name and password in the main Boot ROM menu must be the same as those configured on the FTP Server. 4 Select <1> in the Ethernet sub-menu to download and run the application image (note that this does not save the application image to Flash memory). The console screen displays:
Attached TCP/IP interface to wancom0. Subnet Mask: 0xfffffc00 Attaching network interface lo0... done. Loading...done 8619044 bytes downloaded. Decompressing.....................................
44
After the decompression operation completes, the system starts to boot. Since the downloaded application image is not saved to Flash memory, it cannot survive a reboot. Alternatively, you can: Select <2>, <3>, or <4> in the Ethernet sub-menu at this step to download the application image as the boot file, main, backup, or secure, to Flash memory; select <6> in the Ethernet sub-menu to return to the main Boot ROM menu; and select <2> in the menu to run the new application image. The software upgrade is now complete. Note: Upon completion of application image upgrade, the router reboots and checks Boot ROM version for consistency before starting the Comware software. If the version of the current extended Boot ROM image segment is not the same as that of the extended segment to be started, the system automatically updates the Boot ROM image, and displays Update main bootrom. Updating...done. System will reboot Then, it reboots again.
5.3 Software Upgrade for the Router 6000/RPU2

5.3.1 Boot Menu
Start the router; when the message Press Ctrl-B to enter Boot Menu .......... appears, press <Ctrl+B>. The console screen displays:
Please input bootrom password:
Once the correct password is entered (there is no password by default), the Boot menu is displayed, as shown below: (Note that the menu may be slightly different depending on the version of software loaded).
Boot Menu: 1: Download application program with XMODEM 2: Download application program with NET 3: Download application program with NET to CF card 4: Set application file type 5: Display applications in Flash 6: Clear application configuration 7: Reset console authentication 8: Start up and ignore configuration 9: Boot Rom Operation Menu a: Do not check the version of the software b: Start application program c: Format CF card d: Exit and reboot Enter your choice(1-d):
Note: "The entire Boot ROM image file in the manual includes two segments: extended and basic. You can separately upgrade and back up the extended segment only. These options are described in the following sections.
I.
Option 1: Download application program with XMODEM
Refer to the section Upgrading Software Using Xmodem.
II.
45
Option 2: Download application program with NET
Refer to the section Upgrading the Application Image Using TFTP for the procedures. If you select this option, the following Net Port Download Menu appears:
Net 1: 2: 3: 4: 5: Port Download Menu: Change Net Parameter Download From Net to Flash Download From Net to Ram Upload the config file to host Exit to Main Menu Enter your choice(1-5): 1
III.
Option 3: Download application program with NET to CF card
For the procedures, refer to the section Upgrading the Application Image Using TFTP. If you select this option, the following Net Port Download Menu appears:
Net Port Download Menu: 1: Change Net Parameter 2: Download From Net to CF 3: Download From Net to Ram 4: Upload the config file to host 5: Exit to Main Menu Enter your choice(1-5):
IV.
Option 4: Set application file type
The dual image function is available with the router. By default, the system defines and attempts to boot in order with three boot files: main, backup, and secure. If it fails to boot with the secure boot file, the system will display a booting failure message. For more information on the boot files, refer back to the subsection Main Boot ROM menu in the section Software Upgrade for the Router 6000/RPU. Assume that you have saved three application image files to Flash memory and the CF card. After you select an option, option 4, for example, from Boot Menu, the console screen displays a menu similar to the following:
Please set file type: M=MAIN B=BACKUP S=SECURE ************************************************************************* NO. Name Size Type Time 1 flash:/8061.bin 10093604 N/A Oct/18/2005 13:35:39 2 flash:/ main.bin 12252636 M Oct/20/2005 10:35:13 3 cflash:/d020 11987956 B Oct/18/2005 16:59:28 ************************************************************************* 4 Exit to main menu Enter your choice(1-4):
Select option 1 to define the file whose type is N/A. The system enters the following menu, where you can change the file type of 8061.bin.
Set this file as: 1. Main 2. Backup 3. Exit Enter your choice(1-3):
46
Select option 1 for example to specify the 8061.bin file as the main boot file. After the modification takes effect, the file type of the original main file named mian.bin changes to N/A. Now, the 8061.bin file is the first boot file.
V.
Option 5: Display applications in Flash
If you select option 5, the console screen displays:

M=MAIN B=BACKUP S=SECURE ************************************************************************* NO. Name Size Type Time 1 flash:/8061.bin 10093604 N/A Oct/18/2005 13:35:39 2 flash:/tt 12252636 M Oct/20/2005 10:35:13 3 cflash:/d020 11987956 B Oct/18/2005 16:59:28 ************************************************************************* There are 3 application files totally! Press <Enter> key to continue
Press <Enter> to return to Boot Menu.

VI.
Option 6: Clear application configuration
If you select this option, the screen displays:

Clear configuration, are you sure?[Y/N] Press <Y> to clear the configuration filenamed config.cfg. Press <N> to reject the clear operation.
VII.
Option 7: Reset console authentication
This option allows you to log in from the console port without authentication and reset a password if needed Note that if not saved, the modified configuration will not survive a reboot, Select the option; exit and then restart the router. The screen displays Login authentication ignored, allowing you to log in from the console port without authentication. Note: T his is a one-time operation. It takes effect at the first reboot. Console authentication is required however at subsequent reboots. Boot Menu 8: Start up and ignore configuration.
VIII.
Option 8: Start up and ignore configuration
The system sets an Ignore flag to Flash memory and displays:

Thus, a default factory configuration is used for booting. The system removes the Ignore flag after the reboot completes.
IX.
Option 9: Boot Rom Operation Menu
Enter <9> in the main Boot ROM menu to enter Boot ROM Download Menu as follows for upgrade, backup, or recovery of the Boot ROM program. The following menu displays:
X.
47
Option a: Do not check the version of the software
When upgrading software, make sure that you are using the correct software version. If the upgrade still fails and the system displays invalid version in this case, you can use this option. It allows the system to upgrade software without checking the version of extended Boot ROM image segment, Boot ROM image, and application image for backward compatibility. This option applies only once when selected. When the router is rebooted, version checking is restored.
XI.
Option b: Start application program (from Flash memory)
Select option b to continue booting up with the selected Main/Backup/Secure boot files.
XII.
Option c: Format CF card
This option formats the Compact Flash Card.

XIII.
Option d: Exit and reboot
Exits the Boot Menu and starts the booting process from the very beginning. Just like issuing the reboot command in the CLI.
5.3.2 Upgrading Software Using Xmodem

You can use the console port to upgrade software using Xmodem without the need of setting up a network environment.
I.
Enter Boot Menu (refer to the section Boot Menu) and enter <1> to download an application image using Xmodem. The router supports the following downloading speeds:
Please choose your download speed: 1: 9600 bps 2: 19200 bps 3: 38400 bps 4: 57600 bps 5: 115200 bps 6: Exit to Main Menu Enter your choice(1-6):
Select an option, 5 for 115200 bps for example. The following message appears:
Download speed is 115200 bps. Change the terminal's speed to 115200 bps, and select XModem protocol. Press ENTER key when ready.
Change your terminals baud rate (see Figure 4-4) to the same baud rate for software download (115200 bps in this example). After that, select [Dialin/Disconnect] to disconnect the terminal, and [Dial-in/Dialing] to reconnect it. Then, press <Enter> to start downloading. The system displays:
Please Select Program File Downloading ... CCCCC
Note: The new baud rate takes effect only after you reconnect the terminal emulation program.
48
Select Transfer > Send File in the terminal window. The following dialog box is displayed:
Click <Browse>. Select the file to be downloaded and set protocol to Xmodem. Click <Send>. The following dialog box appears:
After completing download, the system begins writing data to Flash memory, and then displays the following information on the screen:
Download completed. Then, the system asks you to select a file type: please select file to be saved as 1. main application file 2. backup application file 3. secure application file 4. cancel downloading Enter your choice(1-4):
After you select an option, the system begins writing the file to Flash memory.
Writing to flash memory... Please waiting,it need a long time (about 5 min). ############################# Write Flash Success. Please return to 9600 bps. Press ENTER key to reboot the system.
Change the baud rate of the console terminal to 9600 bps, disconnect and re-dial. Then you can see the system boot banner.
II.
49
Upgrading the Entire Boot ROM Program
Enter Boot Menu (see the section Boot Menu) and select option 9 to enter Boot ROM Download Menu as follows:
Select option 1 in the menu to download the entire Boot ROM image using Xmodem. multiple speed options are available. The subsequent steps are the same as those described in the section for upgrading the application image.
Caution: You are recommended to upgrade the entire Boot ROM program unless necessary and with the guide of technical staff, because no means is available for onfield restore in case of an update failure.
III.
Upgrading the extended segment of the Boot ROM image
1 2
Enter Boot Menu (refer to the section Boot Menu) and select option 9 to enter Boot ROM Download Menu. Step 2: Select option 2 in the menu to upgrade the extended segment of the Boot ROM image using Xmodem. Multiple speed options are available. The subsequent steps are the same as those described in the section for upgrading the application image.
Caution: This upgrade approach upgrades only a portion of the Boot ROM image, so you can make a second attempt if errors occur. Note: Upon completion of application image upgrade, the router reboots and checks Boot ROM version for consistency before starting the Comware software. If the version of the current extended Boot ROM image segment is not the same as that of the extended segment to be started, the system automatically updates the Boot ROM image, and displays Upgrade Bootrom............! Download completed.
Please wait, it needs a long time###### Writing into Boot ROM Succeeds. Then, the system continues its boot process.
5.3.3 Backing Up and Restoring the Boot ROM Images Extended Segment
You can back up and restore the BootROM images extended segment to and from the Flash memory. Each is described below.
I.
Backing up to the Flash
Follow these steps to back up the extended segment of the Boot ROM image: 1 2 Enter Boot Menu (refer to the section Boot Menu) and select option 9 to enter Boot ROM Download Menu. Select option 4 in the menu to copy the current extended segment to Flash memory.
Backup Extended Segment, are you sure?[Y/N] Enter <Y>. The system displays: Writing to FLASH.Please wait...#### Backuping Boot ROM program to FLASH successed!
50
3
II.
When Boot ROM Download Menu appears again, select option 5 to exit and reboot the router.
Restoring the extended segment of the Boot ROM image from Flash
If extended Boot ROM segment errors occur or an upgrade attempt is unsuccessful, perform the following steps to restore the extended segment of the Boot ROM image from Flash memory to the Boot ROM: 1 2 Enter Boot Menu (refer to the section Boot Menu), and select option 9 to enter Boot ROM Download Menu. Select option 3 in Boot ROM Download Menu to restore the extended segment from Flash memory.
Restore Extended Segment, are you sure?[Y/N] Enter <Y>. The system displays: Writing to Boot ROM. Please wait...###### Restoring Boot ROM program successed!
When Boot ROM Download Menu appears again, select option 5 to exit and reboot the router.
5.3.4 Upgrading the Application Image Using TFTP

To upgrading the application image with NET, you download the software using an Ethernet interface. In this approach, the router is a TFTP client and connected to a TFTP Server using a fixed Ethernet interface. The following procedure describes how to upgrade the application image using this approach: 1 2 Start the TFTP Server on the PC connected to the Ethernet interface on the router and set the path for getting the source file. In the Boot Menu, select option 2 to enter Net Port Download Menu as follows:
Net 1: 2: 3: Port Download Menu: Change Net Parameter Download From Net to Flash Download From Net to Ram 4: Upload the config file to host 5: Exit to Main Menu Enter your choice(1-5):1
Select option 1 in Net Port Download Menu to change the download parameters as follows:
Change Download parameter Download device Download file name Target file name IP address of eth0 Subnet mask for eth0 IP address of the server IP address of the gateway : eth0 :8061.bin :tt :1.1.1.2 :255.255.0.0 :1.1.1.1 :1.1.1.0
Saving the net configuration, are you sure?[Y/N]
Table 1 Download parameters Parameter Download device Description The Ethernet port for downloading,
51
Parameter Download file name Target file name IP address of eth0 Subnet mask for eth0 IP address of the server IP address of the gateway
Description which must be eth0. Name of the Comware file to be downloaded. Name for saving the downloaded file. IP address of interface eth0. Subnet mask of interface eth0. IP address of the server where Comware is retained You must configure it if the server and the router are not located on the same segment.
4 5
Press <Y> to save the configuration. When Net Port Download Menu appears, select option 2 to download and write the application image to Flash memory. The system displays the following messages:
Starting the TFTP download.................................................. ................................................................. ............ ............................................................. TFTP download completed. File length = [07600856] Writing program code to FLASH... Please wait, it may take a long time.. Writing into Flash Successfully!
The system returns to Net Port Download Menu. If you select option 3 in the menu to directly download the program to the SDRAM and run it there, the downloaded application image cannot survive a reboot because the file is not written to Flash memory. Note: Upon completing the application image upgrade, the router reboots and checks the Boot ROM version for consistency before starting the Comware software. If the version of the current extended Boot ROM image segment is not the same as that of the extended segment to be started, the system automatically updates the Boot ROM image, and displays Upgrade Bootrom............! Download
completed.Please wait, it needs a long time###### Writing into Boot ROM Succeeds. Then, the system continues its boot process.
52
5.4 Maintaining Application Program and Configurations Using the Command Line
After booting the router normally, you can upgrade and backup application program and backup and recover configurations in command line mode.
5.4.1 Maintaining the Router with TFTP Server

The TFTP service provided by the router is the TFTP client. The router serves as the TFTP client, and the file server serves as TFTP server. You can input commands to upload the configuration file and routers application program to the file server, or download the configuration file or application program to the router from the file server.
I.
Network Setup
Set up the hardware, and point the server path to the folder where the file is located. The diagram below shows the networking configuration for maintaining the software using command line mode.
Console
Ethernet ROUTER (TFTP/FTP Client) PC (TFTP/FTP Server)
Configure the IP addresses of the two sides to be on the same network. In this section, the TFTP server is set to 192.168.0.1, and the Ethernet interface connected to it (Ethernet interface 0/0 in this example) is set to 192.168.0.2. Both can use the ping command to check the connection.
II.
Backing up and recovering application program and configure file
After finishing the setup, perform the following steps: 1 View the files included in current file system with the dir command:
<3Com>dir Directory of cf:/ 0 1 2 3 4 -rwdrw-rw-rw-rw14323376 909 1045 14323376 Apr Mar Apr Apr Mar 03 20 04 04 31 2006 2006 2006 2006 2006 15:36:48 09:55:28 10:54:38 11:31:36 17:50:22 main.bin logfile ar-router.cfg configbak.cfg backup.bin
63340 KB total (20928 KB free) File system type of cf: FAT32 <3Com>
53
Use the following commands to back up the config.cfg file on the router to TFTP server and save it as config.bak:
<3Com>tftp 192.168.0.1 put config.cfg config.bak File will be transferred in binary mode Sending file to remote tftp server. Please wait... \ TFTP: 1045 bytes sent in 0 second(s). File uploaded successfully.
Use the following command to download the config.cfg file on the server to the router:
<3Com>tftp 192.168.0.1 get config.cfg config.cfg The file config.cfg exists. Overwrite it?[Y/N]:y Verifying server file... Deleting the old file, please wait... File will be transferred in binary mode Downloading file from remote tftp server, please wait...\ TFTP: 1045 bytes received in 0 second(s) File downloaded successfully.
If a config.cfg file already exists in the router, select <Y/y> to overwrite it.
Caution: If a config.cfg file already exists on the server, it will be overwritten. The above operations are performed under user view. The backup configuration file can be modified with a text editor. The modified configuration file can be downloaded onto the router replacing the current saved configuration, and the modifications will take effect after rebooting. Similarly, you can also download an application program to the router to overwrite the old main program for upgrade at the next reboot.
5.4.2 Maintaining the Router with FTP Server

I.
Maintaining the router when it serves as the server
FTP (File Transfer Protocol) is an application layer protocol in the TCP/IP suite. It mainly transfers files among remote hosts. Transferring data over TCP provides reliable and connection-oriented data transfer service. The FTP service provided by the router is the FTP server. The router serves as the FTP server. You can run the FTP client software to log onto the router and access files on the router. You must install the FTP client software before using FTP. Use the FTP Client with Windows XP for example. 1 Setup hardware maintenance environment as follows:
54
Console
Configure the IP addresses of the two devices to be in the same network. In this section, the PC client is set to 192.168.0.1, and the router Ethernet interface connected to it (Ethernet interface 0/0 in this example) is set to 192.168.0.2. Both can use the ping command to check the connection. Set up the FTP service by enabling the ftp server service and creating a user with service-type ftp. The FTP server supports single-user access only. The remote FTP user sends request to the FTP server, which then executes accordingly and returns the result of the execution to the user. Use the following command to set up the FTP service:
[3Com]ftp server enable % Start FTP server Add FTP authorized user name and password: [3Com]local-user guest user guest [3Com-luser- guest]service-type ftp user [3Com-luser- guest]password simple 123456 123456 for the
Set up the The user type is FTP Add the password user guest
Maintain the router. After setting up the routers FTP service and configuring the user name and password, you can set up the FTP client on your PC (the FTP client with Windows XP for example). Enter ftp at the DOS command prompt:
C:\Documents and Settings\Administrator>ftp ftp> The system prompts ftp> ftp> open 192.168.0.2 Connected to the router IP Connected to 192.168.0.2. 220 FTP service ready. User (192.168.0.2:(none)): guest Enter the user name configured on the router 331 Password required for guest Password: Enter the password 123456 230 User logged in. Successfully connected to the server
You can now use the following command to perform maintenance on the router. In the following example, the main.bin file on the router is backed up to the PC.
ftp> binary mode to binary 200 Type set to I. ftp> lcd c:\temp Local directory now C:\temp. Change the transfer
Change local path
55
ftp> get main.bin main.bin Backup files to PC from the router 200 Port command okay. 150 Opening BINARY mode data connection for main.bin. 226 Transfer complete. ftp: 14323376 bytes received in 16.81Seconds 851.87Kbytes/sec.
Recover the backup file to the router command:

ftp> put main.bin main.bin Recover the local file to the router 200 Port command okay. 150 Opening BINARY mode data connection for main.bin. 226 Transfer complete. ftp: 14323376 bytes sent in 8.29Seconds 1727.37Kbytes/sec. ftp> quit Quit the FTP 221 Server closing.
II.
Maintaining the router when it serves as the client
You can also maintain the router file system using an external FTP server and making the router serve as the client. Perform the following steps: 1 Set up the maintenance environment so that the router serves as the client:
Console
When the router serves as the client, you can run an FTP server program on your PC, and set the server path to the desired file location. Then, add a user name and password for the router to use. 2 Configure the IP addresses of the two devices to be in the same network. In this section, the FTP server is set to 192.168.0.1, and the Ethernet interface connected to it (Ethernet interface 0/0 in this example) is set to 192.168.0.2. Both can use the ping command to check the connection. Maintain the router through the terminal connected to the console port as follows:
<3Com>ftp 192.168.0.1 Trying 192.168.0.1 ... Press CTRL+K to abort Connected to 192.168.0.1. 220 3Com 3CDaemon FTP Server Version 2.0 User(192.168.0.1:(none)): guest configured on 331 User name ok, need password Password: corresponding password 230 User logged in successfully [ftp]
Enter the user name the router Enter the Connect
56
Use the following commands to maintain the router. Use the put and get commands to back up and recover files.
[ftp]get main.bin main.bin the router from Download files to
the server cf:/main.bin has been existing. Overwrite it?[Y/N]:y Overwrite it or not? 200 PORT command successful. 150 File status OK ; about to open data connection 226 Closing data connection; File transfer successful. FTP: 14323376 byte(s) received in 69.256 second(s) 206.00K byte(s)/sec. [ftp]put main.bin main.bin Backup the router files to the server 200 PORT command successful. 150 File status OK ; about to open data connection 226 Closing data connection; File transfer successful. FTP: 14323376 byte(s) sent in 15.974 second(s) 896.00Kbyte(s)/sec. [ftp]quit Quit the FTP 221 Service closing control connection

3com Router 5000 and Router 6000 Release Notes: Part Number: 10016400 Rev AA Published October 2007

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

3com Router 5000 and Router 6000 Release Notes: Part Number: 10016400 Rev AA Published October 2007

Hochgeladen von

Copyright:

Verfügbare Formate

3Com Router 5000 and Router 6000 Release Notes

1.2 Supported Routers

1.3 Online Resources

1.4 New Software Features for V3.11

1.4.1 SIP Server Registration using a DNS Name

1.4.2 SIP Early-Media Parameter

1.4.3 Management Protocol IP Address Parameter

1.4.4 Enhanced 'show ppp mp' Command

1.4.5 Source Specific Multicast (SSM) Mapping

1.4.6 SNMP v3 USM-User Passwords

1.4.7 OSM | CA MIB

1.4.9 PIM SSM (RFC 4607 Source-Specific Multicast for IP)

1.4.10 Kentrox T3/E3 subrate support

1.4.11 CLI command to specify the source address of PKI communication

1.4.12 Fast forwarding with Policy Routing Support

1.4.13 QoS in GRE Tunnel Fast Forwarding

1.4.14 OSPF Fast-Hello Function

1.4.15 SIP supports all standard 18x Temporary Response

1.4.16 HWPing Enhancement

Enhanced HWPing Functions

HWPing Threshold Statistics Requirement

Jitter Test through ICMP

HWPing Supports Unidirectional Performance Test

1.4.17 Filtering of command logs to be sent to TACACS Server

1.4.18 Switchover between HWTACACS Server

1.4.20 RADIUS and TACACS supports VRF Applications

1.4.21 SIP responses to options requests of Softswitch

1.4.24 Global Configuration of the QoS Module Supports Hot Swapping

1.4.28 QoS extension

1.4.29 X2T Supports Carrying the Called Number

1.4.30 XOT Supports DNSBased X.121 Address Resolution

1.4.31 X25 CLI commands enhancement

Adding the Command for Deleting X.25 Facility

X25 Switching Supports Packet Fragmentation and Reassembly

X.25 Many-to-Many Address Translation Is Implemented

1.4.32 HoPE Supports the Sending of Detailed Routes

1.4.33 Policy-Based Routing Supports Auto-Detect

1.4.34 RIP Supports Modifying the COST Value of Particular Routes

1.4.35 Displaying the Device Manufacturing Information

DEVICE_SERIAL_NUMBER MAC_ADDRESS MANUFACTURING_DATE VENDOR_NAME

1.4.36 Supporting Levellized Logging of Commands

1.4.38 Supporting SNMP Query of ADSL/G.SHDSL Uplink/Downlink Rate

1.4.40 IP Host Command Supports Telnet Port Configuration

1.4.42 PBR Supports Modifying the DF Value of IP Headers

1.5 New Bug Fixes for V3.11

1.5.1 Backup IPSec on Loopback Interface

1.5.2 Outputing debugging messages to logbuffer

1.5.4 Frame Relay statistics are not computed correctly

1.5.5 5012/FT1 module: No message indicating FT1 is in BERT test mode

1.6 New Software Support for FIC Modules in V3.11

ROUTER 1-Port CE3 FIC ROUTER 1-Port FT3/CT3 FIC

2. Software Issues Resolved in Previous Releases

2.2 Software Issues Resolved in v3.00

2.3 Documentation Issues Resolved in v3.00

2.4 Software Issues Resolved in v2.41

2.5 Software Issues Resolved in v2.21

2.6 Software Issues Resolved in v2.20

2.7 User Documentation Issues resolved in v2.20

2.8 Software Issues Resolved in v2.30/31

2.9 Documentation Issues Resolved in v2.30/31

3. Known Issues in Release v3.01

3.3 System Management

3.4 Interface Management