NetNumen U31 R22 (V12.15.10) Routine Maintenance Guide - V1.0
NetNumen U31 R22 (V12.15.10) Routine Maintenance Guide - V1.0
NetNumen U31 R22 (V12.15.10) Routine Maintenance Guide - V1.0
Version: 12.15.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: [email protected]
LEGAL INFORMATION
Copyright © 2014 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 Maintenance engineers
l Network monitoring engineers
Chapter 2, Daily Maintenance Describes the checking items for daily maintenance.
Chapter 3, Weekly Maintenance Describes the checking items for weekly maintenance.
Chapter 4, Monthly Maintenance Describes the checking items for monthly maintenance.
Chapter 5, Annual Maintenance Describes the checking items for annual maintenance.
Conventions
This manual uses the following conventions.
Italics Variables in commands. It may also refer to other related manuals and documents.
Bold Menus, menu options, function names, input fields, option button names, check boxes,
drop-down lists, dialog box names, window names, parameters, and commands.
II
l Routine Maintenance
U31 R22 provides an alarm and notification system. Some low-level alarms and faults
can be corrected by the system automatically without manual intervention.
l Troubleshooting
Troubleshooting means to analyze and correct a fault after the fault is reported.
1-1
Removing dust.
1-2
Flow Description
1. Making routine maintenance schedules
Complying with the cycle of each maintenance item, maintenance personnel make
routine maintenance schedules of the next year at the end of this year.
2. Checking routine maintenance items
Maintenance personnel check each routine maintenance item described in this manual
at a proper time.
Note:
It is recommended to check items during non-peak hours, for example, 02:00 to 06:00.
3. Troubleshooting
1-3
a. If the fault affects services. For example, some services cannot be implemented,
handle the fault immediately because it is urgent and critical.
b. If the fault affects operation and maintenance rather than services. For example,
new service commissioning failures or configuration failures, handle the fault in
accordance with the general troubleshooting flow because it is critical but not
urgent.
c. If some alarms are raised, but services, operation, and maintenance are not
affected, pay attention to the fault, and handle the fault in accordance with the
general troubleshooting flow.
If a fault occurs, maintenance personnel handle the fault in accordance with the general
troubleshooting flow. If the fault persists, contact ZTE technical support. Some typical
troubleshooting methods are described below:
l Causes of a fault may be hard to be identified, or a fault occurs casually.
Maintenance personnel should pay attention to the fault, and troubleshoot the
fault in time.
l For a hardware fault hard to be resolved, contact ZTE technical support for spare
parts for convenience of part replacement.
l For a possible software or data fault, back up the corresponding software or data
before software upgrade and data modification for convenience of data check and
restoration.
1-4
l Prepare common tools and instruments, such as screw drivers (straight and
cross), signaling instrument, network cable pliers, multimeter, AC power supply for
maintenance purpose, telephone cable, and network cable. Calibrate instruments
periodically to ensure accuracy.
l Check spare parts periodically to ensure that they are sufficient and in good condition,
and prevent moisture and mildew. Store spare parts and faulty parts separately after
replacement. Supplement common spare parts when they are exhausted. Repair
faulty boards in time and ensure sufficient spare parts for major boards.
l Keep necessary software and materials handy.
l Keep normal temperature and humidity in the equipment room. Keep the equipment
room clean and prevent dust, moisture, rats and insects from entering the equipment
room. The equipment room environment must meet the requirements of the
Environment Acceptance Report.
l Ensure reliable and stable power supplies. Check system grounding and lightning
protection ground periodically, especially before thunderstorm seasons and after
storms.
l Repair broken lamps in time, and do not leave any dark places in the equipment room.
l Perform routine tests and inspections every day in accordance with suggestions
described in this manual, and make records.
l Troubleshoot faults in time after finding them. If a fault is complicated, record original
information, and contact ZTE technical support.
l Put contact information of ZTE technical support in a striking place for timely contact.
Update the latest contacts periodically.
1-5
1-6
Steps
1. In the NMS main window, select Topology > View Topology. The Topology
Management window is displayed.
2. Query the status of an NE in the network topology or NE tree.
l If the NE icon is in green, this NE is operating properly without alarms.
l If alarms of multiple levels occur, the NE icon is displayed in the same color as
the alarm of the highest level.
Move the cursor to the icon to query the alarm levels and number of alarms.
l Icons shows NE statuses.
Detailed icon status meanings are displayed in the Legend area, see Figure 2-1.
By default, the Legend area is not displayed. To display the area, click on the
toolbar.
2-1
Steps
1. In the NMS main window, select Fault > Alarm Monitoring. The Alarm Monitoring
tab is displayed, see Figure 2-2.
2-2
2. Query the current alarms and historical alarms in a day. Focus on critical alarms, link
disconnection alarms, and high CPU/memory/hard disk usage alarms.
3. Select the NE in the NE column to view the corresponding rack diagram.
4. Double-click an alarm to query the detailed information.
5. Click the Handling Suggestions tab to query the troubleshooting suggestions.
6. On the Alarm Monitoring tab, click the drop-down list next to the icon and then
select the to export all rows of the alarm information, or click the icon to export
visible cows of the alarm information.
You can export files in the formats of text, Excel, PDF, HTML, and CSV.
7. In the displayed Save dialog box, enter the user name and select the file type, and
then click Save.
– End of Steps –
Steps
1. In the NMS main window, select Maintenance > System Monitoring. The System
Monitoring window is displayed, see Figure 2-3.
2-3
2. Select the corresponding NMS under Server. Click View in the View Server
Performance area. The View Application Server Performance window is
displayed.
3. Query the CPU and memory usage.
The duration when the instant peak value of the CPU usage exceeds 90% must not
exceed 10 seconds. After an operation, the CPU usage must be decreased to the
normal range. The memory usage must be lower than 80%.
If the subscriber capacity exceeds the designed value, and the CPU usage and
memory usage are high for a long time, this indicates that the system load is high
and capacity expansion is required.
If the subscriber capacity does not reach the designed value, but the CPU usage and
memory usage are frequently high, contact ZTE technical support for assistance.
– End of Steps –
Steps
1. In the U31 R22 client main window, run ems\ums-server\console.exe. The
NetNumen U31 Unified Network Management System - Console window is
displayed.
2-4
Steps
1. Check the disk space to ensure that sufficient space is available.
2. Check whether any fault occurs on the disks, for example, read or write error.
– End of Steps –
Result
l If the disk array space is not enough, add more disks, or back up alarm and
performance data and then delete the data to release some space.
l If a hard disk fault is found, contact ZTE technical support for assistance.
Note:
The time zone and time of the operating system can only be modified before the NMS is
started.
2-5
Steps
1. In the Windows operating system, select Start > Control Panel > Date and Time.
The Date and Time window is displayed.
2. Check the system time zone. If the system time zone and the local time zone are
different, click Change time zone to change the system time zone to the local time
zone.
The system time zone must be modified to the local time zone. Otherwise, alarm
generation time is different from that displayed on the NMS.
3. Synchronized the operating system time to the standard clock source.
– End of Steps –
2-6
Prerequisite
An NE performance task is created in the NMS.
Steps
1. In the NMS main window, select Performance > Measurement Task Management.
The Measurement Task Management window is displayed.
2. Select an NE, the NE measurement task is displayed on the right pane, see Figure
3-1.
3-1
3. Right-click the measurement task, and select Query PM Data by Task from the
shortcut menu. The History Performance Data Query window is displayed.
4. Click the Object Selection tab, and select Group by NE from the Location group
list, see Figure 3-2.
5. Click the Time Selection tab, and set Query granularity and Time settings, see
Figure 3-3.
a. In the NMS main window, select Performance > Data Integrity Query. The Add
Data Integrity Query window is displayed.
b. Select the desired options from the NE type and MO type lists, see Figure 3-4.
3-2
Note:
NE type and MO type must be the same as those set in the measurement task.
c. Click the Location Selection tab, and select an NE, see Figure 3-5.
Note:
The NE must be the same as that selected in the measurement task.
d. Click the Time Selection tab, and set the time range to check the performance
data integrity.
e. Click OK.
The Integrity Status column shows the data integrity of each NE.
3-3
l Have Data means that the performance data at each collection point (every
15 minutes by default) during the query period can be queried.
l No Data means that no performance data at each collection point is queried.
Suppose the query period is a day. If the system can query the performance
data at collection points during one period (00:00:00 to 12:00:00), but fails to
query performance data at collection points during the other period (12:00:00 to
00:00:00), the integrity query result will be displayed on two rows, with the Integrity
Status as Have Data and No Data respectively.
If No Data is displayed in the Integrity Status column, check whether:
i. The task is suspended manually.
ii. The task end time expires.
iii. The start time and end time of the task are set correctly.
Steps
1. In the NMS main window, select Maintenance > System Monitoring. The System
Monitoring window is displayed, see Figure 3-6.
2. Select Application Server. Click View in the View Server Performance area. The
View Application Server Performance window is displayed.
3-4
You should pay much attention to the usage of hard disks where the operating system,
the U31 R22, and the database are installed.
4. Close the View Application Server Performance window. The System Monitoring
window is displayed.
5. In the Monitor Server Performance area, click Configure to set whether to monitor
hard disk space, see Figure 3-8.
If HD Monitoring is selected, the hard disk monitoring threshold must be set as follows:
l Type: Percentage, Absolute, and NO.
l Threshold: Set the threshold based on monitoring type. If the hard disk
usage (percentage or absolute value) exceeds this threshold, an alarm of the
corresponding level (critical, major, minor, and warning) is raised.
l Monitoring Period: hard disk monitoring period, unit: second.
The recommended free space on each server is described as follows:
l The remaining space of the disk C must be larger than 5 GB or cannot be less
than 10% of the total hard disk space. The bigger one between 5 GB and 10%
should be taken.
l For the SUN server, the file system does exceed 85%, and the root file system
does not exceed 70%.
3-5
l The remaining space of dual RAID is not less than 10% of the entire hard drive
capacity.
l The remaining space of the disk where the server data is stored should be 5 GB
above, or no less than 10% of the entire hard drive capacity.
Troubleshooting suggestions are described as follows:
i. Insufficient space of partition C used by the Windows operating system may be
caused by virus infection or large logs of the antivirus software. It is recommended
to update the virus library, check all the partitions of the server for virus, and delete
the logs of antivirus software.
ii. If the hard disk where the data files and log files are saved has no enough space,
delete some unnecessary files in the hard disk to release some space. At the
same time, some operations on the database are required, such as backup of the
alarm database and performance database, and deletion of historical data.
iii. If the alarm persists, contact ZTE technical support for assistance.
– End of Steps –
Steps
1. In the NMS main window, select Maintenance > System Monitoring. The System
Monitoring window is displayed, see Figure 3-9.
3-6
2. Select the corresponding database under Database, and click View in the View
Database Resouce area. The View Database Resources window is displayed.
Query the database information.
Data Space Free Percent of each database must be larger than 5%, and the database
size is normal.
3. Close the View Database Resources window. The System Monitoring window is
displayed.
4. In the Monitor Server Performance area, click Configure to set whether to monitor
the database space, see Figure 3-10.
5. (Optional) If the database space is insufficient, this procedure uses the MSSQL Server
2008 as an example to describe related operations.
a. Clear unused alarms and performance data.
i. In the NMS main window, select Maintenance > System Backup and
Restore. The System Backup and Restore window is displayed.
ii. Select Backup and Deletion Log Data, Backup and Deletion Alarm Data,
and Backup and Deletion PM Data in Backup for data backup and deletion.
The MSSQL database space is not freed after mass data is cleared. The
database must be shrunk to free the occupied space.
Caution!
Before shrinking the database, you should terminate the network management
services.
3-7
iv. Right-click UEP4X_CAF_FM, and select Properties from the shortcut menu.
The Database Properties window is displayed.
v. Select Options in the left navigation tree, and modify Recovery model in the
right pane to Simple, see Figure 3-12. Remember the original mode for mode
retrieval.
3-8
viii. The Shrink Database window is displayed. Click OK to shrink the database.
ix. After shrinking the database, right-click UEP4X_CAF_FM, and select
Properties from the shortcut menu. The Database Properties window is
displayed. Check the database remaining space.
3-9
ii. Right-click UEP4X, and select Properties from the shortcut menu. The
Database Properties window is displayed. Select Files, see Figure 3-15.
iii. Click the button in the row where File Type is Rows Data. The Change
Autogrowth for UEP4X window is displayed.
iv. Select Enable Autogrowth, and set related parameters, see Figure 3-16.
Click OK.
3-10
Set the Autogrowth column where File Type is Log by the same method.
v. Store the data files to other disks. Click Add in the Database Properties
window to add a row in the table, see Figure 3-17.
vi. In the new row, click the button of the Autogrowth column. The Change
Autogrowth dialog box is displayed.
vii. Set the parameters, see Figure 3-18. Click OK.
3-11
viii. Set Logical Name of the data file to uep4x_data2, see Figure 3-19.
ix. In the new row, click the button of the Path column. The Locate Folder
window is displayed. Select a large disk, for example, E:\data, and click OK.
x. Set Logical Name of the data file to uep4x_data2.dbf, see Figure 3-20.
Click OK.
3-12
Steps
1. In the NMS main window, select Maintenance > Task Management > Show Timing
Task. The Task Management window is displayed.
2. Select a task from the left navigation tree, for example, PM Data Backup and Deletion
Task, see Figure 3-21.
3. Click the button to query the task logs, and check whether the task is operating
properly.
4. Click the button to check whether there is any backup task yet to be executed.
If a backup task is operating improperly, verify that the disk space is sufficient and the
network connection is normal. If the fault persists, contact ZTE technical support for
assistance.
3-13
The above figure shows that the performance data is backed up in the \ums-serve
r\rundata\backup\pmbak directory.
– End of Steps –
Note:
Both the virus database and the anti-virus engine must be updated.
Steps
1. Check whether the anti-virus software is installed and updated automatically.
2. Verify that the virus database version is the latest.
– End of Steps –
Steps
1. Perform alarm statistics and analysis on existing alarms.
a. In the NMS main window, select Fault > Alarm Monitoring by NE. The Alarm
Monitoring by NE window is displayed.
The NMS collects statistics on number of alarms of each NE based on alarm
levels. You should pay much attention to critical alarms and alarms that are raised
frequently.
3-14
c. Click the Condition tab, and set the parameters on the Location, Alarm Code,
Time and Others tabs.
d. Click OK. Number of historical alarms of each type is displayed. Pay much
attention to the alarms that are raised frequently.
e. In the left navigation tree, select Fault > History Alarm Busy-Time Statistics.
The History Alarm Busy-Time Statistics window is displayed.
"Busy-Time" means the time when the NMS is busy processing a service. You
may pay much attention to the busy-time alarms.
History Alarm Busy-Time Statistics enable you to only collect statistics on the
historical alarms in busy hours. Similar to basic statistics, you can set mean
duration of alarm statistics or alarm occurrence frequency.
f. On the Basic tab, set Statistic Type, Effective Time, and View Setting, see
Figure 3-24.
3-15
g. Click the Condition tab, and set the parameters on the Location, Alarm Code,
Time and Others tabs.
h. Click OK. Alarm frequency of each period is displayed in the window. Pay much
attention to the alarms that are raised frequently.
– End of Steps –
Steps
1. In the network management window, select Performance > History Performance
Data Query. The History Performance Data Query dialog box is displayed, see
Figure 3-25.
3-16
Steps
1. Use the following commands to check whether error, warning or failure records exist
in messages.
l # more /var/adm/messages|grep error
l # more /var/adm/messages|grep warning
l # more /var/adm/messages|grep fail
2. Use the following commands to check whether error, warning or failure records exist
in Syslog.
l # more /var/log/syslog|grep error
l # more /var/log/syslog|grep warning
l # more /var/log/syslog|grep fail
– End of Steps –
Result
If an error or failure is found in messages or Syslog, check the operation state of
corresponding hardware or software according to the position where the error or failure
occurs.
3-17
Steps
1. In the NMS main window, select Help > License Information > Show License. The
License Information window is displayed. Query the License information.
The License information includes the U31 R22 functions and management scale
information. Different configurations are displayed based on different License files.
2. Query current network status and network scale. If the current network scale is larger
or closed to the License management scale. Apply for a new License file to replace
the old one.
– End of Steps –
3-18
Steps
1. Check the values of the thermometer and hygrometer.
For the temperature and humidity requirements, refer to the following table.
Measure the temperature at a position 1.5 m above the floor and 0.4 m in front of the rack without
front and rear panels.
The short-term operating condition means that the continuous operating period does not exceed 96
hours and the accumulative total period within a year does not exceed 15 days.
If the equipment room temperature does not meet requirements, repair or replace the
air-conditioning system in the equipment room.
If the relative humidity in the equipment room is high, install dehumidification facilities.
if the relative humidity is low, install humidifying facilities.
Verify that there is no sewer pipeline (especially no pipeline connector) passing through
the equipment room.
2. Check the power distribution cabinet, cabinet, shelves, cables, wiring troughs and
other key components.
Fire prevention: All components should be prevented from fire and all fire-fighting
facilities in the equipment room are in good condition.
4-1
Dust prevention: All components should be clean and tidy without apparent dust
attached.
– End of Steps –
Steps
1. In the NMS main window, select Security > Log Management. The Log
Management window is displayed.
2. Double-click a log type, for example, All System Log, check whether there is
information that occurs frequently, mass error information, and operation failure
information, see Figure 4-1.
4-2
– End of Steps –
Steps
1. Check whether the remote maintenance software has been installed on the
maintenance terminal of the U31 R22, such as teamviewer or VNC. Check whether
the maintenance personnel can log in to the remote client or server
2. Check whether the special line is available in the equipment room for remote
maintenance.
– End of Steps –
4-3
4-4
Steps
1. Verify that all power cables, grounding cables and signal cables inside the cabinet are
in good condition without any defect such as damage, aging, corrosion or flash burn.
Note:
Antistatic measures such as use of an antistatic platform with antistatic dress and antistatic
wrist straps must be taken.
To reduce risks, it is recommended that maintenance personnel remove dust under the
guidance of ZTE technical support engineers. The dust removal operation should be
performed when the traffic is low (for example, between 2:00 and 4:00).
5-1
Steps
1. Perform the following steps to clean the dust screen:
i. Disassemble the dust screen from the cabinet, and clean it with water. Dry the
dust screen, and then reinstall it onto the cabinet.
ii. Wipe the cabinet shell with a clean and dry cotton cloth.
iii. Use a vacuum cleaner to remove dust around the air inlets of the cabinet.
2. Perform the following steps to clean the fan shelf:
i. Use a clean cotton cloth, an antistatic soft brush and a vacuum cleaner to remove
dust from fan blades and circuit boards of the backup fan shelf.
ii. Use the backup fan shelf to replace a fan shelf inside the cabinet.
iii. Remove dust from the replaced fan shelf in the same way. The replaced fan shelf
can be used as the backup fan shelf.
iv. Repeat step i. through step iii. to replace other fan shelves inside the cabinet, and
remove dust from these fan shelves.
3. Remove dust from the air conditioner by complying with air conditioner manuals.
– End of Steps –
5-2