Page 1

Alarm Descriptions MINI-LINK TN ETSI

OPERATING INSTRUCTIONS

5/1543-CSH 109 32/1-V1 Uen M


Copyright Š Copyright Ericsson AB 2008–2010. All rights reserved. Disclaimer No part of this document may be reproduced in any form without the written permission of the copyright owner. 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 errors or damage of any kind resulting from the use of this document. Abstract This document describes the alarms handled in the MINI-LINK TN R4 in terms of definition, causes and suggested recovery action to be taken in order to remove the alarm causes.

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Contents

Contents 1

Introduction

1

2

Safety Information

3

3

Preparations

5

3.1

Additional Preparations

5

4

Overview

7

4.1

Consequences

7

4.2

Alarm Analysis

7

4.3

Corrective Actions

7

4.4

Alarm Clearance

8

5

Alarms

9

5.1

AIS (Minor)

9

5.2

AIS (Major)

9

5.3

AIS (Critical)

10

5.4

AIS on Protection Line

10

5.5

AMS 15 min threshold crossing

10

5.6

AMS 24 h threshold crossing

11

5.7

ATPC Capability

12

5.8

ATPC Capability (Far End)

13

5.9

B1 BBE 15 min threshold crossing

14

5.10

B1 BBE 24 h threshold crossing

15

5.11

B1 ES 15 min threshold crossing

16

5.12

B1 ES 24 h threshold crossing

17

5.13

B1 SES 15 min threshold crossing

18

5.14

B1 SES 24 h threshold crossing

19

5.15

B1 Unavailable Period

20

5.16

BBE 15 min threshold crossing

21

5.17

BBE 24 h threshold crossing

22

5.18

BER (Major)

23

5.19

BER (Critical)

23

5.20

Blocked (Far End)

24

5.21

BR Pressed

25

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarm Descriptions

5.22

Carrier Recovery Loss (Major)

26

5.23

Carrier Recovery Loss (Critical)

27

5.24

Clock Loss Of Reference

28

5.25

CLOS

29

5.26

Configuration Aborted

29

5.27

Configuration Failure (Far-End)

30

5.28

Control System Failure (Minor)

30

5.29

Control System Failure (Major)

31

5.30

CTRLOR

31

5.31

Default configuration not accepted

32

5.32

DEG (Minor)

32

5.33

DEG (Major)

33

5.34

DEGFCS

34

5.35

Degraded service: HDLC or IM Group

34

5.36

Degraded service: IM Group

35

5.37

DEGTHEC

35

5.38

Dmod Clock (Major)

36

5.39

Dmod Clock (Critical)

36

5.40

Early Warning

37

5.41

EOSMISSING

38

5.42

EOSMULTIPLE

39

5.43

Equipment error or no holdover capable board provider

39

5.44

ES 15 min threshold crossing

39

5.45

ES 24 h threshold crossing

40

5.46

Ethernet Down (Minor)

41

5.47

Ethernet Down (Critical)

42

5.48

EXC

43

5.49

Excessive Temperature

43

5.50

EXM

44

5.51

FAL <Number> License Missing - <KeyProductName> (Major)

45

5.52

FAL <Number> License Missing (Critical)

45

5.53

FOPR

45

5.54

Free running mode entered

46

5.55

GIDERR

46

5.56

Group Timing Mismatch

47

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarm Descriptions

5.57

Hardware Error: FAU

47

5.58

Hardware Error: Plug-in Unit (Minor)

48

5.59

Hardware Error: Plug-in Unit (Major)

49

5.60

Hardware Error: Plug-in Unit (Critical)

49

5.61

Hardware Error: RAU

50

5.62

Hardware Error: SFP (Major)

50

5.63

Hardware Error: SFP (Critical)

51

5.64

HCC

52

5.65

High BER (Major)

52

5.66

High BER (Critical)

53

5.67

High Temperature

55

5.68

Hitless Phase

56

5.69

Holdover mode entered

56

5.70

ICC

56

5.71

IF LOS R2L (Major)

57

5.72

IF LOS R2L (Critical)

58

5.73

In Repair

59

5.74

Incompatible Units: Plug-in Unit

59

5.75

Incompatible Units: RAU

59

5.76

Insufficient links

60

5.77

Insufficient links (Far-End)

60

5.78

Insufficient resources

61

5.79

Inter MMU Channel Failure

62

5.80

LCASCRC

62

5.81

LFD

62

5.82

Link Fault

63

5.83

Link OAM Loopback

64

5.84

LOA

64

5.85

LOF (Critical)

65

5.86

LOF: RS (Critical)

65

5.87

LOF L2R (Major)

66

5.88

LOF L2R (Critical)

67

5.89

LOF R2L (Major)

67

5.90

LOF R2L (Critical)

69

5.91

LOM

70

5.92

LOMF (Major)

71

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarm Descriptions

5.93

LOMF (Critical)

71

5.94

LOP (Major)

71

5.95

LOP (Critical)

72

5.96

LOS: RAU IF (Major)

72

5.97

LOS (Critical)

73

5.98

LOS: RAU IF (Critical)

73

5.99

LOS: SpiElectrical or SpiOptical (Critical)

74

5.100

LOS L2R (Major)

74

5.101

LOS L2R (Critical)

75

5.102

Loss of Cell Delineation: ATM

75

5.103

Loss of Cell Delineation: IMA Link

76

5.104

Loss of Delay Synchronization

77

5.105

Loss of IMA Frame

78

5.106

Loss of keep alive

78

5.107

Loss of network reference redundancy

79

5.108

Low BER

79

5.109

Low Input Voltage

79

5.110

Lower Layer Down

80

5.111

Missing License

80

5.112

Mod Index

80

5.113

Mode Mismatch

80

5.114

No holdover protection

81

5.115

No Traffic Possible

81

5.116

Node Installation

81

5.117

NONLCAS

82

5.118

Not able to find RMM

82

5.119

NPU Installation

83

5.120

OSPF LSA database overload

83

5.121

PFM

84

5.122

PLCR

84

5.123

PLCT

85

5.124

PLM (Major)

85

5.125

PLM (Critical)

86

5.126

Power Failure (lower input)

86

5.127

PPP down

87

5.128

PTM

87

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarm Descriptions

5.129

Radio Frame (Major)

87

5.130

Radio Frame (Critical)

88

5.131

Radio ID (Major)

88

5.132

Radio ID (Critical)

89

5.133

RAI

90

5.134

RCC (Major)

90

5.135

RCC (Critical)

90

5.136

RDI (Minor)

91

5.137

RDI (Major)

91

5.138

Remote Failure Indication

92

5.139

Remote Tx Switch Over

93

5.140

Reserved Position

93

5.141

RF Input Level (Major)

94

5.142

RF Input Level (Critical)

94

5.143

RF Input Threshold

94

5.144

RF Input Threshold Protection

95

5.145

RF Output Level (Major)

95

5.146

RF Output Level (Critical)

95

5.147

RF Output Level ATPC

95

5.148

RL-IME Degraded Service

96

5.149

RL-IME No Traffic

97

5.150

RL-IME Reassembly Failure

97

5.151

Running configuration not accepted

97

5.152

Rx AFC

98

5.153

RX Frequency (Major)

98

5.154

RX Frequency (Critical)

98

5.155

Rx IF Input

99

5.156

Rx Link Misconnected

99

5.157

Rx Unusable (Far-End)

100

5.158

SES 15 min threshold crossing

100

5.159

SES 24 h threshold crossing

101

5.160

SFP LOS (Major)

101

5.161

SFP LOS (Critical)

102

5.162

SQM

102

5.163

SQMULTIPLE

103

5.164

SQNC

103

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarm Descriptions

5.165

SQNONCONT

104

5.166

SQOR

104

5.167

Squelch threshold reached

104

5.168

Starting up (Far-End)

105

5.169

TIM (Major)

105

5.170

TIM (Critical)

106

5.171

TIM Line Side

107

5.172

TIM Radio Side

107

5.173

TLCR

108

5.174

TLCT

108

5.175

Traffic System Failure (Major)

109

5.176

Traffic System Failure (Critical)

109

5.177

TULOM

109

5.178

TX Frequency (Major)

110

5.179

TX Frequency (Critical)

110

5.180

Tx IF Input (Major)

110

5.181

Tx IF Input (Critical)

111

5.182

Tx Link Misconnected

111

5.183

TX Switch Over

112

5.184

Tx Unusable (Far-End)

112

5.185

Unable to Protect: E1 (Minor)

113

5.186

Unable to Protect: E1 (Critical)

113

5.187

Unable to Protect: LPS (Major)

113

5.188

Unable to Protect: LPS (Critical)

113

5.189

Unable to Protect: MSP (Minor)

114

5.190

Unable to Protect: MSP (Critical)

115

5.191

Unable to Protect: SWITCH (Major)

115

5.192

Unable to Protect: SWITCH (Critical)

116

5.193

Unavailable Period

116

5.194

Unavailable State

117

5.195

Unavailable State Far End

117

5.196

Unequipped (Major)

118

5.197

Unequipped (Critical)

119

5.198

Unit Inaccessible

119

5.199

Unit Removed

120

5.200

Unsupported Unit Type

120

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarm Descriptions

5.201

UPM

120

5.202

User input

121

5.203

Wrong NPU Software

121

5.204

Wrong Position

121

5.205

Wrong Software: Plug-in Unit

122

5.206

WST LOS L2R (Major)

122

5.207

WST LOS L2R (Critical)

122

5.208

WST LOS R2L (Major)

123

5.209

WST LOS R2L (Critical)

123

5.210

XPIC Cable Disconnected

124

5.211

XPIC LOS

124

Reference List

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

127


Alarm Descriptions

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Introduction

1

Introduction This document describes the alarms for MINI-LINK TN R4. It also proposes actions to be taken upon reception of an alarm.

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

1


Alarm Descriptions

2

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Safety Information

2

Safety Information Make sure that the information in the following documents has been understood by the persons performing the procedures: • Personal Health and Safety Information, Reference [8] • System Safety Information, Reference [17] • Supplementary Safety Information for MINI-LINK, Reference [16]

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

3


Alarm Descriptions

4

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Preparations

3

Preparations This section presents the preparations needed for a successful completion of the procedures in this instruction.

3.1

Additional Preparations Consider the following additional preparations: â&#x20AC;˘

Read through all applicable sections and make sure referenced documents are available.

â&#x20AC;˘

Make sure you have access to the NE using MINI-LINK Craft. For more information, see Accessing a Network Element, Reference [1].

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

5


Alarm Descriptions

6

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Overview

4

Overview Each alarm section begins with a short description of the alarm. The following information is also 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 Management Operations, Reference [2].

Severity

The severity of the alarm, for example, Critical or Minor. All severities are described in Fault Management Operations, Reference [2].

ProbableCause

The probable cause of the alarm.

The caption of each alarm section can contain tree parts: Specific Problem, Source, and Severity. Only the parts that are necessary to specify a unique alarm are included in each heading. For example, the caption of the alarm Hardware Error, with source equal to plug-in unit and severity equal to critical, is named ‘‘Hardware Error: Plug-in Unit (Critical)’’. Optionally, the list with information from the Notification List in MINI-LINK Craft is followed by subsections that describe the alarm in more detail, see below.

4.1

Consequences Section that describes what else has happened as a result of this alarm, informs if a switch has occurred, and if there are any masked alarms.

4.2

Alarm Analysis Section describing how to find the root cause of the alarm.

4.3

Corrective Actions Section that describes which actions can be taken in order to recover the system.

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

7


Alarm Descriptions

4.4

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

8

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

5

Alarms This section describes all alarms listed alphabetically.

5.1

AIS (Minor) Alarm Indication Signal (AIS) An AIS is detected on the incoming traffic.

5.2

SpecificProblem

AIS

Source

• • • • •

AlarmType

CommunicationAlarm

Severity

Minor

ProbableCause

AlarmIndicationSignal

E1 E2/E3 MS/RS VC-12 VC-4

AIS (Major) Alarm Indication Signal (AIS) An AIS is detected on the incoming traffic. Probable causes are: •

Transmission error due to severe problem outside this NE.

The signal is replaced by the AIS signal as a consequent action of the detection of certain near-end defects.

SpecificProblem

AIS

Source

• • • • • • •

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

AU4 MS TU-3 TU-12 VC-3 VC-4 VC-12

9


Alarm Descriptions

5.2.1

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

AlarmIndicationSignal

Consequences Service unavailable.

5.2.2

Corrective Actions Cease the particular transmission error.

5.3

AIS (Critical) Alarm Indication Signal (AIS) An AIS is detected on the incoming traffic.

5.4

5.5

SpecificProblem

AIS

Source

Framed E1

AlarmType

CommunicationAlarm

Severity

Critical

ProbableCause

AlarmIndicationSignal

AIS on Protection Line SpecificProblem

AIS

Source

E1

AlarmType

CommunicationAlarm

Severity

Minor

ProbableCause

Indeterminate

AMS 15 min threshold crossing Adaptive Modulation Seconds (AMS) The terminal has been using the minimum modulation longer time than the configured 15 minute threshold. The threshold has been crossed during the current 15 minute interval.

10

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

Applicable for RAU IF (1+0). Applicable for SWITCH (1+1).

5.5.1

SpecificProblem

AMS 15 m threshold crossing

Source

• •

AlarmType

QualityOfServiceAlarm

Severity

Minor

ProbableCause

ThresholdCrossed

RAU IF (1+0) SWITCH

Consequences Decreased traffic capacity for a longer time than expected.

5.5.2

Corrective Actions The problem may be temporary, but if the alarm continues over consecutive 15 min intervals, try the following actions: 1. Verify the Radio Frequency (RF) input power level: it must be above the 10-6 Bit Error Ratio (BER) threshold (at least 5 dB) during good weather conditions. 2. Check the antenna alignment, see Installing Outdoor Equipment, Reference [4]. 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.5.3

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

5.6

AMS 24 h threshold crossing Adaptive Modulation Seconds (AMS) The terminal has been using the minimum modulation longer time than the configured 24 hour threshold. Applicable for RAU IF (1+0).

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

11


Alarm Descriptions

Applicable for SWITCH (1+1).

5.6.1

SpecificProblem

AMS 24 h threshold crossing

Source

• •

AlarmType

QualityOfServiceAlarm

Severity

Minor

ProbableCause

ThresholdCrossed

RAU IF (1+0) SWITCH

Consequences Decreased traffic capacity for a longer time than expected.

5.6.2

Corrective Actions Try the following actions: 1. Verify the Radio Frequency (RF) input power level: it must be above the 10-6 Bit Error Ratio (BER) threshold (at least 5 dB) during good weather conditions. 2. Check the antenna alignment, see Installing Outdoor Equipment, Reference [4]. 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.6.3

Alarm Clearance The alarm is not cleared automatically. To clear it do a warm restart, see Troubleshooting, Reference [18].

5.7

ATPC Capability Automatic Transmit Power Control (ATPC) The terminal is configured for ATPC, but the RAU does not support ATPC. This alarm is activated only if ATPC is turned on (any direction).

12

SpecificProblem

ATPC Capability

Source

RAU

AlarmType

EquipmentAlarm

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

5.7.1

Severity

Major

ProbableCause

ReplacebleUnitTypeMismatch

Consequences It is not possible to use ATPC functionality.

5.7.2

Corrective Actions Replace the RAU to one with ATPC support, see Replacing a Radio Unit, Reference [14].

5.7.3

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

5.8

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 plug-in units does not support ATPC.

5.8.1

SpecificProblem

ATPC Capability (Far End)

Source

All MMUs

AlarmType

EquipmentAlarm

Severity

Major

ProbableCause

ReplacebleUnitTypeMismatch

Consequences It is not possible to enable ATPC functionality.

5.8.2

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

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

13


Alarm Descriptions

5.8.3

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

5.9

