ZXONE Fault Information Collecting - V1.0

ZXONE 9700
Packet OTN Equipment

Fault Information Collecting
Version：V3.00&V3.10
ZTE CORPORATION
No. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://support.zte.com.cn
E-mail: 800@zte.com.cn
LEGAL INFORMATION
Copyright © 2016 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution 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. Additionally, the contents of this document are protected by
contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit the ZTE technical support website http://support.zte.com.cn to inquire for related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No. Revision Date Revision Reason
R1.0 2016-04-01 First edition
Serial Number: SJ-20160303094203-013
Publishing Date: 2016-04-01(R1.0)
SJ-20160303094203-013|2016-04-01(R1.0) ZTE Proprietary and Confidential

Content
About This Manual ......................................................................................... I
Chapter 1 Overview ................................................................................... 1-1
1.1 Meaning of Information Collection ....................................................................... 1-1
1.2 Information Collection Range ............................................................................. 1-1
Chapter 2 Equipment Fault Information Collection ................................ 2-1

2.1 Maintenance Information Collection .................................................................... 2-1
2.1.1 Collecting EMS Version Information........................................................... 2-1
2.1.2 Collecting the Operating System Information About the EMS Server ........... 2-3
2.1.3 Collecting the Disk Usage of the EMS Server ............................................ 2-4
2.1.4 Collecting Alarm Information .................................................................... 2-5
2.1.5 Collecting Performance Information .......................................................... 2-5
2.1.6 Collecting Log Information ....................................................................... 2-7
2.1.7 Collecting the Upload and Comparison Information About EMS Data........... 2-8
2.1.8 Backing Up Data Through the EMS Menu ................................................. 2-9
2.1.9 Backing Up Data Through dbtool............................................................. 2-10
2.2 Monitoring Information Collection ..................................................................... 2-12
2.2.1 Collecting the Monitoring Information About the Master and Slave
Subracks ............................................................................................. 2-12
2.2.2 Collecting NE Monitoring Information ...................................................... 2-13
2.2.3 Collecting the IP Address Information About the SOSC Board .................. 2-13
2.2.4 Collecting the Connection Information About Optical Interfaces ................ 2-14
2.3 Board Information Collection ............................................................................ 2-15
2.3.1 Collecting Board Version Information ...................................................... 2-15
2.3.2 Collecting Agent Log Information ............................................................ 2-17
2.3.3 Collecting the CPU Usage Information About a Board .............................. 2-18
2.4 Protection Switching Information Collection ....................................................... 2-19
2.4.1 OP Protection Information Collection ...................................................... 2-19
2.4.2 ODUK 1+1 Protection Information Collection ........................................... 2-23
Chapter 3 U31 Fault Information Collection ............................................ 3-1

3.1 Fault Background Information Collection ............................................................. 3-1
3.2 Collecting Client Logs and Large Files ................................................................ 3-2
3.3 Server Log and Large File Collection .................................................................. 3-4
3.3.1 Collecting Server Information With the Client Tool ...................................... 3-4

3.3.2 Collecting Server Information With the Server Tool .................................... 3-8
3.4 Collecting Database Logs ................................................................................ 3-10
Glossary .......................................................................................................... I
II

About This Manual
Purpose
This manual describes how to collect the fault information about the ZXONE 9700 quickly,
correctly, and completely.
Intended Audience
This manual is intended for:
l Debugging engineers
l EMS monitoring personnel
l Maintenance engineers
What Is in This Manual

This manual contains the following chapters.
Chapter 1, Overview Describes the meaning of information

collection and the information collection range.
Chapter 2, Equipment Fault Information Collection Describes how to collect maintenance

information, monitoring information, board
information, and protection switching
information.
Chapter 3, U31 Fault Information Collection Describes how to collect fault background
information, client logs and large files, server
logs and large files, and database logs.
Conventions
This manual uses the following conventions.
Danger: indicates an imminently hazardous situation. Failure to comply can result in

death or serious injury, equipment damage, or site breakdown.
Warning: indicates a potentially hazardous situation. Failure to comply can result in

serious injury, equipment damage, or interruption of major services.
Caution: indicates a potentially hazardous situation. Failure to comply can result in

moderate injury, equipment damage, or interruption of minor services.
Note: provides additional information about a topic.

This page intentionally left blank.
II

Chapter 1
Overview
Table of Contents
Meaning of Information Collection .............................................................................1-1
Information Collection Range ....................................................................................1-1
1.1 Meaning of Information Collection

If a device is faulty, troubleshooting relies on the correct, comprehensive, and timely
collection and feedback of fault information.
Fault information is a prerequisite for fast troubleshooting. Incorrect or incomplete fault
information may lead to a more difficult or even diametrically opposite fault diagnosis.
Delayed feedback may delay troubleshooting and severely threaten the stability and
security of the device.
1.2 Information Collection Range

For the information that needs to be collected during the fault analysis of the ZXONE 9700,
refer to Table 1-1.
Table 1-1 Information Collection and Feedback Form
Collection Type Fault Type Collected Information Remarks
Equipment fault Operation and Detailed version of the EMS -

collection maintenance Operating system of the EMS -
server
Disk usage of the EMS -

server
Alarm information -
Performance information -
Log information -
Upload comparison of EMS -

Data
Data backed up through the The username and

EMS menu password must be
provided.
1-1

ZXONE 9700 Fault Information Collecting
Collection Type Fault Type Collected Information Remarks
Data backed up through the The username and

