msc server routine maintenance guide

ZXUN iCX(MSCS)MSC Server

Routine Maintenance Guide

Version: V4.12.10

ZTE CORPORATIONNO. 55, Hi-tech Road South, ShenZhen, P.R.ChinaPostcode: 518057Tel: +86-755-26771900Fax: +86-755-26770801URL: http://ensupport.zte.com.cnE-mail: [email protected]

LEGAL INFORMATIONCopyright 2012 ZTE CORPORATION.

The contents of this document are protected by copyright laws and international treaties. Any reproduction or

distribution of this document or any portion of this document, in any form by any means, without the prior written

consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by

contractual confidentiality obligations.

All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE

CORPORATION or of their respective owners.

This document is provided as is, and all express, implied, or statutory warranties, representations or conditions

are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,

title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the

use of or reliance on the information contained herein.

ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications

covering the subject matter of this document. Except as expressly provided in any written license between ZTE

CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter

herein.

ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.

Users may visit 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 Revison Reason

R1.0 2012-10-31 First edition

Serial Number: SJ-20120730093520-018

Publishing Date: 2012-10-31 (R1.0)

SJ-20120730093520-018|2012-10-31 (R1.0) ZTE Proprietary and Confidential

ContentsAbout This Manual ......................................................................................... I

Chapter 1 Routine Maintenance Overview............................................... 1-1

1.1 Classification ..................................................................................................... 1-1

1.2 Purposes ........................................................................................................... 1-2

1.3 Precautions........................................................................................................ 1-2

1.4 Basic Requirements for Maintenance Personnel................................................... 1-4

1.5 Routine Maintenance Tools ................................................................................. 1-4

1.6 Introduction to Routine Maintenance Operations .................................................. 1-5

Chapter 2 Daily Routine Maintenance ...................................................... 2-1

2.1 Checking System Alarms or Notifications ............................................................. 2-1

2.2 Equipment Room Environment Check ................................................................ 2-2

2.2.1 Checking Equipment Room Temperature ................................................... 2-2

2.2.2 Checking Equipment Room Humidity......................................................... 2-2

2.3 Checking Board Running Status.......................................................................... 2-3

2.4 Performance Statistics Check ............................................................................. 2-4

2.4.1 Checking MTP3 Signaling Links ................................................................ 2-4

2.4.2 Checking SCTP Links............................................................................... 2-5

Chapter 3 Weekly Routine Maintenance .................................................. 3-1

3.1 Clock Check ...................................................................................................... 3-1

3.1.1 Checking Clock Synchronization ............................................................... 3-1

3.1.2 Checking Clock Running Status ................................................................ 3-2

3.2 Resource Usage Check ...................................................................................... 3-3

3.2.1 Checking Hard Disk Usage of the OMP Module ......................................... 3-3

3.2.2 Checking CPU/Memory Usage of the OMM Server..................................... 3-3

3.2.3 Checking the Hard Disk Usage of the OMM Server .................................... 3-4

3.3 Hardware Check ................................................................................................ 3-5

3.3.1 Checking the Chassis Management Module............................................... 3-5

3.3.2 Checking the Switching Board................................................................... 3-5

3.3.3 Check the Power Module .......................................................................... 3-6

3.3.4 Check the Fan Module.............................................................................. 3-6

3.3.5 Checking the GPBB0/GPBX1 Boards ........................................................ 3-7

3.3.6 Checking the rear board GPI1 of the GPBX1.............................................. 3-7

3.4 Windows Operating System Check ..................................................................... 3-8

I


3.4.1 Check the Anti-Virus Software................................................................... 3-8

3.4.2 Checking Virus Database Update .............................................................. 3-8

3.5 Checking Data Backup on LMT ........................................................................... 3-9

3.6 Performance Statistics Check ........................................................................... 3-10

3.6.1 Checking Resource Load........................................................................ 3-10

3.6.2 Checking MscServer Load .......................................................................3-11

Chapter 4 Monthly Routine Maintenance................................................. 4-1

4.1 Checking Versions.............................................................................................. 4-1

4.2 Checking System Alarms and Notifications .......................................................... 4-2

4.3 Checking Heat Radiation of Racks ...................................................................... 4-3

4.4 Checking for Viruses .......................................................................................... 4-3

Chapter 5 Quarterly Routine Maintenance............................................... 5-1

5.1 Cleaning the Dust Screens ................................................................................. 5-1

5.2 CGSL Operating System Check .......................................................................... 5-2

5.2.1 Checking Hard Disk Space ....................................................................... 5-2

5.2.2 Checking Swap Space.............................................................................. 5-2

5.2.3 Checking CPU/Memory Usage.................................................................. 5-3

5.2.4 Checking Log Files................................................................................... 5-4

5.2.5 Checking Disk I/O .................................................................................... 5-4

5.3 Checking Remote Control Tools .......................................................................... 5-5

Chapter 6 Yearly Routine Maintenance .................................................... 6-1

6.1 Equipment Room Environment Check ................................................................. 6-1

6.1.1 Checking the DC Power Supply ................................................................ 6-1

6.1.2 Checking the AC Power Supply................................................................. 6-2

6.2 Hardware Check ................................................................................................ 6-2

6.2.1 Checking Cable Connections .................................................................... 6-2

6.2.2 Checking Spare Parts............................................................................... 6-3

Appendix A Routine Maintenance Forms ............................................... A-1

A.1 Form of Daily Maintenance Records....................................................................A-1

A.2 Form of Weekly Maintenance Records ................................................................A-3

A.3 Form of Monthly Maintenance Records ...............................................................A-5

A.4 Form of Quarterly Maintenance Records .............................................................A-6

A.5 Form of Yearly Maintenance Records..................................................................A-7

Appendix B Cautions for Routine Maintenance ..................................... B-1

Glossary .......................................................................................................... I

II


About This ManualPurpose

This manual describes maintenance classification, routine maintenance items andcommon maintenance methods for the ZXUN iCX(MSCS).

Intended Audience

This manual is intended for:

l Network management engineersl Maintenance engineers

Prerequisite Skill and Knowledge

To use this manual effectively, users should have a general understanding of wirelesstelecommunications technology. Familiarity with the following is helpful:

l Basic operation and maintenance procedures of the ZXUN iCX(MSCS)l Routine troubleshooting methods of the ZXUN iCX(MSCS)

What Is in This Manual

This manual contains the following chapters:

Chapter Summary

1, Routine Maintenance Overview Describes the purposes, classification, precautions, and

operation introduction of routine maintenance.

2, Daily Routine Maintenance Describes the maintenance items, purposes, procedures, and

criteria of daily routine maintenance.

3, Weekly Routine Maintenance Describes the maintenance items, purposes, procedures, and

criteria of weekly routine maintenance.

4, Monthly Routine Maintenance Describes the maintenance items, purposes, procedures, and

criteria of monthly routine maintenance.

5, Quarterly Routine Maintenance Describes the maintenance items, purposes, procedures, and

criteria of quarterly routine maintenance.

6, Yearly Routine Maintenance Describes the maintenance items, purposes, procedures, and

criteria of yearly routine maintenance.

Appendix A, Routine Maintenance

Forms

Provides the forms of routine maintenance records.

Appendix B, Cautions for Routine

Maintenance

Describes the cautions for routine maintenance so that you

can operate the system safely.

I


Related Documentation

The following documentation is related to this manual:

