NetNumen M31 RAN V3!1!10 420 Maintenance Guide

NetNumen M31(RAN)Mobile Network Element Management System

Maintenance Guide

Version 3.10.420

ZTE CORPORATIONZTE Plaza, Keji Road South,Hi-Tech Industrial Park,Nanshan District, Shenzhen,P. R. China518057Tel: (86) 755 26771900Fax: (86) 755 26770801URL: http://ensupport.zte.com.cnE-mail: [email protected]

LEGAL INFORMATION

Copyright © 2006 ZTE CORPORATION.

The contents of this document are protected by copyright laws and international treaties. Any reproduction or distribution ofthis 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 CORPORATIONor 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 theinformation contained herein.

ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications covering the subjectmatter 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.1 July 31, 2009 Review and Test Comments Modification

R1.0 June 27, 2009 First Edition

Serial Number: sjzl20092882

Contents

Preface............................................................... i

Safety Instructions............................................1Safety Precautions.......................................................... 1

Safety Signs .................................................................. 1

Safety Guidelines ........................................................... 3

Maintenance Overview ......................................7Introduction................................................................... 7

Maintenance Classifications.............................................. 7

Common Maintenance Checks and Precautions ................... 9

Daily Routine Maintenance ..............................11Daily Routine Maintenance Items.....................................11

Checking Equipment Room Temperature ...........................12

Checking Equipment Room Humidity ................................13

Checking Running Status of Air-conditioning......................14

Checking Communication Between Server and Client..........14

Checking Communication Between Server and

Low-Level.............................................................16

Checking Hardware........................................................18

Checking Server ............................................................19

Checking Dual Server System Operation Status .................20

Checking Alarms ...........................................................21

Checking Operation Logs ................................................23

Checking Disk Array.......................................................24

Backing up Data............................................................24

Checking System Load ...................................................25

Checking Virus Monitoring Result in Real Time ...................26

Weekly Routine Maintenance .........................29Weekly Routine Maintenance Items ..................................29

Checking History Alarm ..................................................30

Checking Scheduled Query Task ......................................30

Calibrating System Time.................................................31

Checking Database Space...............................................32

Checking Shared Folders on Client ..................................33

Updating Antivirus Software............................................34

Checking Server Progress Status .....................................35

Backing up Data............................................................36

Checking Server Error Logs ............................................37

Checking Server Disk Storage Capacity ............................38

Checking Client Hard Disk Space ....................................39

Monthly Routine Maintenance .........................41Monthly Routine Maintenance Items.................................41

Checking Power Supply Voltage .......................................42

Cleaning Dust on Cabinet ...............................................42

Checking Table Space Usage ..........................................43

Checking Performance Statistic Result of Operation

Network ..............................................................44

Checking Dual System Operation Status ..........................45

Monitoring Test .............................................................46

Quarterly Maintenance ....................................49Quarterly Maintenance Items ..........................................49

Checking Dual Server System Switching ...........................50

Checking Ground Resistance ...........................................53

Clearing History Alarm ...................................................53

Deleting Performance Database.......................................55

Checking Unauthorized Access of Server...........................57

Checking Firewall ..........................................................57

Checking LAN Equipment................................................58

Maintenance Record Form...............................59Daily Maintenance Form .................................................59

Weekly Maintenance Form ..............................................60

Monthly Maintenance Form .............................................62

Quarterly Maintenance Form ...........................................63

Common Alarms and Faults Handling ..............65Overview......................................................................65

Equipment Alarms .........................................................66

Communication Alarms with Lower-level NM..................66

DB Space Insufficient .................................................66

CPU Occupancy of Application Server above

Threshold .........................................................67

Memory Occupancy of Application Server over

Threshold .........................................................67

Space for Application Server Logs Insufficient................68

Catalog Capacity over Threshold..................................68

Common Faults Handling ................................................69

AMO Startup Error .....................................................69

Alarm Forwarding Failure ............................................69

Hard Disk Space Insufficiency .....................................70

Client Fails to connect with Server ...............................70

Server Unable to Start ...............................................70

Database Unable to Start............................................71

Data Table Space Full .................................................72

Alarm Box Unable to Display Audio-Visual Prompt ..........73

Performance Report Problem Caused by Incorrect Time

Zone Settings ...................................................74

Chaotic Performance Alarm Data Caused By

Synchronization Error between Upper and Lower

Level ...............................................................74

Error When Reporting Lower Level Net Manager

Configuration Data.............................................76

Error in Reporting Lower Level Net Manager

Performance Data..............................................76

Northbound Interface Link Interruption.........................76

Failure in Reporting Configuration Data to NMS..............77

Error in Report Alarm Information to NMS.....................78

Failure in Reporting Performance Data to NMS...............78

Data Backup and Recovery ..............................81Log Files Backup ...........................................................81

NetNumen Log Files Backup in Windows OS ..................81

NetNumen Log Files Backup in Solaris OS .....................83

CM Data Backup and Recovery ........................................85

NetNumen CM Data Backup and Recovery.....................85

Database Tables Backup and Recovery .............................93

All Users Database Backup and Recovery ........................ 103

Fault Management database backup............................... 103

Emergency Maintenance................................109Emergency Maintenance Purpose................................... 109

Principle of Emergency Maintenance............................... 110

Emergency Maintenance Flow........................................ 110

Service Check ............................................................. 111

Fault Record ............................................................... 111

Locating Fault ............................................................. 112

Emergency Recourse.................................................... 112

Service Recovery......................................................... 113

Information Record...................................................... 114

Information Collection .................................................. 114

Emergency Maintenance Tables ..................................... 114

Abnormality Record Table ......................................... 114

Equipment Emergency Maintenance Requisition ........... 115

Troubleshooting Record Table .................................... 116

Figures ..........................................................117

Tables ...........................................................121

Glossary ........................................................123

Preface

Purpose This manual provides procedures and guidelines that support themaintenance operation on NetNumen M31(RAN) Mobile NetworkElement Management System.

IntendedAudience

This manual is intended for engineers and technicians who performmaintenance activities on NetNumen M31(RAN) Mobile NetworkElement Management System.

Prerequisite Skilland Knowledge

To use this document effectively, users should have a general un-derstanding of wireless telecommunications technology. Familiar-ity with the following is helpful:

� NetNumen M31(RAN)system and its various components.

� Local operating procedures of NetNumen M31(RAN) system

What Is in ThisManual

This manual contains the following chapters as shown in Table 1:

TABLE 1 CHAPTER SUMMARY

Chapter Summary

Chapter 1, SafetyInstructions

It gives Safety instructions in theNetNumen M31(RAN) maintenanceprocess.

Chapter 2, MaintenanceOverview

Introduces maintenance classificationsand common maintenance check andprecautions.

Chapter 3, Daily RoutineMaintenance.

Introduces the NetNumen M31(RAN)daily maintenance list of items and themaintenance methods.

Chapter 4, WeaklyRoutine Maintenance

Introduces the NetNumenM31(RAN)weakly maintenance list ofitems and the maintenance methods.

Chapter 5, MonthlyRoutine Maintenance

Introduces the NetNumen M31(RAN)monthly maintenance list of items and themaintenance methods.

Chapter 6 ,QuarterlyRoutine Maintenance

Introduces the NetNumen M31(RAN)quarterly maintenance list of items and themaintenance methods.

Chapter 7, MaintenanceRecord Form

Introduces maintenance forms.

Chapter 8, CommonAlarms and FaultsHandling

Introduces common alarms of NetNumenM31(RAN) system and also introducesthe troubleshooting to common faults ofNetNumen M31(RAN) system.

Confidential and Proprietary Information of ZTE CORPORATION i

NetNumen M31(RAN) Maintenance Guide

Chapter Summary

Chapter 9, Data Backupand Recovery

Explains how to take backup and recoveryof log file and CM data.

Chapter 10, EmergencyMaintenance

Introduces the purpose and maintenanceflow and provides the related tables ofemergency maintenance.

ii Confidential and Proprietary Information of ZTE CORPORATION

C h a p t e r 1

Safety Instructions

Table of ContentsSafety Precautions.............................................................. 1Safety Signs ...................................................................... 1Safety Guidelines ............................................................... 3

Safety PrecautionsBSS system can only be installed, operated and maintained by dulytrained and qualified personnel.

Basic requirements to the BSS maintenance personnel are as fol-lows:

� BSS system theoretical knowledge.

� Familiar with BSS device principle and networking.

� Experience with network optimization skill.

Observe the local safety specifications and relevant operatingprocedures during equipment installation, operation and mainte-nance, to avoid any personal injury or damage to the equipment.The safety precautions in this manual can only be used as asupplement to local safety regulations.

Note:

ZTE shall not bear any liabilities incurred by violation of the uni-versal safety operation requirements, or violation of the safetystandard for designing, manufacturing and using the equipment.

Safety SignsSafety Signs Meaning

No Smoking: Smoking isforbidden.

Confidential and Proprietary Information of ZTE CORPORATION 1


Safety Signs Meaning

No flammables: Flammablesmaterials are not allowed.

No touching: Do not touch.

Universal alarm: Common safetyprecautions.

Electric shock: There is highvoltage risk.

Static protection: The device maybe sensitive to static electricity.

Microwave danger: There isstrong electromagnetic field.

Laser danger: There is a stronglaser beam.

The safety reminder falls into four severity levels: Danger,Warning, Caution and Attention. Literal description of the safeprompt is on the right of the safety sign and detailed descriptionis under the safety sign. The format is as follows.

Danger:

Indicates an imminently hazardous situation, which, if not avoided,will result in death or serious injury. This signal word should belimited to only extreme situations.

Warning:

Indicates a potentially hazardous situation, which, if not avoided,could result in death or serious injury.

Caution:

Indicates a potentially hazardous situation, which, if not avoided,could result in minor or moderate injury. It may also be used toalert against unsafe practices.

2 Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1 Safety Instructions

Note:

Indicates a potentially hazardous situation, which, if not avoided,could result in injuries, equipment damage or partial interruptionof services.

Safety GuidelinesTools

Electric Shock:

Make sure to use special tools rather than common tools for high-voltage and AC operations.

High Voltage

Danger:

High voltage is hazardous. Direct or indirect contact with highvoltage or mains supply using a wet object may result in death.

Follow the local safety rules to install AC power equipments.

Do not wear watch, bracelet, ring or other conducting objects dur-ing operation.

Person who is installing AC equipment must be qualified for high-voltage and AC operations.

Prevent moisture from entering the equipment during operation ina damp environment.

Power Cable

Danger:

Never install or uninstall power cables while they are live. Powercables, when contacting a conductor, may cause sparks or electricarc and cause a fire or damage eyes.

Switch off the power supply before installing or disconnecting apower cable.

Make sure that connecting cable and its label meet actual instal-lation requirements before connection.



Drilling Holes

Warning:

Do not drill the cabinet without permission!

Without permission drilling may damage wiring and cables insidethe cabinet. Additionally, metal pieces inside the cabinet createdby the drilling may result in a shorted circuit board.

Use protection gloves and move cables within the cabinet awaybefore using a drill. Pay attention to protect eyes while drilling,for splashing sweepings may damage eyes. After drilling sweepcleanly.

Lightening

Electric Shock:

Strictly forbid to operatie in high-voltage, AC, iron tower or mastin a thunderstorm.

Take lightning and grounding measures in time, during thunder-storms may rise strong electromagnetic field in the atmosphere.

Antistatic

Electrostatic:

Static electricity produced by human body may damage static-sen-sitive components on circuit boards, such as large-scale IntegratedCircuit (IC).

Friction caused by human body activities is root cause of elec-trostatic charge accumulation. Static voltage carried by a humanbody can be up to 30 kV in a dry environment, and can remain inhuman body for a long time. Operator with static may dischargeelectricity through the component and cause damage to it whiletouching equipment or holding a plug-in board, circuit board, ICchip and others.

Wear an antistatic wrist strap and ground the other end well toprevent human static electricity from damaging sensitive compo-nents.

Connect a resistor over 1 MΩ in series on the cable between an-tistatic wrist strap and grounding point, to protect the operatoragainst accidental electric shock. Resistance over 1 MΩ is lowenough to discharge static voltage.

Antistatic wrist strap usage must be subjected to regular check.Do not replace the cable of an antistatic wrist strap with any othercables.

Keep static-sensitive board away from objects that easily gen-erate static electricity, like friction of package bag, transfer boxand transfer belt made from insulation plastic. They may causestatic electricity on components and discharge of static electricitymay damage components when they contact human body or theground.

Keep boards in anti-static bags during storage and transportation.


Chapter 1 Safety Instructions

Discharge static electricity of test device before use, that is,ground it first.

Keep boards away from a strong DC magnetic field, such as cath-ode-ray tube of the monitor. Keep them at least 10 cm away.

Others Do not perform maintenance or debugging inside the equipmentindependently without a qualified personal for help.

Replacing or changing any part in the equipment might result inan unexpected damage.

Be sure not to replace any part or change the equipment unlessauthorized.

Please contact ZTE Corporation if you have any questions.



This page is intentionally blank.


C h a p t e r 2

Maintenance Overview

Table of ContentsIntroduction....................................................................... 7Maintenance Classifications.................................................. 7Common Maintenance Checks and Precautions ....................... 9

