HP 7500-CMW520-R6703 Release Notes © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Noth ing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
Contents Important information ·········································································································································································1 Version information ·············································································································································································1 Version number ····································································································
Upgrading an IRF fabric ················································································································································27 Upgrade from the boot menu ·················································································································································32 Boot menu ····························································································································································
List of Tables Table 1 Version history ...................................................................................................................... 1 Table 2 HP A-MSR product family matrix ............................................................................................. 2 Table 3 Hardware and software compatibility matrix............................................................................ 2 Table 4 ISSU Compatibility matrix ......................................................
This document describes the features, restrictions and guidelines, open problems, and workarounds for version R6703. Before you use this version in a live network, back up the configuration and test the version to avoid software upgrade affecting your live network. Use this document in conjunction with HP 7500-CMW520-R6703 Release Notes (Software Feature Changes) and the documents listed in "Related documentation.
Version number Last version Release date Release type Remarks 7500-CMW5 20-R6626 S7500E-CMW 520-R6616P0 5 2011-0711 New Release Fixes bugs S7500E-CM W520-R6616 P05 S7500E-CMW 520-R6616P0 2 2011-0503 None Fixes bugs S7500E-CM W520-R6616 P02 S7500E-CMW 520-R6616P0 1 2010-1230 None Fixes bugs S7500E-CM W520-R6616 P01 S7500E-CMW 520-R6616 2010-1108 None Fixes bugs S7500E-CM W520-R6616 S7500E-CMW 520-F6615 2010-0813 None Fixes bugs Hardware and software compatibility
Item Specifications HP 7502/7503-S/7503/7506/7506-V/7510 Hardware platform 3Com S7902E/S7903E/S7906E/S7906E-V/S7910E H3C S7502E/S7503E-S/S7503E/S7506E/S7506E-V/S7510E Minimum memory requirements 512M Minimum Flash requirements 64M Shipped with the switch. Boot ROM image (Use the display version command in any view to view the BootRom version. See Note②) System software image 7500-CMW520-R6703.app iMC EAD 5.1 SP1 (E0301P03) iMC MVM 5.1 SP1 (E0201P01) iMC NTA 5.1 (E0201) iMC PLAT 5.
Release Version: HP 7503-6703 Patch Version None : Slot 1 Without Board Slot 2 Without Board LPU 3: Uptime is 0 weeks,0 days,8 hours,18 m inutes HP 7503 LPU with 1 BCM1122 Processor BOARD TYPE: LSQ1GV48SC DRAM: 512M bytes FLASH: 0M bytes NVRAM: 0K bytes PCB 1 Version: VER.
7500-CMW520-F6702 F6702 supports the following new hardware: None 7500-CMW520-R6701 R6701 supports the following new hardware: None 7500-CMW520-R6635 R6635 supports the following new hardware: JD238B HP 7510 Switch Chassis JD241B HP 7506 Vertical Switch Chassis JD239B HP 7506 Switch Chassis JD240B HP 7503 Switch Chassis JD242B HP 7502 Switch Chassis JD243B HP 7503 Switch Chassis w/1 Fabric Slot JD197B HP 7500 48-port 100Base-FX SA Module JD198B HP 7500 48-port 10/100Ba
JC669A HP 7500 20-port Gig-T / 4-port GbE Combo PoE-upgradable SC Module JD191A HP 7500 8-port 10-GbE XFP SD M odule JC713A HP 7500 8-port 10-GbE XFP SD TAA-compliant M odule JD229B HP 7500 48-port Gig-T PoE+ SD Module JC712A HP 7500 48-port Gig-T PoE+ SD TAA-compliant Module JD230A HP 7500 24-port GbE SFP / 2-port 10-GbE XFP SD Module JC714A HP 7500 24-port GbE SFP / 2-port 10-GbE XFP SD TAA-compliant Module JD236A HP 7500 2-port 10-GbE XFP SD Module JD234A HP 7500 16-por
Item MIB file Module Description entPhysicalSoftw areRev hh3c-entity-vendortype-oid .mib ENTITY-MIB Removing "A" from 7500 entPhysicalMod elName hh3c-entity-vendortype-oid .mib ENTITY-MIB Removing "A" from 7500 entPhysicalVend orType hh3c-entity-vendortype-oid .mib ENTITY-MIB Removing "A" from 7500 hh3cLswSlotSoft wareVersion hh3c-lsw-dev-adm.mib HH3C-LSW-DEV-ADM-MIB Removing "A" from 7500 Operation changes Operation changes in 7500-CMW520-R6703 None Restrictions and cautions 1.
saved-configuration (filename)” command before rebooting to the old code. Then, after the code has been downgraded, the device can be logged in from the console or by Telnet, but not SSH. The SSH authentication details will need to be reset. If no backup configuration has been saved but it is still possible to access the device management via some method while running the old code (e.g. Console, Telnet or SSH), then you can redefine all the device management passwords as required.
LSD071172 Symptom: Portal authentication is unavailable when the MPU modifies portal authentication settings. Condition: This symptom might occur if portal authentication settings are modified when CPU usage is high. LSD070985 Symptom: BGP route calculation occupies too many CPU resources during link switchover or fallback. Condition: This symptom might occur if many BGP route reflectors exist. LSD071729 Symptom: The subordinate device in an IRF fabric reboots.
Resolved problems in F6702 LSD69304 Symptom: Multicast traffic matching new multicast forwarding entries cannot be forwarded. Condition: This symptom might occu r when large numbers of multicast forwarding entries and ARP entries exist. LSD070963 Symptom: GTS and WRED configuration s on a port affect each other.
Resolved problems in R6635 LSD66053 Symptom: The memory leaks. Condition: When Portal is enable and HTTP attack occu rs. LSD66086 Symptom: Run display diagnosis on slave-super-engine, it can’t return. Condition: Run display diagnosis on slave-super-engine. LSD64527 Symptom: The LDP session is not stable. Condition: When the device is linked with other company’s device with VLL. LSD62656 Symptom: BGP neighbors are not stable. Condition: When the CPU is highly occupied.
Condition: None. LSD63186 Symptom: In ftp passive mode, ALG fails when the echo character changes. Condition: In ftp passive mode. LSD62656 Symptom: BGP drops out while keep-alive MSG is received. Condition: None. Resolved problems in R6626 LSD62272 Symptom: RRPP fails to operate when the RRPP control VLAN ID is identical with the sub interface VLAN ID. Condition: When the RRPP control VLAN ID is identical with the sub interface VLAN ID.
Condition: When configuring Policy based routing on LSQ1SRP1CB board or EA cards. LSD58764 Symptom: EA board can not transmit OSPF hello packets, and cause that other devices can not build OSPF neighbors across EA boards. Condition: None. LSD58787 Symptom: M ore CF card types are supported CM W520 -F6618L08. Condition: None. Resolved problems in R6616P02 LSD55210 Symptom: Sometimes IP packets will fail to be forwarded. Condition: When configured the IP FRR function.
Condition: None. LSD49124 Symptom: The MA/MD naming format does not support enough special characters. (In CMW520-R6616, the MA/MD naming format supports more special characters.). Condition: None. LSD52059 Symptom: The multicast stream cannot be sampled by sflow in EB/SD line-card. Condition: None.
After registering, you will receive email notification of product enhancements, new driver versions, firmware updates, and other product resources.
Appendix A Feature list Hardware features Table 6 HP 7500 series hardware features Item Specification HP 7502: 175 x 436 x 420 mm (6.89 x 17.17 x 16.54 in.) HP 7503-S: 175 x 436 x 420 mm (6.89 x 17.17 x 16.54 in.) Dimensions (H × W × D) (excluding feet and rack-mounting brackets) HP 7503: 441.7 x 436 x 420mm (17.39 x 17. 17 x 16.54 in.) HP 7506: 575.05 x436 x 420mm (22.64 x 17.17 x 16.54 in.) HP 7506-V: 930.6 x 436 x 420mm (36.64 x 17. 17 x 16.54 in.)) HP 7510: 708.4 x 436 x 420mm (27.89 x 17. 17 x 16.
Item Specification 6 slots (HP 7506-V) 10 slots (HP 7510) Software features Table 7 Software features of the HP 7500 series Category Features Ethernet II IEEE 802.3/802.2 SNAP IEEE 802.3/802.2 Long Frame (1518-1536) Jumbo Frame (1536-9216) VLAN (Port-based VLAN/Subnet-based VLAN/Protocol-based VLAN/Mac-based VLAN) IEEE 802.1Q Layer 2 IEEE802.1p RSTP(802.1w) MSTP(802.1s) LACP(802.
Category Features Static route management RIP OSPF BGP IS-IS Policy based routing IPv6 routing: IPv6 static route management RIPng OSPFv3 BGP+ IS-ISv6 IGMP Snooping IGMP MLD Snooping MLD Multicast PIM-DM PIM-SM PIM-SSM BIDIR-PIM MSDP Remark 802.1p, DSCP, IP precedence, or local precedence by ACL rule Map to output queue by 802.
Category Features NetStream RMON Public MIBs Private MIBs Syslog/Debug IMC CLI Local management File management Dual-image Console login AUX login User access control Telnet (VTY) login SSH login FTP login XMODEM Ping DNS client DHCP server DHCP client DHCP relay agent Application protocols DHCP snooping Telnet FTP client FTP server TFTP client NTP client/server VRRP Availability Dual fabric IRF ISSU RADIUS TACACS+ Security EAD Portal 802.
20
Appendix B Software Upgrade CAUTION: Upgrade software only when necessary and under the guidance of a technical support engineer. Software used for upgrade Boot ROM images Boot ROM images are used to upgrade the Boot ROM program of cards, including the ma in processing units (MPUs) and line processing units (LPUs). A Boot ROM image is a .btw file. NOTE: Generally, there is no need to upgrade the Boot ROM program independently. The device uses the shipped Boot ROM program.
Upgrade mode In-Service Software Upgrade (ISSU) Obje ct Remarks System software This method uses an active/standby switchover mechanism to complete upgrade and does not interrupt services. For more information about ISSU, see the Fundamentals Configuration Guide in the HP 7500 Switch Series Configuration Guides. NOTE: HP recommends you to upgrade software from the CLI when your switch operates normally.
NOTE: You only need to upgrade the active MPU if the device has no standby MPU. # Check the free storage space on the active and standby MPUs. On the active MPU dir Directory of flash:/ 0 -rw- 3597 Sep 01 2009 18:35:28 startup.cfg 1 -rw- 2 -rw- 6625 Jun 02 2010 16:50:51 switch.cfg 27475851 Aug 11 2010 11:04:20 switch001.app 3 -rw- 31782388 Jul 23 2010 09:25:21 switch002.
You can download the .app file through FTP or TFTP. The following illustrates how to download through FTP when the switch serves as the FTP client and a PC serves as the FTP server. 1. Run the FTP server p rogram on the PC (assume its IP address is 10.10.110.1) and configure the username, password, and file storage directory. 2. Download the .app file (newest.app for example) to the active MPU of the switch. # Log in to the PC through FTP. ftp 10.10.110.1 Trying ...
Upgrade Boot ROM Upgrade system software Install patches 1. Upgrade Boot ROM # Upgrade the Boot ROM for the active MPU in slot 0. bootrom update file flash:/newboot.btw slot 0 This command will update bootrom file on the specified board(s), Continue? [Y/N]:y Now updating bootrom, please wait... Start accessing bootflash chip... Bootrom update succeeded in slot 0. # Upgrade the Boot ROM for the standby MPU in slot 1. bootrom update file slot1#flash:/newboot.
# Specify the file newest.app as the main system software image to be used at the next sta rtup of the active MPU. boot-loader file flash:/newest.app slot 0 main This command will set the boot file of the specified board. Continue? [Y/N]:y The specified file will be used as the main boot file at the next reboot on slot 0! # Specify the file newest.app as the main system software image to be used at the next sta rtup of the standby MPU. boot-loader file slot1#flash:/newest.
Upgrading an IRF fabric Upgrade prerequisites # Telnet to the switch or log in through the console port. # Display device information.
Directory of chassis2#slot0#flash:/ 0 -rw- 3597 Sep 01 2009 18:35:28 startup.cfg 1 -rw- 6625 Jun 02 2010 16:50:51 switch.cfg 2 -rw- 27475851 Aug 11 2010 11:04:20 switch002.app 64389 KB total (31788 KB free) On the standby MPU in slot 1 of member device 2 dir chassis2#slot1#flash:/ Directory of chassis2#slot1#flash:/ 0 -rw- 1 -rw- 2 -rw- 3597 Sep 01 2009 18:35:28 startup.cfg 6625 Jun 02 2010 16:50:51 switch.cfg 27475851 Aug 11 2010 11:04:20 switch002.
Trying ... Press CTRL+K to abort Connected to 10.10.110.1 220 3Com 3CDaemon FTP Server Version 2.0 ---Type the username. User(10.10.110.1:(none)):username 331 User name ok, need password ---Enter the passw ord. Password: 230 User logged in # Set the file transfer mode to binary. [ftp] binary 200 Type set to I. # Download the .app file from the PC to the root directory of the storage medium on the active MPU of the IRF fabric. [ftp] get newest.app 227 Entering Passive Mode (10,10,110,1,17,97).
NOTE: Make sure that the upgrade files exist in the root directory of the storage mediu m of the active and standby MPUs of the IRF fabric. Perform the following tasks as needed: Upgrade Boot ROM Upgrade system software Install patches 1. Upgrade Boot ROM # Upgrade the Boot ROM program of the active MPU of the IRF fabric. bootrom update file flash:/newboot.
NOTE: You cannot upgrade the Boot ROM program of the LPUs on the member switches of an IRF fabric. The Boot ROM image stored on the active MPU of the IRF fabric can be used to upgrade the active MPU and LPUs of the IRF fabric, while that stored on a standby MPU of the IRF fabric can be used to upgrade the standby MPU only. 2. Upgrade system software # Specify the file newest.app as the main system software image to be used at the next sta rtup of the active MPU of the IRF fabric.
Patches will be installed. Continue? [Y/N]:y Do you want to continue running patches after reboot? [Y/N]:y Installing patches........ Installation completed, and patches will continue to run after reboot. NOTE: A patch file must have a valid name. Otherwise, the system cannot identify and install it. Table 8 shows the default names of patch files. For more information about patch installation, see Fundamentals in the HP 7500 Switch Series Configuration Guides.
Mac Address : 0023895F954F Press Ctrl+B to enter Boot Menu...2 NOTE: To enter the boot menu, press Ctrl+B within 5 seconds when you see "Press Ctrl+B to enter Boot Menu..." If you failed to do so, restart the switch and try again. The output varies with switch models. Press Ctrl+B. The system prompts you to enter the Boot ROM password: Please input BootRom password: Enter the password and the boot menu appears.
3. Set XMODEM protocol parameters 4. Update through file in device 0. Return to boot menu Enter your choice(0-4): Step4 In the Boot ROM update menu, type 1 to set the TFTP parameters. BootRom update menu: 1. Set TFTP protocol parameters 2. Set FTP protocol parameters 3. Set XMODEM protocol parameters 4. Update through file in device 0. Return to boot menu Enter your choice(0-4):1 Load File name :newboot.btw Switch IP address :10.10.10.2 Server IP address :10.10.10.3 The name of the target .
3: Display all files in device 4: Delete file from device 5: Modify bootrom password 0: Reboot Enter your choice(0-5):0 Step9 Type 0 to reboot the switch. NOTE: The new Boot ROM version takes effect after the reboot. Using FTP through the management Ethernet port Step1 Connect the management Ethernet port of the switch to the PC that stores the target .app file (the IP address of the PC is required), and connect the console port of the switch to the same or another PC.
Step5 After you set the FTP parameters and press Enter, the switch starts to download the upgrade file. When the file is su ccessfully downloaded, the following information appears: Loading...........done! Will you Update Basic BootRom? (Y/N): Step6 Answer Y to the question. The following information appears: Will you Update Basic BootRom? (Y/N): Y Updating Basic BootRom..........done! Updating extended BootRom? (Y/N): Step7 Answer Y to the question.
0. Return to boot menu Enter your choice(0-4): Step3 In the Boot ROM update menu, type 3 to set the Xmodem parameters: BootRom update menu: 1. Set TFTP protocol parameters 2. Set FTP protocol parameters 3. Set XMODEM protocol parameters 4. Update through file in device 0. Return to boot menu Enter your choice(0-4):3 Please select your download baudrate: 1.*9600 2. 19200 3. 38400 4. 57600 5. 115200 0. Exit Enter your choice (0-5):2 Step4 Select an appropriate download baud rate.
Figure 1 The Switch Properties dialog box 38
Figure 2 The console port properties dialog box Step7 Click Conne ct to re-connect to the switch. The following information appears: Now please start transfer file with XMODEM protocol. If you want to exit, Press Downloading ...CCCCCCCCCCCCCCC Step8 Select Transfer > Send File in the HyperTerminal window. In the Send File dialog box that appears, click Browse to select the target .app file, and select Xmodem as the protocol. Figure 3 The Send File dialog box Step9 Click Send.
Figure 4 The Xmodem file send for Switch dialog box Step10 When the file is successfully downloaded, the following information appears: Loading...........done! Will you Update Basic BootRom? (Y/N): Step11 Answer Y to the question. The following information appears: Will you Update Basic BootRom? (Y/N): Y Updating Basic BootRom..........done! Updating extended BootRom? (Y/N): Step12 Answer Y to the question. The following information appears: Updating extended BootRom? (Y/N):Y Updating extended BootRom...
Enter your choice(0-5):0 Step14 Type 0 to reboot the switch. NOTE: After the reboot, you must change the baud rate for HyperTerminal back to 9600 bps by following Step 5 and Step 6. Using an upgrade file on the switch Step1 Connect the console port of the switch to a PC. Step2 Run the terminal emulation program on the PC. Start the switch, enter the boot menu (see Boot menu for more information), and press Ctrl+U when you see "Enter your choice(0 -5):" to enter the Boot ROM update menu.
Step7 Answer Y to the question. The following information appears: Updating Basic BootRom..........done! Updating extended BootRom? (Y/N): Step8 Answer Y to the question. The following information appears: Updating extended BootRom...........done! BootRom update menu: 1. Set TFTP protocol parameters 2. Set FTP protocol parameters 3. Set XMODEM protocol parameters 4. Update through file in device 0. Return to boot menu Enter your choice(0-4):0 Step9 Type 0 to return to the b oot menu.
Step3 Run the terminal emulation program on the PC connected to the console port. Start the switch, enter the boot menu (see Boot menu for more information), and type 1 when you see "Enter your choice(0 -5):" to enter the download protocol menu. BOOT MENU 1. Download application file to device 2. Select application file to boot 3. Display all files in device 4. Delete file from device 5. Modify BootRom password 0.
Step7 Type 0 to return to the b oot menu. After the .app file is successfully downloaded, set the file as the main or backup system software image. For more information, see Set new main and backup system software images. 2. Using FTP through the management Ethernet p ort Step8 Connect the management Ethernet port of the switch to the PC that stores the target .app file (the IP address of the PC is required), and connect the console port of the switch to the same or another PC.
Free space: 37584896 bytes Writing flash.................................................................. ............................................................................... ..........................done! The attribute of old.app is changed from main to none! done! 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):0 Step14 Type 0 to return to the b oot menu. After the .
4. 57600 5. 115200 0. Exit Enter your choice (0-5):2 Step19 Select an appropriate download baud rate. For example, type 2 to select 19200 bps. The following information appears: Please change the terminal's baudrate to 19200 bps and select XMODEM protocol. Press ENTER key when ready. NOTE: If you select the baud rate of 9600 bps, directly go to Step 8. Step20 Disconnect HyperTerminal from the switch by clicking Disconne ct in the HyperTerminal window.
Figure 6 Console port properties dialog box Step8 Click Conne ct to re-connect to the switch. The following information appears: Now please start transfer file with XMODEM protocol. If you want to exit, Press Downloading ...CCCCCCCCCCCCCCC Step9 Select Transfer > Send File in the HyperTerminal window. In the Send File dialog box that appears, click Browse to select the target .app file, and select Xmodem as the protocol. Figure 7 The Send File dialog box Step10 Click Send.
Figure 8 The Xmodem file send for Switch dialog box Step11 When the file is successfully downloaded, the following information appears: Loading ...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC.done ! Free flash Space : 65932288 bytes Writing flash.......................................
The switch uses the main system software image in normal cases, and uses the backup system software image when the main system software image is invalid. Follow these steps to set the new main and backup system software images: Step1 In the boot menu, type 2 to enter the system software image menu. Flash:/ Number. Size(B) Time Name =============================================================================== 1 27451869 Jul/29/2010 17:35:17 newest.
The following might occur at the switch sta rtup: 1. The switch starts up with the ma in system softwa re image. 2. The main system software image is faulty and the switch starts up with the backup system software image. 3. Both the main and backup system software images are faulty and the switch picks a random system software image and starts up with it. 4.
