HP 7500-CMW520-R6708 Release Notes

Transcription

1 HP 7500-CMW520-R6708 Release Notes Copyright 2013 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. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. The information in this document is subject to change without notice.

2 Contents Version information 1 Version number 1 Version history 1 Hardware and software compatibility matrix 2 ISSU Version Compatibility Matrix 4 Upgrading restrictions and guidelines 4 Hardware feature updates CMW520-R CMW520-F6707L CMW520-F6705L CMW520-R CMW520-F CMW520-R CMW520-R Software feature and command updates 7 MIB updates 7 Operation changes 8 Operation changes in 7500-CMW520-R Operation changes in 7500-CMW520-F6707L02 8 Operation changes in 7500-CMW520-F Operation changes in 7500-CMW520-F6705L01 8 Operation changes in 7500-CMW520-R Restrictions and cautions 8 Open problems and workarounds 9 List of resolved problems 9 Resolved problems in R Resolved problems in F6707L02 10 Resolved problems in F Resolved problems in F6705L01 11 Resolved problems in F Resolved problems in R Resolved problems in F Resolved problems in R Resolved problems in R Resolved problems in F Resolved problems in F Resolved problems in R Resolved problems in R6616P05 15 Resolved problems in R6616P02 16 Resolved problems in R6616P01 16 Resolved problems in R Related documentation 17 Documentation set 17 Obtaining documentation 17 i

3 Contacting HP 17 Subscription service 17 Appendix A Feature list 18 Hardware features 18 Software features 19 Appendix B Software Upgrade 23 Software used for upgrade 23 Upgrade methods 23 Upgrade from the CLI 24 Upgrading a standalone switch 24 Upgrading an IRF fabric 28 Upgrade from the boot menu 34 Upgrading Boot ROM from the boot menu 34 Upgrading system software from the boot menu 42 Upgrade from the boot menu 50 Accessing the Boot ROM menu 50 Using the BASIC-BOOTROM menu 51 Using the EXTEND-BOOTROM menu 55 Handling upgrade failures 61 ii

4 List of Tables Table 1 Version history... 1 Table 2 HP 7500 product family matrix... 2 Table 3 Hardware and software compatibility matrix... 3 Table 4 ISSU Compatibility matrix... 4 Table 5 MIB updates... 7 Table 6 HP 7500 series hardware features Table 7 Software features of the HP 7500 series Table 8 Patch files for different types of cards Table 9 MPU information of the IRF fabric Table 10 Boot ROM shortcut keys Table 11 BASIC-BOOTROM menu options Table 12 BASIC-ASSISTANT menu Table 13 EXTEND-BOOTROM menu options Table 14 EXTEND-ASSISTANT menu options iii

5 This document describes the features, restrictions and guidelines, open problems, and workarounds for version R6708 & R6708-US. In the interest of brevity, any reference to R6708 is also applicable to R6708-US for the remainder of this document. 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-R6708 Release Notes (Software Feature Changes) and the documents listed in "Related documentation." Version information Version number Comware software, Version , Release 6708 Note: You can see the version number with the command display version in any view. Please see Note 1. Version history Table 1 Version history Version number Last version Release date Release type Remarks 7500-CMW5 20-R CMW52 0-F6707L Release New feature: Password Recovery; Syslog record; SCP Fixes bugs 7500-CMW5 20-F6707L CMW52 0-F Feature New feature: OSPFv3 NSSA; EPC; M6VPN; 4096 loopback Fixes bugs 7500-CMW5 20-F CMW52 0-F6705L Feature New feature: Route recursion; BFD, FIPS Fixes bugs 7500-CMW5 20-F6705L CMW52 0-F Feature Fixes bugs 7500-CMW5 20-F CMW52 0-R Feature New feature: Auto configuration backup; Delaying MAC auth; Link-group; password related modification; OSPF MD5 auth. Fixes bugs 7500-CMW5 20-R CMW52 0-F Release New feature: Route optimization; Displaying per-port queue-based traffic statistics Fixes bugs 7500-CMW5 20-F CMW52 0- R Feature New feature: sflow for VPN; 802.1X for VLAN groups; MAC authentication critical VLAN; 31-bit subnet mask; source IP conflict prompt; DSCP value for protocol packets Fixes bugs 7500-CMW5 20-R CMW52 0- R New Release Fixes bugs 1

6 Version number Last version Release date Release type Remarks 7500-CMW5 20-R CMW52 0- F Release Fixes bugs 7500-CMW5 20-F CMW52 0- F Feature Fixes bugs 7500-CMW5 20-F CMW52 0- R Feature New Feature: critical VLAN Fixes bugs 7500-CMW5 20-R6626 S7500E-CMW 520-R6616P New Release Fixes bugs S7500E-CM W520-R6616 P05 S7500E-CMW 520-R6616P None Fixes bugs S7500E-CM W520-R6616 P02 S7500E-CMW 520-R6616P None Fixes bugs S7500E-CM W520-R6616 P01 S7500E-CMW 520-R None Fixes bugs S7500E-CM W520-R6616 S7500E-CMW 520-F None Fixes bugs Hardware and software compatibility matrix Before HP 7500 family, there were another 2 product families, i.e. 3Com 7900E and H3C S7500E, shipped to market. All of these three product families have same hardware and software specification except brand. The product matrix is as following. In brief, the HP 7500 SKU will be the representation to all of them in subsequent document. Table 2 HP 7500 product family matrix HP product code HP Com 7900E H3C S7500E JD242B HP Com S7902E H3C S7502E JD243B HP 7503-S None H3C S7503E-S JD240B HP Com S7903E H3C S7503E JD239B HP Com S7906E H3C S7506E JD241B HP 7506-V 3Com S7906E-V H3C S7506E-V JD238B HP Com S7910E H3C S7510E CAUTION: To avoid an upgrade failure, use Table 3 to verify the hardware and software compatibility before performing an upgrade. 2

7 Table 3 Hardware and software compatibility matrix Item Product family Hardware platform Minimum memory requirements Minimum Flash requirements Boot ROM image System software image IMC version inode version SecBlade FW SecBlade NSM SecBlade LB SecBlade SSL VPN Specifications HP 7500 series, 3Com S7900E series and H3C S7500E series HP 7502/7503-S/7503/7506/7506-V/7510 3Com S7902E/S7903E/S7906E/S7906E-V/S7910E H3C S7502E/S7503E-S/S7503E/S7506E/S7506E-V/S7510E 512M 64M Shipped with the switch. (Use the display version command in any view to view the BootRom version. See Note2) 7500-CMW520-R6708.app imc EAD 5.1 SP1 (E0301P03) imc MVM 5.1 SP1 (E0201P01) imc NTA 5.1 (E0201) imc PLAT 5.1 SP1 (E0202P05) imc QoSM 5.1 (E0201) imc TAM 5.1 (E0301) imc UAM 5.1 SP1 (E0301P03) imc UBA 5.1 (E0201) inode PC 5.1 (E0304) and later SECPATH1000FE&SECBLADEII-CMW520-R3166P13 and later SECBLADENSM-CMW520-R3106 and later SECBLADELB-CMW520-R3204P17 and later SECBLADESSLVPN-CMW340-E7111 and later Display the system software and Boot ROM versions: [HP] display version HP Comware Platform Software Comware Software, Version , Release Note1 Copyright (c) Hewlett-Packard Development Company, L.P. HP 7508 uptime is 0 week, 2 days, 19 hours, 14 minutes MPU(M) 0: Uptime is 0 weeks,0 days,8 hours,20 minutes HP 7503 MPU(M) with 1 BCM1125H Processor BOARD TYPE: LSQ1SRP1CB DRAM: 512M bytes FLASH: 64M bytes NVRAM: 512K bytes PCB 1 Version: VER.B PCB 2 Version: VER.B 3