B1 BBE 15 min threshold crossing Background Block Error (BBE) The Synchronous Digital Hierarchy (SDH) BBE counter threshold, set for 15 min time windows, has been crossed the last 15 minutes. The BBE represents the number of Synchronous Transport Module level 1 (STM-1) frames containing at least one error, and is computed by the MMU when the operator enables G.826 performance monitoring. The alarm is raised when the BBE counter value crosses the BBE threshold set by the operator. This value has been configured within the G.826 performance 15 minutes monitoring options.

5.9.1

SpecificProblem

B1 BBE 15 min threshold crossing

Source

RADIO RS

AlarmType

QualityOfServiceAlarm

Severity

Major

ProbableCause

ThresholdCrossed

Consequences Degraded traffic.

5.9.2

Corrective Actions The problem may be temporary, but if the alarm continues over consecutive 15 min intervals, try the following actions: 1. Check if obstacles are placed in the radio path between the two hopsâ&#x20AC;&#x2122; antennas (at clear sky conditions). 2. Verify that the received signal power is as expected (by preforming a link budget calculation). 3. Check that no interference signal is present. 4. Replace the MMU, see Replacing an MMU, Reference [11] or Replacing an MMU2 CS, Reference [12]. 5. Replace the RAU, see Replacing a Radio Unit, Reference [14].

14

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

5.9.3

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

5.10

B1 BBE 24 h threshold crossing Background Block Error (BBE) The Synchronous Digital Hierarchy (SDH) BBE counter threshold, set for 24 h time windows, has been crossed the last 24 hours. The BBE represents the number of Synchronous Transport Module level 1 (STM-1) frames containing at least one error, and is computed by the MMU when the operator enables G.826 performance monitoring. The alarm is raised when the BBE counter value crosses the BBE threshold set by the operator. This value has been configured within the G.826 performance 24 hours monitoring options.

5.10.1

SpecificProblem

B1 BBE 24 h threshold crossing

Source

RADIO RS

AlarmType

QualityOfServiceAlarm

Severity

Major

ProbableCause

ThresholdCrossed

Consequences Degraded traffic.

5.10.2

Corrective Actions The problem may be temporary, but if the alarm continues over consecutive 24 h intervals, try the following actions: 1. Check if obstacles are placed in the radio path between the two hopsâ&#x20AC;&#x2122; antennas (at clear sky conditions). 2. Verify that the received signal power is as expected (by preforming a link budget calculation). 3. Check that no interference signal is present. 4. Replace the MMU, see Replacing an MMU, Reference [11] or Replacing an MMU2 CS, Reference [12]. 5. Replace the RAU, see Replacing a Radio Unit, Reference [14].

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

15


Alarm Descriptions

5.10.3

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

5.11

B1 ES 15 min threshold crossing Errored Seconds (ES) The Synchronous Digital Hierarchy (SDH) ES counter threshold, set for 15 min time windows, has been crossed the last 15 minutes. The ES represents a second in which one or more Synchronous Transport Module level 1 (STM-1) frames contain at least one error, and is computed by the MMU when the operator enables G.826 performance monitoring. The alarm is raised when the ES counter value crosses the ES threshold set by the operator. This value has been configured within the G.826 performance 15 minutes monitoring options.

5.11.1

SpecificProblem

B1 ES 15 min threshold crossing

Source

RADIO RS

AlarmType

QualityOfServiceAlarm

Severity

Minor

ProbableCause

ThresholdCrossed

Consequences This alarm indicates degraded traffic. If the problem continues, it may lead to B1 SES 15 min threshold crossing, see Section 5.13 on page 18.

5.11.2

Corrective Actions The problem may be temporary, but if the alarm continues over consecutive 15 min intervals, try the following actions: 1. Check if obstacles are placed in the radio path between the two hopsâ&#x20AC;&#x2122; antennas (at clear sky conditions). 2. Verify that the received signal power is as expected (by preforming a link budget calculation). 3. Check that no interference signal is present. 4. Replace the MMU, see Replacing an MMU, Reference [11] or Replacing an MMU2 CS, Reference [12]. 5. Replace the RAU, see Replacing a Radio Unit, Reference [14].

16

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

5.11.3

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

5.12

B1 ES 24 h threshold crossing Errored Seconds (ES) The Synchronous Digital Hierarchy (SDH) ES counter threshold, set for 24 h time windows, has been crossed. The ES represents a second in which one or more Synchronous Transport Module level 1 (STM-1) frames contain at least one error, and is computed by the TRU when the operator enables G.826 performance monitoring. The alarm is raised when the ES counter value crosses the ES threshold set by the operator. This value has been configured within the G.826 performance 24 hours monitoring options.

5.12.1

SpecificProblem

B1 ES 24 h threshold crossing

Source

RADIO RS

AlarmType

QualityOfServiceAlarm

Severity

Minor

ProbableCause

ThresholdCrossed

Consequences This alarm indicates degraded traffic. If the problem continues, it may lead to B1 SES 24 h threshold crossing, see Section 5.14 on page 19.

5.12.2

Corrective Actions The problem may be temporary, but if the alarm continues over consecutive 24 h intervals, try the following actions: 1. Check if obstacles are placed in the radio path between the two hopsâ&#x20AC;&#x2122; antennas (at clear sky conditions). 2. Verify that the received signal power is as expected (by preforming a link budget calculation). 3. Check that no interference signal is present. 4. Replace the MMU, see Replacing an MMU, Reference [11] or Replacing an MMU2 CS, Reference [12]. 5. Replace the RAU, see Replacing a Radio Unit, Reference [14].

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

17


Alarm Descriptions

5.12.3

Alarm Clearance The alarm is cleared at the next 24 hour interval where the ES counter threshold no longer is crossed.

5.13

B1 SES 15 min threshold crossing Severely Errored Seconds (SES) The Synchronous Digital Hierarchy (SDH) SES counter threshold, set for 15 min time windows, has been crossed. The SES represents a second in which more than 30% of the Synchronous Transport Module level 1 (STM-1) frames contain at least one error, and is computed by the MMU when the operator enables G.826 performance monitoring. The alarm is raised when the SES counter value crosses the SES threshold set by the operator. This value has been configured within the G.826 performance 15 minutes monitoring options.

5.13.1

SpecificProblem

B1 SES 15 min threshold crossing

Source

RADIO RS

AlarmType

QualityOfServiceAlarm

Severity

Major

ProbableCause

ThresholdCrossed

Consequences Degraded traffic.

5.13.2

Corrective Actions Try the following actions: 1. Check if obstacles are placed in the radio path between the two hopsâ&#x20AC;&#x2122; antennas (at clear sky conditions). 2. Verify that the received signal power is as expected (by preforming a link budget calculation). 3. Check that no interference signal is present. 4. Replace the MMU, see Replacing an MMU, Reference [11] or Replacing an MMU2 CS, Reference [12]. 5. Replace the RAU, see Replacing a Radio Unit, Reference [14].

18

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

5.13.3

Alarm Clearance The alarm is cleared at the next 15 minutes interval where the SES counter threshold no longer is crossed.

5.14

B1 SES 24 h threshold crossing Severely Errored Seconds (SES) The Synchronous Digital Hierarchy (SDH) SES counter threshold, set for 24 h time windows, has been crossed. The SES represents a second in which more than 30% of the Synchronous Transport Module level 1 (STM-1) frames contain at least one error, and is computed by the MMU when the operator enables G.826 performance monitoring. The alarm is raised when the SES counter value crosses the SES threshold set by the operator. This value has been configured within the G.826 performance 24 hours monitoring options.

5.14.1

SpecificProblem

B1 SES 24 h threshold crossing

Source

RADIO RS

AlarmType

QualityOfServiceAlarm

Severity

Major

ProbableCause

ThresholdCrossed

Consequences Degraded traffic.

5.14.2

Corrective Actions Try the following actions: 1. Check if obstacles are placed in the radio path between the two hopsâ&#x20AC;&#x2122; antennas (at clear sky conditions). 2. Verify that the received signal power is as expected (by preforming a link budget calculation). 3. Check that no interference signal is present. 4. Replace the MMU, see Replacing an MMU, Reference [11] or Replacing an MMU2 CS, Reference [12]. 5. Replace the RAU, see Replacing a Radio Unit, Reference [14].

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

19


Alarm Descriptions

5.14.3

Alarm Clearance The alarm is cleared at the next 24 hour interval where the SES counter threshold no longer is crossed.

5.15

B1 Unavailable Period The Synchronous Digital Hierarchy (SDH) Unavailable Period counter threshold has been crossed. The hop is in unavailability status, since 10 consecutive Severely Errored Seconds (SES) have been detected.

5.15.1

SpecificProblem

B1 Unavailable Period

Source

RADIO RS

AlarmType

QualityOfServiceAlarm

Severity

Major

ProbableCause

PerformanceDegraded

Consequences Traffic Loss.

5.15.2

Corrective Actions Perform the following actions: 1. Check if obstacles are placed in the radio path between the two hopâ&#x20AC;&#x2122;s antennas (at clear sky conditions). 2. Verify that the received signal power is as expected (by preforming a link budget calculation). 3. Check that no interference signal is present. 4. Replace the MMU, see Replacing an MMU, Reference [11] or Replacing an MMU2 CS, Reference [12]. 5. Replace the RAU, see Replacing a Radio Unit, Reference [14].

5.15.3

Alarm Clearance The alarm is cleared when the hop exits from the unavailability status. This happens when 10 consecutive non-SES are detected.

20

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

5.16

BBE 15 min threshold crossing Background Block Error (BBE) BBE threshold crossing for 15 min composite performance monitoring. The alarm is raised when the BBE counter value crosses the BBE threshold set by the operator. Applicable for RAU IF (1+0). Applicable for SWITCH (1+1).

5.16.1

SpecificProblem

BBE 15 min threshold crossing

Source

• •

AlarmType

QualityOfServiceAlarm

Severity

Major

ProbableCause

ThresholdCrossed

RAU IF (1+0) SWITCH

Consequences Degraded traffic.

5.16.2

Corrective Actions The problem may be temporary, but if the alarm continues over consecutive 15 min intervals, try the following actions: 1. Check if obstacles are placed in the radio path between the two hops’ antennas (at clear sky conditions). 2. Verify that the received signal power is as expected (by preforming a link budget calculation). 3. Check that no interference signal is present. 4. Replace the MMU, see Replacing an MMU, Reference [11] or Replacing an MMU2 CS, Reference [12]. 5. Replace the RAU, see Replacing a Radio Unit, Reference [14].

5.16.3

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

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

21


Alarm Descriptions

5.17

BBE 24 h threshold crossing Background Block Error (BBE) BBE threshold crossing for 24 hour composite performance monitoring. The alarm is raised when the BBE counter value crosses the BBE threshold set by the operator. Applicable for RAU IF (1+0). Applicable for SWITCH (1+1).

5.17.1

SpecificProblem

BBE 24 h threshold crossing

Source

• •

AlarmType

QualityOfServiceAlarm

Severity

Major

ProbableCause

ThresholdCrossed

RAU IF (1+0) SWITCH

Consequences Degraded traffic.

5.17.2

Corrective Actions The problem may be temporary, but if the alarm continues over consecutive 24 h intervals, try the following actions: 1. Check if obstacles are placed in the radio path between the two hops’ antennas (at clear sky conditions). 2. Verify that the received signal power is as expected (by preforming a link budget calculation). 3. Check that no interference signal is present. 4. Replace the MMU, see Replacing an MMU, Reference [11] or Replacing an MMU2 CS, Reference [12]. 5. Replace the RAU, see Replacing a Radio Unit, Reference [14].

5.17.3

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

22

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

5.18

BER (Major) Bit Error Ratio (BER) The BER calculated by the Forward Error Correction (FEC) for the received signal has exceeded the BER alarm threshold. The incoming signal is so corrupt that the FEC is unable to correct the incoming traffic. Applicable for RAU IF (1+1).

5.18.1

SpecificProblem

BER

Source

RAU IF

AlarmType

Communication

Severity

Major

ProbableCause

DegradedSignal

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

5.18.2

Corrective Actions Check if obstacles are placed in the radio path between the two hopsâ&#x20AC;&#x2122; antennas (at clear sky conditions). 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, Reference [4].

5.18.3

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

5.19

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

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

23


Alarm Descriptions

Applicable for RAU IF (1+0).

5.19.1

SpecificProblem

BER

Source

RAU IF

AlarmType

Communication

Severity

Critical

ProbableCause

DegradedSignal

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

5.19.2

Corrective Actions Check if obstacles are placed in the radio path between the two hopsâ&#x20AC;&#x2122; antennas (at clear sky conditions). 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, Reference [4].

5.19.3

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

5.20

Blocked (Far End) The far-end Inverse Multiplexer over ATM (IMA) group has been blocked (inhibited by the Management System).

24

SpecificProblem

Blocked (Far End)

Source

IMA Group

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

RemoteAlarmInterface

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

5.20.1

Consequences No Asynchronous Transfer Mode (ATM) traffic can be transmitted over the specific IMA group before both the near-end and far-end groups become operational.

5.20.2

Corrective Actions Unblock the far-end group.

5.20.3

Alarm Clearance The alarm is cleared when far-end IMA group has been unblocked.

5.21

BR Pressed Board Removal (BR) button has been pressed, which is a request to take the plug-in unit out of service. The plug-in unit may then be removed. The BR button must always be pressed before removing a plug-in unit, otherwise, the NE might show unstable behavior.

5.21.1

SpecificProblem

BR Pressed

Source

Plug-in Unit

AlarmType

EquipmentAlarm

Severity

Critical

ProbableCause

ReplacableUnitProblem

Consequences The BR (yellow) LED is ON. The plug-in unit gets operational status Out of Service and all traffic-related alarms for this plug-in unit will be disabled. For information on the location of the BR button and BR LED, see LED Descriptions, Reference [5].

5.21.2

Corrective Actions If the plug-in unit should be removed permanently, follow the instructions in Removing a Plug-In Unit, Reference [9]. If the plug-in unit should be replaced by another unit with the same functionality, follow the instructions in the relevant Replacing document.

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

25


Alarm Descriptions

5.21.3

Alarm Clearance The alarm is cleared when the plug-in unit has been removed. The alarm is also cleared if the BR button is pressed once again.

5.22

Carrier Recovery Loss (Major) The Synchronous Digital Hierarchy (SDH) carrier signal cannot be recovered at the demodulator. The 140 MHz spectrum coming from the receiving RAU is too low or too corrupted to lock the carrier. It is generally caused by deep fading. The alarm can also be caused by the following events:

5.22.1

â&#x20AC;˘

Transmission problem on the hop other side Tx.

â&#x20AC;˘

Deep fading on the radio path.

SpecificProblem

Carrier Recovery Loss

Source

RAU IF (1+1)

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

ReceiverFailure

Consequences The system switches on the standby faultless MMU.

5.22.2

Corrective Actions Perform the following actions: 1. Verify that the transmitter on hop other side is correctly working. 2. Verify the frequency settings on the Tx and Rx. 3. Verify the Radio Frequency (RF) input power level: it must be above the 10-6 Bit Error Ratio (BER) threshold (at least 5 dB). 4. Increase the RF input power level (if possible) by acting on the far-end output power. 5. Check the antenna alignment, see Installing Outdoor Equipment, Reference [4]. 6. Verify the link budget calculation. 7. Check for presence of RF interferers.

26

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

8. Check for presence of Intermediate Frequency (IF) interferers (and eventually the RF coaxial cable shielding). 9. Evaluate the presence of selective (multi-path) fading. 10. Perform an IF loop on the MMU, see Fault Management Operations, Reference [2]. If the alarm is still present then replace the active MMU, see Replacing an MMU, Reference [11] or Replacing an MMU2 CS, Reference [12]. 11. Perform an RF loop on the RAU, see Fault Management Operations, Reference [2]. If the alarm is still present then replace the active RAU, see Replacing a Radio Unit, Reference [14]. 12. Execute troubleshooting as step 10 and 11 on the far-end and act consequently.

5.22.3

Alarm Clearance The alarm is cleared when a good quality signal is received.

5.23

