Contents

Introduction· 1

Version information· 1

Version number 1

Version history· 1

Hardware and software compatibility matrix· 3

ISSU compatibility list 5

Upgrade restrictions and guidelines· 5

Hardware feature updates· 6

R1113· 6

R1112· 6

R1111· 6

R1110P06· 6

R1110P05· 6

R1110· 6

E1109· 6

E1108· 6

Software feature and command updates· 6

MIB updates· 7

Operation changes· 7

Operation changes in R1113· 7

Operation changes in R1112· 7

Operation changes in R1111· 8

Operation changes in R1110P06· 8

Operation changes in R1110P05· 8

Operation changes in R1110· 8

Operation changes in E1109· 8

Operation changes in E1108· 8

Restrictions and cautions· 8

Open problems and workarounds· 8

List of resolved problems· 13

Resolved problems in R1113· 13

Resolved problems in R1112· 14

Resolved problems in R1111· 17

Resolved problems in R1110P06· 18

Resolved problems in R1110P05· 19

Resolved problems in R1110· 19

Resolved problems in E1109· 20

Resolved problems in E1108· 22

Related documentation· 22

Documentation set 22

Obtaining documentation· 22

Technical support 22

Appendix A Feature list 23

Hardware features· 23

Software features· 25

Appendix B Upgrading software· 29

System software file types· 29

System startup process· 29

Upgrade methods· 30

Upgrading from the CLI 31

Preparing for the upgrade· 31

Downloading software images to the master switch· 32

Upgrading from the Boot menu· 36

Prerequisites· 36

Accessing the Boot menu· 37

Accessing the basic Boot menu· 38

Accessing the extended Boot menu· 39

Upgrading Comware images from the Boot menu· 40

Upgrading Boot ROM from the Boot menu· 48

Managing files from the Boot menu· 55

List of tables

Table 1 Version history· 1

Table 2 Hardware and software compatibility matrix· 3

Table 3 Compatible APs· 4

Table 4 ISSU compatibility list 5

Table 5 MIB updates· 7

Table 6 Technical specifications of the S6520X-EI/HI series(I) 23

Table 7 Technical specifications of the S6520X-EI/HI series(II) 24

Table 8 Software features· 25

Table 9 Minimum free storage space requirements· 36

Table 10 Shortcut keys· 37

Table 11 Basic Boot ROM menu options· 38

Table 12 BASIC ASSISTANT menu options· 39

Table 13 Extended Boot ROM menu options· 39

Table 14 EXTENDED ASSISTANT menu options· 40

Table 15 TFTP parameter description· 41

Table 16 FTP parameter description· 43

Table 17 TFTP parameter description· 49

Table 18 FTP parameter description· 50

Introduction

This document describes the features, restrictions and guidelines, open problems, and workarounds for version S6520X-CMW710-R1113 Before you use this version on 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 S6520X-CMW710-R1113 Release Notes (Software Feature Changes) and the documents listed in "Related documentation."

Version information

Version number

H3C Comware Software, Version 7.1.070, Release 1113

Note: You can see the version number with the display version command in any view. Please see Note①.

Version history

Table 1 Version history

Hardware and software compatibility matrix

Table 2 Hardware and software compatibility matrix

Table 3 Compatible APs

Sample: To display the host software and Boot ROM version of the S6520X-EI/HI perform the following:

<H3C> display version

H3C Comware Software, Version 7.1.070, Release 1113   ------- Note①                         

Copyright (c) 2004-2019 New H3C Technologies Co., Ltd. All rights reserved.    

H3C S6520X-30QC-EI uptime is 0 weeks, 2 days, 8 hours, 50 minutes              

Last reboot reason : User reboot                                                

Boot image: flash:/s6520x-cmw710-boot-r1113.bin                                

Boot image version: 7.1.070, Release 1113                                       

  Compiled Jan 11 2019 11:00:00                                                

System image: flash:/s6520x-cmw710-system-r1113.bin                            

System image version: 7.1.070, Release 1113                                    

  Compiled Jan 11 2019 11:00:00                                                

Slot 1:                                                                        

Uptime is 0 weeks,2 days,8 hours,50 minutes                                    

S6520X-54QC-EI with 2 Processors                                               

BOARD TYPE:         S6520X-54QC-EI                                             

DRAM:               2048M bytes                                                

FLASH:              1024M bytes                                                

PCB 1 Version:      VER.A                                                       

Bootrom Version:    107    ------ Note②                                                    

CPLD 1 Version:     002                                                        

CPLD 2 Version:     004                                                         

Release Version:    H3C S6520X-54QC-EI-1113                                    

Patch Version  :    None                                                       

Reboot Cause  :     UserReboot                                                  

[SubSlot 0] 48SFP Plus + 2QSFP Plus

ISSU compatibility list

ISSU provides two upgrade types: compatible upgrade and incompatible upgrade. Table 4 provides the approved ISSU upgrade types only between the current version and the history versions within the past 18 months. This matrix does not include history versions that are 18 months earlier than the current version, for which, no ISSU upgrade verification is performed. For more information about ISSU, see Fundamentals Configuration Guide in H3C S6520X Switch Series Configuration Guides.

Table 4 ISSU compatibility list

Upgrade restrictions and guidelines

Before performing a software upgrade, it is important to refer to the Software Feature Changes document for any feature changes in the new version. Also check the most recent version of the related documents (see "Related documentation") available on the H3C website for more information about feature configuration and commands.

Hardware feature updates

R1113

None.

R1112

None.

R1111

None.

R1110P06

None.

R1110P05

None.

R1110

None.

E1109

S6520X-30HC-EI, S6520X-30HC-HI, S6520X-54HC-EI, S6520X-54HC-HI, LSWM2ZSP8P, and LSWM2ZQP2P are supported.

E1108

First release.

Software feature and command updates

For more information about the software feature and command update history, see H3C S6520X-CMW710-R1113 Release Notes (Software Feature Changes).

MIB updates

Table 5 MIB updates

Operation changes

Operation changes in R1113

None.

Operation changes in R1112

None.

Operation changes in R1111

None.

Operation changes in R1110P06

None.

Operation changes in R1110P05

None.

Operation changes in R1110

None.

Operation changes in E1109

None.

Operation changes in E1108

First release.

Restrictions and cautions

None.

Open problems and workarounds

201805230145

·            Symptom: An IRF fabric splits and the master member device is rebooted unexpectedly.

·            Condition: This symptom occurs if heterogeneous IRF loops are formed in a specific network environment.

·            Workaround: None.

201808240664

·      Symptom: The bridging feature does not take effect on L2VPN traffic on an interface configured with VXLAN ACs.

·      Condition: This symptom might occur if bridging is enabled on an interface configured with VXLAN ACs.

·      Workaround: None.

201803140142

·      Symptom: On an IRF fabric that uses the ring topology, an interface receives broadcast traffic in a VLAN. When any of the IRF member devices is rebooted, broadcast storms occur on IRF physical interfaces of the rebooted device, and other IRF member devices’ ports in the same VLAN as the IRF physical interfaces receive a large amount of data traffic.

