No Calibration from E1/T1
OPERATING INSTRUCTIONS
9/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.
9/1543-LZA 104 102/142 Uen A | 2014-03-05
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
9/1543-LZA 104 102/142 Uen A | 2014-03-05
No Calibration from E1/T1
9/1543-LZA 104 102/142 Uen A | 2014-03-05
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 "No Calibration
from E1/T1" 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].
9/1543-LZA 104 102/142 Uen A | 2014-03-05 1
No Calibration from E1/T1
2 Alarm Description
The "No Calibration from E1/T1" alarm is raised when an E1/T1 link is
configured as synchronization source, and calibration of the internal OCXO has
not been possible for a period of 30 days.
2.1 Example of Alarm Details
objectClass "Synchronization"
objectInstance "STN=0,Synchronization=0"
notificationId <>
eventTime <UTC time of activation of alarm>
probableCause x733LossOfSignal(329)
perceivedSeverity warning(4)
alarmType communicationsAlarm(2)
specificProblem "No Calibration from E1/T1"
additionalText "Timing quality too bad or missing
on link"
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 calibration of the • Configuration • The internal OCXO
internal OCXO because of errors. cannot be calibrated.
poor synchronization signal
or missing synchronization • E1/T1 link disabled. • If the alarm is not
source. resolved within
• E1/T1 links not a month, the
synchronized. "Calibration Date
Expired" alarm is
• Poor network
raised.
quality.
2 9/1543-LZA 104 102/142 Uen A | 2014-03-05
Procedure
3 Procedure
To resolve what causes the alarm and get it ceased, do the following:
1. Check the attributes for each available MO E1T1Interface instance.
2. Check that no RBS link with MO Superchannel is dependent on any MO
E1T1Interface instance with receiveClockSource set to "timingReference".
3. Check that no E1/T1 interface used towards the WAN is configured with
attribute type set to "E1_unframed". Configuration of "E1_unframed" is not
recommended because there is no guarantee that the unframed path beat
is generated from a trusted synchronization source.
4. Check that the attribute receiveClockSource is set to "timingReference" for
at least one available E1/T1 interface.
5. Check that no E1/T1 interface, that is configured with receiveClockSource
set to "timingReference", is issuing an alarm using the command
getalarmlist .
• If there is one or more, follow the procedures in the relevant OPI below:
E1/T1 Loss of Signal
E1/T1 Loss of Frame
E1/T1 Alarm Indication Signal
E1/T1 Remote Defect Indication
Exit the procedure if the problem is solved and the alarm is ceased.
• If not, proceed to the next step.
6. Contact the maintenance center for the remote node and instruct them to
check the status of the synchronization source and quality of the network
and E1/T1 links.
7. Check that the attribute values in MO Synchronization are correct.
8. Verify in what calibration state the SIU is by checking the attribute
calibrationStatus in MO Synchronization. The figure below shows the
valid state transitions when using E1/T1 as synchronization source:
9/1543-LZA 104 102/142 Uen A | 2014-03-05 3
No Calibration from E1/T1
• If the value is one of the four "CAL_PROGRESS_X" states, the initial
calibration to verify the quality and stability of the synchronization
source is ongoing and the alarm will be ceased when a new calibration
value has been calculated. The length of the initial calibration period
is 2 hours when using E1/T1 as synchronization source. Exit the
procedure.
• If the value is "CAL_ONGOING" the continuous calibration is ongoing
with good connectivity. Exit the procedure.
• If the value is an error state that is not changed to a
"CAL_PROGRESS_X" or "CAL_ONGOING" state within the time or
condition indicated in the figure above, proceed to the next step.
9. Save debug/troubleshooting information by issuing the command
collectDCGInformation and restart the unit by making a power cycle.
• If the alarm is not reoccurring after the restart, exit the procedure.
• If the alarm reoccurs after the restart, proceed with the next step.
10. Consult the next level of maintenance support.
Further action is outside the scope of these instructions.
4 9/1543-LZA 104 102/142 Uen A | 2014-03-05
Glossary
Glossary
See Reference [1].
9/1543-LZA 104 102/142 Uen A | 2014-03-05 5
No Calibration from E1/T1
6 9/1543-LZA 104 102/142 Uen A | 2014-03-05
Reference List
Reference List
[1] Glossary
[2] Managed Object Model
9/1543-LZA 104 102/142 Uen A | 2014-03-05 7