8 Bootrom Version: Note2 CPLD 1 Version: 002 CPLD 2 Version: 002 Release Version: HP Patch Version : None Slot 1 Without Board Slot 2 Without Board LPU 3: Uptime is 0 weeks,0 days,8 hours,18 minutes HP 7503 LPU with 1 BCM1122 Processor BOARD TYPE: LSQ1GV48SC DRAM: 512M bytes FLASH: 0M bytes NVRAM: 0K bytes PCB 1 Version: VER.C Bootrom Version: Note2 CPLD 1 Version: 003 Release Version: HP Patch Version : None ISSU Version Compatibility Matrix Table 4 ISSU Compatibility matrix Current version History version ISSU compatibility 7500-CMW520-R CMW520-F6707L02 Incompatible 7500-CMW520-F CMW520-F6705L CMW520-F CMW520-R CMW520-F6702L CMW520-F CMW520-R CMW520-R6635 or earlier Incompatible Incompatible Incompatible Incompatible Incompatible Incompatible Incompatible Incompatible Upgrading restrictions and guidelines None. 4

9 Hardware feature updates 7500-CMW520-R6708 R6708 supports the following new hardware: None 7500-CMW520-F6707L02 F6707L02 supports the following new hardware: None 7500-CMW520-F6705L01 F6705L01 supports the following new hardware: None 7500-CMW520-R6703 R6703 supports the following new hardware: JC792A HP port 40GbE QSFP+ SC Module JG373A HP port 40GbE CFP SC Module 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 5

10 JD242B HP 7502 Switch Chassis JD243B HP 7503 Switch Chassis w/1 Fabric Slot JD197B HP port 100Base-FX SA Module JD198B HP port 10/100Base-TX PoE-upgradable SA Module JD199C/JD199B HP port Gig-T PoE-upgradable SA Module JC667A HP port GbE SFP / 8-port GbE Combo SA Module JC668A HP port Gig-T / 4-port GbE PoE-upgradable Combo SA Module JD201A HP port 10-GbE XFP SC Module JD203B HP port GbE SFP SC Module JC704A HP port GbE SFP SC TAA-compliant Module JD204B HP port Gig-T SC Module JD205A HP port GbE SFP / 2-port 10-GbE XFP SC Module JD206A HP port Gig-T / 2-port 10-GbE XFP SC Module JD207A HP port GbE SFP SC Module JD210A HP port Gig-T PoE-upgradable SC Module JC709A HP port Gig-T PoE-upgradable SC TAA-compliant Module JD228B HP port Gig-T / 8-port GbE SFP PoE-upgradable SC Module JC710A HP port Gig-T / 8-port GbE SFP PoE-upgradable SC TAA-compliant Module JD223A HP port GbE SFP / 8-port GbE Combo SC Module JD211B HP port GbE SFP SC Module JF290A HP port 10-GbE SFP+ SC Module JC723A HP port 10-GbE SFP+ SC TAA-compliant Module JC669A HP port Gig-T / 4-port GbE Combo PoE-upgradable SC Module JD191A HP port 10-GbE XFP SD Module JC713A HP port 10-GbE XFP SD TAA-compliant Module JD229B HP port Gig-T PoE+ SD Module JC712A HP port Gig-T PoE+ SD TAA-compliant Module JD230A HP port GbE SFP / 2-port 10-GbE XFP SD Module JC714A HP port GbE SFP / 2-port 10-GbE XFP SD TAA-compliant Module JD236A HP port 10-GbE XFP SD Module JD234A HP port GbE SFP / 8-port GbE Combo SD Module JC718A HP port GbE SFP / 8-port GbE Combo SD TAA-compliant Module JD235A HP port 10-GbE XFP SD Module JC719A HP port 10-GbE XFP SD TAA-compliant Module JD237A HP port GbE SFP SD Module JC721A HP port GbE SFP SD TAA-compliant Module JD221A HP port GbE SFP EB Module JD231A HP port GbE SFP / 8-port GbE Combo EB Module JC715A HP port GbE SFP / 8-port GbE Combo EB TAA-compliant Module JD232A HP port 10-GbE XFP EB Module 6

11 JC716A HP port 10-GbE XFP EB TAA-compliant Module JD233A HP port 10-GbE XFP EB Module Software feature and command updates For more information about the software feature and command update history, see HP 7500-CMW520-R6708 Release Notes (Software Feature Changes). MIB updates Table 5 MIB updates Item MIB file Module Description 7500-CMW520-R6708 none none none none none none none none 7500-CMW520-F6707L02 none none none none none none none none 7500-CMW520-F6707 none none none none none none none none 7500-CMW520-F6705L01 none none none none none none none none 7500-CMW520-F6705 none none none none none none none none 7500-CMW520-R6703 none none none none none none none none 7500-CMW520-F6702 none none none none none none none none 7500-CMW520-R6701 sysdescr rfc1213.mib RFC1213-MIB Removing "A" from 7500 sysobjectid rfc1213.mib RFC1213-MIB Removing "A" from 7500 entphysicalsoftw arerev hh3c-entity-vendortype-oid.mib ENTITY-MIB Removing "A" from

12 Item MIB file Module Description entphysicalmod elname entphysicalvend ortype hh3c-entity-vendortype-oid.mib hh3c-entity-vendortype-oid.mib ENTITY-MIB Removing "A" from 7500 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-R6708 If the MPU BootWare version is 500 or higher, HP recommends upgrading the system software to R6708 or higher to get better security protection. For detailed information, see HP 7500-CMW520-R6708 Release Notes (Software Feature Changes) Operation changes in 7500-CMW520-F6707L02 None Operation changes in 7500-CMW520-F6707 Changed the maximum number of BFD sessions to 128 and the default handshake interval to 1 second in IRF mode. For details, please see HP 7500-CMW520-F6707 Release Notes (Software Feature Changes) Operation changes in 7500-CMW520-F6705L01 None Operation changes in 7500-CMW520-R6703 None Restrictions and cautions 1. SFP+ Direct Attach Cables are not recommended for use as IRF connections because failover and recovery times are extended when this form of copper connection is use. Optical IRF connections are recommended to optimize IRF failure, recovery and convergence times. 2. It takes more than half an hour to collect diagnostic information when the IRF has many configuration parameters. 8

