HP Moonshot-45XGc Switch E2418

Transcription

1 HP Moonshot-45XGc Switch E2418 Release Notes Copyright 2015 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 1 Upgrading restrictions and guidelines 3 Hardware feature updates 3 E R E Software feature and command updates 3 MIB updates 3 Operation changes 4 Operation changes in E Operation changes in R Operation changes in E Restrictions and cautions 5 Open problems and workarounds 5 List of resolved problems 5 Resolved problems in E Resolved problems in R Resolved problems in E Related documentation 14 Obtaining documentation 14 Contacting HP 14 Subscription service 14 Appendix A Feature list 16 Hardware features 16 Software features 16 Appendix B Upgrading software 22 Software types 22 Software file naming conventions 22 Comware image redundancy and loading procedure 22 System startup process 23 Upgrade methods 24 Upgrading from the CLI 25 Preparing for the upgrade 25 Transferring software to the master switch 26 Upgrading the software images 28 Installing a patch package 30 Upgrading Comware software from the BootWare menus 30 Using TFTP to upgrade through the management Ethernet port 31 Using FTP to upgrade through the management Ethernet port 33 Using Xmodem to upgrade through the console port 35 i

3 Upgrading BootWare from the BootWare menus 40 Using TFTP to upgrade through the management Ethernet port 40 Using FTP to upgrade through the management Ethernet port 42 Using Xmodem to upgrade through the console port 44 Handling upgrade failures 49 Appendix C Using BootWare menus Error! Bookmark not defined. 50 Accessing the BootWare menus 50 Using the BASIC-BOOTWARE menu 52 Modifying serial port parameters 52 Updating the extended BootWare segment 53 Updating the entire BootWare 53 Running the primary extended BootWare segment 53 Running the backup extended BootWare segment 54 Accessing the BASIC ASSISTANT menu 55 Using the EXTENDED-BOOTWARE menu 55 Disabling password recovery capability 57 Running the Comware software 58 Upgrading Comware software through the console port 58 Upgrading Comware software through an Ethernet port 59 Managing files 61 Restoring the factory-default configuration 66 Starting up without loading the configuration file 67 Managing the BootWare image 67 Skipping console login authentication 68 Managing storage media 68 Using the EXTENDED ASSISTANT menu 69 Formatting the file system 69 ii

4 List of Tables Table 1 Version history... 1 Table 2 Hardware and software compatibility matrix... 1 Table 3 MIB updates... 3 Table 4 hardware features Table 5 Software features Table 6 Setting TFTP file transfer parameters Table 7 Setting FTP file transfer parameters Table 8 BootWare menus Table 9 BootWare shortcut keys Table 10 BASIC-BOOTWARE menu options Table 11 BASIC ASSISTANT menu Table 12 EXTENDED-BOOTWARE menu options Table 13 Serial submenu options Table 14 Ethernet submenu options Table 15 Setting file transfer parameters Table 16 File CONTROL submenu options Table 17 BootWare Operation menu options Table 18 DEVICE CONTROL menu options Table 19 EXTENDED ASSISTANT menu options iii

5 This document describes the features, restrictions and guidelines, open problems, and workarounds for version E2418. 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 Moonshot-45XGc E2418 Release Notes (Software Feature Changes)> and the documents listed in "Related documentation." Version information Version number HP Comware Software, Version , ESS 2418 Note: You can see the version number with the command display version in any view. Please see Note1. Version history Table 1 Version history Version number Last version Release Date Release type Remarks MOONSHOT- 45XGC-CMW710- E2418 MOONSHOT- 45XGC-CMW710- R ESS version None MOONSHOT- 45XGC-CMW710- R2417 MOONSHOT- 45XGC-CMW710- E Release version None MOONSHOT- 45XGC-CMW710- E2407 First release ESS version None Hardware and software compatibility matrix Table 2 Hardware and software compatibility matrix Item Product family Hardware platform Memory Flash BootWare image Specifications HP MOONSHOT Switch HP MOONSHOT Switch 2GB DDR3 512MB Nand Flash Shipped with the switch. (Use the display version command in any view to view the BootWare version.) 1

6 Item System software image imc version inode version Specifications Switch_FW_45XGc_E2418.ipe imc PLAT 7.1 (E0302) imc EIA 7.1 (E0302) MC EAD 7.1(E0301) imc NTA 7.1 (E0301) imc QoSM 7.1 (E0301) imc UBA 7.1 (E0301) imc BIMS 7.1 (E0301) imc SHM 7.1 (E0301) imc IVM 7.1 (E0301) imc MVM 7.1 (E0301) imc RAM 7.1 (E0301) imc SDNM 7.1 (E0301) imc VCM 7.1 (E0301) imc VFM 7.1 (E0301) inode PC 7.1 (E0302) To display version information for the system software and Boot ROM of MOONSHOT: <HP>dis version HP Comware Software, Version , ESS 2418 Copyright (c) Hewlett-Packard Development Company, L.P. HP Moonshot-45XGc Switch uptime is 0 weeks, 0 days, 0 hours, 40 minutes Last reboot reason : USER reboot Boot image: flash:/moonshot-45xgc-cmw710-boot-e2418.bin Boot image version: , ESS 2418 Compiled Mar :41:19 System image: flash:/moonshot-45xgc-cmw710-system-e2418.bin System image version: , ESS 2418 Compiled Mar :41:19 Slot 1: Uptime is 0 weeks,0 days,0 hours,40 minutes Moonshot-45XGc Switch with 2 Processors BOARD TYPE: Moonshot-45XGc Switch DRAM: 2048M bytes FLASH: 512M bytes PCB 1 Version: VER.C Bootrom Version: 106 CPLD 1 Version: 0x23 CPLD 2 Version: 0x0e CPLD 3 Version: 0x01 Release Version: HP Moonshot-45XGc Switch-2418 Patch Version : None 2

7 Reboot Cause : UserReboot [SubSlot 0] 45*10G downlinks [SubSlot 1] 16*SFP Plus Upgrading restrictions and guidelines None. Hardware feature updates E2418 Added support for the following module: HP Moonshot-16SFP+ Uplink Module. Added updates to CPLDs needed to support HP Moonshot-16SFP+ Uplink Module and HP Moosnhot-4QSFP+ Uplink Module. R2417 None. E2407 Two files - MOONSHOT-CPLD1-V23.jbc, MOONSHOT-CPLD2-V0E03.jbc First release. Software feature and command updates For more information about the software feature and command update history, see HP Moonshot- 45XGc E2418 Release Notes (Software Feature Changes). MIB updates Table 3 MIB updates Item MIB file Module Description MOONSHOT-45XGC-CMW710-E2418 New None None None 3

8 Item MIB file Module Description Modified hh3c-product-id.mib HH3C-OID-MIB MOONSHOT-45XGC-CMW710-R2417 Added hpmoonshot45gcr10 hpmoonshot45xgcr16 hpmoonshot180xgcr16 hpmoonshot180xgcr40 New hh3c-stack.mib hh3c-splat-igsp.mib HH3C-STACK-MIB hh3c-multicastsnooping.mib HH3C-MULTICAST- SNOOPING-MIB HH3C-LswIGSP-MIB Added hh3cstackdomainid Added HH3C-MULTICAST- SNOOPING-MIB Added hh3clswigmpsnoopingmib Object Modified None None None MOONSHOT-45XGC-CMW710-E2407 New First release First release First release Modified First release First release First release Operation changes Operation changes in E2418 None. Operation changes in R2417 Enhanced the feature of establishing neighborship through LLDP Before modification, LLDP cannot establish neighborship when both PSE and PD features are set in the TLVs sent by the neighbor. After modification, LLDP can establish neighborship when both PSE and PD features are set in the TLVs sent by the neighbor. Change to the forwarding of CRC error frames after the cut-through enable command is used to enable cut-through forwarding Before modification, the switch cannot forward CRC error frames after cut-through forwarding is enabled. After modification, the switch supports forwarding CRC frames after cut-through forwarding is enabled. Change to the rate limit Before modification, the rate limit for the following item is 200 pps. 120 OFP_MISS S On SMAC 0 4

