H3C S3100V3_EI-CMW710-R6126P53 Release Notes

Contents

Version information· 1

Version number 1

Version history· 1

Hardware and software compatibility matrix· 2

Upgrading restrictions and guidelines· 3

Hardware feature updates· 3

S3100V3_EI-CMW710-R6126P53· 3

S3100V3_EI-CMW710-R6126P39· 3

S3100V3_EI-CMW710-R6126P38· 3

S3100V3_EI-CMW710-R6126P37· 3

S3100V3_EI-CMW710-R6126P30· 4

S3100V3_EI-CMW710-R6126P13· 4

S3100V3_EI-CMW710-R6126P08· 4

S3100V3_EI-CMW710-R6115P06· 4

S3100V3_EI-CMW710-R6113· 4

S3100V3_EI-CMW710-R6111P05· 4

Software feature and command updates· 4

MIB Updates· 4

Operation Changes· 5

Operation changes in R6126P53· 5

Operation changes in R6126P39· 5

Operation changes in R6126P38· 6

Operation changes in R6126P37· 6

Operation changes in R6126P30· 6

Operation changes in R6126P13· 6

Operation changes in R6126P08· 6

Operation changes in R6115P06· 6

Operation changes in R6113· 6

Operation changes in R6111P05· 6

Restrictions and cautions· 6

Open problems and workarounds· 7

List of resolved problems· 7

Resolved problems in R6126P53· 7

Resolved problems in R6126P39· 8

Resolved problems in R6126P38· 9

Resolved problems in R6126P37· 9

Resolved problems in R6126P30· 14

Resolved problems in R6126P13· 14

Resolved problems in R6126P08· 16

Resolved problems in R6115P06· 17

Resolved problems in R6113· 20

Resolved problems in R6111P05· 21

Related documentation· 21

Documentation set 21

Obtaining Documentation· 21

Technical support 21

Appendix A Feature list 22

Hardware features· 22

Software features· 24

Appendix B Upgrading software· 28

System software file types· 28

System startup process· 28

Upgrade methods· 29

Upgrading from the CLI 30

Preparing for the upgrade· 30

Downloading software images to the master switch· 31

Upgrading the software images· 34

Upgrading from the Boot menu· 35

Prerequisites· 35

Accessing the Boot menu· 36

Accessing the extended Boot menu· 37

Upgrading Comware images from the Boot menu· 39

Upgrading Boot ROM from the Boot menu· 48

Managing files from the Boot menu· 55

Handling software upgrade failures· 58

List of Tables

Table 1 Version history. 1

Table 2 Hardware and software compatibility matrix. 2

Table 3 MIB updates. 4

Table 4 Technical specifications for non-PoE switch models. 22

Table 5 Technical specifications for PoE switch models. 23

Table 6 T Software features of the S3100V3-EI series. 24

Table 7 Minimum free storage space requirements. 36

Table 8 Shortcut keys. 37

Table 9 Extended Boot ROM menu options. 38

Table 10 EXTENDED ASSISTANT menu options. 39

This document describes the features, restrictions and guidelines, open problems, and workarounds for version S3100V3_EI-CMW710-R6126P53. 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 documents listed in "Related documentation."

Version information

Version number

H3C Comware Software, Version 7.1.070, Release 6126P53

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

Version history

Table 1 Version history

Hardware and software compatibility matrix

Table 2 Hardware and software compatibility matrix

Display the system software and Boot ROM versions of S3100V3-EI:

<H3C>dis version                                                           

H3C Comware Software, Version 7.1.070, Release 6126P53          ---------   注①

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

H3C S3100V3-52TP-EI uptime is 0 weeks, 0 days, 0 hours, 1 minute            

Last reboot reason : Kernel abnormality reboot                                 

Boot image: flash:/s3100v3_ei-cmw710-boot-r6126p53.bin                          

Boot image version: 7.1.070, Release 6126P53                                      

  Compiled Feb 10 2017 16:00:00                                                

System image: flash:/s3100v3_ei-cmw710-system-r6126p53.bin                      

System image version: 7.1.070, Release 6126P53                                   

  Compiled Feb 10 2017 16:00:00                                                                                            

Feature image(s) list:                                                         

  flash:/s3100v3_ei-cmw710-freeradius-r6126p53.bin, version: 7.1.070             

  Compiled Apr 13 2017 16:00:00                                                                                                                                                                                  

Slot 1:                                                                        

Uptime is 0 weeks,0 days,0 hours,7 minutes                                      

S3100V3-52TP-EI with 2 Processors                                           

BOARD TYPE:         S3100V3-52TP-EI                                          

DRAM:               512M bytes                                                  

FLASH:              256M bytes                                                 

PCB 1 Version:      VER.A                                                      

Bootrom Version:    126                                             ------  注②

CPLD 1 Version:     001                                                         

Release Version:    H3C S3100V3-52TP-EI-6126P53                             

Patch Version  :    None                                                       

Reboot Cause  :     KernelAbnormalReboot                                       

[SubSlot 0] 32FE+16GE+4SFP     

Upgrading restrictions and guidelines

None.

Hardware feature updates

S3100V3_EI-CMW710-R6126P53

None.

S3100V3_EI-CMW710-R6126P39

BIDI 40KM and 80KM Gigabit transceiver modules are supported.

S3100V3_EI-CMW710-R6126P38

None.

S3100V3_EI-CMW710-R6126P37

None.

S3100V3_EI-CMW710-R6126P30

None.

