operating instructions 2/1543-100/csh 109 32/1...

43
OPERATING INSTRUCTIONS 2/1543-100/CSH 109 32/1-V3 Uen A Alarm Descriptions MINI-LINK CN 210 ETSI Contents 1 Introduction 2 Safety Information 3 Preparations 3.1 Additional Preparations 4 Overview 4.1 Consequences 4.2 Alarm Analysis 4.3 Corrective Actions 4.4 Alarm Clearance 5 Alarms 5.1 AIS (Minor) 5.2 AMS 15 min threshold crossing 5.3 AMS 24 h threshold crossing 5.4 ATPC Capability 5.5 ATPC Capability (Far End) 5.6 BBE 15 min threshold crossing 5.7 BBE 24 h threshold crossing 5.8 BER (Major) 5.9 BER (Critical) 5.10 Default configuration not accepted 5.11 Dmod Clock (Major) 5.12 Dmod Clock (Critical) 5.13 Downstream buffer overflow 5.14 ES 15 min threshold crossing 5.15 ES 24 h threshold crossing 5.16 Ethernet Down (Minor) 5.17 Ethernet Down (Critical) 5.18 Free running mode entered 5.19 Hardware Error: RAU (Minor) 5.20 Hardware Error: RAU (Critical) 5.21 Hardware Error: RMM 5.22 HCC

Upload: truongthuy

Post on 06-Feb-2018

290 views

Category:

Documents


5 download

TRANSCRIPT

Page 1: OPERATING INSTRUCTIONS 2/1543-100/CSH 109 32/1 …docshare04.docshare.tips/files/25573/255734631.pdf · methodology, design and manufacturing. Ericsson shall have no liability for

OPERATING INSTRUCTIONS 2/1543-100/CSH 109 32/1-V3 Uen AAlarm DescriptionsMINI-LINK CN 210 ETSI

Contents

1 Introduction

2 Safety Information

3 Preparations3.1 Additional Preparations

4 Overview4.1 Consequences4.2 Alarm Analysis4.3 Corrective Actions4.4 Alarm Clearance

5 Alarms5.1 AIS (Minor)5.2 AMS 15 min threshold crossing5.3 AMS 24 h threshold crossing5.4 ATPC Capability5.5 ATPC Capability (Far End)5.6 BBE 15 min threshold crossing5.7 BBE 24 h threshold crossing5.8 BER (Major)5.9 BER (Critical)5.10 Default configuration not accepted5.11 Dmod Clock (Major)5.12 Dmod Clock (Critical)5.13 Downstream buffer overflow5.14 ES 15 min threshold crossing5.15 ES 24 h threshold crossing5.16 Ethernet Down (Minor)5.17 Ethernet Down (Critical)5.18 Free running mode entered5.19 Hardware Error: RAU (Minor)5.20 Hardware Error: RAU (Critical)5.21 Hardware Error: RMM5.22 HCC

Page 2: OPERATING INSTRUCTIONS 2/1543-100/CSH 109 32/1 …docshare04.docshare.tips/files/25573/255734631.pdf · methodology, design and manufacturing. Ericsson shall have no liability for

5.23 High Temperature5.24 Hitless Phase5.25 ICC5.26 Insufficient resources5.27 LOS: RAU IF (Major)5.28 LOS (Critical)5.29 LOS: RAU IF (Critical)5.30 Low Input Voltage5.31 Mod Index5.32 Node Installation5.33 No Traffic5.34 Power Failure (upper input port)5.35 Power Failure (lower input port)5.36 Power Failure (upper input port) Slave5.37 Power Failure (lower input port) Slave5.38 PPP down5.39 RAU Power Supply Changed5.40 Radio Frame (Major)5.41 Radio Frame (Critical)5.42 Radio ID (Major)5.43 Radio ID (Critical)5.44 RCC (Major)5.45 Remote Tx Switch Over5.46 Reserved Position5.47 RF Input Level (Major)5.48 RF Input Level (Critical)5.49 RF Input Threshold5.50 RF Input Threshold Protection5.51 RF Output Level (Major)5.52 RF Output Level (Critical)5.53 Running configuration not accepted5.54 Rx AFC5.55 RX Frequency (Major)5.56 RX Frequency (Critical)5.57 Rx IF Input5.58 SES 15 min threshold crossing5.59 SES 24 h threshold crossing5.60 Squelch threshold reached5.61 TX Frequency (Major)5.62 TX Frequency (Critical)5.63 Tx IF Input (Major)5.64 Tx IF Input (Critical)

Page 3: OPERATING INSTRUCTIONS 2/1543-100/CSH 109 32/1 …docshare04.docshare.tips/files/25573/255734631.pdf · methodology, design and manufacturing. Ericsson shall have no liability for

5.65 TX Switch Over5.66 Unable to Protect: SWITCH (Major)5.67 Unable to Protect: SWITCH (Critical)5.68 Unavailable Period5.69 Unit Inaccessible: Slave MMU5.70 Unit Inaccessible: RMM5.71 Unsupported RMM variant - connect FTP server and do upgrade5.72 Unsupported Unit Type5.73 Missing License5.74 User I/O

Reference List

Copyright © Ericsson AB 2011. All rights reserved. No part of this document may bereproduced in any form without the written permission of the copyright owner.

DisclaimerThe contents of this document are subject to revision without notice due to continuedprogress in methodology, design and manufacturing. Ericsson shall have no liabilityfor any error or damage of any kind resulting from the use of this document.

Abstract

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

1 IntroductionThis document describes the alarms for MINI-LINK CN 210 . It also proposes actions to betaken upon reception of an alarm.

2 Safety InformationMake sure that the information in the following documents has been understood by the personsperforming the procedures:

Personal Health and Safety Information System Safety Information Supplementary Safety Information for MINI-LINK

3 Preparations

Page 4: OPERATING INSTRUCTIONS 2/1543-100/CSH 109 32/1 …docshare04.docshare.tips/files/25573/255734631.pdf · methodology, design and manufacturing. Ericsson shall have no liability for

This section presents the preparations needed for a successful completion of the procedures inthis instruction.

3.1 Additional PreparationsConsider the following additional preparations:

Read through all applicable sections and make sure referenced documents are available. Make sure you have access to the NE using MINI-LINK Craft. For more information, see

Accessing a Network Element.

4 OverviewEach alarm section begins with a short description of the alarm. The following information isalso included as reported in the Notification List in MINI-LINK Craft:SpecificProblem The name of the alarm.

Source The source of the alarm.

AlarmType The alarm type. The alarm types are specified in Fault ManagementOperations.