13 3. The hp 7500 product family supports four IRF members in R6635. There are several setup and configuration limitation, please check the Command Line Manual and Operation Manual of new release for detail. 4. If you enable multicast ARP and connect the device to an NLB server through an aggregate interface, any port that receives client traffic must not reside on the same card as any member port of the aggregate interface. Open problems and workarounds LSD68672 LSD62272 LSD62435 Symptom: The IRF fabric may split. Condition: Reboot an IRF fabric comprised of four switches. If the switches are not synchronously rebooted. Workaround: Make sure the switches have similar card configurations, can back up each other, and are rebooted at the same time. If the IRF fabric splits, reboot the smallest IRF system so the switches can join the system to re-form a 4-chassis fabric. Symptom: RRPP fails to operate. Condition: If the RRPP control VLAN ID is identical with the subinterface VLAN ID. Workaround: Do not configure the same VLAN ID for them. Symptom: A subinterface fails to forward traffic to another chassis. Condition: If the VLAN ID of subinterface is identical with the MAD VLAN ID. Workaround: Do not configure the same VLAN ID for them. List of resolved problems Resolved problems in R6708 LSD LSD Symptom: If the OSPF LSDB has multiple Type 5 LSAs that describe default routes, the system prompts an error syslog "The default route has been changed or deleted, protocol is OSPF" during OSPF route calculation. Condition: This symptom occurs if the OSPF LSDB has multiple Type 5 LSAs that describe default routes. Symptom: When many ARP and MAC moves occur on ports or VPNs, ARP might occupy the CPU for a long time, and do not answer ARP requests. Condition: This symptom might be seen when many ARP and MAC moves occur on ports or VPNs. Symptom: PBR fails to work when a packet matches two entries in the PBR policy. 9

14 LSD LSD Condition: This symptom occurs if a packet matches two entries in the PBR policy Symptom: Walking the entphysicalvendortype MIB fails to get the transceiver information on the Combo interfaces. Condition: This symptom can be seen during a walk on the entphysicalvendortype MIB. Symptom: The CPU usage on the 40G card is high when the switch operates normally. Condition: This symptom might be seen when the switch operates normally. Resolved problems in F6707L02 LSD LSD LSD LSD LSD Symptom: A user might fail to pass remote AAA authentication, such as dot1x authentication. Condition: This symptom might occur when remote AAA authentication is configured. Symptom: The monitor handshake-timeout disable-port command fails to take effect after a reboot. Condition: This symptom can be seen after a reboot. Symptom: The remark dot1p action for colored packets modifies only the 802.1p priority in VLAN tags, but does not modify the local precedence, which is used for enqueuing packets. Condition: This symptom can be seen when the remark dot1p action is configured. Symptom: BGP does not accept routes with an aggregator ID of Condition: This symptom can be seen when BGP receives a route with an aggregator ID of from a device of another vendor. Symptom: On an SA card, SFTP and SSH packets are forwarded slowly (less than 100 Kbps). Condition: This symptom can be seen when SFTP and SSH packets are forwarded by an SA card. Resolved problems in F6707 LSD LSD Symptom: An SNMP walk on power MIB returns an incorrect value. Condition: This symptom occurs during an SNMP walk on power supply unit related MIB. Symptom: The device generates a useless log "Send PAAT to all IO boards has failed." Condition: This symptom might occur during the startup of a card installed with a specific fiber module. 10

15 Resolved problems in F6705L01 LSD Symptom: By default, some TCP/UDP ports, such as RADIUS, are in Listening state, need to be closed. Condition: The device starts up with default configuration. Resolved problems in F6705 LSD68133 LSD LSD Symptom: In this version of code, the password encryption within configuration files has been enhanced and cannot be interpreted by earlier revisions of the agent code. More details please reference HP 7500-CMW520-F6705 Release Notes (Software Feature Changes). Condition: If a unit is downgraded to earlier code, it may no longer be possible to login and manage the device. Symptom: If an LPU is rebooted when the switch works in IRF mode and uses the SRPA MPU, the LPU might fail to start up. Condition: This symptom might occur when the switch works in IRF mode and uses the SRPA MPU. Symptom: An SA card on a 7502 fails to forward packets. Condition: This symptom might occur when the 7502 has an SA card and an SC card. Resolved problems in R6703 LSD LSD LSD Symptom: The DHCP server supports a maximum of 128 static IP bindings while some scenarios need more static IP bindings. The maximum number should be changed to Condition: This issue exists on the DHCP server. 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. 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. 11

16 LSD LSD LSD Symptom: The subordinate device in an IRF fabric reboots. Condition: This symptom might occur if undo vsi is executed when the state of the peer is changing. Symptom: IMC cannot show the panel of the switch. Condition: This symptom occurs when IMC accesses the switch. Symptom: Track fails to work when PBR needs to perform a nexthop failover. Condition: This symptom might occur if the following conditions exist: PBR has more than two nodes. The two PBR nodes specify two next hops. Track is used to trigger a nexthop failover. Track fails to work when PBR needs to perform a nexthop failover. LSD LSD LSD Symptom: In an IRF fabric, a card that has IRF physical ports continually reboots, which causes continual reboots of the chassis that hosts the card. Condition: This symptom might occur if an unsupported switch-mode is configured for the card, for example, because of manual configuration file editing or member ID renumbering. Symptom: The IRF fabric splits even though the IRF links are up. Condition: After an MPU exception occurs on an IRF member chassis, this symptom might occur if the chassis cannot complete an active/standby switchover before IRF handshaking times out. Symptom: In an IRF fabric, only the global active MPU starts up normally, and all other MPUs stay in STM init state. Condition: This symptom might occur if the IRF fabric is rebooted while the IRF links are flapping. Resolved problems in F6702 LSD69304 LSD Symptom: Multicast traffic matching new multicast forwarding entries cannot be forwarded. Condition: This symptom might occur when large numbers of multicast forwarding entries and ARP entries exist. Symptom: GTS and WRED configurations on a port affect each other. Condition: This symptom might occur if you delete GTS configuration on a port and then configure WRED on the port because the deleted GTS configuration is restored after you configure WRED. 12

