ZXONE Fault Information Collecting - V1.0
ZXONE Fault Information Collecting - V1.0
ZXONE Fault Information Collecting - V1.0
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
Glossary .......................................................................................................... I
II
Intended Audience
This manual is intended for:
l Debugging engineers
l EMS monitoring personnel
l Maintenance engineers
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.
II
Alarm information -
Performance information -
Log information -
1-1
NE monitoring information -
Connection information -
about optical interfaces
Configuration information -
about protection groups
Database logs -
1-2
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
3. On the Information tab, view the detailed version information and patch version of
each module, see Figure 2-2.
2-2
4. Take a screenshot and save the queried version information about the U31.
– End of Steps –
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.
2-3
3. Take a screenshot and save the queried operating system version and patch
information about the EMS server.
– End of Steps –
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.
4. Take a screenshot and save the queried disk usage information about the EMS server.
– End of Steps –
2-4
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.
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.
2. On the Index/Counter Selection tab, set the parameters. For a description of the
parameters, refer to Table 2-1.
Parameter Description
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
parameters, refer to Table 2-2.
Parameter Description
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
Parameter Description
4. On the Time Selection tab, set the parameters. For a description of the
parameters, refer to Table 2-3.
Parameter Description
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.
– End of Steps –
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.
– End of Steps –
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.
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
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.
– End of Steps –
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.
– End of Steps –
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.
Parameter Description
DBMS Type l For Windows, select SQL Server from the drop-down list.
l For Linux, select Oracle from the drop-down list.
2-10
Parameter Description
5. (Optional) Enter the backup file name in the Name text box.
Note:
Only the Basic Data check box needs to be selected. The other option are used for
fault location.
2-11
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.
– End of Steps –
2-12
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.
– End of Steps –
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
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
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.
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.
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.
– End of Steps –
2-16
Steps
1. Right-click the log tool, and select Edit from the shortcut menu. The log tool file is
displayed, see Figure 2-11.
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
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.
– End of Steps –
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 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.
– End of Steps –
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.
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 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
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.
– End of Steps –
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.
Application Scenario
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.
Application Scenario
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.
Syntax
docmd 0991 AF
2-21
Function
Clears all historical input and output information.
Application Scenario
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.
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.
Application Scenario
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
Syntax
docmd 0991 D4
Function
Checks whether the important data of the APS module is set properly.
Syntax
docmd 0991 E5
Function
Clears the configuration information about all protection groups.
Application Scenario
During system maintenance, you can use this command to clear the configuration
information about protection groups.
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 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.
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.
– End of Steps –
Syntax
aps_version()
Function
Queries the APS version information about the service board.
Syntax
aps_showpg()
2-24
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.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.
Syntax
aps_clear()
Function
Clear all historical information.
2-25
2-26
3-1
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.
3-2
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
Parameter Description
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.
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.
– End of Steps –
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.
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
4. Set the parameters. For a description of the parameters, refer to Table 3-2.
Table 3-2 Parameter Descriptions for Fault Collection Configuration (Client Tool)
Parameter Description
Server address If the EMS client and server are installed on the same
computer, set Server address to 127.0.0.1.
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.
3-6
Parameter Description
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.
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.
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.
5. 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-7
– End of Steps –
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.
3-8
2. Set the parameters. For a description of the parameters, refer to Table 3-3.
Table 3-3 Parameter Descriptions for Fault Collection Configuration (Server Tool)
Parameter Description
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 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.
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.
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.
3. 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.
– End of Steps –
3-9
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.
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.
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.
– End of Steps –
3-11
3-12