Ericsson ASB 150 02 Description

1(42)

Datum/Date Rev

Dokumentnr/DocumentnrUppgjord/Prepared

Dokansv/Godkänd - Doc respons/Approved Kontr/Checked Tillhör/Referens-File/Reference

1999-07-15 F

1545-ASB 150 02 Uen

FAULT TRACING DESCRIPTION

Faktaansvarig - Subject responsible

SEA/EBBMP Stangelberger

SEA/EBBMP ASB 150 02

SEA/EBBS

ASB 150 02

FAULT TRACING

Contents Page

1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1.1 Tools for fault locating. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1.2 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1.3 Replacement of printed board assemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

1.4 Deﬁnitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2 Fault locating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2.1 General checks on start and completion of service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2.2 Indication of LEDs on board(s). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

2.3 Flow chart: No possibility to make calls in PBX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

2.4 Flow chart: Individual board not working . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

2.5 Flow chart: Individual does not work at all . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2.6 Flow chart: Digital trunk does not work at all . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

2.7 Flow chart: Part of individual function not working . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

2.8 Flow chart: Individual facility does not work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

2.9 Flow chart: Individual facility works intermittently. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

2.10 Flow chart: Individual does not work for certain facilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

2.11 Flow chart: Transmission faults. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

2.12 Flow chart: PBX is unstable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

2.13 Flow Charts for Cordless . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

3 Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

3.1 Check on telephone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

3.2 Check RASC connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

3.3 Check CSM connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

3.4 Check on service display DT 288, DT 360, DT 368 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

3.5 Check on conﬁguration data for trunks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

(continued)

1545.fm

Database reference

2(42)

Datum/Date Rev

Dokumentnr/DocumentnrUppgjord/Prepared

Dokansv/Godkänd - Doc respons/Approved Kontr/Checked Tillhör/Referens-File/Reference

1999-07-15 F

1545-ASB 150 02 Uen

FAULT TRACING DESCRIPTION

Faktaansvarig - Subject responsible

3.6 Voltage measurements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

3.7 Check on power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

3.8 System reset. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

3.9 Check on line network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

3.10 Check on programmable parameters for facilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

3.11 Check on resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

3.12 Fault checks / correction of intermittent faults. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

3.13 Fault reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

3.14 Update of board positions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

3.15 Translation and veriﬁcation of revision states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

4 Resistance of temperature sensor at different temperatures . . . . . . . . . . . . . . . . . . . . . . . . . 42

3(42)

Datum/Date Rev

Dokumentnr/DocumentnrUppgjord/Prepared

Dokansv/Godkänd - Doc respons/Approved Kontr/Checked Tillhör/Referens-File/Reference

1999-07-15 F

1545-ASB 150 02 Uen

FAULT TRACING DESCRIPTION

Faktaansvarig - Subject responsible

1 General

These fault locating instructions shall serve as a guide for servicing an ASB 150 02 telephone exchange

(PBX). This document presupposes that all installation and start-of-operation instructions have been ad-

hered to. This document covers only such faults (errors) as equipment malfunctions or some incorrect

programming. When beginning start by classifying the fault type (see page 8).

Generally, when servicing a PBX a hardware fault can only be remedied by replacing the faulty hard-

ware on site and the faulty unit(s) are to be returned to the supplier with a claim for compensation. No

repairs are to be done in the ﬁeld.

The PBX has operation and maintenance programs installed which can be accessed via the PC-pro-

gram RASC and Cordless System Manager software (CSM). These programs run on a PC that can be

situated either in a remote service centre or locally next to the PBX.

The service personnel shall be familiar with the system, in particular regarding RASC and CSM with

their possibilities, as RASC and CSM are the best fault locating aids.

1.1 Tools for fault locating

Fault locating from an operation and maintenance (O&M) centre requires a PC with RASC and CSM

installed and a Hayes-compatible V.32bis modem.

Fault locating on site requires a (portable) PC with RASC and a V.24-cable connected to a free V.24-

port. Additionally required tools are: a voltmeter (DVM), a system telephone, board extractor and a set of

screwdrivers. As the boards are sensitive to electrostatic discharges please use a grounding wrist strap

correctly connected to ground when handling the boards.

The Cordless System Manager software contains functions for Cordless System part regarding

initialization, system maintenance and updating, system fault ﬁnding and repair. As RASC cannot detect

IC-LU boards installed in the system it is advisable to locate these boards to the right of the IC-CU_

board.

The Cordless System Statistics is an extension to the Cordless System Manager. It collects and

interprets statistical information from the Cordless System. It gives an overview of the trafﬁc load of the