Carrier Recovery Loss (Critical) The Synchronous Digital Hierarchy (SDH) carrier signal cannot be recovered at the demodulator. The 140 MHz spectrum coming from the receiving RAU is too low or too corrupted to lock the carrier. It is generally caused by deep fading. The alarm can also be caused by the following events:

5.23.1

â&#x20AC;˘

Transmission problem on the hop other side Tx

â&#x20AC;˘

Deep fading on the radio path

SpecificProblem

Carrier Recovery Loss

Source

RAU IF (1+0)

AlarmType

CommunicationAlarm

Severity

Critical

ProbableCause

ReceiverFailure

Consequences Traffic is lost on the line side and an Alarm Indication Signal (AIS) is sent.

5.23.2

Corrective Actions Perform the following actions:

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

27


Alarm Descriptions

1. Verify that the transmitter on hop other side is correctly working. 2. Verify the frequency settings on the Tx and Rx. 3. Verify the Radio Frequency (RF) input power level: it must be above the 10-6 Bit Error Ratio (BER) threshold (at least 5 dB). 4. Increase the RF input power level (if possible) by acting on the far-end output power. 5. Check the antenna alignment, see Installing Outdoor Equipment, Reference [4]. 6. Verify the link budget calculation. 7. Check for presence of RF interferers. 8. Check for presence of Intermediate Frequency (IF) interferers (and eventually the RF coaxial cable shielding). 9. Evaluate the presence of selective (multi-path) fading. 10. Perform an IF loop on the MMU, see Fault Management Operations, Reference [2]. If the alarm is still present then replace the active MMU, see Replacing an MMU, Reference [11] or Replacing an MMU2 CS, Reference [12]. 11. Perform an RF loop on the RAU, see Fault Management Operations, Reference [2]. If the alarm is still present then replace the active RAU, see Replacing a Radio Unit, Reference [14]. 12. Execute troubleshooting as step 10 and 11 on the far-end and act consequently.

5.23.3

Alarm Clearance The alarm is cleared when a good quality signal is received.

5.24

Clock Loss Of Reference Loss of clock reference.

28

SpecificProblem

Clock Loss Of Reference

Source

MS/RS

AlarmType

EquipmentAlarm

Severity

Minor

ProbableCause

Indeterminate

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

5.25

CLOS Client Signal Loss (CLOS) A client management frame (PTI = 001b) signaling Loss of Client Signal (LCS) (UPI = 00000001b) has been received.

5.25.1

SpecificProblem

CLOS

Source

GFP

AlarmType

CommunicationAlarm

Severity

Critical

ProbableCause

LossOfSignal

Consequences Interface down.

5.25.2

Corrective Actions Remove failure in the Far End.

5.25.3

Alarm Clearance The alarm is cleared when communication is recovered.

5.26

Configuration Aborted The far-end tries to use Inverse Multiplexer over ATM (IMA) configuration parameters not compatible with the near-end configuration.

5.26.1

SpecificProblem

Configuration Aborted

Source

IMA Group

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

ConfigurationOrCustomizationError

Consequences No Asynchronous Transfer Mode (ATM) traffic can be transmitted over the specific IMA group before both the near-end and far-end groups become operational.

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

29


Alarm Descriptions

5.26.2

Corrective Actions Check the far-end IMA configuration: M (IMA Frame Size) = 128, Symmetric Configuration and Operation.

5.26.3

Alarm Clearance The alarm is cleared when the far-end configuration is accepted by the near-end.

5.27

Configuration Failure (Far-End) The far-end does not accept the configuration parameters of the near-end Inverse Multiplexer over ATM (IMA) device and reports unacceptable configuration parameters.

5.27.1

SpecificProblem

Configuration Failure (Far-End)

Source

IMA Group

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

ConfigurationOrCustomizationError

Consequences No Asynchronous Transfer Mode (ATM) traffic can be transmitted over the specific IMA group before both the near-end and far-end groups become operational.

5.27.2

Corrective Actions Check the far-end IMA configuration: M (IMA Frame Size) = 128, Symmetric Configuration and Operation.

5.27.3

Alarm Clearance The alarm is cleared when the near-end configuration is accepted by the far-end.

5.28

Control System Failure (Minor) SpecificProblem

30

Control Failure

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

Source

5.29

â&#x20AC;˘

NE

â&#x20AC;˘

SAU

AlarmType

EquipmentAlarm

Severity

Minor

ProbableCause

CommunicationsSubsystemFailure

Control System Failure (Major) A malfunction related to management, the NPU or the control bus has failed.

5.29.1

SpecificProblem

Control Failure

Source

NE

AlarmType

EquipmentAlarm

Severity

Major

ProbableCause

CommunicationsSubsystemFailure

Consequences The management functionality is reduced or unavailable.

5.29.2

Corrective Actions Try the following: Access the NE locally, see Accessing a Network Element, Reference [1]. 1. Check the site LAN port configuration. 2. Check the alarm list. Replace the NPU if it is damaged, see Replacing an NPU, Reference [13].

5.29.3

Alarm Clearance The alarm is cleared when the management functionality is working again.

5.30

CTRLOR Undefined control word on one or more Virtual Containers (VCs). SpecificProblem

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

CTRLOR

31


Alarm Descriptions

5.31

Source

VCG/LCAS Non-Standard Alarms

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

CommunicationsProtocolError

Default configuration not accepted The MMU/RAU/SFP could not accept the default configuration. This can be caused by an error in the configuration file or by a hardware error. The service (yellow) LED flashes during this alarm.

5.31.1

SpecificProblem

Default configuration not accepted

Source

• • •

AlarmType

EquipmentAlarm

Severity

Major

ProbableCause

ReplaceableUnitTypeMismatch

All MMUs All RAUs All SFPs

Consequences Failure to manage the plug-in unit or the entire node.

5.31.2

Alarm Clearance The alarm is cleared when the configuration file is accepted.

5.32

DEG (Minor) Degraded Signal (DEG) Probable cause: incoming signal of this layer violates the signal degradation threshold.

32

SpecificProblem

DEG

Source

AU4

MS

TU-3

TU-12

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

5.32.1

VC-3

VC-4

VC-12

AlarmType

CommunicationAlarm

Severity

Minor

ProbableCause

DegradedSignal

Consequences Service degraded.

5.32.2

Corrective Actions Check link connection of this layer.

5.33

DEG (Major) Degraded Signal (DEG) The incoming signal has violated the degraded defect threshold for a period longer than the defined monitoring period.

5.33.1

SpecificProblem

DEG

Source

• • •

AlarmType

QualityOfServiceAlarm

Severity

Major

ProbableCause

DegradedSignal

MS/RS VC-12 VC-4

Consequences The service is degraded.

5.33.2

Corrective Actions Check and correct the link connection of the faulty layer.

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

33


Alarm Descriptions

5.33.3

Alarm Clearance The alarm is cleared when the incoming signal is below the degraded defect threshold.

5.34

DEGFCS Degraded Frame Check Sequence (DEGFCS) An excessive number of frames with FCS error have been received. The threshold for this alarm is configurable.

5.34.1

SpecificProblem

DEGFCS

Source

GFP

AlarmType

QualityOfServiceAlarm

Severity

Critical

ProbableCause

PerformanceDegraded

Consequences Interface down.

5.34.2

Corrective Actions 1. Check the Bit Error Ratio (BER), see Troubleshooting, Reference [18]. 2. Check the source.

5.34.3

Alarm Clearance A less than 1/10 threshold number of frames with FCS error has been received. The threshold for this alarm is configurable.

5.35

Degraded service: HDLC or IM Group One or several (but not all) Inverse Multiplexer (IM) interfaces are down, leading to decreased speed on the bridge connection.

34

SpecificProblem

Degraded service

Source

â&#x20AC;˘ â&#x20AC;˘

AlarmType

CommunicationAlarm

HDLC IM Group

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

5.35.1

Severity

Major

ProbableCause

Unavailable

Corrective Actions 1. Check the Bit Error Ratio (BER). 2. Check the source.

5.36

Degraded service: IM Group The defined threshold for discarded frames on the Inverse Multiplexer (IM) group layer is exceeded.

5.37

SpecificProblem

Degraded service

Source

IM Group

AlarmType

QualityOfServiceAlarm

Severity

Major

ProbableCause

DegradedSignal

DEGTHEC Degraded tHEC. An excessive number of frames with tHEC error has been received. The threshold for this alarm is configurable.

5.37.1

SpecificProblem

DEGTHEC

Source

GFP

AlarmType

QualityOfServiceAlarm

Severity

Critical

ProbableCause

PerformanceDegraded

Consequences Interface down.

5.37.2

Corrective Actions 1. Check the Bit Error Ratio (BER), see Troubleshooting, Reference [18]. 2. Check the source.

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

35


Alarm Descriptions

5.37.3

Alarm Clearance A less than 1/10 threshold number of frames with tHEC error has been received. The threshold for this alarm is configurable.

5.38

Dmod Clock (Major) The internal data rate of the MMU 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 MMU or fading. Applicable for RAU IF (1+1).

5.38.1

SpecificProblem

Dmod Clock

Source

RAU IF

AlarmType

EquipmentAlarm

Severity

Major

ProbableCause

TimingProblem

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

5.38.2

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

5.38.3

â&#x20AC;˘

Make a manual switch.

â&#x20AC;˘

Test the radio hop.

Alarm Clearance The alarm is cleared when the internal data rate of the MMU matches the received data rate.

5.39

Dmod Clock (Critical) The Internal data rate of the MMU does not correspond to the received data rate. This fault will cause bit slip in the composite bit stream.

36

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

Probable causes for the fault: faulty MMU or fading. Applicable for RAU IF (1+0).

5.39.1

SpecificProblem

Dmod Clock

Source

RAU IF

AlarmType

EquipmentAlarm

Severity

Critical

ProbableCause

TimingProblem

Consequences Traffic Loss.

5.39.2

Corrective Actions Test the radio hop.

5.39.3

Alarm Clearance The alarm is cleared when the internal data rate of the MMU matches the received data rate.

5.40

Early Warning The threshold for early warning has been passed. Probable causes for this are: •

Fading (flat or selective).

Bad antenna alignment.

Link budget calculation not correct.

Presence of Interferers.

SpecificProblem

Early Warning

Source

RAU IF

AlarmType

CommunicationAlarm

Severity

Minor

ProbableCause

DegradedSignal

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

37


Alarm Descriptions

5.40.1

Consequences Degradation of the signal quality.

5.40.2

Corrective Actions Perform the following actions: 1. Verify the Radio Frequency (RF) input power level: it must be above the 10-6 Bit Error Ratio (BER) threshold (at least 5 dB). 2. Increase the RF input power level (if possible) by acting on the far-end output power. 3. Check the antenna alignment, see Installing Outdoor Equipment, Reference [4]. 4. Verify the link budget calculation. 5. Check for presence of RF interferers. 6. Check for presence of Intermediate Frequency (IF) interferers (and eventually the RF coaxial cable shielding). 7. Evaluate the presence of selective (multi-path) fading. 8. Perform an IF loop on the MMU, see Fault Management Operations, Reference [2]. If the alarm is still present then replace the active MMU, see Replacing an MMU, Reference [11] or Replacing an MMU2 CS, Reference [12]. 9. Perform an RF loop on the RAU, see Fault Management Operations, Reference [2]. If the alarm is still present then replace the active RAU, see Replacing a Radio Unit, Reference [14]. 10. Execute troubleshooting as step 8 and 9 on the far-end and act consequently.

5.40.3

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

5.41

EOSMISSING End Of Sequence (EOS) None of the Virtual Containers (VCs) belonging to the Virtual Concatenation Groups (VCGs) received EOS. SpecificProblem

38

EOSMISSING

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

5.42

Source

VCG/LCAS Non-Standard Alarms

AlarmType

CommunicationAlarm

Severity

Minor

ProbableCause

CommunicationsProtocolError

EOSMULTIPLE End Of Sequence (EOS) More than one Virtual Container (VC) belonging to the Virtual Concatenation Group (VCG) received EOS.

5.43

5.44

SpecificProblem

EOSMULTIPLE

Source

VCG/LCAS Non-Standard Alarms

AlarmType

CommunicationAlarm

Severity

Minor

ProbableCause

CommunicationsProtocolError

Equipment error or no holdover capable board provider SpecificProblem

Equipment error or no holdover capable board provider

Source

NE

AlarmType

CommunicationAlarm

Severity

Critical

ProbableCause

ClockSynchronisationProblem

ES 15 min threshold crossing Errored 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 or more 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

â&#x20AC;˘

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

RAU IF (1+0)

39


Alarm Descriptions

5.44.1

SWITCH

AlarmType

QualityOfServiceAlarm

Severity

Minor

ProbableCause

ThresholdCrossed

Consequences This alarm indicates degraded traffic. If the problem continues, it may lead to SES 15 min threshold crossing, see Section 5.158 on page 100.

5.44.2

Corrective Actions The problem may be temporary, but if the alarm continues over consecutive 15 min intervals, try the following actions: 1. Check if obstacles are placed in the radio path between the two hops’ antennas (at clear sky conditions). 2. Verify that the received signal power is as expected (by performing a link budget calculation). 3. Check that no interference signal is present. 4. Replace the MMU, see Replacing an MMU, Reference [11] or Replacing an MMU2 CS, Reference [12]. 5. Replace the RAU, see Replacing a Radio Unit, Reference [14].

5.44.3

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

5.45

ES 24 h threshold crossing Errored 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 more errored blocks, or at least one defect. Applicable for RAU IF (1+0). Applicable for SWITCH (1+1).

40

SpecificProblem

ES 24 h threshold crossing

Source

RAU IF (1+0)

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

â&#x20AC;˘

5.45.1

SWITCH

AlarmType

QualityOfServiceAlarm

Severity

Minor

ProbableCause

ThresholdCrossed

Consequences This alarm indicates degraded traffic. If the problem continues, it may lead to SES 24 h threshold crossing, see Section 5.159 on page 101.

5.45.2

Corrective Actions The problem may be temporary, but if the alarm continues over consecutive 24 h intervals, try the following actions: 1. Check if obstacles are placed in the radio path between the two hopsâ&#x20AC;&#x2122; antennas (at clear sky conditions). 2. Verify that the received signal power is as expected (by performing a link budget calculation). 3. Check that no interference signal is present. 4. Replace the MMU, see Replacing an MMU, Reference [11] or Replacing an MMU2 CS, Reference [12]. 5. Replace the RAU, see Replacing a Radio Unit, Reference [14].

5.45.3

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

5.46

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

Ethernet down

Source

LAN

AlarmType

CommunicationAlarm

Severity

Minor

ProbableCause

Unavailable

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

41


Alarm Descriptions

5.46.1

Consequences No Ethernet connection.

5.46.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.47

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

5.47.1

SpecificProblem

Ethernet down

Source

â&#x20AC;˘ â&#x20AC;˘

AlarmType

CommunicationAlarm

Severity

Critical

ProbableCause

Unavailable

Bridge Ethernet Bridge

Consequences No Carrier Detected on the Ethernet Port.

5.47.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.47.3

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

42

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

5.48

EXC In case of Poisson distribution of errors assumed, the Bit Error Ratio (BER) exceeds the threshold for excessive errors.

5.48.1

SpecificProblem

EXC

Source

AU4

MS

TU-3

TU-12

VC-3

VC-4

VC-12

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

ExcessiveBitErrorRate

Consequences Service unavailable.

5.48.2

Corrective Actions This is a transmission error. The alarm ceases if the alarm condition ceases. That is, check the cause for this situation on the link.

5.49

Excessive Temperature The unit has reached an excessive temperature. This can be caused by fan failure, too high ambient temperature, component failure, or air flow blocking. SpecificProblem

Excessive Temperature

Source

Plug-in Unit

AlarmType

EquipmentAlarm

Severity

Critical

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

43


Alarm Descriptions

ProbableCause

5.49.1

HighTemperature

Consequences Both control and traffic functions are shut down (operational status Out of Service) in order to reduce dissipated power to a minimum. This is done to avoid permanent damage.