IntroductionMaintenance is a periodic inspection of the equipments to find theproblems during its operation. Solve the problems as early aspossible to avoid potential dangers.

Maintenance ClassificationsDuring routine maintenance, it is needed to locate the defects us-ing some methods. The common maintenance methods includethe following nine kinds.

� Checking Alarms and Operation Log

When the defect takes place, maintenance personnel firstchecks the alarm and operation log files. It checks the alarmsmanagement and operation log interface of NetNumen M31 inBSS operation maintenance center.

Alarm message management is performed to analyze thealarm messages that may occur during the running of thesystem to determine its running status and handle themaccordingly.

The NetNumen M31 records all error information or runningparameters of the system, when it is running. The analysis oflog file and alarm database information may point to the rootcause of the fault. Using this method engineer can analysesthe potential system problems.

� Analysis using Status Indicators

Usually the equipment has status indicators, which may helpthe user assess the running conditions of the equipment. Forexample, usually the server has power and fault indicators,the HUB has port indicators, etc. The status indicators helpanalyze the faulty part and even the cause.



This method requires maintenance personnel be familiar withthe Indicator light state and its meaning on various boards.

� Analyzing through performance management interface

The performance analyzing method is done through perfor-mance management interface of NetNumen M31 in BSS Opera-tion Maintenance Subsystem. Through the performance man-agement interface, the maintenance personnel may implementperformance management and signaling tracing for BSS sys-tem.

Through the performance management interface, user maycreate each performance measure task, produce each perfor-mance report, understand the BSS system’s performance in-dexes. By analyzing the information, the maintenance person-nel may detect load distribution status of the network in time,and regulate network parameters to enhance the network per-formance.

Through signaling tracing interface, user may trace the signal-ing which BSS involves (including Gb port signaling), facilitat-ing review of various signaling flow during system deploymentand maintenance process, and user may detect various typesof problems in the signaling coordination process.

� Analyzing through instruments and meters

One of the most useful troubleshooting methods is to use testinstruments and meters that measure the system running in-dexes and environmental indexes. User can compare thoseindexes with normal instruments and meters to find out thecauses for the errors.

Maintenance personnel use test handset, spectrometer, sig-naling analyzer, error code analyzer and other auxiliary equip-ments, to perform the fault analysis, fault location and elimi-nation.

� Plug-out and Plug-in correction method

When a board defect is detected, user may plug-in and plug-out the boards or the external interface ports, so as to fix de-fects caused by poor connection.

� Comparison method and swap method

Comparison method is the method of comparing possibly de-fective board with similar board in the system (for exampleboards of same slot position in multi-module) for operationalstatus, jumper or connection wire comparison. Through thecomparison, user may determine whether the board has fail-ure.

Swap method is helpful to replace a potentially damaged boardwith a new part to see if the problem is removed. If yes, itmeans that the source of the problem is located. Swap methodis also called as trial and error method, simple and practicallyfeasible in almost every fault handling. However, note that thisoperation must be performed in safe time.

In addition, comparing the status, parameters, log file, andconfiguration parameters of the potentially damaged parts withthe normal values helps find out any inconsistency. Modifyingand testing those values at a safe time can sometimes solvethe problems.


Chapter 2 Maintenance Overview

� Isolation method

When system has faults in some parts, user may separates thefaulty parts from the related board or rack, to judges whetherthe failure is caused by inter connecting.

� Self-checking method

When system or single board is restarted, user may check forerror through self-checking. Commonly engineering personnelcan check board performance when system restarted, in whichthe indicators would flash with a certain regular pattern. Byobserving the flashing pattern, user may determine whetherthe board has problem.

� Synthesis method

In the actual operation, above methods will be combined. Withthe experience of maintenance personnel, various kind of de-fects in the Maintenance process could be fixed.

Common MaintenanceChecks and PrecautionsChecks and precautions for daily maintenance are as follows:

� Maintain normal temperature/humidity in the equipment room.Keep the environment tidy and clean, free from dust and mois-ture. Keep rodents or insects out of the equipment room.

� Ensure that the primary power of the system is stable and reli-able, and check the system grounding and lightning protectionground periodically. Especially before storm seasons and afterthunder storms, check the lightning protection system to makesure all the facilities are in good conditions.

� Establish a full-blown system for maintaining the equipmentroom, to govern the routine work of the maintenance person-nel. An exhaustive duty log should be maintained, to providedetails about system operation, version, data change, upgrad-ing and troubleshooting on day-to-day basis for follow-up anal-ysis and troubleshooting in the event of a fault. Prepare a shiftrecord to clearly define everyone’s responsibility.

� Do not play games or access Internet through terminal. Donot install, run and copy any other software unrelated withthe system at the terminal. Do not use the terminal for otherpurposes.

� Set different NM passwords for different access rights, putthem under strict control and change them periodically. Also,keep the NM passwords accessible only to the maintenancepersonnel.

� The maintenance personnel should receive pre—job training,to learn about the equipment and networks. During mainte-nance operations, they must follow the instructions describedin the manuals related to the NetNumen M31 equipment. Be-



fore contact with the hardware, they must wear an antistaticwrist strap to avoid any static discharge damaging the system.

The maintenance personnel shall be strict in their work andproficient in maintenance, and improve their maintenance pro-ficiency through constant learning.

� Do not reset the equipment, load or change equipment dataat will. In particular, never change the data contained in theNM database at random. Back up the data before making anychanges. Do not delete the backup data until the equipmentruns properly for some time (usually a week) after changingthe data. Maintain a record of the data changes in time.

� The following common user instruments and meters shall behandy: screwdriver (cross or flat head), signaling analyzer,network cable clamp, multimeter, AC power used for mainte-nance, telephone line and network cables. Be sure to test andcalibrate the instruments and meters at regular intervals, toensure their accuracy.

� Check the spare parts and components regularly. Be sure tomaintain a sufficient inventory of common spare parts andcomponents, and verify that they are in good condition. Makesure that they are free of moisture and mould. The spare partsand components must be isolated from those defective onesreplaced during maintenance, and labeled for easy identifica-tion. The common-use spare parts and components must bereplenished in time when used up.

� The software and documentations for potential use duringmaintenance shall be kept at hand at certain place, so thatthey are easy to reach for when necessary.

� Make sure that the lighting in the equipment room is goodenough for the maintenance. Once damaged, the lightingequipment shall be repaired in time, to avoid any inconve-nience during maintenance.

� Resolve any fault as soon as it is detected. In case of anyproblem that cannot be resolved, please contact the local ZTEoffice.

� Put the contact information of the local ZTE office in a promi-nent place, and make it known to all the maintenance person-nel. This would help to contact ZTE for support in time. Updatelatest contact information if it has been changed.

� It is prohibited to run signaling trace program, especially indaytime when traffic load is busy. Signaling trace can be per-formed only under permission from ZTE local office, and in lowcommunication traffic period.


C h a p t e r 3

Daily RoutineMaintenance

Table of ContentsDaily Routine Maintenance Items.........................................11Checking Equipment Room Temperature ...............................12Checking Equipment Room Humidity ....................................13Checking Running Status of Air-conditioning .........................14Checking Communication Between Server and Client..............14Checking Communication Between Server and Low-Level .........16Checking Hardware............................................................18Checking Server ................................................................19Checking Dual Server System Operation Status .....................20Checking Alarms ...............................................................21Checking Operation Logs ....................................................23Checking Disk Array...........................................................24Backing up Data................................................................24Checking System Load .......................................................25Checking Virus Monitoring Result in Real Time .......................26

Daily Routine MaintenanceItemsTable 3 lists the check items to check everyday.

TABLE 3 LIST OF DAILY ROUTINE MAINTENANCE ITEMS

Daily maintenance items Check Items

Temperature and humidity inequipment roomEnvironment monitoring

maintenanceAir-conditioning running status

Communication between serverand client

Communication between serverand lower level NM

Hardware

Maintenance of running status ofmain devices



Daily maintenance items Check Items

Server

Dual Server Operational status

Alarms

Disk Array operational status

Operation logs

Hardware of disk array

Data backup

System Load

Virus Monitoring Result

Checking Equipment RoomTemperature

Purpose The equipment runs normally within an appropriate temperaturerange. By checking equipment room temperature, it can be avoidthat an over-high or over-low temperature makes adverse influ-ences on the system running.

Method Take the temperature reading from thermometer.

Referencestandard

Refer to Table 4 for required temperature of NetNumen M31 (RAN)system.

TABLE 4 NETNUMEN M31 SYSTEM TEMPERATURE REQUIREMENTS

Temperature

Equipment Type Long-term workingconditions

Short-term workingconditions

NetNumen M31 (RAN)Element Managementsystem

0℃~40 ℃ -5℃~45 ℃

Note:

The temperature and humidity of the operating environment insidethe equipment room are measured at the spot that is 1.5m abovethe floor and 0.4m before the rack when there is no protectiveplate in front or back of the equipment rack.

Note:


Chapter 3 Daily Routine Maintenance

Short-term working conditions mean that the successive operatingtime is not more than 48 hours and the accumulated operatingtime per year is not more than 5 days.

Checking Equipment RoomHumidity

Purpose The equipment runs normally within an appropriate humidityrange. By checking equipment room humidity, it can be avoidthat an over-high or over-low humidity makes adverse influenceson the system running.

Method Read the humidity level from hygrometer.

ReferenceStandard

Refer to Table 5 for required temperature of NetNumen M31 sys-tem.

TABLE 5 NETNUMEN M31 SYSTEM TEMPERATURE REQUIREMENTS

Temperature

Equipment Type Long-term workingconditions

Short-term workingconditions

NetNumen M31Element Managementsystem

20 % ~ 90 % 5 % ~ 95 %

Note:

The temperature and humidity of the operating environment insidethe equipment room are measured at the spot that is 1.5m abovethe floor and 0.4m before the rack when there is no protectiveplate in front or back of the equipment rack.

Note:

Short-term working conditions mean that the successive operatingtime is not more than 48 hours and the accumulated operatingtime per year is not more than 5 days.



Checking Running Status ofAir-conditioning

Purpose Perform this procedure to ensure the normal running status of air-conditioning and maintain the humidity and temperature of theequipment room in normal range.

Procedure Check the running status of air-conditioning. Repair or replace itif there are any abnormalities.

Result The air-conditioning runs normally.

Checking CommunicationBetween Server and Client

Context Perform this procedure to ensure that the communication betweenthe server and client of NetNumen M31 (RAN) is normal:

Steps 1. Click Start > Run on the client of NetNumen M31(RAN) systemand ping the IP address of the server to check if the commu-nication between them is normal.

2. Start NetNumen M31 (RAN) server console on server to exam-ine whether process initiation could start, as shown in Figure 1.This includes FTP process and NetNumen M31 (RAN) networkmanagement process.

FIGURE 1 INSPECT COMMUNICATION BETWEEN NETWORK MANAGEMENTSERVER AND CLIENT—I



Note:

If NetNumen M31 needs to link to NMS, user must enter CORBAnotice service process tab window before FTP process and Net-Numen M31 (RAN) network management process self starts,click start button to start CORBA service manually. User alsoneeds to check whether CORBA notice service to starts nor-mally.

3. On client computer, start NetNumen M31 client and input username and password, as shown in Figure 2. Inspect whetherlog in succeeds.

FIGURE 2 INSPECT COMMUNICATION BETWEEN NETWORK MANAGEMENTSERVER AND CLIENT-II

4. After successfully log in, the interface appears, as shown inFigure 3.



FIGURE 3 INSPECT COMMUNICATION BETWEEN NETWORK MANAGEMENTSERVER AND CLIENT - III

END OF STEPS

Result Expected Result:

The response of the server is normal.

Checking CommunicationBetween Server andLow-Level

Context Perform the following procedure to ensure that the communica-tion between the server and low level NM of NetNumen M31(RAN)system is normal.

Steps 1. Click Start > Run on the server of NetNumen M31 system andping the IP address of the low—level NM machine of the serverto check if the communication between them is normal.

2. Log in NetNumen M31(RAN) client, and enter into the Topol-ogy Management view.

3. Inspect server and OMM relation Topology Map, as shown inFigure 4.



FIGURE 4 INSPECT COMMUNICATION BETWEEN NETWORK MANAGEMENTSERVER AND LOWER LEVEL NETWORK MANAGEMENT (1)

4. If link line is not shown between Net Elements in the map, thenselect topology root node NetNumen and right-click on it andsingle click on EXPAND ONE LAYER from pop-up menu, asshown in Figure 5.

FIGURE 5 INSPECT COMMUNICATION BETWEEN NETWORK MANAGEMENTSERVER AND LOWER LEVEL NETWORK MANAGEMENT (2)

5. Inspect lines between NetNumen and each OMM. Green linemeans communication is normal, black line means no man-agement, red line means link interrupted.



6. Check for interrupted links and their alarms of NetNumen andOMM.

7. Run ftp<IP address> < FTP port> command on NetNumen tocheck whether FTP link to OMM works, as shown in Figure 6 .

FIGURE 6 CHECK COMMUNICATION BETWEEN NM SERVER AND LOWERLEVEL NM (3)

Note:

Here OMM is FTP SERVER, uep is default user ofFTP.10.61.100.113 is IP address of OMM. 21 is default FTPport, whose value is input according to actual condition