17 LSD LSD Symptom: OSPF calculation occupies too many CPU resources when flooding occurs because of LSA aging. Condition: This symptom might occur in an OSPF network where large numbers of routes and OSPF neighbors exist and NSR is enabled. Symptom: The private MIB OID value is 25506(HP), and it should be replaced with 6296(Dasan). Condition: Read the MIB tree of a Dasan device. Resolved problems in R6701 LSD68827 LSD69305 LSD69168 LSD68974 Symptom: MPLS works abnormally. Condition: After a switch reboots, IPC communication may fail, resulting in failure of assigning MPLS forwarding entries to cards. Symptom: An anomaly occurs to the switch. Condition: Configure multiple DHCP Options on the DHCP server. Enable debugging on a switch, and then use the switch as the DHCP client to request configuration information from the DHCP server. Symptom: The switch may reboot abnormally. Condition: Disable MPLS LDP on an interface. Symptom: The cross-chassis forwarding packets will be lost. Condition: An IRF system with SRPD fabric on 7506/7503 chassis. Resolved problems in R6635 LSD66053 LSD66086 LSD64527 Symptom: The memory leaks. Condition: When Portal is enable and HTTP attack occurs. Symptom: Run display diagnosis on slave-super-engine, it can t return. Condition: Run display diagnosis on slave-super-engine. Symptom: The LDP session is not stable. Condition: When the device is linked with other company s device with VLL. 13

18 LSD62656 LSD63920 LSD66072 Symptom: BGP neighbors are not stable. Condition: When the CPU is highly occupied. Symptom: the LLDP neighbor s information is wrong. Condition: When the LLDP packets whose LCI value in location ID TLV is zero enter the device. Symptom: Non-compatible transceiver module will be invalidated in 30 days. Condition: Using Non-compatible transceiver module. Resolved problems in F6632 LSD64002 LSD64635 LSD65234 Symptom: The oui-mac learned from the slave board can t be synchronized to the master board. Condition: When voice-vlan is enabled. Symptom: VRRP conflicts when it receives a wrong SIP ARP request. Condition: When VRRP receives a wrong SIP ARP request. Symptom: ATOS HP Switch 7500E LLDP with Aastra IP phones. Condition: HP Switch 7500E LLDP with Aastra IP phones Resolved problems in F6630 LSD63739 LSD63186 LSD62656 Symptom: Supporting the three requirements about Radius. Condition: None. Symptom: In ftp passive mode, ALG fails when the echo character changes. Condition: In ftp passive mode. Symptom: BGP drops out while keep-alive MSG is received. Condition: None. 14

19 Resolved problems in R6626 LSD62272 LSD62435 LSD58210 LSD59694 LSD59757 LSD61343 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. Symptom: A sub interface fails to forward traffic to another chassis when its VLAN ID is identical with the MAD VLAN ID. Condition: When sub interface s VLAN ID is identical with the MAD VLAN ID. Symptom: BGP fails to learn a private summary route received from a BGP peer because the route does not carry the RT attribute. Condition: None. Symptom: The calculated Q-Bridge MIB port list is incorrect. Condition: None Symptom: Memory error occurs, and the link card fails Condition: When the user parameter information from the RADIUS server contains a 63-byte callback-number. Symptom: After a user passes HWTACACS authentication, the device receives an authorization failure packet. Repeated memory releases occur. Condition: After a user passes HWTACACS authentication, the device receives an authorization failure packet. Resolved problems in R6616P05 LSD57826 LSD58764 LSD58787 Symptom: Policy based routing will fail to set the IP-address next hops. Condition: When configuring Policy based routing on LSQ1SRP1CB board or EA cards. Symptom: EA board can not transmit OSPF hello packets, and cause that other devices can not build OSPF neighbors across EA boards. Condition: None. Symptom: More CF card types are supported CMW520-F6618L08. Condition: None. 15

20 Resolved problems in R6616P02 LSD55210 Symptom: Sometimes IP packets will fail to be forwarded. Condition: When configured the IP FRR function. Resolved problems in R6616P01 LSD53884 LSD53222 LSD53378 LSD53667 Symptom: Sometimes a wrong Multi-Active Detection will occur. Condition: When rebooting one chassis with the LSQ1SRP2XB 10GE ports as IRF ports. Symptom: Sometimes in portal stateful failover function, LSQ1SPRD master card cannot establish the failover link with the other device. Condition: None. Symptom: Sometimes the switch-mode is changed to wrong mode. Condition: When the switch upgrades software from R660X version to R661X version. Symptom: Sometimes the portal dynamic ACL does not work because that it conflicts with other ACL or policy-based routing. Condition: None. Resolved problems in R6616 LSD49278 LSD50343 LSD49124 LSD52059 Symptom: Batch shutdown and undo shutdown operations are not supported. Condition: None. Symptom: Voice VLAN does not support enough OUI MAC addresses. (In CMW520-R6616, voice VLAN supports 128 OUI MAC addresses). Condition: None. 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. Symptom: The multicast stream cannot be sampled by sflow in EB/SD line-card. Condition: None. 16

21 Related documentation Documentation set HP 7500 Switch Series Installation Guide HP 7500 Switch Series Configuration Guides (R6700 series) HP 7500 Switch Series Command References (R6700 series) Obtaining documentation To find related documents, browse to the Manuals page of the HP Business Support Center website: Contacting HP For worldwide technical support information, see the HP support website: Before contacting HP, collect the following information: Product model names and numbers Technical support registration number (if applicable) Product serial numbers Error messages Operating system type and revision level Detailed questions Subscription service HP recommends that you register your product at the Subscriber's Choice for Business website: After registering, you will receive notification of product enhancements, new driver versions, firmware updates, and other product resources. 17

22 Appendix A Feature list Hardware features Table 6 HP 7500 series hardware features Item Dimensions (H W D) (excluding feet and rack-mounting brackets) Weight Input AC voltage Max. power consumption Operating temperature Relative humidity (noncondensing) Service card slots Specification HP 7502: 175 x 436 x 420 mm (6.89 x x in.) HP 7503-S: 175 x 436 x 420 mm (6.89 x x in.) HP 7503: x 436 x 420mm (17.39 x x in.) HP 7506: x436 x 420mm (22.64 x x in.) HP 7506-V: x 436 x 420mm (36.64 x x in.)) HP 7510: x 436 x 420mm (27.89 x x in.) HP 7502:< 15kg (33.07 lb) HP 7503-S:< 15kg (33.07 lb) HP 7503:< 25kg (55.11 lb) HP 7506:< 35kg (77.16 lb) HP 7506-V:< 45kg (99.21 lb) HP 7510:< 45kg (99.21 lb) 90V to 264V, 47/63Hz 223.2W (HP 7502) 238.2W (HP 7503-S) W (HP 7503) 707.2W (HP 7506) W (HP 7506-V) 1074W (HP 7510) 0 to 45 10%~90% 2 slots (HP 7502) 2 slots (HP 7503-S) 3 slots (HP 7503) 6 slots (HP 7506) 18

