Beruflich Dokumente
Kultur Dokumente
5500G
Release Notes
SWITCH 5500G, VERSION 3.03.01 RELEASE NOTES
Contents
1. Introduction ............................................................................................................................................... 4
1.1. Scope.................................................................................................................................................... 4
1.2. Online Resources ................................................................................................................................. 4
2. Issues Fixed in Switch 5500G v3.03.01 ................................................................................................... 5
2.1. Static MAC addresses .......................................................................................................................... 5
2.2. 1000BASE-SX SFP 3CSFP91.............................................................................................................. 5
2.3. 10 Gigabit Ethernet Maximum Frame Length ....................................................................................... 5
2.4. IGMP Query.......................................................................................................................................... 5
3. Enhancements to Software ...................................................................................................................... 5
4. Known Issues For Switch 5500G v3.03.01 .............................................................................................. 7
4.1. 802.1x Authentication ........................................................................................................................... 7
4.2. Access Management ............................................................................................................................ 7
4.3. Access Control Lists (ACL) ................................................................................................................... 7
4.4. Clustering.............................................................................................................................................. 8
4.5. Command Line Interface (CLI).............................................................................................................. 8
4.6. DHCP Relay ......................................................................................................................................... 8
4.7. Link Aggregation ................................................................................................................................... 8
4.8. Multiple Spanning Tree (MSTP)............................................................................................................ 8
4.9. Port Security ......................................................................................................................................... 8
4.10. Protocol VLAN .................................................................................................................................... 8
4.11. RADIUS Authentication....................................................................................................................... 8
4.12. Remote Port Mirroring......................................................................................................................... 9
4.13. Routing ............................................................................................................................................... 9
4.14. Secure Shell (SSH)............................................................................................................................. 9
4.15. Security Configurations Limitations..................................................................................................... 9
4.16. Traps..................................................................................................................................................10
4.17. MAU MIB ...........................................................................................................................................10
4.18. Broadcast Storm Control....................................................................................................................10
4.19. Stack Software Auto Upgrade............................................................................................................10
4.20. TACACS+ ..........................................................................................................................................10
4.21. Upgrading with 3Com Network Director (3ND) ..................................................................................10
4.22. Stacking .............................................................................................................................................11
4.23. Web Interface ....................................................................................................................................11
4.24. 1000BASE-SX SFP 3CSFP91...........................................................................................................11
4.25. 1000BASE-LH70 SFP 3CSFP97 .......................................................................................................11
5. Upgrading Software .................................................................................................................................11
5.1. The Contents of the Executable File ....................................................................................................11
5.2. Upgrading from the Command Line Interface ......................................................................................12
5.3. Upgrade using TFTP............................................................................................................................14
5.3.1. Stacks or XRN stacks of the Switch 5500s. .........................................................................................................15
5.3.2. File Distribution .....................................................................................................................................................15
5.3.3. Command Line Interface Switch Setup.................................................................................................................16
5.4. Use Update fabric to upgrade software in the fabric automatically ....................................................16
5.5. Upgrade using FTP (via a network port) ..............................................................................................18
5.6. Upgrade using XModem (via the console cable) .................................................................................19
5.7. Upgrading from the BootROM Interface...............................................................................................20
5.7.1. How to Access the Boot Menu..............................................................................................................................20
5.7.2. Examining the File System ...................................................................................................................................21
1. Introduction
1.1. Scope
This document contains the release notes for the Switch 5500G V3.03.01 Software. These
release notes summarize operational requirements and issues for the following Switch 5500G
products:
Description
V3.03.01 Software
The software image files for the Switch 5500G are as follows:
s4c03_03_01s56.app
s4c03_03_01s168.app
s4f05_00.btm
s4i05_03.web
At the time of this publication, these documents can be found at this link:
http://www.3com.com/products/en_US/result.jsp?selected=6&sort=effdt&sku=WEBSW5500SYS&
order=desc
You can obtain the latest technical information for your Switch, including a list of known problems
and solutions, from the 3Com Knowledgebase: http://knowledgebase.3com.com
3. Enhancements to Software
The V3.03.00 release of the Switch 5500 / 5500G software includes the following enhancements
that work in both standalone and stacked-XRN operation:
DHCP option 82
Proxy ARP
802.1x reauthentication
BPDU Tunnels
Wake on LAN
Scheduled reboots
Password checker
BPDU drop
Voice VLAN
MSTP enhancements
The V3.03.00 release of the Switch 5500 / 5500G software includes the following enhancements
that work only when units are standalone:
ARP inspection
IP source guard
Selective QinQ
HWTACACS
Selective Q-in-Q
IPv6 management
o
Pingv6
Tracertv6
telnetv6
TFTPv6
DNSv6
ARPv6
IGMP snooping v3
IGMP proxy
DNS client
HW Ping
Trace MAC
Access Management cannot be disabled on an individual port without deleting all configured
user bindings on that port.
The behavior of Access Management function is not dependent upon the user-bind settings.
For example Enable Access Management does not block all ports if no user-bind is
configured and Disable Access Management does not disable feature once user-bind is
configured.
If an ACL is filtering based on TCP and UDP port and the IP options field is present, the
5500G does not compensate for it.
When in a stack the ACL resources or configurations from individual units cannot be
displayed. The user has to console or telnet into each unit separately to view these items.
4.4. Clustering
Connecting to a cluster member thru "cluster switch-to" command and disabling the cluster
member doesn't return the control back to the Administrator. The user must reboot the
cluster unit in order to gain control back again.
When a cluster member is down, the cluster member will not allow to be rebooted, however,
there is no error message indicating that the reboot operation was aborted.
When Port Security is configured, excessive authentication requests may flood the RADIUS
server event log. In order to prevent this, enable intrusion mode on the Switch 5500 / 5500G
and set it to block mac.
If a user logs onto the unit via Telnet with the admin user name, the RADIUS server
authenticates the user with level 3 access. If however, the user logs onto the unit via the
console with the admin user name, the RADIUS server authenticates the user with level 1
access.
On the Switch 5500 products, MAC address learning does not support VLAN based learning
modes on inbound or outbound traffic. Because of this, remote bi-direction mirrored traffic
does not pass through the relay switch.
4.13. Routing
Static Routes are advertised back onto the source network. According to RIP Split horizon,
learned routes must not be advertised out the learned interface (back to the source) with a
metric other than 16 (Poison Reverse). This results in counting to infinity problems and slow
convergence of the network for static routes. It is possible to configure all the static routes in
the switches on the network to avoid this problem.
Some additional CLI configuration may be required on the 5500G after deploying security
across your network via 3Com Network Director (3ND).
The default dot1x authentication mode on the 5500G is CHAP. If a different authentication
mode is deployed on the user network, it must also be configured on every switch, using the
CLI dot1x authentication-mode command. In addition, if eap-ttl is being deployed, the device
configuration must be modified by configuring a RADIUS server domain and enabling this
domain. The 5500G uses domain information contained in the dot1x requests to decide
where to send the requests. Therefore, network domains must be configured in each switch
for dot1x authentication to operate correctly. Check the 5500G configuration guide for more
details.
The switch is unable to send user authentication and security violation traps. The following
CLI commands do not take effect:
port-security trap addresslearned
port-security trap intrusion
port-security trap dot1xlogon
port-security trap dot1xlogoff
port-security trap dot1xlogfailure
port-security trap ralmlogon
port-security trap ralmlogoff
port-security trap ralmlogfailure
After configuring the Radius Authentication Server via 3ND, console port logins will not be
granted administrator rights. Also, if the RADIUS service fails, it will become impossible to
access the 5500G via the console port.
It is not possible to modify the Radius Server details via 3ND while users are logged on the
switch via Telnet.
4.16. Traps
Excessive configuration traps should be ignored. The switch sends traps repeatedly on stacks
when entering the system CLI command.
If any unit in a stack does not have enough free space to hold a new image, the auto
upgrade will fail. An auto upgrade occurs when adding a new unit(s) into an existing
stack. If this happens, it is possible that after the next reboot, some units will be running
different versions of software. If this occurs, then the stack will only form with those units
running the same version of software. To prevent this from occurring, it is recommended
that users check to make sure that each unit in a stack has enough space to hold the
new image before upgrading. If there is not enough space, files will manually need to be
deleted in order to free up space.
When upgrading a stack of units, the unit with the lowest number (unit 1) should be
upgraded first. If this is not done, the upgrade may fail. It is recommended that the user
configure a new CLI command on all the units. For example: [Switch] fabric memberauto-update software enable. The auto update does not apply to the bootrom or web
files. For the bootrom and web files, the command update fabric <filename> must be
issued from the CLI on the unit with the lowest number.
4.20. TACACS+
TACACS+ Real-Time Accounting does not work for Telnet, SSH and SFTP clients, however, it is
supported for PPP sessions.
-rw-
951671
10
s4i04_00.web
4.22. Stacking
Switch 5500Gs that have never been added to a stack may report cascade port errors. This will
be addressed in an upcoming 3Com Network Director Service Pack.
5. Upgrading Software
IMPORTANT NOTES:
This chapter describes how to upgrade software on your Switch 5500 / Switch 5500G. This
section covers the following topics:
Examples given in the following sections in this chapter may be from 5500G or from 5500
switches, which operate similarly.
Release Notes
Application Software
Web Software
BootROM Software
11
Before upgrading the software to your Switch 5500 from the CLI, it is important to check the
contents of the flash to ensure that there is enough space to download the new files.
The flash space needed for the new files is approximately 6.0 MB for both Switch 5500-SI
and Switch 5500-EI and 5.8 MB for Switch 5500G-EI.
Directory of unit1>flash:/
1
2
3
4
s4m03_02_03s56v.app
s4e02_02.btm
s4h02_01.web
3comoscfg.def
12
The file list should contain one of each file type (.def and/or .cfg .web, .btm and
.app ).
The display boot-loader will display the currently used .app file(s). The display
startup command will display the currently used .cfg file(s). The display web
package will display the currently used .web file(s).
3. Any additional files should be considered for deletion to allow maximum space for
downloading the new files. To delete a file from the list enter:
delete /unreserved unit1>flash:/filename
To delete files from the list for the remaining units in a fabric, replace unit1 with unit2
(on the next line) and so on for each Switch in the fabric.
If you need more free records, you can delete the backup .app file and backup .web
if you have them. Later the existing .app and .web files can be configured to be the
new backup files after the new version is installed.
4. The /unreserved option will cause the file to be deleted from both the flash and the
recycle-bin. To check that deleted files have been removed from the recycle-bin
enter the following:
reset recycle-bin unit1>flash:/
This can take minutes depending on how many bytes are in the recycle bin.
If the recycle-bin is empty the following is displayed:
% Recycle bin in this directory is empty.
To check that deleted files have been removed from the recycle-bin for the remaining
units in a fabric, replace unit1 with unit2 and so on for each Switch in the fabric.
The following steps enable you to backup each Switch 5500 in the fabric:
1. The default configuration file must have the name 3ComOScfg.def. This file is only
used if there is no active configuration file (.cfg ) in the flash file system. The default
configuration file is the same for every Switch 5500 of the same type (i.e Switch 5500
28-port) and is different to the file for a Switch 5500 of a different type (i.e Switch
5500 52-port). A sample default configuration file is provided by factory default with
the Switch and is not supplied in this upgrade.
Enter the following command:
more 3comoscfg.def
The display similar to the following shows on the first line of the file:
#Switch 5500G-EI 24-Port file version 3.03.01
This file is infrequently changed, so the version number may not match the
application software version number.
The default configuration file can be created by saving the configuration and
renaming the xxx.cfg file as 3ComOScfg.def.
To back up the default configuration file on each Switch in the fabric, enter:
13
Replace unit1 with unit2 and so on for each Switch 5500 in the fabric.
2. The active configuration file can be given any name, provided it ends in the extension
.cfg. 3Com recommends that each fabric is given a unique configuration file name
so that when the file is saved to an external TFTP/FTP server, it is clear which fabric
the file belongs to. To see what configuration files are in use on the switch, use the
command display startup.
To back up the active configuration file on each Switch 5500 in the fabric, enter:
copy unit1>flash:/3ComOScfg.cfg unit1>flash:/030303.cfg
Replace unit1 with unit2 and so on for each Switch 5500 in the fabric. 3Com
recommends that you save the active configuration file for each Switch 5500 in the
fabric and also save it to an external storage device. To save the active configuration
file to a TFTP server in User View enter:
tftp aaa.aaa.aaa.aaa put unit1>flash:/(Configuration filename) (Configuration
filename)_1.cfg
(where aaa.aaa.aaa.aaa is the IP address of the TFTP server)
Replace unit1 with unit2 and _1.cfg with _2.cfg and so on for each Switch in the
fabric.
3. The Web user interface file and the application file must be the same on all switches
in the fabric. It is not necessary to backup these files because they will have a new
version number.
s4m
s4c
s4e
s4f
s4h
s4i
In the examples below the files needed to update Switch 5500G- EI are used. Filenames will
be different for the Switch 5500-SI/EI.
14
15
Replace unit2 with unit3 and so on for each Switch 5500 in the fabric.
3. To copy the new Bootrom firmware file to each Switch in the fabric, enter:
copy unit1>flash:/s4f05_00.btm unit2>flash:/
Replace unit2 with unit3 and so on for each Switch 5500 in the fabric.
To set the remaining Switches in the fabric to boot from the new software, replace
unit1 with unit2 and so on for each Switch in the fabric.
2. To set the Switch to load the new BootROM firmware, enter:
boot bootrom unit1>flash:/s4f05_00.btm
To set the remaining Switches in the fabric to load the new BootROM firmware,
replace unit1 with unit2 and so on for each Switch in the fabric.
3. You will now need to reboot the fabric for the changes to take effect. The Switch
5500 will upgrade the BootROM firmware and boot from the specified software .app
file.
4. Once the unit is boot up, set the web management file in the User view, enter:
boot web-package unit1>flash:/s4h03_03.web main
The files that you have saved in the backup phase can be deleted from the file system on
the unit(s) once you are satisfied the upgrade has been completed successfully and
without any problems. It is good idea to keep a copy of these files on a tftp, FTP or SFTP
server in case of disaster or the Switch 5500 is replaced.
16
3. After the free space is confirmed, the version compatibility comparison will be done to
ensure the new file can work after the switch rebooting. If the comparison fails, the updating
fails too. The following checks are made:
a. For the app and btm files, the hardware/software version number is checked
b. The web file is checked to see if it can run with the running app file.
c. No check is required on the cfg file
If there is conflict with the filename, the updating fails.
4. All checks have been done and the file transmission starts after user confirmation. During
the transmission, if the error happens on any unit, the transmission fails. If the transmission
is done, each unit will write the file into flash. There is a selection for user to confirm whether
the new one will be the file next time to boot, if user selects YES, the new one will hold
main attribute.
Below is an example of how to update the fabric in a stack of 3 Switch 5500Gs. Any
comments are preceded by with #".
Transfer the files to one of the units in the stack
The needed files (.app, .btm and .web) must be transferred to one of the units in the stack. The
update fabric commands will be issued from this unit. If an error occurs with this command, go in
the system view and issue the command: fabric member-auto-update software enable
17
Notice:
Use update fabric command to update all the units in the fabric (stack) by using the
btm, app and web files on a unit in the fabric. But to update web file, btm and app files
have to be updated first to all units then reboot the switches, and then use update
fabric command to update web file to all the remaining units.
18
binary
undo passive
get s4m03_03_01s56e.app
The following information is displayed if the download has been successful:
200 PORT command successful.
150 File status OK ; about to open data connection
.........................................................................226 File transfer successful.
FTP: 4644124 byte(s) received in 73.733 second(s) 71.00K byte(s)/sec.
Download the web file and the bootrom file in the same way.
3. Enter quit to exit.
4. Copy these files as described in File Distribution, steps 1 to 4 under TFTP section.
5. Now activate these files as described in Command Line Interface Switch Setup,
steps 1 to 4 under TFTP section.
6. You can use the update fabric command to upgrade software in a fabric as
described in the TFTP upgrade section.
19
6. Now activate these files as described in Command Line Interface Switch Setup,
steps 1 to 4 under the TFTP section.
7. You can use the update fabric command to upgrade software in a fabric as
described in the TFTP upgrade section.
2. Select Enter (the default is no password). The Boot Menu will be displayed:
BOOT MENU
1. Download application file to flash
2. Select application file to boot
3. Display all files in flash
4. Delete file from flash
5. Modify bootrom password
6. Enter bootrom upgrade menu
7. Skip current configuration file
8. Set bootrom password recovery
9. Set switch startup mode
0. Reboot
Enter your choice (0-9):
20
This option displays all the files in flash and also indicates the file that the Switch
5500 is currently set to boot from (marked with an asterisk). A b by the file number
indicates the file is a backup boot file.
The new files that are required by the Switch 5500-SI/EI are as follows:
s4h03_03.web
s4e03_01.btm
startup.cfg
# this is the main configuration file, your filename will probably be different.
s4m03_03_01s56e.app
The s4m03_03_01s56e.app file is the application software. The name of this file will vary
depending on the Switch type and the encryption level. The Switch 5500G-EI will need the
main configuration file and the following files:
s4c03_03_01s56.app or s4c03_03_01s168.app
s4f05_00.btm
s4i05_03.web
If the filename is in brackets, for example [test.cfg], this indicates that the file has
been deleted from the CLI but is still present in the recycle-bin. . If there is no need
for these files, delete these files first. You may recover enough free records in the
flash:/ file system to continue with the update/upgrade.
21
Any additional files should be considered for deletion to allow maximum space for
downloading the new files.
3. To delete a file from the list, select option 4 from the Boot Menu and select the file
number you wish to delete.
1. From the Boot Menu, select option 1 (Download application file to flash) to display
the following:
Enter your choice (0-9): 1
1. Set TFTP protocol parameters
2. Set FTP protocol parameters
3. Set XMODEM protocol parameters
0. Return to boot menu
Enter your choice (0-3):
Enter the .app file name, Switch 5500s IP address and tftp servers IP address. The
switch and the TFTP server must reside on the same IP subnet. Next, there will be a
prompt to verify :
Are you sure to download file to flash? Yes or No(Y/N)
3. Enter y and the following information is displayed to indicate the file is downloading:
Attached TCP/IP Interface to netdrv0
Attaching network interface lo0...done
Loading.....done
Free flash Space: 10456064 bytes
Writing flash....done!
Please input the file attribute (main/backup/none): main
The attribute of s4m03_02_03s56v.app is changed from main to none!
done!
Note: s4m03_02_03s56v.app was the old existing application file .The newly downloaded
application file will now be used when the switch is rebooted because main was chosen.
If backup is chosen, this file will be used only if the main file is unavailable. None, the file
will be just added to the file system. The attributes can be changed again following the
procedure in section Select Application to Boot.
22
4. Repeat steps 1 to 4 for each of the remaining files (.app and .def files can be
download via this method). Do not use this method for updating the BootROM code.
Use one of the BootROM Upgrading procedures.
3. Enter the .btm file name, Switch 5500s IP address and tftp servers IP address. The
Switch 5500 and the tftp server must reside on the same network. There will be a
prompt to verify :
Are you sure you want to update your bootrom? Yes or No(Y/N)
4. Enter y and the following information is displayed to indicate the file is downloading:
Loading.........................................................................
................................done
Bootrom updating..........done!
23
3. Enter the .app file name, Switch 5500s IP address, FTP Servers IP address and
FTP user name and password. The Switch 5500 and the FTP server must reside on
the same network. There will be a prompt to verify :
Are you sure to download file to flash? Yes or No(Y/N)
4. Enter y and the following information is displayed to indicate the file is downloading:
Loading.....done
Free flash Space: 10456064 bytes
Writing flash....done!
Please input the file attribute (main/backup/none):none done!
5. Repeat steps 1 to 4 for each of the remaining files (.app and .def files can be
download via this method). Do not use this method for updating the BootROM code.
Use one of the BootROM Upgrading procedures.
3. Enter the file name, Switch 5500s IP address, FTP Servers IP address, FTP user
name and password. The switch and the FTP server must reside on the same IP
subnet. There will be a prompt to verify :
Are you sure you want to update your BootROM? Yes or No (Y/N)
4. Enter y and the following information is displayed to indicate the file is downloading:
Loading.........................................................................
................................done
Bootrom updating..........done!
24
5. As the file is downloading, start the XModem send file process with terminal
emulation software, such as Microsoft HyperTerminal, Transfer>Send File.
When the download is complete, the following information is displayed:
Please input the file attribute (main/backup/none):none done!
25
6. Repeat steps 1 to 5 for each of the remaining files (.app and .def files can be
download via this method). Use the following procedure to update the BootROM
code using XModem.
You will also need to change the baud rate on HyperTerminal to 19200 bps and
select XModem protocol.
If supported, you can select Option 5 to increase the speed of the download.
4. Press Enter to start the download. The following information is displayed:
Now please start transfer file with XMODEM protocol
If you want to exit, Press <Ctrl+X>
Loading...CCCCCCCCCCCCCCCCCCCCCCCCCCCCC
5. As the file is downloading, start the XModem send file process with terminal
emulation software, such as Microsoft HyperTerminal.
6. When the download is complete, the following information is displayed:
Are you sure you want to update your BootROM? Yes or No [Y/N]
7. Enter y and the following information is displayed to indicate the file is downloading:
Loading.........................................................................
................................done
BootROM updating..........done!
26
BOOT MENU
1. Download application file to flash
2. Select application file to boot
3. Display all files in flash
4. Delete file from flash
5. Modify bootrom password
6. Enter bootrom upgrade menu
7. Skip current configuration file
8. Set bootrom password recovery
9. Set switch startup mode
0. Reboot
Enter your choice(0-9): 6
At the HyperTerm window, disconnect, click on Call>Disconnect or the click on the off hook
phone icon. Then click on File>Properties or the Properties icon:
27
28
Click on the "Bits per second" drop down menu and change to 115200. Click OK. Click OK again.
To start the transfer of the file, go back on the switch, hit the enter key.
Browse to where the bootROM (.btm) file resides. Check that the Protocol: is Xmodem. Then
click Send. A window with the status of the transfer will appear. The Packet and File: will
increment as the file is transferred:
After the file transfer is completed, done! will appear and the BootROM will be updated
automatically. The following will appear on the switch console port:
29
done!
Bootrom updating..........done!
Click Configure...
30
Change the baud rate back to 19200. Click OK button. Click OK button again.
Hit the Enter key. The Boot Menu will appear.
31
32