T2000 Maintenance and Operation Guide

2.3.2 Checking System Disk Space Occupation Item Checking the system disk space occupation Cause It is suggested that the disk space occupation should not exceed 90%, otherwise the NMS

Target readers Engineers Product version

Edited by Optical Network technical support

department

Document version

T2000 Maintenance and Operation

Guide

Huawei Technologies Co, Ltd

All Rights Reserved

Revision Records

Chapter 1 Purpose 6

1.1 Maintenance Purpose 6

1.2 Operation Purpose 6

1.3 Scope of Application 6

Chapter 2 NMS Maintenance Guide 6

2.1 Types of Routine NMS Maintenance 7

2.2 Basic Principles for Routine Maintenance 7

2.3 Routine NMS Maintenance Items 7

2.3.1 Checking the NMS Hardware 7

2.3.2 Checking System Disk Space Occupation 7

2.3.3 Ensuring Password and Authority Security 8

2.3.4 Monitoring the Database 8

2.3.5 Monitoring the T2000 Server 8

2.3.6 Backing up NMS Data Periodically 9

2.3.7 Checking Log Dump Setting Periodically 10

2.3.8 Checking the Network’s ECC Routing 10

2.3.9 Checking Data Consistency between the NMS and the NEs 10

2.4 Routine NMS Maintenance Item Table 11

Chapter 3 NMS Operation Guide 12

3.1 NMS Operation Description 12

3.1.1 Closing the T2000 NMS and the OS 12

3.1.2 Closing T2000 Prior to Modifying the NM Server’s System Time 12

3.1.3 Using a Special NE User for Each NMS for NE Login 12

3.1.4 Setting Alarm Properties Reasonably to Reduce Unnecessary Alarms 13

3.1.5 Setting Performance Properties Reasonably to Reduce Unnecessary Performance Events 13

3.1.6 Paying Attention to the Results of NMS Operations 13

3.1.7 Precautions for Mass Data Operations 13

3.1.8 Suggestion of Single NE Download at a Time 14

3.1.9 Using Full Activation Only when Necessary 14

3.1.10 Precautions for Multi-Terminal NMS Operations 14

3.1.11 Keeping Data Synchronous when Configuring a Service under Multi-NMS Environment 15

3.1.12 Keeping Data Synchronous after Configuration Modification through Command Lines 15

3.1.13 Backing up NE Database Right after NE Configuration Change 15 3.1.14 Using Service-Impact Operations Only when Necessary 15 3.1.15 Setting Multiplex Section Loop after Downloading an NE Configuration with the NES/RMS 16

OptiX Optical Transmission NMS Routine Maintenance and Operation Guide

Summary:

OptiX Optical Transmission NMS Routine Maintenance and Operation Guide include: Purpose, NMS Maintenance, NMS Operation.

Abbreviation list:

None.

Reference list:

None.

Chapter 1 Purpose

This guide provides instructions on two operations:

1、Routine NMS maintenance for higher efficiency 2、NMS operations for higher security and transmission system stability

1.1 Maintenance Purpose

G u i d e t h e m a i n t e n a n c e p e r s o n n e l t o p e r f o r m r o u t i n e N M S m a i n t e n a n c e : Perform s p pecific m reventive f o a s aintenance, p t t ind ut nd olve roblems imely o

ensure the normal running of the NMS

1.2 Operation Purpose

G u i d e t h e m a i n t e n a n c e p e r s o n n e l t o o p e r a t e t h e N M S i n a m o r e

r e a s o n a b l e a n d p r o p e r w a y : M a s t e r b a s i c N M S o p e r a t i o n s t o i m p r o v e

o pe ra t io n secu ri ty a nd avo id o p ti cal t ra nsm issio n syst em ab no rm ali ty d ue to

improper operations

1.3 Scope of Application

This g uide a t t pplies iManager T o N MSw he 2000 u idely i t n sed I n he etworks n addition, it is also appropriate for the NES/RMS NMS

The maintenance of dual-system and the iManager T2100 NMS is beyond the scope of this guide

For more details, access the following Website:

http://support.huawei.com

Chapter 2 NMS Maintenance Guide

This chapter provides a guide to the maintenance of the NMS itself, including NMS hardware, operating system, NMS database and NMS software.

F o r t h e r o u t i n e m a i n t e n a n c e o f o p t i c a l t r a n s m i s s i o n d e v i c e s , r e f e r t o t h e i r maintenance guides

2.1 Types of Routine NMS Maintenance

1 Daily maintenance

D a i l y m a i n t e n a n c e r e f e r s t o t h e m a i n t e n a n c e p e r f o r m e d e v e r y d a y, w h i c h keeps the maintenance personnel timely informed of the NMS operation On the basis of such information, they can find out problems and troubles timely for quick solutions

2 Periodic maintenance Periodic maintenance is to maintain the system periodically

3 Emergency maintenance Emergency maintenance addresses the maintenance tasks brought about by troubleshooting and network adjustment

2.2 Basic Principles for Routine Maintenance

1) Routinize the maintenance 2 ) Detail the maintenance plan and content for effective implementation

2.3 Routine NMS Maintenance Items

