НОВА (г.Минск) - Главная
| |
|ZXR10 5950-H&5900E Series Ethernet Switch V3.00.11 Version Upgrade Guide |
| |
|R1.1 |
| |
|LEGAL INFORMATION |
| |
|By accepting this certain document of ZTE CORPORATION you agree to the following terms. If you do not agree to the following terms, |
|please notice that you are not allowed to use this document. |
| |
|Copyright © 2015 ZTE CORPORATION. Any rights not expressly granted herein are reserved. This document contains proprietary information |
|of ZTE CORPORATION. Any reproduction, transfer, distribution, use or disclosure of this document or any portion of this document, in |
|any form by any means, without the prior written consent of ZTE CORPORATION is prohibited. |
| |
|[pic] and [pic] are registered trademarks of ZTE CORPORATION. ZTE’s company name, logo and product names referenced herein are either |
|trademarks or registered trademarks of ZTE CORPORATION. Other product and company names mentioned herein may be trademarks or trade |
|names of their respective owners. Without the prior written consent of ZTE CORPORATION or the third party owner thereof, anyone’s |
|access to this document should not be construed as granting, by implication, estopped or otherwise, any license or right to use any |
|marks appearing in the document. |
| |
|The design of this product complies with requirements of environmental protection and personal security. This product shall be stored, |
|used or discarded in accordance with product manual, relevant contract or laws and regulations in relevant country (countries). |
| |
|This document is provided “as is” and “as available”. Information contained in this document is subject to continuous update without |
|further notice due to improvement and update of ZTE CORPORATION’s products and technologies. |
|ZTE CORPORATION |
|Address: |NO. 55 |
| |Hi-tech Road South |
| |ShenZhen |
| |P.R.China |
| |518057 |
|Website: | (TSM-Technical Support) |
|Email: |TSM.Aftersales@.cn |
| | |
Revision History
|Product Version |Document Version |Serial Number |Reason for Revision |
|V3.00.11 |R1.0 | |First published |
|V3.00.11 |R1.1 | |Updated |
| | | | |
Author
|Date |Document Version |Prepared by |Reviewed by |Approved by |
|2015-01-23 |R1.0 |Huang Zhiyan |Huang Zhiyan | |
|2015-1-23 |R1.1 |Gao Xiang | | |
| | | | | |
Applicable to: Commissioning and maintenance engineers
Proposal: Before reading this document, you had better have the following knowledge and skills.
|SEQ |Knowledge and skills |Reference material |
|1 | | |
|2 | | |
|3 | | |
Follow-up document: After reading this document, you may need the following information
|SEQ |Reference material |Information |
|1 | | |
|2 | | |
|3 | | |
About This Document
Summary
|Chapter |Description |
|1 Version Information |Introduces software version status. |
|2 Upgrade Flow |Introduces software version upgrade flow. |
|3 Preparation before Upgrade |Introduces preparations before upgrade. |
|4 Bootrom Upgrade |Introduces bootrom upgrade precautions, upgrade procedures, and check after upgrade.|
|5 Software Version Upgrade |Introduces software version upgrade precautions, upgrade procedures, and inspection |
| |and test after upgrade. |
|6 Upgrading the POE Firmware |Introduces the precautions for the POE upgrade, upgrade procedures, and inspection |
| |and test after the upgrade. |
|7 Version Rollback |Introduces specific rollback steps for different situations. |
|8 Frequently Asked Questions |Introduces the frequently asked questions. |
|AppA Usage Guideline for Common Terminal Software|Introduces how to set and use common upgrade software. |
|and FTP Software | |
TABLE OF CONTENTS
1 Version Information 1
2 Upgrade Flow 2
3 Preparation before Upgrade 4
3.1 Preparation Records before Upgrade 4
3.2 Reading Version Supporting Documents 4
3.3 Preparing Software and Hardware 5
3.4 Setting up an Upgrade Environment 5
3.5 Backing up Data 6
3.5.1 Backing up Configuration Information 6
3.5.2 Backing up Version Files 7
3.6 Checking the Operating Status 8
3.6.1 Checking the operating status of hardware 8
3.6.2 Checking the Operating Status of the System 8
3.6.3 Checking Services 9
3.6.4 Checking Flash Free Space 9
4 Bootrom Upgrade 11
4.1 Precautions 11
4.2 Upgrade Flow 12
4.3 Record of the Upgrade Process 12
4.4 Upgrade Procedure 12
4.4.1 Deleting the Remaining Boot Files 13
4.4.2 Copying Boot Files 13
4.4.3 Upgrading bootrom 14
4.4.4 Verifying the Upgrade 15
4.4.5 Synchronizing the bootrom Master and Slave Zones 15
5 Software Version Upgrade 16
5.1 Precautions 16
5.2 Upgrade Flow 16
5.3 Record of the Upgrade Process 17
5.4 Upgrade Procedure 18
5.4.1 Renaming the Previous Version Files 18
5.4.2 Setting the Backup Version Boot 18
5.4.3 Downloading the Target Version Files through FTP 18
5.4.4 Checking the Target Version 19
5.4.5 Checking the Boot Mode 20
5.4.6 Restarting the Switch 20
5.4.7 Checking the Boot Status of the Device 21
5.4.8 Viewing the New Version Information 21
5.4.9 Checking the Configuration Information 22
5.4.10 Verifying the Upgrade 22
5.4.11 Deleteing the Backup Version File 23
6 Upgrading the POE Firmware 24
6.1 Precautions 24
6.2 Upgrade Flow 25
6.3 Upgrade Process Record 25
6.4 Upgrade Procedures 26
6.4.1 Copying the POE Firmware Version File 26
6.4.2 Upgrading the POE Firmware 27
6.4.3 Verifying the Upgrade 28
7 Version Rollback 29
7.1 Rollback Application 29
7.2 Failure to Start the Device Normally 29
7.3 Abnormal Services 31
7.4 Abnormal POE Power Supply 32
8 Frequently Asked Questions 34
AppA Usage Guideline for Common Terminal Software and FTP Software 35
A.1 Terminal Software 35
A.1.1 HyperTerminal 35
A.1.2 SecureCRT 35
A.2 FTP Tool 36
A.2.1 3CDaemon 37
A.2.2 WFTPD 38
A.3 Araxis merge 38
A.4 EasyManager 39
FIGURES
Figure 2-1 Version Upgrade Flow 2
Figure 4-1 Bootrom Upgrade Flow 12
Figure 5-1 Software Version Upgrade Flow 17
Figure 6-1 POE Upgrade Flowchart 26
TABLES
Table 1-1 Product Model 1
Table 1-2 File List 1
Table 3-1 Preparation Records before Upgrade 4
Table 3-2 Checklist of the System Operating Status 8
Table 4-1 Bootrom Upgrade Process 12
Table 5-1 Software Version Upgrade Process 17
Table 6-1 Record of the POE Firmware Upgrade Process 26
Version Information
( Tip:
This guide is applicable to engineers who are familiar with data products, have experiences in data product upgrade, and pass ZTE Data Products Certificate Test-Level I or above.
ZXR10 5950-H series & &5900E series switches include multiple product models of one product series, as shown in Table 1-1. In which, hardware version of 5900E series is V1.4.
Table 1-1 Product Model
|Product Series |Product Model |
|5950-H series |ZXR10 5950-36TM-H, 5950-36PM-H, 5950-56TM-H, and 5950-56PM-H |
|5900E series |ZXR10 5916E, ZXR10 5928E, ZXR10 5928E-FI, ZXR10 5952E |
The software package for ZXR10 5950-H Series & 5900E Series switches contains many files. Refer to Table 1-2 for the list of the files.
Table 1-2 File List
|File Name (Including |File Type |Product Series/Model/Board |
|Path) | | |
|\5950\HMPU.set |Version |ZXR10 5950-H Series |
|\bootrom.bin |boot file |ZXR10 5950-H Series |
|poe.BIN |POE firmware file |5950-36PM-H and 5950-56PM-H |
Upgrade Flow
Figure 2-1 illustrates the upgrade flow of ZXR10 5950-H Series &5900E Series switches.
Figure 2-1 Version Upgrade Flow
[pic]
1. Preparation before Upgrade
Preparations should be made in advance. For details, refer to 3 Preparation before Upgrade.
2. Bootrom Upgrade
During the preparation, make clear whether Bootrom upgrade is needed in the upgrade. If yes, refer to 4 BOOTROM UPGRADE to perform the upgrade.
This process lasts about 5-10 minutes.
3. Software Version Upgrade
Refer to 5 SOFTWARE VERSION UPGRADE to upgrade the software version. If the upgrade succeeds, the upgrade is completed; if it fails, roll back to the old version.
This process lasts about 20 minutes.
4. Version Rollback
If the version upgrade fails, perform steps for version rollback. Perform different rollback procedures for specific failures. For details, refer to 6 VERSION ROLLBACK.
This process lasts about 30 minutes.
Preparation before Upgrade
This chapter focuses on a series of preparations before the upgrade.
1 Preparation Records before Upgrade
To ensure a quick, accurate and safe upgrade, make good preparations before the upgrade.
Make preparations according to Table 3-1, and record whether each of them is completed.
Table 3-1 Preparation Records before Upgrade
|No. |Preparation |Completed or Not |Record of Preparation |
|1 |Read version supporting documents | | |
|2 |Prepare software and hardware | | |
|3 |Set up an upgrade environment | | |
|4 |Back up configuration information | | |
|5 |Back up version files | | |
|6 |Check the operating status of | | |
| |hardware | | |
|7 |Check the operating status of the | | |
| |system | | |
|8 |Check services | | |
|9 |Check Flash free space | | |
2 Reading Version Supporting Documents
Download version documents, including version release instruction and version upgrade guide (this document itself); and read them carefully.
1. Version Release Instruction
Read the Version Release Instruction for the following information:
– Whether bootrom needs to be upgraded.
– Whether configuration commands of the target version are changed.
2. Version Upgrade Guide
Read it to have a good grasp of the precautions and the specific operation procedure.
3 Preparing Software and Hardware
1. Hardware Preparation
– If possible, prepare spare parts for switches at key nodes and tools necessary for the replacement.
– Prepare serial console cables and network cables needed; and check whether they are usable.
2. Software Preparation
– Request and download version files according to procedures specified by ZTE and check the file size.
– If there are any changes in configuration commands of the target version, acquire the current configuration in advance. Check whether there are any configuration differences between the target version and the original version. If any, record them, and then compile corresponding configuration command scripts according to the format of the new version.
– Prepare FTP/TFTP tool software that is necessary for upgrade, and check if it is usable.
– Prepare Araxis merge for comparing the configuration information before and after the upgrade.
4 Setting up an Upgrade Environment
1. Serial Port Connection
Connect a PC to the device via the serial console cable; open HyperTerminal or other terminal software to configure the serial port attributes:
– Bits per Second (baud rate): 9600
– Data Bits: 8
– Parity: None
– Stop Bits: 1
– Flow Control: None
After the configuration, make sure that the device can be accessed through the serial port. Next, enable automatic logging function for the terminal software.
For details about the setting method, refer to A.1 Terminal Software.
2. Network Cable Connection
Connect the network port of the PC to the service port or management port of the device via the network cable. Configure IP addresses from the same subnet for them to ensure that the two peers can ping through each other.
The PC telnets the IP address of the device. And the device can be logged in properly.
3. Start the FTP Server
Set and start the FTP server software to ensure that it is running properly. For details about the settings of the FTP server, refer to A.2 FTP Tool.
5 Backing up Data
1 Backing up Configuration Information
The current configuration of the device is so vital that it must be backed up before the upgrade. It is used to restore the data after the upgrade.
1. Check the current configuration of the device and save the displayed configuration to the background server.
ZXR10#show running-config
2. Save the current configuration and make sure that it is saved properly.
ZXR10#write
Building configuration...
..[OK]
ZXR10#dir DATA0
Directory of MP-0/1/0: /flash/DATA0
356352 KB total (234200 KB free)
attribute size date time name
1 2048 12-09-2014 14:58 .
2 2048 12-09-2014 14:58 ..
3 ---- 7219 12-09-2014 14:58 startrun.dat
3. Back up the configuration file to the background FTP server.
– Copy the configuration file through the service port:
ZXR10#copy ftp root: /flash/DATA0/startrun.dat //192.168.1.254/startrun.dat @target:target
– Copy the configuration file via the management port:
ZXR10#copy ftp vrf mng root: /flash/DATA0/startrun.dat //192.168.1.254/startrun.dat@target:target
2 Backing up Version Files
If the upgrade fails, the old version is used to restore the operation. Therefore, it is important to back up the version file.
1. View the version file on the current device.
ZXR10#dir
Directory of MP-0/1/0: /flash
356352 KB total (230812 KB free)
attribute size date time name
1 2048 12-09-2014 10:29 .
2 2048 12-09-2014 10:29 ..
3 2048 12-09-2014 10:31 DATA0
4 10 01-01-2010 00:00 1_1_2_0
5 2048 01-01-2010 00:00 641
6 2048 01-01-2010 00:01 syscmd_log
7 10 01-01-2010 00:00 255_1_65535_255
8 2048 01-01-2010 00:00 256
9 2048 01-01-2010 00:00 ssh
10 2048 01-01-2010 00:01 LOG
11 ---- 652740 12-09-2014 10:29 bootrom.bin
12 2048 12-10-2014 09:09 techspt
13 2048 12-09-2014 10:30 lost+found
14 ---- 59104779 07-15-2014 09:39 old.set
15 2048 01-01-2010 00:01 usrcmd_log
16 ---- 63070107 12-09-2014 10:28 HMPU.set
17 2048 01-01-2010 00:01 run_log
2. Back up the version file to the background FTP server.
– Copy the version file through the service port:
ZXR10# copy ftp root: /flash/HMPU.set //192.168.1.254/HMPU.set@target:target
– Copy the version file through the management port:
ZXR10#copy ftp vrf mng root: /flash/HMPU.set //192.168.1.254/HMPU.set@target:target
6 Checking the Operating Status
1 Checking the operating status of hardware
Check whether the hardware is in normal status before the upgrade to avoid latent risks.
Check whether the indicators on the panel are in normal status. The indicator status below is used for your reference.
1. RUN indicator
Off–The main board is faulty.
Flash–The main board is working properly.
2. PWR indicator
Always on–The system power is working normally.
Off–The system power is faulty.
3. LINK/ACT indicator
Flash–There are packets being received or sent on the interface.
On–A link is established on this interface.
Off–No interconnection is established between this interface and another interface.
2 Checking the Operating Status of the System
Check the operating status of the system before the upgrade and record related information for comparison after the upgrade. The main check items are listed in Checking the Operating Status of the System
.Add or delete items according to the actual situation.
Table 3-2 Checklist of the System Operating Status
|Item |Command |Remark |
|Show the software version of the |show version | |
|system | | |
|Display the boot version of the |show bootrom | |
|system | | |
|Show the current configuration |show running-config | |
|file | | |
|Show the CPU utilization |show processor | |
|Show the routing information |show ip forwarding route | |
|Display the types and number of |show ip protocol routing summary | |
|route entries | | |
|Show the port traffic statistics |show interface | |
|Show the layer-3 port information|show ip interface brief | |
|Show the information of the MAC |show mac table | |
|forwarding table | | |
|Show the information of the ARP |show arp | |
|table | | |
|Display the alarm information |show logging alarm | |
|Show the content of the log file |dir | |
|folder | | |
|Show the OSPF adjacency status |show ip ospf neighbor | |
|Show the BGP adjacency status |show ip bgp summary | |
|Show the PIM-SM adjacency |show ip pim neighbor | |
|information | | |
|Show the multicast routes |show ip mroute | |
|Show the MPLS forwarding table |show mpls forwarding-table | |
|Show the system clock |show clock | |
|Show the system temperature |show temperature | |
3 Checking Services
Check the operating status of services on the device. The check items are adjusted according to specific services at the sites where the devices are to be upgraded.
The service check requires collaboration with customers, and the result is confirmed by the customers.
4 Checking Flash Free Space
Before the upgrade, ensure that there is enough flash free space for the new version. If not enough, delete some useless files. If the space is still not enough, the files (such as, log files) that are not necessary for the operation of the system can be backed up to the background FTP server, and then deleted.
1. Check Flash free space
ZXR10#dir
Directory of MP-0/1/0: /flash
356352 KB total (230812 KB free)
attribute size date time name
1 2048 12-09-2014 10:29 .
2 2048 12-09-2014 10:29 ..
3 2048 12-09-2014 10:31 DATA0
4 10 01-01-2010 00:00 1_1_2_0
5 2048 01-01-2010 00:00 641
6 2048 01-01-2010 00:01 syscmd_log
7 10 01-01-2010 00:00 255_1_65535_255
8 2048 01-01-2010 00:00 256
9 2048 01-01-2010 00:00 ssh
10 2048 01-01-2010 00:01 LOG
11 ---- 652740 12-09-2014 10:29 bootrom.bin
12 2048 12-10-2014 09:09 techspt
13 2048 12-09-2014 10:30 lost+found
14 ---- 59104779 07-15-2014 09:39 old.set
15 2048 01-01-2010 00:01 usrcmd_log
16 ---- 63070107 12-09-2014 10:28 HMPU.set
17 2048 01-01-2010 00:01 run_log
2. Delete useless files
ZXR10#delete old.set
Are you sure to delete file(s)?[yes/no]:y
Delete file(s) successfully.
Bootrom Upgrade
Please skip this chapter if bootrom doesn’t need to be upgraded.
This chapter covers precautions, upgrade procedures, emergency handling and bootrom burning procedures.
1 Precautions
ZXR10 5950-H switches support live upgrade of bootrom. Pay attention to the following items during the upgrade:
1. Do not upgrade bootrom online when the CPU utilization is high.
2. Do not power off the system during the live upgrade of bootrom, otherwise the system will be unable to start.
3. Precautions for the bootrom upgrade are as follows:
i. The bootrom master and slave zones are set for the 5950-H.
ii. The master zone of the current boot zone is updated during the bootrom upgrade.
iii. If the bootrom update fails, do not restart the device directly. Try to upgrade bootrom a few more times.
iv. After the bootrom upgrade, if the device fails to load the boot file upon restart, then, when the timer expires, the system will switch back to the current slave zone to start, so as to ensure that the device can restore basic operation.
2 Upgrade Flow
Figure 4-1 Bootrom Upgrade Flow
[pic]
3 Record of the Upgrade Process
During the bootrom upgrade, perform the steps according to the requirements, and record the implementation of each step as shown in Table 4-1.
Table 4-1 Bootrom Upgrade Process
|No. |Step |Completed or Not |Record of Implementation |
|1 |Delete Remaining Boot Files | | |
|2 |Copy Boot Files | | |
|3 |Upgrade Bootrom | | |
|4 |Verify the Upgrade | | |
|5 |Synchronize the bootrom Master and | | |
| |Slave Zones | | |
4 Upgrade Procedure
Perform the upgrade steps as follows.
1 Deleting the Remaining Boot Files
Before the upgrade, delete the bootrom file of the previous version under the flash directory.
ZXR10#dir
Directory of MP-0/1/0: /flash
356352 KB total (230812 KB free)
attribute size date time name
1 2048 12-09-2014 10:29 .
2 2048 12-09-2014 10:29 ..
3 2048 12-09-2014 10:31 DATA0
4 10 01-01-2010 00:00 1_1_2_0
5 2048 01-01-2010 00:00 641
6 2048 01-01-2010 00:01 syscmd_log
7 10 01-01-2010 00:00 255_1_65535_255
8 2048 01-01-2010 00:00 256
9 2048 01-01-2010 00:00 ssh
10 2048 01-01-2010 00:01 LOG
11 ---- 652740 12-09-2014 10:29 bootrom.bin
12 2048 12-10-2014 09:09 techspt
13 2048 12-09-2014 10:30 lost+found
14 ---- 59104779 07-15-2014 09:39 old.set
15 2048 01-01-2010 00:01 usrcmd_log
16 ---- 63070107 12-09-2014 10:28 HMPU.set
17 2048 01-01-2010 00:01 run_log
Delete bootrom file:
ZXR10#delete bootrom.bin
Are you sure to delete file(s)?[yes/no]:y
Delete file(s) successfully.
2 Copying Boot Files
Before the upgrade, copy all boot files that are required for the upgrade to the flash directory of the switch.
– Copy the version file through the service port:
ZXR10#copy ftp //192.168.1.254/bootrom.bin@target:target root: /flash/bootrom.bin
– Copy the version file through the management port:
ZXR10#copy ftp vrf mng //192.168.1.254/bootrom.bin@target:target root: /flash/bootrom.bin
After copying, check the following information:
ZXR10#dir
Directory of MP-0/1/0: /flash
356352 KB total (230812 KB free)
attribute size date time name
1 2048 12-09-2014 10:29 .
2 2048 12-09-2014 10:29 ..
3 2048 12-09-2014 10:31 DATA0
4 10 01-01-2010 00:00 1_1_2_0
5 2048 01-01-2010 00:00 641
6 2048 01-01-2010 00:01 syscmd_log
7 10 01-01-2010 00:00 255_1_65535_255
8 2048 01-01-2010 00:00 256
9 2048 01-01-2010 00:00 ssh
10 2048 01-01-2010 00:01 LOG
11 ---- 652740 12-10-2014 09:29 bootrom.bin
12 2048 12-10-2014 09:09 techspt
13 2048 12-09-2014 10:30 lost+found
14 ---- 59104779 07-15-2014 09:39 old.set
15 2048 01-01-2010 00:01 usrcmd_log
16 ---- 63070107 12-09-2014 10:28 HMPU.set
17 2048 01-01-2010 00:01 run_log
[pic] Note:
The file name of boot saved to the flash directory must be correct and identical to that in the software package.
After copying, use the dir command to check whether the boot file size is consistent with that on the FTP server.
3 Upgrading bootrom
Record the boot information before the upgrade:
ZXR10#show bootrom
[MP(M) , shelf 0 , panel 1]
cpu 0
Bootrom Version :V1.26
Creation Date :2014/7/15
1. Enter the implicit mode of the system.
ZXR10#olleh
zxr10(config-increte)#
2. Upgrade bootrom.
ZXR10(config-corporation)#bootrom update mec master
%Code:164101 Bootrom update success!
If the update succeeds, a message indicating that the update is successful will be displayed.
( Tip:
If a message indicating that the update fails is displayed, please delete the corresponding boot file under the flash directory and recopy a new one to perform the update again.
3. Press ctrl+z to quit the implicit mode.
Exit the implicit mode and restart the device.
4 Verifying the Upgrade
Restart the device to check whether the boot version is updated. The bootrom information of the master zone is displayed only.
ZXR10#show bootrom
[MP(M) , shelf 0 , panel 1]
cpu 0
Bootrom Version :V1.26
Creation Date :2014/7/15
5 Synchronizing the bootrom Master and Slave Zones
After the system is started successfully, upgrade the bootrom version of the slave zone to synchronize the bootrom version of the master and slave zones.
ZXR10(config-corporation)#bootrom update mec slave
%Code:164101 Bootrom update success!
Software Version Upgrade
This chapter describes precautions, upgrade procedures, and inspections and tests after the upgrade.
1 Precautions
1. To facilitate further reason analysis of unexpected upgrade failures, set the auto-logging function of the terminal software before the upgrade.
2. During the process of writing the version into FLASH, do not restart the device or power it off, otherwise FLASH may be damaged.
3. During the process of writing the version into the FLASH, CPU utilization will rise. Therefore, it is forbidden to implement other operations on the device.
4. Rules for handling unexpected problems: recover services as soon as possible before locating the failure cause. Meantime, during the period of the upgrade request, try to collect information as much as possible for subsequent analysis.
5. For unexpected situations that cannot be solved, please contact the version upgrade instructor.
2 Upgrade Flow
Figure 5-1 shows the software version upgrade flow.
Figure 5-1 Software Version Upgrade Flow
[pic]
3 Record of the Upgrade Process
During the software version upgrade, perform the steps according to the requirements, and record the implementation of each step as shown in Table 5-1.
Table 5-1 Software Version Upgrade Process
|No. |Step |Completed or Not |Record of Implementation |
|1 |Rename the Previous Version Files | | |
|2 |Set the Backup Version | | |
|3 |Download the Target Version Files | | |
|4 |Check the Target Version | | |
|5 |Check the Boot Mode | | |
|6 |Restart the Switch | | |
|7 |Check the Boot Status of the Device| | |
|8 |View the New Version Information | | |
|9 |Check the Configuration Information| | |
|10 |Verify the Upgrade | | |
|11 |Version activation | | |
4 Upgrade Procedure
Perform the upgrade steps as follows.
1 Renaming the Previous Version Files
The device supports the backup version boot function for protection. If any error occurs during the new version is loaded, use the backup version files to start the device, so as to reduce upgrade failures caused by version files.
Rename the currently used version files before the upgrade. It is recommended that the name of the version files should be marked with the version number to distinguish different versions.
ZXR10#rename HMPU.set old.set
Delete the previous version files, and retain the currently used version files, if FLASH cannot accommodate two versions. If all historical version files are deleted, the system will be unable to use the backup version for protection.
2 Setting the Backup Version Boot
Set the path or file name of the backup version. Before setting, use the dir command to check whether the backup version is saved in the local device, and ensure that the file name is correct.
ZXR10(config)#nvram back-imgfile old.set
Modify the configuration if the information of the backup version needs to be modified. If the path of the backup version is deleted, the backup version files in the flash directory will be deleted directly.
ZXR10(config)#no nvram back-imgfile //old.set in the flash directory is deleted.
3 Downloading the Target Version Files through FTP
Download the target version files from the FTP server to the flash directory of the switch.
[pic] Note:
The name of the target version files saved to the flash directory must be consistent with that of the boot path.
• Copy the version file through the service port:
ZXR10# copy ftp //192.168.1.254/HMPU.set@target:target root: /flash/HMPU.set
• Copy the version file through the management port:
ZXR10# copy ftp vrf mng //192.168.1.254/HMPU.set@target:target root: /flash/HMPU.set
After downloading, use the dir command to check whether the size of version files is consistent with that on the FTP server.
ZXR10#dir
Directory of MP-0/1/0: /flash
356352 KB total (230812 KB free)
attribute size date time name
1 2048 12-09-2014 10:29 .
2 2048 12-09-2014 10:29 ..
3 2048 12-09-2014 10:31 DATA0
4 10 01-01-2010 00:00 1_1_2_0
5 2048 01-01-2010 00:00 641
6 2048 01-01-2010 00:01 syscmd_log
7 10 01-01-2010 00:00 255_1_65535_255
8 2048 01-01-2010 00:00 256
9 2048 01-01-2010 00:00 ssh
10 2048 01-01-2010 00:01 LOG
11 ---- 652740 12-09-2014 10:29 bootrom.bin
12 2048 12-10-2014 09:09 techspt
13 2048 12-09-2014 10:30 lost+found
14 ---- 59104779 07-15-2014 09:39 old.set
15 2048 01-01-2010 00:01 usrcmd_log
16 ---- 63070107 12-09-2014 10:28 HMPU.set
17 2048 01-01-2010 00:01 run_log
4 Checking the Target Version
Check whether the downloaded target version files are correct to avoid file corruption during copying.
ZXR10#check-imgfile /flash/HMPU.set
Start check the version
....................
Check the version OK.
5 Checking the Boot Mode
Check whether the boot mode is local boot.
ZXR10#show nvram-info
nvram boot-username target
nvram boot-password ******
nvram boot-server 192.168.1.254
nvram default-gateway 192.168.1.254
nvram mng-ip-address 192.168.1.150 255.255.255.0
nvram imgfile-location local flash HMPU.set //local indicates local boot while network indicates boot from the network.
nvram backup-imgfile old.set ///Set the backup startup version. The system will be automatically rolled back to the backup version two hours after the new version is initiated. In actual operations, ZTE recommends you to delete this configuration command directly.
nvram update-back-flag 0x9
If the boot mode is network, use a command to change the boot mode to local, and save the configuration.
ZXR10(config)#nvram imgfile-location local flash HMPU.set
ZXR10(config)#exit
ZXR10#write
6 Restarting the Switch
Use the reload command to restart the device, or press the power switch at the back of the device to restart it.
It takes about 5 minutes to restart the device. During the restart, pay attention to the status of indicators and output information of serial ports.
Generally, it is recommended that, during the upgrade and restart process, the log record function should be enabled to record the upgrade and restart process of the device.
[pic] Note:
If the device cannot start normally, and the reason could not be determined within 30 minutes, this upgrade is regarded to be failed. Refer to emergency handling to roll back to the previous version.
7 Checking the Boot Status of the Device
After the device starts successfully, check the status of the indicators and CPU utilization to ensure that the device is running normally.
ZXR10#show processor
================================================================================
================================================================================
M : Master CPU
S : Slave CPU
Power : Power dissipation (Watt)
CPU(5s): CPU utility measured in the last 5 seconds
CPU(1m): CPU utility measured in 1 minute
CPU(5m): CPU utility measured in 5 minutes
Peak : CPU peak utility measured in 1 minute
PhyMem : Physical memory (Megabyte)
FreeMem: Free memory (Megabyte)
Mem : Memory usage ratio
CPU threshold:80%
MEM threshold:80%
================================================================================
================================================================================
Shelf Panel CPUID Power CPU(5s) CPU(1m) CPU(5m) Peak PhyMem FreeMem Mem
================================================================================
MP(M) 0 1 0 37.1 9% 9% 8% 13% 2048 928 54.656%
--------------------------------------------------------------------------------
8 Viewing the New Version Information
Check the current version information on the device and ensure that its version number is the designated target version number.
ZXR10#show version
5950-36TM-H Software, 5900 Version: V3.00.11.B06, RELEASE SOFTWARE
Copyright (c) 2010-2020 by ZTE Corporation.
Compiled 2014-11-25, 10:00:28
System image files are:
System uptime is 0 days, 0 hours, 8 minutes
[MP(M) , shelf 0 ,panel 1]
cpu 0
Main processor : ARM MV78230 Processor
Bootrom Version : V2.03
Memory : 2042 Mbytes
System Flash : 512 Mbytes
System baud : 9600 baud
System nvram : 8 kbytes
CPUcard CPLD : N/A
CPLD1 Version : V1.00
CPLD2 Version : V1.70
Board Name : 5950-36TM-H
Board PCB : V1.00
9 Checking the Configuration Information
Use the show running-config command to view the current configuration information. Compare it with the configuration information backed up before upgrade to see whether there are any differences.
If configuration commands of the new version are changed, complete the configuration according to configuration commands that are prepared before the upgrade.
If the configuration information is long, it is recommended that Araxis merge should be used to compare the configuration information before and after the upgrade to find the differences in an effective and timely manner. For details about how to use the Araxis merge, refer to A.3 Araxis merge.
10 Verifying the Upgrade
Items to be verified after the upgrade are almost identical to those before the upgrade, including:
1. Check the operating status of hardware
Check whether the system hardware is working properly, and whether the panel indicators are in normal status after the upgrade.
2. Check the operating status of the system
Check the operating status of the system after the upgrade, and compare it with the information recorded before the upgrade to see whether it is working properly. The main check items are listed in Checking the Operating Status of the System
. Add or delete items according to the actual situation.
3. Check Services
Check the operating status of services on the device. The check items are adjusted according to specific services at the sites where the devices are to be upgraded.
The service check requires collaboration with customers, and the result is confirmed by the customers.
[pic] Note:
If the services are abnormal and caused by the device itself, but the causes could not be located within 20 minutes, the upgrade is regarded to be failed. Refer to Emergency Handling to roll back to the previous version.
At this time, the system software version does not match the POE firmware version. If the equipment needs to support the POE function, the power supply may be abnormal. After ensuring that all the non-POE services are verified to be normal, you need to upgrade the POE firmware on line. For the detailed upgrade steps, see chapter 6.
11 Deleteing the Backup Version File
After the upgrade verification operation is completed and services in the new version become normal, you need to delete the backup version file so as to pervent the system from being rolled back to the backup version after 2 hours. Please delete the nvram backup-imgfile configuration command in the operation procedures
ZXR10(config)#no nvram back-imgfile //Delete the old.set file in flash.
ZXR10(config)#exit
ZXR10#write
Building configuration...
.[OK]
Check whether the startup mode of the equipment is local, whether the backup version is deleted, and whether the upgrade rollback flag bit is 0.
ZXR10#show nvram-info
nvram boot-username target
nvram boot-password ******
nvram boot-server 192.168.1.254
nvram default-gateway 192.168.1.254
nvram mng-ip-address 192.168.1.150 255.255.255.0
nvram imgfile-location local flash HMPU.set //local indicates the upgrade in local mode.
nvram backup-imgfile //The backup version is deleted.
nvram update-back-flag 0x0
[pic] Note:
You can only perform this operation after the upgrade is completed and services are verified. Otherwise, you need to copy the old version to Flash during the rollback.
Upgrading the POE Firmware
If it is not necessary to upgrade the POE firmware, you can skip this chapter.
This chapter introduces the precautions for the upgrade, upgrade steps, and emergency troubleshooting methods.
1 Precautions
The ZXR10 5950-H switch supports upgrading the POE firmware online. The upgrade precautions are as follows:
1. Do not upgrade the POE firmware when the CPU usage is high.
2. During the online upgrade of POE, power-off is prohibited. Otherwise, the POE subcard cannot be started.
3. From software version V3.0.11 B08, online upgrade of the POE firmware is supported. Therefore, the POE firmware can be upgraded online after the software upgrade in chapter 5.
4. To implement the POE function, the POE firmware version must match the system software version. Otherwise, the POW power supply function will be invalid. If V3.00.11 has mismatched firmware version on it, the firmware version mismatch alarm will appear. Version matching rules are as follows:
◆ System software version V3.00.11————POE firmware version V3.1.11
◆ System software version V3.00.10————POE firmware version V2.0.34
5. The POE firmware upgrade operation is to update the running POE subcard.
6. After the POE firmware is upgraded through upgrade-firmware, the equipment will be restarted automatically.
7. The POE firmware upgrade must use a version file named poe.BIN. Otherwise, the upgrade will fail. After the file is copied to flash, you should rename is as poe.BIN.
2 Upgrade Flow
Figure 6-1 POE Upgrade Flowchart
[pic]
3 Upgrade Process Record
During the POE firmware upgrade, you should operate according to the upgrade procedures and record each step in the following table.
Table 6-1 Record of the POE Firmware Upgrade Process
|S/N |Procedure |Finished or Not |Execution Situation |
|1 |Copy the POE firmware file. | | |
|2 |Upgrade the POE firmware. | | |
|3 |The equipment is restarted. | | |
|4 |Verify the upgrade. | | |
4 Upgrade Procedures
1 Copying the POE Firmware Version File
Before the upgrade, you should copy the needed POE firmware version file to the flash directory of the switch.
– Use the service port to copy the POE firmware file.
ZXR10#copy ftp //192.168.1.254/poe.BIN@target:target root: /flash/poe.BIN
– Use the management port to copy the boot file.
ZXR10#copy ftp vrf mng //192.168.1.254/poe.BIN@target:target root: /flash/poe.BIN
Then check whether the poe.BIN file exists in the flash directory, as marked yellow below.
ZXR10#dir
ZXR10#dir
Directory of MP-0/T1/0: /flash
356352 KB total (230812 KB free)
attribute size date time name
1 2048 12-09-2014 10:29 .
2 2048 12-09-2014 10:29 ..
3 2048 12-09-2014 10:31 DATA0
4 10 01-01-2010 00:00 1_1_2_0
5 2048 01-01-2010 00:00 641
6 2048 01-01-2010 00:01 syscmd_log
7 10 01-01-2010 00:00 255_1_65535_255
8 2048 01-01-2010 00:00 256
9 2048 01-01-2010 00:00 ssh
10 2048 01-01-2010 00:01 LOG
11 ---- 652740 12-10-2014 09:29 bootrom.bin
12 2048 12-10-2014 09:09 techspt
13 2048 12-09-2014 10:30 lost+found
14 ---- 59104779 07-15-2014 09:39 old.set
15 2048 01-01-2010 00:01 usrcmd_log
16 ---- 63070107 12-09-2014 10:28 HMPU.set
17 2048 01-01-2010 00:01 run_log
18 ---- 32768 12-10-2014 13:29 poe.BIN
[pic] Note:
Please ensure that the name of the POE firmware version file is poe.BIN.
Then run the dir command to check whether the size of the poe.BIN file is the same as that of the file on the FTP server.
2 Upgrading the POE Firmware
Record the POE firmware version before the upgrade:
ZXR10#show poe device
Device ID : 1
PSE power threshold : 0
PSE current power : 26.9w
PSE peak-power : 27.0w
PSE max-power : 1000.0w
Over-temperature auto-recovery : disable
PSE firmware version : V2.0.34
1. Enter the poe configuration mode.
ZXR10#configure terminal
zxr10(config)#poe
zxr10 (config-poe)#
2. Upgrade the POE firmware.
zxr10 (config-poe)# upgrade-firmware poe.BIN device-id 1
.......................................... ..................
If the upgrade succeeds, the system will be restarted automatically after the dots are printed; if the upgrade fails, after the dots are printed, no errors will be returned and the system will not be restarted automatically. This indicates that the upgrade fails.
( Tip:
If the firmware fails to be upgraded, the current version provides the following types of errors:
1. Current POE firmware is the latest, so it doesn’t need to be upgraded: the pse firmware is the latest version!
2. Current board doesn’t support POE function: the board is not support POE!
3. poe.BIN doesn’t exist, or the file is damaged, please do not upgrade it until you change the file: the file poe.BIN is not exist,or has destoryed,please use a correct file!
4. Poe subcard is off position. Please insert the subcard and continue to upgrade: the POE board is not online,please confirm this!
5. Memory of the current system is not sufficient. Please release the system memory and continue to upgrade: the system memory is not enough,please free the memory and contiune this operate!
6. Current POE subcard is busy. Please perform the upgrade later: the POE board busy,please operate late!
If the POE firmware is upgraded unsuccessfully, try to solve the fault according to the error prompts above and then perform the upgrade for it again.
3 Verifying the Upgrade
After the equipment is started, please check whether the POE firmware version is updated.
ZXR10# show poe device
Device ID : 1
PSE power threshold : 0
PSE current power : 26.9w
PSE peak-power : 27.0w
PSE max-power : 1000.0w
Over-temperature auto-recovery : disable
PSE firmware version : V3.1
Version Rollback
This chapter describes specific rollback steps for different situations.
1 Rollback Application
If the upgrade fails, perform steps for version rollback. Perform different rollback steps for different failures:
• The device cannot be started properly after the new version is used.
Roll back to the previous version by booting through network. For details, refer to 6.2.
• Services are abnormal after the new version is used.
Roll back to the previous version to restart the device. For detailed steps, refer to 6.3
• The POE power supply function is abnormal after the new version is used.
Change the software version file to the old version, copy the V2.0 firmware version file and rename it as poe.BIN, and then roll back the POE firmware to the old version. For the detailed rollback procedures, see 7.4 Abnormal POE Power Supply.
[pic] Note:
If the rollback fails or an error occurs, please contact the version upgrade instructor from Customer Service Department of the Network Service Center.
2 Failure to Start the Device Normally
If the device cannot start after the new version is used, the upgrade is regarded to be failed. Perform the following steps to roll back.
1. If the backup version boot is set, and errors occur when the target version is loaded, the system will start through the backup version according to the settings in 5.4.2 Setting the Backup Version Boot.
2. If the backup version boot is not set, and errors occur when the target version is loaded, perform the following steps to roll back:
i. Turn on the power switch to restart the device.
ii. Modify the boot mode to boot through network.
The ZXR10 5950-H allows boot through network from the management port. Before that, ensure that the connection between the port and FTP server is normal.
Restart the device, press any key to enter the boot mode during the countdown period, and then modify boot parameters.
ZXR10 Switch System Bootstrap
ZXR10 36TM System BootRom Version: V1.23
Creation date: Jul 7 2014, 00:09:41
Copyright (c) 2014 by ZTE Corporation.
egiga0, egiga1, egiga2, egiga3
yaffs: Mounting /flash/
Bad block table found at page 262080, version 0x01
Bad block table found at page 262016, version 0x01
Hit any key to stop auto-boot: 0
[boot]: c
Boot Location [0:Net,1:Flash,2:USB]: 0 //0 indicates boot through network. The USB mode is not available yet.
Client IP : 192.168.1.150 // The IP address of the mng interface.
Netmask : 255.255.255.0 //The mask of a network segment.
Server IP : 192.168.1.254 //The address of the background FTP server.
Gateway IP : 192.168.1.254 //The gateway address is the interface address of port number.
FTP User : target //The FTP username is target.
FTP Password : //The password of the username target.
Bootfile : HMPU.set //The network boot path.
Enable Password : //The default value.
MAC Address : 00.d0.d0.c0.00.40
iii. Restart the Switch
Restart the device in boot mode. The system downloads the previous version from the background FTP server automatically.
[boot]: b
Boot Location [0:Net,1:Flash,2:USB]: 0
Client IP : 192.168.1.150
Netmask : 255.255.255.0
Server IP : 192.168.1.254
Gateway IP : 192.168.1.150
FTP User : target
FTP Password :
Bootfile : HMPU.set
Enable Password :
MAC Address : 00.d0.d0.c0.00.40
iv. Verify the rollback
After restarting the switch, check whether the version number is that of the previous version and whether the services are normal.
v. Copy the version to the flash directory
After ensuring that the device and services are working properly, delete the fault version during the upgrade, and copy the normal version files to the flash directory.
• Copy the version file through the service port:
ZXR10# copy ftp //192.168.1.254/HMPU.set@target:target root: /flash/HMPU.set
• Copy the version file through the management port:
ZXR10# copy ftp vrf mng //192.168.1.254/HMPU.set@target:target root: /flash/HMPU.set
vi. Modify the boot mode to local boot.
Change the boot mode from boot through network to local boot:
ZXR10(config)#nvram imgfile-location local flash HMPU.set
ZXR10(config)#exit
ZXR10#write
3 Abnormal Services
If the device is working properly but the services verified in 5.4.10 Verifying the Upgrade are abnormal after the new system software version is used, the upgrade is regarded to be failed. Perform the following steps to roll back to the old version.
1. Delete the new version files that are copied to the flash directory during the upgrade, and modify the name of the previous version file to HMPU.set.
ZXR10#delete HMPU.set
ZXR10#rename old.set HMPU.set
[pic] Note:
Due to the insufficient space of the flash directory, the previous version files are deleted before the upgrade. Recopy the previous version files to the flash directory. For details, see 5.4.2 Download the Target Version Files through FTP.
2. Use the reload command to restart the switch.
3. Verify the rollback.
After restarting the switch, check whether the version number is that of the previous version and whether the services are normal.
[pic] Note:
To ensure the stability and functions of different versions, use the matched bootrom versions during the version upgrade or degrade.
4 Abnormal POE Power Supply
If the device is started properly after the new system software version and POE firmware version are used, but the POE power supply function verified in 6.4.3 Verifying the Upgrade) is abnormal, the upgrade is regarded to be failed. Perform the following steps to roll back to the old version.
1. Delete the POE firmware version file saved in the Flash directory. Copy the V2.0 POE firmware version file correspoding to the V3.0.10 software verison to the Flash directory again.
ZXR10#delete poe.BIN
– Use the service port to copy the POE firmware file.
ZXR10#copy ftp //192.168.1.254/poe.BIN@target:target root: /flash/poe.BIN
– Use the management port to copy the boot file.
ZXR10#copy ftp vrf mng //192.168.1.254/poe.BIN@target:target root: /flash/poe.BIN
2. Delete the new version file that is copied to the flash directory during the upgrade. Then copy the old V3.00.10 version file back to the flash directory.
ZXR10#delete HMPU.set
– Use the service port to copy the POE firmware file.
ZXR10#copy ftp //192.168.1.254/HMPU.set@target:target root: /flash/HMPU.set
– Use the management port to copy the boot file.
ZXR10#copy ftp vrf mng //192.168.1.254/HMPU.set@target:target root: /flash/HMPU.set
3. Upgrade the POE firmware online to version V2.0, and then wait until the device is restarted automatically. The device loads the V3.00.10 software version and gets started.
zxr10(config)#poe
zxr10 (config-poe)# upgrade-firmware poe.BIN device-id 1
.......................................... ..................
4. Verify the rollback.
After the switch is started completely, check whether the system software version is the version before the upgrade, whether the POE firmware version is V2.0, whether the services are normal, and whether the POE power supply function is normal.
[pic] Note:
To ensure the version stability and function implementation, you should use the matching bootrom version and POE firmware version during the upgrade or degradation process.
Frequently Asked Questions
This chapter describes the frequently asked questions during the upgrade.
1. Q: What’s the point when write imgfile is used?
During write imgfile, CPU utilization may be high. In this case, do not implement sophisticated operations, nor view the content on the FLASH directory, because it will affect the writing. During the process of write imgfile, do not power off, otherwise the FLASH directory may be damaged.
2. Q: Why powering off is not recommended for restart?
A: The burst current may impair some components in the board, so the board could not start properly.
3. Q: What information needs to be collected for further analysis when errors occur?
A: Printing information on the serial port, alarming information on the device, and basic information on the device when the services become abnormal. In addition, if the device fails to start normally, pay attention to the status of the indicators on the card.
4. Q: Why a failure occurs when write-image is used?
A: write-image is a command used to save the version files simultaneously for 89E. Due to the management of platform commands, the ZXR10 5950-H still remains this command although the device does not support the master/slave boards. Therefore, an error occurs when the write-image command is used. This problem will be solved in the subsequent version. The copy command is used for the current version.
1 Usage Guideline for Common Terminal Software and FTP Software
1 Terminal Software
Common terminal software includes HyperTerminal and SecureCRT. The following items are set:
• Port attribute
• Automatic logging function
1 HyperTerminal
The HyperTerminal is usually used for the serial port connection. Perform the following steps to set it.
1. Click Start > Programs > Accessories > Communications > HyperTerminal in the operating system. The HyperTerminal main interface and Connection Description dialog box displays.
2. Type the name of the connection in Name of the Connection Description dialog box, and click OK. The Connect To dialog box displays.
3. Select the COM port in the Connect using option of the Connect To dialog box for the host to connect to the device, and click OK. The COM Properties dialog box displays.
4. Click Restore Defaults (R) in the COM Properties dialog box, modify Bits per second (B) as required, and click OK to complete the settings and enter HyperTerminal main interface.
5. If operation logs need to be recorded, click the Transfer (T) menu and select Text Capture (C). The Text Capture dialog box displays. Select log file in the dialog box and click Start to complete the settings.
2 SecureCRT
The SecureCRT is usually used for the serial port connection and telnet connection.
1. Run the SecureCRT software. The SecureCRT main interface and the connect dialog box displays.
If the connect dialog box is closed, click the first button Connect on the tool bar of the main interface or select Connect… in the File menu to open it.
2. Click the third button New Session on the tool bar of the Connect dialog box to establish a new session. The Session Options dialog box displays.
3. Set connection parameters in the Session Options dialog box:
(1) For the connection to a serial port
Name: the name of the connection
Protocol: serial
Port: COM port used for the host to connect the device
Baud rate: baud rate of the device, usually 9600 or 115200
Data bits: 8
Parity: None
Stop bits: 1
(2) For the telnet connection
Name: the name of the connection
Protocol: telnet
Hostname: IP address of the device to be connected
Port: 23
Click OK to complete the settings, and enter SecureCRT main interface.
4. If operation logs need to be recorded, click the File menu, and select Log Session. The Select Log File dialog box displays. Select the log file in the dialog box and click Save (S) to complete the settings.
2 FTP Tool
Common FTP server tools include 3CDaemon and WFTPD. The following items are set:
• FTP username and password
• Directory on the server used for storing the version files or configuration files
Other software tools share the similar configuration.
1 3CDaemon
1. Run the 3CDaemon software on the background host.
2. Open the FTP Server module on the left side, and click Configure FTP Server. The 3CDaemon Configuration dialog box displays. Perform the following steps:
(1) Type the username, such as target, in the above input box.
(2) Click Set/Change user’s password to set the password.
(3) In the input box below, type the directory, such as the IMG directory of Disk D, to save version files or configuration files, or click the button on the right side of the input box to select the directory.
(4) Select Login, Download, or Upload in the list of This user can:.
(5) Click Application (A) to complete the settings.
See Figure A-1.
AppFigure A-1 SCDaemon Window
[pic]
2 WFTPD
1. Run the wftpd software on the background host.
2. Click Security on the menu, and select User/Rights…. The User/Rights Security Dialog dialog box displays. Perform the following steps:
(1) Click New User... to create a user, such as ztezte, and set a password.
(2) Select the user name ztezte in the User Name drop-down box.
(3) Type a directory in the Home Directory box, such as the IMG directory of Disk D, to save version files and configuration files.
3. Click Done to complete the settings.
See Figure A-2.
AppFigure A-1 WFTPD Window
[pic]
3 Araxis merge
The Araxis merge is a file comparison tool. During the version upgrade, it is usually used to compare configurations before and after the upgrade.
The Araxis merge is very easy to use.
1. Run the Araxis merge software. The main interface displays. An input box saying “You can type a filename here” is displayed on both left and right side of the main interface.
2. Click the button ... on the right side of each input box respectively, and select two files that need to be compared. The selected files are displayed on both sides of the main interface, and the different places are clearly marked.
See Figure A-3.
AppFigure A-3 Araxis merge Window
[pic]
4 EasyManager
The EasyManager is a green simple mini NM tool developed for IP products, and is applicable to various maintenance scenarios such as product commissioning, upgrade, preventive maintenance, and information collection. The EasyManager, also referred to as the EM, supports free installation, product version configuration backup, version upgrade of a single device, and version upgrade of bulk devices.
To download the EM, manuals, and guidance videos, and apply for an EM license, go to the serviceability achievement release platform
[pic][pic]
................
................
In order to avoid copyright disputes, this page is only a partial summary.
To fulfill the demand for quickly locating and searching documents.
It is intelligent file search solution for home and business.