dbtool password must be
provided.
Monitoring Monitoring information -

about the master and slave
subracks
NE monitoring information -
IP information about the -

SOSC board
Connection information -
about optical interfaces
Service board Board version information Detailed board

version, including
the minor version
number.
Agent log information -
CPU usage of boards -
Protection OP protection information -
ODUK 1+1 protection -

information
APS module login -

information
Configuration information -
about protection groups
APS historical input -

information
APS historical output -

information
Historical input and output -

records
U31 fault collection EMS Fault background information -
Client logs and large files -
Server logs and large files -
Database logs -
1-2

Chapter 2
Equipment Fault Information
Collection
Table of Contents
Maintenance Information Collection ...........................................................................2-1
Monitoring Information Collection ............................................................................2-12
Board Information Collection ...................................................................................2-15
Protection Switching Information Collection .............................................................2-19
2.1 Maintenance Information Collection

2.1.1 Collecting EMS Version Information
This procedure describes how to collect the detailed version information about the U31.
Steps
1. In the main window of the U31, select Help > About. The About dialog box is
displayed.
2. On the About tab, view the version of the U31, see Figure 2-1.
2-1

Figure 2-1 U31 Version
3. On the Information tab, view the detailed version information and patch version of
each module, see Figure 2-2.
Figure 2-2 Version Information and Patch Versions of Modules
2-2

Chapter 2 Equipment Fault Information Collection
4. Take a screenshot and save the queried version information about the U31.
– End of Steps –
2.1.2 Collecting the Operating System Information About the EMS

Server
This procedure describes how to collect the operating system version and patch
information about the EMS server, analyze the relationship between the operating system
and patch, and check whether the patch must be updated.
Steps
1. On the desktop of the EMS server, right-click My Computer, and select Properties
from the shortcut menu. The System Properties dialog box is displayed.
2. On the General tab, view the operating system version and patch information about
the EMS server, see Figure 2-3.
Figure 2-3 Operating System Information About the EMS Server
2-3

3. Take a screenshot and save the queried operating system version and patch
information about the EMS server.
2.1.3 Collecting the Disk Usage of the EMS Server

This procedure describes how to collect the disk usage information about the U31 server
and check whether the disk usage exceeds the threshold.
Steps
1. On the desktop of the EMS server, double-click My Computer. The My Computer
window is displayed.
2. Right-click the disk where the EMS server is installed, and select Properties from the
shortcut menu. The Properties dialog box is displayed.
3. On the General tab, view the disk usage of the EMS server, see Figure 2-4.
Figure 2-4 Disk Usage Information About the EMS Server
4. Take a screenshot and save the queried disk usage information about the EMS server.
2-4

2.1.4 Collecting Alarm Information

This procedure describes two methods to collect NE alarms in the Topology Management
window: direct query and query through the right-click menu.
Steps
1. Select one of the following methods to query alarms.
l In the Topology Management window, select one or multiple NEs. The current
alarms of the NE or NEs are displayed at the bottom of the Topology Manage-
ment window.
l In the Topology Management window, right-click one or multiple NEs, and select
Active Alarm or History Alarm from the shortcut menu to view the corresponding
alarms.
l In the Topology Management window, right-click one or multiple NEs, select
Fault Management from the shortcut menu, and then select a submenu for the
required operation, see Figure 2-5.
Figure 2-5 Right-Click Menu
2. Take a screenshot and save the queried alarm information.

2.1.5 Collecting Performance Information

This procedure describes how to collect the current performance and historical
performance of NEs through the right-click menu in the Topology Management window.
Prerequisite
l You have performance management permissions.
l Performance measurement tasks are created and performance data exists in the
performance database.
l The links of the NEs whose current performance needs to be collected are established.
2-5

Steps
l Collect the current performance of NEs.
In the Topology Management window, right-click one or multiple NEs, and select
Performance Management > Current Performance Data Query from the shortcut
menu. The Current Performance Data Query window is displayed.
The current performance information about the selected NE or NEs is displayed in
the window. By default, the query granularity of the current performance data is 15
minutes.
l Collect the historical performance of NEs.
1. In the Topology Management window, right-click one or multiple NEs, and

select Performance Management > History Performance Data Query from the
shortcut menu. The History Performance Data Query window is displayed.
2. On the Index/Counter Selection tab, set the parameters. For a description of the
parameters, refer to Table 2-1.
Table 2-1 Descriptions of the Parameters on the Index/Counter Selection Tab
Parameter Description
Common template Select a self-contained or user-defined common template from

the drop-down list or do not select any template.
MO type Keep the default setting (checkpoint).
Available indices/counters If Common template is not set, select the performance items
that you want to query from the MO Tree navigation tree.
Selected indices/counters Displays the performance items selected from the MO Type
navigation tree.
3. On the Object Selection tab, set the parameters. For a description of the
Table 2-2 Descriptions of the Parameters on the Object Selection Tab
Location group Select a location group from the drop-down list.

For example, Query raw data.
Wildcard level Select a wildcard level from the drop-down list.

For example, EQ.
NE location Select the NEs that you want to query from the EMS Server
navigation tree.
If Wildcard level is set to All or NE, this parameter does not
need to be set.
2-6

MO location Select MO locations from the MO Tree navigation tree.