total Cordless System, load per Base Station or per portable telephone. Important data of telephone

calls are stored, for example the duration of calls, the number of hand over and errors like failed calls or

portable telephones that could not be reached.

The Cordless System Manager software has a menu driven user interface. Separate text ﬁles permit

you to translate and obtain the menus in the desired language.

1.2 References

1 B/XU 93:027 Uen.

SAR-routine for Fault reporting and fault handling

2 EN/LZB BS 103 1197 RASC

3 LZY NB 201 01 /n Cordless System Manager Software

4 Service advice: Status of R-states

4(42)

Datum/Date Rev

Dokumentnr/DocumentnrUppgjord/Prepared

Dokansv/Godkänd - Doc respons/Approved Kontr/Checked Tillhör/Referens-File/Reference

1999-07-15 F

1545-ASB 150 02 Uen

FAULT TRACING DESCRIPTION

Faktaansvarig - Subject responsible

1.3 Replacement of printed board assemblies

Before handling printed board assemblies (PBAs) service personnel shall always connect themselves to

ground to prevent damage caused by static discharges.

Older system versions of the PBX must be restarted (e.g. switched OFF and ON) after the replacement

has taken place. As of BP 50/250 Version 3.1 (ASB15002 R10) boards can be replaced during power

on. The board can be exchanged during operation by a board with the same type and number of individ-

uals. Prior to removing the board, it can be disabled for trafﬁc (by RASC) and the new board is put in op-

eration without the need of restarting the exchange. A new board can be inserted in a free slot and put

in operation. When replacing boards be careful when inserting the board in the cabinet as not to dam-

age the backplane connector (e.g. bending pins due to misalignment) or to cause a short circuit on the

layer side of neighbouring boards e.g. by elevated components such as transformers, capacitors.

Note that the PBX will generate warnings to this effect and is therefore advisable to read the relevant

warning log. Also bear in mind that restarts normally generate the alarm and if automatic alarm trans-

mission is active, alarms will be generated to the relevant alarm centre. This can be avoided by

re-classifying the restart codes or by deactivating the alarm transmission.

The changes done to avoid alarms from being issued while servicing shall be reset after ﬁnal restart has

been effected and the system handed over to the customer.

The procedure for replacement of boards is described below:

1 Transfer the (if any) warning log to a ﬁle in RASC if possible for later evaluation and appropriate

measures.

Make a printout of the warning log.

2 Deactivate active alarm.

3 Save conﬁguration data on ﬁle in RASC if possible when CPU-D is to be replaced or with the aid of the

Cordless System Manager if the failure concerns the IC-CU_ or IC-LU.

4 Connect portable equipment LYA 30101 to protect against static electricity.

5 Replace faulty PBA.

6 Restart PBX manually (switch power off and on) or via RASC. If the PBX comprises several cabinets the

cabinet containing the CPU-D_ shall be switched ON as last.

7 Empty the warning log.

8 Reset active alarm if this is required.

9 When replacing the CPU-D_ perform a cold-start in the PBX and update it with the saved conﬁguration

data from RASC in order to restart all programmable data.

Boards with Electrostatic Sensitive Devices (ESD) are marked with a sign.

In the interest of quality and reliability of the system boards, always handle static sensitive boards

Some of the beneﬁts of

ESD protection are:

-less failures/service calls

-lower maintenance costs

-higher customer satisfaction

Use portable equipment LYA 30101

as a protection against electrostatic

discharges.

with special care. Always use a wrist strap connected to a low resistance ground e.g. provided

on the cabinet.

5(42)

Datum/Date Rev

Dokumentnr/DocumentnrUppgjord/Prepared

Dokansv/Godkänd - Doc respons/Approved Kontr/Checked Tillhör/Referens-File/Reference

1999-07-15 F

1545-ASB 150 02 Uen

FAULT TRACING DESCRIPTION

Faktaansvarig - Subject responsible

1.4 Deﬁnitions

Blocked Printed Board Assembly (PBA)

A blocked PBA is normally unable to process trafﬁc. The state of the board is indicated on the board's

LEDs (see under section " Indication of LEDs on board(s)" on page 10) and read outs of revision (R)-

states is made via RASC where the board position is indicated (marked).

See user guide for RASC-menu Maintenance-HW/SW-RP.

Blocked directory number

An individual whose directory number has been blocked cannot generate nor receive trafﬁc. A blocked

directory is not indicated on the LEDs of the device board. See RASC-menu CONFIGURATION.

Cold start

Cold start denotes a restart of the PBX, whereby all programmed data is erased and replaced by default

values initially assigned e.g. factory).

Cold start is performed by placing a strap in the socket provided for this purpose on the front of CPU-D_

