NetNumen N31 UNMS (V5.01.01) Administrator Manual

NetNumen N31 (IP Network)
Unified Network Management System

Administrator Manual (Routine Maintenance)
Version 5.01.01
ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: (86) 755 26771900
Fax: (86) 755 26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright © 2010 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 CORPO-
RATION 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 dis-
claimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose, title or non-in-
fringement. 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 ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No. Revision Date Revision Reason

R1.0 2010–08–18 First edition
Serial Number: SJ-20100817155256-007

Contents
About This Manual............................................. I

Maintenance Overview ......................................1
Maintenance Overview .................................................... 1
Maintenance Purpose ...................................................... 1
Maintenance Classification ............................................... 1
Maintenance Items ......................................................... 2
Maintenance Regulations ................................................. 3
Daily Maintenance .............................................5
Checking Temperature in Equipment Room......................... 5
Checking Humidity in Equipment Room.............................. 6
Checking the Running State of the Server .......................... 6
Checking the Running State of Disk Array .......................... 7
Checking Logs in the Window Operation System ................. 7
Checking the Communication Between Server and
Client.................................................................... 8
Checking the CPU/MEM Utilization of the Server.................. 8
Weekly Maintenance ....................................... 11
Backing Up and Deleting Data .........................................11
Calibrating the System Clock...........................................13
Checking Database Space ...............................................13
Checking the Logs of the Database ..................................15
Checking the Hard Disk Space .........................................15
Checking the Logs of the ServerSolaris ......................... 16
Checking the Running State of Dual Servers......................17
Monthly Maintenance ...................................... 19
Checking Performance Data ............................................19
Checking the Remote Maintenance Tool ............................20
Quarterly Maintenance .................................... 21
Checking the Switching Function Between Dual Servers
...........................................................................21
Clearing the Databases ..................................................22
Confidential and Proprietary Information of ZTE CORPORATION I

NetNumen N31 (IP Network) Administrator Manual (Routine Maintenance)
Figures ............................................................ 23
Tables ............................................................. 25
Glossary .......................................................... 27
II Confidential and Proprietary Information of ZTE CORPORATION

About This Manual
About This Manual NetNumen N31 is a network management system used to manage
mobile network elements. It is an intermediate system between
the upper-layer operation support system and lower-layer network
element management systems. By using NetNumen N31, you
can implement the integrated management of network elements,
including configuration management, fault management, perfor-
mance management, security management, log management and
report management. Meanwhile, it provides unified standard in-
terfaces to upper-layer application systems.
This manual provides the maintenance instructions of NetNumen
N31.
Intended � Maintenance Engineers
Audience
� Network Monitoring Engineers
What is in This
Manual Chapter Summary
Chapter 1, Maintenance Overview Introduces the classification,

methods of routine maintenance
Chapter 2, Daily Maintenance Describes the daily maintenance

items of the NetNumen N31
system
Chapter 3, Weekly Maintenance Describes the weekly maintenance

items of the NetNumen N31
system
Chapter 4, Monthly Maintenance Describes the monthly

maintenance items of the
NetNumen N31 system
Chapter 5, Quarterly Maintenance Describes the quarterly

maintenance items of the
NetNumen N31 system
Confidential and Proprietary Information of ZTE CORPORATION I

This page is intentionally blank.
II Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1
Maintenance Overview
Table of Contents
Maintenance Overview ........................................................ 1
Maintenance Purpose .......................................................... 1
Maintenance Classification ................................................... 1
Maintenance Items ............................................................. 2
Maintenance Regulations ..................................................... 3
Maintenance Overview
Routine maintenance is a preventive behavior. It can detect and
eliminate the potential defects and hazards by regular inspection
and maintenance of equipment or software so as to guarantee
long-term secure, stable and reliable system operation.
Maintenance Purpose
The purpose of maintenance is to avoid potential risks, prevent
malfunctions and remove faults as early as possible by regularly
checking the running status of devices and the network manage-
ment system, analyzing various messages and handling alarms.
Maintenance Classification
By contents, maintenance can be classified into routine mainte-
nance, the handling of notification messages, the handling of alarm
messages, and the handling of common faults.
� Routine Maintenance
Routine maintenance refers to periodical maintenance, for ex-
ample, daily, weekly, monthly or quarterly maintenance. Main-
tenance personnel check the running conditions of devices pe-
riodically and handle the detected faults as early as possible,
so as to avoid potential risks and prevent failures.
� Handling of Notification Messages
Confidential and Proprietary Information of ZTE CORPORATION 1

