BusinessPhone Communication Platform 5.1
Fault Tracing

## Fault locating

### 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 BMS and check the configuration of the PBX with regard to revision states (see Translation and verification 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:

Type Of Fault | Go to
Indication of LEDs on board(s) | LED indications on the PBAs
No call procedures possible in the PBX | Flow chart: No possibility to make calls in PBX
Individual board not working | Flow chart: Individual board not working
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 | Flow chart: Individual does not work at all
Digital trunk (BTU-D) does not work at all | Flow chart: Digital trunk does not work at all
Individual malfunctions partly, intermittent faults, e.g. one connection case is successful and another fails. The fault can be traced to an individual | Flow chart: Part of individual function not working
A certain facility never functions. A certain facility is inaccessible, e.g. intrusion is never possible | Flow chart: Individual facility does not work
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 | Flow chart: Individual facility works intermittently
An individual has no access to a certain facility | Flow chart: Individual does not work for certain facilities
Transmission fault (one way speech, line scratching, etc.) | Flow chart: Transmission faults
PBX unstable (repeated restarts) | Flow chart: PBX is unstable
Faults related to Cordless | Flow Charts for Cordless

Use the following flow charts describing a methodical path for checks and tests to help locate and eliminate the fault. When the flow 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.

#### Description of flow chart symbols

Question |  | 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.
Instruction |  | This symbol contains an instruction for the maintenance engineer.
References |  | This symbol is used as: starting point for a procedure (e.g. START), as a reference to another flowchart, to end a procedure (END).
| This symbol is used as a reference point within a flowchart. This can be to a part of the flowchart on another page (e.g. B or C) or at a part of the flowchart on the same page (e.g.1).
Flow |  | Lines indicate the normal flow. The normal flow is always "down" and "to the right" and in exceptional cases "to the left".
| Arrows are used to indicate flows going "up" or left.

### LED indications on the PBAs

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. Depending on their function the LEDs are in different positions on the front edge.

#### Common LED’s on all boards

##### LED description during start-up

Normal start sequence | LEDs (in connection field 2) | Start sequence aborted 4) | State | Description
L1 red | L2 yellow | L3 green
1 (power up) | ON | ON | OFF |  | RESTART | Lights up immediately for about 20 seconds
ON | ON | ON | Yes | PROM-fault | Start up is interrupted if a fault is discovered during self test.
ON | ON | R-FL1) | Yes | RAM-fault
ON | R-FL1) | R-FL1) | Yes | HD-fault | VMU-HD only: Hard disk is missing/not installed
ON | A-FL3) | A-FL3) | Yes | DSP-fault | VMU-HD only: DSP not loaded
2 (wait) | OFF | S-FL2) | OFF |  | WAIT | Waits for start order from CPU.
3 (start) | OFF | R-FL1) | OFF |  | START | RP reports data to CPU, e.g. type of board
OFF | ON | OFF |  | Database-fault | Condition in case of database mismatch

1 |  | Rapid Flash (Frequency=4Hz).

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

3 |  | Alternate Rapid Flash (Frequency=1,66 Hz). Yellow SW-Led flashes times the code of the first identified error (20 different errors can be coded)

4 |  | In case of an abborted start sequence, the board is faulty and needs to be replaced

##### LED description during operation

LEDs (in connection field 2) | Condition | Description/Correction
L1 red | L2 yellow | L3 green |  |
ON | OFF | OFF | Regional Processor (RP) is disconnected logically from the PCM bus and signalling interface of the back plane | This LED indication occurs during following situations: switching on the system restart of the CP on the CPU or the RP of a peripheral board which detected a board failure CPU is performing a SW-update the board is in shut down mode
ON | S-FL1) | OFF | A new board has been added into a running system, but is not known by the CPU-D4. | Activate the “search” function via BMS, so that the CPU-D4 can detect the new board.
OFF | ON | OFF | One or more resources on the board are blocked | Check the wiring and if the connected equipment is operational, check it’s alarm indication as well as the programming.
OFF | OFF | ON | This indicates normal system operation and at least one individual is active on the board. | Individuals can be: Extensions, trunks, V24 interfaces, DSPs, registers...
OFF | OFF | OFF | Indicates normal system operation | No traffic

1 |  | Slow Flash (100 ms ON and 900 ms OFF).

#### LEDs on the CPU-D4