Severity The severity of the alarm, for example, Critical or Minor. All severities aredescribed in Fault Management Operations.

ProbableCause The probable cause of the alarm.

The caption of each alarm section can contain three parts: Specific Problem, Source, andSeverity. Only the parts that are necessary to specify a unique alarm are included in eachheading. For example, the caption of the alarm Hardware Error, with source equal to RAU andseverity equal to critical, is named "Hardware Error: RAU (Critical)".

Optionally, the list with information from the Notification List in MINI-LINK Craft is followedby subsections that describe the alarm in more detail, see below.

4.1 ConsequencesSection that describes what else has happened as a result of this alarm, informs if a switch hasoccurred, and if there are any masked alarms.

4.2 Alarm AnalysisSection describing how to find the root cause of the alarm.

Page 5: OPERATING INSTRUCTIONS 2/1543-100/CSH 109 32/1 …docshare04.docshare.tips/files/25573/255734631.pdf · methodology, design and manufacturing. Ericsson shall have no liability for

4.3 Corrective ActionsSection that describes which actions can be taken in order to recover the system.

4.4 Alarm ClearanceSection that describes how the alarm is cleared, automatically or as a result of corrective action.

5 AlarmsThis section describes all alarms listed alphabetically.

5.1 AIS (Minor)Alarm Indication Signal (AIS)

An AIS is detected on the incoming traffic.

SpecificProblem AIS

Source o E1

AlarmType CommunicationAlarm

Severity Minor

ProbableCause AlarmIndicationSignal

5.2 AMS 15 min threshold crossingAdaptive Modulation Seconds (AMS)

The terminal has been using the minimum modulation longer time than the configured 15 minutethreshold. The threshold has been crossed during the current 15 minute interval.

Applicable for RAU IF (1+0).

Applicable for SWITCH (1+1).

SpecificProblem AMS 15 m threshold crossing

Source o RAU IF (1+0)

Page 6: OPERATING INSTRUCTIONS 2/1543-100/CSH 109 32/1 …docshare04.docshare.tips/files/25573/255734631.pdf · methodology, design and manufacturing. Ericsson shall have no liability for

o SWITCH

AlarmType QualityOfServiceAlarm

Severity Minor

ProbableCause ThresholdCrossed

5.2.1 Consequences

Decreased traffic capacity for a longer time than expected.

5.2.2 Corrective Actions

The problem may be temporary, but if the alarm continues over consecutive 15 min intervals, trythe following actions:

1. Verify the Radio Frequency (RF) input power level: it must be above the 10-6 Bit ErrorRatio (BER) threshold (at least 5 dB) during good weather conditions.

2. Check the antenna alignment, see Installing Outdoor Equipment.3. Check if obstacles are placed in the radio path between the two hops' antennas (at clear

sky conditions).4. Verify that the Radio Network Planning is correct.

5.2.3 Alarm Clearance

The alarm is cleared when the time spent in the minimum modulation at the end of the interval isless than the AMS 15 min reset threshold.

5.3 AMS 24 h threshold crossingAdaptive Modulation Seconds (AMS)

The terminal has been using the minimum modulation longer time than the configured 24 hourthreshold.

Applicable for RAU IF (1+0).

Applicable for SWITCH (1+1).

SpecificProblem AMS 24 h threshold crossing

Source o RAU IF (1+0)

Page 7: OPERATING INSTRUCTIONS 2/1543-100/CSH 109 32/1 …docshare04.docshare.tips/files/25573/255734631.pdf · methodology, design and manufacturing. Ericsson shall have no liability for

o SWITCH

AlarmType QualityOfServiceAlarm

Severity Minor

ProbableCause ThresholdCrossed

5.3.1 Consequences

Decreased traffic capacity for a longer time than expected.

5.3.2 Corrective Actions

Try the following actions:

1. Verify the Radio Frequency (RF) input power level: it must be above the 10-6 Bit ErrorRatio (BER) threshold (at least 5 dB) during good weather conditions.

2. Check the antenna alignment, see Installing Outdoor Equipment, .3. Check if obstacles are placed in the radio path between the two hops' antennas (at clear

sky conditions).4. Verify that the Radio Network Planning is correct.

5.3.3 Alarm Clearance

The alarm is not cleared automatically. To clear it do a warm restart.

5.4 ATPC CapabilityAutomatic Transmit Power Control (ATPC)

The terminal is configured for ATPC, but the RAU does not support ATPC. This alarm isactivated only if ATPC is turned on (any direction).

SpecificProblem ATPC Capability

Source RAU

AlarmType EquipmentAlarm

Severity Major

ProbableCause ReplacebleUnitTypeMismatch

Page 8: OPERATING INSTRUCTIONS 2/1543-100/CSH 109 32/1 …docshare04.docshare.tips/files/25573/255734631.pdf · methodology, design and manufacturing. Ericsson shall have no liability for

5.4.1 Consequences

It is not possible to use ATPC functionality.

5.4.2 Corrective Actions

Replace the RAU to one with ATPC support, see Replacing a Radio Unit.

5.4.3 Alarm Clearance

The alarm is cleared when ATPC is disabled or if the RAU is replaced to a RAU with ATPCsupport.

5.5 ATPC Capability (Far End)Automatic Transmit Power Control (ATPC)

The terminal on the far-end is configured for ATPC, but at least one of the units does not supportATPC.

SpecificProblem ATPC Capability (Far End)

Source All MMUs

All MINI-LINK CN 210 units

AlarmType EquipmentAlarm

Severity Major

ProbableCause ReplacebleUnitTypeMismatch

5.5.1 Consequences

It is not possible to enable ATPC functionality.

5.5.2 Corrective Actions

Replace far-end terminal to one with ATPC support, see the relevant Replacing document.

5.5.3 Alarm Clearance

The alarm is cleared when ATPC is disabled or if the far-end terminal is replaced to one withATPC support.

Page 9: OPERATING INSTRUCTIONS 2/1543-100/CSH 109 32/1 …docshare04.docshare.tips/files/25573/255734631.pdf · methodology, design and manufacturing. Ericsson shall have no liability for

5.6 BBE 15 min threshold crossingBackground Block Error (BBE)

BBE threshold crossing for 15 min composite performance monitoring. The alarm is raised whenthe BBE counter value crosses the BBE threshold set by the operator.

Applicable for RAU IF (1+0).

Applicable for SWITCH (1+1).

SpecificProblem BBE 15 min threshold crossing

Source o RAU IF (1+0)o SWITCH

AlarmType QualityOfServiceAlarm