(see under section " Indication of LEDs on board(s)" on page 10) and thereafter switching off and on the

DC supply voltage to the cabinet containing CPU-D_. Instead of switching the PBX OFF and ON again

two pins are available in connector ﬁeld 2 on the CPU-D_ which can be short circuited by a plug to in-

voke restart (refer to

section 4.8).

CSM

The Cordless System Manager is a maintenance and conﬁguration software program for the Integrated

Cordless System. A PC with CSM software installed can connect directly to a CPU-D4 on a mainte-

nance port or remotely via internal modem (similar as with RASC) but as in the past it is also possible to

connect CSM directly to the IC-CU_ or via an external modem.

CPU

The central processor unit and its programs.

Device

The PBX can be considered as an interworking unit of function blocks. Such a function block is some-

times called a "device".

Examples of devices are: switch, tone sender, extension, trunk, MFC-register and voice memory.

The placing of the devices on PBAs is arbitrary.

Facility

The functions of a telephone exchange are called facilities. Often a facility consists of several connection

cases. A connection case is initiated by means of a certain procedure from a telephone or other unit

(equipment) connected to the exchange.

Examples of facilities are: internal call, external call, inquiry, transfer, intrusion, conference, sector pag-

ing, various types of diversion, programming of function keys and abbreviated numbers.

Hot swapping

A board of the PBX can be exchanged during operation by a board of the same type and with the same

number of individuals. The board can be disabled for trafﬁc (by RASC) prior unplugging it and the new

board is put in operation without the need of restarting the exchange. A new board can be inserted in a

free slot and put in operation.

6(42)

Datum/Date Rev

Dokumentnr/DocumentnrUppgjord/Prepared

Dokansv/Godkänd - Doc respons/Approved Kontr/Checked Tillhör/Referens-File/Reference

1999-07-15 F

1545-ASB 150 02 Uen

FAULT TRACING DESCRIPTION

Faktaansvarig - Subject responsible

Individual

An individual member (unit) of a group. The PBX possesses, among others, groups of extensions where

an

individual

can connect a telephone.

On analogue trunks each individual can connect (is connected) to a trunk.

On digital trunks several individuals share a single line (cable/interface).

Installed PBA

A PBA is correctly installed if it is physically mounted in a board position stipulated in the appropriate in-

stallation instructions. A correctly installed PBA is a prerequisite for trafﬁc.

See the guide text for RASC-menu MAINTENANCE-HW/SP-RP.

The LEDs on the board identify different board conditions. An explanation of the conditions is given un-

der FAULT LOCATING.

Line network with stubs:

Extension line with extra jacks in the form of a star network. See ﬁgure below.

Line signalling diagram with line test

Several line signalling diagrams for trunks include a line test that is done for both outgoing and incoming

calls. These tests are described in RASC, RASC-menu CONFIGURATION-TRUNKS.

Link supervision

Digital trunks are supervised by the exchange and the state conditions, errors on the digital link to the

public exchange are monitored. The monitoring data can be read out via RASC-menu maintenance-sys-

tem-link supervisor and stored in a ﬁle or printed out.

Minimum system size

A minimum system comprises one cabinet equipped a CPU-D_ and either one ELU-D, ELU-C or ELU-

A.

Power supply

Transformers, battery chargers, batteries and appurtenant cables are all included in the concept "Power

supply".

Programmable parameters

The PBX possesses a considerable number of programmable parameters, which help O&M-personnel

to adapt the function of the PBX to customer requirements. The majority of facilities and individuals can

be programmed. See RASC-menu CONFIGURATION and the Cordless System Manager Software.

PBX

Although with appropriate termination this

connected to the BTU-B.

This conﬁguration must never be

Note:

used for digital telephone extension lines

connected to boards like ELU-D and ELU-C.

is a valid conﬁguration for the ISDN S-interface

7(42)

Datum/Date Rev

Dokumentnr/DocumentnrUppgjord/Prepared

Dokansv/Godkänd - Doc respons/Approved Kontr/Checked Tillhör/Referens-File/Reference

1999-07-15 F

1545-ASB 150 02 Uen

FAULT TRACING DESCRIPTION

Faktaansvarig - Subject responsible

Recommended measure

Each warning code is described in RASC and recommended measures are offered.

See item

Warning

below.

Remote SW upgrading

The system software can be downloaded from a remote maintenance centre. Setting a certain time and

date automatically loads the new software into the system non volatile memory and re-starts the ex-

change.

RP (Regional Processor)

The control system of the PBX is handled by a central processor and a number of regional processors.

A typical task for an RP is to handle the hardware check on the individuals on a PBA.