LEDs ( in connection field 4) | Condition | Description/Correction
L4 red | L5 yellow | L6 green | L7 red |  |
ON | OFF | OFF | OFF | CP is reset | This state occurs during following situation: remote SW upgrading onboard flash check during start up if the watchdog detects a fault. The LED L4 can be ON for up to 2 min. When LED L4 is ON, LED L3 is flashing
OFF | ON | OFF | OFF | Indicates start up of CP (L2 is flashing) |
OFF | S-FL1) | OFF | OFF
OFF | ON | ON | OFF
OFF | OFF | ON | OFF | Indicates at least one entry in the Alarm log | Check the logged errors in BMS and if possible correct the problem
-2) | -2) | -2) | ON | Cold start strap 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.

1. Slow Flash (Frequency=1 Hz).
2. State has no influence

##### LEDs on the CPU-D4 during remote SW upgrading

LEDs ( in connection field 2) | Description of condition
L1 red | L2 yellow | L3 green |
-1) | Fast flashing | -1) | Erasure of the upgrade FLASH before the upload of the new SW will be performed. This takes up to 30 seconds.
ON | One flash | Repeated flashes | Writing into PROM 1. After completion, the green LED flashes several times to recalculate the checksum.
ON | Two flashes | Repeated flashes | Writing into PROM 2. After completion, the green LED flashes several times to recalculate the checksum
ON | Three flashes | Repeated flashes | Writing into PROM 3. After completion, the green LED flashes several times to recalculate the checksum
ON | OFF | Repeated flashes | The green LED flashes during checksum recalculation of the programming data. Then the system restart is invoked.

1. State has no influence

#### LEDs on the IC-CU2,

Normal start sequence | LED ( in connection field 2 | Condition | Description/Correction
L4 red | L5 red | L6 red
1 (initialization) | OFF | ON | ON | CLU starts up |
OFF | ON | R-FL1)
OFF | ON | OFF | SPU starts up |
OFF | R-FL1) | OFF
5 (Operation) | OFF | OFF | OFF |  |
ON |  |  | There is at least one error in the IC-CU2 error log | Read out the error(s) by using the CSM
| ON |  | SPU error | This LED is turned on, if the board’s SPU RP detects a fault. To correct the fault check entries in the CSM and follow suitable solution given.
|  | ON | CLU error | 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.

#### LEDs on IC-LU

Normal start sequence | LED ( in connection field 2 | Condition
L3 red | L6 red
1 (initialization) | ON | ON | CLU start up
ON | R-FL1) | CLU start upr
ON | OFF | SPU start up
R-FL1) | OFF | SPU start up
5 (Operation) | OFF | OFF |
ON |  | This LED is turned on, if the board’s SPU RP detects a fault. To correct the fault check entries in the CSM and follow suitable solution given.
| ON | 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.

1. Rapid Flash (Frequency=4 Hz).

#### LEDs on the IPU

##### LED description during start up

Normal start up sequence | LEDs ( in connection field 2) | Start sequence aborted 6) | Description/Correction
L2 yellow | L3 green | L5 yellow | L6 green | L7 green
Power on | ON | ON | ON | ON | -5) | YES | Board does not start up, switch the power off and then on again.
1 (Startup ) | OFF | OFF | ON | OFF | -5) |  |
-5) | -5) | -5) | -5) | ON |  | Read/Write access on Flash card
OFF | ON | ON | ON | -5) | YES | RAM error occured during selftest
ON | OFF | ON | ON | -5) | YES | PROM Checksum error
ON | OFF | OFF | OFF | -5) |  |
ON | OFF | A-FL2) | OFF | -5) | YES | FPGA error
OFF | ON | OFF | OFF | -5) |  | load program to SDRAM
OFF | ON | OFF | OFF | -5) |  |
OFF | ON | A-FL2) | OFF | -5) | YES | Switch error
ON | ON | OFF | OFF | - |  |
ON | ON | A-FL2) | OFF | -5) | YES | DSP- daughter card error
2 (Wait) | S-FL3) | OFF | S-FL3) | OFF | -5) |  | Waits for CPU start-order
3 (Start) | R-FL1) | OFF | R-FL1) | OFF | -5) |  | device processor reports data to CPU, e.g. type of board
ON 4) | OFF4) | ON4) | OFF4) | -5) | YES | Reported data does not match with the database or an individual is blocked
5 (Operation) | OFF | OFF | OFF | OFF | -5) |  | Entered after PBX has been started.

