General Maintenance Procedure

8/9/2019 General Maintenance Procedure

http://slidepdf.com/reader/full/general-maintenance-procedure 1/38

General Maintenance Procedures

DN9770958Issue 9-1 en

# Nokia Siemens Networks 1 (38)

MSC/HLR, Rel. M14.2, Product Documentation,

v.2



The information in this document is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This documentation is intended for theuse of Nokia Siemens Networks customers only for the purposes of the agreement under whichthe document is submitted, and no part of it may be used, reproduced, modified or transmitted inany form or means without the prior written permission of Nokia Siemens Networks. Thedocumentation has been prepared to be used by professional and properly trained personnel,and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomescustomer comments as part of the process of continuous development and improvement of thedocumentation.

The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given “as is” and all liabilityarising in connection with such hardware or software products shall be defined conclusively andfinally in a separate agreement between Nokia Siemens Networks and the customer. However,Nokia Siemens Networks has made all reasonable efforts to ensure that the instructionscontained in the document are adequate and free of material errors and omissions. NokiaSiemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which

may not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NOEVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THISDOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL,DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUTNOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESSOPPORTUNITY OR DATA, THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THEINFORMATION IN IT.

This documentation and the product it describes are considered protected by copyrights andother intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of Nokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respective owners,and they are mentioned for identification purposes only.

Copyright © Nokia Siemens Networks 2008. All rights reserved.

2 (38) # Nokia Siemens Networks DN9770958Issue 9-1 en




Contents

Contents 3

List of tables 4

List of figures 5

Summary of changes 7

1 General maintenance procedures 91.1 Automatic maintenance functions 101.2 Maintenance recommendations 12

1.2.1 Service of peripheral devices 13

2 Performing daily maintenance routines 152.1 Outputting alarm history 152.2 Outputting current alarms 162.3 Checking working states of computer units 162.4 Checking working states of I/O devices 162.5 Outputting clear codes 162.6 Inspecting printers 172.7 Inspecting tape units 172.8 Updating FB build 182.9 Taking backup copies of FB build on DDS tape 18

2.10 Cleaning CTU 19

3 Performing weekly maintenance routines 233.1 Printing and saving unit states 233.2 Checking status of charging files 233.3 Checking blocked alarms 243.4 Checking date and time 243.5 Checking printers 24

4 Performing monthly maintenance routines 254.1 Checking hardware alarms 254.2 Cleaning visual display unit 254.3 Cleaning printer 26

5 Performing six-monthly maintenance routines 29

6 Performing yearly maintenance routines 316.1 Checking voltages 316.2 Cleaning Floppy Disk Unit 33

7 Marking unused blocks on a hard disk 35

Glossary 37



Contents



List of tables

Table 1. The service of peripheral devices on the DX 200 network element. 13

Table 2. Cleaning the Cartridge Tape Unit 20

Table 3. Cleaning the VDU 26

Table 4. Cleaning the LPT 26

Table 5. Feed voltage to DC/DC converters 31

Table 6. Voltages of racks 32

Table 7. Cleaning the floppy disk unit 33





List of figures

Figure 1. DX 200 fault management principles. 11



List of figures







Summary of changes

Changes between document issues are cumulative. Therefore, the latest

document issue contains all changes made to previous issues.

Changes between issues 9 –1 and 9

Further structural enhancements made in the document.

Changes between issues 9 and 8

The document's layout and structure has been updated.

Changes between issues 8 and 7 –

2

Structural enhancements made in the document, and outdated information

on cleaning a Magnetic Tape Unit (MTU) has been removed.



Summary of changes









If you need to replace a faulty plug-in unit with a new one, consult the

instructions for replacing plug-in units.

For instructions on how to cancel the alarm situation, refer to Cancelling

alarms.

If a fault in the system stops the I/O system of the OMU, the maintenance

software, or the entire network element, no detailed information on the fault

is printed out. Refer to I/O system troubleshooting for more information.

Use Printouts of Starting Phases when monitoring the start or restart of the

network element using the service terminal.

Refer to Recovery and unit working state administration when you need to

know about the restart of functional units and how to change their working

states.

In addition to the instructions mentioned above, there are maintenance

instructions that describe how to change I/O devices, how to maintain the

network and how to use the auxiliary maintenance devices and software.

1.1 Automatic maintenance functions

System maintenance handles all the fault situations and user-initiated

configuration management tasks within the hardware and software of the

system. System Maintenance is responsible for availability performance

on the network element level. It is designed to perform its task as

automatically and autonomously as possible.