·      Condition: This symptom might occur if an interface on a member device in an IRF fabric that uses the ring topology receives broadcast traffic in a VLAN, and any of the IRF member devices is rebooted.

·      Workaround: None.

201809060789

·            Symptom: When a 40-GE interface on an LSWM2QP2P interface module is split into breakout interfaces and the breakout interfaces are assigned to a service loopback group, the CLI is hung.

·            Condition: This symptom occurs if the following operations are repeatedly performed for a 40-GE interface on an LSWM2QP2P interface module on an IRF fabric:

a.    Split the interface into breakout interfaces and combine the breakout interfaces.

b.   Bind the interface to an IRF port and remove the binding.

c.    Assign the breakout interfaces to and remove them from a service loopback group.

·            Workaround: None.

201807270579

·            Symptom: When you execute the issu run switchover command after upgrading a subordinate IRF member device, the system prompts that the operation failed and the software cannot be upgraded successfully.

·            Condition: This symptom occurs if ISSU for multichassis IRF fabrics is not supported.

·            Workaround: None.

201811220408

·            Symptom: VCFC failed to automatically deploy PBR configuration to the device.

·            Condition: This symptom occurs if the automatically deployed PBR configuration contains ACLs with VPNs.

·            Workaround: None.

201811190730/201810310518

·            Symptom: When no traffic exists for MAC authentication users, MAC authentication users always exist, but the MAC addresses of these users will age out and be deleted.

·            Condition: This symptom occurs if MAC authentication is enabled and MAC authentication offline detection is disabled on an interface in a VXLAN network.

·            Workaround: None.

201811120212

·            Symptom: Some MAC addresses of VSIs are lost after a master/subordinate switchover.

·            Condition: This symptom occurs if an aggregate interface is configured with multiple ACs, each AC is associated with a VSI, ACs learn MAC addresses, and a master/subordinate switchover is performed.

·            Workaround: None.

201811120193

·            Symptom: In an EVPN network, the MAC address entries displayed by using the display l2vpn mac-address and display evpn route mac local commands are inconsistent.

·            Condition: This symptom occurs if the following operations are performed:

a.    An aggregate interface is configured with multiple ACs. The aggregate interface receives traffic continuously for a period of time. The ACs learn MAC address entries.

b.   Use the display l2vpn mac-address and display evpn route mac local commands to display the learned MAC address entries.

·            Workaround: None.

201811070629

·            Symptom: When an AC on a 6520X device receives private network traffic, no statistics are collected for the traffic.

·            Condition: This symptom occurs if the statistics enable command is configured on a VSI of a 6520X device in a VXLAN network.

·            Workaround: None.

201811060796

·            Symptom: When an AC of the device receives IGMP queries, they cannot be forwarded.

·            Condition: This symptom occurs if a VSI interface has IGMP snooping enabled and configured with the flooding disable all command in a VXLAN network.

·            Workaround: None.

201810310065

·            Symptom: BFD sessions might flap.

·            Condition: This symptom occurs if a subcard is inserted.

·            Workaround: Insert a subcard before configuring BFD.

201810160530

·            Symptom: When the configured MAC learning limit is reached and the device is disabled from forwarding unknown frames after the MAC learning limit is reached, some unknown frames can still be forwarded.

·            Condition: This symptom occurs if the MAC learning limit is configured and the device is disabled from forwarding unknown frames after the MAC learning limit is reached.

·            Workaround: None.

201812030539

·            Symptom: When BFD MAD is configured, packets destined for UDP port 6784 or 4784 match a wrong ACL and thus are sent to the CPU.

·            Condition: This symptom might occur if the switch configured with BFD MAD receives packets with destination UDP port 6784 or 4784.

·            Workaround: Make sure the switch does not receive packets with destination UDP port 6784 or 4784.

201812120294

·            Symptom: Tunneled public network traffic received from a GRE tunnel cannot be forwarded after de-encapsulation if the incoming interface is a Layer 3 interface and the GRE tunnel uses private IP addresses for encapsulation.

·            Condition: This symptom might occur if a Layer 3 interface receives tunneled public network traffic forwarded through a GRE tunnel that uses private IP addresses for encapsulation.

·            Workaround: None.

201810090212/201810090210

·            Symptom: The switch cannot send ARP packets to the controller.

·            Condition: This symptom might occur if the ARP packets sent by VMs belong to an EVLAN whose ID has the same lower 12 bits as an inband management VLAN ID.

·            Workaround: Make sure an EVLAN ID and an inband management VLAN ID do not have the same lower 12 bits.

201812180528

·            Symptom: The management Ethernet interface on the switch is up, but it is not up and cannot be operated on IMC.

·            Condition: This symptom might occur if the management Ethernet interface is operated through IMC.

·            Workaround: None.

201901290587

·            Symptom: The jumboframe enable command does not take effect on a 100G interface on the front panel if certain operations are performed on that interface.

·            Condition: This symptom might occur if the following operations are performed on a 100G interface on the front panel:

a.    Connect it to a peer interface by using a 100G cable.

b.   Execute the jumboframe enable command.

c.    Shut down and then bring up the peer interface, or re-install the interface module where the peer interface resides.

·            Workaround: Perform one of the following operations:

¡  Execute the jumboframe enable command again on the local 100G interface.

¡  Re-install the interface module where the local 100G interface resides, or shut down and then bring up this interface.

¡  Replace the copper cable with an optical cable.

201811060796

·            Symptom: A VSI is enabled with IGMP snooping and disabled with flooding. When an AC of the VSI receives IGMP queries, the switch cannot transmit the packets to peers through software-based forwarding.

·            Condition: This symptom might occur if a VSI is enabled with IGMP snooping and disabled with flooding.

·            Workaround: None.

201812120294

·            Symptom: The switch cannot forward the public traffic received from a GRE tunnel that uses private IP addresses for tunnel encapsulation if the traffic incoming interface is a Layer 3 interface.

·            Condition: This symptom might occur if a GRE tunnel uses private IP addresses for tunnel encapsulation and the incoming interface for tunneled public traffic is a Layer 3 interface.

·            Workaround: None.

201812190695

·            Symptom: After Layer 3 aggregate subinterfaces are configured, the MAC address learning rate slows down on the main aggregate interface.

·            Condition: This symptom might occur if subinterfaces are created on a Layer 3 aggregate interface, and that interface forwards traffic constantly.

·            Workaround: Do not create Layer 3 aggregate subinterfaces.

201812210690

·            Symptom: When AAA authentication and password control are enabled, Telnet or SSH login takes about 20 seconds.

·            Condition: This symptom might occur if AAA authentication and password control are enabled.

·            Workaround: None.

201901280503

·            Symptom: An IRF fabric formed by S5560X-30F-EI switches splits twice before it becomes stable.

·            Condition: This symptom might occur if abnormal IPC packets are transmitted because the switches do not filter these packets.

·            Workaround: Remove abnormal IPC packets.

201901190109

·            Symptom: A port blocked by RRPP permits loop detection packets.

·            Condition: This symptom might occur if the following conditions exist:

¡  Loop detection is enabled globally.