END OF STEPS


The status of communication link between the server and the lowlevel NM is normal.

Checking HardwareContext Perform the following steps to ensure the hardware works nor-

mally.

Steps 1. Check if the indicators of routers and switches are normal.

2. Check the alarms of links in NetNumen M31 (RAN) system tosee if the link between server and client as well as the linkbetween server and interface machine are normal.

3. Check if there are any fault indications (if the yellow indicatoron the lower part of the disk flashes, it indicates that the disk



faulty) related to hard disks of dual-computer server and diskarray in NetNumen M31 (RAN) system.

END OF STEPS

Result Expected Result are:

� Indicators of routers and switches are normal.

� The link between server and client as well as the link betweenserver and interface machine are normal.

� There are no fault indications related to the hard disks of dual-server and disk array.

Checking ServerContext Perform this procedure to ensure the server of NetNumen M31

(RAN) system runs normally.

Steps 1. Check if there is any abnormal information on the service inter-face of application server when NetNumen M31 (RAN) systemis running, as shown in Figure 7.

FIGURE 7 INSPECT SERVER OPERATION STATUS



Note:

If NetNumen M31 requires NMS connection, user needs tocheck CORBA notification service progress too.

2. On server, run #ps -ef|grep java java command to checkoperation status of server.

END OF STEPS


There is no abnormal information such as interrupted communi-cation link.

Checking Dual ServerSystem Operation Status

Short Description User may wants to restart or shut down the system for to someparticular reason. For different operation objects, the methods ofrestarting or shutting down are different. For a backup node, usermay restart or shut down directly. But for master node, user mustswitch global resource group to back up system before restartingor shutting downmaster node. This ensures NetNumen applicationto provide non-stop service, as manual shutting down or restartingdoes not switch global resource group automatically.

Context Perform the following checks to check dual server system opera-tion status:

Steps 1. Open server cabinet, inspect the front panel of each serverequipment for red indicator alarm.

2. Inspect each server monitor for any abnormal alarm.

3. On server, execute #ps -ef|grep java to check server opera-tion status.

4. Execute #hagui & command log in VCS GUI to check properlogging in operation into VCS.

5. On server terminal, execute # vxprint -htr command, tocheck system general status .

6. On server terminal, execute #vradmin -gdgnetnumen1repstatus rvgnetnumen1 command, to check data copystatus.

7. On server terminal, execute # vxdisk list command, to checkhard disk status.

8. On server terminal, execute # vxprint -lP command, to checklink status.

9. On server terminal, execute # vxdisk -o alldgs list diskgroup command, to check disk group status.



10.On server terminal, execute # vxprint -l lvomc command, tocheck volume status.

Note:

For more dual system operation, refer to NetNumenM31 (RAN)(V3.10.410) Mobile Network Element Management SystemHigh Availability Feature Description Manual.

END OF STEPS

Checking AlarmsContext Check alarm information of the managed network element in man-

agement system to find the running status of the system as fol-lows:

Steps 1. Check system alarm in Fault Management to see if there areany alarms or fault indications.

i. After successful logging into the NetNumen M31(RAN)client click View > Fault Management, Fault Man-agement window appears, as shown in Figure 8. InFault Management interface by default Realtime AlarmMonitor window appears.

FIGURE 8 REAL TIME ALARM MONITOR WINDOW

ii. To view Realtime Notification Monitor click View > Re-altime Notification Monitor in Fault management in-terface.



2. Check the operation logs of NetNumen M31 system to see ifthere are any abnormal records related to the operations.

3. Check the real-time alarms, notifications and current alarmsto find out the causes of alarms and then solve the problem.At the same time, remember to back up the alarms. To viewthe detailed information of the alarms double click on partic-ular alarm, it NetNumen application displays Details windowopens, as shown in Figure 9.

FIGURE 9 SHOWING ALARM DETAILS

Note:

For more details about how to take alarm backup, refer to chap-ter Data Backup and Recovery.

END OF STEPS


� There are no alarms or other abnormal indications in fault man-agement.

� There are no abnormal records in operation logs.

� The cause of the alarm is found out and alarm backup is com-pleted.



Checking Operation LogsContext Check operation log , security log and operation log of NetNumen

M31(RAN) to obtain operating status of the system.

� operation log

This log records users operation information, including log ID,operation level, user name, operation name, host address,command function/detailed info, operation result, cause of fail-ure, access method, operation objective, operation startingtime, operation ending time and related log information.

� Security Log

This log records user logging in information, including log ID,user name, host address, log name, operation time, accessmethod and detailed information.

� System log

This log records server status of scheduled tasks, including logID, level, source, log name, detailed information, host address,operation start time.

Steps 1. Click View> LogManagementmenu, enter log managementview.

2. Select Operation Log from left pane of Long Managementwindow, all log operations displays in right pane, as shownin Figure 10. Check for abnormal records in Operation Logwindow.

FIGURE 10 OPERATION LOG WINDOW

3. Follow the same procedure to check Security Log and SystemLog.

END OF STEPS




There are no abnormal operation records and no unauthorized op-erations, which may adversely influence the system running.

Checking Disk ArrayContext Perform this procedure to ensure that the disk array works nor-

mally and to check if there is enough free disk space.

Steps 1. Check for adequate free space in the hard disks of disk arrayto avoid interruption of alarm and performance data collectionperformed by network management and of report generation.

2. Check if hard disks have any faults related to writing or reading.Please contact ZTE for help if there are any faults.

3. Hard disk checking procedure:

i. Check Indicator

ii. Run Format command on NetNumen server as root userand print current normal hard disk.

� The disk array must have enough free space. If the freespace is not enough, add more disks or delete alarm andperformance data after backup.

� The hard disk has no writing or reading problems. If thereare any, please contact ZTE for help.

END OF STEPS

Backing up DataContext Back up the data to ensure the quick system recovery, in case of

system crash.

Data Backup is done for NM configuration data. It is implementedwith a tool under database management system.

Data backup conditions and period:

� Be sure to backup the data before any data change.

� Back up the data after configuration is performed.

� If no data is modified, it is recommended to backup data onweekly basis.

� In addition to hard disk, backed up data should be stored onthe Managed Object (MO) disk.

Data backupmodes include immediate backup and periodic backup(weekly).

� Immediate backup



Immediate backup refers to the backup conducted by databacking up tool in NetNumen M31 (RAN) system. This toolhelps in database backup of configuration data and can be usedto quickly restore the system before the change had occurred.

� Periodic backup (weekly)

For more details refer to Weekly Routine Maintenance Items.

Note:

Alarm data back up includes history alarms and notification alarms,performance data backup includes primary data, hourly data andweekly data, log data backup includes operation log, security logand system log . The data above are manually or automaticallybacked up by table group task, in which automatically backup isperformed periodically. When defining table group task, user maydefine solution of cleaning data.

Steps 1. For detailed information about how to take backing up of alarmdata, performance data and log data, refer to Database TablesBackup and Recovery

2. For configuration data backup CM Data Backup and Recovery.

END OF STEPS

Result � Check system log in log management, check for task executionstatus. For detailed operation refer to specific operation.

� Check save path of data backup for backed up data.

Checking System LoadContext Checking system load is to see if the load exceeds the threshold.

Steps 1. Log on OMC client and check if there is any over-thresholdalarms.

2. On System Management click Application Serve > Serverperformance>. Server performance window appears asshown in Figure 11.



FIGURE 11 SERVER PERFORMANCE WINDOW

END OF STEPS


Server performance is good with low usage level.

Checking Virus MonitoringResult in Real Time

Context Perform following procedure to check if the OS has virus.

Steps 1. Check the realtime monitoring system of anti-virus softwareon NM server and NM client.

2. For the files infected with virus, kill virus by related anti-virussoftware.

3. Solaris system does not need antivirus software. It usuallydoes not infect virus when SAMBA service is not running. Withdefault installation configuration, Solaris system does not runSAMBA service, user may execute ps -ef |grep samba com-mand to check if SAMBA is started. If SAMBA service is run-



ning, then execute /etc/init.d/samba stop command at rootuser to stop SAMBA service.

Note:

In Unix system , SAMBA is a software package for sharing Unixfile and print service between computers in network by servermessage block protocol SMB.

END OF STEPS


There is no virus in NM server and NM client.





C h a p t e r 4

Weekly RoutineMaintenance

Table of ContentsWeekly Routine Maintenance Items ......................................29Checking History Alarm ......................................................30Checking Scheduled Query Task ..........................................30Calibrating System Time.....................................................31Checking Database Space...................................................32Checking Shared Folders on Client ......................................33Updating Antivirus Software................................................34Checking Server Progress Status .........................................35Backing up Data................................................................36Checking Server Error Logs ................................................37Checking Server Disk Storage Capacity ................................38Checking Client Hard Disk Space ........................................39

Weekly RoutineMaintenance ItemsList of Weekly Maintenance Items of NetNumen M31(RAN) MobileNet Element Management system is as shown in Table 6.

TABLE 6 WEEKLY ROUTINES FOR MAINTENANCE CHECKLIST

Category Test Item

Check Historical Alarm.

Check Server Progress Status.

Calibrate System Time.

Check Disk space of the server.

Check Shared Directory on ClientComputer.

Update Antivirus software .

Running Status of Main Equipment



Category Test Item

Periodic data backup.

Operation and maintenance logbackup.

Check Client Hard Disk Space.

Check Server Error Log.

Check Server Disk Capacity.

Checking History AlarmContext Check the history alarms to analyze for the cause of alarm and

solve the problem. Procedure to check the history alarm is shownbelow:

Steps 1. From main window of Netnumen client, Click View > FaultManagement to pop-up Fault Management window.

2. From left pane of Fault Management window right-click onNetwork Element (NE) to select Show History Alarms fromthe pop-up menu.

3. History Alarm window appears which shows history alarm listof the particular NE.

END OF STEPS

Checking Scheduled QueryTask

Context Check whether scheduled query task has been executed success-fully and whether it expires or suspended.

Note:

Performance management sub-system counts measurementof some performance parameters and service data to presentperformance index of the system. Through scheduled query task,the system periodically counts performance of specified object asscheduled to acquire system performance.

Procedure to check the scheduled query task is as follows:

Steps 1. Click View > Performance Management form main menuof NetNumen to enter Performance Management window.


Chapter 4 Weekly Routine Maintenance

2. From Performance Management window click Perfor-mance Management > Timer Query Task Management.

3. Timer Query TaskManagementwindow will pops up to showthe scheduled query task for user to check for necessary tasks.

4. If the tasks required does not exist, user may create newscheduled query task and configure it to the items and peri-ods as required.

Note:

For more information refer to NetnumenM31(RAN ) Mobile Net-work Element Management System Performance ManagementOperation Guide.

5. If the required task exists, it is suggested to check the valida-tion period of the task, and modify the date if it is to expiringsoon.

6. Select a task in Timer Query Task Management list whoseexecution log is shown in the Timer Query Task Log Listbelow. Check result of execution, as sown in Figure 12.

FIGURE 12 TIMER QUERY TASK

7. A survey report file will be generated accordingly after success-ful completion of the task.

END OF STEPS

Calibrating System TimeContext To make sure system time of OMM is consistent with Netnumen

server management system.



Steps 1. Run date command to check time on Netnumen Server.

2. Check the time on OMM.

3. Check OMM for time consistency with Netnumen Server.

4. If inconsistency exists, refer to topic Chaotic PerformanceAlarm Data Caused By Synchronization Error between Upperand Lower Level .

END OF STEPS

Checking Database SpaceContext Check database storage space to avoid interference caused by in-

sufficient storage space in the system during normal operation.Perform the following procedure to check database space.

Steps 1. Log in NetNumen M31 client and click View > System Man-agement.

2. System pops up SystemManagement window. From SystemManagement click on Database > Database Login.

3. Database Login window pops up. Input Password and clickOK, as shown in Figure 13.

FIGURE 13 CHECK DATABASE SPACE (1)

4. System prompts database login successful, then click OK.

5. Select database server, then click menu DatabaseServer >View Database Resources. View Database Resourceswindow pops-up, as shown in Figure 14.



FIGURE 14 CHECKING DATABASE SPACE (2)

6. Click Tablespace Information and check Free percentage.

END OF STEPS

Result Expected result

Disk space of NetNumen M31 server is no less than 800 M. Andthe free space of each disk should be 20% of the whole space.Otherwise, it is necessary to delete some unused files.

Checking Shared Folders onClient

Short Description When system has useless shared folders, it causes additional bur-den to the system, and security problem is also likely to happen.So check and cancel shared folders regularly.

Context Perform the following steps to cancel the shared folders:

Steps 1. Click Start > My Computer > Shared documents to pop-upShared Document window.

2. Check for shared directories and cancel the unnecessary shar-ing.

END OF STEPS

Result No unnecessarily shared folder exists.



Updating Antivirus SoftwareShort Description This topic describes the procedure to update antivirus for weekly

routine maintenance.

Prerequisites McAfee antivirus software is installed on the system.

Context To update antivirus, perform the following steps.

Steps 1. Right-click icon on taskbar and then click About frompopup menu on Windows taskbar.

FIGURE 15 VIRUS UPDATE INFORMATION