23 Item Specification 6 slots (HP 7506-V) 10 slots (HP 7510) Software features Table 7 Software features of the HP 7500 series Category Layer 2 Layer 3 Routing Features Ethernet II IEEE 802.3/802.2 SNAP IEEE 802.3/802.2 Long Frame ( ) Jumbo Frame ( ) VLAN (Port-based VLAN/Subnet-based VLAN/Protocol-based VLAN/Mac-based VLAN) IEEE 802.1Q IEEE802.1p RSTP(802.1w) MSTP(802.1s) LACP(802.3ad) GARP/GVRP RRPP Mirror Storm suppression (Broadcast / Multicast / Unknown unicast) PoE IPv4 features: ARP(ARP proxy, Gratuitous ARP) IP datagram forwarding (RFC791/1141/950) IP options (strict source route/loose source route/recording route/timestamp)(rfc791/1122) TCP (RFC793) UDP (RFC768) ICMP RFC1213-MIB (including IP, ICMP, TCP, UDP, IF, SNMP) IPv6 features: IPv6 ND IPv6 FIB IPv6 ACL IPv6 tunnel (manually configured tunnel/ Automatic 6to4 tunnel/isatap) Layer-3 routed interface IPv4 routing: 19

24 Category Multicast ACL&QOS Management 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 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.1p, DSCP, IP precedence, local precedence SP WRR CAR Basic ACL Advanced ACL Link ACL VLAN-based ACL Packet filtering Traffic redirect Traffic shaping Line rate WFQ WRED Traffic accounting Flow-based mirroring Port priority SNMP v1/v2/v3 20

25 Category Local management User access control Application protocols Availability Security MPLS Features NetStream RMON Public MIBs Private MIBs Syslog/Debug IMC CLI File management Dual-image Console login AUX login Telnet (VTY) login SSH login FTP login XMODEM Ping DNS client DHCP server DHCP client DHCP relay agent DHCP snooping Telnet FTP client FTP server TFTP client NTP client/server VRRP Dual fabric IRF ISSU RADIUS TACACS+ EAD Portal 802.1X Port Security MPLS LDP MPLS L3VPN MPLS L2VPN 21

26 22

27 Appendix B Software Upgrade Software used for upgrade Boot ROM images Boot ROM images are used to upgrade the Boot ROM program of cards, including the main processing units (MPUs) and line processing units (LPUs). A Boot ROM image is a.btw file. System software images System software images are used at switch startup. The HP 7500 series support two types of system software image: NOTE: Patch package file Main system software image The default system software image a switch uses for startup. Backup system software image The system software image a switch uses for startup when the main system software image is invalid or does not exist. Generally, there is no need to upgrade the Boot ROM program independently. The device uses the shipped Boot ROM program. The examples in this document use BootWare2.00. The output is for illustration only. Patches for the HP 7500 switches are released in a patch package file. A patch package file fixes certain software defects. It contains patch files for multiple cards. It enables you to use one command to bulk-fix bugs for multiple cards. A patch package file corresponds to the system software image version. A patch package file can only fix defects of the corresponding system software image file, but does not add or delete any functions. Upgrade methods You can upgrade switch software by using one of the following methods: Upgrade mode Object Remarks Upgrade from the CLI Upgrade from the boot menu Boot ROM System software Patches Boot ROM System software Reboot the switch to validate the upgrade. This method interrupts services. This method does not interrupt services, and fixes the target system software only. This method can be used when the switch cannot start up. In-Service Software Upgrade (ISSU) 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. 23

28 NOTE: HP recommends you to upgrade software from the CLI when your switch operates normally. To ensure that the active and standby MPUs use the same software version, upgrade them by using the same method. Make sure the system software and Boot ROM are compatible. For the compatibility between the system software and Boot ROM, see the hardware and software compatibility matrix in the Release Notes. You can upgrade the Boot ROM for the LPUs from the CLI only. The command outputs in this document are for reference only. Generally, use incompatible ISSU to upgrade software to this version. Compatible ISSU is applicable only to specific restricted versions. If compatible ISSU is needed, contact the technical support engineer. Upgrade from the CLI The upgrade procedure on a standalone switch is different from that on an Intelligent Resilient Framework (IRF) fabric. This section describes the following topics: NOTE: Upgrading a standalone switch Upgrading an IRF fabric Up to two 7500 series switches can form a distributed IRF fabric. One switch is the master, and the other is the slave. Upgrading a standalone switch Upgrade prerequisites # Telnet to the switch or log in through the console port. # Display device information. <Sysname> display device Slot No. Brd Type Brd Status Subslot Num Sft Ver Patch Ver 0 LSQ1SRP1CB Master None 1 LSQ1SRP1CB Slave None 2 NONE Absent 0 NONE None 3 LSQ1GV48SC Normal None 4 LSQ1GV48SC Normal None The output shows that the switch has two MPUs, an active MPU in slot 0 and a standby MPU in slot 1. You must upgrade software for the two MPUs. 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 <Sysname> dir 24

29 Directory of flash:/ 0 -rw Sep :35:28 startup.cfg 1 -rw Jun :50:51 switch.cfg 2 -rw Aug :04:20 switch001.app 3 -rw Jul :25:21 switch002.app KB total (5636 KB free) On the standby MPU <Sysname> dir slot1#flash:/ Directory of slot1#flash:/ 0 -rw Sep :35:28 startup.cfg 1 -rw Jun :50:51 switch.cfg 2 -rw Aug :04:20 switch001.app 3 -rw Jul :25:21 switch002.app KB total (5636 KB free) Check that the free storage space is sufficient for the new.app file. You can delete undesired files with the delete command to free storage space. # Delete undesired files from the active and standby MPUs. On the active MPU <Sysname> delete /unreserved flash:/switch001.app The content cannot be restored!!! Delete flash:/switch001.app?[y/n]:y Deleting a file permanently will take a long time. Please wait... %Delete file flash:/switch001.app...done. On the standby MPU <Sysname> delete /unreserved slot1#flash:/switch001.app The content cannot be restored!!! Delete slot1#flash:/switch001.app?[y/n]:y Deleting a file permanently will take a long time. Please wait... %Delete file slot1#flash:/switch001.app...done. NOTE: The delete /unreserved file-url command deletes a file permanently and the action cannot be undone. The delete file-url command moves a file to the recycle bin and the file still occupies storage space. To permanently delete the file from the recycle bin, execute the reset recycle-bin command in the original directory of the file. Download the.app file to the switch Download the.app file to the storage medium (such as flash memory) of the active MPU and that of the standby MPU. Skip this section if the file is already located there. 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 program on the PC (assume its IP address is ) 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. 25