Update board position

The database contains, among other things, relevant data for all board (PBA) positions in the PBX. The

database contains also details about the type of PBA that should be installed.

The update means that the database is adapted to physical reality. An update is required in conjunction

with a conﬁguration change of the PBX, e.g. on expansion with new PBAs, on removal of PBAs and

when a PBA is replaced by a different type of PBA.

See RASC-menu Maintenance-HW/SW-RP.

Warm start

Restart of a PBX with no cold start strap installed. This is the normal procedure in conjunction with pow-

er-up or controlled restart via RASC-menu Maintenance-log-reset.

All programmed data is retained.

Warning

The control system of the PBX is structured so that warnings are generated when abnormal situations

occur. The warnings can be read out by O&M-personnel and

also personnel who have access to the

control system's source code.

Warnings that are directed to O&M-personnel are complemented with a recommended measure.

Warnings without recommended measures shall be interpreted by persons with access to the control

system's source code.

8(42)

Datum/Date Rev

Dokumentnr/DocumentnrUppgjord/Prepared

Dokansv/Godkänd - Doc respons/Approved Kontr/Checked Tillhör/Referens-File/Reference

1999-07-15 F

1545-ASB 150 02 Uen

FAULT TRACING DESCRIPTION

Faktaansvarig - Subject responsible

2 Fault locating

2.1 General checks on start and completion of service

Start by identifying the type of fault by collecting as much information about the fault as possible, from

the relevant customer, then (if possible) connect RASC and check the conﬁguration of the PBX with re-

gard to revision states (see point 4.15, Translation and veriﬁcation of revision states) as soon as this is

possible.

The majority of faults can probably be eliminated from the O&M-centre by means of reprogramming or

via telephone contact with the respective customer (operational faults).

Consider to which one of the following main fault categories best describes your fault:

Use the following ﬂow charts describing a methodical path for checks and tests to help locate and

eliminate the fault. When the ﬂow charts lead to a possible cause, this is indicated by a statement giving

the name of the defective part or the cause of the problem, e.g. a defective BTU-_ board is indicated by