9 121 OFP_MATCH S On SMAC OFP_DEVCONF S On SMAC OFP_MACIP_MISS S On SMAC 0 After modification, the rate limit is 600 pps. Change to the priority of OpenFlow protocol packets Before modification, the OpenFlow protocol packets are assigned to queue 2 of the CPU. After modification, the OpenFlow protocol packets are assigned to queue 41 of the CPU. Operation changes in E2407 First release. Restrictions and cautions None. Open problems and workarounds None. List of resolved problems Resolved problems in E2418 CPLD file fixes uplink module power sequencing. CPLD file fixes UID behavior. Resolved problems in R2417 CVE Symptom: CVE Condition: When an OpenSSL SSL/TLS/DTLS server receives a session ticket the integrity of that ticket is first verified. In the event of a session ticket integrity check failing, OpenSSL will fail to free memory causing a memory leak. By sending a large number of invalid session tickets an attacker could exploit this issue in a Denial of Service attack. SSL 3.0 Fallback protection Symptom: SSL 3.0 Fallback protection. Condition: OpenSSL has added support for TLS_FALLBACK_SCSV to allow applications to block the ability for a MITM attacker to force a protocol downgrade. Some client applications (such as browsers) will reconnect using a downgraded protocol to work around interoperability 5

10 CVE bugs in older servers. This could be exploited by an active man-in-the-middle to downgrade connections to SSL 3.0 even if both sides of the connection support higher protocols. SSL 3.0 contains a number of weaknesses including POODLE (CVE ). Symptom: CVE Condition: When OpenSSL is configured with "no-ssl3" as a build option, servers could accept and complete a SSL 3.0 handshake, and clients could be configured to send them. Symptom: The CLI might be halted and not respond for tens of minutes. After the port linkmode command is executed on an interface to change its link mode, the display interface command cannot display the interface. Condition: This symptom occurs when the following conditions exist: The switch is in an IRF fabric and is connected to other devices through aggregate interfaces to form an RRPP network. About 40 RRPP domains are created. The shutdown and then undo shutdown commands are repeatedly executed on the aggregate interfaces. The port link-mode command is repeatedly executed on the interface to change its link mode. Symptom: After the switch is rebooted, the operation of canceling SPBM-related configurations does not take effect. Condition: This symptom occurs after the following procedure is performed: a. The switch is enabled with SPBM and configured with some SPBM features. b. The configuration is saved. c. The switch is rebooted. Symptom: IPv6 routes do not take effect. Some unknown Layer 3 unicast packets cannot trigger ARP entry learning. Condition: This symptom occurs after the switch is changed to the switch-mode 4 mode. Symptom: An IRF fabric cannot be rebooted. Condition: This symptom occurs after the following procedure is performed: a. Execute the mac-address notification mac-move suppression command on the IRF fabric. b. Save the configuration and reboot the entire IRF fabric. Symptom: When multicast traffic is forwarded between sub VLANs, the forwarding entries still exist after sub VLANs are dissociated from its super VLAN. Condition: This symptom occurs after the following procedure is performed: a. Configure a super VLAN and associate it with sub VLANs. 6

11 b. After sub VLANs receive multicast traffic, the debug ipmc show entry all command shows that forwarding entries have been set up. c. Dissociate the sub VLANs from the super VLAN. d. The display multicast forwarding-table command shows that the forwarding entries for the sub VLANs have been deleted. The debug ipmc show entry all command shows that the forwarding entries still exist. Symptom: The automatic configuration feature in HTTP Python method cannot be used. Condition: This symptom occurs if the following conditions exist when you configure the DHCP server on the switch: The DHCP server address pool has the address of the TFTP server. The DHCP server has an automatic configuration file in the HTTP Python method Symptom: After the master/subordinate switchover in an IRF fabric, aggregation group member ports cannot become Selected. Condition: This symptom occurs after the following procedure is performed: a. In the IRF fabric, configure link aggregation to collaborate with BFD on all aggregate interfaces. b. Perform a master/subordinate switchover in the IRF fabric. Symptom: The Tcl script cannot be executed correctly on the switch. Condition: This symptom occurs when the Tcl script to be executed contains two or more continuous new lines. Symptom: The track status of a TRILL port is different from the status of the associated track entry. Condition: This symptom occurs after the following procedure is performed: a. Associate the TRILL port with a track entry. b. Restart the TRILL protocol. Symptom: Incomplete greeting (MOTD) banner is displayed when a console user logs in an IRF fabric through a console port. Condition: This symptom occurs if you perform the following steps: a. Use the header motd command to configure a greeting banner after logging in through the console port. b. Log off the console port. c. Log in again through the console port. Symptom: The UID LED on an IRF subordinate device cannot blink. 7

12 Condition: This symptom occurs if the subordinate device is upgraded with the software images of the master device by using the boot-loader update command. Symptom: The value read from the hh3cifpktbuffree MIB object is not the same as the remaining buffer size displayed by using the display buffer usage command. Condition: This symptom occurs if you use the display buffer usage command and a MIB tool to obtain the remaining buffer size. Symptom: Hosts cannot ping the gateway when primary and secondary VLANs are configured. Condition: This symptom might occur if the following steps are performed: a. Configure the VLAN interface for the primary VLAN, and bind the interface to a VPN instance. b. Associate the primary VLAN with a list of secondary VLANs by using the private-vlan command. Symptom: The packet filter on a VLAN interface filters Layer 2 traffic. Condition: This symptom might in either of the following situations: The packet-filter filter route command, and then the packet filtering rules are configured when the VLAN interface is up. The packet-filter filter route command, and then the packet filtering rules are configured when the VLAN interface is down. Then, the VLAN interface is brought up. Symptom: The device does not forward spanning tree protocol BPDUs without processing them when the spanning tree feature is disabled. Condition: This symptom occurs when the spanning tree feature is globally disabled Symptom: The display interface command shows that the maximum frame length setting is However, the maximum length of frames that can pass through is only Condition: This symptom occurs if the command is used in Layer 2 interface view to prevent jumbo frames to pass through. Symptom: The QoS priority set for voice traffic by using the voice-vlan qos command does not take effect. Condition: This symptom occurs if the lldp tlv-enable med-tlv network-policy vlan-id command has been configured to advertise voice information through LLDP/CDP. Symptom: The packet statistics feature cannot work correctly for Ethernet service instances created on a Layer 2 aggregate interface that uses multichassis aggregation on the S6800 IRF fabric. 8

13 Condition: This symptom occurs if a subordinate device reboots. The packet statistics feature will be unable to count the traffic that pass through the member links on the subordinate device. Symptom: In an OpenFlow network, the switch is repeatedly connected to and disconnected from the controller. Condition: This symptom occurs when the following conditions exist: The controller deploys a flow table to the switch. The default action for the table-miss flow entry is changed to send packets to the controller. The flag is set to send_flow_rem for the table-miss flow entry. Workaround: None. Symptom: Two TRILL access switches become AVFs at the same time, and loops occur. Condition: This symptom occurs when a network segment connects to the TRILL network through two RBs and the Hello interval is set to 255 seconds. Workaround: Decrease the Hello interval. Symptom: In the output from the display version command, WarmReboot might be displayed for the Reboot Cause field, which should be UserReboot. Condition: This symptom occurs when you use the reboot command to reboot the switch and then execute the display version command. Symptom: Some ports specified in a group table cannot forward traffic. Condition: This symptom occurs when the following conditions exist: A controller deploys flow tables and group tables. Master/subordinate switchover is performed in an IRF fabric Symptom: When you delete the specified flow entry, another flow entry is deleted by mistake. Condition: This symptom occurs when the following conditions exist: The controller deploys two flow entries with the same destination MAC address but different VNIs. Delete a flow entry specified by its address ID Symptom: A device cannot be pinged when it is directly connected to an aggregate interface. Condition: This symptom occurs if TRILL is enabled (trill enable) and then disabled (undo trill enable) on the aggregate interface. Symptom: In an OpenFlow network, the switch might lose connectivity to the controller. 9