Severity Major

ProbableCause ThresholdCrossed

5.6.1 Consequences

Degraded traffic.

5.6.2 Corrective Actions

The problem may be temporary, but if the alarm continues over consecutive 15 min intervals, trythe following actions:

1. Check if obstacles are placed in the radio path between the two hops' antennas (at clearsky conditions).

2. Verify that the received signal power is as expected (by performing a link budgetcalculation).

3. Check that no interference signal is present.4. Replace the MINI-LINK CN 210, see Replacing a MINI-LINK CN 2105. Replace the RAU, see Replacing a Radio Unit.

5.6.3 Alarm Clearance

The alarm is cleared at the next 15 minutes interval where the BBE counter threshold no longeris crossed.

Page 10: OPERATING INSTRUCTIONS 2/1543-100/CSH 109 32/1 …docshare04.docshare.tips/files/25573/255734631.pdf · methodology, design and manufacturing. Ericsson shall have no liability for

5.7 BBE 24 h threshold crossingBackground Block Error (BBE)

BBE threshold crossing for 24 hour composite performance monitoring. The alarm is raisedwhen the BBE counter value crosses the BBE threshold set by the operator.

Applicable for RAU IF (1+0).

Applicable for SWITCH (1+1).

SpecificProblem BBE 24 h threshold crossing

Source o RAU IF (1+0)o SWITCH

AlarmType QualityOfServiceAlarm

Severity Major

ProbableCause ThresholdCrossed

5.7.1 Consequences

Degraded traffic.

5.7.2 Corrective Actions

The problem may be temporary, but if the alarm continues over consecutive 24 h intervals, trythe following actions:

1. Check if obstacles are placed in the radio path between the two hops' antennas (at clearsky conditions).

2. Verify that the received signal power is as expected (by performing a link budgetcalculation).

3. Check that no interference signal is present.4. Replace the MINI-LINK CN 210, see Replacing a MINI-LINK CN 210.5. Replace the RAU, see Replacing a Radio Unit.

5.7.3 Alarm Clearance

The alarm is cleared at the next 24 hours interval where the BBE counter threshold no longer iscrossed.

Page 11: OPERATING INSTRUCTIONS 2/1543-100/CSH 109 32/1 …docshare04.docshare.tips/files/25573/255734631.pdf · methodology, design and manufacturing. Ericsson shall have no liability for

5.8 BER (Major)Bit Error Ratio (BER)

The BER calculated by the Forward Error Correction (FEC) for the received signal has exceededthe BER alarm threshold. The incoming signal is so corrupt that the FEC is unable to correct theincoming traffic.

Applicable for RAU IF (1+1).

SpecificProblem BER

Source RAU IF

AlarmType Communication

Severity Major

ProbableCause DegradedSignal

5.8.1 Consequences

Radio Protection Switch will select the other demodulation path if its signal quality is better.

5.8.2 Corrective Actions

Check if obstacles are placed in the radio path between the two hops' antennas (at clear skyconditions).

If the alarm is raised during hop installation, also try the following:

1. Verify that the received signal power is as expected (by doing a link budget calculation).2. Check the antenna alignment, see Installing Outdoor Equipment.

5.8.3 Alarm Clearance

The alarm is cleared when the BER estimation is below the BER alarm threshold.

5.9 BER (Critical)Bit Error Ratio (BER)

The BER calculated by the Forward Error Correction (FEC) for the received signal has exceededthe BER alarm threshold. The incoming signal is so corrupt that the FEC is unable to correct theincoming traffic.

Page 12: OPERATING INSTRUCTIONS 2/1543-100/CSH 109 32/1 …docshare04.docshare.tips/files/25573/255734631.pdf · methodology, design and manufacturing. Ericsson shall have no liability for

Applicable for RAU IF (1+0).

SpecificProblem BER

Source RAU IF

AlarmType Communication

Severity Critical

ProbableCause DegradedSignal

5.9.1 Consequences

Degradation of signal quality. Only for Plesiochronous Digital Hierarchy (PDH).

5.9.2 Corrective Actions

Check if obstacles are placed in the radio path between the two hops' antennas (at clear skyconditions).

If the alarm is raised during hop installation, also try the following:

1. Verify that the received signal power is as expected (by doing a link budget calculation).2. Check the antenna alignment, see Installing Outdoor Equipment.

5.9.3 Alarm Clearance

The alarm is cleared when the BER estimation is below the BER alarm threshold.

5.10 Default configuration not acceptedThe MINI-LINK CN 210 or RAU could not accept the default configuration. This can be causedby an error in the configuration file or by a hardware error. The service (yellow) LED flashesduring this alarm.

SpecificProblem Default configuration not accepted

Source o All MINI-LINK CN 210 unitso All RAUs

AlarmType EquipmentAlarm

Severity Major

Page 13: OPERATING INSTRUCTIONS 2/1543-100/CSH 109 32/1 …docshare04.docshare.tips/files/25573/255734631.pdf · methodology, design and manufacturing. Ericsson shall have no liability for

ProbableCause ReplaceableUnitTypeMismatch

5.10.1 Consequences

Failure to manage the unit or the entire node.

5.10.2 Alarm Clearance

The alarm is cleared when the configuration file is accepted.

5.11 Dmod Clock (Major)The internal data rate of the MINI-LINK CN 210 does not correspond to the received data rate.This fault will cause bit slip in the composite bit stream.

Probable causes for the fault: faulty MINI-LINK CN 210 or fading.

Applicable for RAU IF (1+1).

SpecificProblem Dmod Clock

Source RAU IF

AlarmType EquipmentAlarm

Severity Major

ProbableCause TimingProblem

5.11.1 Consequences

This condition may lead to Unable to Protect or hitless switching not working, if a switch needsto be done later.

5.11.2 Corrective Actions

If the problem is caused by fading when space diversity is used, the system is probably able tocorrect itself and no action is necessary. Otherwise, try the following:

Make a manual switch. Test the radio hop.

5.11.3 Alarm Clearance

Page 14: OPERATING INSTRUCTIONS 2/1543-100/CSH 109 32/1 …docshare04.docshare.tips/files/25573/255734631.pdf · methodology, design and manufacturing. Ericsson shall have no liability for

The alarm is cleared when the internal data rate of the MINI-LINK CN 210 matches the receiveddata rate.

5.12 Dmod Clock (Critical)The Internal data rate of the MINI-LINK CN 210 does not correspond to the received data rate.This fault will cause bit slip in the composite bit stream.

Probable causes for the fault: faulty MINI-LINK CN 210 or fading.