30 <Sysname> ftp Trying... Press CTRL+K to abort Connected to Com 3CDaemon FTP Server Version 2.0 User( :(none)):username 331 User name ok, need password Password: 230 User logged in ---Type the username. ---Enter the password. # 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. [ftp] get newest.app 227 Entering Passive Mode (10,10,110,1,17,97). 125 BINARY mode data connection already open, transfer starting for /newest.app 226 Transfer complete. FTP: byte(s) received in second(s), K byte(s)/sec. [ftp] bye 221 Server closing. 3. Copy the.app file to the standby MPU of the switch. # Copy the file newest.app to the root directory of the storage medium on the standby MPU in slot 1. <Sysname> copy newest.app slot1#flash:/ Copy flash:/newest.app to slot1#flash:/newest.app?[y/n]:y %Copy file flash:/newest.app to slot1#flash:/newest.app...done. NOTE: You can configure the switch as the FTP server, FTP client, or TFTP client. The transfer processes slightly vary. For more information about FTP and TFTP, see the Fundamentals Configuration Guide in the HP 7500 Switch Series Configuration Guides. You can use the transfer procedure described in this section to transfer Boot ROM images, system software images, and patch files for upgrade from the CLI. Upgrade software from the CLI CAUTION: Make sure that the.app file exists in the root directory of the storage medium of the active MPU and the standby MPU. Perform the following tasks as needed: Upgrade Boot ROM Upgrade system software Install patches 1. Upgrade Boot ROM # Upgrade the Boot ROM for the active MPU in slot 0. 26

31 <Sysname> 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. <Sysname> bootrom update file slot1#flash:/newboot.btw slot 1 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 1. # Upgrade the Boot ROM for the LPU in slot 3. <Sysname> bootrom update file flash:/newboot.btw slot 3 This command will update bootrom file on the specified board(s), Continue? [Y/N]:y Now updating bootrom, please wait... Board has finished loading file on Chassis 0 Slot 3. Start accessing bootflash chip... Bootrom update succeeded in slot 3. # Upgrade the Boot ROM for the LPU in slot 4. <Sysname> bootrom update file flash:/newboot.btw slot 4 This command will update bootrom file on the specified board(s), Continue? [Y/N]:y Now updating bootrom, please wait... Board has finished loading file on Chassis 0 Slot 4. Start accessing bootflash chip... Bootrom update succeeded in slot 4. # Reboot the switch to validate the upgrade. <Sysname> reboot Start to check configuration with next startup configuration file, please wait....done! This command will reboot the device. Continue? [Y/N]:y NOTE: The Boot ROM image stored on the active MPU can be used to upgrade both the active MPU and LPUs, while that stored on the standby MPU is 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 startup of the active MPU. <Sysname> 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! 27

32 # Specify the file newest.app as the main system software image to be used at the next startup of the standby MPU. <Sysname> boot-loader file slot1#flash:/newest.app slot 1 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 1! # Reboot the switch to validate the upgrade. <Sysname> reboot Start to check configuration with next startup configuration file, please wait....done! This command will reboot the device. Continue? [Y/N]:y CAUTION: To prevent configuration loss, save the latest configuration changes before you reboot the switch. System software images must be saved in the root directory of the storage medium. You can copy or move system software images to the root directory. For more information about the boot-loader command, see Fundamentals Command Reference in the HP 7500 Switch Series Command References. 3. Install patches # Download the patch files to the root directory of the storage medium of the active MPU and that of the standby MPU, and then install the patch files with the patch install command. <Sysname> system-view [Sysname] patch install flash: 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 the Fundamentals Configuration Guide in the HP 7500 Switch Series Configuration Guides. Table 8 Patch files for different types of cards Card type MPU LPU Auxiliary CPU on a LPU Default patch file name patch_mpu.bin patch_lpu.bin patch_lpo.bin Upgrading an IRF fabric Upgrade prerequisites # Telnet to the switch or log in through the console port. # Display device information. 28

33 <Sysname> display device Chassis Slot Type State Subslot Soft Ver Patch Ver 1 0 LSQ1SRP1CB Master None 1 1 LSQ1SRP1CB Slave None 1 2 LSQ1TGX4SD Normal None 1 3 LSQ1TGX4SD Normal None 1 4 LSQ1TGX4SD Normal None 2 0 LSQ1SRP1CB Slave None 2 1 LSQ1SRP1CB Slave None 2 2 LSQ1TGX4SD Normal None 2 3 LSQ1TGX4SD Normal None 2 4 LSQ1TGX4SD Normal None The output shows that two switches form an IRF fabric. The following table shows the MPU information. Table 9 MPU information of the IRF fabric MPU Member ID Slot number Active MPU of the IRF fabric 1 0 Standby MPU of the IRF fabric 1 1 Standby MPU of the IRF fabric 2 0 Standby MPU of the IRF fabric 2 1 # Check the free storage space of the active and standby MPUs on the IRF fabric. On the active MPU of the IRF fabric <Sysname> dir Directory of flash:/ 0 -rw Sep :35:28 startup.cfg 1 -rw Jun :50:51 switch.cfg 2 -rw Aug :04:20 switch001.app 3 -rw Jul :25:21 switch002.app KB total (5636 KB free) On the standby MPU in slot 1 of member device 1 <Sysname> dir chassis1#slot1#flash:/ Directory of chassis1#slot1#flash:/ 0 -rw Sep :35:28 startup.cfg 1 -rw Jun :50:51 switch.cfg 2 -rw Aug :04:20 switch001.app 3 -rw Jul :25:21 switch002.app KB total (5636 KB free) On the standby MPU in slot 0 of member device 2 <Sysname> dir chassis2#slot0#flash:/ Directory of chassis2#slot0#flash:/ 0 -rw Sep :35:28 startup.cfg 1 -rw Jun :50:51 switch.cfg 2 -rw Aug :04:20 switch002.app KB total (31788 KB free) On the standby MPU in slot 1 of member device 2 29

34 <Sysname> dir chassis2#slot1#flash:/ Directory of chassis2#slot1#flash:/ 0 -rw Sep :35:28 startup.cfg 1 -rw Jun :50:51 switch.cfg 2 -rw Aug :04:20 switch002.app KB total (31788 KB free) Check that the free storage space is sufficient for the files used for upgrade. You can delete undesired files with the delete command to free storage space. # Delete undesired files from the active and standby MPUs of the IRF fabric. On the active MPU of the IRF fabric <Sysname> delete /unreserved flash:/switch001.app The content cannot be restored!!! Delete flash:/switch001.app?[y/n]:y Deleting a file permanently will take a long time. Please wait... %Delete file flash:/switch001.app...done. On the standby MPU in slot 1 of member device 1 <Sysname> delete /unreserved chassis1#slot1#flash:/switch001.app The content cannot be restored!!! Delete file chassis1#slot1#flash:/switch001.app?[y/n]:y Deleting a file permanently will take a long time. Please wait... %Delete file chassis1#slot1#flash:/switch001.app...done. NOTE: The delete /unreserved file-url command deletes a file permanently and the action cannot be undone. The delete file-url command moves a file to the recycle bin and the file still occupies storage space. To permanently delete the file from the recycle bin, execute the reset recycle-bin command in the original directory of the file. Download the.app file to the IRF fabric Download the.app file to the storage medium (such as flash memory) of the active MPU and that of each standby MPU of the IRF fabric. Skip this section if the file is already located there. 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 the PC serves as the FTP server. 1. Run the FTP server program on the PC (assume its IP address is ). Ensure that you have configured the username and password, set the correct file directory, and saved the.app file in the work directory. 2. Download the.app file (newest.app for example) to the active MPU of the IRF fabric. # Log in to the PC through FTP. <Sysname> ftp Trying... Press CTRL+K to abort Connected to Com 3CDaemon FTP Server Version 2.0 User( :(none)):username 331 User name ok, need password Password: ---Type the username. ---Enter the password. 30