l ZXUN iCX(MSCS) MSC Server General Operation Guidel ZXUN iCX(MSCS) MSC Server Performance Management Operation Guidel ZXUN iCX(MSCS) MSC Server Alarm Management Operation Guidel ZXUN iCX(MSCS) MSC Server Alarm Handlingl ZXUN iCX(MSCS) MSC Server Hardware Description

FCC Compliance Statement

This device complies with part 15 of the FCC Rules. Operation is subject to the followingtwo conditions.

1. This device may not cause harmful interference.2. This device must accept any interference received, including interference that may

cause undesired operation.

Changes or modifications not expressly approved by the party responsible for compliancecould void the user's authority to operate the equipment.

Conventions

This manual uses the following typographical conventions:

Typeface Meaning

Italics Variables in commands. It may also refer to other related manuals and documents.

Bold Menus, menu options, function names, input fields, option button names, check

boxes, drop-down lists, dialog box names, window names, parameters, and

commands.

Constant

width

Text that you type, program codes, filenames, directory names, and function names.

[ ] Optional parameters.

{ } Mandatory parameters.

| Separates individual parameter in series of parameters.

Caution: indicates a potentially hazardous situation. Failure to comply can result in

moderate injury, equipment damage, or interruption of minor services.

Note: Provides additional information about a certain topic.

II


Chapter 1Routine MaintenanceOverviewTable of Contents

Classification..............................................................................................................1-1Purposes....................................................................................................................1-2Precautions ................................................................................................................1-2Basic Requirements for Maintenance Personnel ........................................................1-4Routine Maintenance Tools ........................................................................................1-4Introduction to Routine Maintenance Operations ........................................................1-5

1.1 Classification

Description

To effectively implement the functions of the equipment and prevent potential accidents,it is necessary to perform routine maintenance on the running equipment. Routinemaintenance is a preventive measure, which aims to discover and remove the defectsand hidden risks of the equipment in time. Regular check and maintenance improve thesafety, stability and reliability of the equipment.

Category

The routine maintenance can be divided into two categories:

l Daily Routine Maintenancel Regular Routine Maintenance

Daily Routine Maintenance

Daily routine maintenance refers to the maintenance operations that are implementedby the common maintenance personnel every day, with relatively simple maintenanceprocess, such as alarm and notification check and equipment room environment check.

Regular Routine Maintenance

Regular routine maintenance refers to relatively complicated maintenance operations,such as hardware check and operating system check that are regularly implemented bythe trained maintenance personnel in a certain period (for example, a week, a month, aquarter or a year).

1-1


ZXUN iCX(MSCS) Routine Maintenance Guide

1.2 Purposes

Purpose of Daily Maintenance

Daily maintenance helps you to:

l Find out the alarms of the equipment or hidden risks in time and adopt appropriatemeasures to handle and recover the faults so as to maintain the healthy level of theequipment and reduce equipment faults.

l Find out the abnormalities of link status or connection during service running in timeand adopt appropriate measures to handle and recover system faults so as to ensurenormal service running.

l Grasp the running status of the equipment and network in real time, know the runningtrend of the equipment and network, and improve the sudden-event handling efficiencyof the maintenance personnel.

Purpose of Regular Maintenance

Regular maintenance helps you to:

l Make the equipment always remain in good condition, and ensure the safe, stableand reliable running of the system.

l Find out hidden troubles, including natural aging, function expiry and performancedeterioration during the running of the equipment in time, and handle these troublesto prevent the accidents.

1.3 PrecautionsRead and observe the following precautions when you perform routine maintenance.

l Establish a complete set of maintenance regulations for the equipment room tostandardize the routine maintenance work. Create detailed duty logs and makedetailed records of the daily running state of the system, version, data change,upgrading and troubleshooting, so that it will be convenient for fault analysis andtroubleshooting once a fault occurs. Keep a shift record to define the responsibilitiesclearly.

l Maintenance personnel should be well trained on the skills of basic operations andemergency troubleshooting before taking the post and should grasp the knowledgerelated to the equipment maintenance and the networks. During maintenanceoperations, the maintenance personnel must follow the instructions described in therelated manuals of the product. To avoid any accident, the personnel must put onantistatic wrist straps before operating the equipment. The maintenance personnelshould have a precise working attitude and professional maintenance skills, whichshould be enhanced through constant learning.

l Make records for all the important operations (such as board switching, systemresetting, and software loading). Before the operations, the qualified maintenancepersonnel must analyze the feasibility of the operations and take the related backup,

1-2


Chapter 1 Routine Maintenance Overview

emergency, and security measures. Back up the data before you do any change tothem. Do not delete the backup data until the equipment runs properly for a timeperiod (usually a week) after you change the data.

l Set different NMS passwords with different access rights, put them under strictmanagement, and make changes to them periodically. The passwords should beprovided only to the maintenance personnel.

l Do not play games or surf the Internet on PC terminals. Do not install, run or copy anyother software not related to the system on the terminal. Do not use the PC terminalfor any other purposes.

l Have the regularly used tools and meters ready. The regularly used tools and metersinclude screwdrivers (flathead and crosshead), signaling tester, network cable pliers,multi-meter, AC power, telephone line, and network cables. Test and calibrate theinstruments and meters regularly to ensure their accuracy.

l Check spare components regularly to ensure they are sufficient in quantity and are ingood condition, and make sure that the components are not affected by dampness ormould. Keep them away from those faulty ones removed during maintenance. Returnthe faulty boards for repair in time and prepare sufficient spare parts for the majorboards.

l Keep the software and documents that might be used during the maintenance in ahandy place.

l Keep the equipment room in normal temperature and humidity. Keep the environmentneat and clean. Take dust prevention and damp prevention measures. Keep rats andinsects out.

l Ensure the primary power of the system is stable. Check the system grounding andlightning protection ground periodically. Check the lightning protection system beforeand after the storm season to make sure that related facilities are in good condition.

l Make sure that the light in the equipment room is bright enough for the maintenance.Any damaged lamp should be repaired in time.

l The maintenance personnel must perform regular checks and tests each day andmake records by referencing related suggestions in the manual.

l Handle any fault as soon as it is detected. Record the detailed information of theproblem that cannot be solved, and then contact local ZTE office or customer servicecenter for help.

l If there is an emergency in the equipment room, the maintenance personnel mustbe calm and perform troubleshooting according to the Troubleshooting Manual, andcontact local ZTE office or customer service center immediately.

l Keep the contact information of ZTE local office in a noticeable place and let allmaintenance personnel notice it, so they can contact ZTE in time when they needhelp. Maintain the contact information regularly to keep it up to date.

1-3



1.4 Basic Requirements for Maintenance Personnel

Knowledge

l Get familiar with the telecommunication knowledge such as the mobiletelecommunication theory and soft-switching principle.

l Get familiar with signaling protocols related with Signaling System No.7 (SS7),Mobile Application Part (MAP), Signalling Transport (SIGTRAN) and ITU-T Rec.H.248 Gateway Control Protocol (H.248).

l Get familiar with related technical specifications.l Understand the basic knowledge about computer networks, including Ethernet,

TCP/IP, Browser/Server architecture, WEB application and database.l Get familiar with ATCA structure.l Get familiar with product knowledge of the ZXUN iCX(MSCS), concerning functional

structure, call flow, and service flow.

Networking and Running Environment

l Know hardware architecture and performance parameters of the ZXUN iCX(MSCS)system very well.