¡  Loop detection packets are transmitted on a per-VLAN basis, and the switch ignores the blocked state of the outgoing interface for loop detection packets.

·            Workaround: Configure the switch to check whether the outgoing interface for loop detection packets is blocked if loop detection packets are transmitted on a per-VLAN basis.

201901240143

·            Symptom: The IP addresses in the output from the debug qacl show slot x chip x verbose x acl-type x sip x command start with the lowest-order octet.

·            Condition: This symptom might occur if the debug qacl show slot x chip x verbose x acl-type x sip x command is executed.

·            Workaround: None.

201901180043

·            Symptom: On an IRF fabric configured through automated deployment, a port not configured with link aggregation joins a link aggregation group after a master/subordinate switchover.

·            Condition: This symptom might occur if a master/subordinate switchover occurs on an IRF fabric configured through automated deployment.

·            Workaround: None.

201901180848

·            Symptom: In a VCF fabric deployed on a campus network, when an access node reboots, the aggregate interface connected to the access node is automatically deleted from a leaf node.

·            Condition: This symptom might occur if the following conditions exist:

a.    The links between the leaf node and the access node are aggregated automatically.

b.   The director issues configuration to the downlink aggregate interface of the leaf node.

c.    The access node connected to the downlink aggregate interface reboots.

·            Workaround: None.

201805110166

·            Symptom: The interfaces on the LSW2ZSP2P module cannot come up if configured with the port up-mode command.

·            Condition: This symptom might occur if the port up-mode command is executed on interfaces of the LSW2ZSP2P module.

·            Workaround: None.

201808230435

·            Symptom: An interface enabled with SP queuing forwards low-priority traffic.

·            Condition: This symptom might occur if an interface enabled with SP queuing receives traffic with different priorities.

·            Workaround: None.

201812240778

·            Symptom: A 100G interface receives CRC error packets or jumbo frames constantly. When the traffic stops, the number of aborts packets on that interface becomes 0.

·            Condition: This symptom might occur if a 100G interface receives CRC error packets or jumbo frames constantly.

·            Workaround: None.

201901290301

·            Symptom: An IRF fabric cannot forward Layer 3 traffic correctly if it splits and then reunites.

·            Condition: This symptom might occur if the IRF bridge MAC address changes.

·            Workaround: None.

List of resolved problems

Resolved problems in R1113

201811090456/201811120477

·            Symptom: QoS WRR scheduling and SP scheduling are inaccurate.

·            Condition: This symptom occurs if the following conditions exist:

¡  Rate limiting in the outbound direction and QoS WRR queueing are configured on an interface.

¡  Rate limiting in the outbound direction and QoS SP queueing are configured on an interface.

·            Workaround: None.

201810290425

·            Symptom: The maximum number of IGMP multicast groups decreases.

·            Condition: This symptom occurs if both the multicast incoming interface and the multicast outgoing interface are Layer 3 Ethernet interfaces, and then the outgoing interface is changed to a VLAN interface.

201812070260

·            Symptom: IMC displays incorrect information about the four 25-GE breakout interfaces split from a 100-GE interface on the LSWM2ZSP2P module.

·            Condition: This symptom might occur if two 100-GE interfaces on the LSWM2ZSP2P module are split into 25-GE breakout interfaces.

201812100295

·            Symptom: When the switch forwards unfragmentable IPv4 packets larger than the MTU of the outgoing interface, it sends ICMP error messages sourced from 0.0.0.0 or 127.0.0.1 instead of the IP address of the Layer 3 management interface.

·            Condition: This symptom might occur if the switch forwards unfragmentable IPv4 packets larger than the MTU of the outgoing interface.

201809030214

·            Symptom: The state of the management Ethernet interface is incorrect in IMC.

·            Condition: This symptom might occur if the state of the up management Ethernet interface is viewed in IMC.

201901240507

·            Symptom: On an IRF fabric, the MAC addresses obtained by using SNMP are inconsistent with those displayed by using the display mac-address command.

·            Condition: This symptom might occur if the following conditions exist on an IRF fabric:

¡  No multichassis aggregation group is configured.

¡  MAC address synchronization is disabled.

¡  No inter-chassis traffic exists.

201901090479

·            Symptom: The switch reboots unexpectedly and cannot be accessed if certain transceiver modules are installed on a large number of interfaces.

·            Condition: This symptom might occur if certain transceiver modules have frequent RxLOS signal changes after being installed on some interfaces.

201812250549

·            Symptom: A PC Telnets to Device A, and Device A Telnets to Device B. If the Telnet connection of the PC is closed when Device A and Device B are communicating with each other, Device A has residual Telnet processes, high CPU usage, and service interruption.

·            Condition: This symptom might occur if the following conditions exist:

¡  A PC Telnets to Device A, and Device A Telnets to Device B.

¡  The Telnet connection of the PC is closed when Device A and Device B are communicating with each other.

Resolved problems in R1112

201711270359

·            Symptom: IPv6 packets passing a GRE over IPv4 tunnel are not correctly forwarded.

·            Condition: This symptom occurs if a GRE over IPv4 tunnel is established, and IPv6 packets pass the tunnel.

201808200560

·      Symptom: The memory usage of the device is too high, and alarms are generated.

·      Condition: This symptom occurs if the following conditions exist:

¡  The number of DHCPv6 snooping entries that an interface can learn is not limited.

¡  DHCPv6 clients apply for a large number of IPv6 addresses from the DHCPv6 server through the DHCPv6 snooping device.

201809030214

·            Symptom: When sFlow-related commands are executed on a device, the CLI is stuck.

·            Condition: This symptom occurs if sFlow is enabled on multiple interfaces and the device continuously receives traffic, which will be sampled by sFlow.

201809260190

·            Symptom: The qinq enable command configuration on an interface is lost.

·            Condition: This symptom occurs if ISSU is used to upgrade/downgrade the software or reboot the device after an interface is configured with both QinQ and VLAN mapping.

201811270062

·            Symptom: The device does not generate IPSG entries for 802.1X users.

·            Condition: This symptom occurs if 802.1X user come online and obtain IP addresses through DHCPv6.

201811230729

·            Symptom: An access node is automated and connected to a leaf node through two uplinks and the two links are automatically aggregated. However, the topology shows that there are multiple links between the access node and the leaf node, and there is no aggregate interface in the interface group of each node.

·            Condition: This symptom occurs if an access node is automated and connected to a leaf node through two uplinks and the two links are automatically aggregated.

201811220103

·            Symptom: ARP packets cannot be sent to the CPU.

·            Condition: This symptom occurs if an OpenFlow entry that sends ARP packets to the CPU is deployed to the device and then the corresponding VLAN is configured.

201811190549

·            Symptom: IPv6 or MPLS packets of an aggregate interface cannot be matched.

·            Condition: This symptom occurs if OpenFlow deploys a flow entry that matches the incoming traffic of an aggregate interface and uses a physical interface as the outgoing interface.

201811160063

·            Symptom: An interface cannot join a voice VLAN again after leaving the voice VLAN.

·            Condition: This symptom occurs if the following conditions exist:

¡  On an IRF fabric, enable LLDP on an interface on the subordinate device and assign the interface to a voice VLAN. Connect the interface to a voice device that supports LLDP or CDP.

¡  Establish or disconnect the LLDP neighbor relationship on the subordinate device.

201811160037

·            Symptom: Some clients cannot access the network.

·            Condition: This symptom occurs if 802.1X is enabled on an aggregate interface, 1000 users come online in a VLAN, and each user obtains IP addresses through DHCP.

201811120127

·            Symptom: The memory leaks.

·            Condition: This symptom occurs if DHCP/DHCPv6 flood attack protection is repeatedly enabled and disabled and a member device is repeatedly rebooted on an IRF fabric.

201811100117

·            Symptom: The service chain that forwards traffic is not the one configured by the user.

·            Condition: This symptom occurs if the apply service-chain command is used to set the service chain information when applying a PBR policy to the outbound direction of a VXLAN tunnel interface.

201811100091

·            Symptom: OpenFlow issues an IPv6 flow entry unexpectedly when issuing an IPv4 flow entry.

·            Condition: This symptom occurs if OpenFlow issues an IPv4 flow entry that matches the Ethernet type 0x0800.

201811070218

·            Symptom: DHCP flood attack protection errors are printed if a master/subordinate switchover is performed for an IRF fabric.

·            Condition: This symptom occurs if a master/subordinate switchover is performed for an IRF fabric.

201809300526

·            Symptom: The buildruns and prompt messages for the proxy-nd enable and local-proxy-nd enable commands are different on the master device and subordinate device. After a master/subordinate switchover is performed for the IRF fabric, the configurations of the two commands are lost.

·            Condition: This symptom occurs if the proxy-nd enable and local-proxy-nd enable commands are executed on an IRF fabric and then a master/subordinate switchover is performed for the IRF fabric.

201812100822

·            Symptom: Layer 3 traffic of a Layer 3 Ethernet subinterface is falsely forwarded by using a route entry of the VPN instance bound to the main interface.

·            Condition: This symptom might occur if a Layer 3 Ethernet interface and its subinterface are bound to different VPN instances.

201811230526

·            Symptom: When port security is enabled, the switch halts after the display port-security command is executed until the Ctrl+C key combination is used.

·            Condition: This symptom might occur if the following conditions exist:

a.    Secure MAC addresses are configured, the maximum number of secure MAC addresses allowed on an interface is set to 1, and the intrusion protection mode is set to disableport-temporarily on the interface.

b.   A user PC comes online on the interface, and the switch learns the MAC address of the PC. Then an LLDP-capable PC comes online on the same interface.

201812140651

·            Symptom: If all IRF physical interfaces on an IRF member device are provided by the extension interface modules in the same slot, the IRF physical interfaces might go down and then come up in 30 seconds, which causes unwanted IRF fabric split and reunion.

·            Condition: This symptom might occur if all IRF physical interfaces on an IRF member device are provided by the extension interface modules in the same slot.

·            Workaround: Use extension interface modules in different slots to provide IRF physical interfaces on an IRF member device, or use both the interfaces on the front panel and the interfaces on extension interface modules as IRF physical interfaces.

201812180280

·            Symptom: It takes the switch 40 to 70 seconds to learn a MAC address when Layer 3 aggregate interfaces are performing Layer 3 forwarding.

·            Condition: This symptom might occur if the switch learns MAC addresses when Layer 3 aggregate interfaces are performing Layer 3 forwarding.

Resolved problems in R1111

201810090296/201810100054/201810120233

·            Symptom: The following problems occur:

¡  When a portal user performs authentication, the portal authentication page does not open on the user's endpoint.

¡  After a portal user comes online and then clicks Log out on the portal page, the user can still access the network.

·            Condition: This symptom occurs if the following operations are performed:

a.    Multiple MAC-portal users first perform authentication to come online in the BYOD VSI. Then, a user performs second authentication to come online in the service VSI. Then, the user in the service VSI goes offline and then comes online through one of the following operations:

-       The user goes offline and then comes online when the transparent authentication status of the user expires and becomes invalid on the Director server.

-       The user clicks Log out on the authentication success page to go offline, and then comes online.

b.   All users go offline and then come online, and users in the BYOD VSI first come online.

201809300345/201810110697

·            Symptom: When the device is running, the CLI might be stuck and you cannot enter commands at the CLI.

·            Condition: This symptom occurs if ACLs containing counting rules are repeatedly added and deleted.

201810150207

·            Symptom: A portal user fails to come online, and ACL resources remain.

·            Condition: This symptom occurs if the ACL resources of the device are insufficient when a portal user is being assigned an ACL after coming online.

201806040553

·            Symptom: The NMS fails to synchronize the ACL and VLAN information through SNMP.

·            Condition: This symptom occurs if the NMS synchronizes the ACL and VLAN information through SNMP.

201808200580

·      Symptom: The port index is calculated incorrectly. The port does not match the port issued on the device.

·      Condition: This symptom occurs if sFlow is issued by IMC.

201809180685

·            Symptom: When an aggregate interface to which ACLs are issued by IP source guard is deleted, ACLs rules are not correctly deleted, and some ACLs remain. ACLs issued by IP source guard do not meet the specifications.

·            Condition: This symptom occurs if an aggregate interface is configured with multiple ACs and the IP source guard feature, which will issue ACLs to the aggregate interface.

201804020003

·            Symptom: When the MTU is set to 64000 for a tunnel interface, the value that actually takes effect is 1480.

·            Condition: This symptom occurs if the MTU is set to 64000 for a tunnel interface.

201803140144

·            Symptom: Traffic storms exist on IRF physical interfaces transiently.

·            Condition: This symptom occurs if a member device of a ring-topology IRF fabric receives unknown unicast or multicast packets and the device is rebooted at the same time.

201805280088

·            Symptom: Though the member priority of a device with more interfaces is high, it cannot become the master device.

·            Condition: This symptom occurs if S6520X switches of the same series but with different number of interfaces form an IRF fabric.

201808210429/201808270683

·      Symptom: After the priority trust mode is set to DSCP and a DSCP-DSCP priority mapping table is applied to an interface, the interface fails to modify the DSCP value of packets.

·      Condition: This symptom might occur if the priority trust mode is set to DSCP and a DSCP-DSCP priority mapping table is applied to an interface.

201807240090

·            Symptom: The device cannot internally synchronize the learned MAC address entries.

·            Condition: This symptom occurs if the port-security free-vlan command is executed in interface view to configure the port security free VLANs. 

201803140626

·            Symptom: An aggregate interface learns MAC address entries incorrectly. As a result, the aggregate interface forwards traffic improperly.

·            Condition: This symptom occurs if the whole device is rebooted when the aggregate interface has configuration.

201811080922

·            Symptom: The device reboots unexpectedly.

·            Condition: This symptom occurs if the qos sp command is executed on an interface of a subcard.

201810220659

·            Symptom: An interface bound to a VPN cannot be successfully pinged from a directly connected device.

·            Condition: This symptom occurs if the interface is bound to a VPN by using the ip binding vpn-instance vpn-instance-name command.