14 Condition: This symptom might occur if the Layer 3 interface connected to the controller is repeatedly shut down and brought up. Symptom: The State field displays Absent in the output from the display device usb command. Condition: This symptom might occur when the following conditions exist: Multiple switches form an IRF fabric. A USB flash drive is inserted into an IRF member switch. The display device usb command is executed after the IRF fabric is rebooted Symptom: The BFD session stays in down state on a GRE tunnel interface. Condition: This symptom occurs when the following conditions exist: The switch runs OSPF and establishes connections to other devices through the active GRE tunnel. BFD is enabled for OSPF on the GRE tunnel interface Symptom: The Port and protocol VLAN supported field displays No in the output from the display lldp local-information interface command. Condition: This symptom occurs if the lldp tlv-enable dot1-tlv protocol-vlan-id command has been configured on the specified Layer 2 Ethernet interface. Symptom: The output from the display qos-acl resource command shows that the remaining VFP resources are oversized. Condition: This symptom occurs when the following procedure is performed: a. Create plenty of Layer 3 Ethernet subinterfaces, so that VFP resources are 100% used. b. Create a VLAN instance, and bind it to Layer 3 Ethernet interfaces. Symptom: The CLI is stuck. Condition: This symptom occurs when the following conditions exist: Based on the 10-GE interface numbers starting from 1, each four interfaces are assigned to a group. Some interfaces in a group are bound to IRF ports, and the other interfaces in the group are assigned to a service loopback group. Symptom: MPLS-TE RSVP tunnels cannot come up correctly. Condition: This symptom occurs after MPLS-TE RSVP Tunnels are established. Symptom: The global BGP timer does not take effect. Condition: This symptom occurs when the following procedure is performed: 10

15 a. Configure the timer for a specific BGP peer and configure the global timer. b. Use the undo peer timer command to restore the default timer for the peer. c. Execute the reset bgp all command. Symptom: BGP learns routes very slowly. Condition: This symptom occurs after MPLS-TE RSVP tunnels are established. Symptom: An IRF fabric splits. Condition: This symptom occurs if SPBM is disabled when the IRF fabric is receiving traffic from the SPBM network. Symptom: The OperMau field displays Speed(0)/Duplex(Unknown) in the local or neighbor LLDP information of a 10-GE copper interface. Condition: This symptom occurs if the local or neighbor LLDP information is displayed for the interface. Symptom: A 40-G interface cannot be configured to operate in half duplex mode through CLI, but it can be configured to operate in half duplex mode through netconf. Condition: This symptom occurs when netconf is used to configure the 40-G interface to operate in half duplex mode. Symptom: The zone default-zone permit command configuration might fail to be deployed to some VSANs. Condition: This symptom occurs when the following conditions exist: Multiple switches form a network. Reboot all switches in the network Symptom: After the screen disable command is executed, if the display copyright command is executed for multiple Telnet clients at the same time, the remaining CPU decreases and the switch reboots. Condition: This symptom occurs when the following procedure is performed: a. Start the Telnet server, and connect 20 Telnet clients to the server. b. Execute the screen disable command for each client, and then execute the display copyright command. Symptom: The switch is in an SPBM network, and untagged frames are not correctly matched on an interface. Condition: This symptom occurs if the switch is restarting or the frame match criterion of the Ethernet service instance is modified on the interface. 11

16 Symptom: The CLI responds slowly. Condition: This symptom occurs when the priority-flow-control no-drop dot1p or undo priority-flow-control no-drop dot1p command is executed on an Ethernet interface of an 5930 switch. Symptom: After the switch is rebooted, RRPP port state errors occur. Condition: This symptom occurs when the following procedure is performed: a. Ports A1 and A2 of device A and ports B1 and B2 of device B form a loop. The link A1-B1 is in forwarding state, and the link A2-B2 is in blocked state. b. Shut down port A1 of device A. Then, the link A1-B1 changes from the forwarding state to the blocked state, and the link A2-B2 changes from the blocked state to the forwarding state. c. Reboot device B. After device B is rebooted, the two links are both blocked. Symptom: The ACL resources used by RRPP cannot be released. Condition: This symptom occurs when the following procedure is performed: a. Configure plenty of RRPP domains in an IRF fabric. b. Save the configuration and reboot the switch. c. Delete RRPP configurations. Symptom: The switch cannot obtain the asset information of a power module when the display device manuinfo command is executed. Condition: This symptom occurs if the power module is not manufactured by FSP. Symptom: The memory allocation request fails when the switch sends packets. Condition: This symptom occurs if the switch is in an IRF fabric and an interface on the switch is repeatedly brought up and shut down. Symptom: A transceiver module might report a FASTDOWN event. Condition: This symptom occurs when the following procedure is performed: a. Split a 40-G fiber interface into four 10-G breakout interfaces, and bind these 10-G breakout interfaces to IRF ports. b. Install an Avago transceiver module in the 40-G fiber interface and reboot the switch. Symptom: A directly connected device cannot be pinged. Condition: This symptom occurs when MPLS is enabled on multiple VLAN interfaces. Symptom: Error messages similar to the following messages appear. 12

17 DRVMNT/3/ERRORCODE: MdcId=1; ErrCode = , MIM: MIM PW Error. DRVMNT/3/ERRORCODE: MdcId=1; ErrCode = , MIM: SDK Return Fail. DRVMNT/3/ERRORCODE: -Slot=2; MdcId=1; ErrCode = , MIM: SDK Return Fail. Condition: This symptom occurs when the following procedure is performed: a. Use two switches to form an IRF fabric. b. Fully configure the VLANs and VLAN interfaces on the IRF fabric. c. Use the info-center enable command to enable the information center. d. Save the configuration. e. Use the shutdown command on the IRF physical ports to cause an IRF split. f. During the IRF split process, use the undo shutdown command on the IRF physical ports to make the switches form an IRF fabric again. g. Delete VLANs. Symptom: When a command is entered at the CLI, the serial port does not respond. Condition: This symptom occurs when the following procedure is performed: a. Start the switch with a configuration file containing Layer 3 subinterfaces. b. Use the configuration replace file xxx.cfg command to roll the configuration file of the switch back to a configuration file that does not contain Layer 3 subinterfaces. Symptom: In an IRF fabric, the console port of the master member device might not respond, and the subordinate member devices might fail to start correctly. Condition: This symptom occurs when the IRF fabric is restarted. Symptom: When MAD is available, the output from the display mad verbose command shows that the MAD status is Faulty, and the output from the display bfd session command shows the session state is down. The MAD state and the session state are incorrectly displayed. Condition: This symptom occurs when BFD MAD is configured. Symptom: The output from the display ip routing-table statistics command shows that the number of active routes cannot reach 128K. Condition: This symptom occurs when the following procedure is performed: a. Use the switch-mode 4 command to change the operating mode of the switch and restart the switch. b. Add 128K route entries to the routing table. c. Use the display ip routing-table statistics command to display the route statistics. Symptom: The basic features of QCN cannot be used. Condition: This symptom occurs when QCN is configured on the switch. 13

18 Symptom: The USB flash drives cannot be used. Condition: This symptom occurs when the switch has loaded the release E2413. Symptom: The system does not provide prompt information when the number of ARP/ND entries has reached the upper limit. Condition: This symptom can be seen when the number of ARP/ND entries has reached the upper limit. Resolved problems in E2407 First release. Related documentation None 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: 14

19 After registering, you will receive notification of product enhancements, new driver versions, firmware updates, and other product resources. 15

20 Appendix A Feature list Hardware features Table 4 hardware features Item Dimensions (H W D) (excluding feet and rack-mounting brackets) Specification mm x mm x 35.75mm Weight g Input AC voltage Max. power consumption Operating temperature Relative humidity (noncondensing) 12V 57W 0 C to 43 C (32 F to F) 15% to 80% Software features Table 5 Software features Category Full duplex Wire speed L2 switching capacity Whole system Wire speed L2 switching Packet forwarding rate Forwarding mode IRF Features 1280Gbps Up to 893Mpps Store-forward and cut-through Ring topology Daisy chain topology LACP MAD ARP MAD ND MAD BFD MAD IRF comprised of different models 16