l Know the networking architecture of the ZXUN iCX(MSCS) system very well.l Know signaling and protocols of the ZXUN iCX(MSCS) system and the networking

devices very well.l Get familiar with network architecture and channel allocation of the relevant

transmission devices.

Requirements for Device Operations

l Master daily operations of the ZXUN iCX(MSCS).l Know well which operations will cause interruption of some or all services.l Know well which operations will damage devices.l Know well which operations will lead to user complaints.l Know well emergency or backup measures.

Instruments and Meters

The maintenance personnel of the ZXUN iCX(MSCS) must be familiar with how to useinstruments and meters to locate a fault. The common instruments and meters includemulti-meter and the SS7 analyzer.

1.5 Routine Maintenance Tools

Software Maintenance Tools

l Failure observerl Signal trace

1-4


Chapter 1 Routine Maintenance Overview

l Fault managementl Dynamic managementl Performance managementl Log management

Hardware Maintenance Tools

l Frequently-used tools and meters should be provided, such as antistatic wristlet,screwdriver (straight or cross), signaling tester, network cable pliers, multi-meter,telephone line and network cables. The instruments and meters should be checkedand calibrated regularly to ensure their accuracy.

l The spare parts should be often checked to ensure the enough and perfect inventoryof routine spare parts and prevent them against moisture and mildewing. Spare partsshould be stored separately from the damaged ones replaced in the maintenanceprocess, and marked for the convenience of distinguishing them. Common spareparts and components should be replenished in time when used up.

l The software and documentation for potential use during maintenance should be keptat hand as required, so that they are obtainable when necessary.

1.6 Introduction to Routine Maintenance Operationsl You can perform related routine maintenance operations on the Local Maintenance

Terminal (LMT).l To perform related routine maintenance operations on a GPBB0/GPBX1 board, use

either of the following method to log in .

Connect the display, keyboard and mouse respectively to the VGA display, PS/2keyboard and PS/2 mouse port on the GPI1 board.

Log in to the blade server by using the debugging computer:

You can use a remote control tool or the GUI to log in to the blade at theFabric-plane IP addresses for the local network.

Note:

The Windows operating system (Windows XP or Windows 2003) should bealready installed on the debugging computer. The debugging computer cancommunicate properly with the blade.

l For the operations on a Windows operating system, this manual takes Windows 2003for example.

1-5



This page intentionally left blank.

1-6


Chapter 2Daily Routine MaintenanceTable of Contents

Checking System Alarms or Notifications ...................................................................2-1Equipment Room Environment Check .......................................................................2-2Checking Board Running Status.................................................................................2-3Performance Statistics Check.....................................................................................2-4

2.1 Checking System Alarms or NotificationsItem

Check the system alarms or notifications.

Purpose

Make sure that there is no abnormality in the system.

Procedure

1. Log in to the Local Maintenance Terminal(LMT).2. In the web page of the LMT, click (Fault Management) button in the lower left corner

to open the Fault Management tab page as shown in Figure 2-1.

Figure 2-1 Fault Management Tab Page

2-1



3. When checking the system alarms, you should check the following items in every checkperiod.l Current real-time alarms and current alarm recovery informationl Historical alarms occurred in the past 24 hoursl Current real-time notificationsl Historical notifications occurred in the past 24 hours

Criteria

There is no abnormality alarm or notification in the system. Any alarm or notification foundshould be analyzed and processed in time.

1. You can double-click the alarm message on the tab page to view the alarm handlingsuggestions and eliminate the related faults according to the suggestions.

2. If the problem cannot be solved, contact ZTE technical personnel immediately.

2.2 Equipment Room Environment Check

2.2.1 Checking Equipment Room Temperature

Item

Check the equipment room temperature.

Purpose

Make sure that the equipment work under normal temperature.

Procedure

Check the temperature shown on the air conditioner.

Criteria

In normal cases, the temperature in the equipment room is 15 C~25 C.

If the temperature does not reach the standard, you should adjust it in time so that it meetsthe requirements for normal running of the equipment.

2.2.2 Checking Equipment Room Humidity

Item

Check the equipment room humidity.

Purpose

Make sure that the equipment works under normal humidity.

2-2


Chapter 2 Daily Routine Maintenance

Procedure

Check the relative humidity shown at the air conditioner.

Criteria

In normal cases, the relative humidity in the equipment room is 30 %~70 %.

If the humidity does not reach the standard, you should adjust it in time so that it meetsthe requirements for normal running of the equipment.

2.3 Checking Board Running Status

Item

Check the board running status.

Purpose

Make sure each board of the ZXUN iCX(MSCS) runs properly.

Procedure

1. Check the board alarms in the Fault Management tab page of the LMT.

a. Log in to the LMT.

b. In the web page of the LMT, click (Fault Management) button in the lower leftcorner to open the Fault Management tab page.

c. Check the alarms of each board to see whether there is any abnormality on theboard.

2. Check the board indicators on the rack.

Criteria

l There is no alarm for any board fault in the Fault Management tab page of the LMT.l The indicators of each board are proper. The normal status of each commonly used

indicator is shown in the following table.

Indicator Meaning Normal Status Remarks

OOS Service status indicator Off -

OK Health status indicator Flashing green -

H/S Hotswap indicator Off -

ACT Active/standby status

indicator

Active: On

Standby: Off

-

HOST Running/Alarm indicator Flashing green -

2-3



Indicator Meaning Normal Status Remarks

HD1/HD2 Hard disk status indicator Flashing green when the

hard disk is performing

read/write operations

The indicators

are available for

GPBB0/GPBX1

boards only.

Note:

For more details about indicators, see ZXUN iCX(MSCS) MSC Server HardwareDescription.

If any indicator is found abnormal, locate and handle the fault according to thecorresponding alarm messages reported on the LMT. If you cannot solve the problem,contact technical support personnel of ZTE.

2.4 Performance Statistics Check

2.4.1 Checking MTP3 Signaling Links

Item

Check the MTP3 signaling links.

Purpose

Check whether the performance index values of the MTP3 signaling links have obviousfluctuations.

Procedure

1. Log in to the LMT.2. In the web page of the LMT, click (Performance Management) button in the lower

left corner to open the Performance Management tab page.

Note:l Before performing the query for the first time, you must create the corresponding

measurement task.l The path to locate the required type of measurement (MTP3 Link) on the

navigation tree of performance management is as follows: Signal Measurement> N7 Measurement > MTP3 Signaling Link Measurement.

2-4


Chapter 2 Daily Routine Maintenance

3. Query the measurement task of measurement type MTP3 Link. Measure theperformance index values during busy hours based on a collection granularity of 5minutes. The performance indices to be queried include: Average Traffic SignalingLink and MTP3 Link Load.

4. Check the performance indices of the MTP3 signaling links during busy hours. Checkwhether the load is evenly shared among the signaling links or the load of some sig-naling links is too high.

Criteria

l The difference of load between any two links to the same office should not exceed 20%.

l The load of 2 M signaling link should not exceed 0.2 Erl, and that of 64 k signaling linkshould not exceed 0.4 Erl.

In case of abnormalities in performance statistical data, contact themaintenance personnelof related NEs to handle together. If necessary, contact ZTE.

2.4.2 Checking SCTP Links

Item

Check the SCTP links.

Purpose

Check whether the performance index values of the SCTP links have obvious fluctuations.

Procedure




measurement task.l The path to locate the required type of measurement (SCTP Link) on the

navigation tree of performance management is as follows: Signal Measurement> SIGTRAN Measurement > SCTP Link Measurement.