Resolved problems in R1110P06

201808100515

·            Symptom: On an IRF fabric, two copies of each BUM packet of VXLAN are forwarded on the IRF physical interfaces.

·            Condition: This symptom occurs if the IRF fabric acts as a VTEP and the IRF fabric has a member device with slot number 1.

201808060514

·            Symptom: In an EVPN network, BGP and tunnel states flap.

·            Condition: This symptom occurs if an aggregation group is configured with a large number of ACs and IP source guard configurations, and the default command is executed on the corresponding aggregate interface to restore the default settings.

201808160633

·      Symptom: The STP status of ports on an STP-enabled device is incorrect.

·      Condition: This symptom occurs if three devices form a ring network, one device has STP disabled and TC snooping enabled and the other two devices has STP enabled.

Resolved problems in R1110P05

201805070687

·            Symptom: The memory leaks.

·            Condition: This symptom occurs if the configuration file contains QinQ-related configuration and configuration rollback is repeatedly performed for the device.

201808240158/201808240038

·            Symptom: Packets matching a deny node of a routing policy are not forwarded by routes.

·            Condition: This symptom occurs if a routing policy is configured with a deny node.

201808100627

·            Symptom: A user might fail to log in through Web authentication.

·            Condition: This symptom occurs if the following conditions exist:

¡  An interface has both 802.1X authentication and Web authentication enabled.

¡  A user logs in through Web authentication, and sends ARP packets to the device during the login process.

201808070475

·            Symptom: When a user uses packets that carry VLAN tags not permitted by the authentication interface to perform MAC authentication, the user can successfully come online mistakenly.

·            Condition: This symptom occurs if the authentication interface is an aggregate interface.

201807250096

·            Symptom: On a distributed VXLAN gateway network, a DHCP or DHCPv6 client cannot obtain an IP or IPv6 address from the DHCP or DHCPv6 server.

·            Condition: This symptom occurs if the VTEP where the distributed VXLAN gateway acting as the DHCP or DHCPv6 server resides is different from the VTEP to which the DHCP or DHCPv6 client is attached.

Resolved problems in R1110

201804120630

·            Symptom: Some member devices fail to download the upgrade file from the FTP server. The display smartmc upgrade status command output shows that the upgrade status of some member devices is always Downloading.

·            Condition: This symptom occurs if the smartmc upgrade boot-loader command is executed on the commander to upgrade the startup software for multiple member devices at the same time in a SmartMC network.

201804220003

·            Symptom: On a multichassis IRF fabric of the daisy-chain topology, broadcast storms occur on the IRF physical interfaces.

·            Condition: This symptom occurs if the following conditions exist:

¡  The IRF physical interfaces of an IRF member device are connected to common service interfaces of another IRF member device.

¡  There is an IRF physical interface with the internal port number as 0 (the value in the Port column in the output from the debug port mapping command in probe view).

201804230140

·            Symptom: On an IRF fabric, if a member port on an IRF member device joins or leaves a multichassis aggregation group, the ports with the same number on the other member devices become invalid.

·            Condition: This symptom occurs if member ports join or leave a multichassis aggregation group on an IRF fabric.

201804230274

·            Symptom: MAC address entries remain in the lower layer.

·            Condition: This symptom occurs if multiple multiport unicast MAC address entries are configured and then deleted.

201712260679/201712260676

·            Symptom: Packets cannot be forwarded through short-mask ECMP routes.

·            Condition: This symptom occurs if short-mask static ECMP routes are first issued and then long-mask static ECMP routes are issued and these ECMP routes overlap.

201808060061

·            Symptom: Port isolation does not take effect on packets forwarded through the CPU.

·            Condition: This symptom occurs if interfaces are assigned to a port isolation group.

201808140149

·            Symptom: When ARP attack protection is enabled, the rate of ARP packets sent to the CPU is limited to 50 pps.

·            Condition: This symptom occurs if the rate of packets sent to the CPU is 490 pps, which triggers ARP attack protection.

Resolved problems in E1109

201802270713

·            Symptom: The device might reboot in an endless loop.

·            Condition: This symptom occurs if the device is configured as the DHCP server and some packets are forwarded through the CPU.

201802060662

·            Symptom: When a 1000-Mbps transceiver module is plugged in a 10-GE interface, the interface cannot forward traffic.

·            Condition: This symptom occurs if the 10-GE interface with a 1000-Mbps transceiver module plugged receives Layer 3 packets longer than 86 bytes.

201802080178

·            Symptom: When a 40G cable with product code LSWM1QSTK2 (produced by AMPHENO) is installed in an interface, the device cannot start.

·            Condition: This symptom occurs if a QSFP+ interface on the front panel has a 40G cable with product code LSWM1QSTK2 (produced by AMPHENO) installed and the device is started.

201711270652

·            Symptom: Layer 3 packets with the destination unreachable do not match the default route. Instead, these packets are sent to the CPU for software forwarding.

·            Condition: This symptom occurs if the following operations are performed:

a.    Configure the default route 0.0.0.0/0.

b.   Configure the ip unreachables enable command.

201711100161

·            Symptom: The master IRF member device reboots because the memory is exhausted.

·            Condition: This symptom occurs if interactions exist between the IRF member devices (for example, a large number of configurations are repeatedly added and deleted for a long period of time), which cause the master and subordinate member devices to continuously perform synchronization.

201711040204

·            Symptom: On a distributed gateway, the vxlan vni 1 command is configured in VLAN view. The system prompts that the configuration succeeds. However, the vxlan vni 1 command configuration does not exist in VLAN view.

·            Condition: This symptom occurs if the following operations are performed when there are a large number of ACs and VLANs (for example, 3000 ACs and 500 VLANs):

¡  Associate a VLAN with the specified VXLAN.

¡  Execute the undo vlan command.

201711030393

·            Symptom: On an IRF fabric, the ARP flood suppression entry configuration is not the same on the master and subordinate member devices.

·            Condition: This symptom occurs if the arp suppression enable and vxlan commands are executed for many times.

201711270365

·            Symptom: In a VXLAN network, traffic cannot be forwarded if the VXLAN tunnel interface and the corresponding AC interface are on the same interface module.

·            Condition: This symptom occurs if the following conditions exist:

¡  The VXLAN tunnel interface and AC interface are on the same interface module.

¡  VXLAN packets from the tunnel are received, with the outgoing interface as the AC interface on the same interface module.

¡  The AC interface has a 1000_BASE_T_AN_SFP transceiver module installed.

201711290205

·            Symptom: When the ACL used in step c is deleted, the ACL resource is not released.

·            Condition: This symptom occurs if the following operations are performed:

a.    Create an advanced IPv4 or IPv6 ACL.

b.   Use the operator lt, gt, neq, or range in an ACL rule to specify multiple port numbers to match packets.

c.    Use the ACL created in step a for packet filtering in the outbound direction of an interface.

201711290337

·            Symptom: In a VXLAN network, AC resources are not released.

·            Condition: This symptom occurs if a large number of ACs are configured on an aggregate interface and then the aggregate interface is deleted.