5.49.2

Corrective Actions Try the following:

5.49.3

Check that the fan is working properly, see LED Descriptions, Reference [5].

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.

Alarm Clearance The alarm is cleared when the temperature goes below the high temperature threshold for the plug-in unit.

5.50

EXM Extended Header Identifier Mismatch (EXM) The Extended Header Identifier (EXI) field in a received frame does not match the configured value.

5.50.1

SpecificProblem

EXM

Source

GFP

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

PayloadTypeMismatch

# Corrective Actions Check the source.

44

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

5.51

FAL <Number> License Missing - <KeyProductName> (Major) A license for an optional feature, with the specified product number, is missing.

5.51.1

SpecificProblem

FAL <Number> License Missing - <KeyProductName>

Source

NE

AlarmType

Operational Violation

Severity

Major

ProbableCause

DenialOfService

Consequences A warning will be issued on the Licenses page in MINI-LINK Craft.

5.51.2

Corrective Actions Install the corresponding license for the optional feature by following the instructions in License Management Operations, Reference [6].

5.51.3

Alarm Clearance The alarm will be cleared as soon as the corresponding license has been installed.

5.52

FAL <Number> License Missing (Critical) A license for a optional feature with the specifies product number is missing.

5.53

SpecificProblem

FAL <Number> License Missing

Source

NE

AlarmType

Operational Violation

Severity

Critical

ProbableCause

DenialOfService

FOPR Failure on Protocol Receive (FOPR)

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

45


Alarm Descriptions

One or more Link Capacity Adjustment Scheme (LCAS) control packets with CRC (Cyclic Redundancy Check) error have been received on any of the Virtual Containers (VCs) belonging to the Virtual Concatenation Group (VCG).

5.53.1

SpecificProblem

FOPR

Source

VCG/LCAS Standard Alarms

AlarmType

CommunicationAlarm

Severity

Minor

ProbableCause

CommunicationsProtocolError

Corrective Actions Perform the following actions: 1. Check the Bit Error Ratio (BER), see Troubleshooting, Reference [18]. 2. Check the source.

5.54

5.55

Free running mode entered SpecificProblem

Free running mode entered

Source

NE

AlarmType

CommunicationAlarm

Severity

Critical

ProbableCause

LossOfSynchronisation

GIDERR Group ID Error (GIDERR) Active channels (VCs) in a Virtual Concatenation Group (VCG) have a different Group ID.

46

SpecificProblem

GIDERR

Source

VCG/LCAS Standard Alarms

AlarmType

CommunicationAlarm

Severity

Minor

ProbableCause

CommunicationsProtocolError

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

5.55.1

Corrective Actions Check the source.

5.56

Group Timing Mismatch The far-end transmit clock is different from the near-end transmit clock mode. Since the AAU supports only the Common Transmit Clock (CTC) it is likely that the far-end transmit clock has been set to the ITC.

5.56.1

SpecificProblem

Group Timing Mismatch

Source

IMA Group

AlarmType

CommunicationAlarm

Severity

Critical

Consequences No Asynchronous Transfer Mode (ATM) traffic can be transmitted over the specific Inverse Multiplexer over ATM (IMA) group before both the near-end and far-end groups become operational.

5.56.2

Alarm Analysis The far-end transmit clock could be set in ITC mode instead of CTC, which is the only mode supported by the AAU.

5.56.3

Corrective Actions Check if the far-end transmit clock is set to CTC.

5.56.4

Alarm Clearance The alarm is cleared when both the near-end and far-end are configured with the same transmit clock mode (CTC).

5.57

Hardware Error: FAU A malfunction related to hardware. SpecificProblem

Hardware Error

Source

FAU

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

47


Alarm Descriptions

5.57.1

AlarmType

EquipmentAlarm

Severity

Critical

ProbableCause

CoolingFanFailure

Consequences Malfunction due to High Temperature (see Section 5.67 on page 55) or Excessive Temperature (see Section 5.49 on page 43).

5.57.2

Corrective Actions Replace the fan unit, see Replacing a Fan Unit, Reference [10].

5.57.3

Alarm Clearance The alarm is cleared when a working fan unit has been installed.

5.58

Hardware Error: Plug-in Unit (Minor) A malfunction related to hardware, due to control system failure.

5.58.1

SpecificProblem

Hardware Error

Source

Plug-in Unit

AlarmType

EquipmentAlarm

Severity

Minor

ProbableCause

ReplaceableUnitProblem

Consequences Not possible to manage the plug-in unit.

5.58.2

Corrective Actions Try the following: 1. Check management configuration. 2. Make sure that the cable is correctly connected and that it is not damaged. 3. Check the plug-in unit and replace it if is not working correctly, see the relevant Replacing document.

48

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

5.58.3

Alarm Clearance The alarm is cleared when it is possible to manage the plug-in unit.

5.59

Hardware Error: Plug-in Unit (Major) A malfunction related to hardware.

5.59.1

SpecificProblem

Hardware Error

Source

Plug-in Unit

AlarmType

EquipmentAlarm

Severity

Major

ProbableCause

ReplaceableUnitProblem

Consequences The plug-in unit is not working.

5.59.2

Corrective Actions Try the following: 1. Make sure that the cable is correctly connected and that it is not damaged. 2. Check the plug-in unit and replace it if is not working correctly, see the relevant Replacing document.

5.59.3

Alarm Clearance The alarm is cleared when the plug-in unit is working.

5.60

Hardware Error: Plug-in Unit (Critical) A malfunction related to hardware, due to traffic or power system failure. SpecificProblem

Hardware Error

Source

Plug-in Unit

AlarmType

EquipmentAlarm

Severity

Critical

ProbableCause

ReplaceableUnitProblem

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

49


Alarm Descriptions

5.60.1

Consequences The plug-in unit is not working.

5.60.2

Corrective Actions Try the following: 1. Make sure that the cable is correctly connected and that it is not damaged. 2. Check the plug-in unit and replace it if is not working correctly, see the relevant Replacing document.

5.60.3

Alarm Clearance The alarm is cleared when the plug-in unit is working.

5.61

Hardware Error: RAU The RAU has an hardware error and must be replaced.

5.61.1

SpecificProblem

Hardware Error

Source

RAU

AlarmType

EquipmentAlarm

Severity

Critical

ProbableCause

ReplaceableUnitProblem

Consequences Traffic Loss.

5.61.2

Corrective Actions Replace the RAU, see Replacing a Radio Unit, Reference [14].

5.61.3

Alarm Clearance The alarm is cleared when the faulty unit is replaced.

5.62

Hardware Error: SFP (Major) The SFP module has an hardware error and must be replaced. Applicable for protected interface.

50

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

5.62.1

SpecificProblem

Hardware Error

Source

SFP

AlarmType

EquipmentAlarm

Severity

Major

ProbableCause

ReplaceableUnitProblem

Consequences Protection is lost.

5.62.2

Corrective Actions Replace the SFP module.

5.62.3

Alarm Clearance The alarm is cleared when the faulty unit is replaced.

5.63

Hardware Error: SFP (Critical) The SFP module has an hardware error and must be replaced. Applicable for unprotected interface.

5.63.1

SpecificProblem

Hardware Error

Source

SFP

AlarmType

EquipmentAlarm

Severity

Critical

ProbableCause

ReplaceableUnitProblem

Consequences Traffic Loss.

5.63.2

Corrective Actions Replace the SFP module.

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

51


Alarm Descriptions

5.63.3

Alarm Clearance The alarm is cleared when the faulty unit is replaced.

5.64

HCC Hop Communication Channel (HCC) Communication is lost on the HCC, between the MMU and the far-end MMU.

5.64.1

SpecificProblem

HCC

Source

All MMUs

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

Unavailable

Consequences It is not possible to access the Far End.

5.64.2

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

5.65

High BER (Major) Bit Error Ratio (BER) The threshold for Synchronous Digital Hierarchy (SDH) High BER has been passed (BER threshold level). Probable causes for this are:

52

Fading (flat or selective)

Bad antenna alignment

Link budget calculation not correct

Presence of Interferers

SpecificProblem

High BER

Source

RAU IF (1+1)

AlarmType

CommunicationAlarm

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

5.65.1

Severity

Major

ProbableCause

DegradedSignal

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

5.65.2

Corrective Actions Perform the following actions: 1. Verify the Radio Frequency (RF) input power level: it must be above the 10-6 BER threshold (at least 5 dB). 2. Increase the RF input power level (if possible) by acting on far-end output power. 3. Check the antenna alignment, see Installing Outdoor Equipment, Reference [4]. 4. Verify the link budget calculation. 5. Check for presence of RF interferers. 6. Check for presence of Intermediate Frequency (IF) interferers (and eventually the RF coaxial cable shielding). 7. Evaluate the presence of selective (multi-path) fading. 8. Perform an IF loop on the MMU, see Fault Management Operations, Reference [2]. If the alarm is still present then replace the active MMU, see Replacing an MMU, Reference [11] or Replacing an MMU2 CS, Reference [12]. 9. Perform an RF loop on the RAU, see Fault Management Operations, Reference [2]. If the alarm is still present then replace the active RAU, see Replacing a Radio Unit, Reference [14]. 10. Execute troubleshooting as step 8 and 9 on the far-end and act consequently.

5.65.3

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

5.66

High BER (Critical) Bit Error Ratio (BER)

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

53


Alarm Descriptions

The threshold for Synchronous Digital Hierarchy (SDH) High BER has been passed (BER threshold level). Probable causes for this are:

5.66.1

Fading (flat or selective)

Bad antenna alignment

Link budget calculation not correct

Presence of Interferers

SpecificProblem

High BER

Source

RAU IF (1+0)

AlarmType

CommunicationAlarm

Severity

Critical

ProbableCause

DegradedSignal

Consequences Degradation of the quality of the traffic signal line side.

5.66.2

Corrective Actions Perform the following actions: 1. Verify the Radio Frequency (RF) input power level: it must be above the 10-6 BER threshold (at least 5 dB). 2. Increase the RF input power level (if possible) by acting on far-end output power. 3. Check the antenna alignment, see Installing Outdoor Equipment, Reference [4]. 4. Verify the link budget calculation. 5. Check for presence of RF interferers. 6. Check for presence of Intermediate Frequency (IF) interferers (and eventually the RF coaxial cable shielding). 7. Evaluate the presence of selective (multi-path) fading. 8. Perform an IF loop on the MMU, see Fault Management Operations, Reference [2]. If the alarm is still present then replace the active MMU, see Replacing an MMU, Reference [11] or Replacing an MMU2 CS, Reference [12].

54

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

9. Perform an RF loop on the RAU, see Fault Management Operations, Reference [2]. If the alarm is still present then replace the active RAU, see Replacing a Radio Unit, Reference [14]. 10. Execute troubleshooting as step 8 and 9 on the far-end and act consequently.

5.66.3

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

5.67

High Temperature The unit has reached an abnormal temperature. This can be caused by fan failure, too high ambient temperature, component failure, or air flow blocking.

5.67.1

SpecificProblem

High Temperature

Source

Plug-in Unit

AlarmType

EquipmentAlarm

Severity

Minor

ProbableCause

HighTemperature

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

5.67.2

Corrective Actions Try the following: •

Check that the fan is working properly, see LED Descriptions, Reference [5].

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/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

55


Alarm Descriptions

5.67.3

Alarm Clearance The alarm is cleared when the temperature has been stable for 60 seconds below the high temperature threshold for the plug-in unit.

5.68

Hitless Phase Failure of synchronizing of the received traffic in the two MMUs with a duration longer than the time given by Fade Notification Timer.

5.69

5.70

SpecificProblem

Hitless Phase

Source

SWITCH

AlarmType

EquipmentAlarm

Severity

Warning

ProbableCause

ProtectionPathFailure

Holdover mode entered SpecificProblem

Holdover mode entered

Source

NE

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

LossOfSynchronisation

ICC Internal Communication Channel (ICC) Communication is lost on the ICC, between two MMUs in the same terminal. Possible cause: the software or hardware of the MMUs is not compatible.

5.70.1

SpecificProblem

ICC

Source

MMU2 B/C/E/F

AlarmType

CommunicationAlarm

Severity

Major

Consequences Unable to Protect.

56

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

5.70.2

Corrective Actions Try the following: 1. Check the software and hardware of the MMUs. 2. Upgrade software or replace one MMU to achieve compatibility.

5.70.3

Alarm Clearance The alarm is cleared when communication is recovered.

5.71

IF LOS R2L (Major) The failure is caused by loss of the receiving Intermediate Frequency (IF) signal from the RAU to the MMU (only for MMU2 E/F). The alarm can be caused by the following events:

5.71.1

â&#x20AC;˘

A hardware MMU failure in the radio I/f block or the demodulator itself.

â&#x20AC;˘

The demodulation IF carrier has low power level.

SpecificProblem

IF LOS R2L

Source

RAU IF (1+1)

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

LossOfSignal

Consequences Loss of received signal: hitless switch on the faultless Rx.

5.71.2

Corrective Actions Perform the following actions: 1. Verify the RAU settings. 2. Perform an IF loop on the MMU, see Fault Management Operations, Reference [2]. If the alarm is still present then replace the active MMU, see Replacing an MMU, Reference [11]. 3. Replace the RAU, see Replacing a Radio Unit, Reference [14].

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

57


Alarm Descriptions

5.71.3

Alarm Clearance The alarm is cleared when the MMU (or RAU) is replaced, or the demodulator input signal is present.

5.72

IF LOS R2L (Critical) The failure is caused by loss of received Intermediate Frequency (IF) signal from the RAU to the MMU (only for MMU2 E/F). The alarm can be caused by the following events:

5.72.1

â&#x20AC;˘

A hardware MMU failure in the radio I/f block or the demodulator itself.

â&#x20AC;˘

The demodulation IF carrier has low power level.

SpecificProblem

IF LOS R2L

Source

RAU IF (1+0)

AlarmType

CommunicationAlarm

Severity

Critical

ProbableCause

LossOfSignal

Consequences Loss of received signal: traffic is lost on the line side.

5.72.2

Corrective Actions Perform the following actions: 1. Verify the RAU settings. 2. Perform an IF loop on the MMU, see Fault Management Operations, Reference [2]. If the alarm is still present then replace the active MMU, see Replacing an MMU, Reference [11]. 3. Replace the RAU, see Replacing a Radio Unit, Reference [14].

5.72.3

Alarm Clearance The alarm is cleared when the MMU (or RAU) is replaced, or the demodulator input signal is present.

58

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

5.73

5.74

5.75

In Repair SpecificProblem

In Repair

Source

Plug-in Unit

AlarmType

EquipmentAlarm

Severity

Critical

ProbableCause

ReplaceableUnitProblem

Incompatible Units: Plug-in Unit SpecificProblem

Incompatible Units

Source

Plug-in Unit

AlarmType

EquipmentAlarm

Severity

Critical

ProbableCause

ReplacebleUnitTypeMismatch

Incompatible Units: RAU The RAU in use is incompatible with the connected MMU.

5.75.1

SpecificProblem

Incompatible Units

Source

RAU

AlarmType

EquipmentAlarm

Severity

Major

ProbableCause

ReplacebleUnitTypeMismatch

Consequences It is not possible to configure the radio terminal.

5.75.2

Corrective Actions Replace the RAU with one of compatible type, see Replacing a Radio Unit, Reference [14].

5.75.3

Alarm Clearance The alarm is cleared when the RAU is replaced with one of compatible type.

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

59


Alarm Descriptions

5.76

Insufficient links The near-end does not have enough active links in neither the transmit nor the receive directions (less than PTx transmit or PRx receive links are active).

5.76.1

SpecificProblem

Insufficient links

Source

IMA Group

AlarmType

CommunicationAlarm

Severity

Critical

ProbableCause

ConfigurationOrCustomizationError

Consequences No Asynchronous Transfer Mode (ATM) traffic can be transmitted over the specific Inverse Multiplexer over ATM (IMA) group before both the near-end and far-end groups become operational.