3. Query the measurement task of measurement type SCTP. Measure the number ofmessages sent and received during busy hours based on a collection granularity of 5minutes.

2-5



4. Check the performance indices of the SCTP links during busy hours. Check whetherthe load is evenly shared among the signaling links or the load of some signaling linksis too high.

Criteria

l The difference of load between any two associations to the same office should notexceed 20 %.

l The load of each SCTP link should not exceed 0.2 Erl.

In case of abnormalities in performance statistical data, contact themaintenance personnelof related NEs to handle together. If necessary, contact ZTE.

2-6


Chapter 3Weekly Routine MaintenanceTable of Contents

Clock Check...............................................................................................................3-1Resource Usage Check..............................................................................................3-3Hardware Check ........................................................................................................3-5Windows Operating System Check ...........................................................................3-8Checking Data Backup on LMT ..................................................................................3-9Performance Statistics Check...................................................................................3-10

3.1 Clock Check

3.1.1 Checking Clock Synchronization

Item

Check the clock synchronization.

Purpose

Make sure that the time of the OMP module is synchronous with the SNTP server(generally, the OMM server).

Procedure

1. Log in to the LMT. The default tab page is Terminal.

Note:

To open the Terminal tab page, in the web page of the LMT, click (Terminal) buttonin the bottom left corner.

2. Check the SNTP server configuration.

a. On the command navigation tree in the left pane of the Terminal tab page,select Device Configuration > Device Parameter Configuration > NE GlobalParameter Configuration > Show SNTP Server Address to open the SHOWSNTP command interface.

b. Click button to execute the command.

3-1



3. Check the time of the OMP module.

a. On the command navigation tree in the left pane of the Terminal tab page, selectMaintenance Management > Dynamic Management > Time Management >Show Time to open the Show TIME command interface.

b. Click button to execute the command.

4. Check the time of the OMM server. In the web page of the LMT , the time in the bottomright corner is the OMM servers time .

5. Check whether the OMP time is the same as the OMM server time.

Criteria

l The configuration of the SNTP server (the IP address of the SNTP server) is correct.If the SNTP server configuration is not correct, you can change it with the SET SNTPcommand.

l The OMP time is the same as the OMM server. If the OMP time is not correct, youcan change it with the UPD TIME command.

3.1.2 Checking Clock Running Status

Item

Check the clock running status.

Purpose

Make sure that the clock works in the "TRACE" status.

Procedure


Note:


2. On the command navigation tree in the left pane, select Maintenance Management> Patrol Maintenance > Equipment Management > Check System Clock Statusto open the CHECK CLOCK STATUS command configuration interface.

3. Click button to execute the command.4. Check the status of the HOST and T/C indicators (corresponding to the clock sub-card)

on the panel of the SWI1/SWI2 board.

3-2


Chapter 3 Weekly Routine Maintenance

Criteria

l The execution result of the CHECKCLOCK STATUS command shows that the clockworks in "TRACE" status.

l The HOST indicator on the panel of the SWI1/SWI2 board flashes green and the clockstatus indicator T/C is steady on.

If the clock status if abnormal, handle according to alarms. If you cannot remove thisproblem, contact ZTE for help.

3.2 Resource Usage Check

3.2.1 Checking Hard Disk Usage of the OMP Module

Item

Check the OMP module storage usage.

Purpose

Make sure the OMP module has sufficient storage space.

Procedure

1. Log in to the GPBB0 board where the OMP module is located using a remote controltool such as SCRT.

2. Run the df -k command in the Terminal tab page to check the hard disk space.

Criteria

The free space of each file system on the hard disk of the GPBB0 board where the OMPmodule is located should be above 10 % of the total space. Otherwise, you should removethe files of the previous version or expired log files from the disk.

3.2.2 Checking CPU/Memory Usage of the OMM Server

Item

Check the CPU and memory usage of the OMM server.

Purpose

Make sure that the OMM server has sufficient CPU and memory resources.

Procedure

1. Log in to the GPBX1 board of the OMM server using a remote control tool such asvncviewer.

3-3



2. Run the vmstat command in the Terminal window to check the CPU/memory usage.

Note:

You can also check the memory usage of the OMM server with the CHECK MEMORYSTATUS command in the Terminal tab page of the LMT.

Criteria

l Normally, the CPU usage should not exceed 50 %. If the CPU usage exceeds 50 %,check for abnormal processes.

l Normally, the available memory should be more than 90 % of the total. If the memoryusage has exceeded 90 % for a long time, you should expand the physical memory.

3.2.3 Checking the Hard Disk Usage of the OMM Server

Item

Check the hard disk usage of the OMM server.

Purpose

Make sure that the OMM server has sufficient hard disk resource.

Procedure


Note:


2. On the command navigation tree in the left pane, selectMaintenance Management >Patrol Maintenance > OMM Server > Check OMM HDC Status to open the CHECKHDC STATUS command configuration interface.

3. Click button to execute the command.

Criteria

l The file systems where the operating system and the database are located shouldrespectively have at least a free space of 800 MB, and the free space of each should

3-4



be above 10 % of the total size of the file system. If the free space is not enough,delete some useless files.

l The free space in each of the other file systems should also be above 10 % of thetotal size of the file system. If the free space is not enough, delete some useless files.

3.3 Hardware Check

3.3.1 Checking the Chassis Management Module

Item

Check the running status of the new chassis management module (NCMM).

Purpose

Make sure that NCMM runs properly.

Procedure

Check the related indicators of NCMM.

Criteria

l Three alarm indicators respectively marked with ~ are off.l The CPU status indicators respectively marked with HOST flashes green.l The hot-swap indicator marked with H/S is steadily off.l If NCMM works in the active mode, the active/standby status indicator marked with

ACT is steadily on. Otherwise, it is steadily off.

If any indicator is found in improper status, locate the fault according to the correspondingalarm given on the LMT and perform troubleshooting. If the problem still exists, contactZTE for help.

3.3.2 Checking the Switching Board

Item

Check the running status of the switching board (SWBB0/SWBB1).

Purpose

Make sure that the switching board runs properly.

Procedure

Check the indicators on the front panel of the switching board.

3-5



Criteria

l The service status indicator marked with OOS and the hot-swap indicator marked withH/S are off, and the health status indicator marked with OK flashes green.

l The indicators of the two blades (active and standby) should be in the same status.


3.3.3 Check the Power Module

Item

Check the running status of the new power module (NPEM) of the shelf.

Purpose

Make sure that the power module of the shelf runs properly.

Procedure

Check the -48/-60 VA, -48/-60 VB, H/S and OK indicators on the shelfs power module.

Criteria

l The health status indicator marked with OK flashes green.l The power status indicators marked with -48/-60 VA and -48/-60 VB are off.l The hot-swap status indicator marked with H/S is steadily off.


3.3.4 Check the Fan Module

Item

Check the running status of the new fan module (NFCM) of the shelf.

Purpose

Make sure that the fan module of the shelf runs properly.

Procedure

Check the RUN, ALM and H/S indicators on the shelfs fan module.

3-6



Criteria

l The work status indicator marked with RUN flashes green.l The alarm status indicator marked with ALM is steadily off.l The hot-swap status indicator marked with H/S is steadily off.


3.3.5 Checking the GPBB0/GPBX1 Boards

Item

Check the running status of the GPBB0/GPBX1 boards.

Purpose

Make sure that the GPBB0/GPBX1 boards are running properly.