21 Category Link aggregation Features Aggregation of 10-GE ports Static link aggregation Dynamic link aggregation When stacked, supports up to 128 aggregation groups, each supporting up to 16 ports Aggregation of 10-GE ports Aggregation of 40-GE ports Static link aggregation Dynamic link aggregation When stacked, supports up to 128 aggregation groups, each supporting up to 16 ports Data center OpenFlow Flow control PFC DCBX FcoE(FCF/Transit/NPV) TRILL EVB SPBM PBB Supported IEEE 802.3x flow control and back pressure Jumbo Frame Supports maximum frame size of MAC address table VLAN VLAN mapping 128K MAC addresses 1K static MAC addresses Blackhole MAC addresses MAC address learning limit on a port Port-based VLANs (4094 VLANs) Private VLAN Super VLAN MVRP QinQ and selective QinQ One-to-one VLAN mapping Many-to-one VLAN mapping Two-to-two VLAN mapping 17

22 Category ARP ND VLAN virtual interface Router port DHCP UDP helper DNS IPv4 routing Features 16K entries 1K static entries Gratuitous ARP Standard proxy ARP and local proxy ARP ARP source suppression ARP black hole ARP detection (based on DHCP snooping entries/802.1x security entries/static IP-to-MAC bindings) Multicast ARP ARP logging IRDP ARP proxy 8K entries 1K static entries ND proxy 1K Supported Router port aggregation DHCP client DHCP snooping DHCP relay agent DHCP server DHCPv6 snooping DHCPv6 rlay agent DHCPv6 server Supported Dynamic domain name resolution Dynamic domain name resolution client IPv4/IPv6 addresses 1K static routes RIP (Routing Information Protocol) v1/v2; up to 2K IPv4 routes OSPF (Open Shortest Path First) v1/v2; up to 16K IPv4 routes BGP (Border Gateway Protocol); up to 16K IPv4 routes IS-IS (Intermediate System-to-Intermediate System); up to 16K IPv4 routes Configurable maximum number of equal-cost routes; up to 4K equal-cost routes VRRP PBR GR NSR 18

23 Category IPv6 routing URPF MCE BFD Tunnel MPLS IPv4 multicast Features 1K static routes RIPng: Supports up to 2K IPv6 routes OSPF v3: Supports up to 8K IPv6 routes ISISv6: Supports up to 8K IPv6 routes Up to 4K ECMP routes; each ECMP route supports up to 32 next hops Routing policy VRRP PBR GR NSR Reverse route check strict mode and loose mode Supported OSPF/OSPFv3 BGP/BGP4 IS-IS/IS-ISv6 PIM/IPM for IPv6 Static route MAD IPv4 over IPv4 tunnel IPv4 over IPv6 tunnel IPv6 over IPv4 manual tunnel IPv6 over IPv4 6to4 tunnel IPv6 over IPv4 ISATAP tunnel IPv6 over IPv6 tunnel GRE tunnel MPLS VPLS IGMP snooping v1/v2/v3 IGMP report suppression Multicast VLAN IGMP v1/v2/v3 PIM-DM PIM-SM PIM-SSM PIM-BIDIR MSDP PIM snooping Multicast VPN 19

24 Category IPv6 multicast Broadcast/multicast/ unicast storm control MSTP Smart Link Monitor Link QoS/ACL Mirroring Remote mirroring Features MLD snooping v1/v2 MLD report suppression IPv6 multicast VLAN Ipv6 PIM snooping MLD v1/v2 PIM-DM/SM for IPv6 IPv6 PIM-SSM IPv6 BIDIR-PIM Storm control based on port rate percentage PPS-based storm control Bps-based storm control STP/RSTP/MSTP protocol STP Root Guard BPDU Guard Up to 26 groups Multi-instance Smart Link Supported Restriction of the rates at which a port sends and receives packets, with a granularity of 8 kbps. Packet redirect Committed access rate (CAR), with a granularity of traffic limit 8 kbps. Eight output queues for each port Flexible queue scheduling algorithms based on port and queue, including strict priority (SP), Weighted Deficit Round Robin (WDRR), Weighted Fair Queuing (WFQ), SP + WDRR, and SP + WFQ. Remarking of 802.1p and DSCP priorities Packet filtering at L2 (Layer 2) through L4 (Layer 4); flow classification based on source MAC address, destination MAC address, source IP (IPv4/IPv6) address, destination IP (IPv4/IPv6) address, port, protocol, and VLAN. Time range Weighted Random Early Detection (WRED) Queue shaping User profile COPP Explicit Congestion Notification (ECN) Flow mirroring Port mirroring Multiple mirror observing port Port remote mirroring (RSPAN) Layer 3 remote port mirroring(erspam) 20

25 Category Security 802.1X Traffic Management Loading and upgrading Management Maintenance Features Hierarchical management and password protection of users AAA authentication RADIUS authentication HWTACACS SSH 2.0 Port isolation Port security IP-MAC-port binding IP Source Guard MFF HTTPS SSL PKI Portal Boot ROM access control (password recovery) Up to 2,048 users Port-based and MAC address-based authentication Trunk port authentication sflow Loading and upgrading through XModem protocol Loading and upgrading through FTP Loading and upgrading through the trivial file transfer protocol (TFTP) Configuration at the command line interface WEB Remote configuration through Telnet Configuration through Console port Python NETCONF Simple network management protocol (SNMP) IMC NMS System log Hierarchical alarms NTP PTP EAA RMON Debugging information output Ping and Tracert NQA Track Remote maintenance through Telnet 802.1ag 802.3ah DLDP File download and upload through USB port 21

26 Appendix B Upgrading software Software upgrade enables you to have new features and fix bugs. Before performing an upgrade, use the release notes for the new software version to verify software and hardware compatibility and evaluate upgrade impacts. Software types The following software types are available: BootWare image A.bin file that contains a basic segment and an extended segment. The basic segment is the minimum code that bootstraps the system. The extended segment enables hardware initialization and provides system management menus. You can use these menus to load software and the startup configuration file or manage files when the device cannot start up correctly. Comware image Includes the following image subcategories: Boot image A.bin file that contains the Linux operating system kernel. It provides process management, memory management, file system management, and the emergency shell. System image A.bin file that contains the software feature modules for device operation and network services, including device management, interface management, configuration management, and routing. Patch packages Irregularly released packages for fixing bugs without rebooting the device. A patch package does not add new features or functions. Comware software images that have been loaded are called "current software images." Comware images specified to load at the next startup are called "startup software images." BootWare image, boot image, and system image are required for the system to work. These images might be released separately or as a whole in one.ipe package file. If an.ipe file is used, the system decompresses the file automatically, loads the.bin boot and system images, and sets them as startup software images. Typically, the BootWare and startup software images for the device are released in an.ipe file. Software file naming conventions Software image file names use the chassis-comware version-image type-release format, for example, moonshot-45xgc-cmw710-boot-e2418.bin and moonshot-45xgc-cmw710-system-e2418.bin. This document uses boot.bin and system.bin as boot and system image file names. Comware image redundancy and loading procedure You can specify two sets of Comware software images: one main and one backup. 22

27 The system always attempts to start up with the main images. If any main image does not exist or is invalid, the system tries the backup images. Figure 1 shows the entire Comware image loading procedure. If both of the main and backup boot images are invalid or unavailable, connect to the console port and power cycle the device to access the BootWare menus for loading a boot image. To access the Comware system from the emergency shell, you must connect to the console port and load a system image. For more information about using the emergency shell, see HP MOONSHOT Blade Switch Series Fundamentals Configuration Guide. Figure 1 Comware image loading procedure Start Main boot image exists and valid? No Backup boot image No Start up from the BootWare exists and valid? menus Yes Yes Main system image exists and valid? No Backup system image exists and valid? No Main boot image exists and valid? No Start up with the backup boot image and access the emergency shell Yes Yes Yes All patch packages exist and valid? No All backup patch packages exist and valid? No Start up with the main boot image and access the emergency shell Yes Yes Start up with the main images Start up with the backup images System startup process Upon power-on, the BootWare image runs to initialize hardware, and then the startup software images run to start up the entire system, as shown in Figure 2. 23