S3100V3_EI-CMW710-R6126P13

None.

S3100V3_EI-CMW710-R6126P08

None.

S3100V3_EI-CMW710-R6115P06

None.

S3100V3_EI-CMW710-R6113

None.

S3100V3_EI-CMW710-R6111P05

First release.

Software feature and command updates

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

MIB Updates

Table 3 MIB updates

Operation Changes

Operation changes in R6126P53

None.

Operation changes in R6126P39

None.

Operation changes in R6126P38

None.

Operation changes in R6126P37

The priority order of referencing ACLs is modified for MQC, packet filter, and portal.

Before modification: Portal > packet filter > MQC

After modification: Packet filter > MQC > portal

Operation changes in R6126P30

None.

Operation changes in R6126P13

None.

Operation changes in R6126P08

None.

Operation changes in R6115P06

None.

Operation changes in R6113

None.

Operation changes in R6111P05

First release.

Restrictions and cautions

Release R6126P53 must use BootROM 126 or a later version.

Before upgrading the software, you must fully understand the software feature changes between different software versions in H3C S3100V3_EI-CMW710-R6126P53 Release Notes (Software Feature Changes) and evaluate the impacts of the software upgrade on the live network. At the same time, for more information, you can refer to the related documentation sets.

When two devices are connected through non-combo SFP ports (except SFP ports of an S5130S-52F-EI switch) and SFP+ ports that use GE transceiver modules with a transmission distance of 40 km or more, the ports at both ends of a link must be configured with the speed 1000 and duplex full commands.

Open problems and workarounds

1.       201609030105

·            Symptom: Traffic cannot be forwarded between switches.

·            Condition: This symptom occurs if the switches receive packets whose source MAC addresses or destination MAC addresses are different from those already learned on the switches.

·            Workaround: Delete MAC address entries or broadcast packets to update MAC address entries.

List of resolved problems

Resolved problems in R6126P53

1.       201902020022

·            Symptom: When the voice VLAN security mode is enabled and LLDP is enabled for automatic IP phone discovery, the switch drops the LLDPDUs that have voice VLAN tags, and automatic IP phone discovery does not take effect.

·            Condition: This symptom might occur if the voice VLAN security mode is enabled and LLDP is enabled for automatic IP phone discovery.

2.       201903020106

·            Symptom: The switch does not issue an ACL to increase the priority of voice packets when receiving them.

·            Condition: This symptom occurs if the voice VLAN and LLDP for automatic IP phone discovery are both configured.

3.       201903180826

·            Symptom: The system prompts that the IPv6 ACL referenced by a PBR policy does not exist.

·            Condition: This symptom occurs if the IPv6 ACL is created by specifying a name and is referenced by using the name.

4.       201902140378

·            Symptom: The switch series cannot properly communicate with a device using the BCM chip through an established tunnel.

·            Condition: This symptom occurs if a tunnel is established between the switch series and a device using the BCM chip.

5.       201902260316

·            Symptom: When the PoE power change triggers a threshold alarm, the On and Off information is displayed incorrectly in the PoE threshold alarm information.

·            Condition: This symptom occurs if the PoE threshold alarm function is configured and SNMP notification for PoE threshold alarms is enabled.

Resolved problems in R6126P39

1.       201901250098

·            Symptom: On an IRF fabric, execution of the voice-vlan enable command fails for lack of resources.

·            Condition: This symptom might occur if the value obtained by subtracting the number of OUI addresses from the product of the number of voice VLAN-enabled interfaces and the number of IRF member devices is larger than 56.

2.       201901250420

·            Symptom: A PBR policy does not take effect on an interface if link status change occurs on another interface which is the next hop of a large number of routes.

·            Condition: This symptom might occur if link status change occurs on an interface which is the next hop of a large number of routes.

3.       201901250337

·            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-slot traffic exists.

4.       201809110615

·            Symptom: An interface leaves its voice VLAN and cannot join the voice VLAN again.

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

a.    On an IRF fabric, LLDP is enabled and voice VLAN is configured on an interface of a subordinate member device, and the interface is connected to a voice device supporting LLDP and CDP.

b.   Establish or disconnect the LLDP neighbor relationship on the subordinate IRF member device.

Resolved problems in R6126P38

1.       201806150108

·            Symptom: The rate information of a 100-Mbps port is displayed as 1000 Mbps.

·            Condition: This symptom occurs if you execute the link-delay command on the port and set the rate of the peer port to 1000 Mbps.

2.       201812200151

·            Symptom: After a PoE device is powered off and then restarted, the PoE device cannot supply power properly.

·            Condition: This symptom occurs if the PoE device is installed with the PSE module LSPPSE24A, LSPPSE48A, LSPPSE16A, or LSPPSE8A.

3.       201811080865

·            Symptom: The switch acting as a DHCP client cannot obtain IP addresses from an H3C DHCP server.

·            Condition: This symptom occurs if the DHCP-OFFER message sent by the DHCP server uses a unicast MAC address as the destination MAC address.

4.       201811260764

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

Resolved problems in R6126P37

1.       201810120764

·            Symptom: After a two-chassis IRF fabric reboots, MAC authentication users fail authentication on a port of the subordinate member.

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

a.    The IRF member devices each have a port that is working in the userlogin-secure-or-mac port security mode.

b.   The running configuration is saved and the .mdb configuration file is deleted before the IRF fabric is rebooted.

c.    MAC authentication users perform authentication on the port in userlogin-secure-or-mac mode of the subordinate member after the IRF fabric reboots.