Procedure

Check the indicators status on the front panel of each GPBB0/GPBX1 board.

Criteria

l The service status indicator marked with OOS and the hot-swap indicator marked withH/S are steadily off, and the health status indicator marked with OK flashes green.

l The active/standby status indicator marked with ACT is normal (steady on on theactive board and off on the standby board), and the running status/alarm indicatormarked with HOST flashes green.

l During the hard disk read/write operations, the hard disk status indicator marked withHD1/HD2 flashes green.


3.3.6 Checking the rear board GPI1 of the GPBX1

Item

Check the running status of the KVM interface of each GPI1 board.

Purpose

Make sure that the KVM interface of each GPI1 board is running properly.

3-7



Procedure

1. Check the VGA port, PS/2 keyboard port and the PS/2 mouse port on the GPI1 boardto see whether the connection of each is proper. Check whether you can use the KVMto operate the GPBX1 board normally.

2. Check whether the holding screws for the cable joints on the GPI1 board are loose.

Criteria

The VGA port, PS/2 keyboard port and the PS/2 mouse port on the GPI1 board all functionnormally.

If you find anything abnormal and cannot solve the problem, contact of ZTE for help.

3.4 Windows Operating System Check

3.4.1 Check the Anti-Virus Software

Item

Check for anti-virus software installations on the hosts where the Windows operatingsystems are installed.

Purpose

Prevent the Windows operating systems from being infected by viruses.

Procedure

Check whether the anti-virus software is installed on each host where the Windowsoperating system is installed and whether the corresponding virus database is updatedrespectively.

Criteria

The anti-virus software should be already installed on each host where the Windowsoperating system is installed.

3.4.2 Checking Virus Database Update

Item

Check the virus database update of the anti-virus software on each host where theWindows operating system is installed.

Purpose

Prevent virus infection in the Windows operating system.

3-8



Procedure

Check the virus database update dates and update the virus databases on each hostwhere the Windows operating system is installed.

Criteria

l Update the virus database manually at least once a week.l Disable the regular virus scanning function, and manually scan the system for viruses

when the call traffic is low.

3.5 Checking Data Backup on LMT

Item

Check the scheduled tasks of backup data .

Purpose

Make sure that the scheduled tasks of backup data run properly.

Procedure


Note:


2. On the command navigation tree in the left pane, select Configuration DataMaintenance > Backup And Restore > Automatic Backup Management > ShowAutomatic Backup Strategy to open the SHOW AUTO STRATEGY commandconfiguration interface.

Note:

When you are selecting a command under Configuration Data Maintenance> Backup And Restore > Automatic Backup Management on the commandnavigation tree, do not click the button (which displays commonly-used commandsonly) above the navigation tree.

3. Click button to execute the command.

3-9



Note:

To add an automatic backup strategy, execute theADDAUTOSTRATEGY command.

Criteria

The scheduled task of backup the data is correctly configured and activated. The systemproduces the related backup data in the corresponding path for saving the backup files onschedule.

Note:

The scheduled task of backup the data is often set to back up every day. The data tobe backed up includes alarm data, performance data, security data , log data, basicconfiguration data and IP stack configuration data .( Execute the SHOW SYS SETcommand to query the relation between the ID and Name of System Object Set.)

3.6 Performance Statistics Check

3.6.1 Checking Resource Load

Item

Query the measurement data a weekly and check the module resource load.

Purpose

Make sure that the module resource load is proper without obvious fluctuation.

Procedure



3-10




measurement task.l The path to locate the required type of measurement (Resource Load

Measurement) on the navigation tree of performance management is as follows:Global Measurement > Resource Load Measurement.

3. Query the measurement jobs of the measurement type Resource LoadMeasurement. Collect performance index values in busy hour in 5-minute granularity.

The performance indices to be queried include the following counters.

l Mean Ratio of the CPU Usage(%)l Peak Ratio of the CPU Usage(%)l Duration(s) of CPU Keeping in Peak Statel Mean Ratio of the Memory Usage(%)l Peak Ratio of the Memory Usage(%)l Mean Ratio of the Hard Disk Flash Usage(1/10000)l Duration(s) of the Main Processor Keeping Than Statistics Threshold

4. Check the performance indices of themodule resource load in busy hour. Compare theindex values with historical data and check whether the data has obvious fluctuation.

Criteria

The performance indices of the module resource load are within the normal range. Themean ratio of the CPU usage should not exceed 90 %, and the mean ratio of the memoryusage should not exceed 95 %. During the same busy hours, the indices are stable, andcomparing with the historical data, the fluctuation should not exceed 10 %.

l If the average load of all services or signaling modules is very high for a long time,consider capacity expansion according to the current designed capacities and actualnetwork capacities.

l If the average load of only a few main processors is very high, check whether theservice load-sharing an the signaling load-sharing are proper, and whether someCPUs bear heavy load. Plan the improper load-sharing again.

l If the load-sharing is properly and the actual capacity is far less than the designedcapacity, but the average load of some main processors is still high, pay attention to itand contact the local ZTE office to collect relevant log files so as to analyze whetherany hidden safety problem exists.

3.6.2 Checking MscServer Load

Item

Query the measurement data a weekly and check the MscServer load.

3-11



Purpose

Make sure that the MscServer load is proper without obvious fluctuation.

Procedure




measurement task.l The path to locate the required type of measurement (MscServer Load

Measurement) on the navigation tree of performance management is as follows:Global Measurement > MscServer Load Measurement.

3. Query the measurement jobs of the measurement type MscServer LoadMeasurement. Collect performance index values in busy hour in 5-minute granularity.

The performance indices to be queried include the following counters.

l Mean Ratio of the CPU Usage(%)l Peak Ratio of the CPU Usage(%)l Duration(s) of CPU Keeping in Peak Statel Mean Ratio of the Memory Usage(%)l Peak Ratio of the Memory Usage(%)l Mean Ratio of the Hard Disk Flash Usage(1/10000)l Duration(s) of the Main Processor Keeping Than Statistics Threshold

4. Check the performance indices of the MscServer load in busy hour. Compare theindex values with historical data and check whether the data has obvious fluctuation.

Criteria

The performance indices of the MscServer load are within the normal range. The meanratio of the CPU usage should not exceed 90 %, and the mean ratio of the memoryusage should not exceed 95 %. During the same busy hours, the indices are stable, andcomparing with the historical data, the fluctuation should not exceed 10 %.

l If the average load of all services or signaling modules is very high for a long time,consider capacity expansion according to the current designed capacities and actualnetwork capacities.

l If the average load of only a few main processors is very high, check whether theservice load-sharing an the signaling load-sharing are proper, and whether someCPUs bear heavy load. Plan the improper load-sharing again.

3-12



l If the load-sharing is properly and the actual capacity is far less than the designedcapacity, but the average load of some main processors is still high, pay attention to itand contact the local ZTE office to collect relevant log files so as to analyze whetherany hidden safety problem exists.

3-13




3-14


Chapter 4Monthly RoutineMaintenanceTable of Contents

Checking Versions......................................................................................................4-1Checking System Alarms and Notifications.................................................................4-2Checking Heat Radiation of Racks .............................................................................4-3Checking for Viruses ..................................................................................................4-3

4.1 Checking Versions

Item

Check the running versions.

Purpose

Make sure that the version running on each CPU of each board is consistent with the OMMversion.

Procedure


Note:


2. Query the packages running on all the boards.