For example, if Wildcard level is set to EQ, select the
corresponding boards from the MO Tree navigation tree.
If Wildcard level is set to All or NE, this parameter does not
need to be set.
4. On the Time Selection tab, set the parameters. For a description of the
Table 2-3 Descriptions of the Parameters on the Time Selection Tab
Query Granularity Performance collection period.
Time settings period of performance data query.
Effective date The system queries only the performance data within the
effective date.
Effective time The system queries only the performance data within the
effective period.
5. Click OK.
The queried historical performance is displayed in the Query window.
2.1.6 Collecting Log Information

This procedure describes how to collect log information.
Log management is an effective tool used by the system administrator to track the
operational status of the system, locate system faults, and track system usage. With
log management, ordinary users can review historical operations and understand the
operational status of the system.
Log management provides two functions: log recording and log management. With log
management, you can query, delete, and back up logs, view the detailed information about
logs, set log filter conditions, and view operations.
Logs can be divided into operation logs, security logs, and system logs.
l Operation log
Records the operation information about users, including log IDs, operation levels,
usernames, operation names, host addresses, command functions, operation results,
failure causes, connection methods, operation objects, operation start time, operation
end time, and related log information.
l Security log
2-7

Records the log information about user login status, including log IDs, usernames,
host addresses, log names, operation time, connection methods, and detailed
information.
l System log
Records the completion status of scheduled tasks, including log IDs, levels, sources,
log names, detailed information, host addresses, and operation start time.
Steps
1. Select either of the following methods to open the Log Management window.
l In the main window of the U31, select Security > Log Management.
l Click the button on the toolbar.
2. Double-click a node in the Log Management navigation tree in the left pane.
The corresponding log information is displayed in the right pane.
Related Task
Refresh log information: click the button on the toolbar. The system queries the latest
log information in accordance with the current query conditions.
2.1.7 Collecting the Upload and Comparison Information About

EMS Data
This procedure describes how to collect the data changes and synchronization status of
the EMS and obtain information about the data changes of an NE to find and fix faults.
Steps
1. In the main window of the U31, right-click an NE, and select Data Synchronization
from the shortcut menu. The Data Synchronization window is displayed.
Caution!
The data upload and data download operations are risky and may cause service
interruption. Perform the operations with caution.
2. In the Compare Data Item area of the Compare tab, select the data items that need
to be compared, see Figure 2-6.
2-8

Figure 2-6 Data Comparison Information
3. Click the Compare button. The system shows the data comparison progress in a
progress bar.
When the comparison progress reaches 100%, the data comparison result is displayed
in the Result area.
4. Take a screenshot and save the upload and comparison information about EMS data.
2.1.8 Backing Up Data Through the EMS Menu

This procedure describes how to back up data through the EMS menu.
For the data backup and restoration between the EMSs with the same scale and version,
it is recommended to back up and restore data through the U31 menu.
During data backup and restoration, the objects that need to be backed up and restored
must be the same product components with the same version and scale.
Steps
1. In the main window of the U31, select Maintenance > System Backup and Restore.
The System Backup and Restore window is displayed.
Note:
This operation can back up the entire database structure, basic data, and files.
2. Select Backup > Backup Basic Data from the Backup and Restore navigation tree
in the left pane, and set a path to store backup files.
2-9

3. (Optional) Select the Backup File Download Path at Client check box and set a path
to download backup files.
4. Click the Execute button to back up data.
Note:
The reported backup implementation status is displayed in the Execution Result area.
After the backup is completed, a message is displayed in the Execution Result area,
showing that the operation is successful.
The backup files can be viewed in the storage path set in the previous step. Copy the
backup files and send them to experts for analysis.
2.1.9 Backing Up Data Through dbtool

This procedure describes how to back up data through dbtool.
dbtool is a built-in tool of the U31 to back up NE data and EMS data. dbtool supports the
cross-version data restoration, meaning that the data of an early version can be restored
to a late version.
Note:
The data backed up through the U31 cannot be restored through dbtool.
Steps
1. On the U31 server, enable dbtool in accordance with the operating system.
l Windows: /ums-server/utils/dbtool/dbtool.bat
l Linux: /ums-server/utils/dbtool/dbtool.sh
2. Set the parameters in the login window. For a description of the parameters, refer to
Table 2-4.
Table 2-4 Descriptions of the Parameters in the Login Window
Language Language that dbtool is in.
DBMS Type l For Windows, select SQL Server from the drop-down list.
l For Linux, select Oracle from the drop-down list.
DBMS IP IP address of the U31 server.
2-10

DBMS Port Keep the default setting.

For example, 1433.
DBA Administrator name set during the installation of the EMS

database.
For example, sa.
Password Administrator password set during the installation of the EMS

database.
3. Click the Login. The main window of dbtool is displayed.

4. From the dbtool navigation tree in the left pane, select Backup And Restore >
Backup EMS. The Backup EMS tab is displayed in the right pane, see Figure 2-7.
Figure 2-7 Backup EMS Tab (Windows)
5. (Optional) Enter the backup file name in the Name text box.
6. On the Option tab, set backup items.
Note:
Only the Basic Data check box needs to be selected. The other option are used for
fault location.
2-11

7. Click the Backup button.

8. After data is backed up completely, a message box is displayed. Click OK.
The backup files can be viewed in the backup directory. Copy the backup files and
send them to experts for analysis.
2.2 Monitoring Information Collection

