Optix NG-SDH v100r010c03spc203 Upgrade Guide

OptiX NG-SDH
Upgrade Guide_Simulation
Package Diffusion Method
(DataCenter for U2000
V100R005C00)

Issue 01
Date 2012-10-30

HUAWEI TECHNOLOGIES CO., LTD.

Issue 01 (2012-10-30) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd
i

Copyright Huawei Technologies Co., Ltd. 2012. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technol ogies Co., Ltd.
All other trademarks and trade names menti oned in this document are the property of thei r respecti ve
holders.

Notice
The purchased products, services and features 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 purchase scope or the usage scope. Unless otherwise specifi ed in the contract, all statements,
informati on, 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. Every 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.

Huawei Technologies Co., Ltd.
Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
Peopl e's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com

OptiX NG-SDH
Upgrade Guide_Simulat ion Package Diffusion Method
(DataCenter for U2000 V100R005C00) About This Document

ii

About This Document
Intended Audience
This document is intended for:
Technical support engineers
Maintenance engineers
Change History
Updates in Issue 01 (2012-10-30)
This document is the initial release.
OptiX NG-SDH
(DataCenter for U2000 V100R005C00) Contents

iii

Contents
About This Document.................................................................................................................... ii
1 Upgrade Methods.......................................................................................................................... 1
1.1 Package Diffusion..............................................................................................................................................................1
1.2 Upgrade Path ......................................................................................................................................................................1
1.3 Usage Instructions .............................................................................................................................................................2
2 Impact of the Upgrade.................................................................................................................. 3
2.1 Impact on the Existing System During the Upgrade ...................................................................................................3
2.2 Impact on the Existing System After the Upgrade .......................................................................................................3
3 Upgrade Process ............................................................................................................................ 4
3.1 Upgrade Flowchart ............................................................................................................................................................4
3.2 Upgrade Procedure ............................................................................................................................................................4
4 Preparations for the Upgrade...................................................................................................... 6
4.1 Environment Preparations ................................................................................................................................................6
4.1.1 Arranging for the Upgrade Tool ............................................................................................................................6
4.1.2 Obtaining the Reference Documents....................................................................................................................7
4.1.3 Obtaining the Required Software .........................................................................................................................9
4.1.4 Confirming Service Protection Schemes .............................................................................................................9
4.1.5 Saving the Service Configuration .......................................................................................................................10
4.1.6 (Optional)Adding NEs..........................................................................................................................................11
4.1.7 (Optional)Deleting NEs ........................................................................................................................................21
4.1.8 Setting the NMS to the Non-Interrupt Mode ....................................................................................................23
4.2 Pre-upgrade Checklist .....................................................................................................................................................24
4.2.1 Checking the NMS Version .................................................................................................................................25
4.2.2 Checking the Consistency Between the Data on the NMS and the Data on the NE..................................26
4.2.3 Checking the Board Software Version Informat ion About the NE ...............................................................28
4.2.4 Checking Whether the Logical Boards of All Physical Boards Are Added ................................................29
4.2.5 Checking the Health State of the NE .................................................................................................................29
4.2.6 Checking the Running Status of the NE ............................................................................................................29
4.2.7 Checking the ECC Status of the NE...................................................................................................................32
4.2.8 Testing the Memory of the SSN1GSCC Board ................................................................................................33
4.2.9 Checking the Logical Port Types of SSN1SLQ1 Boards and SSN1SL1 Boards .......................................34
OptiX NG-SDH
(DataCenter for U2000 V100R005C00) Contents

iv

4.2.10 Operat ing on ASON Services............................................................................................................................35
4.2.11 Backing Up the NE Database ............................................................................................................................41
4.2.12 Checking Software Package Versions..............................................................................................................42
4.2.13 Checking the Preparations for an Upgrade .....................................................................................................43
5 Upgrade Operations ................................................................................................................... 45
5.1 Package Diffusion............................................................................................................................................................45
5.1.1 Creat ing a Package Diffusion Task.....................................................................................................................45
5.1.2 Running a Package Diffusion Task.....................................................................................................................55
6 Version Rollback......................................................................................................................... 58
6.1 Precautions ........................................................................................................................................................................58
6.2 Rollback Process ..............................................................................................................................................................58
6.3 Procedures of an NE-Level Soft ware Rollback..........................................................................................................59
6.3.1 Rollback During Package Diffusion...................................................................................................................59
6.4 Procedures of a Board-Level Software Rollback .......................................................................................................60
6.5 Verification of a Version Rollback ................................................................................................................................60
7 Upgrade Verification .................................................................................................................. 62
7.1 Verification Checklist ......................................................................................................................................................62
7.2 Verification Procedures ...................................................................................................................................................62
8 Exception Handling .................................................................................................................... 64
8.1 Handling the Isolated Boards.........................................................................................................................................64
8.2 Boards That Does Not Support Package Diffusion....................................................................................................65
9 Associated Tasks and Reference Information ....................................................................... 66
9.1 Recovering the Database of an NE ...............................................................................................................................66
A Upgrade Records ........................................................................................................................ 70
B Glossary........................................................................................................................................ 71
C Acronyms and Abbreviations .................................................................................................. 74

OptiX NG-SDH
(DataCenter for U2000 V100R005C00) 1 Upgrade Methods

1

1 Upgrade Methods
1.1 Package Diffusion
Package diffusion is a network-level software upgrade method and needs to be performed
based on package loading. After package loading is completed on one NE, the NE
automatically diffuses the software package by running the inter-NE communication protocol
to all other NEs to be upgraded on the network. Then, the NEs load the software onto their
boards as required.
The software package applicable in package loading is a virtual package. Instead of packing
the software into one file, the software package collects all the software required by the NE
such as the NE software, board software, FPGA files, and extended BIOS. With the software
package description file, the software package functions as a logical package of the required
software. Then, with the aid of tools, the package loading can be implemented.
The package diffusion method has the following major features:
Package diffusion is a network-level software upgrade method.
Package diffusion spreads the software package according to the network-level topology.
The NEs that load the diffused software package are activated in groups.
The upgrade is highly efficient.
Activation by NE groups is applicable to package diffusion. The boards of different NEs on
the network can be activated at the same time, if the activation operation is unlikely to cause
any problem. According to the network configuration, the DC and NEs create default NE
groups for activation. You may change the groups. For details, see Configuring activation
groups in section 5.1.1 "Creating a Package Diffusion Task."
1.2 Upgrade Path
Source Version Target Version Upgrade Method
OptiX NG-SDH
V100R010C02
OptiX NG-SDH
V100R010C03SPC203
Package diffusion
OptiX NG-SDH
V100R010C02SPC100
OptiX NG-SDH
V100R010C03SPC203
Package diffusion
OptiX NG-SDH
(DataCenter for U2000 V100R005C00) 1 Upgrade Methods

2

Source Version Target Version Upgrade Method
OptiX NG-SDH
V100R010C03
OptiX NG-SDH
V100R010C03SPC203
Package diffusion
OptiX NG-SDH
V100R010C03SPC100
OptiX NG-SDH
V100R010C03SPC203
Package diffusion
OptiX NG-SDH
V100R010C03SPC200
OptiX NG-SDH
V100R010C03SPC203
Package diffusion

1.3 Usage Instructions
This section provides usage instructions for the package diffusion.

For instructions on an upgrade of ASON software, see the OptiX GCP Software Upgrade Guide. This
document can be downloaded from the following path at http://support.huawei.com:
Product catalog > Optical Network > NG SDH > OptiX GCP > Technical Guides > Upgrade Guide
During an upgrade on the existing network, check the service protection configuration
and inter-NE communication status when you reset the SCC board and other boards.
In the process of an upgrade or downgrade, do not insert or remove any board, or power
off the NE.
The package diffusion method cannot be used for a downgrade. Therefore, ensure that
the target version is later than the source version when performing a package diffusion
task.
It is recommended that you save the package for simulation package loading in the root
directory and do not name the folder for the package too long. When you load the
package through FTP, the loading fails if the directory title (including the folder name)
has more than 59 characters.
After an SSN5EFS0/SSN3EFS4/SSN1EMS2/SSN3EGS2/SSN1EFS0A board is
upgraded from a version earlier than 2.33 to 2.33 or later versions, the board needs to be
reset (cold) manually. If the cold reset is not performed, buffer on ports of the board
remains the value before the upgrade.
OptiX NG-SDH
(DataCenter for U2000 V100R005C00) 2 Impact of the Upgrade