a. On the command navigation tree in the left pane, select Version Management> Version Query > Show Running Package to open the SHOW RUNVERcommand configuration interface.

b. Click the button to execute the command.

4-1



c. Click the Operation Record tab. If the Result is Success, click the SHOWRUNVER command to view the detailed execution results in the right of the tabpage.

3. Query the packages running on the OMM server.

a. On the command navigation tree in the lower left pane, select VersionManagement > Version Query > Show Package on OMM Server to open theSHOW OMMPKG command configuration interface.

b. Click the button to execute the command. The current OMM server runningpackages appear in the Text Result tab page.

Criteria

The CPU version of each board is consistent with the version of the server. If you find anyinconsistency, confirm the cause and contact ZTE for help if necessary.

4.2 Checking System Alarms and Notifications

Item

Check the system alarms and notifications.

Purpose

Make sure that there is no abnormality in the system.

Procedure

1. Log in to the LMT.2. In the web page of the LMT, click (Fault Management) button in the lower left corner

to open the Fault Management tab page.3. When checking the system alarms and notifications, you should check the following

items in every check period.l Current real-time alarms, current alarm recovery information and real-time

notificationsl Historical alarms occurred in a monthl Notifications occurred in a week

Criteria

There is no abnormality alarm or notification in the system. Any alarm or notification foundshould be analyzed and processed in time.

1. You can double-click the alarm message on the tab page to view the alarm handlingsuggestions and eliminate the related faults according to the suggestions.

2. If the problem cannot be solved, contact ZTE technical personnel immediately.

4-2


Chapter 4 Monthly Routine Maintenance

4.3 Checking Heat Radiation of Racks

Item

Check the heat radiation of racks.

Purpose

Make sure that the air intakes and outtakes of the racks are not blocked and the fans areworking properly.

Procedure

1. Check when the last cleaning was made and whether the dust filter needs to becleaned. Clean dust filters regularly.

2. Check whether air intakes and outtakes of the racks are blocked.3. Check whether the fans are working normally, whether their rotation speeds are

consistent, and whether there is any abnormal sound.4. Check whether the blank panels at the front and back slots are fixed well.

Criteria

l The dust filters are clean. If they are not clean, clean them.l The air intakes and outtakes are not blocked. If they are blocked, clear the substances

blocking them. If necessary, contact ZTE for help.l The fans are working properly. If they are not, handle the problem. If necessary,

contact ZTE for help.l The blank panels are fixed well. If they are not, fix them.

4.4 Checking for Viruses

Item

Check for and remove viruses on each host where the Windows operating system isinstalled.

Purpose

Prevent the Windows operating system from being infected by viruses.

Procedure

Use the anti-virus software to check for any virus on all the hard disks of each host wherethe Windows operating system is installed by following the anti-virus software instructions.

Criteria

Normally, no virus is found.

4-3



If any virus is found during the check, kill the virus by following the virus handlingsuggestions given by the anti-virus software, and restart the host as long as the normalrunning of services is not affected.

4-4


Chapter 5Quarterly RoutineMaintenanceTable of Contents

Cleaning the Dust Screens.........................................................................................5-1CGSL Operating System Check .................................................................................5-2Checking Remote Control Tools .................................................................................5-5

5.1 Cleaning the Dust ScreensItem

Clean the dust screens of the cabinet.

Purpose

Clean the dust screens periodically to prevent dust from entering the cabinet, which mayaffect the heat dissipation of the cabinet.

Procedure

1. Unlock and open the cabinet door.2. Loosen the fastening bolts of the dust-proof subrack on the cabinet.3. Evenly pull out the dust-proof subrack with two hands, pay attention that do not scatter

the dust on the dust-proof subrack to the cabinet.4. Dismantle the dust-proof subrack, and take out the dust screens.5. Clean the dust screens with warm water (lower than 40 ) and dry them.

Caution!

Do not install the wet dust screens.

6. Install the dust screens into the dust-proof subrack.7. Insert the dust-proof subrack into the cabinet, and fasten it using the bolts.

Criteria

The cleaned dust screens should be clean and dust-free.

5-1



5.2 CGSL Operating System Check

5.2.1 Checking Hard Disk Space

Item

Check the hard disk space of the GPBX1 board.

Purpose

Make sure that the hard disk of the GPBX1 board has enough space.

Procedure

1. Log in to the GPBX1 board of the OMM server using a remote control tool such asXmanager.

2. Run the df -k command in the Terminal window to check the hard disk space. Thefollowing is an instance of the command execution result.

# df -k

Filesystem K-blocks Used Available Use% Mounted on

/dev/sda2 9920624 5939384 3469172 64% /

/dev/sda6 18782896 3834264 13979112 22% /swap

/dev/sda5 29753556 176204 28041540 1% /home

/dev/sda1 497829 16333 455794 4% /boot

tmpfs 517568 0 517568 0% /dev

Criteria

The hard disk usage should not be higher than 90 %. Otherwise, delete some uselessfiles.

5.2.2 Checking Swap Space

Item

Check the swap space of the GPBX1 board.

Purpose

Make sure that the swap space of the GPBX1 board is not used abnormally.

Procedure


5-2


Chapter 5 Quarterly Routine Maintenance

2. Run the swapon -s command in the Terminal window to check the swap space. Thefollowing is an instance of the command execution result.

# swapon -s

Filename Type Size Used Priority

/dev/sda3 partition 16763816 63481 -1

Note:

In this example, the swap space is 16 GB.

Criteria

The swap space usage of the GPBX1 board should not exceed 5 %. Otherwise, payattention to the running of the GPBX1 board. If there is any abnormality, contact ZTE toask related technical personnel to troubleshoot the problems.

5.2.3 Checking CPU/Memory Usage

Item

Check the CPU/memory usage of the GPBX1 board.

Purpose

Make sure that the CPU/memory usage of the GPBX1 board is proper.

Procedure


2. Run the vmstat command in the Terminal window to check the CPU/memory usage.The following is an instance of the command execution result.

# vmstat

procs -----------memory---------- --swap-- ----io--- --system-- -----cpu----

r b swpd free buff cache si so bi bo in cs us sy id wa st

0 0 60 7123156 448944 8008452 0 0 0 0 1052 1182 0 0 100 0 0

0 0 60 7123156 448944 8008452 0 0 0 0 1051 1168 0 0 100 0 0

Criteria

The CPU usage of the GPBX1 board should not exceed 50 % for a long time and thememory usage of the GPBX1 board should not exceed 90 %. Otherwise, pay attention tothe running of the GPBX1 board. If there is any abnormality, contact ZTE to ask relatedtechnical personnel to troubleshoot the problems.

5-3



5.2.4 Checking Log Files

Item

Check the log files of the GPBX1 board.

Purpose

Make sure the GPBX1 board runs properly.

Procedure


2. Check log file /var/log/messages on the GPBX1 board.

Criteria

There is no word like panic, fault or error in the log file. Otherwise, contact ZTE to askrelated technical personnel to troubleshoot the problems.

5.2.5 Checking Disk I/O

Item

Check the disk I/O of the GPBX1 board.

Purpose

Make sure the disk I/O of the GPBX1 board is normal.

Procedure


2. Run the iostat 1 10 command in the Terminal window to check the disk I/O. Thefollowing is an instance of the command execution result.

5-4



Figure 5-1 iostat Execution Result Example

Criteria

The iowait should not exceed 30 % continuously for a long time. Otherwise, contact ZTEto ask related technical personnel to troubleshoot the problems.