2.2.1 Collecting the Monitoring Information About the Master and
Slave Subracks
This procedure describes how to collect the connection information about the monitoring
cables between the master and slave subracks, so that you can analyze whether the NE
monitoring system is faulty.
For OTN devices, the master and slave subracks can be cascaded through the GE
interface, FE interface, and 36-core data cable. For the ZXONE 9700, the master and
slave subracks are cascaded through the GE interface.
Steps
1. Record the connection information about the monitoring cables between subracks.
Ensure that the connections are the same as those in the fiber connection diagram.
Table 2-5 Subrack Cascade Connection Information
Equipment Type Subrack Type Cascading Board Cascading Method
ZXONE 9700 DX41 or NX41 CCP GE interface

subrack
S3 or S6 subrack NCPK and CCPK GE interface
ZXMP M820 or ZXWM Slave subrack without SPWA GE interface

M920 the SCC board
Slave subrack with SPWA GE interface

the SCC board
Slave subrack with SEIA 36-core data cable

the SCC board
ZXMP M721 - NCP FE interface
2. (Optional) Fasten the loose fiber pigtails or data cable interfaces.
2-12

2.2.2 Collecting NE Monitoring Information

This procedure describes how to collect the monitoring information about NEs.
The system provides three monitoring methods: optical monitoring, electrical monitoring,
and back-to-back monitoring.
Context
l Optical monitoring: Data is transmitted between different NEs through the optical
interfaces of the SOSC, SOSCB, and NCP boards. EMS information is transmitted
to different NEs through the optical monitoring channels of the SOSC, SOSCB, and
NCP boards.
l Electrical monitoring: Data is transmitted between different NEs on the basis of the
coordination between the monitoring board and service board. The GCC channel
provided by the service board is used to transmit EMS information between different
NEs, and this connection method is called the electrical monitoring connection
method.
l Back-to-back monitoring: The electrical interfaces of the SOSC or SOSCB board of
two NEs are set in the same network segment. You need to add static routes destined
for the IP addresses of the NEs on the EMS, and then you can manage these two NEs.
Steps
1. Record the monitoring method of and fiber connection information about each NE.
Ensure that the connections are the same as those in the fiber connection diagram.
2. Save NE monitoring information.
2.2.3 Collecting the IP Address Information About the SOSC Board

This procedure describes how to query the IP address information about the SOSC
board to view the information about electrical interfaces (including monitoring electrical
interfaces) and optical interfaces.
Steps
1. In the Topology Management window, double-click the NE that you want to query.
The Rack Chart window is displayed.
2. Right-click the SOSC board, and select NE Management from the shortcut menu. The
NE Management window is displayed.
3. From the Board Operation navigation tree in the left pane, select Communication
Maintenance > Board IP Configuration. The Board IP Configuration window is
displayed, see Figure 2-8.
2-13

Figure 2-8 Querying the IP Address Information About the SOSC Board
4. Take a screenshot and save the queried information.

2.2.4 Collecting the Connection Information About Optical

Interfaces
This procedure describes how to run commands to log in to the SOSC board and collect
the connection information about and status of each interface.
Steps
1. On the desktop, select Start > Run. The Run dialog box is displayed. Enter cmd and
press Enter. The DOS command window is displayed.
2. Run the telnet NE IP address command. The login window is displayed.
3. Enter if -a and press Enter. The information about each interface is displayed, see
Figure 2-9.
2-14

Figure 2-9 Querying the Interface Connection Information About the SOSC Board
1. IP address of the slot 4. IP address of electrical 7. Optical monitoring

2. IP address of electrical interface 3 interface 2
interface 1 5. IP address of electrical 8. Optical monitoring
3. IP address of electrical interface 4 interface 3
interface 2 6. Optical monitoring 9. Optical monitoring
interface 1 interface 4
4. Take a screenshot and save the queried connection information.

2.3 Board Information Collection

2.3.1 Collecting Board Version Information
This procedure describes how to collect the current PCB version information, FEGA
version information, and software version information about a board on an NE.
Context
During the software and hardware version query of a board, the U31 queries only the major
version number by default. By modifying the configuration file, you can query complete
board version information including the major and minor version numbers.
1. Open the \ums-client\procs\ppus\bn.ppu\bn-core.pmu\ica

n-clnt-boardview.par\conf\ini\BoardviewConf.ini file, find
ZTEBoardVerDetail=false, change false to true, and save the file.
2. Re-open the board view window. The complete version information about the board
is displayed.
2-15

Steps
1. In the Topology Management window, double-click the NE that you want to query.
The Rack Chart window is displayed.
2. Right-click the board that you want to query, and select Board Current Version from
the shortcut menu. The Board Current Version dialog box is displayed.
3. View PCB Version Information, FPGA Version Information, and Software Version
Information of the selected board, see Figure 2-10.
Figure 2-10 Querying Board Version Information
4. (Optional) During the software and hardware version query of a board, the U31 queries
only the major version number by default. By modifying the configuration file, you
can query complete board version information including the major and minor version
numbers.
a. Open the BoardviewConf.ini configuration file in the directory \ums-client\p
rocs\ppus\bn.ppu\bn-core.pmu\ican-clnt-boardview.par\conf\i
ni, find the ZTEBoardVerDetail=false line, change false to true, and save the file.
b. Re-open the Board Current Version dialog box. The complete version
information about the board is displayed.
5. Take a screenshot and save the queried version information about the board.
2-16

2.3.2 Collecting Agent Log Information

