Readme Release Notes

3Com Switch 8800
Release Notes
Software version 5.01.21
Part Number: 10016494 Rev. AA
Published December 2007
Contents
Chapter 1 Introduction ........................................................................................................................................................ 3
1.1. Scope .......................................................................................................................................................................... 3
1.2. Online Resources........................................................................................................................................................ 3
1.3. System Requirements ................................................................................................................................................. 3
1.4. Support for New Modules............................................................................................................................................ 4
1.4.1. Release V5.01.21 ...................................................................................................................................................4
1.4.2. Release V5.01.20 ...................................................................................................................................................4

1.5. Enhancements to Software ......................................................................................................................................... 5
1.5.1. V5.01.21 Enhancements/ CLI Changes..................................................................................................................5
1.5.2. V5.01.20 Enhancements ........................................................................................................................................5

1.6. Changes in Behavior ................................................................................................................................................... 6
Chapter 2 Known issues for Switch 8800 V5.01.21 .......................................................................................................... 6
2.1. Configuration File Issues after Software Upgrade ...................................................................................................... 7
2.2. Note regarding features in both Release v3.01.xx and Release v5.01.20/v5.01.21 ................................................... 7
2.3. Unsupported Modules ................................................................................................................................................. 7
2.4. Unsupported Features................................................................................................................................................. 7
2.5. Multicast Protocol ........................................................................................................................................................ 8
2.6. System Management .................................................................................................................................................. 9
2.7. High Availability ........................................................................................................................................................... 9
2.8. Broadcast Storm Control ............................................................................................................................................. 9
2.9. STP ............................................................................................................................................................................. 9
2.10. TFTP ......................................................................................................................................................................... 9
2.11. Boot Code ................................................................................................................................................................. 9
2.12. CoS ........................................................................................................................................................................... 9
2.13. Link Aggregation ....................................................................................................................................................... 9
2.14. QoS ......................................................................................................................................................................... 10
2.15. Super VLAN ............................................................................................................................................................ 10
2.16. Protocol VLAN......................................................................................................................................................... 10
2.17. DHCP Relay ............................................................................................................................................................ 11
2.18. RADIUS................................................................................................................................................................... 11
2.19. ARP ......................................................................................................................................................................... 11
2.20. LACP ....................................................................................................................................................................... 12
2.21. Boot Loader............................................................................................................................................................. 12
2.22. ACL ......................................................................................................................................................................... 12
2.23. Jumbo Frames ........................................................................................................................................................ 12
2.24. SFTP ....................................................................................................................................................................... 12
2.25. Super User Password ............................................................................................................................................. 13
2.26. 802.1x...................................................................................................................................................................... 13
2.27. Hardware................................................................................................................................................................. 13
2.28. ECMP ...................................................................................................................................................................... 14
2.29. SSH ......................................................................................................................................................................... 14
2.30. Web Authentication / Portal..................................................................................................................................... 14
2.31. RIPng ...................................................................................................................................................................... 14
2.32. SFTP Configuration Backup & Restore................................................................................................................... 14
2.33. MAC Authentication................................................................................................................................................. 15
2.34. Gratuitous ARP – Change in default operation ....................................................................................................... 15
2.35. Tunnels.................................................................................................................................................................... 15
2.36. Selective QinQ ........................................................................................................................................................ 16
Copyright © 2007 3Com Corporation. All rights reserved.

2.37. Host Name Length .................................................................................................................................................. 16
2.38. 3C17532 and 3C17532A Limitations ...................................................................................................................... 16
2.39. IGMP ....................................................................................................................................................................... 16
2.40. UDP Helper ............................................................................................................................................................. 16
2.41. Documentation Addendum...................................................................................................................................... 17
Chapter 3 Upgrading Software ......................................................................................................................................... 17
3.1.1. IMPORTANT NOTES: ..........................................................................................................................................17

3.2. General Upgrade Procedure ..................................................................................................................................... 20
3.3. Upgrading Application Software using FTP .............................................................................................................. 25
3.4. Upgrading Application Software Using the BOOT Menu.......................................................................................... 31
3.5. Upgrading Application Software Using Xmodem ...................................................................................................... 36
3.6. Upgrading Application Software Using TFTP............................................................................................................ 42
3.7. Upgrading BootROM Code Using the Command Line Interface............................................................................... 46
3.7.1. Example of Updating the bootROM code on the fabric(s) and I/O modules. ........................................................47
3.8. Upgrading the BootROM Code On the Fabric Using the Boot Menu....................................................................... 52
3.9. Software Update Example......................................................................................................................................... 58
3.9.1. Identify the configuration file and the currently running operational OS agent file. ...............................................58
3.9.2. Identify the bootROM versions and which modules will need the bootROM code to be updated. ........................58
3.9.3. Ensure sufficient space on the master and slave fabric flash(es) and/or compact flash (cf:/) to hold the new
application code (.app files). ...........................................................................................................................................60
3.9.4. Configure an IP address on Ethernet port on the fabric........................................................................................61
3.9.5. Backing up the configuration file and the operational OS agent. Transferring the new .app files to the Switch
8800 using FTP. .............................................................................................................................................................62
3.9.6. How to copy a file from one fabric to another fabric..............................................................................................64
3.9.7. Backing up the current configuration file to the Switch 8800 file system...............................................................66
3.9.8. Updating the bootROM code on the Fabrics and I/O modules. ............................................................................66
3.9.9. Configuring the boot loader to boot from the new software OS agent code..........................................................67
3.9.10. Rebooting the Switch 8800 with the new code ...................................................................................................68
3.9.11. Verify that the software OS is 5.01.21 and the bootROM version is up to date on all the modules. ...................70
3.9.12. Reconfiguring the Configuration file....................................................................................................................72

3Com Switch 8800 Family Page 3
Release Notes v5.01.21
Chapter 1 Introduction
1.1. Scope
These release notes summarize operational requirements and issues for the following Switch 8800
software releases:
Table 1 Software Release Numbers Addressed in These Release Notes

Software Description
Advanced Code V5.01.21 A new version of the Switch 8800 software,
supporting IPv6. Only advanced software is
available for this release.
Boot Code V5.02.06 The latest boot code running on the Switch Fabric.
Boot Code V1.08 The latest main board boot code running on the
I/O Modules.
The software images are as follows:

88h05_01_21s168rec01.app – Switch 8800 Advanced Software (IPv6)
fab05_02_06d.app – Switch Fabric boot code (both 360 Gbps and 720 Gbps)
iom05_01_08.app – Switch 8800 I/O module boot code
8800boot-module1107.app - INTERMEDIATE boot code for I/O modules
ONLY use the 8800boot-module1107.app file if upgrading from I/O module boot code V103 or
earlier. If upgrading from boot versions later than 103, use iom05_01_08.app directly. If upgrading
from 103 or earlier, upgrade in a 2 step process.
This release applies to a new Advanced Software version supporting IPv6

3CR1752593V5 3Com Switch 8800 Advanced Software V5 (IPv6)
1.2. Online Resources

Visit the 3Com web site for the latest documentation and software updates:
http://www.3Com.com
Obtain a copy of the Switch 8800 Installation Guide, Command Reference Guide, or
Configuration Guide.
Obtain current software updates (maintenance releases) and associated release notes for
the Switch 8800 and other 3Com products.
1.3. System Requirements

Each Switch 8800 system has these minimum system requirements:

System Power Supply Fan Tray
Switch 8800 14-Slot Starter Kit (3C17541) 1 2

1.4. Support for New Modules

1.4.1. Release V5.01.21
Release 5.01.21 allows H3C branded modules to run in the 8800. Support is added for the
following modules.
3Com Part # Module Description

LSBM1SRP2N5 H3C S9508 Routing Switch Processing Board(XRCoreEngine II)
LSBM1FP20B1 20-Port 100BASE-FX Interface Module(B),(SFP,LC)
LSBM1FT48B1 48-Port 10/100BASE-TX Interface Module(B),(RJ45)
LSBM1GT48LDB1 48-Port 10/100/1000BASE-T Interface Service Card(DB),(RJ45)
LSBM1XP2DB1 2-Port 10GBASE-R/W Interface Module(DB),(XFP,LC)
LSBM1XP4TDB1 4-Port 10GBase-R/W Ethernet Optical Interface Service Card(DB),(XFP,LC)
LSBM2FT48CA1 48-Port 10/100BASE-TX Interface Module(CA),(RJ45)
LSBM1FP20CA1 20-Port 100BASE-FX Interface Module(CA),(SFP,LC)
LSBM1XP4CA1 4-Port 10GBASE-R/W Interface Module(CA),(XFP,LC)
LSBM1F32GCA1 32-Port 10/100BASE-TX(RJ45) and 4-Port 1000BASE-X(SFP,LC) Interface Module(CA)
LSBM1P4G8CA1 4-Port OC-3c POS(SFP,LC) and 8-Port 1000BASE-X(SFP,LC) Interface Module(CA)
LSBM1SP4CA1 4-Port OC-48c POS Interface Module(CA),(SFP,LC)
LSBM1UP1CA1 1-Port OC-192c POS Interface Module(CA),(XFP,LC)
LSBM1VP2CA1 2-Port OC-192c RPR Interface Module(CA),(XFP,LC)
1.4.2. Release V5.01.20
Release 5.01.20 added support for the following modules.
3Com Part # Module Description

3C17537 3Com Switch 8800 2-port 10G (XFP) IPv6 Module
3C17528A 3Com Switch 8800 48-port 10/100/1000BASE-T (RJ45) IPv6 Access Module

1.5. Enhancements to Software

1.5.1. V5.01.21 Enhancements/ CLI Changes
The V5.01.21 release of the Switch 8800 software included the following enhancements/CLI
changes
ENHANCEMENTS
The V5.01.21 release of the Switch 8800 includes the ability to run H3C branded blades as
described in section 1.4. These blades support various types of new functionality.
Release V5.01.21 includes only advanced code.
CLI CHANGES
The compact flash is now designated cf0 rather than cf. For example use dir cf0:/ rather than dir
cf:/
1.5.2. V5.01.20 Enhancements
The V5.01.20 release of the Switch 8800 software included the following enhancements:
IPv6 Support
RIPng
BGP4+
OSPFv3
PIM-SMv6
PIM-DMv6
Dual Stack
IPv6 Neighbor Discovery
IPv6 Path MTU Discovery
VRRPv3
IPv6 Static Route
IPv6 over IPv4
Manual IPv6 over IPv4 tunnels
Auto IPv6 over IPv4 tunnels
6to4 tunnels
ISATAP
IPv6 over IPv4 GRE tunnel
IPv4 Tunnel Interface
IPv6 Multicast (MLDv1 and MLDv1 Snooping)

ICMPv6
Pingv6
DNS6
TraceRoutev6
Telnet6
FTP6 (Client Only)
TFTP6 (Client Only)
Centralized IPv6 (supports IPv6 using one blade and one-armed routing)
User ACLs (previously removed in v3.01.30)
Proxy Arp (previously removed in v3.01.30)
IGMPv3
PIM-SSM (IPv4 only – since MLDv2 is NOT supported, source specific multicast is not
supported for IPv6)
Graceful Restart
Remote Port Mirroring
Selective QinQ (See attached documentation)
GRE
NOTE: Selective QinQ and GRE functionality is only supported on the following IPv6 capable
modules:
3C17528A 3Com Switch 8800 48-port 10/100/1000BASE-T (RJ45) IPv6 Module
3C17533 3Com Switch 8800 24-port 1000BASE-X (SFP) IPv6 Module
3C17534 3Com Switch 8800 24-port 10/100/1000BASE-T (RJ45) IPv6 Module
3C17536 3Com Switch 8800 4-port 10GBASE-X (XFP) IPv6 Module
3C17537 3Com Switch 8800 2-port 10G (XFP) IPv6 Module
3C17538 3Com Switch 8800 48-port 1000BASE-X (SFP) IPv6 Module
1.6. Changes in Behavior

Beginning with the V5.01.20 release, the Telnet feature is disabled by default. Telnet must be
enabled before it can be used.
Chapter 2 Known issues for Switch 8800 V5.01.21

This section describes known issues in the Switch 8800 V5.01.21 software.

2.1. Configuration File Issues after Software Upgrade

Because the Command Line Interface (CLI) of some features were changed considerably between
release v3.01.xx and release v5.01.20 or v5.01.21, problems could occur when trying to use
a v3.01.xx configuration file on a Switch 8800 running v5.01.20 or v5.01.21 software.
Before upgrading to v5.01.20/v5.01.21 software, save and backup the current configuration.
After the upgrade and the initial reboot, the switch will come up with the default configuration and will
not remember the name of the startup configuration file.
Issue the command "startup saved-configuration <saved-config-file-name>" to set the old

configuration file for the switch to boot with.
A second reboot of the switch is required for that configuration file to come up.
Be aware that any v3.01.xx commands in the configuration file that have changed will be ignored
when the configuration file is read by the v5.01.20/v5.01.21 software. Most of the features have had
some level of CLI changes, however, the following features have had significant changes:
• Quality of Service (QoS)

• Access Control Lists (ACL)
• DHCP relay
• RADIUS
If you are having a problem with a feature, refer to the latest configuration guide/command
reference.
2.2. Note regarding features in both Release v3.01.xx and Release

v5.01.20/v5.01.21
Similar features appear in Switch 8800 Release v3.01.xx and Release v5.01.20/v5.01.21, however,
some of the commands have changed dramatically. If you are having a problem with a feature, refer
to the latest configuration guide/command reference.
2.3. Unsupported Modules

The following modules, which were introduced in the Switch 8800 v3.01.30 release, are not
supported by v5.01.20/v5.01.21 software:
3C17542 3Com Switch 8800 Network Monitoring Module

3C17546 3Com Switch 8800 Firewall Module
3CR1754766 3Com Switch 8800 IPsec Module
3C17548 3Com Switch 8800 VPLS Module
2.4. Unsupported Features

Any feature that is not included in the documentation – whether or not it is on the Command Line
Interface (CLI) is considered unsupported. Additional specific information is included below.

The following features were supported in Release v3.1.3x but are unsupported in Release
v5.01.20/v5.01.21:
• Various ARP Commands – see 2.19 ARP.
• MBGP (Multicast BGP) – this would also affect MSDP implementations
• ISIS
• MPLS and related features:

• LDP
• L3VPNs - MPLS BGP L3VPNs
• L2VPNs - VLL (CCC, Kompella and Martini)
• Virtual Routing and Forwarding Instances (VRFs)
• VPLS
The following features are included in the CLI in the v5.01.20/v5.01.21 release but are not
supported:
• MLD Version 2 (Version 1 works – but Version 2 does NOT work.)

• MPLS TE (i.e., RSVP)
• NAT
• OAM
2.5. Multicast Protocol

In some cases, multicast traffic is not supported on ports with overlapped VLANs. As a result, some
clients will not be able to receive multicast traffic. 3Com recommends that you implement either
fully bridged multicast network or a fully routed multicast network across the link.
In the case of multicast MSDP trans-domain networking, the static RP (Rendezvous Point) mode
should be configured. Otherwise, RP dynamic switchover will make MSDP unable to send the SA
(Source Active) messages across the domains.
If the equivalent routes exist on the upstream and downstream switches, the ASSERT mechanism is
not supported, in which case the PIM SM is recommended. Otherwise, many copies of multicast
packets will impact the downstream switch upon configuration of PIM DM.
The multicast IP flows in address ranges such as X.0.0.X, X.128.0.X, X.0.1.1 and X.128.1.1 are sent
to the CPU for processing as protocol packets. These multicast IP addresses cannot be used as
multicast addresses. Otherwise, the entries of these multicast addresses cannot be established
normally, which will cause multicast forward failure.
In the case of large traffic, the duplication capability of the Trunk port is only 35 copies. If multicast
packets need to be copied to over 35 VLANs from the port, the multicast VLAN is recommended, or
packet loss may occur during packet forwarding.
In the PIM DM mode, it is suggested that the number of the multicast flows in the same group and
from different sources be no greater than 64. Otherwise, problems will occur when there is no
receiver end in the downstream. Some outgoing interfaces in the upstream do not prune, etc.
Until a multicast group is joined by a client the traffic sent from the server will flood out all ports in the
vlan in which the server is connected to. 3Com suggests locating the multicast servers on their own
vlans to avoid unwanted traffic flooding the network.