Note:

The iowait refers to the percentage of the time for CPU to wait for I/O in a statistical periodof time.

5.3 Checking Remote Control Tools

Item

Check the remote control tools (such as vncviewer).

Purpose

Make sure that the remote control tools works properly.

Procedure

1. On the OMM server, check whether the remote desktop is enabled.

a. ChooseSystem >Preferences > Remote Desktop to open theRemote DesktopPreference dialog box, as shown in Figure 5-2.

5-5



Figure 5-2 Preference of Remote Desktop Dialog Box

b. In the dialog box as shown in Figure 5-2, check whether select Allow otherusers to view your desktop and Allow other users to control your desktop,and check whether select Require the user to enter this password and set apassword that is the login password for vncviewer.

c. Click Close to close this dialog box.

2. On the LMT terminal where vncviewer is installed, check whether vnviewer canlog in to the OMM server properly.

a. Double-click the vncviewer software to open the dialog box as shown in Figure5-3.

Figure 5-3 Login Dialog Box

b. Fill in the IP address of the OMM server in the VNC server text box, and thenclick OK. If you have set a password in the Remote Desktop Preference dialogbox on the OMM server, the dialog box as shown inFigure 5-4 pops up. Type thepassword, and then click OK. Otherwise, log in to the main window of the OMMserver directly.

5-6



Figure 5-4 Password Dialog Box

Criteria

The LMT terminal can connected with the OMM server using remote control tool. Ifconnected fail, ping the IP address of the OMM server.

5-7




5-8


Chapter 6Yearly Routine MaintenanceTable of Contents

Equipment Room Environment Check ........................................................................6-1Hardware Check ........................................................................................................6-2

6.1 Equipment Room Environment Check

6.1.1 Checking the DC Power Supply

Item

Check the DC power supply of the equipment.

Purpose

Make sure that the dual-channel DC power supply of the equipment works properly.

Procedure

1. Check and record the DC operating voltage displayed on the DC power supply devicein the equipment room.

2. Check the power of the equipment currently using the DC power supply. If adual-channel power supply is available, check both channels of the power supply.

Caution!

Generally the communication equipment uses a dual-channel power supply, pleasecheck and confirm the two channels of the power system, so as to prevent the potentialhazards which may be caused by a channel of power failure.

Criteria

The standard value of the DC operating voltage is -48 V, and the tolerable variation rangeis -57 V to 40 V.

The standard value of the DC operating voltage is -60 V, and the tolerable variation rangeis -72 V to 50 V .

6-1



If the power supply is abnormal, restore the power supply to normal status as soon aspossible.

6.1.2 Checking the AC Power Supply

Item

Check the AC power supply of the equipment.

Purpose

Make sure that the dual-channel AC power supply of the equipment works properly.

Procedure

1. Check and record the AC operating voltage displayed on the AC power supply devicein the equipment room.

2. Check whether the two-channel power supply of the servers works properly.

Caution!

Generally the communication equipment uses a dual-channel power supply, pleasecheck and confirm the two channels of the power system, so as to prevent the potentialhazards which may be caused by a channel of power failure.

Criteria

l In principle, the AC power supply should adopt a dual-channel UPS power, and theactive/standby and the load sharing devices should be connected to two channels ofthe power supply separately.

l The work range of the AC operating voltage is 220 V22 V and 50 Hz2.5 Hz.l Estimate the AC power supply required by the equipment, and make sure that the

power supply has a power redundancy of at least 20 %.

If the power supply is abnormal, restore the power supply to normal status as soon aspossible.

6.2 Hardware Check

6.2.1 Checking Cable Connections

Item

Check the cable connections.

6-2


Chapter 6 Yearly Routine Maintenance

Purpose

Make sure that the cables of the equipment are properly connected.

Procedure

1. Check the connections of the network cables.2. Check the connections of the inter-cabinet cables.

Criteria

l The network cables are reliably connected and not damaged, with clear labels.l The inter-cabinet cables are firmly and reliably connected. The cables should be in

good condition, with clear labels.

If the cable connection is loose, reconnect it under the direction of ZTE technical supportengineers. If the cables or labels are damaged, replace them by professionals under thedirection of ZTE technical support engineers.

6.2.2 Checking Spare Parts

Item

Check the spare parts.

Purpose

Make sure that the spare parts of the equipment are sufficient and not damaged.

Procedure

1. Check the quantity of the spare parts.2. Check whether the spare parts are damaged.

Criteria

The necessary spare parts should be sufficient and not damaged.

If the spare parts are insufficient or damaged, buy them as soon as possible.

6-3




6-4


Appendix ARoutine Maintenance FormsTable of Contents

Form of Daily Maintenance Records ....................................................................... A-1

Form of Weekly Maintenance Records ................................................................... A-3

Form of Monthly Maintenance Records .................................................................. A-5

Form of Quarterly Maintenance Records ................................................................ A-6

Form of Yearly Maintenance Records ..................................................................... A-7

A.1 Form of Daily Maintenance RecordsTable A-1 ZXUN iCX(MSCS) Daily Maintenance Records

Office Name: Date (D/M/Y):

Attended Time

From __ to __

Off-Going Person: On-Coming Person:

1. Check the system alarms: Check the current and historical alarms or notifications

displayed in the Fault Management tab page of the LMT.

Normal Abnormal

Exceptional symptom:

2. Check the board running status: Check the board alarms in the Fault Management tab

page of the LMT. Check the board indicators on the rack.

Normal Abnormal


3. Check the MTP3 signaling links: Check whether the performance index values of the

MTP3 signaling links have obvious fluctuations in the Performance Management tab page

of the LMT. The fluctuation should not exceed 5 % except in festivals and holidays.

Normal Abnormal


Basic Check Item

4. Check the SCTP links: Check whether the performance index values of the SCTP links

have obvious fluctuations in the Performance Management tab page of the LMT. The

fluctuation should not exceed 5 % except in festivals and holidays.

Normal Abnormal


A-1




Attended Time

From __ to __

Off-Going Person: On-Coming Person:

Equipment Room

Environment

1. Temperature (In normal cases, the temperature shown at the air conditioner in the

equipment room is 15 C~25 C.)

Normal Abnormal

2. Humidity (In normal cases, the relative humidity shown at the air conditioner in the

equipment room is 30 %~70 %.)

Normal Abnormal

Duty Memo Fault and Troubleshooting:

Remaining problems:

Inspection by Team-leader:

A-2


Appendix A Routine Maintenance Forms

A.2 Form of Weekly Maintenance RecordsTable A-2 ZXUN iCX(MSCS) Weekly Maintenance Records

Office name: Date (D/M/Y):

Maintenance Item Result Maintenance

Person

Time

Check whether the time of the OMP module is the same as the

SNTP server.

Check whether the indicators on clock sub-card are in proper

statuses. Check whether the clock works in TRACE status.

Check whether the OMP module has sufficient storage space.

Check whether the OMM server has sufficient CPU and memory

resources.

Check whether the OMM server has sufficient hard disk space.

Check whether the NCMM of each shelf is running properly.

Check whether the switching board of each shelf is running

properly.

Check whether the power module of each shelf is running

properly.

Check whether the fan module of each shelf is running properly.

Check whether the GPBB0/GPBX1 boards are running properly.

Check whether the KVM interface of each rear board GPI1 of the

GPBX1 board is running properly.

Check whether the anti-virus software is installed on the host

