59
1 © Nokia Siemens Networks Presentation / Author / Date For internal use MAINTENANCE SWPLAT ESS

05 DX IPA ESS Maintenance FlexiBSC Et Unités Fonctionnelles

Embed Size (px)

Citation preview

PowerPoint PresentationFor internal use
For internal use
After this training module, the student should be able to:
Theory:
Know the subsystems for supervision in DX200 and IPA2800
Interpret correctly both locally and NetAct generated alarm printouts
Explain the operating states of redundant and non-redundant units
Interpret a diagnostics printout correctly
Practical:
Display unit working states
For internal use
To maintain the functionality of the system even in fault situations
PURPOSE OF MAINTENANCE
This slide is designed to increase interactivity in the beginning of the session.
TIP: Point the questions openly to customers. This works also as a test to see how much they understand about the idea of maintenance.
Q: WHAT IS THE PURPOSE OF MAINTENANCE??
(A:to keep up the quality of the system, even in faulty situations)
“exchange should still work even if the thunder hits it!”
Q:WHY??
A: Customers want to get their calls through: switching
Operators want to have downtime in minimum because of charging. downtime=l>money lost
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
System Functional units
Automatic
MML
OMU
(FROM PREVIOUS SLIDE:)
> THE RESULT: FOCUS ON RELIABILITY
The purpose of this slide is to show how the reliability demands have been implemented in the DX 200 platform
- DX 200 is a distributed system. The only connection between computer units is the message bus. If a unit fails, does it automatically cause the failure to the other one? No, because units are independent.
- If a unit fails,the functions can still be saved. There is backup for crucial units. i.e. DX200 uses redundancies in functional units. There are different redundancy principles (explained in File admin topic & recovery of maintenance)
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
Fault Management - Architecture
inform alarm system if faults found
each domain has its own internal supervision
Diagnostics
informs the operator
informs recovery if the unit may be taken back into use
Recovery System
maintains system performance by taking spare unit into use
Alarm System
new architecture in Alive Supervision
alarms
support for several sources of alarms added (Radio Network, NEMU)
recovery
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
Preventive maintenance to service peripheral devices.
Routine tasks to ensure the good working order of the exchange.
Carried out daily, weekly, fortnightly, monthly, every six months, or yearly.
Preventive and Routine tasks in maintenance
Preventive maintenance to service peripheral devices = La maintenance préventive au service de périphériques.
Routine tasks are part of the daily routine for O&M personnel. The list is not “official”, but it is a collection of different sources in customer documentation.
TIP 1: Tell/ask customers that/if they have something of their own as a list for checking routine tasks. If they do, that is very good. If they do not, they could consider it
TIP 2: The list in the book can be used in two different ways: taken into use as such or used as a reference when defining operator specific list.
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
Daily
Daily
Daily
Make backup copies of the Fallback software build to the removable data storage device
Daily
Weekly
Weekly
Weekly
Weekly
Six monthly
For internal use
inform alarm system if faults found
each domain has its own internal supervision
Diagnostics
informs the operator
informs recovery if the unit may be taken back into use
Recovery System
maintains system performance by taking spare unit into use
Alarm System
Supervision
The purpose of the supervision system is to detect possible faults in the system before any serious disturbances can take place. The supervision system detects disturbance or fault situations and informs the alarm system.
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
Continuous Supervision
(for HW)
(by watchdog for processor)
Supervision Message (for software)
Continuous supervision uses a set of alarm inputs integrated to each plug-in unit of the exchange connected to the system’s hard-wired alarms (in DX 200) or the Hardware Management System (HMS/HMS-A in IPA2800). The plug-in unit uses these alarm inputs for indicating hardware alarms concerning the plug-in unit.
Watchdog timers are hardware-implemented counters used for supervising the operation of real-time processes. Every processor unit in the system must initialise its own watchdog logic regularly; otherwise the watchdog restarts the entire computer unit if the last initialisation has not been performed in time.
Message-based software supervision is used for the supervision of program blocks. OMU built-in test programs start automatically and send special supervision messages regularly to every computer unit via the ATM virtual connections/message bus for internal unit-to-unit communication
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
Real time
Compare time of the system to other system + compare time of each unit to main clock unit e.g. CHU, STU
Supervision Objects
For internal use
in four ways
Notices & Disturbances are additional info, no need to worry (except many of them occur in a short period)
Alarms include *, **, *** alarms (refer to Alarm Ref Manual)
Error ratio counters used for observing events that happen repeatedly.
SW ALARM, FAULTS DETECTED BY SW, BASICALLY ALL ALARMS
FOUR TYPES
error ratio counters
-Explain notices, disturbances, one,two,three star alarms. Questioning technique works well if the customers are familiar with alarms. If time permits & the customers are interested: Explain the alarms numbering 0-999 Notices, 1000-1999 Disturbances, 2000-2999 Alarms .
- Explain error ration counters for example with the help of a flip chart. All calls are marked to the event side and unsuccesful calls to both sides. If a faulty side has reached its value first, alarm is on and both sides restart their counters.
Event side
Faulty side
For internal use
WIRED ALARMS <Hardware Alarm>
SOFTWARE ALARMS
TRUNK CIRCUIT ALARMS
Trunk: a group of PCM circuits going to one direction
ET performs supervision, and failure info is forwarded to alarm system via signalling units.
PIU in SU that collecting alarms: AS7_U (Cartridge)
SUPERVISION SYSTEM DETECTS THE ALARMS AND INFORMS THE ALARM
SYSTEM.
DETECTION OF ALARMS:
- physically connected
- on - off type of alarms or error ratio counters
TIP: Use this slide as a “main slide”. Get back to this slide after going through all three cases
TIP: Instead of using this slide it is efficient to use whiteboard, flip etc to collect together different cases of detection & collection of alarms
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
for Cartridge
Internal Alarms are collected from sub racks (PIU loop), cables (check loop), the clock system, power supply units, fuses and tone generator.
External alarms are generally environmental alarms. Examples are temperature alarms, alarms from an external power supply or humidity level alarms.
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
Supervises HW of the system while the system is working
Tests are not allowed to disturb the system
Produces alarms about the failures with a weight indicating the severity of the failure
System or user starts actions to recover from the detected hardware failure
Target is to cover all the hardware of the network element
In practice HW and SW implementation set the limits
HW controlling SW has the main responsibility to provide HW supervision services.
There are many different ways to supervise condition of the hardware
Data does not get through a path
Alarm bit set by the hardware in a register
Bad counter value
All SFU ports are under supervisioning.
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
inventory)
Passing of system initialisation data in the system start-up phase
Forced control of functional unit states
Controlling cooling and power supply
Transferring short messages to units not having ATM connectivity
Optionally external equipment control and supervision
Functions of the HW Management System
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
PIU level
The Hardware Management System (HMS) provides a duplicated serial bus between the master node (located in the OMU) and every plug-in unit in the system. The bus provides fault tolerant message transfer facility between plug-in units and HMS master node.
The HMS is used in supporting auto-configuration, collecting fault data from plug-in units and auxiliary equipment, collecting condition data external to network element and setting hardware control signals like restart and state control in plug-in units.
The hardware management system is robust. For example, it is independent of system timing and it can read hardware alarms even from a plug-in unit without power. Thus it allows power alarms and remote power on/off switching function.
The hardware management system forms a hierarchical network (see above). The duplicated master network connects the master node with the bridge node of each subrack. The subrack level networks connect the bridge node with each plug-in unit in the subrack.
HMS supports following functions:
In system set-up: Collecting data of existing racks and subracks and their indexes. Collecting equipping data of every subrack, plug-in unit types, their variants and versions.
In normal use: Collecting fault data from plug-in units and auxiliary equipment and condition data external to network element. Setting hardware control signals like restart and state control in plug-in units. Reading and writing of any configuration data stored in non volatile memory of unit computer or control computer to check hardware configuration and to set communication channels between computers for ATM based message passing via the ATM switch fabric. Offering protected message link between HMS master node and an unit having no connectivity via the ATM switch fabric. Controlling auxiliary equipment like fan trays and AC/DC power supplies. Controlling equipment and space external to network element like door locking, temperature and other states, alarms and conditions of street side cabinets, wall mounting cabinets and telecommunication sites or other installation space.
In maintenance operations: Detecting extracting and inserting a plug-in unit. Identifying inserted plug-in unit. Setting automatically configuration data of an inserted plug-in unit.
Under severe fault conditions: HMS is able to read hardware alarms from a plug-in unit without power feed. HMS performs all its tasks even when system timing is missing.
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
IPA2800
Collecting alarms from external equipment
Sending alarms via HMS to OMU
Controlling the lamp panel
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
inform alarm system if faults found
each domain has its own internal supervision
Diagnostics
informs the operator
informs recovery if the unit may be taken back into use
Recovery System
maintains system performance by taking spare unit into use
Alarm System
For internal use
Alarm System Principle(DX200)
Normally to NMS
2
Recovery
System
For internal use
Five Alarm Classes
SW ALARM, FAULTS DETECTED BY SW, BASICALLY ALL ALARMS
FOUR TYPES
error ratio counters
-Explain notices, disturbances, one,two,three star alarms. Questioning technique works well if the customers are familiar with alarms. If time permits & the customers are interested: Explain the alarms numbering 0-999 Notices, 1000-1999 Disturbances, 2000-2999 Alarms .
- Explain error ration counters for example with the help of a flip chart. All calls are marked to the event side and unsuccessful calls to both sides. If a faulty side has reached its value first, alarm is on and both sides restart their counters.
Event side
Faulty side
For internal use
contain very detail info on all classes of faulty situations
can be made locally or at NMS
includes Notice, Disturbance, Alarm, Cancel
Alarm lamp panel
Red : Switch Alarm
For internal use
< ZA?
H ..... ALARM HISTORY HANDLING
L ..... LAMP PANEL HANDLING
P ..... ALARM PARAMETERS HANDLING
T ..... ALARM PRINTING HANDLING
Z; .... RETURN TO MAIN LEVEL <
THE USER CAN OPERATE AN ALARM SYSTEM BY THE ALARM USER INTERFACE
TIP: This slide can be left out. Customers may look at it from the terminals. This slide can be gone through by questioning technique.
CANCEL ALARMS N&E: (IN WHAT SITUATIONS??) Used when the system does not cancel automatically.
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
2. Unit failure information to CPA
3. Information about the faulty unit to Recovery System
4. NELAS informs user and sends alarms to the NMS
5. NELAS stores information on failure situation to Alarm History (WDU
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
MAIN LEVEL COMMAND <___>
F ..... ALARM FLOW HANDLING
H ..... ALARM HISTORY HANDLING
L ..... ALARM OUTPUT HANDLING
P ..... ALARM PARAMETERS HANDLING
T ..... ALARM PRINTING HANDLING
Z; .... RETURN TO MAIN LEVEL
THE USER CAN OPERATE AN ALARM SYSTEM BY THE ALARM USER INTERFACE
TIP: This slide can be left out. Customers may look at it from the terminals. This slide can be gone through by questioning technique.
CANCEL ALARMS N&E: (IN WHAT SITUATIONS??) Used when the system does not cancel automatically.
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
appears
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
Alarm Printing Handling <AT
Operator can define what alarm printout to be printed in a certain equipment
Printing time of active alarm can be set up to 3 times a day
Alarm History <AH
No matter which alarm is printed, all alarms will be stored in alarm history in a ring buffer system, except for those alarm that are block by <AB
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
Long printout format
** ALARM MXU-0
HMALAR OMU-1
** 3050 NO RESPONSE FROM PLUG-IN UNIT
Alarm printout formats
MEANING
The register has received a digit analysis result from the CMREAD program block
which makes the continuation of digit analysis unreasonable.
SUPPLEMENTARY INFORMATION FIELDS
2-13B subscriber number
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
0014 005E 00
* DISTUR BSU-2 1E085 IC2_SS
1153 ERROR IN DIAL ANALYSIS DATA
0030 AA 10 00 00 00 00 00 00 00 00 00 00
Printouts
1153
MEANING
The register has received a digit analysis result from the CMREAD program block
which makes the continuation of digit analysis unreasonable.
SUPPLEMENTARY INFORMATION FIELDS
2-13B subscriber number
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
Alarm Printout DX200
(0033) 2426 CHECKSUM ERROR IN FILE BLOCK
057E0000 FFFFFFFF
For internal use
** ALARM MXU-0
HMALAR OMU-1
For internal use
For internal use
Locating faulty functional unit
For internal use
1. Alarm blocking:
2. Alarm canceling:
3. Alarm history:
4. Operation instructions:
5. External alarm:
block incoming alarm & alarm printing to avoid excessive repetitive alarms, use "AB"
can by done by system or user (except external alarm that user must do it), use "AC"
- in WDU of OMU
- use "AH"
- extra info in alarm printout, e.g.. Who takes care of this alarm
- use "AO"
NO INFORMATION GOES OUTSIDE THE ALARM SYSTEM
NO RECOVERY
HISTORY
AH- MENU
RING BUFFER
OP. INSTRUCTIONS
For internal use
inform alarm system if faults found
each domain has its own internal supervision
Diagnostics
informs the operator
informs recovery if the unit may be taken back into use
Recovery System
maintains system performance by taking spare unit into use
Alarm System
notifies recovery if necessary
The recovery is responsible for eliminating the effects of faults on the operation of the system by using the hardware redundancy and restarting the functional units. For this purpose, it controls the working states of the functional units, the switchovers of units and different kinds of restarts.
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
Takes a redundant unit into use
Sets the faulty unit into test state
Operates automatically or by user
Recovery system
-operating states
2N : SPARE UNIT CAN SWITCH OVER TO THE WORKING STATE ANY TIME MARKER, GSW
N+1 REP: ONE SPARE UNIT
BSU, MOST SIGNALLING UNITS, CCSU
N+1 COMP: ONE MORE THAN NEEDED AND ALL WORKING
BDCU (X.25 CONNECTION)
recovery of the whole element
-only in total power lost or in commissioning
- first OMU then 2N units come up (more on the file administration)
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
Level of Recovery
Call handled by faulty subsystem will drop
All calls drop & charging data btw latest backup and restart will be gone
Situation
Switchover between faulty WO unit and SP unit
concern preprocessor restart and failure in functional unit of N+1 redundancy
By the way BTW
For internal use
Working (WO)
"normal" state of units doing some assigned task in the system
Spare (SP)
Blocked (BL)
Test (TE)
fault is detected -> unit does not participate in the operation of the system
diagnostics may be run
Transition (TR)
unit is moved from one slice to another (Trial configuration)
it will resume its previous state after the move
Blocked state is used when a unit with some configured resources needs to be taken off-line. The unit is given time to finish its current tasks and free the resources in a controlled fashion.
 
In Chorus computers the actors which are running in the TE-EX state may depend from the history of the unit. A chorus unit has two actor configurations, one for the test state and another for all other states. The test configuration is a subset of the "normal" configuration. If the unit enters the TE-EX state via restart (via the TE-RE state), the test configuration will be started, otherwise (i.e. transition directly from WO-EX to TE-EX) the "normal configuration continues to run.
 
Note, that knowing about TR state is suggested for maintenance programs only (those programs that control unit startup or manage Trial configuration). It is suggested to all other programs that they act same way as if unit’s state was SE.
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
State Model - Substates
unit has achieved full functionality
Restarting (RE) - WO, SP, BL, TE
unit startup sequence is in progress
Updating (UP) - SP
processes are updating data from active unit to achieve hot-standby
Idle (ID) - BL
Out of use (OU) - SE, TR
unit is separated but still part of a set of redundant units
No hardware (NH) - SE
unit is configured but not used, or not even physically present
The role of substates is to display dynamic phenomena – usually relating to startup tasks.
Note that the difference between SE-OU and SE-NH is more like a main state difference: SE-NH could conceptually be a separate main state as well, but the substate is used for historical reasons.
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
WO-EX
PIU LED display in this state
The WO-EX state is the normal state of an active unit. A unit in operation is in the restart state WO-RE when it is being restarted.
The working state SP-EX is the normal state of a spare unit. It can be changed into the WO-EX state at any time. In the warm-up state SP-UP, the spare unit warms up its data to match the data on the unit in operation. In the restart state SP-RE, the spare unit is in restart phase.
A unit in the TE-EX state is ready for testing. Now the system or the user may run diagnoses on the unit.
In an error condition, in general the functional unit is automatically set to the SE-OU state.
In the SE state, SE-OU substate means that the unit is found not to be in working condition, but the unit is still under control of the recovery system. If the unit is in SE-NH sub-state, this means that the functional unit is totally isolated from the system. This state SE-NH can only be set manually.
The correct state in non-redundant units is WO-EX. Therefore, all other states are considered to be “incorrect” in regard to the complete configuration of the network element. Non-redundant units have a blocked main state BL, which has three sub-states.
When a unit is in the BL-EX state, it still performs the operations not completed at the moment of blocking, but no new processes will be activated. In the idle state BL-ID, all the operations which were uncompleted at the moment of blocking have been executed, the unit has run empty. In the restart state BL-RE, the blocked unit is in restart phase.
When the traffic situation allows, the unit is set to test state.
A unit in the TE-EX state is ready for running diagnoses.
In the SE state for non-redundant units, the meaning of SE-OU and SE-NH substates are the same as for redundant units.
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
TE-RE Test state, restart
SE-NH Separated, no hardware
Usage of working states
An active unit is in the working state. A blocked unit does not accept any new tasks. A unit in the spare state is a spare unit ready for use at any time. A unit in the testing state is being tested and it is not performing its normal function. In case that automatic recovery action does not succeed and the fault diagnosis has detected a unit to be faulty, the functional unit in general is automatically set to the separated state, substate out-of-use. A unit in the separated state, substate no hardware, is totally separated from the rest of the system. After the fault has been repaired, for example by changing the plug-in unit, the user has to change the state of the unit to the TE-EX state with a state management command and run diagnosis.
Possible working states
Not all functional units do have all the states listed above. There are two different types of working states hierarchies, depending on the unit’s redundancy type. One is implemented for those units following 2N duplicated redundancy or N+1 replaceable redundancy principles. The other hierarchy is used by SN+ loadsharing redundant and by non-redundant units.
The working states of the functional units are determined as follows:
the SP state can only exist with duplicated 2N or N+1 replaceable redundancy
the BL state can only exist with loadsharing SN+ redundancy and with no redundancy
the SP-UP state can only exist if the unit has a spare unit warm-up
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
Switchover
Changing the state of the redundant unit in order to replace the faulty active unit.
WO
SP
TE
The training document at page 30
- Switchover is one of the most important concepts in the recovery system.
- There is a difference between automatic switchover & manual switchover
- automatic switchover:
-SP->WO.
- manual switchover:
- User is changing SP->WO. System automatically drops the WO->SP. User can also change WO->SP, then system will automatically upgrade SP->WO(This is the case with 2N redundancy)
- If the redundancy of the unit is N+1, it is only possible to do manual switchover by changing WO->SP manually. (WHY? Only one spare. If it is updated, it does not know which working unit it has to replace)
TIP: Switchover is explained in the training document under the chapter “operating states”
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
OMU-0 0000H 4002H WO-EX -
DMCU-0 > WO-EX -
For internal use
State change examples (faulty unit case):
WO-EX SP-EX TE-RE TE-EX SE-OU SE-NH (diagnostics found fault in TE-EX)
WO-EX SP-EX TE-RE TE-EX SP-RE SP-EX (diagnostics did not found fault in TE-EX)
EX
EX
OU
RE
RE
UP
EX
RE
NH
OU
SE
TE
SP
WO
TR
Unit is created to configuration
Unit is deleted from configuration
TR -> SP transition is possible when removing Trial configuration. The unit assumes a spare role if there already is an active unit present.
A unit goes to TE state only if a fault has been found and some recovery action made. E.g. a fault switchover:
unit 1 unit 2
TE-RE
TE-EX
When unit 1 has been moved to TE-EX state, diagnostics will be run.
After diagnostics
If there is no fault, unit can be raised to SP-EX via states TE-EX -> SP-RE -> SP-EX
Otherwise, unit will be deleted from configuration via states TE-EX -> SE->OU -> SE-NH
The operator can of course drop the unit to test as well.
Most state transitions cause the unit to be restarted as well. Only in the following transitions no restart is made:
WO-EX -> TE
SP-EX -> TE
BL-ID -> TE
WO-EX -> BL
BL-EX -> WO
BL-ID -> WO
For internal use
Unit is created to configuration
Unit is deleted from configuration
BL-EX -> BL-ID transition is the rresult of notice from SW responsible of resources of a unit in question: if no notice arrives unit stays in BL-EX -
Blocked state needed in order to free resources in controlled way
Controlled resource handling:
If one PQII processor gets faulty, unit has been moved from WO-EX to BL-EX
Resource manager checks when all resources has been released
Unit state can be changed from BL-EX to BL-ID
If unit contains for example 4 PQII processors, 3 PQII processors must be started before next unit gets permission to start. One PQII processor will be started as in background.
Rule: All child units may have stated not higher than parent processor (for example DSP processors can not have higher state than PQII processor in question.
If master PQII processors gets faulty, whole unit needs restart.
NOTE
SN+ redundancy requires still work in A4.2 before it may work properly.
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
? ... DISPLAY MENU
I: ... INTERROGATE UNIT STATE
U: ... RESTART UNIT
S: ... RESTART SYSTEM
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
? ..... DISPLAY MENU
U: ..... RESTART UNIT
S: ..... RESTART SYSTEM
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
SP-EX
WO-EX
TE-EX
SE-OU
SE-NH
BL-EX
WO-EX
TE-EX
SE-OU
SE-NH
Redundancy
Non-Redundancy
- Do not touch/change HW unless state is SE-NH
- FCD(force parameter) allows user to change unit state
w/o going through all the steps. It should not be used.
Command for each State Change: ZUSC
At this point the following should be explained:
- unit state changes step by step
- FCD parameter only to be used in unusual situations for example in change note installations
- If the unit is faulty it is in SE-OU state
SE-NH when changing the PIU
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
Summary of Recovery System
Performing a switchover of a faulty FU with a spare functional unit
Sending a fault locating request to diagnostics.
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
FAULT LOCATION SYSTEM
inform alarm system if faults found
each domain has its own internal supervision
Diagnostics
informs the operator
informs recovery if the unit may be taken back into use
Recovery System
maintains system performance by taking spare unit into use
Alarm System
For internal use
STARTS EITHER AUTOMATICALLY OR BY USER
UNIT MUST BE AT “TEST” STATE
To show the report on the screen, user must connect logical file "DIAGNOS" to the terminal
<IID::DIAGNOS; Interrogate who connects to "DIAGNOS"
<IIS::DIAGNOS::DEV=_____; Connect DIAGNOS to I/O DEV
Before going to Diagnostics, show the slide of four fields of maintenance. Show that the process is going towards diagnostics.
- Recovery system sends “fault location request” to the diagnostics
- Accuracy to locate faulty PIU varies from 70-95 %
- The main purpose of the diagnostics is to locate faulty PIU.
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
Start total/partial Diagnostic (must be total if SYSTEM starts diagnostic)
Study Diagnostic printout
Change PIU
Run total test on Unit and keep on changing until "Unit is OK"
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
D: ..... START I/O DEVICE TEST
H: ..... OUTPUT DIAGNOSTIC REPORT HISTORY
I: ..... INTERROGATE PARTIAL UNIT TESTS
L: ..... LIST FAULTY UNITS/PROCESSOR UNITS
Q; ..... INTERROGATE CURRENT TESTS
S: ..... STOP CURRENT TEST
Diagnostics user interface (DX200)
For internal use
D: ..... START I/O DEVICE TEST
H: ..... OUTPUT DIAGNOSTIC REPORT HISTORY
I: ..... INTERROGATE PARTIAL UNIT TESTS
L: ..... LIST FAULTY UNITS/PROCESSOR UNITS
Q; ..... INTERROGATE CURRENT TESTS
S: ..... STOP CURRENT TEST
Diagnostics user interface (IPA2800)
For internal use
- diagnostics name
- included to total or not (yes=included in total test)
- which PIU is tested
For internal use
For internal use
DIAGNOSIS REPORT LSU-1
TYPE INDEX SUBRACK TRACK
LSP_S 000 01E162 42
LST 000 01E162 47
- Explanations can be found from alarm reference manual
1. ALARM DESCRIPTIONS 3725
MEANING
A diagnostic print-out containing those plug-in units in which a failure has been detected.
In the diagnostic print-out, the plug-in unit type, place of the subrack in the exchange and
the track number have been listed.
SUPPLEMENTARY INFORMATION FIELDS
INSTRUCTIONS
Description of the report is in the document Diagnostics and Testing, Maintenance
Manual, 2.4, Functions in normal failure situations.
Replace the plug-in units suspected faulty.
CANCELLING
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
TYPE INDEX LOCATION
AL2S 0 1A3-0-15
END OF REPORT
IPA2800
- Explanations can be found from alarm reference manual
1. ALARM DESCRIPTIONS 3725
MEANING
A diagnostic print-out containing those plug-in units in which a failure has been detected.
In the diagnostic print-out, the plug-in unit type, place of the subrack in the exchange and
the track number have been listed.
SUPPLEMENTARY INFORMATION FIELDS
INSTRUCTIONS
Description of the report is in the document Diagnostics and Testing, Maintenance
Manual, 2.4, Functions in normal failure situations.
Replace the plug-in units suspected faulty.
CANCELLING
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
The main purpose of the fault location system is to locate
the faulty plug-in unit
Summary of Fault Location System
Device and Action
Daily
Daily
Daily
to the removable data storage device
Daily
Weekly
Weekly
Weekly
Weekly
Six monthly