28 Figure 2 System startup process Start Select the Reboot option to reboot the device BootWare runs Press Ctrl+B promptly? No Startup software images run Yes Enter BootWare menus to upgrade BootWare or startup software images System starts up and CLI appears Finish Upgrade methods You can upgrade system software by using one of the following methods: Upgrading method Software types Remarks Upgrading from the CLI: Upgrading the software images Installing a patch package Upgrading Comware software from the BootWare menus BootWare image Comware images (exclude patches) Patch packages BootWare image Comware images This method is disruptive. You must reboot the entire device to complete the upgrade. This method fixes software defects without requiring a system reboot. Make sure the patch packages match the current software images. A patch package fixes bugs only for its matching software image version. Use this method when the switch cannot start up correctly. CAUTION: Upgrade an IRF fabric from the CLI rather than the BootWare menus. The BootWare menu method increases the service downtime, because it requires that you upgrade the member switches one by one. 24

29 Upgrading from the CLI This section uses a two-chassis IRF fabric as an example to describe how to upgrade software from the CLI. If you are upgrading a standalone switch, ignore the steps for upgrading the subordinate switch. If you have more than two subordinate switches, repeat the steps for the subordinate switches to upgrade their software. For more information about setting up and configuring an IRF fabric, see HP MOONSHOT Blade Switch Series IRF Configuration Guide. NOTE: The output in this document is for illustration only and might vary with software releases. Preparing for the upgrade Before you upgrade software, complete the following tasks: Log in to the IRF fabric through Telnet or the console port (details not shown). Execute the display irf command in any view to identify the number of IRF members and each member switch's role and IRF member ID. <Sysname> display irf MemberID Role Priority CPU-Mac Description *+1 Master afdc Standby af * indicates the device is the master. + indicates the device through which the user logs in. The Bridge MAC of the IRF is: afdb Auto upgrade : no Mac persistent : 6 min Domain ID : 0 Identify the free storage space of each member switch: # Identify the free flash space of the master switch. <Sysname> dir Directory of flash: 0 -rw Jan :23:44 startup.mdb 1 -rw Jan :23:44 startup.cfg 2 -rw Nov :53:48 system.bin 3 drw- - Jan :00:07 seclog 4 drw- - Jan :00:07 diagfile 5 drw- - Jan :00:07 logfile 6 -rw Nov :53:48 boot.bin 7 -rw Nov :53:48 backup.bin KB total ( KB free) # Identify the free flash space of each subordinate switch (for example, switch 2). <Sysname> dir slot2#flash:/ 25

30 Directory of slot2#flash:/ 0 -rw Jan :23:44 startup.mdb 1 -rw Jan :23:44 startup.cfg 2 -rw Nov :53:48 system.bin 3 drw- - Jan :00:07 seclog 4 drw- - Jan :00:07 diagfile 5 drw- - Jan :00:07 logfile 6 -rw Nov :53:48 boot.bin 7 -rw Nov :53:48 backup.bin KB total ( KB free) Compare the free flash space of each member switch with the size of the software file to load. If the space is sufficient, start the upgrade process. If the space is not sufficient, go to the next step. Delete unused files from the flash memory to free space: CAUTION: To avoid data loss, do not delete the current configuration file. To display the current configuration file, execute the display startup command in any view. HP recommends that you preferentially delete unused software images. To avoid inadvertent delete of the current software images, use the display boot-loader command in any view to identify them. The delete /unreserved file-url command deletes a file permanently, and this action cannot be undone. # Use the delete /unreserved file-url command in user view to delete unused files from the flash memory of the master switch. <Sysname> delete /unreserved flash:/backup.bin The file cannot be restored. Delete flash:/backup.bin?[y/n]:y Deleting the file permanently will take a long time. Please wait... Start to delete flash:/backup.bin...done. NOTE: You cannot use the delete file-url command for the purpose of this procedure. This command moves a file to the recycle bin and the file still occupies storage space. # Delete unused files from the flash memory of the subordinate switch. <Sysname> delete /unreserved slot2#flash:/backup.bin The file cannot be restored. Delete slot2#flash:/backup.bin?[y/n]:y Deleting the file permanently will take a long time. Please wait... Start to delete slot2#flash:/backup.bin...done. Transferring software to the master switch The switch can work as an FTP server, FTP client, or TFTP server. Before you upgrade Comware images or install patches, use one of the following methods to transfer the upgrade file to the root directory of the master's flash memory: Downloading images from an FTP server Uploading images from an FTP client to the switch 26

31 Prerequisites Downloading images from a TFTP server This software guide uses an.ipe file to describe the upgrade procedure. Prepare the FTP or TFTP server yourself if you are using the switch as a client. Make sure the IRF fabric has connectivity with the FTP/TFTP server or FTP client. Downloading images from an FTP server 1. Configure the FTP server: # Run FTP server on the PC. # Configure an FTP username and password. # Specify the working directory. # Copy the image file (for example, newest.ipe) to the directory. 2. Execute the ftp command in user view on the IRF fabric to access the FTP server (for example, the server at ). <Sysname> ftp Trying Press CTRL+K to abort Connected to FTP service ready. User( :(none)):username 331 Password required for username. Password: 230 User logged in 3. Enable the binary transfer mode in FTP client view. [ftp] binary 200 Type set to I. 4. Download the upgrade file from the FTP server. [ftp] get newest.ipe 227 Entering Passive Mode (10,10,110,1,17,97). 125 BINARY mode data connection already open, transfer starting for /newest.ipe 226 Transfer complete bytes received in 35 seconds ( kbyte/s) [ftp] bye 221 Server closing. Uploading images from an FTP client to the switch 1. On the IRF fabric: # Enable FTP server in system view. <Sysname> system-view [Sysname] ftp server enable # Add a local user account in system view. [Sysname] local-user abc # Set the password to pwd in plain text in the user account. [Sysname-luser-abc] password simple pwd 27

32 # Set the access service type to ftp in the user account. [Sysname-luser-abc] service-type ftp # Assign the network-admin user role to the user account for uploading files. [Sysname-luser-abc] authorization-attribute user-role network-admin # Execute the quit command to return to the system view. [Sysname-luser-abc] quit # Execute the quit command to return to the user view. [Sysname] quit 2. On the PC: # Use FTP to log in to the IRF fabric (the FTP server at ). c:\> ftp Connected to FTP service ready. User( :(none)):abc 331 Password required for abc. Password: 230 User logged in. # Enable the binary file transfer mode. ftp> binary 200 TYPE is now 8-bit binary. # Upload the file (for example, newest.ipe) to the root directory of the master's flash memory. ftp> put newest.ipe 200 PORT command successful 150 Connecting to port File successfully transferred ftp: bytes sent in secs ( Kbytes/sec). Downloading images from a TFTP server To download an image file from a TFTP server (for example, the server at ): 1. Configure the TFTP server: # Run TFTP server on the PC. # Specify the working directory. # Copy the image file (for example, newest.ipe) to the directory. 2. On the IRF fabric, use TFTP to download the image file to the root directory of the master's flash memory. <Sysname> tftp get newest.ipe % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed M M k 0 --:--:-- 0:03:38 --:--:-- 142k Upgrading the software images To upgrade the software images: 1. Specify the upgrade file as the main startup software image file for the master. <Sysname> boot-loader file flash:/newest.ipe slot 1 main 28