Usually all activities can be performed remotely unless the action to be

taken involves the hardware. Depending on the structure of your network,

you may need to change some of the logical file outputs e.g. diagnostic

and observation outputs to be able to receive all the information that is

needed to perform maintenance activities remotely.

The main areas of system supervision are presented in the figure below.





Figure 1. DX 200 fault management principles.

Supervision of hardware and software for fault detection

. Hardware supervision relies on equipment database and routine

tests executed for hardware components.

. Software supervision detects loss of control in software. The

supervision is based on watchdog timers and supervision

messages.

.

Supervision of real time keeps the units of a system and systems inthe O&M network in the same time.

Alarm handling for analysing the fault information from differentsources and for informing the operator

. Is based on collecting fault observations. These are hardware

alarms and fault observations from program blocks and

preprocessors.

. Makes decisions by using predefined rulebases, and starts up

automatic recovery functions when necessary.

. Stores alarm data in an alarm log file.

. Informs the user with alarm printouts and alarm lamp panel controls.

SUPERVISIONSYSTEM

-Faultdetection

ALARMSYSTEM

-Alarmprintouts

-Updating of failureinformation

RECOVERYSYSTEM

-Faultelimination

FAULTLOCATIONSYSTEM

-Faultlocation

FAILUREAlarm

message

Activationof

faultlocation

Activationof

recovery



General maintenance procedures



Recovery for eliminating the effects of faults

. Eliminates the effects of faults by utilising the redundancy of the

hardware. Processor and preprocessor restarts are also used.

. Controls the restarting of the system so that restarts are carried out

in the correct order quickly and reliably.

. Starts up automatic fault location.

Fault location

. Faults in the system hardware are located in one plug –in unit in 70%

of cases, and in one of four plug –in units in 95% of cases.

. Complies with the ITU-T requirement for the average active repair

time of 30 minutes.

. System hardware configuration data is used for determining which

diagnostic programs should be executed and which configurationparameters should be used. The data is also used for determining

which plug –in units should be suspected as faulty when a fault has

been observed.

. The generated diagnostic reports contain lists of faulty plug –in units.

1.2 Maintenance recommendations

The recommended maintenance routines can be carried out by anyone

from the regular operating personnel of the network element, as these

routines do not require special training or disassembling of equipment.

They can be carried out during normal working hours except where stated

otherwise. The Customer is recommended to keep a network element

diary. The diary should be network element-specific, but you can store it in

the Operation and Maintenance Centre if the network element is not

usually manned.

Start filling in the network element diary already when the network element

is being set up and installed.

You are recommended to record the following events in the network

element diary:

. Hardware changes

. Software and hardware updates (change notes, correction

deliveries, etc.)





. Essential modifications to the configuration or routing in the network

element. Safecopying

. Operational failures

. Any other relevant information

Entries must include the date, time and maintenance personnel's name.

1.2.1 Service of peripheral devices

This section describes the service of the different peripheral devices. Thefocus here is on the equipment, even though the service intervals for the

peripheral devices are mentioned.

This table does not contain any of the equipment that is not supplied by

Nokia but what may have an effect on the performance of the network

element. Nevertheless, it must be regularly tested according to the

manufacturer's instructions. Additionally, there are a few general

maintenance recommendations that you can take into account with the

service of the external equipment. See Performing maintenance routines

on external equipment for more information on the subject.

Table 1. The service of peripheral devices on the DX 200 network element.

DEVICE SERVICE INTERVAL DURATION ACTION

Visual Display Unit (VDU) Monthly 5 - 10 min General cleaning

Cartridge Tape Unit (CTU) Depends on the

operating hours. See

Cleaning CTU for

instructions.

5 - 10 min Cleaning using a

cleaning cartridge

Line Printer (LPT) Monthly , weekly , daily 5 - 10 min General cleaning, change

the printer ribbon

Floppy Disk Unit (FDU) Yearly 15 - 20 min Cleaning using cleaning

disk

Hard Disk Unit (WDU) Usually none, but see

Hard disk drive for

instructions on special

cases.

None None

MO Disk Unit None but if damaged,

send the unit to Nokia's

Hardware Service (HWS)

for repairing

None None



General maintenance procedures







2 Performing daily maintenance routines

During normal hours, you must investigate the alarms as they are

reported.

2.1 Outputting alarm history

Steps

1. Output the alarm history for the previous 24hrs

2. Split the output into smaller units if there is a large number of

alarms.

You can use the CLS parameter to split the output into smaller units.

All alarms must be investigated and accounted for.

Further information

Example