If Then

Last update time is within aweek

No need to update

Last update time is not within aweek

Proceed with step 3

2. Check Last update time and then click OK on ePolicy Or-chestrator Agent dialog box, as shown in Figure 15.

3. Right-click icon and then click Update Now from popupmenu onWindows taskbar. McAfee AutoUpdatewindow popsup, as shown in Figure 16



FIGURE 16 MCAFEE AUTO UPDATE DIALOG BOX

Note:

Links for downloading latest virus definitions files for upgrad-ing are as follows. McAfee Enterprise antivirus software canbe downloaded from the website: http://www.mcafeesecu-rity.com/cn/downloads/default.asp.

END OF STEPS

Checking Server ProgressStatus

Context To Ensure the normal operation of NetNumen M31(RAN) manage-ment system server.

Steps 1. Open Unified network management system console ofNetNumen M31(RAN) server, and check for the abnormal mes-sage, such as abnormal reboot progress etc., as shown in Fig-ure 17.



FIGURE 17 CHECK SERVER OPERATION STATUS

Note:

If NetNumen M31 requires NMS (Network Management Sys-tem) connection, user must check CORBA notification serviceprogress.

2. Execute #ps -ef|grep java command on server to checkserver operation status.

END OF STEPS

Result Server progress starts without error.

Backing up DataContext Data backup in NetNumen M31 is mostly about backup alarm data

(notification alarm and history alarm), performance data, log data,configuration data. When the alarm data, performance data andlog data reaches certain amount, they would occupy too muchdatabase table space and hard disk space and it effects normaloperation of the system. Back up data has the following purposes:

� Quick restoration for inspection and review.

� Clear data after taking backed up to release storage space.



Note:

The alarm data being backed up includes history alarm and alarmnotification. The performance data being backed up include rawdata, hour data and weekly data. The log data being backed upincludes operation log, secure log and system log. The backupof data above are performed by manually or automatically tablecollection task, in which automatically backup is on periodical fre-quency. Besides table collection task definition, user may definescheme to clean data.

Perform the following procedure to back up the data:

Steps 1. For detailed information about how to back up alarm data, per-formance data and log data, refer to Database Tables Backupand Recovery

2. For configuration data backup, refer to CM Data Backup andRecovery.

END OF STEPS

Result Backup completes without error.

� Check system log in log management, check for task executionstatus. For detailed operation refer to specific operation.:

� Check save path of data backup for backed—up data.

Checking Server Error LogsContext Check server error logs to ensure to find the system running acci-

dents in time. Error log record information will be used in systemoperation analysis. Perform the following steps to check servererror logs:

Steps 1. server error record is saved in server log file ( installation di-rectory /ums-svr/log).

2. If dual system is used for backup server, user needs to backuplog file in backup server.

3. Use FTP tool to download log file backed up to local client.

4. In addition to the dual-computer server, it is also necessary tocheck if there are any latest error log files in the log directoryof the NM server.

5. Feed back the error log file (if any) to the local ZTE office im-mediately.

END OF STEPS

Result Inspection Criteria

Deal with the error log files properly.



Checking Server DiskStorage Capacity

Context Perform this procedure to ensure enough disk space of NetNumenM31 server. and check server file system space usage.

Steps 1. On System Management click Application Server >Server performance Server performance window appearsas shown in figure to view real-time conditions of CPU, mem-ory and hard disk usage percentage, as shown in Figure 18.

FIGURE 18 CHECK SERVER DISK STORAGE CAPACITY (1)

2. Or execute #df –k command on server to check disk usage.

3. If dual system server is used, perform the same operation onthe other computer to check disk usage.

Free disk space on dual system server cannot be less than500M. If free space is less than 500M, user should backup re-lated files and clear files which are taken backup.

END OF STEPS



Checking Client Hard DiskSpace

Context Check the free space on client terminal hard disk to ensure normaloperation of the system. The steps to check disk space in Windowsoperation system is explained below.

Steps 1. Open My Computer and right-click on each hard disk driveand select Properties from popup menu. Properties windowappears in properties window user can check total space andfree space of each hard disk.

2. Check each disk for unused files and folder to delete.

The operation system disk and application program disk shouldhave at least 800 M free space. Other disks must have freespace not lower than 20% of disk space. If it is not, deletinguseless files is necessary.

END OF STEPS





C h a p t e r 5

Monthly RoutineMaintenance

Table of ContentsMonthly Routine Maintenance Items.....................................41Checking Power Supply Voltage ...........................................42Cleaning Dust on Cabinet ...................................................42Checking Table Space Usage ..............................................43Checking Performance Statistic Result of Operation Network......................................................................................44Checking Dual System Operation Status ..............................45Monitoring Test .................................................................46

Monthly RoutineMaintenance ItemsMonthly routine maintenance items of NetNumen M31(RAN) sys-tem is as shown in Table 8.

TABLE 8 MONTHLY ROUTINE MAINTENANCE CHECKLIST

Category Test Item

Power supply voltage.Environment monitoringmaintenance

Clean Equipment.

Monitoring Test, dual-computerrunning status.

Check table space usage.

Check data secondary backup.

Check Performance StatisticResult of Operation Network.

Running Status of Main Equipment

Checking operational status of thefans.



Checking Power SupplyVoltage

Context Perform this procedure to ensure that power supply is in good con-dition.

Steps 1. Check voltage and frequency values of the power supply equip-ment.

END OF STEPS

Result The nominal value of the input power is 220V, single phase ACpower supply. The allowed input voltage ranges from 176V to 264VAC, and the frequency ranges from 45Hz to 65Hz.

Power supply range of NetNumen M31(RAN) system is as shownin Table 9.

TABLE 9 POWER SUPPLY RANGE OF NETNUMEN M31 SYSTEM

Parameter Specific Index

Operating power supply 220V, 50Hz

Voltage range 176V~264V

Voltage frequency range 45Hz~65Hz

Cleaning Dust on CabinetShort Description Dust has serious negative effect on computer and PCBs as ex-

cessive dust accumulation could cause short circuit to electroniccomponents. This topic describes the procedure to check the duston cabinet for weekly routine maintenance.

Prerequisites Check antistatic wrist strap is available in equipment room.

Context To check dust on cabinet, perform the following steps.

Steps 1. Wear an anti-static wrist strap.

2. Check the dust on surface of server and cabinet.

3. Check dust in gaps between PCB boards, disk array and cabi-net.

4. If the cabinet, server and the surrounding environment isdusty, clean them thoroughly.

END OF STEPS

Postrequisite If dust is present on the cabinet, use cleaner or soft brush to cleanthe dust.


Chapter 5 Monthly Routine Maintenance

Note:

Clean the equipment on regular basis.

Checking Table SpaceUsage

Short Description Check database space, prevent insufficient database table spacefrom jeopardizing system operation.

Context Perform the following steps to check table space usage:

Steps 1. Login NetNumen M31(RAN) client, from main window of Net-Numen click View > System Management.

2. System Management window opens. Right-click databaseserver to and select Database Login from pop-up menu.

3. The system pops up Database Login dialogue box, then inputpassword and click OK button, as shown in Figure 19.

FIGURE 19 DATABASE LOGIN WINDOW

4. The system prompts Database Login successful . Click OKto confirm.

5. Select target database server and click DatabaseServer >View Database Resource from main menu. The systempops-up View Database Resource dialogue box, as shownin Figure 20.



FIGURE 20 VIEW DATABASE RESOURCE(2)

6. Click Table Space Information tab and to view free spacepercentage.

Usage percentage of any table space is not higher than 90. Iftable space is not enough, increase the space assigned to datafile, or backup and delete useless data record.

END OF STEPS

Checking PerformanceStatistic Result of OperationNetwork

Context Check files generated in timer query task, check relevant perfor-mance, and backup according to requirements.

Steps 1. To check task for expiry date and check task execution whenerror occur. For procedure and more details, refer to CheckingScheduled Query Task topic.

2. Check the detailed information of the file generated, such asfile name, start time and end time, as shown in Figure 21.



FIGURE 21 CHECK PERFORMANCE STATISTIC RESULT OF OPERATIONNETWORK

3. The report file generated is saved in path:..\ZXM-INOS\ums-svr\deploy\runtime\platform\csp-pm-osf\querytask.User may determine system operation status by analyzingperformance statistic report generated.

4. Set up performance statistic backup directory on the harddisk of net manager client to backup details of monthly data.Backup in other media (such as MO disk) is applicable ifnecessary. (optional).

END OF STEPS

Checking Dual SystemOperation Status

Short Description User may restart or shut down the system for some particular pur-pose. For different operation objects, the methods of restarting orshutting down are different. For a backup node, user may restartor shut down directly. But for master node, user must switch overto global resource group to back up system before restarting orshutting down master node. This ensures NetNumen applicationto provide non-stop service. Manual shutting down or restartingdoes not switch over to global resource group automatically.

Context Procedure for checking dual system operation status:

Steps 1. Open server cabinet, inspect the front panel of each serverequipment for red indicator alarm.

2. Check each server monitor for application abnormal alarm.

3. On server, execute #ps -ef|grep java to check server opera-tion status.



4. Execute #hagui & command log in VCS GUI to check properlogging in operation into VCS.

5. On server terminal, execute # vxprint -htr command, tocheck system general status.

6. On server terminal, execute #vradmin -gdgnetnumen1repstatusrvgnetnumen command, to check data copy status.

7. On server terminal, execute # vxdisk list command, to checkhard disk status.

8. On server terminal, execute # vxprint -lP command, to checklink status.

9. On server terminal, execute # vxdisk -o alldgs list disk groupcommand, to check disk group status.

10.On server terminal, execute # vxprint -l lvomc command, tocheck volume status.

Note:

For more details about dual system operations, please see Net-NumenM31 (RAN) (V3.10.410) Mobile Network Element Man-agement System High Availability Feature Description Manual.

END OF STEPS

Result Expected result:

Dual system is working normally, there are no alarms.

Monitoring TestShort Description Monitoring test is a crucial job in daily operation and maintenance.

Maintenance operators can check if NetNumen M31 runs normallythrough the monitoring test system to locate and process faultsin time and ensure the reliable running of NetNumen M31. Moni-toring test provides instant monitoring test for all the processingprocedures of NetNumen M31, which may help to prevent poten-tial troubles.

Context To monitor test, perform the following steps:

Steps 1. Select Help > About item on the menu bar of NetNumen M31client, the About dialog box pops up, switch to the Informa-tion tab, as shown in Figure 22.



FIGURE 22 ABOUT INTERFACE

2. Click the buttonMemory monitor, theMemory Monitor dia-log box pops up, as shown in Figure 23. Click the button ForceGC to call back memory occupied by JAVA running programsforcedly. GC is garbage memory collection.

FIGURE 23 MEMORY MONITOR

3. Suggestions for before doing this test:

i. Because monitoring test brings more load to NetNumenM31 system, it is recommended to arrange the monitor-ing test at about 2 o’clock AM once in a month to avoidtraffic peak.



ii. Analyze the result of monitoring test. If the faults and ab-normalities that cannot be located, please save the moni-toring results and contact the local ZTE office for technicalsupport.

END OF STEPS


The monitoring results have no abnormality. If they have, handlethe trouble as soon as possible, and remove hidden troubles andfaults.


C h a p t e r 6

Quarterly Maintenance

Table of ContentsQuarterly Maintenance Items ..............................................49Checking Dual Server System Switching ...............................50Checking Ground Resistance ...............................................53Clearing History Alarm .......................................................53Deleting Performance Database...........................................55Checking Unauthorized Access of Server...............................57Checking Firewall .............................................................57Checking LAN Equipment....................................................58

Quarterly Maintenance ItemsTable 10 shows the quarterly maintenance items of NetNumenM31(RAN).

TABLE 10 LIST OF WEEKLY MAINTENANCE ITEMS

Category Check items

Check grounding resistance

Check the dual-system switch.

Check history alarm automaticcleaning function for its normaloperation.

Check performance dataautomatic cleaning functionfor its normal operation.

Check client for unauthorizedaccess.

Check server for unauthorizedaccess.

Check the LAN hardware.

Environment monitoring &maintenance

Check firewall installationconfiguration.



Checking Dual ServerSystem Switching

Short Description Occasionally users need to shutdown or reboot the system.Shutdown or rebooting of backup node system can be donedirectly. Shutdown or rebooting master system requires GlobalResource Group to be switched to backup system, in order toensure smooth running of netnumen applications. This is becausemanually shutting down or rebooting system does not trigger au-tomatic switch to Global Resource Group. So it is very importantto confirm Dual-system can switch normally, and operations arenormal after switching. It is recommended check this operationaround 1:00 am.

Context Perform the following steps to check dual server switching system:

Steps 1. Check backup server and master server configuration file, op-eration file to be consistent, perform backup to current routerinformation configuration with key check point in the normalrouting to lower level net manager. It should be able to com-municate by pinging.

2. Shutting down main server node and switching to backup nodeis explained below. For more details about dual system oper-ations refer to NetNumenM31 (RAN) (V3.10.410) Mobile Net-work Element Management System High Availability FeatureDescription Manual .

i. Right-click global resource of NetNumen and select Switchto > Remote Switch from popup menu, as shown in Fig-ure 24.