201711240609

·            Symptom: In a multiport ARP network, the device connected to multiple ports cannot communicate with a device configured with multiport ARP.

·            Condition: This symptom occurs if a multiport ARP network is configured..

Resolved problems in E1108

First release.

Related documentation

Documentation set

·            H3C S6520X-EI & S6520X-HI Switch Series Installation Quick Start

·            H3C S6520X-EI & S6520X-HI Switch Series Installation Guide

·            H3C PSR250-12A & PSR250-12A1 Power Modules User Manual

·            H3C LSWM1FANSCE & LSWM1FANSCBE Fan Trays User Guide

·            H3C LSWM2QP2P Interface Card User Manual

·            H3C LSWM2SP8PM & LSWM2SP8P Interface Cards User Manual

·            H3C LSWM4SP8PM Interface Card User Manual

·            H3C S6520X-EI & S6520X-HI Switch Series Configuration Guides

·            H3C S6520X-EI & S6520X-HI Switch Series Command References

·            H3C LSWM2SP2PM Interface Card User Manual

·            H3C LSPM6FWD Card Manual

·            H3C LSWM2ZQP2P Interface Card User Manual

·            H3C LSWM2ZSP8P Interface Card User Manual

Obtaining documentation

To obtain the related documents from the H3C website at www.h3c.com.hk:

1.       Click http://www.h3c.com.hk/Technical_Documents.

2.       Choose the desired product category and model.

Technical support

service@h3c.com

http://www.h3c.com.hk

Appendix A Feature list

Hardware features

Table 6 Technical specifications of the S6520X-EI/HI series(I)

Table 7 Technical specifications of the S6520X-EI/HI series(II)

Software features

Table 8  Software features

Appendix B Upgrading software

This chapter describes types of software used on the switch and how to upgrade software while the switch is operating normally or when the switch cannot correctly start up.

System software file types

Software required for starting up the switch includes:

·            Boot ROM image—A .bin file that comprises a basic section and an extended section. The basic section is the minimum code that bootstraps the system. The extended section 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 switch cannot correctly start up.

·            Software images—Includes boot images and system images.

¡  Boot image—A .bin file that contains the operating system kernel. It provides process management, memory management, file system management, and the emergency shell.

¡  System image—A .bin file that contains the minimum modules required for device operation and some basic features, including device management, interface management, configuration management, and routing management.

The software images that have been loaded are called “current software images.” The software images specified to load at next startup are called “startup software images.”

These images might be released separately or as a whole in one .ipe package file. If an .ipe file is used, the system automatically decompresses the file, loads the .bin boot and system images in the file and sets them as startup software images. Typically, the Boot ROM and software images for this switch series are released in an .ipe file named main.ipe.

System startup process

Upon power-on, the Boot ROM image runs to initialize hardware and then the software images run to start up the entire system, as shown in Figure 1.

Figure 1 System startup process

Upgrade methods

You can upgrade system software by using one of the following methods:

The output in this document is for illustration only and might vary with software releases. This document uses boot.bin and system.bin to represent boot and system image names. The actual software image name format is chassis-model_Comware-version_image-type_release, for example, S6520X-CMW710-BOOT-Rxxxx.bin and S6520X-CMW710-SYSTEM-Rxxxx.bin.

Upgrading from the CLI

This section uses a two-member IRF fabric as an example to describe how to upgrade software from the CLI. If you have more than two subordinate switches, repeat the steps for the subordinate switch to upgrade their software. If you are upgrading a standalone switch, ignore the steps for upgrading the subordinate switch. For more information about setting up and configuring an IRF fabric, see the installation guide and Virtual Technologies configuration guide for the H3C S6520X-EI & S6520X-HI switch series.

Preparing for the upgrade

Before you upgrade software, complete the following tasks:

1.       Log in to the IRF fabric through Telnet or the console port. (Details not shown.)

2.       Identify the number of IRF members, each member switch's role, and IRF member ID.

<Sysname> display irf

MemberID   Role   Priority  CPU-Mac         Description

 *+1      Master  5         0023-8927-afdc  ---

   2      Standby 1         0023-8927-af43  ---

--------------------------------------------------

 * indicates the device is the master.

 + indicates the device through which the user logs in.

 The Bridge MAC of the IRF is: 0023-8927-afdb

 Auto upgrade                : no

 Mac persistent              : 6 min

 Domain ID                   : 0

3.       Verify that each IRF member switch has sufficient storage space for the upgrade images.

# Identify the free flash space of the master switch.

<Sysname> dir

Directory of flash:

     0      -rw-       41424  Aug 23 2013 02:23:44     startup.mdb

     1      -rw-        3792  Aug 23 2013 02:23:44     startup.cfg

     2      -rw-    53555200  Aug 23 2013 09:53:48     system.bin

     3      drw-           -  Aug 23 2013 00:00:07     seclog

     4      drw-           -  Aug 23 2013 00:00:07     diagfile

     5      drw-           -  Aug 23 2013 00:00:07     logfile

     6      -rw-     9959424  Aug 23 2013 09:53:48     boot.bin

     7      -rw-     9012224  Aug 23 2013 09:53:48     backup.bin

524288 KB total (453416 KB free) 

# Identify the free flash space of each subordinate switch, for example, switch 2.

<Sysname> dir slot2#flash:/

Directory of slot2#flash:/

     0      -rw-       41424  Jan 01 2011 02:23:44     startup.mdb

     1      -rw-        3792  Jan 01 2011 02:23:44     startup.cfg

     2      -rw-    93871104  Aug 23 2013 16:00:08     system.bin

     3      drw-           -  Jan 01 2011 00:00:07     seclog

     4      drw-           -  Jan 01 2011 00:00:07     diagfile

     5      drw-           -  Jan 02 2011 00:00:07     logfile

     6      -rw-     13611008  Aug 23 2013 15:59:00     boot.bin

     7      -rw-     9012224  Nov 25 2011 09:53:48     backup.bin

524288 KB total (453416 KB free)

4.       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 not, go to the next step.

5.       Delete unused files in the flash memory to free space:

# 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...

Deleting file flash:/backup.bin...Done.

# 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...

Deleting file slot2#flash:/backup.bin...Done.

Downloading software images to the master switch

Before you start upgrading software images packages, make sure you have downloaded the upgrading software files to the root directory in flash memory. This section describes downloading an .ipe software file as an example.

The following are ways to download, upload, or copy files to the master switch:

·            FTP download from a server

·            FTP upload from a client

·            TFTP download from a server

Prerequisites

If FTP or TFTP is used, the IRF fabric and the PC working as the FTP/TFTP server or FTP client can reach each other.

Prepare the FTP server or TFTP server program yourself for the PC. The switch series does not come with these software programs.

FTP download from a server

You can use the switch as an FTP client to download files from an FTP server.

To download a file from an FTP server, for example, the server at 10.10.110.1:

1.       Run an FTP server program on the server, configure an FTP username and password, specify the working directory and copy the 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.

<Sysname> ftp 10.10.110.1

Trying 10.10.110.1...

Press CTRL+C to abort