33 Images in IPE: boot.bin system.bin This command will set the main startup software images. Continue? [Y/N]:y Add images to target slot. The specified file list will be used as the main startup software images at the next reboot on slot Specify the upgrade file as the main startup software image file for the subordinate switch. (The subordinate switch will copy the upgrade file automatically from the master to the root directory of its flash memory.) <Sysname> boot-loader file flash:/newest.ipe slot 2 main Images in IPE: boot.bin system.bin This command will set the main startup software images. Continue? [Y/N]:y Add images to target slot. The specified file list will be used as the main startup software images at the next reboot on slot (Optional.) If the IRF fabric has multiple subordinate members, enable the software autoupdate function. <Sysname> system-view [Sysname] irf auto-update enable [Sysname] quit Software auto-update automatically synchronizes the software images of the master switch to new member switches as the main startup software images. 4. Save the configuration to prevent data loss. <Sysname> save The current configuration will be written to the device. Are you sure? [Y/N]:y Please input the file name(*.cfg)[flash:/startup.cfg] (To leave the existing filename unchanged, press the enter key): flash:/startup.cfg exists, overwrite? [Y/N]:y Validating file. Please wait... Saved the current configuration to mainboard device successfully. Slot 2: Save next configuration file successfully. 5. Reboot the IRF fabric to complete 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 Now rebooting, please wait... The system automatically loads the.bin boot and system images in the.ipe file and sets them as the startup software images. 6. If the system detects that the BootWare image has an update, choose to upgrade both the basic and extended segments of the BootWare image for compatibility. 29

34 NOTE: If you choose to not upgrade the BootWare image, the system will prompt for an upgrade at the next reboot. If you fail to make any choice in the required time, the system upgrades the entire BootWare image. 7. Execute the display version command to verify that the current main software images have been updated (details not shown). Installing a patch package 1. Activate the patch package (for example, system-patch.bin) on the master switch and the subordinate switch. <Sysname> install activate patch flash:/system-patch.bin slot 1 <Sysname> install activate patch flash:/system-patch.bin slot 2 2. Verify that the patch package has been activated. <Sysname> display install active Active packages on slot 1: flash:/boot.bin flash:/system.bin flash:/system-patch.bin Active packages on slot 2: flash:/boot.bin flash:/system.bin flash:/system-patch.bin 3. Commit the installation so the patch package continues to take effect after a reboot. <Sysname> install commit 4. Verify that the patch package installation has been committed. <Sysname> display install committed Committed packages on slot 1: flash:/boot.bin flash:/system.bin flash:/system-patch.bin Committed packages on slot 2: flash:/boot.bin flash:/system.bin flash:/system-patch.bin For more information about installing patch packages, see HP MOONSHOT Blade Switch Series Fundamentals Configuration Guide. Upgrading Comware software from the BootWare menus Use one of the following methods to upgrade Comware software from the BootWare menus: Using TFTP to upgrade through the management Ethernet port Using FTP to upgrade through the management Ethernet port 30

35 Using Xmodem to upgrade through the console port For information about using BootWare, see "Error! Reference source not found.." NOTE: The switch does not come with FTP or TFTP server software. Prepare the software yourself. Upgrading through an Ethernet port is faster than through the console port. Using TFTP to upgrade through the management Ethernet port This upgrade procedure uses the switch as a TFTP client. To upgrade software through TFTP: 1. Connect the management Ethernet port of the switch to the file server, and connect the console port of the switch to the configuration terminal. The configuration terminal can be co-located with the TFTP server. 2. Run a TFTP server program on the file server, and specify the file path of the upgrade file. 3. Run the terminal emulation program on the configuration terminal. 4. Start the switch and access the EXTENDED-BOOTWARE menu. 5. Enter 3 in the EXTENDED-BOOTWARE menu to access the Ethernet submenu. ==========================<Enter Ethernet SubMenu>========================== Note:the operating device is flash <1> Download Image Program To SDRAM And Run <2> Update Main Image File <3> Update Backup Image File <4> Modify Ethernet Parameter <0> Exit To Main Menu <Ensure The Parameter Be Modified Before Downloading!> Enter your choice(0-4): 6. Enter 4 to set Ethernet interface parameters. NOTE: To use the default setting for a field, press Enter without entering any information. ======================<ETHERNET PARAMETER SET>============================== Note: '.' = Clear field. '-' = Go to previous field. Ctrl+D = Quit. Protocol (FTP or TFTP):tftp Load File Name Target File Name :test.bin :newest.ipe :test.bin :newest.ipe 31

36 Server IP Address : Local IP Address : Subnet Mask : Gateway IP Address : Table 6 Setting TFTP file transfer parameters Field '.' = Clear field '-' = Go to previous field Ctrl+D = Quit Protocol (FTP or TFTP) Load File Name Target File Name Server IP Address Local IP Address Subnet Mask Gateway IP Address Description Press the dot (.), and then press Enter to clear the setting for a field. Press the hyphen (-), and then press Enter to return to the previous field. Press Ctrl+D to exit the Ethernet parameter settings menu. Set the file transfer protocol to TFTP. Set the name of the file to be downloaded. Set a file name for saving the file in the current storage medium on the switch. The target file must use the same suffix as the source file. By default, the target file name is the same as the source file name. Set the IP address of the TFTP server. Set the IP address of the switch. Set the IP address mask of the switch. Set a gateway IP address if the switch is on a different network than the server. 7. Press Ctrl+D to return to the Ethernet submenu. ==========================<Enter Ethernet SubMenu>========================== Note:the operating device is flash <1> Download Image Program To SDRAM And Run <2> Update Main Image File <3> Update Backup Image File <4> Modify Ethernet Parameter <0> Exit To Main Menu <Ensure The Parameter Be Modified Before Downloading!> Enter your choice(0-4): 8. Enter 2 or 3 to upgrade software images. For example, to upgrade the main Comware software images, enter 2. Loading Done! bytes downloaded! Image file BOOT.bin is self-decompressing... Saving file flash:/ BOOT.bin...Done. Image file SYSTEM.bin is self-decompressing...saving file flash:/ SYSTEM.bin.....Done. 32

37 ==========================<Enter Ethernet SubMenu>========================== Note:the operating device is flash <1> Download Image Program To SDRAM And Run <2> Update Main Image File <3> Update Backup Image File <4> Modify Ethernet Parameter <0> Exit To Main Menu <Ensure The Parameter Be Modified Before Downloading!> Enter your choice(0-4): 9. Enter 0 in the Ethernet submenu to return to the EXTENDED-BOOTWARE menu. 10. Enter 1 in the EXTENDED-BOOTWARE menu to run the new software images. Using FTP to upgrade through the management Ethernet port This upgrade procedure uses the switch as an FTP client. To upgrade Comware software images through FTP: 1. Connect the management Ethernet port of the switch to the file server, and connect the console port of the switch to the configuration terminal. The configuration terminal can be co-located with the FTP server. 2. Run an FTP server program on the file server, specify the file path of the upgrade file, and set the FTP username and password. 3. Run the terminal emulation program on the configuration terminal. 4. Start the switch and access the EXTENDED-BOOTWARE menu. 5. Enter 3 in the EXTENDED-BOOTWARE menu to access the Ethernet submenu. ==========================<Enter Ethernet SubMenu>========================== Note:the operating device is flash <1> Download Image Program To SDRAM And Run <2> Update Main Image File <3> Update Backup Image File <4> Modify Ethernet Parameter <0> Exit To Main Menu <Ensure The Parameter Be Modified Before Downloading!> Enter your choice(0-4): 6. Enter 4 to set Ethernet interface parameters. NOTE: To use the default setting for a field, press Enter without entering any information. ======================<ETHERNET PARAMETER SET>============================== Note: '.' = Clear field. '-' = Go to previous field. 33