Applicable for RAU IF (1+0).

SpecificProblem Dmod Clock

Source RAU IF

AlarmType EquipmentAlarm

Severity Critical

ProbableCause TimingProblem

5.12.1 Consequences

Traffic Loss.

5.12.2 Corrective Actions

Test the radio hop.

5.12.3 Alarm Clearance

The alarm is cleared when the internal data rate of the MINI-LINK CN 210 matches the receiveddata rate.

5.13 Downstream buffer overflowBuffer overflow in the downlink direction.

SpecificProblem Downstream buffer overflow

Source LAN

AlarmType CommunicationAlarm

Page 15: OPERATING INSTRUCTIONS 2/1543-100/CSH 109 32/1 …docshare04.docshare.tips/files/25573/255734631.pdf · methodology, design and manufacturing. Ericsson shall have no liability for

Severity Major

ProbableCause Unavailable

5.14 ES 15 min threshold crossingErrored Seconds (ES)

The Plesiochronous Digital Hierarchy (PDH) ES counter threshold, set for 15 min time window,has been crossed the last 15 minutes. An Errored Second is a one-second period with one ormore errored blocks, or at least one defect.

Applicable for RAU IF (1+0).

Applicable for SWITCH (1+1).

SpecificProblem ES 15 min threshold crossing

Source o RAU IF (1+0)o SWITCH

AlarmType QualityOfServiceAlarm

Severity Minor

ProbableCause ThresholdCrossed

5.14.1 Consequences

This alarm indicates degraded traffic. If the problem continues, it may lead to SES 15 minthreshold crossing, see Section 5.58.

5.14.2 Corrective Actions

The problem may be temporary, but if the alarm continues over consecutive 15 min intervals, trythe following actions:

1. Check if obstacles are placed in the radio path between the two hops' antennas (at clearsky conditions).

2. Verify that the received signal power is as expected (by performing a link budgetcalculation).

3. Check that no interference signal is present.4. Replace the MINI-LINK CN 210, see Replacing a MINI-LINK CN 210.5. Replace the RAU, see Replacing a Radio Unit.

Page 16: OPERATING INSTRUCTIONS 2/1543-100/CSH 109 32/1 …docshare04.docshare.tips/files/25573/255734631.pdf · methodology, design and manufacturing. Ericsson shall have no liability for

5.14.3 Alarm Clearance

The alarm is cleared at the next 15 minutes interval where the ES counter threshold no longer iscrossed.

5.15 ES 24 h threshold crossingErrored Seconds (ES)

The Plesiochronous Digital Hierarchy (PDH) ES counter threshold, set for 24 h time window,has been crossed the last 24 hours. An Errored Second is a one-second period with one or moreerrored blocks, or at least one defect.

Applicable for RAU IF (1+0).

Applicable for SWITCH (1+1).

SpecificProblem ES 24 h threshold crossing

Source o RAU IF (1+0)o SWITCH

AlarmType QualityOfServiceAlarm

Severity Minor

ProbableCause ThresholdCrossed

5.15.1 Consequences

This alarm indicates degraded traffic. If the problem continues, it may lead to SES 24 h thresholdcrossing, see Section 5.59.

5.15.2 Corrective Actions

The problem may be temporary, but if the alarm continues over consecutive 24 h intervals, trythe following actions:

1. Check if obstacles are placed in the radio path between the two hops' antennas (at clearsky conditions).

2. Verify that the received signal power is as expected (by performing a link budgetcalculation).

3. Check that no interference signal is present.4. Replace the MINI-LINK CN 210, see Replacing a MINI-LINK CN 210.

Page 17: OPERATING INSTRUCTIONS 2/1543-100/CSH 109 32/1 …docshare04.docshare.tips/files/25573/255734631.pdf · methodology, design and manufacturing. Ericsson shall have no liability for

5. Replace the RAU, see Replacing a Radio Unit.

5.15.3 Alarm Clearance

The alarm is cleared at the next 24 hours interval where the ES counter threshold no longer iscrossed.

5.16 Ethernet Down (Minor)This alarm can be caused by an Ethernet cable problem or a configuration error.

SpecificProblem Ethernet down

Source Site LAN

AlarmType CommunicationAlarm

Severity Minor

ProbableCause Unavailable

5.16.1 Consequences

No Ethernet connection.

5.16.2 Corrective Actions

Try the following:

1. Check that the Ethernet cable is properly connected and that it is not damaged.2. Check the site LAN port configuration.3. Check the site LAN port to SWITCH configuration.4. Check the SWITCH configuration.

5.17 Ethernet Down (Critical)The interface is down. This alarm can be caused by an Ethernet cable problem or a configurationerror.

SpecificProblem Ethernet down

Source LAN

AlarmType CommunicationAlarm

Page 18: OPERATING INSTRUCTIONS 2/1543-100/CSH 109 32/1 …docshare04.docshare.tips/files/25573/255734631.pdf · methodology, design and manufacturing. Ericsson shall have no liability for

Severity Critical

ProbableCause Unavailable

5.17.1 Consequences

No Carrier Detected on the Ethernet Port.

5.17.2 Corrective Actions

Try the following:

1. Check that the Ethernet cable is properly connected and that it is not damaged.2. Check the site LAN port configuration.

5.17.3 Alarm Clearance

The alarm is cleared when a carrier is detected on the Ethernet port.

5.18 Free running mode enteredThe network synchronization function has entered the free running (hold over) status.

SpecificProblem Free running mode entered

Source NE

AlarmType CommunicationAlarm

Severity Critical

ProbableCause LossOfSynchronisation

5.18.1 Consequences

The synchronization output signal is squelched.

5.18.2 Corrective Actions

No action required.

5.18.3 Alarm Clearance

The alarm is cleared when the network synchronization function enters locked status.

Page 19: OPERATING INSTRUCTIONS 2/1543-100/CSH 109 32/1 …docshare04.docshare.tips/files/25573/255734631.pdf · methodology, design and manufacturing. Ericsson shall have no liability for

5.19 Hardware Error: RAU (Minor)The RAU has a hardware error and must be replaced.

SpecificProblem Hardware Error

Source RAU

AlarmType EquipmentAlarm

Severity Minor

ProbableCause ReplaceableUnitProblem

5.19.1 Consequences

Control system error.

5.19.2 Corrective Actions

Replace the RAU, see Replacing a Radio Unit.

5.19.3 Alarm Clearance

The alarm is cleared when the faulty unit is replaced.

5.20 Hardware Error: RAU (Critical)The RAU has a hardware error and must be replaced.