FIGURE 24 CHECK DUAL-SYSTEM SWITCHING (1)

3. Switch global group window appears. Select target Clusterand System from drop-down lists respectively, as shown inFigure 25. Click OK.


Chapter 6 Quarterly Maintenance


4. Question window appears for confirmation. Click Yes for con-firmation, as shown in Figure 26.


5. In status tab of Cluster Administrator window user can ob-serve that cluster status. Figure 27 shows that Global ResourceGroup netnumen in Cluster clsA1a is getting offline and Fig-ure 28 shows that Global Resource Group netnumen in ClusterclsA1a is offline.





6. After Cluster clsA1a innetnumen resource group is com-pletely offline, the resource group in Cluster clsB1b innetnumen starts getting online, the interface after complet-ing is as shown in Figure 29.


7. Observe for 30 minutes.

8. Reboot backup node EMSRANB1b when test result is normal.Observe if the server gets started normally.

9. Use the similar method to switch to the original master nodeEMSRANA1a.

10. Inspection Criteria :



i. Switching can be performed from master to backup nodeproperly, and also services can be taken over between thedual servers properly.

ii. Routing to lower level net manager is correct, lower levelnet manager could be pinging through.

i. The original client (modify link server as new IP address)can log into the server after switching.

Exception Processing

If it is detected cannot switch normally, it needs to analyzethe reason quickly and check the log record, find the re-source that cannot switch, then inform ZTE local office.

END OF STEPS

Checking GroundResistance

Context Perform this procedure to ensure ground resistance is within saferange.

Steps 1. Test the connection resistance of the rack.

2. Test the ground resistance in the equipment room.

3. Check the protective grounding wires.

4. Check the space between the protection ground and surround-ing signals as well as the space between the power supply andthe ground.

END OF STEPS

Result The expected results are as follows:

� The connection resistance range of the rack must be 0.1 Ω ~0.3 Ω.

� The ground resistance in the equipment room must be lessthan 1 Ω.

� If conditions permit, the PGND is connected to the groundthrough an independent grounding post.

� Sufficient space must be reserved between the PGND andsurrounding signals and between the power supply and theground, preventing any damage to boards due to high voltage.

Clearing History AlarmShort Description Clear historical alarms that are generated in last quarter to lessen

database load.



Steps 1. In database Table Collection Operation, find the table col-lection task to be checked, as shown in Figure 30. It will givethe table collection task name and execution interval period.

FIGURE 30 TABLE COLLECTION OPERATION WINDOW

2. Click View > Log Management to enter Log Managementwindow.

3. From left pane of Log Management window right-click onsystem log and select query system log from popup menu.

4. Query system log window appears.

5. In LogName field select database table collection task fromdrop down menu, as shown in Figure 31.

FIGURE 31 QUERY SYSTEM LOG

6. Click OK , check result is displayed in log list, as shown inFigure 32.



FIGURE 32 LOG RECORD

7. Task implementation period can be seen from the figure and itcan be compared with the table collection task period recordedin the first step of verify.

8. Double-click log to examine log detailed content, check for ab-normal record. No abnormal record table means task is exe-cuted successfully.

END OF STEPS


History alarm automatic cleaning task is executed normally.

Deleting PerformanceDatabase

Short Description Regularly delete database performance data may improve data-base operation speed.

Steps 1. In database Table Collection Operation, find the table col-lection task to be checked, as shown in Figure 33. It will giveperformance management data backup - RNC NE - Raw datatable collection task name and execution interval period.




2. Click View > Log Management to enter Log managementwindow.

3. From left pane of Log Management window right-click onsystem log and select query system log from popup menu.

4. Query system log window appears.

5. In LogName field select performance management databackup - RNC NE - raw data table from dropdown menu, asshown in Figure 34.

FIGURE 34 QUERY SYSTEM LOG

6. ClickOK, check result is displayed in log list, as shown in Figure35.

FIGURE 35 LOG RECORD WINDOW



7. Task implementation period can be seen from the figure and itcan be compared with the table collection task period recordedin the first step of verify.

8. Double-click log to examine log detailed content, check for ab-normal record. No abnormal record table means task is exe-cuted successfully.

END OF STEPS


The Performance data that are generated in last quarter arecleared.

Checking UnauthorizedAccess of Server

Short Description Check server for unauthorized access.

Steps 1. Execute the following commands as the root user.#prstat

2. Check and display information about active processes in sys-tem, look for abnormal process. Default setting of all informa-tion is sorted by the CPU occupancy rate.

END OF STEPS


No abnormal progress.

Checking FirewallShort Description Check firewall installation and configuration to prevent the illegal

access.

Context Checking procedure is as follows:

Steps 1. Check whether firewall whether it meets the ZTE standard.

2. Check whether firewall satisfy the needs of current networksecurity, for example: all intranet address to pass other net-works must make NAT conversion; Close all unused ports.

END OF STEPS

Result Inspection Criteria.

Firewall is properly installed and configured.



Checking LAN EquipmentShort Description This topic describes the procedure to check LAN equipment for

routine maintenance.

Context To check LAN equipment, perform the following steps.

Steps 1. Check indicators on switch and router is normal.

2. Check network setting are correct.

3. Check network cable connection with server/maintenance con-sole.

4. Check if the hard disks of dual-server and disk array in the cab-inet have fault indications. (If the red light flashes, it indicatesthat the hard disk has fault).

END OF STEPS


C h a p t e r 7

Maintenance RecordForm

Table of ContentsDaily Maintenance Form .....................................................59Weekly Maintenance Form ..................................................60Monthly Maintenance Form .................................................62Quarterly Maintenance Form ...............................................63

Daily Maintenance FormRecommended format of daily maintenance form is shown in Table11.

TABLE 11 DAILY MAINTENANCE RECORD FORM

Office Name Date: (MM-DD-YY)

On-duty time: Tillo’clock

Off-duty person: On-duty person:

Basic check items

1. Check the normality of the board indicator. Open the front door ofthe NetNumen M31 (RAN) system, and check the availability of thered-indicator alarm (check the module) on the boards.

[ ] Normal [ ] Abnormal

Abnormal descriptions:

2. Check the normality of the server indicator. Open the front door ofthe server cabinet, and check the availability of any alarm indicationon the server; switch the servers, and check if there is any programrunning the abnormal alarm prompt box on the window.



3. Query of the module alarm information. Enter Alarm managementat the maintenance terminal, check current alarms and history alarmsfor abnormities.



Office Name Date: (MM-DD-YY)

On-duty time: Tillo’clock

Off-duty person: On-duty person:



4. Check the backup of NetNumen M31RAN data configuration. Beforedoing any operation in data, user must do backup. Before any dataoperations, the data must be backed up.



5. Check the performance statistic data Check whether the CPUutilization (%), (each module) and memory (MEM) utilization (%)are normal.



Equipment room environment

1. Temperature (normal: 15℃~25℃) [ ] Normal [ ] Abnormal

2. Humidity (normal: 30%~70%) [ ] Normal [ ] Abnormal

3. Dustproof conditions (good, bad): [ ] Normal [ ] Abnormal

Unresolved problems:

Checked by monitor:

Weekly Maintenance FormRecommended format of weekly maintenance form is shown inTable 12.

TABLE 12 WEEKLY MAINTENANCE RECORD FORM

Office name: Date: (MM-DD-YY)

Maintenance project

1. History alarm backup: Since the system can automatically clearthe alarm log when the alarm logs in the alarm log database growinto a certain extent, it is recommended to periodically back upthe alarm record database. This can provide certain reference fortroubleshooting and awareness of networking running.

Maintenance result:


Chapter 7 Maintenance Record Form


Maintenance personnel: ............................................... Time:

2. O & M system log backup: Operation & Maintenance log ofNetNumen M31 (RAN) every week. User can use a date, such as20041201, to name a backup file. At the same time, it is also requiredto clear operation and maintenance records in the log file base.

Maintenance result:


3. Periodical data backup:

Maintenance result:


4. Check whether the static data and statistical data are set correctly.The maintenance personnel should check if the performance statistictask expires.

Maintenance result:


5. Check viruses on the server at the background. Make sure to selectCheck instead of killing virus directly, lest the file should be deleted,thus causing system fault and interrupting normal services.

Maintenance result:


6. Check the remaining space of each database on the databaseserver, for example, the available database space and the availablelog space.

Maintenance result:


Maintenance result:


7. Adjust system time: Calibrate system time on Net Manager serverper clock source.

Maintenance result:





Problems and solutions:


Monthly Maintenance FormRecommended format of monthly maintenance form is shown inTable 13.

TABLE 13 MONTHLY MAINTENANCE RECORD FORM


Maintenance project

1. Check power supply voltage: Check power supply voltage everymonth. The normal value of the input power is 220V, single phase ACpower, with the allowed input voltage ranging in176V ~ 264V AC, andthe frequency in 45Hz ~ 65Hz.

Maintenance result:


2. Clean the PC surface.

Maintenance result:


3. Performance statistic: monthly statistic report is generated everymonth. The maintenance personnel should back up the statistic dataevery month.

Maintenance result:


4. Check dual-computer switchover. The maintenance personnelshould check dual-system switchover every month.

Maintenance result:





Chapter 7 Maintenance Record Form

Quarterly Maintenance FormRecommended format of Quarterly maintenance form is as shownin Table 14.

TABLE 14 QUARTERLY MAINTENANCE RECORD FORM


Maintenance project

1. Ground resistance check: check grounding resistance on quarterlybasis. Machine room grounding resistance should be within 1Ω.Ther should be sufficient spacing between protective ground andsurrounding signal, power source and ground.

Maintenance result:


2. History alarms handling.

Maintenance result:


3. Clear the performance statistics library every three months.

Maintenance result:


4. Test each basic function of the system.

Maintenance result:








C h a p t e r 8

Common Alarms andFaults Handling

Table of ContentsOverview..........................................................................65Equipment Alarms .............................................................66Common Faults Handling ....................................................69

OverviewThere are four recommended alarm levels. The four alarm levels,which is displayed in the Severity Column of the alarm template,are indicated in descending order of severity as Critical, Major,Minorand Warning.

� Critical

Critical alarm affects all services and all NE resources.

� Major

Major alarm affects most services and resources.

� Minor

Minor alarm hinders the normal operation of some services.

� Warning

Warning alarm affects a certain service or resource.

There is no level classification for notification.

Caution:

Faults of the actual version may differ from what is described inthis manual due to frequent update of ZTE products and fast de-velopment of technologies. If you have found any fault that is notlisted in this manual, please contact the local ZTE office.

This chapter also introduces the troubleshooting to common faultsof NetNumen M31 (RAN) system.



Equipment AlarmsCommunication Alarms withLower-level NM

One communication alarm is described: Access Managed Object(AMO) link broken.

Symptom The broken AMO link causes the communication interruption.

Related Part NM server, lower-level NM interface machine and connected linksare involved.

Cause The network cable may be disconnected; or SWITCH, interfacemachine, network adapter of NM server fails. Interface machineis shutting down or starting.

Handling Check if the interface machine is running properly, if the networkcable and SWITCH work normally as well as if the network adapterof interface machine is normal.

Verification Communication links work normally.

DB Space Insufficient

Symptom Database space for NetNumen M31 alarm and performance statis-tical data storage is insufficient.

Related Part Database server.

Cause Causes of insufficient database space are as follows:

� Data have not been backed up for a long time and the previousbackup files have not been deleted.

� Disk capacity configured is too low due to underestimation onthe traffic load.

Handling To handle the problem, perform the following steps:

1. Check if periodic data backup is set and the backed up files aredeleted. To free the disk space immediately, backup files anddelete them manually.

2. Contact the local ZTE office for upgrading the disk to a highercapacity.

Verification The alarms disappear.

Precautions When the alarm occurs, system can still run; however, systemperformance is affected. It is recommended to handle the problemin a timely manner. Alarms disappear once the disk space is freed.


Chapter 8 Common Alarms and Faults Handling

CPU Occupancy of ApplicationServer above Threshold

Symptoms CPU occupancy of application server exceeds threshold.

Related part NetNumen M31 application server.

Cause Causes of the fault are as follows:

� It may be alarm rush hours and therefore data to be processedmay be huge.

� Performance data collection conflicts with alarm peaks, causingthe server’s processing over threshold.

� Traffic is underestimated and hence CPU equipment is ratherpoor.


1. Check if performance data collection is reasonable and feasible.If not, adjust the collecting time to avoid alarm peaks.

2. Check if it is during alarm burst period.3. Contact ZTE local office to expand or upgrade system config-

uration.

Verification The alarm disappears.

Precautions When the alarm occurs, system can still run; however, systemperformance is affected.

Memory Occupancy of ApplicationServer over Threshold

Symptom Memory occupancy of application server exceeds preset threshold.

Related Part Application server.

Cause Causes of the faults are as follows:

� Processing Too many services may occupy application server’smemory.

� The JVM setting of the server is too low.

� Memory configured is small due to underestimated traffic load.


1. Check the alarm and performance data processed by system.2. Modify JVM configuration.3. Contact ZTE local office to upgrade application server’s mem-

ory.


Precautions When the alarm occurs, system can still run; however, systemperformance is affected.



Space for Application Server LogsInsufficient