3

2 Impact of the Upgrade
2.1 Impact on the Existing System During the Upgrade
The possible impacts on the existing system during an upgrade are as follows.
Impact on Services
After the upgrade of the board software, the board should be reset (warm) so that the new
board software functions. After the upgrade of the FPGA, the board should be reset (cold) so
that the new FPGA functions. Cold reset of a service board interrupts services for less than 10
minutes if the board is not configured with any board-level protection scheme (such as TPS,
BPS, DPS, PPS, and DLAG).
Impact on the Network Communication
After the NE software is activated during upgrade, the NE software is reset and then the new
NE software functions. In the reset process, the communication between the NMS and the NE
is interrupted for less than 10 minutes. During the interruption period, the NMS cannot
monitor the alarms and performance events on the NE.
Impact on the NMS
None.
Impact on Databases
Databases can be upgraded smoothly.
Impact on Reporting Alarms
None.
2.2 Impact on the Existing System After the Upgrade
Alarm Reporting
None.
OptiX NG-SDH
(DataCenter for U2000 V100R005C00) 3 Upgrade Process

4

3 Upgrade Process
3.1 Upgrade Flowchart
This section provides an upgrade flowchart.
Figure 3-1 Upgrade flowchart
Start
Prepare for an upgrade
task
End
Perform the upgrade task
Verify whether the upgrade
task is successful
Verify whether the upgrade is
successful
Roll back the
software version
Yes
Yes
Yes
No
No
No

3.2 Upgrade Procedure
This section provides an upgrade procedure table.
OptiX NG-SDH
(DataCenter for U2000 V100R005C00) 3 Upgrade Process

5

Table 3-1 Upgrade procedure
Step Impact Duration Mandatory
or Optional
Preparatio
ns for the
upgrade
Environment
preparations
None. 20 minutes. Mandatory
Pre-upgrade
check
None. 15 minutes. Mandatory
Package
diffusion
Creating a
package
diffusion task
None. Depends on the
network scale.
Generally, one
hour is required for
50 NEs.
Mandatory
Diffusing and
activating a
software
package
When you upgrade a
line board or a data
processing board, a
cold reset is
performed on the
board and interrupts
services if the board
is loaded with an
FPGA file. If
board-level
protection is
configured on the
board, you need to
perform protection
switching before
performing a cold
reset on the board.
During the
protection
switching, the
services are
interrupted for a
period less than 50
ms, which does not
affect the services.
Depends on the
network scale.
Generally, 7 hours
is required for 100
NEs.
Mandatory
Upgrade verification None. 10 minutes. Mandatory
Version rollback During a version
rollback, a cold reset
may be performed
for boards, affecting
services.
Depends on the
network scale.
Generally, 2 hours
is required.
Optional

OptiX NG-SDH
(DataCenter for U2000 V100R005C00) 4 Preparations for the Upgrade

6

4 Preparations for the Upgrade
4.1 Environment Preparations
This section describes how to prepare the upgrade tools and reference documents, how to
configure protection schemes of services and upgrade tasks on the NMS, how to save the
service configuration, how to add and delete an NE, and how to set the file transfer service
root directory.
4.1.1 Arranging for the Upgrade Tool
This topic describes the tools required for an upgrade.
Precautions
Make sure that the NMS version is U2000 V100R005C00 (with the DC) or later.
Make sure that the Navigator version is 6.2 or later.
Make sure that the user who performs an upgrade is a super user and is authorized to use
the DC.
Procedure
Step 1 Prepare a number of standard network cables.
Step 2 Prepare a PC.

Set the IP address of the PC. Ensure that the IP address of the PC and the IP address of the
GNE are different values on the same network segment. In addition, the IP address of the PC
must be different from the IP addresses of the NEs affiliated to the GNE.
Step 3 Prepare the NMS and make sure that the NMS version is U2000 V100R005C00 (with the
Data Center) or later. You may download the NMS from the following path at
http://support.huawei.com: Software Center > Version Software > Network
OSS&Service > iManager U2000 > iManager U2000-DC.
OptiX NG-SDH

7

Step 4 Prepare the Navigator of version 6.2 or later. You may download the Navigator from the
following path at http://support.huawei.com: Software Center > Version Software >
Optical Network Product Line > Optical Network Tools > Navigator. Query the
Navigator version as shown in the following figure. The Navigator can be used for
downgrading SCC board software on site or remotely.

The query result of the Navigator version is as follows.

Step 5 Prepare other upgrade tools such as jumper caps required for board jumpers.
----End
Result
All the required tools are available.
Postrequisite
None.
4.1.2 Obtaining the Reference Documents
This topic describes how to obtain the reference documents for an upgrade.
Precautions
None.
Procedure
Step 1 Obtain OptiX NG-SDH Upgrade Guide_Simulation Package Loading Method (DataCenter
for U2000 V100R005C00) from the following paths at http://support.huawei.com:
OptiX NG-SDH

8

a. Choose Product catalog > Optical Network > NG SDH, enter the documentation name
in the Search dialog box, and click Search.

b. Choose Product catalog > Optical Network > NG SDH > OptiX OSN 7500 >
Technical Guides > Upgrade Guide, and download the related document.
Step 2 Obtain the OptiX NG-SDH Product Upgrade FAQ - 20080527-B from the following paths at
http://support.huawei.com.
a. See method 1 in step 1.
Step 3 Obtain the Patch Release Notes from the following path at
http://support.huawei.com: Software Center > Version Software > OptiX Network Product
Line > NG SDH > OptiX OSN 7500 > V100R010C03SPC203 > V100R010C03SPC203
Release Documents. Download the desired version and obtain the patch release notes under
the 02-Release Notes directory. OptiX OSN 7500 is taken as an example.
Step 4 Obtain the Summary of Upgrade Methods for the OptiX NG-SDH Product - 20110505-B from
the following path at http://support.huawei.com:
Step 5 Obtain the OptiX OSN 3500 SSN1GSCC's Memory Testing Guide 20080305-A from the
following paths at http://support.huawei.com.
Technical Guides > Reconstruction Guide, and download the related document.
Step 6 Obtain the Operation Guide to Clearing Software Packages on the OptiX OSN
Equipment20090417-B from the following paths at http://support.huawei.com.
Step 7 Obtain the OptiX NG-SDH Product Downgrade Guide (Toolkit)-20090904-B from the
following paths at http://support.huawei.com.
OptiX NG-SDH

9

Step 8 Obtain the OptiX NG-SDH Product Downgrade Guide - 20091202-B from the following
paths at http://support.huawei.com.
Step 9 Obtain the OptiX NG-SDH Product Upgrade Guide (Toolkit V100R004)-20101022-B from
the following paths at http://support.huawei.com.
----End
Result
All the reference files are obtained.
Postrequisite
None.
4.1.3 Obtaining the Required Software
This topic describes how to obtain the software for an upgrade, including the software
package of the target version.
Precautions
The software required for an upgrade can be downloaded from the following path at
http://support.huawei.com: Software Center > Optical Network Product Line > NG SDH.
Procedure
Verify that the software package to be loaded is of the target version and is applicable to the
NE to be upgraded.
Result
All the software required for an upgrade is obtained.
Postrequisite
None.
4.1.4 Confirming Service Protection Schemes
Before performing an upgrade, you need to confirm the protection schemes on the network
and determine whether the existing services are well protected. Field engineers need to work
out a specific service protection scheme based on the actual customer network.
OptiX NG-SDH

10

