E1/T1 Loss of Signal

OPERATING INSTRUCTIONS

4/1543-LZA 104 102/142 Uen A

Copyright

© Ericsson AB 2014. All rights reserved. No part of this document may be

reproduced in any form without the written permission of the copyright owner.

Disclaimer

The contents of this document are subject to revision without notice due to
continued progress in methodology, design and manufacturing. Ericsson shall
have no liability for any error or damage of any kind resulting from the use
of this document.

4/1543-LZA 104 102/142 Uen A | 2014-03-06

 Contents

Contents

1 Introduction 1
1.1 Scope 1
1.2 Target Groups 1
1.3 Prerequisites 1

2 Alarm Description 2
2.1 Example of Alarm Details 2
2.2 Alarm Causes and Consequences 2

3 Procedure 3

Glossary 5

Reference List 7

4/1543-LZA 104 102/142 Uen A | 2014-03-06

E1/T1 Loss of Signal

4/1543-LZA 104 102/142 Uen A | 2014-03-06

 Introduction

1 Introduction

This chapter outlines the scope, intended target groups and prerequisites of
this document.

1.1 Scope
These Operating Instructions (OPI) describe how to handle the "E1/T1 Loss of
Signal" alarm in the Site Integration Unit (SIU 02).

1.2 Target Groups

The intended target groups for this document are:

• Radio Network Engineers.

• System Administrators.

• Field Technicians.

• Installation and Integration personnel.

• Site Engineers.

1.3 Prerequisites
Ensure that the following documents have been read and understood:

• Personal Health and Safety Information.

• System Safety Information.

For information about Managed Object (MO) classes and their attributes, see
Reference [2].

4/1543-LZA 104 102/142 Uen A | 2014-03-06 1

 E1/T1 Loss of Signal

2 Alarm Description

The "E1/T1 Loss of Signal" alarm is raised when a Loss Of Signal (LOS)
is detected on an E1/T1 interface. The objectInstance in the alarm details
indicates which of the E1/T1 interfaces that has the condition.

2.1 Example of Alarm Details

objectClass "E1T1Interface"
objectInstance "STN=0,E1T1Interface=X"; where X=[0..15]
notificationId <>
eventTime <UTC time of activation of alarm>
probableCause x733LossOfSignal(329)
perceivedSeverity minor(3)
alarmType communicationsAlarm(2)
specificProblem "E1/T1 Loss of Signal"
additionalText "LOS"
alarmId <>

2.2 Alarm Causes and Consequences

The table below describes the alarm and lists its likely causes and
consequences.

Table 1 Alarm description, causes and consequences

Description Causes Consequences
No active input signal is detected • Hardware fault. The receive side of the
on the receive part of the E1/T1 E1/T1 interface is not
interface. • Remote equipment is available for traffic.
faulty or taken out of
service.
• Cable or connector
fault.
• Line coding mismatch
with peer side.

2 4/1543-LZA 104 102/142 Uen A | 2014-03-06

 Procedure

3 Procedure

To resolve what causes the alarm and get it ceased, do the following:

1. Check if a Hardware Fault alarm is present using the command

getalarmlist.

• If it is, follow the procedure in the relevant OPI. Exit the procedure if
the problem is solved and the alarm is ceased.

• If not, proceed to the next step.

2. In the alarm details (objectInstance), check which E1T1Interface that

issues the alarm.

3. Check the physical connection and cable type between the interface and
the remote node. Possibly make corrective actions.

• If the alarm ceases after corrections, exit the procedure.

• If not, proceed to the next step.

4. Together with maintenance center of remote node verify that settings for
transmission interfaces of remote node and the unit match each other.
Possibly adjust settings.

• If the alarm ceases after adjusting settings, exit the procedure.

• If not, proceed to the next step.

5. Agree with maintenance center of the remote node to activate - if possible -

line loopback inside that equipment, without disconnecting the cables.

• If line loopback is possible and alarm ceases when activated, the fault
is in the remote node. Report this to the maintenance center of the
remote node and instruct them to deactivate the line loopback and
address the problem. Exit the procedure.

• If line loopback is possible but alarm remains when activated. Report

this to the maintenance center of the remote node and instruct them
to deactivate the line loopback. Agree on the next steps to be taken.
Proceed with the next step.

• If line loopback is not possible agree with the maintenance center of

remote node on the next steps to be taken. Proceed with the next step.

6. Save debug/troubleshooting information by issuing the command

collectDCGInformation and restart the unit by making a power cycle.

Note: Restarting the unit will interrupt all traffic from the RBS through
the unit.

4/1543-LZA 104 102/142 Uen A | 2014-03-06 3

 E1/T1 Loss of Signal

• If the alarm is not reoccurring after the restart the E1/T1 interface may
accidentally have been in a bad state that was cleared by the restart.
Exit the procedure.

• If the alarm reoccurs after the restart, proceed with the next step.

7. Consult the next level of maintenance support.

Further action is outside the scope of these instructions.

4 4/1543-LZA 104 102/142 Uen A | 2014-03-06

 Glossary

Glossary

See Reference [1].

4/1543-LZA 104 102/142 Uen A | 2014-03-06 5

 E1/T1 Loss of Signal

6 4/1543-LZA 104 102/142 Uen A | 2014-03-06

 Reference List

Reference List

[1] Glossary

[2] Managed Object Model

4/1543-LZA 104 102/142 Uen A | 2014-03-06 7