2.       201810120762

·            Symptom: After the switch upgrades to the current software version and loads a text configuration file, command output shows that port security configuration becomes incorrect.

·            Condition: This symptom might occur if the running configuration is saved after port security is configured and then the switch upgrades to the current software version.

3.       201809190880

·            Symptom: An IP phone attached to the switch cannot communicate with the gateway.

·            Condition: This symptom might occur if the port which the IP phone is attached to is shut down and then brought up after the IP phone joins a voice VLAN.

4.       201809180169

·            Symptom: The following symptoms exist after the switch is rebooted:

¡  PoE-capable ports cannot supply power.

¡  In the output from the display environment command, the temperature of the last sensor is higher than the shutdown temperature threshold or displayed as --.

¡  The switch outputs the over temperature alarm.

¡  The SYS LED is red.

·            Condition: This symptom might occur if the power supply priority of multiple ports is set to critical and the switch is powered off before rebooted.

5.       201809150233

·            Symptom: The following symptoms exist after the switch is rebooted or has been running for a period of time:

¡  PoE-capable ports cannot supply power.

¡  In the output from the display environment command, the temperature of the last sensor is higher than the shutdown temperature threshold or displayed as --.

¡  The switch outputs the over temperature alarm.

¡  The SYS LED is red.

·            Condition: This symptom might occur if the switch is powered off before rebooted or has been running for a period of time.

6.       201809140213

·            Symptom: After the switch starts up, PoE-capable ports cannot supply power, and the SYS LED becomes red.

·            Condition: This symptom might occur if the switch starts up correctly.

7.       201808310515

·            Symptom: When the switch has multiple ECMP routes to a destination, the MAC address entries for the next hops are incorrect.

·            Condition: This symptom might occur if the switch has multiple ECMP routes to a destination.

8.       201810290223

·            Symptom: Telnet login fails when the CPU is attacked by packets.

·            Condition: This symptom might occur if the CPU is attacked by packets.

9.       201810220044

·            Symptom: The memory is exhausted when Ethernet interfaces are repeatedly shut down and brought up.

·            Condition: This symptom might occur if Ethernet interfaces are repeatedly shut down and brought up.

10.     201809210670

·            Symptom: The port security process does not respond.

·            Condition: This symptom might occur if LLDP requests user information from the port security module when the disableport-temporarily intrusion protection action is triggered on a port configured with port security.

11.     201804040436

·            Symptom: After an IRF fabric starts up with empty configuration, ARP packets that should be forwarded are sent to the CPU.

·            Condition: This symptom might occur if an IRF fabric starts up with empty configuration.

·            Workaround: None.

12.     201810120112

·            Symptom: When the switch is frequently accessed through SNMP, resources of the switch are exhausted and SNMP access fails.

·            Condition: This symptom might occur if the switch is frequently accessed through SNMP.

13.     201810130049

·            Symptom: The DHCP server stores DHCP client startup files, and the switch acts as a DHCP client. When the switch starts up with empty configuration and then connects to the DHCP server, an error message is output.

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

¡  The DHCP server stores DHCP client startup files.

¡  The switch acts as a DHCP client, and it starts up with empty configuration.

14.     201808230761

·            Symptom: In the display environment command output, the temperature information for the last sensor is incorrect.

·            Condition: This symptom occurs if the display environment command is used to display information about all temperature sensors on the device.

15.     201807310196

·            Symptom: The device reboots unexpectedly.

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

¡  The VLAN interface for the super VLAN is bound to a VPN instance.

¡  The super VLAN is deleted after a new sub VLAN is associated with the super VLAN.

16.     201807310180

·            Symptom: Port isolation does not take effect.

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

¡  Two interfaces in the same VLAN are assigned to the same port isolation group.

¡  One of the two interface receives MLD packets.

¡  MLD snooping is enabled for another VLAN.

17.     201807310170

·            Symptom: If you configure the speed auto or undo speed command on a 10-GE fiber port configured with the speed 1000 command, the system prompts that the operation failed.

·            Condition: This symptom occurs if you configure the speed auto or undo speed command on a 10-GE fiber port configured with the speed 1000 command.

18.     201807310159

·            Symptom: In a Device 1-Gateway-Device 2 network, when multicast NA packets arrive at Device 2, Device 2 forwards the packets back to the gateway. As a result, the ND entries on the gateway move, and Device 1 cannot ping the gateway intermittently.

·            Condition: This symptom occurs if Device 1 sends multicast NA packets in a Device 1-Gateway-Device 2 network.

19.     201807190265

·            Symptom: After the device runs for a period of time, outgoing traffic of an interface on the device cannot be forwarded.

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

¡  A GE interface on the device is configured to autonegotiate the speed and duplex mode.

¡  A peer interface is manually configured with the speed of 100 Mbps and the full duplex mode.

¡  The two interfaces are directly connected.

20.     201808010060

·            Symptom: PBR configured on a VLAN interface does not take effect on Layer 3 traffic with the destination MAC address as the virtual MAC address of a VRRP group's virtual IP address, and cannot forward such traffic according to the specified next hop.

·            Condition: This symptom occurs if PBR is configured on a VLAN interface configured with a VRRP group.

21.     201808010055

·            Symptom: After a PBR policy is configured on a Layer 3 interface, the interface cannot ping the gateway.

·            Condition: This symptom occurs if the Layer 3 interface is configured with an IP address that matches a criterion with an empty forwarding action in the PBR policy.

