Académique Documents
Professionnel Documents
Culture Documents
Issue 01
Date 2018-01-15
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and feat ures are stipulated by the contract made bet ween Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchas e scope or the usage scope. Unless otherwis e specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. E very effort has been made in the
preparation of this document to ensure accuracy of the contents , but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: support@huawei.com
Overview
This document guides you through the upgrade, rollback, and troubleshooting procedures for
OptiX 155/622H(Metro 1000) STM-1/STM-4/STM-16 MSTP Optical Transmission System
V300R005C01SPH307.
Intended Audience
This document is intended for engineers who:
Understand how involved network elements (NEs) are networked and what versions they
are.
Have equipment maintenance experience and skills.
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Change History
Issue Date Author Description
Contents
7 FAQs .............................................................................................................................................. 29
7.1 A Hot Patch Fails to Be Loaded to an NE. Why?.......................................................................................................29
7.2 When a Board-Level Hot Patch Is Being Loaded to an NE, the DC Displays a Message Indicating that a Hot
Patch of the Same or Later Version Has Been Loaded to the NE. Why?......................................................................29
Load
Activate
Delete
Delete
Running Activated
Confirm
System
reset
Idle The patch data has not been loaded to the patch area.
Deactivated The patch data has been loaded to the patch area, but has not taken
effect.
Activated The patch has taken effect and is in the trial running state. If the system
is reset at this time, the patch automatically changes to the deactivated
state after the reset.
Running The patch has taken effect and is in the formal running state. If the
system is reset at this time, the patch remains in the running state after
the reset.
1.1.3 Method for Checking Whether the SCC Board Supports Hot
Patches
NOTE
The hot patch can be used only for an upgrade, and cannot be used for a downgrade. If the hot patch
already exists on the NE, loading the hot patch again to the NE fails.
Use the following method to check whether the system control and communication (SCC)
board supports hot patches:
Issue the :patch-get-area:bid; command to the SCC board to query the patch area
information. If an error is returned, the SCC board does not support hot patches.
If the SCC board in slot 11 does not support hot patches, a timeout error is returned.
:patch-get-area:11
failed! cmd:0x040e error:0x0080 CMD_EXECUTE_TIMEOUT
If the SCC board in slot 2 supports hot patches, the following information is displayed:
:patch-get-area:11
PATCH-AREA-INFO
PatchAreaAddr PatchAreaLen CodeAddr CodeLen CodeFreeLen DataAddr
DataLen DataFreeLen
0x00010000 0x000f0000 0x00010000 0x00078000 0x00075054 0x00088000
0x00078000 0x00077018
Total records :1
NOTE
The OptiX M etro 1000 V300R005C01 supports only board-level hot patches.
V300R005C01SPC302 V300R005C01SPH307
1.4 Precautions
None.
Start
Fail
Load the hot patch.
Succeed
Fail
Verify the upgrade Roll back to the source version
Succeed
End
Time required varies according to the particulars for the site (such as onsite data volume and server
performance).
The "Expected Result" column is completed by onsite engineers.
Precautions
None
Procedure
Run the following command to query the NE software and FPGA versions:
:ver;
Verification
The NE software version is 5.37.05.15P02.
Precautions
None
Procedure
Step 1 Run the following command to check the running status of the NE:
:cfg-get-nestate;
:cfg-get-lmspg
:cfg-get-lmsattrib:PgId;
:cfg-get-lmsbdmap:PgId;
:cfg-get-lmsstate:PgId;
This step uses linear multiplex section protection (MSP) as an example. Other protection
schemes, such as subnetwork connection protection (SNCP), also need to be checked.
Step 4 Run the following command to check the reset records of the SCC board:
:errlog;
Step 5 Run the following commands to check the configuration and the in-service state of logical
boards:
:cfg-get-board;
:cfg-get-phybd;
Step 6 Run the following commands to check the ECC routes of the NE:
:cm-get-eccroute;
:cm-get-maccon;
:cm-get-coreroute;
Step 8 If data in the databases is not consistent, run the following commands to synchronize data in
the databases:
:dbms-copy-all:mdb,drdb;
:dbms-copy-all:drdb,fdb0;
:dbms-copy-all:drdb,fdb1;
:time
:sftm-get-fpatrol-state:bid
:sftm-set-fpatrol:bid,VERCHECK,STOP
:sftm-set-fpatrol:bid,FILEPATROL,STOP
:sftm-set-fpatrol:bid,ASVERCHECK,STOP
NOTE
Replace bid in the preceding commands with 11, the slot ID of the SCC board.
----End
Verification
The basic NE information is correct, and no abnormal alarm is generated.
Step 2 In the navigation tree, right-click the NE to which the hot patch is to be loaded, and choose
Login NE from the shortcut menu.
Step 3 After logging in to the NE, right-click the NE and choose Query Board from the shortcut
menu.
Select 11-scc in the board list that is displayed. Click the red double-arrow button to select the
SCC board to which the hot patch is to be loaded.
Step 4 Click .
The Choose File dialog box is displayed.
Select the hot patch file fpatch.pat, and click Open.
----End
After loading the hot patch is complete, the DC displays the message "Load Software
Completed!"
----End
After activating the hot patch is complete, the DC displays the message "Activating software
completed!"
After committing the hot patch is complete, the DC displays the message "Commit
completed!"
NOTE
After you click Finish, the hot patch is committed and enters the running state. In this case, you cannot
roll back to the source version by using the DC. Instead, you can delete the hot patch by using the
command tool for a rollback.
:patch-get-statemsg:11
PATCH-STATE
ProgVer PatchVer TotalPatchNum
RunPatchNum ActivePatchNum DeactivePatchNum CommPatchNum TempPatchNum
5.37.05.15P02T05 SPH002 2 2
0 0 2 0
Total records :1
----End
4 Checking the NE performance All performance data can be correctly reported, and the
performance values do not experience any abnormal changes
during the upgrade.
11 Checking the NE software version The U2000 version meets the lowest requirement specified in
and the U2000 version the version mapping table.
Procedure
Step 1 Run the following command to check the running status of the NE:
:cfg-get-nestate
Step 2 Run the following command to check the NE software and FPGA versions:
:sftm-get-nesoftver:bid
:per-set-monevent:0,0,0,0,perall,15m,enable ;
:per-get-curdata:0,0,0,0,perall,15m;
Step 5 Run the following command to check the SCC board reset records:
:errlog
Step 6 Run the following command to check whether any abnormal alarms are generated on boards
on the NE:
:alm-get-curdata:0,0
Step 7 Run the following commands to check the ECC routes of the NE:
:cm-get-newbdinfo
:cm-get-eccroute
Step 8 Run the following command to check the status of the MS protocol:
:cfg-get-lmsstate:PgId
Step 10 Run the following commands to check the automatic backup of databases:
:dbms-get-autobackup
:dbms-get-backuptime
:dbms-get-backupperiod
Step 11 Check whether the NE software version matches the U2000 version.
Step 12 Run the following commands to enable periodic file check on the SCC board:
:sftm-set-fpatrol:bid,VERCHECK,START
:sftm-set-fpatrol:bid,FILEPATROL,START
:sftm-set-fpatrol:bid,ASVERCHECK,START
NOTE
Replace bid in the preceding commands with 11, the slot ID of the SCC board.
Expected Results
See Table 5-1.
Start
End
Click Yes.
The system rolls back to the source version.
After clicking Finish to commit the hot patch, you can only delete the hot patch by using the
command tool for a rollback.
Step 1 On the command tool, run the :patch-get-info:bid and :patch-get-statemsg:bid commands to
check whether the hot patch exists on the SCC board.
:patch-get-info:11
PATCH-UNIT-INFO
PatchNo PatchState CodeAddr CodeLen DataAddr DataLen FuncNum
20001 running 0x00010000 0x00002580 0x00088000 0x000002b8 8
20002 running 0x00012580 0x00000a2c 0x000882b8 0x00000d30 1
Total records :2
:patch-get-statemsg:11
PATCH-STATE
ProgVer PatchVer TotalPatchNum
RunPatchNum ActivePatchNum DeactivePatchNum CommPatchNum TempPatchNum
5.37.05.15P02T05 SPH002 2 2
0 0 2 0
Total records :1
Step 2 If the hot patch exists on the SCC board, run the :patch-delete:bid,0 command to delete the
hot patch.
Step 3 Run the :patch-get-info:bid and :patch-get-statemsg:bid commands to check whether the
hot patch has been deleted.
:patch-get-info:11
failed! cmd:0x0406 error:0x9da5 NSERR_PATCH_NULL
:patch-get-statemsg:11
PATCH-STATE
5.37.05.15P02T05 0 0
0 0 0 0
Total records :1
Step 4 After deleting the hot patch, run the :reset command to perform a warm reset on the SCC
board.
----End
7 FAQs
A Upgrade Record
Pre-upgrade Checklist
Upgrade Checklist
Verification Checklist
D
DC Data Center
E
ECC embedded control channel
F
FTP File Transfer Protocol
G
GNE gateway network element
M
MS multiplex section
MSP multiplex section protection
N
NE network element
S
SCC system control and communication
SFTP Secure File Transfer Protocol
SNCP subnetwork connection protection
T
TFTP Trivial File Transfer Protocol