the statement `BTU-_ board defect'. When there are more possible items, they are listed in order of

decreasing probability.

Number TYPE OF FAULT Go to:

2.2 Indication of LEDs on board(s) page 10

2.3 No call procedures possible in the PBX page 15

2.4 Individual board not working page 16

2.5 A single individual does not work at all, e.g. an extension is "dead".

The individual is not able to either initiate or receive calls

page 17

2.6 Digital trunk (BTU-D) does not work at all page 19

2.7 Individual malfunctions partly, intermittent faults, e.g. one connection case is successful

and another fails. The fault can be traced to an individual

page 20

2.8 A certain facility never functions. A certain facility is inaccessible, e.g. intrusion is never

possible

page 21

2.9 A certain facility functions intermittently, that is a certain connection case succeeds on one

occasion, not on another, and where the fault cannot be traced to an individual

page 22

2.10 An individual has no access to a certain facility page 22

2.11 Transmission fault (one way speech, line scratching, etc.) page 23

2.12 PBX unstable (repeated restarts) page 24

2.13 Faults related to Cordless page 25

9(42)

Datum/Date Rev

Dokumentnr/DocumentnrUppgjord/Prepared

Dokansv/Godkänd - Doc respons/Approved Kontr/Checked Tillhör/Referens-File/Reference

1999-07-15 F

1545-ASB 150 02 Uen

FAULT TRACING DESCRIPTION

Faktaansvarig - Subject responsible

Description of ﬂow chart symbols

Question

Instruction

References

Flow

Question?

1

2

4

3

This symbol contains a question with two or three possible

answers being YES (Y), NO (N) or text.

Inputs are points 1 or 4 and outputs are points 2,3 or 4.

This symbol contains an instruction

for the maintenance engineer.

This symbol is used as: starting point for a procedure (e.g. START),

as a reference to another ﬂowchart, to end a procedure (END).

This symbol is used as a reference point within a ﬂowchart. This

can be to a part of the ﬂowchart on another page (e.g. B or C) or at

a part of the ﬂowchart on the same page (e.g.1).

Lines indicate the normal ﬂow. The normal ﬂow is always "down"

Arrows are used to indicate ﬂows going "up" or left.

and "to the right" and in exceptional cases "to the left".

10(42)

Datum/Date Rev

Dokumentnr/DocumentnrUppgjord/Prepared

Dokansv/Godkänd - Doc respons/Approved Kontr/Checked Tillhör/Referens-File/Reference

1999-07-15 F

1545-ASB 150 02 Uen

FAULT TRACING DESCRIPTION

Faktaansvarig - Subject responsible

2.2 Indication of LEDs on board(s)

The front edge of all PBAs in the PBX are equipped with LEDs of different colours. Their purpose and

signalling cadence is described in the following. On system restart all LEDs are ON and go OFF during

start-up sequence. Depending on their function the LEDs are in different positions on the front edge.

CPU-D_

RPs on BTU-_,ELU-_, IC-CU etc.

Connection ﬁeld 2

Connection ﬁeld 4

Connection ﬁeld 6

1st pair (generally RP)

LEDs controlled

by CP

Yellow LED ﬂashes in different ca-

dences during start sequence and is

off during normal operating.

by relevant RP

cold start strap

Position for

2nd pair (e.g. DSPs

3rd pair

4th pair

Not mounted

on all boards

on BTU-D or REG)

Red LED is lit if CP is restarted

The LED can be ONfor up to 2 min. during

upgrading or only 1 to 5 seconds during

start-up conditions.

Go to:

c

Yellow LED ﬂashes in different cadences

during start sequence and is off during

normal operation go to page 11.

Green LED that is directly connected to

alarm log e.g.if warnings occur these war-

ning codes are stored in the warning log

and this LED is turned on go to page 11.

Red LED is ON if cold start strap

(located below) is inserted go to page 11.

Red LED lights up during power on se-

quence . Check if PROMS are

placed and if no yellow and green LEDs

ﬂashes. For LED ﬂashing procedures

during upgrading refer to MAINTENANCE

INSTRUCTION (1541-ASB 150 02).

Go to:

a

on CPU-D

cold start strap

Position for

on CPU-D_

Yellow and green LEDs indicating start,

faults or active ports. During remote up-

grading the number of ﬂashes indicate

which FLASH program memory is being

re-written go to page 11

For LED ﬂashing procedures during up-

grading refer to MAINTENANCE

INSTRUCTION (1541-ASB 150 02).

For LEDs on Integrated Cordless boards

go to page 11

11(42)

Datum/Date Rev

Dokumentnr/DocumentnrUppgjord/Prepared

Dokansv/Godkänd - Doc respons/Approved Kontr/Checked Tillhör/Referens-File/Reference

1999-07-15 F

1545-ASB 150 02 Uen

FAULT TRACING DESCRIPTION

Faktaansvarig - Subject responsible

2.2.1 LEDs on the CPU-D

2.2.2 LEDs on the IC-CU, IC-LU

LED Condition Correction

LEDs in

connection

ﬁeld 2

red RP disconnects PCM

bus and signalling

interface from back

plane

This can occur if the CP on the CPU is restarted or a board failure is

detected by the RP. Check if it concerns just one or more board(s). A

watchdog reset on the board could cause a board restart. System

supervision will invoke a system restart if major faults occur. If LED is

continuouslyONcheck iftheyellow and greenLEDs ﬂashotherwise theRP

is not working

yellow This LED indicates

boardstart-up or if the

board (individual) is

blocked.

This condition is normal for a start-up sequence indicating initialisation or

running self test. If this LED is ON during operation, this indicates blocking

of one or more individual(s). The proper action is to check the wiring and if

the connected equipment is operational (check it’s alarm indication)

green Port is active This indicates normal system operation and one port is active e.g. RASC

LEDs in

connection

ﬁeld 4

red CP is reset This occurs during remote upgrading of the SW or if the watchdog detects

a fault. If LED is continuously on the FLASH PROMS could be re-written

(refer to RP LED conditions)

yellow Flashes during start-

up of CP

This LED ﬂashes during start-up of the CP and is OFF during normal

operation

green Alarm log indication If this LED is ON, check the logged errors, save them to disk and delete

them in the log. Check in which intervals the system logs errors and if

possible correct the cause

LEDs in

connection

ﬁeld 6

red Cold start strap active This LED turns on if the cold start strap below is inserted. This is a warning

that if this strap is not removed during operation the system will start with

initial values on restart. This occurs even if the mains fails intermittently! All

customer data will be lost in this case.

LED Correction

red yellow green

ON Communication to CPU-D_ terminated. Board failure is detected by the RP.

OFF ON ON PROM error (invalid checksum)

OFF ON Flash (4 Hz) RAM error

OFF ON 0,5s ON/4,5s OFF FPGAs not loaded

OFF ON 0,5s ON/0,5s OFF/

0,5s ON/3,5s OFF

EPIC initialization fault

OFF ON 0,5s ON/0,5s OFF/

0,5s ON/0,5s OFF/

0,5s ON/2,5s OFF

Initialization fault of process data

OFF ON 1s ON/1s OFF Invalid FECU connected

red SPU LED on

(see Installation

Instruction for

details)

This LED ﬂashes if the board’s SPU RP detects a fault. To correct the fault

check entries in the CSM and follow suitable solution given.

Flashing -> CPU fail, ON steady -> warning entries not read.

red CLU LED on

(see Installation

Instruction for

details)

This LED is turned on if the board’s CLU RP detects a fault and/or if a base

station is not initialized. Correct the fault, check entries in the CSM and follow

suitable solution given.

12(42)

Datum/Date Rev

Dokumentnr/DocumentnrUppgjord/Prepared

Dokansv/Godkänd - Doc respons/Approved Kontr/Checked Tillhör/Referens-File/Reference

1999-07-15 F

1545-ASB 150 02 Uen

FAULT TRACING DESCRIPTION

Faktaansvarig - Subject responsible

2.2.3 LEDs on other Boards

LED Condition Correction

LEDs in

connection

ﬁeld 2

(upper

part)

red RP disconnects PCM

bus and signalling

interface from back

plane

This can occur if the CP on the CPU is restarted or a board failure is

detected by the RP. Check if it concerns just one or more board(s). A

watchdog reset on the board could cause a board restart. System

supervision will invoke a system restart if major faults occur. If LED is

continuously ON check if the yellow and green LEDs ﬂash, otherwise

the RP is not working.

yellow This LED indicates if

the board is in start-up

procedure or if the

board (individual) is

blocked.

This condition is normal for a start-up sequence indicating initialisation

or running self test. If this LED is ON during operation, this indicates

blocking of one or more individual(s). The proper action is to check the

wiring and if the connected equipment is operational (check it’s alarm

indication).

green Individual is active This indicates normal system operation and at least one e.g. extension

(individual) is active on the board.

LEDs in

connection

ﬁeld 2

(lower

part)

yellow Register is blocked This indicates that the register function on the board is blocked e.g. on

BTU-D or VMU-HD.

green Register is active This indicates normal system operation. This register function is active

on the board e.g. on BTU-D or VMU-HD.

13(42)

Datum/Date Rev

Dokumentnr/DocumentnrUppgjord/Prepared

Dokansv/Godkänd - Doc respons/Approved Kontr/Checked Tillhör/Referens-File/Reference

1999-07-15 F

1545-ASB 150 02 Uen

FAULT TRACING DESCRIPTION

Faktaansvarig - Subject responsible

2.2.4 LED description during start-up

Yellow Green

State Function

Normal start

sequence

LEDs

1 (power up) ON OFF RESTART Lights up immediately for about 20 seconds

ON ON PROM-fault Start up is interrupted if a fault is discovered during

self test.

ON R-FL

1)

RAM-fault

S-FL

2)

OFF WAIT

Entered after restart following fault-free self test

and relevant RP is initiated. Waits for start order

from CPU.

R-FL

1)

OFF START

Entered in state wait for receipt of start order from

CU. RP reports data to CPU, e.g. type of board

ON OFF BLOCKED

Occurs when database does not match with

reported data from RP or

if at least one individual is blocked

4)

R-FL

1)

R-FL

1)

HD-fault

A-FL

3)

A-FL

3)

OFF OFF NORMAL

OFF ON TRAFFIC Trafﬁc on least one individual

Normal idle state that is entered after PBX has been

started. No trafﬁc exists on relevant board/device

Hard disk is missing/not installed

DSP-fault VMU-HD only: DSP not loaded

2

3

4 (operation)

FAULT

Start

sequence

aborted

Condition in case of database mismatch

R-FL

1)

OFF

Data base-

fault

1) Rapid Flash (Frequency=4Hz).

2) Slow Flash (100 ms ON and 900 ms OFF).

4) Applies only for analogue and digital trunks. Individually blocked trunks are

indicated in conﬁguration data and not in RASC-menu Maintenance-HW/SW-RP.

3) Alternate Rapid Flash (Frequency=4Hz). Green and yellow LEDs toggle.

14(42)

Datum/Date Rev

Dokumentnr/DocumentnrUppgjord/Prepared

Dokansv/Godkänd - Doc respons/Approved Kontr/Checked Tillhör/Referens-File/Reference

1999-07-15 F

1545-ASB 150 02 Uen

FAULT TRACING DESCRIPTION

Faktaansvarig - Subject responsible

LEDs on BTU-D

Prom test OK

(1 sec)

RPNORMAL

OFF

Load DSP MFC

(20 sec)

ON

OFF

ON

OFF

Prom test

ERROR

OFF

ON

OFF

ON

RP-GREEN

LED

RP-YELLOW

DSP-YELLOW

DSP-GREEN

OFF

FL-OFF

RP-GREEN

LED

RP-YELLOW

DSP-YELLOW

DSP-GREEN

FL-STARTUP

FL-OFF

OFF

FL-OFF

RPSTARTUP

FL-OFF

OFF

FL-OFF

RPOFF

RPNORMAL

OFF

RP-GREEN

LED

RP-YELLOW

DSP-YELLOW

DSP-GREEN

FL-STARTUP

OFF

FL-OFF

OFF

AFTER DSP LOAD = “OK”

AFTER DSP LOAD = “ERROR”

FLASH TIMES:

FL-OFF

FL-STARTUP

Load DSP MFE

(20 sec)

ON

OFF

ON

= ON 100 msec / OFF 900 msec ﬂash

= 4 Hz ﬂash

RPSTARTUP RPOFF

15(42)

Datum/Date Rev

Dokumentnr/DocumentnrUppgjord/Prepared

Dokansv/Godkänd - Doc respons/Approved Kontr/Checked Tillhör/Referens-File/Reference

1999-07-15 F

1545-ASB 150 02 Uen

FAULT TRACING DESCRIPTION

Faktaansvarig - Subject responsible

2.3 Flow chart: No possibility to make calls in PBX

Remove board after board in

cabinet and measure voltages

on the backplane. Replace

board causing the wrong volta-

ge(s). If the boards are not the

cause replace the back plane.

Verify that the exchange is

supplied with power. Check

48VDC/36VAC supply, the

cabling and if the voltages

are present on the back-

plane. (see point 4.7).

Remove front cover

on cabinet containing

the CPU-D.

Insert cold start strap andremoveit

immediately. Does the red LED

(above cold startstrap) light indica-

ting a cold start and extinguishes

when strap is removed.

Check all revision

states

(see point 4.15).

Check available (free) re-

sources (see point 4.11).

Update to latest

revision state.

Configure mini-PBX

comprising one cabinet

and CPU-D.

Connect RASC.

Continue by increasing size

of PBX with one device

board at a time. Replace

boards that malfunction.

Replace CPU-D

and restart PBX.

START

Y

N

All LEDs

extinguished?

Y

N

Correct?

Connect to RASC.

Verify proper commu-

nication parameters

Y

N

Connection

successful?

Y

N

Power ok?

AA

Y

N

Valid

states?

revision

N

Resources

available?

Y

N

Correct?

Y

N

Fault

remains?

AA

N

Fault

remains?

AA

Restart PBX

AA

= Go to " Completion of service" on page 31

1

Y

1

Y

1

16(42)

Datum/Date Rev

Dokumentnr/DocumentnrUppgjord/Prepared

Dokansv/Godkänd - Doc respons/Approved Kontr/Checked Tillhör/Referens-File/Reference

1999-07-15 F

1545-ASB 150 02 Uen

FAULT TRACING DESCRIPTION

Faktaansvarig - Subject responsible

2.4 Flow chart: Individual board not working

START

Messages logged

Y

N

Remove boardand verifythat all

ICs (EPROMS) are properly

mounted on theirholders,i.e. no

bent legs giving poor contact.

from faulty

board?

Y

N

Revision

Translate message to

revision state of board?

state ok?

Y

N

Mounted

correctly?

Replace board

(see point 1.3).

Connect RASC and read

hardware revision states

(see point 4.15).

Board blocked?

(see point 1.4)

Update board posi-

tion (see point 4.14).

Swap board and restart PBX.

Send the board for swap re-

pair and include fault report

Board installed?

see point 1.4)?

Restart PBX

point 3.1)

Board starts? (see

Correct mounting fault

and reinsert board

Y

N

Board blocked?

see point 1.4)?

Y

N

Y

N

AA

= Go to " Completion of service" on page 31

Y

N

17(42)

Datum/Date Rev

Dokumentnr/DocumentnrUppgjord/Prepared

Dokansv/Godkänd - Doc respons/Approved Kontr/Checked Tillhör/Referens-File/Reference

1999-07-15 F

1545-ASB 150 02 Uen

FAULT TRACING DESCRIPTION

Faktaansvarig - Subject responsible

2.5 Flow chart: Individual does not work at all

START

Extension?

Y

Telephone functions

at another

Y

N

Locate faulty individual

and connect RASC

Trunk?

Y

Check, repair or replace

telephone (see point 4.1)

line position?

Check

MDF and

Cable breaks?

Y

N

Intermittent

fault?

Y

N

Analog/digital?

analog

digital

AE

AA

Line signalling

Y

N

diagram agrees with

line test?

Check with anaolg test

equipment in MDF for dial

tone from public exchange

Fault in public ex-

change.Report fault

to relevant instance.

Another type?

Y

AF

Replace board.

Dial tone?

Y

Fault remains?

Y

N

(see point 4.9)

cabling for breaks.

Correct line

Fault remains?

Y

N

running

AA

Report fault

(see point 4.13)

Y

N

log related

Warning

to fault?

code in warning

Y

N

(see point 4.9)

Check

Correct?

MDF and cabling

Correct line

Fault remains?

Y

N

running

AA

Fault in public ex-

change.Report fault

to relevant instance.

N

AA

= Go to " Completion of service" on page 31

Go to

page 14

Go to

page 13

2

N

AA

Report fault

(see point 4.13)

18(42)

Datum/Date Rev

Dokumentnr/DocumentnrUppgjord/Prepared

Dokansv/Godkänd - Doc respons/Approved Kontr/Checked Tillhör/Referens-File/Reference

1999-07-15 F

1545-ASB 150 02 Uen

FAULT TRACING DESCRIPTION

Faktaansvarig - Subject responsible

V.24

Y

Is there an

entry due to the

fault?

Y

N

Proceed in identifying the

faulty individual

AA

Temperature

Y

sensor

Music

Y

source

Other

Y

type

Measurement

value agrees with table

(see point 5)?

Y

N

Disconnect temperature

sensor and measure

resistance of sensor.

Replace temperature

sensor.

Follow recom-

mended measure.

Connect RASC and

check warning log.

Fault remains?

Y

Correct?

Check cabling

(see point 4.9) use

data tester.

Y

N

Correct cabling

Check cabling

(see point 4.9)

Correct?

Y

N

Has the

PBX been re-

Fault remains?

Y

ming? If not then restart.

N

started after program-

Replace board

(see point 1.3).

Fault remains?

Y

N

Report fault

(see point 4.13)

N

AA

= Go to " Completion of service" on page 31

AF

From

page 12

N

19(42)

Datum/Date Rev

Dokumentnr/DocumentnrUppgjord/Prepared

Dokansv/Godkänd - Doc respons/Approved Kontr/Checked Tillhör/Referens-File/Reference

1999-07-15 F

1545-ASB 150 02 Uen

FAULT TRACING DESCRIPTION

Faktaansvarig - Subject responsible

2.6 Flow chart: Digital trunk does not work at all

Correct programming

Is the

Y

Check in RASC the link

supervision if synchroni-

sation is possible.

Warnings

Y

logged for the

card functions?

Did this

Y

board work before?

Connect to RASC.

ﬁrmware?

Is the

hardware setup

ok? Correct jumper

settings and/or

Y

Correct hard-

ware setups

N

Did this

Y

board work before?

Swap board.

Y

Does it function

correctly?

Send to swap repair

with fault report

network/line

signalling selection

link correct?

N

Is the

Y

ISDN termi-

nation selection

correct?

N

Change selection

Are the

Y

services used

in the PBX subscri-

bed correctly?

N

Change termination

Are the

Y

services used

in the PBX subscri-

bed correctly?

N

If possible collectthesignalling

trace and forward it with the

fault report. (see point 4.13)

AA

= Go to " Completion of service" on page 31

AE

From

page 12

1

N

20(42)

Datum/Date Rev

Dokumentnr/DocumentnrUppgjord/Prepared

Dokansv/Godkänd - Doc respons/Approved Kontr/Checked Tillhör/Referens-File/Reference

1999-07-15 F

1545-ASB 150 02 Uen

FAULT TRACING DESCRIPTION

Faktaansvarig - Subject responsible

2.7 Flow chart: Part of individual function not working

START

Correct?

Verify

Check

line running

Fault remains?

Y

Digital extension?

Y

Connect to RASC

and read warning log.

Warnings

Y

logged resulting

from the

fault?

Verify which individu-

al causes the fault

Trunk?

Other type?

Y

proper wiring

(twisted pair) with no

stubs (extra jack).

Correct wiring. Discon-

nect stubs from old net.

Correct?

Verify

conﬁguration data

for trunks (see point 4.5)

Fault eliminated?

Y

(see point 4.9)

Correct

programming

Replace board

(see point 4.13)

Y

AA

(see point 4.12)

Follow recommended

measure (see point 4.12).

Y

N

AA

= Go to " Completion of service" on page 31

Correct wiring. Discon-

nect stubs from old net.

N

Report fault

(see point 4.13)

Page is loading ...

Ericsson ASB 150 02 Description

Ericsson ASB 150 02 Description

Related papers

Other documents