You can run commands or use a tool to collect log information. This procedure describes
how to use a tool to collect the Qx interface messages, S interface messages, basic APP
report log information about the SD card on the SNP board.
Steps
1. Right-click the log tool, and select Edit from the shortcut menu. The log tool file is
displayed, see Figure 2-11.
Figure 2-11 Log Tool File
2. Change the IP address 192.100.10.1 to the IP address used to log in to the NE, and
then save the file.
3. Double-click the log tool to run it, see Figure 2-12.
2-17

Figure 2-12 Running the Log Tool
The tool automatically exports the log information about the Qx interface messages, S
interface messages, and basic APP messages in the SD card, and then saves them
in the directory of the log tool.
Note:
QxMsg.ozip is the information about Qx interface messages. SMsg.ozip is the
information about S interface messages. APPMsg.ozip is the information about basic
APP messages.
2.3.3 Collecting the CPU Usage Information About a Board

This procedure describes how to collect the CPU usage information about a board.
If you can ping a board successfully, you can run a command to log in to the board and
view its CPU usage information automatically reported by the system.
Steps
2. Run the telnet NE IP address 9023 command. The login window is displayed.
3. Enter the username (admin) and password (admin).
4. Observe the CPU usage information automatically reported by the system.
2-18

5. Take a screenshot and save the CPU usage information about the board.
2.4 Protection Switching Information Collection

The protection methods of the ZXONE 9700 include OP protection and ODUK 1+1
protection.
l The OP protection processing unit is the APS module on the WASON sub-board of
the SNP board.
The common commands of this protection method are docmd 0991 A1, A4, A5, AF,
D3, D4, and D5
You can run one of these commands to query the configuration, status, and APS
messages of the corresponding protection group. However, you cannot run the
commands to set parameters.
l For the ODUK 1+1 protection method, the APS components originally integrated on
the SNP board are integrated on the APP of the service board. You can log in to the
service board and run a common command to query the configuration, status, and
APS messages of the corresponding protection group.
2.4.1 OP Protection Information Collection

2.4.1.1 Logging In to the APS Module
This procedure describes how to run commands to log in to the APS module, and you can
also run commands to query the parameters and status of protection groups.
Steps
2. Run the telnet WASON IP address 9023 command. The login window is displayed.
Note:
You can add 1 to the end of the IP address of the SNP board to obtain the IP address
of the WASON module
3. Enter the username (admin) and password (admin), and press Enter to log in to the
APS module, see Figure 2-13.
2-19

Figure 2-13 Logging In to the APS Module
Note:
If ZTE+ is displayed, it means that the pshell window is displayed. You can run a
query command to collect OP protection information.
If KSH> is displayed, it means that the kshell window is displayed. You can run the
enterpsh command to open the pshell window.
You can switch between the pshell and kshell windows by running the enterksh and
enterpsh commands.
2.4.1.2 Querying the Configuration Information About a Protection Group

This command queries the configuration information about a protection group, including
the properties and service configurations of the protection group.
Syntax
docmd 0991 D3
Function
Queries the configuration information about a protection group, including the properties
and service configurations of the protection group.
Application Scenario
You can use this command to query the actual configuration information about a protection
group, and then compare the information with the preset information to check whether the
protection group is configured properly.
2.4.1.3 Querying the Historical Input Information About the APS Module
This command queries the historical input information about the APS module, including
MCU alarms, E interface messages, and EMS commands.
2-20

Syntax
docmd 0991 A4
Function
Queries the historical input information about the APS module, including MCU alarms, E
interface messages, and EMS commands.
l If a line is faulty, you can run this command to check whether the corresponding
WASON (APS module) receives alarms properly.
l If a line is faulty and the WASON (APS module) receives alarms properly, but
protection switchover fails, you can run this command to check the E interface
messages received by the APS module to check whether the E interface
communicates properly.
l You can run this command to check whether EMS commands are delivered to the
WASON (APS module) properly.
2.4.1.4 Querying the Historical Output Information About the APS Module
This command queries fault alarms and the historical output information about the related
protocols.
Syntax
docmd 0991 A5
Function
Queries the historical output information about the APS module.
l If a line is faulty and the WASON (APS module) receives alarms properly, but
protection switchover fails, you can run this command to check whether the
corresponding APSF sends protocol messages properly.
l After the forced switchover command and other commands are executed, you can run
this command to check whether the WASON (APS module) sends protocol messages
properly.
2.4.1.5 Clearing All Historical Input and Output Information

During system maintenance, you need to clear all historical information before querying
historical input and output information.
Syntax
docmd 0991 AF
2-21

Function
Clears all historical input and output information.
If you need to check whether the receiving and sending mechanism of the WASON (APS
module) is configured properly during system maintenance, you need to run this command
to clear all the historical information before you run the docmd 0991 A4 command to query
the historical input information about the APS module and the docmd 0991 A5 command
to query the historical output information about the APS module.
2.4.1.6 Querying the Switching Status of a Ring Protection Group

This command queries the switching status of a protection group.
Syntax
docmd 0991 A1+ protection group ID
Function
Queries the switching status of the specified protection group.
Note:
There is no character between the command code A1 and the protection group ID. The
protection group ID is a 4-byte hexadecimal number.
If a line is faulty, you can run this command to check whether the switching status of the
protection group is correct.
Result
The command output contains the channel status, signaling information, and node status
of the protection group.
l The channel status and signaling information are provided for R&D personnel for
debugging,
l During operation maintenance, you must focus on the node status of the protection
group:
à ASatus indicates the switching status in direction A.
à BSatus indicates the switching status in direction B.
à 0x01 indicates the idle status.
2-22