Symptom Space for application server logs is insufficient.

Related Part Application Server


� Logs have not been backed up and clean for a long time.

� Log space is set too small.


1. Back up logs regularly and timely and remember to delete logfiles.

2. Enlarge log space.3. Enable the auto-deletion mechanism so that logs can be auto-

matically deleted or discarded once it exceeds the preset sav-ing time.


Precautions It is recommended to adopt the mechanism of backing up andthen deleting because auto-deletion mechanism may delete somecritical logs which may not be able to be retrieved. Only part ofthe logs within preset duration can be saved.

Catalog Capacity over Threshold

Symptom The monitoring catalogue space exceeds preset capability.

Related Part Application server.


� The monitoring catalogue space rises fast.

� The space preset for monitoring catalogue is small.


1. Reset monitoring catalogue capability, and increase the thresh-old.

2. Back up monitoring catalogue, and delete backed up files.


Precautions When the alarm occurs, system can still run; however, systemperformance is affected. It is recommended to handle the problemtimely.



Common Faults HandlingAMO Startup Error

Symptom After AMO installation, system reports error during startup, caus-ing the lower network is unable to be managed.

Cause “AMO cannot be started up” error.

Related Part AMO management in Topology Management

Fault Analysis andLocation

Property information of AMO is inconsistent with that provided byinterface machine.

Troubleshooting To handle the fault, perform the following steps:

1. Try to learn information about inferior NM interface, such asIP address, configuration port no., alarm port no, performanceport no, FTP user name and password used to connect interfacemachine.

2. Compare it with the property information of the current AMOand make sure they are consistent.

3. Restart AMO.

Alarm Forwarding Failure

Symptom Alarms cannot be forwarded to corresponding mailbox or mobilephone for processing.

Cause Alarm forwarding service is set incorrectly.

Related Part Fault management.


Analyze and locate the fault by performing the following proce-dure:

� Mail forwarding

Set the following file:

ums-svr\platform\psl\uep-psl-for-wardinfo.par\mailserver.propertieswhere“mailServerAddress=” is used to configure SMTP server.

i. If forwarding fails, it is recommended to check whetherIP address, user name, and password of SMTP server areconfigured correctly.

ii. If they are correct and forwarding still fails, install winmailon a new server, a mail server, to test again.

� SMS forwarding

Set the following file:

serialgsmodem.properties where “serials=” refers to the se-rial port used for forwarding.



Hard Disk Space Insufficiency

Symptom Hard disk space is insufficient.

Cause “Hard disk space insufficient” alarm.

Related Parts Related parts of the fault are as follows:

� Fault Management

� Performance Management


Analyze and locate the fault by performing the following proce-dure:

� The alarm files are not backed up and the backup files are notdeleted for a long time.

� Alarm and performance data are underestimated, and there-fore small hard disk is configured.

TroubleshootingMethod

To handle the fault, perform the following steps:

� Check if periodic alarm files backup is set and the backup filesare deleted. To free the disk space immediately, backup anddelete the alarm files manually.

� Contact the local ZTE office for upgrading the disk capacity.

Client Fails to connect with Server

Symptom Client Fails to connect with Server.

Possible Cause Login failures of client with server may be caused by the following:

� Client is not connected to server.

� Client version is inconsistent with version of server.

� Language settings of client is inconsistent with that of server.

� Hard disk is out of free space.


1. Check the network connection between client and server.2. Check version consistence between Client is and Server.3. Check the language configuration consistency between

deploy-150minos.properties and deploy-010muep.prop-erties of client with that of server.

Chinese version: ums.locale=zh_CN

English version: ums.locale=en_US

4. Check hard disk free space and delete files not in use.

Server Unable to Start

Symptom NetNumen M31(RAN) server unable to start.

Possible Cause NetNumen M31(RAN) unable to start may be caused by the fol-lowing:



� Oracle databse application is not started correctly.

� Java virtual machine is not started correctly.

� Server configuration file is not correct.

� Server starting file is without execution permission.


1. Run sqlplus sys/password@SID as sysdba command incommand prompt to check connection with Oracle database.If connection fails, check installation instance of database, orlistener of database to determine normal operation of data-base.

2. Check the decompression of files in directory jdk-solaris forcomplete decompression of all files.

3. Check the settings of server configuration files.

Check the IP server settings in deploy-150minos.propertiesand deploy-010muep.properties.

4. Authorize server starting file of execution permission.

Execute the following commands as the root user.

# chmod -R 755 installation directory /ZXM-INOS/ums-svr/bin

Database Unable to Start

Symptom Database unable to start.

Possible Cause Database unable to start might be caused by the following:

� Database is already in operation.

� Database is not properly configured which causes insufficientresource for the start of database.

� System data file required in starting process corrupted.

� User data file corrupted during starting database.

� Hard disk has no free space.

Trouble shooting(Oracle Database)

1. Run sqlplus sys/password@SID as sysdba in commandprompt and check the connection with Oracle.

2. If Database does not start properly, the result will be showedon screen.

If system prompts database is in operation, please stop currentdatabase before running a new database.

If system prompts system data file corrupted, please reinstalldatabase instance.

If system prompts set system parameter, modify the parame-ter in $ORACLE_HOME/dbs/initSID.ora. Usually user maymodify share pool. Save the modification and restart database.

3. Run df –k command to check disk free space.

When disk space has no free space, user may delete someuseless files or move them to other locations. Such as a largefile in the data file disk could be moved to other hard disks.



4. If database starts normally, but the database can not beconnected, please check database listener for starting of theprocess.

Run lsnrctl start to start database listener process.

Data Table Space Full

Symptom Database table space is full For example in performance manage-ment, all tables are emptily, no data is obtainable.

Possible Cause NetNumen M31(RAN) server performance table space or perfor-mance index table space is small, so volume of performance datareported to surpass current table space maximum capacity.

1. Login NetNumen M31 client, and click view > system man-agementfrom standard menu bar.

2. System Management window pops up. Select the particulardatabase from left pane and click DatabaseServer > Data-base Loginfrom main menu bar.

3. A Database Login box will pop up. Input password and clickOK, usually password is “oracle”, as shown in Figure 36.

FIGURE 36 DATABASE LOGIN WINDOW

4. System prompts database login is successful, then single clickOK.

5. Select target database server, then click menu Databas-eServer > Table Collection Operation. Then system willpop-up a dialogue box Table Collection Operation as shownin Figure 37.




6. Select a scheme in the left pane of Table Collection Opera-tion, such asWrnc Table Collection of Performance Man-agement - Raw Data. This scheme is also shown in the rightpane, double click it to see details, as shown above.

7. Right-click the scheme, shortcut menu pops-up , and then clickManually Execute.

8. Manually delete performance data in Database Table Collectionoperation, and adjust automatic clearing settings. The recom-mended preserves days is 7 days.

Alarm Box Unable to DisplayAudio-Visual Prompt

Symtom Alarm Box Unable to Display Audio/Visual Prompt

Possible Cause Alarm box connection failure.


1. First check the physical network connection of alarm box byping command. This would find net cable problems or IP ad-dress conflict.

2. Change port No. of current alarm box to avoid conflicts withthe port used by other purpose on NetNumen M31 server.

3. Check NetNumen M31 server settings of alarm box to ensurethey are consistent with the settings on alarm box. If NetNu-men M31 server has not configured this alarm box, the con-nection indicator would show disconnected status.

4. If alarm box and server are physically connected, NetNumenM31 server has also configured alarm box properly and set itactivated status, the communication status window of alarmbox on NetNumen M31 will show normal. Connection indicatoron alarm box will show connected status.

5. If alarm box monitor shows connects status, but the NetNumenM31 interface shows communication status of alarm box is notnormal, please check other NetNumen M31 servers for theirsettings to this alarm box and whether their communicationstatus is normal.



Performance Report Problem Causedby Incorrect Time Zone Settings

Symptom Date and time in performance reports are inconsistent with currenttime, performance data will display in two lines.

Fault Analysis Time zone setting on client computer is inconsistent with thatof NetNumen(TM) M31 server, for example server time zone is(GMT+05:30),client time zone is (GMT+08:00). System makesmodification to time of time reports according to time zonesettings, Due to performance reports time would be inconsistentwith current time, performance data will display in two lines.

Troubleshooting After time zone modification, performance data shows normally.

Chaotic Performance Alarm DataCaused By Synchronization Errorbetween Upper and Lower Level

Principle ofSynchronization

Use NTP clock synchronization to retrieve clock data periodicallyfrom clock source and modify local time. Lower level net managersets higher level net manager server as clock source.

Symptom Performance data delay alarm appears.

Alarm recovery time is earlier than alarm happening time.

Possible Cause � Lower level time is later than higher level time.

� Lower level time being later than higher level time caused by


1. Check higher level net manager for clock service status.

Modify the deploy-default.properties file in installation di-rectory /ums-svr/deploy directory on NetNumen M31(RAN)server to set NTP service port number, as shown in Figure 38.Recommended setting is 21124.



FIGURE 38 DEPLOY DEFAULT PROPERTIES — I

2. Check lower level net manager for its configuration of higherlevel net manager as clock source. .

Modify deploy-default.properties file in OMM client installa-tion directory /ums-svr/deploy directory , as shown in Figure39.

FIGURE 39 DEPLOY DEFAULT PROPERTIES —II



Error When Reporting Lower LevelNet Manager Configuration Data

Symptom NetNumen M31 has no configuration data. It makes OMM NE mea-surement object to be null when creating performance task.

Possible Cause 1. Error when reporting lower level net manager configurationdata might be caused by the following:OMM and NetNumen M31 server communication link breaks.

2. After NetNumen M31 server restarts, it is carrying on synchro-nization with subordinate net manager, or it is in manual syn-chronization.


1. Check OMM and NetNumen server network link situation.2. Wait a bit moment for synchronization operation to complete,

alarm will continue to report.

Error in Reporting Lower Level NetManager Performance Data

Symptom NetNumen M31 alarm information is unable to report.

Possible Cause NetNumen M31 alarm information unable to report might becaused by the following:

� OMM and NetNumen M31 server communication link breaks.

� After NetNumen M31 server restarts, it is synchronizing withlower level, or is performing alarm synchronization.


1. Check network connection between OMM and server.2. Wait a bit moment, and when synchronization operation com-

pletes, alarm report will continue.

Northbound Interface LinkInterruption

Symptom NMS cannot receive any notice.

Cause Corba notification service or network.

Related Part Northbound alarm, northbound performance, northbound config-uration, northbound file transmission interface.


1. Possibly network interruption. Use ping command to checknetwork communication.

2. Possibly because port is taken. Use telnet or netstat com-mands to check port occupation.

3. Possibly Corba is not started properly. Execute ps - ef | grepcorba command to check Corba process.



4. Possibly because Corba is started later than NeNumen. In thiscase, Corba process exists but none of northbound operationis supported.

5. Possibly because NMS has failure. If the resaons 1–4 does notexist, search NMS object quotation in log files. It is usuallysimilar to “IOR:3546576587…” format. And examine whetherthis object in log file is “not active” status.


1. Check physics equipment (net cable, interface), network pro-tocol, etc in turn, to ensure network communication is out oferror.

2. Releases related port.3. Start system and make sure Corba process is started before

NetNumen M31 process.4. NMS restarts or let NMS do self-check.

Failure in Reporting ConfigurationData to NMS

Symptom � No file generated after configuration object batch uploading.

� Batch upload time of configuration data is very long, and con-versation remains in running status for very long time withoutending.

� Batch uploading configuration data does finish, but session dis-plays operation failure.

Cause 1. Read-write permission of target FTP.2. Scale of configuration data itself.3. Configuration data has problem and causes error in data con-

version.

Related Part FTP server, northbound configuration module.

Fault analysislocation and

handling:

1. If target FTP is NetNumen M31, then users needs to modifyFtpServer.user.nmsftpuser.write as true in file ums-svr \tools \ ftpserver \ conf \ naf-app-ftpuser.properties. Iftarget FTP is not NetNumen M31, then user needs to providea FTP with write permission.

2. Checks NetNumen M31 ums-svr \ tmp \ ftp \ naf \ undercm directory about its sufficient enough storage space, asbatch configuration data will generate temporary file in thislocation. If this directory has massive temporary files, usermay clear files in this directory to release disk space.

3. User may divide the uploading of configuration data into mul-tiple partitions, for instance upload one subnet configurationdata only in one operation. Record ID of subnet with uploadfailures, and save it at subnet with data conversion error.

4. Check configuration data on OMM, for example ID field of MOobject is filled with Chinese character.

5. If single subnet upload also takes long time without returning(for instance over 2 hours), retrieve the log file in directoryums-svr \ log, pack the log file and send to developmentpersonnel for analysis.



Error in Report Alarm Information toNMS

Symptom NMS cannot receive any alarm information.

Cause Corba notification service, NetNumen M31 alarm managementsystem.

Related Part Northbound alarm, public, NetNumen M31 alarm.


� Check for northbound link is working normal.

� Check whether EMS has normal alarm reporting, whether ithas set up filtration rules.

� Possibly Corba is not started properly. Execute ps - ef | grepcorba command to check Corba process.


1. refers to Northbound Interface Link Interruption ensure north-bound link is in normal operation.