Maintenance personnel analyze notification messages reported

during the running of devices on the network, check whether
any fault occurs, and handle the detected faults accordingly.
� Handling of Alarm Messages
Maintenance personnel analyze alarm messages reported
during the running of devices on the network and handle the
alarms accordingly.
� Handling of Common Faults
Maintenance personnel analyze, locate and eliminate common
faults once these faults are detected.
Maintenance Items
Routine EMS maintenance items include equipment hardware and
software.
Users can perform equipment maintenance and management with
the guidance of operation instructions. Also users can add or
delete the maintenance items shown in the table below accord-
ing to the actual network conditions and software requirements to
meet the actual maintenance needs.
The items of routine maintenance involved in the manual are
shown Table 1.
TABLE 1 MAINTENANCE ITEMS
Maintenance Period Maintenance Items
Daily maintenance Checking logs in the system
Checking operation logs
Checking CPU/MEM utilization
Checking Layer 2 interface traffic
Checking the running state of

Layer 2 interface
Checking TCP connection of the

system
Checking the running state of

Layer 3 VLAN interface
Checking the equipment

temperature
Checking the running states of

power and fan
2 Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1 Maintenance Overview
Maintenance Period Maintenance Items
Weekly maintenance Checking remaining flash capacity
Checking equipment configuration
Checking FTP network service port
Checking port mirror
Checking whether the board is

reset abnormally
Backing up system configuration
Monthly maintenance Checking system software version
Checking system time
Backing up system software

version
Modifying equipment password
One-click checking fault diagnosis

information
Checking the running state of the

service
Quarterly maintenance Checking the equipment room

environment
Checking the environment within

the cabinet
Checking the equipment

grounding
Checking equipment power

backup
Checking the spare part of

equipment
Maintenance Regulations
The following rules should be followed in the course of routine
maintenance:
1. Establish and improve the maintenance system, and mainte-
nance personnel regulate their daily work. Have detailed duty
logs, recording the running states of the system, version, data
modification, upgrades, and problem handling, which is easy
for later problem analysis and troubleshooting.
2. Prohibit playing games and online surfing on the computer ter-
minal, and installing, running and copying any software unre-
lated with the system are not allowed.

3. Network password should be set according to levels, perform

strict management and periodic changes.
4. Maintenance personnel receive pre-job training. Have basic
knowledge about equipment and related network, and can op-
erate in accordance with relevant manual instructions. Mainte-
nance personnel should have strict working attitude and high
maintenance levels, and improve their maintenance skills.
5. All the major operations (such as board switch, system reset-
ting, and software loading) should be documented and main-
tenance personnel confirm the feasibility before the operation.
Before carrying out the operation, the maintenance personnel
should back up and take corresponding emergency and safety
measures.
6. Handle the faults in time. For the difficult problems, contact
ZTE Global Customer Support Center for support.