38 Ctrl+D = Quit. Protocol (FTP or TFTP) :ftp Load File Name :test.bin :newest.ipe Target File Name :test.bin :newest.ipe Server IP Address : Local IP Address : Subnet Mask : Gateway IP Address : FTP User Name :abc FTP User Password :PWD Table 7 Setting FTP file transfer parameters Field '.' = Clear field '-' = Go to previous field Ctrl+D = Quit Protocol (FTP or TFTP) Load File Name Target File Name Server IP Address Local IP Address Subnet Mask Gateway IP Address FTP User Name Description Press the dot (.), and then press Enter to clear the setting for a field. Press the hyphen (-), and then press Enter to return to the previous field. Press Ctrl+D to exit the Ethernet parameter settings menu. Set the file transfer protocol to FTP. Set the name of the file to be downloaded. Set a file name for saving the file in the current storage medium on the switch. The file suffix must be the same as the one of the source file name. By default, the target file name is the same as the source file name. Set the IP address of the FTP server. Set the IP address of the switch. Set the IP address mask of the switch. Set a gateway IP address if the switch is on a different network than the server. Set the username for accessing the FTP server. This username must be the same as the one configured on the FTP server. FTP User Password Set the password for accessing the FTP server. This password must be the same as the one configured on the FTP server. 7. Press Ctrl+D to return to the Ethernet submenu. ==========================<Enter Ethernet SubMenu>========================== Note:the operating device is flash <1> Download Image Program To SDRAM And Run <2> Update Main Image File <3> Update Backup Image File <4> Modify Ethernet Parameter 34

39 <0> Exit To Main Menu <Ensure The Parameter Be Modified Before Downloading!> Enter your choice(0-4): 8. Enter 2 to 3 to upgrade software images. For example, to upgrade the main Comware software images, enter 2. Loading Done! bytes downloaded! Image file BOOT.bin is self-decompressing... Saving file flash:/ BOOT.bin...Done. Image file SYSTEM.bin is self-decompressing...saving file flash:/ SYSTEM.bin.....Done. ==========================<Enter Ethernet SubMenu>========================== Note:the operating device is flash <1> Download Image Program To SDRAM And Run <2> Update Main Image File <3> Update Backup Image File <4> Modify Ethernet Parameter <0> Exit To Main Menu <Ensure The Parameter Be Modified Before Downloading!> Enter your choice(0-4): 9. Enter 0 in the Ethernet submenu to return to the EXTENDED-BOOTWARE menu. 10. Enter 1 in the EXTENDED-BOOTWARE menu to run the new software images. Using Xmodem to upgrade through the console port 1. Connect the console port of the switch to the PC that stores the upgrade image file. 2. Run the terminal emulation program on the PC. 3. Start the switch and access the EXTENDED-BOOTWARE menu. 4. Enter 2 in the EXTENDED-BOOTWARE menu to access the Serial submenu. ===========================<Enter Serial SubMenu>=========================== Note:the operating device is flash <1> Download Image Program To SDRAM And Run <2> Update Main Image File <3> Update Backup Image File <4> Modify Serial Interface Parameter <0> Exit To Main Menu Enter your choice(0-4): 5. Enter 4 to change the baud rate of the console port. ===============================<BAUDRATE SET>=============================== Note:'*'indicates the current baudrate Change The HyperTerminal's Baudrate Accordingly 35

40 <Baudrate Available> <1> 9600(Default)* <2> <3> <4> <5> <0> Exit Enter your choice(0-5): 6. Enter an appropriate baud rate option. For example, enter 2 to select bps. Baudrate has been changed to bps. Please change the terminal's baudrate to bps, press ENTER when ready. NOTE: If you choose 9600 bps (the default baud rate), move to step Select Call > Disconnect from the HyperTerminal window to disconnect the HyperTerminal from the switch. Figure 3 Disconnecting the HyperTerminal 8. Select File > Properties in the HyperTerminal window, and click Configure in the popup dialog box. 36

41 Figure 4 Setting switch properties 9. Select from the Bits per second list, and click OK. 37

42 Figure 5 Modifying the baud rate 10. Select Call > Call to reconnect to the switch. Figure 6 Reconnecting to the switch 11. Press Enter in the BootWare interface. The current baudrate is bps ===============================<BAUDRATE SET>=============================== Note:'*'indicates the current baudrate Change The HyperTerminal's Baudrate Accordingly <Baudrate Available> <1> 9600(Default) <2> 19200* <3> <4> <5> <0> Exit Enter your choice(0-5): 38

43 12. Enter 0 to return to the Serial submenu. ===========================<Enter Serial SubMenu>=========================== Note:the operating device is flash <1> Download Image Program To SDRAM And Run <2> Update Main Image File <3> Update Backup Image File <4> Modify Serial Interface Parameter <0> Exit To Main Menu Enter your choice(0-4): 13. Enter 2 to 3 to upgrade the software images. For example, enter 2 to upgrade the main startup software images. Please Start To Transfer File, Press <Ctrl+C> To Exit. Waiting...CCCCC 14. Select Transfer > Send File in the HyperTerminal window. In the Send File dialog box, click Browse to select the source file, and select Xmodem from the Protocol list. Figure 7 Selecting the file to transfer 15. Click Send. Figure 8 File transfer progress 39

44 When the file transfer is complete, the following information appears: Download successfully! bytes downloaded!image file boot.bin is self-decompressing... Input the file name: system.bin Save file...done ===========================<Enter Serial SubMenu>=========================== Note:the operating device is flash <1> Download Image Program To SDRAM And Run <2> Update Main Image File <3> Update Backup Image File <4> Modify Serial Interface Parameter <0> Exit To Main Menu Enter your choice(0-4): 16. Enter 0 in the Serial submenu to return to the EXTENDED-BOOTWARE menu. 17. Enter 1 in the EXTENDED-BOOTWARE menu to run the new software. 18. Change the baud rate of the HyperTerminal back to 9600 bps, and reconnect to the switch. NOTE: The baud rate will restore to the default (9600 bps) at reboot. To set up a console session with the switch after a reboot, you must change the baud rate setting on the configuration terminal back to 9600 bps. Upgrading BootWare from the BootWare menus Use one of the following methods to upgrade the BootWare image from the BootWare menus: Using TFTP to upgrade through the management Ethernet port Using FTP to upgrade through the management Ethernet port Using Xmodem to upgrade through the console port For more information about BootWare, see "Error! Reference source not found.." NOTE: The switch does not come with FTP or TFTP server software. Prepare the software yourself. Upgrading through an Ethernet port is faster than through the console port. Using TFTP to upgrade through the management Ethernet port This upgrade procedure uses the switch as a TFTP client. To upgrade the BootWare image through TFTP: 40

45 1. Connect the management Ethernet port of the switch to the file server, and connect the console port of the switch to the configuration terminal. The configuration terminal can be co-located with the TFTP server. 2. Run a TFTP server program on the file server, and specify the file path of the upgrade file. 3. Run the terminal emulation program on the configuration terminal. 4. Start the switch and access the EXTENDED-BOOTWARE menu. 5. Enter 7 in the EXTENDED-BOOTWARE menu to access the BootWare Operation menu. =========================<BootWare Operation Menu>========================== Note:the operating device is flash <1> Backup Full BootWare <2> Restore Full BootWare <3> Update BootWare By Serial <4> Update BootWare By Ethernet <0> Exit To Main Menu Enter your choice(0-4): 6. Enter 4 to access the BOOTWARE OPERATION ETHERNET submenu. ===================<BOOTWARE OPERATION ETHERNET SUB-MENU>=================== <1> Update Full BootWare <2> Update Extended BootWare <3> Update Basic BootWare <4> Modify Ethernet Parameter <0> Exit To Main Menu Enter your choice(0-4): 7. Enter 4 to set file transfer parameters. For field description, see Table 6. NOTE: To use the default setting for a field, press Enter without entering any information. ==========================<ETHERNET PARAMETER SET>========================== Note: '.' = Clear field. '-' = Go to previous field. Ctrl+D = Quit. Protocol (FTP or TFTP) :tftp Load File Name Target File Name :test.btw :mpu.btw :test.btw :mpu.btw Server IP Address : Local IP Address : Subnet Mask : Gateway IP Address : Press Ctrl+D to return to the BOOTWARE OPERATION ETHERNET submenu. ===================<BOOTWARE OPERATION ETHERNET SUB-MENU>=================== <1> Update Full BootWare 41