2. Clear filtration rules to ensure normal alarm report.3. Reboot system and make sure Corba process is started before

NetNumen M31 process.

Failure in Reporting PerformanceData to NMS

Symptom If NMS fails to report Reporting Performance Data.

Cause NMS has not created related performance task or performance taskbe deleted or be suspended.

Lower level has not reported related performance data. There isno data, so it does not report.

Corresponding data storage space is full (divided into oralce per-formance table space and XML file storage space).

Related Part Performance Management


1. Check whether related task created by northbound existing inperformance management interface.

2. Check whether data of related task has been reported ontoNetNumen M31 in data check interface of performance man-agement.

3. Check ORACLE table space and disk space.


1. Create NMS related performance task or activate related per-formance task.

2. Check OMM for related task, and determine whether it can re-port to NetNumenM31 in time. If it cannot, please refer toOMM Faults handling and processing to solve problem. If itcan, backup the log and send to development personnel foranalysis.

3. Three methods to solve ORACLE table space and disk spaceinsufficiency.

� Increase table space.



� Increase disk storage capacity.

� Back up and delete old data and reduces file preservationtime, Database Tables Backup and Recovery.





C h a p t e r 9

Data Backup andRecovery

Table of ContentsLog Files Backup ...............................................................81CM Data Backup and Recovery ............................................85Database Tables Backup and Recovery .................................93All Users Database Backup and Recovery ............................ 103Fault Management database backup................................... 103

Log Files BackupLogs come in different flavors, so in NetNume log file is one com-posed entirely of lines of text.

Netnumen creates log files that record actions for operations likesystem startup, operations done by user and fault operation.

The current Log file moved to the Zip folder automatically, after aspecific duration has passed or a file size has been reached.

The downside to having programs that can provide useful or ver-bose logging output is the amount of disk space this output canconsume. This is a concern for all operating systems.

In NetNumen system to save the disk space user can take log filesbackup and delete the all log files except current log file. Backuplog file are useful during system crash or for trouble shooting. Usercan take log files backup periodically.

NetNumen Log Files Backup inWindows OS

Context Perform the following steps to take log files backup from serverand client:

Steps 1. Log files backup from NetNumen server:

i. Go to the Log directory from the directory where NetNu-men system is installed as shown in Figure 40.



FIGURE 40 NAVIGATING TO LOG FOLDER

ii. Except current log files, select all the files and zip it. Backupthe zip file.

iii. After backup of log file,s delete all the files including zip fileexcept current log files from log directory shown in Figure41.

FIGURE 41 AFTER LONG FILES DELETION FROM LOG DIRECTORY

2. Recovering NetNumen Sever Log files:


Chapter 9 Data Backup and Recovery

� When system crashes user can restore the log files frombackup disk.

� During system trouble shooting technical personnel can re-fer log files from backup disk.

3. Procedure for log files backup and recovery in NetNumen clientis same as NetNume server.

END OF STEPS

NetNumen Log Files Backup inSolaris OS

Context Perform the following steps to take log files backup from serverand client:

Steps 1. Start the Solaris system as administrator. Change the direc-tory into /ZXM-INO/us-ser/ using CD command as shownin Figure 42.

FIGURE 42 CHANGING THE DIRECTORY IN SOLARIS SYSTEM

2. Archive the files in the log directory to a tar format file calledlog.tar as show in Figure 43.



FIGURE 43 ARCHING FILES IN TAR FORMAT

3. After completion of tar command log.tar file can be seen inums-svr directory as shown in Figure 44.

FIGURE 44 LOG.TAR FILE IN UMS-SVR DIRECTORY

4. Compress and archive the file log.tar as shown in Figure 45.



FIGURE 45 ZIP LOG.TAR FILE

5. Backup the log.tar.gz file. After taking backup, delete all thefile including log.tar.gz file except current log files.

END OF STEPS

CM Data Backup andRecoveryConfiguration management data backup is used during systemcrash.

In the case of single site failure user can recover the configurationmanagement data from backup disk and make the system alive inshort duration. In the case of entire OMM failure also user can re-cover the entire OMM configuration management data in differentOMM and divert all the operations to that OMM to avoid the longtime interception in the system operations.

NetNumen CM Data Backup andRecovery

Context To backup NetNumen Configuration Management (CM) data fromthe client and to recover through client. Perform the followingsteps to take backup Configuration Management data from clientand to restore CM data in particular node or OMM through client.



Steps 1. Taking CM data backup from NetNumen Client.

i. From the NetNumen Topology Management Client clickonOperation >NEManagement > ConfigurationMan-agement as shown in Figure 46.

FIGURE 46 NAVIGATING TO CONFIGURATION MANAGEMENT

ii. In Configuration Management click on Management >Data Management > Data Backup as shown in Figure47

FIGURE 47 NAVIGATING TO DATA BACKUP WINDOW

iii. Selecting destination path for CM data storage :To chooseStorage path click Select button from Data Backup win-dow as shown in Figure 48. Open window appears, selectCM folder and click Open button as shown in Figure 49.Again click open button as shown in Figure 50.



FIGURE 48 DATA BACKUP WINDOW

FIGURE 49 SELECTING CM DIRECTORY



FIGURE 50 SELECTING PATH FOR CM DATA STORAGE

iv. Enter the file name in Fileme prefix and enter remark inBackup remarks. Select the particular managed elementor entire OMM to take backup as shown in Figure 51 andclick OK.

FIGURE 51 SELECTING NODES FOR CM DATA BACKUP

v. After successful backup system shows the result of backupin Data Backup Result window as shown in Figure 52.Click Close.



FIGURE 52 DATA BACKUP RESULT WINDOW

vi. Backup data file will be stored in ums-svr/backup/sysmanager/cm path, as shown in Figure 53.

FIGURE 53 BACKUP FILE STORAGE LOCATION

2. Recovering NetNumen CM data through client:

i. From Topology Management main window click on Op-eration > NE Management > Configuration Manage-ment as shown in Figure 54.



FIGURE 54 NAVIGATING TO CONFIGURATION MANAGEMENT

ii. From Configuration Management window click Man-agement > Data Management > Data Recover.

FIGURE 55 NAVIGATING TO DATA RECOVER

iii. Data recovery window appears as shown in Figure 56.click on Select button to select the file from path. Openwindow appears, as shown in Figure 57. Select the file fromCM folder and click open button as shown in Figure 58.



FIGURE 56 DATA RECOVERY WINDOW

FIGURE 57 OPEN WINDOW



FIGURE 58 SELECTING CM DATA FILE FROM CM FOLDER

iv. Select the node which is to be recovered and click OK, asshown in Figure 59.

FIGURE 59 DATA RECOVERY WINDOW

v. After successful recovery system displays result in DataRecover Result window as shown in Figure 60. To activatethe particular site user can click Set activate configset…button to end this operation click Close.



FIGURE 60 DATA RECOVERY RESULT WINDOW

END OF STEPS

Database Tables Backupand Recovery

Short Description NetNumen system automatically collects specified performanceparameters, all the alarms generated by system, users loginformation and security management information in the formof tables called database tables.During the particular NetNumensystem breakdown, user can divert all the faulty NetNumensystem operations to some other live NetNumen system quicklyby restoring performance management, fault management, logmanagement and security management database tables. Thisoperation reduces recovery time of the system during breakdown.

Context Perform the following steps to take database tables backup andrecovery:

Steps 1. From main menu click View > System Management windowas shown in Figure 61.



FIGURE 61 NAVIGATING TO SYSTEM MANAGEMENT

2. To access database tables, user need to login to oracle data-base:To login to database Click DatabaseServer > DatabaseLogin from System Management main window, as shown inFigure 62 .

FIGURE 62 NAVIGATING TO DATABASE LOGIN

3. Enter the UserName and Password of the oracle database inDatabase Login window as shown in Figure 63. Click OK.



FIGURE 63 LOGIN DATABASE

4. System displays successful login message in Message windowas shown in Figure 64.

FIGURE 64 DATABASE LOGIN SUCCESSFUL MESSAGE

5. After login to database , click DatabaseServer > Table Col-lection Operations from the System Management windowas shown in Figure 65.

FIGURE 65 NAVIGATING TO TABLE COLLECTION OPERATION WINODW

6. Table Collection Operations dialog box appears which con-tains Network Management Performance Database, Net-



workManagement Fault Database, andNetworkManage-ment Common Database tables, as shown in Figure 66.

FIGURE 66 TABLE COLLECTIONS OPERATIONS DIALOG BOX

7. To take backup of the these tables, first select the tables fromany of the three database and right-click on it and select Cre-ate option from popup menu, as shown in Figure 67.

FIGURE 67 NAVIGATING TO TAKE BACKUP OF TABLES

8. In Create Table Collection window click in Name box andenter the file name up to 50 Characters, Characters includesChinese, English and some allowed symbols, restricted sym-bols will not display in text box. After entering name, clickNextStep button as shown in Figure 68.



FIGURE 68 CREATE TABLE COLLECTION TASK STEP 1 OF 4

9. In second step of Table collection task window check the Actionas Export and also check desired Store Type as shown inFigure 69.

User need to choose the location for the export file to store.Click Choose.. button in, Open dialog box appears as shownin Figure 70. Select the corresponding folder to store databasetables and click Open button.

In Time Filter pane select Filtrate Type from drop down list,based on filtrate type enter TTime and DTime. For exampleLast 2 Days(s) filtrate type in TTime column enter 2 as shownin Figure 24(T and D means no of months or Days, like 2 Days,3 months, replace no of days or months in place of T or D).Click Next Step button.




FIGURE 70 CHOOSING PATH IN OPEN DIALOG BOX WINDOW

10. If user wants to delete the tables after taking backup, selectClear option in Basic Setting pane of Create Table Collec-tion Task Step 3 of 4 window as shown inFigure 71.




11. Enter the howmany times need report during the particular du-ration in Period model and Duration panes of Create TableCollection Task Step 4 of 4 window respectively, as shownin Figure 72.


12. In Table collection Operations Oracle window shows theTasks, this task executes automatically as per duration andinterval settings. Backup files will be stored in system backupfolder. User can also execute the task manually by right-click-ing on task and select Manually Execute from popup menuas shown in as shown in Figure 73.



FIGURE 73 NAVIGATING TO EXECUTE TABLES MANUALLY WINDOW

13. In Table Collection Manually Execute Step 1 of 3 windowedit the file name and click Next Step button, as shown inFigure 74.

FIGURE 74 TABLE COLLECTION MANUALLY EXECUTE STEP 1 OF 3

14. In Table Collection Manually Execute Step 2 of 3 windowset the option in Basic setting and Time filter pane as ex-plained earlier and click Next Step button, as shown in Figure75.




15. In Table Collection Manually Execute Step 3 of 3 windowsset the option in Basic setting and Time filter pane as ex-plained earlier and click Execute button, as shown in Figure76.


16. Before executing the task system asks for confirmation, asshown in Figure 77 and Click OK.



FIGURE 77 CONFIRM MESSAGE BEFORE EXECUTING TASK

17. Task will be executed as shown in Figure 78.

FIGURE 78 EXECUTE TASK RESULT WINDOW

END OF STEPS



All Users Database Backupand Recovery

Short Description To backup and recovery of the entire NetNumen’s entire database.All user database backup is commonly used before software up-grade.

Context Perform the following steps take backup of entire database

Steps 1. Login into Oracle database through Solaris OS.

2. Enter the following command to take entire database backup$ exp system / oracle @ SID file = a.dmp log = a.log owner =(database user name1, database user name 2, ... ..., thedatabase user name n)

3. Recovering the database: Each time only one user databasecan be recovered. Enter the following command to recover theentire database.$ imp system / oracle @ SID file = a.dmp log = a.log fromuser= database user name 1 touser = user database 1.

$ imp system / oracle @ SID file = a.dmp log = a.log fromuser= database user name 2 touser = user database 2.

……………………..……………………..$ imp system / oracle @ SID file = a.dmp log = a.log fromuser= database user name n touser = user database n.

END OF STEPS

Fault Management databasebackup

Short Description In the case of Fault Management database backup, user need totake backup only history alarms and notifications. This backupdata will be used by maintenance personnel to find out the reasonfor the particular alarm and to solve the problem.

Context Perform the following steps to take database backup:

Steps 1. To enter into Fault Management system, from main menu clickView > Fault Management, as shown in Figure 79.



FIGURE 79 NAVIGATING TO FAULT MANAGEMENT

2. To backup alarm, user needs to query, from Fault Manage-ment window, select Query > View History Alarms, asshown in Figure 80.

FIGURE 80 NAVIGATING TO QUERY ALARMS

3. History Alarm Query Conditions interface pops up, asshown in the Figure 81.



FIGURE 81 HISTORY ALARM QUERY CONDITION INTERFACE

4. Click button on the History Alarm Query Conditions inter-face toolbar to open Query History Alarm dialog box, as shownin the Figure 82. Set the query conditions and click on OK toexecute the query conditions.



FIGURE 82 QUERYING HISTORY ALARM INTERFACE

5. System displays all current alarms that meet the set condi-tions, as shown in Figure 83

FIGURE 83 HISTORY ALARMS QUERY RESULT



6. Click button on real-time current alarms toolbar, Save di-alog box appears, in save dialog box user need to choose pathfor export file, as shown in Figure 84.