Chapter 2
Daily Maintenance
Table of Contents
Checking Temperature in Equipment Room ............................ 5
Checking Humidity in Equipment Room.................................. 6
Checking the Running State of the Server .............................. 6
Checking the Running State of Disk Array .............................. 7
Checking Logs in the Window Operation System ..................... 7
Checking the Communication Between Server and Client ......... 8
Checking the CPU/MEM Utilization of the Server...................... 8
Checking Temperature in
Equipment Room
Context Temperature is an important factor that may influence the long
term operation of communication equipment. The purpose of tem-
perature check is to prevent adverse impact on the running of com-
munication equipment caused by too high or too low temperature.
Steps � Read the thermometer in the equipment room and check
whether the temperature meets the temperature requirements
for NetNumen N31 as shown in Table 2.
TABLE 2 TEMPERATURE REQUIREMENTS
Long-Term Operation Short-Term Operation
5℃~40℃ –5 ℃~50 ℃
– Measure the temperature at the position 1.5 m above the floor and 0.4m
in front of the rack without front and rear panels.
– Short-term operation means that the equipment works continuously for
no more than 96 hours at a time and works for no more than 15 days in
total during a year.
END OF STEPS
Result The temperature in the equipment room can meet the require-
ments for the equipment.
Postrequisite If the measured temperature is too high or too low, check and
make sure that the air-conditioner in the equipment room func-
tions properly.

Checking Humidity in
Equipment Room
Context The purpose of humidity check is to prevent the adverse impact on
communication equipment caused by too high or too low humidity
in the equipment room.
Steps � Read the thermometer in the equipment room. The require-
ments for NetNumen N31 are shown inTable 3.
TABLE 3 HUMIDITY REQUIREMENTS
Long-Term Operation Short-Term Operation
5%~85% 5%~90%
– Measure the temperature at the position 1.5 m above the floor and 0.4m
in front of the rack without front and rear panels.
– Short-term operation means that the equipment works continuously for
no more than 96 hours at a time and works for no more than 15 days in
total during a year.
END OF STEPS
Result The humidity in the equipment room can meet the requirements
for the equipment.
Postrequisite If the humidity is out of range, perform the following checks:
� Check whether the air-conditioner and ventilation devices are
working properly.
� Check whether the air-conditioner is correctly set.
� Check whether water pipelines are laid under the equipment
room in case of too high humidity. If yes, check whether leak-
age occurs at pipeline joints.
If air conditioning works improperly, please read the matched
manual, or contact the air conditioning manufacturer to solve
the problem as soon as possible. If it is a pipe or joint problem,
please contact the relevant department.
Checking the Running State

of the Server
Context To ensure that NetNumen N31is running properly.
Steps 1. On NetNumen N31, Open Process Running Information in-
terface.
2. Check whether there is an exception message on the screen.
END OF STEPS

Chapter 2 Daily Maintenance
Result There are not any exception messages such as “Broken Commu-
nication Link” and “State Machine Failure”.
Postrequisite If any exception message is found, analyze the message and do
troubleshooting.
If the fault can not be removed, please contact local ZTE office for
support.

of Disk Array
Context Ensure that the disk array has enough space and works properly
without failure.
Steps 1. Check the disk space to ensure that sufficient space is avail-
able.
2. Check whether any fault occurs on the disks, for example, read
or write error.
END OF STEPS
Result � If the space of the disk array is not enough, add more disks,
or backup alarm and performance data and then delete it to
release some space.
� If some hard disk fault is found, contact local office of ZTE for
support.
Checking Logs in the

Window Operation System
Context Operation logs record the operations on the system. View logs in
NetNumen N31 to check for unauthorized operations, wrong oper-
ations, or for the operation of configuration data modification.
Steps 1. On NetNumen N31 server, select Start > Setting > Control
Panel > Administrative Tool > Event Viewer.
2. Check the operation logs on the log management interface.
Pay more attention to the logs recording the configuration data
change.
END OF STEPS
Result � No unauthorized or wrong operation logs.

� No operation logs of wrong configuration data modification.

Checking the Communica

tion Between Server and
Client
Context To check that the communication between NetNumen N31 and the
client is normal.
Steps 1. On NetNumen N31 client, select Start > Run to open the Run
dialog box.
2. Enterping IP address of the server in the dialog box, and check
the ping result.
END OF STEPS
Result The communication between the server and the client is normal if
the server can be successfully pinged.
Checking the CPU/MEM

Utilization of the Server
Context Check whether CPU/MEM utilization meets the requirements.
Steps 1. Select Maintenance > System Monitoring from EMS client
main interface.
System Monitoring interface pops up, as shown in Figure 1.
FIGURE 1 SYSTEM MONITORING INTERFACE