5.76.2

Alarm Analysis The near-end does not have enough active links in both directions. This can be caused by one or more faults affecting the links of the groups or because not enough links have been configured in the group.

5.76.3

Corrective Actions Check if any alarm is reported on the IMA links of the specific group. If no alarms affect the IMA links, add one or more links to the group to reach the required minimum number of links.

5.76.4

Alarm Clearance The alarm is cleared when the near-end terminal has the required number of active links.

5.77

Insufficient links (Far-End) The far-end does not have enough active links in the transmit and/or receive directions and reports that less than PTx transmit or PRx receive links are active.

60

SpecificProblem

Insufficient links (Far-End)

Source

IMA Group

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

5.77.1

AlarmType

CommunicationAlarm

Severity

Critical

ProbableCause

ConfigurationOrCustomizationError

Consequences No Asynchronous Transfer Mode (ATM) traffic can be transmitted over the specific Inverse Multiplexer over ATM (IMA) group before both the near-end and far-end groups become operational.

5.77.2

Alarm Analysis The far-end does not have enough active links in both directions. This can be caused by one or more faults affecting the links of the groups or because not enough links have been configured in the group.

5.77.3

Corrective Actions Check if any alarm is reported on the IMA links of the specific group. If no alarms affect the IMA links, add one or more links to the group to reach the required minimum number of links.

5.77.4

Alarm Clearance No faults affect IMA links of the specific group if it holds the required minimum of active links.

5.78

Insufficient resources The NE does not have the resources to handle this Plug-in Unit. SpecificProblem

Insufficient resources

Source

Plug-In Unit

RAU

SFP

AlarmType

EquipmentAlarm

Severity

Critical

ProbableCause

ReplaceableUnitTypeMismatch

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

61


Alarm Descriptions

5.79

Inter MMU Channel Failure High level fault on inter MMU2 E/F communication of Regenerator Section (RS). Only valid when protected.

5.80

SpecificProblem

Inter MMU Channel Failure

Source

MMU2 E/F

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

LossOfFrame

LCASCRC Link Capacity Adjustment Scheme Cyclic Redundancy Check (LCASCRC) One or more LCAS control packets with Cyclic Redundancy Check (CRC) error have been received on any of the Virtual Containers (VCs) belonging to the Virtual Concatenation Group (VCG).

5.80.1

SpecificProblem

LCASCR

Source

VCG/LCAS Standard Alarms

AlarmType

CommunicationAlarm

Severity

Minor

ProbableCause

CommunicationsProtocolError

Corrective Actions Perform the following actions: 1. Check the Bit Error Ratio (BER), see Troubleshooting, Reference [18]. 2. Check the source.

5.81

LFD Loss of Frame Delineation (LFD) The Generic Framing Procedure (GFP) delineation state machine has left the SYNC state.

62

SpecificProblem

LFD

Source

GFP

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

5.81.1

AlarmType

CommunicationAlarm

Severity

Critical

ProbableCause

FramingError

Consequences Interface down.

5.81.2

Corrective Actions Perform the following actions: 1. Check the Bit Error Ratio (BER), see Troubleshooting, Reference [18]. 2. Check the source.

5.81.3

Alarm Clearance The alarm is cleared when the traffic recovers and the GFP delineation state machine changes to SYNC state. Communication recovers.

5.82

Link Fault This alarm is raised when a Link OAM detects a link fault at an interface.

5.82.1

SpecificProblem

Link fault

Source

LAN

AlarmType

CommunicationAlarm

Severity

Critical

ProbableCause

Unavailable

Consequences No Carrier Detected in Tx direction on the Ethernet Port.

5.82.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/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

63


Alarm Descriptions

5.82.3

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

5.83

Link OAM Loopback A Link OAM loopback can be set at interface by remote Link OAM and the interface will not be able to transmit user traffic. This alarm is raised whenever such loopback is set at an interface by remote Link OAM.

5.83.1

SpecificProblem

OAM loopback set by remote

Source

LAN

AlarmType

CommunicationAlarm

Severity

Critical

ProbableCause

Unavailable

Consequences Egress traffic discarded and ingress traffic loop back to the remote peer on the Ethernet Port.

5.83.2

Corrective Actions Try to remove the Link OAM loop on the peer link OAM entity. If Link OAM functionality is not needed, you may want to disable it as well.

5.83.3

Alarm Clearance The alarm is cleared when link OAM loopback is removed or Link OAM session is terminated

5.84

LOA Loss of Alignment (LOA) LOA for channels with traffic. The differential delay for at least one channel cannot be aligned.

64

SpecificProblem

LOA

Source

VCG/LCAS Standard Alarms

AlarmType

CommunicationAlarm

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

5.85

Severity

Critical

ProbableCause

FramingError

LOF (Critical) Loss of Frame Alignment (LOF) Probable causes for this are as follows:

5.85.1

Fiber broken.

Fiber power mismatch.

The connect rate of the device mismatch.

SpecificProblem

LOF

Source

• • •

AlarmType

CommunicationAlarm

Severity

Critical

ProbableCause

LossOfFrame

E2/E3 Framed E1 MS

Consequences Traffic block.

5.85.2

Corrective Actions Check fiber connection or far-end device.

5.85.3

Alarm Clearance The alarm is cleared when the communication recovers.

5.86

LOF: RS (Critical) Loss Of Frame Alignment (LOF) The Frame Alignment Signal (FAS) was not found. SpecificProblem

LOF

Source

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

RS

65


Alarm Descriptions

5.86.1

AlarmType

CommunicationAlarm

Severity

Critical

ProbableCause

LossOfFrame

Consequences Service unavailable.

5.86.2

Corrective Actions Cease the particular transmission error.

5.87

LOF L2R (Major) The input traffic on the Line interface is corrupted. There is a loss of frame on the receiving line (only for MMU2 E/F).

5.87.1

SpecificProblem

LOF L2R

Source

LINE RS (1+1 EEP/ELP)

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

LossOfFrame

Consequences An Alarm Indication Signal (AIS) is propagated to the radio side. The system switches to the faultless interface.

5.87.2

Corrective Actions Perform the following actions: 1. Check the cable and connector Line side on the MMU. 2. If possible, perform a loop on the external equipment feeding the Line interface of the MMU, see Fault Management Operations, Reference [2]. If no alarm is detected on the external equipment then replace the MMU, see Replacing an MMU, Reference [11]. 3. Replace the MMU, see Replacing an MMU, Reference [11].

66

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

5.87.3

Alarm Clearance The alarm is cleared when the frame alignment on the incoming signal is possible again.

5.88

LOF L2R (Critical) The input traffic on the Line interface is corrupted. There is a loss of frame on the receiving line (only for MMU2 E/F).

5.88.1

SpecificProblem

LOF L2R

Source

LINE RS (1+0, 1+1 SI)

AlarmType

CommunicationAlarm

Severity

Critical

ProbableCause

LossOfFrame

Consequences An Alarm Indication Signal (AIS) is propagated to the radio side. As a consequence traffic is lost on the radio side.

5.88.2

Corrective Actions Perform the following actions: 1. Check the cable and connector Line side on the MMU. 2. If possible, perform a loop on the external equipment feeding the Line interface of the MMU, see Fault Management Operations, Reference [2]. If no alarm is detected on the external equipment then replace the MMU, see Replacing an MMU, Reference [11]. 3. Replace the MMU, see Replacing an MMU, Reference [11].

5.88.3

Alarm Clearance The alarm is cleared when the frame alignment on the incoming signal is possible again.

5.89

LOF R2L (Major) Loss Of Frame (LOF) LOF on the transmitting line (only for MMU2 E/F). Probable causes for this are:

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

67


Alarm Descriptions

5.89.1

Fading (flat or selective)

Bad antenna alignment

Link budget calculation not correct

Presence of interferers

SpecificProblem

LOF R2L

Source

RAU IF(1+1)

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

LossOfFrame

Consequences An Alarm Indication Signal (AIS) is propagated to the line side. The Radio Protection Switch will choose the other MMU if its signal quality is better.

5.89.2

Corrective Actions Perform the following actions: 1. Verify the Radio Frequency (RF) input power level: it must be above the 10-6 Bit Error Ratio (BER) threshold (at least 5 dB). 2. Increase the RF input power level (if possible) by acting on the far-end output power. 3. Check the antenna alignment, see Installing Outdoor Equipment, Reference [4]. 4. Verify the link budget calculation. 5. Check for presence of RF interferers. 6. Check for presence of Intermediate Frequency (IF) interferers (and eventually the RF coaxial cable shielding). 7. Evaluate the presence of selective (multi-path) fading. 8. Perform an IF loop on the MMU, see Fault Management Operations, Reference [2]. If the alarm is still present then replace the active MMU, see Replacing an MMU, Reference [11]. 9. Perform an RF loop on the RAU, see Fault Management Operations, Reference [2]. If the alarm is still present then replace the active RAU, see Replacing a Radio Unit, Reference [14].

68

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

10. Execute troubleshooting as step 8 and 9 on the far-end and act consequently.

5.89.3

Alarm Clearance The alarm is cleared when the frame alignment on the incoming radio signal is possible again.

5.90

LOF R2L (Critical) Loss Of Frame (LOF) LOF on the transmitting line (only for MMU2 E/F). Probable causes for this are:

5.90.1

Fading (flat or selective).

Bad antenna alignment.

Link budget calculation not correct.

Presence of interferers.

SpecificProblem

LOF R2L

Source

RAU IF(1+0)

AlarmType

CommunicationAlarm

Severity

Critical

ProbableCause

LossOfFrame

Consequences An Alarm Indication Signal (AIS) is propagated to the line side. As a consequence the traffic is lost on the line side.

5.90.2

Corrective Actions Perform the following actions: 1. Verify the Radio Frequency (RF) input power level: it must be above the 10-6 Bit Error Ratio (BER) threshold (at least 5 dB). 2. Increase the RF input power level (if possible) by acting on the far-end output power. 3. Check the antenna alignment, see Installing Outdoor Equipment, Reference [4]. 4. Verify the link budget calculation.

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

69


Alarm Descriptions

5. Check for presence of RF interferers. 6. Check for presence of Intermediate Frequency (IF) interferers (and eventually the RF coaxial cable shielding). 7. Evaluate the presence of selective (multi-path) fading. 8. Perform an IF loop on the MMU, see Fault Management Operations, Reference [2]. If the alarm is still present then replace the active MMU, see Replacing an MMU, Reference [11]. 9. Perform an RF loop on the RAU, see Fault Management Operations, Reference [2]. If the alarm is still present then replace the active RAU, see Replacing a Radio Unit, Reference [14]. 10. Execute troubleshooting as step 8 and 9 on the far-end and act consequently.

5.90.3

Alarm Clearance The alarm is cleared when the frame alignment on the incoming radio signal is possible again.

5.91

LOM Loss of Multiframe (LOM) The 2-stage multiframe alignment used for virtual concatenation is lost.

5.91.1

SpecificProblem

LOM

Source

• • •

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

LossOfMultiFrame

VC-12 VC-3 VC-4

Corrective Actions Perform the following actions: 1. Check the Bit Error Ratio (BER), see Troubleshooting, Reference [18]. 2. Check the source.

70

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

5.92

LOMF (Major) Loss of Multiframe (LOMF)

5.93

SpecificProblem

LOMF

Source

VC-4

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

LossOfMultiFrame

LOMF (Critical) Loss of Multiframe (LOMF)

5.94

SpecificProblem

LOMF

Source

Framed E1

AlarmType

CommunicationAlarm

Severity

Critical

ProbableCause

LossOfMultiFrame

LOP (Major) Loss of Pointer (LOP) The incoming signal is corrupted so the pointer cannot be located in the signal.

5.94.1

SpecificProblem

LOP

Source

AU4

TU-3

TU-12

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

LossOfPointer

Consequences The service is unavailable.

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

71


Alarm Descriptions

5.94.2

Corrective Actions Check and correct the link connection of the faulty layer.

5.94.3

Alarm Clearance The alarm is cleared when the incoming signal is not corrupted anymore and the pointer can be located in the incoming signal.

5.95

LOP (Critical) Loss of Pointer (LOP) The incoming signal is corrupted, so the pointer cannot be located in the signal.

5.95.1

SpecificProblem

LOP

Source

â&#x20AC;˘ â&#x20AC;˘

AlarmType

CommunicationAlarm

Severity

Critical

ProbableCause

LossOfPointer

VC-4 VC-12

Consequences The service is unavailable.

5.95.2

Corrective Actions Check and correct the link connection of the faulty layer.

5.95.3

Alarm Clearance The alarm is cleared then the incoming signal is not corrupted anymore, and the pointer can be located in the incoming signal.

5.96

LOS: RAU IF (Major) Loss of Signal (LOS) LOS is detected on the incoming traffic, probably due to traffic failure in transmitting direction.

72

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

Applicable for RAU IF (1+1).

5.97

SpecificProblem

LOS

Source

RAU IF

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

LossOfSignal

LOS (Critical) Loss of Signal (LOS) LOS is detected on the incoming traffic, probably due to traffic failure in transmitting direction.

5.97.1

SpecificProblem

LOS

Source

• •

AlarmType

CommunicationAlarm

Severity

Critical

ProbableCause

LossOfSignal

E1 MS/RS

Consequences The service is unavailable.

5.97.2

Corrective Actions Check cables and equipment in the traffic path.

5.97.3

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

5.98

LOS: RAU IF (Critical) Loss of Signal (LOS) LOS is detected on the incoming traffic, probably due to traffic failure in transmitting direction.

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

73


Alarm Descriptions

Applicable for RAU IF (1+0).

5.99

SpecificProblem

LOS

Source

RAU IF

AlarmType

CommunicationAlarm

Severity

Critical

ProbableCause

LossOfSignal

LOS: SpiElectrical or SpiOptical (Critical) Loss of Signal (LOS) LOS is detected on the incoming traffic, probably due to traffic failure in transmitting direction or fiber/cable failure.

5.99.1

SpecificProblem

LOS

Source

• •

AlarmType

CommunicationAlarm

Severity

Critical

ProbableCause

LossOfSignal

SpiElectrical SpiOptical

Consequences The service is unavailable.

5.99.2

Corrective Actions Check cables and equipment in the traffic path.

5.99.3

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

5.100

LOS L2R (Major) Loss of received signal at the line interface (only for MMU2 E/F). Applicable for 1+1 Enhanced Equipment Protection (EEP)/Equipment and Line Protection (ELP).

74

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

5.100.1

SpecificProblem

LOS L2R

Source

LINE RS (1+1 EEP/ELP)

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

LossOfSignal

Consequences The protection is lost.

5.101

LOS L2R (Critical) Loss of received signal at the line interface (only for MMU2 E/F). Applicable for 1+0 and 1+1 Single Interface (SI).

5.102

SpecificProblem

LOS L2R

Source

LINE RS (1+0, 1+1 SI)

AlarmType

CommunicationAlarm

Severity

Critical

ProbableCause

LossOfSignal

Loss of Cell Delineation: ATM Asynchronous Transfer Mode (ATM) Cells cannot be extracted from the E1 Link configured as a G.804 ATM interface.

5.102.1

SpecificProblem

Loss of Cell Delineation

Source

ATM

AlarmType

CommunicationAlarm

Severity

Critical

ProbableCause

TransmissionError

Consequences There is no ATM traffic in the Rx direction of the specific ATM Interface.

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

75


Alarm Descriptions

5.102.2

Alarm Analysis The network equipment connected to E1 is not configured for ATM service or physical failure at the E1 interface (Loss Of Signal (LOS)/Loss Of Frame (LOF)/Alarm Indication Signal (AIS)).

5.102.3

Corrective Actions Check the configuration of the network equipment interface connected to the specific E1 interface.

5.102.4

Alarm Clearance The alarm is cleared when the transmission convergence is able to delineate and extract ATM cells from the specific link.

5.103