1. Rapid Flash (Frequency=4 Hz).
2. Alternate Rapid Flash (Frequency=1,66 Hz). Yellow SW-Led flashes times the code of the first identified error (20 different errors can be coded)
3. Slow Flash (Frequency=1 Hz).
4. Applies to the LED indication of other boards
5. State has no influence
6. In case of an abborted start sequence, the board is faulty and needs to be replaced

##### LED description during operation

LEDs ( in connection field 2) | LEDs ( in connection field 4) | Description/Correction
L2 yellow | L3 green | L5 yellow | L6 green | L8 yellow | L9 green |
OFF | ON | OFF | ON | -3) | ON | DSP resource allocation. (At least one individual is in traffic)
ON | OFF | OFF | OFF | OFF | OFF | The ethernet link which was previously active is blocked, due to a broken connection.4)
OFF | -3 | ON | -3 | -3 | ON | A resource on the board is blocked, restart the board in order to correct the fault.
OFF | -3) | OFF) | -3) | OFF | ON | 10BaseT (half duplex) connection
OFF | -3) | OFF | -3) | S-FL2) | ON | 10BaseT (full duplex) connection
OFF | -3) | OFF) | -3) | ON | ON | 100BaseT (half duplex) connection
OFF | -3) | OFF | -3) | R-FL1) | ON | 100BaseT (full duplex) connection
OFF | -3) | OFF) | -3) | -3) | ON | ethernet link active (physical layer)

1. Rapid Flash (Frequency=4 Hz).
2. Slow Flash (Frequency=1 Hz).
3. State has no influence
4. This LED combination only appears, if the ethernetlink was active after a board/system start up, and broke down afterwards. The link state code which can be read out in the link supervisor menu in BMS changes in this case it‘s value from 20 (okay ) to 32 ( not okay). If there has been no active ethernet link already after a board/system startup, then the link is also blocked (link state code=32), however the LED L2 is not ON.

#### LEDs on BTU-D, VMU-HD

LEDs ( in connection field 2 | Condition | Description/Correction
L4 yellow | L5 green |  |
R-FL1 | ON | Start-up phase (only BTU-D) | Flashes together with L2
OFF | OFF | Normal operation | The boards is currently in idle state
ON | - | At least one register individual is blocked | The DSP does not work correctly, the board has to be changed
- | ON | At least one register individual is busy |

1. Rapid Flash (Frequency=4 Hz).

#### LEDs on the BTU-E

LEDs ( in connection field 2 | Condition | Description/Correction
L4 yellow | L5 green |  |
OFF | OFF | Normal operation |
ON |  | At least one register is blocked (the register is used in conjunction with line signal sheme CEPT L1) | The register unit does not work correctly, the board has to be changed
| ON | At least one register is busy |

#### LEDs on the MFU

The board is equipped with 5 LEDs divided into two groups. The LEDs L1, L2, L3 (in connection field 2) form a group which applies to the analog and digital extensions, while the LEDs L4,L5 (in connection field 4) form a group which applies to the ISDN trunk lines and registers. The behavoir of this LEDs equals to the indication of two separate boards. For the LED sequences during start up and operation see , Common LED’s on all boards, whereby LED L2 =L4 und LED L3=L5.

### Flow chart: No possibility to make calls in PBX

### Flow chart: Individual board not working

### Flow chart: Individual does not work at all

#### Individual does not work at all – Part 1

#### Individual does not work at all – Part 2

### Flow chart: Digital trunk does not work at all

### Flow chart: Part of individual function not working

### Flow chart: Individual facility does not work

### Flow chart: Individual facility works intermittently

### Flow chart: Individual does not work for certain facilities

### Flow chart: Transmission faults

### Flow chart: PBX is unstable

### Flow Charts for Cordless

#### Flow Charts for Cordless – Part 1

#### Flow Charts for Cordless – Part 2, Common User complaint

#### Flow Charts for Cordless – Part 3, Individual User complaint

#### Flow Charts for Cordless – Part 4, Errors

#### Flow Charts for Cordless – Part 5, No Dial Tone

#### Flow Charts for Cordless – Part 6, CSM Problem

#### Flow Charts for Cordless – Part 7

### Completion of service

On completion of service disconnect BMS and check the warning log for entries. If this is the case adopt the recommended measure(s). If no further measures can be taken note the logs (or printout if possible) and contact your local support facility.

Remaining faults are to be reported (see Fault reporting).

If you cannot fix the problem at the moment start up the exchange again and give the customer instructions how to cope with malfunctions, conclude by making a printout of the warning log and resetting it. Disconnect BMS and place the cover on the exchange.

Revision: PH2 © Ericsson Enterprise 2003