The routine maintenance of the OptiX NMS includes the following items.

2.3.1 Checking the NMS Hardware

Item Checking the NMS hardware

Operation 1 Make sure that the hardware devices such as the NM workstation and terminal router run normally:

Check the mouse, keyboard, monitor and printer If there are abnormalities, contact the hardware suppliers (e.g., SUN and DELL) immediately for solution

2 Check the other devices such as routers (if configured) periodically

2.3.2 Checking System Disk Space Occupation

Item Checking the system disk space occupation

Cause It is suggested that the disk space occupation should not exceed 90%, otherwise the NMS efficiency will be

decreased

Operation  On a workstation, use the df –k command to query the disk space occupation Make sure that the occupation

of the directories “/”, “/T2000” and “/opt” is not higher than 90% If in excess of 90%, it is suggested that the

unidentified super large rubbish files or directories such as the repetitive backed up data, useless files,

directories and log information be cleared

 On a PC, check the occupation of the operating system disk and the occupation of the

SQL SERVER and T2000 NM directories

2.3.3 Ensuring Password and Authority Security

Item Ensuring password and authority security

Operation 1 Set authorities for different levels of maintenance personnel and designate a special personnel to manage

the password and modify it periodically The authority of the NMS user should be consistent with that of the NE user

2 Make sure that the NM station (or PC) is for NM purpose only and isolated from external systems

(principally) When it connects to an external system, security measures such as isolation are required Prohibit maintenance-unrelated operations and uses of maintenance-unrelated floppy disks and software in the NMS in order to fence off computer virus

2.3.4 Monitoring the Database

Item Monitoring the database

Cause The NMS is abnormal if the database is not started

Operation  Follow these steps to check MSSQL7 on a PC:

Check the icon at the bottom right corner of PC A green arrow indicates that the database is running normally, while a red arrow indicates that the database is not enabled and you need to click it manually and then select [Start] to enable the database

 Execute the following commands in the workstation terminal window to check the Sybase database:

T2000%su sybase

$isql -Usa -P -ST2000DBServer 1>quit

$isql -Usa -P -ST2000DBServer_back 1>quit

$su t2000 T2000%

The Sybase command line prompt 1> must be shown at the terminal, indicating the T2000DBServer has been successfully installed and can be automatically started

2.3.5 Monitoring the T2000 Server

Item Monitoring the T2000 server

Cause The four server processes of mdp, ss, toposvr and ems are crucial to guarantee the normal running of

T2000 server

If all the above four server processes are enabled and converge to be one process, the server is normally enabled If one process is missed, the server is not totally enabled If one process has two IDs, the server is repeatedly enabled Restart the server forcefully in the later two circumstances

Operation  Follow these steps to check the T2000 server process on a PC:

Check the PCS icon at the right bottom corner of PC Green indicates that the t2000 server process is

normal, while red indicates that the t2000 server process is abnormal and you need to double click this icon to check which of the four servers of mdp, ss, toposvr and ems are not running (The T2000V1R001 version has the alarm process besides the above four processes)

 Execute the following commands in the workstation terminal window:

T2000%cd /T2000/server T2000%showt2000server Normally, the result should be as follows (The process ID shall be unique):

user is t2000 show ems process

pid = 1140 show mdp process

pid = 1136 show ss process

pid = 1137 show toposvr process

pid = 1138 Note: For the T2000V1R002D008 version, multiple ss processes will be shown without affecting the running of NMS

2.3.6 Backing up NMS Data Periodically

Item Backing up NMS data periodically

Cause 1 NMS data can be recovered timely when NMS is abnormal due to NMS fault and

hardware damage

2 Back up data periodically (once per month in the initial running stage of NMS and once per quarter when the system can run steadily) It is suggested to back up data after the

important data modification or before the NMS upgrading and in other storage devices such as tape drive, magneto-optical disk and U disk

Operation In routine maintenance, it is suggested to back up data onto MO and the operations are as follows:

Manual backup mode

 Workstation T2000%cd /T2000/server/database T2000%backupmo.bat

T2000%tar cvf mo_bak_XXXX.tar mo

 PC Enter the C:\T2000\server\database directory Double click backupmo.bat

Compress the mo directory under the C:\T2000\server\database and back up it to the backup directory You can also back up data manually on the NMS interface (T2000 V1R004 and its succeeding version supports the automatic backup) In the NMS interface, click [System]-[Database backup]-[Manual backup]

Automatic backup

Item Backing up NMS data periodically

T2000 V1R004 and its succeeding version supports the automatic backup In the NMS interface, click [System]-[Database backup]-[Automatic backup]

Data restoration Initialize database, copy the backed up MO data in the /T2000/server/database directory and then execute restoremo.bat under this directory (For the T2000 V1R004 and its succeeding versions at the workstation, execute restoremo.sh ) Use the data restoration operation only when

necessary

Note:

The a bove b m ackup o a t t odes d b nly a r pply o t o he ata ackup nd estoration f he same N v MS F t ersion d u or o r he b ata d pgrade N r estoration etween ifferent MS