Loss of Cell Delineation: IMA Link Asynchronous Transfer Mode (ATM) Cells cannot be extracted from the E1 Link configured as an Inverse Multiplexer over ATM (IMA) Link.

5.103.1

SpecificProblem

Loss of Cell Delineation

Source

IMA Link

AlarmType

CommunicationAlarm

Severity

Critical

ProbableCause

TransmissionError

Consequences No ATM traffic can be received from the specific IMA Link. Related IMA groups can also be affected by the fault: in case the IMA group goes below the "minimum number of (active) links" no ATM traffic can flow at all through the group. In this case the operational status of related ATM-IMA (IMA group) and ATM goes to down. If the IMA group still have a minimum number of links it can still receive the guaranteed bandwidth of traffic.

5.103.2

Alarm Analysis The network equipment connected to E1 is not configured for ATM service or physical failure at the E1 interface (Loss Of Signal (LOS)/Loss Of Frame (LOF)/Alarm Indication Signal (AIS)).

76

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

5.103.3

Corrective Actions Check the configuration of the network equipment interface connected to the specific link.

5.103.4

Alarm Clearance The alarm is cleared when the transmission convergence is able to delineate and extract ATM cells from the specific link.

5.104

Loss of Delay Synchronization The link has a delay higher than the tolerable link differential delay (25 msec) with respect to the other links in the group.

5.104.1

SpecificProblem

Loss of Delay Synchronization

Source

IMA Link

AlarmType

CommunicationAlarm

Severity

Critical

ProbableCause

DegradedSignal

Consequences No Asynchronous Transfer Mode (ATM) traffic can be received from the specific Inverse Multiplexer over ATM (IMA) Link. Related IMA groups can also be affected by the fault: in case the IMA group goes below the "minimum number of (active) links" no ATM traffic can flow at all through the group. In this case the operational status of related ATM-IMA (IMA group) and ATM goes to down. If the IMA group still have a minimum number of links it can still receive the guaranteed bandwidth of traffic.

5.104.2

Alarm Analysis Links belonging to the group have different paths in the network causing an excessive differential delay among the links.

5.104.3

Corrective Actions Try to reduce differential delays by using other links.

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

77


Alarm Descriptions

5.104.4

Alarm Clearance The alarm is cleared when the differential delay of the link sinks below the limit threshold (25 msec).

5.105

Loss of IMA Frame Persistence of a LIF defect at the near-end (more than 2.5 +/- 0.5 sec). Inverse Multiplexer over ATM (IMA) device can not find IMA ICP Cells delimiting IMA Frames.

5.105.1

SpecificProblem

Loss of IMA Frame

Source

IMA Link

AlarmType

CommunicationAlarm

Severity

Critical

ProbableCause

LossOfFrame

Consequences No Asynchronous Transfer Mode (ATM) traffic can be received from the specific IMA Link. Related IMA groups can also be affected by the fault: in case the IMA group goes below the "minimum number of (active) links" no ATM traffic can flow at all through the group. In this case the operational status of related ATM-IMA (IMA group) and ATM goes to down. If the IMA group still have a minimum number of links it can still receive the guaranteed bandwidth of traffic.

5.105.2

Alarm Analysis The far-end link is not configured as an IMA Link.

5.105.3

Corrective Actions Check the far-end link configuration.

5.105.4

Alarm Clearance The alarm is cleared when the IMA device can receive ICP cells from the far-end link.

5.106

Loss of keep alive Loss of keep-alive frames is detected.

78

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

5.107

5.108

SpecificProblem

Loss of keep alive

Source

IM Group

AlarmType

CommunicationAlarm

Severity

Critical

ProbableCause

Unavailable

Loss of network reference redundancy SpecificProblem

Loss of network reference redundancy

Source

NE

AlarmType

CommunicationAlarm

Severity

Minor

ProbableCause

ClockSynchronisationProblem

Low BER Bit Error Ratio (BER) The threshold for Low BER has been passed (MMU2 E/F only).

5.109

SpecificProblem

Low BER

Source

RAU IF

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

DegradedSignal

Low Input Voltage The input voltage is low. If it drops further, one or more plug-in units may stop working. SpecificProblem

Low Input Voltage

Source

NE

AlarmType

EnvironmentalAlarm

Severity

Major

ProbableCause

PowerProblem

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

79


Alarm Descriptions

5.110

Lower Layer Down No throughput on the interface. All Inverse Multiplexer (IM) interfaces are down. For TDM Link, Lower Layer Down (LLD) is reported for BER > 10E-3. For Packet Link, LLD is reported for BER > 10E-6.

5.111

SpecificProblem

Lower Layer Down

Source

IM Group

AlarmType

CommunicationAlarm

Severity

Critical

ProbableCause

Unavailable

Missing License When this plug-in unit was inserted, the total number of plug-in units in the AMM became more than 10, but no license for the optional feature AMM 20p Slot Extension was available. Only applicable for AMM 20p.

5.112

SpecificProblem

Missing license

Source

Plug-in Unit

AlarmType

EquipmentAlarm

Severity

Minor

ProbableCause

ReplaceableUnitTypeMismatch

Mod Index The modulation index of the MMU, controlled by the far-end MMU, is out of the allowed range.

5.113

SpecificProblem

Mod Index

Source

RAU IF

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

DegradedSignal

Mode Mismatch Multiplex Section Protection (MSP) mode mismatch.

80

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

Far-end configured as MSP 1:n and the received K2 byte does not indicate 1+1.

5.113.1

SpecificProblem

Mode Mismatch

Source

MSP

AlarmType

CommunicationAlarm

Severity

Minor

ProbableCause

Indeterminate

Corrective Actions Check and correct configuration mismatch.

5.113.2

Alarm Clearance The alarm is cleared when the K2 byte indicates 1+1.

5.114

5.115

No holdover protection SpecificProblem

No holdover protection

Source

NE

AlarmType

CommunicationAlarm

Severity

Minor

ProbableCause

ClockSynchronisationProblem

No Traffic Possible No throughput on the interface. All Inverse Multiplexer (IM) interfaces are Down.

5.116

SpecificProblem

No Traffic Possible

Source

HDLC

AlarmType

CommunicationAlarm

Severity

Critical

ProbableCause

Unavailable

Node Installation The NE is in Node Installation mode. Enter the URL http://10.0.0.1 to reach the installation wizard.

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

81


Alarm Descriptions

5.117

SpecificProblem

Node Installation

Source

NE

AlarmType

EquipmentAlarm

Severity

Minor

ProbableCause

CommunicationsSubsystemFailure

NONLCAS A sink operating in Link Capacity Adjustment Scheme (LCAS) mode detected a NON-LCAS source.

5.117.1

SpecificProblem

NONLCAS

Source

VCG/LCAS Non-Standard Alarms

AlarmType

CommunicationAlarm

Severity

Warning

ProbableCause

ConfigurationOrCustomizationError

Corrective Actions Check the source.

5.118

Not able to find RMM The Removable Memory Module (RMM) is faulty, missing, or has no contact with the RMM socket.

5.118.1

SpecificProblem

Not able to find RMM

Source

NE

AlarmType

OperationalViolation

Severity

Minor

ProbableCause

Unavailable

Consequences The NE is not able to backup and restore configuration files and to reach the License Key File (LKF) from the RMM. It is not possible to transfer the configuration to a new NPU by moving the RMM, if an NPU replacement will be necessary in the future. As an alternative, the configuration and license files

82

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

can be uploaded to an FTP server. For each optional feature that is used, the FAL <Number> License Missing alarm will be issued.

5.118.2

Corrective Actions Check that the RMM is properly inserted in the RMM socket on the NPU. The RMM must be in contact with the RMM socket. If the alarm is not cleared the RMM is faulty and should be replaced. If optional features are used, a new License Key File (LKF) must be installed on the new RMM. For information on RMM replacement, for example, how to remove and insert an RMM, see Replacing an RMM, Reference [15].

5.118.3

Alarm Clearance The alarm is cleared when a functioning RMM is correctly inserted in the RMM socket.

5.119

NPU Installation The NE is in NPU Installation mode. Enter the URL http://10.0.0.1 to reach the installation wizard.

5.120

SpecificProblem

NPU Installation

Source

NE

AlarmType

EquipmentAlarm

Severity

Major

ProbableCause

CommunicationsSubsystemFailure

OSPF LSA database overload The Open Shortest Path First (OSPF) routing database is full due to too many routers in the network. SpecificProblem

OSPF LSA database overload

Source

NE

AlarmType

CommunicationAlarm

Severity

Minor

ProbableCause

StorageCapacityProblems

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

83


Alarm Descriptions

5.121

PFM Payload FCS Identifier Mismatch (PFM) The Payload FCS Identifier (PFI) field in the received frame does not match the configured value.

5.121.1

SpecificProblem

PFM

Source

GFP

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

PayloadTypeMismatch

Corrective Actions Repair the Virtual Container (VC) trail.

5.121.2

Alarm Clearance The Alarm is cleared when the PFI field in the received frame matches the configured value.

5.122

PLCR Partial Loss of Capacity Received (PLCR) Some of the Virtual Containers (VCs) belonging to a Virtual Concatenation Group (VCG) have been temporarily removed in the receive direction.

5.122.1

SpecificProblem

PLCR

Source

VCG/LCAS Standard Alarms

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

BandwithReduced

Corrective Actions Repair the Virtual Container (VC) trail.

84

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

5.122.2

Alarm Clearance The Alarm is cleared when the temporarily removed VCs have been restored.

5.123

PLCT Partial Loss of Capacity Transmit (PLCT) Some of the Virtual Containers (VCs) belonging to a Virtual Concatenation Group (VCG) have been temporarily removed in the transmit direction.

5.123.1

SpecificProblem

PLCT

Source

VCG/LCAS Standard Alarms

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

BandwithReduced

Corrective Actions Repair the Virtual Container (VC) trail.

5.123.2

Alarm Clearance The Alarm is cleared when the temporarily removed VCs have been restored.

5.124

PLM (Major) Payload Mismatch (PLM) The detection of PLM is based on a comparison between the expected Trail Signal Label (TSL), representing the selected/activated adaption function, and the accepted TSL. SpecificProblem

PLM

Source

VC-3

VC-4

VC-412

AlarmType

CommunicationAlarm

Severity

Major

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

85


Alarm Descriptions

ProbableCause

5.124.1

PayloadTypeMismatch

Consequences Service unavailable.

5.124.2

5.125

Corrective Actions •

Cease the particular transmission error.

Check source.

PLM (Critical) Payload Mismatch (PLM) Non-consistent configuration, so the received C2 byte is not equal to the expected C2 byte.

5.125.1

SpecificProblem

PLM

Source

• •

AlarmType

CommunicationAlarm

Severity

Critical

ProbableCause

SignalLabelMismatch

VC-12 VC-4

Consequences The service will be unavailable.

5.125.2

Corrective Actions Check and correct configuration mismatch.

5.125.3

Alarm Clearance The alarm is cleared when the configuration mismatch is resolved.

5.126

86

Power Failure (lower input) SpecificProblem

Power Failure (lower input)

Source

NE

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

5.127

AlarmType

EquipmentAlarm

Severity

Critical

ProbableCause

PowerProblem

PPP down Failure in the Data Communication Network (DCN) communication.

5.128

SpecificProblem

PPP down

Source

PPP

AlarmType

CommunicationAlarm

Severity

Minor

ProbableCause

Unavailable

PTM Payload Type Identifier Mismatch (PTM) The Payload Type Identifier (PTI) field in the received frame is different from 000b (client data frame), or 100b does not match one of the configured values.

5.128.1

SpecificProblem

PTM

Source

GFP

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

PayloadTypeMismatch

Corrective Actions Perform the following actions: 1. Check the local configuration. 2. Check the remote configuration.

5.129

Radio Frame (Major) The receiver failed to synchronize the frame of the received composite bit stream due to signal failure. Applicable for RAU IF (1+1).

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

87


Alarm Descriptions

5.130

SpecificProblem

Radio Frame

Source

RAU IF

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

LossOfFrame

Radio Frame (Critical) The receiver failed to synchronize the frame of the received composite bit stream due to signal failure. Applicable for RAU IF (1+0).

5.131

SpecificProblem

Radio Frame

Source

RAU IF

AlarmType

CommunicationAlarm

Severity

Critical

ProbableCause

LossOfFrame

Radio ID (Major) The received traffic comes from a terminal with an ID not matching the Far End ID. Possible causes for this is: â&#x20AC;˘

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

â&#x20AC;˘

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).

5.131.1

SpecificProblem

Radio ID

Source

RAU IF

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

PathTraceMismatch

Consequences The protection is lost.

88

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

5.131.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.131.3

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

5.132

Radio ID (Critical) The received traffic comes from a terminal with an ID not matching the Far End ID. Possible causes for this is: â&#x20AC;˘

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

â&#x20AC;˘

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

Applicable for RAU IF (1+0).

5.132.1

SpecificProblem

Radio ID

Source

RAU IF

AlarmType

CommunicationAlarm

Severity

Critical

ProbableCause

PathTraceMismatch

Consequences No connection with far-end and traffic loss.

5.132.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.

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

89


Alarm Descriptions

3. Perform an interference check by measuring input receive level when far-end transmitter is turned off.

5.132.3

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

5.133

RAI Remote Alarm Indication (RAI)

5.134

SpecificProblem

RAI

Source

• •

AlarmType

CommunicationAlarm

Severity

Minor

ProbableCause

RemoteAlarmIndication

E2/E3 Framed E1

RCC (Major) Radio Communication Channel (RCC) Communication is lost on the RCC, between the MMU and the RAU.

5.134.1

SpecificProblem

RCC

Source

All MMUs

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

Unavailable

Consequences Transmitter is switched off which results in traffic loss.

5.135

RCC (Critical) Radio Communication Channel (RCC) The RAU is disconnected from the MMU and therefore out of service.

90

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

5.136

SpecificProblem

RCC

Source

RAU

AlarmType

CommunicationAlarm

Severity

Critical

ProbableCause

Unavailable

RDI (Minor) Remote Defect Indication (RDI) Defect detection at far end. This mechanism allows alignment of the near-end and far-end performance monitoring processes.

5.136.1

SpecificProblem

RDI

Source

• • •

AlarmType

CommunicationAlarm

Severity

Minor

ProbableCause

FarEndReceiverFailure

MS/RS VC-12 VC-4

Consequences The service is unavailable at far end.

5.136.2

Corrective Actions Check alarm at far end and take appropriate action.

5.137

RDI (Major) Remote Defect Indication (RDI) Defect detection at far end. RDI signals convey the defect status of the trail signal at the trail destination (that is, at trail termination sink function) back to the trail origin (that is, trail termination source function). This mechanism allows alignment of the near end and far end performance monitoring processes. SpecificProblem

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

RDI

91


Alarm Descriptions

Source

5.137.1

AU4

MS

TU-3

TU-12

VC-3

VC-4

VC-12

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

FarEndReceiverFailure

Consequences Service unavailable at far end.

5.137.2

Corrective Actions Check alarm on far end and take appropriate action to cease the far end alarm.

5.138

Remote Failure Indication Persistence of an RDI-IMA defect at the near-end (more than 2.5 +/- 0.5 sec). An Rx failure has been detected on the corresponding interface at the near-end IMA unit.

5.138.1

SpecificProblem

Remote Failure Indication

Source

IMA Link

AlarmType

CommunicationAlarm

Severity

Critical

ProbableCause

RemoteAlarmInterface

Consequences Since the far-end detects a failure at the corresponding interface, the link is not active anymore. Related IMA groups can also be affected by the fault: in case the IMA group goes below the "minimum number of (active) links" no Asynchronous Transfer Mode (ATM) traffic can flow at all through the group. In this case the operational status of related ATM-IMA (IMA group) and ATM

92

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

goes to down. If the IMA group still have a minimum number of links it can still transmit the guaranteed bandwidth of traffic.

5.138.2

Alarm Analysis The far-end link should experience any fault from physical (Loss Of Signal (LOS)/Loss Of Frame (LOF)/Alarm Indication Signal (AIS)) or TC (LCD) layer.