à 0x02 indicates the straight-through status.

à 0x03 indicates the switching status.
2.4.1.7 Querying the Important Data of the APS Module

This command queries the important data of the APS module.
Syntax
docmd 0991 D4
Function
Checks whether the important data of the APS module is set properly.
2.4.1.8 Clearing the Configuration Information About All Protection Groups

During system maintenance, you need to clear the configuration information about
protection groups.
Syntax
docmd 0991 E5
Function
Clears the configuration information about all protection groups.
During system maintenance, you can use this command to clear the configuration
information about protection groups.
2.4.2 ODUK 1+1 Protection Information Collection

2.4.2.1 Logging In to the APS Module of the Service Board
This procedure describes how to run commands to log in to the APS module of the service
board, and you can also run commands to query the parameters and status of protection
groups.
Steps
2. Run the telnet NE IP address command. The login window is displayed.
3. Enter the username (admin) and password (adminby).
4. Run the telnet service board IP address 9023 command.
2-23

5. Enter the username (admin) and password (admin), and press Enter to log in to the
APS module, see Figure 2-14.
Figure 2-14 Logging In to the APS Module
Note:
If ZTE+ is displayed, it means that the pshell window is displayed. You can run a
query command to collect OP protection information.
If KSH> is displayed, it means that the kshell window is displayed. You can run the
enterpsh command to open the pshell window.
You can switch between the pshell and kshell windows by running the enterksh and
enterpsh commands.
2.4.2.2 Querying the APS Version

This command queries the APS version information about the service board.
Syntax
aps_version()
Function
Queries the APS version information about the service board.
2.4.2.3 Querying the Configuration Information About a Protection Group

This command queries the configuration information about a protection group, including
the properties and service configurations of the protection group.
Syntax
aps_showpg()
2-24

Function
Queries the configuration information about a protection group, including the properties
and service configurations of the protection group.
You can use this command to query the actual configuration information about a protection
group, and then compare the information with the preset information to check whether the
protection group is configured properly.
2.4.2.4 Querying the Historical Input Information About the APS Module
This command queries the historical input information about a board, including PCC
signaling, S interface signaling, odua overhead, and alarms.
Syntax
aps_showinput()
Function
Queries the historical input information about a board, including PCC signaling, S interface
signaling, odua overhead, and alarms.
2.4.2.5 Querying the Historical Output Information About the APS Module
This command queries the historical output information about a board, including PCC
signaling, S interface signaling, odua overhead, and alarms.
Syntax
aps_showinput()
Function
Queries the historical output information about a board, including PCC signaling, S
interface signaling, odua overhead, and alarms.
2.4.2.6 Clearing All Historical Input and Output Information

During system maintenance, you need to clear all historical information before querying
historical input and output information.
Syntax
aps_clear()
Function
Clear all historical information.
2-25

2-26

Chapter 3
U31 Fault Information
Collection
For U31 faults, you need to collect fault background information, client logs, server logs,
large files, and database logs.
The fault information collection tool of the U31 uses a one-click method to collect computer
configuration files, EMS configuration files, EMS log files, stack files, and dump files.
With this method, faults can be easily located but the backup data of the EMS cannot be
collected.
This tool can be divided into the following two parts:
1. One-click fault information collection tool on the client

This tool can collect the information on both the client and server or independently
collect the information on the client or server. To use this tool to collect the information
on the server, ensure that the server is operating properly.
2. One-click fault information collection tool on the server
This tool can collect only the information on the server.
Table of Contents
Fault Background Information Collection ...................................................................3-1
Collecting Client Logs and Large Files .......................................................................3-2
Server Log and Large File Collection .........................................................................3-4
Collecting Database Logs ........................................................................................3-10
3.1 Fault Background Information Collection

Fault background information includes the operating system and version of the EMS,
network structure, IP configuration, NE quantity and distribution, and interface information.
All these information is the basic information for troubleshooting.
EMS Operating System and EMS Version Collection

l For how to collect the operating system information about the EMS, refer to 2.1.2.
l For how to collect EMS version information, refer to 2.1.1.
3-1

Network Structure Information Collection

EMS network structure and interconnection structure involves the distribution of the client
and server, connections between the EMS and devices, connection between the NMS and
EMS, installation of interfaces, and connections between EMS layers.
IP Configuration Information Collection

The network configuration information about the EMS server includes IP address
configuration information and route configuration information.
NE Quantity and Distribution Information Collection

The management network information about the EMS includes the total number of NEs,
the types and number of devices, and the types, number, and distribution of main services.
An NE access method means how the NE is accessed. For example, the NE is accessed
through a local computer, the DCN, or another NE.
Interface Information Collection

Interface information includes: whether the EMS is configured to active/standby
synchronization, active/standby connection mode and configuration information, manager
ID, process enabling status, connection mode provided by the northbound interface, and
integrated EMS information.
3.2 Collecting Client Logs and Large Files

This procedure describes how to collect logs and large files on the U31 client, including
operation log records, dump files, and thread stack files.
Context
l If you need to collect only client information, click only the Client tab.
l Client information can be collected through the remote desktop.
l Fault information can be collected no matter whether the EMS client is operating.
l When the EMS client and server are installed on the same computer or different
computers, the procedures to collect client logs and large files are the same.
Steps
1. On the client, double-click the information collection tool \ums-client\umd.bat.
The Fault Info Quick Collection Tool window is displayed.
2. Click the Client tab, see Figure 3-1.
3-2