where the Windows operating system is installed.

Check the virus database update dates and update the virus

databases on the host where the Windows operating system is

installed.

Check whether the scheduled task of backing up data is running

properly.

Check whether the resource load is in the normal range, and

whether the fluctuation is lower than 10 %.

Check whether the MscServer load is in the normal range, and

whether the fluctuation is lower than 10 %.

A-3



Office name: Date (D/M/Y):


Person

Time

Problems and Troubleshooting:

Remaining problems:

A-4



A.3 Form of Monthly Maintenance RecordsTable A-3 ZXUN iCX(MSCS) Monthly Maintenance Records


Maintenance Item Result Maintenance Person Time

Check whether the versions running on the CPUs of each board

are consistent with the OMM version.

Check the current alarms and notifications and the historical

alarms and notifications on the LMT. Check whether there is no

abnormality in the system.

Check whether the air intakes and outtakes of the racks are not

blocked and the fans are working properly.

Check for and kill the virus on all the hard disks of each host where

the Windows operating system is installed. Check whether the

operating system of the host is infected by viruses.


Remaining problems:

A-5



A.4 Form of Quarterly Maintenance RecordsTable A-4 ZXUN iCX(MSCS) Quarterly Maintenance Records



Person

Time

Clean the dust screens periodically, so as to prevent dust from

entering the cabinet, which may affect the heat dissipation of the

cabinet.

Check whether the host where the CGSL operating system is

installed has enough hard disk space.

Check whether the swap space of the host where the CGSL

operating system is installed is used abnormally.

Check whether the host where the CGSL operating system is

installed has enough CPU and memory resources.

Check the log files to see whether the host where the CGSL

operating system is installed runs properly.

Check whether the disk I/O of the host where the CGSL operating

system is installed is normal.

Check whether the remote control tool is normal.


Remaining problems:

A-6



A.5 Form of Yearly Maintenance RecordsTable A-5 ZXUN iCX(MSCS) Yearly Maintenance Records


Maintenance Item Result Maintenance Person Time

Check whether dual-channel DC power supply of the equipment

works properly.

Check whether dual-channel AC power supply of the equipment

works properly.

Check whether the cables of the equipment are properly connected.

Check whether the spare parts of the equipment are sufficient and

not damaged.


Remaining problems:

A-7




A-8


Appendix BCautions for RoutineMaintenance

Table B-1 Cautions for Routine Maintenance

Operation Caution Possible Results Caused by Misoperation

Do not unplug online

active board.

l The data synchronization between active and standby boards

requires a particular period when the standby board operates

properly. When the active board is unplugged online, the latest

data on it cannot be completely and automatically backed

up to the standby board, but the system will switch over the

boards automatically. It will easily cause statistical errors and

data loss.

l When the standby board operates improperly, this operation

will interrupt all the service processing of corresponding

module, resulting in partial or global service block in the

system.

Do not press the RST

button on the board

panel at will.

l A board will implement the hardware reset by force in case

of the RST button on the board panel being pressed. Only

qualified maintenance personnel can press it when serious

fault occurs in the system.

l Pressing the RST button on the active board panel will reset

the active board. The consequence is the same as that of

"Unplugging online active board".

Board-related

operations

Do not plug and unplug

boards without wearing

antistatic wrist straps.

The static electricity on human bodies may cause great damage to

the components. If installed or removed without wearing antistatic

wrist straps, the boards may get damaged or operate unstably.

Cable-related

operations

Do not plug or unplug

network cables inside

the cabinet at will.

This operation probably will interrupt services and the

communication between the front-end and back-end systems.

Power-supply-

related operations

Do not operate the power

switches on the cabinet

at will.

You can operate various power switches by following operation

procedure only when serious fault occurs in the system, or

during network upgrade, network expansion, and component

replacement. This operation will stop system operation and

interrupt services.

B-1




B-2


GlossaryATCA- Advanced Telecommunications Computing Architecture

GUI- Graphical User Interface

H.248- ITU-T Rec. H.248 Gateway Control Protocol

IP- Internet Protocol

KVM- Keyboard, Video and Mouse

LMT- Local Maintenance Terminal

MAP- Mobile Application Part

MTP3- Message Transfer Part layer 3

NCMM- New Chassis Management Module

NFCM- New Fan Controller Module

NPEM- New Power Entry Module

OMM- Operation & Maintenance Module

OMP- Operation & maintenance Main Processor

SCTP- Stream Control Transmission Protocol

SIGTRAN- Signalling Transport

SNTP- Simple Network Time Protocol

SS7- Signaling System No. 7

I



TCP- Transfer Control Protocol

UPS- Uninterruptible Power Supply

VGA- Video Graphic Adapter

II


About This ManualChapter 1 Routine Maintenance Overview1.1 Classification1.2 Purposes1.3 Precautions1.4 Basic Requirements for Maintenance Personnel1.5 Routine Maintenance Tools1.6 Introduction to Routine Maintenance Operations

Chapter 2 Daily Routine Maintenance2.1 Checking System Alarms or Notifications2.2 Equipment Room Environment Check 2.2.1 Checking Equipment Room Temperature2.2.2 Checking Equipment Room Humidity

2.3 Checking Board Running Status2.4 Performance Statistics Check2.4.1 Checking MTP3 Signaling Links2.4.2 Checking SCTP Links

Chapter 3 Weekly Routine Maintenance3.1 Clock Check3.1.1 Checking Clock Synchronization3.1.2 Checking Clock Running Status

3.2 Resource Usage Check3.2.1 Checking Hard Disk Usage of the OMP Module3.2.2 Checking CPU/Memory Usage of the OMM Server3.2.3 Checking the Hard Disk Usage of the OMM Server

3.3 Hardware Check3.3.1 Checking the Chassis Management Module3.3.2 Checking the Switching Board3.3.3 Check the Power Module3.3.4 Check the Fan Module3.3.5 Checking the GPBB0/GPBX1 Boards3.3.6 Checking the rear board GPI1 of the GPBX1

3.4 Windows Operating System Check 3.4.1 Check the Anti-Virus Software3.4.2 Checking Virus Database Update

3.5 Checking Data Backup on LMT3.6 Performance Statistics Check3.6.1 Checking Resource Load3.6.2 Checking MscServer Load

Chapter 4 Monthly Routine Maintenance4.1 Checking Versions4.2 Checking System Alarms and Notifications4.3 Checking Heat Radiation of Racks4.4 Checking for Viruses

Chapter 5 Quarterly Routine Maintenance5.1 Cleaning the Dust Screens5.2 CGSL Operating System Check5.2.1 Checking Hard Disk Space5.2.2 Checking Swap Space5.2.3 Checking CPU/Memory Usage5.2.4 Checking Log Files5.2.5 Checking Disk I/O

5.3 Checking Remote Control Tools

Chapter 6 Yearly Routine Maintenance6.1 Equipment Room Environment Check6.1.1 Checking the DC Power Supply6.1.2 Checking the AC Power Supply

6.2 Hardware Check6.2.1 Checking Cable Connections6.2.2 Checking Spare Parts

Appendix A Routine Maintenance FormsA.1 Form of Daily Maintenance RecordsA.2 Form of Weekly Maintenance RecordsA.3 Form of Monthly Maintenance RecordsA.4 Form of Quarterly Maintenance RecordsA.5 Form of Yearly Maintenance Records

Appendix B Cautions for Routine MaintenanceGlossary

msc server routine maintenance guide

Documents