22.     201807310211

·            Symptom: On the DHCP-enabled switch, MAC authentication is enabled on a port. When a user that has already obtained an IP address passes MAC authentication, the switch assigns the user an authorization VLAN but does not assign the user a new IP address.

·            Condition: This symptom occurs if a user that has already obtained an IP address passes MAC authentication.

23.     201807310199

·            Symptom: Some portal-free endpoints cannot ping the external network.

·            Condition: This symptom occurs if the portal free-rule command is used to configure an IP-based portal-free rule that specifies IP addresses with non-all-Fs masks as portal-free.

24.     201807110366

·            Symptom: The CLI is stuck when commands are executed.

·            Condition: This symptom occurs when a DHCP snooping trusted port receives DHCP BOOTP attack packets on an IRF fabric.

25.     201806050721

·            Symptom: An endpoint cannot ping the gateway.

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

¡  The endpoint is connected to the gateway through the device.

¡  The interface connecting the device to the endpoint has the ARP gateway protection feature enabled, but the corresponding VLAN interface is not configured.

26.     201805310529

·            Symptom: When the device acts as a DHCP server and has the EAD assistant feature enabled, PCs attached to the device cannot obtain IP addresses that the DHCP server allocates.

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

a.    Configure 802.1X on the device, and execute the dot1x ead-assistant enable command in system view to enable the EAD assistant feature.

b.   Configure DHCP Server on the device.

27.     201805290123

·            Symptom: Failed to obtain the value of the dot1qTpFdbPort node for VLAN 0.

·            Condition: This symptom occurs when you walk on nodes.

28.     201806130403/201805170528

·            Symptom: The interface does not learn MAC address entries , and the up/down events of interfaces are not reported.

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

¡  The MAC address learning limit is configured on the downlink physical interface.

¡  MAC addresses frequently move between the uplink aggregate interface and the downlink physical interface.

¡  The aggregate interface is repeatedly shut down and brought up.

29.     201806130246

·            Symptom: The device drops Layer 2 multicast data packets with TTL as 1.

·            Condition: This symptom occurs if the igmp-snooping drop-unknown command is configured for a VLAN.

Resolved problems in R6126P30

None.

Resolved problems in R6126P13

1.       201705060208

·            Symptom: A 100-Mbps interface is missing.

·            Condition: This symptom occurs if a 100-Mbps interface is configured as the reflector port of a mirroring group.

2.       201804270329

·            Symptom: After you use the undo mac-vlan all command to delete all MAC-to-VLAN entries, some MAC-to-VLAN entries remain. The system prompts an operation failure if you execute the undo mac-vlan command to delete the specified MAC-to-VLAN entry.

·            Condition: This symptom occurs if MAC-based VLAN is configured on a 52-port device that is not configured with IRF.

3.       201805020063

·            Symptom: Packets cannot be forwarded through an aggregation group. A downlink device cannot ping an uplink device.

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

¡  The downlink link is an aggregate link.

¡  Port isolation is configured on the corresponding aggregate interface.

4.       201708010087

·            Symptom: An MLD report received on an aggregate interface is sent out the aggregate interface by software forwarding.

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

¡  The device receives an MLD report on an aggregate interface..

¡  MLD snooping is not enabled for the VLAN of the report.

¡  MLD snooping is enabled for the other VLANs.

5.       201801160564

·            Symptom: An MLD report received on a downlink aggregate interface is sent out of the aggregate interface rather than forwarded to the uplink device.

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

¡  The device has two chips.

¡  The device receives an MLD report on an aggregate interface with member ports on chip 1.

¡  MLD snooping is not enabled for the VLAN of the report.

¡  MLD snooping is enabled for the other VLANs.

6.       201712210145

·            Symptom: When a large number of IPv6 data packets are sent to the CPU, NS multicast packets cannot be properly sent to the CPU.

·            Condition: This symptom occurs if a large number of IPv6 packets destined for the IP address of the local device are received.

7.       201712090381

·            Symptom: After an aggregate interface of the device receives an IGMP report from a downlink device, the report is forwarded to a downlink Layer 2 device through the aggregate interface. As a result, the Layer 2 device adds the uplink interface to the outgoing interface list of the multicast forwarding table.

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

¡  The device receives an IGMP report on an aggregate interface.

¡  IGMP snooping is not enabled for the VLAN of the report.

¡  IGMP snooping is enabled for the other VLANs.

8.       201803010122

·            Symptom: The following problems occur:

a.    When an interface receives a packet matching a MAC-to-VLAN entry, the interface does not learn the MAC address of the packet, and drops the packet.

b.   The dynamic MAC-based VLAN assignment feature does not take effect. An interface cannot automatically join the corresponding VLAN.

·            Condition: This symptom occurs if manual voice VLAN assignment mode and dynamic MAC-based VLAN assignment are enabled.

9.       201803080385

·            Symptom: After SSH/Telnet packets are forwarded at Layer 3 by the device, SSH/Telnet operates improperly. 

·            Condition: This symptom occurs if SSH/Telnet is enabled on the device and the device forwards the SSH/Telnet packets at Layer 3.

10.     201801230564

·            Symptom: Video conferences freeze because traffic bursts exhaust shared buffer resources and cause traffic loss.

·            Condition: This symptom might occur if traffic bursts exhaust shared buffer resources and cause traffic loss.

11.     201712050364

·            Symptom: The OSPF neighbor state repeatedly flaps and passing OSPF packets cannot be transparently transmitted.

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