Chapter 3 U31 Fault Information Collection
Figure 3-1 Fault Info Quick Collection Tool on the Client (Client Tab)
3. Set the parameters. For a description of the parameters, refer to Table 3-1.
Table 3-1 Parameter Descriptions for the Fault Collection Configuration on the
Client
Time set Begin time and End time: Estimate the period in accordance
with the fault occurrence time.
The collected logs stored in other paths can also be collected
if they are within this period.
This parameter sets the period to collect data.
File type Big file (dump, Dump files and thread stack files are included.
stack) By default, this check box is not selected.
If the system is down, the process is suspended, memory is
abnormal, or the process is restarted, dump files or memory
stack files are required. In this case, large files need to be
collected.
Collection result save path Path to store collected data.

After the collection, you can query the collected files in this path.
3-3

4. Click the Collect button to collect fault information and compress it into a file.
You can query and copy the collected files in the preset storage path.
3.3 Server Log and Large File Collection

Server logs and large files can be collected with the following two tools:
l One-click fault information collection tool on the client

This tool can independently collect the information on the server. To use this tool to
collect the information on the server, ensure that the server is operating properly.
l One-click fault information collection tool on the server
This tool can collect only the information on the server.
3.3.1 Collecting Server Information With the Client Tool

This procedure describes how to use the one-click fault information collection tool on the
client to collect server information through the IP address of the server.
Steps
1. On the client, double-click the information collection tool \ums-client\umd.bat.
The Fault Info Quick Collection Tool window is displayed.
3-4

2. Click Server. The Server tab is displayed. If the EMS client and server are installed
on the same computer, set Server address to 127.0.0.1, see Figure 3-2.
Figure 3-2 Collecting Server Information With the Client Tool 1
3. (Optional) If the EMS client and server are installed on different computers, set Server
address in accordance with the IP address of the computer where the EMS server is
installed, see Figure 3-3.
3-5

Figure 3-3 Collecting Server Information With the Client Tool 2
Table 3-2 Parameter Descriptions for Fault Collection Configuration (Client Tool)
Server address If the EMS client and server are installed on the same
computer, set Server address to 127.0.0.1.
If the EMS client and server are installed on different

computers, set Server address in accordance with the IP
address of the computer where the EMS server is installed.
Time set Begin time and End time: Estimate the period in
accordance with the fault occurrence time.
The collected logs stored in other paths can also be
collected if they are within this period.
3-6