35 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). 125 BINARY mode data connection already open, transfer starting for / newest.app. 226 Transfer complete. FTP: byte(s) received in second(s), K byte(s)/sec. [ftp] bye 221 Server closing. 3. Copy the file newest.app to the root directory of the storage medium on each standby MPU of the IRF fabric. On the standby MPU in slot 1 of member device 1 <Sysname> copy newest.app chassis1#slot1#flash:/ Copy flash:/newest.app to chassis1#slot1#flash:/newest.app?[y/n]:y %Copy file flash:/newest.app to chassis1#slot1#flash:/newest.app...done. On the standby MPU in slot 0 of member device 2 <Sysname> copy newest.app chassis2#slot0#flash:/ Copy flash:/newest.app to chassis2#slot0#flash:/newest.app?[y/n]:y %Copy file flash:/newest.app to chassis2#slot0#flash:/newest.app...done. On the standby MPU in slot 1 of member device 2 <Sysname> copy newest.app chassis2#slot1#flash:/ Copy flash:/newest.app to chassis2#slot1#flash:/newest.app?[y/n]:y %Copy file flash:/newest.app to chassis2#slot1#flash:/newest.app...done. NOTE: You can configure the switch as the FTP server, FTP client, or TFTP client. The transfer processes slightly vary. For more information about FTP and TFTP, see Fundamentals Configuration Guide in the HP 7500 Switch Series Configuration Guides. You can use the transfer procedure described in this section to transfer Boot ROM images, system software images, and patch files for upgrade from the CLI. Upgrade software from the CLI NOTE: Make sure that the upgrade files exist in the root directory of the storage medium of the active and standby MPUs of the IRF fabric. Perform the following tasks as needed: Upgrade Boot ROM Upgrade system software Install patches 31

36 1. Upgrade Boot ROM # Upgrade the Boot ROM program of the active MPU of the IRF fabric. <Sysname> bootrom update file flash:/newboot.btw chassis 1 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 chassis 1 slot 0. # Upgrade the Boot ROM program of each standby MPU of the IRF fabric. On the standby MPU in slot 1 of member device 1 <Sysname> bootrom update file chassis1#slot1#flash:/newboot.btw chassis 1 slot 1 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 chassis 1 slot 1. On the standby MPU in slot 0 of member device 2 <Sysname> bootrom update file chassis2#slot0#flash:/newboot.btw chassis 2 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 chassis 2 slot 0. On the standby MPU in slot 1 of member device 2 <Sysname> bootrom update file chassis2#slot1#flash:/newboot.btw chassis 2 slot 1 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 chassis 2 slot 1. # Reboot the IRF fabric to validate the upgrade. <Sysname> reboot Start to check configuration with next startup configuration file, please wait....done! This command will reboot the device. Continue? [Y/N]:y 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 startup of the active MPU of the IRF fabric. <Sysname> boot-loader file newest.app chassis 1 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 chassis 1 slot 0! 32

37 # Specify the file newest.app as the main system software image to be used at the next startup of the standby MPUs of the IRF fabric. On the standby MPU in slot 1 of member device 1 <Sysname> boot-loader file chassis1#slot1#flash:/newest.app chassis 1 slot 1 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 chassis 1 slot 1! On the standby MPU in slot 0 of member device 2 <Sysname> boot-loader file chassis2#slot0#flash:/newest.app chassis 2 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 chassis 2 slot 0! On the standby MPU in slot 1 of member device 2 <Sysname> boot-loader file chassis2#slot1#flash:/newest.app chassis 2 slot 1 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 chassis 2 slot 1! # Reboot the IRF fabric to validate the upgrade. <Sysname> reboot Start to check configuration with next startup configuration file, please wait....done! This command will reboot the device. Continue? [Y/N]:y CAUTION: To prevent configuration loss, save the latest configuration changes before you reboot the switch. System software images must be saved in the root directory of the storage medium. You can copy or move system software images to the root directory. For more information about the boot-loader command, see Fundamentals Command Reference in the HP 7500 Switch Series Command References. 3. Install patches # Download the patch files to the root directory of the storage medium of the active and standby MPUs, and then install the patch files with the patch install command. <Sysname> system-view [Sysname] patch install flash: 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. 33

38 Upgrade from the boot menu You can upgrade the Boot ROM program and system software image for the MPUs from the boot menu. Upgrading Boot ROM from the boot menu Upgrading system software from the boot menu CAUTION: You cannot simultaneously upgrade the active and standby MPUs from the boot menu. To ensure that the active and standby MPUs use the same software version, upgrade them in turn. Upgrading Boot ROM from the boot menu Upgrade the Boot ROM program from the boot menu by using one of the following methods: Using TFTP through the management Ethernet port Using FTP through the management Ethernet port Using Xmodem through the console port Using an upgrade file on the switch Using TFTP 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. Step2 Run the TFTP server program on the PC connected to the management Ethernet port and specify the file storage directory. Step3 Run the terminal emulation program on the PC connected to the console port. Start the switch, enter the boot menu (see Error! Reference source not found. for more information), and press Ctrl+U when you see "Enter your choice(0-5):" to enter the Boot ROM update menu. 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): 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 34

39 Load File name :newboot.btw The name of the target.btw file Switch IP address : The IP address of the switch Server IP address : The IP address of the PC that stores the.btw file NOTE: The switch must be on the same network segment as the PC storing the upgrade files. Step5 After you set the TFTP parameters and press Enter, the switch starts to download the upgrade file. When the file is successfully downloaded, the following output 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. The following information appears: Updating extended BootRom? (Y/N):Y 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): Step8 Type 0 to return to the boot 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: 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. 35

40 Step2 Run the FTP server program on the PC connected to the management Ethernet port, specify the file storage directory, and set the username and password. Step3 Run the terminal emulation program on the PC connected to the console port. Start the switch, enter the boot menu (see Error! Reference source not found. for more information), and press Ctrl+U when you see "Enter your choice(0-5):" to enter the Boot ROM update menu. 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): Step4 In the Boot ROM update menu, type 2 to set the FTP 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):2 Load File name :newboot.btw The name of the target.btw file Switch IP address : The IP address of the switch Server IP address : The IP address of the PC that stores the.btw file FTP User Name :username The FTP username FTP User Password :12345 The password NOTE: The switch must be on the same network segment as the PC storing the upgrade files. Step5 After you set the FTP parameters and press Enter, the switch starts to download the upgrade file. When the file is successfully 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. The following information appears: Updating extended BootRom? (Y/N):Y Updating extended BootRom...done! BootRom update menu: 36