¡  When a large number of data packets need to be sent to the CPU, these packets are assigned to the same queue as OSPF unicast protocol packets with the TTL being not 1.

¡  The device receives passing OSPF packets.

Resolved problems in R6126P08

1.       201802080372

·            Symptom: The device reboots unexpectedly.

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

¡  The device has learned a large number of MAC address entries.

¡  An interface is added to an aggregation group. The member ports of the aggregation group are repeatedly shut down and brought up.

2.       201802080165

·            Symptom: A maximum of 32 sub-VLANs can be associated with a super VLAN.

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

a.    Create a VLAN interface for a VLAN, and configure an IP address for the VLAN interface.

b.   Configure the VLAN as a super VLAN.

c.    Use the subvlan command to associate sub-VLANs with the super VLAN.

3.       201802100195

·            Symptom: QinQ-related configurations on a port are lost.

·            Condition: This symptom occurs if master/subordinate switchover occurs to an IRF fabric.

4.       201801081024

·            Symptom: The switch cannot ping the destinations in two static routes.

·            Condition: This symptom might occur if the outgoing interface to the next hop in each static route is shut down and then brought up.

5.       201801270451

·            Symptom: The following problems occur:

¡  Interfaces on the device cannot come up properly after cables are inserted.

¡  The CLI is stuck when commands are executed.

¡  The MAC address entry information cannot be obtained in any method.

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

a.    In an STP network, the device has learned a large number of MAC address entries.

b.   The device frequently receives TC-BPDUs, and synchronously updates the MAC address entries.

c.    The display mac-address command is executed to display the MAC address entries of the specified VLAN.

6.       201707220206

·            Symptom: The local device cannot be pinged.

·            Condition: This symptom occurs if a large number of IPV6_ND_PASS packets are sent to the CPU.

7.       201712200919

·            Symptom: In the following cases, the MAC addresses corresponding to ARP entries are inconsistent.

¡  Execute the display mac-address and display arp commands in any view to view the MAC addresses corresponding to ARP entries.

¡  Execute the debug ipv4-drv show arp and debug ipv4-drv show arp commands in probe view to view the MAC addresses corresponding to static ARP entries issued by the device.

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

¡  A static route exists. The link directly connected to a valid next hop of the static route flaps.

¡  The device configured with static routes is rebooted.

8.       201712090114

·            Symptom: If you first configure the IPv6 default route and then configure the ipv6 unreachables enable command, the default route is modified. As a result, the Layer 3 packets with the destination addresses unreachable are sent to the CPU for processing rather than forwarded according to the default route.

·            Condition: This symptom occurs if you configure IPv6 static routes first and then configure the ipv6 unreachables enable command.

Resolved problems in R6115P06

1.       201711220080

·            Symptom: Flow mirroring does not take effect.

·            Condition: This symptom occurs if flow mirroring is configured through a QoS policy and voice VLAN is enabled on the interface where the QoS policy takes effect.

2.       201711210817

·            Symptom: The device cannot learn some MAC addresses.

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

¡  An interface is enabled with voice VLAN and configured with the MAC learning limit.

¡  The interface goes down and then comes up.

3.       201711130845

·            Symptom: When an interface restores to the up state, intrusion protection is triggered exceptionally.

·            Condition: This symptom occurs if the following events occur:

a.    An interface with port security enabled goes down, and the secure MAC address entry ages out.

b.   The interface restores to the up state.

4.       201711020708

·            Symptom: The mac-vlan mac-address command fails to configure a MAC-VLAN entry.

·            Condition: This symptom occurs if the mac-vlan mac-address command is executed on a device with the specific configurations.

5.       201709220167

·            Symptom: The MAC address table information is incorrectly displayed, and the CPU usage reaches 100%.

·            Condition: This symptom occurs if a large number of MAC address entries are added or deleted. 

6.       201709210407

·            Symptom: The HWTACACS server configuration is not deleted as expected, and processes that use the server configuration get abnormal when the switch rolls back configuration.

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

a.    Multiple authentication servers, authorization servers, or accounting servers are configured in an HWTACACS scheme.

b.   The servers of the same type have the same VPN instance and IP address settings but different port number settings.

7.       201709050143

·            Symptom: The secure MAC address bound to port 1 does not age out according to the secure MAC aging timer after the user moves from port 1 to port 2.

·            Condition: This symptom occurs if you enable port security on both ports and set the secure MAC aging timer.

8.       201708140180

·            Symptom: The switch reboots when memory resources are insufficient.

·            Condition: This symptom might occur if memory resources are insufficient.

9.       201709050334

·            Symptom: In the Appendix E environment outlined in RFC 2328, OSPF performs incorrect route calculation.

·            Condition: This symptom occurs if OSPF redistributes multiple routes with the same IP address but different masks or OSPF removes such redistributed routes.

10.     201709040837

·            Symptom: A user fails to log in through MAC authentication after the switch reboots.

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

a.    Enable port security and set the port security mode of the interface to one of the following options:

-       macAddressWithRadius.

-       macAddressOrUserLoginSecure.

-       macAddressElseUserLoginSecure.

-       macAddressOrUserLoginSecureExt.

-       macAddressElseUserLoginSecureExt.

b.   Save the configuration and delete the binary (.mdb) configuration file.

c.    Reboot the switch.

11.     201709040821

·            Symptom: An 802.1X user that passes authentication on an interface is assigned an IP address in the guest VLAN, Auth-Fail VLAN, or critical VLAN instead of an IP address in the authorization VLAN.

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