Chapter 2 Daily Maintenance
2. On the left of System Monitoring view, click Application

Server on the right Server Performance View box, click
View button.
Check the CPU utilization and MEM utilization of the application
server in the application server performance view, as shown in
Figure 2.
FIGURE 2 APPLICATION SERVER PERFORMANCE VIEW
Reference information
� At leisure time, CPU utilization rate is usually 5%, and MEM
utilization rate is 1%.
� At busy time, CPU utilization rate may reach up to 30%, and
MEM utilization rate may reach 10%. The value depends on
the call traffic.
END OF STEPS
Postrequisite � If the system capacity exceeds the designed one, high CPU and
MEM utilization over a long time indicates that the system load
is too heavy and the capacity expansion is needed.
� If the system capacity does not reach the designed one, but
the CPU and MEM utilization is high over a long time, please
contact ZTE for support.


Chapter 3
Weekly Maintenance
Table of Contents
Backing Up and Deleting Data .............................................11
Calibrating the System Clock...............................................13
Checking Database Space...................................................13
Checking the Logs of the Database ......................................15
Checking the Hard Disk Space .............................................15
Checking the Logs of the ServerSolaris ............................. 16
Checking the Running State of Dual Servers..........................17
Backing Up and Deleting

Data
Prerequisites � You have logged in to NetNumen N31 client.
� You have the maintenance operation authority
Context Backup/deletion data are consistent with the backup/deletion data
in Task management module. This difference lies in that Task Man-
agement module performs timing backup/deletion operation, and
the backup/deletion operation here is performed at a single exe-
cution.
Next we will take alarm data as an example to show the data
backup/deletion operation steps:
� Database backup
� Basic data backup
� File backup
� Log data backup/deletion
� Alarm data backup/deletion
� Performance data backup/deletion
� IT performance data backup/deletion
Steps 1. In NetNumen N31 main client interface, select Maintenance
> System Backup, enter System Backup sub-view.
2. Click Backup and Delete Alarm Data on the left pane, as
shown inFigure 3

FIGURE 3 BACKUP AND DELETE ALARM DATA
The parameter explanations are listed in Table 4.
TABLE 4 PARAMETER EXPLANATION FOR BACKUP/DELETION

OPERATIONS
Parameter Name Parameter Explanation
Backup/deletion Backup Only only back up the data of

operation specified time
Backup and Delete: back up the data and
then delete the data from the database
Delete Onlyonly delete the data of specified
time
Backup/deletion Select the content to be backed up / deleted

content
Backup filter type Set the period during which the log data
needs to be backed up. For example, select
Latest T daysthe system will back up the
log data in the latest T days.
Delete filter type Set the period during which the log data
needs to be deleted. For example, select
Latest T daysthe system will delete the log
data in the latest T days.
T Time box Works with backup filter type and delete

filter type, and you can enter the actual
number in the box.
3. Select Backup/delete Operation , Backup/delete Con-

tent, set Backup Filter Type and Delete Filter Type and
corresponding T Time box.
4. (optional) If you want to save the backup file under another
path on the server, Click Backup file Storage Path, and se-
lect button to change the storage path on the server.

Chapter 3 Weekly Maintenance
Note:
The path of Alarm data backup file is NetNumen
N31/backup/fmbak by default.
5. (optional)If you want to save the backup file on the local client,
select Backup File Downloading to Client pathclick Select
button to set the local client path.
Note:
Backup File Downloading to Client Path indicates that the
backup files will be backed up at local client.
6. Click Execute button to start backing up the alarm data.

Execute Result dialog box shows the backup process.
END OF STEPS
Calibrating the System Clock

Context The calibration of system clock is required to guarantee the time
synchronization between the NetNumen N31 server and standard
clock source.
Steps � Check whether the NetNumen M31 server is configured as the
standard clock source
For Windows operation system
Select Start > Set > Control Panel > Date and Time to
view or modify the system time of the server.
For Solaris operation system
Run Date command to view or modify the system time of the
server.
END OF STEPS
Checking Database Space