Precautions
On an NE configured with only one cross-connect board, when a cold reset is performed
for the cross-connect board, a cold reset is automatically performed for all the service
boards. As a result, services are interrupted. To address this problem, use a spare
cross-connect board during the upgrade, or inform the customer of the problem in
advance.
If the boards are configured with DPS and LMS, or DPS and RMS, see the OptiX
NG-SDH Product Upgrade FAQ-20080527-B. Obtain the document according to section
4.1.2 "Obtaining the Reference Documents."
If an FPGA file is loaded to a board, a cold reset is performed for the board during
activation and service interruption may occur. Inform the customer of the possible
service interruption in advance.
Procedure
Formulate a service protection scheme based on actual conditions.
Result
None.
Postrequisite
None.
4.1.5 Saving the Service Configuration
Before upgrading an NE, ensure that the NE is running normally and upload the service
configuration on the NE to NM databases by using the NMS.
Precautions
None.
Procedure
Step 1 Log in to the NMS as a user with the "system maintenance" authority or higher.
Step 2 Choose Configuration > NE Configuration Data Management from the Main Menu.
Step 3 In the NE list on the left, select the NE to be upgraded and click .
Step 4 Select the NE to be upgraded from Configuration Data Management List.
Step 5 Click Upload, or right-click the NE and choose Upload from the shortcut menu.
Step 6 Click OK in the Confirm dialog box.
Step 7 After the service configuration is uploaded, the Operation Result dialog box is displayed.
Click Details to check whether the operation is successful. If yes, click Close. If not, check
the causes according to the prompt in the dialog box. After rectifying the fault, repeat the
preceding steps to save the service configuration.
----End
OptiX NG-SDH

11

Result
The service configuration is saved successfully.
Postrequisite
None.
4.1.6 (Optional)Adding NEs
Before using the independently installed DC to load a software package, you need to add NEs
manually. The version of the independently installed DC is V100R005C00.
Precautions
To add an NE, you can select either of the two methods: Add NE and Search NE.
You can search for two types of NEs by using the Search NE method:
Gateway NEs
Non-gateway NEs
Only after a gateway NE is discovered, you can search for the non-gateway NEs that the
gateway NE manages.
If you display the NE Software Management on the NMS, NEs are automatically added
to NE View. Therefore, you do not need to add NEs manually.
In the case of the NE Software Management, the OptiX NG-SDH 1500A and OptiX
NG-SDH 1500B are considered as one type of equipment, namely, the OptiX NG-SDH
1500. This does not affect package loading.
After the DC starts and the Select Domain is displayed, select Transmission/PTN and
click OK.

The NE Software Management interface is displayed. If the File Transfer Service
Status dialog box is displayed, click OK.
OptiX NG-SDH

12

Procedure
Scenario 1: Adding NEs
Step 1 Start NE Software Management. By default, OptiX/PTN NE View is displayed.

Step 2 Click NE Explorer, and select Create NE from the drop-down menu. Then, the Create NE(s)
window is displayed.

OptiX NG-SDH

13

Step 3 In the Create NE(s) window, select the values of Protocol Type and Gateway Type. In
addition, set Extended ID, NE ID, Resource Name, NE IP/LAN Gateway IP, Port, User
Name, and Password. The default values of Port, User Name, and Password are 1400, szhw,
and nesoft respectively.

Click Create NE.
Step 4 After NEs are added, the Create NE(s) dialog box indicates that the operation is successful.

Step 5 Click Close to close the dialog box. In OptiX/PTN NE View, the added devices are
displayed.
OptiX NG-SDH

14

Scenario 2: Searching for GNEs
Step 1 Start NE Software Management. By default, OptiX/PTN NE View is displayed.

Step 2 Click NE Explorer, and select Search NE(s) from the drop-down menu. Then, the Search
NE(s) window is displayed.
OptiX NG-SDH

15

Step 3 In Search NE(s), click Search Gateway.

Step 4 The Search Gateway NE(s) dialog box is displayed, indicating the process of searching for
GNEs. After the operation is completed, click Details. Then, the discovered GNEs are
displayed by Gateway Type and Gateway Address.
OptiX NG-SDH

16

Click Close to close the dialog box.
Step 5 After the device search is successful, the Search NE(s) window is as follows:

Select the required gateway NE. Click Add Gateway, the Add Gateway window is
displayed.
Step 6 In the Add Gateway window, enter correct values in Port, User Name, and Password. The
default values are 1400, szhw, and nesoft. Select Create the NE.
OptiX NG-SDH

17

Click OK.
Step 7 In the Adding NE(s) dialog box, click Details after the operation is completed. Operation
Result is Operation succeeded.

Click Close to close the prompt dialog box.
Step 8 Repeat Step 5 to add more GNEs. Otherwise, click Close.
OptiX NG-SDH

18

Scenario 3: Searching for non-gateway NEs
Step 1 In Search NE(s), click the desired GNE.

Click Search Non-Gateway.
Step 2 In the Search Non Gateway NE(s) dialog box, click Details after the operation is completed.
The discovered non-gateway NEs are displayed.
OptiX NG-SDH

19

Select the required non-gateway NEs and click Add NE To DC.
Step 3 In the Add NE To DC dialog box, enter correct values in NE Name, Port, User Name, and
Password. The default values of Port, User Name, and Password are 1400, szhw, and
nesoft respectively.

Click OK.
Step 4 In the Adding NE(s) dialog box, click Details after the operation is completed. Operation
Result is Operation succeeded.
OptiX NG-SDH

20

Click Close.
Step 5 Repeat Step 2 to add more non-gateway NEs. Otherwise, click Close.

Step 6 In the Search NE(s) dialog box, click Close.
OptiX NG-SDH

21

Result
The added NEs are listed in the device view.
Postrequisite
None.
4.1.7 (Optional)Deleting NEs
After using the independently installed DC to load a software package, you need to delete
NEs manually.
Precautions
None.
Procedure
Step 1 Start the NE Software Management and OptiX/PTN NE View is displayed.
OptiX NG-SDH

22

Step 2 Select the required NE. Click NE Explorer and select Delete NE(s).

The Operation Confirmation dialog box is displayed.
Step 3 Click Yes. The Deleting NE(s) dialog box is displayed.

Step 4 Click Details. Operation Result is Operation succeeded.
OptiX NG-SDH

23

Step 5 Click Close.
----End
Result
After the operation is completed, the deleted NE is not listed in OptiX/PTN NE View.

Postrequisite
None.
4.1.8 Setting the NMS to the Non-Interrupt Mode
To achieve a smooth upgrade, you need to set the NMS to the non-interrupt mode before an
upgrade.
OptiX NG-SDH

24

Precautions
After an upgrade is completed, you need to set the NMS to the default mode.
Procedure
Step 1 Query the values of the download interruption mode flags IsInterruptMode and
IsMSTPInterruptMode in server > conf > trans_ems.cfg. If the values are not 0, change
them to 0. In this manner, the NMS is set to the non-interrupt mode. The default value of
IsInterruptMode is 1 and the default value of IsMSTPInterruptMode is 0.
Step 2 Shut down and restart the server and client of the NMS.
----End
Result
The NMS is set to the non-interrupt mode.
Postrequisite
None.
4.2 Pre-upgrade Checklist
Before an upgrade, you need to check the conditions of the equipment and network.
Table 4-1 lists the pre-upgrade check items.
Table 4-1 Pre-upgrade check
Item Check Criteria
Checking the current version of the NMS The version must be consistent with the
version mapping table.
Checking the version of the obtained
software
The version must be consistent with the
target version.
Checking whether the logical boards of all
physical boards are added
No alarms indicate that board types
mismatch or logical boards are not added.
Checking the consistency of the data on the
NMS and the data on the NE
The data on the NMS must be consistent
with the data on the NE.
Checking the detailed version information
about the NE
The version information about each board on
the NE must be consistent with the upgrade
requirements.
Checking the running status of the NE The NE basic information must be correct
and there must be no abnormal alarms.
OptiX NG-SDH

25

Item Check Criteria
Checking the status of the ECC
communication on the NE
The ECC protocol must be disabled at the
optical interface that does not use the ECC
communication. In this manner, the NE can
be reachable to the NMS even when the
resources are insufficient.
Testing the memory of the SSN1GSCC
board
The SSN1GSCC board has no memory
problem.
Checking the logical port types of
SSN1SLQ1 boards and SSN1SL1 boards
The logical ports of SSN1SLQ1 boards and
SSN1SL1 boards are optical ports.
Checking the preparations for the upgrade The preparations must be complete and
correct.