¡  Both 802.1X and DHCP are enabled.

¡  An 802.1X guest VLAN, Auth-Fail VLAN, or critical VLAN is configured on the interface.

¡  The server successfully assigns an authorization VLAN.

12.     201709040809

·            Symptom: 802.1X authentication fails on an interface.

·            Condition: This symptom might occur if the following operations are performed:

¡  Enable 802.1X and specify the port-based access control method on an interface.

¡  Set the username request timeout timer by using the dot1x timer tx-period tx-period-value command.

13.     201709040788

·            Symptom: The CLI does not respond in a console port session for a long time.

·            Condition: This symptom occurs if the following sequence of events occurs:

a.    Enable scheme authentication and command accounting for the console port.

b.   Enable STP in interface range view.

14.     201709040766

·            Symptom: A user fails both 802.1X authentication and MAC authentication on an interface.

·            Condition: This symptom occurs if the following sequence of events occurs:

a.    Port security is enabled and the port security mode is set to userlogin-secure-or-mac-ext on an interface.

b.   The user passes MAC authentication after failing 802.1X authentication.

c.    Execute the shutdown and undo shutdown commands on the interface.

d.   The user reinitiates authentication.

15.     201706290743

·            Symptom: A fiber port goes down, and it cannot come up or forward traffic.

·            Condition: This symptom occurs if 1000-Mbps transceiver modules with a transmission distance of 40 km or longer and an optical fiber are used to connect fiber ports without PHYs, and the optical fiber is unplugged and then plugged.

16.     201707040599

·            Symptom: A user might fail authentication on an interface after the interface is shut down and then brought up.

·            Condition: This symptom might occur if both MAC authentication and 802.1X authentication are configured on the interface and authorization ACLs and authorization user profiles are configured on the switch.

17.     201706090032

·            Symptom: A user in the 802.1X guest VLAN, critical VLAN, or Auth-Fail VLAN might fail to update its IP address after it passes 802.1X authentication and is assigned a VLAN.

·            Condition: This symptom might occur if the user in the 802.1X guest VLAN, critical VLAN, or Auth-Fail VLAN triggers 802.1X authentication and the user is assigned a VLAN after passing 802.1X authentication.

18.     201706090030

·            Symptom: A user might fail 802.1X authentication on an interface.

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

a.    An 802.1X guest VLAN, critical VLAN, or Auth-fail VLAN is configured on the interface.

b.   The username request timeout timer is set to a small value by using the dot1x timer tx-period command.

c.    The 802.1X client interacts with the authentication server for a long time to complete 802.1X authentication.

19.     201707040813

·            Symptom: An IRF physical interface cannot be bound to an IRF port in the Web interface.

·            Condition: This symptom might occur if IRF is configured in the Web interface.

Resolved problems in R6113

1.       201612200438

·            Symptom: When a certain USB-to-serial port adapter cable is used, the device continuously outputs garbled characters and reboots.

·            Condition: This symptom occurs if the device uses a certain USB-to-serial port adapter cable.

Resolved problems in R6111P05

First release.

Related documentation

Documentation set

·            H3C S3100V3-EI Switch Series Installation Quick Start

·            H3C S3100V3-EI Switch Series Installation Guide

·            H3C S5130S-HI[EI]&S5110V2&S3100V3-EI Switch Series Configuration Guides-R612x

·            H3C S5130S-HI[EI]&S5110V2&S3100V3-EI Switch Series Command References-R612x

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

[email protected]

http://www.h3c.com.hk

Appendix A Feature list

Hardware features

Table 4 Technical specifications for non-PoE switch models

Table 5 Technical specifications for PoE switch models

Software features

Table 6 T Software features of the S3100V3-EI series

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, S3100V3_EI-CMW710-BOOT-R6126P53.bin and S3100V3_EI-CMW710-SYSM-R6126P53.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 IRF configuration guide for the H3C S3100V3_EI 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 7.

Table 7 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

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

*                                                                              *

*              H3C S3100V3-28TP-EI BOOTROM, Version 126                        *

*                                                                              *

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

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

Creation Date       : Feb 7 2017, 15:11:36                                    

CPU Clock Speed     : 400MHz                                                  

Memory Size         : 512MB                                                    

Flash Size          : 256MB                                                    

CPLD Version        : 001                                                      

PCB Version         : Ver.A                                                    

Mac Address         : 000012346666

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

Press one of the shortcut key combinations at prompt.

Table 8 Shortcut keys

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 9). For more information about password recovery capability, see Fundamentals Configuration Guide in H3C S3100V3-EI 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

Ctrl+Y: Change Work Mode

Ctrl+C: Display Copyright

Enter your choice(0-8):

Table 9 Extended Boot ROM menu options

Table 10 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 11 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

Ctrl+Y: Change Work Mode

Ctrl+C: Display Copyright

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 12 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

Ctrl+Y: Change Work Mode

Ctrl+C: Display Copyright

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

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

The boot.bin image is self-decompressing...

# At the Load File name prompt, enter a name for the boot image to be saved to flash memory.