SpecificProblem Hardware Error

Source RAU

AlarmType EquipmentAlarm

Severity Critical

ProbableCause ReplaceableUnitProblem

5.20.1 Consequences

Traffic Loss.

5.20.2 Corrective Actions

Page 20: OPERATING INSTRUCTIONS 2/1543-100/CSH 109 32/1 …docshare04.docshare.tips/files/25573/255734631.pdf · methodology, design and manufacturing. Ericsson shall have no liability for

Replace the RAU, see Replacing a Radio Unit.

5.20.3 Alarm Clearance

The alarm is cleared when the faulty unit is replaced.

5.21 Hardware Error: RMMThe RMM has a hardware error and must be replaced.

SpecificProblem HW Error

Source RMM

AlarmType EquipmentAlarm

Severity Minor

ProbableCause ReplaceableUnitProblem

5.21.1 Consequences

Entering the grace period, during which all optional features are granted.

5.21.2 Corrective Actions

Replace the RMM, see Replacing an RMM.

5.21.3 Alarm Clearance

The alarm is cleared when the RMM has been replaced.

5.22 HCCHop Communication Channel (HCC)

Communication is lost on the HCC, between the MINI-LINK CN 210 and the far-end MMU orMINI-LINK CN 210.

SpecificProblem HCC

Source All MINI-LINK CN 210 units

AlarmType CommunicationAlarm

Page 21: OPERATING INSTRUCTIONS 2/1543-100/CSH 109 32/1 …docshare04.docshare.tips/files/25573/255734631.pdf · methodology, design and manufacturing. Ericsson shall have no liability for

Severity Major

ProbableCause Unavailable

5.22.1 Consequences

It is not possible to access the Far End.

5.22.2 Alarm Clearance

The alarm is cleared when access to the Far End is recovered.

5.23 High TemperatureThe unit has reached an abnormal temperature.

This can be caused by fan failure, too high ambient temperature, component failure, or air flowblocking.

SpecificProblem High Temperature

Source MMU

AlarmType EquipmentAlarm

Severity Major

ProbableCause HighTemperature

5.23.1 Consequences

The control system functions are shut down (operational status Reduced Service). This gives agraceful degradation through controlled protection switch in a 1+1. Alarms are sent in a 1+0, butthe traffic is still active.

5.23.2 Corrective Actions

Try the following:

Check the ambient temperature and take measures if it is too high. Check for component failure alarms and take care of any problems. Make sure that the air flow is not blocked.

5.23.3 Alarm Clearance

Page 22: OPERATING INSTRUCTIONS 2/1543-100/CSH 109 32/1 …docshare04.docshare.tips/files/25573/255734631.pdf · methodology, design and manufacturing. Ericsson shall have no liability for

The alarm is cleared when the temperature has been stable for 60 seconds below the hightemperature threshold for the unit.

5.24 Hitless PhaseFailure of synchronizing of the received traffic in the two MINI-LINK CN 210 units with aduration longer than the time given by Fade Notification Timer.

SpecificProblem Hitless Phase

Source SWITCH

AlarmType EquipmentAlarm

Severity Warning

ProbableCause ProtectionPathFailure

5.25 ICCInternal Communication Channel (ICC)

Communication is lost on the ICC, between two MINI-LINK CN 210 units in the same terminal.

Possible cause: the software or hardware of the MINI-LINK CN 210 units is not compatible, orthe protection cable has been unplugged.

SpecificProblem ICC

Source CN 210 Master unit

AlarmType CommunicationAlarm

Severity Major

5.25.1 Consequences

Unable to Protect.

5.25.2 Corrective Actions

Try the following:

1. Check the software and hardware of the MINI-LINK CN 210 units.2. Upgrade software or replace one MINI-LINK CN 210 to achieve compatibility.

Page 23: OPERATING INSTRUCTIONS 2/1543-100/CSH 109 32/1 …docshare04.docshare.tips/files/25573/255734631.pdf · methodology, design and manufacturing. Ericsson shall have no liability for

5.25.3 Alarm Clearance

The alarm is cleared when communication is recovered.

5.26 Insufficient resourcesThe NE does not have the resources to handle this unit.

SpecificProblem Insufficient resources

Source RAU slot

AlarmType EquipmentAlarm

Severity Critical

ProbableCause ReplaceableUnitTypeMismatch

5.27 LOS: RAU IF (Major)Loss of Signal (LOS)

LOS is detected on the incoming traffic, probably due to traffic failure in transmitting direction.

Applicable for RAU IF (1+1).

SpecificProblem LOS

Source RAU IF

AlarmType CommunicationAlarm

Severity Major

ProbableCause LossOfSignal

5.28 LOS (Critical)Loss of Signal (LOS)

LOS is detected on the incoming traffic, probably due to traffic failure in transmitting direction.

SpecificProblem LOS

Source o E1

Page 24: OPERATING INSTRUCTIONS 2/1543-100/CSH 109 32/1 …docshare04.docshare.tips/files/25573/255734631.pdf · methodology, design and manufacturing. Ericsson shall have no liability for

o MS/RS

AlarmType CommunicationAlarm

Severity Critical

ProbableCause LossOfSignal

5.28.1 Consequences

The service is unavailable.

5.28.2 Corrective Actions

Check cables and equipment in the traffic path.

5.28.3 Alarm Clearance

The alarm is cleared when traffic is detected in the incoming signal.

5.29 LOS: RAU IF (Critical)Loss of Signal (LOS)

LOS is detected on the incoming traffic, probably due to traffic failure in transmitting direction.

Applicable for RAU IF (1+0).

SpecificProblem LOS

Source RAU IF

AlarmType CommunicationAlarm

Severity Critical

ProbableCause LossOfSignal

5.30 Low Input VoltageThe input voltage is low. If it drops further, one or more units may stop working.

SpecificProblem Low Input Voltage

Page 25: OPERATING INSTRUCTIONS 2/1543-100/CSH 109 32/1 …docshare04.docshare.tips/files/25573/255734631.pdf · methodology, design and manufacturing. Ericsson shall have no liability for

Source NE

AlarmType EnvironmentalAlarm

Severity Major

ProbableCause PowerProblem

5.31 Mod IndexThe modulation index of the MINI-LINK CN 210, controlled by the far-end MMU or MINI-LINK CN 210, is out of the allowed range.

SpecificProblem Mod Index

Source RAU IF

AlarmType CommunicationAlarm

Severity Major

ProbableCause DegradedSignal

5.32 Node InstallationThe NE is in Node Installation mode. Enter the URL http://10.0.0.1 to reach the installationwizard.

