Documente Academic
Documente Profesional
Documente Cultură
Software version 3.02.03 / 3.02.04 Part Number: 10015929 Rev. AA Published March 2007
Contents
1. Introduction ............................................................................................................................................... 2 1.1. Scope.................................................................................................................................................... 2 1.2. Online Resources ................................................................................................................................. 2 1.3. Enhancements to Software................................................................................................................... 3 2. Issues Fixed in Switch 5500 v3.02.03 / v3.02.04 ..................................................................................... 3 2.1. DSCP / CoS Mapping ........................................................................................................................... 3 2.2. Port Security Configuration ................................................................................................................... 3 2.3. RADIUS Configuration .......................................................................................................................... 3 3. Known Issues For Switch 5500 v3.02.03 / v3.02.04 ................................................................................ 4 3.1. 802.1x Authentication ........................................................................................................................... 4 3.2. Access Management ............................................................................................................................ 4 3.3. Access Control Lists (ACL) ................................................................................................................... 4 3.4. Clustering.............................................................................................................................................. 4 3.5. DHCP Relay ......................................................................................................................................... 4 3.6. Link Aggregation ................................................................................................................................... 4 3.7. Multiple Spanning Tree (MSTP)............................................................................................................ 5 3.8. Port Security ......................................................................................................................................... 5 3.9. Protocol VLAN ...................................................................................................................................... 5 3.10. RADIUS Authentication....................................................................................................................... 5 3.11. Remote Port Mirroring......................................................................................................................... 5 3.12. Routing ............................................................................................................................................... 5 3.13. Security Configurations Limitations..................................................................................................... 5 3.14. TACACS+ ........................................................................................................................................... 6 3.15. Upgrade .............................................................................................................................................. 6 3.16. Stacking .............................................................................................................................................. 6 3.17. Web Interface ..................................................................................................................................... 6 4. Upgrading Software .................................................................................................................................. 7 4.1. The Contents of the Executable File ..................................................................................................... 7 4.2. Upgrading from the Command Line Interface ....................................................................................... 7 4.3. Upgrade using TFTP............................................................................................................................10 4.4. FTP (via a network port) ......................................................................................................................11 4.5. XModem (via the console cable)..........................................................................................................12 4.6. Upgrading from the BootROM Interface...............................................................................................13 4.7. Upgrade using TFTP............................................................................................................................14 4.8. BootROM Upgrading using TFTP ........................................................................................................15 4.9. Download Application files to flash using FTP .....................................................................................15 4.10. BootROM Upgrading using FTP ........................................................................................................16 4.11. Upgrade using XModem ....................................................................................................................16 4.12. BootROM Upgrading using XModem.................................................................................................17 4.13. Select Application to Boot ..................................................................................................................18
1. Introduction
1.1. Scope
This document contains the release notes for the Switch 5500 V3.02.03 / V3.02.04 Software. These release notes summarize operational requirements and issues for the following Switch 5500 products: Switch 5500-SI 28-Port (3CR17151-91) Switch 5500-SI 52-Port (3CR17152-91) Switch 5500-EI 28-Port (3CR17161-91) Switch 5500-EI 52-Port (3CR17162-91) Switch 5500-EI PWR 28-Port (3CR17171-91) Switch 5500-EI PWR 52-Port (3CR17172-91) Switch 5500-EI 28-Port FX (3CR17181-91) Switch 5500G-EI 24-Port (3CR17250-91) Switch 5500G-EI 48-Port (3CR17251-91) Switch 5500G-EI PWR 24-Port (3CR17252-91) Switch 5500G-EI PWR 48-Port (3CR17253-91) Switch 5500G-EI 24-Port SFP (3CR17258-91)
Description
The latest version of the Switch 5500-SI / 5500-EI The latest boot code running on the Switch 5500-SI / 5500-EI The latest web code running on the Switch 5500-SI / 5500-EI The latest version of the Switch 5500G-EI The latest boot code running on the Switch 5500G-EI The latest web code running on the Switch 5500G-EI
Switch 5500 Family Release Notes v3.02.03 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
The V3.02.04 release of the Switch 5500G-EI software includes the following additional enhancement: 3CSFP9-81 / 3CSFP9-82 SFP support: The Switch 5500G-EI supports the new 3CSPF9-81 100Base-FX SFP and the 3CSFP9-82 100Base-LX10 SFP.
3.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. Members in a cluster cannot be upgraded while a software upgrade is in progress.
3.12. 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. RIP Poison Reverse is not supported in this software release.
Switch 5500 Family Release Notes v3.02.03 In order for 3ND to receive user authentication and security violation traps from the 5500, the following CLI commands need to be applied to each device after enabling port security from 3ND: 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 5500 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.
3.14. TACACS+
TACACS+ Real-Time Accounting does not work for Telnet, SSH and SFTP clients, however, it is supported for PPP sessions.
3.15. Upgrade
If a 5500 Family switch was previously upgraded using the CLI, 3Com Network Director (3ND) cannot upgrade the web file. In this scenario, the CLI dir command will show the main web file with an asterisk, which means that it has a main attribute. For example: 3* -rw951671 Jan 05 2005 20:20:39 s4i04_00.web
Perform the following steps to insure a successful 3ND upgrade: 1. Run a CLI script deleting all the of the web files on the Switch delete /unres *.web 2. Upgrade the Switch via 3ND in the normal way.
3.16. Stacking
Switch 5500s 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.
4. Upgrading Software
IMPORTANT NOTES: This chapter describes how to upgrade software on your Switch 5500. This section covers the following topics: The contents of the executable file Upgrading from the Command Line Interface (CLI)
Directory of unit1>flash:/ 1 2 3 4 -rw- 3496055 Feb 10 2007 19:33:21 -rw- 310432 Feb 10 2007 19:33:27 -rw- 893111 Feb 10 2007 19:33:40 -rw- 11382 May 22 2006 19:34:51 s4a03_02_03s56.app s4e02_02.btm s4h02_01.web 3comoscfg.def
2. You can check the contents of the flash for the remaining units in the fabric by entering:
dir unit2>flash: dir unit3>flash: dir unit4>flash: dir unit5>flash: dir unit6>flash: dir unit7>flash:
The file list should contain one of each file type ( .web, .def, .cfg and .app ). 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. 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:/
If the recycle-bin is empty the following is displayed: % File cant be found unit1>flash:/ 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: #28-port 3com version 3.2.3 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:
copy unit1>flash:/3ComOScfg.def unit1>flash:/030203.cfg
Replace unit1 with unit2 and so on for each Switch 5500 in the fabric. 2. The active configuration file can been 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 server, it is clear which fabric the file belongs to. To back up the active configuration file on each Switch 5500 in the fabric, enter:
copy unit1>flash:/3ComOScfg.cfg unit1>flash:/030203.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:/3ComOScfg.cfg 3ComOScfg_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.
(where aaa.aaa.aaa.aaa is the IP address of the TFTP server) s4a indicates the Switch filename, see table below for further details:
Switch 5500 Family Filenames Filename Prefix s4a s4b s4c s4e s4f s4h s4i 3Com Switch 5500 Model Switch 5500-SI software Switch 5500-EI software Switch 5500G-EI software Switch 5500-SI/EI bootrom software Switch 5500G-EI bootrom software Switch 5500-SI/EI web software Switch 5500G-EI web software
3. To download the bootrom file, enter: tftp aaa.aaa.aaa.aaa get s4e02_00.btm The BootROM firmware may not require upgrading for every software upgrade. To display the BootROM firmware version in any view enter: display version The following should be displayed: BootROM version is 2.02 The number 2.02 will match the version number in the BootROM file, which is s4e02_02.btm. If the version number of the file matches the displayed version, there is no need to download the bootrom (.btm) file. File Distribution The following commands enable you to distribute your downloaded files to the remaining Switch 5500 devices in the fabric: 1. To copy the new software file to each Switch in the fabric, enter the following from User View: copy unit1>flash:/s4a03_02_03s56.app unit2>flash:/ Replace unit2 with unit3 and so on for each Switch 5500 in the fabric.
10
2. To copy the new default configuration file to each Switch in the fabric, enter: copy unit1>flash:/3ComOScfg.def unit2>flash:/ Replace unit2 with unit3 and so on for each Switch 5500 in the fabric. 3. To copy the new Web user interface file to each Switch in the fabric, enter: copy unit1>flash:/s4e02_02.web unit2>flash:/ Replace unit2 with unit3 and so on for each Switch 5500 in the fabric. 4. To copy the new Bootrom firmware file to each Switch in the fabric, enter: copy unit1>flash:/s4e02_02.btm unit2>flash:/ Replace unit2 with unit3 and so on for each Switch 5500 in the fabric. Command Line Interface Switch Setup 1. To set the Switch to boot from the new software you have downloaded, enter the following:
boot boot-loader unit1>flash:/s4a03_02_03s56.app
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:/s4e02_02.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:/s4e02_00.web main
The files that you have saved in the backup phase should be deleted once the upgrade has completed successfully.
11
2. To download the application file, enter: binary get s4a03_02_03s56.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: 5283304 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.
12
1. Select Enter (the default is no password) to display the following boot menu:
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):
3. Select option 3 from the Boot Menu. A file list similar to the following is displayed:
Enter your choice(0-9): 3 File Number File Size(bytes) File Name ================================================== 1(*) 3496055 s4a03_02_03s56.app 2 310432 s4e02_02.btm 3 893111 s4h02_01.web 4 11382 3comoscfg.def 5(*) 11382 startup.cfg 6 151 private-data.txt Free Space: 2554462 bytes The current application file is s4a03_02_03s56.app (*)-with main attribute (b)-with backup attribute (*b)-with both main and backup attribute
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 asterix). A b by the file number indicates the file is a backup boot file. The files that are required by the Switch 5500 are as follows:
s4h02_01.web
13
The s4a03_02_03s56.app file is the application software. The name of this file will vary depending on the Switch type and the release version. 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. Any additional files should be considered for deletion to allow maximum space for downloading the new files. 4. 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):
3. Enter the file name, Switch IP address and Server IP address to display the following:
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:
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):none done!
5. Repeat steps 1 to 4 for each of the remaining files (.app, .btm, and .cfg files can be download via this method).
14
3. Enter the file name, Switch IP address and Server IP address to display the following:
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!
3. Enter the file name, Switch IP address, Server IP address and FTP user name and password to display the following:
Are you sure to download file to flash? Yes or No(Y/N)
15
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, .btm, and .cfg files can be download via this method).
3. Enter the file name, Switch IP address, Server IP address, FTP user name and password to display the following:
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!
16
3. Select option 2 to set the baud rate to 19200. 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. When the download is complete, the following information is displayed:
Please input the file attribute (main/backup/none):none done!
6. Repeat steps 1 to 5 for each of the remaining files (.app, .btm, and .cfg files can be download via this method).
17
3. Select option 2 to set the baud rate to 19200. 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!
18