File type Process file Collects process configuration files and log files in the
works directory, including global configuration files and
the configuration files and log files of the console.
If this check box is not selected, all files are collected by
default, including the other configuration files of the EMS.
Big file (dump, Dump files and thread stack files are included.
If the system is down, the process is suspended, memory
is abnormal, or the process is restarted, dump files or
memory stack files are required. In this case, large files
need to be collected.
Get Process List Collects the related data of the specified EMS process.
By default, the related data of all EMS processes is
collected.
This function can be enabled only if the EMS is started.

After the collection, you can query the collected files in
this path.
3-7

3.3.2 Collecting Server Information With the Server Tool

This procedure describes how to use the one-click fault information collection tool on the
server to collect server information, including operation log records, dump files, and thread
stack files of the U31 server.
Context
l The system supports server information collection through the remote desktop.
l Server information can be collected manually no matter whether the server is operat-
ing.
l The collected information is stored in the \ums-server\rundata\umd\output\m
anual directory, which cannot be changed.
Steps
1. On the server, double-click the information collection tool \ums-server\umd.bat.
The Fault Info Quick Collection Tool window is displayed, see Figure 3-4.
Figure 3-4 Fault Info Quick Collection Tool on the Server
3-8

Table 3-3 Parameter Descriptions for Fault Collection Configuration (Server Tool)
Time set Begin time and End time: Estimate the period in
accordance with the fault occurrence time.
The collected logs stored in other paths can also be
collected if they are within this period.
File type Process file Collects process configuration files and log files in the
works directory, including global configuration files and
the configuration files and log files of the console.
If this check box is not selected, all files are collected by
default, including the other configuration files of the EMS.
Big file (dump, Dump files and thread stack files are included.
If the system is down, the process is suspended, memory
is abnormal, or the process is restarted, dump files or
memory stack files are required. In this case, large files
need to be collected.
Get Process List Collects the related data of the specified EMS process.
By default, the related data of all EMS processes is
collected.
This function can be enabled only if the EMS is started.

After the collection, you can query the collected files in
this path.
3-9

3.4 Collecting Database Logs

This procedure describes how to collect database logs including operation logs, system
logs, and security logs.
Steps
1. In the main window of the U31, select Maintenance > System Backup and Restore.
The System Backup and Restore window is displayed.
2. Select Backup > Backup and Deletion Log Data from the Backup and Restore
navigation tree in the left pane, the log data backup and deletion area is displayed in
the right pane.
3. Set the parameters as required. In this example, set Backup and Deletion Operation
to Backup Only and select the Operation Log, System Log, and Security Log check
boxes.
Parameter Range Description
Backup and Backup Only, Backup and l Backup Only: Only the data within the
Deletion Deletion, and Deletion Only specified period is backed up.
Operation Backup and Deletion: The data within
the specified period is backed up and
deleted at the same time.
l Deletion Only: Only the data within the
specified period is deleted.
The specified period for data is selected
from the Backup Filter Type list and the
specified period for deletion is selected from
the Deletion Filter Type list.
Backup and Operation Log, System Log, Select one or multiple items that you want to
Deletion and Security Log back up and delete.
Operation
Content
Backup Filter All, Latest T Day(s), T Day(s) Execution period for data backup.
Type Ago, Latest T Month(s), and T For example, if Latest T Day(s) is selected, it
Month(s) Ago means that the data within the latest T days
needs to be backed up. T is set in the T Time
text box.
Deletion All, Latest T Day(s), T Day(s) Execution period for data deletion.
Filter Type Ago, Latest T Month(s), and T For example, if Latest T Day(s) is selected, it
Month(s) Ago means that the data within the latest T days
needs to be deleted. T is set in the T Time
text box.
3-10

Note:
The filter conditions use the server time zone as the start point.
4. (Optional) To change the path to store the backup files on the server, click the Browse
button next to the Backup File Save Path at Server or Remote Server text box.
5. (Optional) To download backup files to the client, click the Browse button next to the
Backup File Download Path at Client text box to set the path on the client.
Note:
If the Backup File Download Path at Client check box is selected, backup files are
stored on the server and client at the same time.
6. Click the Execute button.
Note:
The backup progress is displayed in the Execution Result area until the operation is
completed.
You can view and copy backup files in the preset storage path.
3-11

3-12

Glossary
APS
- Automatic Protection Switching
CPU
- Central Processing Unit
EMS
- Element Management System
MCU
- Module Control Unit
NMS
- Network Management System
OP
- Optical Protection Unit
PCC
- Protection Communication Channel
WASON
- WDM/OTN Automatic Switched Optical Network

ZXONE Fault Information Collecting - V1.0

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

ZXONE Fault Information Collecting - V1.0

Diunggah oleh

Hak Cipta:

ZXONE 9700

Packet OTN Equipment

Revision No. Revision Date Revision Reason

R1.0 2016-04-01 First edition

Serial Number: SJ-20160303094203-013

Publishing Date: 2016-04-01(R1.0)

SJ-20160303094203-013|2016-04-01(R1.0) ZTE Proprietary and Confidential

Chapter 2 Equipment Fault Information Collection ................................ 2-1

Chapter 3 U31 Fault Information Collection ............................................ 3-1

SJ-20160303094203-013|2016-04-01(R1.0) ZTE Proprietary and Confidential

SJ-20160303094203-013|2016-04-01(R1.0) ZTE Proprietary and Confidential

What Is in This Manual

Chapter 1, Overview Describes the meaning of information

Chapter 2, Equipment Fault Information Collection Describes how to collect maintenance

Danger: indicates an imminently hazardous situation. Failure to comply can result in

Warning: indicates a potentially hazardous situation. Failure to comply can result in

Caution: indicates a potentially hazardous situation. Failure to comply can result in

Note: provides additional information about a topic.

SJ-20160303094203-013|2016-04-01(R1.0) ZTE Proprietary and Confidential

SJ-20160303094203-013|2016-04-01(R1.0) ZTE Proprietary and Confidential

1.1 Meaning of Information Collection

1.2 Information Collection Range

Table 1-1 Information Collection and Feedback Form

Collection Type Fault Type Collected Information Remarks

Equipment fault Operation and Detailed version of the EMS -

Disk usage of the EMS -

Upload comparison of EMS -

Data backed up through the The username and

SJ-20160303094203-013|2016-04-01(R1.0) ZTE Proprietary and Confidential

Collection Type Fault Type Collected Information Remarks

Data backed up through the The username and

Monitoring Monitoring information -

IP information about the -

Service board Board version information Detailed board

Agent log information -

CPU usage of boards -

Protection OP protection information -

ODUK 1+1 protection -

APS module login -

APS historical input -

APS historical output -

Historical input and output -

U31 fault collection EMS Fault background information -

Client logs and large files -

Server logs and large files -

SJ-20160303094203-013|2016-04-01(R1.0) ZTE Proprietary and Confidential

2.1 Maintenance Information Collection

SJ-20160303094203-013|2016-04-01(R1.0) ZTE Proprietary and Confidential

Figure 2-1 U31 Version

Figure 2-2 Version Information and Patch Versions of Modules

SJ-20160303094203-013|2016-04-01(R1.0) ZTE Proprietary and Confidential

2.1.2 Collecting the Operating System Information About the EMS

Figure 2-3 Operating System Information About the EMS Server

SJ-20160303094203-013|2016-04-01(R1.0) ZTE Proprietary and Confidential

2.1.3 Collecting the Disk Usage of the EMS Server

Figure 2-4 Disk Usage Information About the EMS Server

SJ-20160303094203-013|2016-04-01(R1.0) ZTE Proprietary and Confidential

2.1.4 Collecting Alarm Information

Figure 2-5 Right-Click Menu

2. Take a screenshot and save the queried alarm information.

2.1.5 Collecting Performance Information

SJ-20160303094203-013|2016-04-01(R1.0) ZTE Proprietary and Confidential

1. In the Topology Management window, right-click one or multiple NEs, and

Table 2-1 Descriptions of the Parameters on the Index/Counter Selection Tab

Common template Select a self-contained or user-defined common template from

MO type Keep the default setting (checkpoint).