SpecificProblem Node Installation

Source NE

AlarmType EquipmentAlarm

Severity Minor

ProbableCause CommunicationsSubsystemFailure

5.33 No TrafficNo Ethernet traffic received from far end terminal.

SpecificProblem No Traffic

Source RL-IME

Page 26: OPERATING INSTRUCTIONS 2/1543-100/CSH 109 32/1 …docshare04.docshare.tips/files/25573/255734631.pdf · methodology, design and manufacturing. Ericsson shall have no liability for

AlarmType CommunicationAlarm

Severity Critical

ProbableCause Unavailable

5.34 Power Failure (upper input port)Missing power at the DC upper connector.

SpecificProblem Power Failure (upper input connector)

Source NE

AlarmType EnvironmentalAlarm

Severity Major

ProbableCause PowerProblem

5.35 Power Failure (lower input port)Missing power at the DC lower connector.

SpecificProblem Power Failure (lower input connector)

Source NE

AlarmType EnvironmentalAlarm

Severity Major

ProbableCause PowerProblem

5.36 Power Failure (upper input port) SlaveMissing power at the DC upper connector.

SpecificProblem Power Failure (upper input connector) Slave

Source NE

AlarmType EnvironmentalAlarm

Severity Major

Page 27: OPERATING INSTRUCTIONS 2/1543-100/CSH 109 32/1 …docshare04.docshare.tips/files/25573/255734631.pdf · methodology, design and manufacturing. Ericsson shall have no liability for

ProbableCause PowerProblem

5.37 Power Failure (lower input port) SlaveMissing power at the DC lower connector.

SpecificProblem Power Failure (lower input connector) Slave

Source NE

AlarmType EnvironmentalAlarm

Severity Major

ProbableCause PowerProblem

5.38 PPP downFailure in the Data Communication Network (DCN) communication.

SpecificProblem PPP down

Source PPP

AlarmType CommunicationAlarm

Severity Minor

ProbableCause Unavailable

5.39 RAU Power Supply ChangedThe RAU power supply has changed automatically because the MMU has detected undervoltageor bad grounding.

SpecificProblem RAU power supply changed

Source MMU

AlarmType EquipmentAlarm

Severity Major

ProbableCause PowerProblem

Page 28: OPERATING INSTRUCTIONS 2/1543-100/CSH 109 32/1 …docshare04.docshare.tips/files/25573/255734631.pdf · methodology, design and manufacturing. Ericsson shall have no liability for

5.39.1 Consequences

DC bypass is turned off and the power supply provides the RAU with +57 V DC.

5.39.2 Corrective Actions

Repair the power supply unit or fix the grounding problem.

5.39.3 Alarm Clearance

The alarm is cleared when the MMU no longer detects undervoltage or bad grounding.

5.40 Radio Frame (Major)The receiver failed to synchronize the frame of the received composite bit stream due to signalfailure.

Applicable for RAU IF (1+1).

SpecificProblem Radio Frame

Source RAU IF

AlarmType CommunicationAlarm

Severity Major

ProbableCause LossOfFrame

5.41 Radio Frame (Critical)The receiver failed to synchronize the frame of the received composite bit stream due to signalfailure.

Applicable for RAU IF (1+0).

SpecificProblem Radio Frame

Source RAU IF

AlarmType CommunicationAlarm

Severity Critical

ProbableCause LossOfFrame

Page 29: OPERATING INSTRUCTIONS 2/1543-100/CSH 109 32/1 …docshare04.docshare.tips/files/25573/255734631.pdf · methodology, design and manufacturing. Ericsson shall have no liability for

5.42 Radio ID (Major)The received traffic comes from a terminal with an ID not matching the Far End ID. Possiblecauses for this is:

Wrong Radio ID has been set in either near-end or far-end terminal. The antenna alignment is incorrect and the near-end radio receives a signal from another

radio on the same frequency.

Applicable for RAU IF (1+1).

SpecificProblem Radio ID

Source RAU IF

AlarmType CommunicationAlarm

Severity Major

ProbableCause PathTraceMismatch

5.42.1 Consequences

The protection is lost.

5.42.2 Corrective Actions

Perform the following actions:

1. Check Radio ID on both near-end and far-end terminal2. If Radio ID is correct on both near-end and far-end, check antenna alignment.3. Perform an interference check by measuring input receive level when far-end transmitter

is turned off.

5.42.3 Alarm Clearance

The alarm is cleared when correct Radio ID is set, or if Remote ID check is disabled.

5.43 Radio ID (Critical)The received traffic comes from a terminal with an ID not matching the Far End ID. Possiblecauses for this is:

Wrong Radio ID has been set in either near-end or far-end terminal.

Page 30: OPERATING INSTRUCTIONS 2/1543-100/CSH 109 32/1 …docshare04.docshare.tips/files/25573/255734631.pdf · methodology, design and manufacturing. Ericsson shall have no liability for

The antenna alignment is incorrect and the near-end radio receives a signal from anotherradio.

Applicable for RAU IF (1+0).

SpecificProblem Radio ID

Source RAU IF

AlarmType CommunicationAlarm

Severity Critical

ProbableCause PathTraceMismatch

5.43.1 Consequences

No connection with far-end and traffic loss.

5.43.2 Corrective Actions

Perform the following actions:

1. Check Radio ID on both near-end and far-end terminal.2. If Radio ID is correct on both near-end and far-end, check antenna alignment.3. Perform an interference check by measuring input receive level when far-end transmitter

is turned off.

5.43.3 Alarm Clearance

The alarm is cleared when correct Radio ID is set, or if Remote ID check is disabled.

5.44 RCC (Major)Radio Communication Channel (RCC)

Communication is lost on the RCC, between the MINI-LINK CN 210 and the RAU.

SpecificProblem RCC

Source All MINI-LINK CN 210 units

AlarmType CommunicationAlarm

Severity Major

Page 31: OPERATING INSTRUCTIONS 2/1543-100/CSH 109 32/1 …docshare04.docshare.tips/files/25573/255734631.pdf · methodology, design and manufacturing. Ericsson shall have no liability for

ProbableCause Unavailable

5.44.1 Consequences

Transmitter is switched off which results in traffic loss.

5.45 Remote Tx Switch OverAn active radio switch ordered from far-end. Only valid in Hot Standby.

SpecificProblem Remote Tx Switch Over

Source SWITCH

AlarmType EquipmentAlarm

Severity Major

ProbableCause ProtectionPathFailure

5.46 Reserved PositionThe unit in this position is of a different type than the position is reserved for.