Connected to 10.10.110.1(10.10.110.1).

220 FTP service ready.

User (10.10.110.1:(none)):username                      

331 Password required for username.

Password:                                                

230 User logged in.

3.       Enable the binary transfer mode.

ftp> binary

  200 Type set to I.

4.       Execute the get command in FTP client view to download the 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.

  32133120 bytes received in 35 seconds (896. 0 kbyte/s)

ftp> bye

221 Server closing.

FTP upload from a client

You can use the IRF fabric as an FTP server and upload files from a client to the IRF fabric.

To FTP upload a file from a client:

On the IRF fabric:

1.       Enable FTP server.

<Sysname> system-view

[Sysname] ftp server enable

2.       Configure a local FTP user account:

# Create the user account.

[Sysname] local-user abc

# Set its password and specify the FTP service.

[Sysname-luser-manage-abc] password simple pwd

[Sysname-luser-manage-abc] service-type ftp

# Assign the network-admin user role to the user account for uploading file to the working directory of the server.

[Sysname-luser-manage-abc] authorization-attribute user-role network-admin

[Sysname-luser-manage-abc] quit

[Sysname] quit

On the PC:

1.       Log in to the IRF fabric (the FTP server) in FTP mode.

c:\> ftp 1.1.1.1

Connected to 1.1.1.1.

220 FTP service ready.

User(1.1.1.1:(none)):abc                              

331 Password required for abc.

Password:                                             

230 User logged in.

2.       Enable the binary file transfer mode.

ftp> binary

200 TYPE is now 8-bit binary.

3.       Upload the file (for example, newest.ipe) to the root directory of the flash memory on the master switch.

ftp> put newest.ipe

200 PORT command successful

150 Connecting to port 10002

226 File successfully transferred

ftp: 32133120 bytes sent in 64.58 secs (497.60 Kbytes/sec).

TFTP download from a server

To download a file from a TFTP server, for example, the server at 10.10.110.1:

1.       Run a TFTP server program on the server, specify the working directory, and copy the file, for example, newest.ipe, to the directory.

2.       On the IRF fabric, execute the tftp command in user view to download the file to the root directory of the flash memory on the master switch.

<Sysname> tftp 10.10.110.1 get newest.ipe

Press CTRL+C to abort.

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current

                                 Dload  Upload   Total   Spent    Left  Speed

100 30.6M    0 30.6M    0     0   143k      0 --:--:--  0:03:38 --:--:--  142k

Upgrading the software images

To upgrade the software images:

1.       Specify the upgrade image file (newest.ipe in this example) used at the next startup for the master switch, and assign the M attribute to the boot and system images in the file.

<Sysname> boot-loader file flash:/newest.ipe slot 1 main

Verifying image file..........Done.                                            

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.                                                     

Decompressing file boot.bin to flash:/boot.bin....................Done.        

Decompressing file system.bin to flash:/system.bin................Done.        

The images that have passed all examinations will be used as the main startup so

ftware images at the next reboot on slot 1.

2.       Specify the upgrade image file as the main startup image file for each subordinate switch. This example uses IRF member 2. (The subordinate switches will automatically copy the file to the root directory of their flash memories.)

<Sysname> boot-loader file flash:/newest.ipe slot 2 main

Verifying image file..........Done.                                            

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.                                                     

Decompressing file boot.bin to flash:/boot.bin....................Done.         

Decompressing file system.bin to flash:/system.bin................Done.        

The images that have passed all examinations will be used as the main startup so

ftware images at the next reboot on slot 2.

3.       Enable the software auto-update function.

<Sysname> system-view

[Sysname] irf auto-update enable

[Sysname] quit

This function checks the software versions of member switches for inconsistency with the master switch. If a subordinate switch is using a different software version than the master, the function propagates the current software images of the master to the subordinate as main startup images. The function prevents software version inconsistency from causing the IRF setup failure.

4.       Save the current configuration in any view 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.       Execute the display version command in any view to verify that the current main software images have been updated (details not shown).

Upgrading from the Boot menu

In this approach, you must access the Boot menu of each member switch to upgrade their software one by one. If you are upgrading software images for an IRF fabric, using the CLI is a better choice.

Prerequisites

Make sure the prerequisites are met before you start upgrading software from the Boot menu.

Setting up the upgrade environment

1.       Use a console cable to connect the console terminal (for example, a PC) to the console port on the switch.

2.       Connect the Ethernet port on the switch to the file server.

3.       Run a terminal emulator program on the console terminal and set the following terminal settings:

¡  Bits per second—9,600

¡  Data bits—8

¡  Parity—None

¡  Stop bits—1

¡  Flow control—None

¡  Emulation—VT100

Preparing for the TFTP or FTP transfer

To use TFTP or FTP:

·            Run a TFTP or FTP server program on the file server or the console terminal.

·            Copy the upgrade file to the file server.

·            Correctly set the working directory on the TFTP or FTP server.

·            Make sure the file server and the switch can reach each other.

Verifying that sufficient storage space is available

When you upgrade software, make sure each member switch has sufficient free storage space for the upgrade file, as shown in Table 9.

Table 9 Minimum free storage space requirements

If no sufficient space is available, delete unused files as described in “Managing files from the Boot menu.”

Scheduling the upgrade time

During the upgrade, the switch cannot provide any services. You must make sure the upgrade has a minimal impact on the network services.

Accessing the Boot menu

Starting......

Press Ctrl+D to access BASIC BOOT MENU

Press Ctrl+T to start heavy memory test

Press Ctrl+E to start flash test

********************************************************************************

*                                                                              *

*                    H3C S6520X-30QC-HI Version 105                    *

*                                                                              *

********************************************************************************

Copyright (c) 2004-2016 New H3C Technologies Co., Ltd.

Creation Date       : Aug  9 2016, 11:29:29

CPU Clock Speed     : 800MHz

Memory Size         : 2048MB

Flash Size          : 512MB

CPLD Version        : 002

PCB Version         : Ver.B

Mac Address         : 703d155618b0

Press Ctrl+B to access EXTENDED BOOT MENU...1

Press one of the shortcut key combinations at prompt.

Table 10 Shortcut keys

Accessing the basic Boot menu

If the extended Boot ROM segment has corrupted, you can repair or upgrade it from the basic Boot menu.

Press Ctrl+D within 1 seconds after the "Press Ctrl+D to access BASIC BOOT MENU" prompt message appears. If you fail to do this within the time limit, the system starts to run the extended Boot ROM segment.

********************************************************************************

*                                                                              *

*                    H3C S6520X-30QC-HI BOOTROM, Version 105                    *

*                                                                              *

********************************************************************************

   BASIC BOOT MENU

1. Update full BootRom

2. Update extended BootRom

3. Update basic BootRom

4. Boot extended BootRom

0. Reboot

Ctrl+U: Access BASIC ASSISTANT MENU

Enter your choice(0-4):

Table 11 Basic Boot ROM menu options

Table 12 BASIC ASSISTANT menu options

Accessing the extended Boot menu