Print and fill in the form attached in "A Upgrade Records."
4.2.1 Checking the NMS Version
Before an upgrade, you need to check whether the current NMS version is consistent with
NMS version specified in the release notes.
Precautions
None.
Procedure
Step 1 Choose Help > About from the Main Menu. The About dialog box is displayed.

Step 2 In the About dialog box, you can see the NMS version.
OptiX NG-SDH

26

----End
Result
The NMS version is consistent with the version mapping table.
Postrequisite
None.
4.2.2 Checking the Consistency Between the Data on the NMS
and the Data on the NE
Check whether the data on the NMS is consistent with the data on the NE.
Precautions
None.
Procedure
Step 1 Log in to the NMS by using a user with the "network maintenance engineer" authority or
higher.
Step 2 Choose Configuration > NE Configuration Data Management from the Main Menu.
OptiX NG-SDH

27

Step 3 On the NE list in the left pane, select the NE to be upgrade, and click .
Step 4 On the Configuration Data Management List tab, select the NE to be upgraded.
Step 5 Click Consistency Check.
Step 6 In the Confirm dialog box that is displayed, click OK.

Step 7 After the consistency check is performed, the Operation Result dialog box is displayed,
indicating whether the operation is successful. If the operation is partially successful, click
Details to obtain more information. If the operation is successful, click Close.

If the data on the NMS is not consistent with the data on the NE, upload the data from the NE to the
NMS.
----End
Result
Data on the NMS and data on the NE are consistent.
OptiX NG-SDH

28

Postrequisite
None.
4.2.3 Checking the Board Software Version Information About
the NE
Before an upgrade, check whether all the board software versions are correct.
Precautions
None.
Procedure
Step 1 Click Administration > NE Software Management > NE Data Backup/Restoration in the
Data Center.
Step 2 Click the Board Information tab, then click Query and wait for the display of the board
information.

----End
Result
All board software versions are consistent with the version information specified in the
release notes.
Postrequisite
None.
OptiX NG-SDH

29

4.2.4 Checking Whether the Logical Boards of All Physical Boards
Are Added
Before an upgrade, ensure that the logical boards of all physical boards are added.
Precautions
None.
Procedure
Check the alarms on each NE. Choose Fault > Browse Current Alarm from the Main Menu.
Result
The BD_NOT_INSTALLED and WRG_BD_TYPE alarms are not reported.
Postrequisite
None.
4.2.5 Checking the Health State of the NE
Before an upgrade, you need to check the health state of the NE to ensure that the NE is
running normally.
Precautions
An OptiX NG-SDH NE of a version earlier than V100R007 does not support a health state
check. Therefore, see section 7.2 "Verification Procedures" to check the NE state.
Procedure
Refer to step 6 of creating the simulation package loading task in the OptiX NG-SDH
Upgrade Guide_Simulation Package Loading Method (DataCenter for U2000
V100R005C00). Obtain the document according to section 4.1.2 "Obtaining the Reference
Documents."
Result
The NE is running normally.
Postrequisite
None.
4.2.6 Checking the Running Status of the NE
Before an upgrade, you need to check the status comprehensively of the NE to ensure that the
NE is running normally.
OptiX NG-SDH

30

Precautions
None.
Procedure
Step 1 Check the alarms and performance data of the NE.
Check the current alarms of the NE.
Choose Fault > Browse Current Alarm from the Main Menu.
Check the historical alarms of the NE.
Choose Fault > Browse History Alarm from the Main Menu.
Check the current performance data of the NE.
Choose Performance > Browse SDH Performance > Current Performance Data
from the Main Menu.
Check the historical performance data of the NE.
Choose Performance > Browse SDH Performance > History Performance Data from
the Main Menu.
Step 2 Check the running status of the NE.
To be specific, check whether the NESTATE_INSTALL alarm is reported. An NE that is
running normally does not report this alarm.
Step 3 Check the configuration of protection groups.
Check the ring MSP configuration of the NE.
Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Choose Configuration > Ring MS from the Function Tree. Ensure that the protection group
is in the normal state.
Check the linear MSP configuration of the NE.
Step 1. Right-click the NE in the Main Topology and choose NE Explorer from the
shortcut menu.
Choose Configuration > Linear MS from the Function Tree. Ensure that the protection
group is in the normal state.
Check the SNCP configuration.
shortcut menu.
Choose Configuration > SNCP Service Control from the Function Tree. Ensure that the
protection group is in the normal state.
Query the status of the DPS protection group.
shortcut menu.
Choose Configuration > Board 1+1 Protection from the Function Tree. Ensure that the
protection group is in the normal state.
Step 4 Check the configuration of logical boards, the online state of boards, and the versions of
boards.
OptiX NG-SDH

31

Choose Inventory > Physical Inventory > Board from the Main Menu. You can see the type
and online state of each board. Record the version information about each board and ensure
the versions of the boards are correct.
Step 5 Check the routes on the NE.
Check the route status.
For ECC routes, choose Communication > NE ECC Link Management from the
Function Tree. Ensure that the state of ECC routes is correct.
For OSI routes, choose Communication > NE OSI Link Management from the
Function Tree. Ensure that the state of OSI routes is correct.
For IP routes, choose Communication > NE IP Link Management from the Function
Tree. Ensure that the state of IP routes is correct.
Step 6 Check the current synchronization clock and the clock source priority.
Choose Configuration > Clock > Clock Synchronization Status from the Function Tree.
Ensure that the clock tracing relationship are correct.
Choose Configuration > Clock > Clock Source Priority from the Function Tree. Ensure
that the clock source priority table is configured correctly.
Step 7 Check the NE time.
Choose Configuration > NE Time Synchronization from the Function Tree. Ensure that the
NE time is synchronized in the preset synchronization mode.
Step 8 Check the resetting records of the SCC board.
Run the following command on the Navigator to check the resetting records of the SCC
board.
:mon-get-errlog:bid
Ensure that the SCC board has no abnormal resetting record.
Step 9 Check the consistency of databases.
Run the following commands on the Navigator to check the consistency of databases.
:dbms-compare-all:drdb,fdb;
:dbms-compare-all:drdb,cfdb;
:dbms-compare-all:fdb,cfdb;
The following return indicates that the databases are consistent.
DBMS-COMPARE-ALL-DBF
DBF_NO DBF_NAME
1 allDBFaresame
The following return indicates that the databases are inconsistent. In this example, the
CfgSncin.dbf and the CfgHsc.dbf databases are inconsistent.
DBMS-COMPARE-ALL-DBF
DBF_NO DBF_NAME
OptiX NG-SDH

32

1 CfgSncIn.dbf
2 CfgHsc.dbf
Then, run the following commands to synchronize the inconsistent databases.
:dbms-copy-all:drdb,fdb;
:dbms-copy-all:drdb,cfdb;
Step 10 Run the following commands to query the active/standby status of the SCC boards, the status
of the active SCC, and the data backup information.
:hsc-get-ms-info;
Master-and-Slave
Master-slot Slave-slot
17 18

The value of Slave-slot is 0, when single SCC board on NE.
:hsc-get-work;
Work-Status : 17 Good 18 Good
:hbu-get-backup-info;
Backup-Info : 0x0000000003
The value 0x00000003 indicates that the data backup is complete. The value 0x00000002
indicates that the data backup is in progress. The value 0x00000000 indicates that the data is
not backed up. On a normal NE, data backup must be complete.

If the data backup is incomplete, run the :hbu-go-batch command to trigger a data backup.
Step 11 Run the following command to query the package loading status.
:sftm-rtrv-state:swdl
SFTM_RTVE_STATE
CPY_TYPE MAIN_STATE SUB_STATE
swdl NORMAL NORMAL

