9500 MPR Alarm - Clearing

Release 6.1.
0 3DB 19291 ABAA Edition 01

Alarm Clearing User Manual
Alcatel-Lucent 9500
MICROWAVE PACKET RADIO
Alarm Clearing User Manual
Alcatel-Lucent Proprietary
This document contains proprietary information of Alcatel-Lucent and is not to
be disclosed or used except in accordance with applicable agreements.
Copyright 2016 © Alcatel-Lucent. All rights reserved
Release 6.1.0 3DB 19291 ABAA Edition 01
All specifications, procedures, and information in this document are subject to change and revision at any time
without notice. The information contained herein is believed to be accurate as of the date of publication. Alcatel-
Lucent provides no warranty, express or implied, regarding its contents. Users are fully responsible for application
or use of the documentation.
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks
are the property of their respective owners.
Copyright 2016 Alcatel-Lucent.
All rights reserved.
Disclaimers
Alcatel-Lucent products are intended for commercial uses. Without the appropriate network design engineering,
they must not be sold, licensed or otherwise distributed for use in any hazardous environments requiring fail-safe
performance, such as in the operation of nuclear facilities, aircraft navigation or communication systems, air traffic
control, direct life-support machines, or weapons systems, in which the failure of products could lead directly to
death, personal injury, or severe physical or environmental damage. The customer hereby agrees that the use, sale,
license or other distribution of the products for any such application without the prior written consent of
Alcatel-Lucent, shall be at the customer's sole risk. The customer hereby agrees to defend and hold Alcatel-Lucent
harmless from any claims for loss, cost, damage, expense or liability that may arise out of or in connection with the
use, sale, license or other distribution of the products in such applications.
This document may contain information regarding the use and installation of non-Alcatel-Lucent products. Please
note that this information is provided as a courtesy to assist you. While Alcatel-Lucent tries to ensure that this
information accurately reflects information provided by the supplier, please refer to the materials provided with any
non-Alcatel-Lucent product and contact the supplier for confirmation. Alcatel-Lucent assumes no responsibility or
liability for incorrect or incomplete information provided about non-Alcatel-Lucent products.
However, this does not constitute a representation or warranty. The warranties provided for Alcatel-Lucent products,
if any, are set forth in contractual documentation entered into by Alcatel-Lucent and its customers.
This document was originally written in English. If there is any conflict or inconsistency between the English
version and any other version of a document, the English version shall prevail.
THIS PRODUCT COMPLIES WITH D.H.H.S. RADIATION PERFORMANCE STANDARDS 21 CFR, 1040.10,
FOR A CLASS 1 LASER PRODUCT.
DANGER
Invisible laser radiation is present when the optic connector is open. AVOID DIRECT EXPOSURE TO BEAM.
This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15
of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the
equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio
frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful
interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful
interference in which case users will be required to correct the interference at their own expense.
Release notes describing revisions to this software may impact operations described in this manual.
This transfer of commodities, technology, or software, if from the United States, is an export in accordance with the
U.S. Export Administration Regulations. Diversion contrary to U.S. law is prohibited. The export or re-export
(further transfer) of such commodities, technology, software or products made from such technology is prohibited
without proper authorization(s) from the U.S. Department of Commerce or other appropriate U.S. government
agencies.
Table of Contents
Preface ............................................................................................................... 17
9500 MPR documentation ................................................................................................... 17
Related documentation ................................................................................................. 19
Naming conventions in the documentation .......................................................................... 21
Audience ...................................................................................................................... 21
Information symbols ......................................................................................................... 21
Contact information ......................................................................................................... 22
Technical support ........................................................................................................ 22
Documentation feedback ............................................................................................... 22
1 — FCC part 15 subpart B ....................................................................................... 23

1.1 — 9500 MPR-A unlicensed radio ....................................................................................... 23
1.2 — FCC Class B compliance statement ................................................................................ 23
1.3 — FCC Class B requirements ........................................................................................... 24
2 — Maintenance philosophy ..................................................................................... 25

2.1 — Troubleshooting....................................................................................................... 25
2.2 — Before going to site checklist....................................................................................... 26
2.3 — Troubleshooting basics .............................................................................................. 27
2.3.1 — Troubleshooting path problems .............................................................................. 28
2.4 — Path problems on a commissioned link ........................................................................... 29
2.4.1 — Weather-related path degradation .......................................................................... 29
2.4.2 — Changed antenna alignment or antenna feed problem .................................................. 29
2.4.3 — New path obstruction.......................................................................................... 30
2.4.4 — Interference from other signal sources ..................................................................... 30
2.5 — Path problems on a new link........................................................................................ 30
2.5.1 — Incorrect antenna alignment ................................................................................. 30
2.5.2 — Mismatching antenna polarizations.......................................................................... 30
2.5.3 — Incorrect path calculations ................................................................................... 31
2.5.4 — Reflections ...................................................................................................... 31
2.6 — Troubleshooting configuration problems ......................................................................... 31
2.6.1 — Compatibility problems ....................................................................................... 31
2.6.2 — Incorrect circuit connections................................................................................. 31
2.6.3 — Incorrect ID naming and commissioning .................................................................... 32
2.6.4 — Incorrect/incompatible trib settings ........................................................................ 32
2.7 — Troubleshooting Ethernet problems ............................................................................... 32
2.7.1 — Troubleshooting TMN problems .............................................................................. 33
3 — Safety awareness.............................................................................................. 35
3.1 — Safety EMC-EMF-ESD norms and equipment labeling ........................................................... 35
3.2 — Safety rules............................................................................................................ 35
3.2.1 — General rules ................................................................................................... 35
3.2.1.1 — Observe safety rules..................................................................................... 35
3.3 — Labels indicating danger, forbidding, command ................................................................ 36
3.3.1 — Dangerous electrical voltages ................................................................................ 37
3.3.1.1 — Labeling: ................................................................................................. 37
9500 MPR Alarm Clearing 5

3.3.1.2 — Safety instructions: ..................................................................................... 38

3.3.2 — Risks of explosions ............................................................................................. 38
3.3.2.1 — Labeling: ................................................................................................. 38
3.3.3 — Moving mechanical parts ...................................................................................... 39
3.3.3.1 — Labeling: ................................................................................................. 39
3.3.4 — Equipment connection to earth.............................................................................. 39
3.3.4.1 — Labeling: ................................................................................................. 39
3.3.5 — Heat-radiating mechanical parts ............................................................................ 40
3.3.5.1 — Labeling: ................................................................................................. 40
3.3.6 — Microwave radiations (EMF norms) .......................................................................... 40
3.3.7 — Electromagnetic compatibility (EMC norms) ............................................................... 42
3.3.8 — Equipment protection against electrostatic discharges .................................................. 43
3.3.8.1 — Cautions to avoid equipment damage ................................................................ 44
3.3.8.2 — Anti static protection device kit ...................................................................... 44
3.3.8.3 — Screw fixing............................................................................................... 44
3.3.8.4 — MSS-ODU cable disconnection / connection ......................................................... 44
3.3.9 — Fan, equipment rack, and equipment cabinet precautions ............................................. 44
3.3.10 — Electrical precautions........................................................................................ 45
3.3.11 — Laser precautions ............................................................................................. 46
4 — Electrostatic-sensitive devices ............................................................................. 49

4.1 — Electrostatic-sensitivity ............................................................................................. 49
4.2 — Handling circuit packs ............................................................................................... 50
5 — Product support information for the ANSI market ..................................................... 51

5.1 — Telephone and email support ...................................................................................... 51
5.1.1 — Customer service telephone and email support ........................................................... 51
5.2 — Product documentation and training .............................................................................. 51
5.2.1 — Product documentation ....................................................................................... 51
5.2.2 — Training .......................................................................................................... 52
5.3 — Technical support center............................................................................................ 53
5.3.1 — After-hours emergency telephone support................................................................. 53
5.3.2 — After-hours nonemergency telephone support ............................................................ 53
5.3.3 — On-site technical support ..................................................................................... 54
5.4 — Repair and return services .......................................................................................... 54
5.5 — Spare parts and replacement cards................................................................................ 54
5.6 — Return for credit or warranty exchange procedure ............................................................. 54
5.7 — Service center......................................................................................................... 55
5.7.1 — Return for repair procedure .................................................................................. 55
5.7.2 — Shipping instructions for repair, credit, or warranty exchange......................................... 55
5.8 — Installation and maintenance services ............................................................................ 56
5.8.1 — Engineering and installation service ........................................................................ 56
5.8.2 — Contract maintenance service ............................................................................... 56
6 9500 MPR Alarm Clearing

6 — Alarm and abnormal condition clearing procedures ................................................... 57

6.1 — Alarm manager / Craft Terminal................................................................................... 58
6.1.1 — Equipment / facility column ................................................................................. 58
6.1.2 — Friendly name / entity column .............................................................................. 59
7 — Supporting information .................................................................................... 177
8 — Facility alarms ............................................................................................... 181

8.1 — Purpose................................................................................................................181
8.2 — General................................................................................................................181
8.3 — Procedure.............................................................................................................183
9 — Abnormal conditions ....................................................................................... 205

9.1 — Purpose................................................................................................................205
9.2 — General................................................................................................................205
9.3 — Procedure.............................................................................................................206
10 — Power alarms ............................................................................................... 219

10.1 — Purpose ..............................................................................................................219
10.2 — General ..............................................................................................................219
10.3 — Procedure ...........................................................................................................220
11 — Equipment alarms ......................................................................................... 239

11.1 — Purpose ..............................................................................................................239
11.2 — General ..............................................................................................................239
11.3 — Procedure ...........................................................................................................240
12 — Radio alarms (MPT-HC, MPT-HC-HQAM, MPT-HL, MPT-HLC, MPT-HLS, MPT-XP,

MPT-XP-HQAM) .................................................................................................... 259
12.1 — Purpose ..............................................................................................................259
12.2 — General ..............................................................................................................259
12.3 — Procedure ...........................................................................................................260
13 — Ethernet alarms (Core-E, CorEvo, EASv2, MPTACC, P8ETH, MSS-O Shelf, MSS-1
Shelf)................................................................................................................ 285
13.1 — Purpose ..............................................................................................................285
13.2 — General ..............................................................................................................285
13.3 — Procedure ...........................................................................................................285
14 — License/software mismatch ............................................................................. 289

14.1 — Purpose ..............................................................................................................289
14.2 — General ..............................................................................................................289
14.3 — Procedure ...........................................................................................................290
15 — Internal loss of communications........................................................................ 295

15.1 — Purpose ..............................................................................................................295
15.2 — General ..............................................................................................................295

15.3 — Procedure ...........................................................................................................296
16 — Threshold crossing alarms (MPT-HC, MPT-HC-HQAM, MPT-HL, MPT-HLC,

MPT-HLS, MPT-XP, MPT-XP-HQAM, P32E1DS1, SDHACC, MSS-1 shelf) ................................. 309
16.1 — Purpose ..............................................................................................................309
16.2 — General ..............................................................................................................309
16.3 — Procedure ...........................................................................................................310
17 — Synchronization alarms (Core-E, CorEvo, MPT-HC, MPT-HC-HQAM, MPT-HL,

MPT-HLC, MPT-HLS, MPT-XP, MPT-XP-HQAM, P32E1DS1, SDHACC) .................................... 319
17.1 — Purpose ..............................................................................................................319
17.2 — General ..............................................................................................................319
17.3 — Procedure ...........................................................................................................320
18 — ATPC loop condition (MPT-HC, MPT-HC-HQAM, MPT-HL, MPT-HLC, MPT-HLS,

MPT-XP, MPT-XP-HQAM) ........................................................................................ 333
18.1 — Purpose ..............................................................................................................333
18.2 — General ..............................................................................................................333
18.3 — Procedure ...........................................................................................................333
19 — DemXPIC LOS ............................................................................................... 341

19.1 — Purpose ..............................................................................................................341
19.2 — General ..............................................................................................................341
19.3 — Procedure ...........................................................................................................341
20 — Loss of alignment (MPT-HC, MPT-HL, MPT-HLC, MPT-HLS, MPT-XP) ............................ 345

20.1 — Purpose ..............................................................................................................345
20.2 — General ..............................................................................................................345
20.3 — Procedure ...........................................................................................................345
21 — Loss of frame (MPT-HC, MPT-HC-HQAM, MPT-HL, MPT-HLC, MPT-HLS, MPT-XP,

MPT-XP-HQAM) .................................................................................................... 349
21.1 — Purpose ..............................................................................................................349
21.2 — General ..............................................................................................................349
21.3 — Procedure ...........................................................................................................349
22 — RPS path fail (MPT-HC, MPT-MC, MPT-HL, MPT-HLC, MPT-XP).................................... 359

22.1 — Purpose ..............................................................................................................359
22.2 — General ..............................................................................................................359
22.3 — Procedure ...........................................................................................................359
23 — Housekeeping alarms ..................................................................................... 365

23.1 — Purpose ..............................................................................................................365
23.2 — General ..............................................................................................................365
23.3 — Procedure ...........................................................................................................365

24 — LAG alarms (Core-E, CorEvo, MPT-HC, MPT-HL, MPT-HC-HQAM, MPT-HLC,

MPT-HLS, MPT-XP, MPT-XP-HQAM, OC-3, MSS-1 shelf) ................................................... 367
24.1 — Purpose ..............................................................................................................367
24.2 — General ..............................................................................................................367
24.3 — Procedure ...........................................................................................................368
25 — Ethernet connectivity fault management alarms ................................................... 373

25.1 — Purpose ..............................................................................................................373
25.2 — General ..............................................................................................................373
25.3 — Procedure ...........................................................................................................374
26 — Clock failure (MPT-HC, MPT-HC-HQAM, MPT-HL, MPT-HLC, MPT-HLS, MPT-XP,

MPT-XP-HQAM) .................................................................................................... 377
26.1 — Purpose ..............................................................................................................377
26.2 — General ..............................................................................................................377
26.3 — Procedure ...........................................................................................................377
27 — Duplicate Address Detected alarms.................................................................... 385

27.1 — Purpose ..............................................................................................................385
27.2 — General ..............................................................................................................385
27.3 — Procedure ...........................................................................................................386
28 — Combiner loss of alignment (MPT-HLC or MPT-HLS) ................................................ 393

28.1 — Purpose ..............................................................................................................393
28.2 — General ..............................................................................................................393
28.3 — Procedure ...........................................................................................................393
29 — Fan Fail (MPT-HLC) ........................................................................................ 399

29.1 — Purpose ..............................................................................................................399
29.2 — General ..............................................................................................................399
29.3 — Procedure ...........................................................................................................399
30 — Fan Communication Problem (MPT-HLS).............................................................. 403

30.1 — Purpose ..............................................................................................................403
30.2 — General ..............................................................................................................403
30.3 — Procedure ...........................................................................................................403
31 — RF Switch Fail (MPT-HLC or MPT-HLS)................................................................. 407

31.1 — Purpose ..............................................................................................................407
31.2 — General ..............................................................................................................407
31.3 — Procedure ...........................................................................................................407
32 — Rx diversity missing (MPT-HLC or MPT-HLS) ......................................................... 411

32.1 — Purpose ..............................................................................................................411
32.2 — General ..............................................................................................................411
32.3 — Procedure ...........................................................................................................411

33 — Radio encryption mismatch (MPT-HC, MPT-HC-HQAM, MPT-HLC, MPT-HLS,

MPT-XP, MPT-XP-HQAM) ........................................................................................ 415
33.1 — Purpose ..............................................................................................................415
33.2 — General ..............................................................................................................415
33.3 — Procedure ...........................................................................................................415
34 — Critical Link Event (Core-E, EASv2, P8ETH).......................................................... 419

34.1 — Purpose ..............................................................................................................419
34.2 — General ..............................................................................................................419
34.3 — Procedure ...........................................................................................................419
35 — OAM discovery not completed (Core-E, CorEvo, EASv2, P8ETH, MSS-1, MSS-O).............. 423
35.1 — Purpose ..............................................................................................................423
35.2 — General ..............................................................................................................423
35.3 — Procedure ...........................................................................................................423
36 — Rate mismatch (CorEvo).................................................................................. 427

36.1 — Purpose ..............................................................................................................427
36.2 — General ..............................................................................................................427
36.3 — Procedure ...........................................................................................................427

List of Figures
3 — Safety awareness.............................................................................................. 35
Figure 3.1 — Compliance boundaries for 9500 MPR transceivers with 1ft (30 cm) antenna:..................... 42
Figure 3.2 — Anti static protection device kit........................................................................... 44
4 — Electrostatic-sensitive devices ............................................................................. 49

Figure 4.1 — Electrostatic-sensitive sign ................................................................................. 49


List of Tables
Preface ............................................................................................................... 17
Table 1 — 9500 MPR documentation ..................................................................................... 17
Table 2 — 9500 MPR related documentation............................................................................ 19
Table 3 — Naming conventions ........................................................................................... 21
6 — Alarm and abnormal condition clearing procedures ................................................... 57

Table 6.1 — Friendly Name/Entity Syntax ............................................................................... 59
Table 6.2 — Friendly name syntax definitions .......................................................................... 61
Table 6.3 — Alarm monitor alarm types ................................................................................. 64
Table 6.4 — Abnormal condition .........................................................................................145
Table 6.5 — Core-E Card LED indications ...............................................................................164
Table 6.6 — CorEvo Card LED indications ..............................................................................165
Table 6.7 — MSS-1 shelf LED indications ................................................................................166
Table 6.8 — Transport Card LED indications ...........................................................................167
Table 6.9 — Ethernet LED indications ...................................................................................168
Table 6.10 — MPT-HL transceiver LED alarm indications ............................................................169
Table 6.11 — MPT-HLC transceiver LED alarm indications ...........................................................171
Table 6.12 — MPT-HLS transceiver front panel indicator details ...................................................173
Table 6.13 — TMN network troubleshooting ...........................................................................174
7 — Supporting information .................................................................................... 177

Table 7.1 — Supporting information .....................................................................................177
8 — Facility alarms ............................................................................................... 181

Table 8.1 — Facility alarms ...............................................................................................183
9 — Abnormal conditions ....................................................................................... 205

Table 9.1 — Abnormal conditions ........................................................................................206
10 — Power alarms ............................................................................................... 219

Table 10.1 — Power Alarms ...............................................................................................220
11 — Equipment alarms ......................................................................................... 239

Table 11.1 — Equipment alarms .........................................................................................240
12 — Radio alarms (MPT-HC, MPT-HC-HQAM, MPT-HL, MPT-HLC, MPT-HLS, MPT-XP,

MPT-XP-HQAM) .................................................................................................... 259
Table 12.1 — Radio alarms ................................................................................................261
13 — Ethernet alarms (Core-E, CorEvo, EASv2, MPTACC, P8ETH, MSS-O Shelf, MSS-1
Shelf)................................................................................................................ 285
Table 13.1 — Ethernet alarms ............................................................................................285

14 — License/software mismatch ............................................................................. 289

Table 14.1 — License/software mismatch alarms .....................................................................290
15 — Internal loss of communications........................................................................ 295

Table 15.1 — Internal communication problem alarms ..............................................................296
16 — Threshold crossing alarms (MPT-HC, MPT-HC-HQAM, MPT-HL, MPT-HLC,

MPT-HLS, MPT-XP, MPT-XP-HQAM, P32E1DS1, SDHACC, MSS-1 shelf) ................................. 309
Table 16.1 — Threshold crossing alarms ................................................................................310
17 — Synchronization alarms (Core-E, CorEvo, MPT-HC, MPT-HC-HQAM, MPT-HL,

MPT-HLC, MPT-HLS, MPT-XP, MPT-XP-HQAM, P32E1DS1, SDHACC) .................................... 319
Table 17.1 — Sync alarms .................................................................................................320
18 — ATPC loop condition (MPT-HC, MPT-HC-HQAM, MPT-HL, MPT-HLC, MPT-HLS,

MPT-XP, MPT-XP-HQAM) ........................................................................................ 333
Table 18.1 — ATPC loop conditions ......................................................................................334
19 — DemXPIC LOS ............................................................................................... 341

Table 19.1 — Clear radio alarms .........................................................................................342
20 — Loss of alignment (MPT-HC, MPT-HL, MPT-HLC, MPT-HLS, MPT-XP) ............................ 345

Table 20.1 — Loss of alignment alarms .................................................................................345
21 — Loss of frame (MPT-HC, MPT-HC-HQAM, MPT-HL, MPT-HLC, MPT-HLS, MPT-XP,

MPT-XP-HQAM) .................................................................................................... 349
Table 21.1 — Loss of frame radio alarms ...............................................................................350
22 — RPS path fail (MPT-HC, MPT-MC, MPT-HL, MPT-HLC, MPT-XP).................................... 359

Table 22.1 — RPS path fail alarms .......................................................................................360
23 — Housekeeping alarms ..................................................................................... 365

Table 23.1 — Housekeeping alarms ......................................................................................366
24 — LAG alarms (Core-E, CorEvo, MPT-HC, MPT-HL, MPT-HC-HQAM, MPT-HLC,

MPT-HLS, MPT-XP, MPT-XP-HQAM, OC-3, MSS-1 shelf) ................................................... 367
Table 24.1 — LAG alarms ..................................................................................................368
25 — Ethernet connectivity fault management alarms ................................................... 373

Table 25.1 — ECFM alarms ................................................................................................374
26 — Clock failure (MPT-HC, MPT-HC-HQAM, MPT-HL, MPT-HLC, MPT-HLS, MPT-XP,

MPT-XP-HQAM) .................................................................................................... 377
Table 26.1 — Clock failure alarm ........................................................................................378

27 — Duplicate Address Detected alarms.................................................................... 385

Table 27.1 — Duplicate address detected alarms .....................................................................386
28 — Combiner loss of alignment (MPT-HLC or MPT-HLS) ................................................ 393

Table 28.1 — Combiner loss of alignment alarm ......................................................................394
29 — Fan Fail (MPT-HLC) ........................................................................................ 399

Table 29.1 — Fan fail alarm ..............................................................................................399
30 — Fan Communication Problem (MPT-HLS).............................................................. 403

Table 30.1 — Fan fail alarm ..............................................................................................403
31 — RF Switch Fail (MPT-HLC or MPT-HLS)................................................................. 407

Table 31.1 — RF Switch Fail alarms ......................................................................................407
32 — Rx diversity missing (MPT-HLC or MPT-HLS) ......................................................... 411

Table 32.1 — Rx diversity missing alarm ................................................................................412
33 — Radio encryption mismatch (MPT-HC, MPT-HC-HQAM, MPT-HLC, MPT-HLS,

MPT-XP, MPT-XP-HQAM) ........................................................................................ 415
34 — Critical Link Event (Core-E, EASv2, P8ETH).......................................................... 419

Table 34.1 — Critical link event alarm ..................................................................................420
35 — OAM discovery not completed (Core-E, CorEvo, EASv2, P8ETH, MSS-1, MSS-O).............. 423
36 — Rate mismatch (CorEvo).................................................................................. 427

Table 36.1 — Rate mismatch alarms ....................................................................................427


Preface
9500 MPR documentation

Table 1 describes the 9500 MPR documentation. See the current Release Notice for part
numbers.
Table 1 — 9500 MPR documentation
Document Description
Alcatel-Lucent Provides a general description of the 9500 MPR product,

9500 MPR Product solutions available, associated components, applications, and
Information Manual some Engineering specifications
This guide replaces the following from previous releases:
• ANSI Product Information
• Product Information and Planning chapters from the ETSI
MSS-1/4/8 User Manual and the MPR-e and MSS-1c User
Manual
Alcatel-Lucent Provides detailed procedures for the initial installation of the

9500 MPR Hardware radio and for replacement of hardware components
Installation and This guide replaces the following from previous releases:
Replacement Manual
• ANSI Installation Practices
• Hardware sections of the Installation chapters from the
ETSI MSS-O/1/4/8 User Manual and the MPR-e and MSS-1c
User Manual
• Hardware replacement procedures from ANSI Maintenance
and Trouble Clearing
Alcatel-Lucent Provides detailed procedures for the initial installation of the

9500 MPR Software 9500 MPR software, software upgrade to the current release,
Installation and NE and software rollback to a previous release
Upgrade Manual This guide replaces the following from previous releases:
• ANSI Software Installation and Upgrade
• Software sections of the Installation chapters from the
ETSI MSS-O/1/4/8 User Manual and the MPR-e and MSS-1c
User Manual

Alcatel-Lucent Provides procedures for performing system operations using the

9500 MPR WebCT WebCT interface, including monitoring and maintenance
User Manual activities. This guide describes, along with the WebEML User
Guide, how to provision, operate, and monitor a shelf with a
CorEvo card.

9500 MPR WebEML WebEML interface, including: provisioning, performance
User Manual monitoring, protection switching, and administration activities.
This guide describes how to provision, operate, and monitor a
radio in a split-mount configuration.
• ANSI Operation and Administration
• NE Management by Software Application chapter from the
ETSI MSS-O/1/4/8 User Manual
• Provisioning chapter from the ETSI MSS-1/4/8 User Manual

9500 MPR MCT User MCT interface, including: provisioning, performance monitoring,
Manual protection switching, and administration activities. This guide
describes how to provision, operate, and monitor a radio in MPR-
e standalone, MSS-1c or Single NE with 7705 SAR configuration.
• NE Management by Software Application chapter from the
MPR-e and MSS-1c User Manual
• Provisioning chapter from the MPR-e and MSS-1c User
Manual
• Maintenance and Trouble Clearing chapter from the MPR-e
and MSS-1c User Manual
Alcatel-Lucent Provides procedures for system installation verification,

9500 MPR Turn-up provisioning, turn-up, and acceptance testing. The guide is to be
Manual used only during initial system turn-up. It is not intended to be
used after equipment has been formally accepted (that is, for
maintenance, system growth, system upgrade, or provisioning
activities).
• ANSI Turn-up
• Lineup and Commissioning chapters from the ETSI MSS-O/
1/4/8 User Manual and the MPR-e and MSS-1c User Manual

Alcatel-Lucent Provides procedures related to the maintenance of the radio

9500 MPR Alarm including how to clear alarms and abnormal conditions. This
Clearing User guide is intended to be used after the equipment has been
Manual installed and tested by the installation and test teams
• ANSI Maintenance and Trouble Clearing
• Maintenance and Trouble Clearing chapter from the ETSI
MSS-O/1/4/8 User Manual
Related documentation
Table 2 describes the 9500 MPR related documentation. See the Release Notice for part
numbers.
Table 2 — 9500 MPR related documentation
Guide Description
Alcatel-Lucent Provides engineering drawings for the 9500 MPR-A

9500 MPR-A
Engineering Support
Documentation
Alcatel-Lucent Provides space to record measurements, capture screen shots,

9500 MPR Test capture photos, and record other information. TRDS tabs serve
Results Data Sheet as records of completion of indicated steps in a Turn-up
procedure. Not all procedures require entries in the TRDS.
Alcatel-Lucent 9500 Provides information about using the configuration file.

MPR Configuration
File Management
Manual

Table 2 — (Continued)9500 MPR related documentation
Guide Description
Alcatel-Lucent Provides transmit power specifications

9500 MPR-A MPT-HL/
HLC Engineering
Specifications
Alcatel-Lucent
9500 MPR-A MPT-
HC/MPR-e
Engineering
Specifications
Alcatel-Lucent
9500 MPR-A MPT-
HQAM Engineering
Specifications
Alcatel-Lucent
9500 MPR-A ODU300
Engineering
Specifications
9500 MPR Frequency Provides part number and tuning information for MPT-MC, HC,
Plan for MPT XP, HC-HQAM and XP-HQAM radios, for modules and for external
Outdoor diplexers.
Transceivers
Alcatel-Lucent Provides technical specifications for MPT Outdoor transceivers,

9500 MPR Technical including general specifications such as dimensions, and radio
Specifications for specifications such as system gain or throughput.
Split Mount
Applications
Alcatel-Lucent Provides technical specifications for MPT-HLC and HLS.

9500 MPR Technical
Specifications for
Full Indoor
Applications
Alcatel-Lucent 9500 Describes TMN networking in the 9500 MPR.

MPR TMN
Networking Guide
Alcatel-Lucent 9500 Provides information about supported cross-connections.

MPR Cross-
connections
Reference Tables

Audience
Naming conventions in the documentation

The generic terms described in Table 3 are used when the topic applies to all of the related
items listed. If the topic is specific to one or a subset of the items listed, the specific names
will be stated in the guide.
Table 3 — Naming conventions
Term Refers to
MPT-HC MPT-HC V2
EAS P8ETH and EASv2 cards

Core Core-E and CorEvo cards
MSS/CORE ports of MSS-O and MSS-1
CorEvo CorEvo-1G and CorEvo-10G cards
PDH E1, DS1, and DS3

SDH STM-1 and OC-3
Audience
This guide is intended for network installers and system administrators who are responsible
for installing, configuring, or maintaining networks. This guide assumes you are familiar
with electronic and networking technologies.
Information symbols
Observe the warnings and notes to avoid injury or equipment damage during installation
and maintenance. Follow the safety procedures and guidelines when working with and near
electrical equipment. Warning statements and notes are provided in each chapter.
The following symbols are contained in the 9500 MPR documentation.

Contact information
Danger: indicates that the described activity or situation may result in serious
personal injury or death; for example, high voltage or electric shock hazards.
Warning: indicates that the described activity or situation may, or will, cause
equipment damage or serious performance problems.
Caution: indicates that the described activity or situation may, or will, cause
service interruption.
Note: provides information that is, or may be, of special interest.
Contact information
Technical support
If you purchased a service agreement for your 9500 MPR and related products from a
distributor or authorized reseller, contact the technical support staff for that distributor or
reseller for assistance. If you purchased an Alcatel-Lucent service agreement, check this
link for instructions to contact Support personnel:
Web: http://support.alcatel-lucent.com
Documentation feedback
If you have questions or comments about this documentation, please contact:
[email protected]

1 — FCC part 15 subpart B
1.1 — 9500 MPR-A unlicensed radio

The JF6-9558H/6933B-9500MPT (MPT-HL) unlicensed radio provides fast deployment
of service with microwave radio. No license and small antennas (no FCC and Industry
Canada requirements) allow immediate turn-up. After the license is received, the
unlicensed MPT-HL radio can be easily converted to the lower 6 GHz licensed band.
The JF6-9558HC/6933B-9558HC (9558HC) unlicensed radio provides fast deployment of

service with microwave radio. No license and small antennas (no FCC and Industry Canada
requirements) allow immediate turn-up. The 9558HC unlicensed radio can not be upgraded
to licensed operation.
The JF6-9558H/6933B-9500MPT and JF6-9558HC/6933B-9558HC unlicensed radio

operates in the 5725-5850 Information, Scientific, and Medical (ISM) band in accordance
with FCC Part 15.247 and IC RSS-210. This unlicensed radio, although operating in the
same band as a spread spectrum radio, operates using narrower bandwidths than spread
spectrum.
The 9558HC 5.8 Unlicensed band (JF6-9558HC/6933B-9558HC) has been certified by the
FCC and Industry Canada as of August 7, 2012.
1.2 — FCC Class B compliance statement

The JF6-9558H/6933B-9500MPT and JF6-9558HC/6933B-9558HC unlicensed radio have
been tested and found to comply with the limits for a Class B digital device, pursuant to
Part 15 of the FCC Rules and IC RSS-210. These limits are designed to provide reasonable
protection against harmful interference when the equipment is operated in a commercial
environment. This equipment generates, uses, and can radiate radio frequency energy and,
if not installed and used in accordance with the instruction manual, may cause harmful
interference to radio communications. Operation of this equipment in a residential area is
likely to cause harmful interference in which case the user will be required to correct the
interference at his own expense.

FCC Class B requirements
1.3 — FCC Class B requirements

This device complies with part 15 of the FCC Rules and IC RSS-210. Operation is subject
to the following three conditions: (1) this device may not cause harmful interference. (2)
This device must accept any interference received, including interference that may cause
undesired operation. (3) This device must be professionally installed.
Cet appareil radio est conforme à IC RSS-210. Son fonctionnement respecte les trois
conditions suivantes: 1) cette radio ne cause pas d’interférences néfastes, 2) cette radio peut
recevoir des interférences, ainsi que des interférences qui peuvent causer des opérations
non désirées, et 3) cette radio doit être installée par des Professionnels.
Caution: Changes or modifications not expressly approved by Alcatel-Lucent could void

the authority to operate the JF6-9558H/6933B-9500MPT and JF6-9558HC/6933B-9558HC
(unlicensed) radio.
Caution: Installation, Turn-Up, Maintenance, and Operation Instruction supplied with the
JF6-9558H/6933B-9500MPT and JF6-9558HC/6933B-9558HC (unlicensed) radio require
strict adherence for continued part 15 of the FCC Rules and IC RSS-210 compliance.
Warning: Regulatory compliance warning: Physical changes or modifications to the

JF6-9558H/6933B-9500MPT and JF6-9558HC/6933B-9558HC (unlicensed) radio are strictly
prohibited.

2 — Maintenance philosophy
Maintenance of the system consists of repair and preventive maintenance. Repair covers
isolation of faults, troubleshooting to the circuit card level, and subsequent replacement of
the faulty circuit card. Circuit card repair is not covered. Preventive maintenance covers
periodic routine tasks that are performed to ensure continued proper operation of the
system.
The system incorporates both software- and firmware-based diagnostics to continuously

monitor system integrity. Also available are diagnostics that can be manually invoked.
Problems detected by diagnostics are reported as alarm/event messages displayed at a user
terminal and/or lighted alarm indicators on the equipment. These messages and lights are
the primary trouble analysis tools for fault isolation.
The instruction “contact next level of technical support for assistance” appears throughout
this manual. The intent of this statement is to escalate the problems that are beyond the
scope of this Task Oriented Practice (TOP) to a higher level of expertise. Users who have
local interim levels and/or procedures should implement those in response to this
instruction. See the Introduction for customer access (HELP) contacts.
2.1 — Troubleshooting
Troubleshooting procedures generally assume the following conditions:
• An alarm indication was received through the Alarm Monitor, Craft Terminal or a
lighted alarm indicator.
• Maintenance personnel are familiar with system operation and use of the Alarm
Monitor and Craft Terminal.
• Maintenance personnel have system administration privileges or a system
administrator is available.
• Replacement components (spares) are available and fully functional.
The following guidelines and information should be observed during troubleshooting:
• Trouble clearing begins with an analysis of alarm indications. The correct chapter is
referenced in the index.

Before going to site checklist
• Clear upstream problems first. This may also clear downstream problems.
• As a rule, no main circuit card should be physically removed unless traffic was
manually switched to protection by entering the appropriate Craft Terminal
command. Exceptions to this are addressed in specific chapters.
• As a rule, no protection circuit card should be physically removed unless a manual
lockout switch issued by entering the appropriate Craft Terminal command.
Exceptions to this are addressed in specific chapters.
• As a rule, in unprotected radio configurations physically removing a circuit card will
cause a loss of traffic. Exceptions to this are addressed in specific chapters.
• To avoid unnecessary service interruption, exercise care when removing circuit
cards, performing commands, and doing other maintenance tasks.
• The procedures in this manual are used to aid in clearing alarms for which protection
is available. If alarms exist on both a card and its mate card, or if alarms exist on a
card and its mate card is not available for protection, always contact the next level of
technical support for assistance with clearing the alarms.
• Always follow electrostatic-sensitive device procedures when handling circuit cards.
• After circuit card replacement, allow time for alarms to clear. As a general rule, allow
a minimum of 120 seconds to clear. Some alarms may take longer to clear. Allow
time for the alarm to clear before assuming the replacement did not clear the trouble.
• When replacing a circuit card does not clear the trouble, remove the replacement
circuit card and return the original circuit card to service.
• When troubleshooting procedures fail to clear the fault, an obscure or multiple fault
is assumed to exist.
2.2 — Before going to site checklist

Where possible, before going to site obtain the following information:
• Does the fault require immediate attention?

• Determine who is the best-placed person to attend the fault.
• Confirm the nature and severity of the reported fault, its location, 9500 MPR type,
frequency band, high/low end ODU or MPT-HL Transceiver, capacity modulation
and configuration (non protected, protected, diversity). Ask:
• Is just one 9500 MPR link affected, or a number of links in the same
geographical area?
• Is the path down completely or is traffic passing but with a BER alarm?
• Is only one or a number of tributaries affected?
• Could the fault be in the equipment connected to 9500 MPR, rather than in 9500
MPR? Are there alarms on other, connected equipment?

Troubleshooting basics
• Is it a hard or intermittent fault?

• Do alarms confirm which end of an alarmed link is faulty?
• Could the weather (rain, ice, high wind, temperature) be a factor in the reported fault?
Note: If the fault suggests a rain fade or other weather related fade condition and it
matches the prevailing weather conditions, do not take any action until the weather
abates.
• Does link history suggest any fault trends?
• Does the fault history for the link indicate a likely cause?
• Is the 9500 MPR link newly installed?
• Has there been any recent work done on the link?
• Ensure that you have with you:
• Appropriate spares. Where an equipment failure is suspected, these should
include replacement Cards/plug-ins, MPT-HL Transceiver and ODU. If an
ODU is suspected then local/national climbing safety requirements must be
adhered to.
• A laptop PC loaded with Craft Terminal, and an Ethernet cable. If an Ethernet
connection is to be used, you need the 9500 MPR Node/Terminal IP address
and also the addresses for any remote sites to be accessed.
• If login security has been enabled, you need the ‘engineer’ password for the
local and also any remote sites to be accessed.
• Any special test equipment that may be needed, such as a BER tester.
• Toolkit.
• Key(s) for access to the site.
2.3 — Troubleshooting basics

This section provides general guidance on 9500 MPR troubleshooting:
Check front-panel LED indications. These provide summary alarm indications, which can
help narrow down the location and type of failure. See addresses Alarm and abnormal
condition clearing procedures for more information.
Note: Where a Status LED on a plug-in is off (unlit), but power to the MSS is confirmed by
LEDs on other plug-ins, check the seating of the affected plug-in.
Check Main Screen. When logging into 9500 MPR with Craft Terminal, the opening screen
is the Main Screen. Use the information provided to check for severity and problem type.
See Table 6.3 for probable cause and recommended action.

Troubleshooting basics
Check the basics first.
• For example, if multiple alarms are present, and these include power supply voltage
or hardware alarms, always check their cause before looking at resultant down-stream
path failure or path warning (signal) alarms.
• Similarly, if a path-related failure is indicated (no hardware or software alarms),
investigate the path. Go to the Craft Terminal History screen (15 minute view) to
check supporting data, such as low RSL and incidence of intermittent pre-failure BER
alarms, which if present are evidence of a path-related failure. See Troubleshooting
path problems in this chapter for more information.
Check if symptoms match the alarm. Alarms reflect the alarm state, but in exceptional
circumstances an alarm may be raised because of a failure to communicate correctly with
the alarm source, or a failure in alarm management processing. Always check to see if
symptoms match the alarm, using LED indications and the Craft Terminal.
Check if recent work may be a cause. Recent work at the site may be a cause or contributing
factor. Check for a configuration change, software upgrade, power recycling (reboot), or
other site work:
• Many hardware alarms are only initiated as a loss-of-communications alarm during a

reboot, software upgrade, or reconfiguration. By not being able to communicate with
the Core, their settings cannot be loaded. The fault may be at the hardware device
(most likely), communications to it, or the Core.
• Hardware/software compatibility alarms will be raised when a new plug-in is
installed that needs a later version of 9500 MPR software.
• Hardware incompatible alarms will be raised when a plug-in is installed in a slot that
has been configured for a different plug-in.
MSS before an ODU. If there is doubt about whether a fault is in the MSS or ODU, always
troubleshoot the MSS first.
Hot-pluggable. MSS cards are hot-pluggable. There is no need to power-down before

replacing, but traffic will be lost unless the plug-in is protected.
Plug-in restoration time. Ensure adequate time is allowed for services to resume when a
plug-in is replaced.
2.3.1 — Troubleshooting path problems

A path-related problem, with the exceptions of interference, reflection, or multipath, is
characterized by traffic being similarly affected in both directions. Generally, if you are
experiencing only a one-way problem, it is not a path problem.

Path problems on a commissioned link
Note: A path extends from ODU or MPT-HL antenna port to ODU or MPT-HL antenna port.
Normally a path problem is signaled by a reduced RSL, and depending on its severity, a
high BER.
Only in worst case situations, such as an antenna knocked out of alignment, will a path fail
completely, and stay that way.
For weather-related problems, such as rain or ducting, the path problem will disappear as
the weather returns to normal.
2.4 — Path problems on a commissioned link

A path problem on an existing link, one that has been operating satisfactorily may be caused
by:
• Weather-related path degradation

• Changed antenna alignment or antenna feed problem
• New path obstruction
• Interference from other signal sources
2.4.1 — Weather-related path degradation

If BER alarms are fleeting/not permanent and RSL returns to its normal, commissioned
level after the alarm is cleared, rain, diffraction, or multipath fading is indicated. Rain fade
is the likely cause of fade for links 13 GHz and higher. Diffraction and multipath/ducting
for links 11 GHz and lower. If these alarms are persistent, there could be a problem with
the link design or original installation.
2.4.2 — Changed antenna alignment or antenna feed problem

If RSLs do not return to commissioned levels after a period of exceptionally strong winds,
suspect antenna alignment. Also, check the antenna for physical damage, such as may occur
with ice-fall. For a remote-mounted ODU or MPT-HL, check its antenna feeder.

Path problems on a new link
2.4.3 — New path obstruction

Where all other parameters check as normal, and the path has potential for it to be
obstructed by construction works, view/survey the path for possible new obstructions.
2.4.4 — Interference from other signal sources

Interference usually affects traffic in just one direction. Unlike other path problems, RSL
is not affected. If suspected, check for new link installations at, or in the same geographical
area, as the affected site. Ultimately, a spectrum analyzer may have to be used to confirm
interference, which is not an easy task given the need to connect directly to the antenna port,
after removing the ODU or MPT-HL.
2.5 — Path problems on a new link

For a new link, potential problems can extend to also include:
• Incorrect antenna alignment

• Mismatching antenna polarizations
• Incorrect path calculations
• Reflections
2.5.1 — Incorrect antenna alignment

One or both antennas incorrectly aligned. See the Alcatel-Lucent 9500 MPR Turn-up
Manual, Antenna Polarization Verification Antenna Feedhorn Verification - XPD
Procedure.
2.5.2 — Mismatching antenna polarizations

Given a typical polarization discrimination of 30 dB, for most links it is not possible to
capture a signal to begin the antenna alignment process.

Troubleshooting configuration problems
2.5.3 — Incorrect path calculations

If the RSLs are too low or too high, antenna alignment is correct, and Tx power settings are
correct, check the path calculations used to determine the link performance. A good
calculation match is +/- 2dB. Disagreements in excess of 3 dB should be investigated.
2.5.4 — Reflections
Reflection (path cancellation) problems may not have been picked up at the path planning
stage, particularly if the survey was a simple line-of-sight. If suspected, resurvey the path.
2.6 — Troubleshooting configuration problems

Configuration problems should only occur during the setup of a new link, or
reconfiguration of an existing link. The more common problems may be broadly
categorized as:
• Compatibility Problems
• Incorrect circuit connections
• Incorrect ID naming and commissioning
• Incorrect/incompatible trib settings
2.6.1 — Compatibility problems

The two alarms that may activate are Configuration Not Supported and SW/HW
Incompatible:
Configuration Not Supported: The plug-in installed is not enabled or is incorrect for the
configuration.
2.6.2 — Incorrect circuit connections

No alarms are activated for incorrect circuit connections. An incorrect assignment means
the expected end-to-end circuit connectivity will not happen. Re-check circuit assignments
for all nodes carrying the lost circuit(s).

Troubleshooting Ethernet problems
Take extra care when configuring ring circuits.
Where the problem is not obvious, use the tributary loopback BER test to track a single
circuit through a 9500 MPR network, beginning at the node closest to the node applying the
BER test.
2.6.3 — Incorrect ID naming and commissioning

All traffic-carrying circuits must have a unique flow ID for the cross-connect capability to
operate.
2.6.4 — Incorrect/incompatible trib settings

Trib line interface settings incorrect, or line levels incompatible. While no alarm activates
for an incorrect setting, its effect may result in line levels being too low (LOS alarm), or too
high, resulting in a high BER.
2.7 — Troubleshooting Ethernet problems

This section gives general guidance on troubleshooting problems related to the four
Ethernet ports on the Core-E Card and the eight Ethernet ports on the P8ETH card.
The most common Ethernet problems are network and connectivity related and therefore
always check the following first:
• Verify link partner capability, provisioning, and connection

• Verify radio provisioning matches link partner
• Verify cabling between radio and link partner
The LEDs on the Core-E and P8ETH Card front panel for each Ethernet connector are a
good indicator of correct connectivity and activity on the Ethernet port. See Table 6.9 for
LEDs that are locally at the alarmed site.
In order for the green Link LED to light:
1. Cable must be connected to Ethernet port

2. Ethernet port must be enabled (provisioned Enabled on Core Settings Screen)
3. Speed and mode (on Core Settings Screen) must be provisioned the same as the link
partner.

The yellow LED opposite the green on the connector indicates activity only. The flashing
yellow LED is not an indicator of signal type or quality.
2.7.1 — Troubleshooting TMN problems

This section gives general guidance on troubleshooting TMN problems related to Ethernet
port 4 on the Core-E Card. Ethernet port 4 on the Core-E Card can be used to transport
SNMP IP data. Troubleshoot port 4 connectivity alarms the same as Ethernet ports 1-3. See
Troubleshooting Ethernet problems.
The most common TMN problems are network related and first alert is normally observed
by improper operation at the SNMP master. Always check the following first:
• Verify master is properly registered in NE to receive traps.

• Verify SNMP version matches system requirements
• Verify correct community string and privileges
• Verify proper network routing.
See Table 6.13 for information about TMN network troubleshooting.


3 — Safety awareness
3.1 — Safety EMC-EMF-ESD norms and equipment

labeling
This section describes the equipment labeling and the norms mandatory or suggested that
must be considered to avoid injuries on persons and/or damage to the equipment.
• Safety rules
• Electromagnetic compatibility (EMC norms)
• Equipment protection against electrostatic discharges
• Cautions to avoid equipment damage
3.2 — Safety rules
3.2.1 — General rules

Before performing any installation, turn-on, tests or operation and maintenance operations,
read carefully the related sections of this manual, specifically:
• Hardware Installation
• Commissioning
• Maintenance and Upgrade
3.2.1.1 — Observe safety rules
When equipment is operating, do not access the equipment parts which are protected with
Cover Plate Shields removable with tools.

Labels indicating danger, forbidding, command
If you must access the equipment parts when it is operating, this is allowed exclusively to
service personnel, where for Service Personnel or Technical assistance is meant:
• “Personnel which has adequate Technical Knowledge and experience necessary to be

aware of the danger that he might find in carrying out an operation and of the
necessary measurements to reduce danger to minimum for him and for others”.
• The Service Personnel can only replace the faulty units with spare parts.
• The Service Personnel is not allowed to repair: hence the access to the parts not
specified is not permitted.
• The keys and/or the tools used to open doors, hinged covers to remove parts which
give access to compartments in which are present high dangerous voltages must
belong exclusively to the service personnel.
For the eventual cleaning of the external parts of the equipment, absolutely do not use any
inflammable substance or substances which in some way may alter the markings and
inscriptions.
It is recommended to use a slightly wet cleaning cloth.
The Safety Rules stated in the handbook describe the operations and/or precautions to
observe to safeguard service personnel during the working phases and to guarantee
equipment safety, that is, not exposing persons, animals, things to the risk of being injured/
damaged.
Whenever the safety protection features have been impaired, REMOVE POWER.
To cut off power proceed to switch off the power supply units as well as cut off power
station upstream (rack or station distribution frame). The safety rules described in this
handbook are distinguished by the following symbol and statement:
3.3 — Labels indicating danger, forbidding, command

Follow the instructions printed on the labels affixed to the units and assemblies.
• Dangerous electrical voltages

• Risks of explosions
• Moving mechanical parts
• Equipment connection to earth
• Heat-radiating mechanical parts
• Microwave radiations (EMF norms)
• Laser precautions
Pay attention to the information stated in the following, and proceed as instructed.

Note: The symbols presented in following paragraphs are all the possible symbols that
could be present on Alcatel-Lucent equipment, but are not all necessarily present on the
equipment this manual refers to.
3.3.1 — Dangerous electrical voltages
3.3.1.1 — Labeling:
The following warning label is affixed next to dangerous voltages (>42.4 Vp; >60 VDC).
If it is a Class 1 equipment connected to mains, then the label associated with it will state
that the equipment will have to be grounded before connecting it to the power supply
voltage, for example:

3.3.1.2 — Safety instructions:
Danger: Carefully observe the specific procedures for installation / turn-up and
commissioning / maintenance of equipment parts where D.C. power is present,
described in the relevant installation / turn-up and commissioning / maintenance
documents and the following general rules:
• Personal injury can be caused by -48VDC. Avoid touching powered terminals with any
exposed part of your body.
• Short circuiting, low-voltage, low-impedance, DC circuits can cause severe arcing that
can result in burns and/or eye damage. Remove rings, watches, and other metal jewelry
before working with primary circuits. Exercise caution to avoid shorting power input
terminals.
3.3.2 — Risks of explosions
This risk is present when batteries are used, and it is signaled by the following label:
Therefore, slits or apertures are made to let air circulate freely and allow dangerous gases
to down flow (battery-emitted hydrogen). A 417-IEC-5641 Norm. compliant label is
affixed next to it indicating that the openings must not be covered up.

3.3.3 — Moving mechanical parts
The following warning label is affixed next to fans or other moving mechanical parts:
Before carrying out any maintenance operation see that all the moving mechanical parts
have been stopped.
3.3.4 — Equipment connection to earth
Terminals for equipment connection to earth, to be done according to international safety

standards, are pointed out by the suitable symbol:

The position of earth connection terminals is specified in the Hardware Installation section.
3.3.5 — Heat-radiating mechanical parts
The presence of heat-radiating mechanical parts is indicated by the following warning label
in compliance with IEC 417 Norm, Fig.5041:
Danger: Safety instructions:
Carefully observe the specific procedures for installation / turn-up and commissioning
/ maintenance of equipment parts where heat-radiating mechanical parts are present,
described in the relevant installation / turn-up and commissioning / maintenance
documents and the following general rule:
Personal injury can be caused by heat. Avoid touching powered terminals with any
exposed part of your body.
3.3.6 — Microwave radiations (EMF norms)

Equipment emitting RF power (Reminder from site preparation procedure):
The site must be compliant with ICNIRP guidelines or local regulation if more restrictive.

The following rules should be strictly applied by Customer:
• Non authorized persons should not enter the compliance boundaries, if any, for the
general public.
• Compliance RF boundaries, if any, related to Electro Magnetic Field exposure must
be marked.
• Workers should be allowed to switch-off the power if they have to operate inside
compliance boundaries.
• Assure good cable connection.
• Install the antenna as high as possible from floor or area with public access (if
possible the cylinder delimiting the compliance boundaries, if any, or the cylinder
corresponding to the transmission area directly in front of antenna with the same
diameter as the antenna, more than 2 meters high).
• Install the antenna as far as possible from other existing equipment emitting RF
power.
Always remember that someone standing in front of the 9500 MPR antenna may cause
traffic shutdown.
Place the relevant stickers:
On the site when applicable (when people can cross the compliance boundaries and/or the
transmission area of the antenna, that is, roof top installation)
• Warning label “Do not stand on the antenna axis”
On the mast (front side)
• EMF emission warning sign (Yellow and black) to be placed at bottom of antenna,
visible by someone moving in front of the antenna (roof top installation)
On the antenna (rear side)
• EMF emission warning sign, placed on the antenna.

Figure 3.1 — Compliance boundaries for 9500 MPR transceivers with 1ft (30 cm) antenna:
3.3.7 — Electromagnetic compatibility (EMC norms)

The equipment's EMC norms depend on the type of installation being carried out such as
cable termination or grounding, and on the operating conditions.
Before carrying out any installation, turn-on, tests & operation and maintenance operations,
read carefully the related sections of this manual, in particular:
• Hardware Installation
• Maintenance and Upgrade
The norms set down to guarantee EMC compatibility, are distinguished inside this manual
by the symbol and term:
1. EMC General Norms - Installation

• All connections (towards the external source of the equipment) made with
shielded cables use only cables and connectors suggested in this manual or in
the relevant Plant Documentation, or those specified in the Customer's
“Installation Norms” (or similar documents)
• Shielded cables must be suitably terminated
• Install filters outside the equipment as required
• Ground connect the equipment utilizing a conductor with proper diameter and
impedance
• Mount shields (if utilized), previously positioned during the installation phase,
but not before having cleaned and degrease it.

• Before inserting the shielded unit proceed to clean and degrease all peripheral
surfaces.
• Screw fasten the units to the subrack.
• To correctly install EMC compatible equipment follow the instructions given.
2. EMC General Norms - Turn-on, Tests & Operation
• Preset the electrical units as required to guarantee EMC compatibility
• Check that the equipment is operating with all the shields properly positioned.
• To properly use EMC compatible equipment observe the information given
3. EMC General Norms - Maintenance
• Before inserting the shielded unit, which will replace the faulty or modified
unit, proceed to clean and degrease all peripheral surfaces.
• Clean the dummy covers of the spare units as well.
• Screw fasten the units to the subrack.
3.3.8 — Equipment protection against electrostatic discharges

Before removing the ESD protections from the equipment, observe the precautionary
measures stated. Make sure that the ESD protections have been replaced and after having
terminated the maintenance and monitoring operations.
Most electronic devices are sensitive to electrostatic discharges, to this concern the
following warning labels have been affixed:
Observe the precautionary measures stated when having to touch the electronic parts during
the installation/maintenance phases.
Workers are supplied with anti static protection devices consisting of an elasticized band
worn around the wrist and a coiled cord connected to the elasticized band and to the stud
on the subrack. See Figure 3.2.

3.3.8.1 — Cautions to avoid equipment damage
3.3.8.2 — Anti static protection device kit
Whenever is necessary to handle spare parts and cards out of their own box, this kit, as
shown in Figure 3.2, must be always warn and its termination must be connected to a
grounded structure, to avoid the possible damage of the electronic devices for electrostatic
discharges.
Figure 3.2 — Anti static protection device kit
3.3.8.3 — Screw fixing
In normal operation conditions, all screws must be always tightened to avoid item
detachment and to ensure the equipment EMI-EMC performance.
• The screw tightening torque must be:

• 2.8 kg x cm (0.28 Newton x m) ±10%
• 2.4317 in lb. (0.2026 ft lb.) ±10%
• Exceeding this value may result in screw breaking.
3.3.8.4 — MSS-ODU cable disconnection / connection
To avoid equipment damage, always unplug the card first before disconnecting the MSS-
ODU cable (at MSS or ODU side).
3.3.9 — Fan, equipment rack, and equipment cabinet

precautions
When installing the equipment observe the following:
Danger:
• Keep your fingers away from the rotating fan blades. Pull the fan-tray card by the
thumbscrews only and wait for the fan blades to stop spinning before you attempt to
remove the fan-tray card completely from the chassis.
• The 9500 MPR requires at least two people to support, align, and attach the MSS-8 shelf
or MPT-HL shelf to an equipment rack. To prevent equipment damage or personal injury,
make sure you have enough help.
• The 9500 MPR requires at least three people to lift and carry an equipment rack populated
with 9500 MPR equipment. To prevent equipment damage or personal injury, make sure
you have enough help or the appropriate lifting and transporting equipment.
• The 9500 MPR requires at least two people to align and secure an equipment rack
populated with 9500 MPR equipment. To prevent equipment damage or personal injury,
make sure you have enough help.
• To prevent personal injury and equipment damage due to unbalanced loading of the
equipment rack or cabinet, make sure the equipment rack or cabinet is properly secured
to the floor, ceiling, or other rigid structure before mounting the 9500 MPR in it. For
approved methods of securing the equipment rack, read the equipment-rack installation
instructions or contact the equipment-rack manufacturer.
3.3.10 — Electrical precautions

Take appropriate safety precautions when performing procedures on electrical equipment.
Hazardous electrical potentials are present when system power is on.
Some procedures in this manual require working with small conductive objects, such as
screwdrivers, fuses, washers, screws, and nuts. When working on a chassis at the top of an
equipment rack, a dropped object that falls into a lower chassis can cause physical damage
and electrical short circuits. To prevent this, place a piece of paper or other cover over the
lower chassis to catch fallen objects. Remove the paper or other cover when work is
complete.

Danger:
• Install the 9500 MPR in a restricted-access area only. Entrance to a restricted-access area
is intended for qualified or trained personnel and access to it is controlled by a locked
barrier.
• The chassis does not contain main overcurrent protection devices. The user must provide
circuit breakers or fuses and disconnects between the power source and the 9500 MPR.
Each power feed from a source (-48 V dc and Return) requires a 25-amp dc-rated fast-trip
circuit breaker or fuse and disconnect. Circuit breakers or fuses must meet applicable local
and national electrical safety codes and be approved for the intended application.
• Make sure you connect the node to a -48 V dc source that is electrically isolated from the
ac source and is reliably connected to earth ground.
• For personal safety, make sure you connect and secure the installation site’s frame-
ground (earth ground) wire to the frame-ground terminal on the 9500 MPR before you
connect any other wires to the node.
• A dc-power source provides high energy, which can cause serious injury or equipment
damage. Only Alcatel-Lucent qualified personnel should connect the dc power to the 9500
MPR. To prevent serious injury or equipment damage, make sure the power source cables
are de-energized before you handle or connect them to the node.
3.3.11 — Laser precautions

Verify that laser labels on equipment state that the system conforms to all applicable
standards of 21 CFR 1040.10. If there are no danger labels, contact Alcatel-Lucent.
The invisible infrared radiation emitted by the fiber-optic transmitter can cause eye
damage. Observe local office procedures and the following dangers:

Danger:
• The use of controls and/or adjustments, or the performance of procedures other than
those specified herein may result in hazardous infrared radiation exposure.
• Laser infrared radiation is not in the visible spectrum; therefore, it is not visible to the
naked eye or with laser safety glasses. Although it cannot be seen, laser radiation may be
present.
• Never look directly into an unterminated fiber-optic connector unless it is absolutely known
that no optical power is being emitted by the connector.
• Never look into a broken optical fiber cable unless it is absolutely known that no laser
radiation is present.
• Never look at an optical fiber splice, cable, or connector unless it is absolutely known that
no laser radiation is present in the fiber. Laser radiation can come from a fiber-optic
transmitter, an Optical Time Domain Reflectometer (OTDR), or other optical test
equipment.
• Never look directly into an unterminated optical connector or cable with a magnifier/
microscope unless it is absolutely known that no laser radiation is being emitted from the
connector or cable. A magnifier or microscope greatly increases the laser radiation hazard
to the eyes.
• This system normally operates as a Class I Laser Product (no hazard). However, during
servicing operations, when optical connectors are being connected, disconnected, or
handled without dust covers, it is possible to be exposed to Class IIIb laser radiation,
which can cause eye damage.
• Everyone within a 10-foot radius of an unterminated optical fiber or connector that is
connected to a powered transmitter must wear laser safety goggles or eye shields.
Laser safety goggles or eye shields are not required if the following work rules are strictly
followed:
1. Always remove electrical power from fiber-optic transmitters before disconnecting

fiber-optic connectors in the path between the transmitter and the receiver.
2. Never connect an unterminated optical cable to a fiber-optic transmitter. Always
connect fiber-optic cables to fiber-optic receivers, test sets, or some other termination
first.


4 — Electrostatic-sensitive devices
4.1 — Electrostatic-sensitivity
An Electrostatic-Sensitive Device (ESD) can withstand voltage spikes of only 10 to
100 volts and can be damaged or effectively destroyed by a discharge that might go
unnoticed by a technician. Some devices have built-in protection. However, because this
protection is effective only against the lower levels of electrostatic charges, a false sense of
security often prevails.
Warning: Common plastic, white foam, cellophane, and masking adhesive tapes must not
come in contact with ESDs or their packaging.
Common plastics (synthetic insulating materials), clothing, and paper or cardboard are the
most common sources of static charges.
Observe special precautions when the ESD sign is displayed. See Figure 4.1.
Figure 4.1 — Electrostatic-sensitive sign
No3013
The following items are examples of ESDs:
• MOS (Metal Oxide Semiconductor) capacitors, transistors, Integrated Circuits (ICs)

• CMOS (Complementary Metal Oxide Semiconductor) transistors, ICs

Handling circuit packs
• JFET (Junction Field Effect Transistors)

• IGFET (Insulated Gate Field Effect Transistors)
4.2 — Handling circuit packs

Although the risk of damage to an ESD is reduced considerably after it is assembled into a
circuit designed to protect sensitive components, take the following precautions to reduce
static charges to harmless levels:
• Handle all circuit packs as ESDs unless they are known not to contain
electrostatic-sensitive parts.
Warning: Heel straps are effective only while standing on conductive or
electrostatic-dissipative surfaces.
• Wear ground straps, wrist (PN 1AD012470001) before and while touching or
handling circuit packs containing ESDs.
• Cover surfaces with resistance to ground in excess of 100 megohms, such as ordinary
tile, with properly grounded static dissipative runners.
• Workbenches must be earth-grounded, and work surfaces must be covered with an
antistatic or static dissipative material bonded to the bench (bolt). A field service kit
(PN 1AD068980001) or equivalent can be used if an adequate workbench is not
available.
• ESDs are delivered with protective packing (containers or conductive foam). The
devices should remain in their original containers until needed. Store (even
temporarily), pack, and ship circuit packs in antistatic bags or containers.
• Containers with ESDs must contact the antistatic work surface, and the wrist strap
must be connected before parts are removed from packaging. Devices must be
handled by their bodies.
• Do not handle printed circuit board or components unnecessarily. Use plastic handle.
• Do not use synthetic bristled brushes or acid brushes to clean circuit packs.
• Handle failed circuit packs with same precautions as good circuit packs.
ESDs are protected when properly packaged in conductive or antistatic packaging.

Acceptable packaging is marked as either conductive or antistatic.

5 — Product support information for the

ANSI market
5.1 — Telephone and email support
5.1.1 — Customer service telephone and email support

Visit the customer support section on Alcatel-Lucent’s website to find telephone and email
contact information for your country:
http://support.alcatel-lucent.com/
After-hours emergency telephone support is available. An emergency is defined as an

out-of-service, traffic-affecting problem or a nonoperating alarm system on traffic-bearing
systems.
5.2 — Product documentation and training
5.2.1 — Product documentation

Product documentation is available through Alcatel-Lucent’s OnLine Customer Support
(OLCS) web site at:
www.documentation.alcatel-lucent.com
Product documentation updates appear on Alcatel-Lucent’s OnLine Customer Support web

site before they are available in any other format.

Product documentation and training
At Alcatel-Lucent’s OnLine Customer Support web site, follow the on-screen instructions
to register for access and obtain a log in ID. In addition to accessing product documentation,
the Alcatel-Lucent’s OnLine Customer Support web site allows the user to view the
following:
• Application notes
• Configuration notes
• Data collections
• Frequently Asked Questions (FAQs)
• General information books
• General Release Documents (GRDs)
• Installation documents
• Methods of Procedure (MOPs)
• Product Change Notifications (PCNs)
• Product Information Bulletins (PIBs)
• Product manual updates
• Software patch and software load documents
• Software Update Documents (SUDs)
• Technical bulletins
• Training documents
• Urgent Product Warnings (UPWs)
5.2.2 — Training
Equipment training is available to all customers. Crafts and maintenance personnel who are
trained by Alcatel-Lucent's Training department can expect more effective assistance if
they need technical assistance. Regularly scheduled courses are available at the training
facilities in Plano, Texas. If a customer cannot attend a standard course, the Training
department can arrange a course for a specific requirement and conduct it at the customer's
facility. For further information, call customer service telephone support and ask for a
training coordinator or write to one of the following addresses:
IN USA: IN CANADA:
Alcatel-Lucent USA Alcatel-Lucent Canada
601 Data Dr. Network Services Division
Plano, Texas 75075-7839 P.O. Box 13600
ATTN: Training M/S 1206-553 Ottawa, Ontario K2K 2E6

Technical support center
The annual Product Training Catalog can be ordered by calling the training coordinator, or
it can be viewed on-line at:
http://www1.Alcatel-Lucent.com/us/product_training/catalog
5.3 — Technical support center

The Technical Support Center (TSC) staff is always ready to provide high-quality technical
assistance. Customers can expect effective telephone assistance when their crafts and
maintenance personnel have been trained by Alcatel-Lucent's Training department and are
equipped with adequate test equipment, spares, and documentation at the site.
5.3.1 — After-hours emergency telephone support

Emergency support is available after-hours for emergencies.
An emergency is defined as an out-of-service, traffic-affecting problem or a nonoperating

alarm system on traffic-bearing systems.
Nonemergency is defined as installation turn-ups, application questions, traffic cutover,

routine maintenance, or other non-service-affecting maintenance. All
non-service-affecting, after-hours telephone services are billable to the customer.
Please provide the operator with the following information:
• Company name
• Caller name
• A telephone number where caller can be reached
• A brief description of the problem, including the product involved
5.3.2 — After-hours nonemergency telephone support

After-hours telephone support to address new installations, system expansions, system
operations, system application, or other non-service-affecting issues is available by
contacting Alcatel-Lucent.

Repair and return services
5.3.3 — On-site technical support

On-site technical support is available when an issue cannot be resolved remotely. This
determination is usually made by Alcatel-Lucent TSC during the problem investigation
process. These services may or may not be billable to a customer. This depends on several
factors such as what type of Service Level Agreement a customer has with Alcatel-Lucent
and the age of the product.
5.4 — Repair and return services

As part of a comprehensive technical support program, Alcatel-Lucent provides factory
repair services for equipment. This service is available both during and after the warranty
period through Alcatel-Lucent's Return and Repair department.
5.5 — Spare parts and replacement cards

For spare parts, spare cards, card exchange, and in-warranty replacement on a routine or
emergency basis, call customer service telephone support.
Provide the following information:
• Customer Contact Name

• Customer Company Name
• Customer telephone number
• Customer E-mail Address
• A brief description of the problem, including product line, part number, and quantity
of parts needed
For emergency assistance after normal business hours, call customer service telephone
support, ask the operator for Emergency Parts Assistance, and provide the operator with the
required information. The operator will contact an appropriate individual to respond.
5.6 — Return for credit or warranty exchange

procedure
Returned equipment must have a Parts Request (PR) number. Obtain an PR number by
calling Alcatel-Lucent.

Service center
No equipment should be returned without an PR number. The following

information is required:
• Description and quantity of equipment to be returned

• Reason for return
• Order number the equipment was purchased against and approximate date of
purchase
5.7 — Service center

The Service Center tests, repairs, and modifies all cards (both in and out of warranty).
Cards received for repair or modification are returned promptly.
5.7.1 — Return for repair procedure

Refer to Return for credit or warranty exchange procedure for information on obtaining an
PR number. Notification to the Service Center and issuance of an PR number by
Alcatel-Lucent personnel must be made prior to shipment of parts. The following
information must be furnished with the request for return authorization:
• Purchase order number or requisition number

• Description and quantity of equipment to be returned
• Reason for return:
• Modification required
• Defective equipment to be repaired
• Warranty status (in or out of warranty) and warranty date stamped on unit
• Specific nature of problem
• Name and telephone number of person who identified problem
• Special instruction/information
5.7.2 — Shipping instructions for repair, credit, or

warranty exchange
Return equipment or parts prepaid to the address provided below. The PR number must be
prominently marked on the shipping label, the packing list, and any correspondence
regarding the order.

Installation and maintenance services
• Include company name, address, and name of person to contact in case of a question.
• Include specific reason for return. (This aids prompt processing.)
• Include the same requisition number or purchase order number that was furnished
with request for return authorization.
• Include type number and part number of unit.
• State whether equipment is in or out of warranty.
• Furnish shipping address for return of unit, if applicable, or other pertinent details.
• Mail purchase order, if applicable, to address shown under Return for Repair
Procedure, Attention: Service Center.
Alcatel Lucent Return
Equipment Address
Alcatel Lucent c/o UPS-SCS
Attn: Repair FE
2240 Outer Loop
Bldg 5 Door 505
Louisville, Ky 40219
5.8 — Installation and maintenance services
5.8.1 — Engineering and installation service

Whether installation for specific equipment or a full turnkey network facility is needed,
Installation Service can help. Alcatel-Lucent has experience in central office, outside plant,
and customer premises applications, and specializes in flexible scheduling and high-quality
service. Qualified staff are in place nationwide, so an installation can be started and
completed promptly.
5.8.2 — Contract maintenance service

Field service from Alcatel-Lucent US and Canada offices are available. Alcatel-Lucent
field service is well-suited for private networks of any size.
Factory-trained service technicians are qualified on similar systems before they are allowed
to maintain customer equipment. They have direct access to additional technical support
around the clock and to all necessary tools and test equipment.

6 — Alarm and abnormal condition

clearing procedures
The MOD300 card and ODU300 radio are supported but no longer documented. See
documentation from R6.0.0 or earlier for ODU300/MOD300 alarm and abnormal condition
clearing information.
See Table 6.3 to identify alarms reported by the Alarm Manager and the corresponding
procedure, which describes how to clear the alarm.
See Table 6.4 to identify Abnormal Condition types and the corresponding procedure,
which describes how to clear the Abnormal Condition type. The EQUIPMENT column list
the entities to which an Abnormal Condition type can apply.
See Table 6.5 to identify Core-E card LED alarm indications and the corresponding
procedure, which describes how to clear the condition type.
See Table 6.6 to identify CorEvo card LED alarm indications and the corresponding
See Table 6.7 to identify MSS-1 shelf CORE LED alarm indications and the corresponding
See Table 6.8 to identify Transport card status LED alarm indications and the
corresponding procedure, which describes how to clear the condition type.
See Table 6.9 to identify Ethernet LED alarm indications and the corresponding procedure,
which describes how to clear the condition type.
See Table 6.10 to identify MPT-HL Transceiver LED alarm indications and the
See Table 6.11 to identify MPT-HLC Transceiver LED alarm indications and the
See Table 6.12 to identify MPT-HLC Transceiver LED alarm indications and the
See Table 6.13 to identify TMN Network Trouble conditions and troubleshooting
techniques, which describes how to clear the condition type.

Alarm manager / Craft Terminal
This manual supports alarm naming conventions for the Alarm Monitor. Alarms may
display differently, or not be displayed, in other interfaces.
To retrieve alarms using the Alarm Monitor, execute the following sequence from the main
menu bar:
Diagnosis>Alarms>NE Alarms
To retrieve Abnormal Conditions using the Craft Terminal, execute the following sequence
from the main menu bar:
Diagnosis>Abnormal Condition List
6.1 — Alarm manager / Craft Terminal
6.1.1 — Equipment / facility column

The EQUIPMENT/FACILITY column in Table 6.3 lists the entities to which an alarm type
can apply. Depending on the entities affected, some alarm types have more than one
corresponding procedure.
In the EQUIPMENT/FACILITY column, equipment entities are listed using the following
definitions:
• AUX: Auxiliary card

• Core-E: Core Switching Module card
• CorEvo: Core Switching Module card, second generation
• EASv2: 8-Port Ethernet Access Switch, second generation
• FAN: MSS-4/8 Fan card
• MPTACC: MPT Access card
• MSS: MSS-O/1/4/8 shelf
• MPT-HC: MPT-HC/MPT-XP/9558HC (MPT ODU) outdoor unit
• MPT-HL: MPT-HL Transceiver card
• MPT-HLC: MPT-HL Transceiver card, second generation
• MPT-HLS: MPT-HLS Transceiver card
• SFP: Small Form Factor Pluggable equipped on listed equipment type
• P2E3DS3: 2-Port DS3 card
• P8ETH: 8-Port Ethernet Access Switch
• P32E1DS1: 32-Port DS1 card

• SDHACC: 2-Port OC-3 card
In the EQUIPMENT/FACILITY column, facility entities are listed using the following
definitions:
• Core-E: Ethernet facility supported by the Core-E card

• CorEvo: Ethernet facility supported by the CorEvo card
• DS3: DS3 facility supported by P2E3DS3 card
• DS1: DS1 facility supported by P32E1DS1 card
• EASv2: Ethernet facility supported by the EASv2 card
• MPT-HC: RF facility supported by MPT-HC/MPT-XP/9558HC (MPT ODU)
outdoor unit
• MPT-HQAM: RF facility supported by MPT-HC-HQAM/MPT-XP-HQAM
(MPT ODU) outdoor unit
• MPT-HL: RF facility supported by MPT-HL Transceiver card
• MPT-HLC: RF facility supported by MPT-HLC Transceiver card
• MPT-HLS: RF facility supported by MPT-HLS Transceiver card
• MSS/CORE: Ethernet facility supported by the MSS-1
• MSS/DS1:DS1 facility supported by the MSS-1 unit
• OC-3: OC-3 facility supported by SDHACC card
• P8ETH: Ethernet facility supported by the P8ETH card
6.1.2 — Friendly name / entity column

The FRIENDLY NAME/ENTITY column identifies the location of the alarming entity.
Equipment friendly names are constructed using the following structure:
r<rack number>s<subrack number>b<board number>d<daughter>
The syntax for equipment Friendly Names / Entities is described in Table 6.1.
Table 6.1 — Friendly Name/Entity Syntax

Location Syntax Values Description
Rack r r01 Rack number

Table 6.1 — Friendly Name/Entity Syntax

Subrack s s1 Subrack number for MSS-O, MSS-1, MSS-4, and MSS-8
shelves
s101 Subrack number for MPT-HLS units
s102
s[3-8][1-4] Subrack number for (MPT ODU) connected to MPTACC card
(MPTACC slot number and Ethernet port number associated
with MPT ODU)
s[3-8][5-8] Subrack number for (MPT ODU) connected to P8ETH/EASv2
card (P8ETHH/EASv2 slot number and Ethernet port
number associated with MPT ODU)
s1[1-6] Subrack number for MPT ODU connected to Core-E card or
MSS-1 (Core-E slot number and Ethernet port number
associated with MPT ODU)
s1[1-3] Subrack number for MPT ODU connected to MSS-O (Core-E
slot number and Ethernet port number associated with
MPT ODU)
s[3-8][5-8] Subrack number for MPT-HL, MPT-HLC transceiver
connected to EASv2 or P8ETH card (EASv2/P8ETH slot
number and Ethernet port number associated with
MPT-HL/MPT-HLC Transceiver)
s1[1-6] Subrack number for MPT-HL, MPT-HLC Transceiver
connected to Core-E card or MSS-1 (Core-E slot number and
Ethernet port number associated with MPT-HL Transceiver)
Board b board#[1-10] Board/slot number of equipment in alarm
b#[1-9]
Slot#[1-9]
Daughter d daughter#[05-06] Daughter SFP port number of equipment in alarm
associated with Core-E card or MSS-1
daughter#04 Daughter SFP port number of equipment in alarm
associated with MSS-O
daughter#[03-04] Daughter SFP port number of equipment in alarm
associated with MPTACC card
associated with EASv2 or P8ETH card
associated with SDHACC card
Radio facility friendly names are constructed using the following structure:
f<facility name>rd<radio direction>b<board number>p<port number>c<channel

number>
DS1, DS3, and Ethernet facility friendly names are constructed using the following
structure:

f<facility name>b<board number>p<port number>
The syntax for facility Friendly Names / Entities is described in Table 6.2.
Table 6.2 — Friendly name syntax definitions
Facility f DS-1-in, out DS1 facility and direction

Name
DS-3-in, out DS3 facility and direction
E1-in, out DS1 facility and direction
EleSdh-in STM-1/OC-3 facility and direction (supported by electrical

SFP)
OptSdh-in STM-1/OC-3 facility and direction (supported by optical SFP)
MAU Ethernet signal
Radio Radio facility

Radio rd Dir#[3-8].[1-4] Radio direction of MPT ODU radio channel in alarm connected
Direction to MPTACC card (MPTACC slot number and port number)
Dir#1.[1-6] Radio direction of MPT ODU radio channel in alarm connected

to Core-E card or MSS-1 (Core-E slot number and port number)
Dir#1.[1-3] Radio direction of MPT ODU radio channel in alarm connected

to MSS-O-E card (Core-E slot number and port number)
Dir#[3-8].[5-8] Radio direction of MPT-HL, MPT-HLC, and MPT-HLS radio

channel in alarm connected to EAS card
Dir#1.[5-6] Radio direction of MPT-HL, MPT-HLC, and MPT-HLS radio

channel in alarm connected to Core card or MSS-1 (Core slot
number and port number)
Board b board#[1-9] board/slot number of MSS-8 (1-9), MSS-4 (1-5) equipment in

alarm
b#[1-9]
Slot#[1-9]
MSS/CORE board/slot number of MSS-1 equipment in alarm
MSS/DS1

Table 6.2 — Friendly name syntax definitions (Continued)
Port p Port#[1-16] E1/DS1 port number of facility in alarm on MSS-1

Number
Port#[1-32] E1/DS1 port number of facility in alarm on P32E1DS1
Port#[1-2] DS3 port number of facility in alarm
Port#[1-2] STM-1/OC-3 port number of facility in alarm
Port#[1-6] Ethernet port number of facility in alarm associated with

Core-E card and MSS-1
Port#[1-4] Ethernet port number of facility in alarm associated with MSS-

O
Port#[1-8] Ethernet port number of facility in alarm associated with
EASv2, P8ETH, and CorEvo
Channel c Ch#1 Main radio channel in alarm

Number
Ch#0 Spare radio channel in alarm
ERPS ERP ERP[1-2]#[1-2] Ethernet Ring Protection Switch
The following are examples to illustrate how to interpret the probable cause and friendly
name combinations:
Example: Probable Cause: Replaceable Unit Missing
• Friendly Name: r01s1/board#8

• Translation: Missing card at r01 (rack 01) s1 (subrack 1 (MSS-8 Shelf)) /
board#8 [missing card provisioned for slot #8]
• Friendly Name: r01s1b3/daughter#05
• Translation: Missing SFP at r01 (rack 01) s1 (subrack 1 (MSS-8 Shelf)) b3 (card
in slot #3 (P8ETH)) /daughter#05 [missing SFP provisioned in slot #3
(P8ETH), SFP port #5]
Example: Probable Cause: Replaceable Unit Type Mismatch
• Friendly Name: r01s1/board#7

• Translation: Card in r01 (rack 01) s1 (subrack 1 (MSS-8 Shelf)) /board#7 [card
installed in slot #7 does not match card configured in Core-E memory]
• Friendly Name: r01subrack#37
• Translation: Card in r01 (rack 01) subrack 37 [MPT-HL Transceiver 3.7,
associated with P8ETH card in slot #3, SFP port #7, does not match MPT-HL
Transceiver configured in Core-E memory]

Example: Probable Cause: Loss Of Signal
• Friendly Name: DS1-in/slot#5/Port#22

• Translation: DS1-input, slot #5, Port #22 [Loss Of incoming DS1 Signal, on
P32E1DS1 card in slot #5, port #22]
• Friendly Name: MAU/Slot#4/Port#7
• Translation: Ethernet signal, slot #4, Port #7 [Loss Of Ethernet Signal on
P8ETH card in slot #4, SFP port #7]
• Friendly Name: MAU/Port#2
• Translation: Ethernet signal, Port #2 [Loss Of Ethernet Signal on the active
Core-E card, port #2]
Example: Probable Cause: Loss Of Frame
• Friendly Name: DS3-in/slot#6/Port#2

• Translation: DS3-input, slot #6, Port #2 [Loss Of DS3 Frame on P2E3DS3 card
in slot #6, port #2]
• Friendly Name: Radio/Dir#3.6/Slot#3/Port#6/Ch#1
• Translation: Radio signal, Direction 3.6, associated with card in slot #3, SFP
port #6, Channel #0 [Loss of Frame on MPT-HL Transceiver 3.6 associated
with P8ETH card in slot #3, SFP port #6, Channel #0 (main)]
• Friendly Name: Radio/Dir#6/Ch#1
• Translation: Radio signal, Direction 6, Channel #0 [Loss of Frame on MPT-HC
#6 channel #0 (spare) associated with card in slot #6]
Table 6.3 describes the alarms that are reported by the Alarm Manager and the
corresponding procedure to clear the alarm.

Table 6.3 — Alarm monitor alarm types

Probable cause Friendly name/entity Facility/ Description See
equipment
1588 TC Fails
Radio/Dir#1.[1]/ MPT ODU Reported when, due to Synchronization
Slot#1/Port#[1-6]/Ch#[1] connected to radio impairments, TC alarms (Core-E,
Core-E time stamping can not be CorEvo, MPT-HC,
Radio/Dir#1.[1-4,7-8]/ MPT ODU guaranteed due to MPT-HC-HQAM,
Slot#1/Port#[1-4,7-8]/ connected to alignment of the local MPT-HL,
Ch#1 CorEvo and remote counters. MPT-HLC, MPT-
Radio/Dir#1.[1-6]/MSS/ MPT ODU HLS, MPT-XP,
CORE/Port#[1-6]/Ch#1 connected to MPT-XP-HQAM,
MSS-1 P32E1DS1,
SDHACC)
Radio/Dir#1.[1-3]/ MPT ODU
Slot#1/Port#[1-3]/Ch#1 connected to
MSS-O
Radio/Dir#[3-8].[1-4]/ MPT ODU
Slot#[3-8]/Port#[1-4]/Ch#1 connected to
MPTACC
P8ETH
RadioTxPower/Dir#[3-8].1- MPT ODU
8]/Slot#[3-8]/Port#[1-8]/ connected to
Ch#1 EASv2
AIS
AU4/Slot#[3-8]/Port#1 Channelized High Order Path alarm Facility alarms
E1 indication signal on a
channelized E1 unit.
TU12#[1-3]-[1-7]-[1-3]/ Channelized Low Order Path alarm
Slot#[3-8]/Port#1 E1 indication signal on a
channelized E1 unit.
E1-in/#[1-3]-[1-7]-[1-3]/ Channelized AIS detected incoming to Facility alarms
Slot#[3-8]/Port1 E1 the SDH-Chan card from
the demarcation panel
for the E-1 facility.
E1-out/#[1-3]-[1-7]-[1-3]/ Channelized AIS detected from the Facility alarms
Slot#[3-8]/Port1 E1 Core-E/CorEvo switch
matrix for the E-1
facility, indicating an
upstream failure.

Table 6.3 — Alarm monitor alarm types (Continued)

equipment
AIS (continued) DS1-in/MSS/DS1/Port#[1- DS1 on MSS-1 AIS detected incoming to Facility alarms
16] shelf the PDH card from the
DS1-in/Slot#[3-8]/Port#[1- DS1 on demarcation panel for
32] P32E1DS1 the DS1 or DS3 facility.
DS3-in/Slot#[3-8]/Port#[1- DS3
2]
E1-in/MSS/E1/Port#[1-16] E1 on MSS-1
shelf
E1-in/Slot#[3-8]/Port#[1- E1 on
32] P32E1DS1
DS1-out/MSS/DS1/Port# DS1 on MSS-1 AIS detected from the Facility alarms
[1-16] shelf Core-E switch matrix for
the DS1 or DS3 facility,
DS1-out/Slot#[3-8]/Port# DS1 on
indicating an upstream
[1-32] P32E1DS1
failure.
DS3-out/Slot#[3-8]/ DS3
Port#[1-2]
E1-out/Slot#[3-8]/Port#[1- E1 on
32] (P32E1DS1)
E1-out/MSS/E1/Port#[1- E1 MSS-1
16]
EleSdh-in/slot#[3-8]/ STM-1/OC-3 AIS detected incoming to Facility alarms
Port[1-2] the SDHACC card from
OptSdh-in/slot#[3-8]/ the demarcation panel
Port[1-2] for the STM-1/OC-3
facility.
EleSdh-out/slot#[3-8]/ STM-1/OC-3 AIS detected from the Facility alarms
Port[1-2] Core-E/CorEvo switch
matrix for the STM-1/
OptSdh-out/slot#[3-8]/
OC-3 facility, indicating
Port[1-2] an upstream failure.
MS/slot#[3-8]/Port1 STM-1


equipment
ATPC High Power Timeout
RadioTxPower/Dir#1.[1- MPT ODU Reported for a ATPC High ATPC loop
6]/Slot#1/Port#[1-6]/ connected to Power Time-out. When condition
Ch#[0-1] Core-E ATPC is enabled, the (MPT-HC, MPT-
RadioTxPower/Dir#1.[1- MPT ODU local transmitter was HC-HQAM,
4,7-8]/Slot#1/Port#[1-4,7- connected to operating continuously at MPT-HL,
8]/Ch#[0-1] CorEvo full power for 5 minutes, MPT-HLC, MPT-
RadioTxPower/Dir#1.[1- MPT ODU and the transmitter was HLS, MPT-XP,
6]/MSS/CORE/Port#[1-6]/ connected to reduced to its minimum MPT-XP-HQAM)
Ch#[0-1] MSS-1 power setting and this
condition notification
RadioTxPower/Dir#1.[1- MPT ODU
was generated. This
3]/Slot#1/Port#[1-3]/Ch#1 connected to
condition will remain
MSS-O shelf
active until a message is
RadioTxPower/Dir#[3- MPT ODU received that the active
8].[1-4]/Slot#[3-8]/ connected to receiver at the other end
Port#[1-4]/Ch#[0-1] MPTACC of the link is no longer
RadioTxPower/Dir#[3- MPT ODU requesting additional
8].[5-8]/Slot#[3-8]/ connected to transmitter power.
Port#[5-8]/Ch#1 P8ETH
RadioTxPower/Dir#[3-8].1- MPT ODU
4]/Slot#[3-8]/Port#[1-4]/ connected to
Ch#[1] EASv2
RadioTxPower/Dir#[3- MPT ODU
8].[5-8]/Slot#[3-8]/ connected to
Port#[5-8]/Ch#[0-1] EASv2
RadioTxPower/Dir#1.[5- MPT-HL
Core-E
CorEvo
6]/MSS/CORE/Port#[5-6]/ connected to
Ch#1 MSS-1
RadioTxPower/Dir#[3- MPT-HL
8].[5-8]/Slot#[3-8]/ connected to
Port#[5-8]/Ch#[0-1] EASv2, P8ETH
RadioTxPower/Dir#1.[5- MPT-HLC
6]/Slot#1/Port#[5-6]/ connected to
Ch#[0-1] Core-E
RadioTxPower/Dir#1.[7- MPT-HLC
8]/Slot#1/Port#[7-8]/ connected to
Ch#[0-1] CorEvo


equipment
ATPC High RadioTxPower/Dir#1.[5- MPT-HLC Reported for a ATPC High ATPC loop
Power Timeout 6]/MSS/CORE/Port#[5-6]/ connected to Power Time-out. When condition
(continued) Ch#[0-1] MSS-1 ATPC is enabled, the (MPT-HC, MPT-
RadioTxPower/Dir#[3- MPT-HLC local transmitter was HC-HQAM,
8].[5-8]/Slot#[3-8]/ connected to operating continuously at MPT-HL,
Port#[5-8]/Ch#[0-1] P8ETH, EASv2 full power for 5 minutes, MPT-HLC, MPT-
RadioTxPower/Dir#[3- MPT-HLS and the transmitter was HLS, MPT-XP,
8].[5-8]/Slot#[3-8]/ connected to reduced to its minimum MPT-XP-HQAM)
Port#[5-8]/Ch#[0-1] EASv2 power setting and this
condition notification
was generated. This
condition will remain
active until a message is
received that the active
receiver at the other end
of the link is no longer
requesting additional
transmitter power.
Bandwidth Degrade for Protection Switch
ERP#[1-2]#[1-2] Core-E, An ERPS Instance has Ethernet alarms
CorEvo entered a Protection (Core-E, CorEvo,
state. EASv2, MPTACC,
P8ETH, MSS-O
Shelf, MSS-1
Shelf)


equipment
Bandwidth Over Flow
Radio/Dir#1.[1-6]/ MPT ODU While the MPT ODU/ Radio alarms
Slot#1/Port#[1-6]/Ch#[0-1] connected to MPT-HL was not (MPT-HC, MPT-
Core-E communicating with the HC-HQAM,
Radio/Dir#1.[1-4,7-8]/ MPT ODU Core-E, EASv2, P8ETH, or MPT-HL,
connected to MSS-1, TDM/SDH MPT-HLC,
Slot#1/Port#[1-4,7-8]/
CorEvo cross-connections were MPT-HLS,
Ch#[0-1]
provisioned with a total MPT-XP,
Radio/Dir#1.[1-6]/MSS/ MPT ODU
bandwidth which exceeds MPT-XP-HQAM)
CORE/Port#[1-6]/Ch#[0-1] connected to the net bandwidth
MSS-1 capacity of the radio
Radio/Dir#1.[1-3]/ MPT ODU profile.
MSS-O shelf
Slot#[3-8]/Port#[1-4]/ connected to
Ch#[0-1] MPTACC
P8ETH
Radio/Dir#[3-8].1-4]/ MPT ODU
Ch#[1] EASv2
Ch#[0-1] EASv2
Radio/Dir#1.[5-6]/ MPT-HL
Core-E
CorEvo
Radio/Dir#1.[5-6]/MSS/ MPT-HL
CORE/Port#[5-6]/Ch#1 connected to
MSS-1
Radio/Dir#[3-8].[5-8]/ MPT-HL
Ch#[0-1] EASv2, P8ETH


equipment
Bandwidth Over Radio/Dir#[3-8].[5-8]/ MPT-HLC or While the MPT ODU/ Radio alarms
Flow Slot#[3-8]/Port#[5-8]/ MPT-HLS MPT-HL was not (MPT-HC, MPT-
(continued) Ch#[0-1] connected to communicating with the HC-HQAM,
EASv2, P8ETH Core-E, EASv2, P8ETH, or MPT-HL,
Radio/Dir#1.[5-6]/ MPT-HLC or MSS-1, TDM/SDH MPT-HLC,
cross-connections were MPT-HLS,
Slot#1/Port#[5-6]/Ch#[0-1] MPT-HLS
connected to provisioned with a total MPT-XP,
Core-E bandwidth which exceeds MPT-XP-HQAM)
Radio/Dir#1.[7-8]/ MPT-HLC or the net bandwidth
capacity of the radio
connected to profile.
CorEvo
Radio/Dir#1.[5-6]/MSS/ MPT-HLC or
CORE/Port#[5-6]/Ch#[0-1] MPT-HLS
connected to
MSS-1
Battery Failure 1
r01/subrack#1 MSS-1/8 An A battery feed failed Power alarms
r01/subrack#[101-102] MPT-HLS or is missing.
r01/s[101-102]/[1-10] MPT-HLS
CLA
Radio/Dir#1.[1-6]/ MPT ODU The standby transmitter Radio alarms
Slot#1/Port#[1-6]/Ch#[0-1] connected to has/had a silent failure (MPT-HC, MPT-
Core-E which caused the far end HC-HQAM,
Radio/Dir#1.[1-4,7-8]/ MPT ODU to request a HSB switch. MPT-HL,
Slot#1/Port#[1-4,7-8]/ connected to MPT-HLC,
Ch#[0-1] CorEvo MPT-HLS,
MPT-XP,
MPT-XP-HQAM)
CORE/Port#[1-6]/Ch#[0-1] connected to
MSS-1
MSS-O shelf
Ch#[0-1] MPTACC
Ch#[0-1] EASv2


equipment
CLA (continued) Radio/Dir#[3-8].[5-8]/ MPT-HL The standby transmitter Radio alarms
Slot#[3-8]/Port#[5-8]/ connected to has/had a silent failure (MPT-HC, MPT-
Ch#[0-1] EASv2, P8ETH which caused the far end HC-HQAM,
to request a HSB switch. MPT-HL,
Radio/Dir#1.[5-6]/ MPT-HLC
MPT-HLC,
Slot#1/Port#[5-6]/Ch#[0-1] connected to MPT-HLS,
Core-E
MPT-XP,
Radio/Dir#1.[7-8]/ MPT-HLC MPT-XP-HQAM)
Slot#1/Port#[7-8]/Ch#[0-1] connected to
CorEvo
Radio/Dir#1.[5-6]/MSS/ MPT-HLC
MSS-1
Radio/Dir#[3-8].[5-8]/ MPT-HLC
Clock Failure
Radio/Dir#1.[1-6]/ MPT ODU The MPT ODU/MPT-HL is Clock failure
Slot#1/Port#[1-6]/Ch#[0-1] connected to not able to lock the air Tx (MPT-HC, MPT-
Core-E symbol rate to the NE HC-HQAM,
Radio/Dir#1.[1-4,7-8]/ MPT ODU clock. MPT-HL,
Slot#1/Port#[1-4,7-8]/ connected to MPT-HLC, MPT-
Ch#[0-1] CorEvo HLS, MPT-XP,
MPT-XP-HQAM)
MSS-1
MSS-O
Ch#[0-1] MPTACC
P8ETH


equipment
Clock Failure Radio/Dir#[3-8].1-4]/ MPT ODU The MPT ODU/MPT-HL is Clock failure
(continued) Slot#[3-8]/Port#[1-4]/ connected to not able to lock the air Tx (MPT-HC, MPT-
Ch#[1] EASv2 symbol rate to the NE HC-HQAM,
clock. MPT-HL,
MPT-HLC, MPT-
HLS, MPT-XP,
Ch#[0-1] EASv2
MPT-XP-HQAM)
Core-E
CorEvo
MSS-1
Radio/Dir#1.[5-6]/ MPT-HLC,
connected to
Core-E
connected to
CorEvo
Radio/Dir#1.[5-6]/MSS/ MPT-HLC,
connected to
MSS-1
Ch#[0-1] P8ETH
Radio/Dir#[3-8].[5-8]/ MPT-HLC,
Slot#[3-8]/Port#[5-8]/ MPT-HLS
Ch#[0-1] connected to
EASv2


equipment
Combiner Loss of Alignment
r01/subrack#1[5-6] MPT-HLC Non-alignment status Combiner loss of
connected to detected between main alignment
Core-E, MSS-1 and diversity flows in (MPT-HLC or
r01/subrack#1[7-8] MPT-HLC configurations with MPT-HLS)
connected to combiner
CorEvo
r01/subrack#[3-8][5-8] MPT-HLC
connected to
EASv2
r01/s[101-102]board#[1- MPT-HLS
10] connected to
EASv2
Critical Link Event
ETHLinkOAM/Slot#1/ Ethernet port The Ethernet port’s link Critical Link
Ports[1-6] on Core-E partner has declared a Event (Core-E,
ETHLinkOAM/Slot#1/ Ethernet port link fault condition. EASv2, P8ETH)
Ports[1-8] on CorEvo
ETHLinkOAM/MSS/CORE/ Ethernet port
Ports[1-6] on MSS-1
ETHLinkOAM/Slot#1/ Ethernet port
Ports[1-4] on MSS-O
ETHLinkOAM/Slot#[3-8]/ Ethernet port
Ports[1-8] on EASv2,
P8ETH
Degrade
Sync-in/Port#1 Core-E Frequency of the source Synchronization
Sync-in/Port#[7-8] CorEvo sync signal is degraded. alarms (Core-E,
SFP Port Managed only if the CorEvo, MPT-HC,
Sync-in/Port#[5-6] MSS-1 sync interface has been MPT-HC-HQAM,
SFP Port configured as a primary MPT-HL,
or secondary MPT-HLC, MPT-
SyncSource/ETH/slot#1/ Core-E User
synchronization source. HLS, MPT-XP,
Port#[1-6] Ethernet Port
MPT-XP-HQAM,
SyncSource/ETH/slot#1/ Core-E User P32E1DS1,
Port#[1-6] Ethernet Port SDHACC)
SyncSource/ETH/slot#1/ MSS-O User
Port#[1-4] Ethernet Port
SyncSource/ETH/MSS/ MSS-1 User
CORE/Port#[1-6] Ethernet Port


equipment
Degrade SyncSource/ETH/ EASv2 User Frequency of the source Synchronization
(continued) slot#[3-8]/Port#[1-8] Ethernet Port signal is degraded. alarms (Core-E,
Managed only if the CorEvo, MPT-HC,
Radio/Dir#1.[1-6]/Slot#1/ MPT ODU
interface has been MPT-HC-HQAM,
Port#[1-6]/Ch#1 connected to
configured as a primary MPT-HL,
Core-E
or secondary MPT-HLC, MPT-
Radio/Dir#1.[1-4,7-8]/ MPT ODU synchronization source. HLS, MPT-XP,
Slot#1/Port#[1-4,7-8]/ connected to MPT-XP-HQAM,
Ch#1 CorEvo P32E1DS1,
Radio/Dir#1.[1-3]/Slot#1/ MPT ODU SDHACC)
MSS-O shelf
MSS-1
EASv2,
MPTACC
EASv2, P8ETH
Radio/Dir#1.[5-6]/Slot#1/ MPT-HL,
Port#[5-6]/Ch#1 MPT-HLC,
MPT-HLS
connected to
Core-E
Radio/Dir#1.[7-8]/Slot#1/ MPT-HL,
Port#[7-8]/Ch#1 MPT-HLC,
MPT-HLS
connected to
CorEvo


equipment
Degrade Radio/Dir#1.[5-6]/MSS/ MPT-HL, Frequency of the source Synchronization
(continued) CORE/Port#[5-6]/Ch#1 MPT-HLC, signal is degraded. alarms (Core-E,
MPT-HLS Managed only if the CorEvo, MPT-HC,
connected to interface has been MPT-HC-HQAM,
MSS-1 configured as a primary MPT-HL,
Radio/Dir#[3-8].[5-8]/ MPT-HL, or secondary MPT-HLC, MPT-
MPT-HLC, synchronization source. HLS, MPT-XP,
Slot#[3-8]/Port#[5-8]/
MPT-HLS MPT-XP-HQAM,
Ch#[0-1] P32E1DS1,
connected to
EASv2, P8ETH SDHACC)
RadioLAG#[1-14] MPT ODU,
MPT-HL,
MPT-HLC,
MPT-HLS
connected to
EASv2, P8ETH
DS1-in/Slot#[3-8]/ P32E1DS1
Port#[1-32]
DS1in/MSS/DS1/Port# MSS-1
[1-16]
E1-in/Slot#[3-8]/Port#[1- P32E1DS1
32]
E1in/MSS/E1/Port# MSS-1
[1-16]
EleSdh-in/slot#[3-8]/ STM-1/OC-3
Port[1-2]
OptSdh-in/slot#[3-8]/ STM-1/OC-3
Port[1-2]
Degrade
EthLAG#[1-14] Core-E, A member(s) of an LAG alarms
CorEvo, Ethernet or Radio LAG (Core-E, CorEvo,
MSS-1 group has no activity. MPT-HC,
RadioLAG#[1-14] MPT ODU, Degrade is declared when MPT-HL, MPT-
MPT-HL, the number of active HC-HQAM,
MPT-HLC ports in the LAG are MPT-HLC, MPT-
MPT-HLS greater than zero and less HLS, MPT-XP,
than the LAG size. MPT-XP-HQAM,
OC-3, MSS-1
shelf)


equipment
Dem XPIC LOS
r01s1b1[1-6]/daughter#04 MPT ODU Bad or missing cable/ DemXPIC LOS
connected to cable connection at XPIC
Core-E, connector on MPT ODU.
MSS-1
r01s1b1[1-4,7-8]/ MPT ODU
daughter#04 connected to
CorEvo
r01s1b1[1-3]/daughter#04 MPT ODU
connected to
MSS-O
r01s1/b[3-8][1-4]/ MPT ODU
MPTACC
r01s[3-8][5-8]b1/ MPT ODU
EASv2, P8ETH
r01/subrack#1[5-6] MPT-HLC
connected to
Core-E,
MSS-1
connected to
CorEvo
connected to
EASv2
r01s[101-102]/board#[1- MPT-HLS
10]


equipment
Demodulator Fail
Radio/Dir#1.[1-6]/ MPT ODU Loss of receive signal, Radio alarms
Slot#1/Port#[1-6]/Ch#[0-1] connected to bad receive signal, or (MPT-HC, MPT-
Core-E internal receive circuit HC-HQAM,
Radio/Dir#1.[1-4,7-8]/ MPT ODU failure. MPT-HL,
connected to MPT-HLC,
Slot#1//Port#[1-4,7-8]/
CorEvo MPT-HLS,
Ch#[0-1]
MPT-XP,
MPT-XP-HQAM)
MSS-1
MSS-O shelf
Ch#[0-1] MPTACC
P8ETH
Ch#[1] EASv2
Ch#[0-1] EASv2
Core-E
CorEvo
MSS-1


equipment
Demodulator Radio/Dir#1.[5-6]/ MPT-HLC, Loss of receive signal, Radio alarms
Fail (continued) Slot#1/Port#[5-6]/Ch#[0-1] MPT-HLS bad receive signal, or (MPT-HC, MPT-
connected to internal receive circuit HC-HQAM,
Core-E failure. MPT-HL,
Radio/Dir#1.[7-8]/ MPT-HLC, MPT-HLC,
MPT-HLS MPT-HLS,
Slot#1/Port#[7-8]/Ch#1
connected to MPT-XP,
CorEvo MPT-XP-HQAM)
connected to
MSS-1
Radio/Dir#[3-8].[5-8]/ MPT-HLC,
EASv2, P8ETH
Dialog Failure
r01/subrack#1[1-6] MPT ODU Temporary Loss of Internal loss of
connected to communication with communications
Core-E, MSS-1 MPT ODU/MPT-HL/
r01/subrack#1[1-4,7-8] MPT ODU MPT-HLC/MPT-HLS
connected to
CorEvo
r01/subrack#1[1-3] MPT ODU
connected to
MSS-O
r01/subrack#[3-8][1-4] MPT ODU
connected to
EASv2,
MPTACC
connected to
EASv2, P8ETH
r01/subrack#[3-8][5-8] MPT-HL,
MPT-HLC, or
MPT-HLS
connected to
EASv2, P8ETH


equipment
Dialog Failure r01/subrack#1[5-6] MPT-HL, Temporary Loss of Internal loss of
(continued) MPT-HLC, or communication with communications
MPT-HLS MPT ODU/MPT-HL/
connected to MPT-HLC
Core-E, MSS-1
r01/subrack#1[7-8] MPT-HL,
MPT-HLC, or
MPT-HLS
connected to
CorEvo
Duplicate Address Detected
TMNEthernet/MngtPort Core-E, Duplication of IPv6 Global Duplicate
CorEvo/TMN Unicast address detected Address
MGMT Port on TMN management Detected alarms
TMNEthernet/Port#4 Core-E, port, Port#4, In-Band
CorEvo/TMN port 1-2
Port#4
TMNInBand#[1-2] Core-E,
CorEvo/TMN
In-Band Port
[1-2]
PPP-IP/RF#1[1-6] MPT ODU Duplication of IPv6 Global Duplicate
connected to Unicast address detected Address
Core-E, MSS-1 on TMN-RF over PPP Detected alarms
PPP-IP/RF#1[1-4,7-8] MPT ODU
connected to
CorEvo
PPP-IP/RF#1[1-3] MPT ODU
connected to
MSS-O
PPP-IP/RF#[3-8][1-4] MPT ODU
connected to
EASv2,
MPTACC
connected to
EASv2, P8ETH


equipment
Duplicate PPP-IP/RF#[3-8][5-8] MPT-HL, Duplication of IPv6 Global Duplicate
address MPT-HLC, Unicast address detected Address
detected MPT-HLS on TMN-RF over PPP Detected alarms
(continued) connected to
EASv2, P8ETH
PPP-IP/RF#1[5-6] MPT-HL,
MPT-HLC,
MPT-HLS
connected to
Core-E, MSS-1
PPP-IP/RF#1[7-8] MPT-HL,
MPT-HLC,
MPT-HLS
connected to
CorEvo
PPP-IP/RF/LAG#[1-14] MPT ODU,
MPT-HL,
MPT-HLC
MPT-HLS


equipment
Early Warning Indication
Radio/Dir#1.[1-6]/ MPT ODU 10E-9 BER detected Radio alarms
Slot#1/Port#[1-6]/Ch#[0-1] connected to (MPT-HC, MPT-
Core-E HC-HQAM,
Radio/Dir#1.[1-4,7-8]/ MPT ODU MPT-HL,
Slot#1/Port#[1-4,7-8]/
CorEvo MPT-HLS,
Ch#[0-1]
MPT-XP,
MPT-XP-HQAM)
MSS-O
MSS-1
Ch#[0-1] MPTACC
P8ETH
Ch#[1] EASv2
Ch#[0-1] EASv2
Core-E
CorEvo
MSS-1


equipment
Early Warning Radio/Dir#1.[5-6]/ MPT-HLC or 10E-9 BER detected Radio alarms
Indication Slot#1/Port#[5-6]/Ch#[0-1] MPT-HLS (MPT-HC, MPT-
(continued) connected to HC-HQAM,
Core-E MPT-HL,
Radio/Dir#1.[7-8]/ MPT-HLC or MPT-HLC,
MPT-HLS,
CorEvo MPT-XP-HQAM)
connected to
MSS-1
Radio/Dir#[3-8].[5-8]/ MPT-HLC or
EASv2, P8ETH
Eth OAM Loss of Continuity
MEP#MDID[1-16]#MA ID Core-E, MEP received no CCM Ethernet
[1-512]#MEPID[1-8191] CorEvo, frames from a peer MEP connectivity
MSS-1, MSS-O during an interval equal fault
to 3.5 times the CCM management
transmission interval alarms
configured at the MEP.
Eth OAM Mismerge Condition
MEP#MDID[1-16]#MA ID Core-E, MEP received a CCM Ethernet
[1-512]#MEPID[1-8191] CorEvo, frame with correct MD connectivity
MSS-1, MSS-O Level but incorrect MA ID. fault
management
alarms
Eth OAM Remote Defect Indicator
[1-512]#MEPID[1-8191] CorEvo, frame with the RDI field connectivity
MSS-1, MSS-O set. fault
management
alarms
Eth OAM Unexpected Levels
[1-512]#MEPID[1-8191] CorEvo, frame with the incorrect connectivity
MSS-1, MSS-O MD Level. fault
management
alarms


equipment
Eth OAM Unexpected MEPID
MEP#MDID[1-16]#MA ID Core-E, Received MEPID value is Ethernet
[1-512]#MEPID[1-8191] CorEvo, different than the connectivity
MSS-1, MSS-O expected MEPID. fault
management
alarms
Eth OAM Unexpected Period
MEP#MDID[1-16]#MA ID Core-E, Received MEP Time-Out Ethernet
[1-512]#MEPID[1-8191] CorEvo, period value is different connectivity
MSS-1, MSS-O than the expected MEP fault
Time-Out period. management
alarms
Excessive Environmental Temperature
r01/subrack#[3-8][5-8] MPT-HL, Excessive temperature on Equipment
MPT-HLC MPT-HL/HLC/HLS alarms
connected to Transceiver
EASv2, P8ETH
MPT-HLC
connected to
Core-E, MSS-1
MPT-HLC
connected to
CorEvo
r01/s[101-102]board/# MPT-HLS
[1-10]
r01/subrack#[3-8][5-8] MPT-HL Failure or Missing MPT-HL Equipment
connected to Transceiver Fan Unit alarms
EASv2, P8ETH detected
connected to
Core-E, MSS-1
r01/subrack#1[7-8] MPT-HL
connected to
CorEvo
Fan Communication Problem
r01s[101-102]/board# MPT-HLS Problem communicating Fan
[1-10] with the MPT-HLS fan has Communication
been detected Problem (MPT-
HLS)


equipment
Fan Fail
r01/subrack#1[5-6] MPT-HLC Failure of at least one Fan Fail (MPT-
connected to MPT-HLC Transceiver Fan HLC)
Core-E, Unit detected
MSS-1
connected to
CorEvo
connected to
EASv2, P8ETH
Firmware Download On Going
r01s1/board#[8] AUX Download Status. A No action
r01s1/board#[1-2] Core-E, download of an FPGA or required.
CorEvo other software unit on
r01s1/board#1 MSS-O the addressed card.
r01s1/MSS/CORE MSS-1
r01s1/board#[3-8] EASv2
MPTACC,
P2E3DS3,
P8ETH,
P32E1DS1,
SDHACC
connected to
Core-E,
MSS-1
r01s1b1[1-4,7-8] MPT ODU
connected to
CorEvo
connected to
MSS-O
connected to
EASv2,
MPTACC
connected to
EASv2, P8ETH


equipment
Firmware r01/subrack#1[5-6] MPT-HL, Download Status. A No action
Download MPT-HLC download of an FPGA or required.
connected to other software unit on
On Going
Core-E, the addressed card.
(continued)
MSS-1
MPT-HLC
connected to
CorEvo
MPT-HLC
connected to
EASv2, P8ETH
r01/s[101-102]board#[1- MPT-HLS
10]
Flash Card r01/subrack#1 Core-E, An indication that the Call CTAC
Failure CorEvo, SNMPv3 agent had a
MSS-O, failure writing the set-up
file to the flash card.
MSS-1
Indicates a failed flash
card on the Core-E,
CorEvo, MSS-O, or MSS-1.
Flash Card r01s1/board#[1-2] Core-E, Flash Card realignment of No action
Realignment in CorEvo Standby Core in progress required
Progress


equipment
High BER
Radio/Dir#1.[1-6]/ MPT ODU Bit Error Rate threshold Radio alarms
Slot#1/Port#[1-6]/Ch#[0-1] connected to (10E-4) exceeded on (MPT-HC, MPT-
Core-E receiver input circuits on HC-HQAM,
Radio/Dir#1.[1-4,7-8]/ MPT ODU MPT ODU, MPT-HL, MPT-HL,
connected to MPT-HLC transceiver. MPT-HLC,
Slot#1/Port#[1-4,7-8]/
CorEvo MPT-HLS,
Ch#[0-1]
MPT-XP,
MPT-XP-HQAM)
MSS-O
MSS-1
Ch#[0-1] MPTACC
P8ETH
EASv2
Ch#[0-1] EASv2
Core-E
CorEvo
MSS-1
connected to
Core-E


equipment
High BER Radio/Dir#1.[7-8]/ MPT-HLC, Bit Error Rate threshold Radio alarms
(continued) Slot#1/Port#[7-8]/Ch#[0-1] MPT-HLS (10E-4) exceeded on (MPT-HC, MPT-
connected to receiver input circuits on HC-HQAM,
CorEvo MPT ODU, MPT-HL, MPT-HL,
Radio/Dir#1.[5-6]/MSS/ MPT-HLC, MPT-HLC transceiver. MPT-HLC,
MPT-HLS,
MSS-1 MPT-XP-HQAM)
Radio/Dir#[3-8].[5-8]/ MPT-HLS
Ch#[0-1] EASv2
EleSdh-in/slot#[3-8]/ SDHACC Bit Error Rate threshold Facility alarms
Port[1-2] (STM-1/OC-3) (10E-5) exceeded on
OptSdh-in/slot#[3-8]/ receiver input circuits on
Port[1-2] SDHACC card from
MS/slot#[3-8]/Port#1 SDHACC demarcation panel for
(STM-1) the OC-3 facility.
EleSdh-out/slot#[3-8]/ SDHACC Bit Error Rate threshold Facility alarms
Port[1-2] (STM-1/OC-3) (10E-5) exceeded on
OptSdh-out/slot#[3-8]/ transmit output circuits
on SDHACC card to the
Port[1-2]
demarcation panel for
the OC-3 facility.
Housekeeping Alarm
ExtPt/Input#[1-6] AUX Housekeeping alarm Housekeeping
ExtPt/Input#[11-14] Fan input is active. alarms
ExtPt/Input#[11-14] MSS-1


equipment
Incompatible Frequency
Radio/Dir#1.[1-6]/ MPT ODU Configured frequency is Radio alarms
Slot#1/Port#[1-6]/Ch#[0-1] connected to outside of the supported (MPT-HC, MPT-
Core-E frequency range. HC-HQAM,
Slot#1/Port#[1-4,7-8]/
CorEvo MPT-HLS,
Ch#[0-1]
MPT-XP,
MPT-XP-HQAM)
MSS-O
MSS-1
Ch#[0-1] MPTACC
P8ETH
Ch#[1] EASv2
Ch#[0-1] EASv2
Core-E
CorEvo
MSS-1


equipment
Incompatible Radio/Dir#1.[5-6]/ MPT-HLC or Configured frequency is Radio alarms
Frequency Slot#1/Port#[5-6]/Ch#[0-1] MPT-HLS outside of the supported (MPT-HC, MPT-
(continued) connected to frequency range. HC-HQAM,
Core-E MPT-HL,
Radio/Dir#1.[7-8]/ MPT-HLC or MPT-HLC,
MPT-HLS MPT-HLS,
CorEvo MPT-XP-HQAM)
connected to
MSS-1
Ch#[0-1] P8ETH
EASv2


equipment
Incompatible Modulation
Radio/Dir#1.[1-6]/ MPT ODU Configured modulation is Radio alarms
Slot#1/Port#[1-6]/Ch#[0-1] connected to not supported by (MPT-HC, MPT-
Core-E MPT ODU or MPT-HLC. HC-HQAM,
Slot#1/Port#[1-4,7-8]/
CorEvo MPT-HLS,
Ch#[0-1]
MPT-XP,
MPT-XP-HQAM)
MSS-O
MSS-1
Ch#[0-1] MPTACC
P8ETH
EASv2
Ch#[0-1] EASv2
Core-E
CorEvo
MSS-1


equipment
Incompatible Radio/Dir#[3-8].[5-8]/ MPT-HL Configured modulation is Radio alarms
Modulation Slot#[3-8]/Port#[5-8]/ connected to not supported by (MPT-HC, MPT-
(continued) Ch#[0-1] EASv2, P8ETH MPT ODU or MPT-HLC. HC-HQAM,
MPT-HL,
Radio/Dir#1.[5-6]/ MPT-HLC or
MPT-HLC,
Slot#1/Port#[5-6]/Ch#[0-1] MPT-HLS MPT-HLS,
connected to
MPT-XP,
Core-E
MPT-XP-HQAM)
connected to
MSS-1
Slot#1/Port#[7-8]/Ch#1 MPT-HLS
connected to
CorEvo
Ch#[0-1] P8ETH
EASv2


equipment
Incompatible Protection
Radio/Dir#1.[1-6]/ MPT ODU Incorrectly configured or Radio alarms
Slot#1/Port#[1-6]/Ch#[0-1] connected to missing RPS/XPIC module (MPT-HC, MPT-
Core-E on MPT ODU. HC-HQAM,
Slot#1/Port#[1-4,7-8]/
CorEvo MPT-HLS,
Ch#[0-1]
MPT-XP,
MPT-XP-HQAM)
MSS-1
MSS-O
Ch#[0-1] MPTACC
Ch#[0-1] EASv2
Incompatible Shifter
Radio/Dir#1.[1-6]/ MPT ODU Configured shifter value Radio alarms
Slot#1/Port#[1-6]/Ch#[0-1] connected to not supported by (MPT-HC, MPT-
Core-E MPT ODU, MPT-HL, or HC-HQAM,
Radio/Dir#1.[1-4,7-8]/ MPT ODU MPT-HLC. MPT-HL,
Slot#1/Port#[1-4,7-8]/
CorEvo MPT-HLS,
Ch#[0-1]
MPT-XP,
MPT-XP-HQAM)
MSS-O
MSS-1
Ch#[0-1] MPTACC
P8ETH
Ch#[1] EASv2


equipment
Incompatible Radio/Dir#[3-8].[5-8]/ MPT ODU Configured shifter value Radio alarms
Shifter Slot#[3-8]/Port#[5-8]/ connected to not supported by (MPT-HC, MPT-
(continued) Ch#[0-1] EASv2 MPT ODU, MPT-HL, or HC-HQAM,
MPT-HLC. MPT-HL,
MPT-HLC,
Slot#1/Port#[5-6]/Ch#[0-1] MPT-HLS MPT-HLS,
connected to
MPT-XP,
Core-E
MPT-XP-HQAM)
connected to
CorEvo
connected to
MSS-1
Ch#[0-1] P8ETH
EASv2


equipment
Incompatible Tx Power
Radio/Dir#1.[1-6]/ MPT ODU Configured RTPC/ATPC Radio alarms
Slot#1/Port#[1-6]/Ch#[0-1] connected to Tx power value or ATPC (MPT-HC, MPT-
Core-E Rx power threshold value HC-HQAM,
Radio/Dir#1.[1-4,7-8]/ MPT ODU not supported by MPT-HL,
Slot#1/Port#[1-4,7-8]/ connected to MPT-HL, MPT-HLC, or MPT-HLC,
Ch#[0-1] CorEvo MPT ODU. MPT-HLS,
Radio/Dir#1.[1-3]/ MPT ODU MPT-XP,
MPT-XP-HQAM)
MSS-O
MSS-1
Ch#[0-1] MPTACC
P8ETH
Ch#[1] EASv2
Ch#[0-1] EASv2
Core-E
CorEvo
MSS-1
connected to
Core-E


equipment
Incompatible Tx Radio/Dir#1.[7-8]/ MPT-HLC or Configured RTPC/ATPC Radio alarms
Power Slot#1/Port#[7-8]/Ch#[0-1] MPT-HLS Tx power value or ATPC (MPT-HC, MPT-
(continued) connected to Rx power threshold value HC-HQAM,
CorEvo not supported by MPT-HL,
Radio/Dir#1.[5-6]/MSS/ MPT-HLC or MPT-HL, MPT-HLC, or MPT-HLC,
MPT ODU. MPT-HLS,
MSS-1 MPT-XP-HQAM)
Slot#[3-8]8]/Port#[5-/ connected to
Ch#[0-1] P8ETH
Slot#[3-8]8]/Port#[5-/ MPT-HLS
EASv2
Internal Communication Problem
r01/subrack#1[1-6] MPT ODU Loss of communications Internal loss of
connected to with MPT ODU, MPT-HL, communications
Core-E, MSS-1 or MPT-HLC.
r01/subrack#1[1-4,7-8] MPT ODU
connected to
CorEvo
connected to
MSS-O
connected to
EASv2,
MPTACC
connected to
EASv2, P8ETH


equipment
Internal r01/subrack#[3-8][5-8] MPT-HL, Loss of communications Internal loss of
communication MPT-HLC with MPT ODU, MPT-HL, communications
problem connected to or MPT-HLC.
(continued) EASv2, P8ETH
MPT-HLC
connected to
Core-E, MSS-1
MPT-HLC,
connected to
CorEvo
r01/subrack#[101-102]/ MPT-HLS
board#[1-10]
LAG Port Down
Radio/Dir#1.[1-3]/ MPT ODU Reported when a member LAG alarms
Slot#1/Port#[1-3]/Ch#1 connected to of an L1 LAG is removed (Core-E, CorEvo,
MSS-O from the LAG group (not MPT-HC,
Radio/Dir#[3-8].[1-4]/ MPT ODU supported on P8ETH). MPT-HL, MPT-
HC-HQAM,
EASv2 MPT-HLC, MPT-
Radio/Dir#[3-8].[5-8]/ MPT ODU, HLS, MPT-XP,
MPT-XP-HQAM,
Slot#[3-8]/Port#[5-8]/Ch#1 MPT-HL,
MPT-HLC, or OC-3, MSS-1
MPT-HLS shelf)
connected to
EASv2


equipment
Link Identifier Mismatch
AirFrame/Dir#1.[1-6]/ MPT ODU Link identifier number Radio alarms
Slot#1/Port#[1-6]/Ch#1, connected to provisioned on MPT ODU/ (MPT-HC, MPT-
Core-E MPT-HL/ MPT-HLC card HC-HQAM,
AirFrame/Dir#1.[1-6]/
settings screen is MPT-HL,
Slot#1/Port#[1-6] different from link MPT-HLC,
AirFrame/Dir#1.[1-4.7-8]/ MPT ODU identifier number MPT-HLS,
Slot#1/Port#[1-4.7-8]/ connected to provisioned at the far end MPT-XP,
Ch#1, CorEvo of hop. MPT-XP-HQAM)
AirFrame/Dir#1.[1-4. 7-8]/
Slot#1/Port#[1-4.7-8]
AirFrame/Dir#1.[1-3]/ MPT ODU
Slot#1/Port#[1-3]/Ch#1, connected to
MSS-O
Slot#1/Port#[1-3]
AirFrame/Dir#1.[1-6]/MSS/ MPT ODU
CORE/Port#[1-6]/Ch#1, connected to
MSS-1
AirFrame/Dir#1.[1-6]/MSS/
CORE/Port#[1-6]
AirFrame/Dir#[3-8].[1-4]/ MPT ODU
Ch#1, MPTACC
AirFrame/Dir#[3-8].[1-4]/
Slot#[3-8]/Port#[1-4]
Ch#1, EASv2, P8ETH
Slot#[3-8]/Port#[5-8]
EASv2


equipment
Link Identifier AirFrame/Dir#1.[5-6]/ MPT-HL Link identifier number Radio alarms
Mismatch Slot#1/Port#[5-6]/Ch#1 connected to provisioned on MPT ODU/ (MPT-HC, MPT-
(continued) Core-E MPT-HL/ MPT-HLC card HC-HQAM,
AirFrame/Dir#1.[7-8]/ MPT-HL settings screen is MPT-HL,
connected to different from link MPT-HLC,
CorEvo identifier number MPT-HLS,
AirFrame/Dir#1.[5-6]/MSS/ MPT-HL provisioned at the far end MPT-XP,
connected to of hop. MPT-XP-HQAM)
CORE/Port#[5-6]/Ch#1
MSS-1
AirFrame/Dir#[3-8].[5-8]/ MPT-HL
Ch#1, EASv2, P8ETH
Slot#[3-8]/Port#[5-8]
AirFrame/Dir#1.[5-6]/ MPT-HLC or
Slot#1/Port#[5-6]/Ch#1, MPT-HLS
connected to
Core-E
Slot#1/Port#[5-6]
AirFrame/Dir#1.[7-8]/MSS/ MPT-HLC or
CORE/Port#[7-8]/Ch#1 MPT-HLS
connected to
CorEvo
ORE/Port#[7-8]
AirFrame/Dir#1.[5-6]/MSS/ MPT-HLC or
CORE/Port#[5-6]/Ch#1, MPT-HLS
connected to
MSS-1
CORE/Port#[5-6]
AirFrame/Dir#[3-8].[5-8]/ MPT-HLC
Ch#1, P8ETH, EASv2
Slot#[3-8]/Port#[5-8]
AirFrame/Dir#[3-8].[5-8]/ MPT-HLS
Ch#1, EASv2
Slot#[3-8]/Port#[5-8]


equipment
Loop Problem
Radio/Dir#1.[1-6]/ MPT ODU Loss of ATPC command ATPC loop
Slot#1/Port#[1-6]/Ch#[0-1] connected to path between far end condition
Core-E transmitter and local (MPT-HC, MPT-
Radio/Dir#1.[1-4,7-8]/ MPT ODU receiver. HC-HQAM,
connected to MPT-HL,
Slot#1/Port#[1-4,7-8]/
CorEvo MPT-HLC, MPT-
Ch#[0-1]
HLS, MPT-XP,
MPT-XP-HQAM)
MSS-O
MSS-1
Ch#[0-1] MPTACC
P8ETH
EASv2
Ch#[0-1] EASv2
Core-E


equipment
Loop Problem Radio/Dir#1.[7-8]/ MPT-HL Loss of ATPC command ATPC loop
(continued) Slot#1/Port#[7-8]/Ch#1 connected to path between far end condition
CorEvo transmitter and local (MPT-HC, MPT-
Radio/Dir#1.[5-6]/MSS/ MPT-HL receiver. HC-HQAM,
connected to MPT-HL,
MSS-1 MPT-HLC, MPT-
Radio/Dir#[3-8].[5-8]/ MPT-HL HLS, MPT-XP,
connected to MPT-XP-HQAM)
Slot#[3-8]/Port#[5-8]/
connected to
Core-E
Slot#1/Port#[7-8]/Ch#1 MPT-HLS
connected to
CorEvo
connected to
MSS-1
Ch#[0-1] P8ETH, EASv2
Ch#[0-1] EASv2


equipment
Loss of Alignment
Hitless/Dir#1.[1-6] MPT ODU Delay/loss of alignment Loss of
connected to between main and alignment
Core-E, MSS-1 protect RPS RF paths (MPT-HC,
Hitless/Dir#1.[1-4,7-8] MPT ODU detected. MPT-HL,
connected to MPT-HLC, MPT-
CorEvo HLS, MPT-XP)
Hitless/Dir#1.[1-2] MPT ODU
connected to
MSS-O
Hitless/Dir#[3-8].[1-4] MPT ODU
connected to
MPTACC
Hitless/Dir#[3-8].[5-8] MPT ODU
connected to
EASv2
Hitless/Dir#[3-8].[5-8] MPT-HL
connected to
EASv2, P8ETH
Hitless/Dir#1.[1-6] MPT-HLC or
MPT-HLS
connected to
Core-E, MSS-1
Hitless/Dir#1.[7-8] MPT-HLC or
MPT-HLS
connected to
CorEvo
Hitless/Dir#[3-8].[5-8] MPT-HLC
connected to
EASv2, P8ETH
Hitless/Dir#[3-8].[5-8] MPT-HLS
connected to
EASv2


equipment
Loss Ethernet Synchronization Message Channel
MAU/Slot#[1-2]/Port#[1-6] Core-E Reported if there is a loss Synchronization
MAU/Slot#[1-2]/Port#[1-8] CorEvo of the Ethernet alarms (Core-E,
MAU/Slot#1/Port#[1-4] MSS-O Synchronization Message CorEvo, MPT-HC,
Channel. The alarm is MPT-HC-HQAM,
MAU/MSS/CORE/Port#[1-6] MSS-1
applicable to Core-E, MPT-HL,
MAU/Slot#[3-8]/Port#[1-8] EASv2 EASv2, and MSS-1 MPT-HLC, MPT-
RadioLAG#[1-14] MPT ODU, Ethernet ports and Radio HLS, MPT-XP,
MPT-HL, interfaces (MPT ODU, MPT-XP-HQAM,
MPT-HLC, MPT-HL, or MPT-HLC) P32E1DS1,
MPT-HLS configured with SSM SDHACC)
Radio/Dir#1.[1-6]/ MPT ODU support enabled and is
Slot#1/Port#[1-6]/Ch#[0-1] connected to assigned as a synchronous
Core-E clock source input.
Radio/Dir#1.[1-4,7-8]/ MPT ODU
Slot#1/Port#[1-4,7-8]/ connected to
Ch#[0-1] CorEvo
MSS-O
MSS-1
Ch#[0-1] MPTACC
P8ETH
EASv2
Ch#[0-1] EASv2


equipment
Loss Ethernet Radio/Dir#1.[5-6]/ MPT-HL Reported if there is a loss Synchronization
Synchronization Slot#1/Port#[5-6]/Ch#1 connected to of the Ethernet alarms (Core-E,
Message Core-E Synchronization Message CorEvo, MPT-HC,
Channel Radio/Dir#1.[7-8]/ MPT-HL Channel. The alarm is MPT-HC-HQAM,
(continued) connected to applicable to Core-E, MPT-HL,
CorEvo EASv2, and MSS-1 MPT-HLC, MPT-
Radio/Dir#1.[5-6]/MSS/ MPT-HL Ethernet ports and Radio HLS, MPT-XP,
connected to interfaces (MPT ODU, MPT-XP-HQAM,
CORE/Port#[5-6]/Ch#1 MPT-HL, or MPT-HLC) P32E1DS1,
MSS-1
configured with SSM SDHACC)
support enabled and is
assigned as a synchronous
clock source input.
connected to
Core-E
Slot#1/Port#[7-8]/Ch#0-1] MPT-HLS
connected to
CorEvo
connected to
MSS-1
Ch#[0-1] EASv2


equipment
Loss of CESoETH Frame
CircuitTDM/MSS/DS1/ DS1 on MSS-1 Packets are not being Facility alarms
Port#[1-16] shelf received by the DS1, DS3,
or OC-3 emulation
CircuitTDM/Slot#[3-8]/ DS1 on
circuits on the receive
Port#[1-32] P32E1DS1
circuits from the switch
CircuitTDM/MSS/E1/ E1 on MSS-1 matrix.
Port#[1-16] shelf
CircuitTDM/Slot#[3-8]/ E1 on
CircuitTDM/Slot#[3-8]/ DS3
Port#[1-2]
CircuitTDM/Slot#[3-8]/ STM-1/OC-3
Port#[1-2]
CircuitTDM#[1-3]-[1-7]- Channelized
[1-3]/Slot#[3-8]/Port#1 E1
Loss of Frame
DS1-in/MSS/DS1/Port#[1- DS1 on MSS-1 Loss of DS1, DS3, E1, STM- Facility alarms
16] shelf 1, or OC-3 frame
DS1-in/Slot#[3-8]/Port#[1- DS1 on detected incoming to the
32] P32E1DS1 PDH/SDH card from the
demarcation panel for
the DS1, DS3, E1, STM-1,
2]
or OC-3 facility.
E1-in/MSS/DS1/Port#[1-16] E1 on MSS-1
shelf
32] P32E1DS1
Port[1-2]
OptSdh-in/slot#[3-8]/
Port[1-2]
MS/Slot#[3-8]/Port#1 Channelized
E1


equipment
Loss of Frame DS1-out/MSS/DS1/ DS1 on MSS-1 Loss of DS1, DS3, E1, STM- Facility alarms
(continued) Port#[1-16] shelf 1, or OC-3 frame
detected from the Core-E
DS1-out/Slot#[3-8]/ DS1 on
switch matrix for the
DS1, DS3, E1, STM-1, or
DS3-out/Slot#[3-8]/ DS3 OC-3 facility
Port#[1-2]
E1-out/MSS/DS1/ E1 on MSS-1
Port#[1-16] shelf
E1-out/Slot#[3-8]/ E1 on
EleSdh-out/slot#[3-8]/ STM-1/OC-3
Port[1-2]
OptSdh-out/slot#[3-8]/
Port[1-2]
E1-out#[1-3]-[1-7]- Channelized
[1-3]/Slot#[3-8]/Port#1 E1
Radio/Dir#1.[1-6]/ MPT ODU Far end TX problems, RF Loss of frame
Slot#1/Port#[1-6]/Ch#[0-1] connected to path problems, or local (MPT-HC, MPT-
Core-E circuit failures have HC-HQAM,
Radio/Dir#1.[1-4,7-8]/ MPT ODU caused BER to increase to MPT-HL,
Slot#1/Port#[1-4,7-8]/ connected to the point that frames are MPT-HLC,
Ch#[0-1] CorEvo being lost. MPT-HLS,
Radio/Dir#1.[1-3]/ MPT ODU MPT-XP,
MSS-O
MSS-1
Ch#[0-1] MPTACC


equipment
Loss of Frame Radio/Dir#[3-8].[5-8]/ MPT ODU Far end TX problems, RF Loss of frame
(continued) Slot#[3-8]/Port#[5-8]/Ch#1 connected to path problems, or local (MPT-HC, MPT-
P8ETH circuit failures have HC-HQAM,
Radio/Dir#[3-8].1-4]/ MPT ODU caused BER to increase to MPT-HL,
the point that frames are MPT-HLC,
EASv2 being lost. MPT-HLS,
Radio/Dir#[3-8].[5-8]/ MPT ODU MPT-XP,
Slot#[3-8]/Port#[5-8]/
Ch#[0-1] EASv2
Core-E
Radio/Dir#1.[7-8]/Slot#1/ MPT-HL
CorEvo
MSS-1
connected to
Core-E
connected to
CorEvo
connected to
MSS-1
Ch#[0-1] EASv2


equipment
Loss of multi-frame
AU4/Slot#[3-8]/Port#1 Channelized Loss of multi-frame Facility alarms
E1 detected for the VC4 (Tx
Direction).
Loss of Pointer
AU4/Slot#[3-8]/Port#1 Channelized Loss of pointer detected Facility alarms
E1 for the AU4 (Tx
Direction).
TU12#[1-3]-[1-7]-[1-3]/ Channelized Loss of pointer detected
Slot#[3-8]/Port#1 E1 for the TU12 (Tx
Direction).
Loss of Protection
Radio/Dir#1.[1-6]/ MPT ODU The radio direction is Radio alarms
Slot#1/Port#[1-6]/Ch#1 connected to affected by a failure that (MPT-HC, MPT-
Core-E radio protection (RPS) HC-HQAM,
Radio/Dir#1.[1-4,7-8]/ MPT ODU can’t recover. Only MPT-HL,
Slot#1/Port#[1-4,7-8]/ connected to reported if RPS is MPT-HLC,
Ch#1 CorEvo provisioned. MPT-HLS,
Radio/Dir#1.[1-6]/MSS/ MPT ODU MPT-XP,
MSS-1
Radio/Dir#1.1/Slot#1/ MPT ODU
Port#1/Ch#1 connected to
MSS-O
MPTACC
EASv2
connected to
Core-E


equipment
Loss of Radio/Dir#1.[7-8]/ MPT-HLC or The radio direction is Radio alarms
Protection Slot#1/Port#[7-8]/Ch#[0-1] MPT-HLS affected by a failure that (MPT-HC, MPT-
(continued) connected to radio protection (RPS) HC-HQAM,
CorEvo can’t recover. Only MPT-HL,
Radio/Dir#1.[5-6]/MSS/ MPT-HLC or reported if RPS is MPT-HLC,
provisioned. MPT-HLS,
MSS-1 MPT-XP-HQAM)
Ch#[0-1] EASv2
Loss of Signal
DS1-in/MSS/DS1/Port#[1- DS1 on MSS-1 No DS1, DS3, or OC-3 Facility alarms
16] input signal detected.
DS1-in/Slot#[3-8]/Port#[1- DS1 on
32] P32E1DS1
E1-in/MSS/DS1/Port#[1-16] E1 on MSS-1
32] P32E1DS1
2]
Port[1-2]
Port[1-2]
Loss of Signal TMNEthernet/MngtPort Core-E, Loss of Signal is declared Ethernet alarms
(continued) CorEvo, MSS- when either: (Core-E, CorEvo,
1, MSS-0 TMN no Ethernet input signal EASv2, MPTACC,
MGMT Port detected on the Ethernet P8ETH, MSS-O
TMNEthernet/MngtPort#4 Core-E, port Shelf, MSS-1
CorEvo, MSS- Shelf)
a communication
1 TMN Port#4 problem with the remote
MAU/Slot#[1-2]/Port#[1-6] Core-E peer (that is, a link down
MAU/Slot#[1-2]/Port#[1-8] CorEvo condition)
MAU/Slot#1/Port#[1-4] MSS-O
MAU/Slot#[3-8]/Port#[1-4] MPTACC
MAU/Slot#[3-8]/Port#[1-8] EASv2, P8ETH


equipment
r01s1[1-6]b1/daughter#03 RPS SFP on Loss of Signal detected on Radio alarms
MPT ODU an MPT ODU/MPT-HL (MPT-HC, MPT-
connected to Ethernet Coupler Port. HC-HQAM,
Core-E, MSS-1 Only reported when RPS MPT-HL,
r01s1[1-4,7-8]b1/ RPS SFP on is provisioned. MPT-HLC,
daughter#03 MPT ODU MPT-HLS,
CorEvo MPT-XP-HQAM)
r01s1[1-2]b1/daughter#03 RPS SFP on
MPT ODU
connected to
MSS-O
r01s1[3-8][1-4]b1/ RPS SFP on
daughter#03 MPT ODU
connected to
EASv2,
MPTACC
MAU/subrack[#3-8].[5-8] MPT-HL,
Port#n MPT-HLC
connected to
EASv2, P8ETH
r01s[101-102]b[1-10]/ RPS SFP on
daughter#03 MPT-HLS
Loss of Signal Sync-in/Port#1 Core-E Generated when no signal Synchronization
(continued) Sync-in/Port#[5-6] MSS-1 is present on the alarms (Core-E,
Sync-in/Port#[7-8] CorEvo incoming Sync-In port. CorEvo, MPT-HC,
MPT-HC-HQAM,
MPT-HL,
MPT-HLC, MPT-
HLS, MPT-XP,
MPT-XP-HQAM,
P32E1DS1,
SDHACC)
EthLAG#[1-14] Core-E, ALL members of an LAG alarms
Core-Evo, Ethernet or Radio LAG (Core-E, CorEvo,
MSS-1, MSS-O group have no activity. MPT-HC,
RadioLAG#[1-14] MPT ODU, Loss of Signal is declared MPT-HL, MPT-
MPT-HL, when the number of HC-HQAM,
MPT-HLC, active ports in the LAG MPT-HLC, MPT-
MPT-HLS, equals zero. HLS, MPT-XP,
MPT-XP-HQAM,
OC-3, MSS-1
shelf)
Low Input Voltage


equipment
r01/subrack#1[1-6] MPT-HC/XP- Reported when the input Radio alarms
HQAM voltage drops below the (MPT-HC, MPT-
connected to configured threshold. HC-HQAM,
Core-E, MSS-1 MPT-HL,
r01/subrack#1[1-4,7-8] MPT-HC/XP- MPT-HLC,
HQAM MPT-HLS,
CorEvo MPT-XP-HQAM)
r01/subrack#1[1-3] MPT-HC/XP-
HQAM
connected to
MSS-O
r01/subrack#[3-8][1-4] MPT-HC/XP-
HQAM
connected to
EASv2,
MPTACC
r01/subrack#[3-8][5-8] MPT-HC/XP-
HQAM
connected to
EASv2, P8ETH


equipment
OAM Discovery Not Completed
ETHLinkOAM/Slot#1/ Ethernet port The Ethernet port (EFM) OAM discovery
Ports[1-6] on Core-E OAM discovery process is not completed
ETHLinkOAM/Slot#1/ Ethernet port not in operational status. (Core-E, CorEvo,
Ports[1-8] on CorEvo EASv2, P8ETH,
ETHLinkOAM/MSS/CORE/ Ethernet port MSS-1, MSS-O)
Ports[1-6] on MSS-1
ETHLinkOAM/Slot#1/ Ethernet port
Ports[1-4] on MSS-O
ETHLinkOAM/Slot#[3-8]/ Ethernet port
Ports[1-8] on EASv2,
P8ETH


equipment
Power Supply Failure
r01/subrack#[3-8][1-4] EASv2 MPT Power Supply Failure Power alarms
r01/subrack#[3-8][1-4] MPTACC detected, either an
r01/subrack#1[1-2] MSS-O Open-Circuit or Over-
Current condition on an
r01/subrack#1[1-2] MSS-1
EASv2, MPTACC, MSS-O,
or MSS-1 power supply
port.
PPP Fail
PPP-IP/RF#1[1-6] MPT ODU TMN over PPP Fail Radio alarms
connected to (MPT-HC, MPT-
Core-E, MSS-1 HC-HQAM,
PPP-IP/RF#1[1-4,7-8] MPT ODU MPT-HL,
CorEvo MPT-HLS,
PPP-IP/RF#1[1-3] MPT ODU MPT-XP,
MSS-O
connected to
EASv2,
MPTACC
connected to
EASv2, P8ETH
PPP-IP/RF#[3-8][5-8] MPT-HL
connected to
EASv2, P8ETH
PPP-IP/RF#1[5-6] MPT-HL
connected to
Core-E, MSS-1
PPP-IP/RF#1[7-8] MPT-HL
connected to
CorEvo
PPP-IP/RF#[3-8][5-8] MPT-HLC
connected to
EASv2, P8ETH


equipment
PPP Fail PPP-IP/RF#1[5-6] MPT-HLC or TMN over PPP Fail Radio alarms
(continued) MPT-HLS (MPT-HC, MPT-
connected to HC-HQAM,
Core-E, MSS-1 MPT-HL,
PPP-IP/RF#1[7-8] MPT-HLC or MPT-HLC,
MPT-HLS MPT-HLS,
CorEvo MPT-XP-HQAM)
PPP-IP/RF#[3-8][5-8] MPT-HLS
connected to
EASv2
Provisioning Mismatch
r01s1/board#[1-2] Core-E, The wrong flash card is License/
CorEvo installed and the current software
r01s1/board#1 MSS-O database is in conflict mismatch
r01s1/MSS/CORE MSS-1 with the license string on
the card.
Radio Encryption Mismatch
Radio/Dir#1.[1-6]/ MPT ODU Radio encryption is Radio encryption
Slot#1/Port#[1-6]/Ch#1 connected to enabled on one end of mismatch
Core-E the radio hop and not on (MPT-HC, MPT-
Radio/Dir#1.[1-4,7-8]/ MPT ODU the other end of the hop. HC-HQAM,
Slot#1/Port#[1-4,7-8]/ connected to Or the radio encryption MPT-HLC,
Ch#1 CorEvo key provisioned on one MPT-HLS,
Radio/Dir#1.[1-3]/ MPT ODU end is different than the MPT-XP,
connected to key provisioned on the MPT-XP-HQAM)
MSS-O other end of the hop.
MSS-1
MPTACC
Radio/Dir#[3-8].[5-8]/ MPT OD
P8ETH
EASv2


equipment
Radio Radio/Dir#[3-8].[5-8]/ MPT ODU Radio encryption is Radio encryption
encryption Slot#[3-8]/Port#[5-8]/Ch#1 connected to enabled on one end of mismatch
mismatch EASv2 the radio hop and not on (MPT-HC, MPT-
(continued) Radio/Dir#1.[5-6]/ MPT-HLC, the other end of the hop. HC-HQAM,
MPT-HLS Or the radio encryption MPT-HLC,
connected to key provisioned on one MPT-HLS,
Core-E end is different than the MPT-XP,
Radio/Dir#1.[7-8]/ MPT-HLC, key provisioned on the MPT-XP-HQAM)
MPT-HLS other end of the hop.
connected to
CorEvo
CORE/Port#[5-6]/Ch#1 MPT-HLS
connected to
MSS-1
EASv2, P8ETH
EASv2
Rate Mismatch
MAU/Slot#[1-2]/Port#[5-8] Core-Evo Reported when the Rate mismatch
configured speed of an (CorEvo)
optical 10 GbEth/1 GbEth
User Ethernet interface
or an optical 1 GbEth
User Ethernet interface is
not compatible with the
provisioned SFP
transceiver.


equipment
Remote Defect Indication
Radio/Dir#1.[1-6]/ MPT ODU Remote Defect Indication Radio alarms
Slot#1/Port#[1-6]/Ch#[0-1] connected to (RDI) in a received radio (MPT-HC, MPT-
Core-E direction. Alarm is HC-HQAM,
Radio/Dir#1.[1-4,7-8]/ MPT ODU reported when an RDI is MPT-HL,
Slot#1/Port#[1-4,7-8]/ connected to received on a given radio MPT-HLC,
Ch#[0-1] CorEvo direction from the MPT-HLS,
Radio/Dir#1.[1-6]/MSS/ MPT ODU remote end of radio link. MPT-XP,
MPT-XP-HQAM)
MSS-1
Radio/Dir#1.[1-3]/Slot#1/ MPT ODU
Port#[1-3]/Ch#[0-1] connected to
MSS-O
Ch#[0-1] MPTACC
P8ETH
EASv2
Ch#[0-1] EASv2
Core-E
Radio/Dir#1.[7-8]/Slot#1/ MPT-HL
CorEvo


equipment
Remote Defect Radio/Dir#1.[5-6]/MSS/ MPT-HL Remote Defect Indication Radio alarms
Indication CORE/Port#[5-6]/Ch#1 connected to (RDI) in a received Radio (MPT-HC, MPT-
(continued) MSS-1 Direction. Alarm is HC-HQAM,
Radio/Dir#[3-8].[5-8]/ MPT-HL reported when an RDI is MPT-HL,
Slot#[3-8]/Port#[5-8]/ connected to received MPT-HLC,
Ch#[0-1] EASv2, P8ETH MPT-HLS,
on a given radio direction
Radio/Dir#1.[5-6]/ MPT-HLC, MPT-XP,
from the remote end of
MPT-XP-HQAM)
Slot#1/Port#[5-6]/Ch#[0-1] MPT-HLS radio link.
connected to
Core-E
Radio/Dir#1.[7-8]/Slot#1/ MPT-HLC,
Port#[7-8]/Ch#1 MPT-HLS
connected to
CorEvo
connected to
MSS-1
Ch#[0-1] EASv2
EleSdh-in/slot#[3-8]/ STM-1/OC-3 Remote Defect Indication Facility alarms
Port[1-2] (RDI) in a received SDH
OptSdh-in/slot#[3-8]/ Direction. Alarm is
Port[1-2] reported when an RDI is
MS/slot#[3-8]/Port1 STM-1 received on a given SDH
direction from the
remote end of SDH/OC-3
link.
Replaceable Unit Missing
r01s1/board#[8] AUX Card/SFP is missing from Equipment
r01s1/board#[1-2] Core-E, slot (Only declared, if the alarms
CorEvo card/SFP has been
r01s1/board#[5,9] FAN, A-FAN, provisioned. Card/SFP
or E-FAN could be unreachable.).


equipment
Replaceable r01s1/board#[3-8] EASv2, Card/SFP is missing from Equipment
Unit Missing MPTACC, slot (Only declared, if the alarms
(continued) P2E3DS3, card/SFP has been
P8ETH, provisioned. Card/SFP
P32E1DS1, could be unreachable.).
SDHACC
r01s1b[1-2]/daughter#[5- SFP on Core-E
6]
r01s1b[1-2]/daughter#[5- SFP on
8] CorEvo
r01s1/board#1/daughter#4 SFP on MSS-O
r01s1b1/daughter#[5-6] SFP on MSS-1
r01s1b[3-8]/daughter#[03-SFP on
04] MPTACC
r01s1b[3-8]/daughter#[05-SFP on EASv2,
08] P8ETH
r01s1b[3-8]/daughter#[01-SFP on
02] SDHACC
r01s[3-8][1-4]b1/ RPS SFP on
daughter#03 MPT ODU
connected to
MPTACC
r01s[3-8][5-8]b1/ RPS SFP on
daughter#03 MPT ODU
connected to
EASv2
MPT ODU
connected to
Core-E, MSS-1
MPT ODU
connected to
MSS-O
r01s1[1-4,7-8]b1/ RPS SFP on
daughter#03 MPT ODU
connected to
CorEvo
r01s[101-102]b[1-10]/ RPS SFP on
daughter#3 MPT-HLS


equipment
Replaceable Unit Problem
r01s1/board#[8] AUX Card failed. Equipment
r01s1/board#[1-2] Core-E, alarms
CorEvo
r01s1/board#[5,9] FAN, A-FAN
or E-FAN
r01s1/board#[3-8] EASv2,
MPTACC,
P2E3DS3,
P8ETH,
P32E1DS1,
SDHACC
connected to
Core-E, MSS-1
connected to
CorEvo
connected to
MSS-O
connected to
MPTACC
connected to
P8ETH
connected to
EASv2


equipment
Replaceable r01/subrack#[3-8][5-8] MPT-HL Card failed Equipment
unit problem connected to alarms
(continued) P8ETH
connected to
Core-E, MSS-1
connected to
CorEvo
connected to
EASv2, P8ETH
connected to
Core-E, MSS-1
connected to
CorEvo
r01/s[101-102]/board# MPT-HLS
[1-10]
r01/s[101-102]/board# MPT-HLS FAN
[11-12]
06]
08] CorEvo
r01s1b1/daughter#04 SFP on
MSS-O
04] MPTACC
08] EASV2, P8ETH
02] SDHACC


equipment
Replaceable r01s[3-8][1-4]b1/ RPS SFP on Card failed. Equipment
unit problem daughter#03 MPT ODU alarms
(continued) connected to
MPTACC
r01s[3-8][5-8]b1/ RPS SFP on
daughter#03 MPT ODU
connected to
EASV2
MPT ODU
connected to
Core-E, MSS-1
r01s1[1-4,7-8]b1/ RPS SFP on
daughter#03 MPT ODU
connected to
CorEvo
MPT ODU
connected to
MSS-O
r01s1[1-6]b1/daughter#04 RPS or XPIC
Module on
MPT ODU
connected to
Core-E, MSS-1
r01s1[1-4,7-8]b1/ RPS or XPIC
daughter#04 Module on
MPT ODU
connected to
CorEvo
r01s1[1-3]b1/daughter#04 RPS or XPIC
Module on
MPT ODU
connected to
MSS-O
r01/subrack#[3-8][5-8]/ XPIC Module
daughter#04 on MPT ODU
connected to
P8ETH


equipment
Replaceable r01s[3-8][1-4]b1/ RPS or XPIC Card failed. Equipment
unit problem daughter#04 Module on alarms
(continued) MPT ODU
connected to
MPTACC
r01s[3-8][1-4]b1/ XPIC Module
daughter#04 on MPT ODU
connected to
EASV2
r01/subrack#[3-8][5-8]/ RPS or XPIC
MPT ODU
connected to
EASV2
r01s1[5-6]b1/daughter#04 Rx Diversity
Module on
MPT-HLC
connected to
Core-E, MSS-1
r01s1[7-8]b1/daughter#04 Rx Diversity
Module on
MPT-HLC
connected to
CorEvo
r01/subrack#[3-8][5-8]/ Rx Diversity
MPT-HLC
connected to
EASv2
r01s[101-102]b[1-10]/ Rx Diversity
MPT-HLS


equipment
Replaceable Unit Type Mismatch
r01s1/board#[8] AUX Card/ODU in slot does not Equipment
r01s1/board#[1-2] Core-E, match card/ODU alarms
CorEvo configured in Core-E,
r01s1/board#[5,9] FAN, A-FAN, CorEvo, MSS-1, MSS-O
or E-FAN memory
r01s1/board#[3-8] EASv2,
MPTACC,
P2E3DS3,
P8ETH,
P32E1DS1,
SDHACC
connected to
Core-E, MSS-1
connected to
CorEvo
connected to
MSS-O
connected to
MPTACC
connected to
P8ETH
connected to
EASv2
connected to
Core-E, MSS-1
connected to
CorEvo


equipment
Replacement r01/subrack#[3-8][5-8] MPT-HL Card/ODU in slot does not Equipment
Unit Type connected to match card/ODU alarms
Mismatch EASv2, P8ETH configured in Core-E
(continued) r01/subrack#1[5-6] MPT-HLC memory
connected to
Core-E, MSS-1
connected to
CorEvo
connected to
EASV2, P8ETH
r01/s[101-102]/board# MPT-HLS
[1-10]
Retiming Buffer Overflow
E1-in/MSS/DS1/Port#[1-16] E1 on MSS-1 Retiming buffer overflow Facility alarms
E1-in/Slot#[3-8]/Port#[1- E1 on for channelized E1/
32] P32E1DS1 E1tributary.
E1-out#[1-3]-[1-7]- Channelized
[1-3]/Slot#[3-8]/Port#1 E1
RF Switch Fail
r01/subrack#1[5-6] MPT-HLC RF switch fail detected RF Switch Fail
connected to (MPT-HLC or
Core-E, MSS-1 MPT-HLS)
connected to
CorEvo
connected to
EASV2
r01s[101-102]board#[1-10] MPT-HLS
RPS Path Fail
RadioProt/Dir#[3-8][1-4] MPT ODU A communication failure RPS path fail
connected to is detected between (MPT-HC, MPT-
MPTACC MPT ODUs. Only reported MC, MPT-HL,
RadioProt/Dir#1[1-6] MPT ODU for an MPT ODUs working MPT-HLC,
connected to in 1+1 configuration with MPT-XP)
Core-E, MSS-1 Virtual Protection.
RadioProt/Dir#1[1-4,7-8] MPT ODU
connected to
CorEvo


equipment
RPS Path Fail RadioProt/Dir#1[1-2] MPT ODU Communication failure is RPS path fail
(continued) connected to detected between RPS (MPT-HC, MPT-
MSS-O coupler port between MC, MPT-HL,
RadioProt/Dir#[3-8][5-8] MPT ODU radio boards. Only MPT-HLC,
connected to reported if RPS is MPT-XP)
EASv2 provisioned.
RadioProt/Dir#[3-8][5-8] MPT-HL
connected to
EASv2, P8ETH
RadioProt/Dir#1[5-6] MPT-HLC
connected to
Core-E, MSS-1
RadioProt/Dir#1[7-8] MPT-HLC
connected to
CorEvo
RadioProt/Dir#[3-8][5-8] MPT-HLC
connected to
EASv2, P8ETH
Rx Diversity Missing
r01s1[5-6]b1/daughter#04 MPT-HLC Combiner function Rx diversity
connected to enabled but Rx Diversity missing
Core-E, MSS-1 module Missing (MPT-HLC or
r01s1[7-8]b1/daughter#04 MPT-HLC MPT-HLS)
connected to
CorEvo
r01s[3-8][5-8]b1/ MPT-HLC
EASv2, P8ETH
r01s[101-102]b[1-10]/ MPT-HLS
daughter#04
Rx Problem
RadioLAG#[1-14] MPT ODU, Reported when a loss of LAG alarms
MPT-HL, traffic occurs due to (Core-E, CorEvo,
MPT-HLC, or issues at the RX blocks or MPT-HC,
MPT-HLS to malformed packets on MPT-HL, MPT-
the L1 LAG data path. HC-HQAM,
(Not supported on L1 MPT-HLC, MPT-
LAGs configured on HLS, MPT-XP,
P8ETH.) MPT-XP-HQAM,
OC-3, MSS-1
shelf)
Secondary Battery Fail
r01/subrack#1 MSS-1/8 B battery feed failed or is Power alarms
r01s[101-102]board#[1-10] MPT-HLS missing.


equipment
Service Selective Drop
RadioLAG#[1-14]/ STM-1/OC-3 Indicates an SDH Flow is LAG alarms
SDHFlowID#[2-4080] selectively dropped due (Core-E, CorEvo,
to a reduction of Radio L1 MPT-HC,
LAG throughput. MPT-HL, MPT-
HC-HQAM,
MPT-HLC, MPT-
HLS, MPT-XP,
MPT-XP-HQAM,
OC-3, MSS-1
shelf)
Standby version mismatch
r01/subrack#1[1-6] MPT ODU Standby software version License/
connected to on MPT ODU/MPT-HL/ software
Core-E, MSS-1 MPT-HLC does not match mismatch
r01/subrack#1[1-4,7-8] MPT ODU software version on
connected to Core-E/CorEvo/MSS-1/
CorEvo MSS-O.
connected to
MSS-O
connected to
MPTACC
connected to
P8ETH
connected to
EASv2
MPT-HLC
connected to
Core-E, MSS-1
MPT-HLC
connected to
CorEvo
MPT-HLC
connected to
EASv2, P8ETH
r01s[101-102]/board#[1- MPT-HLS
10]


equipment
Synchronization Signal Fail
Sync-in/Port#1 Core-E Synchronization Signal Synchronization
Sync-in/Port#[5-6] MSS-1 Fail is reported if the alarms (Core-E,
Sync-in/Port#[5-8] CorEvo received source signal is CorEvo, MPT-HC,
not suitable as a Sync MPT-HC-HQAM,
SyncSource/ETH/ Core-E user
Source. Managed only if MPT-HL,
Slot#1/Port#[1-6] Ethernet Port
the interface has been MPT-HLC, MPT-
SyncSource/ETH/ CorEvo user configured as a primary HLS, MPT-XP,
Slot#1/Port#[1-4,7-8] Ethernet Port or secondary MPT-XP-HQAM,
SyncSource/ETH/ MSS-O user synchronization source. P32E1DS1,
Ethernet Port SDHACC)
Slot#1/Port#[1-4]
SyncSource/ETH/MSS/ MSS-1 user
CORE/Port#[1-6] Ethernet Port
SyncSource/ETH/ EASv2 user
Slot#[3-8]/Port#[1-8] Ethernet Port
Core-E
Radio/Dir#1.[1-4,7-8]/ MPT ODU
Slot#1/Port#[1-4,7-8]/ connected to
Ch#1 CorEv0
MSS-O
MSS-1
MPTACC
P8ETH
Ch#[1] EASv2


equipment
Synchronization Radio/Dir#1.[5-6]/ MPT-HL, Synchronization Signal Synchronization
signal fail Slot#1/Port#[5-6]/Ch#1 MPT-HLC, Fail is reported if the alarms (Core-E,
(continued) MPT-HLS received source signal is CorEvo, MPT-HC,
connected to not suitable as a Sync MPT-HC-HQAM,
Core-E Source. Managed only if MPT-HL,
Radio/Dir#1.[7-8]/ MPT-HL, the interface has been MPT-HLC, MPT-
MPT-HLC, configured as a primary HLS, MPT-XP,
MPT-HLS or secondary MPT-XP-HQAM,
connected to synchronization source. P32E1DS1,
CorEvo SDHACC)
Radio/Dir#1.[5-6]/MSS/ MPT-HL,
CORE/Port#[5-6]/Ch#1 MPT-HLC,
MPT-HLS
connected to
MSS-1
Radio/Dir#[3-8].[5-8]/ MPT-HL,
Slot#[3-8]/Port#[5-8]/Ch#1 MPT-HLC,
MPT-HLS
connected to
EASv2, P8ETH
EASv2
RadioLAG#[1-14] MPT ODU,
MPT-HL,
MPT-HLC,
MPT-HLS
DS1-in/Slot#[3-8]/Port#[1- DS1 on
32] P32E1DS1
DS1-in/MSS/DS1/Port#[1- DS1 on MSS-1
16]
32] P32E1DS1
Port[1-2]
Port[1-2]
MS/Slot[3-8]/Port#1 STM-1


equipment
Threshold Crossing Alarm
Hop/Dir#1[1-6]/Slot#1/ MPT ODU Threshold Crossing Alarm Threshold
Port#[1-6]/Ch#[0-1]- connected to (TCA) indicates alarm crossing alarms
PM15min Core-E threshold has been (MPT-HC, MPT-
exceeded. Applies to HC-HQAM,
Hop/Dir#1[1-6]/Slot#1/
performance monitor MPT-HL,
Port#[1-6]/Ch#[0-1]- parameters with an MPT-HLC, MPT-
PM1day accumulation period of HLS, MPT-XP,
Link/Dir#1[1-6]-PM15min 24 hours and 15 minutes. MPT-XP-HQAM,
Link/Dir#1[1-6]-PM1day P32E1DS1,
Hop/Dir#1[1-4,7-8]/ MPT ODU SDHACC, MSS-1
Slot#1/ connected to shelf)
Port#[1-4,7-8]/Ch#[0-1]- CorEvo
PM15min
Hop/Dir#1[1-4,7-8]/
Slot#1/
Port#[1-4,7-8]/Ch#[0-1]-
PM1day
Link/Dir#1[1-4,7-8]-
PM15min
Link/Dir#1[1-4,7-8]-
PM1day
Hop/Dir#1[1-3]/Slot#1/ MPT ODU
Port#[1-3]/Ch#1-PM15min connected to
Hop/Dir#1[1-3]/Slot#1/ MSS-O
Port#[1-3]/Ch#1-PM1day
Link/Dir#1[1-3]-PM15min
Link/Dir#1[1-3]-PM1day
Hop/Dir#1[1-6]/MSS/ MPT ODU
CORE/ connected to
Port#[1-6]/Ch#[0-1]- MSS-1
PM15min
Hop/Dir#1[1-6]/MSS/
CORE/
Port#[1-6]/Ch#[0-1]-
PM1day


equipment
Threshold Hop/Dir#[3-8][1-4]/ MPT ODU Threshold Crossing Alarm Threshold
Crossing Alarm Slot#[3-8]/ connected to (TCA) indicates alarm crossing alarms
(continued) Port#[1-4]/Ch#[0-1]- MPTACC threshold has been (MPT-HC, MPT-
PM15min exceeded. Applies to HC-HQAM,
Hop/Dir#[3-8][1-4]/
parameters with an MPT-HLC, MPT-
Slot#[3-8]/
accumulation period of HLS, MPT-XP,
Port#[1-4]/Ch#[0-1]- 24 hours and 15 minutes. MPT-XP-HQAM,
PM1day P32E1DS1,
Link/Dir#[3-8][1-4]- SDHACC, MSS-1
PM15min shelf)
Link/Dir#[3-8][1-4]-PM1day
Hop/Dir#[3-8][5-8]/ MPT ODU
Slot#[3-8]/ connected to
Port#[5-8]/Ch#1-PM15min P8ETH
Hop/Dir#[3-8][5-8]/
Slot#[3-8]/
Port#[5-8]/Ch#1-PM15min EASv2
Hop/Dir#[3-8][5-8]/
Slot#[3-8]/
Link/Dir#[3-8][5-8]-
PM15min


equipment
Threshold Hop/Dir#[3-8][1-4]/ MPT ODU Threshold Crossing Alarm Threshold
(continued) Port#[1-4]/Ch#[0-1]- EASv2 threshold has been (MPT-HC, MPT-
Hop/Dir#[3-8][1-4]/
Slot#[3-8]/
PM1day P32E1DS1,
Hop/Dir#[3-8][5-8]/ MPT-HL SDHACC, MSS-1
Slot#[3-8]/ connected to shelf)
Port#[5-8]/Ch#[0-1]- EASv2, P8ETH
PM15min
Hop/Dir#[3-8][5-8]/
Slot#[3-8]/
Port#[5-8]/Ch#[0-1]-
PM1day
Link/Dir#[3-8][5-8]-
PM15min
Hop/Dir#1[5-6]/Slot#1/ MPT-HL
Hop/Dir#1[5-6]/Slot#1/ Core-E
Hop/Dir#1[7-8]/Slot#1/ MPT-HL
CorEvo
Hop/Dir#1[5-6]/MSS/ MPT-HL
CORE/ connected to
Port#[5-6]/Ch#1-PM15min MSS-1
Hop/Dir#1[5-6]/MSS/
CORE/


equipment
Threshold Hop/Dir#1[5-6]/Slot#1/ MPT-HLC, Threshold Crossing Alarm Threshold
Crossing Alarm Port#[5-6]/Ch#1-PM15min MPT-HLS (TCA) indicates alarm crossing alarms
(continued) connected to threshold has been (MPT-HC, MPT-
Core-E exceeded. Applies to HC-HQAM,
Port#[5-6]/Ch#1-PM1day performance monitor MPT-HL,
Link/Dir#1[5-6]/Slot#1/ parameters with an MPT-HLC, MPT-
Port#[5-6]/Ch#1-PM15min accumulation period of HLS, MPT-XP,
Link/Dir#1[5-6]/Slot#1/ 24 hours and 15 minutes. MPT-XP-HQAM,
P32E1DS1,
SDHACC, MSS-1
Hop/Dir#1[7-8]/Slot#1/ MPT-HLC or shelf)
Port#[7-8]/Ch#1-PM15min MPT-HLS
connected to
CorEvo
Link/Dir#1[7-8]/Slot#1/
Port#[7-8]/Ch#1-PM15min
Hop/Dir#1[5-6]/MSS/ MPT-HLC or
CORE/ MPT-HLS
MSS-1
Hop/Dir#1[5-6]/MSS/
CORE/
Port#[5-6]/Ch#1-PM1dayer
Hop/Dir#[3-8][5-8]/ MPT-HLC
PM15min
Hop/Dir#[3-8][5-8]/
Slot#[3-8]/
Port#[5-8]/Ch#[0-1]-
PM1day
Link/Dir#[3-8][5-8]-
PM15min


equipment
Threshold Hop/Dir#[3-8][5-8]/ MPT-HLS Threshold Crossing Alarm Threshold
(continued) Port#[5-8]/Ch#[0-1]- EASv2 threshold has been (MPT-HC, MPT-
Hop/Dir#[3-8][5-8]/
Slot#[3-8]/
PM1day P32E1DS1,
PM15min shelf)
DS1-in/Slot#[3-8]/ DS1 on
Port#[1-32]-PM15min P32E1DS1
DS1-in/Slot#[3-8]/
Port#[1-32]-PM1day
DS1-out/Slot#[3-8]/
Port#[1-32]-PM15min
DS1-out/Slot#[3-8]/
Port#[1-32]-PM1day
E1-in/Slot#[3-8]/ E1 on
E1-in/Slot#[3-8]/
Port#[1-32]-PM1day
E1-out/Slot#[3-8]/
Port#[1-32]-PM15min
E1-out/Slot#[3-8]/
Port#[1-32]-PM1day
DS1-in/MSS/DS1/ DS1 on MSS-1
Port#[1-16]-PM15min shelf
DS1-in/MSS/DS1/
Port#[1-16]-PM1day
DS1-out/MSS/DS1/
Port#[1-16]-PM15min
DS1-out/MSS/DS1/
Port#[1-16]-PM1day


equipment
Threshold E1-in/MSS/E1/ E1 on MSS-1 Threshold Crossing Alarm Threshold
Crossing Alarm Port#[1-16]-PM15min shelf (TCA) indicates alarm crossing alarms
(continued) threshold has been (MPT-HC, MPT-
E1-in/MSS/E1/
exceeded. Applies to HC-HQAM,
Port#[1-16]-PM1day performance monitor MPT-HL,
E1-out/MSS/E1/ parameters with an MPT-HLC, MPT-
Port#[1-16]-PM15min accumulation period of HLS, MPT-XP,
E1-out/MSS/E1/ 24 hours and 15 minutes. MPT-XP-HQAM,
P32E1DS1,
Port#[1-16]-PM1day
SDHACC, MSS-1
EleSdh-in/Slot#[3-8]/ STM-1/OC-3 shelf)
Port#[1-2]-PM15min
EleSdh-in/Slot#[3-8]/
Port#[1-2]-PM1day
EleSdh-out/Slot#[3-8]/
Port#[1-2]-PM15min
Port#[1-2]-PM1day
OptSdh-in/Slot#[3-8]/
Port#[1-2]-PM15min
Port#[1-2]-PM1day
OptSdh-out/Slot#[3-8]/
Port#[1-2]-PM15min
Port#[1-2]-PM1day
Trace Identifier Mismatch
EleSdh-in/slot#[3-8]/ STM-1/OC-3 Trace Identifier Mismatch Facility alarms
Port[1-2] condition indicates there
OptSdh-in/slot#[3-8]/ is a J0 Trace Mismatch
Port[1-2] detected in the incoming
MS/Slot[3-8]/Port#1 STM-1 signal from the
demarcation panel.


equipment
Traffic Down
MPT-HL, traffic occurs and the L1 (Core-E, CorEvo,
MPT-HLC, or LAG data path is MPT-HC,
MPT-HLS unavailable. (Not MPT-HL, MPT-
supported on L1 LAGs HC-HQAM,
configured on P8ETH.) MPT-HLC, MPT-
HLS, MPT-XP,
MPT-XP-HQAM,
OC-3, MSS-1
shelf)
Traffic Loss
RadioLAG#[1-14] MPT ODU, Reported when packet LAG alarms
MPT-HL, loss occurs due to an (Core-E, CorEvo,
MPT-HLC, or extreme latency MPT-HC,
MPT-HLS difference over L1 LAG MPT-HL, MPT-
members or when errors HC-HQAM,
occurs on the L1 LAG data MPT-HLC, MPT-
path. (Not supported on HLS, MPT-XP,
L1 LAGs configured on MPT-XP-HQAM,
P8ETH.) OC-3, MSS-1
shelf)
Tx Problem
MPT-HL, traffic occurs due to (Core-E, CorEvo,
MPT-HLC, or issues at the TX blocks or MPT-HC,
MPT-HLS to malformed packets on MPT-HL, MPT-
the L1 LAG data path. HC-HQAM,
(Not supported on L1 MPT-HLC, MPT-
LAGs configured on HLS, MPT-XP,
P8ETH.) MPT-XP-HQAM,
OC-3, MSS-1
shelf)


equipment
Unavailable Time
Hop/Dir#1[1-6]/Slot#1/ MPT ODU A period of unavailable Threshold
Port#[1-6]/Ch#[0-1]- connected to time begins when 10 crossing alarms
PM15min Core-E consecutive SES events (MPT-HC, MPT-
are detected. Alarms are HC-HQAM,
associated with the MPT-HL,
Port#[1-6]/Ch#[0-1]- performance monitoring MPT-HLC, MPT-
PM1day port. HLS, MPT-XP,
Link/Dir#1[1-6]-PM15min MPT-XP-HQAM,
Link/Dir#1[1-6]-PM1day P32E1DS1,
Hop/Dir#1[1-4,7-8]/ MPT ODU SDHACC, MSS-1
Slot#1/ connected to shelf)
Port#[1-4,7-8]/Ch#[0-1]- CorEvo
PM15min
Hop/Dir#1[1-4,7-8]/
Slot#1/
Port#[1-4,7-8]/Ch#[0-1]-
PM1day
Link/Dir#1[1-4,7-8]-
PM15min
Link/Dir#1[1-4,7-8]-
PM1day
Hop/Dir#1[1-3]/Slot#1/ MPT ODU
Hop/Dir#1[1-3]/Slot#1/ MSS-O
Hop/Dir#1[1-6]/MSS/ MPT ODU
CORE/ connected to
Port#[1-6]/Ch#[0-1]- MSS-1
PM15min
Hop/Dir#1[1-6]/MSS/
CORE/
Port#[1-6]/Ch#[0-1]-
PM1day


equipment
Unavailable Hop/Dir#[3-8][1-4]/ MPT ODU A period of unavailable Threshold
Time Slot#[3-8]/ connected to time begins when 10 crossing alarms
(continued) Port#[1-4]/Ch#[0-1]- MPTACC consecutive SES events (MPT-HC, MPT-
PM15min are detected. Alarms are HC-HQAM,
associated with the MPT-HL,
Hop/Dir#[3-8][1-4]/
performance monitoring MPT-HLC, MPT-
Slot#[3-8]/
port. HLS, MPT-XP,
Port#[1-4]/Ch#[0-1]- MPT-XP-HQAM,
PM1day P32E1DS1,
PM15min shelf)
Hop/Dir#[3-8][5-8]/
Slot#[3-8]/
Hop/Dir#[3-8][1-4]/
Slot#[3-8]/
Hop/Dir#[3-8][5-8]/
Slot#[3-8]/
Link/Dir#[3-8][5-8]-
PM15min


equipment
Unavailable Hop/Dir#1[5-6]/Slot#1/ MPT-HL A period of unavailable Threshold
Time Port#[5-6]/Ch#1-PM15min connected to time begins when 10 crossing alarms
(continued) Core-E consecutive SES events (MPT-HC, MPT-
Port#[5-6]/Ch#1-PM1day associated with the MPT-HL,
Hop/Dir#1[7-8]/Slot#1/ MPT-HL performance monitoring MPT-HLC, MPT-
Port#[7-8]/Ch#1-PM15min connected to port. HLS, MPT-XP,
Hop/Dir#1[7-8]/Slot#1/ CorEvo MPT-XP-HQAM,
P32E1DS1,
SDHACC, MSS-1
Hop/Dir#1[5-6]/MSS/ MPT-HL shelf)
CORE/ connected to
Hop/Dir#1[5-6]/MSS/
CORE/
Hop/Dir#[3-8][5-8]/ MPT-HL
PM15min
Hop/Dir#[3-8][5-8]/
Slot#[3-8]/
Port#[5-8]/Ch#[0-1]-
PM1day
Link/Dir#[3-8][5-8]-
PM15min
Hop/Dir#1[7-8]/Slot#1/ MPT-HLC or
connected to
Core-E
Link/Dir#1[7-8]PM15min
Link/Dir#1[7-8]PM1day
Hop/Dir#1[7-8]/Slot#1/ MPT-HLC or
connected to
CorEvo


equipment
Unavailable Hop/Dir#1[5-6]/MSS/ MPT-HLC or Threshold Crossing Alarm Threshold
Time CORE/ MPT-HLS (TCA) indicates alarm crossing alarms
(continued) Port#[5-6]/Ch#1-PM15min connected to threshold has been (MPT-HC, MPT-
MSS-1 exceeded. Applies to HC-HQAM,
Hop/Dir#1[5-6]/MSS/
CORE/
Port#[5-6]/Ch#1-PM1day accumulation period of HLS, MPT-XP,
Link/Dir#1[5-6]PM15min 24 hours and 15 minutes. MPT-XP-HQAM,
Link/Dir#1[5-6]PM1day P32E1DS1,
Hop/Dir#[3-8][5-8]/ MPT-HLC SDHACC, MSS-1
Slot#[3-8]/ connected to shelf)
PM15min
Hop/Dir#[3-8][5-8]/
Slot#[3-8]/ Port#[5-8]/
Ch#[0-1]-PM1day
Link/Dir#[3-8][5-8]-
PM15min
Hop/Dir#[3-8][5-8]/ MPT-HLS
Port#[5-8]/Ch#[0-1]- EASv2,
PM15min
Hop/Dir#[3-8][5-8]/
Slot#[3-8]/ Port#[5-8]/
Ch#[0-1]-PM1day
Link/Dir#[3-8][5-8]-
PM15min
DS1-in/Slot#[3-8]/ DS1 on
DS1-in/Slot#[3-8]/
Port#[1-32]-PM1day
DS1-out/Slot#[3-8]/
Port#[1-32]-PM15min
DS1-out/Slot#[3-8]/
Port#[1-32]-PM1day


equipment
Unavailable DS1-in/MSS/DS1/ DS1 on MSS-1 A period of unavailable Threshold
Time Port#[1-16]-PM15min shelf time begins when 10 crossing alarms
(continued) consecutive SES events (MPT-HC, MPT-
DS1-in/MSS/DS1/
Port#[1-16]-PM1day associated with the MPT-HL,
DS1-out/MSS/DS1/ performance monitoring MPT-HLC, MPT-
Port#[1-16]-PM15min port. HLS, MPT-XP,
DS1-out/MSS/E1/ MPT-XP-HQAM,
P32E1DS1,
Port#[1-16]-PM1day
SDHACC, MSS-1
E1-in/Slot#[3-8]/ E1 on shelf)
E1-in/Slot#[3-8]/
Port#[1-32]-PM1day
E1-out/Slot#[3-8]/
Port#[1-32]-PM15min
E1-out/Slot#[3-8]/
Port#[1-32]-PM1day
E1-in/MSS/E1/ E1 on MSS-1
Port#[1-16]-PM15min shelf
E1-in/MSS/E1/
Port#[1-16]-PM1day
E1-out/MSS/E1/
Port#[1-16]-PM15min
E1-out/MSS/E1/
Port#[1-16]-PM1day


equipment
Unavailable EleSdh-in/Slot#[3-8]/ STM-1/OC-3 A period of unavailable Threshold
Time Port#[1-2]-PM15min time begins when 10 crossing alarms
(continued) consecutive SES events (MPT-HC, MPT-
Port#[1-2]-PM1day associated with the MPT-HL,
EleSdh-out/Slot#[3-8]/ performance monitoring MPT-HLC, MPT-
Port#[1-2]-PM15min port. HLS, MPT-XP,
EleSdh-out/Slot#[3-8]/ MPT-XP-HQAM,
P32E1DS1,
Port#[1-2]-PM1day
SDHACC, MSS-1
OptSdh-in/Slot#[3-8]/ shelf)
Port#[1-2]-PM15min
Port#[1-2]-PM1day
Port#[1-2]-PM15min
Port#[1-2]-PM1day


equipment
Unconfigured Equipment Present
r01s1/board#[8] AUX Card in MSS shelf slot 2 Equipment
r01s1/board#[2] Core-E, through 8 is not alarms
CorEvo provisioned (enabled) but
r01s1/board#[5,9] FAN, E-FAN, is present in slot.
or A-FAN SFP is not provisioned
(enabled) but is present
in card.
r01s1/board#[3-8] EASV2,
MPTACC,
P2E3DS3,
P8ETH,
P32E1DS1,
SDHACC
06]
08] CorEvo
r01s1b1/daughter#04 SFP on
MS-O
04] MPTACC
r01s1b[3-8]/daughter#[05- SFP on EASv2,
08] P8ETH
02] SDHACC
Underlying Resource Unavailable
EleSdh-in/slot#[3-8]/ OC-3/ STM-1 Underlying Resource Equipment
Port[1-2] Unavailable on OC-3/ alarms
OptSdh-in/slot#[3-8]/ STM-1 Interface -
Port[1-2] transmission resources
affected by equipment
failure. - Alarm URU
These alarms are
reported by the MIB for
the 1350 OMS and are not
reported by the alarm
manager.
E1-in#[1-3]-[1-7]-[1-3]/ Channelized Underlying Resource
Slot#[3-8]/Port#1 E1 port Unavailable on E1
E1-in/Slot#[3-8]/Port#[1- E1 on Interface - transmission
32] P32E1DS1 resources affected by
E1-in/MSS/E1/Port#[1-16] E1 on MSS-1 equipment failure. -
Alarm URU


equipment
Underlying Eth/Slot#1/Port#[1-6] User Ethernet Underlying Resource Equipment
Resource port on Unavailable on Ethernet alarms
Unavailable Core-E Interface - transmission
(continued) Eth/Slot#1/Port#[1-8] User Ethernet resources affected by
port on equipment failure. -
CorEvo Alarm URU
Eth/Slot#1/Port#[1-4] User Ethernet
port on MSS-O
Eth/MSS/CORE/Port#[1-6] User Ethernet
port on MSS-1
Eth/Slot#[3-8]/Port#[1-8] User Ethernet
port on EASv2
r01s1b[1-2]/daughter#[05- SFP User
06] Ethernet port
on Core-E,
MSS-1
08] Ethernet port
on CorEvo
r01s1b[1-2]/daughter#04 SFP User
Ethernet port
on MSS-O
08] Ethernet port
on EASv2
Radio/Dir#1.[1-6]/ MPT ODU Underlying Resource Equipment
Slot#1/Port#[1-6]/Ch#[0-1] connected to Unavailable on Radio alarms
Core-E Interface - transmission
Radio/Dir#1.[1-4,7-8]/ MPT ODU resources affected by
Slot#1/Port#[1-4,7-8]/ connected to equipment failure -
Ch#[0-1] CorEvo Alarm URU
Radio/Dir#1.[1-6]MSS/ MPT ODU
CORE/ connected to
Port#[1-6]/Ch#[0-1] MSS-1
MSS-O
Ch#[0-1] MPTACC
P8ETH


equipment
Underlying Radio/Dir#[3-8].[1-4]/ MPT ODU Underlying Resource Equipment
Resource Slot#[3-8]/Port#[1-4]/Ch#1 connected to Unavailable on Radio alarms
Unavailable EASv2 Interface - transmission
(continued) Radio/Dir#[3-8].[5-8]/ MPT ODU resources affected by
Slot#[3-8]/Port#[5-8]/ connected to equipment failure -
Ch#[0-1] EASv2 Alarm URU
connected to
Core-E
connected to
CorEvo
MSS/CORE/Port#[5-6]/ MPT-HLS
MSS-1
Ch#[0-1] EASv2
Underlying Resource Unavailable Service
E1-in#[1-3]-[1-7]-[1-3]/ Channelized Underlying Resource Equipment
Slot#[3-8]/Port#1 E1 port Unavailable Service on E1 alarms
E1-in/Slot#[3-8]/Port#[1- E1 on Interface - transmission
32] P32E1DS1 resources affected by
E1-in/MSS/E1/Port#[1-16] E1 on MSS-1 equipment failure -
Alarm URUS


equipment
Underlying Radio/Dir#1.[1-6]/ MPT ODU Underlying Resource Equipment
Resource Slot#1/Port#[1-6]/Ch#[0-1] connected to Unavailable Service on alarms
Unavailable Core-E Radio Interface -
Service Radio/Dir#1.[1-4,7-8]/ MPT ODU transmission resources
(continued) connected to affected by equipment
Slot#1/Port#[1-4,7-8]/
CorEvo failure - Alarm URUS
Ch#[0-1]
Radio/Dir#1.[1-6]MSS/ MPT ODU
CORE/ connected to
Port#[1-6]/Ch#[0-1] MSS-1
MSS-O
Ch#[0-1] MPTACC
P8ETH
EASv2
Ch#[0-1] EASv2
connected to
Core-E
connected to
CorEVO
MSS/CORE/Port#[5-6]/ MPT-HLS
MSS-1
Ch#[0-1] EASv2


equipment
Version Mismatch
r01s1/board#[1-2] Core-E, Software version on License/
CorEvo Core-E, CorEvo, MSS-1, software
r01s1/board#1 MSS-O MSS-O, MPT ODU, mismatch
r01s1/MSS/CORE MSS-1 MPT-HL, MPT-HLC, or
MPT-HLS does not match
software version on
connected to
Core-E, CorEvo, MSS-1, or
Core-E, MSS-1
MSS-O.
connected to
CorEvo
connected to
MSS-O
connected to
EASv2
connected to
MPTACC
connected to
P8ETH
MPT-HLC
connected to
Core-E, MSS-1
MPT-HLC
connected to
CorEvo
MPT-HLC
connected to
EASv2, P8ETH
r01/s[101-102]/board#[1- MPT-HLS
10]
1. For MSS-1 applications, In the very specific case where it happens simultaneously
that: a) The negative polarity is connected to ground. b) The voltage value of the line
corresponding to the fuse opened is lower than the value of the voltage line in service,
the battery failure and secondary battery failure alarm may not be properly reported
by JUSM and Alarm Monitor.

Table 6.4 — Abnormal condition
Operation Name Type Description See

(equipment)
Core facing PDH loopback
DS1 Port#[1-16] Internal Loopback The associated entity has a Abnormal

(DS1/E1 on core facing PDH loopback conditions
E1 Port#[1-16] Internal activated at the near end.
MSS-1)
DS1 Port#[1-32] Internal Loopback

(DS1/E1 on
E1 Port#[1-32] Internal
P32E1DS1)
(DS3 on
P2E3DS3)
Core facing SDH loopback
STM-1 Port#[1-2] Internal Loopback The associated entity has a Abnormal

(STM-1/OC-3 core facing SDH (STM-1/ conditions
OC3 Port#[1-2] Internal OC3) loopback activated at
on SDHACC)]
the near end.
Digital core facing loopback
Direction #1.[1-6] Loopback The associated entity has a Abnormal

(MPT ODU loopback activated at the conditions
connected to near end.
Core-E, MSS-1)
Direction #1.[1-4,7-8] Loopback

(MPT ODU
connected to
CorEvo)
Direction #1.[1-3] Loopback

(MPT ODU
connected to
MSS-O)
Direction #[3-8].[1-4] Loopback

(MPT ODU
connected to
MPTACC)

(MPT ODU
connected to
P8ETH)

Table 6.4 — Abnormal condition (Continued)

(equipment)
Digital core Direction #[3-8].[1-8] Loopback The associated entity has a Abnormal
facing loopback (MPT ODU loopback activated at the conditions
(continued) connected to near end.
EASv2)
(MPT-HL, MPT-
HLC, or MPT-
HLS connected
to Core-E,
MSS-1)

(MPT-HL, MPT-
HLC, or MPT-
HLS connected
to CorEvo)

(MPT-HL or
MPT-HLC
connected to
EASv2, P8ETH)

(MPT-HLS
connected to
EASv2)


(equipment)
Forced adaptive modulation

Direction #1.[1-6] - Radio Manual Adaptive Abnormal
Channel #1 (MPT ODU Modulation command has conditions
connected to been executed.
Core-E, MSS-1)
Direction #1.[1-4,7-8] - Radio

Channel #1 (MPT ODU
connected to
CorEvo)
Direction #1.[1-3] Radio

(MPT ODU
connected to
MSS-O)
Direction #[3-8].[1-4] - Radio

Channel #1 (MPT ODU
connected to
MPTACC)

Channel #1 (MPT ODU
connected to
P8ETH)

Channel #1 (MPT ODU
connected to
EASv2)
Direction #1.[5-6] - Radio

Channel #1 (MPT-HL, MPT-
HLC, or MPT-
HLS connected
to Core-E,
MSS-1)

Channel #1 (MPT-HL, MPT-
HLC, or MPT-
HLS connected
to CorEvo)


(equipment)
Forced adaptive Direction #[3-8].[5-8] - Radio Manual Adaptive Abnormal

modulation Channel #1 (MPT-HL or Modulation command has conditions
(continued) MPT-HLC been executed.
connected to
EASv2, P8ETH)

Channel #1 (MPT-HLS
connected to
EASv2)
Forced Switch - EPS
Main#1 Slot#1 Equipment A Forced Equipment Abnormal

Protection Protection Switch (EPS) has conditions
(Core-E, been executed for the
CorEvo) protection group.
Main#1 Slot#[3,5,7] Equipment

Protection
(P2E3DS3,
P32E1DS1,
SDHACC)
Main#1 Slot #[3-8] Equipment

Port #[1-4] Protection
(MPT ODU
connected to
MPTACC)
Main#1 Slot #1 Equipment

Port #[1,3,5] Protection
(MPT ODU
connected to
Core-E)

(MPT ODU
connected to
CorEvo)
Main#1 MSS/CORE Equipment

(MPT ODU
connected to
MSS-1)


(equipment)
Forced switch - Main#1 Slot #1 Equipment A Forced Equipment Abnormal

EPS (continued) Port #1 Protection Protection Switch (EPS) has conditions
(MPT ODU been executed for the
connected to protection group.
MSS-O)
Main#1 Slot #[3,5,7] Equipment
(MPT ODU
connected to
EASv2)

(MPT-HL or
MPT-HLC
connected to
EASV2, P8ETH)

Port #5 Protection
(MPT-HLC
connected to
Core-E)

Port #7 Protection
(MPT-HLC
connected to
CorEvo)
Main#1 MSS/CORE Equipment
Port #5 Protection
(MPT-HLC or
MPT-HLS
connected to
MSS-1)

(MPT-HLS
connected to
EASv2)


(equipment)
Forced switch - Main#1 Slot #1 Rx Radio A Forced Rx Protection Abnormal

RPS Port #[1,3,5] Protection Switch (RPS) has been conditions
(MPT ODU executed for the protection
connected to group.
Core-E)
Main#1 Slot #1 Rx Radio
(MPT ODU
connected to
CorEvo)
Main#1 MSS/CORE Rx Radio

(MPT ODU
connected to
MSS-1)

Port #1 Protection
(MPT ODU
connected to
MSS-O)
Main#1 Slot #[3-8] Rx Radio

(MPT ODU
connected to
MPTACC)
Main#1 Slot #[3,5,7] Rx Radio

(MPT ODU
connected to
EASv2)


(equipment)
Forced switch - Main#1 Slot #1 Rx Radio A Forced Rx Protection Abnormal

RPS (continued) Port #5 Protection Switch (RPS) has been conditions
(MPT-HLC or executed for the protection
MPT-HLS group.
connected to
Core-E)
Main#1 Slot #1 Port #7 Rx Radio
Protection
(MPT-HLC or
MPT-HLS
connected to
CorEvo)
Main#1 MSS/CORE Rx Radio

Port #5 Protection
(MPT-HLC or
MPT-HLS
connected to
MSS-1)

(MPT-HL or
MPT-HLC
connected to
EASv2, P8ETH)

(MPT-HLS
connected to
EASv2)


(equipment)
Forced switch - Main#1 Slot #[3-8] HSB Protection A Forced Tx Protection Abnormal
TPS Port #[1-4] (MPT ODU Switch (TPS) has been conditions
connected to executed for the protection
MPTACC) group.
Main#1 Slot #1 HSB Protection
Port #[1,3,5] (MPT ODU
connected to
Core-E)

connected to
CorEvo)
Main#1 MSS/CORE HSB Protection

connected to
MSS-1)

Port #1 Protection
(MPT ODU
connected to
MSS-O)
Main#1 Slot #[3,5,7] HSB Protection
Port #[5-8] (MPT ODU
connected to
EASv2)

Port #5 (MPT-HLC or
MPT-HLS
connected to
Core-E)

Port #7 (MPT-HLC or
MPT-HLS
connected to
CorEvo)


(equipment)
Forced switch - Main#1 MSS/CORE HSB Protection A Forced Tx Protection Abnormal

TPS (continued) Port #5 (MPT-HLC or Switch (TPS) has been conditions
MPT-HLS executed for the protection
connected to group.
MSS-1)
Port #[5-8] (MPT-HL or
MPT-HLC
connected to
EASv2, P8ETH)

Port #[5-8] (MPT-HLS
connected to
EASv2)
Line facing circuit loopback
Direction #1.[1-6] Loopback The associated entity has a Abnormal

(MPT ODU loopback activated at the conditions
connected to near end.
Core-E, MSS-1)
(MPT ODU
connected to
CorEvo)

(MPT ODU
connected to
MSS-O)

(MPT ODU
connected to
MPTACC)

(MPT ODU
connected to
P8ETH)

(MPT ODU
connected to
EASv2)


(equipment)
Line facing Direction #1.[5-6] Loopback The associated entity has a Abnormal
circuit loopback (MPT-HL, MPT- loopback activated at the conditions
(continued) HLC, or MPT- near end.
HLS connected
to Core-E,
MSS-1)
(MPT-HL, MPT-
HLC, or MPT-
HLS connected
to CorEvo)

(MPT-HL or
MPT-HLC
connected to
EASv2, P8ETH)

(MPT-HLS
connected to
EASv2)
Line facing PDH loopback
DS1 Port#[1-16] External Loopback The associated entity has a Abnormal

(DS1/E1 on line facing PDH (DS1, DS3, conditions
E1 Port#[1-16] External or E1) loopback activated at
MSS-1)
the near end.
DS1 Port#[1-32] External Loopback
(DS1/E1 on
E1 Port#[1-32] External
P32E1DS1)

(DS3 on
P2E3DS3)
Line facing SDH loopback
STM-1 Port#[1-2] External Loopback The associated entity has a Abnormal

(STM-1/OC-3 line facing SDH loopback conditions
OC-3 Port#[1-2] External activated at the near end.
on SDHACC)


(equipment)
Lockout switch - EPS

Spare#0 Slot#2 Equipment A Lockout Equipment Abnormal
Protection Protection Switch (EPS) has conditions
(Core-E, been executed for the
CorEvo) protection group.
Spare#0 Slot#[4,6,8] Equipment

Protection
(P2E3DS3,
P32E1DS1,
SDHACC)
Spare#0 Slot #1 Equipment

(MPT ODU
connected to
Core-E)

(MPT ODU
connected to
CorEvo)
Spare#0 MSS/CORE Equipment
(MPT ODU
connected to
MSS-1)

Port #2 Protection
(MPT ODU
connected to
MSS-O)
Spare#0 Slot#[3-8] Equipment

(MPT ODU
connected to
MPTACC)

(MPT ODU
connected to
EASv2)


(equipment)
Lockout switch - Spare#0 Slot #1 Port #6 Equipment A Lockout Equipment Abnormal

EPS (continued) Protection Protection Switch (EPS) has conditions
(MPT-HLC or been executed for the
MPT-HLS protection group.
connected to
Core-E)
Port #8 Protection
(MPT-HLC or
MPT-HLS
connected to
CorEvo)
Spare#0 MSS/CORE Equipment

Port #6 Protection
(MPT-HLC or
MPT-HLS
connected to
MSS-1)

(MPT-HL or
MPT-HLC
connected to
EASv2, P8ETH)

(MPT-HLS
connected to
EASv2)


(equipment)
Lockout switch - Spare#0 Slot #1 Port #[2,4,6] Rx Radio A Lockout Rx Protection Abnormal
RPS Protection Switch (RPS) has been conditions
(MPT ODU executed for the protection
connected to group.
Core-E)
Spare#0 Slot #1 Port #[2,4,8] Rx Radio
Protection
(MPT ODU
connected to
CorEvo)
Spare#0 MSS/CORE Rx Radio

(MPT ODU
connected to
MSS-1)
Spare#0 Slot #1 Port #2 Rx Radio

Protection
(MPT ODU
connected to
MSS-O)
Spare#0 Slot#[3-8]Port #[1-4] Rx Radio

Protection
(MPT ODU
connected to
MPTACC)
Spare#0 Slot#[4,6,8] Rx Radio

(MPT ODU
connected to
EASv2)
Spare#0 Slot #1 Rx Radio

Port #6 Protection
(MPT-HLC,
MPT-HLS
connected to
Core-E)


(equipment)
Lockout switch - Spare#0 Slot #1 Rx Radio A Lockout Rx Protection Abnormal

RPS (continued) Port #8 Protection Switch (RPS) has been conditions
(MPT-HLC, executed for the protection
MPT-HLS group.
connected to
CorEvo)
Spare#0 MSS/CORE Rx Radio
Port #6 Protection
(MPT-HLC,
MPT-HLS
connected to
MSS-1)

(MPT-HL or
MPT-HLC
connected to
EASv2, P8ETH)

(MPT-HLS
connected to
EASv2)


(equipment)
Lockout switch Spare#0 Slot #1 HSB Protection A Lockout Tx Protection Abnormal

(continued) Port #[2,4,6] (MPT ODU Switch (TPS) has been conditions
connected to executed for the protection
Core-E) group.
Spare#0 Slot #1 HSB Protection
connected to
CorEvo)
Spare#0 MSS/CORE HSB Protection

connected to
MSS-1)
Spare#0 Slot#[3-8] HSB Protection

connected to
MPTACC)
Spare#0 Slot#[4,6,8] HSB Protection

connected to
EASv2)
Spare#0 Slot #1 Port #6 HSB Protection
(MPT-HLC,
MPT-HLS
connected to
Core-E)

(MPT-HLC
MPT-HLS
connected to
CorEvo)
Spare#0 MSS/CORE Port #6 HSB Protection

(MPT-HLC or
MPT-HLS
connected to
MSS-1)


(equipment)
Lockout switch - Spare#0 Slot#[4,6,8] HSB Protection A Lockout Tx Protection Abnormal

TPS (continued) Port #[5-8] (MPT-HL or Switch (TPS) has been conditions
MPT-HLC executed for the protection
connected to group.
EASv2, P8ETH)
Spare#0 Slot#[4,6,8] HSB Protection

Port #[5-8] (MPT-HLS
connected to
EASv2)
Rx main squelch
Direction #1.[5-6] - Radio Main receiver has been Abnormal

Channel #[0-1] (MPT-HLC or squelched. conditions
MPT-HLS
connected to
Core-E, MSS-1)

Channel #[0-1] (MPT-HLC or
MPT-HLS
connected to
CorEvo)

Channel #[0-1] (MPT-HLC
connected to
EASv2, P8ETH)

Channel #[0-1] (MPT-HLS
connected to
EASv2)


(equipment)
Rx Div squelch
Direction #1.[5-6] - Radio Diversity receiver has been Abnormal
Channel #[0-1] (MPT-HLC or squelched. conditions
MPT-HLS
connected to
Core-E, MSS-1)

MPT-HLS
connected to
CorEvo)

connected to
EASv2, P8ETH)

connected to
EASv2)


(equipment)
Tx Mute
Direction #1.[1-6] - Radio Manual or automatic mute Abnormal
Channel #[0-1] (MPT ODU command has been conditions
connected to executed.
Core-E, MSS-1)
Direction #1.[1-4,7-8] - Radio

Channel #[0-1] (MPT ODU
connected to
CorEvo)

connected to
MSS-O)

connected to
MPTACC

Channel #1 (MPT ODU
connected to
P8ETH

Channel #1 (MPT ODU
connected to
EASv2


(equipment)
Tx mute Direction #[3-8].[5-8] - Radio Manual or automatic mute Abnormal

(continued) Channel #[0-1] (MPT ODU command has been conditions
connected to executed.
EASv2
Direction #1.[5-6] - Radio (MPT-HL
Channel #1 connected to
Core-E, MSS-1)
Direction #1.[7-8] - Radio (MPT-HL

Channel #1 connected to
CorEvo)
Direction #[3-8].[5-8] - Radio (MPT-HL

Channel #[0-1] connected to
EASv2, P8ETH)

MPT-HLS
connected to
Core-E, MSS-1)

MPT-HLS
connected to
CorEvo)

connected to
EASv2, P8ETH)

connected to
EASv2)

Table 6.5 — Core-E Card LED indications
LED Indication Probable cause Corrective action
Status OFF Card Not Provisioned Provision card
Not Powered Verify MSS-4/8 shelf fuse is not blown or

missing.
Verify Power cable(s) are properly
terminated at both ends.
Verify voltage level at the power
distribution panel.
Not Equipped Verify that the card is properly installed.
Green Configuration Downloading, SW Wait for configuration download or

Blinking Booting, or flash card realignment. software boot to complete.
Green Card Properly Equipped and Normal Operating condition. No Action

Provisioned. currently In-Service/ required.
Active.
Yellow Card Properly Equipped and Normal operating condition for Standby
Provisioned as EPS. Currently in card.
Standby. No Action required.
Red Card Fail Replace card
Red Blinking Card Mismatch Check alarms for replaceable unit type
mismatch, see
Equipment alarms.
Major Red At least one alarm with Critical or Retrieve alarms using the alarm
Alarm Major severity present in the NE. monitor, see Table 6.3, and
troubleshoot accordingly.
Minor Red At least one alarm with Minor severity Retrieve alarms using the alarm
Alarm present in the NE. monitor, see Table 6.3, and
Warning Yellow At least one alarm with Warning Retrieve alarms using the alarm
severity present in the NE. monitor, see Table 6.3, and
Abnormal Yellow At least one abnormal condition Retrieve abnormal condition using JSUM,
present in the NE. see Table 6.4, and troubleshoot
accordingly.

Table 6.6 — CorEvo Card LED indications

missing.
Verify Power cable(s) are properly t
distribution panel.
Not Equipped Verify that the card is properly installed.


Active.
Yellow Card Properly Equipped and Normal operating condition for Standby
Provisioned as EPS. Currently in card.
Card Mismatch Check alarms for replaceable unit type

mismatch, see Equipment alarms.
Alarm in- Off No alarms, warnings, or abnormal Normal Operating condition. No Action
formation conditions. required.
Yellow At least one abnormal condition Retrieve abnormal condition using JSUM,
Blinking present in the NE. see Table 6.4, and troubleshoot
accordingly.
Yellow At least one alarm with Warning Retrieve alarms using the alarm
severity present in the NE. An monitor, see Table 6.3, and
abnormal condition may also be troubleshoot accordingly.
present.
Red At least one alarm with Major or Minor Retrieve alarms using the alarm
severity present in the NE. An alarm monitor, see Table 6.3, and
with Warning severity or an abnormal troubleshoot accordingly.
condition may also be present.
Red and At least one alarm with Major or Minor Retrieve alarms using the alarm
yellow severity and at least one alarm with monitor, see Table 6.3, and
transition Warning severity is present in the NE. troubleshoot accordingly.

Table 6.7 — MSS-1 shelf LED indications
Status OFF MSS-1 shelf not Provisioned Provision MSS-1 shelf.
MSS-1 shelf not Powered Verify MSS-1 shelf fuse is not blown or
missing.
distribution panel.
MSS-1 shelf not Equipped Verify that the MSS-1 shelf is properly
installed.

Blinking Booting. software boot to complete.
Green MSS-1 shelf Properly Equipped and Normal Operating condition. No Action
Provisioned. currently In-Service. required.
Red MSS-1 shelf Fail Replace MSS-1 shelf
Major Red At least one alarm with Critical or Retrieve alarms using the alarm monitor,
Alarm Major severity present in the NE. see Table 6.3, and troubleshoot
accordingly.
Minor Red At least one alarm with Minor severity Retrieve alarms using the alarm monitor,
Alarm present in the NE. see Table 6.3, and troubleshoot
accordingly.
Warning Yellow At least one alarm with Warning Retrieve alarms using the alarm monitor,
severity present in the NE. see Table 6.3, and troubleshoot
accordingly.
Abnormal Yellow At least one abnormal condition Retrieve abnormal condition using JSUM,
present in the NE. see Table 6.4, and troubleshoot
accordingly.
PFoE Yellow Port is emitting power according to —
the configuration.
OFF Port is not emitting power according

to the configuration.

Table 6.8 — Transport Card LED indications

missing.
distribution panel.
Not Equipped Verify that the card is properly

installed.


Active.
Yellow Card Properly Equipped and Provisioned Normal operating condition for Standby
as EPS. Currently in Standby. card.
No Action required.
Red Blinking Card Mismatch Check alarms for replaceable unit type
mismatch, see
Equipment alarms.
PFoE Yellow Port is emitting power according to the —

configuration.
OFF Port is not emitting power according to

the configuration.

Table 6.9 — Ethernet LED indications
LED Indication Description Probable cause Corrective action
ETH Link Green LED Loss of Ethernet Cable between link partner Connect/repair cable.
Not Lit communication and Ethernet port is
disconnected/
with link partner.
broken.
Speed/Mode provisioning Check local Ethernet

mismatch between link provisioning screen.
partner and Ethernet port. Check link partner
provisioning.

Table 6.10 — MPT-HL transceiver LED alarm indications
Not Powered Verify MPT-HL Transceiver fuse is not

blown or missing.
Verify Power cable is properly
distribution panel.
Invalid Configuration Verify configuration provisioning and

correct as required.
Green Configuration Downloading, or SW Wait for configuration download or

Blinking Booting. (Different blink rates should software boot to complete.
be used to identify each step of the
startup process.)
Green Card Properly Equipped and Normal Operating condition. No

Provisioned. EPS or RPS currently In- Action required.
Service/Active.
Yellow Card Properly Equipped and Normal operating condition for

Provisioned. EPS and RPS currently in Standby MPT-HL Transceiver.
Green/Red Card Properly Equipped and —

Blinking Provisioned. Either TX or RX equipment
or signal Fault. EPS or RPS currently In-
Service/Active. Traffic is probable
affected.
Equipment problem at either near end Check alarms.

or far end: Check abnormal conditions.
Check protection schemes.
Path related problem: Check RSL levels

Check equipment alarms.
Verify no weather related issue.
PA switch at the far end is set to OFF ‘0’ Verify PA switch position at the far
position: end and set to ON ‘1’ position.

Table 6.10 — MPT-HL transceiver LED alarm indications (Continued)
Status Yellow/Red Card Properly Equipped and —

(continued) Blinking Provisioned, TX or RX signal Fault, EPS
and RPS currently in Standby. Traffic
maybe affected:


Red Card Fail Replace MPT-HL Transceiver
Red Blinking MAP Communication Time-out: Check alarms for Internal

Communication between the MPT-HL Communication
Transceiver and the Core-E, EASv2, or Problem, if present, see
P8ETH card or MSS-1 unit is lost.
Internal loss of communications.
Power Green LED MPT-HL Transceiver is emitting power No Action required

Emission ON as expected according to the known
configuration.
Green LED MPT-HL Transceiver is not emitting —

Blinking power due to a forced squelch
condition.
Most probable causes:
TX mute active Release TX mute
PA switch is positioned Off Position PA switch to On position

Green LED MPT-HL Transceiver is not emitting —
OFF power for reasons other than “forced
squelch”.
Transmit Protection Switch (TPS) is Verify MPT-HL Transceiver should be

currently in standby state. in standby state.
Software booting or FPGA download in Wait for software booting or FPGA

progress download to complete

Table 6.11 — MPT-HLC transceiver LED alarm indications
Not Powered Verify MPT-HLC Transceiver fuse is

not blown or missing.
Verify Power cable is properly
distribution panel.
Invalid Configuration Verify configuration provisioning and

correct as required.
Green Configuration Downloading, or SW Wait for configuration download or

Blinking Booting. (Different blink rates should software boot to complete.
be used to identify each step of the
startup process.)
Green Card Properly Equipped and Normal Operating condition. No

Provisioned. EPS or RPS currently In- Action required.
Service/Active.

Provisioned. EPS and RPS currently in Standby MPT-HLC Transceiver.
Green/Red Card properly equipped and —

Blinking provisioned. RX signal fault, EPS or
RPS currently In-Service/Active.
Traffic is probable affected.

PA switch at the far end is set to OFF Verify PA switch position at the far
‘0’ position: end and set to ON ‘1’ position.

Table 6.11 — MPT-HLC transceiver LED alarm indications (Continued)
Status Yellow/Red Card properly equipped and —

(continued) Blinking provisioned, RX signal Fault, EPS and
RPS currently in Standby. Traffic
maybe affected:


Red Card Fail Replace MPT-HLC Transceiver
Red Blinking MAP Communication Time-out: Check alarms for Internal

Communication between the MPT-HLC Communication
Transceiver and the Core-E, EASv2, or Problem, if present, see
P8ETH card or MSS-1 unit is lost.
Internal loss of communications.
Power Green LED MPT-HLC Transceiver is emitting No Action required

Emission ON power as expected according to the
known configuration.
Yellow MPT-HLC Transceiver is not emitting —

power due to a forced squelch
condition including manual PA switch
or an auto-mute condition.
Most probable causes:
TX mute active Release TX mute
PA switch is positioned Off Position PA switch to On position
Red MPT-HLC Transceiver is abnormally —

emitting power in contrast with the
known configuration (Tx Power alarm
is raised during normal operational
mode
Green LED MPT-HLC Transceiver is not emitting —

OFF power for reasons other than “forced
squelch”.
Transmit Protection Switch (TPS) is Verify MPT-HL Transceiver should be

currently in standby state. in standby state.
Software booting or FPGA download in Wait for software booting or FPGA
progress download to complete

Table 6.12 — MPT-HLS transceiver front panel indicator details
LED Indicator Probable Cause Corrective Action
Status (S) Off Card not powered • Verify that the MPT-HLS fuse
is not blown or missing
• Verify that the power cable is
properly terminated at both
ends
• Verify voltage level at the
TRU
Green FPGA Downloading, or SW Booting. Wait for configuration download or

Blinking (Different blink rates identify each software boot to complete.
step of the startup process.)
Green In Service, Normal Operation, and Normal operating condition. No

Properly Provisioned. EPS or RPS action required.
currently In-Service/Active.
Provisioned in 1+1, currently in standby radio. No action required.
Standby.
Green/ Card Properly Equipped and Check alarms.

Red Provisioned, Rx signal fault, EPS Check abnormal conditions.
Blinking and RPS in Standby.
Yellow/ Card Properly Equipped and Check alarms.

Red Provisioned, RX signal Fault, EPS Check abnormal conditions.
Blinking and RPS currently in Standby.
Traffic may be affected.
Red • HW Card Fail Replace MPT-HLS transceiver
• Power supply failure (Auto-
test failure)
• FPGA failures
• LO alarms
• Modem Tx sync alarm
• PA switch active
• Diversity board card fail (only
in combiner mode)
• RF switch fail (only for the
spare MPT-HLS in HSB
configuration)
In a PA critical temperature
condition, the LED remains green.

Table 6.12 — MPT-HLS transceiver front panel indicator details (Continued)
LED Indicator Probable Cause Corrective Action
Status (S) Red MAP Communication Time-out: Check alarms for Internal
(continued) Blinking Communication between the Communication Problem, if
MPT-HLS Transceiver and the present, see Internal loss of
EASv2 cards is lost. This occurs in communications.
split-mount configuration only.
Power Off MPT-HLS Transceiver is not Verify MPT-HL Transceiver should

Emission emitting power, according to the be in standby state.
known configuration, for example,
Hot Standby.
Green MPT-HLS Transceiver is emitting No action required

power as expected according to
the known configuration.
Yellow MPT-HLS Transceiver is not Release Tx Mute or position PA PSU

emitting power due to an operator switch to On position
command, including manual PA
PSU switch or Tx mute.
Red MPT-HLS Transceiver is abnormally —

emitting power, in contrast with
the known configuration (for
example, when Tx power alarm is
raised during normal operative
mode)
Table 6.13 — TMN network troubleshooting
Problem Possible Cause Possible Solution
Unusually slow Normal network management traffic is There may be too many radios being
communication in radio saturating the communications managed within a single region. Split
network channel. the radio network management into
Polling radios for PM data or missed different regions and back-haul the
alarms too rapidly traffic for each region through separate
channels.
Multiple remote software downloads in
process Poll the radios more slowly.
IP traffic other than network Download to fewer radios at a time.
management traffic being routed Configure external routers to allow only
through radio network network management related traffic
through the Management network of
the radios. Dynamic route updates
(OSPF, RIP) may attempt to reroute high
speed traffic through the TMN network
if a high speed ink fails.

Table 6.13 — TMN network troubleshooting (Continued)
Problem Possible Cause Possible Solution
Unable to operate To perform control operations, the Register the Manager as a craft device.
controls using SNMP Manager must be registered as a craft Manager registration type can be
device. changed as needed to type ‘ct’ to allow
control operation and then be changed
back to ‘nml’ for normal operation.
Can Read SNMP objects Incorrect community string Use the correct community string.
but cannot Write to SNMP If the TMN Interface is configured for Use the correct write community string.
objects SNMPv2, the write community string is
probably wrong.
No traps being received Manager not registered in NE to receive Register Manager with NE.
from NE traps Check network connectivity. Check
Communication failure in network redundant network paths and routing.
Traps are blocked by firewall Traceroute (tracert) is useful for
locating path or routing faults.
Check firewall provisioning to allow
trap UDP ports.
Unable to communicate Possible communication path failure or Use traceroute (tracert) to help locate
with the NE through the routing failure within the radio for communication path or routing
radio network (unable to network. problems.
‘ping’ the NE). Incorrect IP address on the PC. Verify PC IP address, subnet, and
default route.
Can ‘ping’ the TMN If using SNMPv2, using the wrong Verify community string, username, and
Interface but cannot community string, username, or passphrase.
communicate with the passphrase. Verify Manager registration with the NE
NE using SNMP, or can Manager not registered or properly and register or correct registration.
only see a few SNMP registered with the NE. The objects
objects in the NE. visible to an unregistered manager are
generally: the 'system' MIB, a few
objects under 'tsdimSnmpNEMibObject',
the 'opticsIMMgrPollingInfoTable', the
'snmpUsmMib', and 'snmpVacmMib'
objects.


7 — Supporting information
Table 7.1 lists the supporting information that is required to perform maintenance and
trouble clearing on the system. The following references are used:
• For information about operation and administration using the WebEML, see the
Alcatel-Lucent 9500 MPR WebEML User Manual.
• For information about operation and administration using the WebCT, see the
Alcatel-Lucent 9500 MPR WebCT User Manual.
• See the Alcatel-Lucent 9500 MPR Product Information Manual to determine card
location and type.
Table 7.1 — Supporting information
Supporting information See
Alarm condition types Alcatel-Lucent 9500 MPR WebEML User Manual

Alcatel-Lucent 9500 MPR WebCT User Manual
Card locations Alcatel-Lucent 9500 MPR Product Information Manual

Product support information Product support information for the ANSI market
Electrostatic-sensitive devices Electrostatic-sensitive devices
Safety awareness Safety awareness

Laser precautions
Maintenance philosophy Maintenance philosophy
Operations support system Alcatel-Lucent 9500 MPR WebEML User Manual

Security/user authorization Alcatel-Lucent 9500 MPR WebEML User Manual

Alarm and event reports, Retrieve Alcatel-Lucent 9500 MPR WebEML User Manual
Clean fiber-optic connectors Alcatel-Lucent 9500 MPR Hardware Installation and

Replacement Manual

Table 7.1 — Supporting information (Continued)
Clock reference and operation mode Alcatel-Lucent 9500 MPR WebEML User Manual
selections Alcatel-Lucent 9500 MPR WebCT User Manual
Log into system Alcatel-Lucent 9500 MPR WebEML User Manual

Loopback (Core Facing) Alcatel-Lucent 9500 MPR WebEML User Manual
Manage cross-connections Alcatel-Lucent 9500 MPR WebEML User Manual

MIB Database Management (Backup and Alcatel-Lucent 9500 MPR WebEML User Manual
Restore) Alcatel-Lucent 9500 MPR WebCT User Manual
Password change Alcatel-Lucent 9500 MPR WebEML User Manual

Performance monitoring Alcatel-Lucent 9500 MPR WebEML User Manual

Protection switching controls Alcatel-Lucent 9500 MPR WebEML User Manual

Provision equipment Alcatel-Lucent 9500 MPR WebEML User Manual

Provision or edit ports Alcatel-Lucent 9500 MPR WebEML User Manual

Preventive maintenance Alcatel-Lucent 9500 MPR Hardware Installation and

Replacement Manual
Protection upgrade and downgrade Alcatel-Lucent 9500 MPR Hardware Installation and
Replacement Manual
Resolve WebEML/TCO Suite/NEtO startup Alcatel-Lucent 9500 MPR Software Installation and NE
issues Upgrade Manual
Software package rollback Alcatel-Lucent 9500 MPR Software Installation and NE

Upgrade Manual
System power down and power up Alcatel-Lucent 9500 MPR Hardware Installation and
Replacement Manual
Upgrade and downgrade radio profile Alcatel-Lucent 9500 MPR Hardware Installation and
Replacement Manual
Upgrade unlicensed MPT-HL radio to lower 6 Alcatel-Lucent 9500 MPR Hardware Installation and
GHz radio Replacement Manual

Table 7.1 — Supporting information (Continued)
Upgrade MPT ODU to MPT ODU L1 LAG port Alcatel-Lucent 9500 MPR Hardware Installation and
Replacement Manual
Upgrade MPT-HL to MPT-HL L1 LAG port Alcatel-Lucent 9500 MPR Hardware Installation and
Replacement Manual


8 — Facility alarms
8.1 — Purpose
This procedure describes how to identify and clear Facility alarms.
8.2 — General
AU4-AIS is a High Order path alarm indication signal on a channelized E1 unit. The AU4-
AIS is specified as all "1"s in the entire High Order path Administrative Unit. The alarm
becomes significant and must be reported if an LOS, LOF, TIM, or MS-AIS alarm for the
input is not present. As consequent action, any E1 extracted from STM-1 will be replaced
with AIS (and then circuit emulated according to the provisioned settings).
TU12-AIS is a Low Order path alarm indication signal on a channelized E1 unit. The
TU12-AIS is specified as all "1"s in the entire Low Order path Tributary Unit. The alarm
becomes significant and must be reported if an LOS, LOF, TIM, MS-AIS or AU4-AIS,
AU4-LOP, VC4-SLM or VC4-LOM alarm for the input is not present. As a consequent
action, the relevant E1 will be replaced with AIS (and then circuit emulated according to
the provisioned settings).
A Retiming Buffer Overflow alarm on channelized E1 indicates overflow or underflow

conditions of the buffer used to perform the retiming of the circuit emulated E1 when Node
Timing TDM clock source is selected. The alarm is reported if there are no defects related
to the Loss of CESoETH Frame alarm or Rx AIS alarm.
A Loss of Pointer or Loss of Multi-frame alarm on channelized E1 has a similar root cause
to the AU4-AIS and TU12-AIS alarms on channelized E1.These alarms are reported if
other alarms are not present.
AIS (on channelized E1-in) is an alarm indication signal on one or more E1input signals
incoming to the NE on the SDHACC card. The problem is associated with the E1 input
signal to the SDHACC card.

General
AIS (on channelized E1-out) is an alarm indication signal detected by the receive circuit
from the radio link on one or more of the channelized E1 lines, indicating an upstream
failure.
AIS (on E1/DS1/3-in) is an alarm indication signal on one or more E1, DS1, or DS3 input
signals incoming to the NE on the P32E1DS1 or P2E3DS3 cards, or MSS-1 shelf. The
problem is associated with the E1, DS1 or DS3 input signal to the P32E1DS1 or P2E3DS3
cards or MSS-1 shelf.
AIS (on E1/DS1/3-out) is an alarm indication signal detected by the receive circuit from the
radio link on one or more of the E1, DS1, or DS3 lines, indicating an upstream failure.
AIS (on Ele/OptSdh-in) is an alarm indication signal on one or more STM-1/OC-3 input
signals incoming to the NE on the SDHACC card. The problem is associated with the input
signal to the SDHACC card.
An AIS (on Ele/OptSdh-out) is an alarm indication signal detected by the receive circuit
from the radio link on one or more of the STM-1/OC-3 lines, indicating an upstream failure.
A High BER (on Ele/OptSdh-in) alarm indicates that Bit Error Rate threshold of 10E-5 has
been exceeded on receiver input circuits from the client to the SDHACC card.
A High BER (on Ele/OptSdh-out) alarm indicates that Bit Error Rate threshold of 10E-5 has
been exceeded on transmit output circuits to the client from the SDHACC card.
A Loss Of CESoETH Frame (CircuitTDM) indicates packets are not being received by the
emulation circuits from the switch matrix.
A Loss Of Frame (E1/DS1/3-in) indicates no E1, DS1 or DS3 frame is detected on the input
from the client to the P32E1DS1 or P2E3DS3 cards, or MSS-1 shelf.
A Loss Of Frame (E1/DS1/3-out) indicates no E1, DS1, or DS3 frame is detected on an E1/
DS1 or DS3 facility from the switch matrix.
A Loss Of Signal (E1/DS1/3-in) indicates no E1, DS1, or DS3 signal is detected on the
input of the P32E1DS1 or P2E3DS3 cards, or MSS-1 shelf.
A Remote Defect Indication in a received STM-1/OC-3 facility indicates that an RDI is

received on an STM-1/OC-3 from the remote end of the STM-1/OC-3 facility.
A Trace Identifier Mismatch indicates a J0 byte value received on the STM-1/OC-3 facility
is different from the provisioned expected value for the STM-1/OC-3 facility.
See the Alcatel-Lucent 9500 MPR Product Information Manual to determine card location
and address.
See the Alcatel-Lucent 9500 MPR WebEML User Manual for information about how to
execute the commands that are described in this procedure.

Procedure
8.3 — Procedure
1. Using the Alarm Monitor, retrieve all alarms.
2. Review the output. See Table 8.1 for information about facility alarms.
Table 8.1 — Facility alarms

Alarm label Friendly name/entity Facility type See
AIS
AU4/Slot#[3-8]/Port#1 Channelized E1 AU4-AIS on
Channelized E1
facility
TU12#[1-3]-[1-7]-[1-3]/Slot#[3-8]/ Channelized E1 TU12-AIS on
Port#1 Channelized E1
facility
E1-in/#[1-3]-[1-7]-[1-3]/Slot#[3-8]/ Channelized E1 TU12-AIS on
facility
E1-out/#[1-3]-[1-7]-[1-3]/Slot#[3-8]/ Channelized E1 TU12-AIS on
facility
DS1-in/MSS/DS1/Port#[1-16] DS1 (MSS/DS1) AIS on E1 or DS1/3
DS1-in/Slot#[3-8]/Port#[1-32] DS1 (P32E1DS1) in on E1, DS1 or DS3
DS3-in/Slot#[3-8]/Port#[1-2] DS3 (P2E3DS3) facility
E1-in/Slot#[3-8]/Port#[1-32] E1 (P32E1DS1)
E1-in/MSS/E1/Port#[1-16] E1 (MSS/E1)
DS1-out/MSS/DS1/Port#[1-16] DS1 (MSS/DS1) AIS on E1 or DS1/3
DS1-out/Slot#[3-8]/Port#[1-32] DS1 (P32E1DS1) out on E1, DS1 or
DS3-out/Slot#[3-8]/Port#[1-2] DS3 (P2E3DS3) DS3 facility
E1-out/Slot#[3-8]/Port#[1-32] E1 (P32E1DS1)
E1-out/MSS/E1/Port#[1-16] E1 (MSS/E1)
EleSdh-in/Slot#[3-8]/Port[1-2] STM-1/OC-3 AIS on EleSdh/
OptSdh-in/Slot#[3-8]/Port[1-2] OptSdh-in on STM-
1/OC-3 facility
EleSdh-out/Slot#[3-8]/Port[1-2] STM-1/OC-3 AIS on EleSdh/
OptSdh-out/Slot#[3-8]/Port[1-2] EleSdh-out on OC-3
facility
Loss of Multi-frame
AU4/Slot#[3-8]/Port#1 Channelized E1 Loss of Multi-frame
on Channelized E1
facility
Loss of Pointer
AU4/Slot#[3-8]/Port#1 Channelized E1 Loss of Pointer on
TU12#[1-3]-[1-7]-[1-3]/Slot#[3-8]/ Channelized E1 Channelized E1
Port#1 facility

Procedure
Table 8.1 — Facility alarms (Continued)

Retiming Buffer Overflow
E1-in/MSS/DS1/Port#[1-16] E1 on MSS-1 Retiming Buffer
E1-in/Slot#[3-8]/Port#[1-32] E1 on P32E1DS1 Overflow on E1
E1-out#[1-3]-[1-7]- Channelized E1 facility
[1-3]/Slot#[3-8]/Port#1
High BER
EleSdh-in/Slot#[3-8]/Port[1-2] STM-1/OC-3 High BER on EleSdh/
OptSdh-in/Slot#[3-8]/Port[1-2] OptSdh-in on STM-
MS/slot#[3-8]/Port#1 STM-1 1/OC-3 facility
EleSdh-out/Slot#[3-8]/Port[1-2] STM-1/OC-3 High BER on EleSdh/
OptSdh-out/Slot#[3-8]/Port[1-2] OptSdh-out on STM-
1/OC-3 facility
Loss of CESoETH Frame
CircuitTDM/MSS/DS1/Port#[1-16] DS1 (MSS-1) Loss Of CESoETH
CircuitTDM/MSS/E1/Port#[1-16] E1 (MSS-1) frame on E1, DS1,
CircuitTDM/Slot#[3-8]/Port#[1-32] E1/DS1 (P32E1DS1) DS3, STM-1, or OC-3
facility
CircuitTDM/Slot#[3-8]/Port#[1-2] DS3
CircuitTDM/Slot#[3-8]/Port#[1-2] STM-1/OC-3
CircuitTDM#[1-3]-[1-7]-[1-3]/ Channelized E1
Slot#[3-8]/Port#1
Loss of Frame
DS1-in/MSS/DS1/Port#[1-16] DS1 (MSS-1) Loss of frame on
E1-in/MSS/E1/Port#[1-16] E1 (MSS-1) E1/DS1/DS3/
DS1-in/Slot#[3-8]/Port#[1-32] DS1 (P32E1DS1) EleSdh/OptSdh-in
facility
EleSdh-in/Slot#[3-8]/Port[1-2] STM-1/OC-3
OptSdh-in/Slot#[3-8]/Port[1-2]
Slot#[3-8]/Port#1
DS1-out/MSS/DS1/Port#[1-16] DS1 (MSS/DS1) Loss of frame on
DS1-out/Slot#[3-8]/Port#[1-32] DS1 (P32E1DS1) E1/DS1/DS3Ele/
E1-out/Slot#[3-8]/Port#[1-32] E1 (P32E1DS1) OptSdh-out facility
DS1-out/MSS/E1/Port#[1-16] E1 (MSS/E1)
DS3-out/Slot#[3-8]/Port#[1-2] DS3
EleSdh-out/Slot#[3-8]/Port[1-2] STM-1/OC-3
OptSdh-out/Slot#[3-8]/Port[1-2]
Slot#[3-8]/Port#1

Procedure
Table 8.1 — Facility alarms (Continued)

Loss of Signal
DS1-in/MSS/DS1/Port#[1-16] DS1 (MSS/DS1) Loss of signal E1/
DS1-in/Slot#[3-8]/Port#[1-32] DS1 (P32E1DS1) DS1/3-in on E1,
E1-in/MSS/E1/Port#[1-16] E1 (MSS/E1) DS1, DS3, or STM-1/
OC-3 facility
DS3-in/Slot#[3-8]/Port#[1-2] DS3
EleSdh-in/Slot#[3-8]/Port[1-2] STM-1/OC-3
OptSdh-in/Slot#[3-8]/Port[1-2]
EleSdh-in/Slot#[3-8]/Port[1-2] STM-1/OC-3 Remote defect
OptSdh-in/Slot#[3-8]/Port[1-2] indication
MS/slot#[3-8]/Port1] STM-1
Trace Identifier Mismatch
EleSdh-in/Slot#[3-8]/Port[1-2] STM-1/OC-3 Trace identifier
OptSdh-in/Slot#[3-8]/Port[1-2] mismatch
None of the above — — Alarm and abnormal
condition clearing
procedures
3. Troubleshoot any of the following:

a. AU4-AIS on Channelized E1 facility
b. TU12-AIS on Channelized E1 facility
c. Loss of Multi-frame on Channelized E1 facility
d. Loss of Pointer on Channelized E1 facility
e. Retiming Buffer Overflow on E1 facility
f. AIS on E1 in on Channelized E1 facility
g. AIS on E1 out on Channelized E1 facility
h. AIS on E1 or DS1/3 in on E1, DS1 or DS3 facility
i. AIS on E1 or DS1/3 out on E1, DS1 or DS3 facility
j. AIS on EleSdh/OptSdh-in on STM-1/OC-3 facility
k. AIS on EleSdh/EleSdh-out on OC-3 facility
l. High BER on EleSdh/OptSdh-in on STM-1/OC-3 facility
m. High BER on EleSdh/OptSdh-out on STM-1/OC-3 facility
n. Loss Of CESoETH frame on E1, DS1, DS3, STM-1, or OC-3 facility
o. Loss of frame on E1/DS1/DS3/EleSdh/OptSdh-in facility
p. Loss of frame on E1/DS1/DS3Ele/OptSdh-out facility
q. Loss of signal E1/DS1/3-in on E1, DS1, DS3, or STM-1/OC-3 facility

Procedure
r. Remote defect indication

s. Trace identifier mismatch
AU4-AIS on Channelized E1 facility
1. Troubleshoot the source of input STM-1 signal that is associated with the
channelized E1 to the SDHCHAN card.
2. Verify the cabling that is associated with the input STM-1 signal to the
SDHCHAN card.
3. Retrieve the alarms using the Alarm Monitor.
4. Did the AU4-AIS alarm clear?
a. If yes, the procedure is complete.
b. If no, contact the next level of technical support for assistance.
TU12-AIS on Channelized E1 facility
SDHCHAN card.
4. Did the TU12-AIS alarm clear?
Loss of Multi-frame on Channelized E1 facility
SDHCHAN card.
4. Did the Loss of Multi-frame alarm clear?
Loss of Pointer on Channelized E1 facility
channelized E1 input signal to the SDHCHAN card.
SDHCHAN card.
4. Did the Loss of Pointer alarm clear?

Procedure

Retiming Buffer Overflow on E1 facility
1. Troubleshoot any possible synchronization alarms; see chapter 17.
3. Did the synchronization alarms clear?
a. If no, continue troubleshooting the synchronization alarms or contact
technical support for assistance.
b. If yes, proceed to step 4.
5. Did the Retiming Buffer Overflow alarm clear?
AIS on E1 in on Channelized E1 facility
1. Troubleshoot the source of input that is associated with the input signal to
the SDHACC card.
2. Verify the cabling that is associated with the input signal to the SDHACC.
4. Did the AIS (on channelized E1-in) alarm clear?
AIS on E1 out on Channelized E1 facility
1. Troubleshoot the upstream source of the incoming channelized E1.
3. Did the AIS (on channelized E1-out) alarm clear?
AIS on E1 or DS1/3 in on E1, DS1 or DS3 facility
the P32E1DS1 or P2E3DS3 cards, or MSS-1.
2. Verify the cabling that is associated with the input signal to the P32E1DS1
or P2E3DS3 cards, or MSS-1.
4. Did the AIS (on E1/DS1/3-in) alarm clear?
AIS on E1 or DS1/3 out on E1, DS1 or DS3 facility

Procedure
1. Troubleshoot the upstream source of the incoming E1, DS1 or DS3.

3. Did the AIS (on E1/DS1/3-out) alarm clear?
AIS on EleSdh/OptSdh-in on STM-1/OC-3 facility
the SDHACC card.
2. Verify the cabling that is associated with the input signal to the SDHACC
card.
4. Did the AIS (on EleSdh/OptSdh-in) alarm clear?
AIS on EleSdh/EleSdh-out on OC-3 facility
1. Troubleshoot the upstream source of the incoming STM-1/OC-3.
3. Did the AIS (on EleSdh/EleSdh-out) alarm clear?
High BER on EleSdh/OptSdh-in on STM-1/OC-3 facility
the SDHACC card from the demarcation panel.
2. Verify the cabling that is associated with the input signal to the SDHACC
card.
4. Did the High BER (on EleSdh/OptSdh-in) alarm clear?
High BER on EleSdh/OptSdh-out on STM-1/OC-3 facility
1. Troubleshoot the upstream source of the incoming STM-1/OC-3.
3. Did the High BER (on EleSdh/OptSdh-out) alarm clear?
Loss Of CESoETH frame on E1, DS1, DS3, STM-1, or OC-3 facility

Procedure
1. Verify that there are no current path or circuit alarms associated with the
facility in alarm for the near end, the far end, and all intermediate NEs.
2. Verify that the radio path PM is not taking errors to traffic.
3. Are there path or circuit alarms, or path PM errors at the near end or far
end NE?
a. If yes, clear the path or circuit alarms, or path PM errors, then go to
step 4.
b. If no, go to step 6.
5. Did the Loss Of CESoETH Frame alarm clear?
6. Verify that the circuit provisioning for near end, the far end, and all
intermediate NEs:
a. Verify that the Signal Mode is set the same and is correct.
b. Verify that the Line Coding is set the same and is correct.
c. Verify that the Flow ID is set the same and is correct.
d. Verify that the Service Profile is set the same and is correct.
7. Is the Service Profile TDM2ETH?
a. If yes, go to step 8.
8. Verify that the TDM2ETH provisioning for the near end, far end, and all
intermediate NEs:
a. Verify that the Payload Size is set the same and is correct.
b. Verify that the TDM Clock Source is set the same and is correct.
c. Verify that the near end ECID Tx and far end ECID Rx are set the same
and are correct.
d. Verify that the far end ECID Tx and near end ECID Rx are set the same
and are correct.
9. Verify that the cross-connection provisioning for the near end, far end, and
all intermediate NEs:
12. Is the facility associated with a LAG?

Procedure
13. Verify that there are no active LAG alarms at all NEs in the LAG associated
with the facility in alarm.
16. Is the facility associated with an ERP (Ring)?
17. Verify that there are no active RING alarms at all NEs in the ring associated
with the facility in alarm.
20.
Caution: The following steps cause a loss of traffic on ALL facilities supported
by the card or MSS-1 shelf, associated with the facility in alarm. Schedule an
appropriate maintenance window per local practices and procedures.
Is it appropriate to proceed with the Loss Of CESoETH Frame procedure?

21. Is the facility protected?
22.
Caution: Reseating a card in an unprotected facility causes a loss of traffic on
ALL facilities that are associated with the card being reseated. Schedule an
For the P32E1DS1 or P2E3DS3 cards, reseat the card at the near end.
Physically remove the card and reinsert.
For the MSS-1 shelf, locate the fuses protecting the A and B battery feeds to
the near end MSS-1 shelf and remove. Wait ten seconds. Then install the
fuses protecting the A and B battery feeds.

Procedure

25.
Caution: Replacing a card in an unprotected facility causes a loss of traffic on
ALL facilities that are associated with the card being replaced. Schedule an
Replace the card that reported the Loss Of CESoETH Frame alarm. See the
Alcatel-Lucent 9500 MPR Hardware Installation and Replacement Manual.
28.
For the P32E1DS1 or P2E3DS3 cards, reseat the card at the far end.
the far end MSS-1 shelf and remove. Wait ten seconds. Then install the fuses
protecting the A and B battery feeds.
31.
Replace the far end card. See the Alcatel-Lucent 9500 MPR Hardware
Installation and Replacement Manual.
34.

Procedure
Caution: Forced/Lockout switching traffic causes a disruption to traffic.
Is the DS1/DS3/OC-3 facility in alarm associated with the main or spare?

a. If main, perform a Forced EPS Switch at the near end using a Craft
Terminal.
b. If spare, perform a Lockout EPS Switch at the near end using a Craft
Terminal.
35. Reseat the card in alarm at the near end. Physically remove the card and
reinsert.
38. Replace the card that reported the Loss Of CESoETH Frame. See the Alcatel-
Lucent 9500 MPR Hardware Installation and Replacement Manual.
40. Did the Loss Of CESoETH Frame condition clear?
41. Is the card in alarm the main or spare?
a. If main, perform a Forced EPS Switch at the far end using a Craft
Terminal.
b. If spare, perform a Lockout EPS Switch at the far end using a Craft
Terminal.
42. Reseat the card in alarm at the far end. Physically remove the card and
reinsert.
45. Replace the far end card. See the Alcatel-Lucent 9500 MPR Hardware

Procedure
47. Did the Loss Of CESoETH Frame condition clear?

48.
Caution: Releasing Forced/Lockout switch may cause a disruption to traffic.
Release the Forced/Lockout EPS Switch at the far end using a Craft
Terminal.
49.
Release the Forced/Lockout EPS Switch at the near end using a Craft
Terminal.
50. The procedure is complete.
Loss of frame on E1/DS1/DS3/EleSdh/OptSdh-in facility
1. Verify that there are no active circuit alarms associated with the facility in
alarm at the near end and client end NE of the facility.
2. Are there active circuit alarms at the near end or client end of the facility?
a. If yes, clear circuit alarms, then go to step 3.
4. Did the Loss Of Frame alarm the clear?
5. Verify that the circuit provisioning for both the near end and client end of
the facility in alarm:
e. Verify that the LBO setting is correct for the installation.
7. Did the Loss Of Frame alarm clear?

Procedure
8. Verify that the Source Signal is error-free with a test set configured to
match the provisioning of the facility.
11. Verify the cabling:
a. Verify the cabling from the customer interconnect to the patch panel
or card as appropriate. Confirm that the connectors are correctly
seated and secured.
b. Verify the cabling from the patch panel to the module if appropriate.
Confirm that the connectors are correctly seated and secured.
14.
Caution: The following steps cause a loss of traffic on ALL facilities that are
supported by the card or MSS-1 shelf, associated with the facility in alarm.
Schedule an appropriate maintenance window per local practices and
procedures.
Is it appropriate to proceed with the Loss Of Frame procedure?

16.
For the P32E1DS1 or P2E3DS3 cards, reseat the card at the near end.

Procedure

19.
Caution: Replacing a card or MSS-1 shelf in an unprotected facility causes a loss
of traffic on ALL facilities that are associated with the card or MSS-1 shelf being
replaced. Schedule an appropriate maintenance window per local practices and
procedures.
Replace the near end card or shelf. See the Alcatel-Lucent 9500 MPR
Hardware Installation and Replacement Manual.
22.
Is the DS1/DS3/OC-3 facility in alarm associated with the main or spare?

a. If main, perform a Forced EPS Switch at the near end using a Craft
Terminal.
b. If spare, perform a Lockout EPS Switch at the near end using a Craft
Terminal.
23. Reseat the card in alarm at the near end. Physically remove card and
reinsert.
26. Replace the near end card. See the Alcatel-Lucent 9500 MPR Hardware
28. Did the Loss Of Frame condition clear?
29.

Procedure
Release the Forced/Lockout EPS Switch at the near end using the Craft
Terminal.
Loss of frame on E1/DS1/DS3Ele/OptSdh-out facility
1. Check the far end facility for Loss of Frame (DS1/3-in, Ele/OptSdh-in) that
is associated with the facility in alarm.
4. Verify that there are no active path or circuit alarms associated with the
facility in alarm for the near end or far end NE.
5. Verify that the radio path PM is not taking errors to traffic.
6. Are the path or circuit alarms, or path PM errors existing at the near end or
far end NE?
a. If yes, clear path or circuit alarms or path PM errors, then go to step 7.
9. Check the circuit provisioning for the near end and far end facility in alarm
and that they are correct, as required:
10. Is the Service Profile TDM2ETH?
11. Check the TDM2ETH provisioning for the near end and far end facility in
alarm and that it is correct, as required:
a. Verify that the Payload Size is set the same and is correct.
b. Verify that the TDM Clock Source is set the same and is correct.

Procedure
c. Verify that the near end ECID Tx and far end ECID Rx are set the same
and are correct.
d. Verify that the far end ECID Tx and near end ECID Rx are set the same
and are correct.
14. Check the cross-connection provisioning at the near end, far end, and all
intermediated NEs that are associated with the facility in alarm are correct,
as required:
a. Verify that the Flow ID is set the same and is correct.
b. Verify that the MAC address is set the same and is correct.
c. Verify that the TDM profile is set correct
d. Verify that the TDM Clock Source is set correct.
17.
by the card or MSS-1 shelf, associated with the facility in alarm. Schedule an
Is it appropriate to proceed with the Loss Of Frame procedure?

19.
ALL facilities that are associated with the card or MSS-1 shelf being reseated.
procedures.
For the SDHACC, P32E1DS1 or P2E3DS3 cards, reseat the card at the near
end. Physically remove the card and reinsert.

Procedure
22.
Replace the near end shelf or card. See the Alcatel-Lucent 9500 MPR
25.
For the SDHACC, P32E1DS1 or P2E3DS3 cards, reseat the card at the far end.
the far end MSS-1 shelf and remove. Wait ten seconds. Then install the fuses
28.
Replace the far end card or shelf. See the Alcatel-Lucent 9500 MPR

Procedure

31.
Is DS1/DS3/OC-3 facility in alarm associated with main or spare?

a. If main, perform a Forced EPS Switch at the near end using the Craft
Terminal.
b. If spare, perform a Lockout EPS Switch at the near end using the Craft
Terminal.
32. Reseat card in alarm at the near end. Physically remove card and reinsert.
38.
Is card in alarm main or spare?

a. If main, perform a Forced EPS Switch at the far end using the Craft
Terminal.
b. If spare, perform a Lockout EPS Switch at the far end using the Craft
Terminal.
39. Reseat the card in alarm at the far end. Physically remove the card and
reinsert.

Procedure

42. Replace the far end card. See the Alcatel-Lucent 9500 MPR Hardware
45.
Caution: Releasing a Forced/Lockout switch may cause a disruption to traffic.
Release the Forced/Lockout EPS Switch at the far end using the Craft
Terminal.
46.
Caution: Releasing a Forced/Lockout switch may cause a disruption to traffic.
Terminal.
Loss of signal E1/DS1/3-in on E1, DS1, DS3, or STM-1/OC-3 facility
1. Troubleshoot source of input to MSS-1 shelf, P32E1DS1 or P2E3DS3, or
SDHACC card.
2. Verify cabling associated with the input signal to the MSS-1 shelf, P32E1DS1
or P2E3DS3, or SDHACC card.
3. Retrieve alarms using the Craft Terminal.
4. Did the Loss Of Signal alarm clear?
5. Retrieve alarms using the Craft Terminal. Determine if Loss Of Signal alarm
is declared against ALL facilities associated with the MSS-1 shelf, P32E1DS1
or P2E3DS3, or SDHACC card.
6. Are ALL facilities associated with the MSS-1 shelf, P32E1DS1 or P2E3DS3, or
SDHACC card declaring Loss Of Signal?

Procedure

8.
Reseat the card that declares the Loss Of Signal alarm. Physically remove
the card and reinsert.
11.
Replace the near end card. See the Alcatel-Lucent 9500 MPR Hardware
Caution: Forced EPS switching traffic causes a disruption to traffic.
a. If main, perform a Forced EPS Switch at the near end using the Craft
Terminal.
b. If spare, perform a Lockout EPS Switch at the near end using the Craft
Terminal.
15. Verify that the card in alarm status is Standby.
16. Reseat the card that declared the Loss Of Signal alarm. Physically remove
the card and reinsert.

Procedure
22.
Caution: Releasing EPS switch may cause a disruption to traffic.
Terminal.
Remote defect indication
1. Retrieve the alarms for the far end of the STM-1/OC-3 facility using the
Alarm Monitor.
2. Determine all of the facility alarms that are declared against the far end
STM-1/OC-3 facility associated with the STM-1/OC-3 facility declaring the
Remote Defect Indication (RDI) and troubleshoot accordingly.
4. Did the RDI alarm clear?
Trace identifier mismatch
1. Using the Craft Terminal, retrieve the provisioned Trace Identifier values
for the alarmed STM-1/OC-3 facility.
Note: The section trace identifier (J0) value is not generated within the 9500 MPR
network. The received J0 value is verified against the provisioned expected value. To
determine the provisioned J0 value the operator must query the originating SDH/OC-3
equipment.
2. Determine the origination of the STM-1/OC-3 facility and retrieve the

provisioned Trace Identifier parameters.
3. Verify that the desired Trace Identifier parameters of the STM-1/OC-3
facility.
4. Determine which Trace Identifier parameters are incorrect.
5. Provision the Trace Identifier parameters according to the results of step 4.

Procedure
7. Did the Trace Identifier Mismatch alarm clear?


Procedure

9 — Abnormal conditions
9.1 — Purpose
This procedure describes how to identify and clear abnormal conditions on cards and
radios.
9.2 — General
A Core Facing PDH Loopback indicates that a PDH (E1, DS1 or DS3) entity has a loopback
activated at the near end.
A Core Facing SDH Loopback indicates that an SDH (STM-1 or OC3) entity has a
loopback activated at the near end.
A Digital Core Facing Loopback indicates that the entity has a loopback activated at the
near end.
A Forced Adaptive Modulation indicates that a manual Forced Adaptive Modulation

command has been issued.
A Forced Switch EPS/RPS/TPS indicates that a forced switch has been executed for the
protection group.
A Line Facing Circuit Loopback indicates that the entity has a loopback activated at the
near end.
A Line Facing PDH Loopback indicates that a PDH entity has a line facing loopback
A Line Facing SDH Loopback indicates that an SDH entity has a line facing loopback
A Lockout Switch EPS/RPS/TPS indicates that a lockout switch has been executed for the
protection group.

Procedure
An Rx Main squelch or Rx Div squelch indicates that a squelch command has been
executed for an MPT-HLC or MPT-HLS combiner.
TxMute indicates that a manual or automatic mute command has been executed.
and address.
See the Alcatel-Lucent 9500 MPR WebEML User Manual or Alcatel-Lucent 9500 MPR
WebCT User Manual for information about how to execute the commands that are
described in this procedure.
9.3 — Procedure
1. Using the Craft Terminal, retrieve abnormal conditions.
2. Review the output. See Table 9.1 for information about abnormal
conditions.
Table 9.1 — Abnormal conditions

Entity Type (equipment) See
DS1 Port#[1-16] Internal Loopback Core facing PDH
E1 Port#[1-16] Internal DS1/E1 on MSS-1 loopback
DS3 Port#[1-2] Internal SLOT#[3-8]
E1 Port3[1-32] Internals
OC3 Port#[1-2] Internal Loopback Core facing SDH
STM-1 Port#[1-2] Internal SLOT#[3-8] loopback

Procedure
Table 9.1 — Abnormal conditions (Continued)

Direction #1.[1-6] Loopback Digital core facing
(MPT ODU connected to Core-E, loopback
MSS-1)
(MPT ODU connected to CorEvo)
(MPT ODU connected to MSS-O)
(MPT ODU connected to MPTACC)
(MPT ODU connected to P8ETH)
(MPT ODU connected to EASv2)
(MPT-HL, MPT-HLC, or MPT-HLS
connected to Core-E, MSS-1)
connected to CorEvo)
(MPT-HL or MPT-HLC connected
to EASv2, P8ETH)
(MPT-HLS connected to EASv2)

Procedure

Direction #1.[1-6] - Channel #1 Radio Forced adaptive
(MPT ODU connected to Core-E, modulation
MSS-1)
Direction #1.[1-4,7-8] - Channel #1 Radio
(MPT ODU connected to CorEvo)
Direction #1.[1-3] Radio
Direction #[3-8].[1-4] - Channel #1 Radio
Direction #1.[5-6] - Channel #1 Radio
to EASv2, P8ETH)
Direction #[3-8].[5-8] - Channel #1 Radio (MPT-HLS connected to
EASv2)

Procedure

Forced switch - EPS
Main#1 Slot#1 Equipment Protection (Core-E, Forced switch -
CorEvo) EPS, RPS, and TPS
Main#1 Slot#[3,5,7] Equipment Protection (P2E3DS3,
P32E1DS1, SDHACC)
Main#1 Slot #[3-8] Port #[1-4] Equipment Protection (MPT ODU
connected to MPTACC)
Main#1 Slot #1 Port #[1,3,5] Equipment Protection (MPT ODU
connected to Core-E)
Main#1 Slot #1 Port #[1,3,7] Equipment Protection (MPT ODU
Main#1 MSS/CORE Port #[1,3,5] Equipment Protection (MPT ODU
connected to MSS-1)
Main#1 Slot #1 Port #1 Equipment Protection (MPT ODU
connected to MSS-O)
Main#1 Slot #[3,5,7] Port #[5-8] Equipment Protection (MPT ODU
connected to EASv2)
Main#1 Slot #1 Port #5 Equipment Protection (MPT-HLC,
or MPT-HLS connected to Core-E)
Main#1 Slot #1 Port #7 Equipment Protection (MPT-HLC,
or MPT-HLS connected to CorEvo)
Main#1 MSS/CORE Port #5 Equipment Protection (MPT-HLC,
or MPT-HLS connected to MSS-1)
Main#1 Slot #[3,5,7] Port #[5-8] Equipment Protection (MPT-HL or
MPT-HLC connected to EASV2,
P8ETH)
Main#1 Slot #[3,5,7] Port #[5-8] Equipment Protection (MPT-HLS
connected to EASv2)
Forced switch - RPS
Main#1 Slot #1 Port #[1,3,5] Rx Radio Protection (MPT ODU Forced switch -
connected to Core-E) EPS, RPS, and TPS
Main#1 Slot #1 Port #[1,3,7] Rx Radio Protection (MPT ODU
Main#1 MSS/CORE Port #[1,3,5] Rx Radio Protection (MPT ODU
connected to MSS-1)
connected to MSS-O)
Main#1 Slot #[3-8] Port #[1-4] Rx Radio Protection (MPT ODU
Main#1 Slot #[3,5,7] Port #[5-8] Rx Radio Protection (MPT ODU
connected to EASv2)

Procedure

Main#1 Slot #1 Port #5 Rx Radio Protection (MPT-HLC or Forced switch -
MPT-HLS connected to Core-E) EPS, RPS, and TPS
Main#1 Slot #1 Port #7 Rx Radio Protection (MPT-HLC or
MPT-HLS connected to CorEvo)
Main#1 MSS/CORE Port #5 Rx Radio Protection (MPT-HLC or
MPT-HLS connected to MSS-1)
Main#1 Slot #[3,5,7] Port #[5-8] Rx Radio Protection (MPT-HL or
MPT-HLC connected to EASv2,
P8ETH)
Main#1 Slot #[3,5,7] Port #[5-8] Rx Radio Protection (MPT-HLS
connected to EASv2)
Forced switch - TPS
Main#1 Slot #1 Port #[1,3,5] HSB Protection (MPT ODU Forced switch -
Main#1 Slot #1 Port #[1,3,7] HSB Protection (MPT ODU
Main#1 MSS/CORE Port #[1,3,5] HSB Protection (MPT ODU
connected to MSS-1)
connected to MSS-O)
Main#1 Slot #[3-8] Port #[1-4] HSB Protection (MPT ODU
Main#1 Slot #[3,5,7] Port #[5-8] HSB Protection (MPT ODU
connected to EASv2)
Main#1 Slot #1 Port #5 HSB Protection (MPT-HLC or MPT-
HLS connected to Core-E)
Main#1 Slot #1 Port #7 HSB Protection (MPT-HLC or MPT-
HLS connected to CorEvo)
Main#1 MSS/CORE Port #5 HSB Protection (MPT-HLC or MPT-
HLS connected to MSS-1)
Main#1 Slot #[3,5,7] Port #[5-8] HSB Protection (MPT-HL or
P8ETH)
Main#1 Slot #[3,5,7] Port #[5-8] HSB Protection (MPT-HLS
connected to EASv2)

Procedure

Direction #1.[1-6] Loopback Line facing circuit
(MPT ODU connected to Core-E, loopback
MSS-1)
Direction #1.[1-4,7-8] Loopback (MPT ODU connected to
CorEvo)
to EASv2, P8ETH)
DS1 Port#[1-16] External Loopback Line facing PDH
(DS1 on MSS-1) loopback
E1 Port#[1-16] External Loopback
(E1 on MSS-1)
E1 Port#[1-32] External (P2E3DS3, P32E1DS1: SLOT#[3-8])
DS3 Port#[1-2] External
STM-1 Port#[1-2] External Loopback Line facing SDH
OC-3 Port#[1-2] External (SDHACC: SLOT#[3-8]) loopback

Procedure

Lockout switch - EPS
Spare#0 Slot#2 Equipment Protection (Core-E, Lockout switch for
CorEvo) EPS, RPS, and TPS
Spare#0 Slot#[4,6,8] Equipment Protection (P2E3DS3,
P32E1DS1, SDHACC)
Spare#0 Slot #1 Port #[2,4,6] Equipment Protection (MPT ODU
connected to Core-E)
Spare#0 Slot #1 Port #[2,4,8] Equipment Protection (MPT ODU
Spare#0 MSS/CORE Port #[2,4,6] Equipment Protection (MPT ODU
connected to MSS-1)
Spare#0 Slot #1 Port #2 Equipment Protection (MPT ODU
connected to MSS-O)
Spare#0 Slot#[3-8] Port #[1-4] Equipment Protection (MPT ODU
Spare#0 Slot#[4,6,8] Port #[5-8] Equipment Protection (MPT ODU
connected to EASv2)
Spare#0 Slot #1 Port #6 Equipment Protection (MPT-HLC
or MPT-HLS connected to Core-E)
Spare#0 Slot #1 Port #8 Equipment Protection (MPT-HLC
or MPT-HLS connected to CorEvo)
Spare#0 MSS/CORE Port #6 Equipment Protection (MPT-HLC
or MPT-HLS connected to MSS-1)
Spare#0 Slot#[4,6,8] Port #[5-8] Equipment Protection (MPT-HL or
P8ETH)
Spare#0 Slot#[4,6,8] Port #[5-8] Equipment Protection (MPT-HLS
connected to EASv2)
Lockout switch - RPS
Spare#0 Slot #1 Port #[2,4,6] Rx Radio Protection (MPT ODU Lockout switch for
Spare#0 Slot #1 Port #[2,4,8] Rx Radio Protection (MPT ODU
Spare#0 MSS/CORE Port #[2,4,6] Rx Radio Protection (MPT ODU
connected to MSS-1)
connected to MSS-O)
Spare#0 Slot#[3-8] Port #[1-4] Rx Radio Protection (MPT ODU
Spare#0 Slot#[4,6,8] Port #[5-8] Rx Radio Protection (MPT ODU
connected to EASv2)
Spare#0 Slot #1 Port #6 Rx Radio Protection (MPT-HLC or
MPT-HLS connected to Core-E)

Procedure

Spare#0 Slot #1 Port #8 Rx Radio Protection (MPT-HLC or Lockout switch for
MPT-HLS connected to CorEvo) EPS, RPS, and TPS
Spare#0 MSS/CORE Port #6 Rx Radio Protection (MPT-HLC or
MPT-HLS connected to MSS-1)
Spare#0 Slot#[4,6,8] Port #[5-8] Rx Radio Protection (MPT-HL or
P8ETH)
Spare#0 Slot#[4,6,8] Port #[5-8] Rx Radio Protection (MPT-HLS
connected to EASv2)
Lockout switch - TPS
Spare#0 Slot #1 Port #[2,4,6] HSB Protection Lockout switch for
(MPT ODU connected to Core-E) EPS, RPS, and TPS
Spare#0 Slot #1 Port #[2,4,8] HSB Protection (MPT ODU
Spare#0 MSS/CORE Port #[2,4,6] HSB Protection
(MPT ODU connected to MSS-1)
connected to MSS-O)
Spare#0 Slot #[3-8] Port #[1-4] HSB Protection
Spare#0 Slot#[4,6,8] Port #[5-8] HSB Protection
Spare#0 Slot #[4,6,8] Port #[5-8] HSB Protection
(MPT-HL connected to EASV2,
P8ETH)
(MPT-HLC or MPT-HLS connected
to Core-E)
to CorEvo)
Spare#0 MSS/CORE Port #6 HSB Protection
to MSS-1)
(MPT-HLC connected to EASv2,
P8ETH)

Procedure

Rx Main squelch
Direction #1.[5-6] - Channel #[0-1] Radio (MPT-HLC or MPT-HLS Rx Main squelch
Direction #1.[7-8] - Channel #[0-1] Radio (MPT-HLC or MPT-HLS
Direction #[3-8].[5-8] - Channel #[0-1] Radio (MPT-HLC connected to
EASv2, P8ETH)
Direction #[3-8].[5-8] - Channel #[0-1] Radio (MPT-HLS connected to
EASv2)
Rx Div squelch
Direction #1.[5-6] - Channel #[0-1] Radio (MPT-HLC or MPT-HLS Rx Div squelch
EASv2, P8ETH)
EASv2)
TxMute
Direction #1.[1-6] - Channel #[0-1] Radio (MPT ODU connected to TXMute
Core-E, MSS-1)
Direction #1.[1-4,7-8] - Channel #[0-1] Radio (MPT ODU connected to
CorEvo)
Direction #1.[1-3] - Channel #[0-1] Radio
Direction #[3-8].[1-4] - Channel #[0-1] Radio
(MPT ODU connected to EASv2
Direction #[3-8].[5-8] - Channel #[0-1] Radio
(MPT ODU connected to EASv2
Direction #1.[5-6] - Channel #1 Radio (MPT-HL connected to
Core-E, MSS-1)
(MPT-HL connected to CorEvo)
Direction #[3-8].[5-8] - Channel #[0-1] Radio (MPT-HL connected to
EASv2, P8ETH)

Procedure

Direction #1.[7-8] - Channel #[0-1] Radio (MPT-HLC or MPT-HLS TXMute
EASv2, P8ETH)
EASv2)
None of the above — Alarm and
abnormal condition
clearing
procedures
3. Troubleshoot one of the following:

a. Core facing PDH loopback
b. Core facing SDH loopback
c. Digital core facing loopback
d. Forced adaptive modulation
e. Forced switch - EPS, RPS, and TPS
f. Line facing circuit loopback
g. Line facing PDH loopback
h. Line facing SDH loopback
i. Lockout switch for EPS, RPS, and TPS
j. Rx Main squelch
k. Rx Div squelch
l. TXMute
1. Ready to release the Core Facing PDH Loopback?
b. If no, the procedure is completed.
2. Using the Craft Terminal, release the loopback.
3. Retrieve the Abnormal Condition List using the Craft Terminal.
4. Did the Core Facing PDH Loopback condition clear?
a. If yes, the procedure is completed.
1. Ready to release the Core Facing SDH Loopback?

Procedure

4. Did the Core Facing SDH Loopback condition clear?
1. Ready to release the Digital Core Facing Loopback?
4. Did the Digital Core Facing Loopback condition clear?
1. Ready for the Forced Adaptive Modulation to be released?
2. Using the Craft Terminal, release the Forced Adaptive Modulation.
4. Did the Forced Adaptive Modulation condition clear?
Forced switch - EPS, RPS, and TPS
1. Ready to release the Forced Switch EPS/RPS/TPS?
Caution: Releasing a Forced Switch causes a disruption to traffic.
2. Using the Craft Terminal, release the Forced Switch EPS/RPS/TPS.
4. Did the Forced Switch EPS/RPS/TPS condition clear?

Procedure

1. Ready to release the loopback?
4. Did the Line Facing Circuit Loopback condition clear?
1. Ready to release the Line Facing PDH Loopback?
4. Did the Line Facing PDH Loopback condition clear?
1. Ready to release the Line Facing SDH Loopback?
4. Did the Line Facing SDH Loopback condition clear?
Lockout switch for EPS, RPS, and TPS
1. Ready to release the Lockout Switch EPS/RPS/TPS?
2. Using the Craft Terminal, release the lockout switch.
4. Did the Lockout Switch EPS/RPS/TPS condition clear?

Procedure

Rx Main squelch
1. Ready for the squelch to be released?
b. If no, the procedure is complete.
2. Using the Craft Terminal, release the squelch.
4. Did the Rx Main squelch condition clear?
Rx Div squelch
1. Ready for the squelch to be released?
2. Using the Craft Terminal, release the squelch.
4. Did the Rx Div squelch condition clear?
TXMute
1. Ready for the TxMute to be released?
2. Using the Craft Terminal, release the TxMute.
4. Did the TxMute condition clear?

10 — Power alarms
10.1 — Purpose
This procedure describes how to identify and clear power alarms that are associated with
the MSS-1/MSS-4/MSS-8 shelf, EASv2, MPTACC card, MSS-O and MSS-1 Core.
10.2 — General
A Battery Failure alarm indicates that the A battery feed has failed or is missing, when
battery protection is available.
A Low Input Voltage alarm indicates that the input voltage has dropped below the
configured threshold.
A Power Supply Failure alarm indicates one or more of the following:
• hardware failure:
• on the EASv2 card supplying power to an MPT-HC/9558HC (MPT-ODU)
• on the MPTACC card supplying power to an MPT-HC/9558HC (MPT-ODU)
• on the MSS-O Core Ethernet ports 1 and 2, supplying power to an MPT-ODU
• on the MSS-1 Core Ethernet ports 1 and 2, supplying power to an MPT-ODU
• bad cable, or an improperly terminated cable between:
• the EASv2 and MPT-ODU
• the MPTACC and MPT-ODU
• the MSS-O and MPT-ODU
• the MSS-1 and MPT-ODU
A Secondary Battery Failure alarm indicates that either the B battery feed has failed or is
missing, when battery protection is available.
The EASv2 card provides power to the MPT ODU using the PFoE supported RJ45
connectors.

Procedure
The MPTACC card provides power to the MPT ODU using the PFoE supported RJ45 or
QMA coaxial connectors.
The MSS-1 Core provides power to the MPT ODU using the two PFoE supported RJ45
connectors.
The MSS-O Core provides power to the MPT ODU using the two PFoE supported RJ45
connectors.
and address, and for information about supported voltage.
10.3 — Procedure
2. Review the output. See Table 10.1 for information about the power alarms.
Table 10.1 — Power Alarms

Alarm label Friendly name/entity Equipment type See
Battery Failure
r01/subrack#1 MSS-1/8 Battery Failure
r01/subrack#[101-102] MPT-HLS
r01/s[101-102]/[1-10] MPT-HLS
Low Input Voltage
r01/subrack#1[1-6] MPT-HC/XP-HQAM Low Input Voltage
connected to Core-E,
MSS-1
r01/subrack#1[1-4,7-8] MPT-HC/XP-HQAM
connected to CorEvo
r01/subrack#1[1-3] MPT-HC/XP-HQAM
connected to MSS-O
r01/subrack#[3-8][1-4] MPT-HC/XP-HQAM
connected to EASv2,
MPTACC
r01/subrack#[3-8][5-8] MPT-HC/XP-HQAM
connected to EASv2,
P8ETH

Procedure
Table 10.1 — Power Alarms (Continued)

r01/subrack#[3-8][1-4] EASv2 Power Supply Failure
r01/subrack#[3-8][1-4] MPTACC
r01/subrack#1[1-2] MSS-O
MPT/Dir#1.[1-2] MSS-1
Secondary Battery Failure
r01/subrack#1 MSS-1/8 Secondary Battery
r01s[101-102]board#[1-10] MST-HLS Failure
condition clearing
procedures

• Battery Failure
• Low Input Voltage
• Power Supply Failure
• Secondary Battery Failure
Battery Failure
1. Verify that there is no blown fuse providing power to the A-power feed.
2. Verify the shelf power cable connections between the MSS-1/8 or MPT-HLS
and the power distribution panel.
3. Verify the A-power connections between the BDFB and power distribution
panel.
4. Verify that the A-power BDFB breakers are in the ON position.
6. Did the Battery Failure clear?
7. Measure the voltage of the A-power feed.
8. Is the measured voltage within the supported voltage range (MSS-8: -40.8
VDC to -57.6 VDC, MSS-1: +20.0 VDC to +60.0 VDC or -20.0 VDC to -60.0 VDC,
MPT-HLS: +20.4 VDC to +57.6 VDC or -20.4 VDC to -57.6 VDC)?
a. If yes, contact the next level of technical support for assistance.
9. Troubleshoot the A-power feed voltage problem.
11. Did Battery Failure condition clear?

Procedure

Low Input Voltage
1. Using site documentation determine the power source of the radio in alarm.
2. Measure the voltage of the power feed(s) for the power source of the radio
declaring the low input voltage alarm.
a. MSS-8: -40.8 VDC to -57.6 VDC
b. MSS-8 W/+24/-48 Volt Converter: +19.0VDC to +36.0 VDC
c. MSS-4: -40.8 VDC to -57.6 VDC
d. MSS-1:
• +20.0 VDC to +60.0 VDC
• -20.0 VDC to -60.0 VDC
e. MSS-O: 110 VAC to 230 VAC
f. Power Injector Box: -38.4 VDC to -57.6 VDC
g. MPT Power Unit:-38.4 VDC to -57.6 VDC
h. MPT Extended Power Unit: -40.8 VDC to -57.6 VDC
• -19.2 VDC to -57.6 VDC
• +19.2 VDC to +57.6 VDC
i. Direct connection to Battery: -28.0 VDC to -57.6 VDC
3. Is the measured voltage within the supported voltage range?
4. Troubleshoot the power feed voltage problem.
6. Did the Low Input Voltage condition clear?
7. Using the Craft Terminal, determine the input voltage, current, and voltage
threshold for the radio in alarm.
8. Are the measured input voltage and current levels reported reasonable for
the radio installation (cable type and length) and the input voltage
measured in step 2?
9. Re-provision the input voltage threshold based upon site documentation and
the results of step 8.

Procedure
Note: The hysteresis associated with the input voltage alarm is 3 VDC.

11. Did the Low Input Voltage condition clear?
12. Is the radio in alarm in a protected system?
13. Is the radio in alarm main or spare?
Caution: Removing power to an in-service radio hop in a protected link requires
switching the traffic onto the standby radio hop.
a. If main, go to step 14.

b. If spare, go to step 18.
14.
Caution: Forced EPS/HSB/RX Radio switching traffic causes a disruption to
traffic.
Perform the Forced EPS Switch using the Craft Terminal.

15. Perform the Forced HSB Switch using the Craft Terminal.
16. Perform the Forced Rx Radio Switch using the Craft Terminal.
17. Go to step 21.
18. Perform the Lockout EPS Switch using the Craft Terminal.
19. Perform the Lockout HSB Switch using the Craft Terminal.
20. Perform the Lockout Rx Radio Switch using the Craft Terminal.
21. Verify radio in alarm status is Standby.
22.
Caution: Removing power to an in-service radio in an unprotected link causes
loss of traffic. Removing power to an in-service radio hop in a protected link
requires switching the traffic onto the standby radio hop.
Inspect the power supply cable and cable connections for the radio port in
alarm.
23. Is the power supply cable damaged or improperly connected?

Procedure

24. Re-terminate, repair, or replace power supply cable as required.
26. Did the Low Input Voltage alarm clear?
27. Which unit is providing power to the radio declaring Low Input Voltage
alarm?
a. If MPTACC, go to step 28.
b. If EASv2, go to step 47.
c. If CorEvo, go to step 67.
d. If MSS-1, go to step 79.
e. If MSS-O, go to step 89.
f. If Power Injector Box, go to step 99.
g. If MPT Power Unit, go to step 99.
h. If MPT Extended Power Unit, go to step 99.
i. If Direct connection to Battery, go to step 109.
28. Determine the MPTACC configuration.
a. Does the MPTACC support one or two radio channels?
b. Are the radio channels protected?
c. Is protection available for both radio channels?
29. Verify that radio protection is available for all traffic that is supported by
the MPTACC to reseat/replace or an appropriate maintenance window is
scheduled per local practices and procedures.
30. Is it appropriate to proceed with the Low Input Voltage procedure?
31. Is the MPTACC in alarm in a protected system?
32. Is the card in alarm main or spare?

Procedure
Caution: The following Cautions apply:

• Removing an in-service card in an unprotected link causes loss of traffic.
Removing an in-service card in a protected link requires switching the traffic
onto the protected channel.
• In redundant MPTACC protected radio configurations, the Main MPTACC
card(s) resides in slots 3, 5, and/or 7. The spare MPTACC cards reside in slots
4, 6, and/or 8.
• In single MPTACC protected radio configurations, the Main MPT ODU and the
spare MPT ODU are supported by a single MPTACC card. Reseating/Replacing
an MPTACC card in this configuration causes a loss of traffic. Schedule an
appropriate maintenance window prior to MPTACC replacement per local
practices and procedures.

33.
traffic.

36. Go to step 40.
37.
Caution: Lockout EPS/HSB/RX Radio switching traffic causes a disruption to
traffic.
Perform the Lockout EPS Switch using the Craft Terminal.

40. Verify card in alarm status is Standby.
41.
Caution: Removing an in-service card in an unprotected link causes loss of
traffic.
Physically reseat card in alarm and wait for the status LED to turn steady
green or amber.

Procedure

44. See Alcatel-Lucent 9500 MPR Hardware Installation and Replacement
Manual to replace MPTACC.
47. Determine the EASv2 configuration.
a. Does the EASv2 support more than one radio direction?
b. Are the radio directions protected or unprotected?
c. Are Ethernet ports configured and carrying traffic?
48. Based on the answers to step 47, verify that the appropriate maintenance
window is scheduled per local practices and procedures.
• Removing an in-service card in a protected link requires switching the traffic

onto the protect hop.
• In protected EASv2 radio configurations, the Main EASv2 based radio resides
in slots 3, 5, and/or 7. The spare EASv2 based radio resides in slots 4, 6, and/
or 8.

52.
traffic.

55. Go to step 59.

Procedure
56.
traffic.

60. Repeat steps 50 through 59 for all radios supported by the EASv2 card.
61.
• Removing an in-service EASv2 card WILL cause a loss of ALL unprotected radio
traffic and ALL Ethernet traffic associated with the EASv2 card.
• Removing an in-service radio in an unprotected link causes loss of traffic.
green or amber.
Manual to replace EASv2.
67. Determine the CorEvo configuration.
a. Is the CorEvo configured in a protected core configuration?
b. Does the CorEvo support more than one radio direction?

Procedure
70. Is the CorEvo in a protected system?

a. If yes, perform the Forced EPS Switch using the Craft Terminal. go to
step 71.
71.
Caution: The following Cautions apply: In protected CorEvo configuration, the
Main CorEvo resides in slot 1. The spare CorEvo resides in slot 2.

72. Verify the main CorEvo status is Standby.
73.
Caution: Removing an In-service CorEvo card WILL cause a loss of ALL radio
traffic and ALL unprotected Ethernet traffic associated with the CorEvo card.
Physically reseat the CorEvo card associated with the radio in alarm and
wait for the status LED to turn steady green or amber.
Manual to replace CorEvo.
79. Determine the MSS-1 configuration.
a. Does the MSS-1 support one or more radio channels?
b. Are DS1 ports configured and carrying traffic?
81. Is it appropriate to proceed with the MSS-1 Low Input Voltage alarm
procedure?
82.

Procedure
Caution: Power cycling an in-service MSS-1 shelf WILL cause a loss of ALL traffic
associated with the MSS-1 shelf.
Remove both the A and B fuses supplying power to the MSS-1 shelf in alarm.
83. Wait ten seconds and install both the A and B fuses removed in step 82. Then
wait for the status LED to turn steady green.
Manual to replace MSS-1 shelf.
89. Determine the MSS-O configuration.
a. Does the MSS-O support one or more radio channels?
b. Are Ethernet ports configured and carrying traffic?
91. Is it appropriate to proceed with the MSS-O Low Input Voltage procedure?
92.
Caution: Power cycling an in-service MSS-O shelf WILL cause a loss of ALL
traffic associated with the MSS-O shelf.
Remove power to the MSS-O shelf in alarm.

93. Wait ten seconds and apply power removed in step 92.
Manual to replace MSS-O shelf.

Procedure

99. Does the Power Injector Box/MPT Power Unit/MPT Extended Power Unit
support one or more radio channels?
100. Based on the answer to step 99, verify that the appropriate maintenance
101. Is it appropriate to proceed with the Power Injector Box/MPT Power Unit/
MPT Extended Power Unit Low Input Voltage procedure?
102.
Caution: Power cycling an in-service Power Injector Box/MPT Power Unit/MPT
Extended Power Unit shelf WILL cause a loss of ALL traffic associated with the
Power Injector Box/MPT Power Unit/MPT Extended Power Unit.
Remove power to the Power Injector Box/MPT Power Unit/MPT Extended

Power Unit in alarm.
Manual to replace Power Injector Box/MPT Power Unit/MPT Extended
Power Unit.
109. Inspect the power supply cable connection at the MPT ODU.
110. Is power supply cable damaged or improperly connected?
111. Re-terminate, repair, or replace power supply cable as required.

Procedure

114. Inspect the power supply cable run between the CorEvo/EASv2/MPTACC/
MSS-0/MSS-1/Power Injector Box/MPT Power Unit/MPT Extended Power
Unit/direct Connection to DC Power and MPT ODU.
115. Is the power supply cable damaged?
116. Repair or replace the power supply cable as required.
119. Which card is Low Input Voltage alarm declared? UPDATE!
a. If CorEvo/EASv2/MPTACC, go to step 120.
b. If MSS-0/MSS-1/Power Injector Box/MPT Power Unit/MPT Extended
Power Unit/direct Connection to DC Power, the procedure is
complete.
120. Were Forced/Lockout EPS/HSB/Rx Radio switches established related to
CorEvo/EASv2/MPTACC cards providing power to the radio in alarm?
121.
Caution: Releasing Forced/Lockout EPS/HSB/RX Radio switch causes a
disruption to traffic.
Release the Forced/Lockout EPS Switch using the Craft Terminal.

122. Release the Forced/Lockout HSB Switch using the Craft Terminal.
123. Release the Forced/Lockout Rx Radio Switch using the Craft Terminal.
124. Repeat steps 121 through 123 until all protection switches are released.
1. Inspect the power supply cable connection for radio port in alarm:
a. For EASv2, verify RJ45 connector for PFoE port 1, 2, 3 or 4.
b. For MPTACC, verify RJ45 connector for PFoE port or Coax connector for
QMA port.
c. For MSS-1 CORE, verify RJ45 connector for PFoE port 1 or 2.
d. For MSS-O CORE, verify RJ45 connector for PFoE port 1 or 2.

Procedure
2. Is the power supply cable damaged or improperly connected?

3. Terminate, repair, or replace power supply cable as required.
5. Did the Power Supply Failure alarm clear?
6. Which card is Power Supply Failure alarm declared?
a. If MPTACC, go to step 7.
b. If MSS-1, go to step 26.
c. If MSS-O, go to step 36.
d. If EASv2, go to step 46.
8. Verify that radio protection is available for all traffic that is supported by
the MPTACC to reseat/replace or appropriate maintenance window is
scheduled per local practices and procedures.
9. Is it appropriate to proceed with the MPTACC Power Supply Failure
procedure?

Procedure

card(s) resides in slots 3, 5, and/or 7. The spare MPTACC cards reside in slots
4, 6, and/or 8.
spare MPT ODU are supported by a single MPTACC card. Reseating/Replacing
an MPTACC card in this configuration causes a loss of traffic. Schedule an
appropriate maintenance window prior to MPTACC replacement per local

traffic.
12. Perform the Forced EPS Switch using the Craft Terminal.
15. Go to step 19.
20.
traffic.
green or amber.
Manual to replace MPTACC.

Procedure

26. Determine the MSS-1 configuration.
a. Does the MSS-1 support one or more radio channels?
b. Are DS1 ports configured and carrying traffic?
28. Is it appropriate to proceed with the MSS-1 CORE Power Supply Failure
procedure?
29.
Caution: Power cycling an in-service MSS-1 shelf WILL cause a loss of ALL traffic
associated with the MSS-1 shelf.
Remove both the A and B fuses supplying power to the MSS-1 shelf in alarm.
30. Wait ten seconds and install both the A and B fuses removed in step 29. Then
wait for the status LED to turn steady green.
Manual to replace MSS-1 shelf.
36. Determine the MSS-O configuration.
a. Does the MSS-O support one or more radio channels?
b. Are Ethernet ports configured and carrying traffic?
38. Is it appropriate to proceed with the MSS-O Power Supply Failure procedure?

Procedure

39.
Caution: Power cycling an in-service MSS-O shelf WILL cause a loss of ALL
traffic associated with the MSS-O shelf.
Remove power to the MSS-O shelf in alarm.

Manual to replace MSS-O shelf.
46. Determine the EASv2 configuration.
a. Does the EASv2 support more than one radio direction?
b. Are the radio directions protected or unprotected?
48. Is it appropriate to proceed with the EASv2 Power Supply Failure procedure?
• Removing an in-service card in a protected link requires switching the traffic

• In protected EASv2 radio configurations, the Main EASv2 based radio resides
in slots 3, 5, and/or 7. The spare EASv2 based radio resides in slots 4, 6, and/
or 8.

Procedure

51.
traffic.

54. Go to step 58.
55.
traffic.

59. Repeat steps 50 through 58 for all radios supported by the EASv2 card.
60.
• Removing an in-service EASv2 card WILL cause a loss of ALL unprotected radio
traffic and ALL Ethernet traffic associated with the EASv2 card.
• Removing an in-service radio in an unprotected link causes loss of traffic.
green or amber.
Manual to replace EASv2.

Procedure

66. Inspect the power supply cable connection at MPT ODU.
67. Is power supply cable damaged or improperly connected?
68. Terminate, repair, or replace power supply cable as required.
71. Inspect the power supply cable run between the EASv2/MPTACC/MSS-1/
MSS-O and MPT ODU.
72. Is the power supply cable damaged?
73. Repair or replace the power supply cable as required.
76. Which card is Power Supply Failure alarm declared?
a. If EASv2/MPTACC, go to step 77.
b. If MSS-O/MSS-1, the procedure is complete.
77. Is EASv2/MPTACC in alarm in a protected system?
78.
Caution: Releasing Forced EPS/HSB/RX Radio switch causes a disruption to
traffic.

Secondary Battery Failure
1. Verify that there is no blown fuse providing power to the B-power feed.

Procedure
2. Verify the shelf power cable connections between the MSS-1/8 or MPT-HLS
and the power distribution panel.
3. Verify the B-power connections between the BDFB and power distribution
panel.
4. Verify that the B-power BDFB breakers are in the ON position.
6. Did the Secondary Battery Failure clear?
7. Measure the voltage of the B-power feed.
8. Is the measured voltage within the supported voltage range (MSS-8: -40.8
VDC to -57.6 VDC, MSS-1: +20.0 VDC to +60.0 VDC or -20.0 VDC to -60.0 VDC,
MPT-HLS: +20.4 VDC to +57.6 VDC or -20.4 VDC to -57.6 VDC)
9. Troubleshoot the B-power feed voltage problem.
11. Did the Secondary Battery Failure condition clear?

11 — Equipment alarms
11.1 — Purpose
This procedure describes how to identify and clear Equipment alarms on cards and radios.
11.2 — General
An Excessive Environmental Temperature alarm indicates that excessive temperature on
MPT-HL, MPT-HLC or MPT-HLS card has been detected, or fan unit has failed, or is
missing on MPT-HL.
A Replaceable Unit Missing alarm indicates that a card/SFP is missing or unreachable from
the configured slot/port location.
A Replaceable Unit Problem alarm indicates that a card/SFP failure has been detected
against the indicated card/SFP.
A Replaceable Unit Type Mismatch alarm indicates that a card is present in a slot/port
provisioned for a different card/SFP type.
A Replaceable Unit Type Mismatch alarm indicates that a radio is present on a radio
channel provisioned for a different radio type.
An Unconfigured Equipment Present alarm indicates that a card/SFP is present in an

unprovisioned slot.
An Underlying Resource Unavailable alarm indicates that transmission resources are

affected by an equipment failure.
A Memory Card Forbidden to Use alarm indicates that the procedure to upgrade a Core-E
card to a CorEvo card has been completed but the Core-E card is still in use. No
configuration of the NE can be performed when this alarm is active.
and address and for information about supported temperatures.

Procedure
11.3 — Procedure
2. Review the output. See Table 11.1 for information about equipment alarms.
Table 11.1 — Equipment alarms

Excessive Environmental Temperature
r01/subrack#[3-8][5-8] MPT-HL, MPT-HLC Excessive
connected to EASv2, P8ETH environmental
r01/subrack#1[5-6] MPT-HL, MPT-HLC temperature
connected to Core-E, MSS-1
r01/subrack#1[7-8] MPT-HL, MPT-HLC
connected to CorEvo
r01s[101-102]/board#[1-10] MPT-HLS

Procedure
Table 11.1 — Equipment alarms (Continued)

Replaceable Unit Missing
r01s1/board#[8] AUX Replaceable unit
r01s1/board#[1-2] Core-E, CorEvo missing
r01s1/board#[5,9] FAN, A-FAN, or E-FAN
r01s1/board#[3-8] EASv2, MPTACC, P2E3DS3,
P8ETH, P32E1DS1, SDHACC
r01s1b[1-2]/daughter#[5-6] SFP on Core-E
r01s1b[1-2]/daughter#[5-8] SFP on CorEvo
r01s1/board#1/daughter#4 SFP on MSS-O
r01s1b[3-8]/daughter#[03-04] SFP on MPTACC
r01s1b[3-8]/daughter#[05-08] SFP on EASv2, P8ETH
r01s1b[3-8]/daughter#[01-02] SFP on SDHACC
r01s[3-8][1-4]b1/daughter#03 RPS SFP on MPT ODU
connected to MPTACC
connected to EASv2
r01s1[1-6]b1/daughter#03 RPS SFP on MPT ODU
connected to MSS-O
r01s1[1-4,7-8]b1/daughter#03 RPS SFP on MPT ODU
connected to CorEvo
r01s[101-102]b[1-10]/daughter#3 RPS SFP on MPT-HLS

Procedure

Replaceable Unit Problem
r01s1/board#[1-2] Core-E, CorEvo problem
r01s1/board#[5,9] FAN, A-FAN or E-FAN
r01/subrack#1[1-6] MPT ODU connected to
Core-E, MSS-1
r01/subrack#1[1-4,7-8] MPT ODU connected to
CorEvo
r01/subrack#1[1-3] MPT ODU connected to MSS-
O
r01/subrack#[3-8][1-4] MPT ODU connected to
MPTACC
P8ETH
EASv2
r01/subrack#[3-8][5-8] MPT-HL connected to P8ETH
r01/subrack#1[5-6] MPT-HL connected to
Core-E, MSS-1
CorEvo
r01/subrack#[3-8][5-8] MPT-HLC connected to
EASv2, P8ETH
r01/subrack#1[5-6] MPT-HLC connected to
Core-E, MSS-1
CorEvo
r01s[101-102]/board#[1-10] MPT-HLS
r01s[101-102]/board#[11-12] MPT-HLS Fan card
r01s1b1/daughter#04 SFP on MSS-O

Procedure

Replaceable unit r01s1b[3-8]/daughter#[05-08] SFP on EASv2, P8ETH Replaceable unit
problem (continued) r01s1b[3-8]/daughter#[01-02] SFP for SDHACC problem
connected to MPTACC
connected to EASV2
connected to CorEvo
connected to MSS-O
r01s1[1-6]b1/daughter#04 RPS or XPIC Module on
MPT ODU connected to
Core-E, MSS-1
r01s1[1-4,7-8]b1/daughter#04 RPS or XPIC Module on
CorEvo
r01s1[1-3]b1/daughter#04 RPS or XPIC Module on
MPT ODU connected to MSS-
O
r01/subrack#[3-8][5-8]/daughter#04 XPIC Module on MPT ODU
connected to P8ETH
r01s[3-8][1-4]b1/daughter#04 RPS or XPIC Module on
MPTACC
r01s[3-8][1-4]b1/daughter#04 XPIC Module on MPT ODU
connected to EASV2
r01/subrack#[3-8][5-8]/ RPS or XPIC Module on
daughter#04 MPT ODU connected to
EASV2
r01s1[5-6]b1/daughter#04 Rx Diversity Module on MPT-
HLC connected to Core-E,
MSS-1
r01s1[7-8]b1/daughter#04 Rx Diversity Module on MPT-
HLC connected to CorEvo
r01/subrack#[3-8][5-8]/ Rx Diversity Module on MPT-
daughter#04 HLC connected to EASv2
r01s[101-102]b[1-10]/daughter#04 Rx Diversity Module on MPT-
HLS

Procedure

Replaceable Unit Type Mismatch
r01s1/board#[1-2] Core-E, CorEvo type mismatch
r01s1/board#[5,9] FAN, A-FAN, or E-FAN
Core-E, MSS-1
CorEvo
r01/subrack#1[1-3] MPT ODU connected to MSS-
O
MPTACC
P8ETH
EASv2
r01/subrack#[3-8][5-8] MPT-HL connected to
EASv2, P8ETH
Core-E, MSS-1
CorEvo
EASV2, P8ETH
Core-E, MSS-1
CorEvo
r01s[101-102]/board#[1-10] MPT-HLS

Procedure

Unconfigured Equipment Present
r01s1/board#[8] AUX Unconfigured
r01s1/board#[2] Core-E, CorEvo equipment
r01s1/board#[5,9] FAN, E-FAN, or A-FAN present
r01s1b1/daughter#04 SFP on MSS-O
r01s1b[3-8]/daughter#[05-08] SFP on EASv2, P8ETH
r01s1b[3-8]/daughter#[01-02] SFP on SDHACC
Underlying Resource Unavailable
ETH/Slot#1/Port#[1-6] User Ethernet port on Underlying
Core-E resource
ETH/Slot#1/Port#[1-8] User Ethernet port on unavailable
CoreEvo
ETH/Slot#1/Port#[1-4] User Ethernet port on MSS-O
ETH/MSS/CORE/Port#[1-6] User Ethernet port on MSS-1
ETH/Slot#[3-8]/Port#[1-8] User Ethernet port on EASv2
r01s1b[1-2]/daughter#[05-06] SFP User Ethernet port on
Core-E, MSS-1
CorEvo
r01s1b[1-2]/daughter#04 SFP User Ethernet port on
MSS-O
MSS-1
E1-in#[1-3]-[1-7]-[1-3]/Slot#[3-8]/Port#1 Channelized E1
E1-in/Slot#[3-8]/Port#[1-32] E1 on P32E1DS1
EleSdh-in/Slot#[3-8]/Port#[1-2] OC-3/STM-1
OptSdh-in/Slot#[3-8]/Port#[1-2]
Radio/Dir#1.[1-6]/Slot#1/Port#[1-6]/ MPT ODU connected to
Ch#[0-1] Core-E
Radio/Dir#1.[1-8]/Slot#1/Port#[1-4,7- MPT ODU connected to
8]/Ch#[0-1] CorEvo
Radio/Dir#1.[1-6]/MSS/CORE/Port#[1- MPT ODU connected to MSS-
6]/Ch#[0-1] 1
Radio/Dir#1.[1-3]/Slot#1/Port#[1-3]/ MPT ODU connected to MSS-
Ch#[0-1] O

Procedure

Underlying resource Radio/Dir#[3-8].[1-4]/Slot#[3-8]/ MPT ODU connected to Underlying
unavailable Port#[1-4]/Ch#[0-1] MPTACC resource
(continued) Radio/Dir#[3-8].[5-8]/Slot#[3-8]/ MPT ODU connected to unavailable
Radio/Dir#[3-8].[1-4]/Slot#[3-8]/ MPT ODU connected to
Port#[1-4]/Ch#1 EASv2
Radio/Dir#1.[5-6]/Slot#1/Port#[5-6]/ MPT-HLC, MPT-HLS
Ch#[0-1] connected to Core-E
Ch#[0-1] connected to CorEvo
Radio/Dir#1.[5-6]/MSS/CORE/Port#[5- MPT-HLC, MPT-HLS
6]/Ch#[0-1] connected to MSS-1
Radio/Dir#[3-8].[5-8]/Slot#[3-8]/ MPT-HLC connected to
Port#[5-8]/Ch#[0-1] EASv2, P8ETH
Radio/Dir#[3-8].[5-8]/Slot#[3-8]/ MPT-HLS connected to
Underlying Resource Unavailable Service
E1-in#[1-3]-[1-7]-[1-3]/Slot#[3-8]/Port#1 Channelized E1 Underlying
E1-in/Slot#[3-8]/Port#[1-32] E1 on P32E1DS1 resource
E1-in/MSS/E1/Port#[1-16] E1 on MSS-1 unavailable
service
Ch#[0-1] Core-E
Radio/Dir#1.[1-8]/Slot#1/Port#[1-4,7- MPT ODU connected to
8]/Ch#[0-1] CorEvo
Radio/Dir#1.[1-6]/MSS/CORE/Port#[1- MPT ODU connected to MSS-
6]/Ch#[0-1] 1
Radio/Dir#1.[1-3]/Slot#1/Port#[1-3]/ MPT ODU connected to MSS-
Ch#[0-1] O
Port#[1-4]/Ch#[0-1] MPTACC
Port#[1-4]/Ch#1 EASv2
Ch#[0-1] connected to Core-E
Ch#[0-1] connected to CorEVO

Procedure

Underlying ResourceRadio/Dir#1.[5-6]/MSS/CORE/Port#[5- MPT-HLC, MPT-HLS Underlying
Unavailable Service6]/Ch#[0-1] connected to MSS-1 resource
(continued) Radio/Dir#[3-8].[5-8]/Slot#[3-8]/ MPT-HLC connected to unavailable
Port#[5-8]/Ch#[0-1] EASv2, P8ETH service
Radio/Dir#[3-8].[5-8]/Slot#[3-8]/ MPT-HLS connected to
Memory Card Forbidden to Use
r01s1/board#[1] Core-E Memory Card
Forbidden to Use
None of the above — — Alarm and
abnormal
condition clearing
procedures

• Excessive environmental temperature
• Replaceable unit missing
• Replaceable unit problem
• Replaceable unit type mismatch
• Unconfigured equipment present
• Underlying resource unavailable
• Underlying resource unavailable service
• Memory Card Forbidden to Use
Excessive environmental temperature
1. Verify that the MPT-HL fan card is equipped and operating properly.
2. Is the MPT-HL fan equipped and operating properly?
3. Is the traffic affected?
4. Replace the unit. See the Alcatel-Lucent 9500 MPR Hardware Installation
and Replacement Manual.
6. Did the Excessive Environmental Temperature alarm clear?

Procedure
7. Verify that the building temperature is within acceptable temperature

range.
8. Verify the condition of MPT-HL/MPT-HLC/MPT-HLS shelf air filter and
replace if air filter condition indicates that filter replacement is required.
See Alcatel-Lucent 9500 MPR Hardware Installation and Replacement
Manual to replace the air filter.
9. Verify that no obstruction occurred that prevents proper air flow through
the MPT-HL/MPT-HLC/MPT-HLS unit.
11. Did the Excessive Environmental Temperature alarm clear?
Replaceable unit missing
1. Visually inspect the indicated slot location.
2. Is the slot location empty?
3. Install the card/SFP type corresponding to slot provisioning.
5. Did the Replaceable Unit Missing alarm clear?
6.
Caution: Performing the Restart NE command may cause a disruption to traffic.
Perform the NE restart on the NE: Supervision/Restart NE. Communication

with the NE is lost during the NE restart and you are logged out of the
system.
7. Log into the NE.
9. Did the Replaceable Unit Missing alarm clear?
Replaceable unit problem

Procedure
Caution: Core-E, CorEvo, EASV2, MPTACC, P2E3DS3, P32E1DS1, P8ETH, and SDHACCC
cards support multiple services in both the protected and not protected configuration,
Reseating and replacing any of these cards may cause a loss of traffic on the other services
supported by the card. Schedule an appropriate maintenance window prior to reseating
or replacing cards per local practices and procedures.
1. What equipment type is the Replaceable Unit Problem declared against?

a. If Core-E, CorEvo, P2E3DS3, or P32E1DS1 go to step 37.
b. If FAN, A-FAN, E-FAN, or MPT-HLS fan, go to step TBD.
c. If MPTACC go to step 45.
d. If EASv2, MPT ODU, or P8ETH go to step 50.
e. If MPT-HL, MPT-HLC, or MPT-HLS, go to step 2.
f. If SFP, go to step 74.
g. If RPS SFP on MPT ODU or MPT-HLS, go to step 96.
h. If RPS or XPIC module on MPT ODU go to step 111.
2. Verify that the MPT-HL/MPT-HLC/MPT-HLS PA switch is in the ON ‘1’
position.
3. Is the MPT-HL/MPT-HLC/MPT-HLS PA switch in the ON ‘1’ position?
4. Ready to move the MPT-HL/MPT-HLC/MPT-HLS PA switch to the ON ‘1’
position?
5. When the MPT-HL/MPT-HLC/MPT-HLS PA is in the OFF ‘0’ position, the
Replaceable Unit Problem condition is raised and Tx Mute > Local > Auto >
Enable is displayed on the EAS Main View Settings tab, the procedure is
complete.
6. Position the MPT-HL/MPT-HLC/MPT-HLS PA switch to the ON ‘1’ position.
8. Did the Replaceable Unit Problem alarm clear?
9. Is the MPT-HL/MPT-HLC/MPT-HLS in alarm in a protected system?
Caution: Performing a Manual EPS/HSB/Rx Radio switch causes a disruption to
traffic.

Procedure
10. Is the MPT-HL/MPT-HLC/MPT-HLS in alarm main or spare?

15. Go to step 20.
20.
traffic.

Manual to replace MPT-HL/MPT-HLC/MPT-HLS.
23. Is the MPT-HL/MPT-HLC/MPT-HLS in alarm in a protected system?
24.
Caution: Releasing Forced EPS/HSB/Rx Radio switch causes a disruption to
traffic.

27. Is the protection scheme configured as Not Revertive?

Procedure
Note: To verify that the replaced MPT-HL/MPT-HLC/MPT-HLS is capable of

carrying traffic, the replaced MPT-HL/MPT-HLC/MPT-HLS must be placed in the
Active state.
28.
Caution: Performing a Manual EPS/HSB/Rx Radio switch causes a disruption to
traffic.
Perform the Manual EPS Switch using the Craft Terminal.

29. Perform the Manual HSB Switch using the Craft Terminal.
30. Perform the Manual Rx Radio Switch using the Craft Terminal.
31. Verify that the replaced MPT-HL/MPT-HLC/MPT-HLS status is Active.
32. Verify that the local and far end radio direction are alarm free and
error-free.
33. Are the local and far end alarm free and error-free?
34. Release the Manual EPS Switch using the Craft Terminal.
35. Release the Manual HSB Switch using the Craft Terminal.
36. Release the Manual Rx Radio Switch using the Craft Terminal.
The procedure is complete.
37. Is the card in alarm in a protected system?
Caution: Forced EPS switching traffic causes a disruption to traffic.

40. Verify that the card in the alarm status is Standby.
41. Go to step 61.
44. Go to step 61.

Procedure

d. Is the power to the radio channels provided by the MPTACC card?
46. Verify that the radio protection is available for all traffic supported by the
MPTACC to be replaced or appropriate maintenance window is scheduled
per local practices and procedures.
47. Is it appropriate to proceed with the MPTACC Replaceable Unit Problem
procedure?

card(s) resides in slots 3, 5, and/or 7. The spare MPTACC card(s) resides in
slots 4, 6, and/or 8.
spare MPT ODU are supported by a single MPTACC card. Replacing an MPTACC
card in this configuration causes a loss of traffic. Schedule an appropriate
maintenance window prior to MPTACC replacement per local practices and
procedures.

50. What equipment type is the Replaceable Unit Problem declared against?
a. If MPT ODU go to step 51.
b. If P8ETH, go to step 52.
51. Is the MPT ODU in alarm supported by the Core-E or CorEvo card?
52. Is the MPT ODU in alarm in a protected system?
53. Is the MPT ODU in alarm the main or spare?

Procedure

54.
traffic.

57. Go to step 61.
62.
traffic.
Physically reseat the card in alarm and wait for the status LED to turn steady
green or amber.
65. Replace the equipment the Replaceable Unit Problem is declared against.
See the Alcatel-Lucent 9500 MPR Hardware Installation and Replacement
Manual.
68.
Caution: Releasing EPS switch may cause a disruption to traffic.

Procedure

70.
Caution: Releasing Forced EPS/HSB/RX Radio switch causes a disruption to
traffic.

74. Is the SFP (Ethernet/OC-3/Radio equipment) in alarm protected?
75. Is the SFP in alarm the main or spare?

77. Perform the Forced HSB Switch using the Craft Terminal (radio SFP only).
78. Perform the Forced Rx Radio Switch using the Craft Terminal (radio SFP
only).
80. Go to step 85.
82. Perform the Lockout HSB Switch using the Craft Terminal (radio SFP only).
83. Perform the Lockout Rx Radio Switch using the Craft Terminal (radio SFP
only).
85.
Caution: Removing SFP in an unprotected system causes a loss of traffic on ALL
facilities that are associated with the SFP removed. Schedule an appropriate
maintenance window per local practices and procedures.
Physically reseat the SFP in alarm.


Procedure

Manual to replace SFP in alarm.
91. Is the SFP protected?
92.

93. Release the Forced/Lockout HSB Switch using the Craft Terminal (radio SFP
only).
94. Release the Forced/Lockout Rx Radio Switch using the Craft Terminal (radio
SFP only).
96. Physically reseat the RPS cable at both ends that are associated with RPS
SFP in alarm.
99. Physically reseat the RPS SFP in alarm.
Manual to replace the RPS SFP in alarm.

Procedure

105. Replace the RPS cable that is associated with the RPS SFP in alarm.
Manual to replace MPT ODU associated with RPS SFP in alarm.
Manual to replace RPS/XPIC module in alarm.
Manual to replace MPT ODU associated with RPS/XPIC module in alarm.
Replaceable unit type mismatch
1. Is the Replaceable Unit Type Mismatch alarm declared against an SFP?
2. Visually inspect the indicated slot location.
3. Is the card in indicated slot location the correct card type?
4. Replace the installed card with card type provisioned in Core memory. See
the Alcatel-Lucent 9500 MPR Hardware Installation and Replacement
Manual.

Procedure
6. Did the Replaceable Unit Type Mismatch alarm clear?

7. Reprovision the slot to the correct card type.
10. Using the Craft Terminal, determine the SFP type in alarm.
11. Is the SFP in alarm the correct SFP type as described in the site engineering
documentation?
12. Replace the SFP with the type corresponding to the SFP card slot
provisioning. See Alcatel-Lucent 9500 MPR Hardware Installation and
Replacement Manual to replace an SFP.
15. Reprovision the SFP slot to the correct SFP type.
Unconfigured equipment present
1. Visually inspect the indicated slot/SFP location.
2. Is the indicated slot location equipped with a card/SFP?
3. Is the card/SFP that is equipped in the slot location expected to be there?
4. Provision the slot to the correct card/SFP type.
6. Did the Unconfigured Equipment Present alarm clear?

Procedure

7. Remove the card/SFP from the slot.
8. Install the blank filler panel or face plate into the slot that the card was
removed.
10. Did the Unconfigured Equipment Present alarm clear?
Underlying resource unavailable
2. Evaluate and troubleshoot other alarms on the equipment reporting the
Underlying Resource Unavailable alarm.
3. Did the Underlying Resource Unavailable alarm clear?
Underlying resource unavailable service
2. Evaluate and troubleshoot other alarms on the equipment reporting the
Underlying Resource Unavailable service alarm.
3. Did the Underlying Resource Unavailable service alarm clear?
Memory Card Forbidden to Use
1. Replace the Core-E card with a CorEvo. See the Core-E to CorEvo Upgrade
Procedure document for more information.
2. Did the Memory Card Forbidden to Use alarm clear?

12 — Radio alarms (MPT-HC, MPT-HC-

HQAM, MPT-HL, MPT-HLC, MPT-HLS,
MPT-XP, MPT-XP-HQAM)
12.1 — Purpose
This procedure describes how to identify and clear radio alarms.
12.2 — General
A Bandwidth Over Flow alarm indicates that while the MPT ODU/MPT-HL/MPT-HLC/
MPT-HLS was not communicating with the MSS-1, Core-E, EASv2, MPTACC, or
P8ETH, TDM2TDM and/or TDM2ETH cross-connections were provisioned with a total
bandwidth which exceeds the net bandwidth capacity of the radio profile.
A CLA alarm indicates that the standby transmitter has/had a silent failure which caused
the far end to request a HSB protection switch.
A Demodulator Fail alarm indicates that a loss of receive signal, bad receive signal, or
internal receive circuit failure.
An Early Warning Indication alarm indicates that a 10E-9 Bit Error Rate detected.
A High BER alarm indicates that Bit Error Rate threshold of 10E-4 has been exceeded on
receiver input circuits.
An Incompatible Frequency alarm indicates that the configured frequency is outside the
supported frequency range.
An Incompatible Modulation alarm indicates that the configured modulation is not

supported by MPT ODU/MPT-HL/MPT-HLC/MPT-HLS in alarm.

Procedure
An Incompatible Protection alarm indicates that the RPS/XPIC module is missing or

equipped with a mixture of RPS and XPIC modules on the MPT ODU protection pair in
alarm.
An Incompatible Shifter alarm indicates that the configured shifter value is not supported
by the MPT ODU/MPT-HL/MPT-HLC/MPT-HLS.
An Incompatible Power/Incompatible TX Power alarm indicates that the configured RTPC/

ATPC Tx power value or ATPC Rx power threshold value is not supported by the
MPT ODU/MPT-HL/MPT-HLC/MPT-HLS.
A Link Identifier Mismatch alarm indicates that the link identifier number provisioned on
MPT ODU/MPT-HL/MPT-HLC/MPT-HLS settings screen is different from the link
identifier number provisioned at the far end of the hop.
A Loss Of Protection alarm indicates that a loss the radio direction is affected by a failure
that radio protection (RPS) cannot recover. The alarm is only reported if the RPS is
provisioned.
A Loss Of Signal alarm indicates that a loss of Ethernet signal is detected on the
MPT ODU/MPT-HL/MPT-HLS coupler port.
A PPP Fail alarm indicates that TMN over PPP has failed.
A Remote Defect Indication in a received Radio Direction. The alarm is reported when an
RDI is received on a given radio direction from the remote end of radio link.
and address.
12.3 — Procedure
2. Review the output. See Table 12.1 for information about radio alarms.

Procedure
Table 12.1 — Radio alarms

Bandwidth Over Flow
Radio/Dir#1.[1-6]/ MPT ODU connected to Bandwidth over
Slot#1/Port#[1-6]/Ch#[0-1] Core-E flow
Radio/Dir#1.[1-4,7-8]/ MPT ODU connected to
Slot#1/Port#[1-4,7-8]/Ch#[0-1] CorEvo
Radio/Dir#1.[1-6]/MSS/ MPT ODU connected to
CORE/Port#[1-6]/Ch#[0-1] MSS-1
Radio/Dir#1.[1-3]/ MPT ODU connected to
Slot#1/Port#[1-3]/Ch#1 MSS-O
Radio/Dir#[3-8].[1-4]/ MPT ODU connected to
Slot#[3-8]/Port#[1-4]/Ch#[0-1] MPTACC
Slot#[3-8]/Port#[5-8]/Ch#1 P8ETH
Radio/Dir#[3-8].1-4]/ MPT ODU connected to
Slot#[3-8]/Port#[1-4]/Ch#[1] EASv2
Slot#[3-8]/Port#[5-8]/Ch#[0-1] EASv2
Radio/Dir#1.[5-6]/ MPT-HL connected to
Slot#1/Port#[5-6]/Ch#1 Core-E
Slot#1/Port#[7-8]/Ch#1 CorEvo
Radio/Dir#1.[5-6]/MSS/ MPT-HL connected to
CORE/Port#[5-6]/Ch#1 MSS-1
Radio/Dir#[3-8].[5-8]/ MPT-HL connected to
Slot#[3-8]/Port#[5-8]/Ch#[0-1] EAS
Radio/Dir#1.[5-6]/ MPT-HLC or MPT-HLS
Slot#1/Port#[5-6]/Ch#[0-1] connected to Core-E
Slot#1/Port#[7-8]/Ch#[0-1] connected to CorEvo
Radio/Dir#1.[5-6]/MSS/ MPT-HLC or MPT-HLS
CORE/Port#[5-6]/Ch#[0-1] connected to MSS-1
Radio/Dir#[3-8].[5-8]/ MPT-HLC or MPT-HLS
Slot#[3-8]/Port#[5-8]/Ch#[0-1] connected to EAS

Procedure
Table 12.1 — Radio alarms (Continued)

CLA
Radio/Dir#1.[1-6]/ MPT ODU connected to CLA
Slot#1/Port#[1-6]/Ch#[0-1] Core-E
Slot#[3-8]/Port#[5-8]/Ch#[0-1] EASv2
Slot#[3-8]/Port#[5-8]/Ch#[0-1] EASv2, P8ETH
Radio/Dir#1.[5-6]/ MPT-HLC connected to
Slot#1/Port#[7-8]/Ch#[0-1] CorEvo
Radio/Dir#1.[5-6]/MSS/ MPT-HLC connected to
Radio/Dir#[3-8].[5-8]/ MPT-HLC connected to

Procedure

Demodulator fail
Radio/Dir#1.[1-6]/ MPT ODU connected to Demodulator fail
Slot#1//Port#[1-4,7-8]/Ch#[0-1] CorEvo
Slot#[3-8]/Port#[5-8]/Ch#[0-1] EASv2
Radio/Dir#1.[5-6]/ MPT-HLC, MPT-HLS
Slot#1/Port#[7-8]/Ch#1 connected to CorEvo
Radio/Dir#1.[5-6]/MSS/ MPT-HLC, MPT-HLS
Radio/Dir#[3-8].[5-8]/ MPT-HLC, MPT-HLS

Procedure

Early Warning Indication
Radio/Dir#1.[1-6]/ MPT ODU connected to Early warning
Slot#1/Port#[1-6]/Ch#[0-1] Core-E indication
Slot#[3-8]/Port#[5-8]/Ch#[0-1] P8ETH
Slot#[3-8]/Port#[5-8]/Ch#[0-1] EASv2
Slot#[3-8]/Port#[5-8]/Ch#[0-1] connected to EASv1,
P8ETH

Procedure

High BER
Radio/Dir#1.[1-6]/ MPT ODU connected to High BER
Slot#1/Port#[1-3]/Ch#[0-1] MSS-O
Slot#[3-8]/Port#[5-8]/Ch#[0-1] EASv2

Procedure

Incompatible Frequency
Radio/Dir#1.[1-6]/ MPT ODU connected to Incompatible
Slot#1/Port#[1-6]/Ch#[0-1] Core-E frequency
Slot#[3-8]/Port#[5-8]/Ch#[0-1] EASv2
Radio/Dir#[3-8].[5-8]/ MPT-HLS connected to
Slot#[3-8]/Port#[5-8]/Ch#[0-1] EASv2

Procedure

Incompatible Modulation
Slot#1/Port#[1-6]/Ch#[0-1] Core-E modulation
Slot#[3-8]/Port#[5-8]/Ch#[0-1] EASv2
Slot#[3-8]/Port#[5-8]/Ch#[0-1] P8ETH
Radio/Dir#[3-8].[5-8]/ MPT-HLC or MPT-HLS
Slot#[3-8]/Port#[5-8]/Ch#[0-1] connected to EASv2

Procedure

Incompatible Protection
Slot#1/Port#[1-6]/Ch#[0-1] Core-E protection
Slot#[3-8]/Port#[5-8]/Ch#[0-1] EASv2
Incompatible Shifter
Slot#1/Port#[1-6]/Ch#[0-1] Core-E shifter
Slot#[3-8]/Port#[5-8]/Ch#[0-1] EASv2
Slot#[3-8]/Port#[5-8]/Ch#[0-1] EASv2

Procedure

Incompatible Tx Power
Radio/Dir#1.[1-6]/ MPT ODU connected to Incompatible Tx
Slot#1/Port#[1-6]/Ch#[0-1] Core-E power
Radio/Dir#1.[1-4,7-8]/Slot#1/ MPT ODU connected to
Port#[1-4,7-8]/Ch#[0-1] CorEvo
Slot#[3-8]/Port#[5-8]/Ch#[0-1] EASv2
Slot#[3-8]/Port#[5-8]/Ch#[0-1] P8ETH

Procedure

Link Identifier Mismatch
AirFrame/Dir#1.[1-6]/ MPT ODU connected to Link identifier
Slot#1/Port#[1-6]/Ch#1, Core-E mismatch
Slot#1/Port#[1-6]
AirFrame/Dir#1.[1-4.7-8]/ MPT ODU connected to
Slot#1/Port#[1-4.7-8]/Ch#1, CorEvo
AirFrame/Dir#1.[1-4. 7-8]/Slot#1/
Port#[1-4.7-8]
AirFrame/Dir#1.[1-3]/ MPT ODU connected to
Slot#1/Port#[1-3]/Ch#1, MSS-O
Slot#1/Port#[1-3]
AirFrame/Dir#1.[1-6]/MSS/ MPT ODU connected to
CORE/Port#[1-6]/Ch#1, MSS-1
CORE/Port#[1-6]
AirFrame/Dir#[3-8].[1-4]/ MPT ODU connected to
Slot#[3-8]/Port#[1-4]/Ch#1, MPTACC
Slot#[3-8]/Port#[1-4]
Slot#[3-8]/Port#[5-8]/Ch#1 EASv2, P8ETH
Slot#[3-8]/Port#[5-8]
Slot#[3-8]/Port#[1-4]/Ch#1 EASv2
AirFrame/Dir#1.[5-6]/ MPT-HL connected to
AirFrame/Dir#1.[7-8]/ MPT-HL connected to
AirFrame/Dir#1.[5-6]/MSS/ MPT-HL connected to

Procedure

Link identifier AirFrame/Dir#[3-8].[5-8]/ MPT-HL connected to Link identifier
mismatch Slot#[3-8]/Port#[5-8]/Ch#1, EASv2, P8ETH mismatch
(continued)
Slot#[3-8]/Port#[5-8]
AirFrame/Dir#1.[5-6]/ MPT-HLC, MPT-HLS
Slot#1/Port#[5-6]/Ch#1, connected to Core-E
Slot#1/Port#[5-6]
AirFrame/Dir#1.[7-8]/MSS/ MPT-HLC, MPT-HLS
CORE/Port#[7-8]/Ch#1 connected to CorEvo
AirFrame/Dir#1.[7-8]/MSS/ORE/
Port#[7-8]
AirFrame/Dir#1.[5-6]/MSS/ MPT-HLC, MPT-HLS
CORE/Port#[5-6]/Ch#1, connected to MSS-1
CORE/Port#[5-6]
AirFrame/Dir#[3-8].[5-8]/ MPT-HLC connected to
Slot#[3-8]/Port#[5-8]/Ch#1, EASv2, P8ETH
Slot#[3-8]/Port#[5-8]
AirFrame/Dir#[3-8].[5-8]/ MPT-HLS connected to
Slot#[3-8]/Port#[5-8]/Ch#1, EASv2
Slot#[3-8]/Port#[5-8]

Procedure

Loss of Protection
Radio/Dir#1.[1-6]/ MPT ODU connected to Loss of protection
Port#[1-4,7-8]/Ch#1 CorEvo
Radio/Dir#1.1/Slot#1/Port#1/Ch#1 MPT ODU connected to
MSS-O
Slot#[3-8]/Port#[1-4]/Ch#1 MPTACC
Slot#1/Port#[5-6]/Ch#1 connected to Core-E
CORE/Port#[5-6]/Ch#1 connected to MSS-1
Loss of Signal
r01s1[1-6]b1/daughter#03 RPS SFP on MPT ODU Loss of signal
MSS-1
connected to CorEvo
connected to MSS-O
r01s1[3-8][1-4]b1/ daughter#03 RPS SFP on MPT ODU
connected to EASv2,
MPTACC
MAU/subrack[#3-8].[5-8] Port#n MPT-HL, MPT-HLC
connected to EASv2,
P8ETH
r01s1[101-102]b[1-10]/daughter#03 RPS SFP on MPT-HLS

Procedure

PPP Fail
PPP-IP/RF#1[1-6] MPT ODU connected to PPP fail
Core-E, MSS-1
PPP-IP/RF#1[1-4,7-8] MPT ODU connected to
CorEvo
PPP-IP/RF#1[1-3] MPT ODU connected to
MSS-O
PPP-IP/RF#[3-8][1-4] MPT ODU connected to
EASv2, MPTACC
PPP-IP/RF#[3-8][5-8] MPT ODU connected to
EASv2, P8ETH
PPP-IP/RF#[3-8][5-8] MPT-HL connected to
EASv2, P8ETH
PPP-IP/RF#1[5-6] MPT-HL connected to
Core-E, MSS-1
PPP-IP/RF#1[7-8] MPT-HL connected to
CorEvo
PPP-IP/RF#[3-8][5-8] MPT-HLC connected to
EASv2, P8ETH
PPP-IP/RF#1[5-6] MPT-HLC or MPT-HLS
MSS-1
PPP-IP/RF#1[7-8] MPT-HLC or MPT-HLS
connected to CorEvo
PPP-IP/RF#[3-8][5-8] MPT-HLS connected to
EASv2

Procedure

Radio/Dir#1.[1-6]/ MPT ODU connected to Remote defect
Slot#1/Port#[1-6]/Ch#[0-1] Core-E indication
Port#[1-4,7-8]/Ch#[0-1] CorEvo
Ch#[0-1] MSS-1
Slot#[3-8]/Port#[5-8]/Ch#[0-1] EASv2
Radio/Dir#1.[7-8]/Slot#1/Port#[7-8]/ MPT-HL connected to
Ch#1 CorEvo
Radio/Dir#1.[7-8]/Slot#1/Port#[7-8]/ MPT-HLC or MPT-HLS
Ch#[0-1] connected to CorEvo
Radio/Dir#1.[5-6]/MSS/Slot#[3-8]/ MPT-HLC or MPT-HLS
Port#[5-8]/Ch#[0-1] connected to MSS-1
Slot#[3-8]/Port#[5-8]/Ch#[0-1] EASv2
abnormal condition
clearing
procedures

Procedure
a. Bandwidth over flow

b. CLA
c. Demodulator fail
d. Early warning indication
e. High BER
f. Incompatible frequency
g. Incompatible modulation
h. Incompatible protection
i. Incompatible shifter
j. Incompatible Tx power
k. Link identifier mismatch
l. Loss of protection
m. Loss of signal
n. PPP fail
o. Remote defect indication
Bandwidth over flow
Note: Total Bandwidth provisioned is validated at the add/drop nodes of the network
only. Pass-Through TDM2TDM and/or TDM2ETH flows supported by the NE are not included
in the total bandwidth validation and must be included in the network design to
determine the net bandwidth capacity of the radio profile required.
1. Verify the cross-connections for the radio with Bandwidth Over Flow alarm
and delete TDM2TDM and/or TDM2ETH cross-connections until the total
bandwidth is equal to or less than the net bandwidth capacity of the radio
profile.
2. Retrieve the alarms Using the Alarm Monitor.
3. Did the Bandwidth Over Flow alarm clear?
CLA
1. Attempt to Clear CLA alarm using the manual switch command?
Caution: Performing a Clear CLA command on MPT ODU, MPT-HL, or MPT-HLC
will cause a loss of traffic on ALL facilities associated with the MPT ODU,
MPT-HL, or MPT-HLC declaring CLA alarm IF the silent failure still exist. The
Clear CLA command Forces traffic onto the radio channel in alarm and resets
the CLA alarm. If the silent failure still exists, ALL traffic will be dropped until
the far end requests a HSB protection switch for the link. The traffic outage
duration will be from 30 to 60 seconds. Schedule an appropriate maintenance
window per local practices and procedures.

Procedure
2. Using the Craft Terminal, on the Protection Schemes tab for the local
MPT ODU/ MPT-HL/MPT-HLC, select HSB Protection for the channel
declaring CLA alarm.
3. On the Commands tab, from the New Value drop down, choose Clear CLA.
4. Click on the Apply button. The Switch confirmation window appears.
5. Click on the OK button.
6. Are both receivers at the far end in alarm and traffic affected?
7. Wait two minutes for the CLA alarm to be declared against the MPT ODU,
MPT-HL, MPT-HLC, or MPT-HLS.
9. Is the CLA alarm declared against the MPT ODU, MPT-HL, MPT-HLC, or MPT-
HLS?
10. Replace the MPT ODU, MPT-HL, MPT-HLC, or MPT-HLS CLA declared against.
Manual.
11.
Caution: Performing a Clear CLA command on MPT ODU, MPT-HL, MPT-HLC, or
MPT-HLS will cause a loss of traffic on ALL facilities associated with the
MPT ODU, MPT-HL, MPT-HLC, or MPT-HLS declaring CLA alarm IF the silent
failure still exist. The Clear CLA command Forces traffic onto the radio channel
in alarm and resets the CLA alarm. If the silent failure still exists, ALL traffic is
dropped until the far end requests a HSB protection switch for the link. The
traffic outage duration is 30 to 60 seconds. Schedule an appropriate
Perform the Clear CLA command.

12. Are both receivers at the far end in alarm and traffic affected?
13. Wait two minutes for the CLA alarm to be declared against the MPT ODU,
MPT-HL, MPT-HLC, or MPT-HLS.
15. Is the CLA alarm declared against the MPT ODU, MPT-HL, MPT-HLC, or MPT-
HLS?

Procedure

Demodulator fail
1. Verify that there are no weather-related conditions.
2. Do weather-related conditions exist?
a. If yes, wait for the weather to clear and recheck alarms. The
procedure is complete.
3. Verify that the RF path is clear.
4. Is the RF path clear?
5. Verify that the RSL is above RX threshold.
6. Is the RSL above the RX threshold?
7. Check the upstream transmitter output power and troubleshoot
accordingly.
9. Did the Demodulator Fail alarm clear?
10. Replace the MPT ODU, MPT-HL, or MPT-HLC Demodulator Fail declared
against. See the Alcatel-Lucent 9500 MPR Hardware Installation and
Replacement Manual.
12. Did the Demodulator Fail alarm clear?
Early warning indication
• No action is required at this time. Monitor the receive signal for increased
degrading. The procedure is complete.
High BER
1. Verify that there are no weather-related conditions.
2. Do weather-related conditions exist?
a. If yes, wait for the weather to clear and recheck the alarms. The

Procedure
5. Verify that the RSL is above the RX threshold.
accordingly.
9. Did the High BER alarm clear?
10. Verify that the antenna is aligned.
11. Is the antenna aligned?
b. If no, align the antenna. See Alcatel-Lucent 9500 MPR Turn-up Manual,
Antenna Polarization Verification Antenna Feed-horn Verification -
XPD Procedure.
13. Did the High BER alarm clear?
Incompatible frequency
1. Using the Craft Terminal, retrieve the provisioned frequency value and
supported frequency of the MPT ODU, MPT-HL, MPT-HLC, or MPT-HLS.
2. Verify the required frequency of the microwave link.
3. Is the required microwave link frequency supported by the MPT ODU,
MPT-HL, MPT-HLC, or MPT-HLS?
4. Reprovision the frequency of the MPT ODU, MPT-HL, MPT-HLC, or MPT-HLS
to the required frequency of the microwave link.
6. Did the Incompatible Frequency alarm clear?

Procedure

7.
Caution: Replacing the MPT ODU, MPT-HL, MPT-HLC, or MPT-HLS in an
unprotected facility causes a loss of traffic on ALL facilities that are associated
with the MPT ODU, MPT-HL, MPT-HLC, or MPT-HLS being replaced. Schedule an
Replace the MPT ODU, MPT-HL, MPT-HLC, or MPT-HLS with the version that
supports the required frequency of the microwave link. See the Alcatel-
9. Did the Incompatible Frequency alarm clear?
Incompatible modulation
1. Using the Craft Terminal, retrieve the provisioned modulation value and
supported modulation of the MPT ODU/MPT-HL/MPT-HLC/MPT-HLS.
2. Verify the required modulation of the microwave link.
3. Is the required microwave link modulation supported by the MPT ODU/
MPT-HL/MPT-HLC/MPT-HLS?
4. Reprovision the modulation of the MPT ODU/MPT-HL/MPT-HLC/MPT-HLS to
the required modulation of the microwave link.
6. Did the Incompatible Modulation alarm clear?
7.
Caution: Replacing the MPT ODU, MPT-HL, MPT-HLC, or MPT-HLS in an
with the MPT ODU, MPT-HL, MPT-HLC, or MPT-HLS being replaced. Schedule an
Replace the MPT ODU/MPT-HL/MPT-HLC/MPT-HLS with the version that

supports the required modulation of the microwave link. See the Alcatel-
9. Did the Incompatible Modulation alarm clear?

Procedure

Incompatible protection
1. Visually inspect the main and spare MPT ODU for missing the RPS/XPIC
module.
2. Is the RPS/XPIC module missing?
Manual to install the appropriate RPS/XPIC module.
5. Did the Incompatible Protection alarm clear?
6. Determine the required RPS/XPIC module type.
7. Are both MPT ODUs equipped with the correct RPS/XPIC module?
Manual to replace the incorrect RPS/XPIC module.
Manual to replace the RPS/XPIC module in alarm.
Incompatible shifter
1. Using the Craft Terminal, retrieve the provisioned shifter value and
supported shifter levels of the MPT ODU, MPT-HL, MPT-HLC, or MPT-HLS.
2. Verify the required shifter value of the microwave link.
3. Is the required microwave link shifter level supported by the MPT ODU,
MPT-HL, MPT-HLC, or MPT-HLS?

Procedure
4. Reprovision the shifter value of the MPT ODU/MPT-HL/MPT-HLC/MPT-HLS to
the required shifter value of the microwave link.
6. Did the Incompatible Shifter alarm clear?
7.
Caution: Replacing the MPT ODU/MPT-HL/MPT-HLC/MPT-HLS in an
with the MPT ODU/MPT-HL/MPT-HLC/MPT-HLS being replaced. Schedule an
Replace the MPT ODU/MPT-HL/MPT-HLC/MPT-HLS with version that

supports the required shifter value of the microwave link. See the Alcatel-
9. Did the Incompatible Shifter alarm clear?
Incompatible Tx power
1. Using the Craft Terminal, retrieve the provisioned RTPC/ATPC Tx power
value and ATPC Rx power threshold value and supported transmit power
levels of the MPT ODU/MPT-HL/ MPT-HLC/MPT-HLS.
2. Verify the required transmit power level of the microwave link.
3. Are the required microwave link RTPC/ATPC Tx power levels and ATPC Rx
power threshold levels supported by the MPT ODU/MPT-HL/MPT-HLC/MPT-
HLS?
4. Reprovision the RTPC/ATPC Tx power levels and/or ATPC Rx power
threshold level of the MPT ODU/MPT-HL/MPT-HLC/MPT-HLS to the required
transmit power level of the microwave link.
6. Did the Incompatible TX Power alarm clear?
7.

Procedure
Caution: Replacing the MPT ODU/MPT-HL/ MPT-HLC/MPT-HLS in an

with the MPT ODU/MPT-HL/MPT-HLC/MPT-HLS being replaced. Schedule an
Replace the MPT ODU/MPT-HL/MPT-HLC/MPT-HLS with the version that

supports the required transmit power level of the microwave link. See the
9. Did the Incompatible TX Power alarm clear?
Link identifier mismatch
1. Using the Craft Terminal, retrieve the provisioned Link Identifier values for
the near end and far end of the hop for the alarmed MPT ODU/MPT-HL/
MPT-HLC/MPT-HLS.
2. Verify the required Link Identifier value of the microwave hop.
3. Determine which Link Identifier values are incorrect.
4. Reprovision the Link Identifier values according to the results of step 3.
6. Did the Link Identifier Mismatch alarm clear?
Loss of protection
1. Retrieve the alarms for the local end of the radio direction using the Alarm
Monitor.
2. Determine all of the radio alarms that are declared against the radio
direction declaring the Loss Of Protection and troubleshoot accordingly.
4. Did the Loss Of Protection alarm clear?
5. Retrieve the alarms for the far end of the radio direction using the Alarm
Monitor.
direction declaring the Loss Of Protection and troubleshoot accordingly.
8. Did the Loss Of Protection alarm clear?

Procedure

Loss of signal
1. Verify that the Core-E/CorEvo/EASv2/MPTACC/P8ETH card Ethernet port is
operating normally.
4. Verify the link cabling between the Core-E/CorEvo/EASv2/MPTACC/P8ETH
card or MSS-1 shelf Ethernet port and the MPT ODU/MPT-HL/MPT-HLC/MPT-
HLS.
PPP fail
1. Retrieve the alarms using the Alarm Monitor, verify that no other radio path
alarms (such as Demodulator Fail) exist, and troubleshoot accordingly.
2. Did other radio path alarms exist and were cleared?
4. Did the PPP Fail alarm clear?
5. Check the provisioning of the far end radio card that is associated with card
in alarm, and verify that the PPP RF is enabled.
6. Is the far end radio card PPP RF disabled?
7. Enable the PPP RF at the far end radio card.
10. Verify that the Link Identifiers match at the local and far end radio cards.

Procedure
11. Do the local and far end Link Identifiers match?

12. Determine which Link Identifier is correct.
13. Reprovision the incorrect Link Identifier.
Remote defect indication
1. Retrieve the alarms for the far end of the radio direction using the Alarm
Monitor.
direction associated with the radio direction declaring the Remote Defect
Indication (RDI) and troubleshoot accordingly.
4. Did the RDI alarm clear?

13 — Ethernet alarms (Core-E, CorEvo,

EASv2, MPTACC, P8ETH, MSS-O Shelf,
MSS-1 Shelf)
13.1 — Purpose
This procedure describes how to identify and clear Loss Of Signal on Ethernet ports on the
Core-E, CorEvo, EASv2, MPTACC, P8ETH, MSS-O shelf, or MSS-1 shelf.
13.2 — General
Loss Of Signal alarm indicates that a loss of Ethernet signal is detected on the port or a
communication problem with the remote peer; for example, a link down condition.
and address.
13.3 — Procedure
2. Review the output. See Table 13.1 for information about the Ethernet
alarms.
Table 13.1 — Ethernet alarms

Loss of Signal

Procedure
Table 13.1 — Ethernet alarms (Continued)

TMNEthernet/MngtPort Core-E, CorEvo, MSS-1, Loss of signal
MSS-0 TMN MGMT Port
TMNEthernet/MngtPort#4 Core-E, CorEvo, MSS-1
TMN Port#4
MAU/Slot#[1]/Port#[1-6] Core-E
MAU/Slot#[1]/Port#[1-8] CorEvo
MAU/Slot#1/Port#[1-4] MSS-O
MAU/Slot#1/Port#[1-6] MSS-1
MAU/Slot#[3-8]/Port#[1-4] MPTACC
MAU/Slot#[3-8]/Port#[1-8] EASv2, P8ETH
Bandwidth Degrade for Protection Switch
ERP[1-2]#1-2] Core-E, CorEvo Bandwidth
degrade for
protection
switch
abnormal
condition
clearing
procedures

a. Loss of signal
b. Bandwidth degrade for protection switch
Loss of signal
1. Verify that the link partner is operating normally.
4. Verify the link partner cabling between the Core-E/CorEvo/EASv2/MPTACC/
P8ETH card or MSS-O/MSS-1 shelf and the link partner.
Bandwidth degrade for protection switch
1. Retrieve the alarms for the radio direction on one node of the Ethernet Ring
reporting the Bandwidth degrade using the Alarm Monitor.

Procedure
direction and troubleshoot accordingly.
4. Did the Bandwidth degrade for protection switch alarm clear?
5. Have all nodes in the Ethernet Ring been verified?
b. If no, repeat steps 1 to 4 for the other nodes in the Ethernet Ring.

Procedure

14 — License/software mismatch
14.1 — Purpose
This procedure describes how to identify and clear License/Software Mismatch alarms
(Provisioning Mismatch or Version Mismatch, Standby Version mismatch) on the Core and
on radios.
14.2 — General
A Provisioning Mismatch alarm is declared against a Core-E/CorEvo card or MSS-1/MSS-
O unit indicates that has an incorrect flash card installed on the Core-E/CorEvo card or
MSS-1/MSS-O unit.
A Standby Version Mismatch alarm indicates that the software version on MPT ODU/
MPT-HL/MPT-HLC/MPT-HLS does not match the software version on the Core-E/
CorEvo.
A Version Mismatch alarm declared against a Core-E/CorEvo indicates that an incorrect

Core-E/CorEvo card is installed in the MSS-4 or MSS-8 slot or the software license string
is not loaded on the Core-E/CorEvo card.
A Version Mismatch alarm declared against the MPT ODU/MPT-HL/MPT-HLC/

MPT-HLS indicates that software version on the MPT ODU/MPT-HL/MPT-HLC/MPT-
HLS does not match the software version on the Core-E/CorEvo.
and address.

Procedure
14.3 — Procedure
2. Review the output. See Table 14.1 for information about License/Software
Mismatch alarms.
Table 14.1 — License/software mismatch alarms

Provisioning Mismatch
r01s1/board#[1-2] Core-E, CorEvo Provisioning
r01s1/board#1 MSS-O mismatch
r01/subrack#1[1-6] MPT ODU connected to Standby version
Core-E, MSS-1 mismatch
CorEvo
r01/subrack#1[1-3] MPT ODU connected
MSS-O
MPTACC
P8ETH
EASv2
Core-E, MSS-1
CorEvo
r01/subrack#[3-8][5-8] MPT-HL connected to
EASv2, P8ETH
Core-E, MSS-1
CorEvo
EASv2, P8ETH
r01s[101-102]/board#[1-10] MPT-HLS

Procedure
Table 14.1 — License/software mismatch alarms (Continued)

Version Mismatch
r01s1/board#[1-2] Core-E, CorEvo Version
mismatch
r01s1/board#1 MSS-O Version
r01s1/MSS/CORE MSS-1 mismatch
(License)
r01/subrack#1[1-6] MPT ODU connected to Version
Core-E, MSS-1 mismatch
r01/subrack#1[1-4,7-8] MPT ODU connected to (Software)
CorEvo
MSS-O
EASv2
MPTACC
P8ETH
MSS-1
connected to CorEvo
r01/subrack#[3-8][5-8] MPT-HL, MPT-HLC
connected to EASv2,
P8ETH
EASv2, P8ETH
r01s[101-102]/board#[1-10] MPT-HLS
abnormal
condition
clearing
procedures

a. Provisioning mismatch
b. Standby version mismatch
c. Version mismatch
d. Version mismatch (License)
e. Version mismatch (Software)
Provisioning mismatch

Procedure
1. Replace the Core-E/CorEvo/MSS-1/MSS-O flash card with the correct flash

card for the license. See Alcatel-Lucent 9500 MPR Hardware Installation
and Replacement Manual.
3. Did the Provisioning Mismatch alarm clear?
2. Verify that the Firmware Download On Going is declared against the
3. Is the Firmware Download On Going declared against the MPT ODU/MPT-HL/
MPT-HLC/MPT-HLS?
4. A Firmware Download On Going alarm indicates that the Core-E/CorEvo/
MSS-1 is downloading the correct software to the MPT ODU/MPT-HL/
MPT-HLC/MPT-HLS. Wait at least 30 minutes for the downloading process to
complete.
6. Did the Standby Version Mismatch alarm clear?
Version mismatch
1. Verify that the Core-E/CorEvo card type is installed in the slot declaring
Version Mismatch alarm.
2. Is the Core-E card type Core-E or is the CorEvo card type CorEvo?
3. Replace the Core-B card with the Core-E/CorEvo card. See Alcatel-Lucent
9500 MPR Hardware Installation and Replacement Manual.
5. Did the Version Mismatch alarm clear?
6. Verify the license string that is installed on the NE.
7. Is the license string correct?

Procedure
8. Replace the Core-E/CorEvo card. See Alcatel-Lucent 9500 MPR Hardware
10. Did the Version Mismatch alarm clear?
Version mismatch (License)
2. Verify the license string that is installed on the NE. Contact the next level
of technical support for assistance.
Version mismatch (Software)
2. Verify that a Firmware Download On Going alarm is declared against the
3. Is the Firmware Download On Going declared against the MPT ODU/MPT-HL/
MPT-HLC/MPT-HLS?
4. A Firmware Download On Going alarm indicates the Core-E/CorEvo/MSS/
CORE is downloading the correct software to the MPT ODU/MPT-HL/
MPT-HLC/MPT-HLS. Wait at least 30 minutes for the downloading process to
complete.
6. Did the Version Mismatch or Standby Version Mismatch alarm clear?

Procedure

15 — Internal loss of communications
15.1 — Purpose
This procedure describes how to identify and clear Dialog Failure and Internal
Communication Problem condition on the radio.
15.2 — General
A Dialog Failure alarm manifests itself in two unique time periods.
The first time period a Dialog Failure condition may be declared is during initial turn-up of
a MPT ODU radio. It is an indication that communications between the MPT ODU and the
MSS shelf has been established, but one or more radio parameters has not been provisioned
by the user. During initial turn-up, treat Dialog Failure as an indication one or more radio
parameters require provisioning.
The second time period Dialog Failure condition may be declared is after communications
with the radio has been established and the radio has been provisioned by the user. It
indicates that a temporary loss of communication between the MSS shelf and MPT ODU/
MPT-HL/MPT-HLC exist. A Dialog Failure condition is declared until communications
are reestablished or a time-out period expires. After the time-out period expires, a Dialog
Failure condition is cleared and an Internal Communication Problem condition is declared.
The Dialog Failure time-out durations varies based on the system configuration. The time-
out durations are:
• 1+0: 20 minutes
• 1+1 HSB: 5 minutes
• 1+1 FD: 20 minutes
An Internal Communication Problem condition indicates that a loss of communications

with the MPT ODU/MPT-HL/MPT-HLC/MPT-HLS.

Procedure
Note: After a radio configuration change, such as transition from 1+1 MPT ODU to MPT
ODU with XPIC, in a rare event, a stuck Dialog Failure alarm may occur. If this condition
exists, to clear the Dialog Failure alarm, the associated MPT Access card must be
reseated.
and address.
See the Alcatel-Lucent 9500 MPR WebEML User Manual or the Alcatel-Lucent 9500 MPR
15.3 — Procedure
2. Review the output. See Table 15.1 for information about internal
communication problem alarms.
Table 15.1 — Internal communication problem alarms

Dialog failure
r01/subrack#1[1-6] MPT ODU connected to Dialog failure
Core-E, MSS-1
r01/subrack#1[1-4, 7-8] MPT ODU connected to
CorEvo
MSS-O
EASv2, MPTACC
r01/subrack#[3-8][[5-8] MPT ODU connected to
EASv2, P8ETH
connected to P8ETH
MSS-1
connected to CorEvo
r01s[101-102]/board#[1-10] MPT-HLS

Procedure
Table 15.1 — Internal communication problem alarms (Continued)

Internal Communication Problem
r01/subrack#1[1-6] MPT ODU connected to Internal
Core-E, MSS-1 communication
r01/subrack#1[1-4,7-8] MPT ODU connected to problem
CorEvo
MSS-O
EASv2, MPTACC
EASv2, P8ETH
connected to EASv2,
P8ETH
MSS-1
Radio/Dir#1.[7-8]/ MPT-HL, MPT-HLC
r01s[101-102]/board#[1-10] MPT-HLS
abnormal
condition
clearing
procedures

a. Dialog failure
b. Internal communication problem
Dialog failure
2. Has the appropriate time-out period expired?
b. If no, wait for the appropriate time-out period to expire before
proceeding to step 3.
4. Did the Dialog Failure alarm clear?

Procedure
5. Is an Internal Communication Problem alarm declared?

a. If yes, see Internal communication problem.
6.
Caution: Physically reseating an MPTACC in an unprotected facility causes a
loss of traffic on ALL facilities that are associated with the MPTACC being
reseated. Schedule an appropriate maintenance window per local practices and
procedures.
Reseat the MPTACC card that is associated with the MPT ODU in alarm.
7. Wait for the status LED to turn steady green or amber.
10. Verify radio port provisioning against site documentation.
11. Is the radio port provisioned per site documentation?
12. Verify radio port fiber cabling per site documentation.
13. Is the radio port fiber cabling correct and connected to the correct MPT
type?
14. Correct MPT fiber cable connections per site documentation.
17. Reprovision the radio port per site documentation.
21. Is a Replaceable Unit Problem alarm declared against the MPT ODU/
MPT-HL/MPT-HLC/MPT-HLS in the protection-pair?

Procedure
a. If yes, see Alarm and abnormal condition clearing procedures to clear

the Replaceable Unit Problem.
22. Verify that power is properly supplied to the MPT ODU/MPT-HL/MPT-HLC/
MPT-HLS in alarm. Correct if required.
23. Was a power problem corrected?
26. Is the MPT ODU/MPT-HL/MPT-HLC/MPT-HLS in a protected system?
27.
Caution: Forced EPS and HSB switching traffic causes a disruption to traffic.
Is the MPT ODU/MPT-HL/MPT-HLC/MPT-HLS in alarm the main or spare?

28. Perform a Forced EPS Switch using the Craft Terminal.
29. Perform a Forced HSB Switch using the Craft Terminal.
30. Perform a Forced Rx Radio Switch using the Craft Terminal.
31. Go to step 35.
32. Perform a Lockout EPS Switch using the Craft Terminal.
33. Perform a Lockout HSB Switch using the Craft Terminal.
34. Perform a Lockout Rx Radio Switch using the Craft Terminal.
35.
Caution: Unseating and reseating the communication link between the
MPT ODU/MPT-HL/MPT-HLC and the Core-E/CorEvo/MPTACC/P8ETH card
MSS-1 shelf in an unprotected facility causes a loss of traffic on ALL facilities
that are associated with the MPT ODU/MPT-HL/MPT-HLC. Schedule an

Procedure
Reseat the RJ45/SFP at the Core-E/CorEvo/EASv2/MPTACC/P8ETH, MSS-O/

MSS-1 shelf Core that is associated with the MPT ODU/MPT-HL/MPT-HLC/
MPT-HLS in alarm.
36. Reseat the SFP at the MPT-HL/MPT-HLC/MPT-HLS in alarm.
39. Which card type is declaring Dialog Failure?
a. If MPT ODU, go to step 40.
b. If MPT-HL/MPT-HLC/MPT-HLS, go to step 60.
40. Is the MPT ODU in alarm supported by the Core-E/P8ETH card, MSS-O shelf
Core, or MSS-1 shelf Core?
41. Is there a second radio channel supported by the MPTACC associated with
the MPT ODU in alarm?
42. Is the second radio channel error-free and alarm free?
43.
Caution: Physically removing power to an MPT ODU in an unprotected facility
causes a loss of traffic on ALL facilities that are associated with the MPT ODU
being replaced. Schedule an appropriate maintenance window per local
Power cycle the MPT ODU.

a. If powered using PFoE/QMA through the MPTACC, EASv2, MSS-O shelf
Core, or MSS-1 shelf Core, use the Craft Terminal to disable power, and
then reprovision power.
b. If MPT ODU is powered using PFoE through a Power Injector Card/
Power Injector Box/MPT Extended Power Unit, disconnect the DC+Data
cable connection to the MPT ODU at the power injector card/box. Wait
10 seconds and reconnect.
c. If MPT ODU is powered using coaxial cable with connection to MPT
Power Unit/MPT Extended Power Unit, disconnect the power cable
connection to the MPT ODU at the MPT Power Unit/MPT Extended
Power Unit. Wait 10 seconds and reconnect.

Procedure
d. If MPT ODU is powered with connection to direct office power, locate

the fuse protecting the MPT ODU and remove. Wait 10 seconds and
reinstall the fuse.
46.
Caution: Physically replacing an MPT ODU in an unprotected facility causes a
loss of traffic on ALL facilities that are associated with the MPT ODU being
procedures.
Replace the MPT ODU in alarm. See Alcatel-Lucent 9500 MPR Hardware
49.
Caution: Physically removing an MPTACC/P8ETH/EASv2/Core-E in an
with the MPTACC/P8ETH/EASv2/Core-E being removed. Schedule an
Reseat the MPTACC/P8ETH/EASv2/Core-E/CorEvo card that is associated

with the MPT ODU in alarm.
53.
Caution: Physically replacing an MPTACC/P8ETH/EASv2/Core-E/CorEvo/MSS-O
Core/MSS-1 in an unprotected facility causes a loss of traffic on ALL facilities
that are associated with the MPTACC/P8ETH/EASv2/Core-E/CorEvo/MSS-O/
MSS-1 being replaced. Schedule an appropriate maintenance window per local
Replace the card that is associated with the MPT ODU in alarm. See the

Procedure
57.
Caution: Replacing an MPT ODU in an unprotected facility causes a loss of
traffic on ALL facilities that are associated with the MPT ODU being replaced.
procedures.
60.
Caution: Reseating an MPT-HL/MPT-HLC/MPT-HLS in an unprotected facility
causes a loss of traffic on ALL facilities that are associated with the MPT-HL/
MPT-HLC reseat. Schedule an appropriate maintenance window per local
Position the MPT-HL/MPT-HLC/MPT-HLS PA switch to the OFF ‘0’ position.

61. Remove the fuse in the power distribution panel that is suppling battery
power to the MPT-HL/MPT-HLC/MPT-HLS.
62. Install the fuse in the power distribution panel that is suppling battery
power to the MPT-HL/MPT-HLC/MPT-HLS.
67.
Caution: Replacing an MPT-HL/MPT-HLC/MPT-HLS in an unprotected facility
MPT-HLC/MPT-HLS being replaced. Schedule an appropriate maintenance

Procedure
Replace the card in alarm. See Alcatel-Lucent 9500 MPR Hardware

71. Is the MPT ODU/MPT-HL/MPT-HLC/MPT-HLS in a protected system?
72. Release the Forced/Lockout EPS Switch using the Craft Terminal.
74. Release the Forced/Lockout Rx Radio Switch using the Craft Terminal. The
Internal communication problem
1. Is traffic affected?
2. Has the Internal Communication Problem alarm been active for more than
five minutes?
b. If no, wait five minutes, then go to step 3.
4. Did the Internal Communication Problem alarm clear?
5. Verify radio port provisioning against site documentation.
6. Is the radio port provisioned per site documentation?
7. Verify radio port fiber cabling per site documentation.
8. Is the radio port fiber cabling correct and connected to the correct MPT
type?
9. Correct MPT fiber cable connections per site documentation.

Procedure

12. Reprovision the radio port per site documentation.
15. Is the radio facility protected?
16. Is the MPT ODU/MPT-HL/MPT-HLC/MPT-HLS in alarm main or spare?
Caution: Forced switching traffic causes a disruption to traffic.

20. Go to step 24.
24. Which card is in alarm?
25. Is the MPT ODU in alarm supported by the Core-E/CorEvo/EASv2/P8ETH
card, MSS-O, or MSS-1 shelf?
26. Is there a second radio channel supported by the MPTACC associated with
the MPT ODU in alarm?
27. Is the second radio channel error-free and alarm free?

Procedure

28.
Caution: Physically removing power to an MPT ODU in an unprotected facility
causes a loss of traffic on ALL facilities that are associated with the MPT ODU
being replaced. Schedule an appropriate maintenance window per local

a. If powered through the EASv2, MPTACC or MSS-1 shelf use the Craft
Terminal to disable power, and then reprovision power.
b. If MPT ODU is powered using PFoE through a Power Injector Card/
Power Injector Box/MPT Extended Power Unit, disconnect the DC+Data
cable connection to the MPT ODU at the Power Injector Card/Power
Injector Box/MPT Extended Power Unit. Wait 10 seconds and
reconnect.
c. If MPT ODU is powered using coaxial connection from MPT Power Unit/
MPT Extended Power Unit, disconnect the power cable connection to
the MPT ODU at the MPT Power Unit/MPT Extended Power Unit. Wait
10 seconds and reconnect.
d. If MPT ODU is powered with connection to direct office power, locate
the fuse protecting the MPT ODU and remove. Wait 10 seconds and
reinstall the fuse.
30. Did Internal Communication Problem alarm clear?
31.
procedures.
34.

Procedure
Caution: Physically reseating an MPTACC in an unprotected facility causes a

loss of traffic on ALL facilities that are associated with the MPTACC reseat.
procedures.
Reseat the MPTACC card that is associated with the MPT ODU in alarm.
38.
Caution: Physically replacing an MPTACC in an unprotected facility causes a
loss of traffic on ALL facilities that are associated with the MPTACC being
procedures.
Replace the MPTACC that is associated with MPT ODU in alarm. See Alcatel-
42.
procedures.
45.

Procedure
Caution: Unseating and reseating the communication link between the

MPT-HL/MPT-HLC/MPT-HLS and the P8ETH, Core-E, CorEvo, EASv2 card or
MSS-1 shelf in an unprotected facility causes a loss of traffic on ALL facilities
that are associated with the MPT-HL/MPT-HLC/MPT-HLS. Schedule an
Unseat and reseat the communication link between the MPT-HL/MPT-HLC/

MPT-HLS and P8ETH, Core-E, CorEvo, EASv2, or MSS-1 unit.
48.
Caution: Replacing the communication link between the MPT-HL/MPT-HLC/
MPT-HLS and the P8ETH, EASv2, Core-E card or MSS-1 shelf in an unprotected
facility causes a loss of traffic on ALL facilities that are associated with the
MPT-HL/MPT-HLC/MPT-HLS. Schedule an appropriate maintenance window per
local practices and procedures.
Replace the communication link between the MPT-HL/MPT-HLC/MPT-HLS

and P8ETH, Core-E, CorEvo, EASv2, or MSS-1 unit.
51.
Caution: Reseating an MPT-HL/MPT-HLC/MPT-HLS in an unprotected facility
MPT-HLC/MPT-HLS reseat. Schedule an appropriate maintenance window per
Position the MPT-HL/MPT-HLC/MPT-HLS PA switch to the OFF ‘0’ position.

52. Remove the fuse in the power distribution panel suppling battery power to
the MPT-HL/MPT-HLC/MPT-HLS.
53. Install the fuse in the power distribution panel suppling battery power to the
MPT-HL/MPT-HLC/MPT-HLS.

Procedure
56.
Caution: Replacing an MPT-HL/MPT-HLC in an unprotected facility causes a loss
of traffic on ALL facilities that are associated with the MPT-HL/MPT-HLC/MPT-
HLS being replaced. Schedule an appropriate maintenance window per local
Replace the MPT-HL/MPT-HLC/MPT-HLS in alarm. See the Alcatel-Lucent

59.


16 — Threshold crossing alarms (MPT-HC,

MPT-HC-HQAM, MPT-HL, MPT-HLC, MPT-
HLS, MPT-XP, MPT-XP-HQAM, P32E1DS1,
SDHACC, MSS-1 shelf)
16.1 — Purpose
This procedure describes how to identify Threshold Crossing Alarms (TCA) Threshold
Crossed or Unavailable Time on radios, P32E1DS1, SDHACC cards or MSS-1 shelf.
16.2 — General
TCA alarms are associated with Performance Monitoring (PM). TCA thresholds are default
values or values configured by the user. Depending on the configured TCA threshold
values provisioned, the severity of the TCA alarms are determined. Due to the nature and
flexibility of TCA alarms, only general recommendations can be provided as a course of
action to clear TCA alarms. Follow local practices and procedures in assessing the severity/
importance of TCA alarms.
A TCA declared against a MPT ODU/MPT-HL/MPT-HLC/MPT-HLS/P32E1DS1/

SDHACC/DS1 or E1 on MSS-1 shelf indicates that the alarm threshold has been exceeded;
applies to the PM parameters with an accumulation period of 15 minutes and/or 24 hours
on the MPT ODU/MPT-HL/MPT-HLC/MPT-HLS/P32E1DS1/SDHACC/DS1 or E1 on
MSS-1 shelf.
Single level threshold crossing mechanism is utilized with 24 hour PM TCA alarms. TCA
alarm is raised when 24 hour threshold is exceeded. Implicit clearing of 24 hour TCA
alarms occurs at the beginning of each 24 hour period. No TCA alarm clear message is sent
by the NE.

Procedure
Dual level threshold crossing mechanism is utilized with 15 minute PM TCA alarms. A
TCA alarm is raised when the high threshold is exceeded. An explicit clearing of the TCA
alarm occurs at the end of a 15 minute period where the current data value does not exceed
the low threshold, and the monitoring period does not contain a suspect interval or an
unavailable period. When this occurs, the NE sends TCA alarm clear message.
An Unavailable Time alarm is declared against a MPT ODU/MPT-HL/MPT-HLC/MPT-

HLS/P32E1DS1/SDHACC/DS1 or E1 on MSS-1 shelf which indicates that ten consecutive
SES events have occurred; applies to the PM parameters on the MPT ODU/MPT-HL/
MPT-HLC/MPT-HLS/P32E1DS1/SDHACC/DS1 on MSS-1 shelf.
and address.
16.3 — Procedure
2. Review the output. See Table 16.1 for information about TCA alarms.
Table 16.1 — Threshold crossing alarms

Probable cause Friendly name/entity Equipment type See
Threshold Crossed
Hop/Dir#1[1-6]/Slot#1/ MPT ODU connected to Threshold
Port#[1-6]/Ch#[0-1]-PM15min Core-E crossed
Port#[1-6]/Ch#[0-1]-PM1day
Hop/Dir#1[1-4,7-8]/Slot#1/ MPT ODU connected to
Port#[1-4,7-8]/Ch#[0-1]-PM15min CorEvo
Hop/Dir#1[1-4,7-8]/Slot#1/
Port#[1-4,7-8]/Ch#[0-1]-PM1day
Link/Dir#1[1-4,7-8]-PM15min
Link/Dir#1[1-4,7-8]-PM1day

Procedure
Table 16.1 — Threshold crossing alarms (Continued)

Threshold Crossed Hop/Dir#1[1-3]/Slot#1/Port#[1-3]/ MPT ODU connected to Threshold
(continued) Ch#1-PM15min MSS-O crossed
Hop/Dir#1[1-3]/Slot#1/Port#[1-3]/
Ch#1-PM1day
Hop/Dir#1[1-6]/MSS/CORE/ MPT ODU connected to
Port#[1-6]/Ch#[0-1]-PM15min MSS-1
Hop/Dir#1[1-6]/MSS/CORE/
Hop/Dir#[3-8][1-4]/Slot#[3-8]/ MPT ODU connected to
Port#[1-4]/Ch#[0-1]-PM15min MPTACC
Hop/Dir#[3-8][1-4]/Slot#[3-8]/
Link/Dir#[3-8][1-4]-PM15min
Hop/Dir#[3-8][5-8]/Slot#[3-8]/
Hop/Dir#[3-8][5-8]/Slot#[3-8]/
Port#[5-8]/Ch#1-PM1day test
Port#[1-4]/Ch#[0-1]-PM15min EASv2
Hop/Dir#[3-8][1-4]/Slot#[3-8]/

Procedure

Threshold Crossed Hop/Dir#1[5-6]/Slot#1/ MPT-HL connected to Threshold
(continued) Port#[5-6]/Ch#1-PM15min Core-E crossed
Hop/Dir#1[7-8]/Slot#1/ MPT-HL connected to
Port#[7-8]/Ch#1-PM15min CorEvo
Hop/Dir#1[5-6]/MSS/CORE/ MPT-HL connected to
Hop/Dir#[3-8][5-8]/Slot#[3-8]/ MPT-HL connected to
Port#[5-8]/Ch#[0-1]-PM15min EASv2, P8ETH
Hop/Dir#[3-8][5-8]/Slot#[3-8]/
Hop/Dir#1[5-6]/Slot#1/ MPT-HLC or MPT-HLS
Port#[5-6]/Ch#1-PM15min connected to Core-E
Hop/Dir#1[7-8]/Slot#1/ MPT-HLC or MPT-HLS
Port#[7-8]/Ch#1-PM15min connected to CorEvo
Hop/Dir#1[5-6]/MSS/CORE/ MPT-HLC or MPT-HLS
Port#[5-6]/Ch#1-PM15min connected to MSS-1
Link/Dir#1[5-6]/MSS/CORE-15min
Link/Dir#1[5-6]/MSS/CORE-PM1day

Procedure

Threshold Crossed Hop/Dir#[3-8][5-8]/Slot#[3-8]/ MPT-HLC connected to Threshold
(continued) Port#[5-8]/Ch#[0-1]-PM15min EASv2, P8ETH crossed
Hop/Dir#[3-8][5-8]/Slot#[3-8]/
Hop/Dir#[3-8][5-8]/Slot#[3-8]/ MPT-HLS connected to
Hop/Dir#[3-8][5-8]/Slot#[3-8]/
DS1-in/Slot#[3-8]/Port#[1-32]- DS1 on P32E1DS1
PM15min
DS1-in/Slot#[3-8]/Port#[1-32]-
PM1day
DS1-out/Slot#[3-8]/Port#[1-32]-
PM15min
PM1day
DS1-in/MSS/DS1/Port#[1-16]- DS1 on MSS-1 shelf
PM15min
DS1-in/MSS/DS1/Port#[1-16]-PM1day
DS1-out/MSS/DS1/Port#[1-16]-
PM15min
PM1day
E1-in/Slot#[3-8]/Port#[1-32]- E1 on P32E1DS1
PM15min
E1-in/Slot#[3-8]/Port#[1-32]-PM1day
E1-out/Slot#[3-8]/Port#[1-32]-
PM15min
PM1day
E1-in/MSS/E1/Port#[1-16]-PM15min E1 on MSS-1 shelf
E1-in/MSS/E1/Port#[1-16]-PM1day
E1-out/MSS/E1/Port#[1-16]-PM15min
E1-out/MSS/E1/Port#[1-16]-PM1day

Procedure

Threshold Crossed EleSdh-in/Slot#[3-8]/ STM-1/OC-3 Threshold
(continued) Port#[1-2]-PM15min crossed
Port#[1-2]-PM1day
Port#[1-2]-PM15min
Port#[1-2]-PM1day
Port#[1-2]-PM15min
Port#[1-2]-PM1day
Port#[1-2]-PM15min
Port#[1-2]-PM1day
Unavailable Time
Hop/Dir#1[1-6]/Slot#1/ MPT ODU connected to Unavailable time
Port#[1-6]/Ch#[0-1]-PM15min Core-E
Hop/Dir#1[1-4,7-8]/Slot#1/ MPT ODU connected to
Port#[1-4,7-8]/Ch#[0-1]-PM15min CorEvo
Hop/Dir#1[1-4,7-8]/Slot#1/
Port#[1-4,7-8]/Ch#[0-1]-PM1day
Link/Dir#1[1-4,7-8]-PM15min
Link/Dir#1[1-4,7-8]-PM1day
Hop/Dir#1[1-3]/Slot#1/Port#[1-3]/ MPT ODU connected to
Ch#1-PM15min MSS-O
Hop/Dir#1[1-3]/Slot#1/Port#[1-3]/
Ch#1-PM1day
Hop/Dir#1[1-6]/MSS/CORE/Port# MPT ODU connected to
[1-6]/Ch#[0-1]-PM15min MSS-1

Procedure

Unavailable time Hop/Dir#[3-8][1-4]/Slot#[3-8]/ MPT ODU connected to Unavailable time
(continued) Port#[1-4]/Ch#[0-1]-PM15min MPTACC
Hop/Dir#[3-8][1-4]/Slot#[3-8]/
Hop/Dir#[3-8][5-8]/Slot#[3-8]/
Hop/Dir#[3-8][1-4]/Slot#[3-8]/
Hop/Dir#[3-8][5-8]/Slot#[3-8]/
Port#[5-6]/Ch#1-PM15min Core-E
Port#[7-8]/Ch#1-PM15min CorEvo
Hop/Dir#1[5-6]/MSS/CORE/ MPT-HL connected to
Hop/Dir#[3-8][5-8]/Slot#[3-8]/ MPT-HL connected to
Hop/Dir#[3-8][5-8]/Slot#[3-8]/

Procedure

Unavailable time Hop/Dir#1[5-6]/Slot#1/ MPT-HLC, MPT-HLS Unavailable time
(continued) Port#[5-6]/Ch#1-PM15min connected to Core-E
Hop/Dir#1[7-8]/Slot#1/ MPT-HLC, MPT-HLS
Port#[7-8]/Ch#1-PM15min connected to CorEvo
Hop/Dir#1[5-6]/MSS/CORE/ MPT-HLC, MPT-HLS
Port#[5-6]/Ch#1-PM15min connected to MSS-1
Hop/Dir#[3-8][5-8]/Slot#[3-8]/ MPT-HLC connected to
Hop/Dir#[3-8][5-8]/Slot#[3-8]/
Hop/Dir#[3-8][5-8]/Slot#[3-8]/ MPT-HLS connected to
Hop/Dir#[3-8][5-8]/Slot#[3-8]/
DS1-in/Slot#[3-8]/Port#[1-32]- DS1 on P32E1DS1
PM15min
DS1-in/Slot#[3-8]/Port#[1-32]-
PM1day
PM15min
PM1day

Procedure

Unavailable time DS1-in/MSS/DS1/Port#[1-16]- DS1 on MSS-1 shelf Unavailable time
(continued) PM15min
DS1-in/MSS/DS1/Port#[1-16]-PM1day
PM15min
PM1day
E1-in/Slot#[3-8]/Port#[1-32]- E1 on P32E1DS1
PM15min
E1-in/Slot#[3-8]/Port#[1-32]-PM1day
PM15min
PM1day
E1-in/MSS/E1/Port#[1-16]-PM15min E1 on MSS-1 shelf
E1-in/MSS/E1/Port#[1-16]-PM1day
E1-out/MSS/E1/Port#[1-16]-PM15min
E1-out/MSS/E1/Port#[1-16]-PM1day
EleSdh-in/Slot#[3-8]/ STM-1/OC-3
Port#[1-2]-PM15min
Port#[1-2]-PM1day
Port#[1-2]-PM15min
Port#[1-2]-PM1day
Port#[1-2]-PM15min
Port#[1-2]-PM1day
Port#[1-2]-PM15min
Port#[1-2]-PM1day
None of the above — — —

a. Threshold crossed
b. Unavailable time
Threshold crossed

Procedure
1. Verify the PM data using the Craft Terminal.

2. Verify the radio channel power levels.
4. Determine the local weather conditions that could affect radio
performance.
5. Following local practices and procedures, determine whether corrective
actions are required.
6. Are corrective actions required?
7. Perform corrective actions per local practices and procedures.
9. Did the Threshold Crossed alarm clear?
Unavailable time
1. Verify the PM data using the Craft Terminal.
2. Verify the radio channel power levels.
4. Determine local weather conditions that could affect radio performance.
5. Following local practices and procedures, determine whether corrective
actions are required.
6. Are corrective actions required?
7. Perform corrective actions per local practices and procedures.
9. Did the Unavailable Time alarm clear?

17 — Synchronization alarms (Core-E,

CorEvo, MPT-HC, MPT-HC-HQAM, MPT-HL,
MPT-HLC, MPT-HLS, MPT-XP, MPT-XP-
HQAM, P32E1DS1, SDHACC)
17.1 — Purpose
This procedure describes how to identify and clear synchronization alarms on the Core,
P32E1DS1, and SDHACC cards and on radios.
17.2 — General
A Degrade alarm indicates that the frequency of the sync source signal is degraded.
A Loss Ethernet Synchronization Message Channel (ESMC) alarm indicates a loss of

communication with the far end synchronization source or a provisioning mismatch with
the far end Ethernet port or radio channel. Loss ESMC is applicable to the Core-E/CorEvo
Ethernet ports and Radio interfaces (MPT ODU/MPT-HL/MPT-HLC/MPT-HLS)
configured with SSM support enabled and is assigned as a synchronous clock source input.
A Loss Of Signal alarm indicates that no signal is present on the incoming Sync-in port.
A Synchronization Signal Fail alarm indicates that the received source signal is not
applicable as a Sync Source.
A 1588 TC Fail alarm indicates, due to radio impairments, TC time stamping can not be
guaranteed due to the alignment of the local and remote counters.
and address.

Procedure
17.3 — Procedure
2. Review the output. See Table 17.1 for information about synchronization
alarms.
Table 17.1 — Sync alarms

Degrade
Sync-in/Port#1 Core-E Degrade
Sync-in/Port#[7-8] CorEvo sync SFP Port
Sync-in/Port#[5-6] MSS-1 sync SFP Port
SyncSource/ETH/slot#1/ Core-E User Ethernet
Port#[1-6] Port
SyncSource/ETH/slot#1/ CorEvo User Ethernet
Port#[1-8] Port
SyncSource/ETH/slot#1/ MSS-O User Ethernet
Port#[1-4] Port
SyncSource/ETH/MSS/ MSS-1 User Ethernet
CORE/Port#[1-6] Port
SyncSource/ETH/ EASv2 User Ethernet
slot#[3-8]/Port#[1-8] Port
Slot#1/Port#[1-4,7-8]/Ch#1 CorEvo
Radio/Dir#1. MPT ODU connected to
[1-3]/Slot#1/Port#[1-3]/Ch#1 MSS-O
MSS/CORE/Port#[1-3]/Ch#1 MSS-1
Slot#[3-8]/Port#[1-4]/Ch#1 EASv2, MPTACC

Procedure
Table 17.1 — Sync alarms (Continued)

Degrade (continued) Radio/Dir#[3-8].[5-8]/ MPT-HL, MPT-HLC, Degrade
Slot#[3-8]/Port#[5-8]/Ch#[0-1] MPT-HLS connected to
EASv2, P8ETH
Radio/Dir#1.[5-6]/ MPT-HL, MPT-HLC,
Slot#1/Port#[5-6]/Ch#1 MPT-HLS connected to
Core-E
Radio/Dir#1.[7-8]/ MPT-HL, MPT-HLC,
Slot#1/Port#[7-8]/Ch#1 MPT-HLS connected to
CorEvo
Radio/Dir#1.[5-6]/MSS/ MPT-HL, MPT-HLC,
CORE/Port#[5-6]/Ch#1 MPT-HLS connected to
MSS-1
RadioLAG#[1-14] MPT ODU, MPT-HL,
MPT-HLC, MPT-HLS
connected to EAS
DS1-in/Slot#[3-8]/Port#[1-32] P32E1DS1
DS1in/MSS/DS1/Port#[1-16] MSS-1
E1-in/Slot#[3-8]/Port#[1-32] P32E1DS1
E1in/MSS/E1/Port#[1-16] MSS-1
EleSdh-in/slot#[3-8]/Port[1-2] STM-1/OC-3
OptSdh-in/slot#[3-8]/Port[1-2]
Loss Ethernet Synchronization Messaging Channel
MAU/Slot#[1-2]/Port#[1-6] Core-E Loss Ethernet
MAU/Slot#[1-2]/Port#[1-8] CorEvo synchronizati
MAU/Slot#1/Port#[1-4] MSS-O on messaging
channel
MAU/Slot#[3-8]/Port#[1-8] EASv2
MPT-HLC, MPT-HLS

Procedure

Loss Ethernet Radio/Dir#1.[1-3]/ MPT ODU connected to Loss Ethernet
synchronization Slot#1/Port#[1-3]/Ch#[0-1] MSS-O synchronizati
messaging channel Radio/Dir#1.[1-6]/MSS/ MPT ODU connected to on messaging
(continued) MSS-1 channel
CORE/Port#[1-6]/Ch#[0-1]
Slot#[3-8]/Port#[5-8]/Ch#[0-1] EASv2
Slot#[3-8]/Port#[5-8]/Ch#[0-1] EASv2
Loss of Signal
Sync-in/Port#1 Core-E Loss of signal
Sync-in/Port#[5-6] MSS-1
Sync-in/Port#[7-8] CorEvo

Procedure

Synchronization Signal Fail
Sync-in/Port#1 Core-E Synchronizati
Sync-in/Port#[5-6] MSS-1 on signal fail
Sync-in/Port#[5-8] CorEvo
SyncSource/ETH/ Core-E user Ethernet
Slot#1/Port#[1-6] Port
SyncSource/ETH/ CorEvo user Ethernet
Slot#1/Port#[1-4,7-8] Port
SyncSource/ETH/ MSS-O user Ethernet
Slot#1/Port#[1-4] Port
SyncSource/ETH/MSS/ MSS-1 user Ethernet
CORE/Port#[1-6] Port
SyncSource/ETH/ EASv2 user Ethernet
Slot#[3-8]/Port#[1-8] Port
Slot#1/Port#[1-4,7-8]/Ch#1 CorEv0

Procedure

Synchronization signal fail Radio/Dir#1.[1-6]/MSS/ MPT-HL connected to Synchronizati
(continued) CORE/Port#[1-6]/Ch#1 MSS-1 on signal fail
MPT-HLC, MPT-HLS
DS1-in/Slot#[3-8]/Port#[1-32] DS1 on P32E1DS1
DS1-in/MSS/DS1/Port#[1-16] DS1 on MSS-1
E1-in/Slot#[3-8]/Port#[1-32] E1 on P32E1DS1
EleSdh-in/slot#[3-8]/Port[1-2] STM-1/OC-3
OptSdh-in/slot#[3-8]/Port[1-2]
MS/Slot[3-8]/Port#1 STM-1
1588 TC Fail
Radio/Dir#1.[1-6]/ MPT ODU connected to 1588 TC Fail
Slot#1/Port#[1-4,7-8]/Ch#1 CorEv0
None of the above — —

Procedure

a. Degrade
b. Loss Ethernet synchronization messaging channel
c. Loss of signal
d. Synchronization signal fail
e. 1588 TC Fail
Degrade
1. Degrade
What is the sync source?
a. If Degrade - Sync-In, go to step 2.
b. If Degrade - Radio port, go to step 7.
c. If Degrade - DS1, E1, OC-3, or STM-1 port, go to step 12.
2. Degrade - Sync-In
Verify that the Sync reference source (GPS or other sync source) is
functioning correctly.
3. Verify the Sync-In cabling and connections to the sync-in port on the Core-E,
CorEvo card or MSS-1 unit (main and spare, if equipped).
4. Verify the Sync cabling and connections to the sync-out port on sync source.
6. Did the Degrade Defect alarm clear?
7. Degrade - Radio port
Retrieve the alarms using the Alarm Monitor.
8. Verify that no other radio path alarms, such as Demodulator Fail. If radio
path alarms exist, troubleshoot accordingly.
9. Did the other radio path alarms exist and were they cleared?
12. Degrade - DS1, E1, OC-3, or STM-1 port
13. Verify that no LOS alarm exists on the sync reference DS1, E1, OC-3, or STM-
1 port. If a LOS alarm exists, troubleshoot accordingly.

Procedure
14. Did an LOS alarm exist on the sync reference DS1, E1, OC-3, or STM-1 port
and was it cleared?
17. Verify that the sync reference DS1, E1, OC-3, or STM-1 port frequency is
correct. If the sync reference frequency is not correct, troubleshoot
accordingly.
18. Was a sync reference DS1, E1, OC-3, or STM-1 port frequency problem
identified and was it corrected?
21. Verify that the sync source provisioning at both the sync source and the
alarming card is correct.
24. Replace the card/SFP the Degrade Defect alarm is declared against. See the
Loss Ethernet synchronization messaging channel
2. Verify no radio or Ethernet alarms are declared against the radio direction
declaring Loss ESMC.
3. Are radio or Ethernet alarms declared against the radio direction or
Ethernet port?

Procedure

radio or Ethernet alarms declared against the radio direction or
Ethernet port.
4. Using the Craft Terminal retrieve the provisioned Synchronization SSM
values for both near end and far end of the Ethernet port or radio hop for
the alarmed synchronization port supported on a Core-E/CorEvo/EASv2/
MSS-1/MSS-O/MPT ODU/MPT-HL/MPT-HLC/MPT-HLS.
5. Verify the desired Synchronization SSM value of the microwave hop.
6. Determine which Synchronization SSM value is correct.
7. Reprovision the Synchronization SSM value according to the results of
step 6.
9. Did the Loss ESMC alarm clear?
Loss of signal
1. Verify sync source provisioning at both the sync source and the alarming
card.
b. f no, go to step 4.
4. Verify Sync reference source (GPS or other sync source) is functioning
properly.
5. Verify Sync-In cabling and connections to sync-in port on Core-E/CorEvo
card or MSS-1 shelf (Main and Spare if equipped).
b. f no, go to step 8.
8. Is traffic affected?
9. What is the unit declaring Loss of Signal?
a. If CorEvo card or MSS-1 shelf, go to step 10.
b. If Core-E card, go to step 16.
10.

Procedure
Caution: Reseating an sync SFP will cause a hit to traffic.
Reseat the sync SFP.

13.
Caution: Replacing a sync SFP will cause a hit to traffic.
Replace the Sync SFP declaring Loss Of Signal. See the Alcatel-Lucent
16. Is Core-E in a protected system?
17.
Caution: Forced/Lockout EPS switching Core-E will cause a hit to traffic.
Is Core-E card in alarm main or spare?

19. Go to step 21.
21.
Caution: Reseating an unprotected Core-E card will cause a hit to traffic.
Reseat the Core-E card declaring Loss Of Signal.

Procedure

24.
Caution: Replacing an unprotected Core-E card will cause a hit to traffic.
Replace the Core-E card declaring Loss Of Signal. See the Alcatel-Lucent
27. Is Core-E in a protected system?
Synchronization signal fail
2. Verify Degrade, Loss ESMC, or Loss of Signal are not also declared against
Sync source declaring Synchronization Signal Fail.
3. Are Degrade, Loss ESMC, or Loss of Signal also declared against synch
source?
a. If yes, see Table 17.1 and clear other Sync alarms before proceeding
to step 4.
5. Did the Synchronization Signal Fail alarm clear?
6. What is the sync source?
a. If Sync-in, go to step 7.
b. If Radio port, go to step 12.
c. If DS1, E1, OC-3 or STM-1 port, go to step 19.

Procedure
7. Sync-in
Verify Sync reference source (GPS or other sync source) is functioning
properly.
8. Verify Sync-In cabling and connections to sync-in port on Core-E card, sync
SFP on CorEvo card or MSS-1 shelf (Main and Spare if equipped).
9. Verify Sync cabling and connections to sync-out port on sync source.
12. Radio port
13. Verify no radio alarms are declared against the radio direction declaring
Synchronization Signal Fail.
14. Are radio alarms declared against the radio direction?
radio alarms declared against the radio direction.
15. Verify no other radio path alarms exist. If radio path alarms exist,
19. DS1, E1, OC-3 or STM-1 port
20. Verify no LOS alarm exists on sync reference DS1, E1, OC-3, or STM-1 port.
If LOS alarm exists, troubleshoot accordingly.
21. Did the an LOS alarm exist on sync reference DS1, E1, OC-3, or STM-1 port
and was it cleared?

Procedure

24. Verify sync reference DS1 or OC-3 port frequency is correct. If sync
reference frequency is not correct, troubleshoot accordingly.
25. Was a sync reference DS1 or OC-3 port frequency problem identified and
was it corrected?
28. Verify sync source provisioning at both the sync source and the alarming
card.
31. Replace the card the Synchronization Signal Fail alarm is declared against.
Manual.
1588 TC Fail
2. Verify that no other radio path alarms, such as Demodulator Fail. If radio
path alarms exist, troubleshoot accordingly.
b. If no, contact the next level of technical support for assistance
5. Did the 1588 TC Fail alarm clear?
b. If no, contact the next level of technical support for assistance

Procedure

18 — ATPC loop condition (MPT-HC, MPT-

HC-HQAM, MPT-HL, MPT-HLC, MPT-HLS,
18.1 — Purpose
This procedure describes how to identify and clear ATPC loop condition (ATPC high
power timeout and Loop Problem) on radios.
18.2 — General
An ATPC high power timeout alarm indicates that the local transmitter was operating
continuously at full power for 5-minutes, and the transmitter power was reduced to its
minimum power setting.
A Loop Problem alarm indicates that loss of ATPC command path between the far end
transmitter and local receiver.
and address.
18.3 — Procedure
1. Using the Alarm Monitor, retrieve all alarm.
2. Review the output. See Table 18.1 for information about ATPC Loop
conditions.

Procedure
Table 18.1 — ATPC loop conditions

RadioTxPower/Dir#1.[1-6]/ MPT ODU connected to ATPC High Power
Slot#1/Port#[1-6]/Ch#[0-1] Core-E Timeout
RadioTxPower/Dir#1.[1-4,7-8]/ MPT ODU connected to
RadioTxPower/Dir#1.[1-6]/MSS/ MPT ODU connected to
RadioTxPower/Dir#1.[1-3]/ MPT ODU connected to
RadioTxPower/Dir#[3-8].[1-4]/ MPT ODU connected to
RadioTxPower/Dir#[3-8].1-4]/ MPT ODU connected to
Slot#[3-8]/Port#[5-8]/Ch#[0-1] EASv2
RadioTxPower/Dir#1.[5-6]/ MPT-HL connected to
RadioTxPower/Dir#1.[7-8]/Slot#1/ MPT-HL connected to
Port#[7-8]/Ch#1 CorEvo
RadioTxPower/Dir#1.[5-6]/MSS/ MPT-HL connected to
RadioTxPower/Dir#[3-8].[5-8]/ MPT-HL connected to
RadioTxPower/Dir#1.[5-6]/ MPT-HLC connected to
RadioTxPower/Dir#1.[7-8]/Slot#1/ MPT-HLC connected to
Port#[7-8]/Ch#[0-1] CorEvo
RadioTxPower/Dir#1.[5-6]/MSS/ MPT-HLC connected to
RadioTxPower/Dir#[3-8].[5-8]/ MPT-HLC connected to

Procedure
Table 18.1 — ATPC loop conditions (Continued)

Loop Problem
Radio/Dir#1.[1-6]/ MPT ODU connected to Loop Problem
Slot#[3-8]/Port#[5-8]/Ch#[0-1] EASv2
RadioTxPower/Dir#1.[7-8]/Slot#1/ MPT-HL connected to
Port#[7-8]/Ch#1 CorEvo
Slot#[3-8]/Port#[5-8]/Ch#[0-1] EASv2
condition clearing
procedures

Procedure

a. ATPC High Power Timeout
b. Loop Problem
1. Using the Craft Terminal, determine whether the local transmit power is at
minimum power setting.
2. Is the local transmit power at its minimum power setting?
3. Troubleshoot the RF path from the near end transmitter to the far end
receiver.
5. Did the ATPC high power timeout alarm clear?
Loop Problem
1. Is the system configured with protection?
3.
Perform a Forced EPS Switch at the near end transmitter using the Craft
Terminal.
4. Perform a Forced HSB Switch at the near end transmitter using the Craft
Terminal.
5. Perform a Forced Rx Radio Switch at the near end transmitter using the
Craft Terminal.
6. Go to step 10.
7.

Procedure
Perform a Lockout EPS Switch at the near end transmitter using the Craft
Terminal.
8. Perform a Lockout HSB Switch at the near end transmitter using the Craft
Terminal.
9. Perform a Lockout Rx Radio Switch at the near end transmitter using the
Craft Terminal.
11. Did the Loop Problem alarm clear?
12.
Replace the MPT ODU, MPT-HL, MPT-HLC, or MPT-HLS in alarm at the near
end. See the Alcatel-Lucent 9500 MPR Hardware Installation and
Replacement Manual.
15. Release the Forced EPS Switch at the near end transmitter using the Craft
Terminal.
16. Release the Forced HSB Switch at the near end transmitter using the Craft
Terminal.
17. Release the Forced Rx Radio Switch at the near end transmitter using the
Craft Terminal.
18. Go to step 22.
19. Release the Lockout EPS Switch at the near end transmitter using the Craft
Terminal.
20. Release the Lockout HSB Switch at the near end transmitter using the Craft
Terminal.
21. Release the Lockout Rx Radio Switch at the near end transmitter using the
Craft Terminal.
23. Did the Loop Problem alarm return?

Procedure

25.
Is the card in alarm main or spare?

26. Perform a Forced EPS Switch at the far end transmitter using the Craft
Terminal.
27. Perform a Forced HSB Switch at the far end transmitter using the Craft
Terminal.
28. Perform a Forced Rx Radio Switch at the far end transmitter using the Craft
Terminal.
29. Go to step 33.
30. Perform a Lockout EPS Switch at the far end transmitter using the Craft
Terminal.
31. Perform a Lockout HSB Switch at the far end transmitter using the Craft
Terminal.
32. Perform a Lockout Rx Radio Switch at the far end transmitter using the Craft
Terminal.
34. Did the Loop Problem alarm clear?
35.
Replace the MPT ODU, MPT-HL, MPT-HLC, or MPT-HLS at the far end. See
Manual.

Procedure

38. Release the Forced EPS Switch at the far end transmitter using the Craft
Terminal.
39. Release the Forced HSB Switch at the far end transmitter using the Craft
Terminal.
40. Release the Forced Rx Radio Switch at the far end transmitter using the
Craft Terminal.
41. Go to step 45.
42. Release the Lockout EPS Switch at the far end transmitter using the Craft
Terminal.
43. Release the Lockout HSB Switch at the far end transmitter using the Craft
Terminal.
44. Release the Lockout Rx Radio Switch at the far end transmitter using the
Craft Terminal.
46. Did the Loop Problem alarm return?

Procedure

19 — DemXPIC LOS
19.1 — Purpose
This procedure describes how to identify and clear the DemXPIC LOS alarm.
19.2 — General
The DemXPIC LOS condition indicates that a bad or missing cable or cable connection at
the XPIC connector on the MPT-HC/MPT-HC-HQAM/MPT-XP/MPT-XP-HQAM/
(MPT ODU), MPT-HLC, and MPT-HLS.
and address.
19.3 — Procedure
2. Review the output. See Table 19.1 for information about clear radio alarms.

Procedure
Table 19.1 — Clear radio alarms

DemXPIC LOS
r01s1/b1[1-6]/daughter#04 MPT ODU connected to DemXPIC LOS
Core-E, MSS-1
r01s1b1[1-4,7-8]/daughter#04 MPT ODU connected to
CorEvo
r01s1b1[1-3]/daughter#04 MPT ODU connected to
MSS-O
r01s1/b[3-8][1-4]/daughter#04 MPT ODU connected to
MPTACC
r01s[3-8][5-8]b1/daughter#04 MPT ODU connected to
EASv2, P8ETH
Core-E, MSS-1
CorEvo
EASv2
r01s[101-102]/board#[1-10] MPT-HLS
condition clearing
procedures
DemXPIC LOS
1. Inspect the XPIC cable is properly terminated, securely connected, and the
cable is not damaged.
2. Is the XPIC cable not properly terminated, connected, or the cable is
damaged?
3. Repair or replace the XPIC cable.
5. Did the DemXPIC LOS alarm clear?
6. Reseat the XPIC cable on the horizontal and vertical MPT ODU/MPT-HLC.

Procedure
9. Replace the XPIC cable between the horizontal and vertical MPT ODU/
MPT-HLC.
12. Reseat the XPIC module on horizontal MPT ODU. See the Alcatel-Lucent
9500 MPR Hardware Installation and Replacement Manual to reseat the
XPIC module.
15. Reseat the XPIC module on the vertical MPT ODU. See the Alcatel-Lucent
9500 MPR Hardware Installation and Replacement Manual to reseat the
XPIC module.
18. Replace the XPIC module on the horizontal MPT ODU. See Alcatel-Lucent
9500 MPR Hardware Installation and Replacement Manual to replace the
XPIC module.
21. Replace the XPIC module on vertical MPT ODU. See the Alcatel-Lucent
XPIC module.
24. Replace the horizontal MPT ODU. See the Alcatel-Lucent 9500 MPR
Hardware Installation and Replacement Manual to replace the MPT ODU.

Procedure

27. Replace the vertical MPT ODU. See Alcatel-Lucent 9500 MPR Hardware
Installation and Replacement Manual to replace the MPT ODU.

20 — Loss of alignment (MPT-HC, MPT-HL,

MPT-HLC, MPT-HLS, MPT-XP)
20.1 — Purpose
This procedure describes how to identify and clear Loss Of Alignment alarm on the radio.
20.2 — General
A Loss Of Alignment alarm indicates that a delay/loss of alignment between the main and
protect RF paths is detected.
and address.
20.3 — Procedure
2. Review the output. See Table 20.1 for information about Loss of Alignment
alarms.
Table 20.1 — Loss of alignment alarms

Loss of Alignment

Procedure
Table 20.1 — Loss of alignment alarms (Continued)

Hitless/Dir#1.[1-6] MPT ODU connected to Loss of alignment
Core-E, MSS-1
Hitless/Dir#1.[1-4,7-8] MPT ODU connected to
CorEvo
Hitless/Dir#1.[1-2] MPT ODU connected to
MSS-O
Hitless/Dir#[3-8].[1-4] MPT ODU connected to
MPTACC
Hitless/Dir#[3-8].[5-8] MPT ODU connected to
EASv2
Hitless/Dir#[3-8].[5-8] MPT-HL connected to
EASv2, P8ETH
Hitless/Dir#1.[1-6] MPT-HLC, MPT-HLS
MSS-1
Hitless/Dir#1.[7-8] MPT-HLC, MPT-HLS
connected to CorEvo
Hitless/Dir#[3-8].[5-8] MPT-HLC connected to
EASv2, P8ETH
Hitless/Dir#[3-8].[5-8] MPT-HLS connected to
EASv2
abnormal condition
clearing procedures
Loss of alignment
1. Verify that the MPT ODU/MPT-HL/MPT-HLC/MPT-HLS in alarm status is
Standby.
2. Is the MPT ODU/MPT-HL/MPT-HLC/MPT-HLS in alarm main or spare?
3.
Perform a Forced EPS Switch using the Craft Terminal.

6. Go to step 10.
7.

Procedure
Perform a Lockout EPS Switch using the Craft Terminal.

10. Which unit is in alarm?
a. If MPT ODU go to step 11.
11. MPT ODU
Remove power to the MPT ODU. If powered through the EASv2, MPTACC or
MSS-1, MSS-O shelf, use the Craft Terminal to disable power, and then
reprovision power. If externally powered, disconnect power to the MPT ODU
in alarm and then reconnect power.
13. Did the Loss Of Alignment alarm clear?
14.
by the Core-E, CorEvo, EASv2, MPTACC, P8ETH card or MSS-1, MSS-O shelf,
associated with the facility in alarm. Schedule an appropriate maintenance
Reseat the Core-E, CorEvo, EASv2, MPTACC or P8ETH card, or MSS-1, MSS-O
shelf that is associated with MPT ODU in alarm.
the MSS-1 shelf and remove. Wait ten seconds. Then install the fuses
15. Wait for the status LED to turn steady amber.
18. See the Alcatel-Lucent 9500 MPR Hardware Installation and Replacement
Manual to replace the card that reported the Loss Of Alignment alarm.

Procedure

22. Replace the MPT ODU in alarm. See Alcatel-Lucent 9500 MPR Hardware
Installation and Replacement Manual to replace MPT ODU.
25. MPT-HL/MPT-HLC/MPT-HLS
Position the MPT-HL/MPT-HLC/MPT-HLS Transceiver PA switch to the OFF
‘0’ position.
26. Remove the fuse in the power distribution panel that supplies battery power
to the MPT-HL/MPT-HLC/MPT-HLS transceiver.
27. Install the fuse in the power distribution panel that supplies battery power
to the MPT-HL/MPT-HLC/MPT-HLS transceiver.
28. Position the MPT-HL/MPT-HLC/MPT-HLS Transceiver PA switch to the ON ‘1’
position.
32. Replace the MPT-HL/MPT-HLC/MPT-HLS in alarm. See the Alcatel-Lucent
MPT-HL/MPT-HLC/MPT-HLS.
The procedure is completed.

21 — Loss of frame (MPT-HC, MPT-HC-

21.1 — Purpose
This procedure describes how to identify and clear Loss of Frame radio alarms.
21.2 — General
A Loss Of Frame alarm indicates the BER has increased to the point that frames are being
lost. Probable causes include far end transmitter problems, RF path problems, or local card
failures.
and address.
21.3 — Procedure
2. Review the output. See Table 21.1 for information about Loss of Frame
radio alarms.

Procedure
Table 21.1 — Loss of frame radio alarms

Radio/Dir#1.[1-6]/ MPT ODU connected to Loss of frame
Slot#1/Port#[1-4,7-8]/Ch#[0-1 CorEvo
Slot#[3-8]/Port#[5-8]/Ch#[0-1] EASv2
Slot#[3-8]/Port#[5-8]/Ch#[0-1] EASv2
abnormal condition
clearing
procedures

Procedure
Loss of frame
3. Verify that there are no weather-related problems.
4. Do weather-related problems exist?
a. If yes, wait for the weather to clear and recheck alarms. The
7. Verify that the RSL is above the RX threshold.
accordingly.
13. Unprotected radio configuration
Is the traffic affected?
b. If MPT-HL/MPT-HLC, go to step 40.
15. MPT ODU
Is the MPT ODU in alarm supported by the Core-E, EASv2, P8ETH card, MSS-
O shelf, or MSS-1 shelf?
16. Is there a second radio channel, at the local and/or at the far end,
supported by the MPTACC associated with the MPT ODU in alarm?

Procedure

17. Is the second radio channel, at the local or at the far end, error-free and
alarm free?
18. Reseat the local MPTACC that is associated with the MPT ODU in alarm.
22. Reseat the far end MPTACC that is associated with the MPT ODU in alarm.
26. Replace the local MPTACC that is associated with the MPT ODU in alarm. See
Manual to replace the MPTACC.
30. Replace the far end MPTACC that is associated with the MPT ODU in alarm.
34. Replace the local MPT ODU in alarm. See Alcatel-Lucent 9500 MPR

Procedure

37. Replace the far end MPT ODU in alarm. See Alcatel-Lucent 9500 MPR
Position the local MPT-HL/MPT-HLC/MPT-HLS Transceiver PA switch to the
OFF ‘0’ position.
41. Remove fuse in power distribution panel suppling battery power to local
MPT-HL/MPT-HLC/MPT-HLS Transceiver.
42. Install fuse in power distribution panel suppling battery power to local
43. Position the local MPT-HL/MPT-HLC/MPT-HLS Transceiver PA switch to the
ON ‘1’ position.
45. Position the far end MPT-HL/MPT-HLC/MPT-HLS Transceiver PA switch to
the OFF ‘0’ position.
46. Remove fuse in power distribution panel suppling battery power to far end
47. Install fuse in power distribution panel suppling battery power to far end
the ON ‘1’ position.
50. Replace the local MPT-HL/MPT-HLC/MPT-HLS. See the Alcatel-Lucent

Procedure
52. Replace the far end MPT-HL. See the Alcatel-Lucent 9500 MPR Hardware
Installation and Replacement Manual to replace the MPT-HL/MPT-HLC/
MPT-HLS Transceiver.
54. Protected radio configuration
Determine the status of the MPT ODU/MPT-HL/MPT-HLC/MPT-HLS declaring
the Loss Of Frame alarm.
a. If Active, go to step 55.
b. If Standby, go to step 56.
56. Is the MPT ODU/MPT-HL/MPT-HLC/MPT-HLS declaring the Loss Of Frame
alarm the main or spare?
57. Perform a Forced Rx Radio Switch using the Craft Terminal on the local
58. Perform a Forced Equipment Switch using the Craft Terminal on the local
59. Perform a Forced HSB Switch using the Craft Terminal on the far end
60. Go to step 64.
61. Perform a Lockout Rx Radio Switch using the Craft Terminal on the local
62. Perform a Lockout Equipment Switch using the Craft Terminal on the local
63. Perform a Lockout HSB Switch using the Craft Terminal on the far end
64. Which unit is in alarm?
65. MPT ODU
Is the MPT ODU in alarm supported by the Core-E, EASv2, P8ETH card, MSS-1
Shelf or MSS-O Shelf?

Procedure

66. Is there a second radio channel, at the local and/or at the far end,
supported by the MPTACC that is associated with the MPT ODU in alarm?
67. Is the second radio channel, at the local or at the far end, error-free and
alarm free?
68. Reseat the local MPTACC that is associated with the MPT ODU in alarm.
72. Reseat the far end MPTACC that is associated with MPT ODU in alarm.
76. Replace the local MPTACC that is associated with MPT ODU in alarm. See the
Alcatel-Lucent 9500 MPR Hardware Installation and Replacement Manual to
replace the MPTACC.
80. Replace the far end MPTACC that is associated with MPT ODU in alarm. See

Procedure
84. Replace the local MPT ODU in alarm. See the Alcatel-Lucent 9500 MPR
87. Replace the far end MPT ODU in alarm. See the Alcatel-Lucent 9500 MPR
Position the local MPT-HL/MPT-HLC/MPT-HLS Transceiver PA switch to the
OFF ‘0’ position.
power to the local MPT-HL/MPT-HLC/MPT-HLS transceiver.
power to the local MPT-HL/MPT-HLC/MPT-HLS transceiver.
93. Position the local MPT-HL/MPT-HLC/MPT-HLS Transceiver PA switch to the
ON ‘1’ position.
96. Remove the fuse in the power distribution panel that is supplying battery
power to the far end MPT-HL/MPT-HLC/MPT-HLS transceiver.
power to the far end MPT-HL/MPT-HLC/MPT-HLS transceiver.
100. Replace the local MPT-HL/MPT-HLC/MPT-HLS. See Alcatel-Lucent 9500 MPR
Hardware Installation and Replacement Manual to replace the MPT-HL/
MPT-HLC/MPT-HLS Transceiver.

Procedure

102. Replace the far end MPT-HL/MPT-HLC/MPT-HLS. See Alcatel-Lucent
104. Verify antenna is aligned.
105. Is the antenna aligned?
b. If no, align the antenna. See Alcatel-Lucent 9500 MPR Turn-up Manual,
Antenna Polarization Verification Procedure.
108. Release the Forced/Lockout Rx Radio Switch using the Craft Terminal on the
local MPT ODU/MPT-HL.
109. Release the Forced/Lockout Equipment Switch using the Craft Terminal on
the local MPT ODU/MPT-HL/MPT-HLC.
110. Release the Forced/Lockout HSB Switch using the Craft Terminal on the far
end MPT ODU/MPT-HL/MPT-HLC.

Procedure

22 — RPS path fail (MPT-HC, MPT-MC,

MPT-HL, MPT-HLC, MPT-XP)
22.1 — Purpose
This procedure describes how to identify and clear an RPS Path Fail alarm on the MPT-HC/
MPT-MC/MPT-XP (MPT ODU), MPT-HL, and MPT-HLC.
22.2 — General
An RPS Path Fail alarm that is declared against the MPT-HL/MPT-HLC indicates that a
failure is detected on the RPS coupler port between the MPT-HL/MPT-HLC protection
pair.
An RPS Path Fail alarm against the MPT ODU indicates that a communication failure is
detected between the MPT ODUs; only reported for MPT ODUs working in 1+1
configuration with Virtual Protection.
and address.
22.3 — Procedure
2. Review the output. See Table 22.1 for RPS Path Fail alarms.

Procedure
Table 22.1 — RPS path fail alarms

RadioProt/Dir#[3-8][1-4] MPT ODU connected to RPS path fail
MPTACC
RadioProt/Dir#1[1-6] MPT ODU connected to
Core-E, MSS-1
RadioProt/Dir#1[1-4,7-8] MPT ODU connected to
CorEvo
RadioProt/Dir#1[1-2] MPT ODU connected to
MSS-O
RadioProt/Dir#[3-8][5-8] MPT ODU connected to
EASv2
RadioProt/Dir#[3-8][5-8] MPT-HL connected to
EASv2, P8ETH
RadioProt/Dir#1[5-6] MPT-HLC connected to
Core-E, MSS-1
CorEvo
MSS-1
RadioProt/Dir#[3-8][5-8] MPT-HLC connected to
EASv2, P8ETH
condition clearing
procedures
RPS path fail

3. Using the Craft Terminal, determine which MPT ODU/MPT-HL/MPT-HLC
status is Standby.
5. MPT ODU
Retrieve the alarms for the radio direction declaring RPS Path Fail using the
Alarm Monitor.
6. Determine all radio alarms that are declared against the radio direction
declaring RPS Path Fail and troubleshoot accordingly.
8. Did RPS Path Fail alarm clear?

Procedure
9. Retrieve the alarms for the protection mate of the radio direction declaring
RPS Path Fail using the Alarm Monitor.
10. Determine all radio alarms declared against the protection mate of the
radio direction declaring RPS Path Fail and troubleshoot accordingly.
12. Did the RPS Path Fail alarm clear?
13. MPT-HL/MPT-HLC
Determine the active radio for the MPT-HL/MPT-HLC protection pair
declaring the RPS Path Fail alarm.
14.

17. Go to step 21.
18.

21. On the MPT-HL/MPT-HLC with status of Standby, position the PA switch to
power to the MPT-HL/MPT-HLC with a status of Standby.
power to MPT-HL/MPT-HLC with a status of Standby.

Procedure

28. Replace the MPT-HL/MPT-HLC with status of Standby. See the Alcatel-
Lucent 9500 MPR Hardware Installation and Replacement Manual to replace
MPT-HL/MPT-HLC.
32. Is the active radio for the MPT-HL/MPT-HLC protection pair declaring the
RPS Path Fail alarm main or spare?
33.

36. Go to step 40.
37.

41. Remove the fuse in the power distribution panel that is suppling the battery
power to the MPT-HL/MPT-HLC with a status of Standby.
42. Install the use in the power distribution panel that is suppling battery power
to the MPT-HL/MPT-HLC with a status of Standby.

Procedure

47. Replace MPT-HL/MPT-HLC with status of Standby. See the Alcatel-Lucent
MPT-HL/MPT-HLC.
51.


Procedure

23 — Housekeeping alarms
23.1 — Purpose
This procedure describes how to identify and clear Housekeeping alarms (External Point
Input) on an AUX or FAN card or MSS-1 unit.
23.2 — General
Housekeeping Alarm inputs are external alarms that are monitored by the NE.
Housekeeping alarms can be provisioned for alarm state active low or high.
Housekeeping Alarm Input [1-6]/[11-14] indicates that the external alarm point is active,
improperly configured, or improperly provisioned.
and address.
23.3 — Procedure
2. Review the output. See Table 23.1 for information about Housekeeping
alarms.

Procedure
Table 23.1 — Housekeeping alarms

Operation Name Equipment type See
ExtPt/Input#[1-6] AUX Housekeeping alarm
ExtPt/Input#[11-14] Fan
ExtPt/Input#[11-14] MSS-1
condition clearing
procedures
Housekeeping alarm
3. Verify the equipment that is associated with housekeeping alarm input
which is in the alarm state.
4. Is the equipment that is associated with housekeeping alarm input [1-6] in
the alarm state?
5. Resolve the problem with external equipment generating the housekeeping
alarm.
6. Did the Housekeeping Alarm clear?
7. Verify the Housekeeping Alarm Input provisioning for housekeeping alarm
input in alarm.
8. Correct the provisioning as required.
11. Verify the Housekeeping Alarm Input configuration for housekeeping alarm
input in alarm.
12. Correct the configuration as required.

24 — LAG alarms (Core-E, CorEvo,

MPT-HC, MPT-HL, MPT-HC-HQAM,
MPT-HLC, MPT-HLS, MPT-XP, MPT-XP-
HQAM, OC-3, MSS-1 shelf)
24.1 — Purpose
This procedure describes how to identify and clear LAG alarms on the Core, radio, and
SDH card.
24.2 — General
A Degrade alarm indicates that a member of an Ethernet or Radio LAG group has no
activity. A Degrade is declared when the number of active ports in the LAG are greater than
zero and less than the LAG size.
A LAG Port Down alarm indicates the indited radio channel was removed from a L1 LAG
group.
A Loss of Signal alarm indicates that ALL members of an Ethernet or Radio LAG have no
activity. A Loss of Signal is declared when the number of active ports in the LAG equals
zero.
A Rx Problem alarm indicates a loss of traffic due to issues at the RX blocks or to

malformed packets on the L1 LAG data path.
A Service Selective Drop alarm indicates an SDH Flow is selectively dropped due to a
reduction of Radio L1 LAG throughput.
A Traffic Down alarm indicates a loss of traffic and the L1 LAG data path is unavailable.
A Traffic Loss alarm indicates packet loss due to extreme latency difference between L1
LAG members or when traffic errors occur on the L1 LAG data path.

Procedure
A Tx Problem alarm indicates a loss of traffic due to issues at the TX blocks or to

malformed packets on the L1 LAG data path.
and address.
24.3 — Procedure
1. Using the Alarm Monitor, retrieve ALL alarms.
2. Review the output. See Table 24.1 for information about LAG alarms.
Table 24.1 — LAG alarms

Degrade
EthLAG#[1-14] Core-E, CorEvo, MSS-1 Degrade
RadioLAG#[1-14] MPT ODU, MPT-HL, MPT-HLC,
MPT-HLS
LAG Port Down
Radio/Dir#1.[1-3]/ MPT ODU connected to MSS-O LAG port down
Radio/Dir#[3-8].[1-4]/ MPT ODU connected to EASv2
Slot#[3-8]/Port#[1-4]/Ch#1
Radio/Dir#[3-8].[5-8]/ MPT ODU, MPT-HL, MPT-HLC,
Slot#[3-8]/Port#[5-8]/Ch#1 MPT-HLS connected to EASv2
Loss of Signal
EthLAG#[1-14] Core-E, CorEvo, MSS-1, MSS-O Loss of signal
RadioLAG#[1-14] MPT ODU, MPT-HL, MPT-HLC
Rx Problem
RadioLAG#[1-14] MPT ODU, MPT-HL, MPT-HLC, Rx problem
MPT-HLS
Service Selective Drop
RadioLAG#[1-14]/ STM-1/OC-3 Service selective drop
SDHFlowID#[2-4080]
Traffic Down
RadioLAG#[1-14] MPT ODU, MPT-HL, MPT-HLC, Traffic down
MPT-HLS
Traffic Loss

Procedure
Table 24.1 — LAG alarms (Continued)

RadioLAG#[1-14] MPT ODU, MPT-HL, MPT-HLC, Traffic loss
MPT-HLS
Tx Problem
RadioLAG#[1-14] MPT ODU, MPT-HL, MPT-HLC, TX problem
MPT-HLS
None of the above — — Alarm and abnormal condition
clearing procedures

a. Degrade
b. LAG port down
c. Loss of signal
d. Rx problem
e. Service selective drop
f. Traffic down
g. Traffic loss
h. TX problem
Degrade
2. Identify the alarms that are declared against members of the LAG group. If
alarms exists, see Alarm and abnormal condition clearing procedures and
3. Did the alarms exist on the LAG group members and were they cleared?
5. Did the Degrade alarm clear?
LAG port down
3. Did alarms exist on the LAG members and were they cleared?

Procedure

5. Did the LAG port down alarm clear?
Loss of signal
3. Did the alarms exist on the LAG members and were they cleared?
5. Did the Loss of Signal alarm clear?
Rx problem
5. Did the Rx problem alarm clear?
Service selective drop
2. Identify the alarms that are declared against members of the LAG group
associated with the affected OC-3. If alarms exists, see Alarm and abnormal
condition clearing procedures and troubleshoot accordingly.

Procedure

5. Did the Service Selective Drop alarm clear?
Traffic down
5. Did the traffic down alarm clear?
Traffic loss
1. Using site documentation determine the expected LAG membership for both
ends of the LAG.
2. Using the Craft Terminal, verify LAG membership for both ends of the LAG.
3. Does the LAG membership agree with site documentation and does the LAG
membership align at both ends of the LAG?
4. Determine the desired LAG membership and provision LAG membership
accordingly.
6. Did the traffic loss alarm clear?
9. Did alarms exist on LAG members and were they cleared?

Procedure

11. Did the traffic loss alarm clear?
TX problem
3. Did the alarms exist on the LAG members and were they cleared?
5. Did the Tx problem alarm clear?

25 — Ethernet connectivity fault

management alarms
25.1 — Purpose
This procedure describes how to identify and clear Ethernet Connectivity Fault
Management (ECFM) alarms.
25.2 — General
An Eth OAM Loss of Continuity alarm indicates that a MEP received no CCM frames from
a peer MEP during an interval equal to 3.5 times the CCM transmission interval configured
at the MEP. This is caused by a failure in the network located between the local and far end
of the MEP.
An Eth OAM MisMerge Condition alarm indicates that a MEP received a CCM frame with
expected MD Level but unexpected MA ID. The MA ID is the MD Name appended with
the MA Format.
An Eth OAM Remote Defect Indication alarm indicates that a MEP received a CCM frame
with the RDI field set.
An Eth OAM Unexpected Level alarm indicates that a MEP received a CCM frame with
the incorrect MD Level. The MEP expects to receive a MD level [0-7] either equal to or
higher than the provisioned MD Level.
An Eth OAM UnexpectedMEPID alarm indicates that received MEPID value is different
than the expected MEPID [1-8191]. The MEP expects to receive the provisioned MEPID.
Eth OAM Unexpected Period alarm indicates that received MEP Transmission Interval
value is different than the expected MEP Transmission Interval [300-hundred-hertz, ten-
ms, hundred-ms, one-sec, ten-sec, one-min, ten-min]. The MEP expects to receive the same
value inside the CCM frame as the provisioned Transmission Interval.

Procedure
and address.
25.3 — Procedure
2. Review the output. See Table 25.1 for information about ECFM alarms.
Table 25.1 — ECFM alarms

Eth OAM loss of continuity
MEP#MDID[1-16]#MA ID Core-E, CorEvo, MSS-1, Eth OAM loss of
[1-512]#MEPID[1-8191] MSS-O continuity
Eth OAM MisMerge condition
MEP#MDID[1-16]#MA ID Core-E, CorEvo, MSS-1, Eth OAM MisMerge
[1-512]#MEPID[1-8191] MSS-O condition
Eth OAM remote defect indication
MEP#MDID[1-16]#MA ID Core-E, CorEvo, MSS-1, Eth OAM remote
[1-512]#MEPID[1-8191] MSS-O defect indication
Eth OAM unexpected level
MEP#MDID[1-16]#MA ID Core-E, CorEvo, MSS-1, Eth OAM unexpected
[1-512]#MEPID[1-8191] MSS-O level
Eth OAM unexpected MEPID
MEP#MDID[1-16]#MA ID Core-E, CorEvo, MSS-1, Eth OAM
[1-512]#MEPID[1-8191] MSS-O unexpectedMEPID
Eth OAM unexpected period
MEP#MDID[1-16]#MA ID Core-E, CorEvo, MSS-1, Eth OAM unexpected
[1-512]#MEPID[1-8191] MSS-O period
condition clearing
procedures

a. Eth OAM loss of continuity
b. Eth OAM MisMerge condition
c. Eth OAM remote defect indication

Procedure
d. Eth OAM unexpected level

e. Eth OAM unexpectedMEPID
f. Eth OAM unexpected period
Eth OAM loss of continuity
1. Locate the failure in the network.
a. If MIPs were created on the MEP, use the Link Trace command using WT
CLI Tool. See the Alcatel-Lucent 9500 MPR WebEML User Manual, WT
CLI Tool Reference Guide for more information.
b. Otherwise, Retrieve the alarms using the Alarm Monitor and locate
alarms associated with the path between the local and far end of the
MEP.
2. Were alarms identified and cleared between the local and far end of the
MEP?
4. Did the Eth OAM Loss of Continuity Condition alarm clear?
Eth OAM MisMerge condition
1. Retrieve MA ID for both ends of the MEP using WT CLI Tool. See the Alcatel-
Lucent 9500 MPR WebEML User Manual, WT CLI Tool Reference Guide for
more information.
2. Determine which MA ID value(s) are incorrect.
3. Reprovision the MA ID value(s) according to the results of step 2.
5. Did the Eth OAM MisMerge Condition alarm clear?
Eth OAM remote defect indication
1. Retrieve the alarms on the far end of the MEP using Alarm Monitor.
2. Check the far end for the one or more of the above RDI set conditions and
3. Were the RDI set condition cleared at the far end of the MEP?

Procedure
5. Did the Eth OAM Remote Defect Indication Level alarm clear?
Eth OAM unexpected level
1. Retrieve the MD Level for both ends of the MEP using WT CLI Tool. See the
Alcatel-Lucent 9500 MPR WebEML User Manual, WT CLI Tool Reference
Guide for more information.
2. Determine which MD Level values are incorrect.
3. Reprovision the MD Level values according to the results of step 2.
5. Did the Eth OAM Unexpected Level alarm clear?
Eth OAM unexpectedMEPID
1. Retrieve MEPID for both ends of the MEP using WT CLI Tool. See the Alcatel-
Lucent 9500 MPR WebEML User Manual, WT CLI Tool Reference Guide for
more information.
2. Determine which MEPID value(s) are incorrect.
3. Reprovision the MEPID value(s) according to the results of step 2.
5. Did the Eth OAM UnexpectedMEPID alarm clear?
Eth OAM unexpected period
1. Retrieve the MEP Transmission Interval for both ends using WT CLI Tool. See
the Alcatel-Lucent 9500 MPR WebEML User Manual, WT CLI Tool Reference
Guide for more information.
2. Determine which MEP Transmission Interval values are incorrect.
3. Reprovision the MEP Transmission Interval according to the results of step 2.
Note: Eth OAM Unexpected Period alarm requires 3.5 times the MEP Transmission Interval
to clear the alarm. For MEP Transmission Interval provisioned one-sec, the alarm requires
3.5 seconds to clear. For MEP Transmission Interval provisioned 10-min, the alarm
requires 35 minutes to clear.

5. Did the Eth OAM Unexpected Period alarm clear?

26 — Clock failure (MPT-HC, MPT-HC-

26.1 — Purpose
This procedure describes how to identify and clear Clock Failure alarm on the MPT-HC/
MPT-HC-HQAM/MPT-XP/MPT-XP-HQAM (MPT ODU), MPT-HL, MPT-HLC and
MPT-HLS.
26.2 — General
A Clock Failure alarm indicates that the MPT ODU, MPT-HL, MPT-HLC, or MPT-HLS
is unable to lock the air Tx symbol rate to the NE clock.
and address.
26.3 — Procedure
2. Review the output. See Table 26.1 for information about Clock Failure
alarms.

Procedure
Table 26.1 — Clock failure alarm

Radio/Dir#1.[1-6]/ MPT ODU connected to Clock failure
Slot#[3-8]/Port#[5-8]/Ch#[0-1] EASv2
Slot#[3-8]/Port#[5-8]/Ch#[0-1] P8ETH
abnormal
condition clearing
procedures
Clock failure

Procedure

2. Unprotected radio configuration
Caution: Power Cycling an in-service MPT ODU, MPT-HL, MPT-HLC, or MPT-HLS in an
unprotected link causes a loss of traffic on ALL facilities that are associated with the
MPT ODU, MPT-HL, MPT-HLC, or MPT-HLS in alarm. Schedule an appropriate
Caution: Replacing the MPT ODU, MPT-HL, MPT-HLC, or MPT-HLS in an unprotected link
causes a loss of traffic on ALL facilities that are associated with the MPT ODU, MPT-HL,
or MPT-HLC, or MPT-HLS in alarm. Schedule an appropriate maintenance window per

4. Verify that it is appropriate to proceed with clear Clock Failure procedure or
appropriate maintenance window is scheduled per local practices and procedures.
5. Is it appropriate to proceed with clear Clock Failure procedure?
7. MPT ODU
Caution: Power Cycling the MPT ODU in an unprotected facility causes a loss of
traffic on ALL facilities that are associated with the MPT ODU in alarm.
procedures.

a. If MPT ODU is powered through EASv2, MPTACC card, MSS-O, or MSS-1
shelf PFoE port, power cycle the MPT ODU. From the MPT Main View, Power
Source tab, Settings tab, disable power source. Wait 10 seconds and then
reapply power source.If MPT ODU is powered through a power injector card/
power injector box, disconnect the DC+Data cable connection to the
MPT ODU at the power injector card/box. Wait 10 seconds and reconnect.
b. If MPT ODU is powered with connection to MPT Power Unit/MPT Extended
Power Unit, disconnect the power cable connection to the MPT ODU at the
MPT Power Unit/MPT Extended Power Unit. Wait 10 seconds and reconnect.

Procedure
c. If MPT ODU is powered with connection to direct office power, locate the fuse
protecting the MPT ODU and remove. Wait 10 seconds and reinstall the fuse.
8. Dialog Failure is declared against the MPT ODU. Wait for Dialog Failure condition
to clear before proceeding.
10. Did the Clock Failure alarm clear?
11.
Caution: Replacing the MPT ODU in an unprotected link causes a loss of traffic
on ALL facilities that are associated with the MPT ODU in alarm. Schedule an
Replace the MPT ODU in alarm. See the Alcatel-Lucent 9500 MPR Hardware
Installation and Replacement Manual to replace MPT ODU.
14. MPT-HL/MPT-HLC
Caution: Power Cycling the MPT-HL/MPT-HLC in an unprotected link causes a loss of
traffic on ALL facilities that are associated with the MPT-HL/MPT-HLC in alarm. Schedule
an appropriate maintenance window per local practices and procedures.
15. Position the MPT-HL/MPT-HLC Transceiver PA switch to the OFF ‘0’ position.
16. Remove the fuse in the power distribution panel that is suppling battery power to the
MPT-HL/MPT-HLC transceiver.
17. Install the fuse in power distribution panel that is suppling battery power to the
MPT-HL/MPT-HLC transceiver.
18. Position the MPT-HL/MPT-HLC Transceiver PA switch to the ON ‘1’ position.
21.
Caution: Replacing the MPT-HL/MPT-HLC in an unprotected link causes a loss
of traffic on ALL facilities that are associated with the MPT-HL/MPT-HLC in
alarm. Schedule an appropriate maintenance window per local practices and
procedures.

Procedure
Replace the local MPT-HL/MPT-HLC. See the Alcatel-Lucent 9500 MPR Hardware
Installation and Replacement Manual to replace the MPT-HL/MPT-HLC
transceiver.
23. Protected radio configuration
24. Determine the status of MPT ODU/MPT-HL/MPT-HLC/MPT-HLS declaring Clock
Failure alarm.
a. If Active, go to step 25.
b. If Standby, go to step 26.
26. Is the MPT ODU/MPT-HL/MPT-HLC/MPT-HLS declaring Clock Failure alarm the
main or spare?
27.
Caution: Forced EPS/HSB/RX Radio switching traffic causes a disruption to traffic.
Perform a Forced Rx Radio Switch using the Craft Terminal.

28. Perform a Forced Equipment Switch using the Craft Terminal.
30. Go to step 34.
31.
Caution: Forced EPS/HSB/RX Radio switching traffic causes a disruption to traffic.
Perform a Lockout Rx Radio Switch using the Craft Terminal.

32. Perform a Lockout Equipment Switch using the Craft Terminal.
35. MPT ODU

Procedure

a. If MPT ODU is powered through EASv2, MPTACC card or MSS-1 shelf Core
PFoE port, power cycle the MPT ODU. From the MPT Main View, Power
Source tab, Settings tab, disable power source. Wait 10 seconds and then
reapply power source.
b. If MPT ODU is powered through a Power Injector Card/Power Injector Box/
MPT Extended Power Unit, disconnect the DC+Data cable connection to the
MPT ODU at the power injector card/box. Wait 10 seconds and reconnect.
c. If MPT ODU is powered with connection to MPT Power Unit/MPT Extended
Power Unit, disconnect the power cable connection to the MPT ODU at the
MPT Power Unit/MPT Extended Power Unit. Wait 10 seconds and reconnect.
d. If MPT ODU is powered with connection to direct office power, locate the fuse
protecting the MPT ODU and remove. Wait 10 seconds and reinstall the fuse.
36. Dialog Failure is declared against the MPT ODU. Wait for Dialog Failure condition
to clear before proceeding.
39. Replace the MPT ODU in alarm. See the Alcatel-Lucent 9500 MPR Hardware
Installation and Replacement Manual to replace the MPT ODU.
Position the MPT-HL/MPT-HLC/MPT-HLS Transceiver PA switch to the OFF ‘0’
position.
43. Remove the fuse in the power distribution panel that is suppling battery power to the
MPT-HL/MPT-HLC/MPT-HLS transceiver.
44. Install the fuse in the power distribution panel that is suppling battery power to the
MPT-HL/MPT-HLC/MPT-HLS transceiver.
45. Position the MPT-HL/MPT-HLC/MPT-HLS Transceiver PA switch to the ON ‘1’
position.

Procedure
48. Replace the MPT-HL/MPT-HLC/MPT-HLS. See the Alcatel-Lucent 9500 MPR

Hardware Installation and Replacement Manual to replace MPT-HL/MPT-HLC/
MPT-HLS Transceiver.
51.
Caution: Releasing Forced/Lockout EPS/HSB/RX Radio switch causes a
disruption to traffic.
Release the Forced/Lockout Rx Radio Switch using the Craft Terminal.

52. Release the Forced/Lockout Equipment Switch using the Craft Terminal.

Procedure

27 — Duplicate Address Detected alarms
27.1 — Purpose
This procedure describes how to identify and clear Duplicate Address Detected alarms.
27.2 — General
Duplicate address detected alarm is raised when a duplicate IPv6 address is detected on a
TMN LAN interface. The following TMN LAN interfaces are checked for a duplicate
address:
• IPv6 Global Unicast address assigned to:

• TMN Local Ethernet interface
• TMN User Ethernet Port 4 interface
• TMN In-Band port #1/2 interface
• TMN-RF Point-to-Point interface
Note: If access to the NE with the incorrect IPv6 address is through the TMN port in alarm,
communication with the NE will be lost when the address is changed. The TMN address
must be changed locally or a different TMN interface must be established to communicate
with the NE.
Note: When a different TMN interface is not available o communicate with the NE with
the incorrect IPv6 address, it is required to correct the IPv6 address on-site.
and address.

Procedure
27.3 — Procedure
2. Review the output. See Table Table 27.1 for information about Duplicate
address detected alarms.
Table 27.1 — Duplicate address detected alarms

TMNEthernet/MngtPort Core-E, CorEvo/TMN MGMT Duplicate address
Port detected - TMN
Ethernet MGMT Port
TMNEthernet/Port#4 Core-E, CorEvo/TMN Port#4 Duplicate address
detected - Port #4
TMN Ethernet
TMNInBand#[1-2] Core-E, CorEvo/TMN In-Band Duplicate address
Port [1-2] detected - TMN
In-Band Port #1/2
PPP-IP/RF#1[1-6] MPT ODU connected to Duplicate address
Core-E, MSS-1 detected - PPP IP/RF
PPP-IP/RF#1[1-4,7-8] MPT ODU connected to Port
CorEvo
PPP-IP/RF#1[1-3] MPT ODU connected to
MSS-O
PPP-IP/RF#[3-8][1-4] MPT ODU connected to EASv2,
MPTACC
PPP-IP/RF#[3-8][5-8] MPT ODU connected to EASv2,
P8ETH
PPP-IP/RF#[3-8][5-8] MPT-HL, MPT-HLC, MPT-HLS
connected to EASv2, P8ETH
PPP-IP/RF#1[5-6] MPT-HL, MPT-HLC, MPT-HLS
PPP-IP/RF#1[7-8] MPT-HL, MPT-HLC, MPT-HLS
connected to CorEvo
PPP-IP/RF/LAG#[1-14] MPT ODU, MPT-HL, MPT-HLC,
MPT-HLS
condition clearing
procedures

a. Duplicate address detected - TMN Ethernet MGMT Port
b. Duplicate address detected - Port #4 TMN Ethernet
c. Duplicate address detected - TMN In-Band Port #1/2
d. Duplicate address detected - PPP IP/RF Port

Procedure
Duplicate address detected - TMN Ethernet MGMT Port

1. Using the Craft Terminal, retrieve the provisioned IPv6 TMN Ethernet Configuration
value for the NE declaring duplicate address detected alarm.
2. Verify the desired IPv6 TMN Ethernet Configuration value for the NE according to
site engineering documentation.
3. Is the provisioned IPv6 TMN Ethernet value correct?
a. If no, go to step 4.
b. If yes, go to step 12.
4.
• If access to the NE with the incorrect IPv6 address is through the TMN port in
alarm, communication with the NE will be lost when the address is changed.
The TMN address must be changed locally or a different TMN interface must
be established to communicate with the NE.
• When a different TMN interface is not available to communicate with the NE
with the incorrect IPv6 address, it is required to correct the IPv6 address
on-site. If the IPv6 address is corrected remotely, communication with the NE
will be lost.
Reprovision IPv6 TMN Ethernet Configuration value for the NE according to site
engineering documentation.
5. Was the IPv6 address changed on-site?
6. Disconnect the TMN Ethernet interface and reconnect.
7. Go to step 10.
8. Disable TMN Ethernet Configuration port in alarm.
9. Enable TMN Ethernet Configuration port in alarm.
11. Did the duplicate address detected alarm clear?
12. Verify the desired IPv6 TMN Ethernet Configuration value for the other devices
connected to the TMN port according to site engineering documentation.
13. Reprovision IPv6 TMN Ethernet Configuration value on the incorrect device with the
correct IPv6 address.
14. Was an IPv6 address changed on the IPv6 TMN Ethernet network?

Procedure

16. Go to step 19.
17. Disable TMN Ethernet Configuration port in alarm.
18. Enable TMN Ethernet Configuration port in alarm.
Duplicate address detected - Port #4 TMN Ethernet
1. Using the Craft Terminal, retrieve the provisioned IPv6 Port #4 TMN Ethernet
Configuration value for the NE declaring duplicate address detected alarm.
2. Verify the desired IPv6 Port #4 TMN Ethernet Configuration value for the NE
according to site engineering documentation.
3. Is the provisioned IPv6 Port #4 TMN Ethernet value correct?
4.
• If access to the NE with the incorrect IPv6 address is through the Port #4 TMN
port in alarm, communication with the NE will be lost when the address is
changed. The TMN address must be changed locally or a different TMN
interface must be established to communicate with the NE.
will be lost.
Reprovision IPv6 Port #4 TMN Ethernet Configuration value for the NE according
to site engineering documentation.
5. Was the IPv6 address changed on-site?
6. Disconnect the Port #4 TMN Ethernet interface and reconnect.
7. Go to step 10.
8. Disable Port #4 TMN Ethernet Configuration port in alarm.
9. Enable Port #4 TMN Ethernet Configuration port in alarm.

Procedure

12. Verify the desired IPv6 Port #4 TMN Ethernet Configuration value for the far end NE
according to site engineering documentation.
13. Reprovision the far end NE with the correct IPv6 address.
14. Was the IPv6 address changed on-site at the near end or far end NE?
16. Go to step 19.
17. Disable Port #4 TMN Ethernet Configuration port.
18. Enable Port #4 TMN Ethernet Configuration port.
Duplicate address detected - TMN In-Band Port #1/2
1. Using the Craft Terminal, retrieve the provisioned IPv6 TMN In-Band Port #1/2
value for the NE declaring duplicate address detected alarm.
2. Verify the desired IPv6 TMN In-Band Port #1/2 value for the NE according to site
3. Is the provisioned IPv6 TMN In-Band Port #1/2 value correct?
4.
• If access to the NE with the incorrect IPv6 address is through the TMN In-Band
Port #1/2 in alarm, communication with the NE will be lost when the address is
changed. The TMN In-Band Port #1/2 address must be changed locally or a
different TMN interface must be established to communicate with the NE.
will be lost.
Reprovision IPv6 TMN In-Band Port #1/2 value for the NE according to site
5. Disable TMN In-Band Port #1/2.
6. Enable TMN In-Band Port #1/2.

Procedure

9. Verify the desired IPv6 TMN In-Band Port #1/2 Ethernet Configuration value for the
far end NE according to site engineering documentation.
10. Reprovision the far end NE with the correct IPv6 address.
11. Disable TMN In-Band Port #1/2.
12. Enable TMN In-Band Port #1/2.
Duplicate address detected - PPP IP/RF Port
1. Using the Craft Terminal, retrieve the provisioned Local IPv6 Address value for the
NE declaring duplicate address detected alarm.
2. Verify the desired Local IPv6 Address value for the NE according to site engineering
documentation.
3. Is the provisioned Local IPv6 Address value correct?
4. Reprovision Local IPv6 Address value for the NE according to site engineering
documentation.
7.
Note: To perform steps 7 and 8 a redundant network path to the far end must exist or an
operator must be on-site at the far end.
Verify the desired Local IPv6 Address value for the far end NE according to site
8. Reprovision the far end NE Local IPv6 Address value with the correct IPv6 address.
Note: After the far end Local IPv6 Address is corrected, a PPP Fail condition will be raised
and clear the duplicate address detected alarm at the site declaring duplicate address
detected.

Procedure

11. Verify the near end PPP-RF port provisioning.
12. Was the near end PPP-RF port provisioned correctly?
13. Reprovision near end PPP-RF port provisioning.
14. Disable near end PPP RF port.
15. Enable near end PPP RF port.
18. Verify the far end PPP-RF port provisioning.
Caution: If the far end PPP-RF port provisioning is corrected/disabled
remotely, communication with the far end NE will be lost and on-site
provisioning will be required to re-establish communications.
19. Was the far end PPP-RF port provisioned correctly?

20. Reprovision far end PPP-RF port provisioning.
21. Disable far end PPP RF port.
22. Enable far end PPP RF port.

Procedure

28 — Combiner loss of alignment

(MPT-HLC or MPT-HLS)
28.1 — Purpose
This procedure describes how to identify and clear Combiner Loss Of Alignment alarm on
the MPT-HLC or MPT-HLS.
28.2 — General
A Combiner Loss Of Alignment alarm indicates that a delay/loss of alignment between the
main and diversity signal is detected by the combiner in diversity/combiner configurations.
and address.
28.3 — Procedure
2. Review the output. See Table 28.1 for information about Combiner Loss of
Alignment alarms.

Procedure
Table 28.1 — Combiner loss of alignment alarm
r01/subrack#1[5-6] MPT-HLC connected to Combiner Loss of

Core-E, MSS-1 alignment

CorEvo
r01/subrack#[3-8][5-8] MPT-HLC connected to EASv2
r01s[101-102]/board# MPT-HLS
[1-10]
condition clearing
procedures
Combiner Loss of alignment

3. Retrieve the alarms using the Alarm Monitor, verify that no other radio path
alarms (such as loss of signal) exist, and troubleshoot accordingly.
4. Did other radio path alarms exist and were they cleared?
6. Did the Combiner Loss of Alignment alarm clear?
7. Using the Craft Terminal, check the RSL values for the main and diversity
receiver for the MPT-HLC/MPT-HLS declaring combiner loss of alignment
alarm and troubleshoot accordingly.
10. Perform an MPT restart on the NE: Supervision/Restart MPT.
11. Wait for the status LED to turn steady amber or green.

Procedure
14.
Caution: Performing the Restart NE command may cause a disruption to traffic.
Perform the NE restart on the NE: Supervision/Restart NE. Communication

with the NE is lost during the NE restart and you are logged out of the
system.
15. Log into the NE.
18. Is the radio direction in a protected configuration?
19. Verify that the MPT-HLC or MPT-HLS in alarm status is Standby.
20. Is the MPT-HLC or MPT-HLS in alarm main or spare?
21.

24. Go to step 28.
25.

28.

Procedure
Caution: The following steps on an unprotected radio direction will cause a loss
of traffic associated with the radio direction in alarm. Schedule an appropriate
Inspect the RF cabling to the main and diversity receiver.

Correct ALL issues identified.
31. Disconnect the data cable connection at the MPT-HLC/MPT-HLS to MSS.
Then reconnect the cable.
35. Position the MPT-HLC/MPT-HLS Transceiver PA switch to the OFF ‘0’
position.
36. Remove the fuse in the power distribution panel that supplies battery power
to the MPT-HLC/MPT-HLS transceiver.
37. Install the fuse in the power distribution panel that supplies battery power
to the MPT-HLC/MPT-HLS transceiver.
38. Position the MPT-HLC/MPT-HLS Transceiver PA switch to the ON ‘1’
position.
42. Replace the MPT-HLC or MPT-HLS in alarm. See the Alcatel-Lucent 9500 MPR
Hardware Installation and Replacement Manual to replace the unit.

Procedure


Procedure

29 — Fan Fail (MPT-HLC)
29.1 — Purpose
This procedure describes how to identify and clear Fan Fail alarm on MPT-HLC.
29.2 — General
A Fan Fail alarm indicates that MPT-HLC card has detected a MPT-HLC fan unit has
failed.
and address.
29.3 — Procedure
Table 29.1 — Fan fail alarm

r01/subrack#1[5-6] MPT-HLC connected to Core-E, Fan Fail
MSS/CORE
r01/subrack#1[7-8] MPT-HLC connected to CorEvo
r01/subrack#[3-8][5-8] MPT-HLC connected to EASv2,
P8ETH
condition clearing
procedures

Procedure
Fan Fail
3. Verify that ALL the MPT-HLC fans are equipped and operating properly.
5. Is it appropriate to proceed with the Fan Fail procedure?
7. Verify that the MPT-HLC in alarm status is Standby.
8. Is the MPT-HLC in alarm status Standby?
b. If no, the following Caution applies.
9.

12. Go to step 16.
16.
Caution: Physically replacing an unprotected MPT-HLC will causes a loss of
traffic on ALL facilities that are associated with the MPT-HLC being replaced.
procedures.
Replace the MPT-HLC. See the Alcatel-Lucent 9500 MPR Hardware Installation
and Replacement Manual to replace MPT-HLC.
19. Did the Fan Fail alarm clear?

Procedure


Procedure

30 — Fan Communication Problem (MPT-

HLS)
30.1 — Purpose
This procedure describes how to identify and clear Fan Communication Problem alarm on
MPT-HLS.
30.2 — General
A Fan Communication Problem alarm indicates that a problem communicating with the
MPT-HLS fan has been detected.
and address.
30.3 — Procedure
Table 30.1 — Fan fail alarm

r01s[101-102]/board# MPT-HLS Fan Communication
[1-10] Problem

Procedure
Table 30.1 — Fan fail alarm (Continued)

condition clearing
procedures
Fan Communication Problem

3. Verify that ALL the MPT-HLS fans are equipped and operating properly.
5. Is it appropriate to proceed with the Fan Fail procedure?
7. Verify that the MPT-HLS in alarm status is Standby.
8. Is the MPT-HLS in alarm status Standby?
b. If no, the following Caution applies.
9.

12. Go to step 16.
16.
Caution: Physically replacing an unprotected MPT-HLS will causes a loss of
traffic on ALL facilities that are associated with the MPT-HLS being replaced.
procedures.

Procedure
Replace the MPT-HLS. See the Alcatel-Lucent 9500 MPR Hardware

Installation and Replacement Manual to replace MPT-HLS.
19. Did the Fan Fail alarm clear?

Procedure

31 — RF Switch Fail (MPT-HLC or MPT-

HLS)
31.1 — Purpose
This procedure describes how to identify and clear RF Switch Fail alarm on the MPT-HLC
or MPT-HLS.
31.2 — General
A RF Switch Fail alarm indicates that a failure is detected on the transmit RF switch.
and address.
31.3 — Procedure
2. Review the output. See Table 31.1 for information about RF Switch Fail
alarms.
Table 31.1 — RF Switch Fail alarms

r01/subrack#1[5-6] MPT-HLC connected to Core-E, RF Switch Fail
MSS-1
r01/subrack#1[7-8] MPT-HLC connected to CorEvo
r01/subrack#[3-8][5-8] MPT-HLC connected to EASv2

Procedure
Table 31.1 — RF Switch Fail alarms

r01s[101-102]b[1-10] MPT-HLS
condition clearing
procedures
RF Switch Fail
3. Inspect the cabling to/from the transmit RF switch:
a. MPT-HLC/MPT-HLS shelf switch power connection
b. MPT-HLC/MPT-HLS shelf TX main and Tx spare connections
c. Transmit RF switch antenna port connection
4. Were issues identified with the cabling to/from the transmit RF switch?
5.
Caution: Muting both the main and spare MPT-HLC/MPT-HLS will causes a loss
of traffic on ALL facilities that are associated with the MPT-HLC/MPT-HLS with
RF Switch Fail alarm. Schedule an appropriate maintenance window per local
Mute both the main and spare transmitters.

6. Correct ALL cable and cable connections as required.
8. Did the RF Switch Fail alarm clear?
9.
Caution: Muting both the main and spare MPT-HLC/MPT-HLS will causes a loss
of traffic on ALL facilities that are associated with the MPT-HLC/MPT-HLS with
RF Switch Fail alarm. Schedule an appropriate maintenance window per local
Mute both the main and spare transmitters.

10. Replace the transmit RF switch.
12. Did the RF Switch Fail alarm clear?

Procedure
13. Unmute the main transmitter.

14. Verify that the main MPT-HLC/MPT-HLS switch status is Active
15. Verify traffic is running error free at the far end associated with the main
transmitter.
16. Unmute the spare transmitter.
18. Verify that the spare MPT-HLC/MPT-HLS switch status is Active
19. Verify traffic is running error free at the far end associated with the spare
transmitter.
20. Did traffic run error-free on both the main and spare transmitters and is the
direction operating normally?
21. Release the Forced HSB Switch using the Craft Terminal.

Procedure

32 — Rx diversity missing (MPT-HLC or

MPT-HLS)
32.1 — Purpose
This procedure describes how to identify and clear Rx Diversity Missing alarm on the
MPT-HLC or MPT-HLS.
32.2 — General
A Rx Diversity Missing alarm indicates that the MPT-HLC or MPT-HLS has been
configured for a diversity receiver configuration but the system does not detect the
diversity/combiner module on the MPT-HLC or MPT-HLS.
and address.
32.3 — Procedure
2. Review the output. See Table 32.1 for information about Rx Diversity
Missing alarms.

Procedure
Table 32.1 — Rx diversity missing alarm

r01/subrack#1[5-6] MPT-HLC connected to Core-E, Rx Diversity Missing
MSS-1
r01s1[7-8]b1/daughter#04 MPT-HLC connected to CorEvo
r01/subrack#[3-8][5-8] MPT-HLC connected to EASv2,
P8ETH
r01s[101-102]b[1-10]/ MPT-HLS
daughter#04
condition clearing
procedures
Rx Diversity Missing
3. Using site engineering documentation determine if the radio direction is
configured for a diversity receiver?
4. Using the Craft Terminal, from the radio main view, Settings tab, select the
SD check-box (unchecked).
5. Click on the Apply button.
7. Did the Rx Diversity Missing alarm clear?
8. Using the Craft Terminal, from the remote inventory drop down, determine
the MPT-HLC or MPT-HLS type.
10. Is it appropriate to proceed with the Rx Diversity Missing alarm procedure?
12. Verify that the MPT-HLC or MPT-HLS in alarm status is Standby.
13. Is the MPT-HLC or MPT-HLS in alarm main or spare?

Procedure

14.

17. Go to step 21.
18.

21.
Caution: Physically replacing an unprotected MPT-HLC or MPT-HLS will causes
a loss of traffic on ALL facilities that are associated with the MPT-HLC or MPT-
HLS being replaced. Schedule an appropriate maintenance window per local
Replace the MPT-HLC or MPT-HLS. Verify that the replacement MPT-HLC or

MPT-HLS type supports the diversity receiver as described in site
engineering documentation. See the Alcatel-Lucent 9500 MPR Hardware
Installation and Replacement Manual to replace the MPT-HLC.
24. Did the Rx Diversity Missing alarm clear?

Procedure

33 — Radio encryption mismatch

(MPT-HC, MPT-HC-HQAM, MPT-HLC,
MPT-HLS, MPT-XP, MPT-XP-HQAM)
33.1 — Purpose
This procedure describes how to identify and clear radio encryption mismatch alarm on
MPT-HC/MPT-HC-HQAM/MPT-XP/MPT-XP-HQAM (MPT ODU), MPT-HLC, and
MPT-HLS.
33.2 — General
A Radio encryption mismatch alarm indicates either radio encryption is enabled only on
one end of the radio hop, or the radio encryption key provisioned on one end of the hop is
does not match the key provisioned on the other end of the hop.
and address.
33.3 — Procedure

Procedure

Radio/Dir#1.[1-6]/ MPT ODU connected to Radio encryption
Slot#1/Port#[1-6]/Ch#1 Core-E mismatch
Port#[1-4,7-8]/Ch#1 CorEvo
abnormal condition
clearing
procedures
Radio encryption mismatch

3. Verify radio encryption is desired on the microwave link in alarm.
4. Is radio encryption desired on the microwave link in alarm?
5. Using site documentation determine the desired encryption key for the
radio link.

Procedure
6. Using the Craft Terminal, provision radio encryption on the far end using the
encryption key identified in step 5.
8. Did the radio encryption mismatch alarm clear?
9. Using the Craft Terminal, provision radio encryption on the near end using
the encryption key identified in step 5.
12. Using the Craft Terminal, disable radio encryption on the far end.
13. Using the Craft Terminal, disable radio encryption on the near end.

Procedure

34 — Critical Link Event (Core-E, EASv2,

P8ETH)
34.1 — Purpose
This procedure describes how to identify and clear critical link event alarm on Core-E,
CorEvo, EASv2, and P8ETH Ethernet ports with Ethernet First Mile (EFM) OAM enabled.
34.2 — General
A critical link event alarm indicates the Ethernet port’s link partner has declared a link fault
condition.
and address.
34.3 — Procedure
2. Review the output. See Table 34.1 for information about critical link event
alarm.

Procedure
Table 34.1 — Critical link event alarm

ETHLinkOAM/Slot#1/Ports[1-6] Ethernet port on Critical link event
Core-E
ETHLinkOAM/Slot#1/Ports[1-8] Ethernet port on
CorEvo
ETHLinkOAM/MSS/CORE/Ports[1-6] Ethernet port on MSS-1
ETHLinkOAM/Slot#1/Ports[1-4] Ethernet port on MSS-O
ETHLinkOAM/Slot#[3-8]/Ports[1-8] Ethernet port on
EASv2, P8ETH
abnormal condition
clearing
procedures
Critical link event

3. Retrieve the alarms using the Alarm Monitor at the NE declaring critical link
event.
4. Are there additional alarms declared against the Ethernet port in alarm?
5. Determine all the alarms declared against the Ethernet port and
7. Did the critical link event alarm clear?
8. Verify the operational status of the link partner and troubleshoot
accordingly.
11. Verify the cabling between the link partner and the Core-E/CorEvo/EASv2/
P8ETH card or the MSS-1 unit.

Procedure
14. Is the Ethernet port configured with an SFP?

15. Replace the SFP at the Core-E/CorEvo/EASv2/P8ETH card or the MSS-1 unit.
18. Replace the SFP at the link partner.

Procedure

35 — OAM discovery not completed

(Core-E, CorEvo, EASv2, P8ETH, MSS-1,
MSS-O)
35.1 — Purpose
This procedure describes how to identify and clear OAM discovery not completed alarm
on Core-E, CorEvo, EASv2, P8ETH, MSS-1 and MSS-O Ethernet ports with Ethernet First
Mile (EFM) OAM enabled.
35.2 — General
A OAM discovery not completed alarm indicates the Ethernet port (EFM) OAM discovery
process is not in operational status.
and address.
35.3 — Procedure

Procedure

ETHLinkOAM/Slot#1/Ports[1-6] Ethernet port on OAM discovery not
Core-E completed
ETHLinkOAM/Slot#1/Ports[1-8] Ethernet port on
CorEvo
ETHLinkOAM/MSS/CORE/Ports[1-6] Ethernet port on MSS-1
ETHLinkOAM/Slot#1/Ports[1-4] Ethernet port on MSS-O
ETHLinkOAM/Slot#[3-8]/Ports[1-8] Ethernet port on
EASv2, P8ETH
abnormal condition
clearing
procedures
OAM discovery not completed

3. Verify Ethernet first mile feature is desired on the Ethernet link in alarm.
4. Is Ethernet first mile feature desired on the Ethernet link in alarm?
5. Using the Craft Terminal, verify/provision Ethernet first mile feature on the
Ethernet port in alarm.
6. Verify/provision Ethernet first mile feature on the Ethernet port link
partner associated with the Ethernet port in alarm.
8. Did the OAM discovery not completed alarm clear?
9. Retrieve the alarms using the Alarm Monitor. Verify the operational status
of the Ethernet port and troubleshoot accordingly.
10. Verify the operational status of the link partner and troubleshoot
accordingly.
13. Using the Craft Terminal, disable Ethernet first mile on the Ethernet port in
alarm.

Procedure


Procedure

36 — Rate mismatch (CorEvo)
36.1 — Purpose
This procedure describes how to identify and clear rate mismatch alarm on CorEvo
Ethernet ports.
36.2 — General
A rate mismatch alarm indicates the configured speed of an 10 GbEth/1 GbEth User
Ethernet interface is not compatible with the equipped SFP transceiver.
and address.
36.3 — Procedure
2. Review the output. See Table 36.1for information about radio alarms.
Table 36.1 — Rate mismatch alarms

MAU/Slot#[1-2]/Port#[5-8] CorEvo Rate mismatch
abnormal condition
clearing
procedures

Procedure
Rate mismatch
3. Using the Craft Terminal, retrieve the provisioned Ethernet interface value
for the Ethernet interface in alarm.
4. Verify the required Ethernet interface rate for the Ethernet interface.
5. Determine if the equipped SFP supports the required Ethernet interface
rate.
6. Does the equipped SFP support the required Ethernet interface rate?
7. Using the Craft Terminal, verify/provision Ethernet interface port in alarm.
9. Did the rate mismatch alarm clear?
10. Replace the SFP.
12. Did the rate mismatch alarm clear?

Customer documentation and product

support
Customer documentation
http://documentation.alcatel-lucent.com
Technical support
http://support.alcatel-lucent.com
Documentation feedback
[email protected]
© 2016 Alcatel-Lucent. All rights reserved.

9500 MPR Alarm - Clearing

Uploaded by

Copyright:

Available Formats

9500 MPR Alarm - Clearing

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

9500 MPR Alarm - Clearing

Uploaded by

Copyright:

Available Formats

Release 6.1.

0 3DB 19291 ABAA Edition 01

Copyright 2016 Alcatel-Lucent.

All rights reserved.

1 — FCC part 15 subpart B ....................................................................................... 23

2 — Maintenance philosophy ..................................................................................... 25

9500 MPR Alarm Clearing 5

3.3.1.2 — Safety instructions: ..................................................................................... 38

4 — Electrostatic-sensitive devices ............................................................................. 49

5 — Product support information for the ANSI market ..................................................... 51

6 9500 MPR Alarm Clearing

6 — Alarm and abnormal condition clearing procedures ................................................... 57

7 — Supporting information .................................................................................... 177

8 — Facility alarms ............................................................................................... 181

9 — Abnormal conditions ....................................................................................... 205

10 — Power alarms ............................................................................................... 219

11 — Equipment alarms ......................................................................................... 239

12 — Radio alarms (MPT-HC, MPT-HC-HQAM, MPT-HL, MPT-HLC, MPT-HLS, MPT-XP,

14 — License/software mismatch ............................................................................. 289

15 — Internal loss of communications........................................................................ 295

9500 MPR Alarm Clearing 7

15.3 — Procedure ...........................................................................................................296

16 — Threshold crossing alarms (MPT-HC, MPT-HC-HQAM, MPT-HL, MPT-HLC,

17 — Synchronization alarms (Core-E, CorEvo, MPT-HC, MPT-HC-HQAM, MPT-HL,

18 — ATPC loop condition (MPT-HC, MPT-HC-HQAM, MPT-HL, MPT-HLC, MPT-HLS,

19 — DemXPIC LOS ............................................................................................... 341

20 — Loss of alignment (MPT-HC, MPT-HL, MPT-HLC, MPT-HLS, MPT-XP) ............................ 345

21 — Loss of frame (MPT-HC, MPT-HC-HQAM, MPT-HL, MPT-HLC, MPT-HLS, MPT-XP,

22 — RPS path fail (MPT-HC, MPT-MC, MPT-HL, MPT-HLC, MPT-XP).................................... 359

23 — Housekeeping alarms ..................................................................................... 365

8 9500 MPR Alarm Clearing

24 — LAG alarms (Core-E, CorEvo, MPT-HC, MPT-HL, MPT-HC-HQAM, MPT-HLC,

25 — Ethernet connectivity fault management alarms ................................................... 373

26 — Clock failure (MPT-HC, MPT-HC-HQAM, MPT-HL, MPT-HLC, MPT-HLS, MPT-XP,

27 — Duplicate Address Detected alarms.................................................................... 385

28 — Combiner loss of alignment (MPT-HLC or MPT-HLS) ................................................ 393

29 — Fan Fail (MPT-HLC) ........................................................................................ 399

30 — Fan Communication Problem (MPT-HLS).............................................................. 403

31 — RF Switch Fail (MPT-HLC or MPT-HLS)................................................................. 407

32 — Rx diversity missing (MPT-HLC or MPT-HLS) ......................................................... 411

9500 MPR Alarm Clearing 9

33 — Radio encryption mismatch (MPT-HC, MPT-HC-HQAM, MPT-HLC, MPT-HLS,

34 — Critical Link Event (Core-E, EASv2, P8ETH).......................................................... 419

36 — Rate mismatch (CorEvo).................................................................................. 427

10 9500 MPR Alarm Clearing

4 — Electrostatic-sensitive devices ............................................................................. 49

9500 MPR Alarm Clearing 11

12 9500 MPR Alarm Clearing

6 — Alarm and abnormal condition clearing procedures ................................................... 57

7 — Supporting information .................................................................................... 177

8 — Facility alarms ............................................................................................... 181

9 — Abnormal conditions ....................................................................................... 205

10 — Power alarms ............................................................................................... 219

11 — Equipment alarms ......................................................................................... 239

12 — Radio alarms (MPT-HC, MPT-HC-HQAM, MPT-HL, MPT-HLC, MPT-HLS, MPT-XP,

9500 MPR Alarm Clearing 13

14 — License/software mismatch ............................................................................. 289

15 — Internal loss of communications........................................................................ 295

16 — Threshold crossing alarms (MPT-HC, MPT-HC-HQAM, MPT-HL, MPT-HLC,