Press Ctrl+B within 1 second (in fast startup mode) or 5 seconds (in full startup mode) after the "Press Ctrl-B to enter Extended Boot menu..." prompt message appears. If you fail to do this, the system starts decompressing the system software.

Alternatively, you can enter 4 in the basic Boot menu to access the extended Boot menu.

The "Password recovery capability is enabled." or "Password recovery capability is disabled." message appears, followed by the extended Boot menu. Availability of some menu options depends on the state of password recovery capability (see Table 13). For more information about password recovery capability, see Fundamentals Configuration Guide in H3C S6520X-EI & S6520X-HI Switch Series Configuration Guides.

Password recovery capability is enabled.

   EXTENDED BOOT MENU

1. Download image to flash

2. Select image to boot

3. Display all files in flash

4. Delete file from flash

5. Restore to factory default configuration

6. Enter BootRom upgrade menu

7. Skip current system configuration

8. Set switch startup mode

0. Reboot

Ctrl+Z: Access EXTENDED ASSISTANT MENU

Ctrl+F: Format file system

Ctrl+P: Change authentication for console login

Ctrl+R: Download image to SDRAM and run

Enter your choice(0-8):

Table 13 Extended Boot ROM menu options

Table 14 EXTENDED ASSISTANT menu options

Upgrading Comware images from the Boot menu

You can use the following methods to upgrade Comware images:

·            Using TFTP to upgrade software images through the Ethernet port

·            Using FTP to upgrade software images through the Ethernet port

·            Using XMODEM to upgrade software through the console port

Using TFTP to upgrade software images through the Ethernet port

1.       Enter 1 in the Boot menu to access the file transfer protocol submenu.

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.       Enter 1 to set the TFTP parameters.

Load File Name      :update.ipe

Server IP Address   :192.168.0.3

Local IP Address    :192.168.0.2

Subnet Mask         :255.255.255.0

Gateway IP Address  :0.0.0.0

Table 15 TFTP parameter description

3.       Enter all required parameters, and enter Y to confirm the settings. The following prompt appears:

Are you sure to download file to flash? Yes or No (Y/N):Y

4.       Enter Y to start downloading the image file. To return to the Boot menu without downloading the upgrade file, enter N.

Loading.........................................................................

................................................................................

................................................................................

................................................................Done!

5.       Enter the M (main), B (backup), or N (none) attribute for the images. In this example, assign the main attribute to the images.

Please input the file attribute (Main/Backup/None) M

Image file boot.bin is self-decompressing...

Free space: 534980608 bytes

Writing flash...................................................................

................................................................................

...................................................................Done!

Image file system.bin is self-decompressing...

Free space: 525981696 bytes

Writing flash...................................................................

................................................................................

................................................................................

................................................................................

................................................................................

................................................................................

.......................................................................Done!

6.       Enter 0 in the Boot menu to reboot the switch with the new software images.

   EXTENDED BOOT MENU

1. Download image to flash

2. Select image to boot

3. Display all files in flash

4. Delete file from flash

5. Restore to factory default configuration

6. Enter BootRom upgrade menu

7. Skip current system configuration

8. Set switch startup mode

0. Reboot

Ctrl+Z: Access EXTENDED ASSISTANT MENU

Ctrl+F: Format file system

Ctrl+P: Change authentication for console login

Ctrl+R: Download image to SDRAM and run

Enter your choice(0-8): 0

Using FTP to upgrade software images through the Ethernet port

1.       Enter 1 in the Boot menu to access the file transfer protocol submenu.

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.       Enter 2 to set the FTP parameters.

Load File Name      :update.ipe

Server IP Address   :192.168.0.3

Local IP Address    :192.168.0.2

Subnet Mask         :255.255.255.0

Gateway IP Address  :0.0.0.0

FTP User Name       :switch

FTP User Password   :***

Table 16 FTP parameter description

3.       Enter all required parameters, and enter Y to confirm the settings. The following prompt appears:

Are you sure to download file to flash? Yes or No (Y/N):Y

4.       Enter Y to start downloading the image file. To return to the Boot menu without downloading the upgrade file, enter N.

Loading.........................................................................

................................................................................

................................................................................

................................................................Done!

5.       Enter the M (main), B (backup), or N (none) attribute for the images. In this example, assign the main attribute to the images.

Please input the file attribute (Main/Backup/None) M

Image file boot.bin is self-decompressing...

Free space: 534980608 bytes

Writing flash...................................................................

................................................................................

...................................................................Done!

Image file system.bin is self-decompressing...

Free space: 525981696 bytes

Writing flash...................................................................

................................................................................

................................................................................

................................................................................

................................................................................

................................................................................

.......................................................................Done!

   EXTENDED BOOT MENU

1. Download image to flash

2. Select image to boot

3. Display all files in flash

4. Delete file from flash

5. Restore to factory default configuration

6. Enter BootRom upgrade menu

7. Skip current system configuration

8. Set switch startup mode

0. Reboot

Ctrl+Z: Access EXTENDED ASSISTANT MENU

Ctrl+F: Format file system

Ctrl+P: Change authentication for console login

Ctrl+R: Download image to SDRAM and run

Enter your choice(0-8):0

6.       Enter 0 in the Boot menu to reboot the switch with the new software images.

Using XMODEM to upgrade software through the console port

XMODEM download through the console port is slower than TFTP or FTP download through the Ethernet port. To save time, use the Ethernet port as long as possible.

1.       Enter 1 in the Boot menu to access the file transfer protocol submenu.

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.       Enter 3 to set the XMODEM download baud rate.

Please select your download baudrate:

1.* 9600

2.  19200

3.  38400

4.  57600

5.  115200

0.  Return to boot menu

Enter your choice(0-5):5

3.       Select an appropriate download rate, for example, enter 5 to select 115200 bps.

Download baudrate is 115200 bps                              

Please change the terminal's baudrate to 115200 bps and select XMODEM protocol

Press enter key when ready

4.       Set the serial port on the terminal to use the same baud rate and protocol as the console port. If you select 9600 bps as the download rate for the console port, skip this task.

a.      Select Call > Disconnect in the HyperTerminal window to disconnect the terminal from the switch.

Figure 2 Disconnecting the terminal from the switch

b.      Select File > Properties, and in the Properties dialog box, click Configure.

Figure 3 Properties dialog box

c.      Select 115200 from the Bits per second list and click OK.

Figure 4 Modifying the baud rate

d.      Select Call > Call to reestablish the connection.

Figure 5 Reestablishing the connection

5.       Press Enter. The following prompt appears:

Are you sure to download file to flash? Yes or No (Y/N):Y

6.       Enter Y to start downloading the file. (To return to the Boot menu, enter N.)

Now please start transfer file with XMODEM protocol

If you want to exit, Press <Ctrl+X>

Loading ...CCCCCCCCCCCCCCCCCCCCCCCCC 

7.       Select Transfer > Send File in the HyperTerminal window.

Figure 6 Transfer menu

8.       In the dialog box that appears, click Browse to select the source file, and select Xmodem from the Protocol list.

Figure 7 File transmission dialog box

9.       Click Send. The following dialog box appears:

Figure 8 File transfer progress