SpecificProblem Reserved Position

Source RAU

AlarmType EquipmentAlarm

Severity Critical

ProbableCause ReplaceableUnitTypeMismatch

5.47 RF Input Level (Major)The received Radio Frequency (RF) input signal level has dropped below the threshold for thereceiver.

Applicable for RF (1+1).

SpecificProblem RF Input Level

Source RF (1+1)

Page 32: OPERATING INSTRUCTIONS 2/1543-100/CSH 109 32/1 …docshare04.docshare.tips/files/25573/255734631.pdf · methodology, design and manufacturing. Ericsson shall have no liability for

AlarmType CommunicationAlarm

Severity Major

ProbableCause ReceiverFailure

5.48 RF Input Level (Critical)The received Radio Frequency (RF) input signal level has dropped below the threshold for thereceiver.

Applicable for RF (1+0).

SpecificProblem RF Input Level

Source RF

AlarmType CommunicationAlarm

Severity Critical

ProbableCause ReceiverFailure

5.49 RF Input ThresholdThe Radio Frequency (RF) input level has dropped below the RF Input Alarm Threshold.

SpecificProblem RF Input Threshold

Source o RFo SWITCH

AlarmType CommunicationAlarm

Severity Warning

ProbableCause DegradedSignal

5.50 RF Input Threshold ProtectionThe Radio Frequency (RF) input level of both receivers in a protected terminal has droppedbelow their respective RF Input Alarm Threshold.

Page 33: OPERATING INSTRUCTIONS 2/1543-100/CSH 109 32/1 …docshare04.docshare.tips/files/25573/255734631.pdf · methodology, design and manufacturing. Ericsson shall have no liability for

SpecificProblem RF Input Threshold Protection

Source SWITCH

AlarmType CommunicationAlarm

Severity Warning

ProbableCause DegradedSignal

5.51 RF Output Level (Major)A major degradation of transmitter output power is detected. Applicable for RAU IF (1+1)standby transmitter.

SpecificProblem RF Output Level

Source RF

AlarmType CommunicationAlarm

Severity Major

ProbableCause TransmitterFailure

5.52 RF Output Level (Critical)The receiver frequency synthesizer loop is unlocked. Applicable for RAU IF (1+0) and RAU IF(1+1) active transmitter.

SpecificProblem RF Output Level

Source RF

AlarmType CommunicationAlarm

Severity Critical

ProbableCause TransmitterFailure

5.53 Running configuration not acceptedThe MINI-LINK CN 210 or RAU could not accept the running configuration; the service LED isflashing. The unit could also be subject to a software upgrade.

Page 34: OPERATING INSTRUCTIONS 2/1543-100/CSH 109 32/1 …docshare04.docshare.tips/files/25573/255734631.pdf · methodology, design and manufacturing. Ericsson shall have no liability for

SpecificProblem Running configuration not accepted

Source o All MINI-LINK CN 210 unitso All RAUs

AlarmType EquipmentAlarm

Severity Major

ProbableCause ReplaceableUnitTypeMismatch

5.53.1 Corrective Actions

Remove board or clear reservation.

5.54 Rx AFCThe frequency of the received signal is outside the range of the Automatic Frequency Control(AFC) in the RAU receiver.

SpecificProblem Rx AFC

Source RF

AlarmType CommunicationAlarm

Severity Major

ProbableCause ReceiverFailure

5.55 RX Frequency (Major)The receiver frequency synthesizer loop is unlocked.

Applicable for RF (1+1).

SpecificProblem RX Frequency

Source RF (1+1)

AlarmType CommunicationAlarm

Severity Major

ProbableCause ReceiverFailure

Page 35: OPERATING INSTRUCTIONS 2/1543-100/CSH 109 32/1 …docshare04.docshare.tips/files/25573/255734631.pdf · methodology, design and manufacturing. Ericsson shall have no liability for

5.56 RX Frequency (Critical)The receiver frequency synthesizer loop is unlocked.

Applicable for RF (1+0).

SpecificProblem RX Frequency

Source RF (1+0)

AlarmType CommunicationAlarm

Severity Critical

ProbableCause ReceiverFailure

5.57 Rx IF InputFailure on the receiver Intermediate Frequency (IF) signal from the RAU to the MINI-LINK CN210.

SpecificProblem Rx IF Input

Source RAU IF

AlarmType CommunicationAlarm

Severity Major

ProbableCause ReceiverFailure

5.58 SES 15 min threshold crossingSeverely Errored Seconds (SES)

SES threshold crossing for 15 minutes composite performance monitoring.

Applicable for RAU IF (1+0).

Applicable for SWITCH (1+1).

SpecificProblem SES 15 min threshold crossing

Page 36: OPERATING INSTRUCTIONS 2/1543-100/CSH 109 32/1 …docshare04.docshare.tips/files/25573/255734631.pdf · methodology, design and manufacturing. Ericsson shall have no liability for

Source o RAU IFo SWITCH

AlarmType QualityOfServiceAlarm

Severity Major

ProbableCause ThresholdCrossed

5.59 SES 24 h threshold crossingSeverely Errored Seconds (SES)

SES threshold crossing for 24 hours composite performance monitoring.

Applicable for RAU IF (1+0).

Applicable for SWITCH (1+1).

SpecificProblem SES 24 h threshold crossing

Source o RAU IFo SWITCH

AlarmType QualityOfServiceAlarm

Severity Major

ProbableCause ThresholdCrossed

5.60 Squelch threshold reachedThe quality level of the synchronization reference has reached the Squelch quality level.

SpecificProblem Squelch threshold reached

Source NE

AlarmType CommunicationAlarm

Severity Critical

ProbableCause LossOfSynchronisation

Page 37: OPERATING INSTRUCTIONS 2/1543-100/CSH 109 32/1 …docshare04.docshare.tips/files/25573/255734631.pdf · methodology, design and manufacturing. Ericsson shall have no liability for

5.60.1 Consequences

The synchronization output signal is squelched.

5.60.2 Corrective Actions

No action required.

5.60.3 Alarm Clearance

The alarm is cleared when the synchronization reference reaches a quality level above theSquelch quality level.

5.61 TX Frequency (Major)Transmitter frequency synthesizer loop is unlocked.

Applicable for RAU IF (1+1).

SpecificProblem TX Frequency

Source RF

AlarmType CommunicationAlarm

Severity Major

ProbableCause TransmitterFailure

5.62 TX Frequency (Critical)Transmitter frequency synthesizer loop is unlocked.

Applicable for RAU IF (1+0).