41 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): Step8 Type 0 to return to the boot 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: Reboot Enter your choice(0-5):0 Step9 Type 0 to reboot the switch. NOTE: The Boot ROM upgrade takes effect at the next startup. Using Xmodem through the console port Step1 Connect the console port of the switch to the PC that stores the upgrade files. Step2 Run the terminal emulation program on the PC. Start the switch, enter the boot menu (see Error! Reference source not found. for more information), and press Ctrl+U when you see "Enter your choice(0-5):" to enter the Boot ROM update menu. 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): 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 37

42 Please select your download baudrate: 1.* Exit Enter your choice (0-5):2 Step4 Select an appropriate download baud rate. For example, type 2 to select bps. The following information appears: Please change the terminal's baudrate to bps and select XMODEM protocol. Press ENTER key when ready. NOTE: If you want to use the baud rate of 9600 bps, select it and directly go to Step 7. In this case, the system does not display the above information. Step5 Disconnect HyperTerminal from the switch by clicking Disconnect in the HyperTerminal window. Step6 Select File > Properties in the HyperTerminal window, click Configure in the popup dialog box, and select the baud rate of bps in the console port properties dialog box. Figure 1 The Switch Properties dialog box 38

43 Figure 2 The console port properties dialog box Step7 Click Connect to re-connect to the switch. The following information appears: Now please start transfer file with XMODEM protocol. If you want to exit, Press <Ctrl+X> 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. The following dialog box appears: 39

44 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...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): Step13 Type 0 to return to the boot 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: Reboot 40

45 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 Error! Reference source not found. for more information), and press Ctrl+U when you see "Enter your choice(0-5):" to enter the Boot ROM update menu. 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): Step3 In the Boot ROM update menu, type 4. The following information appears: Flash:/ Number. Size(B) Time Name =============================================================================== Aug/17/ :20:10 private-data.txt Aug/17/ :21:05 startup.cfg 3(*-) Jul/29/ :35:17 switch000.app Jul/29/ :35:17 update.btw Aug/17/ :20:21 system.xml Aug/19/ :59:51 mpu.btw May/10/ :59:11 config.cfg Free space: bytes The current application file is:flash:/switch000.app The backup application file is:flash:/switch000.app Please input the file number:4 Step4 Type the number of the target.btw file. The following information appears: The file you selected is flash:/update.btw, update from it? Yes or No(Y/N)Y Step5 Answer Y to the question. The following information appears: Load file from flash to sdram...done! The file you selected is not the primary boot file, are you sure you want to update from it? Yes or No(Y/N)Y Step6 Answer Y to the question. The following information appears: Will you Update Basic BootRom? (Y/N): 41

46 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 boot 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: Reboot Enter your choice(0-5):0 Step10 Type 0 to reboot the switch. NOTE: The Boot ROM upgrade takes effect at the reboot. Upgrading system software from the boot menu Download new system software images Download new system software images to your switch by using one of the following methods: NOTE: Using TFTP through the management Ethernet port Using FTP through the management Ethernet port Using Xmodem through the console port Skip this section if the new system software image already exists on your switch. 1. Using TFTP 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. Step2 Run the TFTP server program on the PC connected to the management Ethernet port and specify the file storage directory. 42

47 Step3 Run the terminal emulation program on the PC connected to the console port. Start the switch, enter the boot menu (see Error! Reference source not found. 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. Reboot Enter your choice(0-5):1 Step4 In the download protocol menu, type 1 to set the TFTP parameters. 1. Set TFTP protocol parameter 2. Set FTP protocol parameter 3. Set XMODEM protocol parameter 0. Return to boot menu Enter your choice(0-3): 1 Load File name :newest.app The name of the target.app file Switch IP address : The IP address of the switch Server IP address : The IP address of the PC that stores the.app file NOTE: The switch must be on the same network segment as the PC storing the upgrade files. Step5 Set the TFTP parameters and press Enter. The following information appears: Are you sure to download file to flash? Yes or No (Y/N):Y Step6 Answer Y to the question. The switch starts to download the file. When the download is complete, the following appears: Loading done! Free space: 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 43

48 Step7 Type 0 to return to the boot 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 port 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. Step9 Run the FTP server program on the PC connected to the management Ethernet port, specify the file storage directory, and set the username and password. Step10 Run the terminal emulation program on the PC connected to the console port. Start the switch, enter the boot menu (see Error! Reference source not found. for more information), and press 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. Reboot Enter your choice(0-5):1 Step11 In the download protocol menu, type 2 to set the FTP parameters. 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): 2 Load File name :newest.app The name of the target.app file Switch IP address : The IP address of the switch Server IP address : The IP address of the PC that stores the.app file FTP User Name :username The FTP username. FTP User Password :12345 The password. NOTE: The switch must be on the same network segment as the PC storing the upgrade files. Step12 Set the FTP parameters and press Enter. The following information appears: Are you sure to download file to flash? Yes or No (Y/N):y Step13 Answer Y to the question. The switch starts to download the file. When the download is complete, the following information appears: Loading done! 44

49 Free space: 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 boot 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. 3. Using Xmodem through the console port Step15 Connect the console port of the switch to the PC that stores the target.app file. Step16 Run the terminal emulation program on the PC. Start the switch, enter the boot menu (see Error! Reference source not found. 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. Reboot Enter your choice(0-5):1 Step17 In the download protocol menu, type 3. The switch asks you to provide the name of the file you want to download. 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 Load File name :update.app The name of the file to be downloaded Step18 Type the file name and the download baud rate menu appears. Please select your download baudrate: 1.*

50 Exit Enter your choice (0-5):2 Step19 Select an appropriate download baud rate. For example, type 2 to select bps. The following information appears: Please change the terminal's baudrate to 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 Disconnect in the HyperTerminal window. Step21 Select File > Properties in the HyperTerminal window, click Configure in the popup dialog box, and select the baud rate of bps in the console port properties dialog box. Figure 5 Switch Properties dialog box 46

51 Figure 6 Console port properties dialog box Step8 Click Connect to re-connect to the switch. The following information appears: Now please start transfer file with XMODEM protocol. If you want to exit, Press <Ctrl+X> 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. The following dialog box appears: 47

52 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 : bytes Writing flash done! 1. Set TFTP protocol parameter 2. Set FTP protocol parameter 3. Set XMODEM protocol parameter 0. Return to boot menu Enter your choice(0-3): Step12 Type 0 to return to the boot menu. NOTE: When the system reboots, you must change the baud rate for HyperTerminal back to 9600 bps by following Step 6 and Step 7. Set new main and backup system software images After you download a new system software image to the switch, set the file as the main or backup system software image. 48