Prerequisites Oracle 10g database has been installed.
Context The utilization of each table in the database can not exceed 90%.
Checking database space periodically can prevent severe influence
on the running of the NetNumen N31 system caused by the short-
age of table space.

Steps 1. In Oracle database server, double click the file in the database
installation directory /oracle/product/10.2.0/Db_1/in-
stall/portlist.ini to check theHTTP port number of Oracle
management control panel.
For example, the port number is 1158:
FIGURE 4 PORT NUMBER VIEW
Figure
2. In configuration client, enter http://10.44.115.106:1158/e-

m/consoleand pop up the login interface
10.44.115.106 is the IP address of Oracle database
server1158 is the port number and it can be modified according
to actual environment.
3. Enter the user name and password of the database, choose
SYSDBA for Authority . ClickLogin button
4. Click OK button.
5. Click Management Tabselect Storage > Table Space
6. Check the utilization of each table space.
If the table space utilization rate is over 90%, the follow-up
treatment should be done.
END OF STEPS
Postrequisite � Back up the history data files onNetNumen N31 to other me-
dia, and delete the backup files. Data files are stored in the
installation directory ums-server\rundata\tracedata.
� If some table space is insufficient, expand the table space. The
steps are described as follows:
i. In Object Name enter the name of table space to be ex-
panded, for example UEP4X_CAF_FM. Click Start button to
check the utilization rate of the table space.
ii. Click the database table space name, and check the specific
information of the table space.
iii. If the table space has multiple data files, click the data file
to be modified such as UEP4X_CAF_FM.DBF.
iv. Click Edit button.
v. To modify File Size of data file, click Execute button and
pop-up file size editing complete interface.

Checking the Logs of the

Database
Prerequisites Oracle 10g database had been installed.
Context Check the logs of Oracle database generated by the operating sys-
tem (such as Windows) on the server to find and handle errors or
failures in time. Improve the system performance by analyzing
the data.
Steps 1. Open the installation directory of Oracle data-
base\oracle\product\10.2.0\db_1\NETWORK\log
2. Check the log file to find whether there are logs on system
faults such as abnormal communications.
3. Open Oracle database installation directory \oracle\prod-
uct\10.2.0\admin\CTS\bdump where CTS is actual database
instance name.
4. Check the log file alert_cts.log and check whether there are
exception records.
END OF STEPS
Postrequisite If an error or failure is found in the log, take the corresponding

measures according to the records.
Checking the Hard Disk

Space
Context Check the hard disk space of the application server periodically
to ensure that enough hard disk space is available to support the
running of the NetNumen N31 system. The commands used to
check hard disk space are different depending on the operating
system installed on the server.
Steps 1. For Windows operation system
i. Double-click My Computer
ii. Right-click Disk (C ) select Properties to check the disk
space.
iii. If the system has multiple partitions, check the disk space
of other partitions.
2. For Solaris operation system
Enter the following command to check the hard disk utilization
of the server.
#df -k
Normally, the recommended free space on each server is as
follows:

� The free space of each PC should ensure 5Gbyte above, or

free space should be no less than 10% of the entire hard
drive capacity. (5Gbyte or 10% of hard drive capacity, take
the larger value).
� For SUN server, the file system does exceed 85%, and the
root file system does not exceed 70%.
� The remaining space of dual RAID is not less than 10% of
the entire hard drive capacity.
� The remaining space of the disk where the server data is
placed should ensure 5Gbyte above, or should be no less
than 10% of the entire hard drive capacity. (5Gbyte or 10%
of hard drive capacity, take the larger value).
END OF STEPS
Postrequisite � Insufficient space of the Disk C used by the Windows operating