FIGURE 84 SAVE WINDOW

7. Successful saved message appears, as shown in Figure 85

FIGURE 85 CONFIRMATION MESSAGE

8. To export Notification follow the same steps as History alarms.

END OF STEPS





C h a p t e r 10

Emergency Maintenance

Table of ContentsEmergency Maintenance Purpose....................................... 109Principle of Emergency Maintenance................................... 110Emergency Maintenance Flow............................................ 110Service Check ................................................................. 111Fault Record ................................................................... 111Locating Fault ................................................................. 112Emergency Recourse........................................................ 112Service Recovery............................................................. 113Information Record.......................................................... 114Information Collection...................................................... 114Emergency Maintenance Tables ......................................... 114

Emergency MaintenancePurposeEmergency fault is a fault that causes the failure in providing basicservices, system being unable to work for more than 30 minutesor human safety hazards, or other problems that should be solvedin emergencies upon request by the carrier.

The main purposes of emergency troubleshooting are as follows:

� Handle the faults as soon as possible.

� Restore interrupted services as soon as possible, therebyavoiding or reducing the loss caused by the faults.

During NetNumen M31 system running, fault may occur onsome parts. When the fault occurs, the maintenance personnelshould locate and then handle the fault as soon as possible.When the emergency fault occur, inform ZTE maintenance per-sonnel and prepare the remote maintenance software (such asPCANYWHERE), necessary telephone lines, modem and othermaintenance tools.



Principle of EmergencyMaintenanceRestoring interrupted service is the principle of emergency faulthandling.

Once emergency faults on the equipment are reported or found(Level 1 fault), to minimize damage or loss it is required to clearthe faults and restore the system as soon as possible. Handleemergency faults according to the procedure of emergency faultslocation and analysis. Meanwhile, contact local ZTE office for tech-nical support.

According to statistical data, system faults may comprise: com-plete or partial power failure, network failure, database fault andother faults. It is recommended to conduct troubleshooting inaforesaid key aspects. If it is confirmed that power and commu-nication is OK, one may resort to Alarm Management System tolocate the node where problem possibly lies in.

Emergency MaintenanceFlowThe emergency maintenance flow involves the following steps:

1. Service check2. Record abnormalities3. Make initial location and analysis of faults.4. Launch the emergency aid.5. Service recovery6. Service observation7. Information record.

The emergency maintenance flow chart is as shown in Figure 86.


Chapter 10 Emergency Maintenance

FIGURE 86 EMERGENCY MAINTENANCE FLOW

Service CheckJudge if the reported faults are related to this network manage-ment system or the lower-level network management. Check ifthere are abnormalities in the equipment environment (tempera-ture, humidity or power supply).

And then the maintenance personnel should record the fault infor-mation.

Fault RecordBefore/During the start of the emergency recovery plan or the faultrecovery, make records of the running version and phenomena inthe abnormality table Abnormality Record Table.

Back up OMC configuration data properly.



Note:

The abnormality record is very useful in emergency aid and thesubsequent problem analysis and summary. Therefore, be sure tofill a complete abnormality record.

Locating FaultAfter fault information is obtained, analyze and judge fault infor-mation to locate the fault.

The fault location is the procedure of locating the direct reasonfrom multiple possible causes. That is, exclude impossible factorsthrough the analysis and certain means and methods and compar-ison of various possible causes, and finally determine the cause ofthe fault. In terms of equipment, the main fault causes are asfollows:

� Hardware faults: including transmission fault, power fault, LANnetwork fault or component damages.

� Software faults: including foreground software fault, databasesoftware fault or dual-computer management software failure.

It is necessary to analyze and judge the fault causes with the helpof maintenance tools of fault management and signaling trace.

The maintenance personnel should often locate the fault by exclu-sive method and give full considerations of onsite conditions.

Emergency RecourseIf the interrupted services can not be restored after troubleshoot-ing or some vital system faults happen, then collect the necessaryfault information and ask ZTE 24-hour service hotline for help.ZTE provides three emergency recourse channels: 24-hour servicehotline, remote technical support and onsite technical support, asshown in Figure 87.



FIGURE 87 EMERGENCY RECOURSE

1. Service hotline

ZTE provides 7*24-hour technical support services. Whenemergency faults occur, dial ZTE Customer Support Centerhotline : 8008301118 or 4008301118 or 0755-26770800 andit is better to provide the record table of onsite abnormality,facilitating ZTE maintenance personnel to learn and thenlocate the fault.

2. Remote support

Based on the information provided by the service hotline, thetechnical engineer can log in the abnormal office remotely. Incase of common faults, customer can solve them through tech-nical engineer guidance. In case of complex faults, technicalengineers are assigned to the site to provide onsite technicalsupport.

3. Onsite technical support

When the maintenance engineer arrives at the site, they willadopt some necessary maintenance measures to restore thecommunication as soon as possible.

Service RecoveryIf the methods provided in this manual and remote emergency aidcannot help to locate faults and recover it is necessary to performforced handover of dual-computer.



Information RecordWhen an emergency fault is handled and the service runs normally,please fill in the troubleshooting record table. If you are asked foremergency service hotline for help, it is necessary to review theresult to ZTE local office, enabling us to provide better after-saleservices for carriers.

Information CollectionWhen the service is restored, it is necessary to collect data ofstatistic report, running logs and history alarms and feed back thefault handling results to ZTE Customer Support Center. Then thedata are sent to the customer support department.

Emergency MaintenanceTablesAbnormality Record Table

Table 15 below serves as an example only. Optimize according toactual NetNumen M31 maintenance items.

TABLE 15 ABNORMALITY RECORD TABLE

Equipmentname

EquipmentnameEquipmentNo.

Item Abnormality description

Faultoccurrence time

Faultoccurrencescope

Serious alarmitem reportedby OMC



Equipmentname

EquipmentnameEquipmentNo.

Operation loginformation ofOMC

Projectinformation

For example, the environment of the equipmentroom: temperature and humidity change. Recordit if any.

Equipment Emergency MaintenanceRequisition

This requisition is to notify ZTE technical support center when thecarrier fails to solve the fault on his own. It is better to attach theon-site fault record Table 16 with the fax, to allow ZTE personnelto locate and eliminate the faults more easily.

TABLE 16 EQUIPMENT EMERGENCY MAINTENANCE REQUISITION

The user should fill in the following fields.

Equip-mentname

Equip-ment No.

Softwareversion

Com-plainttime

(HH-MM-DD-YY)

Complai-nant

Tele-phone

Com-plaintcompanyor organi-zation

Whether in thewarranty period

( ) Y ( ) N

Abnormality Record Table (Please attach it on the blank below) :

Details of the handling process (as detailed as possible ):

Reviewed by:

Stamp of thedepartment:

ZTE personnel should fill in the following fields:

Solution Time ofsettle-ment

O Guide through telephone O Remotemaintenance O On-site support

(HH-MM-DD-YY)



The user should fill in the following fields.

Handled by:Handling result:

Stamp of thedepartment:


Troubleshooting Record Table

troubleshooting record table is as shown in Table 17

TABLE 17 TROUBLESHOOTING RECORD TABLE

Equipmentname

EquipmentNo.

Faultoccurrence time

(HH-MM-DD-YY)

Faultelimination time

(HH-MM-DD-YY)

Fault type: hardware equipment fault, power fault, transmissionnetwork fault, data modification and other faults.

Fault source: user complaint, alarm system, fault found duringmaintenance and other sources.

Fault phenomena:

Solution:

Summary:

Signature of the attendant: Signature of the handling person:


Figures

Figure 1 Inspect Communication Between Network

Management Server And Client—I .......................14


Management Server And Client-II ........................15


Management Server And Client - III .....................16


Management Server And Lower Level Network

Management (1)................................................17


Management Server And Lower Level Network

Management (2)................................................17

Figure 6 Check Communication Between Nm Server And

Lower Level Nm (3) ..........................................18

Figure 7 Inspect Server Operation Status..............................19

Figure 8 Real Time Alarm Monitor Window ............................21

Figure 9 Showing Alarm Details ...........................................22

Figure 10 Operation Log Window .........................................23

Figure 11 Server Performance Window .................................26

Figure 12 Timer Query Task ................................................31

Figure 13 Check Database Space (1) ...................................32

Figure 14 Checking Database Space (2) ...............................33

Figure 15 Virus Update Information .....................................34

Figure 16 Mcafee Auto Update Dialog Box .............................35

Figure 17 Check Server Operation Status..............................36

Figure 18 Check Server Disk Storage Capacity (1) .................38

Figure 19 Database Login Window ......................................43

Figure 20 View Database Resource(2) .................................44

Figure 21 Check Performance Statistic Result of Operation

Network ..........................................................45

Figure 22 About Interface ...................................................47

Figure 23 Memory Monitor ..................................................47

Figure 24 Check Dual-system Switching (1) .........................50

Figure 25 Check Dual-system Switching (2) ..........................51







Figure 30 Table Collection Operation Window.........................54

Figure 31 Query System Log ...............................................54

Figure 32 Log Record .........................................................55


Figure 34 Query System Log ...............................................56

Figure 35 Log Record Window .............................................56

Figure 36 Database Login Window .......................................72


Figure 38 Deploy Default Properties — I ...............................75

Figure 39 Deploy Default Properties —II ...............................75

Figure 40 Navigating To Log Folder ......................................82

Figure 41 After Long Files Deletion From Log Directory ...........82

Figure 42 Changing The Directory In Solaris System .............83

Figure 43 Arching Files In Tar Format ...................................84

Figure 44 Log.Tar File In Ums-Svr Directory .........................84

Figure 45 Zip Log.Tar File ...................................................85

Figure 46 Navigating To Configuration Management ...............86

Figure 47 Navigating To Data Backup Window .......................86

Figure 48 Data Backup Window ...........................................87

Figure 49 Selecting Cm Directory.........................................87

Figure 50 Selecting Path For Cm Data Storage.......................88

Figure 51 Selecting Nodes For Cm Data Backup .....................88

Figure 52 Data Backup Result Window..................................89

Figure 53 Backup File Storage Location.................................89

Figure 54 Navigating To Configuration Management ...............90

Figure 55 Navigating to Data Recover...................................90

Figure 56 Data Recovery Window.........................................91

Figure 57 Open Window .....................................................91

Figure 58 Selecting Cm Data File From Cm Folder ..................92

Figure 59 Data Recovery Window.........................................92

Figure 60 Data Recovery Result Window ...............................93

Figure 61 Navigating To System Management .......................94

Figure 62 Navigating To Database Login ...............................94

Figure 63 Login Database ...................................................95

Figure 64 Database Login Successful Message .......................95

Figure 65 Navigating To Table Collection Operation Winodw .....95


Figures

Figure 66 Table Collections Operations Dialog Box..................96

Figure 67 Navigating To Take Backup Of Tables ......................96

Figure 68 Create Table Collection Task Step 1 Of 4 .................97


Figure 70 Choosing Path In Open Dialog Box Window .............98



Figure 73 Navigating To Execute Tables Manually Window ..... 100

Figure 74 Table Collection Manually Execute Step 1 Of 3 ....... 100



Figure 77 Confirm Message Before Executing Task ............... 102

Figure 78 Execute Task Result Window ............................... 102

Figure 79 Navigating To Fault Management ......................... 104

Figure 80 Navigating To Query Alarms................................ 104

Figure 81 History Alarm Query Condition Interface............... 105

Figure 82 Querying History Alarm Interface......................... 106

Figure 83 History Alarms Query Result ............................... 106

Figure 84 Save Window ................................................... 107

Figure 85 Confirmation Message ........................................ 107

Figure 86 Emergency Maintenance Flow.............................. 111

Figure 87 Emergency Recourse.......................................... 113





Tables

Table 1 Chapter Summary .................................................... i

Table 3 List of Daily Routine Maintenance Items.....................11

Table 4 Netnumen M31 System Temperature Requirements .....12

Table 5 Netnumen M31 System Temperature Requirements .....13

Table 6 Weekly Routines For Maintenance Checklist ................29

Table 8 Monthly Routine Maintenance Checklist......................41

Table 9 Power Supply Range Of Netnumen M31 System ..........42

Table 10 List of Weekly Maintenance Items ...........................49

Table 11 Daily Maintenance Record Form .............................59

Table 12 Weekly Maintenance Record Form ...........................60

Table 13 Monthly Maintenance Record Form ..........................62

Table 14 Quarterly Maintenance Record Form ........................63

Table 15 Abnormality Record Table..................................... 114

Table 16 Equipment Emergency Maintenance Requisition ...... 115

Table 17 Troubleshooting Record Table................................ 116





Glossary

BSS - Base Station Subsystem

CPU - Central Processing Unit

FTP - File Transfer Protocol

IP - Internet Protocol

LAN - Local Area Network

MO - Management Object

NAT - Network Address Translation

NM - Network Management

NMS - Network Management System

OMC - Operation & Maintenance Center

OMM - Operation & Maintenance Module

PCB - Printed Circuit Board

PGND - Protection Ground

RAN - Radio Access Network

SMB - Server Message Block

VCS - Veritas Cluster Server


Documents

NetNumen M31 RAN V3!1!10 420 Maintenance Guide