2.6. System Management

When FTP or TFTP is used to upgrade the Switch 8800 from the boot menu, the file will retain the
original filename. The system image filename should not be renamed when the boot menu is used.
This issue does not occur when upgrading the device using the CLI.
Flash on the 3C17508 fabric (360Gig) is not large enough to store the v5.01.20/v5.01.21 image.
Use the compact flash to store and boot the image and any backup images. The compact flash is
sufficient to store multiple images. The 3C17539 fabric (720Gig) on-board flash is large enough to
store a primary and backup image.
2.7. High Availability

Under some circumstances, a user may experience a short but noticeable network convergence
delay when a Switch 8800 fabric switchover occurs. A one-second switchover can be achieved
when STP is disabled and RIP routing protocol is enabled.
2.8. Broadcast Storm Control

Broadcast Storm Control (BSC) is not supported on 10-gigabit ports for the Switch 8800.
2.9. STP
A port with STP disabled will still forward received BPDUs. To prevent flooding of received BPDU’s,
enable STP globally and then disable STP per port.
2.10. TFTP
TFTP file transfer of v5.01.20/v5.01.21 software may fail using the 3CServer application. It is
recommended that customers use another TFTP application for TFTP transfers.
2.11. Boot Code

Boot code upgrade on slave switch fabric fails if boot code doesn't exist in local flash. Copy the boot
code manually to both switch fabrics.
2.12. CoS
For Switch 8800 CoS, there are prioritization issues with lower default port priorities. For untagged
packets, if the ingress port user priority corresponds to a lower traffic class than the egress port user
priority, the packets will be prioritized according to the egress port priority. This does not affect
tagged packets. Untagged packets are classified according to the following algorithm. Traffic class
(TC) equals the maximum of the TC associated with the Source Address and the TC associated with
the Destination Address.
When the Switch 8800 routes traffic over a tagged link, all packets that are not previously marked
with a CoS value will have a default value of 3 (Best Effort) applied to them. This only applies to
routed traffic. Layer 2 switched-traffic is not manipulated by the Switch 8800.
2.13. Link Aggregation

A disconnected port is still displayed as a selected member of a Link Aggregation group.

In previous releases, if the master port (lowest number port in the aggregation) in a link aggregation
changed vlans, all ports in the aggregation changed to the new vlan. In v5.01.20/v5.02.21, only the
master port changes vlan membership. There are 3 ways to address this:
1. Put all ports in the correct vlan prior to creating the link-aggregation.
2. Put all ports in the correct vlan after creating the link-aggregation.
3. Use the port group functionality after you have created and populated the link-aggregation -
e.g. to port all ports in link-agg group 1 in vlan 3 as access ports use the following
commands
a. [SW8800] port-group aggregation 1 <cr>
b. [SW8800-port-group-aggregation-1] port access vlan 3 <cr>
c. [SW8800-port-group-aggregation-1] quit<cr>
2.14. QoS
To ensure accurate traffic policing, CBS and EBS should be at least as large the MTU of the traffic
being filtered. 3Com recommends that the CBS and EBS be 2 times the size of the largest packet
expected.
On the same port, traffic shaping and WRR (Weighted Round Robin) cannot be enabled
simultaneously, or the WRR queue dispatching mode will not function.
The 100Base port can only dispatch 5 queues at one time. If it is required to send packets from over
5 queues, please use the WRR mode. Otherwise, dispatching over 5 queues may result in the
situation where the queues with low priorities cannot be dispatched and therefore the packets in
them cannot be sent.
The 3C17532 module and 3C17526 module do not support the WRR mode, so do not enable the
WRR mode on either the 3C17532 or 3C17526 board. Instead, the SP (Strict-Priority) mode should
be used.
2.15. Super VLAN

The Super VLAN feature implementation on the Switch 8800 does not allow Layer 3 communication
between sub-VLANs by default. This does NOT impact communication from the sub-VLANs out to
the network. It only impacts communication between one sub-VLAN and another. To enable Layer
3 communication between sub-VLANs, proxy ARP should be enabled on the sub-VLANs.
Try to reduce the number of SubVLANs attached to a SuperVLAN. The more SubVLANs that are
attached to a SuperVLAN, the worse its ARP learning capability will be. In the case of a full
configuration with 64 SubVLANs, the ARP learning capability will be degraded (2 per second, along
with queue overflow).
2.16. Protocol VLAN

Upper level Protocol VLAN commands are missing / not working. It is recommended that you use
the lower level commands as detailed below.
if ip ARP is desired – should use the command
[SW8800] proto mode ethernetii etype 0806
if Appletalk ARP is desired – should use the command

[SW8800] proto mode ethernetii etype 80F3
[SW8800] proto mode snap etype 80F3
The protocol vlan command “protocol at” does not cover snap encapsulated appletalk packets. If
you want to classify snap encapsulated appletalk packets on vlan X use the
[SW8800 – vlanX] protocol mode snap etype 809B <cr>
2.17. DHCP Relay

Significant changes have been made to the command line interface for this feature. Please refer to
the new configuration and command reference manuals for info on setting up this feature.
2.18. RADIUS
Significant changes have been made to the command line interface for this feature. Please refer to
the new configuration and command reference manuals for info on setting up this feature.
If an accounting server is not present – user should set accounting to optional. Otherwise log-in will
fail when the accounting server is not found.
A super password should be set. When logging in thru RADIUS, the super command may be
required to access the full set of system commands.
2.19. ARP
Commands that control the following ARP parameters are NOT included in v5.01.20 or v5.01.21.
These commands existed in all version 3 releases starting with 3.01.21.
Size of the ARP table.
ARP entries are reserved for Aggregated Links.
ARP entries available on the fabric/chassis.
ARP entries available for single ports.
The ARP table does not show Aging time.
A Switch 8800 with all Advanced MX modules (e.g., 3C17531) can learn 8K ARP entries per module
and up to 64K ARP entries per chassis. 7 aggregated link groups are supported (max link
aggregation for Advanced MX Modules is 7 groups of 8 ports in a system with all Advanced MX
Modules).
The Static Multicast ARP Across Modules feature is not included in this release. This feature was
included in v3.01.22 and 3.01.31/3.01.32 – not included in 3.01.30 or releases before 3.01.22.
Feature supports network load balancing.

2.20. LACP
Dynamic LACP has been removed from the v5.01.20/v5.01.21 release. It is recommended that the
more deterministic static LACP be used instead. Static LACP allows more customer control over the
network configuration.
2.21. Boot Loader

When using the boot-loader file (filename or pathname) slot (slot number of the fabric) (main
or backup attribute) command without a fully qualified pathname (e.g. cf0:/ or flash:/), the default is
not always flash. Example: boot-loader file 88h05_01_21s168rec01.app slot 6 main command
would be clearer if entered: boot-loader file cf0:/88h05_01_21s168rec01.app slot 6 main (or cf:/
88h05_01_21s168rec01.app slot 6 main if using the 5.01.20 release) or boot-loader file
flash:/88h05_01_21s168rec01.app slot 6 main.
Caution should be taken when specifying a code version. Use the full path name if in doubt. Use the
“display boot” command to verify that the correct agent code has been specified.
2.22. ACL
The default application order for the ACL rules is configuration order. This means that the rules are
applied in the order entered. This can be changed to auto order by using the command ACL number
xx match-order auto. In auto order, rules with a smaller range will dominate. For example: a deny
rule for a host will dominate over a permit rule for a LAN segment and traffic from that host will be
disallowed.
In the Ethernet frame header ACLs (numbers 4000 thru 4999), the vlan-id option is no longer
available. Depending upon your application, the following features may be able to be used as
substitutes:
1. Normal vlan ingress/egress rules.

2. Vlan ACLs
3. QoS policies could be used to classify based on Service Vlan Id (outer vlan tag in the case
of QinQ or the only tag in the case of a normal tagged packet) or Customer Vlan Id. NOTE:
These QoS policies can not be applied to the console or vty connections.
2.23. Jumbo Frames

The minimum jumbo frame size supported is 1552.
The 2-port 10 Gigabit Module (3C17512) supports Jumbo Frame sizes of 1518, 1536, 1552, 9022,
9192 and 10240. Setting the jumbo frame size to a value other than these supported values will
automatically set the value to the next higher jumbo frame size. For example, setting the jumbo
frame to 9216 will set the jumbo frame size to 10240 for the port.
2.24. SFTP
The Switch 8800 V5.01.20/V5.01.21 supports one SFTP connection only.

When a file is copied from SW8800 flash to a local drive, the file date is not changed so the local and
flash files have the same date. When a file is copied from local to flash, the file date follows the
SW8800 clock time (via CLI command "dir") and it shows different time - three hours behind the time
from WinSCP. For example, the SW8800 clock time is 14:55:00 UTC Fri 2006/06/02. When a file is
copied from local to the SW8800 flash via WinSCP (running on Windows XP with time zone of
Eastern time), the file date is 14:55:00 on the SW8800, but on WinSCP, the original file date is
6/2/2006 11:55:00 AM.
Can't rename file name on Flash if the file size is very large. When a file over 1.5M in size is
renamed on the SW8800 flash, it returns "Error renaming file 'xxx' to 'yyy'. Error decoding SFTP
packet (9,4,9)"
Can't edit a file on Flash, if the file size is very large. It causes the SSH connection to drop and
requests that the user re-login. If the passphase to login again is entered, SW8800 "display users"
shows two SFTP connections, although there is only one SFTP connection at this moment.
2.25. Super User Password

The ls.pwd file is where the super user password is stored. This file is created automatically when
the super user password is configured. Do not delete this file, otherwise the super user password will
be lost. Please remember to backup this file in addition to the configuration file. Once this file is
deleted, there is no way to retrieve the existing super user password. If this should happen, you
must create a new password for the super user.
2.26. 802.1x
When Microsoft Windows 2000 IAS server is enabled with DNS server/client services and the
Preferred DNS server address is configured on the NIC card, 802.1x Authentication may fail the first
authentication from 802.1x client side and request authentication twice. 3Com suggest that you
remove the DNS server address on the NIC card or use the loopback IP address (127.0.0.1)
When a large number of users conduct 802.1X authentication, it is suggested that the handshake
time be prolonged to 180 seconds. Otherwise, as the number of users passing the authentication
grows, some of the online users will be forced to go offline due to handshake failure. When the
number of users exceeds 1,000, only a few users remain online.
PAP does not work with 802.1x.
Vlan auto-assignment using mac authentication does not work..
2.27. Hardware
On the 3C17532 module, you cannot perform egress port mirroring as destination port on an Access
or Hybrid untagged port; Otherwise, the mirrored packets may be incorrectly tagged. As a result,
some network adapters cannot identify the packets.
The heat dissipation is not satisfactory if a 3C17526 module is inserted in slot 0 of a 14-Slot chassis.
If it is necessary to use a 3C17526 module, please do not inserted in the slot 0 of the 14-Slot
chassis. Otherwise, the four 10GE port cooling fans will be overheated, with the temperature
exceeding the normal work range (0~70°C).

When 3C17536 and 3C17538 modules are installed in the Switch 8800 chassis, they are in a power
down state by default. The user must manually power them up before they can be used.
2.28. ECMP
Load sharing can be implemented on only 2~6 equivalent routes. It is suggested that no more than 6
equivalent routes be used, or load sharing will be degraded.
Load sharing can be implemented through aggregations of only 2~4 links. No more than 4 links
should be used for aggregations, or load sharing through the link aggregation will not achieve a
satisfactory result
2.29. SSH
The password-control login-attempt does not determine how many times one SSH user
can retry his password before he is put into the blacklist. Instead, it is the ssh server authentication-
retries command that will control an SSH user's retry attempts.
If the user wants to have both Telnet and SSH service types available, they must be added at the
same time. If they are added one at a time, the second service type entered will replace the first
service type, rather than being added to it.
When using password control, the telnet session is terminated after 3 attempts, no matter what the
password-control login-attempts is set to. This is a change in operation from previous releases
where the telnet session was not terminated until the password control login limit was reached.
As in previous releases, however, the user is not blacklisted until the password control login
attempts limit is reached. For example, if password-control login-attempt is set to 10, the user will be
able to make 3 attempts before the telnet session is terminated. The user can re-establish telnet
and make another 3 attempts. This can be done until 10 attempts have been reached, at which
point, the SW8800 will lock the user out for the specified time.
2.30. Web Authentication / Portal

Web Authentication / Portal functionality is displayed in the command line interface, however, the
feature is not supported.
2.31. RIPng
When using RIPng route summarization, the switch will stop sending updates of the summarized
routes out of some of the other interfaces.
2.32. SFTP Configuration Backup & Restore
It is not possible to backup or restore the configuration if the configuration file is on compact flash
when using SFTP.

Workaround: please configure the default directory for the user before initiating the SFTP transfer,
e.g.
local-user 3com
work-directory cf:/
service-type ssh
2.33. MAC Authentication
When a MAC address is sent to a RADIUS server for authentication, the Switch 8800 will send the
MAC addresses without dashes (e.g. 00301bae794a rather than 00-30-1b-ae-79-4a).
When authenticating MAC Addresses, the Switch 8800 sends user names and passwords to the
RADIUS server in lower case, regardless of how the user enters it (upper or lower case) on the
Switch.
2.34. Gratuitous ARP – Change in default operation
Beginning with the 5.01.20 release, by default, the SW8800 will not cache an ARP entry when it is
sent a gratuitous ARP. You can change this by using the following command:
[SW8800] gratuitous-arp-learning enable
This change in default operation improves security, but may cause issues in certain circumstances.
For example, a stacked device may change its MAC address if there is a change in the mastership
of the stack. Usually gratuitous ARP is used to update connecting devices.
2.35. Tunnels
IPv6 packets may use the IPv4 interface MAC address. If a “display interface vlan X” command is
issued, the user will see a hardware (MAC) address for IP packet frame types and a hardware
address for IPv6 packet frame types. Generally, when responding to an IPv6 ping, the SW8800 will
respond with the IPv6 MAC address, however, when forwarding or tunneling an IPv6 packet the user
will generally see the IP MAC address. Be aware of this when setting up ACLs or monitoring traffic.
Tunnels (IPv6/IPv4, GRE) do not support multicast. This is included in the documentation – but is
also included here for clarity. Some tunnels may allow PIM to be configured on the tunnel interface,
however, multicast traffic will not cross the tunnel.
3Com uses a different IPv6 tunnel MTU than Cisco. MTU is 1500 for 3Com and 1480 for Cisco. If
OSPF is being run between the tunnel interfaces, users should set the 3Com IPv6 MTU to 1480 in
interface tunnel view. See the following example for tunnel 2/0/1:
[SW8800] interface tunnel2/0/1<cr>

[SW8800-Tunnel2/0/1] ipv6 mtu 1480 <cr>
[SW8800-Tunnel2/0/1] quit <cr>

2.36. Selective QinQ

Rather than using the port priority to fill in the priority in the outer tag, selective QinQ maps the inner
priority to the outer tag. Users can workaround this by using “remark behavior” to control the outer
priority tag as follows:
[SW8800]traffic behavior 1
[SW8800-behavior-1]remark dot1p 7
2.37. Host Name Length

For IPv4, the maximum host name (for ping, telnet, ftp, tftp, traceroute, etc.) is 20 characters. If
using hostnames longer than 20 characters, please use the IP address directly for ping, etc.
NOTE: The default domain name is in addition to the 20 character limit. For example, if the host
name is 19 characters and the default domain name is another 6 characters - that will work, as long
as the user pings hostname rather than ping hostname.defaultdomainname.
2.38. 3C17532 and 3C17532A Limitations