system may be caused by virus infection or too large log of an-
tivirus 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.
� 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 opera-
tions on the database are required, such as backup of alarm
database and performance database, and deletion of history
data.
� If a system file is infected with virus and can not be repaired,
it is recommended to copy the same file from another server
or software version and replace the infected one. Reinstall the
operating system if file replacement can not solve the problem.
Checking the Logs of the

ServerSolaris
Context Check the logs on the server to find and handle errors or failures in
time. The commands used to check the system logs are different
depending on the operating system installed on the server.
Steps 1. Use the following commands to check whether error, warning
or failure records exist in messages.
� # more /var/adm/messages|grep error
� # more /var/adm/messages|grep warning
� # more /var/adm/messages|grep fail
2. Use the following commands to check whether error, warning
or failure records exist in Syslog.
� # more /var/log/syslog|grep error
� # more /var/log/syslog|grep warning

� # more /var/log/syslog|grep fail

END OF STEPS
Result If an error or failure is found in messages or Syslog, check the

running state of corresponding hardware or software according to
the position where the error or failure occurs.

of Dual Servers
Context Check whether the dual servers are running properly.
Steps 1. Open the cabinet where the servers are placed, and check
whether there is any red alarm indication for each server.
2. Check whether there is any alarm caused by improperly run-
ning programs displayed on the monitor screen of each server.
3. If any alarm is found on either server, contact local office of
ZTE for troubleshooting.
END OF STEPS
Result There is no alarm on dual servers.


Chapter 4
Monthly Maintenance
Table of Contents
Checking Performance Data ................................................19
Checking the Remote Maintenance Tool ................................20
Checking Performance Data

Context Check and analyze whether the statistical performance data in-
dexes meet the corresponding range requirements.
Steps 1. In EMS client interface, select Performance > Performance
Data Query, and Performance Data Query interface pops
up, as shown in Figure 5
FIGURE 5 PERFORMANCE DATA QUERY
2. Select Network Type and Measurement Object Type, and

choose the index/counter to be queried.
3. Select Query Object Tab and select the network element as
the measurement object.

4. Select Time Query Tab, set Query Granularity, Time Span

Query Valid TimeValid Time Span
5. Click OK and the query result is displayed on Performance
Management interface.
END OF STEPS
Result Each performance index is within the required range and has no
great difference from recent index value.
Postrequisite If an index varied greatly in some day, query the details of the per-
formance data in that day further (using the smaller granularity)
and analyze the query result to find the cause of the unexpected
performance index change.
Checking the Remote

Maintenance Tool
Prerequisites � The communication between the base station and EMS is nor-
mal.
� The server is running properly.
Context Remote monitoring software is usually installed on the mainte-
nance terminal so that maintenance personnel can maintain the
NetNumen N31 client or server remotely. Check whether the con-
nection to the client or server is available for the purpose of remote
monitoring.
Steps 1. Check whether the remote maintenance software has been in-
stalled on the maintenance terminal of the NetNumen N31,
such as Pcanywhere. Check the remote client or server can be
logged in to by dialing or via the Internet so that the system
maintenance can be done by using the remote maintenance
software.
2. Check whether the special line is available in the equipment
room for remote maintenance.
3. Maintenance personnel in the equipment room can operate the
remote maintenance software skillfully.
END OF STEPS

Chapter 5
Quarterly Maintenance
Table of Contents
Checking the Switching Function Between Dual Servers .........21
Clearing the Databases ......................................................22
Checking the Switching

Function Between Dual
Servers
Context Check the switching function between two servers in a dual-server
NetNumen N31 system.
Steps 1. Check whether the profiles and running files on the active
server and standby server are consistent. Back up the current
route configuration. And then check whether the route to the
lower-level network element management system is normal
by pingingthe server of the lower-level network element
management system.
2. Turn off the active server, and switch to the standby server.
3. Wait and observe for 30 minutes.
4. Restart the standby server and make sure that it is successfully
started.
5. Switch back to the original server.
END OF STEPS
Result � The system can successfully switch between two servers with
successful service handover.
� The route to the lower-level network element management
system is correct, that is, you can successfully pingit on the
NetNumen N31.
� You can successfully log in to the server by using the account
allocated to the lower-level network element management sys-
tem.
Postrequisite If the system fails to switch between dual servers, check the log
records to find the resource that can not be switched first. Then
contact local office of ZTE for troubleshooting.