Generally, the loaded package enters the normal state after the package loading is complete.
----End
Result
The result verification is specified in the preceding procedure.
Postrequisite
None.
4.2.7 Checking the ECC Status of the NE
The ECC protocol must be disabled at the optical interface that does not use the ECC
communication. In this manner, the NE can be reachable to the NMS even when the resources
are insufficient.
OptiX NG-SDH

33

Precautions
None.
Procedure
Step 1 Run the following command to disable the ECC protocol at the required optical interface.
:cm-del-ohpchan:bid,portid,chantype;
Step 2 Save the setting of disabling or enabling the ECC protocol manually. Otherwise, the default
setting is recovered after the SCC board is reset.
Run the following commands to save the setting of disabling or enabling the ECC protocol at
the optical interface:
:dbms-copy-all:drdb,fdb;
:dbms-copy-all:drdb,cfdb;
If the NE houses dual SCC boards, run the following command to perform synchronization
between the two boards.
:hbu-go-batch
Step 3 Run the :hbu-get-backup-info command to query the backup information. If the value
0x00000002 is returned, it indicates that the data is being backed up. If the value 0x00000003
is returned, it indicates that the data is backed up.
----End
Result
The ECC protocol is disabled at the optical interface that does not use the ECC
communication.
4.2.8 Testing the Memory of the SSN1GSCC Board
If the NE to be upgraded houses the SSN1GSCC board, you need to test the memory of the
board before the upgrade. Ensure that the SSN1GSCC board does not have any problem
caused by memory modification.
Precautions
None.
Procedure
Step 1 According to the board code, check whether the SSN1GSCC board was produced before
October 2006.
Step 2 Test whether the SSN1GSCC board is faulty by testing the memory of the SSN1GSCC board
according to the OptiX OSN 3500 SSN1GSCC's Memory Testing Guide-20080305-A. Obtain
the document according to section 4.1.2 "Obtaining the Reference Documents."
Step 3 If the memory of the SSN1GSCC board is faulty, perform active/standby switching in the
case of dual SCC boards, or perform a warm reset for the board in the case of a single SCC
OptiX NG-SDH

34

board. If the active/standby switching or warm reset does not solve the memory problem,
replace the SSN1GSCC board.
----End
Result
The required NE has no exception due to memory modification.
Postrequisite
None.
4.2.9 Checking the Logical Port Types of SSN1SLQ1 Boards and
SSN1SL1 Boards
If the NE to be upgraded houses SSN1SLQ1 or SSN1SL1 boards, verify that all logical ports
of the SSN1SLQ1 or SSN1SL1 boards are optical ports. If any of their logical port is an
electrical port, change it to an optical port before upgrading the NE.
Precautions
If the electrical logical port carries services, switch the services to an idle optical port and then
reconfigure the electrical logical port so it is an optical port.
Procedure
Step 1 Run the :cfg-get-port:Bid,Pid; command to check whether the SSN1SLQ1 or SSN1SL1
boards are configured with logical ports.
If the return result is NSERR_CFG_GET_NULL, no logical port is configured and the
check is complete. If the return result shows that porttype is sdh-eport, go to Step 2.
Step 2 Run the :cfg-del-port:Bid,Pid command to delete the electrical logical port and then issue the
cfg-get-port:Bid, Pid command to check whether the port has been successfully deleted.
Then, go to the next step.
Step 3 Run the :cfg-add-port:Bid,Pid,porttype,portlevel command to configure an optical logical
port (porttype is sdh-opport) and check whether the port has been successfully configured.
The following is an example.
#9-3540:szhw [zzzz][][2011-11-04 09:30:14+00:00]>
:cfg-add-port:1,1,sdh-opport,stm-1
#9-3540:szhw [zzzz][][2011-11-04 09:30:17+00:00]>
:cfg-verify
#9-3540:szhw [zzzz][][2011-11-04 09:30:23+00:00]>
:cfg-get-port:1,0
INSTALLED-PORT
Bid Pid PortType PortLevel
1 1 sdh-opport stm-1
OptiX NG-SDH

35

Total records :1
#9-3540:szhw [zzzz][][2011-11-04 10:21:50+00:00]>
----End
Result
All logical ports of SSN1SLQ1 or SSN1SL1 boards on the NE to be upgraded are optical
ports.
Postrequisite
None.
4.2.10 Operating on ASON Services
Downgrading the ASON Services

If the source version is ASON R1 and ASON services are involved in the upgrade, you need
to downgrade the ASON services to static services. Otherwise, directly proceed to "Locking
Service Rerouting" in section "
."
Step 1 Choose Configuration > SDH ASON > ASON Trail Management in the Main Topology of
the U2000. In the Filter dialog box, click Filter All, as shown in the following figure.
OptiX NG-SDH

36

The Prompt dialog box is displayed. Click Yes, as shown in the following figure.

Step 2 Choose Service > SDH Trail > Manage SDH Trail. Click Filter All in the Set Trail
Browse Filter Criteria interface.
OptiX NG-SDH

37

The Manage SDH Trail window is displayed. Select the service to be downgraded, and
right-click the service. A shortcut menu is displayed. Choose Delete from Network Layer
from the shortcut menu, as shown in the following figure.

The Confirm dialog box is displayed. Click OK, as shown in the following figure.
OptiX NG-SDH

38

After the operation is successful, the Operation Result dialog box is displayed. Click Close
to close the dialog box, as shown in the following figure.

Step 3 Select and right-click the ASON service in the SDH ASON Trail Management window. A
shortcut menu is displayed. Choose Downgrade to Traditional Service from the shortcut
menu, as shown in the following figure.

The Prompt dialog box is displayed. Click Yes to start the downgrade, as shown in the
following figure.

OptiX NG-SDH

39

After the downgrade is successful, the Operation Result dialog box is displayed. Click Close
to close the dialog box, as shown in the following figure.

----End
Locking Service Rerouting
The rerouting of ASON services need be locked only when the source version is ASON
V100R002 or a version later than ASON V100R002 and ASON services are involved in the
upgrade.
Step 1 Choose Configuration > SDH ASON > ASON Trail Management in the Main Topology of
the U2000. In the Filter dialog box, click Filter All, as shown in the following figure.

OptiX NG-SDH

40

Step 2 Click Synchronize in the SDH ASON Trail Management window. The Synchronize dialog
box is displayed, as shown in the following figure.

Click Synchronize to synchronize the service information about the entire network and obtain
information about all the ASON services.
Step 3 Select and right-click an ASON service. A shortcut menu is displayed. Choose Set Routing
Attributes from the shortcut menu. The Set Routing Attributes dialog box is displayed.
Select Locked from the Lockout drop-down list box, and then click OK, as shown in the
following figure.

OptiX NG-SDH

41

After the locking is successful, the Operation Result dialog box is displayed. Click Close to
close the dialog box, as shown in the following figure.

----End
4.2.11 Backing Up the NE Database
Before an upgrade, you need to copy the NE database to the flash memory. Then, you can
restore the database in case of data loss.
Precautions
None.
Procedure
Step 1 Choose Configuration > NE Configuration Data Management from the Main Menu. The
NE Configuration Data Management tab is displayed.
Step 2 On the NE Configuration Data Management tab, click Back Up NE Data and select Back
Up Database to SCC.
OptiX NG-SDH

42

Step 3 In the dialog box that is displayed, click OK. The Operation Result dialog box is displayed,
indicating that the operation is successful. Wait for five minutes and the database is copied
onto the flash memory.

----End
Result
The NE database is backed up successfully.
Postrequisite
None.
4.2.12 Checking Software Package Versions
Before an upgrade, you need to check the software package versions and ensure that they are
consistent with the current NE software.
Precautions
None.
OptiX NG-SDH

43

Procedure
Step 1 Run the following command:
:sftm-query-pkgver
The following return indicates that no software package is present.
:sftm-query-pkgver
Pkg Version
Active Standby
If a software package is present, the version information about the software package is
returned. For example:
:sftm-query-pkgver
Pkg Version
Active Standby
5.21.18.11B01B 5.21.18.11B01B
Total records :1

