Download as pdf or txt
Download as pdf or txt
You are on page 1of 295

Tellabs ® 8000 Network Manager R17A

Fault Management Problem Types

70178_03
27.11.09
Document Information

Revision History

Document No. Date Description of Changes


70178_03 27.11.09 CTE2-R has been added and the CTE2-S faults have been updated.
A new fault ECC link down has been added to Tellabs® 6300
Managed Transport System Nodes chapter.
70178_02 30.09.09 OMH2 and CTE2-S units have been added.
E1C status descriptions have been updated for the situations when
1+1 protection is activated

© 2009 Tellabs. All rights reserved.

This Tellabs manual is owned by Tellabs or its licensors and protected by U.S. and international copyright laws, conventions and
treaties. Your right to use this manual is subject to limitations and restrictions imposed by applicable licenses and copyright laws.
Unauthorized reproduction, modification, distribution, display or other use of this manual may result in criminal and civil penalties.
The following trademarks and service marks are owned by Tellabs Operations, Inc. or its affiliates in the United States and/or
other countries: TELLABS ®, TELLABS ® logo, TELLABS and T symbol ®, and T symbol ®.

Any other company or product names may be trademarks of their respective companies.

The specifications and information regarding the products in this manual are subject to change without notice. All statements,
information, and recommendations in this manual are believed to be accurate but are presented without warranty of any kind,
express or implied. Users must take full responsibility for their application of any products.

Adobe ® Reader ® are registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

2
Document Information

Terms and Abbreviations

Term Explanation
AIS Alarm Indication Signal
DMA Deferred Maintenance Alarm
FMS Fault Management System
GPT General Problem Type
MEI Maintenance Event Information
NTU Network Terminating Unit
PMA Prompt Maintenance Alarm
R Red LED
S Service alarm
SPT Specific Problem Type
Y Yellow LED

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

3
Tellabs ® 8000 Network Manager R17A 70178_03
Fault Management Problem Types © 2009 Tellabs.

4
Table of Contents

Table of Contents

About the Manual .............................................................................................................. 11

Objectives....................................................................................................................................................................... 11
Audience......................................................................................................................................................................... 11
Related Documentation .................................................................................................................................................. 11
Discontinued Products.................................................................................................................................................... 11
Document Conventions .................................................................................................................................................. 11
Documentation Feedback................................................................................................................................................12

1 General ........................................................................................................................ 13

2 GPT List....................................................................................................................... 14

3 AIU ............................................................................................................................... 19

4 CAE.............................................................................................................................. 25

5 CEU.............................................................................................................................. 28

6 CCO, CCS.................................................................................................................... 33

7 CCO-UNI, CCS-UNI ..................................................................................................... 36

8 CCU.............................................................................................................................. 39

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

5
Table of Contents

9 CXU-M.......................................................................................................................... 40

10 E1C .............................................................................................................................. 44

11 E3C .............................................................................................................................. 50

12 EAE .............................................................................................................................. 55

13 ECS .............................................................................................................................. 57

14 EPS-5T, EPS-10T......................................................................................................... 60

15 ESO-5T ........................................................................................................................ 62

16 ESU .............................................................................................................................. 66

17 FBU .............................................................................................................................. 73

18 FRU .............................................................................................................................. 79

19 GCH-A.......................................................................................................................... 83

20 GMH ............................................................................................................................. 84

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

6
Table of Contents

21 GMM............................................................................................................................. 92

22 GMU, GMU-A, GMU-M ................................................................................................ 96

23 GMX ........................................................................................................................... 104

24 GMX2 .........................................................................................................................113

25 ISD-NT, ISD-LT .......................................................................................................... 119

26 ISD-LT16 .................................................................................................................... 123

27 IUM-5T, IUM-10T, IUM-8 ............................................................................................ 127

28 LIU............................................................................................................................... 131

29 NTU-2M...................................................................................................................... 133

30 NTU-A ........................................................................................................................ 136

31 OMH, OMH-A............................................................................................................. 139

32 OMH2-8, OMH2-16 .................................................................................................... 146

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

7
Table of Contents

33 QMH ........................................................................................................................... 153

34 RBS-E1, RBS-T1 ....................................................................................................... 162

35 SBU............................................................................................................................ 165

36 SCP ............................................................................................................................ 169

37 SCU, CCU .................................................................................................................. 172

38 SCU-H ........................................................................................................................ 176

39 SMH-U........................................................................................................................ 181

40 SMU (Tellabs ® 8120 Mini Nodes M, VM, C, VG, SBM 2048 V, SBM 2048 E) ......... 191

41 SMU (Tellabs ® 8120 Mini Node PM) ........................................................................ 203

42 STU-56 ....................................................................................................................... 213

43 STU-1088, STU-2048................................................................................................. 216

44 SXU-A, SXU-B, SXU-V .............................................................................................. 219

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

8
Table of Contents

45 SXU-C ........................................................................................................................ 225

46 Tellabs ® 6300 Managed Transport System Nodes ................................................ 228

47 Tellabs ® 8110 NTUs CTE-S, CTE-S/208, CTU-S, CTU-512..................................... 241

48 Tellabs ® 8110 Network Terminating Units CTU-R, CTE-R, CTE-R/208,


STE-10M ..................................................................................................................... 245

49 Tellabs ® 8110 Network Terminating Units CTE2-R, CTE2-S ................................. 249

50 Tellabs ® 8110 Network Terminating Unit HTU-2M ................................................. 254

51 Tellabs ® 8110 Network Terminating Unit STU-160 ................................................ 258

52 Tellabs ® 8110 Network Terminating Units STU-320, STU-576, STU-1088-2W,


STU-2304 .................................................................................................................... 261

53 VCM-5T, VCM-10T, VCM-5T-A, VCM-10T-A, VCM 402, GCH-A ............................. 265

54 VMM ........................................................................................................................... 269

55 XCG............................................................................................................................ 272

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

9
Table of Contents

56 NMS ........................................................................................................................... 284

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

10
About the Manual

About the Manual

Objectives

Tellabs ® 8000 Network Manager Fault Management Problem Types document lists the fault events
gathered from the Tellabs ® 8100 managed access system network by Fault Management System.

Note that this document concentrates on Tellabs 8100 specific faults. For information on Tellabs
8600 related faults, see Tellabs ® 8600 Managed Edge System Fault Management Configuration
Guide and Tellabs 8600 NE Faults under 8000 Network Manager Basic Package - Fault
Management System in Tellabs ® 8000 network manager on-line help. For more information on
Tellabs 8800 related faults, refer to Tellabs 8800 Multiservice Router Faults under 8000 Network
Manager Basic Package - Fault Management System in Tellabs 8000 manager on-line help. For
more information on Tellabs 7100 related faults, refer to Tellabs 7100 NE Faults under 8000
Network Manager Basic Package - Fault Management System in Tellabs 8000 manager on-line help.
For more information on Tellabs 7300 related faults, refer to Tellabs 7300 NE Faults under 8000
Network Manager Basic Package - Fault Management System in Tellabs 8000 manager on-line help.

Audience

This information is aimed at system administration personnel.

Related Documentation

Tellabs ® 8100 Managed Access System Node Describes features of Tellabs 8100 network
Technical Description (12118_XX) elements.
Tellabs ® 8600 Managed Edge System Provides an overview of Tellabs 8600 system fault
Fault Management Configuration Guide management and instructions on how to configure
(50115_XX) it with CLI.

Discontinued Products

Tellabs ® 8100 Managed Access System Discontinued Products list can be found in Tellabs Portal,
www.portal.tellabs.com by navigating to Product Documentation > Managed Access > Tellabs
8100 Managed Access System (Includes all 81XX products) > Technical Documentation >
Network Element Manuals > 8100 List of Discontinued Products.

Document Conventions

This is a note symbol. It emphasizes or supplements information in the document.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

11
About the Manual

This is a caution symbol. It indicates that damage to equipment is possible if the instructions
are not followed.

This is a warning symbol. It indicates that bodily injury is possible if the instructions are not
followed.

Documentation Feedback

Please contact us to suggest improvements or to report errors in our documentation:

Email: fi-documentation@tellabs.com

Fax: +358.9.4131.2430

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

12
1 General

1 General
The fault events gathered from the Tellabs ® 8100 managed access system network by Fault
Management System contain two problem type identifiers:

• General Problem Type (GPT)


• Specific Problem Type (SPT)
The GPT number assigns a fault to one of the general problem classes. The SPT number of a fault
event is unit type specific. It identifies the fault in detail.

A fault event reported by a network unit contains two fault status fields:

• Maintenance status
• Service status
The maintenance status has three categories:

• Prompt Maintenance Alarm (PMA)


• Deferred Maintenance Alarm (DMA)
• Maintenance Event Information (MEI)
The service status of a fault event has two categories:

• Service alarm (S)


• Non-service alarm (non-S)
These alarm categories are defined in ITU-T Rec. M.20.

All CCITT references concern Blue Book, 1988. When applicable, the references to former CCITT
Recommendations have been amended to the ITU-T references. These ITU-T references are listed
with the date of the valid ITU-T Recommendation in Tellabs ® 8100 Managed Access System Node
Technical Description.

This document first lists the GPTs currently defined in the system. After this the possible fault
events of different Tellabs 8100 units are introduced by listing their GPT and SPT values followed
by the maintenance and service status and the SPT descriptive texts displayed in the alarm records
as well as their short explanations.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

13
2 GPT List

2 GPT List
General Problem Types known by the Tellabs ® 8000 network manager Fault Management System
are as follows:

GPT No. GPT Description


1 "Unpredicted fault"
2 "Reset"
3 "Installation errors"
4 "Power supply faults"
5 "Memory faults"
6 "Missing subracks"
7 "Extra subracks"
8 "Missing units"
9 "Extra units"
10 "Incorrect or missing interface module"
11 "Fatal problems in protected signal (1 + 1)"
12 "Missing interface signal"
13 "BER 10E-3"
14 "BER 10E-4"
15 "BER 10E-5"
16 "BER 10E-6"
17 "BER 10E-7"
18 "BER 10E-8"
19 "BER 10E-9"
20 "Frame far-end alarm"
21 "Multiframe far-end alarm"
22 "CRC errors from far-end"
23 "AIS"
24 "Frame alignment lost"
25 "Multiframe alignment lost"
26 "CRC faults"
27 "Loops"
28 "IA faults"
29 "Unexpected neighbor node"
30 "Buffer slips"
31 "Clock far-end alarm"

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

14
2 GPT List

GPT No. GPT Description


32 "ASIC problems"
33 "X-Connect bus problems"
34 "Master clock problems"
35 "Time-controlled connections"
36 "Start permission problems"
37 "Opto component problems"
38 "Bus sync fault"
39 "Clock fault"
40 "Missing IA activity"
41 "Configured bit overlap"
42 "AIS from X-bus"
43 "AIS in signaling"
44 "Local VTP bus problems"
45 "Cluster VTP bus problems"
46 "Fatal problems in protected SXUs"
47 "Fault database reinitialization"
48 "Unavailable state in terms of G.821"
49 "Signal quality alarm"
50 "Missing carrier"
51 "Line scanning"
52 "DTE scanning"
53 "Protection switch in forced position for 1 + 1 protection"
54 "Protection switch in forced position for protected SXUs"
55 "Incompatible system and application SW"
56 "NTU line fault"
57 "NTU power fault"
58 "Fault masks"
59 "Line tests"
60 "Performance event"
61 "Fault database reconfiguration"
62 "General HW fault"
63 "IF blocked"
64 "Input level error"
65 "Output level error"
66 "Signaling error"
67 "Errors in Tx/Rx signal"
68 "External alarm"
69 "Setup conflict"

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

15
2 GPT List

GPT No. GPT Description


70 "Authorized access"
71 "Unauthorized access attempt"
72 "No backup settings"
73 "SSF"
74 "Protection group failed"
75 "Loss of cell delineation"
76 "Call establishment error"
77 "Communications protocol error"
78 "Communications subsystem failure"
79 "Configuration or customization error"
80 "Congestion"
81 "Corrupt data"
82 "Response time excessive"
83 "Retransmission rate excessive"
84 "Software error"
85 "Storage capacity problem"
86 "Threshold crossed"
87 "Timing problem"
88 "Underlying resource unavailable"
89 "Version mismatch"
90 "Protection switchover"
91 "Performance event for G.826"
92-99 Reserved for future
100 "Indeterminate"
101 "AIS"
102 "Call setup failure"
103 "Degraded signal"
104 "Far end receiver failure"
105 "Framing error"
106 "Loss of frame"
107 "Loss of pointer"
108 "Loss of signal"
109 "Payload type mismatch"
110 "Transmission error"
111 "Remote alarm interface"
112 "Excessive BER"
113 "Path trace mismatch"
114 "Unavailable"

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

16
2 GPT List

GPT No. GPT Description


115 "Signal label mismatch"
116 "Loss of multiframe"
117 "Remote 6300 alarm"
118-150 Reserved for communications alarm related probable causes
151 "Backplane failure"
152 "Data set problem"
153 "Equipment identifier duplication"
154 "External IF device problem"
155 "Line card problem"
156 "Multiplexer problem"

157 "NE identifier duplication"


158 "Power problem"
159 "Processor problem"
160 "Protection path failure"
161 "Receiver failure"
162 "Replaceable unit missing"
163 "Replaceable unit type mismatch"
164 "Synchronization source mismatch"
165 "Terminal problem"
166 "Timing problem"
167 "Transmitter failure"
168 "Trunk card problem"
169 "Replaceable unit problem"
170-200 Reserved for equipment alarm related probable causes
201 "Air compressor failure"
202 "Air conditioning failure"
203 "Air dryer failure"
204 "Battery discharging"
205 "Battery failure"
206 "Commercial power failure"
207 "Cooling fan failure"
208 "Engine failure"
209 "Fire detector failure"
210 "Fuse failure"
211 "Generator failure"
212 "Low battery threshold"
213 "Pump failure"
214 "Rectifier failure"

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

17
2 GPT List

GPT No. GPT Description


215 "Rectifier high voltage"
216 "Rectifier low voltage"
217 "Ventilations system failure"
218 "Enclosure door open"
219 "Explosive gas"
220 "Fire"
221 "Flood"
222 "High humidity"
223 "High temperature"
224 "High wind"
225 "Ice build up"
226 "Intrusion detection"
227 "Low fuel"
228 "Low humidity"
229 "Low cable pressure"
230 "Low temperature"
231 "Low water"
232 "Smoke"
233 "Toxic gas"
234-249 Reserved for environmental alarm related probable causes.
250 "Control channel problems"
251 "DB/HW inconsistency"
252 "NMS Server component"
253 "UNIX Server component"
254 "Management system alarm"
255 Reserved for future use.
256 "Database Replication"
10000 "Alarm received from NMS/10"
10001 "Alarm received from Tellabs 6300 equipment"
10002 "Alarm received from AXC network element"
10003 "Alarm received from SNMP node"
10004 "Alarm received from Tellabs 8600 equipment"
10005 "Alarm received from MINI-LINK equipment"
10006 "Alarm received from RNC network element"
10007 "Alarm received from BTS network element"
10008 "Alarm received from Tellabs 8800 equipment"
10009 "Alarm received from Tellabs 860x equipment"
10010 "Alarm received from Tellabs 7100 equipment"

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

18
3 AIU

3 AIU
SPT GPT Status SPT Description
2 2 PMA "Reset (DXXP)"
There has been a unit reset (always detected after the
power-up of the unit).
3 3 PMA "System clock missing"
19.44 MHz clock of the AIU is missing.
4 39 PMA "16/20 Mhz clocks not locked"
19.44 MHz clock of AIU not locked with 16.896 MHz clock
of the node.
5 38 PMA "F/MSYNC problem in x-bus"
The fault is activated if X-bus synchronization pulse
transmitted by SXU is missing. A typical reason for this fault
is that SXU is missing.
6 28 PMA "IA alarm from IA monitoring"
The IA addresses do not work correctly.
7 72 PMA "Backup unit fault"
Extended backup unit not responding. Probably it is missing
or not in inventory, or the control unit of the node has a
wrong version of software.
8 4 PMA "VB1: +5 V (BUS1) "
The VB 1 voltage is below the threshold limit.
9 4 PMA "Power +12 V"
The board 12 V supply voltage is below the threshold limit.
10 2 PMA "Reset (ATMP)"
There has been a unit reset (detected always after the
power-up of the unit).
11 4 PMA "Power +3.3 V"
The board 3.3 V supply voltage is below the threshold limit.
12 4 PMA "Protected bus voltages"
Protected bus voltages are above the threshold limit (limit
depends on the calibration and the A/D resolution).
13 39 PMA "Node clock missing"
16.896 MHz node clock missing. A typical reason for this
fault is that SXU is missing.
14 36 PMA "Start permission denied"
Most likely the unit does not belong to the node configuration.
15 62 PMA "ATMP not responding"
Communication between AIU processor modules not OK.
16 5 PMA "RAM fault (Abz531) "
ABU: A background process has detected a RAM location
where the read value does not match the written test pattern.
17 5 PMA "DPRAM fault (abz531) "
ABU: An error in Dual-port RAM.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

19
3 AIU

SPT GPT Status SPT Description


18 5 PMA "EPROM fault (abz531) "
ABU: The calculated check sum does not match the stored
one.
19 5 PMA "EEPROM write error (abz531) "
ABU: Error when writing to the EEPROM memory.
20 5 PMA "EEPROM checksum error (abz531)"
ABU: The calculated check sum does not match the stored
one.
21 5 PMA "Flash write error (abz531) "
ABU: Error when writing to the flash memory (main bank).
22 5 PMA "Flash copy error (abz531) "
ABU: Error when writing to the flash memory (shadow
bank).
23 5 PMA "Flash erase error (abz531) "
ABU: Error during the erase of the flash memory (shadow
bank).
24 5 PMA "Flash duplicate error (abz531) "
ABU: Duplicated parameters (the same ID) detected during
the start-up.
25 5 PMA "Flash shadow error (abz531) "
ABU: The shadow bank of the flash is not erased during
the start-up.
26 5 PMA "Flash checksum error (abz531) "
ABU: The calculated check sum does not match the stored
one.
27 5 PMA "Missing settings (abz531) "
ABU: One of the setting structures has been corrupted in the
non-volatile memory.
28 69 PMA "Settings corrupted"
Fatal setup corruption. The unit must be configured again or
it must be replaced with a slot where the compatible unit is
registered; unit inherits settings.
29 55 PMA "Incompatible EPROM/FLASH SW"
ABU: The downloaded software (in the flash) is not
compatible with the system software in EPROMs.
30 5 PMA "Chksum err in dwnlded sw (abz531) "
ABU: The downloaded software has been corrupted.
31 55 PMA "Incompatible sw DXXP/ATMP"
Software version mismatch between DXXP (ABU) and
ATMP (ACP).
32 69 PMA "Setup data mismatch"
ACP: Conflict in the backup setting parameters (for example
an incompatible replacement unit (AIU1:4 replaced with
AIU1:1)).
33 3 PMA "Initialization error (Abz531) "
ABU: Initialization phase failed.
35 5 PMA "RAM fault (acz700x) "
ACP: A background process has detected a RAM location
where the read value does not match the written test pattern.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

20
3 AIU

SPT GPT Status SPT Description


36 5 PMA "EPROM fault (acz700x) "
ACP: The calculated check sum does not match the stored
one.
37 5 PMA "EEPROM fault (acz700x) "
ACP: Error when accessing to EEPROM.
38 5 PMA "Flash write error (acz700x) "
ACP: Error when writing to the flash memory (main bank).
39 5 PMA "Flash copy error (acz700x) "
ACP: Error when writing to the flash memory (shadow bank).
40 5 PMA "Flash erase error (acz700x) "
ACP: Error during the erase of the flash memory (shadow
bank).
41 5 PMA "Flash duplicate error (acz700x) "
ACP: Duplicated parameters (the same ID) detected during
the start-up.
42 5 PMA "Flash shadow error (acz700x) "
ACP: The shadow bank of the flash is not erased during
the start-up.
43 5 PMA "Flash checksum error (acz700x) "
ACP: The calculated check sum does not match the stored
one.
44 5 PMA "Missing settings (acz700x) "
ACP: One of the setting structures has been corrupted in the
non-volatile memory.
45 32 PMA "Cell Processor failure"
POST failure in the ATMC cell processor.
46 32 PMA "Cell Processor memory error"
ATMC SRAM memory access failure.
47 55 PMA "Incompatible EPROM/FLASH SW"
ACP:The downloaded software (in the flash) is not
compatible with the system software in EPROMs.
48 5 PMA "Checksum error in dwnlded sw"
ACP: The downloaded software has been corrupted.
49 3 PMA "Initialization error (Acz700x) "
Initialization of application SW unsuccessful (after the
power-up of the unit).
50 32 PMA "Tx FPGA fault"
POST Failure in ABP (Tx FPGA block).
51 32 PMA "Rx FPGA fault"
POST Failure in ABP (Rx FPGA block).
52 5 PMA "RAM fault"
ATM virtual trunk interface module SRAM test detected a
memory fault.
53 10 PMA "Missing module"
ATM virtual trunk or the ATM access interface module
defined in the settings is missing.
54 10 PMA "Conflict in module type"
ATM virtual trunk or the ATM access interface module: there
is a conflict between the installed module and the settings.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

21
3 AIU

SPT GPT Status SPT Description


55 27 MEI "ATM access interface module internal loopback"
An interface loop is created in the ATM access interface
module. It loops transmitted data and the clock signal back
to the interface receiver.
57 30 DMA "Rx buffer overflow "
Cells have been discarded due to the ATM Virtual Trunk
interface physical cell buffer overflow.
58 58 MEI "Fault masked/test"
Unit main block faults masked. Alarms are not generated as
consequences of fault conditions.
59 62 PMA "HW fault in module"
A severe error in the ATM virtual trunk interface module.
60 32 PMA "ATM access interface ASIC failure"
A severe ASIC failure in the ATM access interface module.
61 5 PMA "ATM access interface module EEPROM failure"
Failure to access ATM access interface module EEPROM.
62 30 PMA "ATM accessport receive fifo alarm"
ATM Access interface receiver physical layer FIFO full.
Cells have been discarded.
63 86 DMA "Unavailablity threshold crossed"
A user-defined 15-minute period threshold value for
Unavailability of ATM Access interface digital transmission
path is exceeded. See ITU-T G.827. This thresholded alarm
goes off when a full 15-minute period without this threshold
crossed has been detected.
64 86 DMA "NumESs threshold crossed"
A user-defined 15 min period threshold value for Errored
Seconds (ES) of ATM Access interface digital transmission
path is exceeded. See ITU-T G.826. This thresholded alarm
goes off when a full 15-minute period without this threshold
crossed has been detected.
65 86 DMA "NumSESs threshold crossed"
A user-defined 15-minute period threshold value for Severely
Errored Seconds (SES) of the ATM Access interface digital
transmission path is exceeded. See ITU-T G.826. This
thresholded alarm goes off when a full 15-minute period
without this threshold crossed has been detected.
66 108 PMA "Loss of Signal (LOS)"
Loss of Signal defect is declared when a supervised signal
has not had any transitions for a period of time. See ITU-T
G.783.
67 86 DMA "BIP-8 RS (B1) threshold crossed"
A user-defined threshold value for Bit Interleaved Parity
error in the Regenerator Section (B1 byte in SDH SOH)
is exceeded. This thresholded alarm goes off when a full
15-minute period without this threshold crossed has been
detected.
68 86 DMA "BIP-24 MS (B2) threshold crossed"
A user-defined threshold value for Bit Interleaved Parity
error in the Multiplexer Section (B2 bytes in SDH SOH) is
exceeded.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

22
3 AIU

SPT GPT Status SPT Description


69 86 DMA "BIP-8 PS (B3) threshold crossed"
A user-defined threshold value for Bit Interleaved Parity
error in the Path Section (B3 byte in SDH POH) is exceeded.
This thresholded alarm goes off when a full 15-minute period
without this threshold crossed has been detected.
70 68 MEI "Loss of Continuity (LOC) in management VP"
Loss of Continuity detected in the management VP
connection. See ITU-T I.610.
71 86 DMA "Excessive discarded HEC error cells"
A user-defined 15 min period threshold value for discarded
HEC errored cells exceeded. This thresholded alarm goes
off when a full 15 min period without this threshold crossed
has been detected.
72 86 DMA "Excessive discarded PROT error cells"
A user-defined 15-minute period threshold value for
discarded protocol errored cells exceeded. Protocol
errored cells are for example cells with unknown (not
assigned/configured) VPI. This thresholded alarm goes off
when a full 15-minute period without this threshold crossed
has been detected.
74 75 PMA "Loss of Cell Delineation LCD"
Out of Cell Delineation (OCD) anomaly has persisted long
enough to cause Loss of Cell Delineation (LCD) defect. See
ITU-T I.432.2.
75 80 MEI "AtmVT casual congestion alarm"
Temporary congestion detected. The ATM Virtual Trunk
interface cell buffer queue length has exceeded the
user-defined threshold value. This alarm goes off within 1
second after the queue length is below the threshold.
76 80 MEI "Atm VT congested Second alarm"
Congested second detected. The ATM Virtual Trunk interface
cell buffer queue length has exceeded the user-defined
threshold value (temporary/casual congestion threshold) for
long enough (user-defined percentage of 1 second) within 1
second period to be declared as “congested second”. This
alarm goes off within 1 second after a non-congested second.
77 80 MEI "Atm VT Persistently congested alarm"
Persistently congested period detected. ATM Virtual
Trunk interface cell buffer queue length has exceeded the
user-defined number of consecutive “congested seconds” to
be declared as “persistently congested period”. This alarm
goes off within 1 second after a non-congested second.
80 68 MEI "VP defect"
Virtual Path connection defect detected (indicated by VP-AIS
or VP-RDI reception).
81 106 PMA "Loss Of Frame (LOF)"
Loss Of Frame detected. See ITU-T G.783.
82 107 PMA "Loss Of Pointer (AU_LOP)"
Loss Of AU-Pointer detected. See ITU-T G.783.
83 101 MEI "Multiplex Section AIS (MS_AIS)"
Multiplex Section Alarm Indication Signal (AIS) detected.
See ITU-T G.783 and G.707.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

23
3 AIU

SPT GPT Status SPT Description


84 101 MEI "Path AIS (AU_AIS)"
Path (AU) Alarm Indication Signal (AIS) detected. See
ITU-T G.783 and G.707.
85 111 MEI "Multiplex Section RDI (MS_RDI)"
Multiplex Section Remote Defect Indication (RDI) detected.
See ITU-T G.783 and G.707.
86 111 MEI "Path RDI (AU_RDI)"
Path (AU) Remote Defect Indication (RDI) detected. See
ITU-T G.783 and G.707.
87 109 PMA "PayLoad Mismatch (PLM)"
PayLoad Mismatch (PLM) detected. Accepted C2 byte (in
SDH POH) codes are “0001 0011” (13H) for “ATM mapping”
and “0000 0001” (01H) for “Equipped - non-specific”. All
other codes cause PLM defect. See ITU-T G.783 and G.707.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

24
4 CAE

4 CAE
SPT GPT Status SPT Description
1 1 PMA, S "SW unpredicted"
This fault condition should never occur (or is not yet
supported).
2 2 PMA, S "Reset"
There has been a unit reset (detected always after the
power-up of the unit).
3 36 PMA, S "Start permission denied"
No start permission. The unit is not in its correct place.
4 4 PMA "Power +5 V (interface)"
The voltage is below the threshold limit (about 4.6 V
depending on the calibration and the A/D resolution).
5 4 PMA "Power +5 V (Vcc)"
The voltage is below the threshold limit (about 4.6 V
depending on the calibration and the A/D resolution).
6 4 PMA "Power +12 V"
The voltage is below the threshold limit (about 11.3 V
depending on the calibration and the A/D resolution).
7 4 PMA "Power -10 V"
The voltage is above the threshold limit (about -9.0 V
depending on the calibration and the A/D resolution).
8 4 PMA "Power -5 V (combo)"
The voltage is above the threshold limit (about -4.6 V
depending on the calibration and the A/D resolution).
9 55 PMA, S "Incompatible EPROM/FLASH SW"
The downloaded software (in the flash) is not compatible
with the system software in EPROMs.
10 55 PMS, S "Chksum err in downloaded SW"
The downloaded software has been corrupted.
11 5 PMA, S "RAM fault"
A background process has found a RAM location where the
read value does not match the written test pattern.
12 5 PMA, S "EPROM fault"
The calculated check sum does not match the stored one.
13 5 PMA "Flash write error"
Error when writing to the flash memory (main bank).
14 5 PMA "Flash copy error"
Error when writing to the flash memory (shadow bank).
15 5 PMA "Flash erase error"
Error during the erase of the flash memory (shadow bank).
16 5 PMA "Flash duplicate error"
Duplicated parameters (the same ID) detected during the
start-up.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

25
4 CAE

SPT GPT Status SPT Description


17 5 PMA "Flash shadow error"
The shadow bank of the flash is not erased during the start-up.
18 5 PMA, S "Flash check sum error"
The calculated check sum does not match the stored one.
19 3 PMA, S "Setup error"
One of the setting structures has been corrupted in the
non-volatile memory.
20 38 PMA, S "Bus sync fault"
No 8100 system bus synchronization from SXU detected.
21 40 PMA, S "BUS IA activity missing, VF"
The interface address is not activated on the cross-connection
bus by the SXU.
22 40 PMA, S "BUS IA activity missing, Sig."
The interface address is not activated on the cross-connection
bus by the SXU.
30 32 PMA, S "ASIC register error"
A faulty register in the ASIC.
31 32 PMA, S "Unit HW fault"
A hardware fault in the base unit.
32 10 PMA, S "Conflict in module type"
The module type defined in the settings does not match the
actual module type in the hardware.
33 3 PMA, S "Provisioning error"
A provisioning parameter value is not within a specific range
or a module type conflict.
40 62 PMA, S "IF combo fault"
A fault in the combo circuit used for the interface.
41 62 PMA, S "IF ADPCM fault"
A fault in the ADPCM circuit used for the interface.
42 64 DMA "IF input level error"
The input signal level is not within the parameterized limits.
43 65 DMA "IF output level error"
The output signal level is not within the parameterized limits.
44 66 DMA "IF signaling error"
Not monitored.
45 62 PMA, S "HW fault in upper module"
A fault in the upper interface module.
46 62 PMA, S "HW fault in lower module"
A fault in the lower interface module.
51 27 MEI, S "Unit loop"
The unit loop is active - all channels are looped back to the
interfaces.
52 27 MEI, S "IF loop to user"
The interface loop is active (back to the interface).
53 27 MEI, S "IF loop to net"
The interface loop is active (back to the cross-connection).
54 27 MEI, S "IF Testing"
Not monitored.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

26
4 CAE

SPT GPT Status SPT Description


60 58 MEI "Faults masked"
Faults are masked
(alarms are not generated as consequences of fault
conditions).
61 63 MEI, S "IF blocked off"
The interface has been blocked from the use.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

27
5 CEU

5 CEU
SPT GPT Status SPT Description
2 1 PMA ”Reset (DXXP)”
There has been a unit reset (detected always after the
power-up of the unit).
3 2 PMA ”System clock missing”
19.44 Mhz clock of the CEU is missing.
4 3 PMA ”16/20 Mhz clocks not locked”
19.44 Mhz clock of the CEU not locked with 16.896 Mhz
clock of the node.
5 39 PMA ”F/MSYNC problem in XBUS”
The fault is activated if X-bus synchronization pulse
transmitted by the SXU is missing. A typical reason for this
fault is that SXU is missing.
6 38 PMA ”IA alarm from IA monitoring”
The IA addresses do not work correctly.
7 28 PMA ”Backup unit fault”
Extended backup unit not responding. Probably it is missing
or not in inventory, or the control unit of the node has a
wrong version of software.
8 72 PMA ”VB 1: +5 V (BUS 1)”
The VB 1 voltage is below the threshold limit.
9 4 PMA ”Power +12 V”
The board 12 V supply voltage is below the threshold limit.
10 4 PMA ”Reset (ATMP)”
There has been a unit reset (detected always after the
power-up of the unit).
11 2 PMA ”Power +3.3 V”
The board 3.3 V supply voltage is below the threshold limit.
12 4 PMA ”Protected bus voltage”
Protected bus voltages are above the threshold limit (limit
depends on the calibration and the A/D resolution).
13 4 PMA ”Node clock missing”
16.896 Mhz node clock missing. A typical reason for this
fault is that SXU is missing.
14 39 PMA ”Start permission denied”
Most likely the unit does not belong to the node configuration.
15 36 PMA ”ATMP not responding”
Communication between CEU processor modules not OK.
16 62 PMA ”RAM fault (abz531)”
ABU: A background process has detected a RAM location
where the read value does not match the written test pattern.
17 5 PMA ”DPRAM fault (abz531)”
ABU: Dual-port RAM not OK.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

28
5 CEU

SPT GPT Status SPT Description


19 5 PMA ”EEPROM write error (abz531)”
ABU: Error during writing to the EEPROM memory.
20 5 PMA ”EEPROM checksum error (abz531)”
ABU: The calculated check sum does not match the stored
one.
21 5 PMA ”Flash write error (abz531)”
ABU: Error during writing to the flash memory (main bank).
22 5 PMA ”Flash copy error (abz531)”
ABU: Error during writing to the flash memory (shadow
bank).
23 5 PMA ”Flash erase error (abz531)”
ABU: Error during erase of the flash memory (shadow bank).
24 5 PMA ”Flash duplicate error (abz531)”
ABU: Duplicated parameters (same ID) detected during
start-up.
25 5 PMA ”Flash shadow error (abz531)”
ABU:The shadow bank of the flash is not erased during
start-up.
26 5 PMA ”Flash checksum error (abz531)”
ABU: The calculated check sum does not match the stored
one.
27 5 PMA ”Missing settings (abz531)”
ABU: One of the setting structures has been corrupted in the
non-volatile memory.
28 69 PMA ”Settings corrupted”
Fatal setup corruption. The unit must be configured again
or it must be replaced to a slot where compatible unit is
registered; unit inherits settings.
29 55 PMA ”Incompatible sw EPROM/flash”
ABU: The downloaded software (on the flash) is not
compatible with the system software on the EPROMs.
30 5 PMA ”Chksum err in dwnlded sw (abz531)”
ABU: The downloaded software has been corrupted.
31 55 PMA ”Incompatible sw DXXP/ATMP”
Software version mismatch between DXXP (ABU) and
ATMP (ACP).
32 5 PMA ”FPGA download failed”
The FPGA of ABP module failed to initialize
33 3 PMA ”Initialization error (abz531)”
ABU: Initialization phase failed.
35 5 PMA ”RAM fault (acz700x)”
ACP: A background process has detected a RAM location
where the read value does not match the written test pattern.
36 5 PMA ”EPROM fault (acz700x)”
ACP: The calculated check sum does not match the stored
one.
37 5 PMA ”EEPROM fault (acz700x)”
ACP: Error during access to EEPROM.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

29
5 CEU

SPT GPT Status SPT Description


38 5 PMA ”Flash write error (acz700x)”
ACP: Error during writing to the flash memory (main bank).
39 5 PMA ”Flash copy error (acz700x)”
ACP: Error during writing to the flash memory (shadow
bank).
40 5 PMA ”Flash erase error (acz700x)”
ACP: Error during erase of the flash memory (shadow bank).
41 5 PMA ”Flash duplicate error (acz700x)”
ACP: Duplicated parameters (same ID) detected during
start-up.
42 5 PMA ”Flash shadow error (acz700x)”
ACP: The shadow bank of the flash is not erased during
start-up.
43 5 PMA ”Flash checksum error (acz700x)”
ACP: The calculated check sum does not match the stored
one.
44 5 PMA ”Missing settings (acz700x)”
ACP: One of the setting structures has been corrupted in the
non-volatile memory.
45 32 PMA ”Cell Processor failure”
POST failure in ATMC cell processor.
46 32 PMA ”Cell Processor memory error”
ATMC SRAM memory access failure.
47 55 PMA ”Incompatible sw EPROM/flash”
ACP: The downloaded software (on the flash) is not
compatible with the system software on the EPROMs.
48 5 PMA ”Checksum error in dwnlded sw”
ACP: The downloaded software has been corrupted.
49 3 PMA ”Initialization error (acz700x)”
Initialization of application SW unsuccessful (after the
power-up of the unit).
50 5 PMA ”SBI error in ABP”
Error in SBI block of ABP(AAL1)
51 5 PMA ”UTOPIA parity error in ABP”
UTOPIA parity error in ABP (AAL1)
52 5 PMA ”RAM parity error in ABP”
RAM parity error in ABP (AAL1)
53 10 PMA ”Missing module”
ATM circuit emulation or ATM Access interface module
defined in the settings is missing.
54 10 PMA ”Conflict in module type”
ATM virtual trunk or ATM access interface module: here
there is a conflict between the installed module and the
settings.
55 27 MEI ”ATM access interface module internal loopback”
An interface loop is created in the ATM access interface
module. It loops transmitted data and the clock signal back
to the interface receiver.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

30
5 CEU

SPT GPT Status SPT Description


58 58 MEI ”Fault masked/test”
Unit interface block faults masked. Alarms are not generated
as consequences of fault conditions.
59 62 PMA ”HW fault in module ABP”
HW fault in ABP ( e.g. in AAL1 or LTA)
60 32 PMA ”ATM access interface ASIC failure”
A severe ASIC failure in the ATM access interface module.
61 5 PMA ”ATM access interface module EEPROM failure”
Failure to access ATM access interface module EEPROM.
62 30 PMA ”AtmAccessportReceiveFifoAlarm”
ATM Access interface receiver physical layer FIFO full.
Cells have been discarded.
66 108 PMA ”Loss of Signal (LOS)”
Loss of Signal defect is declared when a supervised signal
has not had any transitions for a period of time. See ITU-T
G.783.
71 86 DMA ”ExcessivediscardedHecErrorCells”
A user-defined 15 min. period threshold value for discarded
HEC errored cells exceeded.
72 86 DMA ”ExcessivediscardedProtErrorCells”
A user-defined 15 min. period threshold value for discarded
protocol errored cells exceeded. Protocol errored cells are for
example cells with unknown (not assigned/configured) VPI.
74 75 PMA ”Loss of Cell Delineation (LCD)”
Out of Cell Delineation (OCD) anomaly has persisted long
enough to cause Loss of Cell Delineation (LCD) defect. See
ITU-T I.432.2.
81 106 PMA ”Loss Of Frame (LOF)”
Loss Of Frame detected. See ITU-T G.783.
82 107 PMA ”Loss Of Pointer (AU_LOP)”
Loss Of AU-Pointer detected. See ITU-T G.783.
83 101 MEI ”Multiplex Section AIS (MS_AIS)”
Multiplex Section Alarm Indication Signal (AIS) detected.
See ITU-T G.783 and G.707.
84 101 MEI ”Path AIS (AU_AIS)”
Path (AU) Alarm Indication Signal (AIS) detected. See
ITU-T G.783 and G.707.
85 111 MEI ”Multiplex Section RDI (MS_RDI)”
Multiplex Section Remote Defect Indication (RDI) detected.
See ITU-T G.783 and G.707.
86 111 MEI ”Path RDI (AU_RDI)”
Path (AU) Remote Defect Indication (RDI) detected. See
ITU-T G.783 and G.707.
87 109 PMA ”PayLoad Mismatch (PLM)”
PayLoad Mismatch (PLM) detected. Accepted C2 byte
codes are “0001 0011” (13H) for “ATM mapping” and
“0000 0001” (01H) for “Equipped - non-specific”. All other
codes cause PLM defect. See ITU-T G.783 and G.707.
100 101 MEI ”P12s AIS”
The received 2 Mbit/s signal is AIS.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

31
5 CEU

SPT GPT Status SPT Description


101 106 PMA ”P12s Frame alignment lost”
The receiver cannot synchronize with the frame in the
received 2 Mbit/s signal.
102 104 MEI ”P12s Frame far end alarm received”
TS0/B3 is in state 1 in the received 2 Mbit/s signal.
103 91 MEI “Performance event for G.826”
At least one of the performance event counters differs from
zero during the last 15-minute period.
104 103 MEI ”P12s Degraded signal”
The configured error threshold is exceeded in the received
2 Mbit/s signal.
105 116 PMA ”Multiframe alignment lost”
The receiver cannot synchronize with the CAS multiframe in
the received 2 Mbit/s signal.
106 101 MEI ”AIS in signaling (TS16)”
There is a TS16 AIS in the received 2 Mbit/s signal.
107 29 PMA ”qosStatus”
The quality of service threshold has been exceeded for BBE,
ES or SES in the received 2 Mbit/s signal during a 24-hour
period.
108 29 PMA ”qosTrStatus”
The quality of service threshold has been exceeded for BBE,
ES or SES in the received 2 Mbit/s signal during a 15-minute
period.
109 29 MEI “Control network problem”
Control network problem detected by CEU
110 101 MEI ”VP-AIS”
A VP-LEVEL FAULT: not implemented in R1.0
111 104 MEI ”VP-RDI”
A VP-LEVEL FAULT: not implemented in R1.0
112 68 MEI ”VP-LOC”
A VP-LEVEL FAULT: not implemented in R1.0
113 68 MEI ”VC defect”
Severe VC-level fault: It can be due to CC fault, AIS or RDI
114 29 MEI ”VC traffic problem”
VC-level fault due to NNM mismatch, consistent buffer
overflow/underflow, cell loss/misinsert

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

32
6 CCO, CCS

6 CCO, CCS
SPT GPT Status SPT Description
1 1 PMA, S "Unpredicted Fault Condition"
This fault condition should never occur (or is not yet
supported).
2 2 PMA, S "Reset"
There has been a unit reset (detected always after the
power-up of the unit).
3 36 PMA, S "Start permission denied"
No start permission. The unit is not in its correct place.
4 4 PMA "Power supply +5 V (interface)"
The voltage is below the threshold limit (about 4.6 V
depending on the calibration and the A/D resolution).
5 4 PMA "Power supply +5 V (Vcc)"
The voltage is below the threshold limit (about 4.6 V
depending on the calibration and the A/D resolution).
6 4 PMA "Power supply +12 V"
The voltage is below the threshold limit (about 11.3 V
depending on the calibration and the A/D resolution).
7 4 PMA "Power supply -10 V"
The voltage is above the threshold limit (about -9.0 V
depending on the calibration and the A/D resolution).
8 4 PMA "Power supply -5 V (combo)"
The voltage is above the threshold limit (about -4.6 V
depending on the calibration and the A/D resolution).
9 55 PMA, S "Incompatible SW in EPROM and FLASH"
The downloaded software (in the flash) is not compatible
with the system software in EPROMs.
10 55 PMA, S "Check Sum Error in Downloaded Program"
The downloaded software has been corrupted.
11 5 PMA, S "RAM Fault"
A background process has found a RAM location where the
read value does not match the written test pattern.
12 5 PMA, S "EPROM Fault"
The calculated check sum does not match the stored one.
13 5 PMS "Flash Write Error"
Error when writing to the flash memory (main bank).
14 5 PMA "Flash Copy Error"
Error when writing to the flash memory (shadow bank).
15 5 PMA "Flash Erase Error"
Error during the erase of the flash memory (shadow bank).
16 5 PMA "Flash Duplicate Error"
Duplicated parameters (the same ID) detected during the
start-up.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

33
6 CCO, CCS

SPT GPT Status SPT Description


17 5 PMA "Flash Shadow Error"
The shadow bank of the flash is not erased during the start-up.
18 5 PMA, S "Flash Check Sum Error"
The calculated check sum does not match the stored one.
19 3 PMA, S "Setup error"
One of the setting structures has been corrupted in the
non-volatile memory.
20 3 PMA "Installation Error"
Parameter telling unit type (CCO/CCS) missing or is
corrupted in setup.
21 38 PMA, S "Bus sync fault"
No 8100 system bus synchronization from SXU detected.
22 40 PMA, S "BUS IA activity missing, VF"
The interface address is not activated on the cross-connection
bus by SXU.
23 40 PMA, S "BUS IA activity missing, Sig."
The interface address is not activated on the cross-connection
bus by the SXU.
24 32 PMA, S "ASIC Register error"
A faulty register in the ASIC.
25 62 PMA, S "Unit HW Fault"
A hardware fault in the base unit.
26 10 PMA, S "Conflict in module type"
The module type defined in the settings does not match the
actual module type in the hardware.
27 27 MEI, S "Unit Loop On"
The unit loop is active - all channels are looped back to the
interfaces.
29 4 PMA "Power supply +50V (Module)"
Voltage fault in CCS 50V power.
30 4 PMA "Power supply -50V (Module)"
Voltage fault in CCS -50V power.
31 58 MEI "fault mask"
Faults are masked (alarms are not generated as consequences
of fault conditions).
34 64 DMA "IF Input Level Error"
The input signal level is not within the parameterized limits.
35 65 DMA "IF Output Level Error"
The output signal level is not within the parameterized limits.
36 27 MEI, S "IF Loop to User On"
The interface loop is active (back to the interface).
37 27 MEI, S "IF Loop to Net On"
The interface loop is active (back to the cross-connection).
38 63 MEI, S "IF Blocked OFF"
The interface has been blocked from the use.
39 12 PMA, S "Loss of PBX Voltage"
PBX voltage is not detected from PBX connected to CCO.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

34
6 CCO, CCS

SPT GPT Status SPT Description


40 42 MEI, S "AIS from Network"
AIS is detected from network.
41 68 MEI, S "Overload"
Overload voltage detected in the CCO input.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

35
7 CCO-UNI, CCS-UNI

7 CCO-UNI, CCS-UNI
SPT GPT Status SPT Description
1 1 PMA "Unpredicted Fault Condition"
This fault condition should never occur (or is not yet
supported).
2 1 PMA "Software error"
Software has noted an inconsistency in its own logic.
3 1 PMA "Software error in Signaling Controller"
The main processor has received an unknown message from
the Signaling Controller.
4 2 PMA, S "Reset"
There has been a unit reset (detected always after the
power-up of the unit).
5 2 PMA, S "Reset in Signaling Controller"
There has been a reset in the Signaling Controller (detected
always after the power-up of the unit).
6 3 PMA, S "Setup error"
One of the setting structures has been corrupted in the
non-volatile memory.
7 4 PMA "Power +5 V (subrack)"
The voltage is below the threshold limit (about 4.6 V
depending on the calibration and the A/D resolution).
8 4 PMA "Power +5 V"
The voltage is below the threshold limit (about 4.6 V
depending on the calibration and the A/D resolution).
9 4 PMA "Power +12 V"
The voltage is below the threshold limit (about 11.3 V
depending on the calibration and the A/D resolution).
10 4 PMA "Power -10 V"
The voltage is above the threshold limit (about -9.0 V
depending on the calibration and the A/D resolution).
11 4 PMA "Power -20 V"
The voltage is above the threshold limit
12 5 PMA, S "RAM fault"
A background process has found a RAM location where the
read value does not match the written test pattern.
13 5 PMA, S "RAM fault in Signaling Controller"
A background process in the Signaling Controller has
detected a RAM location where the read value does not
match the written test pattern.
14 5 PMA, S "PROM fault"
The calculated check sum does not match the stored one.
15 5 PMA, S "Flash write error"
Error when writing to the flash memory (main bank).

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

36
7 CCO-UNI, CCS-UNI

SPT GPT Status SPT Description


16 5 PMA, S "Flash copy error"
Error when writing to the flash memory (shadow bank).
17 5 PMA, S "Flash erase error"
Error during the erase of the flash memory (shadow bank).
18 5 PMA, S "Flash duplicate error"
Duplicated parameters (the same ID) detected during the
start-up.
19 5 PMA, S "Flash shadow error"
The shadow bank of the flash is not erased during the start-up.
20 5 PMA, S "Flash checksum error"
The calculated check sum does not match the stored one.
21 5 PMA, S "Flash fault in Signaling Controller"
The Signaling Controller has detected an error in its own
flash memory.
22 10 PMA, S "Missing module 1"
The interface module defined in the settings is missing.
23 10 PMA, S "Missing module 2"
The interface module defined in the settings is missing.
24 10 PMA, S "Conflict in module type 1"
The module type defined in the settings does not match the
actual module type in the hardware.
25 10 PMA, S "Conflict in module type 2"
The module type defined in the settings does not match the
actual module type in the hardware.
26 25 PMA, S "Loss of multiframe sync"
Loss of multiframe synchronization state detected by the
Signaling Controller
40 27 MEI, S "Interface loop to net"
The interface loop is active (back to the cross-connection).
41 27 MEI, S "Equipment loop to net"
The equipment loop is active (back to the cross-connection).
42 27 MEI, S "Line loop to user"
The line loop is active (back to the interface).
27 32 PMA, S "ASIC fault in base unit"
The fault is activated if the difference between write/read
configuration data of ASIC has been detected.
28 36 PMA, S "Start permission denied"
No start permission. The unit is not in its correct place.
29 38 PMA, S "Bus sync fault"
No 8100 system bus synchronization from SXU detected.
30 40 PMA, S "IA activity missing"
The interface address is not activated on the cross-connection
bus by SXU.
43 42 MEI, S "AIS from Network"
AIS is detected from network.
31 55 PMA, S "Missing application program"
There is no downloaded software in flash or the revision is
wrong.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

37
7 CCO-UNI, CCS-UNI

SPT GPT Status SPT Description


32 55 PMA, S "Checksum error in downloaded SW"
The downloaded software has been corrupted.
44 58 MEI "Faults masked"
Faults are masked (alarms are not generated as consequences
of fault conditions).
33 62 PMA, S "HW fault in base unit"
A hardware fault in the base unit.
34 62 MEI "Strapping conflict"
The strapping info of the base unit PCB is not what the
software expects. Maybe the software is installed in a wrong
unit.
35 62 PMA, S "HW fault in module 1"
A hardware fault in module 1.
36 62 PMA, S "HW fault in module 2"
A hardware fault in module 2.
37 62 PMA, S "No response from Signaling Controller"
A timeout occurred when waiting response from the
Signaling Controller.
38 62 PMA, S "Error message from Signaling Controller"
The Signaling Controller returned an error to test message
(other than RAM or flash error).
45 62 PMA, S "Fault in interface"
Line interface does not work as expected.
46 63 MEI, S "IF blocked off"
The interface has been blocked from the use.
39 69 DMA "Setup conflict"
Information stored in the setup is self-contradictory.
50 4 PMA, R ”Temperature high”
Input air is too warm or fan is broken. All channels are
blocked to save hardware.
47 69 MEI "Filter coefficients missing"
The coefficients of the Signal Processing Codec Filter
(SICOFI) are missing. Default coefficients are used.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

38
8 CCU

8 CCU
See 37 SCU, CCU.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

39
9 CXU-M

9 CXU-M
SPT GPT Status SPT Description
1 1 PMA, S "SW unpredicted"
This fault condition should never occur (or is not yet
supported).
2 2 PMA, S "Reset"
There has been a unit reset (detected always after the
power-up of the unit).
3 4 PMA, S "VB 2"
The VB 2 voltage is below the threshold limit
(about 4.6 V depending on the calibration and the A/D
resolution).
4 4 PMA, S "VB 1"
The VB 1 voltage is below the threshold limit
(about 4.6 V depending on the calibration and the A/D
resolution).
5 4 PMA, S "Power +5 V"
The board logic supply voltage is below the threshold limit
(about 4.6 V depending on the calibration and the A/D
resolution).
6 4 PMA, S "Power +12 V"
The board 12 V supply voltage is below the threshold limit
(about 11.3 V depending on the calibration and the A/D
resolution).
7 4 PMA, S "VPLL"
Not monitored.
8 4 PMA, S "Power -10 V"
The board negative supply voltage is above the threshold
limit
(about -9.0 V depending on the calibration and the A/D
resolution).
9 5 PMA "Incompatible EPROM/FLASH SW"
The downloaded software (in the flash) is not compatible
with the system software in EPROMs.
10 5 PMA "Chksum err in downloaded SW"
The downloaded software has been corrupted.
11 5 PMA, S "RAM fault"
A background process has found a RAM location where the
read value does not match the written test pattern.
12 5 PMA, S "EPROM fault"
The calculated check sum does not match the stored one.
13 5 PMA, S "Flash write error"
Error when writing to the flash memory (main bank).
14 5 PMA, S "Flash copy error"
Error when writing to the flash memory (shadow bank).

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

40
9 CXU-M

SPT GPT Status SPT Description


15 5 PMA, S "Flash erase error"
Error during erase of the flash memory (shadow bank).
16 5 PMA, S "Flash duplicate error"
Duplicated parameters (the same ID) detected during the
start-up.
17 5 PMA, S "Flash shadow error"
The shadow bank of the flash is not erased during the start-up.
18 5 PMA, S "Flash check sum error"
The calculated check sum does not match the stored one.
19 5 PMA, S "Missing settings"
One of the setting structures has been corrupted in the
non-volatile memory.
20 3 PMA, S "Installation error"
SXU does not belong to the inventory.
21 33 PMA, S "X-connect DTS bus fault"
The cross-connect bus for the channel associated signaling
(the DTS bus) does not work.
22 33 PMA, S "X-connect DT bus fault"
The data cross-connect bus (the DT bus) does not work.
23 33 PMA, S "X-connect ISB bus fault"
The inter-subrack bus (ISB between the master and the slave
subrack) does not work.
24 32 PMA, S "ASIC latch fault"
An ASIC setting cannot be corrected by a checking the
background process
(CXU-M, CXU-A, CXU-S).
25 32 MEI "ASIC latch warning"
An ASIC setting is corrected by a checking the background
process
(CXU-M, CXU-A, CXU-S).
26 33 PMA, S "X-connect RAM fault"
Problem detected in the configuring cross-connect matrix.
27 34 MEI "Loss of master clock locking"
The internal clock is used and the fallback list contains
entries.
28 34 MEI "Fallback list warning"
The lowest choice is used (there are more than one choice in
the fallback list).
29 34 PMA "Loss of external clock"
The external clock input is enabled but the clock, connected
to input, is not acceptable.
30 34 PMA "Phase-locked loop alarm"
The phase-locked loop of the master clock cannot be locked
to any clock.
31 34 MEI "External clock warning"
The external clock is included in the fallback list but the
external clock input is disabled.
32 31 MEI "Clock far-end alarm, choice 1"
The state of the fallback list choice 1 indicates the clock
far-end alarm.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

41
9 CXU-M

SPT GPT Status SPT Description


33 31 MEI "Clock far-end alarm, choice 2"
The state of the fallback list choice 2 indicates the clock
far-end alarm.
34 31 MEI "Clock far-end alarm, choice 3"
The state of the fallback list choice 3 indicates the clock
far-end alarm.
35 31 MEI "Clock far-end alarm, choice 4"
The state of the fallback list choice 4 indicates the clock
far-end alarm.
36 31 MEI "Clock far-end alarm, choice 5"
The state of the fallback list choice 5 indicates the clock
far-end alarm.
37 35 MEI "Time controlled X-conn warning"
A delta fault indicating a problem when switching
time-controlled cross-connection on/off. Additional
information can be read from the error log of the time control
process.
38 5 MEI "Swp trk flash list conflict"
A corrupted swap-trunk record has been detected in the
non-volatile memory after the unit reset. The record has
been deleted.
39 5 MEI "Pass trk flash list conflict"
A corrupted passivate-trunk record has been detected in the
non-volatile memory after the unit reset. The record has
been deleted.
40 5 PMA, S "Flash list check sum error"
One of the flash lists (e.g. port descriptor list) has been
corrupted.
42 61 PMA "Reconfiguring X-conn flash DB"
The background protection process of the passive CXU-M
has detected that the cross-connect configuration is different
in the active and passive sides. The passive CXU-M is
reconfiguring itself.
43 5 MEI "Dummy X-conn commands cleared"
An uncompleted cross-connection detected in a slave after
the reset. The cross-connection has been deleted.
44 61 MEI "Slave X-conns not initialized"
The cross-connections of a slave subrack are not yet
initialized after the reset.
45 33 DMA "XD-conns not initialized "
Signaling cross-connections are not initialized.
55 34 MEI "Unstable SSM"
SSM byte values are not valid.
56 34 MEI "Faulty clock source of choice 1"
The state of fallback list entry 1 is faulty.
57 34 MEI "Faulty clock source of choice 2"
The state of fallback list entry 2 is faulty.
58 34 MEI "Faulty clock source of choice 3"
The state of fallback list entry 3 is faulty.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

42
9 CXU-M

SPT GPT Status SPT Description


59 34 MEI "Faulty clock source of choice 4"
The state of fallback list entry 4 is faulty.
60 34 MEI "Faulty clock source of choice 5"
The state of fallback list entry 5 is faulty.
61 34 PMA "Clock failure switchover fault"
A fault becomes active if the next three conditions are
fulfilled:
1. External clock is enabled.
2. External clock is in the fallback list.
3. Internal clock is in use (clocks at the FB list are not
reliable).
62 34 MEI "Fallback list entry 2 used"
Fallback list entry 2 is used.
63 34 MEI "Fallback list entry 3 used"
Fallback list entry 3 is used.
64 34 MEI "Fallback list entry 4 used"
Fallback list entry 4 is used.
65 34 MEI "Fallback list entry 5 used"
Fallback list entry 5 is used.
66 34 MEI "Internal clock used"
Internal clock is used as a master clock for node.
67 34 MEI "CXU-A ARAM inconsistency"
68 34 MEI "CXU-A ARAM restore event"

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

43
10 E1C

10 E1C
SPT GPT Status SPT Description
1 1 PMA "SW unpredicted"
This fault should never occur.
2 2 PMA "Reset"
There has been a unit reset (detected always after the
power-up of the unit). Note: This is a delta event, not an
active fault.
3 11 PMA "Loss of protected signal"
In 1+1 protection mode both interfaces IF1 and IF2 have
faults which in unprotected mode have S status.
4 69 MEI "Reading extended backup settings"
The unit is reading its extended backup settings from ext.
backup unit. Do not interrupt.
5 69 PMA "Extended settings corrupted"
Fatal setup corruption. The unit must be configured again
or it must be replaced to a slot where a compatible unit is
registered. The unit inherits settings.
6 72 PMA "No extended backup unit address"
The control unit returns no address of the extended backup
unit. The capacity of the extended backup unit may have
run out.
7 72 PMA "Extended backup unit fault"
No answer or error message from the extended backup unit
(it may be missing, it is not in inventory or SCU may have
run out of backup space).
8 38 PMA "Bus sync. fault"
The fault is activated if the X-bus synchronization pulse
transmitted by SXU is missing. A typical reason for this fault
is that SXU is missing. If only one interface unit has this
fault although there are other interface units in the subrack
then the fault is most likely in that particular unit.
9 36 PMA "Start request denied"
Most likely the unit does not belong to the node configuration.
11 5 PMA "RAM fault"
A background process has detected a RAM location where
the read value does not match the written test pattern.
12 5 PMA "File system fatal error"
Flash system failed. Replace the unit with a spare unit.
13 5 MEI "File system warning"
The flash file system is damaged.
14 5 PMA "SW checksum error on RAM"
The running application software has corrupted. The
calculated check sum does not match with the stored one
on RAM.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

44
10 E1C

SPT GPT Status SPT Description


15 5 PMA "SW checksum error on boot flash"
The boot software has corrupted. The calculated check sum
does not match with the stored one on boot flash.
18 5 PMA "Flash setup checksum error"
One of the setting structures is corrupted in the non-volatile
memory. The calculated check sum does not match with the
stored one in the flash setting structure.
19 5 PMA "Missing settings"
One of the setting structures is missing from the non-volatile
memory.
22 39 PMA "Tx clock fault"
The fault is activated if the transmit clock phase locking to
the X-bus fails.
23 40 PMA, S / "IA activity missing"
DMA The fault is activated if the unit cannot find its locked
interface address on the cross-connection bus. SXU should
activate IA on the bus if the interface is locked. The fault
status level is lowered if 1+1 protection is activated.
27 12 PMA, S / "Rx signal missing"
DMA The received signal level is below the acceptable level. The
fault status level is lowered if 1+1 protection is activated.
28 42 MEI "AIS from X-bus"
The fault is activated if the frame synchronization word and
RAI from the X-bus and TS0 B2 changes between "0" and
"1" are missing.
29 23 MEI "Rx-signal is AIS"
The fault is activated if 2 or less zeros in a 2-frame period are
recognized. The fault is deactivated if 3 or more zeros in a
2-frame period are recognized.
30 26 DMA "CRC missing"
The fault is activated if framing can be found and the CRC
multiframe alignment has been lost for 100-200 ms. The
fault is deactivated if the multiframe alignment has been
found. This fault indicates that the remote end most likely
does not use CRC.
31 26 PMA, S / "Frame alignment lost by CRC"
DMA See CCITT G.706 Frame alignment recovery (2048 mode
≥ 915 CRC block errors detected). The fault status level is
lowered if 1+1 protection is activated.
32 24 PMA, S / "Frame alignment lost"
DMA See CCITT G.706 Loss of frame alignment. The fault status
level is lowered if 1+1 protection is activated.
33 103 DMA "Degraded protected signal"
In 1+1 protected mode the selected 2 Mbit/s signal has a
signal degraded fault.
37 29 PMA, S / "No response to NNM message"
DMA The control channel of the interface is used and the neighbor
node supervision option of the interface is on and no NNM
(Neighbor Node Monitoring) message has been received
from the interface within 8 seconds. The fault status level is
lowered if 1+1 protection is activated.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

45
10 E1C

SPT GPT Status SPT Description


38 29 PMA, S / "Own NNM messages received"
DMA The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received
NNM message contains the same identification data as the
NNM message sent to the interface. The fault status level is
lowered if 1+1 protection is activated.
39 29 PMA, S / "Wrong IDs in NNM messages"
DMA The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received
NNM message contains unexpected neighbor identification
data. The fault status level is lowered if 1+1 protection is
activated.
40 27 MEI "Interface loop"
An interface loop is created on physical line interface chip.
It loops the transmit data and the clock signal back to the
interface receiver (back to the equipment). AIS is sent from
the interface and the yellow alarm LED is switched on.
41 27 MEI "Equipment loop"
Similar to the interface loop except that the loop is made on
MUX/DEMUX.
42 27 MEI "Loop: MUX/DEMUX back to line"
Rx data is looped back to the interface transmitter. When the
HDLC channel is used, it works with this line loop. All other
bits are looped back to the interface.
43 27 MEI "Line loop made by neighbor"
This alarm is activated if the HDLC channel is in use and
MUX/DEMUX back to the line loop has been activated from
the remote end.
44 27 MEI "Remote controlled line loop"
This alarm is activated if the HDLC channel is in use and
MUX/DEMUX back to the line loop has been activated to
the neighbor unit.
45 43 MEI "AIS in signaling"
The fault is activated if a signal in the signaling timeslot
contains less than 2 zeros during a multiframe period.
50 25 PMA, S / "MFrame alignment lost"
DMA The fault is activated if two consecutive faulty multiframe
alignment words are received or if all signaling time slots
in one multiframe contain only zeros ("0"). The fault is
deactivated when the frame alignment is detected and the
first four bits of the signaling timeslot are found to be zeros
("0") and when the prior signaling timeslot had at least one
bit in state "1". The fault status level is lowered if 1+1
protection is activated.
55 20 MEI "Frame far-end alarm"
The state of the far-end alarm bit TS0 B3 will be switched
if the opposite state is received in 3 consecutive frames.
State "1" is used for alarm. Alarm status depends on fault
consequences (AIS insertion into the signaling timeslot).
56 20 MEI "Frame far-end alarm"
The state of the far-end alarm bit TS0 B3 will be switched
if the opposite state is received in 3 consecutive frames.
State "1" is used for alarm. Alarm status depends on fault
consequences (AIS insertion into the signaling timeslot).

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

46
10 E1C

SPT GPT Status SPT Description


57, 58 21 MEI "MFrame far-end alarm"
The state of signaling timeslot’s frame 0 B6 alarm bit will be
switched if the opposite state is received in 3 consecutive
frames. State "1" is used for alarm. Alarm status depends on
fault consequences (AIS insertion into the signaling timeslot).
68 58 MEI "Faults masked/test"
The fault is activated when the interface Fault mask setting is
on (all interface faults are cleared).
69 30 DMA "Frequency difference in Rx signal"
The frequency of the received 2 Mbit/s signal has offset with
the node clock.
70 30 MEI "Buffer slip(s)/1 hour"
The fault is activated if one or more buffer slip(s) have been
detected during the last hour.
71 41 DMA "HDLC overlap with X-bus"
The fault is activated if the HDLC control channel bit(s) are
also used by the cross-connection bus.
72 41 DMA "MCLK RAI overlap with X-bus"
The fault is activated if the MCLK/RAI bit is also used by
the cross-connection bus.
73 32 PMA "ASIC register error"
The fault is activated if the difference between write/read
configuration data of ASIC has been detected.
78 69 DMA "Port locking conflict"
The fault is activated if SXU has the port descriptor but the
unit interface is unlocked or SXU does not have the port
descriptor although the interface is locked. Use lock/unlock.
79 53 MEI "Protection switch forced"
The unit is in 1+1 protected mode and the protection switch
has been forced to select signal from IF1 or IF2.
82 112 PMA, S / "Excessive errors"
DMA Once every second, block errors shall be compared with the
limit value. If errors count ≥ limit, the one second shall be
declared BAD, otherwise it shall be declared GOOD. The
Excessive errors shall be detected if M consecutive BAD
seconds have occurred. The Excessive errors shall be cleared
if M consecutive GOOD seconds have occurred. The values
of M range from 2 to 9. The fault status level is lowered if
1+1 protection is activated.
83 103 DMA "Degraded errors"
Once every second, block errors shall be compared with the
limit value. If errors count ≥ limit, the one second shall be
declared BAD, otherwise it shall be declared GOOD. The
Degraded errors shall be detected if M consecutive BAD
seconds have occurred. The Degraded errors shall be cleared
if M consecutive GOOD seconds have occurred. The values
of M range from 2 to 9.
84 91 MEI "Performance event"
This fault is activated as a delta fault when G.826 supervision
is used if at least one performance event has occurred in a
15-minute period. (for Tellabs 8000 manager purposes only)

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

47
10 E1C

SPT GPT Status SPT Description


87 114 PMA, S / "Unavail (G.826)"
DMA A period of unavailable time begins at the onset of ten
consecutive SES events. These ten seconds are considered to
be part of unavailable time. A new period of available time
begins at the onset of ten consecutive non-SES events. These
ten seconds are considered to be part of available time. The
fault status level is lowered if 1+1 protection is activated.
88 114 PMA, S / "Unavail far end"
DMA A period of far end unavailable time (only when
unidirectional performance collection used) begins at the
onset of ten consecutive far end SES events. These ten
seconds are considered to be part of far end unavailable time.
A new period of available time begins at the onset of ten
consecutive non-far end SES events. These ten seconds are
considered to be part of available time. The fault status level
is lowered if 1+1 protection is activated.
89 49 DMA "Qos"
Quality of service. Quality of signal in 24–hour period. At
least one of the BBE, ES or SES limits exceeded. Cleared
when the period changes.
90 49 DMA "Qostr"
Quality of service, threshold reset. Quality of signal in a
15-minute period. At least one of the upper ES, BBE or SES
limits exceeded. Cleared when found a period where the
lower ES, BBE or SES limits has not been exceeded.
92 55 PMA "HW/SW version conflict"
The software is in a wrong unit or in a wrong unit version.
96 53 MEI "Ring force switch"
Ring protection force switch (loop) is active (this control is
activated by the user and no timeout for this exists).
97 20 MEI "Pilot bit far end alarm"
A pilot bit far end alarm is detected from the X-bus.
98 42 MEI "Pilot bit AIS"
Pilot bit AIS (S-status) is detected from the X-bus.
99 27 MEI "Ring protection loop"
Ring protection loop is active (an S-status fault in the Rx
signal causes this).
100 53 MEI "Ring lockout from protection"
Ring protection is locked out from protection -> protection
loop will not be made even if the Rx signal has the S-status
fault active (this control is activated by the user and no
timeout for this exists).
200 5 PMA "Downloaded SW missing"
The application software cannot be started, because the
downloaded software is missing. The unit is not operational
until new software has been downloaded.
201 5 PMA "Downloaded SW in reset loop"
The application software cannot be started due to a fatal
error. The unit is not operational until new software has been
downloaded.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

48
10 E1C

SPT GPT Status SPT Description


202 5 PMA "Downloaded SW incompatible"
The application software cannot be started, because
the permanent boot software is incompatible with the
downloaded application software in the flash. The unit is not
operational until new software has been downloaded.
203 5 PMA "Downloaded SW checksum error"
The application software cannot be started, because the
downloaded application software has corrupted. The
calculated check sum does not match with the one stored in
downloadable flash. The unit is not operational until new
software has been downloaded.
204 5 PMA "Downloaded SW disabled"
The application software cannot be started, because the
application software is disabled. The unit is not operational
until new software has been downloaded.
205 5 PMA "Downloaded SW faulty"
The application software cannot be started, because the
downloaded file is invalid. The unit is not operational until
new software has been downloaded.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

49
11 E3C

11 E3C
SPT GPT Status SPT Description
1 1 PMA "SW unpredicted"
This fault should never occur.
2 2 PMA "Reset"
The unit has been reset (the fault detected always after the
power-up).
3 11 PMA "Loss of protected signal"
In 1+1 protected mode both received 2 Mbit/s signals have
a fault (S status).
4 4 PMA "Power supply +5V"
The output voltage of the unit power supply module is below
the threshold.
5 4 PMA "Power supply +12V"
The output voltage of the unit power supply module is below
the threshold.
6 4 PMA "Power supply -10V"
The output voltage of the unit power supply module is below
the threshold.
7 4 PMA "Power supply +3.3V"
The output voltage of the unit power supply module is below
the threshold.
8 38 PMA "Xbus synchr. Pulse failed"
The unit does not receive X-bus synchronization signals. A
typical reason for this fault is that SXU is missing. If only
one of the units in the subrack has this fault, the fault is most
likely in the E3C unit.
9 36 PMA "Start request denied"
Most likely the unit does not belong to the node configuration.
10 3 PMA "Initialization error"
The initialization of the application software was
unsuccessful (after the power-up of the unit).
11 5 PMA "CPU RAM fault"
A background process has detected a RAM location where
the read value does not match with the written test pattern.
12 5 PMA "Flash file system fatal error"
Flash system has failed. Replace the unit with a spare unit.
13 5 MEI "Flash file system warning"
The flash file system is damaged.
14 5 PMA "SW checksum error in RAM"
The calculated check sum does not match with the stored
one on RAM.
16 5 PMA "SW checksum error in download Flash"
The calculated check sum does not match with the stored
one on downloadable flash.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

50
11 E3C

SPT GPT Status SPT Description


19 5 PMA "Missing settings"
One of the setting structures is missing in the non-volatile
memory.
22 39 PMA "Tx Clock fault"
The unit can not lock to the node clock.
23 40 PMA "Xbus address activity missing"
The unit does not receive its X-bus address. If other units in
the subrack do not report this fault, E3C is presumed to be
faulty.
28 42 MEI "AIS from X-bus"
The 2 Mbit/s framer of the unit cannot synchronize with
TS0 from the X-bus in the mode where TS0 is transported
to the 8100 network.
29 23 MEI "E1 AIS received"
There is AIS in the received 2 Mbit/s signal.
30 26 DMA "E1 CRC missing"
The receiver cannot synchronize with the CRC4 multiframe
in the received 2 Mbit/s signal. This fault most likely
indicates that the remote end does not use CRC4.
31 26 PMA "E1 Loss of frame alignment by CRC"
The receiver cannot synchronize with the frame in the
received 2 Mbit/s signal due to > 915 CRC block errors.
32 24 PMA "E1 Loss of frame alignment"
The receiver cannot synchronize with the frame in the
received 2 Mbit/s signal.
33 103 DMA "Degraded protected signal"
In 1+1 protected mode the selected 2 Mbit/s signal has a
signal degraded fault.
37 29 PMA "No response to NNM message"
The neighbor node supervision of the interface is on and no
NNM message has been received from the interface within
8 seconds.
38 29 PMA "Own NNM messages received"
The neighbor node supervision of the interface is on and the
received NNM message contains the same identification data
as sent to the interface.
39 29 PMA "Wrong IDs in NNM messages"
The neighbor node supervision of the interface is on and the
received NNM message contains unexpected identification
data.
41 27 MEI "Equipment loop"
The transmitted 2 Mbit/s signal is looped back to the X-bus
direction.
42 27 MEI "Line loop"
The received 2 Mbit/s is looped back to the 34 Mbit/s
interface.
43 27 MEI "Line loop made by neighbor"
The node at the remote end of the 2 Mbit/s trail has activated
a line loop via the HDLC control channel.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

51
11 E3C

SPT GPT Status SPT Description


44 27 MEI "Remote controlled line loop"
The unit has activated a remote line loop to the node at
the remote end of the 2 Mbit/s trail via the HDLC control
channel.
45 43 MEI "Rx signal AIS in TS16 (CAS)"
There is a TS16 AIS in the received 2 Mbit/s signal.
46 69 MEI "Reading extended backup settings"
The unit is reading its extended backup settings from the
extended backup unit. Do not interrupt.
47 69 PMA "Extended settings corrupted"
Fatal setup corruption. The unit must be reconfigured or it
must be moved to a slot where a compatible unit is registered.
The unit inherits settings.
48 72 PMA "No extended backup unit address"
The control unit returns no address of the extended backup
unit. The capacity of the extended backup unit may have
run out.
49 72 PMA "Extended backup unit fault"
No answer or error message from the extended backup unit
(it may be missing, it is not in inventory or it may have run
out of backup space).
50 25 PMA "CAS frame alignment lost"
The receiver cannot synchronize with the CAS multiframe in
the received 2 Mbit/s signal.
55 20 MEI "E1 Remote defect (RDI), action enabled"
TS0/B3 is in state 1 in the received 2 Mbit/s signal, AIS
inserted into TS16.
56 20 MEI "E1 Remote defect (RDI), action disabled"
TS0/B3 is in state 1 in the received 2 Mbit/s signal.
57 21 MEI "TS16 remote defect (RDI), action enabled"
The receiver cannot synchronize with the CAS multiframe in
the received 2 Mbit/s signal.
58 21 MEI "TS16 remote defect (RDI), action disabled"
Frame 0/TS16/B6 has been received in state 1.
60 12 PMA "E3 received signal missing"
34 Mbit/s received line signal is lost.
61 23 MEI "E3 AIS received"
There is AIS in the 34 Mbit/s received line signal.
62 24 PMA "E3 Loss of frame alignment"
Frame alignment to the received 34 Mbit/s signal has failed.
63 20 MEI "E3 Remote defect indication (RDI)"
The 34 Mbit/s received line signal has B11 in state 1.
64 23 MEI "E2 AIS received"
There is AIS in the 8 Mbit/s received signal.
65 24 PMA "E2 Loss of frame alignment"
Frame alignment to the received 8 Mbit/s signal has failed.
66 20 MEI "E2 Remote defect indication (RDI)"
The 8 Mbit/s received line signal has B11 in state 1.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

52
11 E3C

SPT GPT Status SPT Description


68 58 MEI "Faults masked"
The operator has set the Fault Mask on for the 2 Mbit/s
interface (all faults in this interface are cleared).
69 30 DMA "Frequency difference in rx signal"
The frequency of the received 2 Mbit/s signal has offset with
the node clock.
70 30 MEI "Buffer slips/1 hour"
One or more buffer slips have been detected during the last
hour (the received signal has offset).
71 41 DMA "HDLC timeslot conflict with X-bus"
HDLC control channel bits are also configured for payload
cross-connection.
72 41 DMA "Master clock RAI overlap with X-bus"
RAI bits are also configured for payload cross-connection.
73 32 PMA "ASIC register error"
A mismatch in ASIC configuration data has been detected.
78 69 DMA "Port locking conflict"
The fault is activated if SXU has the port descriptor but
the interface of the unit is unlocked or SXU does not have
the port descriptor although the interface is locked. Use
lock/unlock.
79 53 MEI "Forced protection switch"
The 2 Mbit/s interface is in 1+1 protected mode and the
protection switch has been forced to either interface.
81 5 PMA "Flash setup checksum error"
The calculated check sum does not match with the stored
one on flash.
82 112 PMA/DMA1 "E1 Excessive errors"
The configured error threshold is exceeded in the received
2 Mbit/s signal.
83 103 PMA /DMA1 "E1 Degraded signal"
The configured error threshold is exceeded in the received
2 Mbit/s signal.
84 91 MEI "G.826 performance event"
E3C has non-zero performance data available for 8100
manager.
87 114 PMA "G826 unavailable state bidir/unidir near end"
In bidirectional operation the 2 Mbit/s signal is unavailable
in either or both directions of transmission (10 consecutive
SES seconds).
88 114 PMA "G826 unavailable state unidir far end"
In unidirectional operation the 2 Mbit/s received signal is
unavailable at the far end (10 consecutive SES seconds).
89 49 DMA "G826 24 h threshold crossing QOS"
The quality of service threshold has been exceeded for BBE,
ES or SES in the received 2 Mbit/s signal during a 24-hour
period.

1Configurable

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

53
11 E3C

SPT GPT Status SPT Description


90 49 DMA "G826 15 m threshold crossing QOSTR"
The quality of service threshold has been exceeded for BBE,
ES or SES in the received 2 Mbit/s signal during a 15-minute
period.
92 55 PMA "HW/SW version conflict"
The software is in a wrong unit or in a wrong unit version.
96 53 MEI "Ring force switch"
The ring protection switch is forced active.
97 20 MEI "Pilot bit remote alarm (TS0/Bj from Xbus)"
The 2 Mbit/s framer of the unit has detected pilot bit far end
indication bit from the X-bus in the mode where pilot bits are
transported in the 8100 network.
98 42 MEI "Pilot bit AIS (TS0/BI from Xbus)"
The 2 Mbit/s framer of the unit has detected pilot bit AIS
indication bit (S-status) from the X-bus in the mode where
pilot bits are transported in the 8100 network.
99 27 MEI "Ring protection loop"
The ring protection switch is activated.
100 53 MEI "Ring lockout from protection"
The protection switch has denied access to the protecting
path.
200 5 PMA "Boot SW: Downloaded SW missing"
The application software cannot be started, because the
downloaded software is missing. The unit is not operational
until new software has been downloaded.
201 5 PMA "Boot SW: Downloaded SW in reset loop"
The application software cannot be started due to a fatal
error. The unit is not operational until new software has been
downloaded.
202 5 PMA "Boot SW: Downloaded SW incompatible"
The application software cannot be started, because
the permanent boot software is incompatible with the
downloaded application software in the flash. The unit is not
operational until new software has been downloaded.
203 5 PMA "Boot SW: Downloaded SW checksum error"
The application software cannot be started, because the
downloaded application software has corrupted. The
calculated check sum does not match with the one stored in
downloadable flash. The unit is not operational until new
software has been downloaded.
204 5 PMA "Boot SW: Downloaded SW disabled"
The application software cannot be started, because the
application software is disabled. The unit is not operational
until new software has been downloaded.
205 5 PMA "Boot SW: Downloaded SW faulty"
The application software cannot be started, because the
downloaded file is invalid. The unit is not operational until
new software has been downloaded.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

54
12 EAE

12 EAE
SPT GPT Status SPT Description
1 1 PMA, S "SW unpredicted"
This fault condition should never occur (or is not yet
supported).
2 2 PMA, S "Reset"
There has been a unit reset (detected always after the
power-up of the unit).
3 36 PMA, S "Start request denied"
No start permission. The unit is not in its correct place.
4 4 PMA "Power +5 V (interface)"
The voltage is below the threshold limit
(about 4.6 V depending on the calibration and the A/D
resolution).
5 4 PMA "Power +5 V (Vcc)"
The voltage is below the threshold limit
(about 4.6 V depending on the calibration and the A/D
resolution).
6 4 PMA "Power +12 V"
The voltage is below the threshold limit
(about 11.3 V depending on the calibration and the A/D
resolution).
7 4 PMA "Power -10 V"
The voltage is above the threshold limit
(about -9.0 V depending on the calibration and the A/D
resolution).
8 55 PMA, S "Incompatible EPROM/FLASH SW"
The downloaded software (in the flash) is not compatible
with the system software in EPROMs.
9 55 PMA, S "Chksum err in downloaded SW"
The downloaded software has been corrupted.
11 5 PMA, S "RAM fault"
A background process has detected a RAM location where
the read value does not match the written test pattern.
12 5 PMA, S "EPROM fault"
The calculated check sum does not match the stored one.
13 5 PMA "Flash write error"
Error when writing to the flash memory (main bank).
14 5 PMA "Flash copy error"
Error when writing to the flash memory (shadow bank).
15 5 PMA "Flash erase error"
Error during the erase of the flash memory (shadow bank).
16 5 PMA "Flash duplicate error"
Duplicated parameters (the same ID) detected during the
start-up.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

55
12 EAE

SPT GPT Status SPT Description


17 5 PMA "Flash shadow error"
The shadow bank of the flash is not erased during the start-up.
18 5 PMA, S "Flash check sum error"
The calculated check sum does not match the stored one.
19 3 PMA, S "Setup error"
One of the setting structures has been corrupted in the
non-volatile memory.
20 55 PMA "SW error"
A software condition that should never happen.
21 38 PMA, S "Bus sync fault"
No 8100 system bus synchronization from SXU detected.
22 40 PMA, S "BUS IA activity missing, VF"
The interface address is not activated on the cross-connection
bus by SXU.
23 32 PMA, S "ASIC register error"
A faulty register in the ASIC.
24 32 PMA, S "Unit HW fault"
A hardware fault in the base unit.
25 10 PMA, S "Conflict in module type"
The module type defined in the settings does not match the
actual module type in the hardware.
26 69 PMA "Port conflict"
A conflict in port descriptors between the unit and SXU.
27 62 PMA, S "HW fault in module 1"
A fault in the upper interface module.
28 62 PMA, S "HW fault in module 2"
A fault in the lower interface module.
29 38 PMA "MSYN missing"
The ADPCM circuits cannot be used.
31 58 MEI "Faults masked"
Faults are masked
(alarms are not generated as consequences of fault
conditions).

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

56
13 ECS

13 ECS
SPT GPT Status SPT Description
1 1 PMA, S "Software Unpredicted"
This fault condition should never occur (or is not yet
supported).
2 2 PMA "Unit in Reset"
There has been a unit reset (detected always after the
power-up of the unit).
3 4 PMA "Power Backplane +5V"
The voltage is below the threshold limit (about 4.6 V
depending on the calibration and the A/D resolution).
4 4 PMA "Power PDF +5V"
The voltage is below the threshold limit (about 4.6 V
depending on the calibration and the A/D resolution).
5 4 PMA "Power +12V"
The board 12 V supply voltage is below the threshold limit
(about 11.3 V depending on the calibration and the A/D
resolution).
6 4 PMA "Power -10V"
The board negative supply voltage is above the threshold
limit (about -9.0 V depending on the calibration and the
A/D resolution).
7 5 PMA, S "RAM Fault UBU"
A background process has detected a RAM location where
the read value does not match the written test pattern.
8 5 PMA, S "RAM Fault Interface module 1"
A background process has detected a RAM location where
the read value does not match the written test pattern.
9 5 PMA, S "RAM Fault Interface module 2"
A background process has detected a RAM location where
the read value does not match the written test pattern.
10 5 PMA, S "EPROM Fault"
The calculated check sum does not match the stored one.
11 5 PMA "Flash write error"
Error when writing to the flash memory (main bank).
12 5 PMA "Flash copy error"
Error when writing to the flash memory (shadow bank).
13 5 PMA "Flash erase error"
Error during the erase of the flash memory (shadow bank).
14 5 PMA "Flash duplicate error"
Duplicated parameters (the same ID) detected during the
start-up.
15 5 PMA "Flash shadow error"
The shadow bank of the flash is not erased during the
start-up.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

57
13 ECS

SPT GPT Status SPT Description


16 5 PMA, S "Flash check sum error"
Parameter setting check sum error detected.
17 5 PMA, S "Setup Structure Error"
One of the setting structures has been corrupted in the
non-volatile memory.
18 10 PMA, S "Wrong or missing If mod1"
Wrong or missing interface module detected.
19 10 PMA, S "Wrong or missing If mod2"
Wrong or missing interface module detected.
36 14 PMA "BER 10 -4"
Bit error rate is more than 10E-4.
37 15 PMA "BER 10-5"
Bit error rate is more than 10E-5.
38 16 PMA "BER 10-6"
Bit error rate is more than 10E-6.
39 20 MEI "Frame Far End Alarm"
Frame is lost at the far-end.
40 23 MEI, S "AIS"
Signal from line is AIS.
41 24 PMA, S "Frame Alignment Lost"
See G.706 Loss of frame alignment.
42 27 MEI,S "Channel in Loopback"
Channel loop is active.
20 32 PMA, S "ASIC Error"
Error detected in the ASIC.
21 32 PMA, S "Unit Hardware Error"
Unit Hardware Error
22 32 PMA, S "FPGA Error Interface module 1"
FPGA Error in interface module 1
23 32 PMA, S "FPGA Error Interface module 2"
FPGA Error in interface module 2
24 36 PMA, S "Start Permission Denied"
No start permission. The unit is not in its correct place
25 38 PMA, S "Bus Sync Fault"
No 8100 system bus synchronization from SXU detected.
26 40 PMA, S "IA Activity Missing CIF1 P1"
The interface address is not activated on the cross-connection
bus by SXU.
27 40 PMA, S "IA Activity Missing CIF1 P2"
The interface address is not activated on the cross-connection
bus by SXU.
28 40 PMA, S "IA Activity Missing CIF2 P1" The interface address is not
activated on the cross-connection bus by the SXU.
29 40 PMA, S "IA Activity Missing CIF2 P2"
The interface address is not activated on the cross-connection
bus by SXU.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

58
13 ECS

SPT GPT Status SPT Description


43 48 PMA, S "G.821 Unavailable state"
The fault is activated if G.821 supervision is used and the
state of the signal becomes unavailable (10 consecutive SES
seconds). The fault is deactivated when 10 consecutive
seconds not classified as SES have been found.
30 55 PMA "Incompatible EPROM/FLASH SW"
The downloaded software (in the flash) is not compatible
with the system software in EPROMs
31 55 PMA, S "Dnl Program Checksum Error"
The downloaded software has been corrupted.
45 58 MEI "Faults Masked"
Faults are masked.
44 60 PMA, S "Performance Event"
This fault is activated as a delta fault if the G.821 supervision
is used and at least one performance limit has been exceeded
in a 15-minute period.
32 62 PMA, S "HW Err Interface Module 1"
Fault in the interface module 1.
33 62 PMA, S "HW Err Interface Module 2"
Fault in the interface module 2.
34 62 PMA, S "Dsp Comm Err Interface Mod1"
Dsp communication errors in the interface module 1.
35 62 PMA, S "Dsp Comm Err Interface Mod2"
Dsp communication errors in the interface module 2.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

59
14 EPS-5T, EPS-10T

14 EPS-5T, EPS-10T
SPT GPT Status SPT Description
1 1 PMA "SW unpredicted"
This fault condition should never occur (or is not yet
supported).
2 1 PMA, S "DSP application failure"
Digital signaling processor application version failure.
3 2 PMA "Reset"
There has been a unit reset (detected always after the
power-up of the unit).
4 3 PMA "Setup structure corrupted"
One of the setting structures has been corrupted.
5 4 PMA "Power +5 V (subrack)"
The voltage is below the threshold limit (about 4.6 V
depending on the calibration and the A/D resolution).
6 4 PMA "Power +5 V"
The voltage is below the threshold limit (about 4.6 V
depending on the calibration and the A/D resolution).
7 4 PMA, S "Power +12V"
The board 12 V supply voltage is below the threshold limit
(about 11.3 V depending on the calibration and the A/D
resolution).
8 4 PMA "Power -10V"
The board negative supply voltage is above the threshold
limit (about -9.0 V depending on the calibration and the A/D
resolution).
9 5 PMA, S "RAM fault"
A background process has detected a RAM location where
the read value does not match the written test pattern.
10 5 PMA, S "EPROM fault"
The calculated check sum does not match the stored one.
11 5 PMA "Flash write error"
Error when writing to the flash memory.
12 5 PMA "Flash copy error"
Error when writing to the flash memory.
13 5 PMA "Flash erase error"
Error during the erase of the flash memory.
14 5 PMA "Flash duplicate error"
Duplicated parameters (the same ID) detected during the
start-up.
15 5 PMA "Flash shadow error"
The shadow bank of the flash is not erased during the start-up.
16 5 PMA, S "Flash check sum error"
Parameter setting check sum error detected.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

60
14 EPS-5T, EPS-10T

SPT GPT Status SPT Description


17 9 PMA, S "Unit not registered"
There is a unit which has not been registered as a part of the
subrack inventory.
18 10 PMA, S "Missing module"
The interface module defined in the settings is missing.
19 10 PMA, S "Conflict in module type"
There is a conflict between the installed module and the
settings.
20 32 PMA, S "ASIC fault in base unit"
The fault is activated if the difference between write/read
configuration data of ASIC has been detected.
21 32 PMA, S "ASIC fault in module"
The fault is activated if the difference between write/read
configuration data of ASIC has been detected.
22 36 PMA "Start permission denied"
Most likely the unit does not belong to the node configuration.
23 38 PMA, S "Bus sync fault"
No 8100 system bus synchronization from SXU detected.
24 40 PMA, S "Missing IA activity"
The fault is activated if the unit cannot find its locked
interface address on the cross-connection bus. SXU should
activate IA on the bus if the interface is locked.
25 55 PMA, S "Incompatible EPROM/FLASH SW"
The downloaded software (in the flash) is not compatible
with the system software in EPROMs.
26 55 PMA "Chksum err in downloaded SW"
The downloaded software has been corrupted.
27 62 PMA, S "HW fault in base unit"
Hardware does not work as expected.
28 62 PMA "HW fault in module"
Hardware does not work as expected.
29 62 PMA, S "UBU to module comm error"
Communication error between the base unit (UBU) and the
module.
30 62 PMA, S "Reset self test failure"
Power on reset self test failure.
31 69 PMA "Setup conflict"
Information stored to setup is self-contradictory.
32 5 PMA, S "DSP readback test failure"
Digital signaling processor readback test has failed.
33 24 MEI "Loss of synchronization"
See CCITT G.706 Loss of frame alignment.
34 27 MEI "Unit test loop on"
Local loop or test activated.
35 62 PMA, S "Internal test failure"
Fault in the hardware.
36 58 MEI "Fault mask"
Faults are masked.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

61
15 ESO-5T

15 ESO-5T
SPT GPT Status SPT Description
1 1 PMA, S "SW unpredicted"
This fault condition should never occur (or is not yet
supported).
2 2 PMA "Unit in reset"
There has been a unit reset (detected always after the
power-up of the unit).
3 4 PMA "Power backplane +5 V"
The voltage is below the threshold limit (about 4.6 V
depending on the calibration and the A/D resolution).
4 4 PMA "Power PDF +5 V"
The voltage is below the threshold limit (about 4.6 V
depending on the calibration and the A/D resolution).
5 4 PMA "Power +12 V"
The voltage is below the threshold limit (about 11.3 V
depending on the calibration and the A/D resolution).
6 4 PMA "Power -10 V"
The voltage is above the threshold limit (about -9.0 V
depending on the calibration and the A/D resolution).
7 5 PMA, S "RAM fault UBU"
A background process has found a RAM location where the
read value does not match the written test pattern.
8 5 PMA, S "RAM fault IF 1"
A background process has found a RAM location where the
read value does not match the written test pattern in IF 1.
9 5 PMA, S "EPROM fault"
The calculated check sum does not match the stored one.
10 5 PMA, S "Boot PROM fault"
The Boot PROM on IF1 is malfunctioning.
11 5 PMA "Flash write error UBU"
Error when writing to the flash memory.
12 5 PMA "Flash write error IF 1"
Error when writing to the flash memory.
13 5 PMA "Flash copy error"
Error when writing to the flash memory.
14 5 PMA "Flash erase error UBU"
Errors during the erase of the flash memory.
15 5 PMA "Flash erase error IF1"
Error during the erase of the flash memory.
16 5 PMA "Flash duplicate error"
Duplicated parameters (the same ID) detected during the
start-up.
17 5 PMA "Flash shadow error"
The shadow bank of the flash is not erased during the start-up.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

62
15 ESO-5T

SPT GPT Status SPT Description


18 5 PMA, S "Flash check sum error UBU"
The calculated check sum does not match the stored one.
19 5 PMA, S "Flash check sum error IF1"
The calculated check sum does not match the stored one.
20 5 PMA, S "Setup structure error"
Error in settings structure of flash memory.
21 10 PMA, S "Wrong or missing IF module"
The module type defined in the settings does not match the
actual module type in the hardware.
22 32 PMA, S "ASIC Error"
A faulty register in the ASIC.
23 32 PMA, S "Unit hardware error"
A hardware fault in the base unit.
24 32 PMA, S "IF module FPGA error"
The FPGA image has not loaded properly or a diagnostic
test of the FPGA has failed.
25 36 PMA, S "Start permission denied"
No start permission. The unit is not in its correct place.
26 38 PMA, S "Bus sync fault"
No 8100 system bus synchronization from SXU detected.
27 40 PMA, S "IA activity missing CIF 1 Port 1"
The interface address is not activated on the cross-connection
bus by SXU.
28 40 PMA, S "IA activity missing CIF 1 Port 2"
The interface address is not activated on the cross-connection
bus by SXU.
29 55 PMA "Incompatible EPROM/FLASH SW"
The downloaded software (in the flash) is not compatible
with the system software in EPROMs.
30 55 PMA, S "Checksum error in Dnl program"
The downloaded software has been corrupted.
31 62 PMA, S "IF module hardware error"
A hardware fault in the interface module.
32 62 PMA, S "MC68MH360 communication error"
The communication link is down between UBU IF1.
33 23 MEI, S "AIS(Cessation of flags on provisioned C-channel) "
Flags are not being detected on Serial Communication
Channel.
34 27 MEI, S ”Channel in loopback"
The loop is active.
35 58 MEI ”Faults masked”
Faults are masked. (Alarms are not generated as
consequences of fault conditions).
36 79 MEI ”Activation failed”
Attempted activation of an ISDN user port failed.
37 79 MEI ”Interface ID not identical”
Attempted to restart the V5 interface with an interface id
different from that of LE.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

63
15 ESO-5T

SPT GPT Status SPT Description


38 79 MEI ”Variant ID not identical”
Attempted to restart the V5 interface with a variant id
different from that of LE.
39 79 MEI ”Variant does not exist”
Attempted to restart the V5 interface with an unknown
variant.
40 79 MEI ”Internal failure”
V5 Control data link failure or RESTART ACK not received
after interface restart attempted.
43 77 MEI ”Attempt to verify/switch to same variant”
Attempted to reprovision the V5 interface using the current
Variant Id.
44 77 MEI ”Protocol discriminator error”
Received V5 message from LE with bad protocol
discriminator.
45 77 MEI ”L3 addr error”
V5 Message has unknown layer 3 address.
46 77 MEI ”Message type unrecognized”
Received V5 message type from LE is unrecognized.
47 77 MEI ”Out of sequence information element”
Received V5 message from LE has out of sequence
information element.
48 77 MEI ”Repeated optional information element”
Received V5 message from LE has repeated optional
information element.
49 77 MEI ”Mandatory information element missing”
Received V5 message from LE has missing mandatory
information element.
50 77 MEI ”Unrecognized information element”
Received V5 message from LE has unrecognized information
element.
51 77 MEI ”Mandatory information element error”
Received V5 message from LE has invalid mandatory
information element.
52 77 MEI ”Optional information element error”
Received V5 message from LE has invalid optional
information element.
53 77 MEI ”Message not compatible with path state”
V5 message not expected in the current PSTN path state.
54 77 MEI ”Repeated mandatory information element”
Received V5 message from LE has repeated mandatory
information element.
55 77 MEI ”Invalid sequence number received”
V5 message has variable length information element with
code value lower than that of preceding variable length
information element.
56 77 MEI ”Next sequence number unavailable”
V5 message has next sequence number unavailable.
57 77 MEI ”Tt timer expired”
SIGNAL ACK message has not been received from LE.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

64
15 ESO-5T

SPT GPT Status SPT Description


59 77 MEI ”T3 timer expired 3rd time”
DISCONNECT or DISCONNECT COMPLETE message
not received from LE.
60 77 MEI ”Message received is too short”
V5 message received is too short.
61 77 MEI ”Message received is too long”
V5 message received is too long.
65 77 MEI ”Too many information elements”
V5 message received has too many information elements.
66 77 MEI ”Control function error”
A V5 control protocol message is invalid.
70 77 MEI ”Message received during out of service state”
A V5 message has been received in the interface
out-of-service state.
71 77 MEI ”Timer T01 expired 2nd time”
PORT CONTROL ACK message has not been received from
LE.
72 77 MEI ”Timer T02 expired 2nd time”
COMMON CONTROL ACK message has not been received
from LE.
80 77 PMA, S ”Interface module configuration not restored”
The configuration stored in the non-volatile memory has not
been copied to RAM properly following a reset.
81 2 PMA, S ”Interface Module Reset”
IF1 has been reset.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

65
16 ESU

16 ESU
SPT GPT Status SPT Description
1 1 PMA “SW unpredicted”
This fault condition should never occur.
2 2 PMA “Reset”
There has been a unit reset (detected always after the
power-up of the unit). Note that this is a delta event, not
an active fault.
4 69 MEI “Reading extended backup settings”
The unit is reading its extended backup settings from the
extended backup unit. Do not interrupt.
5 69 PMA “Extended settings corrupted”
Fatal setup corruption. The unit must be configured again
or it must be moved to a slot where a compatible unit is
registered; the unit inherits settings.
6 72 PMA “No extended backup unit address”
The control unit returns no address of the extended backup
unit. The capacity of the extended backup unit may have
run out.
7 72 PMA “Extended backup unit fault”
No answer or error message from the extended backup unit
(it may be missing, it is not in inventory or SCU may have
run out of backup space).
8 38 PMA, S “Bus sync. fault”
The fault is activated if the X-bus synchronization pulse
transmitted by SXU is missing. A typical reason for this fault
is that SXU is missing. If only one interface unit has this
fault although there are other interface units in the subrack
then the fault is most likely in that particular unit.
9 36 PMA, S “Start request denied”
Most likely the unit does not belong to the node configuration.
11 5 PMA, S “RAM fault”
A background process has detected a RAM location where
the read value does not match with the written test pattern.
12 5 PMA, S “File system fatal error”
Flash system failed. Replace the unit with a spare unit.
13 5 MEI “File system warning”
The flash file system is damaged.
14 5 PMA “SW checksum error on RAM”
The running application software has corrupted. The
calculated check sum does not match with the stored one
on RAM.
15 5 PMA “SW checksum error on boot flash”
The boot software has corrupted. The calculated check sum
does not match with the stored one on boot flash.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

66
16 ESU

SPT GPT Status SPT Description


18 5 PMA, S “Flash setup checksum error”
One of the setting structures is corrupted in the non-volatile
memory. The calculated check sum does not match with the
stored one in the flash setting structure.
19 5 PMA, S “Missing settings”
One of the setting structures is missing in the non-volatile
memory.
22 39 PMA, S “Tx clock fault”
The fault is activated if the interface module transmitting
clock phase locking to the X-bus clock fails.
23 40 PMA, S “IA activity missing”
The fault is activated if the unit cannot find its locked
interface address on the cross-connection bus. SXU should
activate IA on the bus if the interface is locked.
24 10 PMA, S “IF module missing”
The interface module defined in the settings is missing.
25 10 PMA, S “Wrong interface module”
There is a conflict between the installed module and the
settings.
26 57 MEI “NTU power off”
The “NTU power off" message has been received from an
NTU losing its power supply voltage.
27 12 PMA, S “Rx signal missing”
The signal level is below a specific level (the level depends
on the used interface module and the selected bit rate).
28 42 MEI, S “AIS from X-BUS”
The fault is activated if the frame synchronization word and
RAI from the X-bus and TS0 B2 changes between "0" and
"1" are missing.
29 23 MEI, S “Rx-signal is AIS”
The fault is activated if 2 or less zeros in a 2-frame period
are recognized. The fault is deactivated if 3 or more zeros in
a 2-frame period are recognized.
30 26 DMA “CRC missing”
The fault is activated if framing can be found and the CRC
multiframe alignment has been lost for 100-200 ms.
The fault is deactivated if the multiframe alignment has been
found. This fault indicates that the remote end most likely
does not use CRC.
31 26 PMA, S “Frame alignment lost by CRC”
See CCITT G.706 Frame alignment recovery (2048 mode ≥
915 CRC block errors detected).
32 24 PMA, S “Frame alignment lost”
See CCITT G.706 Loss of frame alignment.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

67
16 ESU

SPT GPT Status SPT Description


33 13 PMA, S “BER1E-3”
See ITU-T G.736. The bit error rate is calculated from faulty
frame alignment words or from code errors. The bit error
rate 1E-3 limits from frame alignment words: 2048 kbit/s
and n x 64 kbit/s count time 4 seconds.
Count to activate alarm: 94
Count to deactivate alarm: 17
Error rate 10E-3 limits from code errors:
Count time 1 second
Bit rate (kbit/s): 2048
Activation limit: 1973
Deactivation limit: 229
10-3 alarm status depends on fault consequences (AIS
insertion).
34 13 DMA “BER1E-3”
See the above explanation.
37 29 PMA, S “No response to NNM message”
The control channel of the interface is used and the neighbor
node supervision option of the interface is on and no NNM
(Neighbor Node Monitoring) message has been received
from the interface within 8 seconds.
38 29 PMA, S “Own NNM messages received”
The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received
NNM message contains the same identification data as the
NNM message sent to the interface.
39 29 PMA, S “Wrong IDs in NNM message”
The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received
NNM message contains unexpected neighbor identification
data.
40 27 MEI, S “Loop: IF back to equipment”
An interface loop is created in the interface module. It loops
transmitted data and the clock signal back to the interface
receiver.
41 27 MEI, S “Loop: MUX/DEMUX back to eq”
Similar to Interface back to equipment loop except that the
loop is made before the interface module in the ESU unit
base card.
42 27 MEI, S “Loop: MUX/DEMUX back to line”
Rx data is looped back to the interface transmitter. When the
HDLC channel is used, it works with this line loop. All other
bits are looped back to the interface.
43 27 MEI, S “Line loop made by neighbor”
This alarm is activated if the HDLC channel is in use and
MUX/DEMUX back to the line loop has been activated from
the remote end, or BTE module is used and the remote end
has activated the V.54 loop.
44 27 MEI, S “Remote controlled line loop”
This alarm is activated if the HDLC channel is in use and
MUX/DEMUX back to the line loop has been made to the
neighbor unit, or BTE module is used and the V.54 loop has
been made to the remote end.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

68
16 ESU

SPT GPT Status SPT Description


45 43 MEI, S “AIS in signaling”
The fault is activated if a signal in the signaling timeslot
contains less than 2 zeros during a multiframe period.
50 25 PMA, S “MFrame alignment lost”
The fault is activated if two consecutive faulty multiframe
alignment words are received, or if all signaling time slots
in one multiframe contain only zeros ("0"). The fault is
deactivated when the frame alignment is detected and the
first four bits of the signaling timeslot are found to be zeros
("0") and when the prior signaling timeslot had at least one
bit in state "1".
55 20 MEI, S “Frame far-end alarm”
The state of the far-end alarm bit TS0 B3 will be switched
if the opposite state is received in 3 consecutive frames.
State "1" is used for alarm. Alarm status depends on fault
consequences (AIS insertion into the signaling timeslot).
56 20 MEI “Frame far-end alarm”
The state of the far-end alarm bit TS0 B3 will be switched
if the opposite state is received in 3 consecutive frames.
State "1" is used for alarm. Alarm status depends on fault
consequences (AIS insertion into the signaling timeslot).
57 21 MEI, S “MFrame far-end alarm”
The state of signaling timeslot’s frame 0 B6 alarm bit will
be switched if the opposite state is received in 3 consecutive
frames. State "1" is used for alarm. Alarm status depends
on fault consequences (AIS insertion into the signaling
timeslot).
58 21 MEI “MFrame far-end alarm”
See the above explanation.
67 16 DMA “BER1E-6”
BER1E-6 error rate is calculated from CRC block errors
when bit rate > 1024 kbit/s. Counting time is 10 seconds
and the limit for the fault condition depends on the used bit
rate (2048 limit is 10).
68 58 MEI “Faults masked/test”
The fault is activated when the interface Fault mask setting
is on (all interface faults are cleared).
69 30 DMA “Frequency difference”
The measurement period is 15 seconds and the phase-drifting
limit is 18 ms. The fault is activated if the phase-drifting
limit has been exceeded in 3 measurements out of 4.
70 30 MEI “Buffer slip(s)/1 hour”
The fault is activated if one or more buffer slip(s) have been
detected during the last hour.
71 41 DMA “HDLC overlap with X-bus”
The fault is activated if the HDLC control channel bit(s) are
also used by the cross-connection bus.
72 41 DMA “MCLK RAI overlap with X-bus”
The fault is activated if the MCLK/RAI bit is also used by
the cross-connection bus.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

69
16 ESU

SPT GPT Status SPT Description


73 32 PMA, S “ASIC register error”
The fault is activated if the difference between write/read
configuration data of ASIC has been detected.
74 91 MEI “Performance event”
This fault is activated as a delta fault when G.826 supervision
is used if at least one performance event has been occurred
in a 15-minute period.
78 69 DMA “Port locking conflict”
The fault is activated if SXU has the port descriptor but the
unit interface is unlocked or SXU does not have the port
descriptor although the interface is locked. Use lock/unlock.
82 112 PMA, S “Excessive errors”
Once every second, block errors shall be compared with the
limit value. If errors count ≥ limit, the one second shall be
declared BAD, otherwise it shall be declared GOOD.
The Excessive errors shall be detected if M consecutive BAD
seconds have occurred. The Excessive errors shall be cleared
if M consecutive GOOD seconds have occurred. The values
of M range from 2 to 9.
83 103 DMA “Degraded errors”
Once every second, block errors shall be compared with
limit value. If errors count ≥ limit, the one second shall be
declared BAD, otherwise it shall be declared GOOD.
The Degraded errors shall be detected if M consecutive BAD
seconds have occurred. The Degraded errors shall be cleared
if M consecutive GOOD seconds have occurred. The values
of M range from 2 to 9
84 49 DMA “Noise margin alarm”
The quality of the line is not good enough for data
communications
85 24 PMA, S “Loss of HDSL frame”
See ETSI TS 101 135 Loss of HDSL frame alignment.
86 75 PMA, S “Chain number conflict”
The existing numbering differs from the defined and the
re-numbering operation is recommended.
87 114 PMA, S “Unavail (G.826)”
A period of unavailable time begins at the onset of ten
consecutive SES events. These ten seconds are considered to
be part of unavailable time. A new period of available time
begins at the onset of ten consecutive non-SES events. These
ten seconds are considered to be part of available time.
88 114 PMA, S “Unavail far end”
A period of far end unavailable time (only when
unidirectional performance collection used) begins at the
onset of ten consecutive far end SES events. These ten
seconds are considered to be part of far end unavailable time.
A new period of available time begins at the onset of ten
consecutive non-far end SES events. These ten seconds are
considered to be part of available time.
89 49 DMA “Qos”
Quality of service. Quality of signal in 24 hours period.
At least one of the BBE, ES or SES limits exceeded. Cleared
when period changes.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

70
16 ESU

SPT GPT Status SPT Description


90 49 DMA “Qostr”
Quality of service, threshold reset. Quality of signal in a
15-minute period.
At least one of the upper ES, BBE or SES limits has been
exceeded. Cleared when found a period where the lower ES,
BBE or SES limits has not been exceeded.
92 55 PMA, S “Hw/sw version conflict”
The software is in a wrong unit or in a wrong unit version.
93 68 DMA “Door open”
Indicates that door of modem is open.
94 68 DMA “Customer alarm 1”
Indicates that external (1) alarm in modem is active.
95 68 DMA “Customer alarm 2”
Indicates that external (2) alarm in modem is active.
97 20 MEI “Pilot bit far end alarm”
A pilot bit far end alarm is detected from X-bus.
98 42 MEI, S “Pilot bit AIS”
Pilot bit AIS (S-status) is detected from the X-bus.
103 12 DMA “Rx signal missing“
The signal level is below a specific level (the level depends
on the used interface module and the selected bit rate).
200 5 PMA, S “Downloaded SW missing”
The application software cannot be started, because the
downloaded software is missing. The unit is not operational
until new software has been downloaded.
201 5 PMA, S “Downloaded SW in reset loop”
The application software cannot be started due to a fatal
error. The unit is not operational until new software has been
downloaded.
202 5 PMA, S “Downloaded SW incompatible”
The application software cannot be started, because
the permanent boot software is incompatible with the
downloaded application software in the flash. The unit is not
operational until new software has been downloaded.
203 5 PMA, S “Downloaded SW checksum error”
The application software cannot be started, because the
downloaded application software has corrupted. The
calculated check sum does not match with the one stored in
downloadable flash. The unit is not operational until new
software has been downloaded.
204 5 PMA, S “Downloaded SW disabled”
The application software cannot be started, because the
application software is disabled. The unit is not operational
until new software has been downloaded.
205 5 PMA, S “Downloaded SW faulty”
The application software cannot be started, because the
downloaded file is invalid. The unit is not operational until
new software has been downloaded.
206 86 DMA “Link traffic threshold exceeded”
Traffic load on the link exceeds the threshold configured.
(See the Fault Monitoring Parameters dialog.)

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

71
16 ESU

SPT GPT Status SPT Description


207 86 DMA “Frame errors threshold exceeded”
The amount of received erroneous packets/minute exceeds
the threshold configured. (See the Fault Monitoring
Parameters dialog.)
208 77 MEI “Connectivity lost”
The Background Connectivity Monitoring tool has lost its
connectivity.
209 63 PMA “Ethernet MAC/PHY link down”
This fault is applied to all ports. In case of X-bus port or DSL
line, this information is received from HDLC/LAPF layer.
210 63 PMA “MAC address limit of the port exceeds”
The number of learned MAC addresses in a port is too high.
211 78 DMA “MAC address table full”
The MAC address database of the L2 switch is full.
212 77 DMA “Aggregate member link down”
One or more physical link(s) of an aggregate is down. In
case of X-bus port or DSL line, this information is received
from HDLC/LAPF layer.
213 77 PMA “Aggregate group link down”
All physical links of an aggregate are down. In case of
X-bus port or DSL line, this information is received from
HDLC/LAPF layer.
214 84 PMA ”FPGA load failed”
Firmware load to FPGA chip has failed.
215 62 PMA ”PCI bus error”
Local PCI bus bridge has detected an error on PCI bus.
216 62 PMA ”BUS error reported by the Ethernet Switch”
Ethernet switch has read illegal data from PCI bus or PCI
bus is overloaded.
217 5 PMA ”Out of Ethernet switch management RAM”
Memory region reserved for Ethernet switch related
management data is full.
218 5 PMA ”Out of DMA RAM”
Memory region reserved for direct memory access operations
is full.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

72
17 FBU

17 FBU
SPT GPT Status SPT Description
1 1 PMA, R “SW unpredicted”
This fault condition should never occur.
2 2 PMA, S, R “Reset”
The unit has been reset (the fault is detected always after
power-up).
3 11 PMA, S, R “Loss of protected signal”
In 1+1 protected mode both received 2 Mbit/s signals have
a fault (S-status).
4 4 PMA, R “Power supply +5V”
The output voltage of the unit power supply is below the
threshold.
5 4 PMA, R “Power supply +12V”
The output voltage of the unit power supply is below the
threshold.
6 4 PMA, R “Power supply -10V”
The output voltage of the unit power supply is below the
threshold.
7 4 PMA, R “Power supply +3.3V”
The output voltage of the unit power supply is below the
threshold.
8 38 PMA, S, R “X-bus synchr. pulse failed”
The unit does not receive X-bus synchronization signals. A
typical reason for this fault is that SXU is missing. If only
one of the units in the subrack has this fault, the fault is most
likely in the FBU unit.
9 36 PMA, S, R “Start request denied”
Most likely the unit does not belong to the node configuration.
10 3 PMA, S, R “Initialization error”
The initialization of the application software was
unsuccessful (after the power-up of the unit).
11 5 PMA, S, R “CPU RAM fault”
A background process has detected a RAM location where
the read value does not match with the written test pattern
13 5 PMA, R “Flash file system fatal error”
The flash system has failed. Replace the unit with a spare
unit.
14 5 MEI “Flash file system bad block found”
A small part of the flash memory is faulty (this part is
blocked from use).
15 5 DMA, R “SW checksum error in RAM”
The calculated check sum does not match with the stored
one on RAM.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

73
17 FBU

SPT GPT Status SPT Description


16 5 DMA, R “SW checksum error in boot flash”
The calculated check sum does not match with the stored
one on boot flash.
17 5 DMA, R “SW checksum error in download flash”
The calculated check sum does not match with the stored
one on downloadable flash.
19 5 PMA, S, R “Missing settings”
One of the setting structures is missing in the non-volatile
memory.
20 4 PMA, R “Power supply +55V”
The external remote power supply voltage is below the
threshold in unprotected mode or both input voltages have
failed in protected mode.
21 4 DMA, R “Power supply +55V protecting”
The external protecting remote power supply voltage is
below the threshold in protected mode.
22 39 PMA, S, R “Tx Clock fault”
The unit can not lock to the node clock
23 40 PMA, S, R “X-bus address (IA) activity missing”
The unit does not receive its X-bus address. If other units
in the subrack do not report this fault, FBU is presumed to
be faulty.
24 10 PMA, S, R “Interface module missing”
The interface module defined in the settings is missing.
27 12 PMA, S, R “Rx 2 M signal missing”
This alarm indicates an FBU fault or an open 2 Mbit/s matrix
connection in FBU.
28 42 MEI, S, Y “AIS from X-bus”
The 2 Mbit/s framer of the unit cannot synchronize with
TS0 from the X-bus in the mode where TS0 is transported
to the 8100 network.
29 23 MEI, S, Y “Rx 2 M signal AIS”
A received 2 Mbit/s signal is AIS or a fault exists in the
Flexbus signal.
30 26 DMA, R “CRC4 missing”
The receiver cannot synchronize to the CRC4 multiframe in
the received 2 Mbit/s signal. This fault most likely indicates
that the remote end does not use CRC4.
31 26 PMA, S, R “Frame alignment lost by CRC4”
The receiver cannot synchronize with the frame in the
received 2 Mbit/s signal due to 915 CRC block errors.
32 24 PMA, S, R “Frame alignment lost”
The receiver cannot synchronize with the frame in the
received 2 Mbit/s signal.
33 103 DMA, R “Degraded protected signal”
In 1+1 protected mode the selected 2 Mbit/s signal has a
signal degraded fault.
34 5 PMA, S, R “EEPROM write error”
An error during writing to the EEPROM memory.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

74
17 FBU

SPT GPT Status SPT Description


35 5 PMA, S, R “EEPROM checksum error”
The calculated check sum does not match with the one stored
on EEPROM.
37 29 PMA, S, R “No response to NNM message”
The neighbor node supervision of the interface is on and no
NNM message has been received from the interface within
8 seconds.
38 29 PMA, S, R “Own NNM messages received”
The neighbor node supervision of the interface is on and the
received NNM message contains the same identification data
as sent to the interface.
39 29 PMA, S, R “Wrong IDs in NNM messages”
The neighbor node supervision of the interface is on and the
received NNM message contains unexpected identification
data.
41 27 MEI, S, Y “Loop back to equipment”
The transmitted 2 Mbit/s signal is looped back to the X-bus
direction.
42 27 MEI, S, Y “Line back to line”
The 2 Mbit/s signal received from the Flexbus interface is
looped back to the Flexbus interface.
43 27 MEI, S, Y “Remote line loop made by neighbor”
The node at the remote end of the 2 Mbit/s trail has activated
a line loop via the HDLC control channel.
44 27 MEI, S, Y “Remote controlling line loop”
The unit has activated a remote line loop to the node at
the remote end of the 2 Mbit/s trail via the HDLC control
channel.
45 43 MEI, S, Y “AIS in signaling (TS16)”
There is a TS16 AIS in the received 2 Mbit/s signal.
46 69 MEI, R “Reading extended backup settings”
The unit is reading its extended backup settings from the
extended backup unit. Do not interrupt.
47 69 PMA, R “Extended settings corrupted”
The unit must be reconfigured or it must be moved to a slot
where a compatible unit is registered. In this case the unit
will copy parameters from this compatible unit.
48 72 PMA, R “No extended backup unit address”
The capacity of the extended backup unit may have run out.
49 72 PMA, Y “Extended backup unit fault”
No answer or error message from the extended backup unit
(it may be missing, it is not in inventory or SCU may have
run out of backup space).
50 25 PMA, S, R “Multiframe alignment lost”
The receiver cannot synchronize with the CAS multiframe in
the received 2 Mbit/s signal.
55 20 MEI, S, Y “Frame far end alarm, action enabled”
TS0/B3 is in state 1 in the received 2 Mbit/s signal, AIS
inserted into TS16.
56 20 MEI, Y “Frame far end alarm, action disabled”
TS0/B3 is in state 1 in the received 2 Mbit/s signal.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

75
17 FBU

SPT GPT Status SPT Description


57 21 MEI, S, Y “Multiframe far end alarm, action enabled”
Frame0/TS16/B6 has been received in state 1, AIS inserted
into TS16.
58 21 MEI, Y “Multiframe far end alarm, action disabled”
Frame0/TS16/B6 has been received in state 1.
68 58 MEI, Y “Faults masked”
The operator has set the Fault Mask on for the 2 Mbit/s
interface (all faults in this interface are cleared).
69 30 DMA, R “Frequency difference in rx signal”
The frequency of the received 2 Mbit/s signal has offset with
the node clock.
70 30 MEI, RB “Buffer slips/1 hour”
One or more buffer slips have been detected during the last
hour (the received signal has offset).
71 41 DMA, R “HDLC overlap with X-bus”
HDLC control channel bits are also configured for payload
cross-connection.
72 41 DMA, R “Master clock RAI overlap with X-bus”
RAI bits are also configured for payload cross-connection.
73 32 PMA, S, R “ASIC register error”
A mismatch in ASIC configuration data has been detected.
78 69 DMA, R “Port locking conflict”
The fault is activated if SXU has the port descriptor but
the interface of the unit is unlocked or SXU does not have
the port descriptor although the interface is locked. Use
lock/unlock.
79 53 MEI, R “Forced protection switch”
The 2 Mbit/s interface is in 1+1 protected mode and the
protection switch has been forced to either interface.
81 5 PMA, S, R “Flash setup checksum error”
The calculated check sum does not match with the one stored
on flash.
82 112 PMA, S, R “Excessive errors”
The configured error threshold is exceeded in the received
2 Mbit/s signal.
83 103 DMA, R “Degraded signal”
The configured error threshold is exceeded in the received
2 Mbit/s signal.
84 91 MEI “G.826 performance event”
FBU has non-zero performance data available for 8100
manager.
87 114 PMA, S “G.826 unavailable state bidir./unidir near end”
In bidirectional operation the 2 Mbit/s signal is unavailable
in either or both directions of transmission (10 consecutive
SES seconds).
88 114 PMA, S “G.826 unavailable state unidir FE”
In unidirectional operation the 2 Mbit/s received signal is
unavailable at the far end (10 consecutive SES seconds).

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

76
17 FBU

SPT GPT Status SPT Description


89 49 DMA “G.826 24 h threshold crossing QOS”
The quality of service threshold has been exceeded for BBE,
ES or SES in the received 2 Mbit/s signal during a 24-hour
period.
90 49 DMA “G.826 15 m threshold crossing QOSTR”
The quality of service threshold has been exceeded for BBE,
ES or SES in the received 2 Mbit/s signal during a 15-minute
period.
92 55 PMA, S, R “HW/SW version conflict”
The software is in a wrong unit or in a wrong unit version.
97 20 MEI, Y “Pilot bit remote alarm (TS0/Bj from Xbus)”
The 2 Mbit/s framer of the unit has detected pilot bit far end
indication bit from the X-bus in the mode where pilot bits are
transported in the 8100 network.
98 42 MEI, S, Y “Pilot bit AIS (TS0/Bi from Xbus)”
The 2 Mbit/s framer of the unit has detected pilot bit AIS
indication bit (S-status) from the X-bus in the mode where
pilot bits are transported in the 8100 network.
100 155 PMA, S, R “Critical/major failure in the IU/OU”
The Flexbus part has a critical/major fault. Detailed
information on the fault is reported to 8100 manager via
Nokia NMS/10 MF Agent.
101 155 DMA, S, R “Minor failure in the IU/OU”
The Flexbus part has a minor fault. Detailed information on
the fault is reported to 8100 manager via Nokia NMS/10
MF Agent.
102 155 MEI, Y “Warning in the IU/OU”
The Flexbus part has a warning. Detailed information on
the fault is reported to 8100 manager via Nokia NMS/10
MF Agent.
1000 10000 PMA "Fault in power supply"
1002 10000 DMA “Loss of backup power supply”
1020 10000 PMA "Blocked from use"
1021 10000 MEI "Loop to interface"
1022 10000 MEI "Loop to equipment"
1023 10000 MEI “Test mode active”
1025 10000 MEI "Test generator on"
1048 10000 PMA "Loss of incoming signal"
1064 10000 PMA "Alarm signal is received"
1066 10000 MEI "AIS 2M platform interface"
1073 10000 MEI “AIS 1.5M T1 interface”
1081 10000 PMA "Loss of frame alignment"
1099 10000 PMA "Error rate > 1E-3"
1100 10000 DMA "Error rate > 1E-4"
1101 10000 DMA "Error rate > 1E-5"
1102 10000 DMA "Error rate > 1E-6"

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

77
17 FBU

SPT GPT Status SPT Description


1113 10000 PMA "Buffer overflow (or underflow)"
1128 10000 PMA "Fault in equipment"
1137 10000 PMA "Fault in oscillator"
1139 10000 PMA "Subrack is missing units"
1140 10000 PMA "Subrack has excessive units"
1141 10000 MEI "Forced control on"
1142 10000 PMA "Fault in installation of equipment"
1143 10000 PMA "Fault in change-over function"
1144 10000 PMA "Operating error"
1148 10000 PMA "Equipment reset"
1149 10000 MEI "Forced indication"
1150 10000 PMA "Fault in unit"
1162 10000 MEI "Database full"
1165 10000 DMA "Real time lost fault"
1172 10000 MEI “Yellow alarm”
1179 10000 MEI "Far-end alarm"
1184 10000 MEI "Real time updated"
1185 10000 MEI "Connection or settings have changed"
1186 10000 DMA "Configuration error"
1240 10000 PMA "Active alarm point"
1256 10000 DMA "15 min G826 ES threshold crossed"
1257 10000 PMA "15 min G826 SES threshold crossed"
1258 10000 DMA "15 min G826 BBE threshold crossed"
1259 10000 MEI "24h G826 ES threshold crossed"
1260 10000 MEI "24h G826 SES threshold crossed"
1261 10000 MEI "24h G826 BBE threshold crossed"
1262 10000 PMA "Unavailability"
1263 10000 MEI "Statistics reset"

The FBU faults with SPT above 999 are related to the FIU19 node.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

78
18 FRU

18 FRU
SPT GPT Status SPT Description
1 1 PMA, S "SW unpredicted"
This fault condition should never occur (or is not yet
supported).
2 2 PMA, S "UBU reset"
There has been a unit reset (detected always after the
power-up of the unit) in the FRU base unit (UBU).
3 3 PMA, S "Setup structure corrupted"
One of the setting structures has been corrupted.
4 4 PMA "Power +5 V (subrack)"
The voltage is below the threshold limit
(about 4.6 V depending on the calibration and the A/D
resolution).
5 4 PMA "Power +5 V (unit)"
The voltage is below the threshold limit
(about 4.6 V depending on the calibration and the A/D
resolution).
6 4 PMA "Power +12 V (unit)"
The voltage is below the threshold limit
(about 11.3 V depending on the calibration and the A/D
resolution).
7 4 PMA "Power -10 V (unit)"
The voltage is above the threshold limit
(about -9.0 V depending on the calibration and the A/D
resolution).
8 5 PMA, S "RAM fault (ubz534)"
A background process has detected a RAM location in the
FRU base unit (UBU) where the read value does not match
the written test pattern.
9 5 PMA "Shared memory fault (Ubz534)"
A background process has detected a RAM location in the
shared memory (UBU-FRE) where the read value does not
match the written test pattern.
10 5 PMA, S "EPROM fault (ubz534)"
The calculated check sum does not match the stored one.
11 5 PMA "Flash write error (ubz534)"
Error when writing to the flash memory (main bank).
12 5 PMA "Flash copy error"
Error when writing to the flash memory (shadow bank).
13 5 PMA "Flash erase error"
Error during the erase of the flash memory (shadow bank).
14 5 PMA "Flash duplicate error"
Duplicated parameters (the same ID) detected during the
start-up.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

79
18 FRU

SPT GPT Status SPT Description


15 5 PMA "Flash shadow error"
The shadow bank of the flash is not erased during the start-up.
16 5 PMA, S "Flash check sum error"
The calculated check sum does not match the stored one.
17 5 PMA, S "Missing settings (ubz534)"
One of the setting structures has been corrupted in the
non-volatile memory.
18 10 PMA, S "Missing module"
The Frame Relay daughter module is missing.
19 10 PMA, S "Conflict in module type"
There is a conflict between the installed module and the
settings.
20 27 MEI, S "CIF ASIC loop on physical port 1"
A local 2048 kbit/s loop or test activated in physical port 1.
21 27 MEI, S "CIF ASIC loop on physical port 2" A local 2048 kbit/s loop
or test activated in physical port 2.
22 27 MEI, S "CIF ASIC loop on physical port 3"
A local 2048 kbit/s loop or test activated in physical port 3.
23 27 MEI, S "CIF ASIC loop on physical port 4"
A local 2048 kbit/s loop or test activated in physical port 4.
24 32 PMA, S "ASIC fault in base unit"
Difference between write/read configuration data of ASIC
has been detected in the base unit.
25 32 PMA, S "ASIC fault in base unit"
Difference between write/read configuration data of ASIC
has been detected in the base unit.
26 36 PMA, S "Start permission denied"
No start permission. Most likely the unit is not in its correct
place.
27 38 PMA, S "Bus sync. fault"
The fault is activated if the X-bus synchronization pulse
transmitted by SXU is missing. A possible reason for this
fault is that SXU is missing.
28 40 PMA, S "Missing IA activity"
The interface address is not activated on the cross-connection
bus by SXU.
29 55 PMA "Incompatible EPROM/FLASH SW"
The fault is activated if there is downloaded software in flash
but the revision is wrong (for example if EPROM SW is r5.5
and downloaded SW is r6.1).
30 55 PMA, S "Chksum err in downloaded SW"
The downloaded software has been corrupted.
31 58 MEI "Faults masked"
Faults are masked (alarms are not generated as consequences
of fault conditions).
32 62 PMA, S "HW fault in base unit"
Base unit hardware does not work as expected.
33 62 PMA, S "HW fault in module"
Module hardware does not work as expected.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

80
18 FRU

SPT GPT Status SPT Description


34 62 PMA, S "UBU to module comm error"
Communication error between base unit (UBU) and module
(FRE).
35 69 DMA "Setup data mismatch"
Information stored to the setup is self-contradictory.
36 72 PMA "Backup unit (SCP) fault"
Error in extended backup unit (SCP).
37 89 PMA, S "Incompatible SW UBU/FRE"
The base unit (UBU) software revision is incompatible with
the module (FRE) software revision.
38 1 PMA, S "FRE fatal error"
A fatal error in the FRE module. User data traffic is stopped.
39 1 DMA "FRE non-fatal error"
A non-fatal error in the FRE module. Most likely memory or
buffers are below recommended levels and action is required
to correct the problem although the user data traffic is not
necessarily stopped.
40 2 PMA, S "FRE reset"
There has been a module (FRE) reset.
41 5 PMA "FRE flash error"
Error in the module (FRE) flash memory.
42 5 PMA, S "FRE PRAM error"
Error in the module (FRE) battery backed up parameter
memory.
43 5 PMA "FRE I/O error in DRAM or SRAM"
An I/O error in module (FRE) DRAM or SRAM.
44 62 PMA, S "FRE Power-On self test failure"
Failure occurred during the module (FRE) Power-On Self
Test (POST).
45 77 PMA, S "FR link protocol (LMI) status down"
Frame Relay link protocol (FR LMI, PPP LCP, etc.
depending on the logical port type) status is DOWN.
46 77 PMA, S "FR trunk protocol (OSPF) down"
Frame Relay trunk protocol (OSPF) state is something else
than FULL. OSPF protocol may be just coming up.
47 80 MEI "FR log. port 1 min. congestion threshold exceeded"
The user (NMS) defined congestion percentage threshold
(rate over a one minute period) for generating a warning/fault
indication has been exceeded in this Frame Relay logical
port.
48 86 PMA, S "FR log. port frame errors/min. threshold exceeded"
The user (NMS) defined frame errors per one minute
threshold for generating a fault indication has been exceeded
in this Frame Relay logical port.
49 1 PMA, S "FR virtual circuit operational status down"
This Frame Relay circuit is down. No user data passed.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

81
18 FRU

SPT GPT Status SPT Description


50 27 MEI, S "FR virtual circuit loop on"
This Frame Relay Virtual Circuit (VC) has a local loop
activated. User traffic in this VC is looped back. Traffic in
other VCs is not affected.
51 69 PMA, S "Logical port forced to unlock state"
Logical port forced to unlock.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

82
19 GCH-A

19 GCH-A
See 53 VCM-5T, VCM-10T, VCM-5T-A, VCM-10T-A, VCM 402, GCH-A .

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

83
20 GMH

20 GMH
SPT GPT Status SPT Description
1 1 PMA "SW unpredicted"
This fault condition should never occur (or is not yet
supported).
2 2 PMA "Reset"
There has been a unit reset (detected always after the
power-up of the unit).
3 11 PMA, S "Loss of protected signal"
In 1+1 protection mode both interfaces IF1 and IF2 have
faults which in unprotected mode have S status.
4 4 PMA "Power + 5 V"
The voltage is below the threshold limit (about 4.6 V
depending on the calibration and the A/D resolution).
5 4 PMA "Power +12 V"
The voltage is below the threshold limit (about 11.3 V
depending on the calibration and the A/D resolution).
6 4 PMA "Power -10 V"
The voltage is above the threshold limit (about -9.0 V
depending on the calibration and the A/D resolution).
7 36 PMA, S "Start request denied"
Most likely the unit does not belong to the node configuration.
8 38 PMA, S "Bus sync. fault"
The fault is activated if the X-bus synchronization pulse
transmitted by SXU is missing. A typical reason for this fault
is that SXU is missing. If only one GMH unit has this fault
although there are other GMH units in the subrack, the fault
is most likely in the GMH unit.
9 5 PMA, S "Tx RAM error"
There is a difference between written and read data in the
Tx data buffer RAM.
10 5 PMA, S "Rx RAM error"
There is a difference between written and read data in the
Rx data buffer RAM.
11 5 PMA, S "RAM fault"
A background process has detected a RAM location where
the read value does not match the written test pattern.
12 5 PMA, S "EPROM fault"
The calculated check sum does not match the stored one.
13 5 PMA "Flash write error"
Error when writing to the flash memory (main bank).
14 5 PMA "Flash copy error"
Error when writing to the flash memory (shadow bank).
15 5 PMA "Flash erase error"
Error during the erase of the flash memory (shadow bank).

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

84
20 GMH

SPT GPT Status SPT Description


16 5 PMA "Flash duplicate error"
Duplicated parameters (the same ID) detected during the
start-up
17 5 PMA "Flash shadow error"
The shadow bank of the flash is not erased during the start-up.
18 5 PMA, S "Flash check sum error"
The calculated check sum does not match the stored one.
19 5 PMA, S "Missing settings"
One of the setting structures has been corrupted in the
non-volatile memory.
20 59 MEI, S "BTE Tx line test"
The fault is activated if the Tx-test pattern generator of the
BTE module is activated (used in V.54 remote loop).
22 39 PMA, S "Tx clock fault"
The fault is activated if the interface module transmitting
clock phase locking to X-bus clock fails.
23 40 PMA, S "IA activity missing"
The fault is activated if the unit cannot find its locked
interface address on the cross-connection bus. SXU should
activate IA on the bus if the interface is locked.
24 10 PMA, S "IF module missing"
The interface module defined in the settings is missing.
25 10 PMA, S "Wrong interface module"
There is a conflict between the installed module and the
settings.
26 57 MEI "NTU power off/local loop"
The fault is activated if the module used is BTE 232 and
wetting current is on and the received current value differs
in frequency of 1.5º4.5 Hz and the current value difference
is more than 1.5.
27 12 PMA, S "Rx signal missing"
The signal level is below a specific level (the level depends
on the used interface module and the selected bit rate).
28 42 MEI, S "AIS from X-BUS"
The fault is activated if the frame synchronization word and
RAI from the X-bus and TS0 B2 changes between "0" and
"1" are missing.
29 23 MEI, S "Rx signal is AIS"
The fault is activated if 2 or less/2M mode or 8 or less/8M
mode zeros in a 2-frame period are recognized. The fault is
deactivated if 3 or more/2M mode or 12 or more/8M mode
zeroes in a 2-frame period are recognized.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

85
20 GMH

SPT GPT Status SPT Description


30 26 DMA "CRC missing"
The fault is activated if framing can be found in the 2M
mode and the CRC multiframe alignment has been lost for
100...200 ms, or if in the 8M mode CRC alignment losses
have been found more than 6 times in a 3-second period due
to excessive block errors.
The fault is deactivated if the multiframe alignment has been
found in the 2M mode and in the 8M mode when no more
than one frame alignment lost due to excessive CRC block
errors in a 3-second-period has been found.
This fault indicates that the remote end most likely does not
use the CRC.
31 26 PMA, S "Frame alignment lost by CRC"
See CCITT G.706 Frame alignment recovery (2048 mode ≥
915 CRC block errors detected).
32 24 PMA, S "Frame alignment lost"
See CCITT G.706 Loss of frame alignment.
33 13 PMA, S "BER10E-3"
See ITU-T G.736. The bit error rate is calculated from faulty
frame alignment words or from code errors. The bit error rate
10E-3 limits from frame alignment words:
2048 kbit/s and n x 64 kbit/s count time 4 seconds
Count to activate alarm: 94
Count to deactivate alarm: 17
8448 kbit/s and count time 2 seconds
Count to activate alarm: 199
Count to deactivate alarm: 48
Error rate 10E-3 limits from code errors:
Count time 1 second
2048 kbit/s
Activation limit: 1973
Deactivation limit: 229
8448 kbit/s
Activation limit: 8296
Deactivation limit: 839
10-3 alarm status depends on fault consequences (AIS
insertion).
34 13 DMA "BER10E-3"
See ITU-T G.736. The bit error rate is calculated from faulty
frame alignment words or from code errors. The bit error rate
10E-3 limits from frame alignment words:
2048 kbit/s and n x 64 kbit/s count time 4 seconds
Count to activate alarm: 94
Count to deactivate alarm: 17
8448 kbit/s and count time 2 seconds
Count to activate alarm: 199
Count to deactivate alarm: 48
Error rate 10E-3 limits from code errors:
Count time 1 second
2048 kbit/s
Activation limit: 1973
Deactivation limit: 229
8448 kbit/s
Activation limit: 8296
Deactivation limit: 839
10-3 alarm status depends on fault consequences (AIS
insertion).

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

86
20 GMH

SPT GPT Status SPT Description


35 56 MEI "NTU line break"
The fault is activated if the module used is BTE 232 and
wetting current is on and the received current value is lower
than 1.2 mA.
36 56 MEI "NTU short circuit"
The fault is activated if the module used is BTE 232 and
wetting current is on and received current value is higher
than 6.5 mA.
37 29 PMA, S "No response to NNM message"
The control channel of the interface is used and the neighbor
node supervision option of the interface is on and no NNM
(Neighbor Node Monitoring) message has been received
from the interface within 8 seconds.
38 29 PMA, S "Own NNM messages received"
The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received
NNM message contains the same identification data as the
NNM message sent to the interface.
39 29 PMA, S "Wrong ID’s in NNM message"
The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received
NNM message contains unexpected neighbor identification
data.
40 27 MEI, S "Loop: IF back to equipment"
An interface loop is created in the interface module. It loops
transmitted data and the clock signal back to the interface
receiver.
41 27 MEI, S "Loop: MUX/DEMUX back to eq."
Similar to Interface back to equipment loop except that the
loop is made before the interface module in the GMH unit
base card.
42 27 MEI, S "Loop: MUX/DEMUX back to line"
Rx data is looped back to the interface transmitter. When the
HDLC channel is used, it works with this line loop. All other
bits are looped back to the interface.
43 27 MEI, S "Line loop made by neighbor"
This alarm is activated if the HDLC channel is in use and
MUX/DEMUX back to the line loop has been activated from
the remote end, or the BTE module is used and the remote
end has activated the V.54 loop.
44 27 MEI, S "Remote controlled line loop"
This alarm is activated if the HDLC channel is in use and
MUX/DEMUX back to line loop has been made to the
neighbor unit, or the BTE module is used and the V.54 loop
has been made to the remote end.
45 43 MEI, S "AIS in signaling"
The fault is activated if a signal in the signaling timeslot
contains less than 2 zeros during a multiframe period.
46 43 MEI, S "AIS in signaling group A"
The fault is activated if a signal in the signaling timeslot
contains less than 2 zeros during a multiframe period.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

87
20 GMH

SPT GPT Status SPT Description


47 43 MEI, S "AIS in signaling group B"
The fault is activated if a signal in the signaling timeslot
contains less than 2 zeros during a multiframe period.
48 43 MEI, S "AIS in signaling group C"
The fault is activated if a signal in the signaling timeslot
contains less than 2 zeros during a multiframe period.
49 43 MEI, S "AIS in signaling group D"
The fault is activated if a signal in the signaling timeslot
contains less than 2 zeros during a multiframe period.
50 25 PMA, S "MFrame alignment lost"
The fault is activated if two consecutive faulty multiframe
alignment words are received or if all signaling time slots
in one multiframe contain only zeros ("0"). The fault is
deactivated when the frame alignment is detected and the
first four bits of the signaling timeslot are found to be zeros
("0") and when the prior signaling timeslot had at least one
bit in state "1".
51 25 PMA, S "MFrame alignment lost, group A"
See above.
52 25 PMA, S "MFrame alignment lost, group B"
See above.
53 25 PMA, S "MFrame alignment lost, group C"
See above.
54 25 PMA, S "MFrame alignment lost, group D"
See above.
55 20 MEI, S "Frame far-end alarm"
The state of the far-end alarm bit TS0 B3 will be switched
if the opposite state is received in 3 consecutive frames.
State "1" is used for alarm. Alarm status depends on fault
consequences (AIS insertion into the signaling timeslot).
56 20 MEI "Frame far-end alarm"
The state of the far-end alarm bit TS0 B3 will be switched
if the opposite state is received in 3 consecutive frames.
State "1" is used for alarm. Alarm status depends on fault
consequences (AIS insertion into the signaling timeslot).
57 21 MEI, S "MFrame far-end alarm"
The state of signaling timeslot’s frame 0 B6 alarm bit will be
switched if the opposite state is received in 3 consecutive
frames. State "1" is used for alarm. Alarm status depends on
fault consequences (AIS insertion into the signaling timeslot).
58 21 MEI "MFrame far-end alarm"
The state of signaling timeslot’s frame 0 B6 alarm bit will be
switched if the opposite state is received in 3 consecutive
frames. State "1" is used for alarm. Alarm status depends on
fault consequences (AIS insertion into the signaling timeslot).
59 21 MEI, S "MFrame far-end alarm, group A"
The state of signaling timeslot’s frame 0 B6 alarm bit will be
switched if the opposite state is received in 3 consecutive
frames. State "1" is used for alarm. Alarm status depends on
fault consequences (AIS insertion into the signaling timeslot).

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

88
20 GMH

SPT GPT Status SPT Description


60 21 MEI "MFrame far-end alarm, group A"
The state of signaling timeslot’s frame 0 B6 alarm bit will be
switched if the opposite state is received in 3 consecutive
frames. State "1" is used for alarm. Alarm status depends on
fault consequences (AIS insertion into the signaling timeslot).
61 21 MEI, S "MFrame far-end alarm, group B"
The state of signaling timeslot’s frame 0 B6 alarm bit will be
switched if the opposite state is received in 3 consecutive
frames. State "1" is used for alarm. Alarm status depends on
fault consequences (AIS insertion into the signaling timeslot).
62 21 MEI "MFrame far-end alarm, group B"
The state of signaling timeslot’s frame 0 B6 alarm bit will be
switched if the opposite state is received in 3 consecutive
frames. State "1" is used for alarm. Alarm status depends on
fault consequences (AIS insertion into the signaling timeslot).
63 21 MEI, S "MFrame far-end alarm, group C"
The state of signaling timeslot’s frame 0 B6 alarm bit will be
switched if the opposite state is received in 3 consecutive
frames. State "1" is used for alarm. Alarm status depends on
fault consequences (AIS insertion into the signaling timeslot).
64 21 MEI "MFrame far-end alarm, group C"
The state of signaling timeslot’s frame 0 B6 alarm bit will be
switched if the opposite state is received in 3 consecutive
frames. State "1" is used for alarm. Alarm status depends on
fault consequences (AIS insertion into the signaling timeslot).
65 21 MEI, S "MFrame far-end alarm, group D"
The state of signaling timeslot’s frame 0 B6 alarm bit will be
switched if the opposite state is received in 3 consecutive
frames. State "1" is used for alarm. Alarm status depends on
fault consequences (AIS insertion into the signaling timeslot).
66 21 MEI "MFrame far-end alarm, group D"
The state of signaling timeslot’s frame 0 B6 alarm bit will be
switched if the opposite state is received in 3 consecutive
frames. State "1" is used for alarm. Alarm status depends on
fault consequences (AIS insertion into the signaling timeslot).
67 16 DMA "BER10E-6"
BER10E-6 error rate is calculated from CRC block errors
when bit rate ≥ 1024 kbit/s. Counting time is 10 seconds
and the limit for the fault condition depends on the bit rate
used (2048 limit is 10).
68 58 MEI "Faults masked/test"
The fault is activated when the interface Fault mask setting
is on
(all interface faults are cleared).
69 30 DMA "Frequency difference"
The measurement period is 15 seconds and the phase-drifting
limit is 5 ms (in USW versions newer than 6.7 the limit is 18
ms). The fault is activated if the phase-drifting limit has been
exceeded in 3 measurements out of 4.
70 30 MEI "Buffer slip(s)/1 hour"
The fault is activated if one or more buffer slip(s) have been
detected during the last hour.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

89
20 GMH

SPT GPT Status SPT Description


71 41 DMA "HDLC overlap with X-bus"
The fault is activated if the HDLC control channel bit(s) are
also used by the cross-connection bus.
72 41 DMA "MCLK RAI overlap with X-bus"
The fault is activated if the MCLK/RAI bit is also used by
the cross-connection bus.
73 32 PMA, S "ASIC register error"
The fault is activated if the difference between write/read
configuration data of ASIC has been detected.
74 60 DMA "G821 limit event"
This fault is activated as a delta fault if the G.821 supervision
is used and at least one performance limit (SES, ES, RAI
second, CRCE) has been exceeded in a 15-minute period.
75 48 PMA, S "G821 unavailable state"
The fault is activated if the G.821 supervision is used and
the state of the signal becomes unavailable (10 consecutive
SES seconds). The fault is deactivated when 10 consecutive
seconds not classified as SES have been found.
78 69 DMA "Port locking conflict"
The fault is activated if the SXU has the port descriptor but
the unit interface is unlocked or the SXU does not have
the port descriptor although the interface is locked. Use
lock/unlock.
79 53 MEI "Protection switch forced"
The unit is in 1+1 protected mode and the protection switch
has been forced to select signal from IF1 or IF2.
80 55 PMA "Incompatible EPROM/FLASH SW"
The fault is activated if there is downloaded software in the
flash but the revision is wrong (for example if EPROM SW
is r5.5 and downloaded SW is r6.1).
81 5 PMA "Chksum err in downloaded SW"
The downloaded software has been corrupted.
82 112 DMA, (S) "Excessive errors"
Once every second, block errors shall be compared with the
limit value. If errors count ≥ limit, the one second shall be
declared BAD, otherwise it shall be declared GOOD.
The Excessive errors shall be detected if M consecutive BAD
seconds have occurred.
The Excessive errors shall be cleared if M consecutive
GOOD seconds have occurred.
M value range 2..9.
83 103 DMA, (S) "Degraded errors"
Once every second, block errors shall be compared with the
limit value. If errors count ≥ limit the one second shall be
declared BAD, otherwise it shall be declared GOOD.
The Degraded errors shall be detected if M consecutive BAD
seconds have occurred.
The Degraded errors shall be cleared if M consecutive
GOOD seconds have occurred.
M value range 2..9.
84 49 DMA "Noise margin alarm"
The quality of the line is not good enough for data
communications.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

90
20 GMH

SPT GPT Status SPT Description


85 24 PMA, S "Loss of HDSL frame"
See ETSI TS 101 135 Loss of HDSL frame alignment.
86 75 PMA, S "Chain number conflict"
The existing numbering differs from defined, and
re-numbering operation is recommended.
87 114 PMA, S "UNAVAIL (G.826)"
A period of unavailable time begins at the onset of ten
consecutive SES events. These ten seconds are considered to
be part of unavailable time. A new period of available time
begins at the onset of ten consecutive non-SES events. These
ten seconds are considered to be part of available time.
88 114 PMA, S "UNAVAIL far end"
A period of far end unavailable time (only when
unidirectional performance collection used) begins at the
onset of ten consecutive far end SES events. These ten
seconds are considered to be part of far end unavailable time.
A new period of available time begins at the onset of ten
consecutive non-far end SES events. These ten seconds are
considered to be part of available time.
89 49 DMA "QOS"
Quality of signal. 24 hours period.
At least one of SES, BBE or ES limit exceeded. Cleared
when period changes.
90 49 DMA, S "QOSTR"
Quality of signal. 15 minutes period.
At least one of limits ES, BBE , SES has been exceeded.
Cleared when found a period where none of the ES, BBE or
SES limits has been exceeded.
Note that ES and BBE have upper/lower limit so that upper
must be exceeded to get a fault and lower is used as a limit
when fault is activated.
91 55 PMA, S "Missing application program"
There is no application program in the flash memory.
Download the latest version of the program.
92 55 PMA, S "HW/SW version conflict"
Current HW version is incompatible with the current SW.
93 68 DMA, R "Door open"
Indicates that the modem door, e.g. 8110 OTU-2M is open
(8110 OTU-2M is connected to QMH interface).
94 68 DMA, R "Customer alarm 1"
Indicates that the external (1) alarm in modem, e.g. 8110
OTU-2M is active (8110 OTU-2M is connected to QMH
interface).
95 68 DMA, R "Customer alarm 2"
Indicates that the external (2) alarm in modem, e.g. 8110
OTU-2M is active (8110 OTU-2M is connected to QMH
interface).
250 117 PMA “AIS Reported from 6300”
6300 Trail is broken, PBC, 6300 VC4 is Unavailable or there
is a Setup failure. See I/F message for additional information.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

91
21 GMM

21 GMM
SPT GPT Status SPT Description
1 1 PMA "Unpredicted Fault"
This fault condition should never occur (or is not yet
supported).
2 2 PMA, S "Reset"
There has been a unit reset (detected always after the
power-up of the unit).
3 4 PMA "Power +5 V (subrack)"
The voltage is below the threshold limit
(about 4.6 V depending on the calibration and the A/D
resolution).
4 4 PMA "Power +5 V (unit)"
The voltage is below the threshold limit
(about 4.6 V depending on the calibration and the A/D
resolution).
5 4 PMA "Power +12 V (unit)"
The voltage is below the threshold limit
(about 11.3 V depending on the calibration and the A/D
resolution).
6 4 PMA "Power -10 V (unit)"
The voltage is above the threshold limit
(about -9.0 V depending on the calibration and the A/D
resolution).
7 36 PMA, S "Start permission denied"
No start permission. The unit is not in its correct place.
8 38 PMA, S "Bus sync fault"
The fault is activated if the X-bus synchronization pulse
transmitted by SXU is missing. A possible reason for this
fault is that SXU is missing.
11 5 PMA, S "RAM fault"
A background process has found a RAM location where the
read value does not match the written test pattern.
12 5 PMA, S "EPROM Fault"
The calculated check sum does not match the stored one.
13 5 PMA "Flash write error"
Error when writing to the flash memory (main bank).
14 5 PMA "Flash copy error"
Error when writing to the flash memory (shadow bank).
15 5 PMA "Flash erase error"
Error during the erase of the flash memory (shadow bank).
16 5 PMA "Flash duplicate error"
Duplicated parameters (the same ID) detected during the
start-up.
17 5 PMA "Flash shadow error"
The shadow bank of the flash is not erased during the start-up.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

92
21 GMM

SPT GPT Status SPT Description


18 5 PMA, S "Flash check sum error"
Parameter setting check sum error detected.
19 5 PMA, S "Missing settings"
One of the setting structures has been corrupted in the
non-volatile memory.
20 5 PMA, S "EEPROM fault"
EEPROM fault.
25 5 PMA "Chksum err in downloaded SW"
The downloaded software has been corrupted.
26 55 PMA "Incompatible EPROM/FLASH SW"
The downloaded software (in the flash) is not compatible
with the system software in the EPROMs.
30 11 PMA, S "Loss of protected signal"
In 1+1 protection mode both interfaces IF1 and IF2 have
faults which in unprotected mode have an S status.
31 53 MEI "Protection switch forced"
The unit is in 1+1 protected mode and the protection switch
has been forced to select signal from IF1 or IF2.
35 62 PMA, S "HW fault in base unit"
Hardware does not work as expected.
36 62 PMA, S "HW fault in base unit"
Hardware does not work as expected.
37 62 PMA, S "HW fault in base unit"
Hardware does not work as expected.
38 62 PMA, S "HW fault in base unit"
Hardware does not work as expected.
39 62 PMA, S "HW fault in base unit"
Hardware does not work as expected.
40 62 PMA, S "HW fault in base unit"
Hardware does not work as expected.
41 10 PMA, S "Missing module"
The interface module defined in the settings is missing
42 10 PMA, S "Conflict in module type"
There is a conflict between the installed module and the
settings.
43 62 PMA, S "HW fault in base unit"
Hardware does not work as expected.
44 62 PMA, S "HW fault in base unit"
Hardware does not work as expected.
45 62 PMA, S "HW fault in base unit"
Hardware does not work as expected.
46 40 PMA, S "Missing IA activity"
The fault is activated if the unit cannot find its locked
interface address on the cross-connection bus. SXU should
activate IA on the bus if the interface is locked.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

93
21 GMM

SPT GPT Status SPT Description


47 29 PMA, S "No response to NNM messages"
The control channel of the interface is used and the neighbor
node supervision option of the interface is on and no NNM
(Neighbor Node Monitoring) message has been received
from the interface within a specified period.
48 29 PMA, S "Own NNM message received"
The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received
NNM message contains the same identification data as the
NNM message sent to the interface.
49 29 PMA, S "Wrong IDs in NNM message"
The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received
NNM message contains unexpected neighbor identification
data.
50 41 DMA "HDLC overlap with X-Bus"
The fault is activated if the HDLC control channel bit(s) are
also used by the cross-connection bus.
51 58 MEI,S "Fault masked / test"
The fault is activated when the interface Fault mask setting
is on
(all interface faults are cleared).
52 27 MEI, S "Interface loopback"
An interface loop is created in the interface module. It loops
transmitted data and the clock signal back to the interface
receiver.
53 27 MEI, S "Equipment loopback"
Similar to Interface back to equipment loop except that the
loop is made before the interface module in the GMM unit
base card.
54 27 MEI, S "Line loopback"
Rx data is looped back to the interface transmitter.
55 27 MEI, S "Line loop made by neighbor"
This alarm is activated if the HDLC channel is in use and
MUX/DEMUX back to the line loop has been made to the
neighbor unit.
56 27 MEI, S "Remote line loopback"
This alarm is activated if the HDLC channel is in use and
MUX/DEMUX back to the line loop has been made to the
neighbor unit, or the BTE module is used and the V.54 loop
has been made to the remote end.
57 27 MEI, S "CSU line loopback"
The signal is looped back to the line (loop made by the T1
data link).
58 27 MEI, S "CSU payload loopback"
The payload signal is looped back to the line (loop made by
the T1 data link).
61 12 PMA, S "Loss of input signal"
The signal level is below a specific level.
62 12 DMA, S "Loss of input signal"
The signal level is below a specific level.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

94
21 GMM

SPT GPT Status SPT Description


63 12 MEI, S "Loss of input signal"
The signal level is below a specific level.
64 24 PMA, S "Loss of frame on input signal"
Loss of frame alignment.
65 24 DMA, S "Loss of frame on input signal"
Loss of frame alignment.
66 24 MEI, S "Loss of frame on input signal"
Loss of frame alignment.
67 23 PMA, S "AIS on input signal"
‘1’ is received continuously.
68 23 DMA, S "AIS on input signal"
‘1’ is received continuously.
69 23 MEI, S "AIS on input signal"
‘1’ is received continuously.
70 20 PMA, S "FrFEA (yellow alarm)"
Frame is lost at the far-end.
71 20 DMA, S "FrFEA (yellow alarm)"
Frame is lost at the far-end.
72 20 MEI, S "FrFEA (yellow alarm)"
Frame is lost at the far-end.
73 13 MEI "BER 10e-3"
Bit error rate is worse than 10-3.
81 48 PMA, S "G821 unavailable state"
The fault is activated if the G.821 supervision is used and
the state of the signal becomes unavailable (10 consecutive
SES seconds). The fault is deactivated when 10 consecutive
seconds not classified as SES have been found.
82 60 DMA "G821 performance event"
This fault is activated as a delta fault if the G.821 supervision
is used and at least one performance limit (SES, ES, RAI
second, CRCE) has been exceeded in a 15-minute period.
83 48 PMA, S "TR820 unavailable state"
The fault is activated if the state of the signal becomes
unavailable (10 consecutive SES seconds). The fault is
deactivated when 10 consecutive seconds not classified as
SES have been found.
84 60 DMA "TR820 performance event"
The 15min or one day threshold has been exceeded.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

95
22 GMU, GMU-A, GMU-M

22 GMU, GMU-A, GMU-M


SPT GPT Status SPT Description
1 1 PMA, S "SW unpredicted"
This fault condition should never occur (or is not yet
supported).
2 2 PMA, S "Reset (gmz460)"
There has been a unit reset (detected always after the
power-up of the unit).
3 4 PMA "VB1: +5 V (BUS1)"
The voltage is below the threshold limit (about 4.6 V
depending on the calibration and the A/D resolution).
4 4 PMA "Power +12 V"
The voltage is below the threshold limit (about 11.3 V
depending on the calibration and the A/D resolution).
5 4 PMA "Power -10 V"
The voltage is above the threshold limit (the limit depends on
the calibration and the A/D resolution).
6 4 PMA "Power +3.3 V (gmz460)"
The voltage is above the threshold limit (limit depends on the
calibration and the A/D resolution).
7 4 PMA "Protected bus voltages"
Protected bus voltages are above the threshold limit (limit
depends on the calibration and the A/D resolution).
8 37 MEI "Opt.bias limit (50) exceeded"
Not monitored!
9 37 MEI "Opt.bias limit (100) exceeded"
Not monitored!
10 37 DMA "Tx power limit exceeded"
Transmit power of the optical interface module exceeds its
limit.
11 5 PMA, S "RAM fault (gmz460)"
A background process has detected a RAM location where
the read value does not match the written test pattern.
12 5 PMA, S "EPROM fault (gmz460)"
The calculated check sum does not match with the stored one.
13 5 PMA, S "EEPROM write error (gmz460)"
Error when writing to the memory.
14 5 PMA, S "EEPROM checksum error (gmz460)"
The calculated check sum does not match with the stored one.
15 5 PMA "Flash write error (gmz460)"
Error when writing to the flash memory (main bank).
16 5 PMA "Flash copy error (gmz460)"
Error when writing to the flash memory (shadow bank).
17 5 PMA "Flash erase error (gmz460)"
Error during the erase of the flash memory (shadow bank).

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

96
22 GMU, GMU-A, GMU-M

SPT GPT Status SPT Description


18 5 PMA "Flash duplicate error (gmz460)"
Duplicated parameters (the same ID) detected during the
start-up.
19 5 PMA "Flash shadow error (gmz460)"
The shadow bank of the flash is not erased during the start-up.
20 5 PMA "Flash check sum error (gmz460)"
The calculated check sum does not match with the stored one.
21 5 PMA, S "Missing Settings"
One of the setting structures has been corrupted in the
non-volatile memory.
22 5 PMA, S "CRC err.LAC RAM 1/2/3/4"
CRC error detected in one of the ASIC’s RAM memories.
23 62 DMA "Clock frequency outsize of holdover range"
Node clock cannot be measured by GMU for the holdover
mode.
24 223 MEI "Temperature measurement"
Unit temperature exceeds its limit.
25 5 PMA, S "EPROM fault (gmz461) "
The calculated check sum does not match with the stored one.
26 5 PMA, S "EEPROM write error (gmz461) "
Error when writing to the EEPROM memory.
27 5 PMA, S "EEPROM checksum error (gmz461) "
The calculated check sum does not match the stored one.
28 5 PMA "Flash write error (gmz461) "
Error when writing to the flash memory (main bank).
29 5 PMA "Flash copy error (gmz461) "
Error when writing to the flash memory (shadow bank).
30 39 PMA, S "System clock missing"
19.44 MHz clock of GMU is missing.
31 39 PMA, S "Node clock missing"
16.896 MHz node clock missing. A typical reason for this
fault is that SXU is missing.
32 30 MEI "SOH/POh slips (XBI) "
Not monitored!
33 39 DMA "16/20MHz clocks not locked"
19.44 MHz of the GMU clock not locked with 16.896 MHz
clock of the node.
34 38 PMA, S "F/MSYNC problem in X-bus"
The fault is activated if the X-bus synchronization pulse
transmitted by SXU is missing. A typical reason for this fault
is that SXU is missing. If only one GMU unit has this fault
although there are other GMU units in the subrack then the
fault is most likely in the GMU unit.
35 28 PMA, S "IA alarm from IA mon."
The IA addresses do not work correctly.
36 62 PMA "POH/SOH blk counter fault"
Not monitored!

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

97
22 GMU, GMU-A, GMU-M

SPT GPT Status SPT Description


37 62 PMA "Osc.D/A conv.limit exceeded"
Not monitored!
38 41 DMA "Hdlc/x-bus in same TS"
The fault is activated if the HDLC control channel bit(s) are
also used by the cross-connection bus. The HDLC control
channel is located in a cross-connect TS. Control channel
data overdrives cross-connection data.
39 72 PMA "Extended backup unit fault"
Extended backup unit not responding.
Probably it is missing or not in inventory.
40 58 MEI "Faults masked"
The fault is activated when the interface Fault mask setting is
on.
41 10 PMA, S "If module missing"
The interface module defined in the settings is missing.
42 10 PMA, S "Incorrect if module"
There is a conflict between the installed module and the
settings.
43 39 PMA, S "LO transmitt clk"
Loss of the 155.52 MHz transmit clock when using STM-1
interface module.
44 55 PMA, S "Incomp. EPROM/FLASH SW (gmz460)"
The fault is activated if there is downloaded software in flash
but the revision is wrong
(for example if EPROM SW is r5.5 and downloaded SW
is r6.1).
45 5 PMA, S "Checksum error in dnl SW (gmz460)"
The downloaded software has been corrupted.
46 27 MEI, S "ES Equipment loop"
ES loop is active.
Electrical section Tx to Rx loop activate.
47 69 PMA "Setup data mismatch"
Information stored to the setup is self-contradictory.
48 3 PMA, S "Initialization error (gmz460)"
Initialization of application SW unsuccessful (after the
power-up of the unit).
49 108 PMA, S "LOS"
Loss of signal.
Loss of signal defect is declared when a supervised signal
has not had any transitions for a period of time or the signal
indicating degradation of level in the received signal is
activated.
50 27 MEI, S "OS Equipment loop"
OS loop is active.
51 5 PMA "Flash erase error (gmz461)"
Error during the erase of the flash memory (shadow bank).
52 106 PMA, S "LOF"
See CCITT G.706 Loss of frame alignment.
Loss of frame. Frame alignment is done according to
requirements presented in DE/TM-1015-1 and G.783.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

98
22 GMU, GMU-A, GMU-M

SPT GPT Status SPT Description


53 73 PMA, S "SSF"
Server signal fail.
Defect in above layer sets SSF to below layer (a defect
occurred in the upper layer activates an SSF fault in the
lower layer).
54 113 MEI PMA, "TIM"
S Received trace identifier does not match the expected one.
55 103 DMA "DEG"
Signal degrade.
Once every second, block errors shall be compared with the
limit value. If errors count ≥ limit, the one second shall be
declared BAD, otherwise it shall be declared GOOD.
The Signal Degrade defect (dDEG) shall be detected if M
consecutive BAD seconds have occurred.
The Signal Degrade defect (dDEG) shall be cleared if M
consecutive GOOD seconds have occurred.
M value range 2..9.
56 111 MEI "RDI"
Remote defect indicator
5 consecutive equal new values of the RxRDI.
57 114 DMA "UNAVAIL"
Performance monitoring in an unavailable state (G.774.01).
58 49 PMA "QOS"
Quality of signal. 24 hours period.
At least one of SES, BBE or ES limit exceeded. Cleared
when period changes.
59 49 PMA "QOSTR"
Quality of signal. 15 minutes period.
At least one of limits ES, BBE , SES has been exceeded.
Cleared when found a period where none of the ES, BBE or
SES limits has been exceeded.
Note that ES and BBE have upper/lower limit so that upper
must be exceeded to get a fault and lower is used as a limit
when the fault is activated.
60 29 PMA, S "No response to NNM message"
The control channel of the interface is used and the neighbor
node supervision option of the interface is on and no NNM
(Neighbor Node Monitoring) message has been received
from the interface within 8 seconds.
61 29 PMA, S "Own NNM message received"
The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received
NNM message contains the same identification data as the
NNM message sent to the interface.
62 29 PMA, S "Wrong id in NNM msg"
The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received
NNM message contains unexpected neighbor identification
data.
63 27 MEI, S "Line loop made by NN"
This alarm is activated if the HDLC channel is in use and
MUX/DEMUX back to the line loop has been activated from
the remote end.
Rx to TX loop activated by the neighbor node.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

99
22 GMU, GMU-A, GMU-M

SPT GPT Status SPT Description


64 27 MEI, S "VC2 loop"
VC2 loop is active.
65 27 MEI, S "VC12 loop"
VC12 loop is active.
66 73 DMA "SSF (working)"
Protected channel has a serious fault (MS 1+1 or SNC
protection).
67 101 PMA, S "AIS"
Alarm indication signal. In the S34M interface AIS defect is
detected according to DE/TM-01015-2-1.
68 27 MEI, S "RS Line loop"
RS loop is active.
Regeneration section Rx to Tx loop activate.
69 107 PMA, S "LOP"
Loss of pointer.
The TU-pointer is interpreted according to ETSI
DE/TM-105-1.
70 5 PMA "Flash duplicate error (gmz461)"
Duplicated parameters (the same ID) detected during the
start-up
71 109 PMA, S "SLM"
Signal label mismatch.
Received signal label not valid.
72 109 PMA, S "UNEQ"
Received signal label in the UNEQ state.
73 25 PMA, S "LOM"
Loss of multiframe alignment.
The multiframe indication byte H4 is interpreted according
to ITU G.783 recommendations
74 5 PMA "Flash shadow error (gmz461)"
The shadow bank of the flash is not erased during the start-up.
75 5 PMA "Flash check sum error (gmz461)"
The calculated check sum does not match with the stored one.
76 77 DMA "FOP"
Failure of protocol when using MS 1+1 protection:
-Protection switching time not within 50 ms.
-Request active, but no answer from far end.
- One end is in 1+1 mode and the other in 1:1.
77 21 MEI, S "MRDI groupA"
When three consecutive equal new values of RxFEA are
received it is accepted in AcFEA.
Multiframe remote defect indicator in signaling group A.
78 101 MEI, S "MAIS groupA"
Multiframe Alarm indication signal in signaling group A.
The signaling AIS is detected when one signaling multiframe
is all ‘1’ or contains only one ‘0’.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

100
22 GMU, GMU-A, GMU-M

SPT GPT Status SPT Description


79 25 PMA "MLOF groupA"
The multiframe alignment is lost when two consecutive
wrong FSW values or all ‘0’ multiframes are found. The next
signaling byte with four zeros in bits 1..4 is considered to be
the correct FSW. To avoid a false alignment it is required that
the previous signaling byte was not all ‘0’.
Multiframe loss of frame in signaling group A.
80 5 PMA, S "Missing Settings (gmz461)"
One of the setting structures has been corrupted in the
non-volatile memory.
81 2 PMA, S "Reset (gmz461)"
There has been a unit reset (detected always after the
power-up of the unit).
82 5 PMA, S "RAM Fault (gmz461)"
A background process has detected a RAM location where
the read value does not match the written test pattern.
83 4 PMA "Power +3.3 V(gmz461)"
The voltage is above the threshold limit (limit depends on the
calibration and the A/D resolution)
84 36 PMA, S "Start permission denied"
Most likely the unit does not belong to the node configuration.
85 55 PMA, S "Incomp. EPROM/FLASH SW (gmz461)"
The fault is activated if there is downloaded software in the
flash but the revision is wrong (for example if EPROM SW is
r5.5 and downloaded SW is r6.1).
86 5 PMA, S "Checksum error in dnl SW (gmz461)"
The downloaded software has been corrupted.
87 3 PMA, S "Initialization error (gmz461)"
Initialization of application SW unsuccessful (after the
power-up of the unit).
88 21 MEI, S "MRDI groupB"
Multiframe remote defect indicator in signaling group B.
89 101 MEI, S "MAIS groupB"
Multiframe Alarm indication signal in signaling group B.
90 25 PMA, S "MLOF groupB"
Multiframe loss of frame in signaling group B.
91 21 MEI, S "MRDI groupC"
Multiframe remote defect indicator in signaling group C.
92 101 MEI, S "MAIS groupC"
Multiframe Alarm indication signal in signaling group C.
93 25 PMA, S "MLOF groupC"
Multiframe loss of frame in signaling group C.
94 27 MEI, S "MSP Equipment loop"
MSP loop is active.
95 27 MEI, S "MS Line loop"
MS loop is active.
96 27 MEI, S "S4D Line loop"
S4D loop is active.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

101
22 GMU, GMU-A, GMU-M

SPT GPT Status SPT Description


97 27 MEI, S "E34M Equipment loop"
E34M loop is active.
98 27 MEI, S "O34M Equipment loop"
O34M loop is active.
99 27 MEI, S "PS34M Line loop"
PS34M loop is active.
100 27 MEI, S "PS34MP Equipment loop"
PS34MP loop is active.
101 62 PMA, S "LO ph. locking for 68.368MHz (34M)"
Loss of phase locking for 68.368MHz when using the S34M
interface module. The 34.368 MHz transmit clock cannot
be generated.
102 73 DMA "SSF (protecting)"
Protecting channel has a serious fault (MS 1+1 or SNC
protection).
103 74 PMA, S "Group failed"
Both working and protecting channels failed when using MS
1+1 or SNC protection.
104 103 DMA "Group DEG"
Block errors indicated read from MS1+1 protected TTP or
connection protection group.
105 62 MEI "Osc. phase transient suppression fail"
Tx phase transient over limits.
106 21 MEI, S "MRDI"
Multiframe remote defect indicator.
107 101 MEI, S "MAIS"
Multiframe Alarm indication signal in signaling.
108 25 PMA, S "MLOF"
Multiframe loss of frame in signaling.
109 69 PMA "Settings corrupted"
Fatal setup corruption. The unit must be configured again
or it must be replaced to a slot where a compatible unit is
registered; unit inherits settings.
110 72 PMA "No extended backup unit address"
Control unit returns no address of the extended backup unit.
Capacity of the extended backup unit may have run out
(especially when not using the SCP unit).
111 30 DMA "Buffer slip(s) / 1 hour"
Not monitored.
112 36 PMA "Improper control unit"
Not used in GMU and GMU-M.
113 36 PMA "Improper environment"
GMU-M does not work in 8170 cluster node.
114 117 PMA “Remote 2M unavailable”
Remote 6300 2M port is unavailable. PBC
PayloadTypeMismatch, LossOfSignal, AIS, LossOfFrame or
Setup failure. See I/F message for additional information.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

102
22 GMU, GMU-A, GMU-M

SPT GPT Status SPT Description


115 117 PMA “Trail unavailable reported from 6300”
6300 trail is broken, PBC, 6300 VC4 is unavailable or there
is a Setup failure. See I/F message for additional information.
116 112 PMA, S, R “EXC”
Once every second block errors shall be compared with a
limit value that can be defined. If errors count ≥ limit, the
one second shall be declared BAD, otherwise it shall be
declared GOOD.
The Excessive error defect shall be detected if M (can be
defined) consecutive BAD seconds have occurred.
The Excessive errors defect shall be cleared if M consecutive
GOOD seconds have occurred.
158 91 MEI “Performance event for G.826”
At least one of the performance event counters differs from
zero during the last 15-minute period."
250 117 PMA “Remote 2M Unavailable”
Remote 6300 2M port is unavailable. PBC
PayloadTypeMismatch, LossOfSignal, AIS, LossOfFrame or
Setup failure. See I/F message for additional information.
251 117 PMA “Trail Unavailable Reported from 6300”
6300 Trail is broken, PBC, 6300 VC4 is unavailable or there
is a Setup failure. See I/F message for additional information.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

103
23 GMX

23 GMX
SPT GPT Status SPT Description
1 1 PMA, S "SW unpredicted"
This fault condition should never occur (or is not yet
supported).
2 2 PMA, S "Reset "
There has been a unit reset (detected always after the
power-up of the unit).
3 4 PMA "VB1: +5 V "
The voltage is below the threshold limit (about 4.6 V
depending on the calibration and the A/D resolution).
4 4 PMA "Power +12 V"
The voltage is below the threshold limit (about 11.3 V
depending on the calibration and the A/D resolution).
5 4 PMA "Power -10 V"
The voltage is above the threshold limit (limit depends on the
calibration and the A/D resolution).
6 4 PMA "Power +3.3 V "
The voltage is above the threshold limit (limit depends on the
calibration and the A/D resolution).
7 4 PMA " Power +5 V (BUS)"
The voltage is above the threshold limit (limit depends on the
calibration and the A/D resolution).
8 37 MEI "Opt. bias limit (50) exceeded"
Not monitored.
9 37 MEI "Opt. bias limit (100) exceeded"
Not monitored
10 37 DMA "Tx power limit exceeded"
Transmit power of the optical interface module exceeds its
limit.
11 5 PMA, S "RAM Fault"
A background process has detected a RAM location where
the read value does not match the written test pattern.
13 5 PMA, S "EEPROM write error "
Error when writing to the memory.
14 5 PMA, S "EEPROM checksum error"
The calculated check sum does not match the stored one.
16 69 PMA "Reading extended backup settings"
The unit is reading its extended backup settings from the ext.
backup unit. Do not interrupt.
18 5 PMA "File system bad block found"
One of the blocks in the flash system is not in use anymore.
20 5 PMA "File system fatal error"
Flash system failed. Replace the unit with a spare unit.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

104
23 GMX

SPT GPT Status SPT Description


21 5 PMA, S "Missing Settings"
One of the setting structures has been corrupted in the
non-volatile memory.
22 5 PMA, S "CRC err.LAC RAM 1/2/3/4"
CRC error detected in one of the ASIC’s RAM memories.
23 62 DMA "Clock frequency outside of holdover range"
Node clock cannot be measured by GMX for the holdover
mode.
24 223 MEI "Temperature measurement"
Unit temperature exceeds its limit.
25 5 PMA, S "HW conflict "
Interface module version incorrect. Use a newer version.
30 39 PMA, S "20 Mhz node clock missing"
19.44 MHz clock of the GMX is missing.
31 39 PMA, S "16 Mhz node clock missing"
16.896 MHz node clock is missing. In an 8150 basic node, a
typical reason for this fault is that SXU is missing.
32 30 MEI "SOH/POH slips (XBI) "
Not monitored.
33 39 DMA "16/17MHz clocks not locked"
19.44 MHz of the GMX clock not locked with the 16.896
MHz clock of the node.
34 38 PMA, S "F/MSYNC problem in X-bus"
X-bus synchronization pulse missing.
35 28 PMA, S "IA alarm from IA monitoring"
The IA addresses do not work correctly.
36 62 PMA "POH/SOH blk counter fault"
Not monitored.
37 62 PMA "Osc.D/A conv.limit exceeded"
Not monitored.
38 41 DMA "HDLC/x-bus in same TS"
The fault is activated if the HDLC control channel bit(s) are
also used by the cross-connection bus. The HDLC control
channel is located in a cross-connect TS. Control channel
data overdrives cross-connection data.
39 72 PMA "Extended backup unit fault"
Extended backup unit not responding.
Probably it is missing or not in inventory.
40 58 MEI "Faults masked"
The fault is activated when the interface Fault mask setting is
on.
41 10 PMA, S "IF module missing"
The interface module defined in the settings is missing.
42 10 PMA, S "Incorrect if.module"
There is a conflict between the installed module and the
settings.
43 39 PMA, S "LO transmit clk"
Loss of the 155.52 MHz transmit clock when using the
STM-1 interface module.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

105
23 GMX

SPT GPT Status SPT Description


44 55 PMA, S "Incompatible SW"
The fault is activated if there is downloaded software in the
flash but the revision is wrong
(for example if EPROM SW is r5.5 and downloaded SW
is r6.1).
45 5 PMA, S "Checksum error in dnl SW"
The downloaded software has been corrupted.
46 27 MEI, S "ES Equipment loop"
ES loop is active.
Electrical section Tx to Rx loop activate.
47 69 PMA "Setup data mismatch (GMX A/B) "
Difference detected between two GMXs’ non-volatile
settings.
48 3 PMA, S "Initialization error (SDH part) "
Initialization of application SW unsuccessful (after the
power-up of the unit).
49 108 PMA, S "LOS"
Loss of signal.
Loss of signal defect is declared when a supervised signal
has not had any transitions for a period of time or the signal
indicating degradation of level in the received signal is
activated.
50 27 MEI, S "OS Equipment loop"
OS loop is active.
52 106 PMA, S "LOF"
See CCITT G.706 Loss of frame alignment.
Loss of frame. Frame alignment is done according to
requirements presented in DE/TM-1015-1 and G.783.
53 73 PMA, S "SSF"
Server signal fail.
Defect in above layer sets SSF to below layer (a defect
occurred in the upper layer activates an SSF fault in the
lower layer).
54 113 PMA, S "TIM"
Received trace identifier does not match the expected one.
55 103 DMA "DEG (-raded errors)"
Signal degrade.
Once every second, block errors shall be compared with the
limit value. If errors count ≥ limit, the one second shall be
declared BAD, otherwise it shall be declared GOOD.
The Signal Degrade defect (dDEG) shall be detected if M
consecutive BAD seconds have occurred.
The Signal Degrade defect (dDEG) shall be cleared if M
consecutive GOOD seconds have occurred.
M value range 2..9.
56 111 MEI "RDI"
Remote defect indicator
5 consecutive equal new values of the RxRDI.
57 114 DMA "UNAVAIL"
Performance monitoring in an unavailable state (G.774.01).

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

106
23 GMX

SPT GPT Status SPT Description


58 49 PMA "QOS"
Quality of signal. A 24-hour period.
At least one of SES, BBE or ES limit exceeded. Cleared
when period changes.
59 49 PMA "QOSTR"
Quality of signal. A 15-minute period.
At least one of limits ES, BBE , SES has been exceeded.
Cleared when found a period where none of the ES, BBE or
SES limits has been exceeded.
Note that ES and BBE have upper/lower limit so that the
upper must be exceeded to get a fault and the lower is used as
a limit when the fault is activated.
60 29 PMA, S "No response to NNM message"
The control channel of the interface is used and the neighbor
node supervision option of the interface is on and no NNM
(Neighbor Node Monitoring) message has been received
from the interface within 8 seconds.
61 29 PMA, S "Own NNM message received"
The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received
NNM message contains the same identification data as the
NNM message sent to the interface.
62 29 PMA, S "Wrong ID in NNM msg"
The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received
NNM message contains unexpected neighbor identification
data.
63 27 MEI, S "Line loop made by NN"
This alarm is activated if the HDLC channel is in use and
MUX/DEMUX back to the line loop has been activated from
the remote end.
Rx to TX loop activated by the neighbor node.
64 27 MEI, S "VC2 loop"
VC2 loop is active.
65 27 MEI, S "VC12 loop"
VC12 loop is active.
66 73 DMA "SSF (working) "
Protected channel has a serious fault (MS 1+1 or SNC
protection).
67 101 PMA, S "AIS"
Alarm indication signal. In the S34M interface AIS defect is
detected according to DE/TM-01015-2-1.
68 27 MEI, S "RS Line loop"
RS loop is active.
Regeneration section Rx to Tx loop activate.
69 107 PMA, S "LOP"
Loss of pointer.
The TU pointer is interpreted according to ETSI
DE/TM-105-1.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

107
23 GMX

SPT GPT Status SPT Description


70 5 PMA "EXC (-essive errors)"
Once every second, block errors shall be compared with
settable limit value. If errors count ≥ limit, the one second
shall be declared BAD, otherwise it shall be declared GOOD.
The Excessive error defect shall be detected if M (settable)
consecutive BAD seconds have occurred.
The Excessive errors defect shall be cleared if M consecutive
GOOD seconds have occurred.
71 109 PMA, S "SLM"
Signal label mismatch.
Received signal label not valid.
72 109 PMA, S "UNEQ"
Received signal label in the UNEQ state.
73 25 PMA, S "LOM"
Loss of multiframe alignment.
The multiframe indication byte H4 is interpreted according
to ITU G.783 recommendations
76 77 DMA "FOP"
Failure of protocol when using MS 1+1 protection:
- Protection switching time not within 50 ms.
- Request active, but no answer from far end.
- One end is in 1+1 mode and the other in 1:1.
77 21 MEI, S "MRDI GroupA"
When three consecutive equal new values of RxFEA are
received it is accepted in the AcFEA.
Multiframe remote defect indicator in signaling group A.
78 101 MEI, S "MAIS groupA"
Multiframe Alarm indication signal in signaling group A.
The signaling AIS is detected when one signaling multiframe
is all ‘1’ or contains only one ‘0’.
79 25 PMA "MLOF groupA"
The multiframe alignment is lost when two consecutive
wrong FSW values or all ‘0’ multiframe is found. The next
signaling byte with four zeros in bits 1..4 is considered to be
the correct FSW. To avoid a false alignment it is required that
the previous signaling byte was not all ‘0’.
Multiframe loss of frame in signaling group A.
83 4 PMA "Power +3.3 V (BUS)"
The voltage is above the threshold limit (limit depends on the
calibration and the A/D resolution)
84 36 PMA, S "Start permission denied"
Most likely the unit does not belong to the node configuration.
85 33 PMA, S "X-Connect Bus Alarm, internal bus 1"
PCB, ASIC or connector failure in the GMX unit.
86 33 PMA, S "X-Connect Bus Alarm, internal bus 2"
PCB, ASIC or connector failure in the GMX unit.
87 3 PMA, S "Initialization error (XC part) "
Initialization of application SW unsuccessful (after the
power-up of the unit).
88 21 MEI, S "MRDI groupB"
Multiframe remote defect indicator in signaling group B.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

108
23 GMX

SPT GPT Status SPT Description


89 101 MEI, S "MAIS groupB"
Multiframe Alarm indication signal in signaling group B.
90 25 PMA, S "MLOF groupB"
Multiframe loss of frame in signaling group B.
91 21 MEI, S "MRDI groupC"
Multiframe remote defect indicator in signaling group C.
92 101 MEI, S "MAIS groupC"
Multiframe Alarm indication signal in signaling group C.
93 25 PMA, S "MLOF groupC"
Multiframe loss of frame in signaling group C.
94 27 MEI, S "MSP Equipment loop"
MSP loop is active.
95 27 MEI, S "MS Line loop"
MS loop is active.
96 27 MEI, S "S4D Line loop"
S4D loop is active.
97 27 MEI, S "E34M Equipment loop"
E34M loop is active.
98 27 MEI, S "O34M Equipment loop"
O34M loop is active.
99 27 MEI, S "PS34M Line loop"
PS34M loop is active.
100 27 MEI, S "PS34MP Equipment loop"
PS34MP loop is active.
101 62 PMA, S "LO ph. Locking for 68.368MHz (34M) "
Loss of phase locking for 68.368MHz when using the S34M
interface module. The 34.368 MHz transmit clock cannot
be generated.
102 73 DMA "SSF (protecting) "
Protecting channel has a serious fault (MS 1+1 or SNC
protection).
103 74 PMA, S "Group Failed"
Both working and protecting channels failed when using the
MS 1+1 or SNC protection.
104 103 DMA "Group DEG"
Block errors indicated read from MS1+1 protected TTP or
connection protection group.
105 62 MEI "Osc. phase transient suppression fail"
Tx phase transient over limits.
106 21 MEI, S "MRDI"
Multiframe remote defect indicator.
107 101 MEI, S "MAIS"
Multiframe Alarm indication signal in signaling.
108 25 PMA, S "MLOF"
Multiframe loss of frame in signaling.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

109
23 GMX

SPT GPT Status SPT Description


109 69 PMA "Settings corrupted"
Fatal setup corruption. The unit must be configured again,
or it must be replaced with a slot where compatible unit is
registered; unit inherits settings.
110 72 PMA "No extended backup unit address"
Control unit returns no address of the extended backup unit.
Capacity of the extended backup unit may have run out.
111 30 DMA "Buffer slip(s) / 1 hour"
Not monitored.
112 36 PMA "Improper control unit"
Not monitored.
113 36 PMA "Improper environment"
Not monitored.
117 33 DMA "X-Connect Bus1 Fault, upper shelf"
The cross-connect bus 1 is faulty. Bus 2 is used.
118 33 DMA "X-Connect Bus2 Fault, upper shelf"
The cross-connect bus 2 is faulty. Bus 1 is used.
119 33 PMA, S "X-Connect Bus Alarm, upper shelf"
Both cross-connect buses in the upper shelf are faulty. GMX
tries to use both buses in turn.
120 34 MEI "Loss of master clock locking"
The holdover clock is used and the fallback list contains
entries.
121 34 MEI "Fallback list warning"
The lowest choice is used (there are more than one choice in
the fallback list).
122 34 PMA "Loss of external clock"
The external clock input is enabled but the clock, connected
to input, is not acceptable.
123 34 PMA "Phase locked loop alarm"
The phase-locked loop of the master clock cannot be locked
to any clock.
124 34 MEI "External clock warning"
The external clock is included in the fallback list but the
external clock input is disabled.
125 34 MEI "Fallback list entry 2 used"
Fallback list entry 2 is used.
126 34 MEI "Fallback list entry 3 used"
Fallback list entry 3 is used.
127 34 MEI "Fallback list entry 4 used"
Fallback list entry 4 is used.
128 34 MEI "Fallback list entry 5 used"
Fallback list entry 5 is used.
129 34 MEI "Clock in holdover"
Holdover clock is used as a master clock for the node.
130 5 PMA, S "Flash list check sum error"
One of the flash lists (e.g. port descriptor list) has been
corrupted.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

110
23 GMX

SPT GPT Status SPT Description


131 32 PMA, S "X-connect error"
The internal data loop test is not successful. The
cross-connect matrix may be faulty.
132 32 PMA, S "ASIC latch error"
ASIC setting cannot be corrected by checking the background
process.
133 32 MEI "ASIC latch warning"
ASIC setting is corrected by checking the background
process.
134 32 MEI "X-connect RAM A14 warning"
Not monitored.
135 33 DMA "X-connect bus 1 fault, lower shelf "
The cross-connect bus 1 is faulty. Bus 2 is used.
136 33 DMA "X-connect bus 2 fault, lower shelf "
The cross-connect bus 2 is faulty. Bus 1 is used.
137 33 PMA, S "X-connect bus alarm, lower shelf "
Both cross-connect buses in the lower shelf are faulty. GMX
tries to use both buses in turn.
138 35 PMA "Time controlled X-connect warning"
A delta fault indicating a problem when switching
time-controlled cross-connection on/off. Additional
information can be read from the error log of the time control
process.
139 5 MEI "X-connect flash list conflict"
A corrupted cross-connect record has been detected in the
non-volatile memory after the unit reset. The record has
been deleted.
140 5 MEI "PortDesc flash list conflict"
A corrupted port descriptor record has been detected in the
non-volatile memory after unit reset. The record has been
deleted.
141 5 MEI "Swapped trunk flash list conflict"
A corrupted swap-trunk record has been detected in the
non-volatile memory after unit reset. The record has been
deleted.
142 5 MEI "Passivated trunk fls list conflict"
A corrupted passivate-trunk record has been detected in the
non-volatile memory after the unit reset. The record has
been deleted.
143 61 PMA "Reconfiguring X-connect database"
The background protection process of the passive GMX has
detected that the cross-connect configuration is different
in the active and passive sides. The passive GMX is
reconfiguring itself.
144 34 MEI "Faulty clock source of choice 1"
The state of fallback list entry 1 is faulty.
145 34 MEI "Faulty clock source of choice 2"
The state of fallback list entry 2 is faulty.
146 34 MEI "Faulty clock source of choice 3"
The state of fallback list entry 3 is faulty.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

111
23 GMX

SPT GPT Status SPT Description


147 34 MEI "Faulty clock source of choice 4"
The state of fallback list entry 4 is faulty.
148 34 MEI "Faulty clock source of choice 5"
The state of fallback list entry 5 is faulty.
149 34 MEI "Unstable SSM"
SSM byte values are not valid.
150 34 PMA "Clock failure switchover fault"
A fault becomes active if the following three conditions are
fulfilled:
1. External clock is enabled.
2. External clock is in fallback list.
3. Internal clock is in use (clocks at the FB list are not
reliable).
151 28 MEI, PMA, "Unit IA fault"
S Data transfer between GMX and a specified channel unit
does not work.
152 33 PMA, S, R "Active SBUS fault"
All connected TU-12 objects have parity errors on the active
SBUS
153 33 DMA, R "Passive SBUS fault"
All connected TU-12 objects have parity errors on the passive
SBUS
154 33 PMA, S, R "SBUS A activated"
SBUS A is switched to the active SBUS
155 33 PMA, S, R "SBUS B activated"
SBUS B is switched to the active SBUS
156 92 PMA, S, R "TU-12 fault on active SBUS"
Parity error of the TU-12 object allocated by the specified
unit on the active SBUS
157 92 DMA, R "TU-12 fault on passive SBUS"
Parity error of the TU-12 object allocated by the specified
unit on the passive SBUS
158 91 MEI ”Performance event for G.826”
At least one of the performance event counters differs from
zero during the last 15-minute period.
159 62 MEI "Unit initializing"
The unit is initializing. No operator actions should be carried
out with the unit, yet.
250 117 PMA “Remote 2M Unavailable”
Remote 6300 2M port is unavailable. PBC LossOfSignal,
AIS, LossOfFrame or Setup failure. See I/F message for
additional information.
251 117 PMA “Trail Unavailable Reported from 6300”
6300 Trail is broken, PBC, 6300 VC4 is unavailable, or there
is a setup failure. See I/F message for additional information.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

112
24 GMX2

24 GMX2
SPT GPT Status SPT Description
1 1 PMA, S "SW unpredicted"
This fault condition should never occur (or is not yet
supported).
2 2 PMA, S "Reset"
There has been a unit reset (detected always after the
power-up of the unit).
16 69 PMA "Reading extended backup settings"
The unit is reading its extended backup settings from the ext.
back-up unit. Do not interrupt.
20 5 PMA "Flash check sum error"
The calculated check sum does not match the stored one.
21 5 PMA, S "Missing Settings"
One of the setting structures has been corrupted in the
non-volatile memory.
24 223 MEI "Temperature too high"
The temperature of the unit exceeds its limit.
31 39 PMA, S "Node clock missing"
16.896 MHz node clock missing.
39 72 PMA "Extended backup unit fault"
The extended backup unit is not responding. Probably it is
missing or it is not in the inventory.
40 58 MEI "Faults masked"
The fault is activated when the interface fault mask setting is
on.
45 5 PMA, S "Checksum error in downloaded code"
The downloaded software has been corrupted.
47 69 PMA "Setup data mismatch"
A difference detected between non-volatile settings of two
GMX2 units.
49 108 PMA, S "LOS"
Loss of signal. A loss of signal defect is declared when a
supervised signal has not had any transitions for a period
of time or the signal indicating degradation of level in the
received signal is activated.
52 106 PMA, S "LOF"
Loss of frame.
53 73 PMA, S "SSF"
Server signal fail.
54 113 PMA, S "TIM"
Trace identifier mismatch.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

113
24 GMX2

SPT GPT Status SPT Description


55 103 DMA "DEGraded errors"
Signal degrade.
Once every second, block errors shall be compared with the
limit value. If the error count ≥ limit, the one second shall be
declared BAD, otherwise it shall be declared GOOD.
The Signal Degrade defect (dDEG) shall be detected if M
consecutive BAD seconds have occurred.
The Signal Degrade defect (dDEG) shall be cleared if M
consecutive GOOD seconds have occurred.
The value of M ranges 2..9.
56 111 MEI "RDI"
Remote defect indicator.
57 114 DMA "UNAVAIL"
Performance monitoring is in an unavailable state (G.774.01).
58 49 DMA "QOS"
Quality of signal. A 24-hour period.
At least one of the SES, BBE or ES limits exceeded. Cleared
when the period changes.
59 49 DMA "QOSTR"
Quality of signal. A 15-minute period.
At least one of the ES, BBE , SES limits has been exceeded.
Cleared when found a period where none of the ES, BBE or
SES limits has been exceeded.
Note that ES and BBE have upper/lower limit so that the
upper must be exceeded to get a fault and the lower is used as
a limit when the fault is activated.
65 27 MEI, S "VC12 loop"
A VC12 loop is active.
66 73 DMA "SSF (working) "
The protected channel has a serious fault (MS 1+1 or SNC
protection).
67 101 PMA, S "AIS"
Alarm indication signal.
69 107 PMA, S "LOP"
Loss of pointer.
71 109 PMA, S "SLM"
Path signal label mismatch.
72 109 PMA, S "UNEQ"
The received signal label is in the UNEQ state.
73 25 PMA, S "Loss of H4 multiframe"
Loss of multiframe alignment.
The multiframe indication byte H4 is interpreted according to
the ITU G.783 recommendations.
76 77 DMA "Failure of APS protocol"
Failure of protocol when using MS 1+1 protection:
• The protection switching time is not within 50 ms.
• The request is active, but no answer has been received
from the far end.
• One end is in 1+1 mode and the other in 1:1.
84 36 PMA, S "Start permission denied"
Most likely the unit does not belong to the node configuration.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

114
24 GMX2

SPT GPT Status SPT Description


102 73 DMA "SSF (protecting) "
The protecting channel has a serious fault (MS 1+1 or SNC
protection).
103 74 PMA, S "Group Failed"
Both working and protecting channels failed when using the
MS 1+1 or SNC protection.
104 103 DMA "Group degraded"
Block errors read from an MS 1+1 protected TTP or
connection protection group.
106 21 MEI, S "CAS multiframe RDI"
TS16 bit 6 alarm.
107 101 MEI, S "MAIS"
AIS in TS16 Multiframe.
108 25 PMA, S "MLOF"
Loss of Multiframe in TS16.
109 69 PMA "Settings corrupted"
Fatal set-up corruption. The unit must be configured again,
or it must be replaced with a slot where a compatible unit is
registered; the unit inherits settings.
110 72 PMA "No extended backup unit address"
The control unit returns no address of the extended backup
unit.
The capacity of the extended backup unit may have run out.
130 5 PMA, S "Flash list check sum error"
One of the flash lists (e.g. port descriptor list) has been
corrupted.
139 5 MEI "X-connect flash list conflict"
A corrupted cross-connect record has been detected in the
non-volatile memory after the unit reset. The record has been
deleted.
140 5 MEI "PortDesc flash list conflict"
A corrupted port descriptor record has been detected in the
non-volatile memory after the unit reset. The record has been
deleted.
141 5 MEI "Swapped trunk flash list conflict"
A corrupted swap-trunk record has been detected in the
non-volatile memory after the unit reset. The record has been
deleted.
142 5 MEI "Passivated trunk flash list conflict"
A corrupted passivate-trunk record has been detected in the
non-volatile memory after the unit reset. The record has been
deleted.
143 61 PMA "Reconfiguring X-connect database"
The background protection process of the passive GMX2
has detected that the cross-connect configuration is different
in the active and passive sides. The passive GMX2 is
reconfiguring itself.
151 28 MEI, PMA, "Unit IA fault"
S The GMX2 test of X-bus interface unit #N failed.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

115
24 GMX2

SPT GPT Status SPT Description


158 91 MEI ”Performance event”
At least one of the performance event counters differs from
zero during the last 15-minute period.
160 69 PMA "Reading backup from peer unit"
The unit is reading parameter back-ups from the peer unit.
161 69 PMA "Peer backup unit fault"
Parameter copying from the peer unit failed.
162 33 PMA,S "X-Connect bus alarm"
Error detected on the cross-connection bus.
163 24 DMA "Inter cross-connection unit bus fault"
Error detected on the bus connecting cross-connection units.
164 34 MEI "Fallback list warning"
More than one entry added to the fallback list, but only one
entry can be used. This warning is blocked if quality levels
are enabled.
165 34 DMA "Loss of timing input"
All references in the fallback list are lost, an internal holdover
clock is used.
166 34 MEI "Forced clock selection"
The clock selection is forced with an external command.
167 34 DMA "Excessive frequency offset fallback list entry 1"
Frequency of the reference clock is out of the PLL locking
range.
168 34 DMA "Excessive frequency offset fallback list entry 2"
Frequency of the reference clock is out of the PLL locking
range.
169 34 DMA "Excessive frequency offset fallback list entry 3"
Frequency of the reference clock is out of the PLL locking
range.
170 34 DMA "Excessive frequency offset fallback list entry 4"
Frequency of the reference clock is out of the PLL locking
range.
171 34 DMA "Excessive frequency offset fallback list entry 5"
Frequency of the reference clock is out of the PLL locking
range.
172 34 DMA "Excessive frequency offset fallback list entry 6"
Frequency of the reference clock is out of the PLL locking
range.
173 34 DMA "Excessive frequency offset fallback list entry 7"
Frequency of the reference clock is out of the PLL locking
range.
174 34 DMA "Excessive frequency offset fallback list entry 8"
Frequency of the reference clock is out of the PLL locking
range.
175 34 DMA "Excessive frequency offset fallback list entry 9"
Frequency of the reference clock is out of the PLL locking
range.
176 34 DMA "Excessive frequency offset fallback list entry 10"
Frequency of the reference clock is out of the PLL locking
range.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

116
24 GMX2

SPT GPT Status SPT Description


187 34 MEI "Fallback list 2nd priority used"
The second priority reference has been selected.
188 34 MEI "Fallback list 3rd priority used"
The third priority reference has been selected.
189 34 MEI "Fallback list 4th priority used"
The fourth priority reference has been selected.
190 34 MEI "Fallback list 5th priority used"
The fifth priority reference has been selected.
191 34 MEI "Fallback list 6th priority used"
The sixth priority reference has been selected.
192 34 MEI "Fallback list 7th priority used"
The seventh priority reference has been selected.
193 34 MEI "Fallback list 8th priority used"
The eighth priority reference has been selected.
194 34 MEI "Fallback list 9th priority used"
The ninth priority reference has been selected.
195 34 MEI "Fallback list 10th priority used"
The tenth priority reference has been selected.
196 34 PMA,S "SEC is not functioning"
The SEC hardware is not functioning correctly.
197 34 PMA,S "Framer Master Clock is Missing"
The master clock of framer is not functioning correctly.
198 34 PMA,S "78MHz is Missing"
78MHz oscillator is not functioning correctly.
199 34 PMA,S "SEC is missing auxiliary frequency"
The base board is not feeding auxiliary frequency to SEC.
200 34 DMA "Station clock input Loss of Signal"
The external clock has been enabled, but the signal is missing.
201 34 DMA "Station clock input Loss of Frame"
The external clock has been enabled, but frame
synchronization has failed.

202 34 DMA "Station clock input AIS"


Alarm indication signal.
203 3 PMA,S "Initialization error"
The unit failed to initialize properly.
206 27 MEI,S "Equipment loop"
The signal transmitted out is also looped back to the receiver
of the interface.
207 10 MEI "Unexpected SFP module type"
The SFP tranceiver module type does not match with the
expected type.
208 27 MEI,S "VC-4 loop"
The signal received by the VC-4 sink is looped back to the
source.
209 113 MEI "MRDI"
Multiframe remote defect indication.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

117
24 GMX2

SPT GPT Status SPT Description


211 69 PMA,S “Parameter inconsistency with peer unit (resetting)”
The unit has copied parameters from the peer unit and need
to reset in order to take the parameters into use.
212 223 DMA, S “Operation degraded due to too high temperature (resetting)”
Some of the unit operations are disabled to cool the unit. The
unit will reset after the cooling period.
213 101 MEI, S “AIS from 1/0 direction”
TS0/B2 from XBUS = ’1’ (represents nx64 kbps signal).

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

118
25 ISD-NT, ISD-LT

25 ISD-NT, ISD-LT
SPT GPT Status SPT Description
1 1 PMA "SW unpredicted"
This fault condition should never occur (or is not yet
supported).
2 2 PMA, S "Reset"
There has been a unit reset (detected always after the
power-up of the unit).
3 4 PMA "Power +5 V (subrack)"
The voltage is below the threshold limit
(about 4.6 V depending on the calibration and the A/D
resolution).
4 4 PMA "Power +5 V"
The voltage is below the threshold limit
(about 4.6 V depending on the calibration and the A/D
resolution).
5 4 PMA "Power +12 V"
The voltage is below the threshold limit
(about 11.3 V depending on the calibration and the A/D
resolution).
6 4 PMA "Power -10 V"
The voltage is above the threshold limit
(about -9.0 V depending on the calibration and the A/D
resolution).
7 38 PMA, S "Bus sync. fault"
The fault is activated if the X-bus synchronization pulse
transmitted by SXU is missing. A possible reason for this
fault is that SXU is missing.
8 36 PMA, S "Start permission denied"
Most likely the unit does not belong to the node configuration.
9 55 PMA "SW in flash incompatible with ROM"
There is downloaded software in the flash but the revision is
wrong (for example if EPROM SW is r5.5 and downloaded
SW is r6.1).
10 55 PMA, S "Chksum error in downloaded software"
The downloaded software has been corrupted.
11 5 PMA, S "RAM fault"
A background process has detected a RAM location where
the read value does not match the written test pattern.
12 5 PMA, S "EPROM fault"
The calculated check sum does not match the stored one.
13 5 PMA, S "Flash write error"
Error when writing to the flash memory (main bank).
14 5 PMA, S "Flash copy error"
Error when writing to the flash memory (shadow bank).

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

119
25 ISD-NT, ISD-LT

SPT GPT Status SPT Description


15 5 PMA, S "Flash erase error"
Error during the erase of the flash memory (shadow bank).
16 5 PMA, S "Flash duplicate error"
Duplicated parameters (the same ID) detected during the
start-up.
17 5 PMA, S "Flash shadow error"
The shadow bank of the flash is not erased during the start-up.
18 5 PMA, S "Flash check sum error"
The calculated check sum does not match the stored one.
19 3 PMA, S "Setup error"
One of the setting structures has been corrupted in the
non-volatile memory.
20 1 PMA "Software error"
Software has noted an inconsistency in its own logic.
22 10 PMA, S "Missing module 1"
The interface module defined in the settings is missing.
23 10 PMA, S "Missing module 2"
The interface module defined in the settings is missing.
24 10 PMA, S "Conflict in module type 1"
There is a conflict between the installed module and the
settings.
25 10 PMA, S "Conflict in module type 2"
There is a conflict between the installed module and the
settings.
26 27 MEI, S "Unit test loop on"
Local loop or test activated (by the manager).
27 29 PMA, S "No response to NNM message"
The control channel of the interface is used and the neighbor
node supervision option of the interface is on and no NNM
(Neighbor Node Monitoring) message has been received
from the interface within a specified period.
28 29 PMA, S "Own NNM messages received"
The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received
NNM message contains the same identification data as the
NNM message sent to the interface.
29 29 PMA, S "Unexpected NNM message"
The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received
NNM message contains unexpected neighbor identification
data.
30 32 PMA, S, R "ASIC fault in base unit"
Difference between write/read configuration data of CIF asic
has been detected.
31 32 PMA, S "Fault in Xilinx 1"
Difference between write/read configuration data of Xilinx
has been detected.
32 32 PMA, S "Fault in Xilinx 2"
Difference between write/read configuration data of Xilinx
has been detected.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

120
25 ISD-NT, ISD-LT

SPT GPT Status SPT Description


33 40 PMA, S "IA activity missing"
The interface address is not activated on the cross-connection
bus by SXU.
62 "HW fault in base unit"
Hardware does not work as expected.
62 "HW strapping conflict with SW"
The strapping info of the base unit PCB is not what the
software expects. Maybe the software is installed in a wrong
unit.
62 "HW fault in module 1"
Hardware does not work as expected.
62 "HW fault in module 2"
Hardware does not work as expected.
62 "Setup conflict"
Information stored to the setup is self-contradictory.
39 12 PMA, S "Loss of input signal"
Signal missing in the Rx direction.
41 13 DMA "Bit error rate 10E-3"
Bit error rate estimated to exceed 10E-3.
42 22 DMA "CRC errors from far-end"
CRC errors detected at the far-end.
48 30 DMA "Input buffer slip"
Either data buffer overflow/underflow or phase jump in
timing of internal serial bus in the unit.
51 48 PMA, S "G821 unavailable state"
The fault is activated if the G.821 supervision is used and
the state of the signal becomes unavailable (10 consecutive
SES seconds). The fault is deactivated when 10 consecutive
seconds not classified as SES have been found.
53 57 PMA, S "NTU power fault"
NTU has lost its power supply; possibly it is switched off.
54 58 MEI "Fault masks"
The fault is activated when the interface Fault mask setting
is on
(all interface faults are cleared).
55 60 DMA "Performance event"
This fault is activated as a delta fault if the G.821 supervision
is used and at least one performance limit (SES, ES, RAI
second, CRCE) has been exceeded in a 15-minute period.
57 56 PMA "Activation failure"
The standardized activation procedure of the U interface with
the remote device has not succeeded.
58 57 MEI "U interface power fault"
NT1 has lost power supply in the U interface.
59 24 PMA, S "Out of frame"
See CCITT G.706 Loss of frame alignment.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

121
25 ISD-NT, ISD-LT

SPT GPT Status SPT Description


60 112 DMA,(S) "Excessive errors"
Once every second block errors shall be compared with limit
value. If errors count ≥ limit, the one second shall be declared
BAD, otherwise it shall be declared GOOD.
The Excessive errors shall be detected if M consecutive BAD
seconds have occurred.
The Excessive errors shall be cleared if M consecutive
GOOD seconds have occurred.
M value range 2..9.
61 103 DMS,(S) "Degraded errors"
Once every second block errors shall be compared with limit
value. If errors count ≥ limit, the one second shall be declared
BAD, otherwise it shall be declared GOOD.
The Degraded errors shall be detected if M consecutive BAD
seconds have occurred.
The Degraded errors shall be cleared if M consecutive
GOOD seconds have occurred.
M value range 2..9.
62 164 MEI "Loss of synchr. in S-interface"
NT1 and TE are not in synchronization. Possibly power is
off in TE.
63 59 MEI, S "SSP mode active"
Send Single Pulse mode active
64 57 PMA, S "NTU remote power fault"
No power feeding from the ISD unit (probably too low
voltage setting in ISD or missing cable).

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

122
26 ISD-LT16

26 ISD-LT16
SPT GPT Status SPT Description
1 1 PMA "Unpredicted fault condition"
This fault condition should never occur (or is not yet
supported).
2 2 PMA, S "Reset"
There has been a unit reset (detected always after the
power-up of the unit).
3 4 PMA "Power supply +5 V (subrack)"
The voltage is below the threshold limit
(about 4.6 V depending on the calibration and the A/D
resolution).
4 4 PMA "Power supply +5 V (Unit)"
The voltage is below the threshold limit
(about 4.6 V depending on the calibration and the A/D
resolution).
5 4 PMA "Power supply +12 V"
The voltage is below the threshold limit
(about 11.3 V depending on the calibration and the A/D
resolution).
6 4 PMA "Power supply -10 V"
The voltage is above the threshold limit
(about -9.0 V depending on the calibration and the A/D
resolution).
7 38 PMA, S "Bus sync fault"
No 8100 system bus synchronization from SXU detected.
8 36 PMA, S "Start permission denied by SXU-V"
Most likely the unit does not belong to the node configuration.
9 55 PMA, S "Missing or incompatible application program"
There is no downloaded software in flash or the revision is
wrong.
10 55 PMA, S "Checksum error in downloaded SW"
The downloaded software has been corrupted.
11 5 PMA, S "RAM fault"
A background process has detected a RAM location where
the read value does not match the written test pattern.
12 5 PMA, S "PROM fault"
The calculated check sum does not match with the stored one.
13 5 PMA, S "Flash write error"
Error when writing to the flash memory (main bank).
14 5 PMA, S "Flash copy error"
Error when writing to the flash memory (shadow bank).
15 5 PMA, S "Flash erase error"
Error during the erase of the flash memory (shadow bank).

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

123
26 ISD-LT16

SPT GPT Status SPT Description


16 5 PMA, S "Flash duplicate error"
Duplicated parameters (the same ID) detected during the
start-up.
17 5 PMA, S "Flash shadow error"
The shadow bank of the flash is not erased during the start-up.
18 5 PMA, S "Flash check sum error"
The calculated check sum does not match the stored one.
19 3 PMA, S "Setup structure corrupted"
One of the setting structures has been corrupted in the
non-volatile memory.
20 1 PMA "Software error"
Software has noted an inconsistency in its own logic.
21 4 PMA "Power supply +3.3 V"
The voltage is below the threshold limit (the limit depends on
the calibration and the A/D resolution).
22 10 PMA, S "Missing module 1"
The interface module defined in the settings is missing.
23 10 PMA, S "Missing module 2"
The interface module defined in the settings is missing.
24 10 PMA, S "Conflict in module type 1"
There is a conflict between the installed module and the
settings.
25 10 PMA, S "Conflict in module type 2"
There is a conflict between the installed module and the
settings.
26 27 MEI, S "Interface loop to net"
An interface loop is created in the interface module. It loops
transmitted data back to the interface receiver.
27 29 PMA, S "No response to NNM message"
The control channel of the interface is used and the neighbor
node supervision option of the interface is on and no NNM
(Neighbor Node Monitoring) message has been received
from the interface within a specified period.
28 29 PMA, S "Own NNM messages received"
The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received
NNM message contains the same identification data as the
NNM message sent to the interface.
29 29 PMA, S "Unexpected NNM message"
The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received
NNM message contains unexpected neighbor identification
data.
30 32 PMA, S, R "ASIC fault in base unit"
The fault is activated if difference between write/read
configuration data of ASIC has been detected.
31 32 PMA, S "Fault in Xilinx 1"
Difference between write/read configuration data of Xilinx
has been detected.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

124
26 ISD-LT16

SPT GPT Status SPT Description


32 32 PMA, S "Fault in Xilinx 2"
Difference between write/read configuration data of Xilinx
has been detected.
33 40 PMA, S "IA activity missing"
The interface address is not activated on the cross-connection
bus by SXU.
34 62 PMA, S "HW fault in base unit"
Base unit hardware does not work as expected.
35 62 MEI "HW strapping conflict with SW"
The strapping info of the base unit PCB is not what the
software expects. Maybe the software is installed on a wrong
unit.
36 62 PMA, S "HW fault in module 1"
Module hardware does not work as expected.
37 62 PMA, S "HW fault in module 2"
Module hardware does not work as expected.
38 62 DMA "Setup conflict"
Information stored to the setup is self-contradictory.
39 12 PMA, S "Loss of input signal"
Loss of input signal.
40 4 PMA "Temperature high"
If temperature is above the limit, 90 C, the unit will set the
Red LED and will drop the remote power feeding to zero
in every U-interface line. When temperature is decreased
below 85 C, the unit will set remote power feeding back to
U-interface lines.
41 13 DMA "Bit error rate"
BER more than 10E-3.
42 22 DMA "CRC error from far end"
CRC errors from far-end.
48 30 DMA "Input Buffer Slip"
Input Buffer Slip.
51 48 PMA, S "Unavailable state by G.821"
The fault is activated if the G.821 supervision is used and
the state of the signal becomes unavailable (10 consecutive
SES seconds). The fault is deactivated when 10 consecutive
seconds not classified as SES have been found.
53 57 PMA, S "NTU power fault"
NTU power fault.
54 58 MEI "Fault masks"
The fault is activated when interface fault mask setting is on
(all interface faults are cleared).
55 60 DMA "Performance event"
This fault is activated as a delta fault if the G.821 supervision
is used and at least one performance limit (SES, ES, RAI
second, CRCE) has been exceeded during a 15-minute period.
57 56 PMA "Activation failure"
U-Interface activation failure.
58 57 MEI "U-IF short circuit power fault"
U-interface short circuit power fault

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

125
26 ISD-LT16

SPT GPT Status SPT Description


59 24 PMA, S "Out of Frame"
Out of Frame
60 112 DMA,(S) "Excessive errors"
Once every second block errors shall be compared with limit
value. If errors count ≥ limit, the one second shall be declared
BAD, otherwise it shall be declared GOOD.
The Excessive errors shall be detected if M consecutive BAD
seconds have occurred.
The Excessive errors shall be cleared if M consecutive
GOOD seconds have occurred.
M value range 2..9.
61 103 DMS,(S) "Degraded errors"
Once every second block errors shall be compared with limit
value. If errors count ≥ limit, the one second shall be declared
BAD, otherwise it shall be declared GOOD.
The Degraded errors shall be detected if M consecutive BAD
seconds have occurred.
The Degraded errors shall be cleared if M consecutive
GOOD seconds have occurred.
M value range 2..9.
62 164 MEI "Loss of synchr. in S-interface"
NT1 and TE are not in synchronization. Possibly power is
off in TE.
63 59 MEI, S "SSP/DT mode active"
SSP/DT mode is active.
64 57 PMA, S "NTU remote power fault"
No power feeding from the ISD unit (probably too low
voltage setting in ISD or a cable is missing).
71 114 DMA "G.826 not available"
G.826 is not supported
72 49 PMA "QOS 24 hours period"
Quality of service. Quality of signal in a 24-hour period.
At least one of the BBE, ES or SES limits has been exceeded.
Cleared when the period changes.
73 49 PMA "QOS 15 minutes period"
Quality of service, threshold reset. Quality of signal in a
15-minute period.
At least one of the upper BBE, ES or SES limits has been
exceeded. Cleared when found a period where the lower
BBE, ES or SES limits has not been exceeded.
74 91 MEI "Performance event for G.826"
At least one of the performance event counters differs from
zero during the last 15-minute period.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

126
27 IUM-5T, IUM-10T, IUM-8

27 IUM-5T, IUM-10T, IUM-8


SPT GPT Status SPT Description
1 1 PMA "SW unpredicted"
This fault condition should never occur (or is not yet
supported).
2 2 PMA, S "Reset"
There has been a unit reset (detected always after the
power-up of the unit).
3 4 PMA "Power +5 V (subrack)"
The voltage is below the threshold limit
(about 4.6 V depending on the calibration and the A/D
resolution).
4 4 PMA "Power +5 V"
The voltage is below the threshold limit
(about 4.6 V depending on the calibration and the A/D
resolution).
5 4 PMA "Power +12 V"
The voltage is below the threshold limit
(about 11.3 V depending on the calibration and the A/D
resolution).
6 4 PMA "Power -10 V"
The voltage is above the threshold limit
(about -9.0 V depending on the calibration and the A/D
resolution).
7 38 PMA, S "Bus sync. fault"
The fault is activated if the X-bus synchronization pulse
transmitted by SXU is missing. A possible reason for this
fault is that SXU is missing.
8 36 PMA, S "Start request denied"
Most likely the unit does not belong to the node configuration.
9 55 PMA, S "Incompatible EPROM/FLASH SW"
The fault is activated if there is downloaded software in the
flash but the revision is wrong (for example if EPROM SW is
r5.5 and downloaded SW is r6.1).
10 55 PMA, S "Chksum err in downloaded SW"
The downloaded software has been corrupted.
11 5 PMA, S "RAM fault"
A background process has detected a RAM location where
the read value does not match the written test pattern.
12 5 PMA, S "EPROM fault"
The calculated check sum does not match the stored one.
13 5 PMA, S "Flash write error"
Error when writing to the flash memory (main bank).
14 5 PMA, S "Flash copy error"
Error when writing to the flash memory (shadow bank).

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

127
27 IUM-5T, IUM-10T, IUM-8

SPT GPT Status SPT Description


15 5 PMA, S "Flash erase error"
Error during the erase of the flash memory (shadow bank).
16 5 PMA, S "Flash duplicate error"
Duplicated parameters (the same ID) detected during the
start-up.
17 5 PMA, S "Flash shadow error"
The shadow bank of the flash is not erased during the start-up.
18 5 PMA, S "Flash check sum error"
The calculated check sum does not match the stored one.
19 3 PMA, S "Setup error"
One of the setting structures has been corrupted in the
non-volatile memory.
20 1 PMA "Software error"
Software has noted an inconsistency in its own logic.
22 10 PMA, S "IF 1 module missing"
The interface module defined in the settings is missing.
23 10 PMA, S "IF 2 module missing"2
The interface module defined in the settings is missing.
24 10 PMA, S "Wrong interface module 1"
There is a conflict between the installed module and the
settings.
25 10 PMA, S "Wrong interface module 2"2
There is a conflict between the installed module and the
settings.
26 27 MEI, S "Local loop or test active"
Local loop or test activated (by 8100 manager).
27 29 PMA, S "No response to NNM message"
The control channel of the interface is used and the neighbor
node supervision option of the interface is on and no NNM
(Neighbor Node Monitoring) message has been received
from the interface within a specified period.
28 29 PMA, S "Own NNM messages received"
The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received
NNM message contains the same identification data as the
NNM message sent to the interface.
29 29 PMA, S "Wrong ID’s in NNM message"
The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received
NNM message contains unexpected neighbor identification
data.
30 32 PMA, S "ASIC register error (base unit)"
The fault is activated if the difference between write/read
configuration data of ASIC has been detected.
31 32 PMA, S "ASIC register error (IF module 1)" 2
The fault is activated if the difference between write/read
configuration data of ASIC has been detected.

2This fault applies only to IUM-5T and IUM-10T.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

128
27 IUM-5T, IUM-10T, IUM-8

SPT GPT Status SPT Description


32 32 PMA, S "ASIC register error (IF module 2)" 2
The fault is activated if the difference between write/read
configuration data of ASIC has been detected.
33 40 PMA, S "IA activity missing"
The interface address is not activated on the cross-connection
bus by SXU.
34 62 PMA, S "HW fault (base unit)"
Hardware does not work as expected.
35 62 MEI "Strapping conflict"
The strapping info of the base unit PCB is not what the
software expects. Maybe the software is installed in a wrong
unit.
36 62 PMA, S "HW fault (IF module 1)"
Hardware does not work as expected.
37 62 PMA, S "HW fault (IF module 2)" 2
Hardware does not work as expected.
38 69 DMA "Setup conflict"
Information stored to the setup is self-contradictory.
39 12 PMA, S "Loss of input signal"
Signal missing in the Rx direction.
41 13 DMA "BER10E-3"
Bit error rate estimated to exceed 10E-3. The bit error rate is
calculated from the U interface multiframe CRC.
42 22 DMA "CRC errors from far-end"
CRC errors detected at the far-end.
46 27 MEI, S "Local loop or test active"
Local loop or test activated (by the manager).
48 30 DMA "Input buffer slip"
Either data buffer overflow/underflow or phase jump in
timing of internal serial bus in the unit.
51 48 PMA, S "G821 unavailable state"
The fault is activated if the G.821 supervision is used and
the state of the signal becomes unavailable (10 consecutive
SES seconds). The fault is deactivated when 10 consecutive
seconds not classified as SES have been found.
53 57 PMA, S "NTU power fault"
NTU has lost its power supply; possibly it is switched off.
54 58 MEI "Faults masked/test"
The fault is activated when the interface Fault mask setting
is on
(all interface faults are cleared).
55 60 DMA "G821 limit event"
This fault is activated as a delta fault if the G.821 supervision
is used and at least one performance limit (SES, ES, RAI
second, CRCE) has been exceeded in a 15-minute period.
57 56 PMA "Activation failure"
The standardized activation procedure of the U interface with
the remote device has not succeeded.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

129
27 IUM-5T, IUM-10T, IUM-8

SPT GPT Status SPT Description


58 72 PMA "NTU backup failed"
Plug and Play operations towards NTU failed. NTU behind
the interface is not backed up. Check NNM settings both
in IUM and NTU (message sending and supervision must
be enabled).
59 72 PMA "Extended backup unit fault"
No answer or error message from the extended backup unit
(it may be missing, not in inventory or - if SCU or XCG - run
out of backup space).
60 72 PMA "No extended backup unit address"
Part of the start-up sequence IUM unit asks from SCU the
address of the extended backup unit. There is no answer
to that request, or returned address is faulty. One possible
reason is that backup unit(s) - if SCU or XCG - is run out
of backup space.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

130
28 LIU

28 LIU
SPT GPT Status SPT Description
1 1 PMA, S "SW unpredicted"
This fault condition should never occur (or is not yet
supported).
2 2 PMA, S "Reset"
There has been a unit reset (detected always after the
power-up of the unit).
3 3 PMA, S "Set-up structure corrupted"
One of the setting structures has been corrupted in the
non-volatile memory.
4 4 PMA "Power +5 V (subrack)"
The voltage is below the threshold limit.
5 4 PMA "Power +5 V (unit)"
The voltage is below the threshold limit.
6 4 PMA "Power +12 V (unit)"
The voltage is below the threshold limit.
7 4 PMA "Power –10 (unit)V"
The voltage is above the threshold limit.
8 5 PMA, S "RAM Fault(Ubz543)"
A background process has detected a RAM location where
the read value does not match the written test pattern.
9 5 PMA, S "NMS Path Server unreachable"
The DXX Server was queried in order to get a control path
for the LIU configuration communication. There was not
yet path to the DXX Server or the DXX Server that was
queried did not answer, because it was down, unreachable or
overloaded at that particular time.
11 5 PMA "Flash write error(Ubz543)"
Error when writing to the flash memory (main bank).
12 5 PMA "Flash copy error(Ubz543)"
Error when writing to the flash memory (shadow bank).
13 5 PMA "Flash erase error(Ubz543)"
Error during the erase of the flash memory (shadow bank).
14 5 PMA "Flash duplicate error(Ubz543)"
Duplicated parameters (the same ID) detected during the
start-up.
15 5 PMA "Flash shadow error(Ubz543)"
The shadow bank of the flash is not erased during the start-up.
16 5 PMA, S "Flash check sum error(Ubz543)"
The calculated check sum does not match the stored one.
17 5 PMA, S "Missing settings (Ubz543)"
One of the setting structures has been corrupted in the
non-volatile memory.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

131
28 LIU

SPT GPT Status SPT Description


18 10 PMA, S "Missing router module"
The LIU unit is unable to find its internal IP routing module.
19 10 PMA, S "Conflict in module type"
The defined module type in the settings does not match the
actual module type in the hardware.
26 36 PMA, S "Start permission denied"
Most likely the unit does not belong to the node configuration.
27 38 PMA, S "Bus sync fault"
The fault is activated if the X-bus synchronization pulse
transmitted by SXU is missing. A typical reason for this fault
is that SXU is missing.
28 40 PMA, S "Missing IA activity"
The fault is activated if the unit cannot find its locked
interface address on the cross-connection bus. SXU should
activate IA on the bus if the interface is locked.
29 55 PMA "Incompatible EPROM/FLASH SW"
The fault is activated if there is downloaded software in the
flash but the revision is wrong.
30 55 PMA, S "Checksum error in downloaded SW"
The downloaded SW is corrupted.
31 58 MEI "Faults masked"
The fault is activated when the interface Fault mask setting
is on
(all interface faults are cleared).
36 72 PMA "Backup unit (SCP) fault"
Error generated by the backup unit.
40 2 PMA, S "ERH580/581 reset"
The internal routing module of LIU is currently resetting
itself and unable to receive commands.
49 1 PMA, S "WAN-link configuration error"
The parameters for the datalink between the LIU interfaces
and the internal router have not been set.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

132
29 NTU-2M

29 NTU-2M
SPT GPT Status SPT Description
1 1 PMA, S "SW unpredicted"
This fault condition should never occur (or is not yet
supported).
2 2 PMA, S "Reset"
There has been a unit reset (detected always after the
power-up of the unit).
3 3 PMA, S "Setup error"
One of the setting structures has been corrupted in the
non-volatile memory.
4 4 PMA "Power +5V (Vcc)"
The voltage is below the threshold limit.
5 4 PMA "Power +12V"
The voltage is below the threshold limit.
6 4 PMA "Power -5V"
The voltage is above the threshold limit.
7 4 PMA "Power -10V"
The voltage is above the threshold limit.
8 5 PMA, S "RAM fault"
A background process has detected a RAM location where
the read value does not match the written test pattern.
9 5 PMA, S "EPROM fault"
The calculated checksum does not match the stored one.
10 5 PMA "Flash write error"
Error when writing to the flash memory (main bank).
11 5 PMA "Flash copy error"
Error when writing to the flash memory (shadow bank).
12 5 PMA "Flash erase error"
Error during the erase of the flash memory (shadow bank).
13 5 PMA "Flash duplicate error"
Duplicated parameters (the same ID) detected during the
start-up.
14 5 PMA "Flash shadow error"
The shadow bank of the flash is not erased during the start-up.
15 5 PMA, S "Flash check sum error"
The calculated check sum does not match the stored one.
16 55 PMA, S "Incompatible EPROM/FLASH SW"
The downloaded software (in the flash) is not compatible
with the system software in EPROM.
17 55 PMA, S "Checksum error in downloaded SW"
The downloaded software has been corrupted.
19 12 PMA, S "Missing line signal"
No signal on the line.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

133
29 NTU-2M

SPT GPT Status SPT Description


21 51 MEI "Line rate scanning"
NTU is searching the right line rate.
22 52 MEI "DTE rate scanning "
NTU is searching the right DTE rate (113 signal).
23 23 MEI, S "AIS in input signal"
Signal from the line is AIS (”1”).
24 58 MEI "Fault mask on"
Faults are masked.
27 27 MEI, S "Digital loop"
V.54 loop 2. NTU loops received data back to the line. Loop
is activated by NTU’s keys.
31 59 MEI, S "Transmit & Receive test"
V.52 compliant 511-bit pattern is transmitted and errors in
the receiver are counted.
33 20 MEI "Frame far-end alarm"
Frame is lost at the far-end. ( Rx signal missing, Rx signal is
AIS, loss of frame alignment, BER 10-3 or degraded signal.)
34 29 PMA, S "Wrong neighbor"
The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received
NNM message contains unexpected neighbor identification
data.
35 29 PMA, S "No response to NNM msg"
The control channel of the interface is used and the neighbor
supervision option of the interface is on and no NNM
(Neighbor Node Monitoring) message has been received
from the interface within 8 seconds.
36 29 PMA, S "Own NNM msg received"
The control channel of the interface is used and the neighbor
supervision option of the interface is on and received NNM
message contains same identification data as the NNM
message sent to the interface.
37 26 DMA "CRC missing"
Frame alignment word is detected but the CRC multiframe
is not.
38 26 PMA, S "Frame align. lost by CRC"
See G.706 Frame alignment recovery.
39 24 PMA, S "Frame alignment lost"
See G.706 Loss of frame alignment.
40 13 PMA, S "BER more than 10-3"
Bit error rate is more than 10E-3. Bit error rate is calculated
from frame alignment words.
41 60 DMA "G.821 limit event"
This fault is activated as a delta fault if the G.821 supervision
is used and at least one performance limit has been exceeded
in a 15-minute period.
42 48 PMA, S "G.821 unavailable state"
The fault is activated if the G.821 supervision is used and the
state of signal becomes unavailable (10 consecutive SES
seconds). The fault is deactivated when 10 consecutive
seconds not classified as SES have been found.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

134
29 NTU-2M

SPT GPT Status SPT Description


43 3 PMA, S "Door Open"
The installation unit door of NTU-2M is open.
44 12 PMA, S "Rx signal missing"
No signal in the 2M G.703 interface.
45 30 DMA "DTE out of sync"
DTE clock is unusable (Frequency difference between DTE
transmit and receive directions more than about 50 ppm)
46 16 DMA "BER 10E-6"
Error rate is worse than 10-6. The bit error rate is calculated
from crc and/or code errors.
47 30 DMA "Frequency difference"
DTE transmit and receive directions are not frequency
locked.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

135
30 NTU-A

30 NTU-A
SPT GPT Status SPT Description
1 1 PMA, S "SW unpredicted"
This fault condition should never occur (or is not yet
supported).
2 2 PMA, S "Reset"
Processor reset caused by watchdog or power-off-situation.
3 4 PMA, S "Power fault"
One of the supervised voltage levels is not acceptable.
4 39 PMA, S "Clock fault"
Processor or datapump oscillator frequency is wrong.
5 51 MEI "Line scanning"
NTU is searching the right line rate.
6 52 MEI "DTE scanning"
NTU is searching the right DTE rate (113 signal).
7 23 MEI, S "Rx signal AIS" 3
’1’ is received continuously.
8 49 PMA, S "Signal quality alarm"
There is a signal on line but it is not acceptable for the
receiver.
9 50 PMA, S "Rx signal missing"
No signal on the line.
10 5 PMA, S "RAM fault"
A background process has detected a RAM location where
the read value does not match the written test pattern.
11 5 PMA, S "EPROM fault"
The calculated check sum does not match the stored one.
12 5 PMA, S "EEPROM fault"
NTU parameters are stored twice in EEPROM; both blocks
are faulty.
13 5 DMA "EEPROM backup fault"
Backup block of NTU parameters is faulty.
14 5 PMA "EEPROM unique fault"
Some statistics info, serial number, HW version etc. are
stored only once in EEPROM. The block is faulty.
15 20 MEI "Frame far-end alarm"
Frame is lost at the far-end.
16 29 PMA, S "Wrong neighbor"
The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received
NNM message contains unexpected neighbor identification
data.

3SBM 384A (discontinued), SBM 768A (discontinued), RBM 384A, RBM 768A

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

136
30 NTU-A

SPT GPT Status SPT Description


17 29 PMA, S "No response to NNM message"
The control channel of the interface is used and the neighbor
node supervision option of the interface is on and no NNM
(Neighbor Node Monitoring) message has been received
from the interface within 8 seconds.
18 29 PMA, S "Own NNM message received"
The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received
NNM message contains the same identification data as the
NNM message sent to the interface.
19 26 DMA "CRC missing"3
Frame alignment word is detected but the CRC multiframe
is not.
20 13 PMA, S "BER10E-3"
Bit error rate is more than 10E-3. Bit error rate is calculated
from frame alignment words.
21 26 PMA, S "Frame alignment lost by CRC" 3
See G.706 Frame alignment recovery.
22 24 PMA, S "Frame alignment lost"
See G.706 Loss of frame alignment. Loss of frame
synchronization state in case of V.110 or X.30. 3
23 27 MEI, S "Local loop"
V.54 loop 3. NTU’s transmitter is connected to the receiver.
24 27 MEI, S "Digital loop"
V.54 loop 2. NTU loops received data back to the line. The
loop is activated by NTU’s keys.
25 27 MEI, S "Digital loop made by neighbor"
Same loop as above, but it is activated by the neighbor. The
neighbor unit uses management channel to give the loop
command.
26 27 MEI, S "Remote loop V.54"
V.54 loop 2 (digital loop) is formed in the remote unit.
27 27 MEI, S "DTE loop"
Loop in NTU’s DTE card.
28 27 MEI, S "Remote loop B V.54"
V.54 loop 2 (digital loop) activated by the remote unit.
29 59 MEI, S "Transmit & Receive test"
V.52 compliant 511-bit pattern is transmitted and errors in the
receiver are counted.
30 27 MEI, S "Remote controlled line loop"
Line loop in neighbor unit activated by NTU. NTU uses
management channel to give the loop command.
31 58 MEI, S "Fault mask on"
Faults are masked.
32 60 DMA "G.821 limit event"
This fault is activated as a delta fault if the G.821 supervision
is used and at least one performance limit has been exceeded
in a 15-minute period.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

137
30 NTU-A

SPT GPT Status SPT Description


33 48 PMA, S "G.821 unavailable state"
The fault is activated if the G.821 supervision is used and
the state of the signal becomes unavailable (10 consecutive
SES seconds). The fault is deactivated when 10 consecutive
seconds not classified as SES have been found.
34 56 MEI "NTU short circuit"
Receiver wetting current is too high.4
35 56 MEI "NTU line break"
Receiver wetting current is too low.4
36 57 MEI "NTU power off"
Receiver wetting current is changing at a frequency of about
2.5 Hz, which is an indication of a power-off-situation at
remote NTU. 4
37 67 PMA "FAS-errors"5
Frame synchronization word errors detected in case of V.110
or X.30.
38 25 PMA, S "Loss of multiframe sync"5
Loss of multiframe synchronization state in case of V.110
or X.30.
39 30 DMA "Tx buffer alignment"5
V.110 or X.30 buffer slip.
40 30 DMA "Rx buffer alignment"5
V.110 or X.30 buffer slip.
41 42 MEI, S "AIS detected from network"5
Signal from line is AIS.
42 67 PMA, S "Code errors from input"5
No input clock (NRZ).
43 26 DMA "CRC errors from near-end"5
CRC errors detected.
44 32 PMA, S "ASIC register err in V110"5
Error detected in the ASIC hardware.
55 5 PMA, S "RL state program error"5
Remote loop V.54 state machine in RAM is corrupted.

4RBM 384A, RBM 64A


5SBM 64A (discontinued), RBM 64A

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

138
31 OMH, OMH-A

31 OMH, OMH-A
SPT GPT Status SPT Description
1 1 PMA "SW Unpredicted"
This fault condition should never occur.
2 2 PMA "Reset"
There has been a unit reset (detected always after the
power-up of the unit). Note: this is a delta event, not an
active fault
3 11 PMA, S "Loss of protected signal"
In 1+1 protection mode both interfaces IF1 and IF2 have
faults which in unprotected mode have S status.
4 69 MEI "Reading extended backup settings"
The unit is reading its extended backup settings from the
extended backup unit. Do not interrupt.
5 69 PMA "Extended settings corrupted"
Fatal setup corruption. The unit must be reconfigured or it
must be moved to a slot where a compatible unit is registered.
The unit inherits settings.
6 72 PMA "No extended backup unit address"
The control unit returns no address of the extended backup
unit. The capacity of the extended backup unit may have
run out.
7 72 PMA "Extended backup unit fault"
No answer or error message from the extended backup unit
(it may be missing, it is not in inventory or SCU may have
run out of backup space).
8 38 PMA, S "Bus sync. fault"
The fault is activated if the X-bus synchronization pulse
transmitted by SXU is missing. A typical reason for this fault
is that SXU is missing. If only one interface unit has this
fault although there are other interface units in the subrack
then the fault is most likely in that particular unit.
9 36 PMA, S "Start request denied"
Most likely the unit does not belong to the node configuration.
11 5 PMA, S "RAM fault"
A background process has detected a RAM location where
the read value does not match with the written test pattern.
12 5 PMA, S "File system fatal error"
Flash system failed. Replace the unit with a spare unit.
13 5 MEI "File system warning"
The flash file system is damaged.
14 5 PMA "SW checksum error on RAM"
The running application software has corrupted. The
calculated check sum does not match with the stored one
on RAM.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

139
31 OMH, OMH-A

SPT GPT Status SPT Description


15 5 PMA "SW checksum error on boot flash"
The boot software has corrupted. The calculated check sum
does not match with the stored one on boot flash.
18 5 PMA, S "Flash setup checksum error"
One of the setting structures is corrupted in the non-volatile
memory. The calculated check sum does not match with the
stored one in the flash setting structure.
19 5 PMA, S "Missing settings"
One of the setting structures is missing in the non-volatile
memory.
22 39 PMA, S "Tx clock fault"
The fault is activated if the interface module transmitting
clock phase locking to the X-bus clock fails.
23 40 PMA, S "IA activity missing"
The fault is activated if the unit cannot find its locked
interface address on the cross-connection bus. SXU should
activate IA on the bus if the interface is locked.
24 10 PMA, S "IF module missing"
The interface module defined in the settings is missing.
25 10 PMA, S "Wrong interface module"
There is a conflict between the installed module and the
settings.
26 57 MEI “NTU power off”
The "NTU power off"-message has been received from an
NTU losing its power supply voltage.
27 12 PMA, S "Rx signal missing"
The signal level is below a specific level (the level depends
on the used interface module and the selected bit rate).
28 42 MEI, S "AIS from X-BUS"
The fault is activated if the frame synchronization word and
RAI from the X-bus and TS0 B2 changes between "0" and
"1" are missing.
29 23 MEI, S "Rx-signal is AIS"
The fault is activated if 2 or less zeros in a 2-frame period are
recognized. The fault is deactivated if 3 or more zeros in a
2-frame period are recognized.
30 26 DMA "CRC missing"
The fault is activated if framing can be found and the CRC
multiframe alignment has been lost for 100-200 ms.
The fault is deactivated if the multiframe alignment has been
found. This fault indicates that the remote end most likely
does not use CRC.
31 26 PMA, S "Frame alignment lost by CRC"
See CCITT G.706 Frame alignment recovery (2048 mode ≥
915 CRC block errors detected).
32 24 PMA, S "Frame alignment lost"
See CCITT G.706 Loss of frame alignment.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

140
31 OMH, OMH-A

SPT GPT Status SPT Description


33 13 PMA, S "BER1E-3"
See ITU-T G.736. The bit error rate is calculated from faulty
frame alignment words or from code errors. The bit error rate
1E-3 limits from frame alignment words: 2048 kbit/s and n x
64 kbit/s count time 4 seconds
Count to activate alarm: 94
Count to deactivate alarm: 17
Error rate 1 E-3 limits from code errors:
Count time 1 second
Bit rate (kbit/s): 2048
Activation limit: 1973
Deactivation limit: 229
10-3 alarm status depends on fault consequences (AIS
insertion).
34 13 DMA "BER1E-3"
See the above explanation.
37 29 PMA, S "No response to NNM message"
The control channel of the interface is used and the neighbor
node supervision option of the interface is on and no NNM
(Neighbor Node Monitoring) message has been received
from the interface within 8 seconds.
38 29 PMA, S "Own NNM messages received"
The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received
NNM message contains the same identification data as the
NNM message sent to the interface.
39 29 PMA, S "Wrong IDs in NNM message"
The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received
NNM message contains unexpected neighbor identification
data.
40 27 MEI, S "Loop: IF back to equipment"
An interface loop is created in the interface module. It loops
transmitted data and the clock signal back to the interface
receiver.
41 27 MEI, S "Loop: MUX/DEMUX back to eq"
Similar to the Interface back to equipment loop except that
the loop is made before the interface module in the OMH
unit base card.
42 27 MEI, S "Loop: MUX/DEMUX back to line"
Rx data is looped back to the interface transmitter. When the
HDLC channel is used, it works with this line loop. All other
bits are looped back to the interface.
43 27 MEI, S "Line loop made by neighbor"
This alarm is activated if the HDLC channel is in use and
MUX/DEMUX back to the line loop has been activated from
the remote end, or BTE module is used and the remote end
has activated the V.54 loop.
44 27 MEI, S "Remote controlled line loop"
This alarm is activated if the HDLC channel is in use and
MUX/DEMUX back to the line loop has been made to the
neighbor unit, or BTE module is used and the V.54 loop has
been made to the remote end.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

141
31 OMH, OMH-A

SPT GPT Status SPT Description


45 43 MEI, S "AIS in signaling"
The fault is activated if a signal in the signaling timeslot
contains less than 2 zeros during a multiframe period.
50 25 PMA, S "MFrame alignment lost"
The fault is activated if two consecutive faulty multiframe
alignment words are received, or if all signaling time slots
in one multiframe contain only zeros ("0"). The fault is
deactivated when the frame alignment is detected and the
first four bits of the signaling timeslot are found to be zeros
("0") and when the prior signaling timeslot had at least one
bit in state "1".
55 20 MEI, S "Frame far-end alarm"
The state of the far-end alarm bit TS0 B3 will be switched
if the opposite state is received in 3 consecutive frames.
State "1" is used for alarm. Alarm status depends on fault
consequences (AIS insertion into the signaling timeslot).
56 20 MEI "Frame far-end alarm"
See the above explanation.
57 21 MEI, S "MFrame far-end alarm"
The state of signaling timeslot’s frame 0 B6 alarm bit will be
switched if the opposite state is received in 3 consecutive
frames. State "1" is used for alarm. Alarm status depends on
fault consequences (AIS insertion into the signaling timeslot).
58 21 MEI "MFrame far-end alarm"
See the above explanation.
67 16 DMA "BER1E-6"
BER1E-6 error rate is calculated from CRC block errors
when bit rate > 1024 kbit/s. Counting time is 10 seconds
and the limit for the fault condition depends on the used bit
rate (2048 limit is 10).
68 58 MEI "Faults masked/test"
The fault is activated when the interface Fault mask setting
is on
(all interface faults are cleared).
69 30 DMA "Frequency difference"
The measurement period is 15 seconds and the phase-drifting
limit is 18 ms. The fault is activated if the phase-drifting
limit has been exceeded in 3 measurements out of 4.
70 30 MEI "Buffer slip(s)/1 hour"
The fault is activated if one or more buffer slip(s) have been
detected during the last hour.
71 41 DMA "HDLC overlap with X-bus"
The fault is activated if the HDLC control channel bit(s) are
also used by the cross-connection bus.
72 41 DMA "MCLK RAI overlap with X-bus"
The fault is activated if the MCLK/RAI bit is also used by
the cross-connection bus.
73 32 PMA, S "ASIC register error"
The fault is activated if the difference between write/read
configuration data of ASIC has been detected.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

142
31 OMH, OMH-A

SPT GPT Status SPT Description


74 91 MEI "Performance event"
This fault is activated as a delta fault when G.826 supervision
is used if at least one performance event has been occurred
in a 15-minute period.
78 69 DMA "Port locking conflict"
The fault is activated if SXU has the port descriptor but the
unit interface is unlocked or SXU does not have the port
descriptor although the interface is locked. Use lock/unlock.
79 53 MEI "Protection switch forced"
The unit is in 1+1 protected mode and the protection switch
has been forced to select signal from IF1 or IF2.
82 112 PMA, S "Excessive errors"
Once every second, block errors shall be compared with the
limit value. If errors count ≥ limit, the one second shall be
declared BAD, otherwise it shall be declared GOOD.
The Excessive errors shall be detected if M consecutive BAD
seconds have occurred. The Excessive errors shall be cleared
if M consecutive GOOD seconds have occurred. The value
of M range 2..9.
83 103 DMA "Degraded errors"
Once every second, block errors shall be compared with the
limit value. If errors count ≥ limit, the one second shall be
declared BAD, otherwise it shall be declared GOOD.
The Degraded errors shall be detected if M consecutive BAD
seconds have occurred. The Degraded errors shall be cleared
if M consecutive GOOD seconds have occurred. The value
of M range 2..9.
84 49 DMA "Noise margin alarm"
The quality of the line is not good enough for data
communications.
85 24 PMA, S "Loss of HDSL frame"
See ETSI TS 101 135 Loss of HDSL frame alignment.
86 75 PMA, S "Chain number conflict"
The existing numbering differs from the defined and the
re-numbering operation is recommended.
87 114 PMA, S "Unavail (G.826)"
A period of unavailable time begins at the onset of ten
consecutive SES events. These ten seconds are considered to
be part of unavailable time. A new period of available time
begins at the onset of ten consecutive non-SES events. These
ten seconds are considered to be part of available time.
88 114 PMA, S "Unavail far end"
A period of far end unavailable time (only when
unidirectional performance collection used) begins at the
onset of ten consecutive far end SES events. These ten
seconds are considered to be part of far end unavailable time.
A new period of available time begins at the onset of ten
consecutive non-far end SES events. These ten seconds are
considered to be part of available time.
89 49 DMA "Qos"
Quality of service. Quality of signal in 24 hours period.
At least one of the BBE, ES or SES limits exceeded. Cleared
when period changes.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

143
31 OMH, OMH-A

SPT GPT Status SPT Description


90 49 DMA "Qostr"
Quality of service, threshold reset. Quality of signal in a
15-minute period.
At least one of the upper ES, BBE or SES limits has been
exceeded. Cleared when found a period where the lower ES,
BBE or SES limits has not been exceeded.
92 55 PMA, S "HW/SW version conflict"
The software is in a wrong unit or in a wrong unit version.
93 68 DMA "Door open"
Indicates that door of modem is open.
94 68 DMA "Customer alarm 1"
Indicates that external (1) alarm in modem is active.
95 68 DMA "Customer alarm 2"
Indicates that external (2) alarm in modem is active.
96 53 MEI "Ring force switch"
Ring protection force switch (loop) is active (this control is
activated by the user and no timeout for this exists).
97 20 MEI "Pilot bit far end alarm"
A pilot bit far end alarm is detected from X-bus.
98 42 MEI, S "Pilot bit AIS"
Pilot bit AIS (S-status) is detected from the X-bus.
99 27 MEI "Ring protection loop"
Ring protection loop is active (S-status fault in Rx signal
causes this).
100 53 MEI "Ring lockout from protection"
Ring protection is locked out from protection -> protection
loop will not be made even if the Rx signal has the S-status
fault active (this control is activated by the user and no
timeout for this exists)
101 11 PMA, S "Loss of protected DSL line signal"
In 1+1 line protection mode Line1 and Line2 of both
interfaces have faults which cause loss of protected signal.
102 103 DMA "Degraded protected signal"
In 1+1 protected mode the selected signal has a signal
degraded fault.
103 12 DMA "Rx signal missing"
The signal level is below a specific level (the level depends
on the used interface module and the selected bit rate).
200 5 PMA, S "Downloaded SW missing"
The application software cannot be started, because the
downloaded software is missing. The unit is not operational
until new software has been downloaded.
201 5 PMA, S "Downloaded SW in reset loop"
The application software cannot be started due to a fatal
error. The unit is not operational until new software has been
downloaded.
202 5 PMA, S "Downloaded SW incompatible"
The application software cannot be started, because
the permanent boot software is incompatible with the
downloaded application software on flash. The unit is not
operational until new software has been downloaded.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

144
31 OMH, OMH-A

SPT GPT Status SPT Description


203 5 PMA, S "Downloaded SW checksum error"
The application software cannot be started, because the
downloaded application software has corrupted. The
calculated check sum does not match with the one stored in
downloadable flash. The unit is not operational until new
software has been downloaded.
204 5 PMA, S "Downloaded SW disabled"
The application software cannot be started, because the
application software is disabled. The unit is not operational
until new software has been downloaded.
205 5 PMA, S "Downloaded SW faulty"
The application software cannot be started, because the
downloaded file is invalid. The unit is not operational until
new software has been downloaded.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

145
32 OMH2-8, OMH2-16

32 OMH2-8, OMH2-16
SPT GPT Status SPT Description
1 1 PMA "SW Unpredicted"
This fault condition should never occur.
2 2 PMA "Reset"
There has been a unit reset (detected always after the
power-up of the unit). Note: this is a delta event, not an
active fault
3 11 PMA, S "Loss of protected signal"
In 1+1 protection mode both interfaces IF1 and IF2 have
faults which in unprotected mode have S status.
4 69 MEI "Reading extended backup settings"
The unit is reading its extended backup settings from the
extended backup unit. Do not interrupt.
5 69 PMA "Extended settings corrupted"
Fatal setup corruption. The unit must be configured again
or it must be replaced to a slot where compatible unit is
registered. The unit inherits settings.
6 72 PMA "No extended backup unit address"
The control unit returns no address of the extended backup
unit. The capacity of the extended backup unit may have
run out.
7 72 PMA "Extended backup unit fault"
No answer or error message from the extended backup unit
(it may be missing, not in inventory or SCU may have run
out of backup space).

8 38 PMA, S "Bus sync. fault"


The fault is activated if the X-bus synchronization pulse
transmitted by SXU is missing. A typical reason for this fault
is that SXU is missing. If only one interface unit has this
fault although there are other interface units in the subrack
then the fault is most likely in that particular unit.
9 36 PMA, S "Start request denied"
Most likely the unit does not belong to the node configuration.
11 5 PMA, S "RAM fault"
A background process has detected a RAM location where
the read value does not match with the written test pattern.
12 5 PMA, S "File system fatal error"
Flash system failed. Replace the unit with a spare unit.
13 5 MEI "File system warning"
The flash file system is damaged.
14 5 PMA "SW checksum error on RAM"
The running application software has corrupted. The
calculated check sum does not match with the stored one
on RAM.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

146
32 OMH2-8, OMH2-16

SPT GPT Status SPT Description


15 5 PMA "SW checksum error on boot flash"
The boot software has corrupted. The calculated check sum
does not match with the stored one on boot flash.
18 5 PMA, S "Flash setup checksum error"
One of the setting structures is corrupted in the non-volatile
memory. The calculated check sum does not match with the
stored one in the flash setting structure.
19 5 PMA, S "Missing settings"
One of the setting structures is missing in the non-volatile
memory.
22 39 PMA, S "Tx clock fault"
The fault is activated if the interface module transmitting
clock phase locking to the X-bus clock fails.
23 40 PMA, S / "IA activity missing"
DMA The fault is activated if the unit cannot find its locked
interface address on the cross-connection bus. SXU should
activate IA on the bus if the interface is locked.
26 57 MEI, S “NTU power off”
The "NTU power off"-message has been received from an
NTU losing its power supply voltage.
27 12 PMA, S / "Rx signal missing"
DMA The signal level is below a specific level (the level depends
on the used interface module and the selected bit rate). The
fault status level is lowered if 1+1 protection is activated.
28 42 MEI, S "AIS from X-BUS"
The fault is activated if the frame synchronization word and
RAI from the X-bus and TS0 B2 changes between "0" and
"1" are missing.
29 23 MEI, S "Rx-signal is AIS"
The fault is activated if 2 or less zeros in a 2-frame period are
recognized. The fault is deactivated if 3 or more zeros in a
2-frame period are recognized.
30 26 DMA "CRC missing"
The fault is activated if framing can be found and the CRC
multiframe alignment has been lost for 100-200 ms.
The fault is deactivated if the multiframe alignment has been
found. This fault indicates that the remote end most likely
does not use CRC.
31 26 PMA, S / "Frame alignment lost by CRC"
DMA See CCITT G.706 Frame alignment recovery (2048 mode
≥ 915 CRC block errors detected).The fault status level is
lowered if 1+1 protection is activated.
32 24 PMA, S "Frame alignment lost"
See CCITT G.706 Loss of frame alignment.The fault status
level is lowered if 1+1 protection is activated.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

147
32 OMH2-8, OMH2-16

SPT GPT Status SPT Description


33 13 PMA, S "BER1E-3"
See ITU-T G.736. The bit error rate is calculated from faulty
frame alignment words or from code errors. The bit error rate
1E-3 limits from frame alignment words: 2048 kbit/s and n x
64 kbit/s count time 4 seconds
Count to activate alarm: 94
Count to deactivate alarm: 17
Error rate 1 E-3 limits from code errors:
Count time 1 second
Bit rate (kbit/s): 2048
Activation limit: 1973
Deactivation limit: 229
10-3 alarm status depends on fault consequences (AIS
insertion).
34 13 DMA "BER1E-3"
See the above explanation.
37 29 PMA, S / "No response to NNM message"
DMA The control channel of the interface is used and the neighbor
node supervision option of the interface is on and no NNM
(Neighbor Node Monitoring) message has been received
from the interface within 8 seconds. The fault status level is
lowered if 1+1 protection is activated.
38 29 PMA, S / "Own NNM messages received"
DMA The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received
NNM message contains the same identification data as the
NNM message sent to the interface.
39 29 PMA, S / "Wrong IDs in NNM message"
DMA The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received
NNM message contains unexpected neighbor identification
data.
40 27 MEI, S "Interface Loop"
.An interface loop is created on a physical line interface chip.
It loops the transmit data and the clock signal back to the
interface receiver (back to the equipment).
41 27 MEI, S "Equipment Loop"
Similar to the Interface back to equipment loop except that
the loop is made before the interface module in the OMH
unit base card.
42 27 MEI, S "Line Loop"
Rx data is looped back to the interface transmitter. When the
HDLC channel is used, it works with this line loop. All other
bits are looped back to the interface.
43 27 MEI, S "Line loop made by neighbor"
This alarm is activated if the HDLC channel is in use and
MUX/DEMUX back to the line loop has been activated from
the remote end.
44 27 MEI, S "Remote controlled line loop"
This alarm is activated if the HDLC channel is in use and
MUX/DEMUX back to the line loop has been made to the
neighbor unit.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

148
32 OMH2-8, OMH2-16

SPT GPT Status SPT Description


45 43 MEI, S "AIS in signaling"
The fault is activated if a signal in the signaling time slot
contains less than 2 zeros during a multiframe period.
50 25 PMA, S / "MFrame alignment lost"
DMA The fault is activated if two consecutive faulty multiframe
alignment words are received, or if all signaling time slots
in one multiframe contain only zeros ("0"). The fault is
deactivated when the frame alignment is detected and the
first four bits of the signaling timeslot are found to be zeros
("0") and when the prior signaling timeslot had at least one
bit in state "1". The fault status level is lowered if 1+1
protection is activated.
55 20 MEI, S "Frame far-end alarm"
The state of the far-end alarm bit TS0 B3 will be switched
if the opposite state is received in 3 consecutive frames.
State "1" is used for alarm. Alarm status depends on fault
consequences (AIS insertion into the signaling timeslot).
56 20 MEI "Frame far-end alarm"
See the above explanation.
57 21 MEI, S "MFrame far-end alarm"
The state of signaling timeslot’s frame 0 B6 alarm bit will be
switched if the opposite state is received in 3 consecutive
frames. State "1" is used for alarm. Alarm status depends on
fault consequences (AIS insertion into the signaling timeslot).
58 21 MEI "MFrame far-end alarm"
See the above explanation.
67 16 DMA "BER1E-6"
BER1E-6 error rate is calculated from CRC block errors
when bit rate > 1024 kbit/s. Counting time is 10 seconds
and the limit for the fault condition depends on the used bit
rate (2048 limit is 10).
68 58 MEI "Faults masked/test"
The fault is activated when the interface Fault mask setting
is on
(all interface faults are cleared).
69 30 DMA ""Frequency difference in Rx signal
The frequency of the received 2 Mbit/s signal has offset with
the node clock.
70 30 MEI "Buffer slip(s)/1 hour"
The fault is activated if one or more buffer slip(s) have been
detected during the last hour.
71 41 DMA "HDLC overlap with X-bus"
The fault is activated if the HDLC control channel bit(s) are
also used by the cross-connection bus.
72 41 DMA "MCLK RAI overlap with X-bus"
The fault is activated if the MCLK/RAI bit is also used by
the cross-connection bus.
73 32 PMA, S "ASIC register error"
The fault is activated if the difference between write/read
configuration data of ASIC has been detected.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

149
32 OMH2-8, OMH2-16

SPT GPT Status SPT Description


74 91 MEI "Performance event"
This fault is activated as a delta fault when G.826 supervision
is used if at least one performance event has been occurred
in a 15-minute period.
78 69 DMA "Port locking conflict"
The fault is activated if SXU has the port descriptor but the
unit interface is unlocked or SXU does not have the port
descriptor although the interface is locked. Use lock/unlock.
79 53 MEI "Protection switch forced"
The unit is in 1+1 protected mode and the protection switch
has been forced to select signal from IF1 or IF2.
82 112 PMA, S, "Excessive errors"
DMA Once every second, block errors shall be compared with the
limit value. If errors count ≥ limit, the one second shall be
declared BAD, otherwise it shall be declared GOOD.
The Excessive errors shall be detected if M consecutive BAD
seconds have occurred. The Excessive errors shall be cleared
if M consecutive GOOD seconds have occurred. The value
of M range from 2 to 9.
83 103 DMA "Degraded errors"
Once every second, block errors shall be compared with the
limit value. If errors count ≥ limit, the one second shall be
declared BAD, otherwise it shall be declared GOOD.
The Degraded errors shall be detected if M consecutive BAD
seconds have occurred. The Degraded errors shall be cleared
if M consecutive GOOD seconds have occurred. The value
of M range from 2 to 9.
84 49 DMA "Noise margin alarm"
The quality of the line is not good enough for data
communications.
86 75 PMA, S "Chain number conflict"
The existing numbering differs from the defined and the
re-numbering operation is recommended.
87 114 PMA, S / "Unavail (G.826)"
DMA A period of unavailable time begins at the onset of ten
consecutive SES events. These ten seconds are considered to
be part of unavailable time. A new period of available time
begins at the onset of ten consecutive non-SES events. These
ten seconds are considered to be part of available time. The
fault status level is lowered if 1+1 protection is activated.
88 114 PMA, S / "Unavail far end"
DMA A period of far end unavailable time (only when
unidirectional performance collection used) begins at the
onset of ten consecutive far end SES events. These ten
seconds are considered to be part of far end unavailable time.
A new period of available time begins at the onset of ten
consecutive non-far end SES events. These ten seconds are
considered to be part of available time. The fault status level
is lowered if 1+1 protection is activated.
89 49 DMA "Qos"
Quality of service. Quality of signal in 24 hours period.
At least one of the BBE, ES or SES limits exceeded. Cleared
when period changes.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

150
32 OMH2-8, OMH2-16

SPT GPT Status SPT Description


90 49 DMA "Qostr"
Quality of service, threshold reset. Quality of signal in a
15-minute period.
At least one of the upper ES, BBE or SES limits has been
exceeded. Cleared when found a period where the lower ES,
BBE or SES limits has not been exceeded.
92 55 PMA, S "HW/SW version conflict"
The software is in a wrong unit or in a wrong unit version.
96 53 MEI "Ring force switch"
Ring protection force switch (loop) is active (this control is
activated by the user and no timeout for this exists).
97 20 MEI "Pilot bit far end alarm"
From X-bus pilot bit far end alarm is detected.
98 42 MEI, S "Pilot bit AIS"
Pilot bit AIS (S-status) is detected from the X-bus.

99 27 MEI "Ring protection loop"


Ring protection loop is active (S-status fault in Rx signal
causes this).
100 53 MEI "Ring lockout from protection"
Ring protection is locked out from protection -> protection
loop will not be made even if the Rx signal has the S-status
fault active (this control is activated by the user and no
timeout for this exists)
102 103 DMA "Degraded protected signal"
In 1+1 protected mode the selected signal has a signal
degraded fault.
200 5 PMA "Downloaded SW missing"
The application software cannot be started, because the
downloaded software is missing. The unit is not operational
until new software has been downloaded.
201 5 PMA "Downloaded SW in reset loop"
The application software cannot be started due to a fatal
error. The unit is not operational until new software has been
downloaded.
202 5 PMA "Downloaded SW incompatible"
The application software cannot be started, because
the permanent boot software is incompatible with the
downloaded application software on flash. The unit is not
operational until new software has been downloaded.
203 5 PMA "Downloaded SW checksum error"
The application software cannot be started, because the
downloaded application software has been corrupted. The
calculated check sum does not match with the one stored in
downloadable flash. The unit is not operational until new
software has been downloaded.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

151
32 OMH2-8, OMH2-16

SPT GPT Status SPT Description


204 5 PMA "Downloaded SW disabled"
The application software cannot be started, because the
application software is disabled. The unit is not operational
until new software has been downloaded.
205 5 PMA "Downloaded SW faulty"
The application software cannot be started, because the
downloaded file is invalid. The unit is not operational until
new software has been downloaded.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

152
33 QMH

33 QMH
SPT GPT Status SPT Description
1 1 PMA "SW unpredicted"
This fault condition should never occur (or is not yet
supported).
2 2 PMA "Reset"
There has been a unit reset (detected always after the
power-up of the unit).
3 11 PMA, S "Loss of protected signal"
In 1+1 protection mode both interfaces IF1 and IF2 have
faults which in unprotected mode have S status.
4 4 PMA "Power + 5 V"
The voltage is below the threshold limit (about 4.6 V
depending on the calibration and the A/D resolution).
5 4 PMA "Power +12 V"
The voltage is below the threshold limit (about 11.3 V
depending on the calibration and the A/D resolution).
6 4 PMA "Power -10 V"
The voltage is above the threshold limit (about -9.0 V
depending on the calibration and the A/D resolution).
7 36 PMA, S "Power +3,3 V (VP3)"
The voltage is below the threshold limit (limit depends on
the calibration and the A/D resolution).
8 38 PMA, S "Bus sync. fault"
The fault is activated if the X-bus synchronization pulse
transmitted by SXU is missing. A typical reason for this fault
is that SXU is missing. If only one QMH/GMH unit has
this fault although there are other QMH/GMH units in the
subrack then the fault is most likely in the QMH unit.
9 36 PMA, S "Start request denied"
Most likely the unit does not belong to the node configuration.
11 5 PMA, S "RAM fault"
A background process has detected a RAM location where
the read value does not match the written test pattern.
12 5 PMA, S "EPROM fault"
The calculated check sum does not match the stored one.
13 5 PMA "Flash write error"
Error when writing to the flash memory (main bank).
14 5 PMA "Flash copy error"
Error when writing to the flash memory (shadow bank).
15 5 PMA "Flash erase error"
Error during the erase of the flash memory (shadow bank).
16 5 PMA "Flash duplicate error"
Duplicated parameters (the same ID) detected during the
start-up

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

153
33 QMH

SPT GPT Status SPT Description


17 5 PMA "Flash shadow error"
The shadow bank of the flash is not erased during the start-up.
18 5 PMA, S "Flash check sum error"
The calculated check sum does not match the stored one.
19 5 PMA, S "Missing settings"
One of the setting structures has been corrupted in the
non-volatile memory.
20 59 MEI, S "BTE Tx line test"
The fault is activated if the Tx test pattern generator of the
BTE module is activated (used in V.54 remote loop).
22 39 PMA, S "Tx clock fault"
The fault is activated if the interface module transmitting
clock phase locking to the X-bus clock fails.
23 40 PMA, S "IA activity missing"
The fault is activated if the unit cannot find its locked
interface address on the cross-connection bus. SXU should
activate IA on the bus if the interface is locked.
24 10 PMA, S "IF module missing"
The interface module defined in the settings is missing.
25 10 PMA, S "Wrong interface module"
There is a conflict between the installed module and the
settings.
26 57 MEI "NTU power off/local loop"
The fault is activated if the module used is BTE 232 and
wetting current is on and the received current value differs
in frequency of 1.5º4.5 Hz and current value difference is
more than 1.5
27 12 PMA, S "Rx signal missing"
The signal level is below a specific level (the level depends
on the used interface module and the selected bit rate).
28 42 MEI, S "AIS from X-BUS"
The fault is activated if the frame synchronization word and
RAI from the X-bus and TS0 B2 changes between "0" and
"1" are missing.
29 23 MEI, S "Rx signal is AIS"
The fault is activated if 2 or less/2M mode or 8 or less/8M
mode zeros in a 2-frame period are recognized. The fault is
deactivated if 3 or more/2M mode or 12 or more/8M mode
zeros in a 2-frame period are recognized.
30 26 DMA "CRC missing"
The fault is activated if framing can be found in the 2M
mode and the CRC multiframe alignment has been lost for
100...200 ms, or if in the 8M mode CRC alignment losses
have been found more than 6 times in a 3-second period due
to excessive block errors.
The fault is deactivated if the multiframe alignment has been
found in the 2M mode and in the 8M mode when no more
than one frame alignment lost due to excessive CRC block
errors in a 3-second-period has been found.
This fault indicates that the remote end most likely does not
use the CRC.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

154
33 QMH

SPT GPT Status SPT Description


31 26 PMA, S "Frame alignment lost by CRC"
See CCITT G.706 Frame alignment recovery (2048 mode ≥
915 CRC block errors detected).
32 24 PMA, S "Frame alignment lost"
See CCITT G.706 Loss of frame alignment.
33 13 PMA, S "BER10E-3"
See ITU-T G.736. The bit error rate is calculated from faulty
frame alignment words or from code errors. The bit error rate
10E-3 limits from frame alignment words:
2048 kbit/s and n x 64 kbit/s count time 4 seconds
Count to activate alarm: 94
Count to deactivate alarm: 17
8448 kbit/s and count time 2 seconds
Count to activate alarm: 199
Count to deactivate alarm: 48
Error rate 10E-3 limits from code errors:
Count time 1 second
2048 kbit/s
Activation limit: 1973
Deactivation limit: 229
8448 kbit/s
Activation limit: 8296
Deactivation limit: 229
10-3 alarm status depends on fault consequences (AIS
insertion).
34 13 DMA "BER10E-3"
See ITU-T G.736. The bit error rate is calculated from faulty
frame alignment words or from code errors. The bit error rate
10E-3 limits from frame alignment words:
2048 kbit/s and n x 64 kbit/s count time 4 seconds
Count to activate alarm: 94
Count to deactivate alarm: 17
8448 kbit/s and count time 2 seconds
Count to activate alarm: 199
Count to deactivate alarm: 48
Error rate 10E-3 limits from code errors:
Count time 1 second
2048 kbit/s
Activation limit: 1973
Deactivation limit: 229
8448 kbit/s
Activation limit: 8296
Deactivation limit: 839
10-3 alarm status depends on fault consequences (AIS
insertion).
35 56 MEI "NTU line break"
The fault is activated if the module used is BTE 232 and
wetting current is on and the received current value is lower
than 1.2 mA.
36 56 MEI "NTU short circuit"
The fault is activated if the module used is BTE 232 and
wetting current is on and the received current value is higher
than 6.5 mA.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

155
33 QMH

SPT GPT Status SPT Description


37 29 PMA, S "No response to NNM message"
The control channel of the interface is used and the neighbor
node supervision option of the interface is on and no NNM
(Neighbor Node Monitoring) message has been received
from the interface within 8 seconds.
38 29 PMA, S "Own NNM messages received"
The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received
NNM message contains the same identification data as the
NNM message sent to the interface.
39 29 PMA, S "Wrong ID’s in NNM message"
The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received
NNM message contains unexpected neighbor identification
data.
40 27 MEI, S "Loop: IF back to equipment"
An interface loop is created in the interface module. It loops
transmitted data and the clock signal back to the interface
receiver.
41 27 MEI, S "Loop: MUX/DEMUX back to eq."
Similar to Interface back to equipment loop except that the
loop is made before the interface module in the GMH unit
base card.
42 27 MEI, S "Loop: MUX/DEMUX back to line"
Rx data is looped back to the interface transmitter. When the
HDLC channel is used, it works with this line loop. All other
bits are looped back to the interface.
43 27 MEI, S "Line loop made by neighbor"
This alarm is activated if the HDLC channel is in use and
MUX/DEMUX back to the line loop has been activated from
the remote end, or BTE module is used and the remote end
has activated the V.54 loop.
44 27 MEI, S "Remote controlled line loop"
This alarm is activated if the HDLC-channel is in use and
MUX/DEMUX back to the line loop has been made to the
neighbor unit, or BTE module is used and the V.54 loop has
been made to the remote end.
45 43 MEI, S "AIS in signaling"
The fault is activated if a signal in the signaling timeslot
contains less than 2 zeros during a multiframe period.
46 43 MEI, S "AIS in signaling group A"
The fault is activated if a signal in the signaling timeslot
contains less than 2 zeros during a multiframe period.
47 43 MEI, S "AIS in signaling group B"
The fault is activated if a signal in the signaling timeslot
contains less than 2 zeros during a multiframe period.
48 43 MEI, S "AIS in signaling group C"
The fault is activated if a signal in the signaling timeslot
contains less than 2 zeros during a multiframe period.
49 43 MEI, S "AIS in signaling group D"
The fault is activated if a signal in the signaling timeslot
contains less than 2 zeros during a multiframe period.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

156
33 QMH

SPT GPT Status SPT Description


50 25 PMA, S "MFrame alignment lost"
The fault is activated if two consecutive faulty multiframe
alignment words are received or if all signaling time slots
in one multiframe contain only zeros ("0"). The fault is
deactivated when the frame alignment is detected and the
first four bits of the signaling timeslot are found to be zeros
("0") and when the prior signaling timeslot had at least one
bit in state "1".
51 25 PMA, S "MFrame alignment lost, group A"
See above.
52 25 PMA, S "MFrame alignment lost, group B"
See above.
53 25 PMA, S "MFrame alignment lost, group C"
See above.
54 25 PMA, S "MFrame alignment lost, group D"
See above.
55 20 MEI, S "Frame far-end alarm"
The state of the far-end alarm bit TS0 B3 will be switched
if the opposite state is received in 3 consecutive frames.
State "1" is used for alarm. Alarm status depends on fault
consequences (AIS insertion into the signaling timeslot).
56 20 MEI "Frame far-end alarm"
The state of the far-end alarm bit TS0 B3 will be switched
if the opposite state is received in 3 consecutive frames.
State "1" is used for alarm. Alarm status depends on fault
consequences (AIS insertion into the signaling timeslot).
57 21 MEI, S "MFrame far-end alarm"
The state of signaling timeslot’s frame 0 B6 alarm bit will be
switched if the opposite state is received in 3 consecutive
frames. State "1" is used for alarm. Alarm status depends on
fault consequences (AIS insertion into the signaling timeslot).
58 21 MEI "MFrame far-end alarm"
The state of signaling timeslot’s frame 0 B6 alarm bit will be
switched if the opposite state is received in 3 consecutive
frames. State "1" is used for alarm. Alarm status depends on
fault consequences (AIS insertion into the signaling timeslot).
59 21 MEI, S "MFrame far-end alarm, group A"
The state of signaling timeslot’s frame 0 B6 alarm bit will be
switched if the opposite state is received in 3 consecutive
frames. State "1" is used for alarm. Alarm status depends on
fault consequences (AIS insertion into the signaling timeslot).
60 21 MEI "MFrame far-end alarm, group A"
The state of signaling timeslot’s frame 0 B6 alarm bit will be
switched if the opposite state is received in 3 consecutive
frames. State "1" is used for alarm. Alarm status depends on
fault consequences (AIS insertion into the signaling timeslot).
61 21 MEI, S "MFrame far-end alarm, group B"
The state of signaling timeslot’s frame 0 B6 alarm bit will be
switched if the opposite state is received in 3 consecutive
frames. State "1" is used for alarm. Alarm status depends on
fault consequences (AIS insertion into the signaling timeslot).

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

157
33 QMH

SPT GPT Status SPT Description


62 21 MEI "MFrame far-end alarm, group B"
The state of signaling timeslot’s frame 0 B6 alarm bit will be
switched if the opposite state is received in 3 consecutive
frames. State "1" is used for alarm. Alarm status depends on
fault consequences (AIS insertion into the signaling timeslot).
63 21 MEI, S "MFrame far-end alarm, group C"
The state of signaling timeslot’s frame 0 B6 alarm bit will be
switched if the opposite state is received in 3 consecutive
frames. State "1" is used for alarm. Alarm status depends on
fault consequences (AIS insertion into the signaling timeslot).
64 21 MEI "MFrame far-end alarm, group C"
The state of signaling timeslot’s frame 0 B6 alarm bit will be
switched if the opposite state is received in 3 consecutive
frames. State "1" is used for alarm. Alarm status depends on
fault consequences (AIS insertion into the signaling timeslot).
65 21 MEI, S "MFrame far-end alarm, group D"
The state of signaling timeslot’s frame 0 B6 alarm bit will be
switched if the opposite state is received in 3 consecutive
frames. State "1" is used for alarm. Alarm status depends on
fault consequences (AIS insertion into the signaling timeslot).
66 21 MEI "MFrame far-end alarm, group D"
The state of signaling timeslot’s frame 0 B6 alarm bit will be
switched if the opposite state is received in 3 consecutive
frames. State "1" is used for alarm. Alarm status depends on
fault consequences (AIS insertion into the signaling timeslot).
67 16 DMA "BER10E-6"
BER10E-6 error rate is calculated from CRC block errors
when bit rate ≥ 1024 kbit/s. Counting time is 10 seconds
and the limit for the fault condition depends on the used bit
rate (2048 limit is 10).
68 58 MEI "Faults masked/test"
The fault is activated when the interface Fault mask setting
is on
(all interface faults are cleared).
69 30 DMA "Frequency difference"
The measurement period is 15 seconds and the phase-drifting
limit is 5 ms (in USW versions newer than 6.7 the limit is 18
ms). The fault is activated if the phase-drifting limit has been
exceeded in 3 measurements out of 4.
70 30 MEI "Buffer slip(s)/1 hour"
The fault is activated if one or more buffer slip(s) have been
detected during the last hour.
71 41 DMA "HDLC overlap with X-bus"
The fault is activated if the HDLC control channel bit(s) are
also used by the cross-connection bus.
72 41 DMA "MCLK RAI overlap with X-bus"
The fault is activated if the MCLK/RAI bit is also used by
the cross-connection bus.
73 32 PMA, S "ASIC register error"
The fault is activated if the difference between write/read
configuration data of ASIC has been detected.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

158
33 QMH

SPT GPT Status SPT Description


74 60 DMA "G821 limit event"
This fault is activated as a delta fault if the G.821 supervision
is used and at least one performance limit (SES, ES, RAI
second, CRCE) has been exceeded in a 15-minute period.
75 48 PMA, S "G821 unavailable state"
The fault is activated if the G.821 supervision is used and
the state of the signal becomes unavailable (10 consecutive
SES seconds). The fault is deactivated when 10 consecutive
seconds not classified as SES have been found.
78 69 DMA "Port locking conflict"
The fault is activated if SXU has the port descriptor but the
unit interface is unlocked or SXU does not have the port
descriptor although the interface is locked. Use lock/unlock.
79 53 MEI "Protection switch forced"
The unit is in 1+1 protected mode and the protection switch
has been forced to select signal from IF1 or IF2.
80 55 PMA "Incompatible EPROM/FLASH SW"
The fault is activated if there is downloaded software in the
flash but the revision is wrong (for example if EPROM SW
is r5.5 and downloaded SW is r6.1).
81 5 PMA "Chksum err in downloaded SW"
The downloaded software has been corrupted.
82 112 DMA, (S) "Excessive errors"
Once every second, block errors shall be compared with the
limit value. If errors count ≥ limit, the one second shall be
declared BAD, otherwise it shall be declared GOOD.
The Excessive errors shall be detected if M consecutive BAD
seconds have occurred.
The Excessive errors shall be cleared if M consecutive
GOOD seconds have occurred.
M value range 2..9.
83 103 DMA, (S) "Degraded errors"
Once every second, block errors shall be compared with
limit value. If errors count ≥ limit, the one second shall be
declared BAD, otherwise it shall be declared GOOD.
The Degraded errors shall be detected if M consecutive BAD
seconds have occurred.
The Degraded errors shall be cleared if M consecutive
GOOD seconds have occurred.
M value range 2..9.
84 49 DMA, R ”Noise margin alarm”
The quality of the line is not good enough for data
communications.
85 24 PMA, S, R ”Loss of HDSL frame”
See ETSI TS 101 135 Loss of HDSL frame alignment.
86 75 PMA, S, R ”Chain number conflict”
The existing numbering differs from the defined and the
re-numbering operation is recommended.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

159
33 QMH

SPT GPT Status SPT Description


87 114 PMA, S ”Unavail (G.826)”
A period of unavailable time begins at the onset of ten
consecutive SES events. These ten seconds are considered to
be part of unavailable time. A new period of available time
begins at the onset of ten consecutive non-SES events. These
ten seconds are considered to be part of available time.
88 114 PMA, S ”Unavail far end”
A period of far end unavailable time (only when
unidirectional performance collection used) begins at the
onset of ten consecutive far end SES events. These ten
seconds are considered to be part of far end unavailable time.
A new period of available time begins at the onset of ten
consecutive non-far end SES events. These ten seconds are
considered to be part of available time.
89 49 DMA ”Qos”
Quality of service. Quality of signal in 24 hours period.
At least one of the BBE, ES or SES limits exceeded. Cleared
when period changes.
90 49 DMA, S, R ”Qostr”
Quality of service, threshold reset. Quality of signal in a
15-minute period.
At least one of the upper ES, BBE or SES limits exceeded.
Cleared when found a period where the lower ES, BBE or
SES limits has not been exceeded.
91 55 PMA, S, R ”Missing application program”
Downloaded software is missing
92 55 PMA, S, R ”HW/SW version conflict”
The software is in a wrong unit or in a wrong unit version
93 68 DMA, R "Door open"
Indicates that door of modem, e.g. 8110 OTU-2M is open
(8110 OTU-2M is connected to the QMH interface).
94 68 DMA, R "Customer alarm 1"
Indicates that external (1) alarm in modem, e.g. 8110
OTU-2M is active (8110 OTU-2M is connected to the QMH
interface).
95 68 DMA, R "Customer alarm 2"
Indicates that external (2) alarm in modem, e.g. 8110
OTU-2M is active (8110 OTU-2M is connected to the QMH
interface).
96 53 MEI, Y “Ring force switch”
Ring protection force switch (loop) is active (this control is
activated by user and no timeout for this exists).
97 20 MEI, Y “Pilot bit far end alarm”
From X-bus pilot bit far end alarm is detected.
98 42 MEI, S, Y “Pilot bit AIS”
Pilot bit AIS (S-status) from the X-bus is detected.
99 27 MEI, Y “Ring protection loop”
Ring protection loop is active (S-status fault in Rx-signal
causes this).

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

160
33 QMH

SPT GPT Status SPT Description


100 53 MEI, Y “Ring lockout from protection”
Ring protection is locked out from protection ⇒ protection
loop will not be made even if the Rx signal has the S-status
fault active (this control is activated by the user and no
timeout for this exists)
250 117 PMA “AIS Reported from 6300”
6300 Trail is broken, PBC, 6300 VC4 is unavailable or there
is a setup failure. See I/F message for additional information.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

161
34 RBS-E1, RBS-T1

34 RBS-E1, RBS-T1
SPT GPT Status SPT Description
1 1 PMA, S "SW unpredicted"
This fault condition should never occur (or is not yet
supported).
2 2 PMA, S "Reset"
There has been a unit reset (detected always after the
power-up of the unit).
18 5 PMA, S "Flash check sum error"
The calculated check sum does not match the stored one.
25 10 PMA, S "Wrong interface module" 6
The interface module is incorrect.
27 12 PMA, S "Rx signal missing"6
No signal on the line.
29 23 MEI, S "Rx signal AIS"6
Signal from the line is Alarm Indication Signal.
30 26 DMA "CRC missing"6
Frame alignment word is detected but CRC multiframe is not.
32 24 PMA, S "Frame alignment lost"6
See CCITT G.706 Loss of frame alignment.
34 13 DMA "BER 10E-3"6
See ITU-T G.736. The bit error rate is calculated from faulty
frame alignment words or from code errors. The bit error rate
10E-3 limits from frame alignment words:
2048 kbit/s and N * 64 kbit/s count time 4 seconds
Count to activate alarm: 94
Count to deactivate alarm: 17
8448 kbit/s and count time 2 seconds
Count to activate alarm: 199
Count to deactivate alarm: 48
Error rate 10E-3 limits from code errors:
Count time 1 second
2048 kbit/s
Activation limit: 1973
Deactivation limit: 229
8448 kbit/s
Activation limit: 8296
Deactivation limit: 839
10E-3 alarm status depends on fault consequences (AIS
insertion).
42 27 MEI, S "Loop: Mux/Demux back to line" 6
Rx data is looped back to the interface transmitter. When the
HDLC channel is used, it works with this line loop. All other
bits are looped back to the interface.

6RBS-E1

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

162
34 RBS-E1, RBS-T1

SPT GPT Status SPT Description


42 10 PMA, S "Wrong interface module/conflict in module"7
The interface module is incorrect.
51 58 MEI, S "Faults masked / test"6
The fault is activated when the interface Fault mask setting
is on (all interface faults are cleared).
54 27 MEI, S "Loop: Mux/Demux back to line"7
Rx data is looped back to the interface transmitter. When the
HDLC channel is used, it works with this line loop. All other
bits are looped back to the interface.
55 20 DMA "Remote alarm indication"6
RAI detected from the line.
57 27 MEI, S "Fault message for CSU line loop"7
A fault message for CSU line loop.
58 27 MEI, S "Fault message for CSU payload loop"7
A fault message for CSU payload loop.
61 12 PMA, S "Rx signal missing"7
No signal on the line.
64 24 PMA, S "Frame alignment lost" 7
See CCITT G.706 Loss of frame alignment.
69 23 MEI, S "Rx signal AIS"7
Signal from the line is Alarm Indication Signal.
70 30 DMA "Rx Buffer slip / BUFIN"6
Buffer slip in the 8100 system bus interface
72 20 DMA "Remote Alarm Indication" 7
RAI detected from the line.
73 13 MEI "BER 10E-3" 7
See ITU-T G.736. The bit error rate is calculated from faulty
frame alignment words or from code errors. The bit error rate
10E-3 limits from frame alignment words:
2048 kbit/s and N * 64 kbit/s count time 4 seconds
Count to activate alarm: 94
Count to deactivate alarm: 17
8448 kbit/s and count time 2 seconds
Count to activate alarm: 199
Count to deactivate alarm: 48
Error rate 10E-3 limits from code errors:
Count time 1 second
2048 kbit/s
Activation limit: 1973
Deactivation limit: 229
8448 kbit/s
Activation limit: 8296
Deactivation limit: 839
10E-3 alarm status depends on fault consequences (AIS
insertion).
74 60 DMA "G821 limit event"6
This fault is activated as a delta fault if the G.821 supervision
is used and at least one performance limit has been exceeded
in a 15-minute period.

7RBS-T1

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

163
34 RBS-E1, RBS-T1

SPT GPT Status SPT Description


75 48 PMA, S "G821 unavailable state"6
The fault is activated if the G.821 supervision is used and
the state of the signal becomes unavailable (10 consecutive
SES seconds). The fault is deactivated when 10 consecutive
seconds not classified as SES have been detected.
81 60 PMA, S "G821 unavailable state" 7
This fault is activated as a delta fault if the G.821 supervision
is used and at least one performance limit has been exceeded
in a 15-minute period.
82 48 DMA "G821 limit event"7
The fault is activated if the G.821 supervision is used and
the state of the signal becomes unavailable (10 consecutive
SES seconds). The fault is deactivated when 10 consecutive
seconds not classified as SES have been detected.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

164
35 SBU

35 SBU
SPT GPT Status SPT Description
0 0 - "Reserved"
1 1 PMA, S, R "SW unpredicted"
This fault condition should never occur (or is not yet
supported).
2 2 PMA, S, R "Reset"
There has been a unit reset (detected always after the
power-up of the unit).
3 3 PMA, S, R "Initialization error"
Initialization of the application SW unsuccessful (after the
power-up of the unit).
4 36 PMA, S, R "Start permission denied"
Most likely the unit does not belong to the node configuration.
10 4 PMA, R "Power +5 V (PDF)"
SBU power module failure.
11 4 PMA, R "Power +12 V (PDF)"
SBU power module failure.
12 4 PMA, R "Power -10 V (PDF)"
SBU power module failure.
13 4 PMA, R "Power +3.3 V (PDF)"
SBU power module failure.
14 4 PMA, R "Power +5 V (BUS)"
Protected bus auxiliary power failure.
15 4 PMA, R "Power +3.3 V (BUS)"
Protected bus auxiliary power failure.
20 5 PMA, S, R "RAM fault"
A background process has detected a RAM location where
the read value does not match the written test pattern.
21 5 PMA, R "EEPROM write error"
Error when writing to the EEPROM memory.
22 5 PMA, R "EEPROM checksum error"
The calculated check sum does not match the stored one in
EEPROM.
23 5 PMA, R "File system fatal error"
Flash system failed. Replace the unit with a spare unit.
24 5 MEI, R "File system bad block found"
One of the blocks in the flash system is not in use anymore.
25 5 PMA, R "SW chksum error on RAM"
The calculated check sum does not match the stored one in
RAM.
26 5 PMA, R "SW chksum error on boot flash"
The calculated check sum does not match the stored one in
boot flash.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

165
35 SBU

SPT GPT Status SPT Description


27 5 PMA, R "SW chksum error on DNL flash"
The calculated check sum does not match the stored one in
downloadable flash.
28 5 PMA, S, R "Missing settings"
One of the setting structures is missing from the non-volatile
memory.
29 5 PMA, R "Flash setup checksum error"
The calculated check sum does not match the stored one in
flash.
35 69 MEI, R "Reading ext. backup settings"
The unit is reading its extended backup settings from the ext.
backup unit. Do not interrupt.
36 69 PMA, R "Extended settings corrupted"
Fatal setup corruption. The unit must be configured again
or it must be replaced to a slot where a compatible unit is
registered; the unit inherits settings.
37 72 PMA, R "No extended backup unit addr."
The control unit returns no address of the extended backup
unit.
Capacity of the extended backup unit may have run out.
38 72 PMA, Y "Extended backup unit fault"
No answer or error message from the extended backup unit
(it may be missing, it may not be in the inventory or SCU
runs out of backup space).
40 10 PMA, S, R "Interface module missing"
The interface module defined in the settings is missing.
41 10 PMA, S, R "Incorrect interface module"
There is a conflict between the installed module and the
settings.
42 39 PMA, S, R "Internal oscillator failure"
The clock in the interface module has failed.
43 62 PMA, S, R "Internal processing error"
Error in processor for path overhead termination in the
interface module.
50 62 PMA, S, R "SBUS alarm"
The active (in use for the time being) SBUS does not work.
51 62 DMA, R "SBUS A fault"
The passive (not in use for the time being) SBUS A does
not work.
52 62 DMA, R "SBUS B fault"
The passive (not in use for the time being) SBUS B does
not work.
53 62 PMA, R "SBUS A activated, delta fault"
SBUS switch happened. SBUS A is now in use.
54 62 PMA, R "SBUS B activated, delta fault"
SBUS switch happened. SBUS B is now in use.
60 108 PMA, S, R "LOS"
Loss of signal defect is declared when a supervised signal
has not had any transitions for a period of time.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

166
35 SBU

SPT GPT Status SPT Description


61 27 MEI, S, Y "Equipment loop"
The E1 signal received from GMX (VC-12) is looped back
to GMX.
62 27 MEI, S, Y "Line loop"
The signal received at the E1 physical interface is looped
back to the E1 transmit interface.
63 23 MEI, S, Y "AIS"
The received E1 signal is Alarm Indication Signal.
70 73 MEI, S, Y "SSF"
The VC-12 signal from SBUS is in SSF (server signal fail)
state.
71 73 PMA, S, R "UNEQ"
The VC-12 signal from SBUS is in UNEQ (unequipped)
state.
72 113 PMA, S, R "TIM"
Trace identifier mismatch. The received trace identifier does
not match the expected one.
73 103 DMA, R "DEG"
Signal degrade.
Once every second, block errors shall be compared with the
limit value. If error count ≥ limit, the one second shall be
declared BAD, otherwise it shall be declared GOOD.
The Signal Degrade defect (dDEG) shall be detected if M
consecutive BAD seconds have occurred.
The Signal Degrade defect (dDEG) shall be cleared if M
consecutive GOOD seconds have occurred.
74 111 MEI, Y "RDI"
Remote defect indicator.
5 consecutive equal new values of RxRDI.
75 114 PMA, S "UNAVAIL"
Performance monitoring in unavailable state (G.774.01).
76 49 DMA "QOS"
Quality of service. The quality of signal in a 24-hour period.
At least one of the BBE, ES or SES limits exceeded. Cleared
when the period changes.
77 49 DMA "QOSTR"
Quality of service, threshold reset. Quality of signal in a
15-minute period.
At least one of the upper ES, BBE or SES limits exceeded.
Cleared when found a period where the lower ES, BBE or
SES limits has not been exceeded.
78 109 PMA, S, R "PLM"
Payload mismatch detected.
80 100 PMA, S, R "VC-12 active SBUS A alarm"
SBUS A is working only partially and is in use for the time
being and causes a defect to the VC-12 signal.
81 100 PMA, S, R "VC-12 active SBUS B alarm"
SBUS B is working only partially and is in use for the time
being and causes a defect to the VC-12 signal.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

167
35 SBU

SPT GPT Status SPT Description


82 100 DMA, R "VC-12 passive SBUS A fault"
SBUS A is working only partially, but is not in use for the
time being.
83 100 DMA, R "VC-12 passive SBUS B fault"
SBUS B is working only partially, but is not in use for the
time being.
84 91 MEI “Performance event for G.826”
At least one of performance event counters differs from zero
during the last 15-minute period.
90 58 MEI, Y "Faults masked"
Faults are masked (alarms are not generated as consequences
of fault conditions).
250 117 PMA “AIS Reported from 6300”
6300 Trail is broken, PBC, 6300 VC4 is Unavailable or there
is a setup failure. See I/F message for additional information.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

168
36 SCP

36 SCP
SPT GPT Status SPT Description
1 1 PMA "SW unpredicted"
This fault condition should never occur (or is not yet
supported).
2 2 PMA "Reset"
There has been a unit reset (detected always after the
power-up of the unit).
3 5 PMA "RAM fault"
A background process has detected a RAM location where
the read value does not match the written test pattern.
4 5 PMA "EPROM fault"
The calculated check sum does not match the stored one.
5 5 PMA "Flash write error"
Error when writing to the flash memory (main bank).
6 5 PMA "Flash copy error"
Error when writing to the flash memory (shadow bank).
7 5 PMA "Flash erase error"
Error during the erase of the flash memory (shadow bank).
8 5 PMA "Flash duplicate error"
Duplicated parameters (the same ID) detected during the
start-up.
9 5 PMA "Flash shadow error"
The shadow bank of the flash is not erased during the
start-up.
10 5 PMA "Flash check sum error"
The calculated check sum does not match the stored one.
11 5 PMA "Missing settings"
One of the setting structures has been corrupted in the
non-volatile memory.
12 55 PMA, R "Incompatible EPROM/FLASH SW"
The revision number of the downloaded SW in flash differs
from the SW revision number in EPROM
(for example if EPROM SW is R1.1 and downloaded SW is
R2.0).
13 5 PMA, R "Checksum error in downloaded SW"
The downloaded software has been corrupted.
14 3 PMA, R "Initialization errors"
The initialization phase failed.
15 69 PMA, R "Setup inconsistency"
Bookkeeping data of backed up units is corrupted (While
this is on, it is recommended not to replace any units with
compatible ones because it is not guaranteed that the new
unit inherits all of the old unit’s settings).

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

169
36 SCP

SPT GPT Status SPT Description


16 36 PMA, S "Start permission denied"
No permission to start. The unit is not in its correct place.
17 72 PMA "No backup settings from unit in address 1"
No backup settings from the unit in address 1.
18 72 PMA "No backup settings from unit in address 2"
No backup settings from the unit in address 2.
19 72 PMA "No backup settings from unit in address 3"
No backup settings from the unit in address 3.
20 72 PMA "No backup settings from unit in address 4"
No backup settings from the unit in address 4.
21 72 PMA "No backup settings from unit in address 5"
No backup settings from the unit in address 5.
22 72 PMA "No backup settings from unit in address 6"
No backup settings from the unit in address 6.
23 72 PMA "No backup settings from unit in address 7"
No backup settings from the unit in address 7.
24 72 PMA "No backup settings from unit in address 8"
No backup settings from the unit in address 8.
25 72 PMA "No backup settings from unit in address 9"
No backup settings from the unit in address 9.
26 72 PMA "No backup settings from unit in address 10"
No backup settings from the unit in address 10.
27 72 PMA "No backup settings from unit in address 11"
No backup settings from the unit in address 11.
28 72 PMA "No backup settings from unit in address 12"
No backup settings from the unit in address 12.
29 72 PMA "No backup settings from unit in address 13"
No backup settings from the unit in address 13.
30 72 PMA "No backup settings from unit in address 14"
No backup settings from the unit in address 14.
31 72 PMA "No backup settings from unit in address 15"
No backup settings from the unit in address 15.
32 72 PMA "No backup settings from unit in address 16"
No backup settings from the unit in address 16.
33 72 PMA "No backup settings from unit in address 17"
No backup settings from the unit in address 17.
34 72 PMA "No backup settings from unit in address 18"
No backup settings from the unit in address 18.
35 72 PMA "No backup settings from unit in address 19"
No backup settings from the unit in address 19.
36 72 PMA "No backup settings from unit in address 20"
No backup settings from the unit in address 20.
37 72 PMA "No backup settings from unit in address 21"
No backup settings from the unit in address 21.
38 72 PMA "No backup settings from unit in address 22"
No backup settings from the unit in address 22.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

170
36 SCP

SPT GPT Status SPT Description


39 72 PMA "No backup settings from unit in address 23"
No backup settings from the unit in address 23.
40 72 PMA "No backup settings from unit in address 24"
No backup settings from the unit in address 24.
41 72 PMA "No backup settings from unit in address 25"
No backup settings from the unit in address 25.
42 72 PMA "No backup settings from unit in address 26"
No backup settings from the unit in address 26.
43 72 PMA "No backup settings from unit in address 27"
No backup settings from the unit in address 27.
44 72 PMA "No backup settings from unit in address 28"
No backup settings from the unit in address 28.
45 72 PMA "No backup settings from unit in address 29"
No backup settings from the unit in address 29.
46 72 PMA "No backup settings from unit in address 30"
No backup settings from the unit in address 30.
47 72 PMA "No backup settings from unit in address 31"
No backup settings from the unit in address 31.
48 72 PMA "No backup settings from unit in address 32"
No backup settings from the unit in address 32.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

171
37 SCU, CCU

37 SCU, CCU
SPT GPT Status SPT Description
1 1 PMA "SW unpredicted"
This fault condition should never occur (or is not yet
supported).
2 2 PMA "Reset"
There has been a unit reset (detected always after the
power-up of the unit).
3 4 DMA "VB 1: + 5 V (BUS1)"
The VB 1 voltage is below the threshold limit (about 4.6 V
depending on the calibration and the A/D resolution).
4 4 DMA "VB 2: + 5 V (BUS2)"
The VB 2 voltage is below the threshold limit (about 4.6 V
depending on the calibration and the A/D resolution).
5 4 DMA "Vcc 1"
The bus interface supply voltage is below the threshold
limit (about 4.6 V depending on the calibration and the A/D
resolution).
6 4 PMA "Power + 5 V"
The board logic supply voltage is below the threshold limit
(about 4.6 V depending on the calibration and the A/D
resolution).
7 4 PMA "Power +12 V"
The board 12 V supply voltage is below the threshold limit
(about 11.3 V depending on the calibration and the A/D
resolution).
8 4 PMA "Power -10 V"
The board negative supply voltage is above the threshold
limit (about -9.0 V depending on the calibration and the
A/D resolution).
9 4 PMAS "Prog V0"
The voltage is below the threshold limit (about 11.3 V
depending on the calibration and the A/D resolution).
10 4 PMA "Prog V1"
The flash programming voltage is below the threshold limit
(about 11.3 V depending on the calibration and the A/D
resolution).
11 5 PMA "RAM fault"
A background process has detected a RAM location where
the read value does not match the written test pattern.
12 5 PMA "EPROM fault"
The calculated check sum does not match the stored one.
13 5 PMA "Flash write error"
Error when writing to the flash memory (main bank).
14 5 PMA "Flash copy error"
Error when writing to the flash memory (shadow bank).

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

172
37 SCU, CCU

SPT GPT Status SPT Description


15 5 PMA "Flash erase error"
Error during the erase of the flash memory (shadow bank).
16 5 PMA "Flash duplicate error"
Duplicated parameters (the same ID) detected during the
start-up.
17 5 PMA "Flash shadow error"
The shadow bank of the flash is not erased during the start-up.
18 5 PMA "Flash check sum error"
The calculated check sum does not match the stored one.
19 5 PMA "Missing settings"
One of the setting structures has been corrupted in the
non-volatile memory.
20 3 PMA, S "Installation error"
The inventory must be created.
21 8 PMA, S "Missing unit"
A registered unit is not in its place.
22 9 MEI "Extra unit"
There is a unit which has not been registered as part of the
subrack inventory.
23 44 DMA "Local VTP Bus 1"
Problems detected in the local control bus 1. The local
control bus 2 is used permanently from now on. Test the
local control bus and clear the fault from the test window.
24 44 DMA "Local VTP Bus 2"
Problems detected in the local control bus 2. The local
control bus 1 is used permanently from now on. Test the
local control bus and clear the fault from the test window.
25 46 PMA, S "Faulty X-connection system"
Both of the redundant cross-connection units are faulty.
26 5 PMA "Flash list check sum error"
One of the flash lists (e.g. port descriptor list) has been
corrupted.
27 5 PMA "Incompatible EPROM/FLASH SW"
The downloaded software (in the flash) is not compatible
with the system software in EPROMs.
28 5 PMA "Chksum err in downloaded SW"
The downloaded software has been corrupted.
29 54 MEI "Forced state in SXU/CXU act."
One of the redundant cross-connection units has been forced
to be active. The automatic change-over is not possible.
30 45 DMA "Cluster VTP Bus 1"
Problems detected in the cluster control bus 1. The cluster
control bus 2 is used permanently from now on. Test the
cluster control bus and clear the fault from the test window.
31 45 DMA "Cluster VTP Bus 2"
Problems detected in the cluster control bus 2. The cluster
control bus 1 is used permanently from now on. Test the
cluster control bus and clear the fault from the test window.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

173
37 SCU, CCU

SPT GPT Status SPT Description


32 6 PMA, S "Missing subrack"
A registered slave subrack is not accessible through the
cluster control bus.
33 7 MEI "Extra subrack"
There is a slave subrack which has not been registered as part
of 8170 cluster node. The fault condition is not monitored.
34 4 PMA "Battery not ready"
The battery is not yet fully charged after a complete discharge
(the voltage has not yet reached about 50 V).
35 68 PMA "External alarm 1"
There is a contact closure between the pins 1 and 6 of the
alarm interface module SCL 415.
36 4 PMA "AC off"
The AC input voltage is not detected.
37 68 PMA "External alarm 2"
There is a contact closure between the pins 3 and 8 of the
alarm interface module SCL 415.
38 10 PMA "Incorrect/missing IF module"
The setup of SCU/CCU requires a specific interface module.
The setup or the module must be changed.
39 4 DMA "Loss of prot. power (fuse)"
There is at least one fault in the protected power supply. The
next fault in the power supply may be critical.
40 70 MEI "Authorized access"
Authorized access.
41 71 PMA "Unauthorized access attempt"
Unauthorized access attempted.
42 90 MEI "SXU 1 (Primary) activated"
The primary SXU unit is activated.
43 90 MEI "SXU 2 (Secondary) activated"
The secondary SXU unit is activated.
44 90 MEI " CXU-M 15 (Primary) activated "
CXU-M in slot 15 (Primary) has been activated.
45 90 MEI " CXU-M 31 (Secondary) activated "
CXU-M in slot 31 (Secondary) has been activated.
46 90 MEI "Secondary CXU-M active"
The redundant CXU-M is active.
47 4 MEI "Loss of PFU-A (Primary)"
PFU-A is not working.
48 4 MEI "Loss of PFU-B (Secondary)"
PFU-B is not working.
49 90 MEI "Delay has increased"
SCU/CCU polls SXU/CXU-M and their reply to the poll has
exceeded the answer time limit of 2 seconds.
50 90 PMA "Switch-over has happened because of long delay"
CCU polls CXU-M and its reply to CCU has exceeded the
answer time limit of 4 seconds after which CCU decides that
CXU-M is having troubles and makes a switch-over.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

174
37 SCU, CCU

SPT GPT Status SPT Description


51 4 PMA "RPU failed"
There is no input voltage, input voltage is too low or RPU
has a hardware fault.
52 4 PMA "RPU output over current"
At least one RPU output is overloaded. There is a short
circuit on the line to far end equipment, far end equipment
is overloading the line, far end equipment is faulty or ’RPU
failed’ alarm is active.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

175
38 SCU-H

38 SCU-H
SPT GPT Status SPT Description
1 1 PMA "SW unpredicted"
This fault condition should never occur (or is not yet
supported).
2 2 PMA "Reset"
There has been a unit reset (detected always after the
power-up of the unit).
3 4 DMA "Installation error"
The inventory must be created.
4 4 DMA "Power +5.0 V (PDF)"
SCU-H power module failure.
5 4 DMA "Power +12.0 V (PDF)"
SCU-H power module failure.
6 4 PMA "Power –10.0 V (PDF)"
SCU-H power module failure.
7 4 PMA "Power +3.3 V (PDF)"
SCU-H power module failure.
8 4 PMA "Power +5.0 V (Baseboard)"
SCU-H baseboard power failure.
9 4 PMAS "Power +5.1 V VCC1 (BUS)"
Node power failure.
10 4 PMA "Power +5.1 V VCC2 (BUS)"
Node power failure.
11 4 PMA "Power +3.3 V (Baseboard)"
SCU-H baseboard power failure.
12 4 PMA "Temperature (Baseboard)"
Temperature of SCU-H is below +5 or above +60 Celsius
degrees. This fault will go off if temperature is between +10
and +55 Celsius degrees.
13 4 PMA "Power +3.4 V VP3_1 (BUS)"
Node power failure.
14 4 PMA " Power +3.4 V VP3_3 (BUS)"
Node power failure.
21 8 PMA, S "Missing unit"
A registered unit is not in its place.
22 9 MEI "Extra unit"
There is a unit which has not been registered as part of the
subrack inventory.
32 6 PMA, S "Missing subrack"
A registered slave subrack is not accessible through the
cluster control bus.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

176
38 SCU-H

SPT GPT Status SPT Description


33 7 MEI "Extra subrack"
There is a slave subrack which has not been registered as part
of 8170 cluster node. The fault condition is not monitored.
40 5 PMA "RAM fault"
A background process has detected a RAM location where
the read value does not match the written test pattern.
41 5 PMA "SW chksum error on ROM" The calculated check sum does
not match the stored one in ROM.
42 5 PMA "SW chksum error on RAM"
The calculated check sum does not match the stored one in
RAM.
43 5 PMA, S "EEP(IO)ROM write error"
Error when writing to the memory.
44 5 PMA, S "EEP(IO)ROM check sum error"
The calculated check sum does not match the stored one in
EEPROM.
45 5 PMA, S "File system fatal error"
Flash system failed. Replace the unit with a spare unit.
46 5 MEI "File system bad block found"
One of the blocks in the flash system is not in use anymore.
47 5 PMA "Flash setup check sum error"
The calculated check sum does not match the stored one in
flash.
48 5 PMA "Flash list check sum error"
One of the flash lists (e.g. port descriptor list) has been
corrupted.
49 5 PMA "Missing settings"
One of the setting structures is missing from the non-volatile
memory.
50 5 PMA "Incompatible SW in ROM and FLASH"
The downloaded software (in the flash) is not compatible
with the system software in the ROM.
51 5 PMA, S "FAN/PFU-H EEP(IO)ROM check sum error"
The calculated check sum does not match the stored one in
FAN/PFU-H EEPROM.
60 68 DMA "I/O Input alarm"
The fault is activated by the input of the alarm I/O module.
70 10 PMA "Incorrect/missing IF module"
The setup of SCU-H requires a specific interface module.
The setup or the module must be changed.
80 44 DMA "Local VTP Bus 1"
Problems detected in the local control bus 1. The local
control bus 2 is used permanently from now on. Test the local
control bus and clear the fault from the test window.
81 44 DMA "Local VTP Bus 2"
Problems detected in the local control bus 2. The local
control bus 1 is used permanently from now on. Test the local
control bus and clear the fault from the test window.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

177
38 SCU-H

SPT GPT Status SPT Description


82 45 DMA "Cluster VTP Bus 1"
Problems detected in the cluster control bus 1. The cluster
control bus 2 is used permanently from now on. Test the
cluster control bus and clear the fault from the test window.
83 45 DMA "Cluster VTP Bus 2"
Problems detected in the cluster control bus 2. The cluster
control bus 1 is used permanently from now on. Test the
cluster control bus and clear the fault from the test window.
90 46 PMA, S "Faulty cross-connection system"
Both of the redundant cross-connection units are faulty.
91 54 MEI "Forced state in cross-connection unit activation"
One of the redundant cross-connection units has been forced
to be active. The automatic change-over is not possible.
100 70 MEI "Authorized access"
Authorized access.
101 71 PMA "Unauthorized access attempt"
Unauthorized access attempted.
110 90 MEI "SXU 1 (Primary) activated"
The primary SXU unit is activated.
111 90 MEI "SXU 2 (Secondary) activated"
The secondary SXU unit is activated.
112 90 MEI "CXU-M 15 (Primary) activated "
CXU-M in slot 15 (Primary) has been activated.
113 90 MEI "CXU-M 31 (Secondary) activated "
CXU-M in slot 31 (Secondary) has been activated.
114 90 MEI "Secondary CXU-M active"
The redundant CXU-M is active.
115 4 DMA "Loss of primary PFU"
The primary PFU is not working.
116 4 DMA "Loss of secondary PFU"
The secondary PFU is not working.
120 62 PMA, S "Fan unit failure"
Fan unit failure. Two or more fans are stopped.
121 62 DMA "Fan unit failure"
Fan unit failure. One fan is stopped.
130 3 PMA "Initialization errors"
The initialization phase failed.
131 69 PMA "Setup inconsistency"
Bookkeeping data of backed up units is corrupted (While
this is on, it is recommended not to replace any units with
compatible ones because it is not guaranteed that the new
unit inherits all of the old unit’s settings).
140 72 PMA "No backup settings (U1)"
No backup settings from the unit in address 1.
141 72 PMA "No backup settings (U2)"
No backup settings from the unit in address 2.
142 72 PMA "No backup settings (U3)"
No backup settings from the unit in address 3.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

178
38 SCU-H

SPT GPT Status SPT Description


143 72 PMA "No backup settings (U4)"
No backup settings from the unit in address 4.
144 72 PMA "No backup settings (U5)"
No backup settings from the unit in address 5.
145 72 PMA "No backup settings (U6)"
No backup settings from the unit in address 6.
146 72 PMA "No backup settings (U7)"
No backup settings from the unit in address 7.
147 72 PMA "No backup settings (U8)"
No backup settings from the unit in address 8.
148 72 PMA "No backup settings (U9)"
No backup settings from the unit in address 9.
149 72 PMA "No backup settings (U10)"
No backup settings from the unit in address 10.
150 72 PMA "No backup settings (U11)"
No backup settings from the unit in address 11.
151 72 PMA "No backup settings (U12)"
No backup settings from the unit in address 12.
152 72 PMA "No backup settings (U13)"
No backup settings from the unit in address 13.
153 72 PMA "No backup settings (U14)"
No backup settings from the unit in address 14.
154 72 PMA "No backup settings (U15)"
No backup settings from the unit in address 15.
155 72 PMA "No backup settings (U16)"
No backup settings from the unit in address 16.
156 72 PMA "No backup settings (U17)"
No backup settings from the unit in address 17.
157 72 PMA "No backup settings (U18)"
No backup settings from the unit in address 18.
158 72 PMA "No backup settings (U19)"
No backup settings from the unit in address 19.
159 72 PMA "No backup settings (U20)"
No backup settings from the unit in address 20.
160 72 PMA "No backup settings (U21)"
No backup settings from the unit in address 21.
161 72 PMA "No backup settings (U22)"
No backup settings from the unit in address 22.
162 72 PMA "No backup settings (U23)"
No backup settings from the unit in address 23.
163 72 PMA "No backup settings (U24)"
No backup settings from the unit in address 24.
164 72 PMA "No backup settings (U25)"
No backup settings from the unit in address 25.
165 72 PMA "No backup settings (U26)"
No backup settings from the unit in address 26.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

179
38 SCU-H

SPT GPT Status SPT Description


166 72 PMA "No backup settings (U27)"
No backup settings from the unit in address 27.
167 72 PMA "No backup settings (U28)"
No backup settings from the unit in address 28.
168 72 PMA "No backup settings (U29)"
No backup settings from the unit in address 29.
169 72 PMA "No backup settings (U30)"
No backup settings from the unit in address 30.
170 72 PMA "No backup settings (U31)"
No backup settings from the unit in address 31.
171 72 PMA "No backup settings (U32)"
No backup settings from the unit in address 32.
180 2 PMA "Ethernet chip reset"
Problems in Ethernet communication have caused Ethernet
chip to reset.
181 62 PMA,S "FAN unit missing"
FAN2 (RXS 808) unit is missing.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

180
39 SMH-U

39 SMH-U
SPT GPT Status SPT Description
1 1 PMA "SW unpredicted"
This fault condition should never occur (or is not yet
supported).
2 2 PMA "Reset"
There has been a unit reset (detected always after the
power-up of the unit).
3 11 PMA, S "Loss of protected signal"
In 1+1 protection mode both interfaces IF1 and IF2 have
faults which in unprotected mode have S status.
4 4 PMA "Power + 5 V"
The voltage is below the threshold limit
(about 4.6 V depending on the calibration and the A/D
resolution).
5 4 PMA "Power +12 V"
The voltage is below the threshold limit
(about 11.3 V depending on the calibration and the A/D
resolution).
6 4 PMA "Power -12V"
The voltage is above the threshold limit
(Voltage amount depends on the calibration and the A/D
resolution).
7 4 PMA, S "VPLL"
Not monitored.
8 38 PMA, S "Bus sync. fault"
No cross-connection bus synchronization detected.
11 5 PMA, S "RAM fault"
A background process has detected a RAM location where
the read value does not match the written test pattern.
12 5 PMA, S "EPROM fault"
The calculated check sum does not match the stored one.
13 5 PMA "Flash write error"
Error when writing to the flash memory (main bank).
14 5 PMA "Flash copy error"
Error when writing to the flash memory (shadow bank).
15 5 PMA "Flash erase error"
Error during the erase of the flash memory (shadow bank).
16 5 PMA "Flash duplicate error"
Duplicated parameters (the same ID) detected during the
start-up.
17 5 PMA "Flash shadow error"
The shadow bank of the flash is not erased during the start-up.
18 5 PMA, S "Flash check sum error"
The calculated check sum does not match the stored one.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

181
39 SMH-U

SPT GPT Status SPT Description


19 5 PMA, S "Missing settings"
One of the setting structures has been corrupted in the
non-volatile memory.
20 59 MEI, S "BTE Tx line test"
The fault is activated if the Tx-test pattern generator of the
BTE module is activated (used in the V.54 remote loop).
22 39 PMA, S "Tx clock fault"
The fault is activated if the interface module transmitting
clock phase locking to X-bus clock fails.
23 40 PMA, S "IA activity missing"
The fault is activated if the unit cannot find its locked
interface address on the cross-connection bus. SXU should
activate the IA on the bus if the interface is locked.
24 10 PMA, S "IF module missing"
The interface module defined in the settings is missing.
25 10 PMA, S "Wrong interface module"
There is a conflict between the installed module and the
settings.
26 57 MEI "NTU power off/local loop"
The fault is activated if the module used is BTE-384 and
wetting current is on and the received current value differs
in frequency of 1.5º4.5 Hz and the current value difference
is more than 1.5 mA.
27 12 PMA, S "If signal missing"
The signal level is below a specific level (the level depends
on the interface module used and the selected bit rate).
28 42 MEI, S "AIS from X-BUS"
The fault is activated if the frame synchronization word and
RAI from the X-bus and TS0 B2 changes between "0" and
"1" are missing.
29 23 MEI, S "Rx signal is AIS"
The fault is activated if 2 or less/2M mode or 8 or less/8M
mode zeros in a 2-frame period are recognized.
The fault is deactivated if 3 or more/2M mode or 12 or
more/8M mode zeros in a 2-frame period are recognized.
30 26 DMA "CRC -multiframe lost"
The fault is activated if framing can be found in the 2M
mode and the CRC multiframe alignment has been lost for
100…200 ms, or if in the 8M mode CRC alignment losses
have been found more than 6 times in a 3-second period due
to excessive block errors.
The fault is deactivated if in the 2M mode the multiframe
alignment has been found and in the 8M mode when no more
than one frame alignment lost due to excessive CRC block
errors in a 3-second period has been detected.
This fault indicates that the remote end most probably does
not use CRC.
31 26 PMA, S "Frame alignment lost by CRC"
See CCITT G.706 Frame alignment recovery
(2048 mode ≥ 915 CRC block errors detected).
32 24 PMA, S "Frame alignment lost"
See CCITT G.706 Loss of frame alignment.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

182
39 SMH-U

SPT GPT Status SPT Description


33 13 PMA, S "BER10E-3"
See ITU-T G.736. The bit error rate is calculated from faulty
frame alignment words or from code errors. The bit error rate
10E-3 limits from frame alignment words:
2048 kbit/s and n x 64 kbit/s count time 4 seconds
Count to activate alarm: 94
Count to deactivate alarm: 17
8448 kbit/s and count time 2 seconds
Count to activate alarm: 199
Count to deactivate alarm: 48
Error rate 10E-3 limits from code errors:
Count time 1 second
2048 kbit/s
Activation limit: 1973
Deactivation limit: 229
8448 kbit/s
Activation limit: 8296
Deactivation limit: 839
10E-3 alarm status depends on fault consequences (AIS
insertion).
34 13 DMA "BER10E-3"
See ITU-T G.736. The bit error rate is calculated from faulty
frame alignment words or from code errors. The bit error rate
10E-3 limits from frame alignment words:
2048 kbit/s and n x 64 kbit/s count time 4 seconds
Count to activate alarm: 94
Count to deactivate alarm: 17
8448 kbit/s and count time 2 seconds
Count to activate alarm: 199
Count to deactivate alarm: 48
Error rate 10E-3 limits from code errors:
Count time 1 second
2048 kbit/s
Activation limit: 1973
Deactivation limit: 229
8448 kbit/s
Activation limit: 8296
Deactivation limit: 839
10E-3 alarm status depends on fault consequences (AIS
insertion).
35 56 MEI "NTU line break"
The fault is activated if the module used is BTE-384 and
wetting current is on and the received current value is lower
than 1.2 mA.
36 56 MEI "NTU short circuit"
The fault is activated if the module used is BTE-384 and
wetting current is on and the received current value is higher
than 6.5 mA.
37 29 PMA, S "No response to NNM message"
The control channel of the interface is used and the neighbor
node supervision option of the interface is on and no NNM
(Neighbor Node Monitoring) message has been received
from the interface within 8 seconds.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

183
39 SMH-U

SPT GPT Status SPT Description


38 29 PMA, S "Own NNM messages received"
The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received
NNM message contains the same identification data as the
NNM message sent to the interface.
39 29 PMA, S "Wrong ID’s in NNM message"
The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received
NNM message contains unexpected neighbor identification
data.
40 27 MEI, S "IF back to equipment"
An interface loop is created in the interface module. It loops
transmitted data and the clock signal back to the interface
receiver.
41 27 MEI, S "MUX/DEMUX back to eq."
Similar to Interface back to equipment loop except that the
loop is made before the interface module on the GMH unit
base card.
42 27 MEI, S "MUX/DEMUX back to line"
Rx data is looped back to the interface transmitter. When the
HDLC channel is used, it works with this line loop. All other
bits are looped back to the interface.
43 27 MEI, S "Line loop made by neighbor"
This alarm is activated if the HDLC channel is in use and
MUX/DEMUX back to line loop has been made from the
remote end or the BTE module is used and remote end has
activated the V.54 loop.
44 27 MEI, S "Remote controlled line loop"
This alarm is activated if the HDLC channel is in use and
MUX/DEMUX back to line loop has been made to the
neighbor unit or the BTE module is used and the V.54 loop
has been made to the remote end.
45 43 MEI, S "AIS in signaling"
The fault is activated if a signal in the signaling timeslot
contains less than 2 zeros during a multiframe period.
46 43 MEI, S "AIS in signaling group A"
See above.
47 43 MEI, S "AIS in signaling group B"
See above.
48 43 MEI, S "AIS in signaling group C"
See above.
49 43 MEI, S "AIS in signaling group D"
See above.
50 25 PMA, S "MFrame alignment lost"
The fault is activated if two consecutive faulty multiframe
alignment words are received or if all signaling timeslots in
one multiframe contain only zeros ("0").
The fault is deactivated when the frame alignment is detected
and the first four bits of signaling timeslot are found to be
zeros ("0") and when the prior signaling timeslot had at least
one bit in state "1".

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

184
39 SMH-U

SPT GPT Status SPT Description


51 25 PMA, S "MFrame alignment lost, group A"
See above.
52 25 PMA, S "MFrame alignment lost, group B"
See above.
53 25 PMA, S "MFrame alignment lost, group C"
See above.
54 25 PMA, S "MFrame alignment lost, group D"
See above.
55 20 MEI, S "Frame far-end alarm"
The state of the far-end alarm bit TS0 B3 will be switched if
the opposite state is received in 3 consecutive frames. State
"1" for alarm.
Alarm status depends on fault consequences
(AIS insertion into the signaling timeslot).
56 20 MEI "Frame far-end alarm"
The state of the far-end alarm bit TS0 B3 will be switched if
the opposite state is received in 3 consecutive frames . State
"1" for alarm.
Alarm status depends on fault consequences
(AIS insertion into the signaling timeslot).
57 21 MEI, S "MFrame far-end alarm"
The state of signaling timeslot’s frame 0 B6 alarm bit will be
switched if the opposite state is received in 3 consecutive
frames. State "1" for alarm.
Alarm status depends on fault consequences
(AIS insertion into the signaling timeslot).
58 21 MEI "MFrame far-end alarm"
The state of signaling timeslot’s frame 0 B6 alarm bit will be
switched if the opposite state is received in 3 consecutive
frames. State "1" for alarm.
Alarm status depends on fault consequences
(AIS insertion into the signaling timeslot).
59 21 MEI, S "MFrame far-end alarm, group A"
The state of signaling timeslot’s frame 0 B6 alarm bit will be
switched if the opposite state is received in 3 consecutive
frames. State "1" for alarm.
Alarm status depends on fault consequences
(AIS insertion into the signaling timeslot).
60 21 MEI "MFrame far-end alarm, group A"
The state of signaling timeslot’s frame 0 B6 alarm bit will be
switched if the opposite state is received in 3 consecutive
frames. State "1" for alarm.
Alarm status depends on fault consequences
(AIS insertion into the signaling timeslot).
61 21 MEI, S "MFrame far-end alarm, group B"
The state of signaling timeslot’s frame 0 B6 alarm bit will be
switched if the opposite state is received in 3 consecutive
frames. State "1" for alarm.
Alarm status depends on fault consequences
(AIS insertion into the signaling timeslot).

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

185
39 SMH-U

SPT GPT Status SPT Description


62 21 MEI "MFrame far-end alarm, group B"
The state of signaling timeslot’s frame 0 B6 alarm bit will be
switched if the opposite state is received in 3 consecutive
frames. State "1" for alarm.
Alarm status depends on fault consequences
(AIS insertion into the signaling timeslot).
63 21 MEI, S "MFrame far-end alarm, group C"
The state of signaling timeslot’s frame 0 B6 alarm bit will be
switched if the opposite state is received in 3 consecutive
frames. State "1" for alarm.
Alarm status depends on fault consequences
(AIS insertion into the signaling timeslot).
64 21 MEI "MFrame far-end alarm, group C"
The state of signaling timeslot’s frame 0 B6 alarm bit will be
switched if the opposite state is received in 3 consecutive
frames. State "1" for alarm.
Alarm status depends on fault consequences
(AIS insertion into the signaling timeslot).
65 21 MEI, S "MFrame far-end alarm, group D"
The state of signaling timeslot’s frame 0 B6 alarm bit will be
switched if the opposite state is received in 3 consecutive
frames. State "1" for alarm.
Alarm status depends on fault consequences
(AIS insertion into the signaling timeslot).
66 21 MEI "MFrame far-end alarm, group D"
The state of signaling timeslot’s frame 0 B6 alarm bit will be
switched if the opposite state is received in 3 consecutive
frames. State "1" for alarm.
Alarm status depends on fault consequences
(AIS insertion into the signaling timeslot).
67 16 DMA "BER10E-6"
BER10E-6 error rate is calculated from CRC block errors
when bit rate ≥ 1024 kbit/s. Counting time is 10 seconds and
the limit for the fault condition depends on the bit rate used
(2048 limit is 10).
68 58 MEI "Faults masked/test"
The fault is activated when the interface Fault mask setting
is on
(all interface faults are cleared).
69 30 DMA "Frequency difference"
The measurement period is 15 seconds and the phase-drifting
limit is 5 ms. The fault is activated if the phase-drifting limit
has been exceeded in 3 measurements out of 4.
70 30 MEI "Buffer slip(s)/1 hour"
The fault is activated if one or more buffer slip(s) have been
detected during the last hour.
71 41 DMA "HDLC overlap with X-bus"
The fault is activated if the HDLC control channel bit(s) are
also used by the cross-connection bus.
72 41 DMA "MCLK RAI overlap with X-bus"
The fault is activated if the MCLK/RAI bit is also used by
the cross-connection bus.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

186
39 SMH-U

SPT GPT Status SPT Description


73 32 PMA, S "ASIC register error"
The fault is activated if the difference between write/read
configuration data of ASIC has been detected.
74 60 DMA "Performance event"
This fault is activated as a delta fault if the G.821 supervision
is used and at least one performance limit has been exceeded
in a 15-minute period.
75 48 PMA, S "Unavailable state"
The fault is activated if the G.821 supervision is used and
the state of the signal becomes unavailable (10 consecutive
SES seconds). The fault is deactivated when 10 consecutive
seconds not classified as SES have been detected.
76 69 PMA "Extended setting backup inconsistency"
Inconsistency in extended setting backup.
78 69 DMA "Port locking conflict"
The fault is activated if the cross-connection system has
the port descriptor but the interface is unlocked or the
cross-connection system does not have the port descriptor
although the interface is locked. Use lock/unlock.
79 53 MEI "Protection switch forced"
The unit is in 1+1 protected mode and the protection switch
has been forced to select signal from IF1 or IF2.
80 55 PMA "Incompatible EPROM/FLASH SW"
The downloaded software (in the flash) is not compatible
with the system software in EPROMs.
81 5 PMA "Chksum err in downloaded SW"
The downloaded software has been corrupted.
84 49 DMA "Noise margin alarm"
The quality of the line is not good enough for data
communications.
85 24 PMA, S "Loss of HDSL frame"
See ETSI TS 101 135 Loss of HDSL frame alignment.
86 75 PMA, S "Chain number conflict"
The existing numbering differs from the defined numbering
and renumbering operation is recommended.
87 114 PMA, S "UNAVAIL (G.826)"
A period of unavailable time begins at the onset of ten
consecutive SES events. These ten seconds are considered to
be part of unavailable time. A new period of available time
begins at the onset of ten consecutive non-SES events. These
ten seconds are considered to be part of available time.
88 114 PMA, S "UNAVAIL far end"
A period of far end unavailable time (only when
unidirectional performance collection used) begins at the
onset of ten consecutive far end SES events. These ten
seconds are considered to be part of far end unavailable time.
A new period of available time begins at the onset of ten
consecutive non-far end SES events. These ten seconds are
considered to be part of available time.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

187
39 SMH-U

SPT GPT Status SPT Description


89 49 DMA "QOS"
Quality of signal. 24-hour period.
At least one of SES, BBE or ES limits exceeded. Cleared
when the period changes.
90 49 DMA, S "QOSTR"
Quality of signal. 15-minute period.
At least one of limits ES, BBE , SES has been exceeded.
Cleared when found a period where none of the ES, BBE or
SES limits has been exceeded.
Note that ES and BBE have upper/lower limit so that the
upper must be exceeded to get a fault and the lower is used as
a limit when the fault is activated.
142 4 PMA "VB 2"
The VB 2 voltage is below the threshold limit.
143 4 PMA "VB 1"
The VB 1 voltage is below the threshold limit.
144 112 DMA, S "Excessive errors"
Once every second, block errors shall be compared with the
limit value. If errors count ≥ limit, the one second shall be
declared BAD, otherwise it shall be declared GOOD.
The Excessive errors shall be detected if M consecutive BAD
seconds have occurred.
The Excessive errors shall be cleared if M consecutive
GOOD seconds have occurred.
M value range 2..9.
145 103 DMA "Degraded errors"
Once every second, block errors shall be compared with the
limit value. If errors count ≥ limit, the one second shall be
declared BAD, otherwise it shall be declared GOOD.
The Degraded errors shall be detected if M consecutive BAD
seconds have occurred.
The Degraded errors shall be cleared if M consecutive GOOD
seconds have occurred.
M value range 2..9.
150 32 PMA, S "X-connect RAM fault"
A problem detected in configuring the cross-connect matrix.
152 28 PMA, S "Block IA fault"
Data transfer between the cross-connection and a specified
block (interface/port) does not work.
153 34 MEI "Loss of master clock locking"
The internal clock is used and the fallback list contains
entries.
154 34 MEI "Fallback list warning"
The lowest choice is used (there are more than one choice in
the fallback list).
155 34 PMA "Loss of external clock"
The external clock input is enabled but the clock, connected
to the input, is not acceptable.
156 34 PMA "Phase-locked loop alarm"
The phase-locked loop of the master clock cannot be locked
to any clock.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

188
39 SMH-U

SPT GPT Status SPT Description


157 35 MEI "External clock warning"
The external clock is included in the fallback list but the
external clock input is not enabled.
158 31 MEI "Clock far-end alarm choice 1"
The state of the choice 1 in the fallback list indicates the
clock far-end alarm.
159 31 MEI "Clock far-end alarm choice 2"
The state of the choice 2 in the fallback list indicates the
clock far-end alarm.
160 31 MEI "Clock far-end alarm choice 3"
The state of the choice 3 in the fallback list indicates the
clock far-end alarm.
161 31 MEI "Clock far-end alarm choice 4"
The state of the choice 4 of the fallback list indicates the
clock far-end alarm.
162 31 MEI "Clock far-end alarm choice 5"
The state of the choice 5 in the fallback list indicates the
clock far-end alarm.
170 5 PMA, S "Flash list check sum error"
One of the flash lists (e.g. port descriptor list) has been
corrupted.
172 32 PMA, S "ASIC latch error"
An ASIC setting cannot be corrected by a checking
background process.
173 32 MEI "ASIC latch warning"
An ASIC setting is corrected by a checking background
process.
178 35 MEI "Time controlled X-conn warning"
A delta fault is indicating a problem when switching
the time-controlled cross-connection on/off. Additional
information can be read from the error log of the time control
process.
179 5 MEI "X-connect flash list conflict"
A corrupted cross-connect record has been detected in the
non-volatile memory after the unit reset. The record has
been deleted.
180 5 MEI "PortDescr flash list conflict"
A corrupted port descriptor record has been detected in the
non-volatile memory after the unit reset. The record has
been deleted.
181 5 MEI "Swapped trunk flash list conflict"
A corrupted swap-trunk record has been detected in the
non-volatile memory after the unit reset. The record has
been deleted.
182 5 MEI "Passivated trunk flash list conflict"
A corrupted passivate-trunk record has been detected in the
non-volatile memory after the unit reset. The record has
been deleted.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

189
39 SMH-U

SPT GPT Status SPT Description


183 55 PMA, S "Missing application program"
There is no application program in the flash memory.
Download the latest version of the program.
232 68 DMA "I/O input alarm"
The fault is activated by the input of the Alarm I/O module.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

190
40 SMU (Tellabs ® 8120 Mini Nodes M, VM, C, VG, SBM 2048 V, SBM 2048 E)

40 SMU (Tellabs ® 8120 Mini Nodes M, VM, C, VG,


SBM 2048 V, SBM 2048 E)
SPT GPT Status SPT Description
1 1 PMA “SW unpredicted”
This fault condition should never occur (or is not yet
supported).
2 2 PMA “Reset”
There has been a unit reset (detected always after the
power-up of the unit).
3 11 PMA, S “Loss of protected signal”
In 1+1 protection mode both interfaces IF1 and IF2 have
faults which in unprotected mode have S status.
4 4 PMA “Power + 5 V”
The voltage is below the threshold limit
(about 4.6 V depending on the calibration and the A/D
resolution).
5 4 PMA “Power +12 V”
The voltage is below the threshold limit
(about 11.3 V depending on the calibration and the A/D
resolution).
6 4 PMA “Power –10 V”
The voltage is above the threshold limit
(about –9.0 V depending on the calibration and the A/D
resolution).
7 4 PMA, S “VPLL”
Not monitored.
8 38 PMA, S “Bus sync. Fault”
No cross-connection bus synchronization detected.
9 5 PMA, S Tx RAM error”
There is a difference between written and read data in the
Tx-data buffer RAM of the framed interface.
10 5 PMA, S “Rx RAM error”
There is a difference between written and read data in the Rx
data buffer RAM of the framed interface.
11 5 PMA, S “RAM fault”
A background process has detected a RAM location where
the read value does not match the written test pattern.
12 5 PMA, S “EPROM fault”
The calculated check sum does not match the stored one.
13 5 PMA “Flash write error”
Error when writing to the flash memory (main bank).
14 5 PMA “Flash copy error”
Error when writing to the flash memory (shadow bank).

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

191
40 SMU (Tellabs ® 8120 Mini Nodes M, VM, C, VG, SBM 2048 V, SBM 2048 E)

SPT GPT Status SPT Description


15 5 PMA “Flash erase error”
Error during the erase of the flash memory (shadow bank).
16 5 PMA “Flash duplicate error”
Duplicated parameters (the same ID) detected during the
start-up.
17 5 PMA “Flash shadow error”
The shadow bank of the flash is not erased during the start-up.
18 5 PMA, S “Flash check sum error”
The calculated check sum does not match the stored one.
19 5 PMA, S “Missing settings”
One of the setting structures has been corrupted in the
non-volatile memory.
20 59 MEI, S “BTE Tx line test”
The fault is activated if the Tx-test pattern generator of the
BTE module is activated (used in the V.54 remote loop).
22 39 PMA, S “Tx clock fault”
The fault is activated if the interface module transmitting
clock phase locking to X-bus clock fails.
23 40 PMA, S “IA activity missing”
The fault is activated if the unit cannot find its locked
interface address on the cross-connection bus. SXU should
activate the IA on the bus if the interface is locked.
24 10 PMA, S “IF module missing”
The interface module defined in the settings is missing.
25 10 PMA, S “Wrong interface module”
There is a conflict between the installed module and the
settings.
26 57 MEI “NTU power off/local loop”
The fault is activated if the module used is BTE-384 and
wetting current is on and the received current value differs
in frequency of 1.5º4.5 Hz and the current value difference
is more than 1.5 mA.
27 12 PMA, S “Rx signal missing”
The signal level is below a specific level (the level depends
on the interface module used and the selected bit rate).
28 42 MEI, S “AIS from X-BUS”
The fault is activated if the frame synchronization word and
RAI from the X-bus and TS0 B2 changes between “0” and
“1” are missing.
29 23 MEI, S “Rx signal is AIS”
The fault is activated if 2 or less/2M mode or 8 or less/8M
mode zeros in a 2-frame period are recognized.
The fault is deactivated if 3 or more/2M mode or 12 or
more/8M mode zeros in a 2-frame period are recognized.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

192
40 SMU (Tellabs ® 8120 Mini Nodes M, VM, C, VG, SBM 2048 V, SBM 2048 E)

SPT GPT Status SPT Description


30 26 DMA “CRC missing”
The fault is activated if framing can be found in the 2M
mode and the CRC multiframe alignment has been lost for
100…200 ms, or if in the 8M mode CRC alignment losses
have been found more than 6 times in a 3-second period due
to excessive block errors.
The fault is deactivated if in the 2M mode the multiframe
alignment has been found and in the 8M mode when no more
than one frame alignment lost due to excessive CRC block
errors in a 3-second-period has been detected.
This fault indicates that the remote end most probably does
not use CRC.
31 26 PMA, S “Frame alignment lost by CRC”
See CCITT G.706 Frame alignment recovery.
(2048 mode ≥ 915 CRC block errors detected).
32 24 PMA, S “Frame alignment lost”
See CCITT G.706 Loss of frame alignment.
33 13 PMA, S “BER10E-3”
See ITU-T G.736. The bit error rate is calculated from faulty
frame alignment words or from code errors. The bit error rate
10E-3 limits from frame alignment words:
2048 kbit/s and n x 64 kbit/s count time 4 seconds
Count to activate alarm: 94
Count to deactivate alarm: 17
8448 kbit/s and count time 2 seconds
Count to activate alarm: 199
Count to deactivate alarm: 48
Error rate 10E-3 limits from code errors:
Count time 1 second
2048 kbit/s
Activation limit: 1973
Deactivation limit: 229
8448 kbit/s
Activation limit: 8296
Deactivation limit: 839
10E-3 alarm status depends on fault consequences (AIS
insertion).
34 13 DMA “BER10E-3”
See ITU-T G.736. The bit error rate is calculated from faulty
frame alignment words or from code errors. The bit error rate
10E-3 limits from frame alignment words:
2048 kbit/s and n x 64 kbit/s count time 4 seconds
Count to activate alarm: 94
Count to deactivate alarm: 17
8448 kbit/s and count time 2 seconds
Count to activate alarm: 199
Count to deactivate alarm: 48
Error rate 10E-3 limits from code errors:
Count time 1 second
2048 kbit/s
Activation limit: 1973
Deactivation limit: 229
8448 kbit/s
Activation limit: 8296
Deactivation limit: 839
10E-3 alarm status depends on fault consequences (AIS
insertion).

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

193
40 SMU (Tellabs ® 8120 Mini Nodes M, VM, C, VG, SBM 2048 V, SBM 2048 E)

SPT GPT Status SPT Description


35 56 MEI “NTU line break”
The fault is activated if the module used is BTE-384 and
wetting current is on and the received current value is lower
than 1.2 mA.
36 56 MEI “NTU short circuit”
The fault is activated if the module used is BTE-384 and
wetting current is on and the received current value is higher
than 6.5 mA.
37 29 PMA, S “No response to NNM message”
The control channel of the interface is used and the neighbor
node supervision option of the interface is on and no NNM
(Neighbor Node Monitoring) message has been received
from the interface within 8 seconds.
38 29 PMA, S “Own NNM messages received”
The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received
NNM message contains the same identification data as the
NNM message sent to the interface.
39 29 PMA, S “Wrong ID’s in NNM message”
The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received
NNM message contains unexpected neighbor identification
data.
40 27 MEI, S “Loop: IF back to equipment”
An interface loop is created in the interface module. It loops
transmitted data and the clock signal back to the interface
receiver.
41 27 MEI, S “Loop: MUX/DEMUX back to eq.”
Similar to Interface back to equipment loop except that the
loop is made before the interface module on the GMH unit
base card.
42 27 MEI, S “Loop: MUX/DEMUX back to line”
Rx data is looped back to the interface transmitter. When the
HDLC channel is used, it works with this line loop. All other
bits are looped back to the interface.
43 27 MEI, S “Line loop made by neighbor”
This alarm is activated if the HDLC channel is in use and
MUX/DEMUX back to line loop has been made from the
remote end or the BTE module is used and remote end has
activated the V.54 loop.
44 27 MEI, S “Remote controlled line loop”
This alarm is activated if the HDLC channel is in use and
MUX/DEMUX back to line loop has been made to the
neighbor unit or the BTE module is used and the V.54 loop
has been made to the remote end.
45 43 MEI, S “AIS in signaling”
The fault is activated if a signal in the signaling timeslot
contains less than 2 zeros during a multiframe period.
46 43 MEI, S “AIS in signaling group A”
See above.
47 43 MEI, S “AIS in signaling group B”
See above.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

194
40 SMU (Tellabs ® 8120 Mini Nodes M, VM, C, VG, SBM 2048 V, SBM 2048 E)

SPT GPT Status SPT Description


48 43 MEI, S “AIS in signaling group C”
See above.
49 43 MEI, S “AIS in signaling group D”
See above.
50 25 PMA, S “Mframe alignment lost”
The fault is activated if two consecutive faulty multiframe
alignment words are received or if all signaling timeslots in
one multiframe contain only zeros (“0”).
The fault is deactivated when the frame alignment is detected
and the first four bits of signaling timeslot are found to be
zeros (“0”) and when the prior signaling timeslot had at least
one bit in state “1”.
51 25 PMA, S “Mframe alignment lost, group A”
The fault is activated if two consecutive faulty multiframe
alignment words are received or if all signaling timeslots in
one multiframe contain only zeros (“0”).
The fault is deactivated when the frame alignment is detected
and the first four bits of signaling timeslot are found to be
zeros (“0”) and when the prior signalling timeslot had at least
one bit in state “1”.
52 25 PMA, S “Mframe alignment lost, group B”
The fault is activated if two consecutive faulty multiframe
alignment words are received or if all signaling timeslots in
one multiframe contain only zeros (“0”).
The fault is deactivated when the frame alignment is detected
and the first four bits of signaling timeslot are found to be
zeros (“0”) and when the prior signaling timeslot had at least
one bit in state “1”.
53 25 PMA,S “Mframe alignment lost, group C”
The fault is activated if two consecutive faulty multiframe
alignment words are received or if all signaling timeslots in
one multiframe contain only zeros (“0”).
The fault is deactivated when the frame alignment is detected
and the first four bits of signaling timeslot are found to be
zeros (“0”) and when the prior signaling timeslot had at least
one bit in state “1”.
54 25 PMA, S “Mframe alignment lost, group D”
The fault is activated if two consecutive faulty multiframe
alignment words are received or if all signaling timeslots in
one multiframe contain only zeros (“0”).
The fault is deactivated when the frame alignment is detected
and the first four bits of signaling timeslot are found to be
zeros (“0”) and when the prior signaling timeslot had at least
one bit in state “1”.
55 20 MEI, S “Frame far-end alarm”
The state of the far-end alarm bit TS0 B3 will be switched if
the opposite state is received in 3 consecutive frames. State
“1” for alarm.
Alarm status depends on fault consequences
(AIS insertion into the signaling timeslot).

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

195
40 SMU (Tellabs ® 8120 Mini Nodes M, VM, C, VG, SBM 2048 V, SBM 2048 E)

SPT GPT Status SPT Description


56 20 MEI “Frame far-end alarm”
The state of the far-end alarm bit TS0 B3 will be switched if
the opposite state is received in 3 consecutive frames . State
“1” for alarm.
Alarm status depends on fault consequences
(AIS insertion into the signaling timeslot).
57 21 MEI, S “Mframe far-end alarm”
The state of signaling timeslot’s frame 0 B6 alarm bit will be
switched if the opposite state is received in 3 consecutive
frames. State “1” for alarm.
Alarm status depends on fault consequences
(AIS insertion into the signaling timeslot).
58 21 MEI “Mframe far-end alarm”
The state of signaling timeslot’s frame 0 B6 alarm bit will be
switched if the opposite state is received in 3 consecutive
frames. State “1” for alarm.
Alarm status depends on fault consequences
(AIS insertion into the signaling timeslot).
59 21 MEI, S “Mframe far-end alarm, group A”
See above.
60 21 MEI “Mframe far-end alarm, group A”
See above.
61 21 MEI, S “Mframe far-end alarm, group B”
See above.
62 21 MEI “Mframe far-end alarm, group B”
See above.
63 21 MEI, S “Mframe far-end alarm, group C”
See above.
64 21 MEI “Mframe far-end alarm, group C”
See above.
65 21 MEI, S “Mframe far-end alarm, group D”
See above.
66 21 MEI “Mframe far-end alarm, group D”
See above.
67 16 DMA “BER10E-6”
BER10E-6 error rate is calculated from CRC block errors
when bit rate ≥ 1024 kbit/s. Counting time is 10 seconds and
the limit for the fault condition depends on the bit rate used
(2048 limit is 10).
68 58 MEI “Faults masked/test”
The fault is activated when the interface Fault mask setting
is on
(all interface faults are cleared).
69 30 DMA “Frequency difference”
The measurement period is 15 seconds and the phase-drifting
limit is 5 ms. The fault is activated if the phase-drifting limit
has been exceeded in 3 measurements out of 4.
70 30 MEI “Buffer slip(s)/1 hour”
The fault is activated if one or more buffer slip(s) have been
detected during the last hour.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

196
40 SMU (Tellabs ® 8120 Mini Nodes M, VM, C, VG, SBM 2048 V, SBM 2048 E)

SPT GPT Status SPT Description


71 41 DMA “HDLC overlap with X-bus”
The fault is activated if the HDLC control channel bit(s) are
also used by the cross-connection bus.
72 41 DMA “MCLK RAI overlap with X-bus”
The fault is activated if the MCLK/RAI bit is also used by the
cross-connection bus.
73 32 PMA, S “ASIC register error”
The fault is activated if the difference between write/read
configuration data of ASIC has been detected.
74 60 DMA “G821 limit event”
This fault is activated as a delta fault if the G.821 supervision
is used and at least one performance limit has been exceeded
in a 15-minute period.
75 48 PMA “G821 unavailable state”
The fault is activated if the G.821 supervision is used and
the state of the signal becomes unavailable (10 consecutive
SES seconds). The fault is deactivated when 10 consecutive
seconds not classified as SES have been detected.
78 69 DMA “Port locking conflict”
The fault is activated if the cross-connection system has
the port descriptor but the interface is unlocked or the
cross-connection system does not have the port descriptor
although the interface is locked. Use lock/unlock.
79 53 MEI “Protection switch forced”
The unit is in 1+1 protected mode and the protection switch
has been forced to select signal from IF1 or IF2.
80 55 PMA “Incompatible EPROM/FLASH SW”
The downloaded software (in the flash) is not compatible with
the system software in EPROMs.
81 5 PMA “Chksum err in downloaded SW”
The downloaded software has been corrupted.
82 112 DMA, (S) "Excessive errors"
Once every second, block errors shall be compared with the
limit value. If errors count ≥ limit, the one second shall be
declared BAD, otherwise it shall be declared GOOD. The
Excessive errors shall be detected if M consecutive BAD
seconds have occurred. The Excessive errors shall be cleared
if M consecutive GOOD seconds have occurred. M value
range 2..9.
83 103 DMA, (S) "Degraded errors"
Once every second, block errors shall be compared with the
limit value. If errors count ≥ limit, the one second shall be
declared BAD, otherwise it shall be declared GOOD.
The Degraded errors shall be detected if M consecutive BAD
seconds have occurred.
The Degraded errors shall be cleared if M consecutive GOOD
seconds have occurred.
M value range 2..9.
85 12 PMA, S “Interface signal missing”
No carrier state of the baseband module. Faulty input signal
in case of the G.703 module.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

197
40 SMU (Tellabs ® 8120 Mini Nodes M, VM, C, VG, SBM 2048 V, SBM 2048 E)

SPT GPT Status SPT Description


86 27 MEI, S “Interface loop active”
Interface loop activated (by 8100 manager).
88 56 MEI "Wetting current high"
Wetting current high.
89 56 MEI "Wetting current low"
Wetting current low.
90 24 PMA, S “Loss of frame sync”
Loss of frame synchronization state in case of V.110 or X.30.
91 67 PMA “FAS-errors”
Frame synchronization word errors detected in case of V.110
or X.30.
92 25 PMA, S “Loss of multiframe sync”
Loss of multiframe synchronization state in case of V.110
or X.30.
93 30 DMA “Tx buffer alignment”
V.110 or X.30 buffer slip.
94 30 DMA “Rx buffer alignment”
V.110 or X.30 buffer slip.
95 42 MEI, S “AIS detected from network”
Alarm Indication Signal from the cross-connection bus.
96 67 PMA, S “Code errors from input”
Code errors (HDB3, AMI or G.703 codir/contra). No input
clock (NRZ).
97 22 DMA “CRC errors from far-end”
CRC errors detected at the far-end.
98 26 DMA “CRC errors from near-end”
CRC errors detected at the near-end.
99 30 DMA “Rx buffer slips”
Buffer slip in the 8100 system bus interface (n x 64 kbit/s).
100 30 DMA “Tx buffer slips”
Buffer slip in the 8100 system bus interface (n x 64 kbit/s).
101 40 PMA, S “IA activity missing”
The fault is activated if the unit cannot find its locked
interface address on the cross-connection bus. SXU should
activate the IA on the bus if the interface is locked.
102 20 MEI, S “Alarm from far-end”
Alarm bit set in V.110 or X.30 frame.
110 32 PMA, S “ASIC register err in V110”
Error detected in ASIC. HW error in the V110 block of ASIC.
111 32 PMA, S “ASIC register err in RL”
Error detected in ASIC. HW error in the RL block of ASIC.
112 32 PMA, S “ASIC register err in PMP”
Error detected in ASIC. HW error in the PMP block of ASIC.
113 32 PMA, S “ASIC register err in CRP”
Error detected in ASIC. HW error in the CRP block of ASIC.
114 32 PMA, S “ASIC register err in IRP”
Error detected in ASIC. HW error in the IRP block of ASIC.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

198
40 SMU (Tellabs ® 8120 Mini Nodes M, VM, C, VG, SBM 2048 V, SBM 2048 E)

SPT GPT Status SPT Description


115 32 PMA, S “ASIC register err in IFM”
Error detected in ASIC. HW error in the IFM block of ASIC.
116 32 PMA, S “ASIC register err in SYNTE”
Error detected in ASIC. HW error in the SYNTE block of
ASIC.
117 32 PMA, S “ASIC register err in CK”
Error detected in ASIC. HW error in the CK block of ASIC.
118 32 PMA, S “ASIC register err in CIF”
Error detected in ASIC. HW error in the CIF block of ASIC.
120 27 MEI, S “Local loop or test active”
Local loop or test activated (by 8100 manager).
121 27 MEI, S “V.54 loop active”
The V.54 loop activated (by an interface signal or from
far-end).
122 10 PMA, S “Wrong interface module”
There is a conflict between the installed module and the
settings.
123 50 MEI, S “105 off in input”
The 105 signal is off in input and the 105 supervision is
selected in parameters.
124 57 MEI “Power off in input”
Incoming data signal (103) is not within the ITU-T
specifications.
127 58 MEI, S “Faults masked/test”
The fault is activated when the interface Fault mask setting
is on
(all interface faults are cleared).
130 48 MEI, S “G821 unavailable state”
The fault is activated if the G.821 supervision is used and
the state of the signal becomes unavailable (10 consecutive
SES seconds). The fault is deactivated when 10 consecutive
seconds not classified as SES have been detected.
131 5 PMA, S “RL state program error”
Remote loop state program is not stored (HW error).
132 60 MEI “G821 limit event”
This fault is activated as a delta fault if the G.821 supervision
is used and at least one performance limit has been exceeded
in a 15-minute period.
150 32 PMA, S “X-connect RAM fault”
A problem detected in configuring the cross-connect matrix.
152 28 PMA, S “Block IA fault”
Data transfer between the cross-connection and a specified
block (interface/port) does not work.
153 34 MEI “Loss of master clock locking”
The internal clock is used and the fallback list contains entries.
154 34 MEI “Fallback list warning”
The lowest choice is used (there are more than one choice in
the fallback list).

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

199
40 SMU (Tellabs ® 8120 Mini Nodes M, VM, C, VG, SBM 2048 V, SBM 2048 E)

SPT GPT Status SPT Description


155 34 PMA “Loss of external clock”
The external clock input is enabled but the clock, connected
to the input, is not acceptable.
156 34 PMA “Phase-locked loop alarm”
The phase-locked loop of the master clock cannot be locked
to any clock.
157 35 MEI “External clock warning”
The external clock is included in the fallback list but the
external clock input is not enabled.
158 31 MEI “Clock far-end alarm choice 1”
The state of the choice 1 in the fallback list indicates the
clock far-end alarm.
159 31 MEI “Clock far-end alarm choice 2”
The state of the choice 2 in the fallback list indicates the
clock far-end alarm.
160 31 MEI “Clock far-end alarm choice 3”
The state of the choice 3 in the fallback list indicates the
clock far-end alarm.
161 31 MEI “Clock far-end alarm choice 4”
The state of the choice 4 in the fallback list indicates the
clock far-end alarm.
162 31 MEI “Clock far-end alarm choice 5”
The state of the choice 5 in the fallback list indicates the
clock far-end alarm.
170 5 PMA, S “Flash list check sum error”
One of the flash lists (e.g. port descriptor list) has been
corrupted.
172 32 PMA, S “ASIC latch error”
An ASIC setting cannot be corrected by a checking
background process.
173 32 MEI “ASIC latch warning”
An ASIC setting is corrected by a checking background
process.
178 35 PMA “Time controlled X-conn warning”
A delta fault is indicating a problem when switching
the time-controlled cross-connection on/off. Additional
information can be read from the error log of the time control
process.
179 5 MEI “X-connect flash list conflict”
A corrupted cross-connect record has been detected in the
non-volatile memory after the unit reset. The record has been
deleted.
180 5 MEI “PortDescr flash list conflict”
A corrupted port descriptor record has been detected in the
non-volatile memory after the unit reset. The record has been
deleted.
181 5 MEI “Swp trk flash list conflict”
A corrupted swap-trunk record has been detected in the
non-volatile memory after the unit reset. The record has been
deleted.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

200
40 SMU (Tellabs ® 8120 Mini Nodes M, VM, C, VG, SBM 2048 V, SBM 2048 E)

SPT GPT Status SPT Description


182 5 MEI “Pass trk flash list conflict”
A corrupted passivate-trunk record has been detected in the
non-volatile memory after the unit reset. The record has been
deleted.
183 55 PMA, S “Missing application program”
There is no application program in the flash memory.
Download the latest version of the program.
185 62 MEI "Cooling fan alarm"
Fan does not work properly.
186 4 PMA, S “Power –5 V”8
The voltage is above the threshold limit
(about –4.6 V depending on the calibration and the A/D
resolution).
187 62 PMA, S “Channel board fault”8
Wrong board.
188 3 PMA, S “SMU configuration conflict” 8
HW does not support the current configuration.
190 38 PMA, S “Bus sync. Fault”
No cross-connection bus synchronization detected.
191 40 PMA, S “Bus IA activity missing, VF” 8
The interface address is not activated on the cross-connection
bus by SXU.
193 32 PMA, S “ASIC register error”
The fault is activated if the difference between write/read
configuration data of ASIC has been detected.
192 40 PMA, S “Bus IA activity missing, Sig.”8
The interface address is not activated on the cross-connection
bus by the SXU.
194 32 PMA, S “Unit HW fault”8
A hardware fault in the base unit.
195 10 PMA, S “Conflict in module type”8
The defined module type in the settings does not match the
actual module type in the hardware.
3 196 PMA, S “Provisioning error”8
A provisioning parameter value is not within specified range
or there is a module type conflict.
27 197 MEI, S “Unit loop”8
The unit loop is active – all channels are looped back to the
interfaces.
62 198 PMA, S “Module HW fault”8
Fault in the interface module.
62 199 PMA, S “Module HW fault”8
Fault in the interface module.
58 200 MEI “Faults masked”8
Faults are masked (alarms are not generated as consequences
of fault conditions).

8SBM 2048 V, Tellabs 8120 mini VM, Tellabs 8120 mini C

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

201
40 SMU (Tellabs ® 8120 Mini Nodes M, VM, C, VG, SBM 2048 V, SBM 2048 E)

SPT GPT Status SPT Description


64 201 DMA “IF input level error”8
The input signal level is not within the limits of parameters.
65 202 DMA “IF output level error”8
The output signal level is not within the limits of parameters.
27 203 MEI, S “IF loop to user”8
The interface loop is active (back to the interface).
27 204 MEI, S “IF loop to net”8
The interface loop is active (back to the cross-connection).
27 205 MEI, S “IF testing”8
Not monitored.
63 206 MEI, S “IF blocked off”8
The interface has been blocked from the use.
66 207 DMA “IF signaling error”8
Not monitored.
38 220 PMA, S “Bus sync. Fault”8
No cross-connection bus synchronization detected.
32 222 PMA, S “ASIC register error”8
The fault is activated if the difference between write/read
configuration data of ASIC has been detected.
40 221 PMA, S “Bus IA activity missing, VF”8
The interface address is not activated on the cross-connection
bus by SXU.
32 223 PMA, S “Unit HW fault”8
A hardware fault in the base unit.
10 224 PMA, S “Conflict in module type” 8
The defined module type in the settings does not match the
actual module type in the hardware.
69 225 PMA “Port conflict”8
A conflict in port descriptors between the unit and SXU.
62 226 PMA, S “Module HW fault” 8
Fault in the interface module.
62 227 PMA, S “Module HW fault” 8
Fault in the interface module.
38 228 PMA “MSYN missing”8
The ADPCM circuits cannot be used.
58 230 MEI “Faults masked” 8
Faults are masked (alarms are not generated as consequences
of fault conditions).
10 231 PMA, S “Conflict in module type” 9
The defined alarm IO module type in the settings does not
match the actual module type in the hardware.
68 232 DMA “I/O Input Alarm” 10
Alarm module input indication.

9Tellabs 8120 mini VG, SBM 2048 E


10Tellabs 8120 mini VG, SBM 2048 E

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

202
41 SMU (Tellabs ® 8120 Mini Node PM)

41 SMU (Tellabs ® 8120 Mini Node PM)


SPT GPT Status SPT Description
1 1 PMA, R “SW unpredicted”
This fault condition should never occur (or is not yet
supported).
2 2 PMA, R “Reset”
There has been a unit reset (detected always after the
power-up of the unit).
3 11 PMA, S, R “Loss of protected signal”
In 1+1 protection mode both interfaces IF1 and IF2 have
faults which in unprotected mode have S status.
4 4 PMA, R “Power + 5 V”
The voltage is below the threshold limit
(about 4.6 V depending on the calibration and the A/D
resolution).
5 4 PMA, R “Power +12 V”
The voltage is below the threshold limit
(about 11.3 V depending on the calibration and the A/D
resolution).
6 4 PMA, R “Power –10 V”
The voltage is above the threshold limit
(about –9.0 V depending on the calibration and the A/D
resolution).
7 4 PMA, S, R “VPLL”
Not monitored.
8 38 PMA, S, R “Bus sync. Fault”
No cross-connection bus synchronization detected.
9 5 PMA, S, R Tx RAM error”
There is a difference between written and read data in the
Tx-data buffer RAM of the framed interface.
10 5 PMA, S, R “Rx RAM error”
There is a difference between written and read data in the Rx
data buffer RAM of the framed interface.
11 5 PMA, S, R “RAM fault”
A background process has detected a RAM location where
the read value does not match the written test pattern.
12 5 PMA, S, R “EPROM fault”
The calculated check sum does not match the stored one.
13 5 PMA, R “Flash write error”
Error when writing to the flash memory (main bank).
14 5 PMA, R “Flash copy error”
Error when writing to the flash memory (shadow bank).
15 5 PMA, R “Flash erase error”
Error during the erase of the flash memory (shadow bank).

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

203
41 SMU (Tellabs ® 8120 Mini Node PM)

SPT GPT Status SPT Description


16 5 PMA, R “Flash duplicate error”
Duplicated parameters (the same ID) detected during start-up.
17 5 PMA, R “Flash shadow error”
The shadow bank of the flash is not erased during start-up.
18 5 PMA, S, R “Flash check sum error”
The calculated check sum does not match the stored one.
19 5 PMA, S, R “Missing settings”
One of the setting structures has been corrupted in the
non-volatile memory.
20 1 PMA, R "Software error (POTS)"
21 1 PMA, R "Software error in sign. controller (POTS)"
The main processor has received an unknown message from
the Signaling Controller.
22 2 PMA, S, R "Reset in sign. controller"
There has been a reset in the Signaling Controller (detected
always after the power-up of the unit).
23 3 PMA, S, R "Setup error"
One of the setting structures has been corrupted in the
non-volatile memory.
24 4 PMA, R "-20 V (POTS)"
25 5 PMA, S, R "RAM fault in sign. controller"
A background process in the Signaling Controller has
detected a RAM location where the read value does not match
the written test pattern.
26 5 PMA, S, R "Flash fault in signaling controller"
The Signaling Controller has detected an error in its own
flash memory.
27 10 PMA, S, R "Missing POTS Module"
The interface module defined in the settings is missing.
28 10 PMA, S, R "Missing POTS Module"
The interface module defined in the settings is missing.
29 10 PMA, S, R "Conflict in POTS Module Type"
The module type defined in the settings does not match the
actual module type in the hardware.
30 10 PMA, S, R "Conflict in POTS Module Type"
The module type defined in the settings does not match the
actual module type in the hardware.
31 25 PMA, S, R "Loss of multiframe sync"
Loss of multiframe synchronization state detected by the
Signaling Controller
32 32 PMA, S, R "ASIC fault"
33 38 PMA, S, R "Bus sync fault"
No 8100 system bus synchronization from SXU detected.
34 40 PMA, S, R "IA activity missing"
The interface address is not activated on the cross-connection
bus by SXU.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

204
41 SMU (Tellabs ® 8120 Mini Node PM)

SPT GPT Status SPT Description


35 62 MEI, R "HW strapping conflict with SW"
The strapping info of the base unit PCB is not what the
software expects. Maybe the software is installed in a wrong
unit.
36 62 PMA, S, R "HW Fault in POTS Module"
Hardware does not work as expected.
37 62 PMA, S, R "HW Fault in POTS Module"
Hardware does not work as expected.
38 62 PMA, S, R ”No response from sign. controller”
A timeout occurred when waiting response from the Signaling
Controller.
39 62 PMA, S, R "Error message from sign. controller"
The Signaling Controller returned an error to test message
(other than RAM or flash error).
40 62 DMA, R "Setup conflict"
Information stored in the setup is self-contradictory.
41 4 PMA, R "Temperature high"
Input air is too warm or fan is broken. All channels are
blocked to save hardware.
43 32 PMA, S, R "X-Connect RAM Fault"
44 28 PMA, S, Y "Block 1 IA Fault"
45 28 PMA, S, Y "Block 2 IA Fault"
46 28 PMA, S, Y "Block 3 IA Fault"
47 28 PMA, S, Y "Block 4 IA Fault"
48 28 PMA, S, Y "POTS IA Fault"
50 34 MEI "Loss of Master Clock Locking"
The holdover clock is used and the fallback list contains
entries.
51 34 MEI "Fallback List Warning"
The lowest choice is used (there are more than one choice in
the fallback list).
52 34 PMA, R "Loss of External Clock"
The external clock input is enabled but the clock, connected
to input, is not acceptable.
53 34 PMA, R "Phase Locked Loop Alarm"
The phase-locked loop of the master clock cannot be locked
to any clock.
54 34 MEI "External Clock Warning"
The external clock is included in the fallback list but the
external clock input is disabled.
55 31 MEI, Y "Clock Far End Alarm of Choice 1"
56 31 MEI, Y "Clock Far End Alarm of Choice 2"
57 31 MEI, Y "Clock Far End Alarm of Choice 3"
58 31 MEI, Y "Clock Far End Alarm of Choice 4"
59 31 MEI, Y "Clock Far End Alarm of Choice 5"

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

205
41 SMU (Tellabs ® 8120 Mini Node PM)

SPT GPT Status SPT Description


60 5 PMA, S, R "Flash List Check Sum Error"
One of the flash lists (e.g. port descriptor list) has been
corrupted.
61 32 PMA, S, R "ASIC Latch Error"
ASIC setting cannot be corrected by checking the background
process.
62 32 MEI "ASIC Latch Warning"
ASIC setting is corrected by checking the background
process.
63 35 PMA "Time Controlled X-Connect Warning"
A delta fault indicating a problem when switching
time-controlled cross-connection on/off. Additional
information can be read from the error log of the time control
process.
64 5 MEI "X-Connect Flash List Conflict"
A corrupted cross-connect record has been detected in the
non-volatile memory after the unit reset. The record has been
deleted.
65 5 MEI "PortDesc Flash List Conflict"
A corrupted port descriptor record has been detected in the
non-volatile memory after unit reset. The record has been
deleted.
66 5 MEI "Swapped Trunk Flash List Conflict"
A corrupted swap-trunk record has been detected in the
non-volatile memory after unit reset. The record has been
deleted.
67 5 MEI "Passivated Trunk Fls List Conflict"
A corrupted passivate-trunk record has been detected in the
non-volatile memory after the unit reset. The record has been
deleted.
68 55 PMA, S, R "Missing application program"
Downloaded software is missing.
69 62 MEI, R "Cooling fan alarm"
Fan does not work properly.
70 4 PMA, S, R "Power -5V"
The voltage is above the threshold limit
(about –4.6 V depending on the calibration and the A/D
resolution).
71 62 PMA, S, R "Channel Board Fault"
Wrong board.
72 3 PMA, S, R "SMU Configuration Conflict"
HW does not support the current configuration.
75 59 MEI, S, Y "BTE Tx Line Test"
The fault is activated if the Tx-test pattern generator of the
BTE module is activated (used in V.54 remote loop).
77 39 PMA, S, R "Tx Clock Fault"
The fault is activated if the interface module transmitting
clock phase locking to X-bus clock fails.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

206
41 SMU (Tellabs ® 8120 Mini Node PM)

SPT GPT Status SPT Description


78 40 PMA, S, R "IA Activity Missing"
The fault is activated if the unit cannot find its locked interface
address on the cross-connection bus. SXU should activate IA
on the bus if the interface is locked.
79 10 PMA, S, R "IF Module Missing"
The interface module defined in the settings is missing.
80 10 PMA, S, R "Wrong IF Module"
There is a conflict between the installed module and the
settings.
81 57 MEI, Y "NTU Power Off"
82 12 PMA, S, R "IF Signal Missing"
The signal level is below a specific level (the level depends
on the interface module used and the selected bit rate).
83 42 MEI, S, Y "AIS from X-BUS"
The fault is activated if the frame synchronization word and
RAI from the X-bus and TS0 B2 changes between "0" and
"1" are missing.
84 23 MEI, S, Y "Rx Signal Is AIS"
The fault is activated if 2 or less/2M mode or 8 or less/8M
mode zeros in a 2-frame period are recognized. The fault is
deactivated if 3 or more/2M mode or 12 or more/8M mode
zeroes in a 2-frame period are recognized.
85 26 DMA, R "CRC-Multiframe Lost"
86 26 PMA, S, R "Frame Alignment Is Lost by CRC"
87 24 PMA, S, R "Frame Alignment Is Lost"
88 13 PMA, S, R "BER10E-3"
89 13 DMA, R "BER10E-3"
90 56 MEI, Y "NTU Line Break"
The fault is activated if the module used is BTE 232 and
wetting current is on and the received current value is lower
than 1.2 mA.
91 56 MEI, Y "NTU Short Circuit"
The fault is activated if the module used is BTE 232 and
wetting current is on and received current value is higher
than 6.5 mA.
92 29 PMA, S, R "No Response to NNM Message"
The control channel of the interface is used and the neighbor
node supervision option of the interface is on and no NNM
(Neighbor Node Monitoring) message has been received from
the interface within 8 seconds.
93 29 PMA, S, R "Own NNM Messages Received"
The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received
NNM message contains the same identification data as the
NNM message sent to the interface.
94 29 PMA, S, R "Wrong ID’s in NNM Message"
The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received
NNM message contains unexpected neighbor identification
data.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

207
41 SMU (Tellabs ® 8120 Mini Node PM)

SPT GPT Status SPT Description


95 27 MEI, S, Y "Interface Back to Equipment"
An interface loop is created in the interface module. It loops
transmitted data and the clock signal back to the interface
receiver.
96 27 MEI, S, Y "MUX/DEMUX Back to Equipment"
Similar to ’Interface back to equipment’ loop except that the
loop is made before the interface module in the GMH unit
base card.
97 27 MEI, S, Y "MUX/DEMUX Back to Line"
Rx data is looped back to the interface transmitter. When the
HDLC channel is used, it works with this line loop. All other
bits are looped back to the interface.
98 27 MEI, S, Y "Line Loop Made by Neighbor"
This alarm is activated if the HDLC channel is in use and
MUX/DEMUX back to the line loop has been activated from
the remote end, or the BTE module is used and the remote
end has activated the V.54 loop.
99 27 MEI, S, Y "Remote Controlled Line Loop"
This alarm is activated if the HDLC channel is in use and
MUX/DEMUX back to line loop has been made to the
neighbor unit, or the BTE module is used and the V.54 loop
has been made to the remote end.
100 43 MEI, S, Y "AIS in Signaling"
The fault is activated if a signal in the signaling timeslot
contains less than 2 zeros during a multiframe period.
101 43 MEI, S, Y "AIS in Signaling Group A"
The fault is activated if a signal in the signaling timeslot
contains less than 2 zeros during a multiframe period.
102 43 MEI, S, Y "AIS in Signaling Group B"
The fault is activated if a signal in the signaling timeslot
contains less than 2 zeros during a multiframe period.
103 43 MEI, S, Y "AIS in Signaling Group C"
The fault is activated if a signal in the signaling timeslot
contains less than 2 zeros during a multiframe period.
104 43 MEI, S, Y "AIS in Signaling Group D"
The fault is activated if a signal in the signaling timeslot
contains less than 2 zeros during a multiframe period.
105 25 PMA, S, R "MFrame Alignment Lost"
The fault is activated if two consecutive faulty multiframe
alignment words are received or if all signaling time slots
in one multiframe contain only zeros ("0"). The fault is
deactivated when the frame alignment is detected and the first
four bits of the signaling timeslot are found to be zeros ("0")
and when the prior signaling timeslot had at least one bit in
state "1".
106 25 PMA, S, R "MFrame Alignment Lost in Group A"
See above.
107 25 PMA, S, R "MFrame Alignment Lost in Group B"
See above.
108 25 PMA, S, R "MFrame Alignment Lost in Group C"
See above.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

208
41 SMU (Tellabs ® 8120 Mini Node PM)

SPT GPT Status SPT Description


109 25 PMA, S, R "MFrame Alignment Lost in Group D"
See above.
110 20 MEI, S, Y "Frame Far End Alarm"
The state of the far-end alarm bit TS0 B3 will be switched
if the opposite state is received in 3 consecutive frames.
State "1" is used for alarm. Alarm status depends on fault
consequences (AIS insertion into the signaling timeslot).
111 20 MEI, Y "Frame Far End Alarm"
See above.
112 21 MEI, S, Y "MFrame Far End Alarm"
The state of signaling timeslot’s frame 0 B6 alarm bit will
be switched if the opposite state is received in 3 consecutive
frames. State "1" is used for alarm. Alarm status depends on
fault consequences (AIS insertion into the signaling timeslot).
113 21 MEI, Y "MFrame Far End Alarm"
See above.
114 21 MEI, S, Y "MFrame Far End Alarm in Group A"
See above.
115 21 MEI, Y "MFrame Far End Alarm in Group A"
See above.
116 21 MEI, S, Y "MFrame Far End Alarm in Group B"
See above.
117 21 MEI, Y "MFrame Far End Alarm in Group B"
See above.
118 21 MEI, S, Y "MFrame Far End Alarm in Group C"
See above.
119 21 MEI, Y "MFrame Far End Alarm in Group C"
See above.
120 21 MEI, S, Y "MFrame Far End Alarm in Group D"
See above.
121 21 MEI, Y "MFrame Far End Alarm in Group D"
See above.
122 16 DMA, R "BER10E-6"
BER10E-6 error rate is calculated from CRC block errors
when bit rate ≥ 1024 kbit/s. Counting time is 10 seconds and
the limit for the fault condition depends on the bit rate used
(2048 limit is 10).
123 58 MEI, Y "Fault Mask"
124 30 DMA, R "Frequency Difference"
The measurement period is 15 seconds and the phase-drifting
limit is 5 *s. The fault is activated if the phase-drifting limit
has been exceeded in 3 measurements out of 4.
125 30 MEI, RB "Buffer Slip"
The fault is activated if one or more buffer slip(s) have been
detected during the last hour.
126 41 DMA, R "HDLC Overlap with X-BUS"
The fault is activated if the HDLC control channel bit(s) are
also used by the cross-connection bus.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

209
41 SMU (Tellabs ® 8120 Mini Node PM)

SPT GPT Status SPT Description


127 41 DMA, R "Master Clock Rai Overlap with XBus"
The fault is activated if the MCLK/RAI bit is also used by the
cross-connection bus.
128 32 DMA, S, R "ASIC Register Error"
The fault is activated if the difference between write/read
configuration data of ASIC has been detected.
129 69 DMA, R "Port Locking Conflict"
The fault is activated if the SXU has the port descriptor but the
unit interface is unlocked, or the SXU does not have the port
descriptor although the interface is locked. Use lock/unlock.
130 112 PMA, S, R "Excessive Errors"
131 103 DMA, R "Degraded errors"
134 53 MEI, R "Protection Switch Forced"
The unit is in 1+1 protected mode and the protection switch
has been forced to select signal from IF1 or IF2.
135 55 PMA, R "Incompatible EPROM/Flash SW"
The fault is activated if there is downloaded software in the
flash but the revision is wrong (for example if EPROM SW is
r5.5 and downloaded SW is r6.1).
136 5 PMA, R "Chksum Err in Downloaded SW"
The downloaded software has been corrupted.
137 60 DMA "Performance Event"
138 48 PMA, S "Unavailable State"
139 60 DMA "Performance Event"
140 48 PMA, S "Unavailable State"
141 114 PMA, S "Unavail (G.826)"
142 114 PMA, S "Unavail Far End"
143 49 DMA "QOS"
144 49 DMA, S, R "QOSTR"
145 57 MEI, Y "NTU Power Off"
146 11 PMA, S, R "Loss of Protected Signal"
147 12 PMA, S, R "Rx Signal Missing"
148 49 DMA, R "Noise Margin Alarm"
The quality of the line is not good enough for data
communications.
149 24 PMA, S, R "Loss of HDSL Frame"
See ETSI TS 101 135 Loss of HDSL frame alignment.
150 12 DMA, R "Rx-Signal Missing"
151 23 MEI, S, Y "Rx-Signal is AIS"
152 24 PMA, S, R "Frame Alignment is Lost"
153 20 MEI, S, Y "Frame Far End Alarm"
154 26 DMA, R "CRC Missing"

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

210
41 SMU (Tellabs ® 8120 Mini Node PM)

SPT GPT Status SPT Description


155 68 DMA, R "Door Open"
Indicates that the modem door, e.g. 8110 OTU-2M is open
(8110 OTU-2M is connected to the QMH interface).
156 68 DMA, R "Customer Alarm 1"
157 68 DMA, R "Customer Alarm 2"
158 75 PMA, S, R "Chain Number Conflict"
The existing numbering differs from the defined numbering.
Re-numbering operation is recommended.
160 24 PMA, S, R "FSA Loss of Frame Sync"
161 67 PMA, Y "FAS-Errors"
162 25 PMA, S, R "MFS Loss of Multiframe Sync"
163 30 DMA, R "TXADJ Tx Buffer Alignment"
164 30 DMA, R "RXADJ Rx Buffer Alignment"
165 42 MEI, S, R "AIS Detected from Network"
166 67 PMA, S, R "CERR Code Errors from Input"
167 22 DMA, R "CRC_FAR Crc Errors from Far End"
168 26 DMA, R "CRC_NEAR Crc Errors from Near End"
169 30 DMA, R "RX_SLIP Rx Buffer Slips"
170 30 DMA, R "TX_SLIP Tx Buffer Slips"
171 40 PMA, S, R "BUS IA Activity Missing"
172 20 MEI, S, Y "Alarm from Far End"
173 32 PMA, S, R "V110 ASIC Register Error"
174 32 PMA, S, R ”RL ASIC Register Error"
175 32 PMA, S, R "PMP ASIC Register Error"
176 32 PMA, S, R "CRP ASIC Register Error"
177 32 PMA, S, R "IRP ASIC Register Error"
178 32 PMA, S, R "IFM ASIC Register Error"
179 32 PMA, S, R "SYNTE ASIC Register Error"
180 32 PMA, S, R "CK ASIC Register Error"
181 32 PMA, S, R "CIF ASIC Register Error"
182 27 MEI, S, Y "Local Loop On"
183 27 MEI, S, Y "V54 Loop On"
184 10 PMA, S, R "Wrong Interface Module"
There is a conflict between the installed module and the
settings.
185 50 MEI, S, R "105 Off in Input"
The 105 signal is off in input and the 105 supervision is
selected in parameters.
186 57 MEI, Y "Power Off in Input"
187 58 MEI, S, Y "Faults Masked"
188 60 MEI "G821 Alarms"

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

211
41 SMU (Tellabs ® 8120 Mini Node PM)

SPT GPT Status SPT Description


190 5 PMA, S, R "RL State Program"
204 10 PMA, S, R "Conflict in Module Type"
The defined module type in the settings does not match the
actual module type in the hardware.
205 68 DMA, R "I/O Input Alarm"
The fault is activated by the input of the alarm I/O module.
206 68 DMA, R "I/O Input Alarm"
The fault is activated by the input of the alarm I/O module.
207 68 DMA, R "I/O Input Alarm"
The fault is activated by the input of the alarm I/O module.
208 68 DMA, R "I/O Input Alarm"
The fault is activated by the input of the alarm I/O module.
211 27 MEI, S, Y "Interface Loop to Net"
The interface loop is active (back to the cross-connection).
212 27 MEI, S, Y "Equipment Loop to Net"
The equipment loop is active (back to the cross-connection).
213 27 MEI, S, Y "Line Loop to User"
The line loop is active (back to the interface).
214 42 MEI, S, Y "AIS from Network"
AIS is detected from network.
215 62 PMA, S, R "Fault in Interface"
Line interface does not work as expected.
216 62 MEI, S "IF Blocked off"
The interface has been blocked from use.
217 69 MEI, Y "Filter coefficients missing"
The coefficients of the Signal Processing Codec Filter
(SICOFI) are missing. Default coefficients are used.
218 58 MEI, Y "Faults masked"

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

212
42 STU-56

42 STU-56
SPT GPT Status SPT Description
1 1 PMA "SW unpredicted"
This fault condition should never occur (or is not yet
supported).
2 2 PMA, S "Reset"
There has been a unit reset (detected always after the
power-up of the unit).
3 3 PMA, S "Setup error"
One of the setting structures has been corrupted in the
non-volatile memory.
4 4 PMA "Power +5V"
The voltage is below the threshold limit (about 4.75 V
depending on the calibration and the A/D resolution).
5 4 PMA "Power +12V"
The voltage is below the threshold limit (about 11.4 V
depending on the calibration and the A/D resolution).
6 4 PMA "Power -5V"
The voltage is above the threshold limit (about -4.5 V
depending on the calibration and the A/D resolution).
7 4 PMA "Power -10V"
The voltage is above the threshold limit (about -9.5 V
depending on the calibration and the A/D resolution).
8 5 PMA, S "RAM fault"
A background process has detected a RAM location where
the read value does not match the written test pattern.
9 5 PMA, S "EPROM fault"
The calculated checksum does not match the stored one.
10 5 PMA, S "Flash write error"
Error when writing to the flash memory (main bank).
11 5 PMA, S "Flash copy error"
Error when writing to the flash memory (shadow bank).
12 5 PMA, S "Flash erase error"
Error during the erase of the flash memory (shadow bank).
13 5 PMA, S "Flash duplicate error"
Duplicated parameters (the same ID) detected during the
start-up.
14 5 PMA, S "Flash shadow error"
The shadow bank of the flash is not erased during the start-up.
15 5 PMA, S "Flash check sum error"
The calculated check sum does not match the stored one.
16 55 PMA, S "Incompatible FLASH SW"
The downloaded software (in the flash) is not compatible with
the system software in EPROM.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

213
42 STU-56

SPT GPT Status SPT Description


17 55 PMA, S "Checksum error in Dnl program"
The downloaded software has been corrupted.
18 29 MEI "Wrong neighbor"
The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received
NNM message contains unexpected neighbor identification
data
19 29 MEI "No response to NNM message"
The control channel of the interface is used and the neighbor
supervision option of the interface is on and no NNM
(Neighbor Node Monitoring) message has been received from
the interface within 8 seconds.
20 29 MEI "Own NNM message received"
The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received
NNM message contains the same identification data as the
NNM message sent to the interface.
21 58 MEI "Fault mask on"
Faults are masked.
22 12 PMA, S "Loss of line signal"
Data communication through the U interface is broken
23 13 PMA, S "BER 10E-3"
Bit error rate estimated to exceed 10E-3. Bit error rate is
calculated from the multiframe CRC block errors of the U
interface.
24 42 MEI, S "AIS detected from network"
Signal from the line is Alarm Indication Signal.
25 26 DMA "CRC faults"
CRC faults in the U interface
26 27 MEI "Analog loop to interface"
Analog loop to interface in the U interface
27 27 MEI "Digital loop"
Digital loop in the U interface
28 60 DMA "G.821 limit event"
This fault is activated as a delta fault if the G.821 supervision
is used and at least one performance limit has been exceeded
in a 15-minute period.
29 48 PMA, S "G.821 unavailable state"
The fault is activated if the G.821 supervision is used and
the state of signal becomes unavailable (10 consecutive SES
seconds). The fault is deactivated when 10 consecutive
seconds not classified as SES have been found.
30 24 PMA, S "FSA loss of frame sync"
Loss of frame synchronization state in case of V.110 or X.30
31 67 PMA "FAS errors"
Frame synchronization word errors detected in case of V.110
or X.30
32 25 PMA, S "MFS loss of multiframe sync"
Loss of multiframe synchronization state in case of V.110
or X.30

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

214
42 STU-56

SPT GPT Status SPT Description


33 30 DMA "Tx buffer alignment"
V.110 or X.30 buffer slip
34 30 DMA "Rx buffer alignment"
V.110 or X.30 buffer slip
35 42 MEI, S "AIS detected from network"
Alarm Indication Signal from the cross-connection bus
36 67 PMA, S "CERR code errors from input"
Code errors (HDB3, AMI or G.703 codir/contra). No input
clock (NRZ)
37 26 PMA, S "CRC errors from near-end"
CRC errors detected at the near-end
38 20 MEI, S "Alarm from far-end"
Alarm bit set in V.110 or X.30 frame
39 32 PMA, S "ASIC register error in V.110"
Error detected in the ASIC hardware
40 57 PMA, S "DTE power off"
DTE power off.
41 60 DMA "G.821 limit event"
This fault is activated as a delta fault if the G.821 supervision
is used and at least one performance limit has been exceeded
in a 15-minute period.
42 48 PMA, S "G.821 unavailable state"
The fault is activated if the G.821 supervision is used and
the state of signal becomes unavailable (10 consecutive SES
seconds). The fault is deactivated when 10 consecutive
seconds not classified as SES have been found.
43 27 MEI, S "Local loop"
V.54 loop 3. The transmitter of NTU is connected to receiver.
44 27 MEI, S "Digital loop"
V.54 loop 2. NTU loops received data back to the line. Loop
is activated by the keys of NTU.
45 27 MEI, S "Digital loop made by neighbor"
The same loop than the digital loop, but it is activated by a
neighbor. The neighbor unit uses management channel to
give a loop command.
46 27 MEI, S "Remote loop V.54"
V.54 loop 2 (digital loop) is formed in remote unit.
47 27 MEI, S "Remote loop B V.54"
V.54 loop 2 (digital loop) activated by remote unit.
48 59 MEI, S "Transmit & Receive test"
V.52 compliant 511-bit pattern is transmitted and errors in
receiver are counted.
49 5 MEI, S "RL state program error"
Remote loop state program error not stored (HW error).
50 50 PMA, S "105 off in DTE"
The 105 signal is off in DTE and the 105 supervision is
selected in IF parameters
51 10 PMA, S "Missing IF card"
Missing interface card.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

215
43 STU-1088, STU-2048

43 STU-1088, STU-2048
SPT GPT Status SPT Description
1 1 PMA "SW unpredicted"
This fault condition should never occur (or is not yet
supported).
2 2 PMA, S "Reset"
There has been a unit reset (detected always after the
power-up of the unit).
3 3 PMA, S "Setup error"
One of the setting structures has been corrupted in the
non-volatile memory.
4 4 PMA "Power +5V (Vcc)"
The voltage is below the threshold limit (about 4.75 V
depending on the calibration and the A/D resolution).
5 4 PMA "Power +12V"
The voltage is below the threshold limit (about 11.4 V
depending on the calibration and the A/D resolution).
6 4 PMA "Power -5V"
The voltage is above the threshold limit (about -4.5 V
depending on the calibration and the A/D resolution).
7 4 PMA "Power -10V"
The voltage is above the threshold limit (about -9.5 V
depending on the calibration and the A/D resolution).
8 5 PMA, S "RAM fault"
A background process has detected a RAM location where
the read value does not match the written test pattern.
9 5 PMA, S "EPROM fault"
The calculated checksum does not match the stored one.
10 5 PMA, S "Flash write error"
Error when writing to the flash memory (main bank).
11 5 PMA, S "Flash copy error"
Error when writing to the flash memory (shadow bank).
12 5 PMA, S "Flash erase error"
Error during the erase of the flash memory (shadow bank).
13 5 PMA, S "Flash duplicate error"
Duplicated parameters (the same ID) detected during the
start-up.
14 5 PMA, S "Flash shadow error"
The shadow bank of the flash is not erased during the start-up.
15 5 PMA, S "Flash check sum error"
The calculated check sum does not match the stored one.
16 55 PMA, S "Incompatible EPROM/FLASH SW"
The downloaded software (in the flash) is not compatible with
the system software in EPROM.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

216
43 STU-1088, STU-2048

SPT GPT Status SPT Description


17 55 PMA, S "Checksum error in downloaded SW"
The downloaded software has been corrupted.
18 10 PMA, S "Missing DTE interface module"
The DTE interface module is missing or incorrect.
19 12 PMA, S "Missing line signal"
No signal on the line.
20 12 PMA, S "Missing DTE signal"
No signal on DTE.
21 51 MEI "Line rate scanning"
NTU is searching the right line rate.
22 52 MEI "DTE rate scanning "
NTU is searching the right DTE rate (113 signal).
23 23 MEI, S "AIS in input signal"
Signal from the line is Alarm Indication Signal.
24 58 MEI "Fault mask on"
Faults are masked.
25 13 PMA, S "Signal quality alarm"
Not monitored.
26 27 MEI, S "Local loop"
V.54 loop 3. The transmitter of NTU is connected to receiver.
27 27 MEI, S "Digital loop"
V.54 loop 2. NTU loops received data back to the line. The
loop is activated by the keys of NTU.
28 27 MEI, S "Digital loop made by neighbor"
The same loop than the digital loop, but it is activated by a
neighbor. The neighbor unit uses management channel to
give a loop command.
29 27 MEI, S "Remote loop V.54"
V.54 loop 2 (digital loop) is formed in remote unit.
30 27 MEI, S "Remote loop B V.54"
V.54 loop 2 (digital loop) activated by remote unit.
31 59 MEI, S "Transmit & Receive test"
V.52 compliant 511-bit pattern is transmitted and errors in
receiver are counted.
32 27 MEI, S "Neighbor node loop"
NTU uses management channel to give a loop command to
the unit of the neighbor node (GMH).
33 20 MEI "Frame far-end alarm"
Frame is lost at the far-end.
34 29 PMA, S "Wrong neighbor"
The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received
NNM message contains unexpected neighbor identification
data.
35 29 PMA, S "No response to NNM msg"
The control channel of the interface is used and the neighbor
supervision option of the interface is on and no NNM
(Neighbor Node Monitoring) message has been received from
the interface within 8 seconds.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

217
43 STU-1088, STU-2048

SPT GPT Status SPT Description


36 29 PMA, S "Own NNM msg received"
The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received
NNM message contains the same identification data as the
NNM message sent to the interface.
37 26 DMA "CRC missing"
Frame alignment word is detected but CRC multiframe is not.
38 26 PMA, S "Frame align. lost by CRC"
See G.706 Frame alignment recovery.
39 24 PMA, S "Frame alignment lost"
See G.706 Loss of frame alignment.
40 13 PMA, S "BER more than 10-3"
Bit error rate is more than 10E-3. Bit error rate is calculated
from frame alignment words.
41 60 DMA "G.821 limit event"
This fault is activated as a delta fault if the G.821 supervision
is used and at least one performance limit has been exceeded
in a 15-minute period.
42 48 PMA, S "G.821 unavailable state"
The fault is activated if the G.821 supervision is used and
the state of signal becomes unavailable (10 consecutive SES
seconds). The fault is deactivated when 10 consecutive
seconds not classified as SES have been found.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

218
44 SXU-A, SXU-B, SXU-V

44 SXU-A, SXU-B, SXU-V

The faults with SPT from 100 to 241 apply only to SXU-V.

SPT GPT Status SPT Description


1 1 PMA, S "SW unpredicted"
This fault condition should never occur (or is not yet
supported).
2 2 PMA, S "Reset"
There has been a unit reset (detected always after the
power-up of the unit).
3 4 PMA, S "VB 2"
The VB 2 voltage is below the threshold limit (about 4.6 V
depending on the calibration and the A/D resolution).
4 4 PMA, S "VB 1"
The VB 1 voltage is below the threshold limit (about 4.6 V
depending on the calibration and the A/D resolution).
5 4 PMA, S "Power +5 V"
The board logic supply voltage is below the threshold limit
(about 4.6 V depending on the calibration and the A/D
resolution).
6 4 PMA, S "Power +12 V"
The board 12 V supply voltage is below the threshold limit
(about 11.3 V depending on the calibration and the A/D
resolution).
7 4 PMA, S "VPLL"
Not monitored.
8 4 PMA, S "Power -10 V"
The board negative supply voltage is above the threshold
limit (about -9.0 V depending on the calibration and the A/D
resolution).
9 5 PMA "Incompatible EPROM/FLASH SW"
The downloaded software (in the flash) is not compatible with
the system software in EPROMs.
10 5 PMA "Chksum err in downloaded SW"
The downloaded software has been corrupted.
11 5 PMA, S "RAM fault"
A background process has detected a RAM location where
the read value does not match the written test pattern.
12 5 PMA, S "EPROM fault"
The calculated check sum does not match the stored one.
13 5 PMA, S "Flash write error"
Error when writing to the flash memory (main bank).

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

219
44 SXU-A, SXU-B, SXU-V

SPT GPT Status SPT Description


14 5 PMA, S "Flash copy error"
Error when writing to the flash memory (shadow bank).
15 5 PMA, S "Flash erase error"
Error during the erase of the flash memory (shadow bank).
16 5 PMA, S "Flash duplicate error"
Duplicated parameters (the same ID) detected during the
start-up.
17 5 PMA, S "Flash shadow error"
The shadow bank of the flash is not erased during the start-up.
18 5 PMA, S "Flash check sum error"
The calculated check sum does not match the stored one.
19 5 PMA, S "Missing settings"
One of the setting structures has been corrupted in the
non-volatile memory.
20 32 PMA, S "X-connect RAM fault"
A problem detected in configuring the cross-connect matrix.
21 3 PMA, S "Installation error"
SXU does not belong to the inventory.
22 28 PMA, S "Unit IA fault"
Data transfer between SXU and a specified channel unit does
not work.
23 34 MEI "Loss of master clock locking"
The internal clock is used and the fallback list contains entries.
24 34 MEI "Fallback list warning"
The lowest choice is used (there are more than one choice in
the fallback list).
25 34 PMA "Loss of external clock"
The external clock input is enabled but the clock, connected
to the input, is not acceptable.
26 34 PMA "Phase-locked loop alarm"
The phase-locked loop of the master clock cannot be locked
to any clock.
27 34 MEI "External clock warning"
The external clock is included in the fallback list but the
external clock input is disabled.
28 31 MEI "Clock far-end alarm, choice 1"
The state of the choice 1 in the fallback list indicates the clock
far-end alarm.
29 31 MEI "Clock far-end alarm, choice 2"
The state of the choice 2 in the fallback list indicates the clock
far-end alarm.
30 31 MEI "Clock far-end alarm, choice 3"
The state of the choice 3 in the fallback list indicates the clock
far-end alarm.
31 31 MEI "Clock far-end alarm, choice 4"
The state of the choice 4 in the fallback list indicates the clock
far-end alarm.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

220
44 SXU-A, SXU-B, SXU-V

SPT GPT Status SPT Description


32 31 MEI "Clock far-end alarm, choice 5"
The state of the choice 5 in the fallback list indicates the clock
far-end alarm.
40 5 PMA, S "Flash list check sum error"
One of the flash lists (e.g. port descriptor list) has been
corrupted.
41 32 PMA, S "X-connect loop error"
The internal data loop test is not successful. The cross-connect
matrix may be faulty.
42 32 PMA, S "ASIC latch error"
An ASIC setting cannot be corrected by a checking
background process.
43 32 MEI "ASIC latch warning"
An ASIC setting is corrected by a checking background
process.
44 32 MEI "X-connect RAM A14 warning"
Not monitored.
45 33 DMA "X-connect bus 1 fault"
The cross-connect bus 1 is faulty. The bus 2 is used.
46 33 DMA "X-connect bus 2 fault"
The cross-connect bus 2 is faulty. The bus 1 is used.
47 33 PMA, S "X-connect bus alarm"
Both cross-connect buses are faulty. SXU tries to use both
buses in turn.
48 35 PMA "Time controlled X-conn warning"
A delta fault is indicating a problem when switching
the time-controlled cross-connection on/off. Additional
information can be read from the error log of the time control
process.
49 5 MEI "X-connect flash list conflict"
A corrupted cross-connect record has been detected in the
non-volatile memory after the unit reset. The record has been
deleted.
50 5 MEI "PortDescr flash list conflict"
A corrupted port descriptor record has been detected in the
non-volatile memory after the unit reset. The record has been
deleted.
51 5 MEI "Swp trk flash list conflict"
A corrupted swap-trunk record has been detected in the
non-volatile memory after the unit reset. The record has been
deleted.
52 5 MEI "Pass trk flash list conflict"
A corrupted passivate-trunk record has been detected in the
non-volatile memory after the unit reset. The record has been
deleted.
53 61 PMA "Reconfiguring X-conn DB"
The background protection process of the passive SXU has
detected that the cross-connect configuration is different in the
active and passive sides. The passive SXU is reconfiguring
itself.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

221
44 SXU-A, SXU-B, SXU-V

SPT GPT Status SPT Description


55 34 MEI "Unstable SSM"
SSM byte values are not valid.
56 34 MEI "Faulty clock source of choice 1 "
The state of the entry 1 of the fallback list is faulty.
57 34 MEI "Faulty clock source of choice 2 "
The state of the entry 2 in the fallback list is faulty.
58 34 MEI "Faulty clock source of choice 3 "
The state of the entry 3 in the fallback list is faulty.
59 34 MEI "Faulty clock source of choice 4 "
The state of the entry 4 in the fallback list is faulty.
60 34 MEI "Faulty clock source of choice 5 "
The state of the entry 5 in the fallback list is faulty.
61 34 PMA "Clock failure switchover fault "
A fault becomes active if the next three conditions are
fulfilled:
1. External clock is enabled.
2. External clock is in the fallback list.
3. Internal clock is in use (clocks at the FB list are not
reliable).
62 34 MEI "Fallback list entry 2 used "
The entry 2 of the fallback list is used.
63 34 MEI "Fallback list entry 3 used "
The entry 3 of the fallback list is used
64 34 MEI "Fallback list entry 4 used "
The entry 4 of the fallback list is used.
65 34 MEI "Fallback list entry 5 used "
The entry 5 of the fallback list is used
66 34 MEI "Internal clock used "
The internal clock is used as master clock for the node.
67 74 MEI "CCG communication fault "
SXU cannot communicate with the peer SXU in the far end
node of CCG (communication error?).
68 74 MEI "CCG EPS activation fault "
SXU cannot communicate with the peer EPS in the near end
node of CCG (communication error?).
69 114 MEI "CCG CMC fault "
Compressed Channel unusable for switching, xc fault.
70 82 MEI "CCG threshold alarm "
The number of free CLCs has decreased below threshold at
least once during the previous 15-minute period.
71 114 MEI "CCG blocking alarm "
Switch to CLC is blocked at least once during the previous
15-minute period
72 114 MEI "CCG switch request failed "
Switch to CLC failed to complete at least once during the
previous 15-minute period.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

222
44 SXU-A, SXU-B, SXU-V

SPT GPT Status SPT Description


73 89 MEI "Passive flash version fault"
Version of flash list in the passive SXU is older than in the
active SXU, or the passive SXU is not communicating with
the active one.
100 5 PMA, R, S ”ESX RAM Fault”
101 5 PMA, R, S ”Flash Write Error”
102 5 PMA, R, S ”Flash Erase Error”
103 5 PMA, R, S ”Flash Checksum error”
104 5 PMA, R, S ”ESX-717 HW Failure”
105 5 PMA, R ”ESX-717 DB Mismatch”
106 58 MEI, Y ”ESX Faults Masked”
150 131 MEI, Y ”Receiver Overrun”
151 167 MEI, Y ”Transmitter Under-run”
152 27 MEI, S, Y ”Port In Loopback”
160 74 PMA, R, S ”TV5-AUP DL Failure”
161 82 MEI, Y ”Capacity Threshold Exceeded”
170 74 PMA, R, S ”TV5-AUP DL Failure”
180 74 PMA, R, S ”TV5-AUP DL Failure”
181 62 DMA, Y ”Port Activation Failed”
190 1 PMA, R, S ”V5 Stack Internal Failure”
191 69 MEI, Y ”Interface ID mismatch”
192 69 MEI, Y ”Variant ID mismatch”
193 69 MEI, Y ”Variant Does Not Exist”
194 69 MEI, Y ”Attempt to Switch to Same Variant”
195 73 MEI, Y ”Protocol Discriminator Error”
196 73 MEI, Y ”L3 Address Error”
197 73 MEI, Y ”Message Type Unrecognized”
198 73 MEI, Y ”Out of Sequence Information Element”
199 73 MEI, Y ”Repeated Optional Information Element”
200 73 MEI, Y ”Mandatory Information Element Missing”
201 73 MEI, Y ”Unrecognized Information Element”
202 73 MEI, Y ”Optional Information Element Error”
203 73 MEI, Y ”Mandatory Information Element Error”
204 73 MEI, Y ”Optional Information Element Error”
205 73 MEI, Y ”Message not Compatible with Path State”
206 73 MEI, Y ”Repeated Mandatory Information Element”
207 73 MEI, Y ”Invalid Sequence Number Received”
208 73 MEI, Y ”Next Sequence Number Unavailable”
209 73 MEI, Y ”Message Received is Too Short”

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

223
44 SXU-A, SXU-B, SXU-V

SPT GPT Status SPT Description


210 73 MEI, Y ”Message Received is Too Long”
211 73 MEI, Y ”Too Many Information Elements”
212 73 MEI, Y ”Control Function Error”
213 73 MEI, Y ”Message Received During Out of Service State”
214 74 PMA, R, S ”Control DL Failure”
215 74 PMA, R, S ”PSTN DL Failure”
216 74 PMA, R, S ”Link Control DL Failure”
217 74 PMA, R, S ”BCC DL Failure”
218 74 PMA, R, S ”Protection DL Primary Failure”
219 74 PMA, R, S ”Protection DL Secondary Failure”
220 74 MEI, Y ”Tt Timer Expired”
221 74 MEI, Y ”T3 Timer Expired 3rd Time”
222 74 MEI, Y ”Timer T01 Expired 2nd Time”
223 74 MEI, Y ”Timer T02 Expired 2nd Time”
224 82 MEI, Y ”Capacity Threshold Exceeded”
230 69 MEI, Y, S ”Link ID Mismatch”
240 62 PMA, R, S ”Active C-channel Failure”
241 62 MEI, Y ”Active C-channel Protection Switch”

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

224
45 SXU-C

45 SXU-C
SPT GPT Status SPT Description
1 1 PMA, S "SW unpredicted"
This fault condition should never occur (or is not yet
supported).
2 2 PMA, S "Reset"
There has been a unit reset (detected always after the
power-up of the unit).
3 4 PMA, S "VB 2"
The VB 2 voltage is below the threshold limit (about 4.6 V
depending on the calibration and the A/D resolution).
4 4 PMA, S "VB 1"
The VB 1 voltage is below the threshold limit (about 4.6 V
depending on the calibration and the A/D resolution).
5 4 PMA, S "Power +5 V"
The board logic supply voltage is below the threshold limit
(about 4.6 V depending on the calibration and the A/D
resolution).
6 4 PMA, S "Power +12 V"
The board 12 V supply voltage is below the threshold limit
(about 11.3 V depending on the calibration and the A/D
resolution).
7 4 PMA, S "VPLL"
Not monitored.
8 4 PMA, S "Power -10 V"
The board negative supply voltage is above the threshold
limit (about -9.0 V depending on the calibration and the A/D
resolution).
9 5 PMA "Incompatible EPROM/FLASH SW"
The downloaded software (in the flash) is not compatible with
the system software in EPROMs.

10 5 PMA, S “Chksum err in downloaded SW"


The downloaded software has been corrupted.
11 5 PMA, S "RAM fault"
A background process has found a RAM location where the
read value does not match the written test pattern.
12 5 PMA, S "EPROM fault"
The calculated check sum does not match the stored one.
13 5 PMA, S "Flash write error"
Error when writing to the flash memory (main bank).
14 5 PMA, S "Flash copy error"
Error when writing to the flash memory (shadow bank).
15 5 PMA, S "Flash erase error"
Error during the erase of the flash memory (shadow bank).

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

225
45 SXU-C

SPT GPT Status SPT Description


16 5 PMA, S "Flash duplicate error"
Duplicated parameters (the same ID) found during the
start-up.
17 5 PMA, S "Flash shadow error"
The shadow bank of the flash is not erased during the start-up.
18 5 PMA, S "Flash check sum error"
The calculated check sum does not match the stored one.

19 5 PMA, S "Missing settings"


One of the setting structures has been corrupted in the
non-volatile memory.
20 32 PMA, S "X-connect RAM fault"
A problem detected in configuring the cross-connect matrix.
21 3 PMA, S "Installation error"
SXU does not belong to the inventory.
22 28 PMA, S "Unit IA fault"
Data transfer between SXU and a specified channel unit does
not work.
23 34 MEI "Loss of master clock locking"
The subrack clock cannot be locked to the cluster clock. The
internal clock is used.
24 34 MEI "Fallback list warning"
Not monitored.
25 34 PMA "Loss of external clock"
Not monitored.
26 34 PMA "Phase-locked loop alarm"
The phase-locked loop cannot be locked to any clock.
27 34 MEI "External clock warning"
Not monitored.
28 31 MEI "Clock far-end alarm, choice 1"
Not monitored.
29 31 MEI "Clock far-end alarm, choice 2"
Not monitored.
30 31 MEI "Clock far-end alarm, choice 3"
Not monitored.
31 31 MEI "Clock far-end alarm, choice 4"
Not monitored.
32 31 MEI "Clock far-end alarm, choice 5"
Not monitored.
33 5 PMA, S "Flash list check sum error"
One of the flash lists (e.g. port descriptor list) has been
corrupted.
34 32 PMA, S "Inter-subrack bus fault"
The inter-subrack bus (between the master subrack and the
slave subrack) does not work.
35 32 PMA, S "ASIC latch fault"
An ASIC setting cannot be corrected by a checking
background process.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

226
45 SXU-C

SPT GPT Status SPT Description


36 32 MEI "ASIC latch warning"
An ASIC setting is corrected by a checking background
process.
37 33 DMA "X-connect bus 1 fault"
The cross-connect bus 1 is faulty. The bus 2 is used.
38 33 DMA "X-connect bus 2 fault"
The cross-connect bus 2 is faulty. The bus 1 is used.
39 33 PMA, S "X-connect bus alarm"
Both cross-connect buses are faulty. SXU tries to use both
buses in turn.
40 5 MEI "X-connect flash list conflict"
A corrupted cross-connect record has been detected in the
non-volatile memory after the unit reset. The record has been
deleted.
41 5 MEI "PortDescr flash list conflict"
A corrupted port descriptor record has been detected in the
non-volatile memory after the unit reset. The record has been
deleted.
42 61 PMA "Reconfiguring X-conn flash DB"
The background protection process of the passive SXU has
detected that the cross-connect configuration is different in the
active and passive sides. The passive SXU is reconfiguring
itself.
43 61 MEI "Initializing X-conn RAM DB"
SXU-C is initializing itself after the reset.
44 5 MEI "Swp trk flash list conflict"
A corrupted swap-trunk record has been detected in the
non-volatile memory after the unit reset. The record has been
deleted.
45 5 MEI "Swp conn flash list conflict"
A corrupted swap-connection record has been detected in
the non-volatile memory after the unit reset. The record has
been deleted.
46 33 PMA, S "XBUS allocation integrity error"
XBUS allocation error.
47 33 PMA, S, V "Invalid ISB Cable Installation"
ISB cables are installed incorrectly. Check the installation
immediately.
48 32 MEI ”SXU-C ARAM Restore Event”
An internal ARAM memory consistency error has been
detected and fixed.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

227
46 Tellabs ® 6300 Managed Transport System Nodes

46 Tellabs ® 6300 Managed Transport System


Nodes
SPT Status SPT Description
0 MEI “Indeterminate”
The cause of the fault cannot be determined.
1 MEI, S “AIS”
Alarm indication signal.
2 PMA, S “Application subsystem failure”
Application subsystem failure
3 DMA “DEG”
Signal degraded.
4 MEI “RDI”
Remote defect indicator.
6 PMA, S “LOF”
Loss of frame alignment.
7 PMA, S “LOP”
Loss of pointer.
8 PMA, S “LOS”
Loss of signal. The loss of signal defect is declared when a supervised
signal has not had any transitions for a period of time or the signal indicating
degradation of level in the received signal is activated.
9 PMA, S “SLM”
Signal label mismatch. Received signal label is not valid.
10 PMA, S “Transmission error”
Transmission error.

12 DMA “DEG”
Degraded signal
13 PMA, S “TIM”
Received path trace identifier does not match the expected one.
15 PMA, S “Equipment malfunction”
Equipment malfunction
16 PMA, S “LOM”
Loss of multiframe alignment.
28 PMA, S “LOF”
Loss of frame alignment.
29 PMA, S “LOS”
Loss of signal. The loss of signal defect is declared when a supervised
signal has not had any transitions for a period of time or the signal indicating
degradation of level in the received signal is activated.
48 PMA, S “Software program error”
Software program error.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

228
46 Tellabs ® 6300 Managed Transport System Nodes

SPT Status SPT Description


50 DMA “Unacceptable temperature”
Unacceptable temperature.
57 DMA “Version mismatch”
Version mismatch.
58 DMA “Power problem”
Power problem.
62 DMA, S “Unit missing”
A registered unit is not in its place.
63 PMA, S “Unit type mismatch”
A registered unit type is not what is expected.
66 PMA, S “LOM”
Loss of multiframe alignment.
67 PMA, S ”LOP”
Loss of pointer.
68 DMA, S ”Loss of alignment”
Loss of alignment.
69 PMA, S ”Excessive errors”
Excessive errors.
70 PMA, S ”TIM”
Received path trace identifier does not match the expected one.
71 MEI, S ”AIS”
Alarm indication signal.
72 MEI ”RDI”
Remote defect indicator.
73 MEI, S ”SSF”
Server signal fail defect in above layer sets Server Signal Fail (SSF) to below
layer (a defect occurred in the upper layer activates an SSF fault in the lower
layer).
74 PMA, S ”SLM”
Signal label mismatch. Received signal label is not valid.
75 PMA, S ”UNEQ”
Received signal label in the unequipped state.
76 PMA, S ”Sequence mismatch”
Sequence mismatch.
77 PMA, S ”Max. differential delay exceeded”
Maximum differential delay exceeded.
78 DMA ”GFP EXI mismatch”
GFP EXI mismatch.
79 DMA ”GFP UPI mismatch”
GFP UPI mismatch.
80 PMA, S ”GFP loss of frame alignment”
GFP loss of frame alignment.
81 DMA "GFP loss of client signal"
GFP loss of client signal.
82 DMA "GFP loss of client synchronization"
GFP loss of client synchronization.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

229
46 Tellabs ® 6300 Managed Transport System Nodes

SPT Status SPT Description


85 PMA, S "LAPF frame mismatch"
LAPF frame mismatch.
86 PMA, S "LAPF LMI link down"
LAPF LMI link down.
87 PMA, S "LAPS frame mismatch"
LAPS frame mismatch.
88 PMA, S "Proprietary information missing"
Proprietary information missing.
91 DMA, S "Unit missing"
Unit missing.
92 PMA, S "Unit type mismatch"
Unit type mismatch.
93 PMA, S "MPLS OAM TTSI mismatch"
MPLS OAM TTSI mismatch.
94 DMA "MPLS OAM TTSI mismerge"
MPLS OAM TTSI mismerge.
95 PMA, S "MPLS OAM loss of connectivity"
MPLS OAM loss of connectivity.
96 DMA "MPLS OAM excess rate"
MPLS OAM excess rate.
97 PMA, S "Ethernet OAM link down"
Ethernet OAM link down.
99 MEI "Lock out of protection pending"
Lock out of protection pending.
100 MEI "Forced switch pending"
Forced switch pending.
101 DMA "Air compressor failure"
Air compressor failure detected.
102 DMA "Air conditioning failure"
Air conditioning failure detected.
103 DMA "Air dryer failure"
Air dryer failure detected.
104 DMA "Battery discharging"
Battery discharging detected.
105 DMA "Battery failure"
Battery failure detected.
106 PMA, S "Commercial power failure"
Commercial power failure detected.
107 DMA "Cooling fan failure"
Cooling fan failure detected.
108 PMA "Engine failure"
Engine failure detected.
109 DMA "Fire detector failure"
Fire detector failure detected.
110 DMA "Fuse failure"
Fuse failure detected.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

230
46 Tellabs ® 6300 Managed Transport System Nodes

SPT Status SPT Description


111 DMA "Generator failure"
Generator failure detected.
112 PMA "Low battery threshold"
Low battery threshold detected.
113 PMA "Pump failure"
Pump failure detected.
114 PMA "Rectifier failure"
Rectifier failure detected.
115 DMA "Rectifier high voltage"
Rectifier high voltage detected.
116 DMA "Rectifier low voltage"
Rectifier low voltage detected.
117 DMA "Failure in ventilation system"
Failure in ventilation system.
118 DMA "Enclosure door open"
Enclosure door is open.
119 PMA "Explosive gas"
Explosive gas detected.
120 PMA "Fire"
Fire detected.
121 PMA "Flood"
Flood detected.
122 DMA "High humidity"
High humidity detected.
123 DMA "High temperature"
High temperature detected.
124 DMA "High wind"
High wind detected.
125 DMA "Ice build up"
Ice build up detected.
126 PMA "Intrusion detection"
Intrusion detection.
127 PMA "Low fuel"
Low fuel detected.
128 DMA "Low humidity"
Low humidity detected.
129 DMA "Low cable pressure"
Low cable pressure detected.
130 DMA "Low temperature"
Low temperature detected.
131 DMA "Low water"
Low water detected.
132 PMA "Smoke"
Smoke detected.
133 PMA "Toxic gas"
Toxic gas detected.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

231
46 Tellabs ® 6300 Managed Transport System Nodes

SPT Status SPT Description


151 PMA "Storage capacity problem"
Storage capacity problem.
255 PMA “Network Element unavailable”
Network element is unavailable.
32002 PMA, S "Frequency out of range"
Frequency out of range.
32003 PMA, S "UNEQ"
Received signal label in the unequipped state.
32004 DMA "PLL out of lock"
PLL out of lock.
32005 PMA, S "TIM"
Received section trace identifier does not match the expected one.
32006 MEI, S "SSF"
Server signal fail defect in above layer sets Server Signal Fail (SSF) to below
layer (a defect occurred in the upper layer activates an SSF fault in the lower
layer).
32010 DMA "Receive power too high"
Receive power is too high.
32011 DMA "Receive power too low"
Receive power is too low.
32012 PMA, S "Optical transmit fail"
Optical transmit fail.
32013 DMA "Optical transmit degraded"
Optical transmit degraded.
32015 PMA, S "Loop back active"
Loop back is active.
32017 PMA, S "AIS insertion is forced"
AIS insertion is forced.
32018 PMA, S "Insertion test access connection is active"
Insertion test access connection is active.
32019 PMA, S “GFP type mismatch”
There is a Generic Framing Procedure (GFP) type mismatch.
32050 DMA “Loss of alignment”
Loss of alignment.
32052 PMA, S “Sequence indicator mismatch”
Sequence indicator mismatch.
32053 MEI "Link shut down"
Link shut down.
32054 MEI "Client signal failure"
Client signal failure.
32055 MEI, S "Port forced off"
Port forced off.
32056 PMA, S “Extension header identifier mismatch”
Extension header identifier mismatch.
32057 PMA “User payload identifier mismatch”
User payload identifier mismatch.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

232
46 Tellabs ® 6300 Managed Transport System Nodes

SPT Status SPT Description


32058 DMA “Total loss of capacity, TX”
Total loss of capacity, TX.
32059 DMA “Total loss of capacity, RX”
Total loss of capacity, RX.
32060 MEI “Partial loss of capacity, TX”
Partial loss of capacity, TX.
32061 MEI “Partial loss of capacity, RX”
Partial loss of capacity, RX.
32062 PMA, S “Sequence indicator out of range”
Sequence indicator out of range.
32063 PMA, S “Member not deskewable”
Member not deskewable.
32064 PMA, S “Member not deskewable”
Member not deskewable.
32065 DMA “Loss of continuity”
Loss of continuity.
32066 DMA “Unexpected MEG level”
Unexpected MEG level.
32067 DMA “MEG mismerged”
MEG mismerged.
32068 DMA “Unexpected MEP”
Unexpected MEP.
32069 DMA “Unexpected continuity check period”
Unexpected continuity check period.
32070 PMA, S “CRC error”
CRC error.
32071 DMA "FEC bit error injection active"
FEC bit error injection is active.
32072 MEI "Backward defect indication (BDI)"
Backward defect indication (BDI).
32073 PMA,S "Open connection indication (OCI)"
Open connection indication (OCI).
32074 PMA,S "Locked (LCK)"
Locked (LCK).
32075 PMA,S "Loss of character synchronization"
Loss of character synchronization.
32076 DMA "ECC link down"
ECC link is down
32101 PMA "High temperature"
High temperature detected.
32102 PMA "Low temperature"
Low temperature detected.
32105 DMA, S "Unit/subrack type mismatch"
A registered unit or subrack type is not what is expected.
32109 DMA “Switch to secondary power”
The node has switch to the secondary power source.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

233
46 Tellabs ® 6300 Managed Transport System Nodes

SPT Status SPT Description


32112 PMA, S “Loss of T0”
Loss of T0.
32113 DMA "Configuration error"
Configuration error.
32114 DMA “APS FOP, time-out (slot 1)”
Automatic Protection Switching (APS) Failure of Protocol (FOP), time-out
(slot 1).
32115 DMA, S “APS FOP, received node ID (slot 1)”
APS FOP, received node ID (slot 1).
32117 DMA “APS FOP, switching state (slot 1)”
APS FOP, switching state (slot 1).
32118 DMA “APS FOP, unstable signaling (slot 1)”
APS FOP, unstable signaling (slot 1).
32120 DMA, S “APS FOP, received request code (slot 1)”
APS FOP, received request code (slot 1).
32124 DMA “APS FOP, received default code (slot 1)”
APS FOP, received default code (slot 1).
32126 DMA “Protection voltage too low”
Protection voltage is too low.
32129 DMA “DTMF EOW failure”
Dual Tone Multi-frequency (DTMF) Engineering Order-Wire (EOW) failure.
32130 DMA "Flash failure"
Flash failure.
32131 PMA, S "Power failure"
Power failure.
32132 DMA "Sw reset and rebooted"
Sw reset and rebooted.
32133 PMA, S "Sw reset constantly"
Sw reset constantly.
32134 PMA "Loss of phase lock"
Loss of phase lock.
32135 PMA "Internal frame signal lost"
Internal frame signal is lost.
32136 PMA "Internal frame signal lost"
Internal frame signal is lost.
32137 PMA "Internal frame signal lost"
Internal frame signal is lost.
32138 DMA "Internal frame signal degraded"
Internal frame signal is degraded.
32139 DMA "Internal frame signal degraded"
Internal frame signal is degraded.
32140 DMA "Internal frame signal degraded"
Internal frame signal is degraded.
32141 DMA "Real-time clock missing"
Real-time clock is missing.
32142 PMA, S "TISI cable misconnected"
Tributary Internal Section Interface (TISI) cable is misconnected.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

234
46 Tellabs ® 6300 Managed Transport System Nodes

SPT Status SPT Description


32144 PMA, S "Optical transmitter failure"
Optical transmitter failure detected.
32145 DMA "Optical transmitter degraded"
Optical transmitter is degraded.
32146 DMA "Protection capacity used"
Equipment protection capacity has been used.
32147 PMA, S "Protection configuration error"
Equipment protection configuration error.
32148 PMA, S "TISI cable missing"
TISI cable is missing.
32149 PMA “Test mode active”
Test mode is active.
32150 DMA "Protection capability problem"
Protection module is incapable of protecting.
32151 DMA "VCO (oscillator) failure"
Failure of VCO (oscillator).
32152 DMA "VCXO (oscillator) failure"
Failure of VCXO (oscillator).
32153 DMA "TCXO (oscillator) failure"
Failure of TCXO (oscillator).
32154 DMA "AISXO (oscillator) failure"
Failure of AISXO (oscillator).
32155 PMA, S "Loss of timing (working)"
Loss of timing in the working side.
32156 PMA, S "Loss of timing (protection)"
Loss of timing in the protection side.
32157 PMA, S “TISI port internal section failure”
TISI port internal section failure.
32158 DMA “TISI port internal section degraded”
TISI port internal section is degraded.
32159 PMA, S "UB1 power missing"
UB1 power is missing.
32160 PMA, S "UB2 power missing"
UB2 power is missing.
32161 DMA “APS FOP, time-out (slot 20)”
APS FOP, time-out (slot 20).
32162 DMA, S “APS FOP, received node ID (slot 20)”
APS FOP, received node ID (slot 20).
32163 DMA “APS FOP, switching state (slot 20)”
APS FOP, switching state (slot 20).
32164 DMA “APS FOP, unstable signaling (slot 20)”
APS FOP, unstable signaling (slot 20).
32165 DMA, S “APS FOP, received request code (slot 20)”
APS FOP, received request code (slot 20).
32166 DMA “APS FOP, received default code (slot 20)”
APS FOP, received default code (slot 20).

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

235
46 Tellabs ® 6300 Managed Transport System Nodes

SPT Status SPT Description


32167 MEI “User defined”
This fault is defined by the user.
32168 MEI “User defined”
This fault is defined by the user.
32169 MEI “User defined”
This fault is defined by the user.
32170 MEI “User defined”
This fault is defined by the user.
32171 MEI “User defined”
This fault is defined by the user.
32172 MEI “User defined”
This fault is defined by the user.
32173 MEI “User defined”
This fault is defined by the user.
32174 MEI “User defined”
This fault is defined by the user.
32179 PMA, S "Optical frequency mismatch"
Optical frequency mismatch.
32180 MEI “Output power out of range”
Output power is out of range.
32184 PMA “MS-SPRing not supported”
MS-SPRing is not supported.
32187 PMA “MSP not supported”
Multiplex Section Protection (MSP) is not supported.
32188 DMA, S “Protection architecture mismatch”
There is a mismatch in the protection architecture.
32189 DMA, S “Inappropriate request code received”
Inappropriate request code has been received.
32190 DMA, S “Illegal request code received”
Illegal request code has been received.
32191 DMA, S “Selector Control Mismatch”
There is a Selector Control mismatch.
32192 DMA, S “Unstable APS signaling”
APS signaling is unstable.
32199 PMA ”ESM critical”
Ethernet Switch Module (ESM) critical.
32200 DMA ”ESM major”
Ethernet Switch Module (ESM) major.
32201 MEI ”ESM minor”
Ethernet Switch Module (ESM) minor.
32202 MEI ”ESM warning”
Ethernet Switch Module (ESM) warning.
32203 PMA, S ”ESM slot mismatch”
Ethernet Switch Module (ESM) slot mismatch.
32209 PMA, S ”ESM usage mismatch”
Ethernet Switch Module (ESM) usage mismatch.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

236
46 Tellabs ® 6300 Managed Transport System Nodes

SPT Status SPT Description


32250 DMA “Actual module not expected”
Actual module is not expected.
32251 PMA, S “RTM failure”
Real Time Marker (RTM) failure.
32252 PMA, S “TIP module missing”
Tributary Interface Protection (TIP) module is missing.
32253 PMA, S “Internal HISI failure”
Internal Higher Order Internal Section Interface (HISI) failure.
32254 DMA “Internal HISI degraded”
Internal HISI degraded.
32255 PMA, S “Missing bus clock”
Bus clock is missing.
32256 PMA, S “Power down”
Power is down.
32257 PMA, S “iRMS failure”
Internal Regenerator/Multiplexer Section (iRMS) failure.
32258 DMA “iRMS degraded”
iRMS degraded.
32260 DMA "MSP interface degraded"
MSP interface degraded.
32261 DMA "MSP interface failure"
MSP interface failure.
32262 DMA “Ambient high temperature”
Ambient temperature is high.
32263 DMA “Switch fet high temperature”
Temperature of the switch field effect transistor (FET) is high.
32264 DMA “Lifetime expectancy exceeded”
Lifetime expectancy exceeded.
32265 DMA “Fan speed low”
Fan speed is low.
32266 DMA “Fan speed very low”
Fan speed is very low.
32267 PMA, S “Frequency out of range on T0”
Frequency is out of range on T0.
32268 PMA, S "FPGA failure"
FPGA failure
32269 MEI "Actual transceiver not expected"
Actual transceiver not expected.
32271 PMA, S "Proprietary information missing"
Proprietary information missing.
32272 PMA, S "Digital diagnostics not supported"
Digital diagnostics not supported.
32273 DMA "Laser bias current out of range"
Laser bias current out of range.
32274 DMA "Transceiver temperature out of range"
Transceiver temperature out of range.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

237
46 Tellabs ® 6300 Managed Transport System Nodes

SPT Status SPT Description


32275 DMA "Transceiver supply voltage out of range"
Transceiver supply voltage out of range.
32276 PMA, S "Transceiver response failure"
Transceiver response failure.
32277 DMA "Module response failure"
Module response failure.
32278 DMA "Internal APS illegal request"
Internal APS illegal request.
32279 PMA “Loss of internal timing”
Loss of internal timing.
32280 PMA, S "Internal section failure"
Internal section failure.
32281 DMA "Internal section degraded"
Internal section degraded.
32282 DMA "Fan failure"
Fan failure.
32283 MEI "Fan degraded"
Fan degraded.
32284 PMA "Firmware file missing"
Firmware file missing.
32285 PMA "Loss of clock"
Loss of clock.
32286 PMA,S "High temperature reset alert"
High temperature reset alert.
32401 DMA "Loss of synchronization source"
Loss of synchronization source.
32402 DMA "Loss of synchronization"
Loss of synchronization.
32404 DMA "Synchronization output squelched"
Synchronization output squelched.
32411 DMA "Synchronization source frequency out of range"
Synchronization source frequency out of range.
32412 DMA "UB power too high"
UB power is too high.
32413 DMA "UB power too low"
UB power is too low.
32414 DMA "Vcc (+5V) voltage too high"
Vcc (+5V) voltage is too high.
32415 DMA "Vcc (+5V) voltage too low"
Vcc (+5V) voltage is too low.
32416 DMA "Vee (-5V) voltage too high"
Vee (-5V) voltage is too high.
32417 DMA "Vee (-5V) voltage too low"
Vee (-5V) voltage is too low.
32418 DMA "Power load too high"
Power load is too high.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

238
46 Tellabs ® 6300 Managed Transport System Nodes

SPT Status SPT Description


32419 DMA "Temperature too high"
Temperature is too high.
32450 DMA “Station clock AIS inserted”
Station clock AIS inserted.
32451 DMA ”APS architecture mismatch”
Automatic Protection Switching (APS) architecture mismatch.
32452 DMA ”APS inappropriate request”
Automatic Protection Switching (APS) inappropriate request.
32453 DMA ”APS illegal request”
Automatic Protection Switching (APS) illegal request.
32455 DMA ”APS unstable”
Automatic Protection Switching (APS) unstable.
32456 DMA ”APS time out”
Automatic Protection Switching (APS) time out.
32457 DMA ”APS illegal node id”
Automatic Protection Switching (APS) illegal node id.
32458 DMA ”APS illegal state”
Automatic Protection Switching (APS) illegal state.
32459 DMA ”APS default signaling”
Automatic Protection Switching (APS) default signaling.
32459 DMA ”APS default signaling”
Automatic Protection Switching (APS) default signaling.
32460 DMA "Protection module used"
Protection module used.
32461 MEI ”Lock out of protection pending”
Lock out of protection pending.
32462 MEI ”Forced switch pending”
Forced switch pending.
32463 DMA “Failure of protocol, TX”
Failure of protocol, TX.
32464 DMA “Failure of protocol, RX”
Failure of protocol, RX.
32465 DMA “MS-SPRing switch active”
MS-SPRing switch active.
32466 MEI "Asymmetric MSP group"
An asymmetric MSP group.
40103 PMA “LCP link down”
LCP link down.
40104 PMA “PSU input missing”
PSU input missing.
40105 PMA “Replacable unit failure”
Replacable unit failure.
40106 DMA “Selector B loss of sources”
Selector B loss of sources.
40107 PMA, S “PHY link shut down”
PHY link shut down.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

239
46 Tellabs ® 6300 Managed Transport System Nodes

SPT Status SPT Description


40108 PMA, S “Received sequnce number too high”
Received sequnce number too high.
40109 MEI “Ethernet OAM peer critical event”
Ethernet OAM peer critical event.
40110 MEI “Ethernet OAM peer dying gasp”
Ethernet OAM peer dying gasp.
40111 MEI “Ethernet OAM peer link fault”
Ethernet OAM peer link fault.
40112 PMA,S “LCAS shut down”
LCAS shut down.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

240
47 Tellabs ® 8110 NTUs CTE-S, CTE-S/208, CTU-S, CTU-512

47 Tellabs ® 8110 NTUs CTE-S, CTE-S/208, CTU-S,


CTU-512

Tellabs 8110 CTE-S and CTE-S/208 have four different versions, i.e. G.703, V.35, V.36, X.21,
whereas Tellabs 8110 CTU-S has three different versions, i.e, G.703, V.35, X.21.

SPT GPT Status SPT Description


1 1 PMA, S, “Unpredicted Fault Condition“
R (This fault condition should never occur)
2 2 PMA, S, “Reset”
R There has been a unit reset (detected always after the power-up
of the unit).
3 3 PMA, S, “Setup error“
R One of the setting structures has been corrupted (or is missing) in
the non-volatile memory.
4 4 PMA, R “Reserved“
5 4 PMA, R “Reserved“
6 4 PMA, R “Reserved“
7 4 PMA, R “Reserved“
8 5 PMA, S, “RAM Fault“
R A background process has detected a RAM location where the
read value does not match the written test pattern.
9 5 PMA, S, “System Software Corrupted “
R The calculated checksum does not match with the stored one.
10 5 PMA, R “Flash Write Error“
Error when writing to the flash memory (main bank).
11 5 PMA, R “Flash Copy Error“
Error when writing to the flash memory (shadow bank).
12 5 PMA, R “Flash Erase Error“
Error during the erase of the flash memory (shadow bank).
13 5 PMA, R “Flash Duplicate Error“
Duplicated parameters (the same ID) detected during the start-up.
14 5 PMA, R “Flash Shadow Error“
The shadow bank of the flash is not erased during the start-up.
15 5 PMA, S, “ Flash Check Sum Error “
R The calculated check sum does not match the stored one.
16 55 PMA, S, “Incompatible software in FLASH“
R The downloaded software (on the flash) is not compatible with
the system software.
17 55 PMA, S, “Checksum Error in Downloaded SW“
R The downloaded software has been corrupted.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

241
47 Tellabs ® 8110 NTUs CTE-S, CTE-S/208, CTU-S, CTU-512

SPT GPT Status SPT Description


18 27 MEI, S, “Local loop“
Y V.54 loop 3. NTU’s transmitter is connected to the receiver.
19 27 MEI, S, “Reserved“
Y
20 27 MEI, S, “Digital loop“
Y V.54 loop 2. NTU loops received data back to the line.
21 27 MEI, S, “Digital loop made by neighbor“
Y Same loop as the digital loop, but it is activated by the neighbor.
The neighbor unit uses management channel to give the loop
command.
22 27 MEI, S, “Remote loop V.54“
Y V.54 loop 2 (digital loop) is formed in the remote unit.
23 27 MEI, S, “Remote loop B V.54“
Y V.54 loop 2 (digital loop) activated by the remote unit.
24 59 MEI, S, “Transmit & Receive test“
Y V.52 compliant 511-bit pattern is transmitted and errors in the
receiver are counted.
25 27 MEI, S, “Neighbor Node Loop“
Y The NTU uses management channel to give the loop command to
the unit of the neighbor node (GMH).
26 27 MEI, S, “Reserved“
Y
27 27 MEI, S, “DTE Loop“
Y DTE loop activated.
28 12 PMA, S, “Reserved“
R
29 12 PMA, S, “Missing signal on line 1“
R No signal on the line 1.
30 12 PMA, S, “Missing signal on line 2“
R No signal on the line 2.
31 49 MEI, Y “Reserved”
32 49 MEI, Y “Noise margin too small in line 1“
33 49 MEI, Y “Noise margin too small in line 2“
34 32 PMA, S, “Reserved“
R
35 32 PMA, S, “Reserved“
R
36 32 PMA, S, “Datapump configuration error“
R This fault is activated if software does not get response from the
datapump.
37 32 MEI, S, “Reserved“
Y
38 60 DMA “Reserved“
39 48 PMA, S “Reserved“
40 58 MEI, Y “Fault mask on“
The fault is activated when the interface Fault mask setting is on
(all interface faults are cleared).

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

242
47 Tellabs ® 8110 NTUs CTE-S, CTE-S/208, CTU-S, CTU-512

SPT GPT Status SPT Description


41 20 MEI, S, “Frame far-end alarm“
Y Frame is lost at the far-end.
42 26 DMA, R “CRC missing“
Frame alignment word is detected but CRC multiframe is not.
43 26 PMA, S, “Frame alignment lost by CRC“
R See G.706 Frame alignment recovery.
44 24 PMA, S, “Frame alignment lost“
R See G.706 Loss of frame alignment.
45 13 PMA, S, “BER more than 10E-3“
R Bit error rate is more than 10E-3. The bit error rate is calculated
from frame alignment words.
46 16 DMA, R “BER more than 10E-6“
Bit error rate is more than 10E-6. The bit error rate is calculated
from CRC.
47 23 MEI, S, “Line signal is AIS“
Y Continuous ’1’ is received.
48 12 PMA, S, “Rx signal missing”
R There is no signal on the DTE connection.
49 23 MEI, S, “RX signal is AIS“
Y The signal from DTE is AIS(”1”).
50 23 MEI, S, “TS0 received from line is AIS“
Y The TS0 signal received from DTE is AIS.
51 23 MEI, S, “TS0 resynchronization“
Y TS0 is resynchronized.
52 58 MEI, Y “Fault mask on“
The fault is activated when the interface fault mask is on.
53 30 MEI, “Reserved“
RB
54 30 MEI, “Reserved“
RB
55 30 DMA, Y “Reserved“
56 30 DMA, Y “Reserved“
57 30 DMA, R “DTE out of synchronization“
Input clock is not clocked to the network. Frequency difference is
> 50ppm.
58 30 DMA, R “Frequency Difference“
Input clock is not clocked to the network. Frequency difference is
< 50ppm.
59 10 PMA, S, “Reserved“
R
60 10 PMA, S, “Reserved“
R
61 22 DMA, R “Missing End-to-End CRC“
End-to-End CRC missing.
62 26 PMA, S, “End-to-End CRC errors“
R There are errors detected in the end-to-end CRC supervision.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

243
47 Tellabs ® 8110 NTUs CTE-S, CTE-S/208, CTU-S, CTU-512

SPT GPT Status SPT Description


63 42 MEI, S, "End-to-End CRC AIS"
Y Continuous ’1’ is received in the end-to-end CRC.
64 32 PMA, S, “MIF ASIC problems“
R One of the components is faulty.
65 5 PMA, S, “RL state program error“
R One of the components is faulty.
66 51 MEI, Y “Reserved“
67 52 MEI, Y “Reserved“
68 29 PMA, S, “Wrong neighbor“
R The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received NNM
message contains unexpected neighbor identification data.
69 29 PMA, S, “No response to NNM message“
R The control channel of the interface is used and the neighbor
supervision option of the interface is on, and no NNM (Neighbor
Node Monitoring) message has been received from the interface
within 8 seconds.
70 29 PMA, S, “Own NNM message received“
R The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received NNM
message contains the same identification data as the NNM
message sent to the interface.
71 114 DMA “G.826 UNAVAIL“
A period of unavailable time begins at the onset of ten consecutive
SES events. These ten seconds are considered to be part of
unavailable time. A new period of available time begins at the
onset of ten consecutive non-SES events. These ten seconds are
considered to be part of available time.
72 49 PMA “QOS Quality of signal. 24 hours period.“
Quality of signal. 24 hours period.
At least one of SES, BBE or ES limit exceeded. Cleared when
period changes.
73 49 PMA “QOSTR Quality of signal. 15 minutes period.“
Quality of signal. A 15-minute period.
At least one of limits ES, BBE , SES has been exceeded. Cleared
when found a period where none of the ES, BBE or SES limits
has been exceeded.
Note that ES and BBE have upper/lower limit so that upper must
be exceeded to get a fault and lower is used as a limit when the
fault is activated.
74 91 MEI “Performance event for G.826“
At least one of performance event counters differs from zero
during the last 15-minute period.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

244
48 Tellabs ® 8110 Network Terminating Units CTU-R, CTE-R, CTE-R/208, STE-10M

48 Tellabs ® 8110 Network Terminating Units


CTU-R, CTE-R, CTE-R/208, STE-10M
SPT GPT Status SPT Description
1 1 PMA “Unpredicted Fault Condition“
(This fault condition should never occur.)
2 2 PMA, S “Reset”
There has been a unit reset (detected always after the power-up
of the unit).
3 3 PMA, S “Setup error“
One of the setting structures has been corrupted (or is missing) in
the non-volatile memory.
8 5 PMA, S ”Memory fault, RAM”
A background process has detected a RAM location where the
read value does not match the written test pattern.
9 5 PMA, S ”Memory fault, EPROM”
The calculated checksum does not match the stored one.
10 5 PMA, S ”Memory fault, flash write error”
Error when writing to the flash memory (main bank).
11 5 PMA, S ”Memory fault, flash copy error”
Error when writing to the flash memory (shadow bank).
12 5 PMA, S ”Memory fault, flash erase error”
Error during the erase of the flash memory (shadow bank).
13 5 PMA, S ”Memory fault, flash duplicate error”
Duplicated parameters (the same ID) detected during start-up.
14 5 PMA, S ”Memory fault, flash shadow error”
The shadow bank of the flash is not erased during start-up.
15 5 PMA, S ”Memory fault, flash checksum error”
The calculated check sum does not match the stored one.
16 55 PMA, S ”Software incompatible in flash”
The downloaded software (in the flash) is not compatible with
the system software in EPROM.
17 55 PMA, S ”Checksum error in downloaded software”
The downloaded software has been corrupted.
18 27 MEI, S ”Local loop”
V.54 loop 3. NTU’s transmitter is connected to the receiver.
20 27 MEI, S ”Digital loop”
V.54 loop 2. NTU loops received data back to the line.
21 27 MEI, S ”Digital loop made by neighbor”
Same loop as the digital loop, but it is activated by the neighbor.
The neighbor unit uses management channel to give the loop
command.
22 27 MEI, S ”Remote loop V.54”
V.54 loop 2 (digital loop) is formed in the remote unit.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

245
48 Tellabs ® 8110 Network Terminating Units CTU-R, CTE-R, CTE-R/208, STE-10M

SPT GPT Status SPT Description


23 27 MEI, S ”Remote loop B V.54”
V.54 loop 2 (digital loop) activated by the remote unit.
24 59 MEI, S ”Transmit & Receive test”
V.52 compliant 511-bit pattern is transmitted and errors in the
receiver are counted.
25 27 MEI, S ”Neighbor Node Loop”
The NTU uses management channel to give the loop command to
the unit of the neighbor node (GMH).
27 27 MEI, S, “DTE Loop”
Y DTE loop is activated.
29 12 PMA, S ”Missing signal on line 1”
No signal on line 1.
30 12 PMA, S ”Missing signal on line 2”
No signal on line 2.
32 49 MEI ”Noise margin too small in line 1”
Not monitored.
33 49 MEI ”Noise margin too small in line 2”
Not monitored.
34 12 PMA, S, ”Missing signal on line 3”
R No signal on the line 3.
34 32 “Reserved”
PMA, S
35 12 PMA, S, ”Missing signal on line 4”
R No signal on the line 4.
35 32 PMA, S “Reserved”
36 32 PMA, S ”Datapump configuration error”
This fault is activated if software does not get response from the
datapump.
37 32 MEI, S “Reserved”
38 49 MEI, Y ”Noise margin too small in line 3”
Noise margin is too small in the line 3.
39 49 MEI, Y ”Noise margin too small in line 4”
Noise margin is too small in the line 4.
40 58 MEI ”Fault mask on”
The fault is activated when the interface Fault mask setting is on
(all interface faults are cleared).
41 20 MEI ”Frame far-end alarm”
Frame is lost at the far-end.
42 26 PMA, S ”CRC missing”
Frame alignment word is detected but CRC multiframe is not.
43 26 PMA, S ”Frame alignment lost by CRC”
See G.706 Frame alignment recovery.
44 24 PMA, S ”Frame alignment lost”
See G.706 Loss of frame alignment.
45 13 PMA, S ”BER more than 10E-3”
Bit error rate is more than 10E-3. The bit error rate is calculated
from frame alignment words.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

246
48 Tellabs ® 8110 Network Terminating Units CTU-R, CTE-R, CTE-R/208, STE-10M

SPT GPT Status SPT Description


46 16 PMA, S ”BER more than 10E-6”
Bit error rate is more than 10E-6. The bit error rate is calculated
from CRC.
47 23 MEI, S ”Line signal is AIS”
Continuous ’1’ is received.
52 58 MEI, Y “Fault mask on“
The fault is activated when the interface fault mask is on.
61 22 DMA, R “Missing End-to-End CRC“
End-to-End CRC is missing.
62 26 PMA, S, “End-to-End CRC errors“
R There are errors detected in the end-to-end CRC supervision.
63 42 MEI, S, "End-to-End CRC AIS"
Y Continuous ’1’ is received in the end-to-end CRC.
64 32 PMA, S ”MIF ASIC problems”
One of the components is faulty.
65 5 PMA, S ”RL state program error”
One of the components is faulty.
66 51 MEI ”Reserved”
68 29 PMA, S ”Wrong neighbor”
The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received NNM
message contains unexpected neighbor identification data.
69 29 PMA, S ”No response to NNM message”
The control channel of the interface is used and the neighbor
supervision option of the interface is on, and no NNM (Neighbor
Node Monitoring) message has been received from the interface
within 8 seconds.
70 29 PMA, S ”Own NNM message received”
The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received NNM
message contains the same identification data as the NNM
message sent to the interface.
71 114 DMA, S ”G.826 unavailable state”
72 49 PMA “QOS Quality of signal. 24-hour period.“
Quality of signal. A period of 24 hours.
At least one of the SES, BBE or ES limits has been exceeded. The
fault is cleared when a 24-hour period changes.
73 49 PMA “QOSTR Quality of signal. 15-minute period.“
Quality of signal. A 15-minute period.
At least one of ES, BBE, SES limits has been exceeded. The fault
is cleared when a period during which none of the ES, BBE or
SES limits has been exceeded, is found.
Note that ES and BBE have an upper/lower limit so that the upper
limit must be exceeded to activate a fault and the lower limit is
used as a limit when the fault is activated.
74 91 MEI “Performance event for G.826“
At least one of the performance event counters differs from zero
during the last 15-minute period.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

247
48 Tellabs ® 8110 Network Terminating Units CTU-R, CTE-R, CTE-R/208, STE-10M

SPT GPT Status SPT Description


80 86 DMA ”Frames errors threshold exceeded”
The amount of received erroneous packets/minute exceeds the
threshold configured. (See the Fault Monitoring Parameters
dialog.)
81 86 DMA ”WAN link traffic threshold exceeded”
Traffic load on the WAN link exceeds the threshold configured.
(See the Fault Monitoring Parameters dialog.)
82 62 PMA, S ”Router module communication error”
The NTU control processor is not able to communicate with the IP
router/bridge processor.
83 5 PMA, S ”Downloaded SW error (sbz670)”
There is an error in the IP router/bridge software that prevents
from using the software.
84 86 DMA “Outbound dropped packets threshold exceeded”
This fault is activated if there are more dropped packets in the
outbound direction than configured in the Outbound Threshold
parameter. This could indicate abnormal network traffic caused by
e.g. a virus or applications that do not function properly. Check
also that outbound rules are properly configured.
85 86 DMA "Inbound dropped packets threshold exceeded"
This fault is activated if there are more dropped packets in the
inbound direction than configured in the Inbound Threshold
parameter. This could indicate abnormal network traffic from
hostile sources. Check also that inbound rules are properly
configured.
86 85 DMA "Session table full"
This fault means that network address translation resources are
exhausted.
Possible causes include misbehaving applications or Denial Of
Service type of attacks from hostile sources.
87 12 PMA, S “LMI has set port operational state down”
The operational state of the port has been set down by LMI.
88 86 DMA, S “IP connections to a monitored destination lost“
This fault is declared when the Background Connectivity
Monitoring tool has detected that the connection to a monitored
destination (an IP address) has been lost. The target device may be
down or there is a break in network connections.
89 85 PMA, S “OSPF link state database full“
8110 CTE-R/8110 CTU-R/8110 STE-10M has run out of memory
resources reserved for OSPF link state advertisements (LSAs).
90 63 PMA “Ethernet MAC/PHY link down”
The Ethernet MAC/PHY link is down.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

248
49 Tellabs ® 8110 Network Terminating Units CTE2-R, CTE2-S

49 Tellabs ® 8110 Network Terminating Units


CTE2-R, CTE2-S
SPT GPT Status SPT Description
1 1 PMA “Unpredicted Fault Condition“
(This fault condition should never occur.)
2 2 PMA, S “Reset”
There has been a unit reset (detected always after the power-up
of the unit).
3 5 PMA, S “Flash file system fatal error“
Flash system failed. Replace unit with spare unit.
4 5 MEI “Flash file system warning”
The flash file system is damaged.
5 5 PMA “SW checksum error in RAM”
The calculated check sum does not match with the stored one
on RAM.
6 5 PMA “SW checksum error in boot flash”
The calculated check sum does not match with the stored one
on boot flash.
7 5 PMA, S “Missing settings”
One of the setting structures is missing in the non-volatile
memory.
8 5 PMA, S ”Flash setup checksum error”
The calculated check sum does not match with the stored one
on flash.
9 5 PMA ”BOOT SW: Downloaded SW missing”
The application software cannot be started, because the
downloaded software is missing. The unit is not operational until
new software has been downloaded.
10 5 PMA ”BOOT SW: Downloaded SW in reset loop”
The application software cannot be started due to a fatal
error. The unit is not operational until new software has been
downloaded.
11 5 PMA ”BOOT SW: Downloaded SW incompatible”
The application software cannot be started, because the
permanent boot software is incompatible with the downloaded
application software in the flash. The unit is not operational until
new software has been downloaded.
12 5 PMA ”BOOT SW: Downloaded SW checksum error”
The application software cannot be started, because the
downloaded application software has corrupted. The calculated
check sum does not match with the one stored in downloadable
flash. The unit is not operational until new software has been
downloaded.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

249
49 Tellabs ® 8110 Network Terminating Units CTE2-R, CTE2-S

SPT GPT Status SPT Description


13 5 PMA ”BOOT SW: Downloaded SW disabled”
The application software cannot be started, because the
application software is disabled. The unit is not operational until
new software has been downloaded.
14 5 PMA ”BOOT SW: Downloaded SW faulty”
The application software cannot be started, because the
downloaded file is invalid. The unit is not operational until new
software has been downloaded.
18 27 MEI, S ”Local loop”
V.54 loop 3. NTU’s transmitter is connected to the receiver.
20 27 MEI, S ”Digital loop”
V.54 loop 2. NTU loops received data back to the line.
21 27 MEI, S ”Digital loop made by neighbor”
Same loop as the digital loop, but it is activated by the neighbor.
The neighbor unit uses management channel to give the loop
command.
22 27 MEI, S ”Remote loop V.54”
V.54 loop 2 (digital loop) is formed in the remote unit.
23 27 MEI, S ”Remote loop B V.54”
V.54 loop 2 (digital loop) activated by the remote unit.
24 59 MEI, S ”Transmit & Receive test”
V.52 compliant 511-bit pattern is transmitted and errors in the
receiver are counted.
25 27 MEI, S ”Neighbor Node Loop”
The NTU uses management channel to give the loop command
to the unit of the neighbor node (OMH2).
26 27 MEI, S, Y “Interface Loop”
Data is looped back to the line from the G.703 interface card.
27 27 MEI, S, Y “DTE Loop”
DTE loop is activated.
29 12 PMA, S ”Missing signal on line 1”
No signal on line 1.
30 12 PMA, S ”Missing signal on line 2”
No signal on line 2.
32 49 MEI ”Noise margin too small in line 1”
33 49 MEI ”Noise margin too small in line 2”
40 58 MEI ”Fault mask on”
The fault is activated when the interface Fault mask setting is on
(all interface faults are cleared).
41 20 MEI ”Frame far-end alarm”
Frame is lost at the far-end.
42 26 PMA, S ”CRC missing”
Frame alignment word is detected but CRC multiframe is not.
43 26 PMA, S ”Frame alignment lost by CRC”
See G.706 Frame alignment recovery.
44 24 PMA, S ”Frame alignment lost”
See G.706 Loss of frame alignment.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

250
49 Tellabs ® 8110 Network Terminating Units CTE2-R, CTE2-S

SPT GPT Status SPT Description


45 13 PMA, S ”BER more than 10E-3”
Bit error rate is more than 10E-3. The bit error rate is calculated
from frame alignment words.
46 16 PMA, S ”BER more than 10E-6”
Bit error rate is more than 10E-6. The bit error rate is calculated
from CRC.
47 23 MEI, S ”Line signal is AIS”
Continuous ’1’ is received.
48 12 PMA, S, “Rx signal missing”
R There is no signal on the DTE connection.
49 23 MEI, S, Y “RX signal is AIS “
The signal from the DTE is Alarm Indication Signal ("1").
50 23 MEI, S, Y “TS0 from DTE is AIS “
The signal received from DTE is Alarm Indication Signal.
51 23 MEI, S, Y “TS0 resynchronization”
TS0 is resynchronized.
52 58 MEI, Y “Fault mask on“
The fault is activated when the interface fault mask is on.
53 30 MEI, R “TX buffer slips”
The data transmitted towards DTE experiences errors due to
wrong timing.
54 30 MEI, R “RX buffer slips”
The data received from DTE experiences errors due to wrong
timing.
57 30 DMA, R “DTE out of syncronization”
The DTE connection needs to be synchronized.
58 30 DMA, R “Frequency Difference“
Input clock is not locked to the network. Frequency difference
is <50ppm.
61 22 DMA, R “Missing End-to-End CRC“
End-to-End CRC is missing.
62 26 PMA, S, “End-to-End CRC errors“
R There are errors detected in the end-to-end CRC supervision.
63 42 MEI, S, Y "End-to-End CRC AIS"
Continuous ’1’ is received in the end-to-end CRC.
68 29 PMA, S ”Wrong neighbor”
The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received NNM
message contains unexpected neighbor identification data.
69 29 PMA, S ”No response to NNM message”
The control channel of the interface is used and the neighbor
supervision option of the interface is on, and no NNM (Neighbor
Node Monitoring) message has been received from the interface
within 8 seconds.
70 29 PMA, S ”Own NNM message received”
The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received NNM
message contains the same identification data as the NNM
message sent to the interface.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

251
49 Tellabs ® 8110 Network Terminating Units CTE2-R, CTE2-S

SPT GPT Status SPT Description


71 114 DMA ”G.826 unavailable state”
A period of unavailable time begins at the onset of ten
consecutive SES events. These ten seconds are considered to be
part of unavailable time. A new period of available time begins at
the onset of ten consecutive non-SES events. These ten seconds
are considered to be part of available time.
72 49 PMA “QOS Quality of signal. 24-hour period.“
Quality of signal. A period of 24 hours.
At least one of the SES, BBE or ES limits has been exceeded.
The fault is cleared when a 24-hour period changes.
73 49 PMA “QOSTR Quality of signal. 15-minute period.“
Quality of signal. A 15-minute period.
At least one of ES, BBE, SES limits has been exceeded. The
fault is cleared when a period during which none of the ES, BBE
or SES limits has been exceeded, is found.
Note that ES and BBE have an upper/lower limit so that the
upper limit must be exceeded to activate a fault and the lower
limit is used as a limit when the fault is activated.
74 91 MEI “Performance event for G.826“
At least one of the performance event counters differs from zero
during the last 15-minute period.
80 86 DMA ”Frames errors threshold exceeded”
The amount of received erroneous packets/minute exceeds the
threshold configured. (See the Fault Monitoring Parameters
dialog.)
81 86 DMA ”WAN link traffic threshold exceeded”
Traffic load on the WAN link exceeds the threshold configured.
(See the Fault Monitoring Parameters dialog.)
82 62 PMA, S ”Router module communication error”
The NTU control processor is not able to communicate with the
IP router/bridge processor.
83 5 PMA, S ”Downloaded SW error”
There is an error in the IP router/bridge software that prevents
from using the software.
84 86 DMA “Outbound dropped packets threshold exceeded”
This fault is activated if there are more dropped packets in the
outbound direction than configured in the Outbound Threshold
parameter. This could indicate abnormal network traffic caused
by e.g. a virus or applications that do not function properly.
Check also that outbound rules are properly configured.
85 86 DMA "Inbound dropped packets threshold exceeded"
This fault is activated if there are more dropped packets in the
inbound direction than configured in the Inbound Threshold
parameter. This could indicate abnormal network traffic from
hostile sources. Check also that inbound rules are properly
configured.
86 85 DMA "Session table full"
This fault means that network address translation resources are
exhausted.
Possible causes include misbehaving applications or Denial Of
Service type of attacks from hostile sources.
87 12 PMA, S “LMI has set port operational state down”
The operational state of the port has been set down by LMI.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

252
49 Tellabs ® 8110 Network Terminating Units CTE2-R, CTE2-S

SPT GPT Status SPT Description


88 86 DMA, S “IP connections to a monitored destination lost“
This fault is declared when the Background Connectivity
Monitoring tool has detected that the connection to a monitored
destination (an IP address) has been lost. The target device may
be down or there is a break in network connections.
89 85 PMA, S “OSPF link state database full“
8110 CTE-R/8110 CTU-R/8110 STE-10M has run out of memory
resources reserved for OSPF link state advertisements (LSAs).
90 63 PMA “Ethernet MAC/PHY link down”
The Ethernet MAC/PHY link is down.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

253
50 Tellabs ® 8110 Network Terminating Unit HTU-2M

50 Tellabs ® 8110 Network Terminating Unit


HTU-2M
SPT GPT Status SPT Description
1 1 PMA "SW unpredicted"
This fault condition should never occur (or is not yet supported).
2 2 PMA, S "Reset"
There has been a unit reset (detected always after the power-up
of the unit).
3 3 PMA, S "Setup error"
One of the setting structures has been corrupted in the non-volatile
memory.
4 4 PMA "Power +5V (Vcc)"
Not monitored.
5 5 PMA "Power +12V"
Not monitored.
6 6 PMA "Power -5V"
Not monitored.
7 7 PMA "Power -10V"
Not monitored.
8 5 PMA, S "RAM fault"
A background process has detected a RAM location where the
read value does not match the written test pattern.
9 5 PMA, S "EPROM fault"
The calculated checksum does not match the stored one.
10 5 PMA "Flash write error"
Error when writing to the flash memory (main bank).
11 5 PMA "Flash copy error"
Error when writing to the flash memory (shadow bank).
12 5 PMA "Flash erase error"
Error during the erase of the flash memory (shadow bank).
13 5 PMA "Flash duplicate error"
Duplicated parameters (the same ID) detected during the start-up.
14 5 PMA "Flash shadow error"
The shadow bank of the flash is not erased during the start-up.
15 5 PMA, S "Flash check sum error"
The calculated check sum does not match the stored one.
16 55 PMA, S "Incompatible EPROM/FLASH SW"
The downloaded software (in the flash) is not compatible with
the system software in EPROM.
17 55 PMA, S "Checksum error in downloaded SW"
The downloaded software has been corrupted.
18 27 MEI, S "Local loop"
V.54 loop 3. NTU’s transmitter is connected to the receiver.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

254
50 Tellabs ® 8110 Network Terminating Unit HTU-2M

SPT GPT Status SPT Description


19 27 MEI, S "HDSL local loop"
Local loop has been activated by the HDSL channel.
20 27 MEI, S "Digital loop"
V.54 loop 2. NTU loops received data back to the line. The loop is
activated by NTU’s keys.
21 27 MEI, S "Digital loop made by neighbor"
Same loop than the digital loop, but it is activated by the neighbor.
The neighbor unit uses management channel to give the loop
command.
22 27 MEI, S "Remote loop V.54"
V.54 loop 2 (digital loop) is formed in the remote unit.
23 27 MEI, S "Remote loop B V.54"
V.54 loop 2 (digital loop) activated by the remote unit.
24 59 MEI, S "Transmit & Receive test"
V.52 compliant 511-bit pattern is transmitted and errors in the
receiver are counted.
25 27 MEI, S "Neighbor node loop"
NTU uses management channel to give the loop command to the
unit of the neighbor node (GMH).
26 27 MEI, S "Interface loop"
Interface loop activated.
27 27 MEI, S "DTE loop"
DTE loop activated.
29 12 PMA, S "Missing signal on line 1"
No signal in line 1.
30 12 PMA, S "Missing signal on line 2"
No signal on line 2.
32 49 MEI "Noise margin is too small in line 1"
Not monitored.
33 49 MEI "Noise margin is too small in line 2"
Not monitored.
34 32 PMA, S "MDP ASIC problems"
Not monitored.
35 32 PMA, S "Datapump communication error"
This fault is activated if software does not get a response from
the datapump.
36 32 PMA, S "Datapump configuration error"
Datapump gives ”configuration error” error when software tries
to give it a new configuration.
37 32 MEI, S "Datapump forced to reset"
This fault is activated when datapump does not respond and it
is forced to reset.
38 60 DMA "G.821 limit event"
This fault is activated as a delta fault if the G.821 supervision is
used and at least one performance limit has been exceeded in a
15-minute period.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

255
50 Tellabs ® 8110 Network Terminating Unit HTU-2M

SPT GPT Status SPT Description


39 48 PMA, S "G.821 unavailable state"
The fault is activated if the G.821 supervision is used and the state
of signal becomes unavailable (10 consecutive SES seconds). The
fault is deactivated when 10 consecutive seconds not classified
as SES have been found.
40 58 MEI "Fault mask on"
The fault is activated when the interface Fault mask setting is on
(all interface faults are cleared).
41 20 MEI "Frame far-end alarm"
Frame is lost at the far-end.
42 26 DMA "CRC missing"
Frame alignment word is detected but the CRC multiframe is not.
43 26 PMA, S "Frame align. lost by CRC"
See G.706 Frame alignment recovery.
44 24 PMA, S "Frame alignment lost"
See G.706 Loss of frame alignment.
45 13 PMA, S "BER more than 10-3"
Bit error rate is more than 10E-3. The bit error rate is calculated
from frame alignment words.
46 16 PMA, S "BER more than 10E-6"
Bit error rate is more than 10E-6. The bit error rate is calculated
from CRC.
47 23 MEI, S "Line signal is AIS"
Continuous ’1’ is received.
48 12 MEI, S "RX signal missing"
There is no signal in the DTE connection.
49 23 MEI, S "RX signal is AIS"
The signal from the DTE is AIS(”1”).
50 23 MEI, S "TS0 received from line is AIS"
The TS0 signal received from DTE is AIS.
51 23 MEI, S "TS0 resynchronization"
TS0 is resynchronized.
52 58 MEI "Fault mask on"
The fault is activated when the interface fault mask is on.
53 30 DMA "TX buffer slips"
The data transmitted towards DTE experiences errors due to
wrong timing.
54 30 DMA "RX buffer slips"
The data received from DTE experiences errors due to wrong
timing.
55 30 DMA "TX buffer alignment"
Buffer for transmit direction is realigned.
56 30 DMA "RX buffer alignment"
Buffer for receive direction is realigned.
57 30 DMA "DTE out of synchronization"
DTE connection needs to be synchronized.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

256
50 Tellabs ® 8110 Network Terminating Unit HTU-2M

SPT GPT Status SPT Description


58 30 DMA "Frequency difference"
The measurement period is 15 seconds and the phase-drifting limit
is 5 *s. The fault is activated if the phase-drifting limit has been
exceeded in 3 measurements out of 4.
59 10 PMA, S "Wrong interface module"
There is a conflict between the installed module and the settings.
59 10 PMA, S "Wrong interface module"
There is a conflict between the installed module and the settings.
60 10 PMA, S "Interface module missing"
The interface module defined in the settings is missing.
61 22 PMA, S "Missing End-to-End CRC"
End-to-End CRC missing
62 26 DMA "End-to-End CRC errors"
There are errors detected in the end-to-end CRC supervision.
64 32 PMA, S "MIF ASIC problems"
One of the components is faulty.
65 5 PMA, S "RL state program error"
One of the components is faulty.
66 51 MEI "Line rate scanning"
NTU is searching the right line rate.
67 52 MEI "DTE rate scanning"
NTU is searching the right DTE rate (113 signal).
68 29 PMA, S "Wrong neighbor"
The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received NNM
message contains unexpected neighbor identification data.
69 29 PMA, S "No response to NNM msg"
The control channel of the interface is used and the neighbor
supervision option of the interface is on and no NNM (Neighbor
Node Monitoring) message has been received from the interface
within 8 seconds.
70 29 PMA, S "Own NNM msg received"
The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received NNM
message contains the same identification data as the NNM
message sent to the interface.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

257
51 Tellabs ® 8110 Network Terminating Unit STU-160

51 Tellabs ® 8110 Network Terminating Unit


STU-160
SPT GPT Status SPT Description
1 1 PMA "SW unpredicted"
This fault condition should never occur (or is not yet supported).
2 2 PMA, S "Reset"
There has been a unit reset (detected always after the power-up
of the unit).
3 3 PMA, S "Setup error"
One of the setting structures has been corrupted in the non-volatile
memory.
4 4 PMA "Power +5V (Vcc)"
The voltage is below the threshold limit (about 4.75 V depending
on the calibration and the A/D resolution).
5 4 PMA "Power +12V"
The voltage is below the threshold limit (about 11.4 V depending
on the calibration and the A/D resolution).
6 4 PMA "Power -5V"
The voltage is above the threshold limit (about -4.5 V depending
on the calibration and the A/D resolution).
7 4 PMA "Power -10V"
The voltage is above the threshold limit (about -9.5 V depending
on the calibration and the A/D resolution).
8 5 PMA, S "RAM fault"
A background process has detected a RAM location where the
read value does not match the written test pattern.
9 5 PMA, S "EPROM fault"
The calculated checksum does not match the stored one.
10 5 PMA, S "Flash write error"
Error when writing to the flash memory (main bank).
11 5 PMA, S "Flash copy error"
Error when writing to the flash memory (shadow bank).
12 5 PMA, S "Flash erase error"
Error during the erase of the flash memory (shadow bank).
13 5 PMA, S "Flash duplicate error"
Duplicated parameters (the same ID) detected during the start-up.
14 5 PMA, S "Flash shadow error"
The shadow bank of the flash is not erased during the start-up.
15 5 PMA, S "Flash check sum error"
The calculated check sum does not match the stored one.
16 55 PMA, S "Incompatible EPROM/FLASH SW"
The downloaded software (in the flash) is not compatible with the
system software in EPROM.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

258
51 Tellabs ® 8110 Network Terminating Unit STU-160

SPT GPT Status SPT Description


17 55 PMA, S "Checksum error in downloaded SW"
The downloaded software has been corrupted.
18 29 MEI "Wrong neighbor"
The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received NNM
message contains unexpected neighbor identification data.
19 29 MEI "No response to NNM message"
The control channel of the interface is used and the neighbor
supervision option of the interface is on and no NNM (Neighbor
Node Monitoring) message has been received from the interface
within 8 seconds.
20 29 MEI "Own NNM message received"
The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received NNM
message contains the same identification data as the NNM
message sent to the interface.
21 58 MEI "Fault mask on"
Faults are masked.
22 12 PMA, S "Loss of line signal"
Data communication through the U interface is broken.
23 13 PMA, S "BER 10E-3"
Bit error rate estimated to exceed 10E-3. Bit error rate is
calculated from the multiframe CRC block errors of the U
interface.
24 42 MEI, S "AIS detected from network"
Signal from the line is Alarm Indication Signal.
25 26 DMA "CRC faults"
CRC faults in the U interface.
26 27 MEI "Analog loop to interface"
Analog loop to interface in the U interface.
27 27 MEI "Digital loop"
Digital loop in the U interface.
28 60 DMA "G.821 limit event"
This fault is activated as a delta fault if the G.821 supervision is
used and at least one performance limit has been exceeded in a
15-minute period.
29 48 PMA, S "G.821 unavailable state"
The fault is activated if the G.821 supervision is used and
the state of signal becomes unavailable (10 consecutive SES
seconds). The fault is deactivated when 10 consecutive seconds
not classified as SES have been found.
30 24 PMA, S "Loss of frame sync"
Loss of frame synchronization state in case of V.110 or X.30.
31 67 PMA "FAS errors"
Frame synchronization word errors detected in case of V.110 or
X.30
32 25 PMA, S "Loss of multiframe sync"
Loss of multiframe synchronization state in case of V.110 or X.30.
33 30 DMA "Tx buffer alignment"
V.110 or X.30 buffer slip

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

259
51 Tellabs ® 8110 Network Terminating Unit STU-160

SPT GPT Status SPT Description


34 30 DMA "Rx buffer alignment"
V.110 or X.30 buffer slip
35 42 MEI, S "AIS detected from network"
Alarm Indication Signal from the cross-connection bus.
36 67 PMA, S "Code errors from input"
Code errors (HDB3, AMI or G.703 codir/contra). No input clock
(NRZ)
37 26 PMA, S "CRC errors from near-end"
CRC errors detected at the near-end.
38 20 MEI, S "Alarm from far-end"
Alarm bit set in V.110 or X.30 frame.
39 32 PMA, S "ASIC register error in V.110"
Error detected in the ASIC hardware
40 57 PMA, S "DTE power off"
DTE power is off.
41 60 DMA "G.821 limit event"
This fault is activated as a delta fault if the G.821 supervision is
used and at least one performance limit has been exceeded in a
15-minute period.
42 48 PMA, S "G.821 unavailable state"
The fault is activated if the G.821 supervision is used and
the state of signal becomes unavailable (10 consecutive SES
seconds). The fault is deactivated when 10 consecutive seconds
not classified as SES have been found.
43 27 MEI, S "Local loop"
V.54 loop 3. The transmitter of NTU is connected to receiver.
44 27 MEI, S "Digital loop"
V.54 loop 2. NTU loops received data back to the line. Loop is
activated by the keys of NTU.
45 27 MEI, S "Digital loop made by neighbor"
The same loop than the digital loop, but it is activated by a
neighbor. The neighbor unit uses management channel to give
a loop command.
46 27 MEI, S "Remote loop V.54"
V.54 loop 2 (digital loop) is formed in remote unit.
47 27 MEI, S "Remote loop B V.54"
V.54 loop 2 (digital loop) activated by remote unit.
48 59 MEI, S "Transmit & Receive test"
V.52 compliant 511-bit pattern is transmitted and errors in
receiver are counted.
49 5 MEI, S "RL state program error"
Remote loop state program error not stored (HW error).
50 50 PMA, S "105 off in DTE"
The 105 signal is off in DTE and the 105 supervision is selected
in IF parameters.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

260
52 Tellabs ® 8110 Network Terminating Units STU-320, STU-576, STU-1088-2W, STU-2304

52 Tellabs ® 8110 Network Terminating Units


STU-320, STU-576, STU-1088-2W, STU-2304
SPT GPT Status SPT Description
1 1 PMA "SW unpredicted"
This fault condition should never occur (or is not yet supported).
2 2 PMA, S "Reset"
There has been a unit reset (detected always after the power-up
of the unit).
3 3 PMA, S "Setup error"
One of the setting structures has been corrupted in the non-volatile
memory.
4 4 PMA "Power +5V (Vcc)"
Not monitored
5 5 PMA "Power +12V"
Not monitored
6 6 PMA "Power -5V"
Not monitored
7 7 PMA "Power -10V"
Not monitored
8 5 PMA, S "RAM fault"
A background process has detected a RAM location where the
read value does not match the written test pattern.
9 5 PMA, S "EPROM fault"
The calculated checksum does not match the stored one.
10 5 PMA, S "Flash write error"
Error when writing to the flash memory (main bank).
11 5 PMA, S "Flash copy error"
Error when writing to the flash memory (shadow bank).
12 5 PMA, S "Flash erase error"
Error during the erase of the flash memory (shadow bank).
13 5 PMA, S "Flash duplicate error"
Duplicated parameters (the same ID) detected during the start-up.
14 5 PMA, S "Flash shadow error"
The shadow bank of the flash is not erased during the start-up.
15 5 PMA, S "Flash check sum error"
The calculated check sum does not match the stored one.
16 55 PMA, S "Incompatible EPROM/FLASH SW"
The downloaded software (in the flash) is not compatible with the
system software in EPROM.
17 55 PMA, S "Checksum error in downloaded SW"
The downloaded software has been corrupted.
18 27 MEI, S "Local loop"
V.54 loop 3. The transmitter of NTU is connected to receiver.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

261
52 Tellabs ® 8110 Network Terminating Units STU-320, STU-576, STU-1088-2W, STU-2304

SPT GPT Status SPT Description


20 27 MEI, S "Digital loop"
V.54 loop 2. NTU loops received data back to the line. The loop
is activated by the keys of NTU.
21 27 MEI, S "Digital loop made by neighbor"
The same loop than the digital loop, but it is activated by a
neighbor. The neighbor unit uses management channel to give
a loop command.
22 27 MEI, S "Remote loop V.54"
V.54 loop 2 (digital loop) is formed in remote unit.
23 27 MEI, S "Remote loop B V.54"
V.54 loop 2 (digital loop) activated by remote unit.
24 59 MEI, S "Transmit & Receive test"
V.52 compliant 511-bit pattern is transmitted and errors in
receiver are counted.
25 27 MEI, S "Neighbor node loop"
NTU uses management channel to give a loop command to the
unit of the neighbor node (GMH).
26 27 MEI, S "Interface loop"
Data is looped back to the line from the G.703 interface card.
27 27 MEI, S "DTE loop"
Data is looped back to the DTE connection from NTU.
28 12 PMA, S "Missing line"
No signal on the line.
31 49 MEI "Noise margin is too small"
The quality of the line is not good enough for data
communications.
34 32 PMA, S "MDP ASIC problems"
Not monitored.
35 32 PMA, S "Datapump communication error"
This fault is activated if the software does not get response from
the datapump
36 32 PMA, S "Datapump configuration error"
The datapump gives ”configuration error” when software tries to
give to the datapump a new configuration.
37 32 MEI, S "Datapump forced to reset"
This fault is activated when the datapump does not respond and it
is forced to reset.
38 60 DMA "G.821 limit event"
This fault is activated as a delta fault if the G.821 supervision is
used and at least one performance limit has been exceeded in a
15-minute period.
39 48 PMA, S "G.821 unavailable state"
The fault is activated if the G.821 supervision is used and
the state of signal becomes unavailable (10 consecutive SES
seconds). The fault is deactivated when 10 consecutive seconds
not classified as SES have been found.
40 58 MEI "Fault mask on"
The fault is activated when the interface Fault mask setting is on
(all interface faults are cleared).

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

262
52 Tellabs ® 8110 Network Terminating Units STU-320, STU-576, STU-1088-2W, STU-2304

SPT GPT Status SPT Description


41 20 MEI "Frame far-end alarm"
Frame is lost at the far-end.
42 26 DMA "CRC missing"
Frame alignment word is detected but CRC multiframe is not.
43 26 PMA, S "Frame align. lost by CRC"
See G.706 Frame alignment recovery.
44 24 PMA, S "Frame alignment lost"
See G.706 Loss of frame alignment.
45 13 PMA, S "BER more than 10-3"
Bit error rate is more than 10E-3. Bit error rate is calculated from
frame alignment words.
46 16 PMA, S "BER more than 10E-6"
Bit error rate is more than 10E-6. The bit error rate is calculated
from CRC.
47 23 MEI, S "Line signal is AIS"
Continuous ’1’ is received.
48 12 MEI, S "RX signal missing"
There is no signal on DTE connection.
49 23 MEI, S "RX signal is AIS"
The signal from the DTE is Alarm Indication Signal (”1”).
50 23 MEI, S "TS0 received from line is AIS"
The signal received from DTE is Alarm Indication Signal.
51 23 MEI, S "TS0 resynchronization"
TS0 is resynchronized.
52 58 MEI "Fault mask on"
The fault is activated when the interface Fault mask is on.
53 30 DMA "TX buffer slips"
The data transmitted towards DTE experiences errors due to
wrong timing.
54 30 DMA "RX buffer slips"
The data received from DTE experiences errors due to wrong
timing.
55 30 DMA "TX buffer alignment"
Buffer for transmit direction is realigned.
56 30 DMA "RX buffer alignment"
Buffer for receive direction is realigned.
57 30 DMA "DTE out of synchronization"
The DTE connection needs to be synchronized.
58 30 DMA "Frequency difference"
The measurement period is 15 seconds and the phase-drifting
limit is 5 *s. The fault is activated if the phase-drifting limit has
been exceeded in 3 measurements out of 4.
59 10 PMA, S "Wrong interface module"
There is a conflict between the installed module and the settings.

60 10 PMA, S "Interface module missing"


The interface module defined in the settings is missing.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

263
52 Tellabs ® 8110 Network Terminating Units STU-320, STU-576, STU-1088-2W, STU-2304

SPT GPT Status SPT Description


61 22 PMA, S "Missing End-to-End CRC"
End-to-End CRC is missing
62 26 DMA "End-to-End CRC errors"
There are errors detected on end-to-end CRC supervision.
64 32 PMA, S "MIF ASIC problems"
One of the components is faulty.
65 5 PMA, S "RL state program error"
One of the components is faulty.
66 51 MEI "Line rate scanning"
NTU is searching the right line rate.
67 52 MEI "DTE rate scanning"
NTU is searching the right DTE rate (113 signal).
68 29 PMA, S "Wrong neighbor"
The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received NNM
message contains unexpected neighbor identification data.
69 29 PMA, S "No response to NNM msg"
The control channel of the interface is used and the neighbor
supervision option of the interface is on and no NNM (Neighbor
Node Monitoring) message has been received from the interface
within 8 seconds.
70 29 PMA, S "Own NNM msg received"
The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received NNM
message contains the same identification data as the NNM
message sent to the interface.
71 42 MEI, S, "End-to-End CRC is AIS"
Y Continuous ’1’ is received on end-to-end CRC.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

264
53 VCM-5T, VCM-10T, VCM-5T-A, VCM-10T-A, VCM 402, GCH-A

53 VCM-5T, VCM-10T, VCM-5T-A, VCM-10T-A,


VCM 402, GCH-A
SPT GPT Status SPT Description
1 1 PMA, S "SW Unpredicted"
This fault condition should never occur (or is not yet supported).
2 2 PMA, S "Reset"
There has been a unit reset (detected always after the power-up
of the unit).
3 4 PMA "Power +5 V"
The voltage is below the threshold limit (about 4.6 V depending
on the calibration and the A/D resolution).
4 4 PMA "Power +5 V"
The voltage is below the threshold limit (about 4.6 V depending
on the calibration and the A/D resolution).
5 4 PMA "Power +12 V"
The board 12 V supply voltage is below the threshold limit (about
11.3 V depending on the calibration and the A/D resolution).
6 4 PMA "Power -10 V"
The board negative supply voltage is above the threshold
limit (about -9.0 V depending on the calibration and the A/D
resolution).
7 38 PMA, S "Bus sync fault"
No 8100 system bus synchronization from SXU detected.
8 36 PMA, S "Start request denied"
No permission to start. The unit is not in its correct place.
9 55 PMA, S "Incompatible EPROM/FLASH SW"
The downloaded software (in the flash) is not compatible with the
system software in EPROMs.
10 55 PMA, S "Chksum err in downloaded SW"
The downloaded software has been corrupted.
11 5 PMA, S "RAM fault"
A background process has detected a RAM location where the
read value does not match the written test pattern.
12 5 PMA, S "EPROM fault"
The calculated check sum does not match the stored one.
13 5 PMA "Flash write error"
Error when writing to the flash memory (main bank).
14 5 PMA "Flash copy error"
Error when writing to the flash memory (shadow bank).
15 5 PMA "Flash erase error"
Error during the erase of the flash memory (shadow bank).
16 5 PMA "Flash duplicate error"
Duplicated parameters (the same ID) detected during the start-up.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

265
53 VCM-5T, VCM-10T, VCM-5T-A, VCM-10T-A, VCM 402, GCH-A

SPT GPT Status SPT Description


17 5 PMA "Flash shadow error"
The shadow bank of the flash is not erased during the start-up.
18 5 PMA, S "Flash check sum error"
Parameter setting check sum error detected.
19 3 PMA, S "Setup error"
One of the setting structures has been corrupted in the non-volatile
memory.
30 24 PMA, S "Loss of frame sync"
Loss of frame synchronization state in case of V.110 or X.30.
31 67 PMA "FAS-errors"
Frame synchronization word errors detected in case of V.110 or
X.30.
32 25 PMA, S "Loss of multiframe sync"
Loss of multiframe synchronization state in case of V.110 or X.30.
33 30 DMA "Tx buffer alignment"
V.110 or X.30 buffer slip.
34 30 DMA "Rx buffer alignment"
V.110 or X.30 buffer slip.
35 42 MEI, S "AIS detected from network"
Alarm Indication Signal from the cross-connection bus.
36 67 PMA, S "Code errors from input"
Code errors (HDB3, AMI or G.703 codir/contra). No input clock
(NRZ).
37 22 DMA "CRC errors from far-end"
CRC errors detected at the far-end
38 26 DMA "CRC errors from near-end"
CRC errors detected at the near-end.
39 30 DMA "Rx buffer slips"
Buffer slip in the 8100 system bus interface (n x 64 kbit/s).
40 30 DMA "Tx buffer slips"
Buffer slip in the 8100 system bus interface (n x 64 kbit/s).
41 40 PMA, S "IA activity missing"
The interface address is not activated on the cross-connection
bus by SXU.
42 20 MEI, S "Alarm from far-end"
Alarm bit set in V.110 or X.30 frame.
50 32 PMA, S "ASIC register err in V110"
Error detected in ASIC. HW error in the V110 block of ASIC.
51 32 PMA, S "ASIC register err in RL"
Error detected in ASIC. HW error in the RL block of ASIC.
52 32 PMA, S "ASIC register err in PMP"
Error detected in ASIC. HW error in the PMP block of ASIC.
53 32 PMA, S "ASIC register err in CRP"
Error detected in ASIC. HW error in the CRP block of ASIC.
54 32 PMA, S "ASIC register err in IRP"
Error detected in ASIC. HW error in the IRP block of ASIC.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

266
53 VCM-5T, VCM-10T, VCM-5T-A, VCM-10T-A, VCM 402, GCH-A

SPT GPT Status SPT Description


55 32 PMA, S "ASIC register err in IFM"
Error detected in ASIC. HW error in the IFM block of ASIC.
56 32 PMA, S "ASIC register err in SYNTE"
Error detected in ASIC. HW error in the SYNTE block of ASIC.
57 32 PMA, S "ASIC register err in CK"
Error detected in ASIC. HW error in the CK block of ASIC.
58 32 PMA, S "ASIC register err in CIF"
Error detected in ASIC. HW error in the CIF block of ASIC.
60 27 MEI, S "Local loop or test active"
Local loop or test activated (by 8100 manager).
61 27 MEI, S "V.54 loop active"
V.54 loop activated (by interface signal or from far-end).
62 10 PMA, S "Wrong interface module"
Wrong interface module detected.
63 50 MEI, S "105 off in input"
The 105 signal is off in input and the 105 supervision is selected
in parameters.
64 57 MEI "Power off in input"
Alternate wetting current detected in case of BTE-64 or BTE-384.
Incoming data signal (103) is not in accordance with the ITU-T
specifications (VCM).
65 12 PMA, S "Interface signal missing"
No carrier state of the baseband module (GCH). Faulty input
signal in case of the G.703 module (GCH).
66 27 MEI, S "Interface loop active"
Interface loop activated (by 8100 manager).
67 58 MEI, S "Faults masked/test"
Faults are masked (alarms are not generated as consequences of
fault conditions).
68 56 MEI "Wetting current high" (GCH)
High wetting current detected in case of BTE-64 or BTE-384.
70 48 PMA, S "G821 unavailable state"
The fault is activated if the G.821 supervision is used and the
state of the signal becomes unavailable (10 consecutive SES
seconds). The fault is deactivated when 10 consecutive seconds
not classified as SES have been found.
71 5 PMA, S "RL state program error"
Remote loop state program not stored (HW error).
72 60 DMA "G821 limit event"
This fault is activated as a delta fault if the G.821 supervision is
used and at least one performance limit has been exceeded in a
15-minute period.
78 29 PMA, S ”Wrong IDs in NNM message”
The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received NNM
message contains unexpected neighbor identification data.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

267
53 VCM-5T, VCM-10T, VCM-5T-A, VCM-10T-A, VCM 402, GCH-A

SPT GPT Status SPT Description


79 29 PMA, S "No response to NNM message"
The control channel of the interface is used and the neighbor node
supervision option of the interface is on and no NNM (Neighbor
Node Monitoring) message has been received from the interface
within 8 seconds.
80 29 PMA, S "Own NNM messages received"
The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received NNM
message contains the same identification data as the NNM
message sent to the interface.
82 27 MEI, S "Local loop made by neighbor"
This alarm is ON if the local loop at near end has been activated
by far end (data is looped back to the line interface).
83 27 MEI, S "Rem cntr loc loop at far end"
This alarm is ON if the local loop at far end has been activated by
near end (data is looped back to the line interface).
250 117 PMA “AIS Reported from 6300”
6300 Trail is broken, PBC, 6300 VC4 is Unavailable or there is a
setup failure. See I/F message for additional information.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

268
54 VMM

54 VMM
SPT GPT Status SPT Description
1 1 "SW Unpredicted"
PMA, S This fault condition should never occur (or is not yet supported).
2 2 PMA, S "Reset"
There has been a unit reset (detected always after the power-up
of the unit).
3 4 PMA "Power +5 V"
The voltage is below the threshold limit
(about 4.6 V depending on the calibration and the A/D
resolution).
4 4 PMA "Power +5 V"
The voltage is below the threshold limit
(about 4.6 V depending on the calibration and the A/D
resolution).
5 4 PMA "Power +12 V"
The board 12 V supply voltage is below the threshold limit
(about 11.3 V depending on the calibration and the A/D
resolution).
6 4 PMA "Power -10 V"
The board negative supply voltage is above the threshold limit
(about -9.0 V depending on the calibration and the A/D
resolution).
7 38 PMA, S "Bus sync fault"
No 8100 system bus synchronization from SXU detected.
8 36 PMA, S "Start request denied"
No permission to start. The unit is not in its correct place.
9 55 PMA, S "Incompatible EPROM/FLASH SW"
The downloaded software (in the flash) is not compatible with
the system software in EPROMs.
10 55 PMA, S "Chksum err in downloaded SW"
The downloaded software has been corrupted.
11 5 PMA, S "RAM fault"
A background process has detected a RAM location where the
read value does not match the written test pattern.
12 5 PMA, S "EPROM fault"
The calculated check sum does not match the stored one.
13 5 PMA "Flash write error"
Error when writing to the flash memory (main bank).
14 5 PMA "Flash copy error"
Error when writing to the flash memory (shadow bank).
15 5 PMA "Flash erase error"
Error during the erase of the flash memory (shadow bank).
16 5 PMA "Flash duplicate error"
Duplicated parameters (the same ID) detected during the start-up.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

269
54 VMM

SPT GPT Status SPT Description


17 5 PMA "Flash shadow error"
The shadow bank of the flash is not erased during the start-up.
18 5 PMA, S "Flash check sum error"
Parameter setting check sum error detected.
19 3 PMA, S "Setup error"
One of the setting structures has been corrupted in the
non-volatile memory.
20 24 PMA, S "Loss of frame sync"
Loss of frame synchronization state.
21 67 PMA 21 "FAS-errors"
Frame synchronization word errors detected.
22 30 DMA "Tx buffer alignment"
V.110 buffer slip.
23 42 MEI, S "AIS detected from network"
Alarm Indication Signal from the cross-connection bus.
24 26 DMA "CRC errors from near-end"
CRC errors detected at the near-end.
25 40 PMA, S "IA activity missing"
The interface address is not activated on the cross-connection
bus by SXU.
26 32 PMA, S "XILINX register error"
An error detected in the XILINX (HW error).
27 32 PMA, S "CIF ASIC register error"
An error detected in ASIC. HW error in the CIF block of ASIC.
28 27 MEI, S "Local loop or test active"
Local loop or test activated (by 8100 manager).
29 27 MEI, S "Interface loop active"
Interface loop activated (by 8100 manager).
30 27 MEI, S Local loop made by the neighbor.
This alarm is activated if the HDLC channel is in use and line
loop has been activated from the remote end.
31 27 MEI, S "Remote controlled line loop"
This alarm is activated if the HDLC channel is in use and line
loop has been made to the neighbor unit.
32 10 PMA, S "Wrong interface module"
Wrong interface module detected.
33 58 MEI, S "Faults masked/test"
Faults are masked (alarms are not generated as consequences of
fault conditions).
34 60 DMA "G821 limit event"
This fault is activated as a delta fault if the G.821 supervision is
used and at least one performance limit has been exceeded in a
15-minute period.
35 48 PMA, S "G821 unavailable state"
The fault is activated if the G.821 supervision is used and the
state of the signal becomes unavailable (10 consecutive SES
seconds). The fault is deactivated when 10 consecutive seconds
not classified as SES have been found.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

270
54 VMM

SPT GPT Status SPT Description


36 29 PMA, S "Wrong neighbor"
The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received NNM
message contains unexpected neighbor identification data
37 29 PMA, S "No response to NNM message"
The control channel of the interface is used and the neighbor
node supervision option of the interface is on and no NNM
(Neighbor Node Monitoring) message has been received from
the interface within 8 seconds.
38 29 PMA, S "Own NNM messages received"
The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received NNM
message contains the same identification data as the NNM
message sent to the interface.
39 42 PMA, S "Interface signal missing"
The signal level is below a specific level (the level depends on
the used interface module and the selected bit rate).

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

271
55 XCG

55 XCG
SPT GPT Status SPT Description
1 1 PMA "SW unpredicted"
This fault condition should never occur (or is not yet supported).
2 2 PMA "Reset"
There has been a unit reset (detected always after the power-up
of the unit).
3 11 PMA, S "Loss of protected signal"
In 1+1 protection mode both interfaces IF1 and IF2 have faults
which in unprotected mode have S status.
4 4 PMA "Power + 5 V"
The voltage is below the threshold limit
(about 4.6 V depending on the calibration and the A/D
resolution).
5 4 PMA "Power +12 V"
The voltage is below the threshold limit
(about 11.3 V depending on the calibration and the A/D
resolution).
5 4 PMA "Power +12 V"
The voltage is below the threshold limit
(about 11.3 V depending on the calibration and the A/D
resolution).
6 4 PMA "Power -10 V "
The voltage is above the threshold limit
(about -9.0 V depending on the calibration and the A/D
resolution).
7 4 PMA, S "VPLL"
Not monitored.
8 38 PMA, S "Bus sync. Fault"
No cross-connection bus synchronization detected.
10 34 MEI "Unstable SSM"
The clock source from SSM is not stable.
11 5 PMA, S "RAM fault"
A background process has detected a RAM location where the
read value does not match the written test pattern.
12 5 PMA, S "EPROM fault"
The calculated check sum does not match the stored one.
13 5 PMA "Flash write error"
Error when writing to the flash memory (main bank).
14 5 PMA "Flash copy error"
Error when writing to the flash memory (shadow bank).
15 5 PMA "Flash erase error"
Error during the erase of the flash memory (shadow bank).
16 5 PMA "Flash duplicate error"
Duplicated parameters (the same ID) detected during the start-up.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

272
55 XCG

SPT GPT Status SPT Description


17 5 PMA "Flash shadow error"
The shadow bank of the flash is not erased during the start-up.
18 5 PMA, S "Flash check sum error"
The calculated check sum does not match the stored one.
19 5 PMA, S "Missing settings"
One of the setting structures has been corrupted in the
non-volatile memory.
20 59 MEI, S "BTE Tx line test"
The fault is activated if the Tx-test pattern generator of the BTE
module is activated (used in the V.54 remote loop).
21 32 PMA, S "X-connect loop error"
The internal data loop test is not successful. The cross-connect
matrix may be faulty.
22 39 PMA, S "Tx clock fault"
The fault is activated if the interface module transmitting clock
phase locking to X-bus clock fails.
23 40 PMA, S "IA activity missing"
The fault is activated if the unit cannot find its locked interface
address on the cross-connection bus. SXU should activate IA on
the bus if the interface is locked.
24 10 PMA, S "IF module missing"
The interface module defined in the settings is missing.
25 10 PMA, S "Wrong interface module"
There is a conflict between the installed module and the settings.
26 57 MEI "NTU power off/local loop"
The fault is activated if the module used is BTE-384 and wetting
current is on and the received current value differs in frequency
of 1.5...4.5 Hz and the current value difference is more than 1.5
mA.
27 12 PMA, S "Rx signal missing"
The signal level is below a specific level (the level depends on
the interface module used and the selected bit rate).
28 42 MEI, S "AIS from X-BUS"
The fault is activated if the frame synchronization word and
RAI from the X-bus and TS0 B2 changes between "0" and "1"
are missing.
29 23 MEI, S "Rx signal is AIS"
The fault is activated if 2 or less/2M mode or 8 or less/8M mode
zeros in a 2-frame period are recognized.
The fault is deactivated if 3 or more/2M mode or 12 or more/8M
mode zeros in a 2-frame period are recognized.
30 26 DMA "CRC –multiframe lost"
The fault is activated if framing can be found in the 2M mode and
the CRC multiframe alignment has been lost for 100…200 ms, or
if in the 8M mode CRC alignment losses have been found more
than 6 times in a 3-second period due to excessive block errors.
The fault is deactivated if in the 2M mode the multiframe
alignment has been found and in the 8M mode when no more
than one frame alignment lost due to excessive CRC block errors
in a 3-second period has been detected.
This fault indicates that the remote end most probably does not
use CRC.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

273
55 XCG

SPT GPT Status SPT Description


31 26 PMA, S "Frame alignment lost by CRC"
See CCITT G.706 Frame alignment recovery.
(2048 mode ≥ 915 CRC block errors detected).
32 24 PMA, S "Frame alignment lost"
See CCITT G.706 Loss of frame alignment.
33 13 PMA, S "BER10E-3"
See ITU-T G.736. The bit error rate is calculated from faulty
frame alignment words or from code errors. The bit error rate
10E-3 limits from frame alignment words:
2048 kbit/s and n x 64 kbit/s count time 4 seconds
Count to activate alarm: 94
Count to deactivate alarm: 17
8448 kbit/s and count time 2 seconds
Count to activate alarm: 199
Count to deactivate alarm: 48
Error rate 10E-3 limits from code errors:
Count time 1 second.
2048 kbit/s
Activation limit: 1973
Deactivation limit: 229
8448 kbit/s
Activation limit: 8296
Deactivation limit: 839
10E-3 alarm status depends on fault consequences (AIS
insertion).
34 13 DMA "BER10E-3"
See ITU-T G.736. The bit error rate is calculated from faulty
frame alignment words or from code errors. The bit error rate
10E-3 limits from frame alignment words:
2048 kbit/s and n x 64 kbit/s count time 4 seconds
Count to activate alarm: 94
Count to deactivate alarm: 17
8448 kbit/s and count time 2 seconds
Count to activate alarm: 199
Count to deactivate alarm: 48
Error rate 10E-3 limits from code errors:
Count time 1 second
2048 kbit/s
Activation limit: 1973
Deactivation limit: 229
8448 kbit/s
Activation limit: 8296
Deactivation limit: 839
10E-3 alarm status depends on fault consequences (AIS
insertion).
35 56 MEI "NTU line break"
The fault is activated if the module used is BTE-384 and wetting
current is on and the received current value is lower than 1.2 mA.
36 56 MEI "NTU short circuit"
The fault is activated if the module used is BTE-384 and wetting
current is on and the received current value is higher than 6.5 mA.
37 29 PMA, S "No response to NNM message"
The control channel of the interface is used and the neighbor
node supervision option of the interface is on and no NNM
(Neighbor Node Monitoring) message has been received from
the interface within 8 seconds.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

274
55 XCG

SPT GPT Status SPT Description


38 29 PMA, S "Own NNM messages received"
The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received NNM
message contains the same identification data as the NNM
message sent to the interface.
39 29 PMA, S "Wrong ID’s in NNM message"
The control channel of the interface is used and the neighbor
supervision option of the interface is on and the received NNM
message contains unexpected neighbor identification data.
40 27 MEI, S "IF back to equipment"
An interface loop is created in the interface module. It loops
transmitted data and the clock signal back to the interface
receiver.
41 27 MEI, S "MUX/DEMUX back to eq."
Similar to Interface back to equipment loop except that the loop
is made before the interface module on the GMH unit base card.
42 27 MEI, S "MUX/DEMUX back to line"
Rx data is looped back to the interface transmitter. When the
HDLC channel is used, it works with this line loop. All other bits
are looped back to the interface.
43 27 MEI, S "Line loop made by neighbor"
This alarm is activated if the HDLC channel is in use and
MUX/DEMUX back to line loop has been made from the remote
end or the BTE module is used and remote end has activated
the V.54 loop.
44 27 MEI, S "Remote controlled line loop"
This alarm is activated if the HDLC channel is in use and
MUX/DEMUX back to line loop has been made to the neighbor
unit or the BTE module is used and the V.54 loop has been made
to the remote end.
45 43 MEI, S "AIS in signaling"
The fault is activated if a signal in the signaling timeslot contains
less than 2 zeros during a multiframe period.
46 43 MEI, S "AIS in signaling group A"
See above.
47 43 MEI, S "AIS in signaling group B"
See above.
48 43 MEI, S "AIS in signaling group C"
See above.
49 43 MEI, S "AIS in signaling group D"
See above.
50 25 PMA, S "MFrame alignment lost"
The fault is activated if two consecutive faulty multiframe
alignment words are received or if all signaling timeslots in one
multiframe contain only zeros ("0").
The fault is deactivated when the frame alignment is detected
and the first four bits of signaling timeslot are found to be zeros
("0") and when the prior signaling timeslot had at least one bit
in state "1".
51 25 PMA, S "MFrame alignment lost, group A"
See above.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

275
55 XCG

SPT GPT Status SPT Description


52 25 PMA, S "MFrame alignment lost, group B"
See above.
53 25 PMA, S "MFrame alignment lost, group C"
See above.
54 25 PMA, S "MFrame alignment lost, group D"
See above.
55 20 MEI, S "Frame far-end alarm"
The state of the far-end alarm bit TS0 B3 will be switched if
the opposite state is received in 3 consecutive frames. State "1"
for alarm.
Alarm status depends on fault consequences
(AIS insertion into the signaling timeslot).
56 20 MEI "Frame far-end alarm"
The state of the far-end alarm bit TS0 B3 will be switched if
the opposite state is received in 3 consecutive frames. State "1"
for alarm.
Alarm status depends on fault consequences
(AIS insertion into the signaling timeslot).
57 21 MEI, S "MFrame far-end alarm"
The state of signaling timeslot’s frame 0 B6 alarm bit will be
switched if the opposite state is received in 3 consecutive frames.
State "1" for alarm.
Alarm status depends on fault consequences
(AIS insertion into the signaling timeslot).
58 21 MEI "MFrame far-end alarm"
The state of signaling timeslot’s frame 0 B6 alarm bit will be
switched if the opposite state is received in 3 consecutive frames.
State "1" for alarm.
Alarm status depends on fault consequences
(AIS insertion into the signaling timeslot).
59 21 MEI, S "MFrame far-end alarm, group A"
The state of signaling timeslot’s frame 0 B6 alarm bit will be
switched if the opposite state is received in 3 consecutive frames.
State "1" for alarm.
Alarm status depends on fault consequences
(AIS insertion into the signaling timeslot).
60 21 MEI "MFrame far-end alarm, group A"
The state of signaling timeslot’s frame 0 B6 alarm bit will be
switched if the opposite state is received in 3 consecutive frames.
State "1" for alarm.
Alarm status depends on fault consequences
(AIS insertion into the signaling timeslot).
61 21 MEI,S "MFrame far-end alarm, group B"
The state of signaling timeslot’s frame 0 B6 alarm bit will be
switched if the opposite state is received in 3 consecutive frames.
State "1" for alarm.
Alarm status depends on fault consequences
(AIS insertion into the signaling timeslot).
62 21 MEI "MFrame far-end alarm, group B"
The state of signaling timeslot’s frame 0 B6 alarm bit will be
switched if the opposite state is received in 3 consecutive frames.
State "1" for alarm.
Alarm status depends on fault consequences
(AIS insertion into the signaling timeslot).

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

276
55 XCG

SPT GPT Status SPT Description


63 21 MEI, S "MFrame far-end alarm, group C"
The state of signaling timeslot’s frame 0 B6 alarm bit will be
switched if the opposite state is received in 3 consecutive frames.
State "1" for alarm.
Alarm status depends on fault consequences
(AIS insertion into the signaling timeslot).
64 21 MEI "MFrame far-end alarm, group C"
The state of signaling timeslot’s frame 0 B6 alarm bit will be
switched if the opposite state is received in 3 consecutive frames.
State "1" for alarm.
Alarm status depends on fault consequences
(AIS insertion into the signaling timeslot).
65 21 MEI, S "MFrame far-end alarm, group D"
The state of signaling timeslot’s frame 0 B6 alarm bit will be
switched if the opposite state is received in 3 consecutive frames.
State "1" for alarm.
Alarm status depends on fault consequences
(AIS insertion into the signalling timeslot).
66 21 MEI "MFrame far-end alarm, group D"
The state of signaling timeslot’s frame 0 B6 alarm bit will be
switched if the opposite state is received in 3 consecutive frames.
State "1" for alarm.
Alarm status depends on fault consequences
(AIS insertion into the signaling timeslot).
67 16 DMA "BER10E-6"
BER10E-6 error rate is calculated from CRC block errors when
bit rate ≥ 1024 kbit/s. Counting time is 10 seconds and the limit
for the fault condition depends on the bit rate used (2048 limit
is 10).
68 58 MEI "Faults masked/test"
The fault is activated when the interface Fault mask setting is on
(all interface faults are cleared).
69 30 DMA "Frequency difference"
The measurement period is 15 seconds and the phase-drifting
limit is 5 ms. The fault is activated if the phase-drifting limit has
been exceeded in 3 measurements out of 4.
70 30 MEI "Buffer slip"
The fault is activated if one or more buffer slip(s) have been
detected during the last hour.
71 41 DMA "HDLC overlap with X-bus"
The fault is activated if the HDLC control channel bit(s) are also
used by the cross-connection bus.
72 41 DMA "MCLK RAI overlap with X-bus"
The fault is activated if the MCLK/RAI bit is also used by the
cross-connection bus.
73 32 PMA, S "ASIC register error"
The fault is activated if the difference between write/read
configuration data of ASIC has been detected.
74 60 DMA "Performance event"
This fault is activated as a delta fault if the G.821 supervision is
used and at least one performance limit has been exceeded in a
15-minute period.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

277
55 XCG

SPT GPT Status SPT Description


75 48 PMA, S "Unavailable state"
The fault is activated if the G.821 supervision is used and the
state of the signal becomes unavailable (10 consecutive SES
seconds). The fault is deactivated when 10 consecutive seconds
not classified as SES have been detected.
76 69 PMA "Extended setting backup inconsistency"
Inconsistency in extended setting backup.
78 69 DMA "Port locking conflict"
The fault is activated if the cross-connection system has the port
descriptor but the interface is unlocked or the cross-connection
system does not have the port descriptor although the interface is
locked. Use lock/unlock.
79 53 MEI "Protection switch forced"
The unit is in 1+1 protected mode and the protection switch has
been forced to select signal from IF1 or IF2.
80 55 PMA "Incompatible EPROM/FLASH SW"
The downloaded software (in the flash) is not compatible with
the system software in EPROMs.
81 5 PMA "Chksum err in downloaded SW"
The downloaded software has been corrupted.
82 28 PMA, S "Unit 1 IA Fault"
Data transfer between the cross-connection unit and a specified
channel unit does not work.
83 28 PMA, S "Unit 2 IA Fault"
Data transfer between the cross-connection unit and a specified
channel unit does not work.
84 28 PMA, S "Unit 3 IA Fault"
Data transfer between the cross-connection unit and a specified
channel unit does not work.
85 28 PMA, S "Unit 4 IA Fault"
Data transfer between the cross-connection unit and a specified
channel unit does not work.
86 28 PMA, S "Unit 5 IA Fault"
Data transfer between the cross-connection unit and a specified
channel unit does not work.
87 28 PMA, S "Unit 6 IA Fault"
Data transfer between the cross-connection unit and a specified
channel unit does not work.
88 28 PMA, S "Unit 7 IA Fault"
Data transfer between the cross-connection unit and a specified
channel unit does not work.
89 28 PMA, S "Unit 8 IA Fault"
Data transfer between the cross-connection unit and a specified
channel unit does not work.
90 28 PMA, S "Unit 9 IA Fault"
Data transfer between the cross-connection unit and a specified
channel unit does not work.
91 28 PMA, S "Unit 10 IA Fault"
Data transfer between the cross-connection unit and a specified
channel unit does not work.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

278
55 XCG

SPT GPT Status SPT Description


92 28 PMA, S "Unit 11 IA Fault"
Data transfer between the cross-connection unit and a specified
channel unit does not work.
93 28 PMA, S "Unit 12 IA Fault"
Data transfer between the cross-connection unit and a specified
channel unit does not work.
94 28 PMA, S "Unit 13 IA Fault"
Data transfer between the cross-connection unit and a specified
channel unit does not work.
95 28 PMA, S "Unit 14 IA Fault"
Data transfer between the cross-connection unit and a specified
channel unit does not work.
96 28 PMA, S "Unit 15 IA Fault"
Data transfer between the cross-connection unit and a specified
channel unit does not work.
97 28 PMA, S "Unit 16 IA Fault"
Data transfer between the cross-connection unit and a specified
channel unit does not work.
98 28 PMA, S "Unit 17 IA Fault"
Data transfer between the cross-connection unit and a specified
channel unit does not work.
99 28 PMA, S "Unit 18 IA Fault"
Data transfer between the cross-connection unit and a specified
channel unit does not work.
100 28 PMA, S "Unit 19 IA Fault"
Data transfer between the cross-connection unit and a specified
channel unit does not work.
101 28 PMA, S "Unit 20 IA Fault"
Data transfer between the cross-connection unit and a specified
channel unit does not work.
102 8 PMA, S "Missing Unit 1"
A registered unit is not in its place.
103 8 PMA, S "Missing Unit 2"
A registered unit is not in its place.
104 8 PMA, S "Missing Unit 3"
A registered unit is not in its place.
105 8 PMA, S "Missing Unit 4"
A registered unit is not in its place.
106 8 PMA, S "Missing Unit 5"
A registered unit is not in its place.
107 8 PMA, S "Missing Unit 6"
A registered unit is not in its place.
108 8 PMA, S "Missing Unit 7"
A registered unit is not in its place.
109 8 PMA, S "Missing Unit 8"
A registered unit is not in its place.
110 8 PMA, S "Missing Unit 9"
A registered unit is not in its place.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

279
55 XCG

SPT GPT Status SPT Description


111 8 PMA, S "Missing Unit 10"
A registered unit is not in its place.
112 8 PMA, S "Missing Unit 11"
A registered unit is not in its place.
113 8 PMA, S "Missing Unit 12"
A registered unit is not in its place.
114 8 PMA, S "Missing Unit 13"
A registered unit is not in its place.
115 8 PMA, S "Missing Unit 14"
A registered unit is not in its place.
116 8 PMA, S "Missing Unit 15"
A registered unit is not in its place.
117 8 PMA, S "Missing Unit 16"
A registered unit is not in its place.
118 8 PMA, S "Missing Unit 17"
A registered unit is not in its place.
119 8 PMA, S "Missing Unit 18"
A registered unit is not in its place.
120 8 PMA, S "Missing Unit 19"
A registered unit is not in its place.
121 8 PMA, S "Missing Unit 20"
A registered unit is not in its place.
122 9 MEI "Extra Unit 1"
There is a unit which has not been registered as part of the
subrack inventory.
123 9 MEI "Extra Unit 2"
There is a unit which has not been registered as part of the
subrack inventory.
124 9 MEI "Extra Unit 3"
There is a unit which has not been registered as part of the
subrack inventory.
125 9 MEI "Extra Unit 4"
There is a unit which has not been registered as part of the
subrack inventory.
126 9 MEI "Extra Unit 5"
There is a unit which has not been registered as part of the
subrack inventory.
127 9 MEI "Extra Unit 6"
There is a unit which has not been registered as part of the
subrack inventory.
128 9 MEI "Extra Unit 7"
There is a unit which has not been registered as part of the
subrack inventory.
129 9 MEI "Extra Unit 8"
There is a unit which has not been registered as part of the
subrack inventory.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

280
55 XCG

SPT GPT Status SPT Description


130 9 MEI "Extra Unit 9"
There is a unit which has not been registered as part of the
subrack inventory.
131 9 MEI "Extra Unit 10"
There is a unit which has not been registered as part of the
subrack inventory.
132 9 MEI "Extra Unit 11"
There is a unit which has not been registered as part of the
subrack inventory.
133 9 MEI "Extra Unit 12"
There is a unit which has not been registered as part of the
subrack inventory.
134 9 MEI "Extra Unit 13"
There is a unit which has not been registered as part of the
subrack inventory.
135 9 MEI "Extra Unit 14"
There is a unit which has not been registered as part of the
subrack inventory.
136 9 MEI "Extra Unit 15"
There is a unit which has not been registered as part of the
subrack inventory.
137 9 MEI "Extra Unit 16"
There is a unit which has not been registered as part of the
subrack inventory.
138 9 MEI "Extra Unit 17"
There is a unit which has not been registered as part of the
subrack inventory.
139 9 MEI "Extra Unit 18"
There is a unit which has not been registered as part of the
subrack inventory.
140 9 MEI "Extra Unit 19"
There is a unit which has not been registered as part of the
subrack inventory.
141 9 MEI "Extra Unit 20"
There is a unit which has not been registered as part of the
subrack inventory.
142 4 PMA "VB 2"
The VB 2 voltage is below the threshold limit.
143 4 PMA "VB 1"
The VB 1 voltage is below the threshold limit.
144 112 DMA, "Excessive errors"
(S) Once every second, block errors shall be compared with the limit
value. If errors count ≥ limit, the one second shall be declared
BAD, otherwise it shall be declared GOOD.
The Excessive errors shall be detected if M consecutive BAD
seconds have occurred.
The Excessive errors shall be cleared if M consecutive GOOD
seconds have occurred.
M value range 2..9.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

281
55 XCG

SPT GPT Status SPT Description


145 103 DMA, "Degraded errors"
(S) Once every second, block errors shall be compared with the limit
value. If errors count ≥ limit, the one second shall be declared
BAD, otherwise it shall be declared GOOD.
The Degraded errors shall be detected if M consecutive BAD
seconds have occurred.
The Degraded errors shall be cleared if M consecutive GOOD
seconds have occurred.
M value range 2..9.
150 32 PMA, S "X-connect RAM fault"
A problem detected in configuring the cross-connect matrix.
152 28 PMA, S "Block IA fault"
Data transfer between the cross-connection and a specified block
(interface/port) does not work.
153 34 MEI "Loss of master clock locking"
The internal clock is used and the fallback list contains entries.
154 34 MEI "Fallback list warning"
The lowest choice is used (there are more than one choice in
the fallback list).
155 34 PMA "Loss of external clock"
The external clock input is enabled but the clock, connected to
the input, is not acceptable.
156 34 PMA "Phase-locked loop alarm"
The phase-locked loop of the master clock cannot be locked to
any clock.
157 35 MEI "External clock warning"
The external clock is included in the fallback list but the external
clock input is not enabled.
158 31 MEI "Clock far-end alarm choice 1"
The state of the choice 1 in the fallback list indicates the clock
far-end alarm.
159 31 MEI "Clock far-end alarm choice 2"
The state of the choice 2 in the fallback list indicates the clock
far-end alarm.
160 31 MEI "Clock far-end alarm choice 3"
The state of the choice 3 in the fallback list indicates the clock
far-end alarm.
161 31 MEI "Clock far-end alarm choice 4"
The state of the choice 4 in the fallback list indicates the clock
far-end alarm.
162 31 MEI "Clock far-end alarm choice 5"
The state of the choice 5 in the fallback list indicates the clock
far-end alarm.
163 34 MEI "Faulty clock source of choice 1"
The state of the choice 1 in the fallback list is faulty.
164 34 MEI "Faulty clock source of choice 2"
The state of the choice 2 in the fallback list is faulty.
165 34 MEI "Faulty clock source of choice 3"
The state of the choice 3 in the fallback list is faulty.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

282
55 XCG

SPT GPT Status SPT Description


166 34 MEI "Faulty clock source of choice 4"
The state of the choice 4 in the fallback list is faulty.
167 34 MEI "Faulty clock source of choice 5"
The state of the choice 5 in the fallback list is faulty.
168 20 MEI “Pilot bit far end alarm”
A pilot bit far end alarm is detected in the X-bus.
169 42 MEI, S “Pilot bit AIS”
Pilot bit AIS (S-status) is detected in the X-bus.
170 5 PMA, S "Flash list check sum error"
One of the flash lists (e.g. port descriptor list) has been corrupted.
172 32 PMA, S "ASIC latch error"
An ASIC setting cannot be corrected by a checking background
process.
173 32 MEI "ASIC latch warning"
An ASIC setting is corrected by a checking background process.
178 35 MEI "Time controlled X-conn warning"
A delta fault is indicating a problem when switching the
time-controlled cross-connection on/off. Additional information
can be read from the error log of the time control process.
179 5 MEI "X-connect flash list conflict"
A corrupted cross-connect record has been detected in the
non-volatile memory after the unit reset. The record has been
deleted.
180 5 MEI "PortDescr flash list conflict"
A corrupted port descriptor record has been detected in the
non-volatile memory after the unit reset. The record has been
deleted.
181 5 MEI "Swapped trunk flash list conflict"
A corrupted swap-trunk record has been detected in the
non-volatile memory after the unit reset. The record has been
deleted.
182 5 MEI "Passivated trunk flash list conflict"
A corrupted passivate-trunk record has been detected in the
non-volatile memory after the unit reset. The record has been
deleted.
183 55 PMA, S "Missing application program"
There is no application program in the flash memory. Download
the latest version of the program.
250 117 PMA “AIS Reported from 6300”
6300 Trail is broken, PBC, 6300 VC4 is Unavailable or there is a
setup failure. See I/F message for additional information.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

283
56 NMS

56 NMS
SPT GPT Status SPT Description
1 252 PMA, "DXX Server Supervisor down"
MEI DXX Server Supervisor is down.
2 252 PMA, "Recovery Server Supervisor down"
MEI Recovery Server Supervisor is down.
3 252 PMA, "Private Subnetwork Server Supervisor down"
MEI Private Subnetwork Server Supervisor is down.
4 252 PMA, "DXX Server Supervisor paused"
MEI DXX Server Supervisor is paused.
5 252 PMA, "Recovery Server Supervisor paused"
MEI Recovery Server Supervisor is paused.
6 252 PMA, "Private Subnetwork Server Supervisor paused"
MEI Private Subnetwork Server Supervisor is paused.
7 252 PMA "Connector Server down"
Connector Server is down.
10 252 PMA "Communication Service down"
Communication Service is down.
11 252 PMA "Control Channel & Recovery Service down"
Control Channel and Recovery Service is down.
12 252 PMA "Consistency Checker Service down"
Consistency Checker Service is down.
13 252 PMA "Fault Manager Services down"
Fault Manager Services are down.
14 252 PMA "Performance Manager Poller down"
Performance Manager Poller is down.
15 252 PMA "Log Printer Service down"
Log Printer Service is down.
16 252 PMA "Real Time Manager Service down"
Real Time Manager Service is down.
17 252 PMA "Coordinator Process down"
Coordinator Process is down.
18 252 PMA "Asynchronous Link down"
Asynchronous Link is down.
19 252 PMA "X.25 Link down"
X.25 Link is down.
20 252 PMA "Transport Initializer Service down"
Transport Initializer Service is down.
21 252 PMA "Partitioned Log Printer down"
Partitioned Log Printer is down.
22 252 PMA "DXX Backup Server down"
DXX Backup Server is down.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

284
56 NMS

SPT GPT Status SPT Description


23 252 PMA "Fault Data Server down"
Fault Data Server is down.
24 252 PMA "Line Fault Server Services down"
Line Fault Server Services are down.
25 252 PMA "Fault Filter Services down"
Fault Filter Services are down.
26 252 PMA "Ethernet Link down"
Ethernet Link is down.
27 252 PMA "Ring Fault Server Process down"
Ring Fault Server Process is down.
28 252 PMA "Periodic Performance Management System Server process
down"
Periodic Performance Management System Server process is
down.
40 252 PMA "Recover Management Server down"
Recover Management Server is down.
41 252 PMA "Recovery Management - Trunk recovery down"
Recovery Management - Trunk recovery is down.
42 252 PMA "Recovery Management - Circuit recovery down"
Recovery Management - Circuit recovery is down.
43 252 PMA "Recovery Management - Accounting down"
Recovery Management - Accounting is down.
50 252 DMA "Private Subnetwork Change Message Server down"
Private Subnetwork Change Message Server is down.
51 252 DMA "Private Subnetwork Data Cache Service down"
Private Subnetwork Data Cache Service is down.
52 252 DMA "Private Subnetwork Recovery Control Service down"
Private Subnetwork Recovery Control Service is down.
60 252 PMA "Circuit X-connect Service down"
Circuit X-connect Service is down.
61 252 PMA "Name Server down"
Name Server is down.
62 252 PMA "Test Data Server down"
Test Data Server is down.
63 252 PMA "Database Object Server down"
Database Object Server is down.
64 252 PMA "NMS Component Monitoring down"
NMS Component Monitoring is down.
65 252 PMA "License Server down"
License Server is down.
70 252 PMA "Asynchronous Link broken"
Asynchronous Link is broken.
71 252 PMA "X.25 Link broken"
X.25 Link is broken.
72 252 PMA "IP Link broken"
IP Link is broken.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

285
56 NMS

SPT GPT Status SPT Description


78 252 DMA "A long database transaction has exceeded DBPM Threshold 1"
A long database transaction has exceeded the DBPM Threshold
1.
79 252 DMA "A long database transaction has exceeded DBPM Threshold 2"
A long database transaction has exceeded the DBPM Threshold
2.
80 252 DMA, "Database Transaction Log full"
PMA, Database Transaction Log is full.
MEI
81 252 DMA, "Database Data Area full"
PMA, Database Data Area is full.
MEI
82 252 DMA "A blocking database process has exceeded DBPM Threshold 1"
A blocking database process has exceeded the DBPM Threshold
1.
83 252 DMA "A blocking database process has exceeded DBPM Threshold 2"
A blocking database process has exceeded the DBPM Threshold
2.
84 252 DMA "Database Process Monitor down"
Database Process Monitor is down.
85 252 DMA, "Replica database transaction log full"
PMA, Replica database transaction log is full.
MEI
86 252 DMA, "Replica database data area full"
PMA, Replica database data area is full.
MEI
87 252 DMA, "Fault history database transaction log full"
PMA, Fault history database transaction log is full.
MEI
88 252 DMA, "Fault history database data area full"
PMA, Fault history database data area is full.
MEI
90 252 DMA "Control Path too long for transport service"
Control Path is too long for transport service.
101 254 PMA "Protected ring down"
There are service affecting faults on both sides of the ring or at
either or both ring end nodes.
102 254 DMA "One side of the protected ring down"
There are service affecting fault(s) on one side of the ring.
103 254 MEI "Non-service affecting fault(s) in the protected ring"
There are non-service affecting fault(s) within the protected ring.
110 252 MEI, "SNMP Communication Service down"
PMA SNMP Communication Service is down.
111 252 MEI, “SNMP Fault Manager Services down”
PMA SNMP Fault Manager Services are down.
112 252 MEI, "SNMP Performance Manager Poller down"
PMA SNMP Performance Manager Poller is down.
113 252 MEI, "SNMP Real Time Manager Service down"
PMA SNMP Real Time Manager Service is down.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

286
56 NMS

SPT GPT Status SPT Description


114 252 MEI, "SNMP Server Backup Controller down"
PMA SNMP Server Backup Controller is down.
115 252 MEI, "SNMP Consistency Checker Service down"
PMA SNMP Consistency Checker Service is down.
120 252 MEI, "SNMP Server Supervisor down"
PMA SNMP Server Supervisor is down.
121 252 MEI, "SNMP Server Supervisor paused"
PMA SNMP Server Supervisor is paused.
122 252 MEI, "Management Server Supervisor down"
PMA Management Server Supervisor is down.
123 252 MEI, "Management Server Supervisor paused"
PMA Management Server Supervisor is paused.
124 252 MEI, "North-Bound Fault Interface down"
PMA North-Bound Fault Interface is down.
125 252 MEI, "North-Bound Fault Interface paused"
PMA North-Bound Fault Interface is paused.
126 252 MEI, "Fault Server down"
PMA Fault Server is down.
127 252 MEI, "Fault Server paused"
PMA Fault Server is paused.
128 252 MEI, "North-Bound Interface Kernel down"
PMA North-Bound Interface Kernel is down.
129 252 MEI, "Communication Adapter of North-Bound Interface down"
PMA Communication Adapter of North-Bound Interface is down.
130 252 DMA "Management Server change handling down"
Management Server change handling is down.
131 252 DMA "Management Server recovery handling down"
Management Server recovery handling is down.
132 252 MEI, "Management Server down"
PMA Management Server is down
140 253 DMA "Unix system critical error"
Unix system critical error.
141 253 DMA "Unix system error"
Unix system error.
142 253 DMA "Unix system warning"
Unix system warning.
145 252 DMA "Web Reporter Server down"
Web Reporter Server is down.
146 252 DMA "Web Reporter Periodical Report Generation Service down"
Web Reporter Periodical Report Generation Service is down.
147 252 DMA "Web Reporter IIS Service down"
Web Reporter IIS Service is down.
148 252 DMA "Web Reporter Trend Collection Service down"
Web Reporter Trend Collection Service is down.
150 252 DMA "Communication Server NMS/10 Adapter down"
Communication Server NMS/10 Adapter is down.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

287
56 NMS

SPT GPT Status SPT Description


151 252 DMA "Communication Server 6300 Adapter down"
Communication Server 6300 Adapter is down.
152 252 PMA "Communication Server SNMP Adapter down"
Communication Server SNMP Adapter is down.
153 252 DMA "Generic Performance Handler down"
Generic Performance Handler is down.
154 252 DMA "RNC communication adapter down"
RNC communication adapter is down.
155 252 DMA "PMS Data Saver process down"
PMS Data Saver process is down.
156 252 DMA "PMS Summary process down"
PMS Summary process is down.
157 252 DMA "PMS Ageing process down"
PMS Ageing process is down.
160 252 DMA "NMS/10 Agent down"
NMS/10 Agent is down.
161 252 DMA "NM2100 EMS Server down"
NM2100 EMS Server is down.
164 252 PMA "3GPP Adapter down"
3GPP Adapter is down.
165 252 DMA "Communication Server down"
Communication Server is down.
166 252 DMA "Communication Server paused"
Communication Server is paused.
168 252 DMA "Event received from an unknown NE"
Event received from an unknown network element, address
mapping is not available.
169 252 DMA "Unrecognized data content in NE generated data"
Unrecognized data content in network element generated data.
170 252 DMA "Generic Database Assistant down"
Generic Database Assistant is down.
171 252 DMA "Generic Communication Server Backup Controller down"
Generic Communication Server Backup Controller is down.
172 252 DMA "Data Collection Scheduler down"
Data Collection Scheduler is down.
173 252 DMA "Data Collector Process down"
Data Collector Process is down.
174 252 DMA "Real Time Manager down"
Real Time Manager is down.
175 252 DMA "Notification Handler Process down"
Notification Handler Process is down.
176 252 PMA "NWI3 communication adapter down"
NWI3 communication adapter is down.
177 252 PMA "NWI3 Registration Service down"
NWI3 Registration Service is down.
178 252 PMA "NWI3 Publication Service down"
NWI3 Publication Service is down.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

288
56 NMS

SPT GPT Status SPT Description


179 252 PMA "Generic discovery process down"
Generic discovery process is down.
180 252 PMA "TP4 Gateway process down"
TP4 Gateway process is down.
181 252 PMA "Generic Consistency Checker process down"
Generic Consistency Checker process is down.
182 252 PMA "IP Gateway process down"
IP Gateway process is down.
183 251 PMA "Configuration Backup failed"
Configuration Backup has failed.
184 251 DMA "DB/HW inconsistency (MODULE)"
Module parameters in the database and network element are
inconsistent.
185 251 DMA "DB/HW inconsistency (IF)"
Interface parameters in the database and network element are
inconsistent.
186 251 DMA "DB/HW inconsistency (E3C E3 IF)"
E3C E3 interface parameters in the database and network
element are inconsistent.
187 251 DMA "DB/HW inconsistency (E3C E2 IF)"
E3C E2 interface parameters in the database and network
element are inconsistent.
188 251 DMA "DB/HW inconsistency (CEU VPLP INV)"
CEU VPLP INV parameters in the database and network element
are inconsistent.
189 251 DMA "DB/HW inconsistency (CCS-UNI TV5IFPAR)"
CCS-UNI TV5IFPAR parameters in the database and network
element are inconsistent.
190 251 DMA "DB/HW inconsistency (CEU STM1PAR)"
CEU STM1PAR parameters in the database and network element
are inconsistent.
191 251 DMA "DB/HW inconsistency (CEU LPORT)"
CEU LPORT parameters in the database and network element
are inconsistent.
192 251 DMA "DB/HW inconsistency (CEU VPTTP)"
CEU VPTTP parameters in the database and network element
are inconsistent.
193 251 PMA "DB/HW inconsistency (Variant INV)"
Variant INV parameters in the database and network element
are inconsistent.
194 251 PMA "DB/HW inconsistency (Variant)"
Variant parameters in the database and network element are
inconsistent.
195 251 PMA "DB/HW inconsistency (FRU LPORT)"
FRU LPORT parameters in the database and network element
are inconsistent.
196 251 PMA "DB/HW inconsistency (SBU VC12)"
SBU VC12 parameters in the database and network element are
inconsistent.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

289
56 NMS

SPT GPT Status SPT Description


201 251 PMA "DB/HW inconsistency (SCU-H HDLC IF)"
SCU-H HDLC interface parameters in the database and network
element are inconsistent.
202 251 PMA "DB/HW inconsistency (SCU-H Ethernet IF)"
SCU-H Ethernet interface parameters in the database and
network element are inconsistent.
203 251 PMA "DB/HW inconsistency (SCU-H Extended Unit)"
SCU-H Extended Unit parameters in the database and network
element are inconsistent.
204 251 DMA "DB/HW inconsistency (GMX p12s)"
GMX p12s parameters in the database and network element are
inconsistent.
205 251 DMA "DB/HW inconsistency (LIU LPORT)"
LIU LPORT interface parameters in the database and network
element are inconsistent.
206 251 DMA "DB/HW inconsistency (LIU PPORT)"
LIU PPORT parameters in the database and network element
are inconsistent.
207 251 DMA "DB/HW inconsistency (LIU Extended Unit)"
LIU Extended Unit parameters in the database and network
element are inconsistent.
208 251 DMA "DB/HW inconsistency (FRU Extended Unit)"
FRU Extended Unit parameters in the database and network
element are inconsistent.
209 251 DMA "DB/HW inconsistency (ESO ISDN IF)"
ESO ISDN interface parameters in the database and network
element are inconsistent.
210 251 DMA "DB/HW inconsistency (ESO PSTN IF)"
ESO PSTN interface parameters in the database and network
element are inconsistent.
211 251 DMA "DB/HW inconsistency (ESO V51 IF)"
ESO V51 interface parameters in the database and network
element are inconsistent.
212 251 DMA "DB/HW inconsistency (ESO Extended Unit)"
ESO Extended Unit parameters in the database and network
element are inconsistent.
213 251 DMA "DB/HW inconsistency (CCO-UNI IF)"
CCO-UNI interface parameters in the database and network
element are inconsistent.
214 251 DMA "DB/HW inconsistency (CCS-UNI IF)"
CCS-UNI interface parameters in the database and network
element are inconsistent.
215 251 DMA "DB/HW inconsistency (CCO-UNI Extended Unit)"
CCO-UNI Extended Unit parameters in the database and network
element are inconsistent.
216 251 DMA "DB/HW inconsistency (CCS-UNI Extended Unit )"
CCS-UNI Extended Unit parameters in the database and network
element are inconsistent.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

290
56 NMS

SPT GPT Status SPT Description


217 251 DMA "DB/HW inconsistency (QMH IF)"
QMH interface parameters in the database and network element
are inconsistent.
218 251 DMA "DB/HW inconsistency (RBS IF)"
RBS interface parameters in the database and network element
are inconsistent.
219 251 DMA "DB/HW inconsistency (AIU VTI INV)"
AIU VTI INV interface parameters in the database and network
element are inconsistent.
220 251 DMA "DB/HW inconsistency (AIU VT IF)"
AIU VT interface parameters in the database and network
element are inconsistent.
221 251 DMA "DB/HW inconsistency (AIU IF)"
AIU interface parameters in the database and network element
are inconsistent.
222 251 DMA "DB/HW inconsistency (FRU LPORT)"
FRU LPORT parameters in the database and network element
are inconsistent.
223 251 DMA "DB/HW inconsistency (SMH V24 IF)"
SMH V24 interface parameters in the database and network
element are inconsistent.
224 251 DMA "DB/HW inconsistency (ECS X50)"
ECS X50 parameters in the database and network element are
inconsistent.
225 251 DMA "DB/HW inconsistency (ECS V110)"
ECS V110 parameters in the database and network element are
inconsistent.
226 251 DMA "DB/HW inconsistency (ECS MOD)"
ECS MOD parameters in the database and network element are
inconsistent
227 251 DMA "DB/HW inconsistency (XCG IF)"
XCG interface parameters in the database and network element
are inconsistent.
228 251 DMA "DB/HW inconsistency (ISD IF)"
ISD interface parameters in the database and network element
are inconsistent.
229 251 DMA "DB/HW inconsistency (GMU/GMX VCG)"
GMU/GMX VCG parameters in the database and network
element are inconsistent.
230 251 DMA "DB/HW inconsistency (GMU/GMX SNC)"
GMU/GMX SNC parameters in the database and network
element are inconsistent.
231 251 DMA "DB/HW inconsistency (GMU/GMX VC INV)"
GMU/GMX VC INV parameters in the database and network
element are inconsistent.
232 251 DMA "DB/HW inconsistency (GMU/GMX VC2 IF)"
GMU/GMX VC2 interface parameters in the database and
network element are inconsistent.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

291
56 NMS

SPT GPT Status SPT Description


233 251 DMA "DB/HW inconsistency (GMU/GMX VC12 IF)"
GMU/GMX VC12 interface parameters in the database and
network element are inconsistent.
234 251 DMA "DB/HW inconsistency (GMU/GMX 34M IF)"
GMU/GMX 34M interface parameters in the database and
network element are inconsistent.
235 251 DMA "DB/HW inconsistency (GMU/GMX STM1 IF)"
GMU/GMX STM1 interface parameters in the database and
network element are inconsistent.
236 251 DMA "DB/HW inconsistency (GMM TS)"
GMM TS parameters in the database and network element are
inconsistent.
237 251 DMA "DB/HW inconsistency (GMM IF)"
GMM interface parameters in the database and network element
are inconsistent.
238 251 DMA "DB/HW inconsistency (Al-Out)"
Al-Out parameters in the database and network element are
inconsistent.
239 251 DMA "DB/HW inconsistency (IUM IF)"
IUM interface parameters in the database and network element
are inconsistent.
240 251 DMA "DB/HW inconsistency (EPS IF)"
EPS interface parameters in the database and network element
are inconsistent.
241 251 DMA "DB/HW inconsistency (Al-In)"
Al-In parameters in the database and network element are
inconsistent.
242 251 DMA "DB/HW inconsistency (VMM IF)"
VMM interface parameters in the database and network element
are inconsistent.
243 251 DMA "DB/HW inconsistency (CCO IF)"
CCO interface parameters in the database and network element
are inconsistent.
244 251 DMA "DB/HW inconsistency (CCS IF)"
CCS interface parameters in the database and network element
are inconsistent.
245 251 DMA "DB/HW inconsistency (BB IF)"
BB interface parameters in the database and network element
are inconsistent.
246 251 DMA "DB/HW inconsistency (CAE IF)"
CAE interface parameters in the database and network element
are inconsistent.
247 251 DMA "DB/HW inconsistency (EAE IF)"
EAE interface parameters in the database and network element
are inconsistent.
248 251 DMA "DB/HW inconsistency (GCH IF)"
GCH interface parameters in the database and network element
are inconsistent.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

292
56 NMS

SPT GPT Status SPT Description


249 251 DMA "DB/HW inconsistency (GMH IF)"
GMH interface parameters in the database and network element
are inconsistent.
250 251 DMA "DB/HW inconsistency (VCM IF)"
VCM interface parameters in the database and network element
are inconsistent.
251 251 DMA "DB/HW inconsistency (NTU)"
NTU parameters in the database and network element are
inconsistent.
252 251 DMA "DB/HW inconsistency (unit)"
Unit parameters in the database and network element are
inconsistent.
253 251 DMA "DB/HW inconsistency (subrack)"
Subrack parameters in the database and network element are
inconsistent.
254 251 DMA "DB/HW inconsistency (node)"
Node parameters in the database and network element are
inconsistent.
255 250 PMA "NMS Control channel broken"
Control channel is broken.
256 250 PMA "Control Path too long for NTU transport service"
The control path is too long for the NTU transport service.
257 251 DMA "DB/HW inconsistency (ESU IF)"
ESU interface parameters in the database and network element
are inconsistent.
262 252 DMA "SLA Server process down"
PMS Data Saver (database) process is down.
263 252 DMA "Interval & utilization calculation process down"
Performance management Interval & utilization fault calculation
process down.
264 251 PMA,S "SRAM check required. Please contact Tellabs representative
for further instructions."
The serial number of the unit is included in the SRAM list. The
unit potentially contains a problematic SRAM component, and
has not been identified as repaired or checked yet.
501 252 DMA "Route Master unavailable"
Route Master is unavailable.
502 252 DMA "Route Master running configuration conflict"
Route Master running configuration conflict.
503 252 DMA "Route Master startup configuration conflict"
Route Master startup configuration conflict.
510 252 DMA "NetAct CORBA NameService not accessible"
NetAct CORBA NameService is not accessible.
511 252 DMA "NetAct NWI3 Registration Service not accessible"
NetAct NWI3 registration service is not accessible.
512 252 DMA "NetAct 3GPP AlarmIRP service not accessible"
NetAct 3GPP AlarmIRP service is not accessible.
513 252 DMA "NetAct 3GPP BCMIRP service not accessible"
NetAct 3GPP BCMIRP service is not accessible.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

293
56 NMS

SPT GPT Status SPT Description


514 252 DMA "NetAct 3GPP FMNotifIRP service not accessible"
NetAct 3GPP FMNotifIRP service is not accessible.
515 252 DMA "NetAct 3GPP BCMNotifIRP service not accessible"
NetAct 3GPP BCMNotifIRP service is not accessible.
516 252 DMA "RNC Mediator not accessible"
RNC Mediator is not accessible.
520 252 DMA "Corba name service down"
Corba name service is down.
521 252 DMA "Corba notification service down"
Corba notification service is down.
522 252 DMA "Customer service down"
Customer service is down.
523 252 DMA "Element management service down"
Element management service is down.
524 252 DMA "MPLS VPN Provisioning service down"
MPLS VPN Provisioning service is down.
525 252 DMA "Log service down"
Log service is down.
526 252 DMA "NMS Topology service down"
NMS Topology service is down.
527 252 DMA "Online Core Network Monitor service down"
Online Core Network Monitor service is down.
528 252 DMA "Packet Loop Testing service down"
Packet Loop Testing service is down.
529 252 DMA "QOS service down"
QOS service is down.
530 252 DMA "BGP Route Reflector front end service down"
BGP Route Reflector front end service is down.
531 252 DMA "Security service down"
Security service is down.
532 252 DMA "Authentication Keys service down"
Authentication Keys service is down.
533 252 DMA "PMS service down"
PMS service is down.
534 252 DMA "Network management service down"
Network management service is down.
536 252 DMA "System service down"
System service is down.
537 256 MEI, "Replication latency has exceeded the preset latency value"
DMA, Replication latency has exceeded the preset latency value.
PMA
538 256 DMA "Replication network link may be down"
Replication network link may be down.
539 253 MEI "HA cluster has performed a switch over"
HA cluster has performed a switch over
540 253 PMA "HA system suspect"
HA system suspect.

Tellabs ® 8000 Network Manager R17A 70178_03


Fault Management Problem Types © 2009 Tellabs.

294
56 NMS

SPT GPT Status SPT Description


541 253 MEI "Disk failure"
Disk failure.
542 253 MEI "Heart beat failure"
Heart beat failure.
543 253 MEI "LAN failure"
LAN failure.
544 253 MEI "Replication Server down"
Replication Server is down.
545 252 MEI "Server down"
Server is down.
546 256 DMA "Automatic Switchover"
Automatic switchover.
547 256 MEI "Manual Switchover"
Manual switchover.
548 252 MEI, "Backup has errors"
DMA, Backup has errors.
PMA
549 252 MEI, "DB check has errors"
DMA, Database check has errors.
PMA
550 252 MEI, "Index re-org has errors"
DMA, Index re-org has errors.
PMA
551 252 MEI, "DB suspect"
DMA, DB suspect.
PMA

551 256 MEI, "DB suspect"


DMA, DB suspect.
PMA
552 252 DMA "Service Management Service down"
Service Management Service is down.
553 252 DMA "Service Management Service process down"
Service Management Service process is down.
554 252 DMA "Macro Manager Service down"
Macro Manager Service is down.
555 252 DMA "Macro Manager process down"
Macro Manager process is down.
556 252 DMA "The TCP port range has been exhausted in 8600 node
communication"
The TCP port range defined is too small and cannot support
enough simultaneous connections to the Tellabs 8600 nodes.
557 252 DMA "The execution of automatic maintenance procedure failed"
The execution of an automatic maintenance procedure has failed.
558 252 DMA "Automatic maintenance procedures are overdue"
Automatic maintenance procedures are overdue.

70178_03 Tellabs ® 8000 Network Manager R17A


© 2009 Tellabs. Fault Management Problem Types

295

You might also like