Clearing the Databases

Context Clear all kinds of databases to delete useless data.
Steps 1. On the NetNumen N31 client, check and make sure that logs
have been backed up on the hard disk.
The whole database and log files both can be backed up.
2. Delete the logs from corresponding databases, such as the logs
one month ago.
END OF STEPS
Result All data is backed up and the useless data is cleared from the
databases.

Figures
Figure 1 System Monitoring Interface .................................... 8

Figure 2 Application Server Performance View ........................ 9
Figure 3 Backup and Delete Alarm Data................................12
Figure 4 Port Number View ................................................14
Figure 5 Performance Data Query ........................................19


Tables
Table 1 Maintenance Items .................................................. 2

Table 2 Temperature requirements ........................................ 5
Table 3 Humidity Requirements ............................................ 6
Table 4 Parameter Explanation for Backup/Deletion
Operations........................................................12


Glossary
CPU
- Central Processing Unit
EMS
- Element Management System
HTTP
- Hypertext Transfer Protocol
PC
- Personal Computer

NetNumen N31 UNMS (V5.01.01) Administrator Manual

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

NetNumen N31 UNMS (V5.01.01) Administrator Manual

Uploaded by

Copyright:

Available Formats

NetNumen N31 (IP Network)

Unified Network Management System

Copyright © 2010 ZTE CORPORATION.

The ultimate right to interpret this product resides in ZTE CORPORATION.

Revision No. Revision Date Revision Reason

Serial Number: SJ-20100817155256-007

About This Manual............................................. I

Confidential and Proprietary Information of ZTE CORPORATION I

II Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1, Maintenance Overview Introduces the classification,

Chapter 2, Daily Maintenance Describes the daily maintenance

Chapter 3, Weekly Maintenance Describes the weekly maintenance

Chapter 4, Monthly Maintenance Describes the monthly

Chapter 5, Quarterly Maintenance Describes the quarterly

Confidential and Proprietary Information of ZTE CORPORATION I

This page is intentionally blank.

II Confidential and Proprietary Information of ZTE CORPORATION

Confidential and Proprietary Information of ZTE CORPORATION 1

Maintenance personnel analyze notification messages reported

TABLE 1 MAINTENANCE ITEMS

Maintenance Period Maintenance Items

Daily maintenance Checking logs in the system

Checking operation logs

Checking CPU/MEM utilization

Checking Layer 2 interface traffic

Checking the running state of

Checking TCP connection of the

Checking the running state of

Checking the equipment

Checking the running states of

2 Confidential and Proprietary Information of ZTE CORPORATION

Maintenance Period Maintenance Items

Weekly maintenance Checking remaining flash capacity

Checking equipment configuration

Checking FTP network service port

Checking port mirror

Checking whether the board is

Backing up system configuration

Monthly maintenance Checking system software version

Checking system time

Backing up system software

Modifying equipment password

One-click checking fault diagnosis

Checking the running state of the

Quarterly maintenance Checking the equipment room

Checking the environment within

Checking the equipment

Checking equipment power

Checking the spare part of

Confidential and Proprietary Information of ZTE CORPORATION 3

3. Network password should be set according to levels, perform

4 Confidential and Proprietary Information of ZTE CORPORATION

TABLE 2 TEMPERATURE REQUIREMENTS

Long-Term Operation Short-Term Operation

Confidential and Proprietary Information of ZTE CORPORATION 5

TABLE 3 HUMIDITY REQUIREMENTS

Long-Term Operation Short-Term Operation

Checking the Running State

6 Confidential and Proprietary Information of ZTE CORPORATION

Checking the Running State

Checking Logs in the

Result � No unauthorized or wrong operation logs.

Confidential and Proprietary Information of ZTE CORPORATION 7

Checking the Communica