5.138.3

Corrective Actions Check that the corresponding near-end link is properly connected and configured.

5.138.4

Alarm Clearance The alarm is cleared when the far-end no longer detects any link failure.

5.139

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

5.140

SpecificProblem

Remote Tx Switch Over

Source

SWITCH

AlarmType

EquipmentAlarm

Severity

Major

ProbableCause

ProtectionPathFailure

Reserved Position The plug-in unit in this position is of a different type than the position is reserved for. SpecificProblem

Reserved Position

Source

• • •

AlarmType

EquipmentAlarm

Severity

Critical

ProbableCause

ReplaceableUnitTypeMismatch

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

Plug-in Unit RAU SFP

93


Alarm Descriptions

5.141

RF Input Level (Major) The received Radio Frequency (RF) input signal level has dropped below the threshold for the receiver. Applicable for RF (1+1).

5.142

SpecificProblem

RF Input Level

Source

RF (1+1)

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

ReceiverFailure

RF Input Level (Critical) The received Radio Frequency (RF) input signal level has dropped below the threshold for the receiver. Applicable for RF (1+0).

5.143

SpecificProblem

RF Input Level

Source

RF

AlarmType

CommunicationAlarm

Severity

Critical

ProbableCause

ReceiverFailure

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

94

SpecificProblem

RF Input Threshold

Source

• •

AlarmType

CommunicationAlarm

Severity

Warning

ProbableCause

DegradedSignal

RF SWITCH

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

5.144

RF Input Threshold Protection The Radio Frequency (RF) input level of both receivers in a protected terminal has dropped below their respective RF Input Alarm Threshold.

5.145

SpecificProblem

RF Input Threshold Protection

Source

SWITCH

AlarmType

CommunicationAlarm

Severity

Warning

ProbableCause

DegradedSignal

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

5.146

SpecificProblem

RF Output Level

Source

RF

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

TransmitterFailure

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

5.147

SpecificProblem

RF Output Level

Source

RF

AlarmType

CommunicationAlarm

Severity

Critical

ProbableCause

TransmitterFailure

RF Output Level ATPC Automatic Transmit Power Control (ATPC)

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

95


Alarm Descriptions

This alarm indicates that the ATPC Fallback functionality has been activated. The transmitter output power has been continuously at Maximum ATPC Output Power too long. This can occur due to several reasons:

5.147.1

Maximum ATPC Output Power is set too low.

The hop attenuation has increased (steady-state).

The transmitter Power Amplifier is deteriorating.

The Low Noise Amplifier in Rx is deteriorating.

SpecificProblem

RF Output Level ATPC

Source

RF

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

TransmitterFailure

Consequences The hop might be down or it may have low availability.

5.147.2

Corrective Actions Try the following: 1. Increase the Maximum ATPC Output Power. 2. Check if obstacles are placed in the radio path between the two hops’ antennas (at clear sky conditions). 3. If the RAU is faulty, replace it, see Replacing a Radio Unit, Reference [14]. To restore normal ATPC function again: 1. Disable ATPC (that is set Output Power Mode to RTPC). 2. Enable ATPC again.

5.147.3

Alarm Clearance The alarm is cleared when normal ATPC function is restored.

5.148

RL-IME Degraded Service SpecificProblem

96

Degraded Service

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

5.149

5.150

5.151

Source

RL-IME

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

Unavailable

RL-IME No Traffic SpecificProblem

No Traffic

Source

RL-IME

AlarmType

CommunicationAlarm

Severity

Critical

ProbableCause

Unavailable

RL-IME Reassembly Failure SpecificProblem

Reassembly failure

Source

RL-IME

AlarmType

QualityOfServiceAlarm

Severity

Major

ProbableCause

DegradedSignal

Running configuration not accepted The MMU/RAU/SFP could not accept the running configuration; the service LED is flashing. The unit could also be subject to a software upgrade. SpecificProblem

Running configuration not accepted

Source

• • •

AlarmType

EquipmentAlarm

Severity

Major

ProbableCause

ReplaceableUnitTypeMismatch

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

All MMUs All RAUs All SFPs

97


Alarm Descriptions

5.151.1

Corrective Actions Remove board or clear reservation.

5.152

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

5.153

SpecificProblem

Rx AFC

Source

RF

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

ReceiverFailure

RX Frequency (Major) The receiver frequency synthesizer loop is unlocked. Applicable for RF (1+1).

5.154

SpecificProblem

RX Frequency

Source

RF (1+1)

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

ReceiverFailure

RX Frequency (Critical) The receiver frequency synthesizer loop is unlocked. Applicable for RF (1+0).

98

SpecificProblem

RX Frequency

Source

RF (1+0)

AlarmType

CommunicationAlarm

Severity

Critical

ProbableCause

ReceiverFailure

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

5.155

Rx IF Input Failure on the receiver Intermediate Frequency (IF) signal from the RAU to the MMU.

5.156

SpecificProblem

Rx IF Input

Source

RAU IF

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

ReceiverFailure

Rx Link Misconnected Rx link is not connected to the same far-end Inverse Multiplexer over ATM (IMA) unit as the other Rx links in the group.

5.156.1

SpecificProblem

Rx Link Misconnected

Source

IMA Group

AlarmType

CommunicationAlarm

Severity

Critical

ProbableCause

ConfigurationOrCustomizationError

Consequences No Asynchronous Transfer Mode (ATM) traffic can be received from the specific IMA Link. Related IMA groups can also be affected by the fault: in case the IMA group goes below the "minimum number of (active) links" no ATM traffic can flow at all through the group. In this case the operational status of related ATM-IMA (IMA group) and ATM goes to down. If the IMA group still have a minimum number of links it can still receive the guaranteed bandwidth of traffic.

5.156.2

Alarm Analysis Wrong connection of the Rx IMA link.

5.156.3

Corrective Actions Connect the Rx IMA link to the same far-end IMA unit as the other Rx links in the group.

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

99


Alarm Descriptions

5.156.4

Alarm Clearance The alarm is cleared when the Rx IMA link has been correctly connected to the far-end IMA unit.

5.157

Rx Unusable (Far-End) The alarm is reported when the far-end Inverse Multiplexer over ATM (IMA) unit has determined that its Rx link cannot be used for reception in the group.

5.157.1

SpecificProblem

Rx Unusable (Far-End)

Source

IMA Group

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

RemoteAlarmInterface

Consequences No Asynchronous Transfer Mode (ATM) traffic can be transmitted over the specific IMA Link. Related IMA groups can also be affected by the fault: in case the IMA group goes below the "minimum number of (active) links" no ATM traffic can flow at all through the group. In this case the operational status of related ATM-IMA (IMA group) and ATM goes to down. If the IMA group still have a minimum number of links it can still transmit the guaranteed bandwidth of traffic.

5.157.2

Alarm Analysis A fault in the far-end link or protocol shall be detected by the IMA unit at Rx direction.

5.157.3

Corrective Actions Check the status of the far-end Rx link.

5.157.4

Alarm Clearance The alarm is cleared when the far-end Rx link failure has been removed or the cause at the corresponding near-end link.

5.158

SES 15 min threshold crossing Severely Errored Seconds (SES)

100

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

SES threshold crossing for 15 minutes composite performance monitoring. Applicable for RAU IF (1+0). Applicable for SWITCH (1+1).

5.159

SpecificProblem

SES 15 min threshold crossing

Source

• •

AlarmType

QualityOfServiceAlarm

Severity

Major

ProbableCause

ThresholdCrossed

RAU IF SWITCH

SES 24 h threshold crossing Severely Errored Seconds (SES) SES threshold crossing for 24 hours composite performance monitoring. Applicable for RAU IF (1+0). Applicable for SWITCH (1+1).

5.160

SpecificProblem

SES 24 h threshold crossing

Source

• •

AlarmType

QualityOfServiceAlarm

Severity

Major

ProbableCause

ThresholdCrossed

RAU IF SWITCH

SFP LOS (Major) SFP reports loss of signal. SpecificProblem

SFP LOS

Source

LINE RS (1+1)

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

LossOfSignal

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

101


Alarm Descriptions

5.161

SFP LOS (Critical) SFP reports loss of signal.

5.162

SpecificProblem

SFP LOS

Source

LINE RS (1+0 and active SI)

AlarmType

CommunicationAlarm

Severity

Critical

ProbableCause

LossOfSignal

SQM Sequence Indicator Mismatch (SQM) The received sequence number does not match the configured sequence number. It can be caused by Synchronous Digital Hierarchy (SDH) cross-connection misconfiguration.

5.162.1

SpecificProblem

SQM

Source

• • •

AlarmType

CommunicationAlarm

Severity

Critical

ProbableCause

CommunicationsProtocolError

VC-12 VC-3 VC-4

Consequences Interface down.

5.162.2

Corrective Actions Perform the following actions: 1. Check the SDH cross-connection configuration. 2. Check the local configuration. 3. Check the remote configuration. 4. Check the Bit Error Ratio (BER), see Troubleshooting, Reference [18].

102

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

5.162.3

Alarm Clearance The alarm is cleared when the received sequence number matches the configured sequence number. Communication recovers.

5.163

SQMULTIPLE Multiple sequence numbers received. There are two or more equal sequence numbers in different Virtual Containers (VCs).

5.163.1

SpecificProblem

SQMULTIPLE

Source

VCG/LCAS Standard Alarms

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

CommunicationsProtocolError

Corrective Actions Perform the following actions: 1. Check the remote configuration. 2. Check the Bit Error Ratio (BER), see Troubleshooting, Reference [18].

5.164

SQNC The received sequence numbers for this Virtual Concatenation Group (VCG) are not consistent (out-of-range or non-continuous).

5.164.1

SpecificProblem

SQNC

Source

VCG/LCAS Standard Alarms

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

CommunicationsProtocolError

Corrective Actions Perform the following actions: 1. Check the remote configuration. 2. Check the Bit Error Ratio (BER), see Troubleshooting, Reference [18].

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

103


Alarm Descriptions

5.165

SQNONCONT Non-continuous sequence numbers received (per Virtual Concatenation Group (VCG)).

5.165.1

SpecificProblem

SQNONCONT

Source

VCG/LCAS Standard Alarms

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

CommunicationsProtocolError

Corrective Actions Perform the following actions: 1. Check the remote configuration. 2. Check the Bit Error Ratio (BER), see Troubleshooting, Reference [18].

5.166

SQOR Sequence number out-of-range received (per Virtual Concatenation Group (VCG)).

5.166.1

SpecificProblem

SQOR

Source

VCG/LCAS Standard Alarms

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

CommunicationsProtocolError

Corrective Actions Perform the following actions: 1. Check the remote configuration. 2. Check the Bit Error Ratio (BER), see Troubleshooting, Reference [18].

5.167

104

Squelch threshold reached SpecificProblem

Squelch threshold reached

Source

NE

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

5.168

AlarmType

CommunicationAlarm

Severity

Critical

ProbableCause

LossOfSynchronisation

Starting up (Far-End) The far-end Inverse Multiplexer over ATM (IMA) unit is starting up (restarting).

5.168.1

SpecificProblem

Starting up (Far-End)

Source

IMA Group

AlarmType

CommunicationAlarm

Severity

Warning

ProbableCause

Indeterminate

Consequences No ATM traffic can be transmitted over the specific IMA group before both the near-end and far-end groups become operational.

5.168.2

Alarm Analysis The far-end IMA group has been restarted.

5.168.3

Corrective Actions Wait until the IMA group becomes operational.

5.168.4

Alarm Clearance Usually this is a temporary alarm which is cancelled as soon as the IMA group becomes operational again, or it presents another specific failure condition (for instance "Insufficient links").

5.169

TIM (Major) Trace Identified Mismatch (TIM) The detection of TIM is based on a comparison between the accepted Trail Trace Identifier (TTI) and the expected TTI, configured through the Network Management System (NMS). If TIM detection is disabled at the NMS, TIM is considered "false".

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

105


Alarm Descriptions

5.169.1

SpecificProblem

TIM

Source

AU4

RS

TU-3

TU-12

VC-3

VC-4

VC-12

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

PathTraceMismatch

Consequences Service may be unavailable.

5.169.2

5.170

Corrective Actions •

Check configuration of TxTTI at source.

Check configuration of expected TTI at sink.

Check cross-connections.

TIM (Critical) Trace Identifier Mismatch (TIM) Configuration mismatch between the expected Trail Trace identifier (TTI) and the received TTI.

106

SpecificProblem

TIM

Source

• • •

AlarmType

CommunicationAlarm

Severity

Critical

MS/RS VC-12 VC-4

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

ProbableCause

5.170.1

PathTraceMismatch

Consequences The service might be unavailable.

5.170.2

Corrective Actions Check configuration of TTI in source sink and cross-connections.

5.170.3

Alarm Clearance The alarm is cleared when the received TTI is equal to the expected TTI.

5.171

TIM Line Side Trace Identifier Mismatch (TIM) TIM at the Line side.

5.172

SpecificProblem

TIM Line Side

Source

LINE RS

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

PathTraceMismatch

TIM Radio Side Trace Identifier Mismatch (TIM) TIM at the Radio side. SpecificProblem

TIM Radio Side

Source

RADIO RS

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

PathTraceMismatch

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

107


Alarm Descriptions

5.173

TLCR Total Loss of Capacity Receive (TLCR) Link Capacity Adjustment Scheme (LCAS) has removed all members.

5.173.1

SpecificProblem

TLCR

Source

VCG/LCAS Standard Alarms

AlarmType

CommunicationAlarm

Severity

Critical

ProbableCause

BandwithReduced

Consequences Interface down.

5.173.2

Corrective Actions Perform the following actions: 1. Repair the Virtual Container (VC) trail. 2. Check the Multiplex Section (MS), Regenerator Section (RS), and L1.

5.173.3

Alarm Clearance The alarm is cleared when communication is recovered.

5.174

TLCT Total Loss of Capacity Transmit (TLCT) Probable cause is Link Capacity Adjustment Scheme (LCAS) has removed all members.

108

SpecificProblem

TLCT

Source

VCG/LCAS Standard Alarms

AlarmType

CommunicationAlarm

Severity

Critical

ProbableCause

BandwithReduced

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

5.174.1

Consequences Interface down.

5.174.2

Corrective Actions Perform the following actions: 1. Repair the Virtual Container (VC) trail. 2. Check the Multiplex Section (MS), Regenerator Section (RS), and L1.

5.174.3

Alarm Clearance The alarm is cleared when communication is recovered.

5.175

5.176

5.177

Traffic System Failure (Major) SpecificProblem

Traffic System Failure

Source

NE

AlarmType

EquipmentAlarm

Severity

Major

ProbableCause

CommunicationsSubsystemFailure

Traffic System Failure (Critical) SpecificProblem

Traffic System Failure

Source

NE

AlarmType

EquipmentAlarm

Severity

Critical

ProbableCause

CommunicationsSubsystemFailure

TULOM Tributary Unit Loss of Multiframe (TULOM) SpecificProblem

TULOM

Source

VC-4

AlarmType

CommunicationAlarm

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

109


Alarm Descriptions

5.178

Severity

Critical

ProbableCause

LossOfMultiFrame

TX Frequency (Major) Transmitter frequency synthesizer loop is unlocked. Applicable for RAU IF (1+1).

5.179

SpecificProblem

TX Frequency

Source

RF

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

TransmitterFailure

TX Frequency (Critical) Transmitter frequency synthesizer loop is unlocked. Applicable for RAU IF (1+0).

5.180

SpecificProblem

TX Frequency

Source

RF

AlarmType

CommunicationAlarm

Severity

Critical

ProbableCause

TransmitterFailure

Tx IF Input (Major) Failure on the received Intermediate Frequency (IF) signal from the MMU to the RAU. Applicable for RAU IF (1+1).

110

SpecificProblem

Tx IF Input

Source

RAU IF

AlarmType

Communication

Severity

Major

ProbableCause

TransmitterFailure

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

5.181