Step 2 If a software package is present and its version is different from the version of current NE
software, clear the software package before you perform loading. For details on clearing the
software package, see the Operation Guide to Clearing the Software Package on the OptiX
NG-SDH Equipment-20090417-B. Obtain the document according to section 4.1.2 "Obtaining
the Reference Documents."
----End
Result
The software package is not present, or is present and has a version consistent with the current
NE software.
Postrequisite
None.
4.2.13 Checking the Preparations for an Upgrade
After the preceding checks are performed, confirm that all the preparations are done. In this
manner, you can ensure the smooth process of an upgrade.
Precautions
Before an upgrade, export and save the script of NE configuration data.
Procedure
Step 1 Ensure that the protection groups on the NE are normal. If certain protection groups are in a
non-IDLE state, rectify the faults to recover the protection groups to the IDLE state. After that,
the upgrade operation can be performed.
Step 2 Clear the equipment alarms that affect an upgrade.
Step 3 Confirm all the current alarms.
OptiX NG-SDH

44

Step 4 Ensure that the current version of the NMS is consistent with the version matching table.
Step 5 Save the MO of the NMS and collect data. In this manner, you can save the configurations of
the NE, such as the services and the protection groups, to provide comparison for the upgrade.
Step 6 Ensure that you have read through the OptiX NG-SDH Product Upgrade FAQ-20080527-B.
Obtain the document according to section 4.1.2 "Obtaining the Reference Documents."
Step 7 (Optional) If the NE with an extended subrack is an OptiX NG-SDH 3500 and needs to be
upgraded to version V100R008C02 or later, manually add the logical board of the XCE on the
extended subrack. Otherwise, the board on the extended subrack cannot be activated normally
when the oamport interface (EXT interface) on the master subrack is disabled after an
upgrade.
----End
Result
All the preparations are done.
Postrequisite
None.
OptiX NG-SDH
(DataCenter for U2000 V100R005C00) 5 Upgrade Operations

45

5 Upgrade Operations
5.1 Package Diffusion
This topic describes the procedure for performing the package diffusion.
5.1.1 Creating a Package Diffusion Task
When you adopt the package diffusion method to upgrade or downgrade an NE, you need to
create a package diffusion task first.
Precautions
If you need to use the FTP transport protocol, save the software package in the server path
that is specified for the FTP server. If you need to use the default transport protocol, save the
software package in a path on the NMS server.
Procedure
Step 1 Choose Inventory > Fiber/Cable > Fiber/Cable Management from the Main Menu. The
Fiber/Cable Management tab is displayed.

OptiX NG-SDH

46

Step 2 Click Save As in the lower right corner of the tab. The Saving Options dialog box is
displayed.

Select the path where the files are stored and click OK.
Step 3 Choose Administration > NE Software Management > NE Data Backup/Restoration
from the Main Menu. The NE Data Backup/Restoration tab is displayed.
The File Transfer Service Status dialog box may be displayed, indicating that the SFTP and
TFTP are not started and the FTP is running.
Step 4 If the FTP mode is not used or the required FTP server is not started, click OK and start the
FTP, SFTP, and TFTP servers. Enter the username and password on each server, and assign
read and write rights. Choose Administration > NE Software Management > FTP Settings
from the Main Menu. The following dialog box is displayed.

OptiX NG-SDH

47

Step 5 On the File Transfer Service Setting tab, enter the specified username and password. Then,
click Test FTP, Test SFTP, and Test TFTP.

If the Operation Result dialog box indicates that the operation is successful, click OK. If the
Operation Result dialog box indicates that the operation is not successful, check whether the
third-party software is enabled normally.
Step 6 On the NE View tab, select the required NE and click Update Version to obtain the version
information about the required NE.

In the Update Version dialog box that is displayed, click Close.
OptiX NG-SDH

48

Step 7 Select the required NE and choose New Task > Package Diffuse Upgrade/Downgrade Task
from the shortcut menu.

A package diffusion task can be created for one NE. If a package diffusion task is created for
more than two NEs, ensure that all the NEs are affiliated to the same gateway NE. Otherwise,
the package diffusion task cannot be created.
Step 8 Then, the Create Task [Package Diffusion Upgrade/Downgrade] dialog box is displayed.
Perform the following configurations.

CAUTION

When only one NE needs to be upgraded, the simulation package diffusion method can also
be used. If more NEs need to be upgraded in a task, the NEs must share one gateway NE;
otherwise, the task cannot be created.
In Task Type, select Upgrade.
In Task Name, enter the task name.
Select the NE Type and NE Version from the Object Tree.
Set Activation Level. It is recommended that you select Board Level from the
drop-down menu.
Select the required NE and click Query.
OptiX NG-SDH

49

Step 9 If the query result is normal, click Next. The Operation Configuration [Package Diffusion
Upgrade/Downgrade] dialog box is displayed.
In the case of a complete version upgrade, it is recommended that the operation(s) take the
default value(s). Only the selected operations are performed during the upgrade. Otherwise,
they are not performed. You can select Pause Before Current Operation to make the task
pauses before an operation. If Pause Before Current Operation is not selected, the task is
performed in the order of the configured operations.
OptiX NG-SDH

50

Target Version: indicates the target version of the upgrade. If the package loading files of the
target version are already in the software database of the Data Center, you can directly select
the target version from the drop-down menu. This item is optional. To import software, click
.
Start Time: indicates the time when the package diffusion starts. The package diffusion task
starts automatically when the preset time arrives. If Start Time is not set, you need to
manually start the task. This item is optional.

Do not select Custom package because this function is not supported. If you select this
item, the loading fails.
If you have selected Force to load selected GNE through FTP, ensure that the directory
title (including the folder name) has less than 59 Characters; if the directory title has more
than 59 Characters, the loading fails.
Step 10 Select the operation steps.
Configure the precheck items.
If you only need to check the NE, you can select the operation only. That is, the upgrade
operations only include the precheck.
In the Operation Configuration [Package Diffusion Upgrade/Downgrade] dialog box,
select the Precheck check box and click Configure Precheck Items.
OptiX NG-SDH

51

Select Alarm and Health and click OK. The item Extended Check is optional. If you select
the item, you need to import the scripts for the check.
Configure backup items.
select the Backup check box. Click Configure Backup Information. The Configure
Backup Operation dialog box is displayed.

Select Data File and click OK.
Configure the software files to be loaded.
select the Load Software check box. Click Configure Package. The Select Package
File(s) dialog box is displayed.
OptiX NG-SDH

52

Find the directory for saving the software package of the target version. Then, select the
package description file (*.pkg), and click OK.
Configure the activation item.
select the Activate check box. Click Configure Activation. The Configure Activation
dialog box is displayed.

OptiX NG-SDH

53

To get activation groups according to the fiber configuration file, select Select Optical Fiber
Configuration File and click to select the fiber configuration file. Then, click Get
Default Activation.
NOTE

If you select this method and connect two boards that will be reset (cold) through one optical fiber, the
boards will be set to one group.
If you do not need to configure activation groups according to the fiber configuration file,
click Get Default Activation.

Select the required board and click to add a new activation group. You can click
to move the NE to the previous group, or click to move the NE to the next group.
Another approach is to click and drag the board to the required group. The first and second
activation groups, however, cannot be modified.
Configure the postcheck items.
For details, refer to steps described in the precheck items.
Step 11 After the configurations of the required operations are complete, click Next. The
Confirmation [Package Diffusion Upgrade/Downgrade] dialog box is displayed.
OptiX NG-SDH

54

In the Confirmation [Package Diffusion Upgrade/Downgrade] dialog box, the previous
configurations are listed. Check whether the configurations of the upgrade operations are
correct. To modify the configurations, click Previous to return to the previous dialog box. If
all the configurations are correct, click OK.
Step 12 Till now, the package diffusion task is created. You can view the new package diffusion task
on the NE Upgrade Task Management tab. As shown in the following figure, the new task
is in the Not Run state.

----End
OptiX NG-SDH

55

Postrequisite
Run the package diffusion task to upgrade or downgrade an NE.
5.1.2 Running a Package Diffusion Task