Load File name  : default_file boot-update.bin       (At the prompt,

Free space: 470519808 bytes

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

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

The system-update.bin image is self-decompressing...

# At the Load File name prompt, enter a name for the system image to be saved to flash memory.

Load File name  : default_file system-update.bin     

Free space: 461522944 bytes

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

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

Your baudrate should be set to 9600 bps again!

Press enter key when ready

11.    If the baud rate of the HyperTerminal is not 9600 bps, restore it to 9600 bps as described in step 5.a. If the baud rate is 9600 bps, skip this step.

   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

Ctrl+Y: Change Work Mode

Ctrl+C: Display Copyright

Enter your choice(0-8): 0

12.    Enter 0 in the Boot menu to reboot the system with the new software images.

Upgrading Boot ROM from the Boot menu

You can use the following methods to upgrade the Boot ROM image:

·            Using TFTP to upgrade Boot ROM through the Ethernet port

·            Using FTP to upgrade Boot ROM through the Ethernet port

·            Using XMODEM to upgrade Boot ROM through the console port

Using TFTP to upgrade Boot ROM through the Ethernet port

1.       Enter 6 in the Boot menu to access the Boot ROM update menu.

1. Update full BootRom

2. Update extended BootRom

3. Update basic BootRom

0. Return to boot menu

Enter your choice(0-3):

2.       Enter 1 in the Boot ROM update menu to upgrade the full Boot ROM.

The file transfer protocol submenu appears:

1. Set TFTP protocol parameters

2. Set FTP protocol parameters

3. Set XMODEM protocol parameters

0. Return to boot menu

Enter your choice(0-3):

3.       Enter 1 to set the TFTP parameters.

Load File Name      :update.btm

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 13 TFTP parameter description

4.       Enter all required parameters and press Enter to start downloading the file.

Loading.................................................Done! 

5.       Enter Y at the prompt to upgrade the basic Boot ROM section.

Will you Update Basic BootRom? (Y/N):Y

Updating Basic BootRom...........Done.

6.       Enter Y at the prompt to upgrade the extended Boot ROM section.

Updating extended BootRom? (Y/N):Y

Updating extended BootRom.........Done.

7.       Enter 0 in the Boot ROM update menu to return to the Boot menu.

1. Update full BootRom

2. Update extended BootRom

3. Update basic BootRom

0. Return to boot menu

Enter your choice(0-3):

8.       Enter 0 in the Boot menu to reboot the switch with the new Boot ROM image.

Using FTP to upgrade Boot ROM through the Ethernet port

1.       Enter 6 in the Boot menu to access the Boot ROM update menu.

1. Update full BootRom

2. Update extended BootRom

3. Update basic BootRom

0. Return to boot menu

Enter your choice(0-3):

2.       Enter 1 in the Boot ROM update menu to upgrade the full Boot ROM.

The file transfer protocol submenu appears:

1. Set TFTP protocol parameters

2. Set FTP protocol parameters

3. Set XMODEM protocol parameters

0. Return to boot menu

Enter your choice(0-3):

3.       Enter 2 to set the FTP parameters.

Load File Name     :update.btm

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  :123

Table 14 FTP parameter description

4.       Enter all required parameters and press Enter to start downloading the file.

Loading.................................................Done! 

5.       Enter Y at the prompt to upgrade the basic Boot ROM section.

Will you Update Basic BootRom? (Y/N):Y

Updating Basic BootRom...........Done.

6.       Enter Y at the prompt to upgrade the extended Boot ROM section.

Updating extended BootRom? (Y/N):Y

Updating extended BootRom.........Done.

7.       Enter 0 in the Boot ROM update menu to return to the Boot menu.

1. Update full BootRom

2. Update extended BootRom

3. Update basic BootRom

0. Return to boot menu

Enter your choice(0-3):

8.       Enter 0 in the Boot menu to reboot the switch with the new Boot ROM image.

Using XMODEM to upgrade Boot ROM 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 6 in the Boot menu to access the Boot ROM update menu.

1. Update full BootRom

2. Update extended BootRom

3. Update basic BootRom

0. Return to boot menu

Enter your choice(0-3):

2.       Enter 1 in the Boot ROM update menu to upgrade the full Boot ROM.

The file transfer protocol submenu appears:

1. Set TFTP protocol parameters

2. Set FTP protocol parameters

3. Set XMODEM protocol parameters

0. Return to boot menu

Enter your choice(0-3):

3.       Enter 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

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

5.       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 9 Disconnecting the terminal from the switch

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

Figure 10 Properties dialog box

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

Figure 11 Modifying the baud rate

d.   Select Call > Call to reestablish the connection.

Figure 12 Reestablishing the connection

6.       Press Enter to start downloading the file.

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 13 Transfer menu

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

Figure 14 File transmission dialog box

9.       Click Send. The following dialog box appears:

Figure 15 File transfer progress

10.    Enter Y at the prompt to upgrade the basic Boot ROM section.

Loading ...CCCCCCCCCCCCCC  ...Done! 

Will you Update Basic BootRom? (Y/N):Y

Updating Basic BootRom...........Done.

11.    Enter Y at the prompt to upgrade the extended Boot ROM section.

Updating extended BootRom? (Y/N):Y

Updating extended BootRom.........Done.

12.    If the baud rate of the HyperTerminal is not 9600 bps, restore it to 9600 bps at the prompt, as described in step 4.a. If the baud rate is 9600 bps, skip this step.

Please change the terminal's baudrate to 9600 bps, press ENTER when ready.

13.    Press Enter to access the Boot ROM update menu.

14.    Enter 0 in the Boot ROM update menu to return to the Boot menu.

1. Update full BootRom

2. Update extended BootRom

3. Update basic BootRom

0. Return to boot menu

Enter your choice(0-3):

15.    Enter 0 in the Boot menu to reboot the switch with the new Boot ROM image.

Managing files from the Boot menu

From the Boot menu, you can display files in flash memory to check for obsolete files, incorrect files, or space insufficiency, delete files to release storage space, or change the attributes of software images.

Displaying all files

Enter 3 in the Boot menu to display all files in flash memory and identify the free space size.

   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

Ctrl+Y: Change Work Mode

Ctrl+C: Display Copyright

Enter your choice(0-8): 3

The following is a sample output:

Display all file(s) in flash:

File Number    File Size(bytes)     File Name

================================================================================

1              8177                 flash:/testbackup.cfg

2(*)           53555200             flash:/system.bin

3(*)           9959424              flash:/boot.bin

4              3678                 flash:/startup.cfg_backup

5              30033                flash:/default.mdb

6              42424                flash:/startup.mdb

7              18                   flash:/.pathfile

8              232311               flash:/logfile/logfile.log

9              5981                 flash:/startup.cfg_back

10(*)          6098                 flash:/startup.cfg

11             20                   flash:/.snmpboots

Free space: 464298848 bytes

The current image is boot.bin

(*)-with main attribute

(b)-with backup attribute

(*b)-with both main and backup attribute

Deleting files

If storage space is insufficient, delete obsolete files to free up storage space.

To delete files:

1.       Enter 4 in the Boot menu:

Deleting the file in flash:

File Number    File Size(bytes)     File Name

================================================================================

1              8177                 flash:/testbackup.cfg

2(*)           53555200             flash:/system.bin

3(*)           9959424              flash:/boot.bin

4              3678                 flash:/startup.cfg_backup

5              30033                flash:/default.mdb

6              42424                flash:/startup.mdb

7              18                   flash:/.pathfile

8              232311               flash:/logfile/logfile.log

9              5981                 flash:/startup.cfg_back

10(*)          6098                 flash:/startup.cfg

11             20                   flash:/.snmpboots

Free space: 464298848 bytes

The current image is boot.bin

(*)-with main attribute

(b)-with backup attribute

(*b)-with both main and backup attribute

2.       Enter the number of the file to delete. For example, enter 1 to select the file testbackup.cfg.

Please input the file number to change: 1

3.       Enter Y at the confirmation prompt.

The file you selected is testbackup.cfg,Delete it? (Y/N):Y

Deleting....................................Done!

Changing the attribute of software images

Software image attributes include main (M), backup (B), and none (N). System software and boot software can each have multiple none-attribute images but only one main image and one backup image on the switch. You can assign both the M and B attributes to one image. If the M or B attribute you are assigning has been assigned to another image, the assignment removes the attribute from that image. If the removed attribute is the sole attribute of the image, its attribute changes to N.

For example, the system image system.bin has the M attribute and the system image system-update.bin has the B attribute. After you assign the M attribute to system-update.bin, the attribute of system-update.bin changes to M+B and the attribute of system.bin changes to N.

To change the attribute of a system or boot image:

1.       Enter 2 in the Boot menu.

   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

Ctrl+Y: Change Work Mode

Ctrl+C: Display Copyright

Enter your choice(0-8): 2

2.       1 or 2 at the prompt to set the attribute of a software image. (The following output is based on the option 2. To set the attribute of a configuration file, enter 3.)

1. Set image file

2. Set bin file

3. Set configuration file

0. Return to boot menu

Enter your choice(0-3): 2

File Number    File Size(bytes)     File Name

================================================================================

1(*)              53555200              flash:/system.bin

2(*)              9959424               flash:/boot.bin

3                 13105152              flash:/boot-update.bin

4                 91273216              flash:/system-update.bin

Free space: 417177920 bytes

(*)-with main attribute

(b)-with backup attribute

(*b)-with both main and backup attribute

Note:Select .bin files. One but only one boot image and system image must be included.

3.       Enter the number of the file you are working with. For example, enter 3 to select the boot image boot-update.bin. and enter 4 to select the system image system-update.bin.

Enter file No.(Allows multiple selection):3

Enter another file No.(0-Finish choice):4

4.       Enter 0 to finish the selection.

Enter another file No.(0-Finish choice):0

You have selected:

flash:/boot-update.bin

flash:/system-update.bin

5.       Enter M or B to change its attribute to main or backup. If you change its attribute to M, the attribute of boot.bin changes to none.

Please input the file attribute (Main/Backup) M

This operation may take several minutes. Please wait....

Next time, boot-update.bin will become default boot file!

Next time, system-update.bin will become default boot file! 

Set the file attribute success!

Handling software upgrade failures

If a software upgrade fails, the system runs the old software version.

To handle a software upgrade failure:

1.       Verify that the software release is compatible with the switch model and the correct file is used.

2.       Verify that the software release and the Boot ROM release are compatible. For software and Boot ROM compatibility, see the hardware and software compatibility matrix in the correct release notes.

3.       Check the physical ports for a loose or incorrect connection.

4.       If you are using the console port for file transfer, check the HyperTerminal settings (including the baud rate and data bits) for any wrong setting.

5.       Check the file transfer settings:

¡  If XMODEM is used, you must set the same baud rate for the terminal as for the console port.

¡  If TFTP is used, you must enter the same server IP addresses, file name, and working directory as set on the TFTP server.

¡  If FTP is used, you must enter the same FTP server IP address, source file name, working directory, and FTP username and password as set on the FTP server.

6.       Check the FTP or TFTP server for any incorrect setting.

7.       Check that the storage device has sufficient space for the upgrade file.