3C17532 and 3C17532A modules are designed to be used as access modules. They are supposed
to be connected to PCs, rather than connected into the core of the network. In addition to the
standard list of limitations for the 3C17532 and 3C17532A access modules, the modules have the
following additional limitations
1. Modules have 4 queues rather than 8 queues.
2. Modules may not prioritize packets as expected depending on which ports are used for
incoming streams.
3. Port mirroring may experience issues:
a. On tunnel interface, may only see inbound traffic, even if both directions are
selected.
b. May not be able to setup remote mirroring with the 3C17532 as the remote source.
4. With QinQ, 2 tags may be added to an untagged packet. In most instances, users should
avoid using untagged vlans connected to the QinQ enabled port – this will eliminate this
problem.
2.39. IGMP
When running IGMPv3 please be sure that all multicast clients are also IGMPv3 capable. If not,
3Com suggests running IGMP version 2.
Within a single VLAN running IGMP version 3, multicast will always forward to a client regardless of
the message type sent by the end station.
2.40. UDP Helper
UDP helper does not forward a packet with a time to live (TTL) of 1. It decrements the TTL during
the forwarding process. This may cause issues with protocols like UNIX NIS, which are generated
with a TTL of 1. It should NOT be a problem with protocols like NetBios that are generated with a
higher TTL.

2.41. Documentation Addendum

The following information is missing from the Switch 8800 documentation:
Setting up Selective QinQ
The SW8800 uses QoS Policies to setup selective QinQ. The following example shows how to map
an incoming packet with a customer tag of vlan 3 and 4 with an outer (service vlan) tag of 5. Policy
is applied to port gigabit-ethernet2/1/1
# Create the traffic classifier

# Yes – you do want to use if-match service-vlan-id in this case. At the end of the process vlans 3
and 4 will be the customer vlan ids – but as incoming packets, they are NOT encapsulated yet.
Therefore they are the outer tags.
[SW8800] traffic classifier selective operator or <cr>
[SW8800-classifier-selective] if-match service-vlan-id 3 4 <cr>
[SW8800-classifier-selective] quit<cr>
#Create the desired behavior – nest with top-most vlan-id of 5.

[SW8800] traffic behavior selective <cr>
[SW8800-behavior-selective] nest top-most vlan-id 5<cr>
[SW8800-behavior-selective] quit <cr>
# Create a policy mapping the classifier to the desired behavior

[SW8800] qos policy selective
[SW8800-qospolicy-selective] classifier selective behavior selective <cr>
[SW8800-qospolicy-selective] quit <cr>
# Create a flow-template – this is required