If the board software of SSN4EGS4 is upgraded to 1.25 or later for a larger buffer size of
ports, a cold reset needs to be performed on the board after the upgrade.
If the board software of SSN5EFS0, SSN1EFS0A, SSN3EFS4, SSN3EGS2, SSN1EMS2
is upgraded to 2.33 or later for a larger buffer size of ports, a cold reset needs to be
performed on the board after the upgrade.
If the board software of SSN1EGSH is upgraded to 3.05 or later for a larger buffer size of
If the board software of SSN1EAS2 is upgraded to 1.93 or later for a larger buffer size of
After the package diffusion task is created, start the upgrade or downgrade task by performing
the following steps.
Context
None.
Procedure
Step 1 On the NE Upgrade Task Management tab, select the new package diffusion task and
choose Start Task from the shortcut menu.

The Task Start Confirmation dialog box is displayed. Click Yes.
OptiX NG-SDH

56

On the NE Upgrade Task Management tab, you can see that the new package diffusion task
is running.

Step 2 If you select Pause Before Current Operation for an operation when creating the package
diffusion task, the package diffusion task pauses before this operation. To continue the task,
you need to select the task and choose Continue Task from the shortcut menu.

Step 3 After all the operations of the package diffusion task are complete, you can see the operation
result of this task.
OptiX NG-SDH

57

----End
OptiX NG-SDH
(DataCenter for U2000 V100R005C00) 6 Version Rollback

58

6 Version Rollback
6.1 Precautions
Be familiar with certain precautions before you perform a rollback operation.

Use the software version rollback function only when an exception occurs in the upgrade
process. This function enables the software to return to the original version. Before you
perform a rollback operation, ensure that the software or software package of the target
version is ready.
This section describes how to perform an NE-level rollback and a board-level rollback. It
is recommended that you use the NE-level rollback method. If an NE-level rollback fails
or if only an onsite rollback is supported, use the board-level rollback method.
In the rollback process, a smooth downgrade of databases is not supported. Therefore,
services may be interrupted in the process. Save the service configuration data properly
and back up the database package before a rollback. This method ensures that services can
be restored successfully after a rollback.
Rollback During Package Diffusion Loading
If an NE is loaded with a software package for the first time and a rollback is required,
the rollback fails because the software package of the target version is not available in
the CF card.
A rollback can be performed only before the NE submits an upgrade task.
A rollback fails if the NE has no CF card.
6.2 Rollback Process
This section uses flow charts to illustrate the rollback steps.
OptiX NG-SDH

59

Flowchart for a Rollback During Package Diffusion Loading
Figure 6-1 Flowchart
Start
Perform an NE-level
rollback
Roll back the software
version of the system
control board
Roll back the software
versions of other boards
End
Perform a board-
level rollback
Verify whether the rollback is
successful
Yes
No

6.3 Procedures of an NE-Level Software Rollback
This section describes the steps for performing a rollback in a specific scenario.
6.3.1 Rollback During Package Diffusion
This section provides various rollback methods during package diffusion and describes
associated operations.
Precautions
Several rollback methods are available if the package diffusion method is used for upgrade.
During the actual operation, select an appropriate rollback method depending the running
phase of the package diffusion task.
Table 6-1 Conditions of rollback methods during package diffusion
Operation Condition Remarks
Package diffusion The package diffusion task is complete. None
Toolkit The package diffusion task is complete. None
Board-level loading The package diffusion task is complete. None

OptiX NG-SDH

60

Procedure
Package loading: see the OptiX NG-SDH Upgrade Guide_Simulation Package Loading
Method (DataCenter for U2000 V100R005C00). Obtain the document according to
section 4.1.2 "Obtaining the Reference Documents."
Toolkit: For details, see the Remote Software Degrade Guide to the OptiX NG-SDH
(Toolkit)-20090904-B.
Board-level loading: For details, see the Software Degrade Guide to the OptiX NG-SDH
- -20091202-B.
Postrequisite
None.
6.4 Procedures of a Board-Level Software Rollback
A board-level software rollback is applicable when an NE-level rollback fails, only the on-site
rollback operation is supported, or the basic BIOS needs to be downgraded. A board-level
software rollback can be an NE software rollback or a board software rollback.
For details, see the OptiX NG-SDH Products Software Downgrade Guide-20091202-B.
6.5 Verification of a Version Rollback
After a rollback is complete, check whether the version runs normally according to the
checklist.
Precautions
After a rollback is complete, check whether the version runs normally according to the
checklist.
Table 6-2 Verification checklist of a version rollback
SN Item Criteria Check
Result
1 Checking the running
status of the NE
The NE is running normally. OK
2 Checking the
consistency between
the configuration
data on the NMS and
the configuration
data on the NE
The configuration data on the NE side is
consistent with the configuration data on the
NMS side.
OK
3 Checking the
software versions
The software versions are consistent with the
OK
OptiX NG-SDH

61

SN Item Criteria Check
Result
4 Checking the ECC
routes on the NE
The network routing information is
complete.
OK
5 Checking the version
of the NMS
The version of the NMS meets the lowest
mapping requirements. For details, see the
OK
6 Checking with the
customer whether
services are normal
after the rollback
All the services are normal. OK

Procedure
For details, see section 4.2.6 "Checking the Running Status of the NE."
Step 2 Check the consistency between the configuration data on the NMS and the configuration data
on the NE.
For details, see section 4.2.2 "Checking the Consistency Between the Data on the NMS and
the Data on the NE."
Step 3 Check the software versions.
Step 4 Check the ECC routes on the NE.
For details, see section 4.2.7 "Checking the ECC Status of the NE."
Step 5 Check the version of the NMS.
For details, see section 4.2.1 "Checking the NMS Version."
Step 6 Check with the customer whether services are normal after the rollback.
All the services are normal after the rollback.
----End
Postrequisite
None.
OptiX NG-SDH
(DataCenter for U2000 V100R005C00) 7 Upgrade Verificat ion

62

7 Upgrade Verification
7.1 Verification Checklist
This section provides the checklist for verifying an upgrade.
Verification checklist of an upgrade

Print A "Upgrade Records" for future use.
7.2 Verification Procedures
This section describes the items to be checked and check criteria.
Procedure
For details, see section 4.2.6 "Checking the Running Status of the NE."
Step 2 Check the consistency between the configuration data on the NMS and the configuration data
on the NE.
For details, see section 4.2.2 "Checking the Consistency Between the Data on the NMS and
the Data on the NE."
Step 3 Check the software versions.
For details, see section 4.2.3 "Checking the Board Software Version Information About the
NE."
Step 4 Check the routes on the NE.
Issue the following commands to check whether the route information of the network is OK.
:cm-get-newbdinfo
Step 5 Check the version of the NMS.
For details, see section 4.2.1 "Checking the NMS Version."
Step 6 Check with the customer whether services are normal after the upgrade.
OptiX NG-SDH
(DataCenter for U2000 V100R005C00) 7 Upgrade Verificat ion

63

All the services are normal after the upgrade.
----End
OptiX NG-SDH
(DataCenter for U2000 V100R005C00) 8 Exception Handling

64

8 Exception Handling
Certain exceptions may occur in the upgrade process. This chapter describes how to handle
them.
8.1 Handling the Isolated Boards
Precautions
If the upgrade error tolerance mode is disabled, do not perform this operation.
Handling Procedure
Step 1 After the activation operation fails, some boards are isolated.

Step 2 Query the isolated boards.
OptiX NG-SDH
(DataCenter for U2000 V100R005C00) 8 Exception Handling

65

