4.3 Upgrading Software Using Xmodem ...................................................................................... 20
4.4 Upgrading Software Using TFTP (option 1) ............................................................................. 21
4.5 Upgrading Software Using TFTP (option 2) ............................................................................. 22
3Com Router 5000 and Router 6000 Family Release Notes v2.41 • Page 2
1. Introduction
1.1 Scope
These release notes summarize the operational requirements and known issues for the 3Com®
Router 5000 and Router 6000 software releases listed Table 1. This release notes supersede the
v2.20, v2.21, v2.30/2.31, and v2.40 Release Notes for the Router 5000 and Router 6000.
This release provides an update to the Router 5000 and Router 6000. The software for the
Router 6000 RPU2 will not load on the Router 6000 RPU.
Table 1: Software Release v2.41
Software Release Filenames Description
R6y02_41e.bin The encrypted software agent which runs on the Router 6040
and 6080 RPU2 (including bootrom)
R6y02_41v.bin The basic software agent which runs on the Router 6040 and
6080 RPU2 (including bootrom)
R6x02_41e.bin The encrypted software agent which runs on the Router 6040
and 6080 RPU (including bootrom)
R6x02_41v.bin The basic software agent which runs on the Router 6040 and
6080 RPU (including bootrom)
R5y02_41v.bin The basic software agent which runs on the 5012, 5232, 5642,
5842 Routers
R5y02_41e.bin The encrypted software agent which runs on the 5012, 5232,
5642, 5842 Routers
bootromfull9-17.bin Router 5000 Boot ROM file for 5012, 5232, 5642, 5842
This section describes issues that have been resolved since previous releases of the software.
3Com Router 5000 and Router 6000 Family Release Notes v2.41 • Page 6
2.1 Software Issues Resolved Since v2.30/2.31
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.
• 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.
2.2 Software Issues Resolved from v2.11
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 of Promiscuous mode, 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>.”
3Com Router 5000 and Router 6000 Family Release Notes v2.41 • Page 7
• 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.
• 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.
3Com Router 5000 and Router 6000 Family Release Notes v2.41 • Page 8
2.3 Software Issues Resolved from v2.20
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
• 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.4 User Documentation Issues resolved From 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
Loading...
+ 16 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.