[SW8800] flow-template selective basic service-vlan-id customer-vlan-id <cr>
# Apply the flow template and the qos policy to the desired port.
[SW8800] interface gig2/1/1
[SW8800-GigabitEthernet2/1/1] flow-template selective <cr>
[SW8800-GigabitEthernet2/1/1 qos apply policy selective inbound
Chapter 3 Upgrading Software

3.1.1. IMPORTANT NOTES:
Always save the configuration file before upgrading software images.
At the present time the flash on the 3C17508 fabric (360Gig) is not large enough to store the 5.01.21
image. The .app file is approximately is 30165 KB. The size of the 3C17508 fabric (360Gig) flash is
15621 KB. Use the compact flash to store and boot the image and any backup images. The
compact flash is sufficient to store multiple images. The 3C17539 fabric (720Gig) on-board flash is
large enough to store a primary and backup image. The size of the 3C17539 fabric (720Gig) flash is
64389 KB. If desired, the primary image could be stored on flash, and the backup image could be
stored on compact flash. Be aware that the configuration file (the .cfg file) can often be larger than
5KB when deciding on how to layout the file system.
Upgrade from V3 to V5 is not supported by the Agent Update functionality in 3Com Network Director
and Enterprise Management Suite. However, upgrade within V5 (i.e., from v5.01.20 to v5.01.21) is
supported.

Be aware that the 5.01.21 release contains not only operational code for the fabrics
(88h05_01_21s168rec01.app), but also boot code images for the fabric and the I/O modules. The
fabric bootROM code is named fab05_02_06d.app (current version is 206) and the I/O module
bootROM code is named iom05_01_08.app (current version is 108). Use the _display ver
command to examine the current BootROM Version.
The 8800 Switch Fabric MUST be running bootROM V206 or greater before attempting to boot the
5.01.21 operational code. If this is not done, the Fabric will not boot up properly.
When upgrading to the v5.01.21 image, make sure that the fabric operational code, fabric bootROM
code and I/O module bootROM code are upgraded BEFORE the Switch 8800 is rebooted. If this is
not done, the Switch 8800 will not boot up properly.
If the I/O modules are currently running bootROM code version V103 or earlier, you cannot upgrade
directly to V108 bootROM code. You must upgrade to V107 bootROM code first and then after the
Switch 8800 is rebooted the I/O modules can be upgraded to V108 (iom03_01_08.app). If you try to
upgrade from bootROM code V103 or earlier directly to V108, the system will prompt that the
upgrade file is not compatible and the upgrade will fail. V107 bootRom code is included with the
5.01.21 release bundle in the event that you need to upgrade to this version of bootRom code first.
The V107 bootROM code is named 8800boot-module1107.app.
The bootROM file must be on each fabric that is being updated. You can not update bootROM on
the slot 1 fabric if the bootROM file is only on slot 0. Copy the bootROM file to the file system of slot
1. More recent application files support the bootROM file being stored on compact flash or flash, but
earlier versions may require that the bootROM file be on flash.
To upgrade the software application image of a 7, 10 or 14 slot Switch 8800, use the applicable
procedures in sections below for upgrading through FTP, Boot Menu, Xmodem, or TFTP. FTP and
tftp are much quicker than using the boot menu procedure or Xmodem. Xmodem has a much
slower download speed because the serial port is used. In addition, updating a unit with dual fabrics
is more difficult when using the boot menu/Xmodem.
Unless indicated otherwise, the examples use the slot numbering for a 7-slot chassis. Slots 0 and 1
on a 7-slot contain the master and slave fabrics respectively. These slots correspond to slots 4 and
5 on a 10-slot chassis and to slots 6 and 7 on a 14-slot chassis. The examples also assume that the
master fabric is in the lower numbered slot – which is usually but not always the case. The master
fabric may also be referred to as the primary fabric. The slave fabric may also be referred to as the
secondary fabric.
When setting the boot-loader – always use the full path name flash:/, slot1#flash, cf:/, cf0:/,
slot1#cf:/, slot1#cf0: and confirm that the file has been set correctly using the display boot
command.
If a compact flash is used – ensure that it is recognized when the dir cf:/ or dir cf0:/ or the dir
slot1#cf:/ or the dir slot1#cf0:/commands are issued. If not recognized – it may not be formatted
correctly for use with the 8800. If necessary, use the format cf: or format cf0: command with
caution. Format will erase the contents of the compact flash.

Before you upgrade the software image, there are several things to remember:
Confirm if an operational code has been loaded before initiating software upgrade.
Check the current version of the operational code and Boot ROM version of the modules before
upgrading. To inquire about the current versions number:
<SW8800>_display version
3Com Corporation
3COM OS SW8800 V5.01.21s168rec
Copyright(c) 2004-2007 3Com Corporation and its licensors. All rights reserved.
Switch 8800 uptime is 0 week, 5 days, 4 hours, 45 minutes
Back up the current image, BootROM program files (.app files) and configuration files to a PC or
an FTP or tftp server, for possible rollback in case of failed upgrade. An example using FTP to
backup these files is located here Backing up the configuration file and the operational OS
agent.
After you install the redundant fabric module, you must wait for several minutes [at least 6
minutes] until a CLI message indicates that the slave is synchronized to the master, then save
the configuration. Use the command display switchover state to verify the synchronization
state. Fabrics are synchronized when the message real time and routine backup is displayed.
For example:
Fabrics are NOT synchronized:

<SW8800>dis switchover state
HA FSM State(master): Waiting batch backup request from slave.
Fabrics are synchronized:

<SW8800>dis sw st
HA FSM State(master): Realtime and routine backup to slave.
When upgrading through the boot menu, use the management port on the master fabric to
download an application code. For tftp/ftp, you can use the management port (the Ethernet port
on the fabric) or a VLAN interface (in-band Ethernet port on an I/O module, not a Network
Application Module).
You must set the boot-loader file to the new boot-loader name file after you download it. This
has to be done on each fabric. For example, in a 14 slot Switch 8800 with dual fabrics:
<SW8800> boot-loader file cf:/88h05_01_21s168rec01.app slot 6 main
<SW8800> boot-loader file slot7#cf:/88h05_01_21s168rec01.app slot 7 main
Use the display boot-loader command to verify:
<SW8800> display boot-loader
The primary app to boot of board 6 at the next time is: cf:/88h05_01_21s168rec01.app
The primary app to boot of board 7 at the next time is: cf:/88h05_01_21s168rec01.app

<SW8800>
Note: Above application name may vary.
After you upgrade both fabrics and upgrade the BootROM code (Upgrading BootROM Code
Using the Command Line Interface ) and save the configuration, then you must reboot the switch
so the new software code can be loaded.
You can check free space on the Switch 8800 with the dir command, in user view. Example:
For a 7 slot chassis with dual fabrics – master fabric in slot 0, slave fabric in slot 1 - the
commands dir, dir cf:/, dir slot1#flash:/ and dir slot1:cf:/ are required to check free space on
the master fabric, master compact flash, slave fabric and slave compact flash, respectively. Use
cf0:/ rather than cf:/ if already at v5.01.21.
You may need to delete files and clear the recycle bin (using the delete file and reset recycle-
bin commands) to make room for a new application image file. These commands (delete
<slot1#flash:/file> or delete <slot1#cf:/file> and reset recycle slot1#flash:/ or reset recycle
slot1#cf:/) need to be executed for both the master and the slave fabric modules. Reset
recycle bin can take minutes depending on how many bytes are in the recycle bin. Use cf0:/
rather than cf:/ if already at v5.01.21.
Another way to delete a file permanently is by issuing the delete /unreserved filename
command. This can take minutes depending on the size of the file.
It may be useful in some cases to download directly to compact flash (cf). The procedures below
do not require this if the fabric is a 3C17539 fabric (720Gig). If the fabric is a 3C17508 fabric
(360Gig) this will have to be done. To copy directly to compact flash, use the destination option.
For example: instead of using: tftp 10.10.110.1 get 88h05_01_21s168rec01.app use: tftp
10.10.110.1 get 88h05_01_21s168rec013.app cf:/ 88h05_01_21s168rec01.app. Use cf0:/
rather than cf:/ if already at v5.01.21.
Upgrade to the latest boot code on the fabric(s) or the fabric(s) will not boot up properly.
Upgrade should occur at the point indicated in the following procedures.
3.2. General Upgrade Procedure

To upgrade the Switch 8800:
1. Copy the existing application code from the flash to the compact flash to ensure that a
valid image exists on the 8800. [This step is optional. It is recommended that you
always maintain a valid APP file on flash/compact flash. However, it is not required.
Just do NOT reboot without a valid APP file and make sure the boot-loader is configured
to boot from that valid APP file.]
In the following example, dual fabrics are installed in a 7-slot chassis. Use the following
commands:
<SW8800> copy 88h05_01_21rec01.app cf:/ 88h05_01_21rec01.app
<SW8800> copy slot1#flash:/ 88h05_01_21rec01.app slot1#cf:/ 88h05_01_21rec01.app

2. If NOT already running the latest boot code - upgrade the BootROM - Upgrading
BootROM Code Using the Command Line Interface for more details. The current
release of BootROM for the fabrics is 206, for the I/O modules it is 108.
3. Ensure sufficient space on the master and slave fabric flash(es) or compact flash (cf:/) to
hold the new application code (.app files). See the dir commands described above.
Delete files as necessary; see the delete and reset recycle commands described
above. The code size for Advanced Code 88h05_01_21s168rec01.app is 30,888,988
bytes. The bootROM code for the fabric(s) (fab05_02_06d.app size is 326896) and I/O
modules (iom05_01_08d.app size is 207696) will be placed on flash:/ on the fabric(s).
4. If the fabric is a 3C17539 720 Gbps fabric, download the new software OS agent code
to the master fabric’s flash:/ or cf:/ (compact flash) in Slot0 in a 7-slot chassis, Slot4 in a
10-slot chassis, and Slot6 in a 14-slot chassis using one of the procedures outlined in
Upgrading Application Software using FTP, Upgrading Application Software Using the
BOOT Menu, Upgrading Application Software Using Xmodem or Upgrading Application
Software Using TFTP. Do not issue the reboot command until the bootROM has been
updated.
If the fabric is a 3C17508 360Gbps fabric, download the new code to the master fabrics
compact flash (cf:/) in Slot0 in a 7-slot chassis, Slot4 in a 10-slot chassis, and Slot6 in a
14-slot chassis using one of the procedures outlined in Section Upgrading Application
Software using FTP, Upgrading Application Software Using the BOOT Menu, Upgrading
Application Software Using Xmodem or Upgrading Application Software Using TFTP. Do
not issue the reboot command until the bootROM has been updated.
5. If the fabric is a 3C17539 720Gbps fabric, copy the new code from the master fabric
flash:/ or cf:/ and to the backup fabric flash:/ or cf:/:
Slot0 to Slot1 in a 7-slot chassis
Slot 6 to Slot7 in 14-slot chassis
Use the following command to copy to flash:/:
<SW8800> copy flash:/88h05_01_21s168rec01.app slot1#flash:/88h05_01_210s168rec01.app
Use the following command to copy to cf:/:
<SW8800> copy cf:/88h05_01_21s168rec01.app slot1#cf:/88h05_01_21s168rec01.app
It can take several minutes to copy the code from the master to the slave fabric. The CLI will
not respond during this operation.
If the fabric is a 3C17508 360 Gbps fabric copy the new code from the primary fabric cf:/
to the backup fabric cf:/ :
Slot 6 to Slot7 in 14-slot chassis
Use the following command:
<SW8800> copy cf:/88h05_01_21s168rec01.app slot1#cf:/88h05_01_21s168rec01.app
It can take several minutes to copy the code from the master to the slave. The CLI will not
respond during this operation.
6. Use the following commands to configure the boot loader with primary and backup app
files.

Use these commands if running software OS V3.x.x:
Below are the primary files the switch fabrics will load upon boot.
<SW8800> boot boot-loader pri flash:/88h05_01_21s168rec01.app slot 0
<SW8800> boot boot-loader pri slot1#flash:/88h05_01_21s168rec01.app slot 1
Optional: Below are the backup files the switch fabrics will load if
there is a problem with the primary files.
<SW8800> boot-loader backup cf:/88h03_01_31s256rec02.app slot 0

<SW8800> boot-loader backup slot1#cf:/88h03_01_31s256rec02.app slot 1
Use these commands if running software OS V5.x.x:
Below are the primary files the switch fabrics will load upon boot.
<SW8800> boot-loader file flash:/88h05_01_21s168rec01.app slot 0 main
<SW8800> boot-loader file slot1#flash:/88h05_01_21s168rec01.app slot 1 main
Optional: Below are the backup files the switch fabrics will load if
there is a problem with the primary files.
<SW8800> boot-loader file cf:/88h05_01_20s168rec03.app slot 0 backup
<SW8800> boot-loader file slot1#cf:/88h05_01_20s168rec03.app slot 1 backup
Notes:
1. Above application name may vary.
2. If already at v5.01.21 – use cf0:/ rather than cf:/
7. Use the display boot command to ensure that the boot loader has been set correctly.
8. Save the configuration. Make a backup copy of the configuration if not already done.
Display start will display the current configuration file. You can also make a copy of the
current configuration file with a different name, it can be saved to flash: and/or cf:
(compact flash) on the master and backup fabrics. See the example below. It can also
be backed up to an FTP or tftp server.
Example, the startup file is named sw8800dc1.cfg. Your configuration file

will have a different name.
<SW8800>save
The configuration will be written to flash:/sw8800dc1.cfg
Are you sure?[Y/N]y
Now saving current configuration to the device.
Saving configuration flash:/sw8800dc1.cfg. Please wait...
Configuration is saved successfully.

<SW8800>dis start
MainBoard:
Startup saved-configuration file: flash:/sw8800dc1.cfg
Next startup saved-configuration file: flash:/sw8800dc1.cfg
<SW8800>copy flash:/sw8800dc1.cfg flash:/sw8800dc1bac.cfg
Copy flash:/sw8800dc1.cfg to flash:/sw8800dc1bac.cfg?[Y/N]:y

100% complete
Copy file flash:/sw8800dc1.cfg to flash:/sw8800dc1bac.cfg...Done.
<SW8800>copy flash:/sw8800dc1.cfg cf:/sw8800dc1bac.cfg
Copy flash:/sw8800dc1.cfg to cf:/sw8800dc1bac.cfg?[Y/N]:y
100% complete
Copy file flash:/sw8800dc1.cfg to cf:/sw8800dc1bac.cfg...Done.
<SW8800>copy flash:/sw8800dc1.cfg slot5#flash:/sw8800dc1Backup.cfg
Copy flash:/sw8800dc1.cfg to slot5#flash:/sw8800dc1backup.cfg?[Y/N]:y
100% complete
Copy file flash:/sw8800dc1.cfg to slot5#flash:/sw8800dc1backup.cfg...Done.
<SW8800>copy flash:/sw8800dc1.cfg slot5#cf:/sw8800dc1Backup.cfg
Copy flash:/sw8800dc1.cfg to slot5#cf:/sw8800dc1backup.cfg?[Y/N]:y
100% complete
Copy file flash:/sw8800dc1.cfg to slot5#cf:/sw8800dc1backup.cfg...Done.
9. Issue the reboot command and enter Y at the reboot prompt so the system reboots.
10. User can verify which code is running by using the display version or the _display
version command.
11. After the reboot, the configuration file will need to be reconfigured using the start saved-
configuration (configuration pathname) command. This is only necessary once. You
will need access to the console port. You will NOT be able to telnet into the Switch 8800
at this time. Then reboot the switch again. Answer Y to the question “Current
configuration will be lost in next startup if you continue. Continue?”.
IF YOU ARE UPGRADING FROM V3.01.02

1. V3.01.02 does NOT support a backup image – so the boot-loader commands are
somewhat different.
a. Perform steps 1 thru 5 above – except that you are upgrading from 3.01.02
rather than 3.01.21.
b. After downloading the new code, change the boot-loader on the master to boot
the new code using the following command and specify the appropriate slot for
your chassis.
<SW8800> boot boot-loader flash:/88h05_01_21s168rec01.app slot 0
c. After downloading the new code, change the boot-loader on the slave to boot
the new code using the following command and specify the appropriate slot for
your chassis.
<SW8800> boot boot-loader slot1#flash:/88h05_01_21s168rec01.app slot1
d. Upgrade the bootROM code using section 4.6
e. You can use the display boot-loader command to verify that the new code will
run the next time the chassis is booted.
f. Save the configuration, then issue the reboot command and enter Y at the
reboot prompt so the system reboots
g. User can verify which code is running by using the display version or the
_display version command
2. After upgrading to the new code, a backup image can be set.
a. Set a primary and backup file as shown in Step 6 above.

b. Use the display boot command to ensure that the boot loader has been set
correctly
c. Save the configuration, then issue the reboot command and enter Y at the
reboot prompt so the system reboots
d. User can verify which code is running by using the display version or the
_display version command.
NOTE: In the following examples, the IP address of the local computer which is acting as the FTP or
TFTP server is 10.10.110.1 and the image is 88h05_01_21s168rec01.app. Actual IP addresses and
filenames will depend on your system and software versions.
User input is bold faced.
These examples assume that the Switch 8800 is set up with an IP address on the Ethernet port on
the fabric. To set up the Ethernet port on the fabric with an IP address, use the following commands
in super-user mode:
[SW8800]interface M-Ethernet 6/0/0
[SW8800-M-Ethernet 6/0/0] ip address 10.10.110.2 255.255.255.0

3.3. Upgrading Application Software using FTP

NOTE: There are FTP/TFTP servers on the 3Com.com website. Search for “tftp server”. They are
located in “3Com Software Library – Utilities for 32 bit Windows”
Before you upgrade:
• Make sure you have access to the console port (serial port- 9600 Baud, 8, 1 and parity is
none) on the fabric.
• Verify that there is a connection between the FTP server and the Switch 8800 (use the ping
command).
• Verify that the FTP server is setup according to the manufacturer’s instructions and that
it is enabled and pointing to the correct upload/download directory. This is the directory
that contains the files that will be used for the update. The needed files are
88h05_01_21s168rec01.app, iom05_01_08d.app and fab05_02_06d.app.
• When using the Switch 8800 as an FTP client, if this is message is returned:
202 Command PASV not implemented
Enter undo pas at the [ftp] prompt.
There are two ways of downloading program files: FTP to a local PC from a switch and FTP to a
switch from a local PC. In the first mode, a PC with FTP server application serves as a FTP server.
There is a complete update procedure example using FTP in section Software Update Example.
Use the following procedure to upgrade software using the first method:
1. Login to the switch with super-user privileges, usually user admin.
2. Verify that there are enough free space on flash: and/or compact flash on the fabric(s) to
copy the files needed. The software OS agent file 88h05_01_21s168rec01.app size is
30888988 records. The bootROM code for the fabric(s) (fab05_02_06d.app size is
326896) and I/O modules (iom05_01_08d.app size is 207696) will be placed on flash:
on the fabric(s). See sections IMPORTANT NOTES: and General Upgrade Procedure
for more information on the file system commands. For an example, see section Ensure
sufficient space on the master and slave fabric flash(es) and/or compact flash (cf:/) to
hold the new application code (.app files).
3. Upgrade the BootROM code by using the upgrade procedures in section Upgrading
BootROM Code Using the Command Line Interface
4. Identify the currently used configuration file.
5. From the Switch 8800 command line, FTP the file from the FTP server to the system.
6. Copy the application file from the primary fabric to the backup fabric.
7. Set the boot parameters to specify the file to boot the system from.
8. Reboot the system. Make sure you can access the console port before you reboot.
9. After the reboot, the configuration file will need to be reconfigured using the start saved-
configuration (configuration pathname) command. This is only necessary once. You
will need access to the console port. You will NOT be able to telnet into the Switch 8800
at this time. Then reboot the switch again. Answer Y to the question “Current
configuration will be lost in next startup if you continue. Continue?”.
The following example illustrates this procedure:

NOTES:
1. The general upgrade procedure (General Upgrade Procedure and IMPORTANT NOTES:)
contains more details related to copying files, etc.
2. The following example illustrates this procedure. This procedure was done using the console
port on the primary fabric.
<SW8800>su
Password:
Now user privilege is 3 level, and just commands which level is
equal to or less than this level can be used.
Privilege note: 0-VISIT, 1-MONITOR, 2-SYSTEM, 3-MANAGE
#####################################################################
UPGRADE THE BOOTROM AT THIS POINT – GO TO Upgrading BootROM Code
Using the Command Line Interface
#####################################################################
#######################################################################
Do a dis start, know where your configuration file is and what the
filename is. This information will be needed later in this procedure.
#######################################################################
<SW8800> ftp 10.10.110.1

Trying ...
Press CTRL+K to abort
Connected.
220 3Com 3CDaemon FTP Server Version 2.0
User(none):anonymous
331 User name ok, need password
Password: xxxxxxx
230 User logged in
[ftp]bin
200 Type set to I.
###########################################################
If the fabric is a 3C17508 fabric (360Gig), software OS
agent code has to be copied to compact flash (cf:). If the
fabric is a 3C17539 fabric (720Gig), the software OS agent
code can be copied to flash:/ (provided there are enough free
records) or cf:/. In the commands below, cf:/ is used.
###########################################################
[ftp]get 88h05_01_21s168rec01.app cf:/88h05_01_21s168rec01.app

227 Entering passive mode (10,10,110,1,14,66) PORT command successful.
125 Using existing data connection
226 Closing data connection; File transfer successful.
FTP: 30888988 byte(s) received in 70.354 second(s) 439.00K byte(s)/sec.
[ftp] quit
221 Service closing control connection
###########################################################
See the general procedure for more details on copying files,
Making space on flash, etc. (Files must be on BOTH fabrics)
###########################################################
<SW8800>copy cf:/88h05_01_21s168rec01.app slot1#cf:/88h05_01_21s168rec01.app

Copy cf:/88h05_01_21s168rec01.app to slot5#cf:/88h05_01_21s168rec01.app?[Y/N]:y
1% complete ……
100% complete
Copy file cf:/88h05_01_21s168rec01.app to slot5#cf:/88h05_01_21s168rec01.app...
Done.

The CLI will not respond during this operation.
####################################################################
IF CURRENTLY RUNNING THE 3.01.02 Code
Assumes 7 slot chassis – fabrics in slot 0 and 1.
After the switch is rebooted with the new application code running,
then the boot-loader for the backup image can be configured.
#####################################################################
<SW8800> boot boot-loader cf:/88h05_01_21s168rec01.app slot 0
The specified file will be booted next time!
<SW8800> boot boot-loader slot1#cf:/88h05_01_21s168rec01.app slot 1
############################################################
Use the display boot command to verify the Boot-loader
configuration.
############################################################
###########################################################
IF CURRENTLY RUNNING THE 3.01.22 or 3.01.30 Code
Your backup filename maybe different.
• Assumes 14 slot chassis – fabrics in slot 6 and 7
###########################################################
<SW8800> boot boot-loader pri cf:/88h05_01_21s168rec01.app slot 6
<SW8800> boot boot-loader pri slot1#cf:/88h05_01_21s168rec01.app slot 7
<SW8800> boot boot-loader backup cf:/88h03_01_22rc02.app slot 6

<SW8800> boot boot-loader backup slot1#cf:/88h03_01_22rc02.app slot 7
############################################################
configuration.
############################################################
###########################################################
###########################################################

NOTE: Use cf0:/ rather than cf:/ if running v5.01.21

############################################################
configuration.
############################################################
<SW8800> save
The configuration will be written to the device.
Are you sure? [Y/N] y
Now saving current configuration to the device.
Saving configuration flash:/sw8800.cfg Please wait…
…..
Configuration is saved to flash memory successfully.
<SW8800> reboot

############################################################################
Login to the switch with super-user privileges, usually user admin.
IF UPGRADING FROM A V3 CODE VERSION TO A V5 CODE VERSION - The start-up file has to
be configured again. The switch will be set to defaults. This only has to be done
once, after the first reboot.
IF UPGRADING BETWEEN V5 CODE VERSIONS – This step is not necessary. Start-up

(configuration) file should remain the same. Use display start to confirm.
############################################################################
<SW8800> dis start
MainBoard:
Current startup saved-configuration file: NULL
Next startup saved-configuration file: NULL
SlaveBoard:
############################################################################
The configuration file used on this switch is sw8800dc1.cfg. There is on a copy on
flash: on both the master and the slave fabric.
############################################################################
<SW8800>dir
Directory of flash:/
0 -rw- 326680 Nov 13 2007 18:41:36 fab03_02_03d.app
1 drw- - Jan 01 2003 00:00:24 hafile
2 -rw- 4 Jan 21 2006 04:18:37 snmpboots
3 -rw- 248 Oct 23 2004 09:59:54 manuinfo.txt
4 -rw- 267648 Jan 21 2006 04:56:13 lsbsrp1n01118.app
5 -rw- 524392 Jan 21 2006 04:56:39 lsblmcua01107.app
6 -rw- 118 Sep 20 2006 21:18:12 ls.pwd
7 -rw- 207696 Nov 13 2007 18:41:56 iom03_01_08d.app
8 -rw- 272898 Nov 13 2007 18:42:19 iop03_02_05d.app
9 -rw- 3950 Nov 14 2007 10:27:35 sw8800dc1.cfg
10 -rw- 326896 Nov 13 2007 19:35:36 fab05_02_06d.app
11 -rw- 207696 Nov 13 2007 19:36:03 iom05_01_08d.app
12 -rw- 273034 Nov 13 2007 19:36:16 iop05_02_06d.app
13 -rw- 3803 Nov 14 2007 10:00:40 sw8800dc1backu.cfg
15621 KB total (13198 KB free)
############################################################################
Configure the switch to use from the desired configuration file. Notice that the
configuration file was set on both the master and slave fabric. Your filename
will be different.
############################################################################
<SW8800>start saved-configuration flash:/sw8800dc1.cfg
Please wait ...
Setting the master board ............ Done!
Setting the slave board ...... Done!
############################################################################
Verify what was just configured.
############################################################################
<SW8800>dis start
MainBoard:
SlaveBoard:
############################################################################
Reboot the switch. Answer Y to the question “Current configuration will be lost
in next startup if you continue. Continue?”.
############################################################################
<SW8800>reboot
Start to check configuration with next startup configuration file, please
wait
......

This command will reboot the device. Current configuration will be lost
in next startup if you continue. Continue? [Y/N]:Y
This will reboot device. Continue? [Y/N]:y
For more detailed descriptions of the set up and procedures for upgrading software, see the
remaining sections in this chapter.
In second method, a switch serves as a FTP server. Users log in the switch from a local PC by FTP.
Configure switch to be an FTP Server. Create a user account (8800) to use the switch as an FTP
server. The local-users working directory on the switch is compact flash (cf:/) or flash:/. The working
directory should be where the software OS agent file 88h05_01_21s168rec01.app will reside. Enter
the system view (sys), if not already in the system view.
[SW8800]ftp server enable
% Start FTP server
[SW8800]local-user 8800
New local user added
[SW8800-luser-8800]service-type ftp
Use the following commands (depending on the current code version) to set the work directory.
[SW8800-luser-8800]service-type ftp ftp-directory cf:/
OR
[SW8800-luser-8800]work-directory cf:/
[SW8800-luser-8800]password simple 880088008800

NOTE: Use cf0:/ rather than cf:/ if running 5.01.21
FTP to the switch from a local PC and transmit application file to the switch. Assuming the software
OS agent code is file 88h05_01_20s168rec03.app; the fabric BootROM file is fab05_02_06d.app
and iom05_01_08d.app is the bootROM file for I/O modules. Verify that there is connectivity
between the FTP server and client. Ping can be used. In the example below a PC is used, a
command window (or DOS window) was opened. The IP address of the Swtich 8800 is 192.168.0.1.
The file 88h05_01_20s168rec03.app will be transferred to the Switch 8800’s compact flash on the
master fabric.
C:\> ftp 192.168.0.1
Connected to 192.168.0.1.
220 FTP service ready.
User (192.168.0.2:(none)): 8800
331 Password required for 8800.
Password: (enter password)
230 User logged in.
ftp> bin
200 Type set to I.
ftp> put c:\SW8800\88h05_01_21s168rec01.app
200 Port command okay.

150 Opening BINARY mode data connection for 88h05_01_21s168rec01.app.

226 Transfer complete.
ftp: 3088898 bytes sent in 135.51 Seconds 227.95K bytes/sec.
ftp> bye

3.4. Upgrading Application Software Using the BOOT Menu

This section illustrates an upgrade of the Switch 8800 through the BOOT menu using TFTP. You
can also use FTP by entering information for FTP in Step 6.
To perform this procedure, you must have a network connection to the Ethernet port on the Switch
8800 master fabric module. This procedure is done from the console port on the master fabric.
New application code will NOT run with older bootROM code. Please update bootROM code first.
See section Upgrading BootROM Code Using the Command Line Interface.
Make sure there are enough free records to fit the file 88h05_01_21s168rec01.app, size is
30888988 Bytes. If the fabric is a 3C17508 fabric (360Gig), the file has to be loaded on CF:/ (or
CF0:/). For more information on file system commands, see sections IMPORTANT NOTES: and
General Upgrade Procedure.
After powering on the Switch 8800 or after a reboot of the Switch 8800, the BootROM program runs
automatically. In the examples below the new software OS agent code 88h05_01_21s168rec01.app
is loaded on CF:/. (CF0:/ if already running 5.01.21)
The terminal displays the following information:
NOTE: If at BootROM code 206, the following banner will be displayed. If not at bootROM code 206
– STOP – do NOT proceed. Go to Upgrading BootROM Code Using the Command Line Interface .
The new application code will not run with older versions of boot code.
Starting...
*************************************************
* *
* Switch 8800 Bootrom, Version 206 *
* *
*************************************************
Copyright (c) 2004-2007 3Com Corporation and its licensors.

CPU type : MPC755
CPU L2 Cache : 1024KB
CPU Clock Speed : 400MHz
BUS Clock Speed : 100MHz
Memory Size : 512MB
Board self testing...........................

The board is steady
SlotNo of this board is 4
The MCX is present
BootRom main system CRC check is OK
82559 register testing is OK
EPLD1 testing is OK
EPLD2 testing is OK
16c2552 register testing is OK
Please check LEDs......................LED testing finished
The switch's Mac address is 0020.9c69.ec98

Press Ctrl+B to enter Boot Menu... 5
NOTE: To access the BOOT Menu, press Ctrl+B during the 5 seconds that “Press Ctrl-B to enter
Boot Menu...” prompt displays. Within 5 seconds, the system begins program decompression. At
this time if you want to access the BOOT Menu, you must reboot the switch.
password:
1. Enter the BootROM password. After entering the correct password (no password is set
for the switch by default, just hit “Enter”), the system will access the BOOT Menu:
Caution: While using the switch, keep in mind the modified BootROM password.
MAIN MENU
1. Boot with default mode

2. Boot from primary file
3. Boot from backup file
4. Enter serial submenu
5. Enter ethernet submenu
6. Modify Flash description area
7. Modify bootrom password
0. Reboot
Enter your choice(0-7): 6
2. Option 1 boots from the default mode (flash or compact flash). Select option 6 to set the
default mode. User input is bold faced.
Modify primary boot information
Please input '0' or '1' ('0':Boot from Flash, '1':Boot from CF card)
BootDev = 1 1
FlashFileName = 88h03_01_21rc09sp01.app 88h05_01_21s168rec01.app

The file name you input is 88h05_01_20s168rec03.app,
Are you sure? Yes or No(Y/N)Y
CF card FileName = 88h05_01_21s168rec01.app
Writing main boot information...done
Modify backup boot information? Yes or No(Y/N)N
3. The Main Menu displays:
MAIN MENU



0. Reboot
4. Enter option 5. The Ethernet Submenu displays:
ETHERNET SUBMENU
1. Download file to SDRAM through ethernet interface and boot

2. Download file to Flash through ethernet interface
3. Download file to CF card through ethernet interface
4. Modify ethernet interface boot parameter
0. Return to main menu
Be sure to select 4 to modify boot parameter before downloading!

5. Select option 4 to modify the boot parameter in flash before downloading. Note that for
the flags entry, you must enter 0x80 if you want to download using TFTP, or 0x0 if you
want to download using FTP. In the example below 158.101.23.252 is the IP address of
the ethernet port on the fabric. 158.101.23.100 is the IP address of the FTP server, the
ftp user id is Update with a password of password. The Switch and FTP server are on
the same IP network so a gateway was not needed.
Note: Two protocols for download, tftp & ftp.

You can modify the flags following the menu.
tftp--0x80, ftp--0x0.
boot device : fei

unit number : 0
processor number : 0
host name : 8512
file name : oemflag.app
inet on ethernet (e) : 192.168.0.13
host inet (h) : 192.168.0.12
user (u) : 8512
ftp password (pw) : 123
flags (f) : 0x0
'.' = clear field; '-' = go to previous field; ^D = quit
boot device : fei0

host name : 8512
file name : oemflag.app 88h05_01_21s168rec01.app
inet on ethernet (e) : 192.168.0.13 158.101.23.252
inet on backplane (b):
host inet (h) : 192.168.0.12 158.101.23.100
gateway inet (g) :
user (u) : 8512 Update
ftp password (pw) (blank = use rsh): 123 password
flags (f) : 0x0
target name (tn) :
startup script (s) :
other (o) :

Write flash...done!
6. The Ethernet submenu displays.
ETHERNET SUBMENU


7. Enter option 3 to download to compact flash (CF:/). The following information displays:
Attached TCP/IP interface to fei0.

Attaching network interface lo0... done.
boot device : fei

unit number : 0
host name : 8512
file name : 88h05_01_21s168rec01.app
host inet (h) : 158.101.23.100
user (u) : Update
ftp password (pw) : password
flags (f) : 0x0
Prepare for loading....OK

Loading.......................done
Initialize CF card...done
Free CF card space : 226856960 bytes

Writing CF card...............................................................
Done
8. The Ethernet submenu displays.
ETHERNET SUBMENU
9. Enter option 0 to return to the Main Menu.

10. The Main Menu displays, select option 0. The system will reboot from modified boot loader
information that was configured in Step 3.

MAIN MENU

0. Reboot

Rebooting...
ZBB_TEST
Starting...
*************************************************
* *
* *
*************************************************

CPU type : MPC755
Memory Size : 512MB

The board is steady
The MCX is present
EPLD1 testing is OK
EPLD2 testing is OK

Auto-booting...
Boot from primary file

Boot from cf:/88h05_01_21s168rec01.app
Loading from CF card...done
Decompress Image................................................................
......................................................OK!
Starting at 0x10000...
Be sure the BaudRate is 9600bps!
System is loading, please wait!
***This took a few minutes.
User interface con0 is available.

Press ENTER to get started.
Log in to the system with super-user privileges, usually user admin.
If this message is displayed:

“System is in slave status; can't respond to your command.”
Mastership on the fabrics changed over to the slave. Move the serial and Ethernet cables to the other
fabric.
Note: You must insure the upgrade of the operational OS agent code is compatible with the
existing Boot ROM program of the I/O module. Otherwise, you have to upgrade them during
fabric Application program upgrade.
3.5. Upgrading Application Software Using Xmodem

The Xmodem protocol transmits files through a serial port and supports both 128-byte and 1K-byte
packets. The Switch 8800 only supports 128-byte transfers. Xmodem also supports two types of
check; normal checksum and CRC. When there is a packet error, retransmission is supported,
normally 10 times.
The Xmodem protocol completes transmission by receiving and sending programs. The receiving
program first sends the negotiating characters to negotiate the check means. After passing the
negotiation, the sending program begins to send the packet. The receiving program checks the
packet according to the negotiated means after receiving a complete packet. The acknowledgement
characters are sent after passing the check and then the sending program continues to send the
next packet. If the check fails, negative characters are sent and the sending program sends the
packet again.
NOTE: The default console port connection is 9600 Baud, 8 Data Bits, Parity none, 1 Stop bit and
None for flow control.
To perform this procedure, you must have a serial connection to the console port on the Switch 8800
master fabric module. Windows HyperTerminal was used in the examples. It can normally be found
at Start>All Programs>Accessories>Communications>HyperTerminal. The file
88h05_01_21s168rec01.app is needed for this procedure, it is also on this same PC.
After powering on the Switch 8800, the BootROM program runs automatically. The terminal displays
the following information:
NOTE: If at BootROM code 206, the following banner will be displayed. If not at bootROM code 206
– STOP – do NOT proceed. Go to section Upgrading BootROM Code Using the Command Line
Interface. The new application code will not run with older versions of boot code.
Starting...
*************************************************
* *
* *
*************************************************


CPU type : MPC755
Memory Size : 512MB

The board is steady
The MCX is present
EPLD1 testing is OK
EPLD2 testing is OK
To access the BOOT Menu, press Ctrl+B during the 5 seconds that “Press Ctrl-B to enter Boot
Menu...” prompt displays. Within 5 seconds, the system begins program decompression. At this
time if you want to access the BOOT Menu, you must reboot the switch.
password:
Boot Menu...” prompt displays. Within 5 seconds, the system begins program decompression. At
1. The system will display the MAIN MENU if successful. Enter 4 in the Main Menu and press
Enter. Then the Serial Submenu displays:
MAIN MENU

0. Reboot
SERIAL SUBMENU
1. Download file to SDRAM through serial interface and boot

2. Download file to Flash through serial interface
3. Download file to CF card through serial interface
4. Modify serial interface boot parameter

2. Choose option 4 to change the serial interface baud rate parameter. The following
options display:
1: 9600(default)
2: 19200
3: 38400
4: 57600
5: 115200
please select an appropriate baudrate:

BaudRate is 115200 bps. Please change the terminal's speed to 115200
bps
3. Choose the highest baud rate that the application and the Switch 8800 support. In this
case both HyperTerm and the Switch 8800 support 115200 baud rate, option 5. Change
the baud rate on HyperTerminal at the configuration terminal, so that the baud rate is
consistent with the selected download baud rate of the Switch 8800. After the baud rate
setting at the configuration terminal is completed, disconnect the terminal and reconnect
it. On the HyperTerm window, click on Call>Disconnect, then click on File>Properties.
Then click on “Configure”. Change the bits to 115200, click “OK”, then click on Call>Call.
4. Return to the Switch 8800. Enter “Enter” and the following menu will appear:
1: 9600(default)
2: 19200
3: 38400

4: 57600
5: 115200
0: Return to serial submenu
please select an appropriate baudrate.

5. Select option 0 to return to the “Serial Submenu”. To start the download, select option 3.
SERIAL SUBMENU

Please Select File .

XMODEM downloading ...CCCC
While the console is at “XMODEM downloading ...”, on the PC, configure HyperTerm to send the
file:
1. Select [Transfer\Send File] from the terminal window.
2. Click Browse in the Send file dialog box, shown below and select the application you
want to download.
3. Change the protocol name for the download to Xmodem.
Figure 1 Send File dialog box
4. Click Send. The dialog box shown below will display:

Figure 2 Xmodem file send dialog box
This window will appear until the transfer is complete. The “Packet” count and “File” should
increment as the file is transferred.
After the download is complete, the system interface is shown as follows:

XMODEM downloading ...CCCC Download successfully!
If the file already exists the following prompt will appear:

cf:/88h05_01_21s168rec01.app already exist,
Delete it?(Y/N):Y
Deleting file....done
Otherwise the following will appear:

Free CF card space : 225980416 bytes
Writing CF
card...............................................................Done
5. From the serial submenu select 0 to return to the main boot menu
SERIAL SUBMENU


6. Select option 6, to display and if necessary, modify the boot loader information to boot
from the newly downloaded file.
MAIN MENU
0. Reboot
BootDev = 1
FlashFileName = 88h05_01_21s168rec01.app
CF card FileName = 88h05_01_21s168rec01.app
Modify backup boot information? Yes or No(Y/N)N
This is configured to use the newly installed software operational agent code installed on compact
flash (CF card), otherwise answer Y to the prompt “Modify backup boot information? Yes
or No(Y/N)” and configure as necessary.
7. From the Boot Menu, select option 2 to boot the newly downloaded file from flash.
MAIN MENU

0. Reboot
Rebooting….
8. Change the baud rate back to 9600 in HyperTerm. The boot process baud rate is 9600.

3.6. Upgrading Application Software Using TFTP

TFTP (Trivial File Transfer Protocol) is a simple file transfer protocol that is used without complex
interaction between clients and servers.
The client initiates a TFTP transmission. To download files, the client sends a read request packet to
the TFTP server, receives the packet from the server, and sends the acknowledgement to the
server. To upload files, the client sends a write request packet to the TFTP server, sends the data
packet to the server, and receives the acknowledgement from the server.
Switch 8800 provides the functions of the TFTP client.
FYI: There are FTP/TFTP servers on the 3Com.com website. Search for “tftp server”. The servers
are located in “3Com Software Library-Utilities for 32 bit Windows”.
Before you upgrade:
Make sure you have access to the console port (serial port- 9600 Baud, 8,1 and none) on
the master fabric.
Verify that there is a connection between the TFTP server and the Switch 8800 (use the
ping command).
Verify that the TFTP server is set up according to the manufacturer’s instructions and that it
is enabled and pointing to the correct directory. This is the directory that contains the files
that will be used for the update. The needed files are 88h05_01_20s168rec03.app,
iom05_01_08d.app and fab05_02_06d.app.
To upgrade using TFTP:
1. Verify that you are logged in with super-user privileges.
2. Verify that there are enough free records on flash: and/or compact flash on the fabric(s)
to copy the files needed. The software OS agent file 88h05_01_21s168rec01.app size is
30888988 records. The bootROM code for the fabric(s) (fab05_02_06d.app size is
326896) and I/O modules (iom05_01_08d.app size is 207696) will be placed on flash:/
on the fabric(s). For more information on the file system, see IMPORTANT NOTES: and
General Upgrade Procedure
3. Upgrade the BootROM - see section Upgrading BootROM Code Using the Command
Line Interface.
4. Identify the currently used configuration file.
5. From the Switch 8800 command line (in user view), TFTP the image file from the TFTP
server to the Switch 8800 using the following command:
tftp <TFTP Server IP Address> get <Source File/image>< Dest File-Optional>
6. Set the boot parameters to specify the file to boot the system from, using the following
command:
boot boot-loader <pri/backup> filename slot (fabric slot number) or if on a Com5 code
version – boot-loader file filename slot (fabric slot number) <main/backup>
7. Copy the software OS agent application code from the primary fabric to the backup
fabric.
8. Reboot the system. Make sure you can access the console port on the master fabric
before you reboot.
9. After the reboot, if upgrading from a V3 code version to a V5 code version, the
configuration file will need to be reconfigured using the start saved-configuration
(configuration file pathname) command. This is only necessary once. It is also not
necessary if upgrading between V5 code version. You will need access to the console

port. You will NOT be able to telnet into the Switch 8800 at this time. Then reboot the
switch again. Answer Y to the question “Current configuration will be lost in next startup
if you continue. Continue?”.
The following example illustrates this procedure using the software OS agent code filename:
88h05_01_21s168rec01.app. This procedure was done from the console port on the master
fabric. The currently running software OS agent code and configuration files have been backed
up.
NOTE: The general upgrade procedure (IMPORTANT NOTES: and General Upgrade Procedure
sections) contains more details on copying files and making sure there are enough free records
on flash: and/or compact flash (cf:), etc. See section Ensure sufficient space on the master and
slave fabric flash(es) or compact flash (cf:/) to hold the new application code (.app files). for an
example.
#######################################################################
UPGRADE THE BOOTROM AT THIS POINT –

GO TO Upgrading BootROM Code Using the Command Line Interface
#######################################################################
#######################################################################
Do a dis start, know where your configuration file is and what the
filename is. This information will be needed later in this procedure.
#######################################################################
##############################################################
If the fabric(s) is a 3C17508 fabric (360Gig), software OS
agent code has to be copied to compact flash (cf:). If the
fabric is a 3C17539 fabric (720Gig), the software OS agent
code can be copied to flash:/ (provided there are enough free
records) or cf:/. In the commands below, cf:/ is used.
###############################################################
<SW8800>tftp 10.10.110.1 get 88h05_01_21s168rec01.app cf:/88h05_01_21s168rec01.app

File will be transferred in binary mode
Downloading file from remote tftp server, please wait... /
TFTP: 30888988 bytes received in 201 second(s).
File downloaded successfully.
Copy cf:/88h05_01_21s168rec01.app to slot1#cf:/88h05_01_21s168rec01.app?[Y/N]:y
1% complete
(This took about 4-5 minutes with no other activity on the switch.)
100% complete
Copy file cf:/88h05_01_21s168rec01.app to slot1#cf:/88h05_01_21s168rec01.app...D
one.
The CLI will not respond during this operation.
Assumes 7 slot chassis – fabrics in slot 0 and 1
###########################################################
After upgrading to V5.01.21– can then set backup app file.
###########################################################

<SW8800> boot boot-loader cf:/88h05_01_21s168rec01.app slot 0

<SW8800> boot boot-loader slot1#cf:/88h05_01_21s168rec01.app slot 1
############################################################
configuration.
############################################################
Assumes 14 slot chassis – fabrics in slot 6 and 7

###########################################################
IF CURRENTLY RUNNING THE 3.01.22 or 3.01.30 Code.
###########################################################
<SW8800> boot boot-loader pri cf:/88h05_01_21s168rec01.app slot 6

<SW8800> boot boot-loader pri slot1#flash:/88h05_01_21s168rec01.app slot 7
<SW8800> boot boot-loader backup cf:/88h03_01_22rc02.app slot 6

<SW8800> boot boot-loader backup slot1#cf:/88h03_01_22rc02.app slot 7
############################################################
configuration.
############################################################
<SW8800> save
The configuration will be written to the device
Are you sure?[Y/N] y
Now saving current configuration to the device
Saving configuration flash:/sw8800/cfg Please wait …
….
Configuration is saved to flash memory successfully.
<SW8800>reboot
This command will reboot the system. Continue? [Y/N] y
###########################################################
###########################################################

NOTE: Use cf0:/ rather than cf:/ if running v5.01.21

############################################################
configuration.
############################################################
############################################################################
From the master fabrics console port, login to the switch with super-user
privileges, usually user admin. Telnet to the switch will not work at this time.

IF UPGRADING FROM A V3 CODE VERSION TO A V5 CODE VERSION - The start-up file has to
be reconfigured. The switch will be set to defaults. This only has to be done once,
after the first reboot. IF UPGRADING BETWEEN V5 CODE VERSIONS – this step is not
required.
############################################################################
<SW8800> dis start
MainBoard:
SlaveBoard:
############################################################################
The configuration file used on this switch is sw8800dc1.cfg. There is on a copy
on flash: on both the master and the slave fabric.
############################################################################
<SW8800>dir
0 -rw- 326680 Nov 13 2007 18:41:36 fab03_02_03d.app

1 drw- - Jan 01 2003 00:00:24 hafile
2 -rw- 4 Jan 21 2006 04:18:37 snmpboots
6 -rw- 118 Sep 20 2006 21:18:12 ls.pwd
7 -rw- 207696 Nov 13 2007 18:41:56 iom03_01_08d.app
8 -rw- 272898 Nov 13 2007 18:42:19 iop03_02_05d.app
9 -rw- 3950 Nov 14 2007 10:27:35 sw8800dc1.cfg
10 -rw- 326896 Nov 13 2007 19:35:36 fab05_02_06d.app
11 -rw- 207696 Nov 13 2007 19:36:03 iom05_01_08d.app
12 -rw- 273034 Nov 13 2007 19:36:16 iop05_02_06d.app
############################################################################
Configure the switch to use the desired configuration file. Notice that the
configuration file was set on both the master and slave fabric.
Your filename will be different.
############################################################################

Please wait ...
############################################################################
############################################################################
<SW8800>dis start
MainBoard:
SlaveBoard:
############################################################################
Reboot the switch. Answer Y to the question “Current configuration will be
lost in next startup if you continue. Continue?”.
############################################################################
<SW8800>reb
Start to check configuration with next startup configuration file, please wait
......
This command will reboot the device. Current configuration will be lost in
next startup if you continue. Continue? [Y/N]:y

3.7. Upgrading BootROM Code Using the Command Line Interface
3Com recommends that you upgrade the BootROM code in parallel with the operational code. The
new application code will NOT run with older versions of boot code.
The latest BootROM code in the 5.01.21 release is version 206 (fab05_02_06d.app) for the fabric
and version 108 (iom05_01_08.app) for the I/O modules.
If the I/O modules are currently running bootROM code version V103 or earlier, you cannot upgrade
directly to V108 bootROM code. You must upgrade to V107 bootROM code first and then after the
Switch 8800 is rebooted the I/O modules can be upgraded to V108 (iom03_01_08.app). If you try to
upgrade from bootROM code V103 or earlier directly to V108, the system will prompt that the
upgrade file is not compatible and the upgrade will fail. V107 bootRom code is included with the
5.01.21 release bundle in the event that you need to upgrade to this version of bootRom code first.
The V107 bootROM code is named 8800boot-module1107.app.
Except as noted below – until the full application upgrade has been completed as described in the
sections above - it is NOT required to reboot the device. You can set the new boot code and the
new OS application agent code simultaneously –then reboot and the device will come up with the
new application/boot code combination.
Use the following procedure to upgrade boot code on each switch fabric and I/O module. The slot
number for the switch fabric depends on the chassis. Please download fabric bootROM file
fab05_02_06d.app to both master and slave switch fabrics.
1. Login to the switch with super-user privileges, usually user admin.
2. If not already backed up, save the configuration file and currently running software OS
agent code by uploading it to a temporary server. Use the command display start to
display the currently used configuration file. Use the display boot to display the
currently used primary software OS agent code. Make a note of these files.
Use one of the download procedures in these Release Notes.
3. Check the current bootROM versions to see which fabric(s) and I/O modules are going to
need to be updated, use the _display version command.
4. Check to see if there are enough free records in the flash:/ file system on the fabrics to
download the bootROM app files. The bootROM code for the fabrics (fab05_02_06d.app
size is 326896) and I/O modules (iom05_01_08d.app size is 207696) will be placed on
flash:/ on both fabrics. IMPORTANT NOTES:and General Upgrade Procedure provides
more details on the commands needed to examine the file system and remove files. An
example of examining the file system can be found at Ensure sufficient space on the master
and slave fabric flash(es) or compact flash (cf:/) to hold the new application code (.app files).
Using one of the download procedures in these Release Notes:
5. Download the latest bootROM app files (fab05_02_06d.app and iom05_01_08d.app) to

the master fabric.
6. Download the fab05_02_06d.app bootROM app file to the slave fabric or copy the file
from the master fabric to the slave fabric.
7. Update the bootROM code using the following commands:

Example, if running rev 3.x.x:

<SW8800>boot bootrom fab05_02_06d.app slot 6
If running rev 5.x.x:

<SW8800>bootrom update file flash:/fab05_02_06d.app slot 6
3.7.1. Example of Updating the bootROM code on the fabric(s) and I/O modules.
Below is an example of the above procedure using an FTP server and a 10-slot Switch 8800 with
dual fabrics installed in slots 4 and 5. The Switch 8800 has an IP address of 158.101.23.252/24. The
FTP servers address is 158.101.23.100/24. The file system has already been checked for available
free records.
Check the current bootROM versions to see which modules are going to need to be updated, use
the _dis ver command. In the example below both Fabrics in slot 4 and 5, are running BootROM
Version 203- rev 206 is the current rev. The I/O modules in slot 0 and 2 need to be updated from
BootROM Version 107 to Version 108.
<SW8800> _dis ver

3Com Corporation
3Com OS Software Version COMWAREHZV300R001B09D021SP06
Switch 8800 Software Version V100R003B02D021SP06
Switch 8800 V3.01.30s512rec06
Copyright(c) 2004-2006 3Com Corporation and its licensors. All rights

reserved.
Compiled Dec 30 2006 01:15:08, RELEASE SOFTWARE
Switch 8800 uptime is 0 week, 0 day, 0 hour, 34 minutes
3C17508 4: uptime is 0 week,0 day,0 hour,34 minutes

Switch 8800 with 1 MPC755 Processor
512M bytes SDRAM
16384K bytes Flash Memory
512K bytes NVRAM Memory
PCB Version : Ver.B
BootROM Version : 203
CPLD Version : 000
Software Version : 3.01.30s512re

512M bytes SDRAM
PCB Version : Ver.B
CPLD Version : 002

Switch 8800 LPU with 1 MPC8245 Processor

128M bytes SDRAM

PCB Version : Ver.B
CPLD Version : 002
CPUCard 1
PCB Ver : REV.0
CPLD Ver : 001

128M bytes SDRAM
PCB Version : Ver.B
CPLD Version : 002
CPUCard 1
PCB Ver : REV.0
CPLD Ver : 001

128M bytes SDRAM
PCB Version : REV.0
CPLD Version : 002
CPUCard 1
PCB Ver : REV.0
CPLD Ver : 001

256M bytes SDRAM
PCB Version : Ver.E
CPLD Version : 004
CPUCard 1
PCB Ver : Ver.C
CPLD Ver : 001
Verify connectivity to the FTP server, use ping. Backup the configuration file and the currently
running software OS agent app file. Then download the bootROM files to the master and slave
fabrics.
[SW8800] ping 158.101.23.100

PING 158.101.23.100: 56 data bytes, press CTRL_C to break
Reply from 158.101.23.100: bytes=56 Sequence=1 ttl=128 time=1 ms


--- 158.101.23.100 ping statistics ---

5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 1/1/1 ms
*enter a “ctrl-z” to get back to the user view.
<SW8800>ftp 158.101.23.100
Trying ...
Connected.
220 3Com FTP Server Version 1.1
User(none):Update (User id created on the FTP server)
Password: (enter the password, it will not be echo’ed)
230 User logged in
[ftp]ls
200 PORT command successful.
150 File status OK ; about to open data connection
.
..
88h05_01_20s168rec03.app
88h05_01_20s168rec03.zip
fab05_02_06d.app
iom05_01_08d.app
iop05_02_06d.app
226 Closing data connection
FTP: 364 byte(s) received in 0.485 second(s) 750.00byte(s)/sec.
[ftp]bin
200 Type set to I.
[ftp]put sw8800dc1.cfg <<This is the configuration file being copied

to the FTP server. The dis start command displays the current
configuration file being used. Your filename will be different.
150 Opening BINARY mode data connection for sw8800dc1.cfg.
226 File transfer successful
FTP: 3950 byte(s) sent in 0.702 second(s), 5.00Kbyte(s)/sec.
[ftp]put cf:/88h03_01_30s512rec06.app <<Example - This is the currently

running software OS file. This is the current primary file used for the
boot. The dis boot command displays the software OS agent files used
during a bootup. If there is not a backup of this file, now is the time to
do so. Your filename maybe different.

[ftp]get fab05_02_06d.app <<Copy the new bootROM code app files to the
master fabric.
\|/226 File transfer successful.
[ftp]get iom05_01_08d.app
[ftp]get fab05_02_06d.app slot5#flash:/fab05_02_06d.app <<Copy the new

bootROM code app files to the slave fabric.
[ftp]get iom05_01_08d.app slot5#flash:/iom05_01_08d.app <<This is

optional, the I/O module bootROM code can be updated from the master
fabric. This is done just in case something should happen to the master
fabric.
[ftp]bye
Next, update the bootROM of the modules that are not up to date.

This will update BootRom file on board 4 . Continue? [Y/N] y
Board 4 upgrading BOOTROM, please wait...
Upgrade board 4 BOOTROM succeeded!
<SW8800>boot bootrom slot5#flash:/fab05_02_06d.app slot 5
<SW8800>boot bootrom iom05_01_08d.app slot 0

Frame 0 IO Board 0 upgrade BOOTROM succeeded!

Frame 0 IO Board 2 upgrade BOOTROM succeeded
If you can not get the new bootROM code loaded on the fabrics, stop now,
and call customer service support if you can not resolve the problem. Do not
proceed any further until the new bootROM code has loaded successfully on
the fabrics.

3.8. Upgrading the BootROM Code On the Fabric Using the Boot
Menu
This procedure would most likely be used only if the Command Line Interface, User and System
Views can not be accessed. This could occur if the new software OS agent code
(88h05_01_21s168rec01.app) was loaded and the switch was rebooted without updating the
BootROM code on the fabric.
To perform this procedure, you must have a network connection to the Ethernet port on the Switch
8800 master fabric module. This procedure is done from the console port on the master fabric. A
FTP or tftp server can be used. The file needed is fab05_02_06d.app, it is in the upload/download
directory of the FTP/tftp server.
After powering on the Switch 8800 or after a reboot of the Switch 8800, the BootROM program runs
automatically.
NOTE: The new application code will not run with older versions of boot code.
Starting...
*************************************************
* *
* Switch 8800 Bootrom, Version XXX *
* *
*************************************************
Copyright (c) 2004-200X 3Com Corporation and its licensors.

CPU type : MPC755
Memory Size : 512MB

The board is steady
The MCX is present
EPLD1 testing is OK
EPLD2 testing is OK
Boot Menu...” prompt displays. After the 5 seconds, the system begins program decompression. At
password:

1. Enter the BootROM password. After entering the correct password (no
password is set for the switch by default), the system will access the MAIN
MENU. The MAIN MENU will probably look like one of the following formats.
Pick the option “Enter ethernet submenu”, option 5 in both the menu’s below.
MAIN MENU MAIN MENU
1. Boot with default mode 1. Boot with default mode

2. Boot from primary file 2. Boot from Flash
3. Boot from backup file 3. Boot from CF card
4. Enter serial submenu 4. Enter serial submenu
5. Enter ethernet submenu 5. Enter ethernet submenu
6. Modify Flash description area 6. Modify Flash description area
7. Modify bootrom password 7. Modify bootrom password
0. Reboot 0. Reboot
Enter your choice(0-7): 5 Enter your choice(0-7): 5
2. The bootROM code file to be transferred has to be configured. In the example

below, the fabrics new bootROM code filename is fab05_02_06d.app, the IP
address on the fabrics Ethernet port is 158.101.23.252, the IP address of the FTP
server is 158.101.23.100. The FTP user id is Update, the password is password.
FTP is going to be used to transfer the bootROM code file. The FTP server and the
Switch 8800 are on the same IP network, so a gateway was not needed. Tftp could
also be used, flags (f) would need to modified to 0x80. User input is bold.
ETHERNET SUBMENU


Note: Two protocols for download, tftp & ftp.

You can modify the flags following the menu.
tftp--0x80, ftp--0x0.
boot device : fei

unit number : 0
host name : 8512
file name : 88h03_01_30s512rec06.app
host inet (h) : 158.101.185.47
user (u) : John
ftp password (pw) : john
flags (f) : 0x0

'.' = clear field; '-' = go to previous field; ^D = quit
boot device : fei0

host name : 8512
file name : 88h03_01_30s512rec06.app fab05_02_06d.app
inet on ethernet (e) : 158.101.185.98 158.101.23.252
inet on backplane (b):
host inet (h) : 158.101.185.47 158.101.23.100
gateway inet (g) :
user (u) : John Update
ftp password (pw) (blank = use rsh): john password
flags (f) : 0x0
target name (tn) :
startup script (s) :
other (o) :
Write flash...done!
3. Transfer the file from the FTP server to the Switch 8800’s flash. Select option 2.
ETHERNET SUBMENU


boot device : fei

unit number : 0
host name : 8512
file name : fab05_02_06d.app
host inet (h) : 158.101.23.100
user (u) : Update
ftp password (pw) : password
flags (f) : 0x0
Prepare for loading....OK
Loading...done
Flash file system init...done
Free flash Space : 15365120 bytes
Writing Flash.......................Done
4. To install the new bootROM code on the master fabric, return to the Main Menu,
option 0 at the Ethernet Submenu, then enter a ctrl-u at the Main Menu, next select
the file number of the file fab05_02_06d.app. Enter Y, to confirm.

ETHERNET SUBMENU


MAIN MENU

0. Reboot
Enter your choice(0-7): (enter a ctrl-u)

No. File Size Date Time File Name
=========================================================
1. 4 2005-07-09 18:29:15 snmpboots
2. 6086 2005-07-29 17:50:31 fw_vrrp_2chassis_old.cfg
3. 3236 2005-08-03 18:54:47 ipsec.cfg
4. 4477 2007-06-18 15:19:07 private-data.txt
5. 326680 2005-07-09 18:34:23 fab03_02_03d.app
6. 5344 2005-07-26 12:33:30 sw800_old.cfg
7. 3691 2007-06-18 10:34:15 sw8800dc1.cfg
8. 3236 2007-06-13 12:43:42 sw8800dc1bac.cfg
9. 46 2007-06-13 19:00:16 ls.pwd
10. 326896 2007-06-18 15:32:13 fab05_02_06d.app
11. 207696 2007-06-13 19:40:55 iom05_01_08d.app
12. 3803 2007-06-14 10:01:45 sw8800dc1backup.cfg
The default boot file have not been selected.
Free Space : 15037440 bytes

Please input the file number to update bootrom: 10

The file you select is fab05_02_06d.app
Update bootrom(only main system)? Yes or No(Y/N)y
Update Bootrom..........................done
5. If you desire to bring the Switch 8800 up, examine the boot-loader configuration and
change it if necessary, ”Modify Flash description area”. In the example below the
software OS agent file 88h05_01_21s168rec01.app is loaded on the CF:/.
MAIN MENU

0. Reboot

BootDev = 1
FlashFileName = 88h05_01_20s168rec03.app
CF card FileName = 88h03_01_30s512rec06.app 88h05_01_21s168rec01.app

The file name you input is 88h05_01_21s168rec01.app,
are you sure? Yes or No(Y/N)y
Writing main boot information...done
Change backup boot information? Yes or No(Y/N)n
6. Depending on the MAIN MENU, choose either option 2 or 3.
MAIN MENU MAIN MENU
1. Boot with default mode 1. Boot with default mode

2. Boot from primary file 2. Boot from Flash
3. Boot from backup file 3. Boot from CF card
4. Enter serial submenu 4. Enter serial submenu
5. Enter ethernet submenu 5. Enter ethernet submenu
6. Modify Flash description area 6. Modify Flash description area
7. Modify bootrom password 7. Modify bootrom password
0. Reboot 0. Reboot
Enter your choice(0-7): 2 Enter your choice(0-7): 3



Booting from CF card

Decompress
Image..................................................................
......................................................................O
K!
Starting at 0x10000......
Login to the switch with super-user privileges, usually user admin. To verify that the new
bootROM code is installed, use the command display version.
<SW8800>
%Jun 19 11:12:15:15 2007 SW8800 SHELL/4/LOGIN: Console login from con0
<SW8800>dis ver
3Com Corporation
Switch 8800 Software Version 5.01
Copyright (c) 2004-2007 3Com Corporation and its licensors. All rights
reserved.
Switch 8800 uptime is 0 week, 0 day, 0 hour, 0 minute
3C17508 5: uptime is 0 weeks,0 days,0 hours,0 minutes

512M bytes SDRAM
PCB Version : Ver.B
CPLD Version : 002
Software Version : 5.01.21s168rec01

3.9. Software Update Example
In the example below a 10-slot Switch 8800, with dual fabrics is updated from rev 3.01.30 to rev
5.01.21. FTP is used to transfer the files. The files required for the update have been loaded on
the FTP server. The files needed are 88h05_01_21s168rec01.app, fab05_02_06d.app and
iom05_01_08d.app. If you have only 88h05_01_21s168rec01.zip, extract this file to get the afore
mentioned files.
The update was done from the console port on the master fabric. The default settings are 9600
Baud, 8 data bits, 1 stop bit and parity is None.
3.9.1. Identify the configuration file and the currently running operational OS agent file.
Check to see what files are being used for the bootup process and what is the configuration file.
These files need to be backed up. The backup of the configuration file and the primary software
OS file will be backed up using FTP later in the procedure.
<SW8800>dis boot
The primary app to boot of board 4 at the next time is:
cf:/88h03_01_30s512rec06.app
The backup app to boot of board 4 at the next time is: flash:/8500.app
The app to boot of board 4 at this time is:
cf:/88h03_01_30s512rec06.app
cf:/88h03_01_30s512rec06.app
The backup app to boot of board 5 at the next time is:
cf:/88h03_01_30s512rec06.app
<SW8800>dis start
MainBoard:
SlaveBoard:
3.9.2. Identify the bootROM versions and which modules will need the bootROM code to be
updated.
To check the current bootROM versions use the _dis ver command. Both Fabrics in slot 4 and 5
are running BootROM Version 203- rev 206 is the current rev. The I/O modules in slot 0 and 2
need to be updated from BootROM Version 107 to Version 108.
<SW8800> _dis ver

3Com Corporation
3Com OS Software Version COMWAREHZV300R001B09D021SP06

Switch 8800 V3.01.30s512rec06
Copyright(c) 2004-2006 3Com Corporation and its licensors. All rights

reserved.
Compiled Dec 30 2006 01:15:08, RELEASE SOFTWARE

512M bytes SDRAM
PCB Version : Ver.B
CPLD Version : 000

512M bytes SDRAM
PCB Version : Ver.B
CPLD Version : 002

128M bytes SDRAM
PCB Version : Ver.B
CPLD Version : 002
CPUCard 1
PCB Ver : REV.0
CPLD Ver : 001

128M bytes SDRAM
PCB Version : Ver.B
CPLD Version : 002
CPUCard 1
PCB Ver : REV.0
CPLD Ver : 001

128M bytes SDRAM
PCB Version : REV.0

CPLD Version : 002

CPUCard 1
PCB Ver : REV.0
CPLD Ver : 001

256M bytes SDRAM
PCB Version : Ver.E
CPLD Version : 004
CPUCard 1
PCB Ver : Ver.C
CPLD Ver : 001
3.9.3. Ensure sufficient space on the master and slave fabric flash(es) and/or compact
flash (cf:/) to hold the new application code (.app files).
Check to see if there are enough free records in the file system on the fabrics. Both flash: and cf:
need to be checked. The fabric in this procedure is a 3C17508 360G, the new software OS code
for rev 5 and later has to be placed on cf: on both fabrics. There is not enough free records on the
flash:/ of the fabric 3C17508 for rev 5.X and later. The software OS file
88h05_01_21s168rec01.app size is 30888988 records. The bootROM code for the fabrics
(fab05_02_06d.app size is 326896) and I/O modules (iom05_01_08d.app size is 207696) will be
placed on flash:/ on both fabrics.
<SW8800>dir flash:/
0 -rw- 326680 Nov 13 2007 18:41:36 fab03_02_03d.app

1 drw- - Jan 01 2003 00:00:24 hafile
2 -rw- 4 Jan 21 2006 04:18:37 snmpboots
6 -rw- 118 Sep 20 2006 21:18:12 ls.pwd
7 -rw- 207696 Nov 13 2007 18:41:56 iom03_01_08d.app
8 -rw- 272898 Nov 13 2007 18:42:19 iop03_02_05d.app
9 -rw- 3803 Nov 13 2007 18:47:26 sw8800dc1.cfg
<SW8800>dir cf:
Directory of cf:/
0 drw- - Nov 13 2007 17:49:28 logfile

1 -rw- 6883625 Feb 24 2007 01:39:46 88h03_01_02s56rec17.app
2 -rw- 21746694 Nov 13 2007 18:39:28 88h03_01_30s512rec06.app

<SW8800>dir slot5#flash:/
Directory of slot5#flash:/
0 drw- - May 28 2003 06:29:05 hafile

1 -rw- 4 Jul 09 2005 18:29:15 snmpboots
2 -rw- 6086 Jul 29 2005 17:50:31 fw_vrrp_2chassis_old.cfg
3 -rw- 3236 Aug 03 2005 18:54:47 ipsec.cfg
4 -rw- 326680 Jul 09 2005 18:34:23 fab03_02_03d.app
5 -rw- 5344 Jul 26 2005 12:33:30 sw800_old.cfg
6 -rw- 3803 Nov 13 2007 17:32:18 sw8800dc1.cfg
7 -rw- 3236 Nov 13 2007 12:43:42 sw8800dc1bac.cfg
8 -rw- 46 Nov 13 2007 19:00:16 ls.pwd
<SW8800>dir slot5#cf:/
Directory of slot5#cf:/
0 -rw- 326680 Mar 02 2007 04:36:04 fab03_02_03d.app

1 drw- - Feb 26 2007 10:38:56 logfile
2 -rw- 5713 Jul 27 2005 17:49:08 fw_vrrp_2chassis.cfg
3 -rw- 524392 Dec 21 2005 15:49:46 lsblmcua01107.app
4 -rw- 6604 Feb 19 2007 23:28:20 poe_nbx_vcx_old.cfg
5 -rw- 207696 Mar 02 2007 04:34:54 iom03_01_08d.app
6 -rw- 272898 Mar 02 2007 04:35:26 iopm03_02_05d.app
7 -rw- 4627 Mar 02 2007 04:37:30 nmm.cfg
8 -rw- 11418 Mar 02 2007 04:38:24 congruent.cfg
9 -rw- 4713 Mar 02 2007 04:39:46 option82.cfg
10 -rw- 6656 Mar 02 2007 04:40:00 nmmv8.cfg
11 -rw- 6679 Mar 02 2007 04:40:30 nmmv5test.cfg
13 -rw- 268256 Dec 01 2006 23:32:52 fab03_01_23d.app
14 -rw- 21746694 Feb 14 2007 06:07:22 88h03_01_30s512rec06.app
There are enough free records to proceed with the update. If there where not enough free
records, first try to reset recycle-bin to see if free records could be recovered easily. Next, files
would have to be deleted (use the command delete /unreserved (filename)). I would start with
oldest software OS file (.app) and old bootROM files after they where backed up to an FTP or tftp
server.
3.9.4. Configure an IP address on Ethernet port on the fabric.
The files can be transferred to the Switch 8800 in many ways, FTP, tftp, boot menu and xmodem
(very slow). Below they will be transferred using FTP thru the use of the out of band Ethernet port
on the fabric. An in-band Ethernet port on an I/O module could also be used. Below the IP
address 158.101.23.252/24 is configured on the fabrics Ethernet port. The IP network is the same
as the IP network that the FTP server 158.101.23.100/24 is connected too, so a gateway is not
needed.

<SW8800>sys
System View: return to User View with Ctrl+Z.
[SW8800]int m-e
[SW8800]int M-Ethernet 4/0/0
[SW8800-M-Ethernet4/0/0]ip add 158.101.23.252 24
[SW8800-M-Ethernet4/0/0]
%Jun 13 19:30:41 2007 SW8800 L2INF/5/VLANIF LINK STATUS CHANGE:
M-Ethernet4/0/0: is UP
%Jun 13 19:30:41 2007 SW8800 IFNET/5/UPDOWN:

Line protocol on the interface M-Ethernet4/0/0 is UP
Check the connectivity to the FTP server, try pinging, might have to be done twice.
[SW8800-M-Ethernet4/0/0]ping 158.101.23.100
Request time out
Request time out
Request time out
Request time out
Request time out
--- 158.101.23.100 ping statistics ---

100.00% packet loss
[SW8800-M-Ethernet4/0/0]ping 158.101.23.100
--- 158.101.23.100 ping statistics ---

0.00% packet loss
round-trip min/avg/max = 1/1/1 ms
[SW8800-M-Ethernet4/0/0]q
3.9.5. Backing up the configuration file and the operational OS agent. Transferring the
new .app files to the Switch 8800 using FTP.
The new bootROM code and software OS agent code will be transferred to both the master and
slave fabrics using FTP and the copy command. The configuration file and the currently running
operational OS agent will also be backed up to the FTP server. The working (or upload/download)
directory on the FTP server is the directory where the new software OS agent file and bootROM
files reside.
[SW8800]
*enter a “ctrl-z” to get back to the user view.

<SW8800>ftp 158.101.23.100
Trying ...
Connected.
220 3Com FTP Server Version 1.1
User(none):Update (User id created on the FTP server)
Password: (enter the password, it will not be echo’ed)
230 User logged in
[ftp]ls
.
..
88h05_01_21s168rec01.app
88h05_01_21s168rec01.zip
fab05_02_06d.app
iom05_01_08d.app
iop05_02_06d.app
226 Closing data connection
FTP: 364 byte(s) received in 0.485 second(s) 750.00byte(s)/sec.
[ftp]bin
200 Type set to I.
[ftp]put sw8800dc1.cfg <<This is the configuration file being copied

to the FTP server. Your filename will be different.
150 Opening BINARY mode data connection for sw8800dc1.cfg.
[ftp]put cf:/88h03_01_30s512rec06.app <<This is the currently running

software OS file. This is the current primary file used for the boot.
The dis boot command displays the software OS files used during a
bootup. Your filename will maybe different.

[ftp]get fab05_02_06d.app
[ftp]get iom05_01_08d.app


[ftp]get fab05_02_06d.app slot5#flash:/fab05_02_06d.app

[ftp]get iom05_01_08d.app slot5#flash:/iom05_01_08d.app

[ftp]get 88h05_01_21s168rec01.app cf:/88h05_01_21s168rec01.app

FTP: 30888988 byte(s)received in 70.34 second(s) 439.00K byte(s)/sec.
[ftp]bye
Print out a copy of the configuration file. There maybe a need for this later after rev 5.01.20 is up
and running.
3.9.6. How to copy a file from one fabric to another fabric
The slave fabric cf: still does not have 88h05_01_20s168rec03.app file. This can be copied to
slot5#cf:/ using FTP again or copy from the Primary fabric cf: to the slave cf:. Below is the copy
from the master fabric cf: to the slave fabric CF:.
*Use ? to see the next options or arguments to a command.
<SW8800>copy cf:/88h05_01_21s168rec01.app ?
STRING<1-64> [drive][path][file name]
cf:/ Device name
flash:/ Device name
slot5#cf:/ Device name
slot5#flash:/ Device name

Copy cf:/88h05_01_21s168rec01.app to
slot5#cf:/88h05_01_21s168rec01.app?[Y/N]:y
1% complete
(This took about 4-5 minutes with no other activity on the switch.)
100% complete
Copy file cf:/88h05_01_21s168rec01.app to
slot5#cf:/88h05_01_21s168rec01.app...Done.
Make a quick check of the file system to make sure all the files are present.

<SW8800>dir flash:
0 -rw- 326680 Nov 13 2007 18:41:36 fab03_02_03d.app

1 drw- - Jan 01 2003 00:00:24 hafile
2 -rw- 4 Jan 21 2006 04:18:37 snmpboots
6 -rw- 118 Sep 20 2006 21:18:12 ls.pwd
7 -rw- 207696 Nov 13 2007 18:41:56 iom03_01_08d.app
8 -rw- 272898 Nov 13 2007 18:42:19 iop03_02_05d.app
9 -rw- 3803 Nov 13 2007 18:47:26 sw8800dc1.cfg
10 -rw- 326896 Nov 13 2007 19:35:36 fab05_02_06d.app
11 -rw- 207696 Nov 13 2007 19:36:03 iom05_01_08d.app
12 -rw- 273034 Nov 13 2007 19:36:16 iop05_02_06d.app
<SW8800>dir cf:
Directory of cf:/
0 drw- - Nov 13 2007 17:49:28 logfile

1 -rw- 6883625 Feb 24 2007 01:39:46 88h03_01_02s56rec17.app
2 -rw- 21746694 Nov 13 2007 18:39:28 88h03_01_30s512rec06.app
3 -rw- 30706779 Nov 13 2007 19:42:50 88h05_01_21s168rec01.app
<SW8800>dir slot5#cf flash:

Directory of slot5#flash:/
0 drw- - May 28 2003 06:29:05 hafile

1 -rw- 4 Jul 09 2005 18:29:15 snmpboots
2 -rw- 6086 Jul 29 2005 17:50:31 fw_vrrp_2chassis_old.cfg
3 -rw- 3236 Aug 03 2005 18:54:47 ipsec.cfg
4 -rw- 326680 Jul 09 2005 18:34:23 fab03_02_03d.app
5 -rw- 5344 Jul 26 2005 12:33:30 sw800_old.cfg
6 -rw- 3803 Nov 13 2007 17:32:18 sw8800dc1.cfg
8 -rw- 46 Nov 13 2007 19:00:16 ls.pwd
9 -rw- 326896 Nov 13 2007 19:38:22 fab05_02_06d.app
10 -rw- 207696 Nov 13 2007 19:40:55 iom05_01_08d.app
<SW8800>dir slot5#cf:
Directory of slot5#cf:/
0 -rw- 326680 Mar 02 2007 04:36:04 fab03_02_03d.app

1 drw- - Feb 26 2007 10:38:56 logfile
2 -rw- 5713 Jul 27 2005 17:49:08 fw_vrrp_2chassis.cfg

3 -rw- 524392 Dec 21 2005 15:49:46 lsblmcua01107.app

4 -rw- 6604 Feb 19 2007 23:28:20 poe_nbx_vcx_old.cfg
5 -rw- 207696 Mar 02 2007 04:34:54 iom03_01_08d.app
6 -rw- 272898 Mar 02 2007 04:35:26 iopm03_02_05d.app
7 -rw- 4627 Mar 02 2007 04:37:30 nmm.cfg
8 -rw- 11418 Mar 02 2007 04:38:24 congruent.cfg
9 -rw- 4713 Mar 02 2007 04:39:46 option82.cfg
10 -rw- 6656 Mar 02 2007 04:40:00 nmmv8.cfg
11 -rw- 6679 Mar 02 2007 04:40:30 nmmv5test.cfg
13 -rw- 30888988 Nov 13 2007 19:51:34 88h05_01_21s168rec01.app
14 -rw- 268256 Dec 01 2006 23:32:52 fab03_01_23d.app
15 -rw- 21746694 Feb 14 2007 06:07:22 88h03_01_30s512rec06.app
3.9.7. Backing up the current configuration file to the Switch 8800 file system
Make sure there are plenty of copies of the current configuration file. When going from rev 3.x to
rev 5.x some commands have changed and some configuration after the update is probably
going to be necessary.
The configuration file is copied to flash: and cf: on both fabrics.
<SW8800>copy flash:/sw8800dc1.cfg flash:/sw8800dc1Backup.cfg

Copy flash:/sw8800dc1.cfg to flash:/sw8800dc1backup.cfg?[Y/N]:y
100% complete
Copy file flash:/sw8800dc1.cfg to flash:/sw8800dc1backup.cfg...Done.
<SW8800>copy flash:/sw8800dc1.cfg cf:/sw8800dc1Backup.cfg
Copy flash:/sw8800dc1.cfg to cf:/sw8800dc1backup.cfg?[Y/N]:y
100% complete
Copy file flash:/sw8800dc1.cfg to cf:/sw8800dc1backup.cfg...Done.
<SW8800>copy flash:/sw8800dc1.cfg slot5#flash:/sw8800dc1Backup.cfg
Copy flash:/sw8800dc1.cfg to slot5#flash:/sw8800dc1backup.cfg?[Y/N]:y
100% complete
Copy file flash:/sw8800dc1.cfg to
slot5#flash:/sw8800dc1backup.cfg...Done.
<SW8800>copy flash:/sw8800dc1.cfg slot5#cf:/sw8800dc1Backup.cfg
Copy flash:/sw8800dc1.cfg to slot5#cf:/sw8800dc1backup.cfg?[Y/N]:y
100% complete
Copy file flash:/sw8800dc1.cfg to slot5#cf:/sw8800dc1backup.cfg...Done.
Backups have been done and all the files are in place. The fabric is a 3C17508 360G, the new
software OS agent code rev 5.01.20 (88h05_01_20s168rec03.app) is on the cf: of both fabrics.
The bootROM code for the fabrics (fab05_02_06d.app) and I/O modules (iom05_01_08d.app)
have been placed on the flash:/ of both fabrics. Having the bootROM code for I/O modules on the
slave fabric is optional.
3.9.8. Updating the bootROM code on the Fabrics and I/O modules.

Update the fabrics and the I/O modules using the boot bootROM command.

<SW8800>boot bootrom slot5#flash:/fab05_02_06d.app slot 5

Frame 0 IO Board 0 upgrade BOOTROM succeeded!

Frame 0 IO Board 2 upgrade BOOTROM succeeded
If you can not get the new bootROM code loaded on the fabrics, stop now,
and call customer service support if you can not resolve the problem. Do
not proceed any further until the new bootROM code has loaded
successfully on the fabrics.
3.9.9. Configuring the boot loader to boot from the new software OS agent code
Next, configure the fabrics to boot up using the newly installed software OS agent file for rev
5.1.21.
<SW8800>boot boot-loader pri cf:/88h05_01_21s168rec01.app slot 4

Notice: Please check the current bootrom version, if it doesn't match
the new host software, please upgrade the bootrom version before
reboot!
We’re good. The new bootROM code has already been updated on both fabrics.
<SW8800>boot boot-loader pri slot5#cf:/88h05_01_21s168rec01.app slot 5

Notice: Please check the current bootrom version, if it doesn't match
the new host software, please upgrade the bootrom version before
reboot!
Use the dis boot command to verify the boot loader configuration changes that were just made.
The master and slave fabric should both being using the new software OS file
88h05_01_21s168rec01.app as the primary app.

<SW8800>dis boot
cf:/88h05_01_21s168rec01.app
The backup app to boot of board 4 at the next time is: flash:/8500.app
cf:/88h03_01_30s512rec06.app
cf:/88h05_01_21s168rec01.app
cf:/88h03_01_30s512rec06.app
cf:/88h03_01_30s512rec06.app
Next, the boot loader is configured for backup software OS agent file. This is used if the primary
file can not be loaded for some reason. I like to use “is currently running fine” OS. FYI: If there is
a need to go back to the older release, you may have to use one of the backup’ed configuration
files. The reason for this is that some of the commands may have changed from rev 3.X to 5.X.
Note: The application name below may vary, use your file.
<SW8800>boot boot-loader backup cf:/88h03_01_30s512rec06.app slot 4

Set backup boot file successfully!
<SW8800>boot boot-loader backup slot5#cf:/88h03_01_30s512rec06.app s 5
Set backup boot file successfully!
<SW8800>dis boot
cf:/88h05_01_21s168rec01.app
cf:/88h03_01_30s512rec06.app
cf:/88h03_01_30s512rec06.app
cf:/88h05_01_21s168rec01.app
cf:/88h03_01_30s512rec06.app
cf:/88h03_01_30s512rec06.app
<SW8800>dis start
MainBoard:
SlaveBoard:
3.9.10. Rebooting the Switch 8800 with the new code
The switch will have to be rebooted in order for the new software OS agent 5.01.21 (file
88h05_01_21s168rec01.app) to be loaded.
<SW8800>reboot
This command will reboot the system. Continue? [Y/N] y

ZBB_TEST
Starting...
*************************************************
* *
* *
*************************************************

CPU type : MPC755
Memory Size : 512MB

The board is steady
The MCX is present
EPLD1 testing is OK
EPLD2 testing is OK
The switch's Mac address is 0020.9c69.bad1
Press Ctrl+B to enter Boot Menu...

Auto-booting...

Boot from cf:/88h05_01_21s168rec01.app <<the NEW CODE, Yahoo!!
Decompress
Image................................................................
.......................................................................
.......................................................................
......................................................OK!
Startup configuration file does not exist.

Please note the message above. The configuration file will need to be configured after the
switch is up and running. The switch will require another reboot. This will have to be done from
the master fabrics console port.
Login into the switch, with all configuration privileges, usually user admin. This will have to be
done from the master fabrics console port. The default settings are 9600 Baud, 8 data bits, 1 stop
bit and parity is none. Telnet access to the Switch 8800 will not work at this point.
Make sure the master and slave fabrics are synchronized. The fabrics below are synchronized.
Fabrics are NOT synchronized, if the command dis switchover state returns the message “HA
FSM State(master): Waiting batch backup request from slave.”
<SW8800>dis switchover sta

3.9.11. Verify that the software OS is 5.01.21 and the bootROM version is up to date on all
the modules.
Verify that the software OS is 5.01.21 and the bootROM version is up to date on all the modules.
If the fabrics bootROM code were not up to date, we would know before now. We would not have
gotten this far and would have to try recovering the switch thru the boot menu. See section
Upgrading the BootROM Code On the Fabric Using the Boot Menu
<SW8800>_dis ver
3Com Corporation
3Com OS Software Version COMWAREV500R002B28D016SP02
Copyright (c) 2004-2007 3Com Corporation and its licensors. All rights
reserved.
Compiled Oct 15 2007 19:15:45, RELEASE SOFTWARE

512M bytes SDRAM
PCB Version : Ver.B
CPLD Version : 000

512M bytes SDRAM


PCB Version : Ver.B
CPLD Version : 002

128M bytes SDRAM
PCB Version : Ver.B
CPLD Version : 002
CPUCard 1
PCB Ver : REV.0
CPLD Ver : 001

128M bytes SDRAM
PCB Version : Ver.B
CPLD Version : 002
CPUCard 1
PCB Ver : REV.0
CPLD Ver : 001

128M bytes SDRAM
PCB Version : REV.0
CPLD Version : 002
CPUCard 1
PCB Ver : REV.0
CPLD Ver : 001

256M bytes SDRAM
PCB Version : Ver.E
CPLD Version : 004
CPUCard 1
PCB Ver : Ver.C
CPLD Ver : 001

3.9.12. Reconfiguring the Configuration file
The configuration file has to be reconfigured again. Currently the switch is set to defaults.
<SW8800> dis start

MainBoard:
SlaveBoard:
The configuration file sw8800dc1.cfg is on flash: on both the fabric and the slave. Your filename
will be different.
<SW8800>dir
0 -rw- 326680 Nov 13 2007 18:41:36 fab03_02_03d.app

1 drw- - Jan 01 2003 00:00:24 hafile
2 -rw- 4 Jan 21 2006 04:18:37 snmpboots
6 -rw- 118 Sep 20 2006 21:18:12 ls.pwd
7 -rw- 207696 Nov 13 2007 18:41:56 iom03_01_08d.app
8 -rw- 272898 Nov 13 2007 18:42:19 iop03_02_05d.app
9 -rw- 3950 Nov 14 2007 10:27:35 sw8800dc1.cfg
10 -rw- 326896 Nov 13 2007 19:35:36 fab05_02_06d.app
11 -rw- 207696 Nov 13 2007 19:36:03 iom05_01_08d.app
12 -rw- 273034 Nov 13 2007 19:36:16 iop05_02_06d.app
Configure the switch to use from the desired configuration file. Notice that the configuration file
was set on both the master and slave fabric.

Please wait ...
<SW8800>dis start
MainBoard:
Next startup saved-configuration file:
flash:/sw8800dc1.cfg
SlaveBoard:


Reboot the switch.

Important: Answer Y to the question “Current configuration will be lost in next startup if you
continue. Continue?”.
<SW8800>reb
Start to check configuration with next startup configuration file,
please wait
......
This command will reboot the device. Current configuration will be
lost in nex
t startup if you continue. Continue? [Y/N]:y
#Nov 14 10:57:14:587 2007 SW8800 COMMONSY/4/REBOOT:
Reboot device by command.
%Nov 14 10:57:14:683 2007 SW8800 DEV/4/SYSTEM REBOOT:

System is rebooting now.
ZBB_TEST
Starting...
*************************************************
* *
* *
*************************************************

CPU type : MPC755
Memory Size : 512MB

The board is steady
The MCX is present
EPLD1 testing is OK
EPLD2 testing is OK

The switch's Mac address is 0020.9c69.bad1
Press Ctrl+B to enter Boot Menu...

Auto-booting...

Decompress
Image................................................................
......................................................OK!
Login into the switch. Make sure the fabrics are synchronized. Verify the configuration file.
<SW8800>
%Nov 14 11:02:06:504 2007 SW8800 SHELL/4/LOGIN: Console login from con0
<SW8800>dis swit st
<SW8800>dis start
MainBoard:
Current startup saved-configuration file:
SlaveBoard:
Current startup saved-configuration file:
FYI: Rev 5.01.20 does not enable telnet by default. This allows telnet access to the switch. To
enable:
<SW8800>sys
System View: return to User View with Ctrl+Z.
[SW8800]telnet server ena

% Telnet server has been started

The configuration may have changed from rev 3.X. Using the printout of the configuration file and
enter a dis cu command on the switch 8800 take a look at the configuration differences if any.
ACL commands have changed at rev 5.01.21. They will need to be updated. Other commands
have also changed. Please refer to the Configuration and Command Reference Guides.

Readme Release Notes

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Readme Release Notes

Enviado por

Direitos autorais:

Formatos disponíveis

3Com Switch 8800

1.4.1. Release V5.01.21 ...................................................................................................................................................4

1.4.2. Release V5.01.20 ...................................................................................................................................................4

1.5.1. V5.01.21 Enhancements/ CLI Changes..................................................................................................................5

1.5.2. V5.01.20 Enhancements ........................................................................................................................................5

Copyright © 2007 3Com Corporation. All rights reserved.

3.1.1. IMPORTANT NOTES: ..........................................................................................................................................17

application code (.app files). ...........................................................................................................................................60

3.9.4. Configure an IP address on Ethernet port on the fabric........................................................................................61

8800 using FTP. .............................................................................................................................................................62

3.9.6. How to copy a file from one fabric to another fabric..............................................................................................64

3.9.12. Reconfiguring the Configuration file....................................................................................................................72

Table 1 Software Release Numbers Addressed in These Release Notes

The software images are as follows:

This release applies to a new Advanced Software version supporting IPv6

1.2. Online Resources

1.3. System Requirements

Copyright © 2007 3Com Corporation. All rights reserved.

System Power Supply Fan Tray

Switch 8800 14-Slot Starter Kit (3C17541) 1 2

1.4. Support for New Modules

3Com Part # Module Description

1.4.2. Release V5.01.20

Release 5.01.20 added support for the following modules.

3Com Part # Module Description

Copyright © 2007 3Com Corporation. All rights reserved.

1.5. Enhancements to Software

1.5.2. V5.01.20 Enhancements

Copyright © 2007 3Com Corporation. All rights reserved.

1.6. Changes in Behavior

Chapter 2 Known issues for Switch 8800 V5.01.21

Copyright © 2007 3Com Corporation. All rights reserved.

2.1. Configuration File Issues after Software Upgrade

Issue the command "startup saved-configuration <saved-config-file-name>" to set the old

• Quality of Service (QoS)

2.2. Note regarding features in both Release v3.01.xx and Release

2.3. Unsupported Modules

3C17542 3Com Switch 8800 Network Monitoring Module

2.4. Unsupported Features

Copyright © 2007 3Com Corporation. All rights reserved.

• Various ARP Commands – see 2.19 ARP.

• MBGP (Multicast BGP) – this would also affect MSDP implementations

• MPLS and related features:

• MLD Version 2 (Version 1 works – but Version 2 does NOT work.)

2.5. Multicast Protocol

Copyright © 2007 3Com Corporation. All rights reserved.

2.6. System Management

2.7. High Availability

2.8. Broadcast Storm Control

2.11. Boot Code

2.13. Link Aggregation

Copyright © 2007 3Com Corporation. All rights reserved.

2.15. Super VLAN

2.16. Protocol VLAN

if ip ARP is desired – should use the command

[SW8800] proto mode ethernetii etype 0806

if Appletalk ARP is desired – should use the command

Copyright © 2007 3Com Corporation. All rights reserved.

[SW8800] proto mode ethernetii etype 80F3

[SW8800] proto mode snap etype 80F3

[SW8800 – vlanX] protocol mode snap etype 809B <cr>

2.17. DHCP Relay

Copyright © 2007 3Com Corporation. All rights reserved.