Output all alarms from 16th May 97 at 9.30 (AHP).

ZAHP::1997–

05–

16,09–

30–

0

Example

Output 3-star alarms from 16th May 97 at 10.00

ZAHP::CLS=AL3:1997–05–16,10–0–0



Performing daily maintenance routines



2.2 Outputting current alarms

Steps

1. Output current alarms (AHO)

ZAHO;

2.3 Checking working states of computer units

Steps

1. Check that any abnormal working states are accounted for (USI)

ZUSI:COMP;

You can use the USL command to list units in an incorrect state. The

following command lists all the units in incorrect state (that is, other

than WO-EX or SP-EX or if the unit is in faulty state, FLTY):

ZUSL:,INCO:ALL;

2.4 Checking working states of I/O devices

Steps

1. Check the working states of I/O devices (ISI)

For example, to check the states of I/O devices connected to the

OMU, provide the following.

ZISI:,OMU:ALL;

2.5 Outputting clear codes

Steps

1. Output the clear codes (TUT)

ZTUT:CLR;





2. Study the report and investigate any abnormal trends

You can obtain the previous measurement period using the TUL

command.

ZTUL:SER;

3. Use the TOF command to monitor an unexpectedly high amount

of certain clear codes

ZTOF:S,,<codes>;

You can monitor 5 different clear codes simultaneously. The results(in ASCII) will be output via the TRAOBS logical file.

Note

Remember that clear code monitoring, as well as any other monitoring,

is not meant to be left on permanently.

2.6 Inspecting printers

Steps

1. Ensure that all printers have enough paper for the next 24 hours

2. Ensure that all printers are operating correctly

2.7 Inspecting tape units

Steps

1. Ensure that all tape units have enough tape for the next 24

hours

2. Ensure that all tape units are operating correctly






2.8 Updating FB build

Before you start

To be able to update the FB build, you need to have the FB build created

already by using the mode=full parameter of the WKS command.

Note

Take fallbacks during low traffic, for example, at night.

Steps

1. Update the FB build (WKS)

ZWKS:MODE=DATA;

Note

You can do this only if the node contains a full fallback copy of the BU

build.

2. Check in the log file that the backup was successful (WKP)

ZWKP:DATA:EMODE;

Further information

For more information on the fallback copying procedure, see the

instructions on Safecopying .

2.9 Taking backup copies of FB build on DDS tape

This section describes how to copy the FB build to the Cartridge Tape Unit

(CTU).





Note

Use several DAT tapes and swap them each week to prevent a tape

failure during the operation from destroying the only backup.

Steps

1. Check the name of the directory where the fallback copy is

stored (WQO)

ZWQO:CR;

Note

Make sure that the FB build has been updated as described in section

Updating the FB build .

2. Copy the files (IPS)

The following command copies data from the system disk located in

the OMU to the CTU located in the same OMU.

ZIPS:”OMU”,WDU-S,/FB980815,,,:,CTU-0,,,:

NAME=BACKUP1, DIR=INC, ISD=Y;

3. Always remove the tape from the drive

This prevents dust from entering the drive mechanism.

Further information

For more information on how to take a backup of the FB build, refer to

instructions on Safecopying .

2.10 Cleaning CTU

This section describes the service of the Cartridge Tape Unit (CTU).






Table 2. Cleaning the Cartridge Tape Unit

DEVICE All models

SERVICE INTERVAL In backup copying, service takes place after every 25 hours of use. It takes

approximately 25 hours to write 7 cartridge tapes full.

When information is stored continuously, as in charging, cleaning takes place after 5

cartridge tapes are written full. If the tapes are not written full, you can clean the

CTU less frequently.

Note, always clean the CTU if the indicator on the unit indicates that the read-write

head is dirty.

ESTIMATED

DURATION

5 - 10 min

TOOLS Cleaning cartridge (for example, HP92283K)

Note

The Cartridge Tape Unit (CTU) drive must be cleaned every 25 hours

working time using a cleaning tape (for example, HP92283K).

The 25 hours mentioned in the table above refers to active operating

time that the tape unit spends reading or writing on the tape. The

passive operating time is insignificant from the service point of view. Always remove the tape from the drive after backup copying.

Clean the CTU with a cleaning tape. Discard the cleaning tape after 25

uses and start using a new one. The cleaning must not be done too

often because it shortens the life of the cartridge tape unit. However,

cleaning must not be omitted, since it ensures the faultless functioning

of the CTU.

Steps

1. Remove the tape from the tape unit if necessary

2. Insert the cleaning tape into the drive