v e r s i o n s , y o u c a n o n l y a d o p t t h e s c r i p t - e x p o r t i n g m o d e : E x p o r t t h e configuration script of NMS in the case that the data at the NMS side and the

N E s i d e a r e c o n s i s t e n t , a n d c l i c k t h e m e n u [ M a i n t e n a n c e c o n s o l e ] -[ M a i n t e n a n c e ] - -[ C o n f i g u r a t i o n d a t a m a n a g e m e n t ] - -[ S c r i p t e x p o r t / i m p o r t ] t o

export the “Global configuration file” and then back up the script

In addition, you can back up data through the dump mode on the workstation and through the SQL SERVER out-of-box backup tool on PC As the backup data is quite large, it is suggested to back up only once during the trial office period

2.3.7 Checking Log Dump Setting Periodically

Item Checking log dump setting periodically

Cause An overlarge log may slow down the NMS operation Although T2000 has provided an automatic log dump

function, you should check the log dump configuration periodically to prevent it from being modified

Operation Enter the NMS menu and select [System] - [Data dump] to check if the periodic log dump or overflow log dump

have been configured for the alarm event, abnormality and performance event If not, reconfigure them Usually

the log dump configuration has been defaulted by the NMS

2.3.8 Checking the Network’s ECC Routing

Item Checking the network’s ECC routing

Cause Verify the connections between the NMS and the NEs

Operation Enter [Maintenance console] - [Communication] - [NE ECC link management]to select an NE and perform

as follows:

1 Go through the ECC routes of the gateway NE to make sure that all the subnet NEs are covered by the target NE

2 Analyze the NEs far from the ECC to see if they select the shortest ECC route

2.3.9 Checking Data Consistency between the NMS and the NEs

Item Checking data consistency between the NMS and the NEs

Cause Avoid NE data configuration by other NMSs, which causes data inconsistence between the NMS and the NE and

the possible impact on the services

Operations 1 This check is suggested under normal network running

Enter the NMS menu and select [Configuration] - [Data consistency checking

2 configuration] to check the consistency of all the NEs on whole network one by one

3 If the inconsistent NEs exist, locate the reason and then upload

2.4 Routine NMS Maintenance Item Table

Date: Month Year

Maintenance

type

Maintenance item Maintenance

cycle

Maintenance status Remarks Maintenance

personnel

Equipment

Environment

External situations(Power supply

system, UPS, fire,

dust and lightning)

Daily  Normal  Abnormal

Temperature (Normal

2 Humidity (Normally

Equipment room cleanness(good/bad) Daily  Good Bad Checking virus on PC Daily  Normal  Abnormal NMS Check Checking NMS’ login to NE Daily  Normal  Abnormal

Checking alarm and abnormality

Checking the database running

Monitoring T2000 server running

Checking the hardware status

Checking the disk space occupation Weekly  Normal  Abnormal Controlling the security of

password and authority Monthly  Modified Unmodified Checking the log dump

configuration

Monthly  Normal  Abnormal

type

Maintenance item Maintenance

cycle

Maintenance status Remarks Maintenance

personnel

Checking the data consistency between NMS side and NE side Monthly  Normal  Abnormal NMS Data backup Monthly  Finished Unfinished

Remote maintenance test Quarterly  Normal  Abnormal

Note: T a he t bove o t t ables N r nly m ouch s he MS outine aintenance uggestions.

F o r t h e o t h e r d e v i ce ma i n t e n a n ce , r e f e r t o t h e i r co r r e s p o n d i n g ma i n t e n a n ce proposals

Chapter 3 NMS Operation Guide

3.1 NMS Operation Description

This section gives some suggestions on the T2000 NMS operation, aiming to

i n s t r u c t t h e m a i n t e n a n c e s t a f f w i t h t h e i r r o u t i n e N M S o p e r a t i o n s f o r h i g h e r reasonability, efficiency and security

3.1.1 Closing the T2000 NMS and the OS

Item Closing the T2000 NMS and the OS

Cause Always avoid abnormal shutdown while T2000 is running The NMS keeps transaction when it is running, so

abnormal closedown, either to the system or to the computer, may cause damage to the data, the system or

the hardware and hence an NMS fault Unreasonable operations include:

1 Computer power-off when the NMS is running

2 Illegal power-off (especially for SUN workstation)

Suggestion Closing methods:

1 Select [System] - [Close Server] from the NMS menu to close the NMS server

2 Power off the computer normally (after normally closing the NMS)

Windows OS: Select [Run] – [Close Computer]

Solaris OS: Run #/usr/sbin/shutdown –y –g0 –i5 to power off the computer

Note: If you are logging into the T2000 NMS as a user of administrator’s level, be sure not to close the running

server by selecting the “Close Server” operation (available for user) by mistake

3.1.2 Closing T2000 Prior to Modifying the NM Server’s System Time

Item Closing T2000 prior to modifying the NM server’s system time

Cause It is a limit in the system Modifying the system time may lead to T2000 time coordinate confusion, and hence

failure to trigger the T2000 server’s refresh message As a result, these abnormalities may occur: failure to

refresh interface color, failure to close alarm acknowledgement dialog box, no alarm tone and non-configured