Title | Size | Downloads |
---|---|---|
S5136S_EI-CMW710-R6817P02.zip ![]() |
71.89 MB | |
MD5-S5136S_EI-CMW710-R6817P02.rar ![]() |
0.16 KB | |
H3C S5136S_EI-CMW710-R6817P02 Release Notes.pdf | 1.06 MB |
|
H3C S5136S_EI-CMW710-R6817P02 Release Notes |
|
|
Copyright © 2025 New H3C Technologies Co., Ltd. All rights reserved. No part of this manual may be reproduced or transmitted in any form or by any means without prior written consent of New H3C Technologies Co., Ltd. The information in this document is subject to change without notice. |
Contents
Hardware and software compatibility matrix· 1
Upgrade restrictions and guidelines· 3
Software feature and command updates· 3
Operation changes in R6817P02· 4
Open problems and workarounds· 4
Resolved problems in R6817P02· 5
Fixed security vulnerabilities· 11
System software file types· 12
Setting up the upgrade environment 14
Downloading software images to the master switch· 16
Upgrading from the Boot menu· 19
Accessing the extended Boot menu· 21
Remote Upgrading through CLI 23
Accessing the extended Boot menu· 25
Software Upgrading via Console Port (Xmodem Protocol) 27
Software Upgrading via Ethernet Interface (FTP/TFTP) 29
List of tables
Table 1 Hardware and software compatibility matrix· 1
Table 3 Software features of the S5136S_EI series· 7
Table 4 Minimum free storage space requirements· 20
Table 6 Extended Boot ROM menu options· 22
Table 7 EXTEND-ASSISTANT menu options· 23
Table 9 Extended Boot ROM menu options· 26
Table 10 EXTEND-ASSISTANT menu options· 27
Introduction
This document describes the features, restrictions and guidelines, open problems, and workarounds for version S5136S_EI-CMW710-R6817P02. 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 the documents listed in "Related documentation."
Version information
Version number
H3C Comware Software, Version 7.1.070, Release 6817P02
Note: You can see the version number with the command display version in any view. Please see Note①.
Version history
IMPORTANT: The software feature changes listed in the version history table for each version are not complete. To obtain complete information about all software feature changes in each version, see the Software Feature Changes document for this release notes. |
Version number | Last version | Branch version | Release date | Release type | Remarks |
S5136S_EI-CMW710-R6817P02 | S5136S_EI-CMW710-R6817 | B70D064SP345702 | 2025-05-10 | Release version | Fixed bugs |
S5136S_EI-CMW710-R6817 | First release | B70D064SP34XX_SWITCH | 2025-04-07 | Release version | First release |
Hardware and software compatibility matrix
CAUTION: To avoid an upgrade failure, use Table 1 to verify the hardware and software compatibility before performing an upgrade. |
Table 1 Hardware and software compatibility matrix
Item | Specifications |
Product family | S5136S_EI Series |
Hardware platform | S5136S-8T4XS-EI-Q S5136S-8FP4XS-EI-Q S5136S-48T4S-EI-Q S5136S-48T4X-EI-Q S5136S-48S2T4X-EI S5136S-48ST4X-EI S5136S-24S8T4X-EI S5136S-24T4X-EI-Q S5136S-16T4X-EI-Q S5136S-24T4S-EI-Q S5136S-48FP4X-EI S5136S-48P4X-EI S5136S-48P4S-EI S5136S-48FP4S-EI S5136S-24FP4S4X-EI S5136S-24FP4T4S-EI S5136S-16FP4X-EI S5136S-24P4X-EI S5136S-10FPT4X-EI-Q S5136S-10T4X-EI-Q |
Memory | 2048M |
Flash | 512M |
Boot ROM version | Version 102 or higher (Note: Use the display version command in any view to view the version information. Please see Note②) |
Software images and their MD5 checksums | S5136S_EI-CMW710-R6817P02.ipe(See the MD5 file) |
iMC version number | iMC ACLM 7.3 (E0705P12) iMC BIMS 7.3 (E0506H01) iMC DM 7.3 (E0705P12) iMC EAD 7.3 (E0611P10) iMC EIA (TAM) 7.3 (E0611P13) iMC EIA (UAM) 7.3 (E0611P13) iMC iCC 7.3 (E0705P12) iMC IPM 7.3(E0609) iMC NTA 7.3 (E0707L06) iMC PLAT 7.3 (E0705P12) iMC QoSM 7.3 (E0505P01) iMC SHM 7.3 (E0707L06) iMC UBA UCenter E0707L06 iMC VLAN 7.3 (E0705P12) |
iNode version number | iNode PC 7.3 (E0585) |
Remarks | N/A |
Display the system software and Boot ROM versions of S5136S_EI:
<H3C>dis version
H3C Comware Software, Version 7.1.070, Release 6817P02
Copyright (c) 2004-2025 New H3C Technologies Co., Ltd. All rights reserved.
H3C S5136S-10T2S2X-EI-Q uptime is 0 weeks, 1 day, 21 hours, 20 minutes
Last reboot reason : User reboot
Boot image: flash:/s5136s_ei-cmw710-boot-r6817p02.bin
Boot image version: 7.1.070, Release 6817P02
Compiled Apr 01 2025 16:00:00
System image: flash:/s5136s_ei-cmw710-system-r6817P02.bin
System image version: 7.1.070, Release 6817P02
Compiled Apr 01 2025 16:00:00
Slot 1:
Uptime is 0 weeks,1 day,21 hours,20 minutes
S5136S-10T2S2X-EI-Q 1 Processor with 2 cores
BOARD TYPE: S5136S-10T2S2X-EI-Q
DRAM: 2048M bytes
FLASH: 512M bytes
PCB 1 Version: VER.B
Bootrom Version: 102
CPLD 1 Version: 001
Release Version: H3C S5136S-10T2S2X-EI-Q-6817P02
Patch Version : None
Reboot Cause : UserReboot
[SubSlot 0] 10GE+2SFP Combo+2SFP Plus
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
S5136S_EI-CMW710-R6817P02
None.
S5136S_EI-CMW710-R6817
First release.
Software feature and command updates
MIB updates
Item | MIB file | Module | Description |
S5136S_EI-CMW710-R6817P02 | |||
New | None | None | None |
Modified | None | None | None |
S5136S_EI-CMW710-R6817 | |||
New | First release | First release | First release |
Modified | First release | First release | First release |
Operation changes
Operation changes in R6817P02
None
Operation changes in R6817
First release.
Restrictions and cautions
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.
When you use this version of software, make sure you fully understand the restrictions and cautions described in this section.
Restrictions
None.
Cautions
Open problems and workarounds
202503181154
· Symptom: Input pause frames are not counted in the display interface command output when flow control is enabled.
· Condition: This symptom occurs when flow control is enabled.
· Workaround: None.
202502261154
· Symptom: On an IRF fabric, the debug qacl show acl-resources command shows that ACL resources used by portal users were not released.
· Condition: This symptom occurs if the ACL resources on one member device is insufficient and portal users come online and go offline repeatedly.
· Workaround: Actual user scenarios have an extremely low probability of consuming only one ACL resource; additionally, the issue has not been reproduced in multiple tests.
List of resolved problems
Resolved problems in R6817P02
202504150535
· Symptom: After you configure multiple mirroring actions, the mirroring configuration is displayed correctly, but flow mirroring does not take effect.
· Condition: This symptom might occur after you configure MQC on an interface and configure multiple mirroring actions, making system resources insufficient.
202504251340
· Symptom: Failed to connect the switch to the Cloudnet platform by pressing the MODE button.
· Condition: This symptom might occur when you connect a switch to the Cloudnet platform by pressing the MODE button.
Resolved problems in R6817
First release.
Troubleshooting resources
To obtain troubleshooting resources for the product:
1. Access Technical Documents at http://www.h3c.com/en/Technical_Documents.
2. Select the device category and model.
3. Select the Maintain or Maintenance menu.
Related documentation
· H3C S5136S-EI Switch Series Installation Guide
· H3C S5136S-EI Switch Series Hardware Information and Specifications
· H3C S5136S-EI Switch Series Configuration Guides
· H3C S5136S-EI Switch Series Command References
Technical support
To obtain technical assistance, contact H3C by using one of the following methods:
· Email:
[email protected] (countries and regions except Hong Kong, China)
[email protected] (Hong Kong, China)
· Technical support hotline number. To obtain your local technical support hotline number, go to the H3C Service Hotlines website: https://www.h3c.com/en/Support/Online_Help/Service_Hotlines/
To access documentation, go to the H3C website at http://www.h3c.com/en/.
Please refer to H3C S5136S-EI Switch Series Installation Guide
Table 3 Software features of the S5136S_EI series
Feature | S5136S_EI series switch |
Full duplex Wire speed L2 switching capacity | S5136S-24T4S-EI-Q, S5136S-24FP4T4S-EI:56Gbps S5136S-8T4XS-EI-Q, S5136S-8FP4XS-EI-Q: 96Gbps S5136S-10T4X-EI-Q:100Gbps S5136S-48T4S-EI-Q, S5136S-48FP4S-EI:104 Gbps S5136S-48S2T4X-EI:108Gbps S5136S-16T4X-EI-Q:112Gbps S5136S-48T4X-EI-Q, S5136S-48FP4X-EI, S5136S-48P4X-EI, S5136S-48ST4X-EI: 176Gbps S5136S-24T4X-EI-Q, S5136S-24FP4S4X-EI, S5136S-24S8T4X-EI: 128Gpbs |
Whole system Wire speed L2 switching Packet forwarding rate | S5136S-24T4S-EI-Q, S5136S-24FP4T4S-EI:41.7Gbps S5136S-8T4XS-EI-Q, S5136S-8FP4XS-EI-Q: 71.43Gbps S5136S-10T4X-EI-Q:74.4Gbps S5136S-48T4S-EI-Q, S5136S-48FP4S-EI :77.4 Gbps S5136S-48S2T4X-EI:80.4Gbps S5136S-16T4X-EI-Q:83.3Gbps S5136S-48T4X-EI-Q, S5136S-48FP4X-EI, S5136S-48P4X-EI, S5136S-48ST4X-EI: 130.95Gbps S5136S-24T4X-EI-Q, S5136S-24FP4S4X-EI, S5136S-24S8T4X-EI:95.24Gpbs |
IRF | Ring topology Daisy chain topology LACP MAD ARP MAD |
Link aggregation | Aggregation of 1-GE ports Aggregation of 10-GE ports Static link aggregation Dynamic link aggregation Inter-device aggregation A maximum of 1 aggregation groups on a device A maximum of 124 inter-device aggregation groups A maximum of 8 ports for each aggregation group |
Flow control | IEEE 802.3x flow control |
Jumbo Frame | Supports maximum frame size of 10000 |
MAC address table | 16K MAC addresses 1K static MAC addresses Blackhole MAC addresses MAC address learning limit on a port |
VLAN | Port-based VLANs (4094 VLANs) QinQ VLAN mapping |
ARP | 2K entries 512 static entries Gratuitous ARP ARP black hole ARP detection (based on DHCP snooping entries/802.1X security entries/static IP-to-MAC bindings) ARP source suppression |
ND | Entries Static entries |
VLAN virtual interface | 32 |
DHCP | DHCP client DHCP snooping DHCP relay DHCP server DHCPv6 Server DHCPv6 relay DHCPv6 snooping |
UDP Helper | UDP Helper |
DNS | Static DNS Dynamic DNS IPv4 and IPv6 DNS |
unicast route | IPv4 and IPv6 static routes Routing policies Policy-based routing IPv6 policy-based routing |
Broadcast/multicast/unicast storm control | Storm control based on port rate percentage PPS-based storm control Bps-based storm control |
MSTP | STP/RSTP/MSTP protocol STP Root Guard BPDU Guard 128 PVST instances |
QoS/ACL | Remarking of 802.1p and DSCP priorities Packet filtering at L2 (Layer 2) through L4 (Layer 4) Eight output queues for each port SP/WRR/SP+WRR queue scheduling algorithms Port-based rate limiting Flow-based redirection Time range |
Mirroring | Stream mirroring Port mirroring |
Security | Hierarchical management and password protection of users AAA authentication RADIUS authentication HWTACACS LDAP SSH 2.0 Port isolation 802.1X Portal Port security MAC-address-based authentication IP Source Guard HTTPS PKI IPsec EAD Public key management |
802.1X | Up to 2K users Port-based and MAC address-based authentication Trunk port authentication Dynamic 802.1X-based QoS/ACL/VLAN assignment |
Loading and upgrading | Loading and upgrading through XModem protocol Loading and upgrading through FTP Loading and upgrading through the trivial file transfer protocol (TFTP) |
Management | Configuration at the command line interface Remote configuration through Telnet Configuration through Console port Simple network management protocol (SNMP) Remote Monitoring(RMON) IMC NMS System log Hierarchical alarms NTP Power supply alarm function Fan and temperature alarms |
Maintenance | Debugging information output Ping and Tracert Remote maintenance through Telnet NQA 802.1ag 802.3ah DLDP Virtual Cable Test |
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.
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.
| NOTE: Boot ROM images are not released along with the boot images and system images. To get a version of Boot ROM image, contact the H3C technical support. |
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
You can upgrade system software by using one of the following methods:
Upgrading method | Software types | Remarks |
Upgrading from the CLI | · Boot ROM image · Software images | · You must reboot the switch to complete the upgrade. · This method can interrupt ongoing network services. |
Upgrading from the Boot menu | · Boot ROM image · Software images | Use this method when the switch cannot correctly start up.
Upgrading an IRF fabric from the CLI instead of the Boot menu. The Boot menu method increases the service downtime, because it requires that you upgrade the member switches one by one. |
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, S5136S_EI-CMW710-BOOT-R6817P02.bin and S5136S_EI -CMW710-SYSM- R6817P02.bin.
1. Verify that the system state, redundancy state, and state of each slot are stable.
<Sysname> display system stable state
System state : Stable
Redundancy state : No redundance
Slot CPU Role State
1 0 Active Stable
2. If the device is unstable, use the following commands to troubleshoot the issue:
¡ Use the display device command to verify that the device is operating correctly.
¡ Use the display ha service-group command to verify that bulk backup has been finished for all modules.
¡ Use the display system internal process state command in probe view to verify that services are running correctly.
3. If a slot persists in unstable state or there are other unrecoverable issues, contact the technical support.
Setting up the upgrade environment
Before you upgrade system software, complete the following tasks:
· Set up the upgrade environment as shown in Figure 2.
· Configure routes to make sure that the router and the file server can reach each other.
· Run a TFTP or FTP server on the file server.
· Log in to the CLI of the router through the console port.
· Copy the upgrade file to the file server and correctly set the working directory on the TFTP or FTP server.
· Make sure that the upgrade has minimal impact on the network services. During the upgrade, the router cannot provide any services.
Figure 2 Setting up the upgrade environment
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 S5136S-EI switch series.
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.
IMPORTANT: Each IRF member switch must have free storage space that is at least two times the size of the upgrade image file. |
# Identify the free flash space of the master switch.
<Sysname> dir
Directory of flash:
0 -rw- 220684 Jan 01 2013 00:17:13 defaultfile.zip
1 drw- - Jan 01 2013 00:17:27 diagfile
2 drw- - Jan 01 2013 00:17:28 license
3 drw- - Jan 01 2013 00:17:27 logfile
4 drw- - Jan 01 2013 00:17:41 pki
5 -rw- 6161408 Jan 01 2013 00:17:27 boot.bin
6 -rw- 50729984 Jan 01 2013 00:17:27 system.bin
7 drw- - Jan 01 2013 00:17:27 seclog
8 drw- - Jan 01 2013 00:17:49 versionInfo
507904 KB total (275908 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- 220684 Jan 01 2013 00:17:13 defaultfile.zip
1 drw- - Jan 01 2013 00:17:27 diagfile
2 drw- - Jan 01 2013 00:17:28 license
3 drw- - Jan 01 2013 00:17:27 logfile
4 drw- - Jan 01 2013 00:17:41 pki
5 -rw- 6161408 Jan 01 2013 00:17:27 boot.bin
6 -rw- 50729984 Jan 01 2013 00:17:27 system.bin
7 drw- - Jan 01 2013 00:17:27 seclog
8 drw- - Jan 01 2013 00:17:49 versionInfo
507904 KB total (199436 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:
CAUTION: · To avoid data loss, do not delete the current configuration file. For information about the current configuration file, use the display startup command. · The delete /unreserved file-url command deletes a file permanently and the action cannot be undone. · The delete file-url command moves a file to the recycle bin and the file still occupies storage space. To free the storage space, first execute the undelete command to restore the file, and then execute the delete /unreserved file-url command. |
# 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
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 is Image (Binary)
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 the file flash:/newest.ipe on slot 1......Done.
Images in IPE:
boot.bin
system.bin
This command will set the main startup software images. Continue? [Y/N]:y
Add images to slot 1.
Decompressing file boot.bin to flash:/boot.bin....................Done.
Decompressing file system.bin to flash:/system.bin................Done.
Verifying the file flash:/boot.bin on slot 1...Done.
Verifying the file flash:/system.bin on slot 1............Done.
The images that have passed all examinations will be used as the main startup software 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 the file flash:/newest.ipe on slot 2......Done.
Images in IPE:
boot.bin
system.bin
This command will set the main startup software images. Continue? [Y/N]:y
Add images to slot 2.
Decompressing file boot.bin to flash:/boot.bin....................Done.
Decompressing file system.bin to flash:/system.bin................Done.
Verifying the file flash:/boot.bin on slot 2...Done.
Verifying the file flash:/system.bin on slot 2.........Done.
The images that have passed all examinations will be used as the main startup software 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).
| NOTE: The system automatically checks the compatibility of the Boot ROM image and the boot and system images during the reboot. If you are prompted that the Boot ROM image in the upgrade image file is different than the current Boot ROM image, upgrade both the basic and extended sections of the Boot ROM image for compatibility. If you choose to not upgrade the Boot ROM image, the system will ask for an upgrade at the next reboot performed by powering on the switch or rebooting from the CLI (promptly or as scheduled). If you fail to make any choice in the required time, the system upgrades the entire Boot ROM image. |
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.
TIP: Upgrading through the Ethernet port is faster than through the console port. |
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.
| NOTE: The file server and the configuration terminal can be co-located. |
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
IMPORTANT: For the switch to start up correctly, do not delete the main startup software images when you free storage space before upgrading Boot ROM. On the Boot menu, the main startup software images are marked with an asterisk (*). |
When you upgrade software, make sure each member switch has sufficient free storage space for the upgrade file, as shown in Table 4.
Table 4 Minimum free storage space requirements
Upgraded images | Minimum free storage space requirements |
Comware images | Two times the size of the Comware upgrade package file. |
Boot ROM | Same size as the Boot ROM upgrade image file. |
If no sufficient space is available, delete unused files.
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.
Starting......
Press Ctrl+D to access BASIC-BOOTWARE MENU...
Press Ctrl+T to access BOOTWARE DIAG-TEST MENU
********************************************************************************
* *
* H3C S5136S-10T2S2X-EI-Q BOOTROM, Version 102 *
* *
********************************************************************************
Copyright (c) 2004-2025 New H3C Technologies Co., Ltd.
Creation Date : Jan 29 2025
Memory Type : DDR4 SDRAM
Memory Size : 2048MB
Memory Speed : 1200MHz
CPLD Version : 001
PCB Version : Ver.B
Mac Address : 00e0fc005100
BootRom Validating...
Press Ctrl+B to access EXTENDED BOOT MENU...1
Press one of the shortcut key combinations at prompt.
Shortcut keys | Prompt message | Function | Remarks |
Ctrl+B | Press Ctrl+B to enter Extended Boot menu... | Accesses the extended Boot menu. | Press the keys within 1 second (in fast startup mode) or 5 seconds (in full startup mode) after the message appears. You can upgrade and manage system software and Boot ROM from this menu. |
Accessing the extended Boot menu
To access the extended Boot menu:
1. Press Ctrl+B within 1 second (in fast startup mode) or 5 seconds (in full startup mode) after the "Press Ctrl+B to access EXTENDED BOOT MENU..." prompt message appears. If you fail to do this, the system starts decompressing the system software.
2. Press Enter at the prompt for password.
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 6).
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
9. Set The Operating Device
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-9):
Table 6 Extended Boot ROM menu options
Option | Tasks |
1. Download image to flash | Download a software image file to the flash. |
2. Select image to boot | Specify the main and backup software image file for the next startup. Specify the main and backup configuration files for the next startup. This task can be performed only if password recovery capability is enabled. |
3. Display all files in flash | Display files on the flash. |
4. Delete file from flash | Delete files to free storage space. |
5. Restore to factory default configuration | Delete the current next-startup configuration files and restore the factory-default configuration. This option is available only if password recovery capability is disabled. |
6. Enter BootRom upgrade menu | Access the Boot ROM upgrade menu. |
7. Skip current system configuration | Start the switch without loading any configuration file. This is a one-time operation and takes effect only for the first system boot or reboot after you choose this option. This option is available only if password recovery capability is enabled. |
8. Set switch startup mode | Set the startup mode to fast startup mode or full startup mode. |
0. Reboot | Reboot the switch. |
Ctrl+F: Format File System | Format the current storage medium. |
Ctrl+P: Change authentication for console login | Skip the authentication for console login. This is a one-time operation and takes effect only for the first system boot or reboot after you choose this option. This option is available only if password recovery capability is enabled. |
Ctrl+R: Download image to SDRAM and run | Download a system software image and start the switch with the image. This option is available only if password recovery capability is enabled. |
Ctrl+Z: Access EXTENDED ASSISTANT MENU | Access the EXTEND-ASSISTANT menu. For options in the menu, see Table 7. |
Table 7 EXTEND-ASSISTANT menu options
Option | Task |
1. Display Memory | Display data in the memory. |
2. Search Memory | Search the memory for a specific data segment. |
0. Return to boot menu | Return to the extended Boot ROM menu. |
| NOTE: The procedure of upgrading Boot ROM is the same as upgrading system software. This guide takes upgrading Boot ROM as an example. |
Software Upgrading
IMPORTANT: Upgrade software only when necessary and under the guidance of a technical support engineer. |
The device software can be upgraded through console port, TFTP, and FTP.
Remote Upgrading through CLI
You may upgrade the application and Boot ROM program of a device remotely through command line interface (CLI). Get the application and Boot ROM program, app.ipe and Boot.btm for example, from the FTP server as follows:
< Sysname > ftp 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.
ftp> get app.ipe
227 Entering Passive Mode (10,10,110,1,17,97).
125 BINARY mode data connection already open, transfer starting for /app.ipe
226 Transfer complete.
32133120 bytes received in 35 seconds (896. 0 kbyte/s)
ftp> bye
221 Server closing.
<Sysname> bootrom update file flash:/update.btm slot 1
This command will update the Boot ROM file on the specified board(s), Continue? [Y/N]:y
Now updating the Boot ROM, please wait............................Done.
< Sysname > boot-loader file flash:/app.ipe slot 1 main
Verifying the file flash:/app.ipe on slot 1......Done.
Images in IPE:
boot.bin
system.bin
This command will set the main startup software images. Continue? [Y/N]:y
Add images to slot 1.
Decompressing file boot.bin to flash:/boot.bin....................Done.
Decompressing file system.bin to flash:/system.bin................Done.
Verifying the file flash:/boot.bin on slot 1...Done.
Verifying the file flash:/system.bin on slot 1............Done.
The images that have passed all examinations will be used as the main startup software images at the next reboot on slot 1.
< Sysname > display boot-loader
Software images on slot 1:
Current software images:
flash:/boot.bin
flash:/system.bin
Main startup software images:
flash:/boot.bin
flash:/system.bin
Backup startup software images:
None
After upgrading the new application file, reboot the device to have the upgraded application take effect.
Boot Menu
The Boot ROM menus include a basic Boot menu and an extended Boot menu.
The extended Boot menu is provided by the extended Boot ROM segment. From this menu, you can perform various tasks, including upgrading Boot ROM, upgrading and managing system software images, and managing files. For more information, see "Accessing the extended Boot menu."
Both the basic Boot menu and extended Boot menu support using XMODEM to upgrade Boot ROM through the console port.
If the extended Boot ROM segment has corrupted, you can repair or upgrade it from the basic Boot menu.
| NOTE: The procedures for upgrading Boot ROM and system software from the extended Boot menu are the same except that you must choose different options from the Boot menu (1 for upgrading system software, and 6 for upgrading Boot ROM) to start the upgrade procedure. This appendix describes only the Boot ROM upgrade procedure. |
To upgrade software from Boot ROM menus:
1. Connect a configuration terminal such as a PC to the console port of the switch with a console cable.
2. Run the terminal emulation program on the PC.
3. Power on the switch.
The switch starts up and displays the following message:
Starting......
Press Ctrl+D to access BASIC BOOT MENU
Booting Normal Extend BootWare....
***************************************************************************
* *
* BOOTROM, Version 102 *
* *
***************************************************************************
Creation Date : Jun 4 2024
Memory Type : DDR4 SDRAM
Memory Size : 2048MB
Memory Speed : 1200MHz
CPLD Version : 002
PCB Version : Ver.A
Mac Address : 103f8c78d8c4
Press Ctrl+B to access EXTENDED BOOT MENU...0
4. Press one of the shortcut key combinations at prompt.
Shortcut keys | Prompt message | Function | Remarks |
Ctrl+B | Press Ctrl-B to enter Extended Boot menu... | Accesses the extended Boot menu. | Press the keys within 1 second (in fast startup mode) or 5 seconds (in full startup mode) after the message appears. You can upgrade and manage system software and Boot ROM from this menu. |
Accessing the extended Boot menu
To access the extended Boot menu:
1. Press Ctrl+B within 1 second (in fast startup mode) or 5 seconds (in full startup mode) after the "Press Ctrl+B to access EXTENDED BOOT MENU..." prompt message appears. If you fail to do this, the system starts decompressing the system software.
2. Press Enter at the prompt for password.
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 6).
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
9. Set The Operating Device
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-9):
Table 9 Extended Boot ROM menu options
Option | Tasks |
1. Download image to flash | Download a software image file to the flash. |
2. Select image to boot | Specify the main and backup software image file for the next startup. Specify the main and backup configuration files for the next startup. This task can be performed only if password recovery capability is enabled. |
3. Display all files in flash | Display files on the flash. |
4. Delete file from flash | Delete files to free storage space. |
5. Restore to factory default configuration | Delete the current next-startup configuration files and restore the factory-default configuration. This option is available only if password recovery capability is disabled. |
6. Enter BootRom upgrade menu | Access the Boot ROM upgrade menu. |
7. Skip current system configuration | Start the switch without loading any configuration file. This is a one-time operation and takes effect only for the first system boot or reboot after you choose this option. This option is available only if password recovery capability is enabled. |
8. Set switch startup mode | Set the startup mode to fast startup mode or full startup mode. |
0. Reboot | Reboot the switch. |
Ctrl+F: Format File System | Format the current storage medium. |
Ctrl+P: Change authentication for console login | Skip the authentication for console login. This is a one-time operation and takes effect only for the first system boot or reboot after you choose this option. This option is available only if password recovery capability is enabled. |
Ctrl+R: Download image to SDRAM and run | Download a system software image and start the switch with the image. This option is available only if password recovery capability is enabled. |
Ctrl+Z: Access EXTENDED ASSISTANT MENU | Access the EXTEND-ASSISTANT menu. For options in the menu, see Table 7. |
Table 10 EXTEND-ASSISTANT menu options
Option | Task |
1. Display Memory | Display data in the memory. |
2. Search Memory | Search the memory for a specific data segment. |
0. Return to boot menu | Return to the extended Boot ROM menu. |
| NOTE: The procedure of upgrading Boot ROM is the same as upgrading system software. This guide takes upgrading Boot ROM as an example. |
Software Upgrading via Console Port (Xmodem Protocol)
Step 1: Enter 1 in the Boot menu. Press <Enter> and the system will access the download program menu.
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
Step 2: Enter 3 in the download program menu. Select to implement the software upgrading via Xmodem protocol. Press <Enter> and the screen will display the following information:
Please select your download baudrate:
1. * 9600
2. 19200
3. 38400
4. 57600
5. 115200
6. Exit
Enter your choice (0-5):
Step 3: Select the appropriate download speed based on the actual requirements. For example, enter 5 to select the download speed as 115200bps. Press <Enter> and the system will display the following information:
Download baudrate is 115200 bps. Please change the terminal's baudrate to 115200 bps, and select XMODEM protocol.
Press ENTER key when ready.
Step 4: Follow the above prompt and change the baud rate on the console terminal, so that the baud rate is consistent with the selected download baud rate of the software. After the baud rate setting at the console terminal is completed, disconnect the terminal and reconnect it. Press <Enter> to start downloading, and the screen will display the following information:
Are you sure to download file to flash? Yes or No(Y/N)y
Now please start transfer file with XMODEM protocol.
If you want to exit, Press <Ctrl+X>.
Downloading ... CCCCC
| NOTE: After the terminal baud rate is modified, it is necessary to disconnect and then re-connect the terminal emulation program to validate the new setting. |
Step 5: Select [Transfer\Send File] from the terminal window. Click <Browse> in the pop-up window (as shown Figure 3) and select the software to be downloaded. Change the protocol name to Xmodem.
Step 6: Click <Send> and the system will display the window as shown Figure 4.
Step 7: After the downloading of the program is completed, “Load File name” should be input in order to write the file to flash. Then file attribute should be set.
Please input the file attribute (Main/Backup/None) m
The boot.bin image is self-decompressing...
Load File name : boot.bin # Set the name of the downloaded Boot package
Free space: 470519808 bytes
Writing flash...................................................................
.............Done!
The system.bin image is self-decompressing...
Load File name : system.bin # Set the name of the downloaded System software package
Free space: 461522944 bytes
Writing flash...................................................................
.............Done!
Your baudrate should be set to 9600 bps again!
Press enter key when ready
Software Upgrading via Ethernet Interface (FTP/TFTP)
Software Upgrading via TFTP
Introduction to TFTP
TFTP (trivial file transfer protocol) is a type of simple file transfer protocol in the TCP/IP protocol suite that applies between clients and servers. TFTP is normally realized on the UDP basis to provide unreliable data transfer service.
TFTP upgrading procedure
Step 1: Select an Ethernet interface for downloading on the S5136S_EI. Connect the switch to the PC (where the upgrading file is located) via the interface. At the same time, you should connect the switch to a PC via the console port (The PC should be the same as the PC where the upgrading file is located).
Step 2: Run the TFTP server program on the PC connected with the Ethernet interface for upgrading, and specify the file path of the upgrading program.
CAUTION: QX series switches are not shipped with TFTP Server program. |
Step 3: Run the terminal emulation program on the PC connected to the Console port, and boot the switch to access the Boot menu.
Step 4: Enter 1 in the Boot menu. Press <Enter> and the system will access the download program menu.
Please set application file download protocol parameter:
1. Set TFTP protocol parameter
2. Set FTP protocol parameter
3. Set XMODEM protocol parameter
0. Return to boot menu
Enter your choice(0-3):1
Step 5: Enter 1 in the download program menu. Select to use TFTP for the software upgrading. Press <Enter> and the screen will display the following information:
Load File Name : app.bin
Server IP Address :192.168.1.132
Local IP Address : 192.168.1.122
Gateway IP Address :
Step 6: Complete the relevant information based on the actual requirements and press <Enter>. The screen will display the following information:
Are you sure to download file to flash? Yes or No(Y/N)
Step 7: Enter Y and the system starts downloading the file. Enter N and the system will return to Boot menu. Take entering Y as an example. Enter Y and press <Enter>, the system begins downloading programs. After the downloading is completed, the system starts write-flash operation. Upon completion of this operation, the file attribute should be set.
Writing flash..............................................................
................Done!
Please input the file attribute (Main/Backup/None) M
Done!
Software Upgrading via FTP
Introduction to FTP
Through the Ethernet port, the S5136S_EI can serve as an FTP server or client. It provides another means to download the system program and configure the files. In the following description we assume that the S5136S_EI serves as an FTP client.
FTP upgrading procedure
Step 1: Select an Ethernet interface for downloading on the S5136S_EI. Connect the switch to the PC (where the upgrading file is located and whose IP address should be known) via the interface. At the same time, you should connect the switch to a PC via the Console port (the PC should be the same as the PC where the upgrading file is located).
Step 2: Run the FTP server program on the PC connected to the Ethernet interface for upgrading, and specify the file path of the upgrading program.
Step 3: Run the terminal emulation program on the PC connected to the Console port, and boot the switch to access the Boot menu.
Step 4: Enter 1 in the Boot menu. Press <Enter> and the system will access the download program menu.
Please set application file download protocol parameter:
1. Set TFTP protocol parameter
2. Set FTP protocol parameter
3. Set XMODEM protocol parameter
0. Return to boot menu
Enter your choice(0-3):2
Step 5: Enter 2 in the download program menu. Select FTP for the software upgrading. Press <Enter> and the screen will display the following information:
Load File Name : app.bin
Server IP Address :192.168.1.132
Local IP Address :192.168.1.122
Gateway IP Address :192.168.0.200
FTP User Name : s4000
FTP User Password : s4000
Step 6: Complete the relevant information based on the actual requirements and press <Enter>. The screen will display the following information:
Are you sure to download file to flash? Yes or No(Y/N):
Step 7: Enter Y and the system starts downloading the file. Enter N and the system will return to Boot menu. Take the first case as an example. Enter Y and press <Enter>, the system begins downloading programs. After the downloading is completed, the system starts write-flash operation. Upon completion of this operation, the file attribute should be set.
Writing flash..............................................................
................Done!
Please input the file attribute (Main/Backup/None) M
Done!
BootRom auto update
The BootRom is packed with application, when BootRom boot the application, it check the version of the BootRom, if the version is not the same, the BootRom will be auto updated.
Starting......
************************************************************************
* *
* BOOTROM, Version 102 *
* *
************************************************************************
Creation Date : Jun 4 2024
Memory Type : DDR4 SDRAM
Memory Size : 2048MB
Memory Speed : 1200MHz
CPLD Version : 002
PCB Version : Ver.A
Mac Address : 103f8c78d8c4
Press Ctrl+B to access EXTENDED BOOT MENU...0
Loading the main image files...
Loading file flash:/system.bin...................................Done.
Loading file flash:/boot.bin.........Done.
Extended BootRom Version is not equal,updating? (Y/N):
Updating extended BootRom........Done.
Basic BootRom Version is not equal,updating? (Y/N):
Updating Basic BootRom....Done.
BootRom updated,System is rebooting now.
Starting......
Press Ctrl+D to access BASIC BOOT MENU
Booting Normal Extend BootWare....
************************************************************************
* *
* BOOTROM, Version 102 *
* *
************************************************************************
Creation Date : Jun 4 2024
Memory Type : DDR4 SDRAM
Memory Size : 2048MB
Memory Speed : 1200MHz
CPLD Version : 002
PCB Version : Ver.A
Mac Address : 103f8c78d8c4
Press Ctrl+B to access EXTENDED BOOT MENU...0
Loading the main image files...
Loading file flash:/system.bin...........................................Done.
Loading file flash:/boot.bin.........Done.
Image file flash:/boot.bin is self-decompressing.........................................................................................................................................................................................................................................................................................................................................................................................................................................Done.
System is starting...
Cryptographic algorithms tests passed.