Make sure this is done with the same care as with a cartridge tape to

avoid damage to the loading system.

3. Wait until it is ejected automatically (2-3 mins)





Note

Discard the cleaning tape after 25 uses and start using a new cleaning

tape.

4. Insert a cartridge tape into the tape unit

Storage of cartridge tapes

Store the cartridge tapes in their protective covers. Avoid storing the tapes

near strong magnetic fields.

Tape operating circumstances:

. Temperature from 5 to 45 degrees Celsius

. Relative humidity from 20 to 80 %

Tape storage circumstances:

. Temperature from 5 to 32 degrees Celsius

. Relative humidity from 20 to 60 %

Note

If you store tapes in temperatures other than the operating temperature,

do not insert them into the drive immediately. Before using such a tape,

let the temperature difference even out by keeping the tape in the

operating temperature for at least two hours.












3.3 Checking blocked alarms

Steps

1. Check the blocked alarms (ABO)

ZABO;

2. Look for any blocked alarms that cannot be accounted for

3.4 Checking date and timeSteps

1. Check the date and time of the network element (DCD)

ZDCD;

Note

Remember that changing the time affects all time measurements

currently in progress in the network element (or elements). Thisincludes, for example, traffic measurement periods and measurement

of the conversation time in detailed charging. The effects of changing

the time must be taken into account in these measurements (in the

analysis and further processing of the results).

3.5 Checking printers

Steps

1. Check the printer ribbons

2. Clean the printers if required





4 Performing monthly maintenance

routines

This section describes the routines to be carried out at one-monthintervals.

4.1 Checking hardware alarms

Steps

1. Check the hardware alarms and alarm inputs (WAE)

The following command tests the alarm inputs of all cartridges inrack 1A:

ZWAE:1A;

Note

This command only works in network elements with cartridge

construction.

4.2 Cleaning visual display unit

This section describes the service of the Visual Display Unit (VDU).

The table below shows the Visual Display Unit service interval, the

estimated duration of service, and the tools needed in service.



Performing monthly maintenance routines



Table 3. Cleaning the VDU

DEVICE All models

SERVICE INTERVAL Monthly

ESTIMATED DURATION 5 - 10 min

TOOLS Soft cloth and cleaning fluid or suitable cleaner tissue

Note

Fluids containing oils or alcohol must not be used for the cleaning. Amild soap solution is suitable.

Steps

1. Wipe the screen, the case, and the keyboard

Use a cloth moistened with the cleaning solution or with ready-made

cleaner tissues.

2. Adjust the brightness and contrast of the display if necessary

Note

Avoid having the display unit adjusted too bright since that shortens the

lifetime of the Cathod Ray Tube (CRT).

4.3 Cleaning printer

This section describes the service of printers (LPT).

The table below shows the printer service interval, the estimated duration

of service, and the tools needed in service.

Table 4. Cleaning the LPT

DEVICE All models





Table 4. Cleaning the LPT (cont.)

SERVICE INTERVAL Monthly

ESTIMATED DURATION 5 - 10 min

TOOLS Soft cloth, vacuum cleaner equipped with an absolute filter

when necessary

Note

Cleaning fluids containing alcohol must not be used when cleaning therubber-coated parts of the printer.

Steps

1. Disconnect the printer from the mains power supply

2. Open the cover

3. Vacuum clean the inside of the printer

You need to do this with a vacuum cleaner that is equipped with an

absolute filter and a thin plastic nozzle.

4. Change the ribbon if necessary

5. Close the cover

6. Connect the printer to the mains power supply



Performing monthly maintenance routines





5 Performing six-monthly maintenance

routines

Running fault diagnoses and changing unit states

Run fault diagnoses on all spare computer units, message buses, and

clock units.

Note

The routines in this section should be carried out in low traffic periods.

Steps

1. Change the unit state to TE (USC)

For example, to change the SSU 0 –1 to test state:

ZUSC:SSU,0,1:TE;

2. Run the fault diagnosis (UDU)

For example, to run all fault diagnoses on SSU 0 –1:

ZUDU:SSU,0,1;

3. If any of the fault diagnoses fail, investigate and correct the

fault.

You can do this by using the normal maintenance procedures.

4. Change the unit states of the units diagnosed above to WO-EX

(USC)

ZUSC;



Performing six-monthly maintenance routines



Note

In larger network elements the above routines will be time-consuming.

The operator may first wish to perform the fault diagnoses followed by

unit changeovers one month later. The frequency of the routines can be

adjusted accordingly. Carry out the unit changeovers during low traffic.