46 <2> Update Extended BootWare <3> Update Basic BootWare <4> Modify Ethernet Parameter <0> Exit To Main Menu Enter your choice(0-4): 9. Enter a number from 1 to 3 as needed. For example, enter 1 to upgrade the entire BootWare image. Loading...Done! bytes downloaded! Updating Basic BootWare? [Y/N] 10. Enter Y to upgrade the basic BootWare segment. Updating Basic BootWare...Done! Updating Extended BootWare? [Y/N] 11. Enter Y to upgrade the extended BootWare segment. Updating Extended BootWare...Done! ===================<BOOTWARE OPERATION ETHERNET SUB-MENU>=================== <1> Update Full BootWare <2> Update Extended BootWare <3> Update Basic BootWare <4> Modify Ethernet Parameter <0> Exit To Main Menu Enter your choice(0-4): 12. Enter 0 in the BOOTWARE OPERATION ETHERNET submenu to return to the BootWare Operation menu. 13. Enter 0 in the BootWare Operation menu to return to the EXTENDED-BOOTWARE menu. 14. Enter 0 in the EXTENDED-BOOTWARE menu to reboot the switch. Using FTP to upgrade through the management Ethernet port This upgrade procedure uses the switch as an FTP client. To upgrade the BootWare image through FTP: 1. Connect the management Ethernet port of the switch to the file server, and connect the console port of the switch to the configuration terminal. The configuration terminal can be co-located with the FTP server. 2. Run an FTP server program on the file server, specify the file path of the upgrade file, and set the FTP username and password. 3. Run the terminal emulation program on the configuration terminal. 4. Start the switch and access the EXTENDED-BOOTWARE menu. 5. Enter 7 in the EXTENDED-BOOTWARE menu to access the BootWare Operation menu. =========================<BootWare Operation Menu>========================== 42

47 Note:the operating device is flash <1> Backup Full BootWare <2> Restore Full BootWare <3> Update BootWare By Serial <4> Update BootWare By Ethernet <0> Exit To Main Menu Enter your choice(0-4): 6. Enter 4 to access the BOOTWARE OPERATION ETHERNET submenu. ===================<BOOTWARE OPERATION ETHERNET SUB-MENU>=================== <1> Update Full BootWare <2> Update Extended BootWare <3> Update Basic BootWare <4> Modify Ethernet Parameter <0> Exit To Main Menu Enter your choice(0-4): 7. Enter 4 to set file transfer parameters. For field descriptions, see Table 7. NOTE: To use the default setting for a field, press Enter without entering any information. ==========================<ETHERNET PARAMETER SET>========================== Note: '.' = Clear field. '-' = Go to previous field. Ctrl+D = Quit. Protocol (FTP or TFTP):ftp Load File Name :test.btw :mpu.btw Target File Name :test.btw :mpu.btw Server IP Address : Local IP Address : Subnet Mask : Gateway IP Address : FTP User Name :abc FTP User Password :pwd 8. Press Ctrl+D to return to the BOOTWARE OPERATION ETHERNET submenu. ===================<BOOTWARE OPERATION ETHERNET SUB-MENU>=================== <1> Update Full BootWare <2> Update Extended BootWare <3> Update Basic BootWare <4> Modify Ethernet Parameter <0> Exit To Main Menu Enter your choice(0-4): 43

48 9. Enter a number from 1 to 3 as needed. For example, enter 1 to upgrade the entire BootWare image. Loading...Done! bytes downloaded! Updating Basic BootWare? [Y/N] 10. Enter Y to upgrade the basic BootWare segment. Updating Basic BootWare...Done! Updating Extended BootWare? [Y/N] 11. Enter Y to upgrade the extended BootWare segment. Updating Extended BootWare...Done! ===================<BOOTWARE OPERATION ETHERNET SUB-MENU>=================== <1> Update Full BootWare <2> Update Extended BootWare <3> Update Basic BootWare <4> Modify Ethernet Parameter <0> Exit To Main Menu Enter your choice(0-4): 12. Enter 0 in the BOOTWARE OPERATION ETHERNET submenu to return to the BootWare Operation menu. 13. Enter 0 in the BootWare Operation menu to return to the EXTENDED-BOOTWARE menu. 14. Enter 0 in the EXTENDED-BOOTWARE menu to reboot the switch. Using Xmodem to upgrade through the console port 1. Connect the console port of the switch to the PC that stores the upgrade image file. 2. Run the terminal emulation program on the PC. 3. Start the switch and access the EXTENDED-BOOTWARE menu. 4. Enter 7 in the EXTENDED-BOOTWARE menu to access the BootWare Operation menu. =========================<BootWare Operation Menu>========================== Note:the operating device is flash <1> Backup Full BootWare <2> Restore Full BootWare <3> Update BootWare By Serial <4> Update BootWare By Ethernet <0> Exit To Main Menu Enter your choice(0-4): 5. Enter 3 to access the BOOTWARE OPERATION SERIAL submenu. ====================<BOOTWARE OPERATION SERIAL SUB-MENU>==================== <1> Update Full BootWare <2> Update Extended BootWare <3> Update Basic BootWare <4> Modify Serial Interface Parameter <0> Exit To Main Menu 44

49 Enter your choice(0-4): 6. Enter 4 to change the baud rate of the console port. ===============================<BAUDRATE SET>=============================== Note:'*'indicates the current baudrate Change The HyperTerminal's Baudrate Accordingly <Baudrate Available> <1> 9600(Default)* <2> <3> <4> <5> <0> Exit Enter your choice(0-5):2 7. Enter an appropriate baud rate option. For example, enter 2 to select bps. Baudrate has been changed to bps. Please change the terminal's baudrate to bps, press ENTER when ready. NOTE: If you choose 9600 bps (the default baud rate), move to step Select Call > Disconnect from the HyperTerminal window to disconnect the HyperTerminal from the switch. Figure 9 Disconnecting the HyperTerminal 9. Select File > Properties in the HyperTerminal window, and click Configure in the popup dialog box. 45

50 Figure 10 Setting switch properties 10. Select from the Bits per second list, and click OK. Figure 11 Modifying the baud rate 46

51 11. Select Call > Call to reconnect to the switch. Figure 12 Reconnecting to the switch 12. Press Enter in the BootWare interface. The current baudrate is bps ===============================<BAUDRATE SET>=============================== Note:'*'indicates the current baudrate Change The HyperTerminal's Baudrate Accordingly <Baudrate Available> <1> 9600(Default) <2> 19200* <3> <4> <5> <0> Exit Enter your choice(0-5): 13. Enter 0 to return to the BOOTWARE OPERATION SERIAL submenu. ====================<BOOTWARE OPERATION SERIAL SUB-MENU>==================== <1> Update Full BootWare <2> Update Extended BootWare <3> Update Basic BootWare <4> Modify Serial Interface Parameter <0> Exit To Main Menu Enter your choice(0-4): 14. Enter a number from 1 to 3 as needed. For example, enter 1 to upgrade the entire BootWare image. Please Start To Transfer File, Press <Ctrl+C> To Exit. Waiting...CCCC 15. Select Transfer > Send File in the HyperTerminal window. In the Send File dialog box, click Browse to select the source file, and select Xmodem from the Protocol list. 47

52 Figure 13 Selecting the file to transfer 16. Click Send. Figure 14 File transfer progress When the file transfer is complete, the following information appears: Download successfully! bytes downloaded! Updating Basic BootWare? [Y/N] 17. Enter Y to upgrade the basic BootWare segment. Updating Basic BootWare...Done! Updating Extended BootWare? [Y/N] 18. Enter Y to upgrade the extended BootWare segment. Updating Extended BootWare...Done! ====================<BOOTWARE OPERATION SERIAL SUB-MENU>==================== <1> Update Full BootWare <2> Update Extended BootWare <3> Update Basic BootWare <4> Modify Serial Interface Parameter <0> Exit To Main Menu 48