Tx IF Input (Critical) Failure on the received Intermediate Frequency (IF) signal from the MMU to the RAU. Applicable for RAU IF (1+0).

5.182

SpecificProblem

Tx IF Input

Source

RAU IF

AlarmType

Communication

Severity

Critical

ProbableCause

TransmitterFailure

Tx Link Misconnected The Tx link is not connected to the same far-end Inverse Multiplexer over ATM (IMA) unit as the others Tx links in the group.

5.182.1

SpecificProblem

Tx Link Misconnected

Source

IMA Group

AlarmType

CommunicationAlarm

Severity

Critical

ProbableCause

ConfigurationOrCustomizationError

Consequences No Asynchronous Transfer Mode (ATM) traffic can be transmitted over the specific IMA Link. Related IMA groups can also be affected by the fault: in case the IMA group goes below the "minimum number of (active) links" no ATM traffic can flow at all through the group. In this case the operational status of related ATM-IMA (IMA group) and ATM goes to down. If the IMA group still have a minimum number of links it can still transmit the guaranteed bandwidth of traffic.

5.182.2

Alarm Analysis Wrong connection of Tx IMA link.

5.182.3

Corrective Actions Connect the Tx IMA link to the same far-end IMA unit as the other Tx links in the group.

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

111


Alarm Descriptions

5.182.4

Alarm Clearance The alarm is cleared when the Tx IMA link has been correctly connected to the far-end IMA unit.

5.183

5.184

TX Switch Over SpecificProblem

TX Switch Over

Source

SWITCH

AlarmType

EquipmentAlarm

Severity

Major

ProbableCause

ProtectionPathFailure

Tx Unusable (Far-End) The alarm is reported when the far-end Inverse Multiplexer over ATM (IMA) unit has determined that its Tx link cannot be used for transmission in the group.

5.184.1

SpecificProblem

Tx Unusable (Far-End)

Source

IMA Group

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

RemoteAlarmInterface

Consequences No Asynchronous Transfer Mode (ATM) traffic can be received from the specific IMA Link. Related IMA groups can also be affected by the fault: in case the IMA group goes below the "minimum number of (active) links" no ATM traffic can flow at all through the group. In this case the operational status of related ATM-IMA (IMA group) and ATM goes to down. If the IMA group still have a minimum number of links it can still receive the guaranteed bandwidth of traffic.

5.184.2

Alarm Analysis A fault in the far-end link or protocol shall be detected by the IMA unit at Tx direction.

5.184.3

Corrective Actions Check the status of the far-end Tx link.

112

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

5.184.4

Alarm Clearance The alarm is cleared when the far-end Tx link failure has been removed.

5.185

5.186

Unable to Protect: E1 (Minor) SpecificProblem

Unable to Protect

Source

E1

AlarmType

CommunicationAlarm

Severity

Minor

ProbableCause

ProtectionPathFailure

Unable to Protect: E1 (Critical) The protection has failed. Both interfaces fail or the traffic is locked to a failing interface.

5.187

SpecificProblem

Unable to Protect

Source

E1

AlarmType

CommunicationAlarm

Severity

Critical

ProbableCause

ProtectionPathFailure

Unable to Protect: LPS (Major) The system is no longer able to provide protection of the line side. Loss Of Signal (LOS) or Loss Of Frame (LOF) on one path.

5.188

SpecificProblem

Unable to Protect

Source

LPS

AlarmType

Communication

Severity

Major

ProbableCause

ProtectionPathFailure

Unable to Protect: LPS (Critical) The system is no longer able to provide protection of the line side.

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

113


Alarm Descriptions

5.189

SpecificProblem

Unable to Protect

Source

LPS

AlarmType

Communication

Severity

Critical

ProbableCause

ProtectionPathFailure

Unable to Protect: MSP (Minor) The protection has failed. Failure on one of the two lines involved in an Multiplex Section Protection (MSP) configuration. Probable causes for this are:

5.189.1

The line has a fault condition (Loss Of Signal (LOS)).

One LTU 155 board is faulty (Equipment fault).

One LTU 155 board is in repair (not present).

MSP is configured on only one of the two Synchronous Transport Module level 1 (STM-1) boards.

Manual switch mode is configured (traffic is locked to one of the two lines).

SpecificProblem

Unable to Protect

Source

MSP

AlarmType

QualityOfServiceAlarm

Severity

Minor

ProbableCause

Indeterminate

Consequences Only one of the two STM-1 lines in the MSP configuration is operative. Failure of this line also will lead to complete loss of traffic.

5.189.2

Corrective Actions Check the above mentioned probable causes.

5.189.3

Alarm Clearance The alarm is cleared when the STM-1 lines are operative.

114

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

5.190

Unable to Protect: MSP (Critical) The protection has failed. Failure on both lines involved in an Multiplex Section Protection (MSP) configuration. Probable causes for this are:

5.190.1

Both lines has a fault condition (Loss Of Signal (LOS)).

Both LTU 155 boards are faulty (Equipment fault).

Both LTU 155 boards are in repair (not present).

Manual switch mode is configured (traffic is locked to one of the two lines) and this line is faulty.

SpecificProblem

Unable to Protect

Source

MSP

AlarmType

QualityOfServiceAlarm

Severity

Critical

ProbableCause

Indeterminate

Consequences Both Synchronous Transport Module level 1 (STM-1) lines in the MSP configuration are faulty. The result is complete loss of traffic.

5.190.2

Corrective Actions Check the above mentioned probable causes.

5.190.3

Alarm Clearance The alarm is completely cleared when both STM-1 lines are operative. If one of the two lines becomes operative, the alarm changes severity from Critical to Minor.

5.191

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.

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

115


Alarm Descriptions

5.192

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

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

5.193

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

Unavailable Period The Plesiochronous Digital Hierarchy (PDH) Unavailable Period counter threshold has been crossed, due to possible radio propagation problem. Applicable for RAU IF (1+0). Applicable for SWITCH (1+1).

116

SpecificProblem

Unavailable Period

Source

• •

AlarmType

QualityOfServiceAlarm

Severity

Major

RAU IF SWITCH

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

ProbableCause

5.194

PerformanceDegraded

Unavailable State Unavailable State is activated after ten consecutive Severely Errored Seconds (SES).

5.194.1

SpecificProblem

Unavailable State

Source

l • • • • • • • • • • •

AU4 E1 E2/E3 Framed E1 MS/RS MSP TU-3 TU-12 VC-3 VC-4 VC-12

AlarmType

QualityOfServiceAlarm

Severity

Critical

ProbableCause

Unavailable

Consequences Service unavailable.

5.194.2

Corrective Actions Eliminate defects that cause SES or Unavailable Seconds (UAS).

5.194.3

Alarm Clearance The alarm is cleared after ten consecutive non-SES.

5.195

Unavailable State Far End At the far end, Unavailable State is activated after ten consecutive Severely Errored Seconds (SES). SpecificProblem

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

Unavailable State Far End

117


Alarm Descriptions

5.195.1

Source

• • • • • • • •

AU4 MS/RS MSP TU-3 TU-12 VC-3 VC-4 VC-12

AlarmType

QualityOfServiceAlarm

Severity

Critical

ProbableCause

Unavailable

Consequences Service unavailable at far end.

5.195.2

Corrective Actions Eliminate defects that cause SES or Unavailable Seconds (UAS).

5.196

Unequipped (Major) The interface has no content, since the unit is not configured.

5.196.1

SpecificProblem

Unequipped

Source

• • • • • •

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

Indeterminate

AU4 TU-3 TU-12 VC-3 VC-4 VC-12

Consequences The service is unavailable.

118

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

5.196.2

Corrective Actions Check cross-connection of the alarmed path.

5.196.3

Alarm Clearance The alarm is cleared when the cross-connection is established.

5.197

Unequipped (Critical) Non-consistent configuration, the unequipped defect is detected in the C2 byte.

5.197.1

SpecificProblem

Unequipped

Source

â&#x20AC;˘ â&#x20AC;˘

AlarmType

CommunicationAlarm

Severity

Critical

ProbableCause

PayloadTypeMismatch

VC-12 VC-4

Consequences The service will be unavailable.

5.197.2

Corrective Actions Check and correct configuration.

5.197.3

Alarm Clearance The alarm is cleared when the configuration is corrected.

5.198

Unit Inaccessible The unit is not accessible. SpecificProblem

Unit Inaccessible

Source

Plug-in Unit

AlarmType

EquipmentAlarm

Severity

Minor

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

119


Alarm Descriptions

ProbableCause

5.199

ReplaceableUnitProblem

Unit Removed The unit is removed.

5.200

SpecificProblem

Unit Removed

Source

Plug-in Unit

AlarmType

EquipmentAlarm

Severity

Critical

ProbableCause

ReplaceableUnitProblem

Unsupported Unit Type The unit type is not supported by the software.

5.201

SpecificProblem

Unsupported Unit Type

Source

• • •

AlarmType

EquipmentAlarm

Severity

Critical

ProbableCause

ReplaceableUnitTypeMismatch

Plug-in Unit RAU SFP

UPM User Payload Identifier Mismatch (UPM) The User Payload Identifier (UPI) field in the received Generic Framing Procedure (GFP) frame does not match the configured value.

120

SpecificProblem

UPM

Source

GFP

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

PayloadTypeMismatch

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

5.201.1

Consequences The service is not trusted and may be unavailable.

5.201.2

Corrective Actions Correct the user payload information and check configuration in both ends of the path.

5.201.3

Alarm Clearance The alarm is cleared when the UPI field in the received GFP frame matches the configured value.

5.202

User input The Specific Problem and Severity are defined on the User Input Configuration page, see Reference [7]. SpecificProblem

User input

Source

User Input

AlarmType

EnvironmentalAlarm

Severity

User Defined

ProbableCause

5.203

Wrong NPU Software The unit needs a later (updated) NPU software release.

5.204

SpecificProblem

Wrong NPU Software

Source

Plug-in unit

AlarmType

EquipmentAlarm

Severity

Critical

ProbableCause

SoftwareEnvironmentProblem

Wrong Position The unit is in the wrong position in the AMM. SpecificProblem

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

Wrong Position

121


Alarm Descriptions

5.205

Source

Plug-in Unit

AlarmType

EquipmentAlarm

Severity

Critical

ProbableCause

ReplaceableUnitTypeMismatch

Wrong Software: Plug-in Unit The software revision on the unit is not aligned with the Software Baseline (SBL).

5.206

SpecificProblem

Wrong Software

Source

Plug-in Unit

AlarmType

EquipmentAlarm

Severity

Critical

ProbableCause

SoftwareEnvironmentProblem

WST LOS L2R (Major) Traffic failure in the transmitting direction of the Wayside Channel (only for MMU2 E/F).

5.207

SpecificProblem

WST LOS L2R

Source

RAU IF (1+1)

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

LossOfSignal

WST LOS L2R (Critical) Traffic failure in the transmitting direction of the Wayside Channel (only for MMU2 E/F).

122

SpecificProblem

WST LOS L2R

Source

RAU IF (1+0)

AlarmType

CommunicationAlarm

Severity

Critical

ProbableCause

LossOfSignal

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

5.208

WST LOS R2L (Major) The Wayside Channel Receiver on one of the MMU2 E/F in a 1+1 protection configuration detects loss of input signal.

5.208.1

SpecificProblem

WST LOS R2L

Source

RAU IF (1+1)

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

LossOfSignal

Consequences Protection lost on the Wayside Channel on MMU2 E/F.

5.208.2

Alarm Clearance The alarm is cleared when an input signal is received on the Wayside Channel on MMU2 E/F.

5.209

WST LOS R2L (Critical) The Wayside Channel Receiver on the MMU2 E/F detects loss of input signal.

5.209.1

SpecificProblem

WST LOS R2L

Source

RAU IF (1+0)

AlarmType

CommunicationAlarm

Severity

Critical

ProbableCause

LossOfSignal

Consequences Traffic is lost on the Wayside Channel on MMU2 E/F.

5.209.2

Alarm Clearance The alarm is cleared when an input signal is received on the Wayside Channel on MMU2 E/F.

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

123


Alarm Descriptions

5.210

XPIC Cable Disconnected Loss of the Cross Polarization Interference Canceller (XPIC) baseband cross-signal due to disconnected or broken XPIC cross-cable between two MMU2 F modems in XPIC mode.

5.210.1

SpecificProblem

XPIC Cable Disconnected

Source

MMU2 F

AlarmType

EquipmentAlarm

Severity

Major

ProbableCause

ReplaceableUnitMissing

Consequences Degraded receiving thresholds, performance (BER) or loss of traffic.

5.210.2

Corrective Actions Connect the XPIC cross-cable or replace the faulty one.

5.210.3

Alarm Clearance The alarm is cleared when a non faulty XPIC cross-cable is correctly connected between the two MMU2 F in XPIC mode.

5.211

XPIC LOS The alarm is raised when the Cross Polarization Interference Canceller (XPIC) baseband cross-signal between two MMU2 F in XPIC mode is lost, with the XPIC cross-cable correctly connected. Loss of the XPIC baseband cross-signal due to MMU2 F internal hardware or software fault. Not due to disconnected XPIC cross-cable.

124

SpecificProblem

XPIC LOS

Source

MMU2 F

AlarmType

CommunicationAlarm

Severity

Major

ProbableCause

LossOfSignal

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Alarms

5.211.1

Consequences Degraded receiving thresholds, performance (BER) or loss of traffic.

5.211.2

Corrective Actions Replace the MMU2 F, see Replacing an MMU, Reference [11].

5.211.3

Alarm Clearance The alarm is cleared when the XPIC baseband cross-signal is present again.

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

125


Alarm Descriptions

126

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15


Reference List

Reference List

[1]

Accessing a Network Element , MINI-LINK TN ETSI, 3/1543-CSH 109 32/1-V1

[2]

Fault Management Operations, MINI-LINK TN ETSI, 4/1543-CSH 109 32/1-V1

[3]

Handling Faulty Equipment, MINI-LINK TN ETSI, 1/1541-CSH 109 32/1-V1

[4]

Installing Outdoor Equipment, MINI-LINK TN ETSI, 1/1531-HRA 901 03/1-V1

[5]

LED Descriptions, MINI-LINK TN ETSI, 24/1543-CSH 109 32/1-V1

[6]

License Management Operations, MINI-LINK TN ETSI, 9/1543-CSH 109 32/1-V1

[7]

MINI-LINK Craft User Interface Descriptions , MINI-LINK TN ETSI, 7/1551-CSH 109 32/1-V1

[8]

Personal Health and Safety Information, 124 46-2885

[9]

Removing a Plug-In Unit, MINI-LINK TN ETSI, 20/1543-CSH 109 32/1-V1

[10] Replacing a Fan Unit, MINI-LINK TN ETSI, 42/1543-CSH 109 32/1-V1 [11] Replacing an MMU, MINI-LINK TN ETSI, 37/1543-CSH 109 32/1-V1 [12] Replacing an MMU2 CS, MINI-LINK TN ETSI, 38/1543-CSH 109 32/1-V1 [13] Replacing an NPU, MINI-LINK TN ETSI, 35/1543-CSH 109 32/1-V1 [14] Replacing a Radio Unit, MINI-LINK TN ETSI, 41/1543-CSH 109 32/1-V1 [15] Replacing an RMM, MINI-LINK TN ETSI, 36/1543-CSH 109 32/1-V1 [16] Supplementary Safety Information for MINI-LINK, 124 46-HSD 101 16/1 [17] System Safety Information, 124 46-2886 [18] Troubleshooting, MINI-LINK TN ETSI, 5/154 43-CSH 109 32/1-V1 [19] Upgrading or Downgrading a SW Baseline , MINI-LINK TN ETSI, 12/1543-CSH 109 32/1-V1

5/1543-CSH 109 32/1-V1 Uen M | 2010-02-15

127

51123212 tn alarm descriptions  

Ericsson TN Alarms Discriptions

51123212 tn alarm descriptions  

Ericsson TN Alarms Discriptions

Advertisement