6 Performing yearly maintenance routines

This section presents the routines to be carried out yearly.

6.1 Checking voltages

Cartridge construction

There is no need to check the voltages in cartridge construction networkelements.

Subrack construction

If the network element construction is based on subracks, check thevoltages of the subracks at the vertical power buses.

Steps

1. Measure the supply voltage at the rack-specific power supply

points

Refer to the table below for the voltage tolerances.

Table 5. Feed voltage to DC/DC converters

Nominal voltage Tolerance

-48 V -41.5 V to -57 V

-60 V -48 V to -75 V

2. Check and measure the voltages of the vertical power busses

Refer to the table for the tolerances of idle voltages.



Performing yearly maintenance routines



Table 6. Voltages of racks

Nominal voltage Tolerances of idle voltages

5.1 V 5.10 - 5.20 V

12.1 V 12.10 - 12.25 V

120 V 120 - 130 V (49.5 - 50.5 Hz)

Note

Measured voltages must be within +/- 5% of the nominal voltage. If thevoltage does not meet the tolerance requirements, replace the power

supply unit and send the faulty unit to service.

3. Check the earthing connections visually

4. Measure the voltage difference between the earth (DOV) and +

lead (0V)

Note

The voltage difference must be under 1V. If the voltage difference is

greater than 1V, do the following:

a. Check what the difference was when the network element was

installed and commissioned

b. Check the results of previous measurements if there are any

c. Check that the voltage meter is correctly calibrated

d. Check that the voltage meter is properly connected

e. Measure the voltage difference in each earthing connection

5. If the measurement result is still not within the allowed limits,

note this down in the network element diary







. When you remove a disk from the drive, always return it to the case.

. Keep the disks away from magnetic fields and ferromagneticsubstances which can become magnetized. A strong magnetic field

will destroy the data on the disks.

. Do not expose the disks to heat or sunshine.

. Do not touch or try to clean the surfaces of a disk. Rubbing may

destroy the data on the disk.

. Use 3,5" HD disks only.





7 Marking unused blocks on a hard disk

Hard disk drives need no service.

However, with time there will be read and write errors on the disks due to

corrupted blocks. These blocks can be marked as 'bad blocks', that is,

unused blocks.

Steps

1. Mark these blocks as 'bad blocks', that is, unused blocks (IWB)

For example, to take block number 1234H out of use, do thefollowing:

Z I W B : : W B : B , 1 2 3 4 ;

For more information on bad blocks, see section Bad blocks in

Introduction to replacing WDUs .

If there are a lot of bad blocks on a disk, the disk can be replaced

with a new one. For instructions on replacing the hard disk, see

Replacing the hard disk unit .



Marking unused blocks on a hard disk







Glossary

Abbreviations

BU (Backup) Backup, refer to Backup (BU) build in concepts.

FB (Fallback) Fallback, refer to Fallback (FB) build in concepts.

LFILES

(Loadable

Files directory)

The LFILES directory contains the data files loaded and updated by the file

system. The directory can also contain data files loaded by the initial

loading system.

SCMANA

(Software

Configuration

Management

directory)

The Software Configuration Management directory, that is, the directory for

managing the software builds. This directory only contains files (SOMAFI)

which are used by the build management function integrated into the

exchange. The name is identified by the software (including boot) and it

must not be changed.

UT (Untitled) Untitled, refer to Untitled (UT) build in concepts.

Concepts

BU (Backup

build)

A build on disk that is usually defined as active and in use, and which is

therefore normally loaded by the initial loading system when the exchange

is restarted. The BACKUP build cannot be removed with buildmanagement commands.

Cartridge Cartridge is a capsule into which the plug-in units are placed. The cartridge

is placed in a rack.

Change note Notification of a change or modification in a product (equipment or a plug-

in unit, software or hardware) sent to a customer.

Correction

delivery

Software which consists of chosen corrections to faults.

FB (Fallback

build)

A safecopy build of the BACKUP build on disk. The exchange can be

returned to the FALLBACK build with MML commands.

Preventive

maintenance

Maintenance carried out at predetermined intervals or according to

prescribed criteria and intended to reduce the probability of failure or the

degradation of the functioning of an item.

Service

terminal

A terminal which can be connected to a system for maintenance and

operating purposes.



Glossary



Subrack The subrack construction contains racks which are equipped with

subracks.

UT (Untitled

build)

Software build which is created without a need to make it active. The

system allows more than one build to have this status. For example, the

status of the FB build becomes UT when you use the WQS command to

create an FB build.


Documents

General Maintenance Procedure