Step 3 Handle the isolated boards.
Board-level loading is required to upgrade the TN11OBU1 board. For details, see the OptiX
NG-SDH Upgrade Guide_Simulation Package Loading Method (DataCenter for
V100R005C00. Obtain the document according to section 4.1.2 "Obtaining the Reference
Documents."
Right-click the desired task and choose Continue from the shortcut menu.

----End
8.2 Boards That Does Not Support Package Diffusion
The TN11OBU1 board does not support package diffusion.
Board-level loading is required to upgrade the TN11OBU1 board. For details, see the OptiX
NG-SDH Product Software Upgrade Guide (TOOLKIT V100R004) - 20101022-B. Obtain the
document according to section 4.1.2 "Obtaining the Reference Documents."
OptiX NG-SDH
(DataCenter for U2000 V100R005C00) 9 Associated Tasks and Reference Informat ion

66

9 Associated Tasks and Reference
Information
9.1 Recovering the Database of an NE
After an upgrade fails, you can recover the database from the NMS server or NMS client if
the database is backed up.
Precautions
You must be a user with the network operator authority of the U2000.
The computer where the U2000 is installed must communicate with the NE normally.
If the database recovery operation is performed on the NMS client, the SFTP server must
be configured and the SFTP server must be started.
The recovery operation cannot be performed on multiple devices of different types.
Information about NEs of the same type can be viewed in the right pane if you select an
NE of a specific type in the NE type tree, as shown in the following figure.

OptiX NG-SDH

67

Before you recover the database package of an ASON NE, ensure that the NE storing the backup
database package has the same NE software version, NE ID, and node ID as the NE whose database
needs to be recovered. If an ASON NE has a different node ID after database recovery, confusion occurs
on the entire ASON control plane. In this case, modifying a node ID by using an ASON-related feature
causes residual cross-connections. Automatic cleanup of residual cross-connections may incorrectly
delete certain ASON services.
Procedure
Step 1 On the U2000, choose Administration > NE Software Management > NE Data
Backup/Restoration from the Main Menu. The NE View tab is displayed.
Step 2 In the NE View tab, right-click one or more NEs of the same type.
Step 3 Choose Recover from the shortcut menu to display the Recover dialog box.

Step 4 In the Recover dialog box, select the file to be recovered from the File Name drop-down list.
If the file to be recovered is not found in the drop-down list, click Browse to display the
Select File dialog box, as shown in the following figure.
OptiX NG-SDH

68

Step 5 Select NMS Server or NMS Client to recover the file. By default, NMS Server is selected.
If you select NMS Server, the backup file on the NMS server is recovered. In the
Selected File dialog box, specify the path of the backup file.
If you select NMS Client, click to select the backup file on the NMS client.
Specify the path of the backup file in the Selected File dialog box. The path of the
backup file is displayed in the File To Be Recovered text box.
Step 6 Click OK. The path of the backup file to be recovered is displayed in the File Name
drop-down list. The backup file is stored on the NMS server or NMS client.
Step 7 Click Start. In the Operation Confirmation dialog box that is displayed, click Yes.

In the Operation Status column, the recovery progress is displayed. If activation operation is not
performed five minutes after a successful recovery, the DC tool automatically performs a rollback and
this recovery is canceled.
Step 8 Right-click the NE whose database is recovered, and choose Activation Database from the
shortcut menu. In the Activation Database dialog box that is displayed, select Deliver To
Board and then click Start if the NE is of V100R008C02 or later; click Start if the NE is of a
version earlier than OptiX NG-SDH V100R008C02. In the latter case, you need to perform a
warm reset for the board after database activation is complete. In this manner, the
configuration data can be delivered.
OptiX NG-SDH

69

The OptiX NG-SDH NE of V100R008C02 or later provides the function of automatically delivering
configuration data to boards.
Select Deliver To Board only when the NE software supports the function of automatically
delivering configuration data to boards.
When the configuration data is delivered to boards, a warm reset is performed for these boards in
turn.
----End
OptiX NG-SDH
(DataCenter for U2000 V100R005C00) A Upgrade Records

70

A Upgrade Records
Name of Site Upgrade Time
Source Version
Number
Target Version Number
Upgrade Personnel Personnel from the customer:
Personnel from Huawei:
The upgrade is
successful or fails?

Upgrade Checklist Conclusion Remarks of Anomaly
Handling
Checklist before the
upgrade

Checklist of upgrade
procedures

Verification checklist
after the upgrade

OptiX NG-SDH
(DataCenter for U2000 V100R005C00) B Glossary

71

B Glossary
A
Alarm A visible or an audible indication to notify the person concerned that a failure or an
emergency has occurred. See also Event.
Alarm suppression When alarms of various levels occur at the same time, certain lower-level alarms are
suppressed by higher-level alarms, and therefore will not be reported.
Alarm indication On the cabinet of an NE, there are three indicators with different colors indicating
the current state of the NE. You can stop the NE alarm indication through the
Network Management System (NMS).
Attenuator A passive component that attenuates an electrical or optical signal.

C
Client A kind of terminal (PC or workstation) connected to a network that can send
instructions to a server and get results through a user interface. See also server.
Configuration To set the basic parameters of an operation object.
Configuration Data A command file for an NE which defines the configuration of the NE hardware.
With the file, the NE can coordinate with other NEs in the entire network.
Configuration data is the key factor for the normal running of the entire network.
Current Alarms Alarms that have not been cleared, or those that have been cleared but are not
acknowledged.

E
Ethernet A data link level protocol comprising the OSI model's bottom two layers. It is a
broadcast networking technology that can use several different physical media,
including twisted pair cable and coaxial cable. Ethernet usually uses CSMA/CD.
TCP/IP is commonly used with Ethernet networks.

F
Fiber jumper The fiber which is used to connect the subrack with the ODF.
OptiX NG-SDH

72

Forced Switch This command performs ring switching from working channels to the protection
channels. This switch occurs regardless of the state of the protection channels, unless
the protection channels are satisfying a higher priority bridge request.

G
Gateway NE Gateway Network Element. Gateway NE provides the communications between NEs
and network management system.

L
Laser The device that generates the directional light covering a narrow range of
wavelengths. Laser light is more coherent than ordinary light. Semiconductor diode
lasers are the used light source in fiber-optic system.
Loopback The fault of each path on the optical fiber can be located by setting loopback for each
path of the line. There are three types of loopback modes: Non-loopback, Outloop,
and Inloop.

M
Main Topology A basic component of man-machine interface for the NMS. The main topology
displays the networking details and the basic information about NEs, alarms of
subnets, communication status.
MSP The MSP function provides capability for switching a signal between and including
two MST functions, from a working to a protection channel.

N
NE Network element that contains hardware and the software running on the hardware.
Generally, one network element should contain one SCC board at least, which
manages and monitors the entire network element. The NE software runs on the SCC
board.
NE Explorer A main operation interface of the NMS. An expandable object tree (function tree) is
absent at the lower left pane of the interface. The user can fast locate the operation
object from the object tree and then perform configuration, management and
maintenance accordingly.

O
Optical Connector A component normally attached to an optical cable or piece of apparatus for the
purpose of providing frequent optical interconnection/disconnection of optical fibers
or cables.

R
Receiver Sensitivity Receiver sensitivity is defined as the minimum acceptable value of average received
power at point R to achieve a 1 x 10-10 BER.
OptiX NG-SDH

73

S
Single-fiber
bidirectional
transmission
On the transmission line, the optical signals of different wavelengths in the transmit
and receive directions are transmitted over one fiber.
Subnet The logical entity in the transmission network and comprises a group of network
management objects. A subnet can contain NEs and other subnets. A subnet planning
can enhance the organization of a network view.

T
Tributary loopback A fault location method. A fault can be located for each service path by performing
loopback on each path of the tributary board. There are three types of loopback
modes: Non-loopback, Outloop, and Inloop.

U
User The user of the NMS client, and the user and password define the corresponding
authority of operation and management of the NMS.

OptiX NG-SDH
(DataCenter for U2000 V100R005C00) C Acronyms and Abbreviations

74

C Acronyms and Abbreviations
D
DC Data Center
DCC Data Communication Channel

E
ECC Embed Control Channel

L
LMS Linear Multiplex Section protection

R
RMS Ring Multiplex Section protection

S
SCC System Control & Communication Unit
SDH Synchronous Digital Hierarchy

T
TPS Tributary Protection Switch

Optix NG-SDH v100r010c03spc203 Upgrade Guide

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Optix NG-SDH v100r010c03spc203 Upgrade Guide

Încărcat de

Drepturi de autor:

Formate disponibile

OptiX NG-SDH

S-ar putea să vă placă și