SpecificProblem TX Frequency

Source RF

AlarmType CommunicationAlarm

Severity Critical

ProbableCause TransmitterFailure

Page 38: OPERATING INSTRUCTIONS 2/1543-100/CSH 109 32/1 …docshare04.docshare.tips/files/25573/255734631.pdf · methodology, design and manufacturing. Ericsson shall have no liability for

5.63 Tx IF Input (Major)Failure on the received Intermediate Frequency (IF) signal from the MINI-LINK CN 210 to theRAU.

Applicable for RAU IF (1+1).

SpecificProblem Tx IF Input

Source RAU IF

AlarmType Communication

Severity Major

ProbableCause TransmitterFailure

5.64 Tx IF Input (Critical)Failure on the received Intermediate Frequency (IF) signal from the MINI-LINK CN 210 to theRAU.

Applicable for RAU IF (1+0).

SpecificProblem Tx IF Input

Source RAU IF

AlarmType Communication

Severity Critical

ProbableCause TransmitterFailure

5.65 TX Switch Over

SpecificProblem TX Switch Over

Source SWITCH

AlarmType EquipmentAlarm

Severity Major

ProbableCause ProtectionPathFailure

Page 39: OPERATING INSTRUCTIONS 2/1543-100/CSH 109 32/1 …docshare04.docshare.tips/files/25573/255734631.pdf · methodology, design and manufacturing. Ericsson shall have no liability for

5.66 Unable to Protect: SWITCH (Major)The system is no longer able to provide protection of the radio side, due to:

A Tx alarm on one path. A common Tx/Rx alarm on one path. An Rx alarm on one path and the duration is longer than 200 s (default value).

SpecificProblem Unable to Protect

Source SWITCH

AlarmType EquipmentAlarm

Severity Major

ProbableCause ProtectionPathFailure

5.67 Unable to Protect: SWITCH (Critical)The system is no longer able to provide protection of the radio side, due to:

A Tx alarm on both paths. A common Tx/Rx alarm on both paths. An Rx alarm on both paths and the duration is longer than 200 s (default value).

SpecificProblem Unable to Protect

Source SWITCH

AlarmType EquipmentAlarm

Severity Critical

ProbableCause ProtectionPathFailure

5.68 Unavailable PeriodThe Plesiochronous Digital Hierarchy (PDH) Unavailable Period counter threshold has beencrossed, due to possible radio propagation problem.

Applicable for RAU IF (1+0).

Applicable for SWITCH (1+1).

Page 40: OPERATING INSTRUCTIONS 2/1543-100/CSH 109 32/1 …docshare04.docshare.tips/files/25573/255734631.pdf · methodology, design and manufacturing. Ericsson shall have no liability for

SpecificProblem Unavailable Period

Source o RAU IFo SWITCH

AlarmType QualityOfServiceAlarm

Severity Major

ProbableCause PerformanceDegraded

5.69 Unit Inaccessible: Slave MMUThe unit is not accessible.

SpecificProblem Unit Inaccessible

Source Slave MMU

AlarmType EquipmentAlarm

Severity Critical

ProbableCause Unavailable

5.70 Unit Inaccessible: RMMThe RMM is not accessible because of a fault or because no RMM is present.

SpecificProblem Unit Inaccessible

Source RMM

AlarmType EquipmentAlarm

Severity Minor

ProbableCause ReplaceableUnitProblem

5.70.1 Consequences

Entering the grace period, during which all optional features are granted.

5.70.2 Corrective Actions

Page 41: OPERATING INSTRUCTIONS 2/1543-100/CSH 109 32/1 …docshare04.docshare.tips/files/25573/255734631.pdf · methodology, design and manufacturing. Ericsson shall have no liability for

Replace the RMM, see Replacing an RMM.

5.70.3 Alarm Clearance

The alarm is cleared when access to the RMM has been restored.

5.71 Unsupported RMM variant - connect FTP server anddo upgradeThe hardware variant of the RMM is not supported by the software.

SpecificProblem Unsupported RMM variant - connect FTP server and do upgrade

Source RMM

AlarmType EquipmentAlarm

Severity Minor

ProbableCause SoftwareEnvironment

5.71.1 Consequences

Entering the grace period, during which all optional features are granted.

5.71.2 Corrective Actions

Upgrade the software to a version that supports the new RMM hardware variant, see Upgradingor Downgrading a SW Load Module.

5.71.3 Alarm Clearance

The alarm is cleared when the software has been upgraded to a version that supports the newRMM hardware variant.

5.72 Unsupported Unit TypeThe unit type is not supported by the software.

SpecificProblem Unsupported Unit Type

Source o RAU

AlarmType EquipmentAlarm

Page 42: OPERATING INSTRUCTIONS 2/1543-100/CSH 109 32/1 …docshare04.docshare.tips/files/25573/255734631.pdf · methodology, design and manufacturing. Ericsson shall have no liability for

Severity Critical

ProbableCause ReplaceableUnitTypeMismatch

5.73 Missing LicenseThe License is missing.

SpecificProblem Missing License

Source NE

AlarmType OperationalViolation

Severity Critical

ProbableCause DenialOfService

5.74 User I/OThe Specific Problem and Severity can be found on the User I/O Ports page

SpecificProblem User input

Source User Input

AlarmType EnvironmentalAlarm

Severity User Defined

ProbableCause

Reference List[1] Accessing a Network Element, 59/1543-100/CSH 109 32/1-V3[2] Fault Management Operations, 1/1543-100/CSH 109 32/1-V3[3] Installing Outdoor Equipment, 19/1531-100/CSH 109 32/1-V3[4] MINI-LINK Craft User Interface Descriptions, 22/1551-100/CSH 109 32/1-V3[5] Personal Health and Safety Information, 124 46-2886[6] Replacing a MINI-LINK CN 210, 7/1543-100/CSH 109 32/1-V3[7] Replacing an RMM, 9/1543-100/CSH 109 32/1-V3

Page 43: OPERATING INSTRUCTIONS 2/1543-100/CSH 109 32/1 …docshare04.docshare.tips/files/25573/255734631.pdf · methodology, design and manufacturing. Ericsson shall have no liability for

[8] Replacing a Radio Unit, 10/1543-100/CSH 109 32/1-V3[9] Supplementary Safety Information for MINI-LINK, 124 46-HSD 101 16/2[10] System Safety Information, 124 46-2886[11] Upgrading or Downgrading a SW Load Module, 58/1543-100/CSH 109 32/1-V3

Alarm Descriptions MINI-LINK CN 210 ETSI