9500 MPR-A R5 1 0 Maintenance - TroubleClearing 3EM23956AOAA - 01

Maintenance and Trouble Clearing 3EM23956AO Edition 01
Alcatel-Lucent 9500
MICROWAVE PACKET RADIO for ANSI | RELEASE 5.1.0
Maintenance and Trouble Clearing
3EM23956AO Edition 01
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 2014 © Alcatel-Lucent. All rights reserved.
Alcatel-Lucent assumes no responsibility for the accuracy of the information presented, which is subject to change
without notice.
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 2014 Alcatel-Lucent.
All rights reserved.
Disclaimers
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.
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.
Table of Contents
1 — Preface .......................................................................................................... 21
1.1 — About the 9500 MPR-A documentation ............................................................................ 21
1.1.1 — Related documentation ....................................................................................... 22
1.2 — Audience ............................................................................................................... 23
1.3 — Information symbols ................................................................................................. 24
1.4 — Contact information.................................................................................................. 24
1.4.1 — Technical support .............................................................................................. 24
1.4.2 — Documentation ................................................................................................. 25
2 — FCC part 15 subpart B ....................................................................................... 27

2.1 — 9500 MPR-A unlicensed radio ....................................................................................... 27
2.2 — FCC Class B compliance statement ................................................................................ 27
2.3 — FCC Class B requirements ........................................................................................... 28
3 — Introduction ................................................................................................... 29
3.1 — Overview ............................................................................................................... 29
3.2 — Writing conventions .................................................................................................. 29
3.3 — Admonishments ....................................................................................................... 29
3.4 — Related documentation.............................................................................................. 30
3.5 — Document types....................................................................................................... 30
3.5.1 — Task index list (IXL) ............................................................................................ 30
3.5.2 — Routine task list (RTL)......................................................................................... 30
3.5.3 — Trouble analysis procedure (TAP) ........................................................................... 30
3.5.4 — Detailed level procedure (DLP) .............................................................................. 31
4 — Maintenance philosophy ..................................................................................... 33

4.1 — Troubleshooting....................................................................................................... 33
4.2 — Before going to site checklist....................................................................................... 34
4.3 — Troubleshooting basics .............................................................................................. 35
4.3.1 — Troubleshooting path problems .............................................................................. 36
4.4 — Path problems on a commissioned link ........................................................................... 37
4.4.1 — Weather-related path degradation .......................................................................... 37
4.4.2 — Changed antenna alignment or antenna feed problem .................................................. 37
4.4.3 — New path obstruction.......................................................................................... 38
4.4.4 — Interference from other signal sources ..................................................................... 38
4.5 — Path problems on a new link........................................................................................ 38
4.5.1 — Incorrect antenna alignment ................................................................................. 38
4.5.2 — Mismatching antenna polarizations.......................................................................... 38
4.5.3 — Incorrect path calculations ................................................................................... 38
4.5.4 — Reflections ...................................................................................................... 39
4.6 — Troubleshooting configuration problems ......................................................................... 39
4.6.1 — Compatibility problems ....................................................................................... 39
4.6.2 — Incorrect circuit connections................................................................................. 39
4.6.3 — Incorrect ID naming and commissioning .................................................................... 40
4.6.4 — Incorrect/incompatible trib settings ........................................................................ 40
4.7 — Troubleshooting Ethernet problems ............................................................................... 40
9500 MPR-A Maintenance and Trouble Clearing 3EM23956AO Edition 01 5

4.7.1 — Troubleshooting TMN problems .............................................................................. 41
5 — Safety awareness.............................................................................................. 43
5.1 — Safety EMC-EMF-ESD norms and equipment labeling ........................................................... 43
5.2 — Safety rules............................................................................................................ 43
5.2.1 — General rules ................................................................................................... 43
5.2.1.1 — Observe safety rules..................................................................................... 43
5.3 — Labels indicating danger, forbiddance, command .............................................................. 44
5.3.1 — Dangerous electrical voltages ................................................................................ 45
5.3.1.1 — Labeling: ................................................................................................. 45
5.3.1.2 — Safety instructions: ..................................................................................... 45
5.3.2 — Risks of explosions ............................................................................................. 46
5.3.2.1 — Labeling: ................................................................................................. 46
5.3.3 — Moving mechanical parts...................................................................................... 47
5.3.3.1 — Labeling: ................................................................................................. 47
5.3.4 — Equipment connection to earth.............................................................................. 47
5.3.4.1 — Labeling: ................................................................................................. 47
5.3.5 — Heat-radiating mechanical parts ............................................................................ 48
5.3.5.1 — Labeling: ................................................................................................. 48
5.3.6 — Microwave radiations (EMF norms) .......................................................................... 48
5.3.7 — Electromagnetic compatibility (EMC norms) ............................................................... 50
5.3.8 — Equipment protection against electrostatic discharges .................................................. 51
5.3.8.1 — Cautions to avoid equipment damage ................................................................ 52
5.3.8.2 — Anti static protection device kit ...................................................................... 52
5.3.8.3 — Screw fixing............................................................................................... 52
5.3.8.4 — MSS-ODU300 cable disconnection / connection ..................................................... 52
5.3.9 — Fan, equipment rack, and equipment cabinet precautions ............................................. 53
5.3.10 — Electrical precautions........................................................................................ 53
5.3.11 — Laser precautions ............................................................................................. 54
6 — Electrostatic-sensitive devices ............................................................................. 57

6.1 — Electrostatic-sensitivity ............................................................................................. 57
6.2 — Handling circuit packs ............................................................................................... 58
7 — Product support information ............................................................................... 59

7.1 — Telephone and email support ...................................................................................... 59
7.1.1 — Customer service telephone and email support ........................................................... 59
7.2 — Product documentation and training .............................................................................. 59
7.2.1 — Product documentation ....................................................................................... 59
7.2.2 — Training .......................................................................................................... 60
7.3 — Technical support center............................................................................................ 60
7.3.1 — After-hours emergency telephone support................................................................. 61
7.3.2 — After-hours non emergency telephone support ........................................................... 61
7.3.3 — On-site technical support ..................................................................................... 61
7.4 — Repair and return services .......................................................................................... 61
6 9500 MPR-A Maintenance and Trouble Clearing 3EM23956AO Edition 01

7.5 — Spare parts and replacement cards................................................................................ 62
7.5.1 — Return for credit or warranty exchange procedure....................................................... 62
7.6 — Service center......................................................................................................... 62
7.6.1 — Return for repair procedure .................................................................................. 63
7.6.2 — Shipping instructions for repair, credit, or warranty exchange......................................... 63
7.7 — Installation and maintenance services ............................................................................ 63
7.7.1 — Engineering and installation service ........................................................................ 64
7.7.2 — Contract maintenance service ............................................................................... 64
8 — IXL-100 Task index list ....................................................................................... 65
9 — IXL-101 Alarm and abnormal condition clearing procedures ........................................ 67

9.1 — Alarm manager / craft terminal ................................................................................... 68
9.1.1 — Equipment / facility column ................................................................................. 68
9.1.2 — Friendly name / entity column .............................................................................. 69
10 — IXL-102 Support procedures ............................................................................ 161
11 — IXL-103 Equipment replacement procedures........................................................ 163
12 — IXL-104 Supporting information ........................................................................ 165
13 — RTL-100 Preventive maintenance procedures ...................................................... 167
14 — TAP-100 Facility alarms .................................................................................. 169

14.1 — Purpose ..............................................................................................................169
14.2 — General ..............................................................................................................169
14.3 — Procedure ...........................................................................................................170
15 — TAP-101 Abnormal conditions .......................................................................... 189

15.1 — Purpose ..............................................................................................................189
15.2 — General ..............................................................................................................189
15.3 — Procedure ...........................................................................................................190
16 — TAP-102 Power alarms ................................................................................... 219

16.1 — Purpose ..............................................................................................................219
16.2 — General ..............................................................................................................219
16.3 — Procedure ...........................................................................................................220
17 — TAP-103 Equipment alarms.............................................................................. 227

17.1 — Purpose ..............................................................................................................227
17.2 — General ..............................................................................................................227
17.3 — Procedure ...........................................................................................................228
18 — TAP-104 Radio alarms (MPT-HC, MPT-HL, MPT-HLC, MPT-HLC, MPT-XP, MOD300,

ODU300, 9558HC) ................................................................................................ 245
18.1 — Purpose ..............................................................................................................245

18.2 — General ..............................................................................................................245
18.3 — Procedure ...........................................................................................................246
19 — TAP-105 Ethernet alarms (Core-E, EASv2, MPTACC, P8ETH, MSS-1 Shelf Core).............. 269
19.1 — Purpose ..............................................................................................................269
19.2 — General ..............................................................................................................269
19.3 — Procedure ...........................................................................................................269
20 — TAP-106 License/software mismatch.................................................................. 273

20.1 — Purpose ..............................................................................................................273
20.2 — General ..............................................................................................................273
20.3 — Procedure ...........................................................................................................273
21 — TAP-107 Internal loss of communications ............................................................ 279

21.1 — Purpose ..............................................................................................................279
21.2 — General ..............................................................................................................279
21.3 — Procedure ...........................................................................................................280
22 — TAP-108 Threshold crossing alarms (MOD300, MPT-HC, MPT-HL, MPT-HLC,

MPT-XP, 9558HC, P32E1DS1, MSS-1 shelf P32E1DS1) .................................................... 293
22.1 — Purpose ..............................................................................................................293
22.2 — General ..............................................................................................................293
22.3 — Procedure ...........................................................................................................294
23 — TAP-109 Synchronization alarms (Core-E, MOD300, MPT-HC, MPT-HL, MPT-HLC,

MPT-XP, P32E1DS1, SDHACC, 9558HC) ...................................................................... 303
23.1 — Purpose ..............................................................................................................303
23.2 — General ..............................................................................................................303
23.3 — Procedure ...........................................................................................................304
24 — TAP-110 ATPC loop conditions (MOD300, MPT-HC, MPT-HL, MPT-HLC, MPT-XP,

9558HC) ............................................................................................................ 315
24.1 — Purpose ..............................................................................................................315
24.2 — General ..............................................................................................................315
24.3 — Procedure ...........................................................................................................315
25 — TAP-111 Cable LOS ........................................................................................ 321

25.1 — Purpose ..............................................................................................................321
25.2 — General ..............................................................................................................321
25.3 — Procedure ...........................................................................................................321
26 — TAP-112 Loss of alignment (MOD300, MPT-HC, MPT-HL, MPT-HLC, MPT-XP,

9558HC) ............................................................................................................ 327
26.1 — Purpose ..............................................................................................................327
26.2 — General ..............................................................................................................327
26.3 — Procedure ...........................................................................................................327

27 — TAP-113 Loss of frame (MOD300, MPT-HC, MPT-HL, MPT-HLC, MPT-XP, 9558HC)........... 333
27.1 — Purpose ..............................................................................................................333
27.2 — General ..............................................................................................................333
27.3 — Procedure ...........................................................................................................333
28 — TAP-114 RPS path fail (MPT-HC, MPT-HL, MPT-HLC, MPT-XP, 9558HC) ........................ 345
28.1 — Purpose ..............................................................................................................345
28.2 — General ..............................................................................................................345
28.3 — Procedure ...........................................................................................................345
29 — TAP-115 Rx fail (MOD300) ............................................................................... 351

29.1 — Purpose ..............................................................................................................351
29.2 — General ..............................................................................................................351
29.3 — Procedure ...........................................................................................................351
30 — TAP-116 Housekeeping alarms.......................................................................... 357

30.1 — Purpose ..............................................................................................................357
30.2 — General ..............................................................................................................357
30.3 — Procedure ...........................................................................................................357
31 — TAP-117 LAG alarms (Core-E, MPT-HC, MPT-HL, MPT-HLC, MPT-XP, ODU300,

9558HC, MSS-1 shelf Core) ..................................................................................... 359
31.1 — Purpose ..............................................................................................................359
31.2 — General ..............................................................................................................359
31.3 — Procedure ...........................................................................................................359
32 — TAP-118 Ethernet connectivity fault management alarms ....................................... 363

32.1 — Purpose ..............................................................................................................363
32.2 — General ..............................................................................................................363
32.3 — Procedure ...........................................................................................................364
33 — TAP-119 Clock failure (MPT-HC, MPT-HL, MPT-HLC, MPT-XP, 9558HC) ........................ 367
33.1 — Purpose ..............................................................................................................367
33.2 — General ..............................................................................................................367
33.3 — Procedure ...........................................................................................................367
34 — TAP-120 Duplicate Address Detected alarms ........................................................ 375

34.1 — Purpose ..............................................................................................................375
34.2 — General ..............................................................................................................375
34.3 — Procedure ...........................................................................................................376
35 — TAP-121 Combiner loss of alignment (MPT-HLC).................................................... 383

35.1 — Purpose ..............................................................................................................383
35.2 — General ..............................................................................................................383
35.3 — Procedure ...........................................................................................................383
36 — TAP-122 Fan Fail .......................................................................................... 387

36.1 — Purpose ..............................................................................................................387

36.2 — General ..............................................................................................................387
36.3 — Procedure ...........................................................................................................387
37 — TAP-123 RF Switch Fail (MPT-HLC) .................................................................... 391

37.1 — Purpose ..............................................................................................................391
37.2 — General ..............................................................................................................391
37.3 — Procedure ...........................................................................................................391
38 — TAP-124 Rx diversity missing (MPT-HLC) ............................................................. 395

38.1 — Purpose ..............................................................................................................395
38.2 — General ..............................................................................................................395
38.3 — Procedure ...........................................................................................................395
39 — DLP-100 Mechanical card removal and installation ................................................ 399

39.1 — Purpose ..............................................................................................................399
39.2 — General ..............................................................................................................399
39.3 — Procedure ...........................................................................................................399
40 — DLP-101 MPT-HL/MPT-HLC transceiver air filter replacement ................................... 401

40.1 — Purpose ..............................................................................................................401
40.2 — General ..............................................................................................................401
40.3 — RECOMMENDED MATERIALS .......................................................................................401
40.4 — RECOMMENDED TOOLS.............................................................................................401
40.5 — Procedure ...........................................................................................................402
41 — DLP-102 SFP replacement ............................................................................... 403

41.1 — Purpose ..............................................................................................................403
41.2 — General ..............................................................................................................403
41.3 — Procedure ...........................................................................................................403
42 — DLP-103 Core switching module (Core-E) replacement ........................................... 405

42.1 — Purpose ..............................................................................................................405
42.2 — Perquisites ..........................................................................................................405
42.3 — General ..............................................................................................................405
42.4 — Procedure ...........................................................................................................406
43 — DLP-104 Core switching module (Core-E) flash card replacement .............................. 413
43.1 — Purpose ..............................................................................................................413
43.2 — Prerequisites ........................................................................................................413
43.3 — General ..............................................................................................................413
43.4 — Procedure ...........................................................................................................415
44 — DLP-105 Ethernet Access Switch replacement (EASv2 and P8ETH) ............................. 423
44.1 — Purpose ..............................................................................................................423
44.2 — Prerequisites ........................................................................................................423
44.3 — General ..............................................................................................................423
44.4 — Procedure ...........................................................................................................424

45 — DLP-106 MSS-4/8 shelf FAN replacement............................................................. 431
45.1 — Purpose ..............................................................................................................431
45.2 — Prerequisites ........................................................................................................431
45.3 — General ..............................................................................................................431
45.4 — Procedure ...........................................................................................................431
46 — DLP-107 MOD300 (radio modem) replacement...................................................... 433

46.1 — Purpose ..............................................................................................................433
46.2 — Prerequisites ........................................................................................................433
46.3 — General ..............................................................................................................433
46.4 — Procedure ...........................................................................................................434
47 — DLP-108 MPT-HL/MPT-HLC transceiver replacement .............................................. 437

47.1 — Purpose ..............................................................................................................437
47.2 — Prerequisites ........................................................................................................437
47.3 — General ..............................................................................................................437
47.4 — Procedure ...........................................................................................................438
48 — DLP-109 ODU300 replacement ......................................................................... 441

48.1 — Purpose ..............................................................................................................441
48.2 — Prerequisites ........................................................................................................441
48.3 — General ..............................................................................................................441
48.4 — Procedure ...........................................................................................................442
49 — DLP-110 P2E3DS3 (2-Port DS3) replacement ........................................................ 445

49.1 — Purpose ..............................................................................................................445
49.2 — Prerequisites ........................................................................................................445
49.3 — General ..............................................................................................................445
49.4 — Procedure ...........................................................................................................446
50 — DLP-111 P32E1DS1 (32-Port DS1) replacement ..................................................... 449

50.1 — Purpose ..............................................................................................................449
50.2 — Prerequisites ........................................................................................................449
50.3 — General ..............................................................................................................449
50.4 — Procedure ...........................................................................................................450
51 — DLP-112 Clean fiber-optic connectors ................................................................ 453

51.1 — Purpose ..............................................................................................................453
51.2 — Prerequisites ........................................................................................................453
51.3 — Recommended Tools...............................................................................................453
51.4 — General ..............................................................................................................454
51.5 — Procedure ...........................................................................................................454
52 — DLP-113 System power down and power up ......................................................... 459

52.1 — Purpose ..............................................................................................................459
52.2 — General ..............................................................................................................459
52.3 — Procedure ...........................................................................................................459

53 — DLP-114 MPTACC (MPT Access) replacement ........................................................ 463
53.1 — Purpose ..............................................................................................................463
53.2 — Prerequisites ........................................................................................................463
53.3 — General ..............................................................................................................463
53.4 — Procedure ...........................................................................................................464
54 — DLP-115 MPT ODU replacement (MPT-HC, MPT-XP, 9558HC) .................................... 467

54.1 — Purpose ..............................................................................................................467
54.2 — Prerequisites ........................................................................................................467
54.3 — General ..............................................................................................................467
54.4 — Procedure ...........................................................................................................468
55 — DLP-116 Auxiliary (AUX) replacement ................................................................ 473

55.1 — Purpose ..............................................................................................................473
55.2 — Prerequisites ........................................................................................................473
55.3 — General ..............................................................................................................473
55.4 — Procedure ...........................................................................................................473
56 — DLP-117 Protection upgrade and downgrade procedures......................................... 475

56.1 — Purpose ..............................................................................................................475
56.2 — General ..............................................................................................................475
56.3 — PDH protection .....................................................................................................475
56.4 — Radio protection ...................................................................................................475
56.5 — Modulation scheme ................................................................................................476
56.6 — Procedure ...........................................................................................................476
57 — DLP-118 Upgrade and downgrade radio profile ..................................................... 485

57.1 — Purpose ..............................................................................................................485
57.2 — General ..............................................................................................................485
57.3 — Radio profile ........................................................................................................485
57.4 — Procedure ...........................................................................................................486
58 — DLP-119 Upgrade unlicensed MPT-HL radio to lower 6 GHz radio .............................. 489
58.1 — Purpose ..............................................................................................................489
58.2 — General ..............................................................................................................489
58.3 — Procedure ...........................................................................................................489
59 — DLP-120 +24/-48 volt converter replacement....................................................... 493

59.1 — Purpose ..............................................................................................................493
59.2 — Prerequisites ........................................................................................................493
59.3 — General ..............................................................................................................493
59.4 — Procedure ...........................................................................................................494
60 — DLP-121 Power injector replacement................................................................. 497

60.1 — Purpose ..............................................................................................................497
60.2 — Perquisites ..........................................................................................................497
60.3 — General ..............................................................................................................497
60.4 — Procedure ...........................................................................................................498

61 — DLP-122 RPS/XPIC module replacement .............................................................. 501
61.1 — Purpose .............................................................................................................501
61.2 — Prerequisites ........................................................................................................501
61.3 — General ..............................................................................................................501
61.4 — Procedure ...........................................................................................................502
62 — DLP-123 Upgrade MPT ODU to MPT ODU L1 LAG port.............................................. 505

62.1 — Purpose ..............................................................................................................505
62.2 — General ..............................................................................................................505
62.3 — Procedure ...........................................................................................................506
63 — DLP-124 Upgrade MPT-HL to MPT-HL L1 LAG port.................................................. 509

63.1 — Purpose ..............................................................................................................509
63.2 — General ..............................................................................................................509
63.3 — Procedure ...........................................................................................................511
64 — DLP-125 MPT Power Unit replacement ............................................................... 515

64.1 — Purpose ..............................................................................................................515
64.2 — Prerequisites ........................................................................................................515
64.3 — General ..............................................................................................................515
64.4 — Procedure ...........................................................................................................516
65 — DLP-126 SDHACC (2-Port OC-3) Replacement ....................................................... 519

65.1 — PURPOSE.............................................................................................................519
65.2 — PREREQUISITES .....................................................................................................519
65.3 — GENERAL.............................................................................................................519
65.4 — Procedure ...........................................................................................................520
66 — DLP-127 Software package rollback ................................................................... 523

66.1 — Purpose ..............................................................................................................523
66.2 — General ..............................................................................................................523
66.3 — Procedure ...........................................................................................................524
67 — DLP-128 MSS-1 shelf replacement ..................................................................... 529

67.1 — Purpose ..............................................................................................................529
67.2 — Prerequisites ........................................................................................................529
67.3 — General ..............................................................................................................529
67.4 — Procedure ...........................................................................................................530
68 — DLP-129 Resolve WebEML/TCO Suite/NEtO startup issues ........................................ 533

68.1 — Purpose ..............................................................................................................533
68.2 — Prerequisites ........................................................................................................533
68.3 — General ..............................................................................................................533
68.4 — Procedure ...........................................................................................................534

List of Figures
5 — Safety awareness.............................................................................................. 43
Figure 5.1 — Compliance boundaries for 9500 MPR-A transceivers with 1ft (30 cm) antenna: .................. 50
Figure 5.2 — Anti static protection device kit........................................................................... 52
6 — Electrostatic-sensitive devices ............................................................................. 57

Figure 6.1 — Electrostatic-sensitive sign ................................................................................. 57
51 — DLP-112 Clean fiber-optic connectors ................................................................ 453

Figure 51.1 — Fiber-optic connector inspection .......................................................................455
Figure 51.2 — Fiber-optic connector types, illustrations .............................................................456
Figure 51.3 — Fiber-optic connector types, photographs.............................................................456
59 — DLP-120 +24/-48 volt converter replacement....................................................... 493

Figure 59.1 — +24/-48 Volt converter cabling diagram ...............................................................495

Figure 63.1 — MPT-HL to L1 LAG information message ...............................................................513
Figure 63.2 — MPT-HL to L1 LAG warning message ....................................................................513

Figure 66.1 — Software bank with upgrade software version Committed status .................................525
Figure 66.2 — Software bank with Initial software version Standby status ........................................525
Figure 66.3 — Software Management Action - Forced Activation ...................................................526
Figure 66.4 — Software bank with initial software version Committed status ....................................527
Figure 66.5 — Software bank with upgrade software version Standby status .....................................527

List of Tables
1 — Preface .......................................................................................................... 21
Table 1.1 — 9500 MPR-A documentation ................................................................................ 21
Table 1.2 — 9500 MPR-A related documentation....................................................................... 23
Table 1.3 — Information symbols ......................................................................................... 24
7 — Product support information ............................................................................... 59

Table 7.1 — Alcatel-Lucent addresses ................................................................................... 60
8 — IXL-100 Task index list ....................................................................................... 65

Table 8.1 — Task Index List ................................................................................................ 65
9 — IXL-101 Alarm and abnormal condition clearing procedures ........................................ 67

Table 9.1 — Equipment friendly name syntax definitions ............................................................ 69
Table 9.2 — Friendly name syntax definitions .......................................................................... 71
Table 9.3 — Alarm monitor alarm types ................................................................................. 73
Table 9.4 — Abnormal condition .........................................................................................135
Table 9.5 — Core-E Card LED indications ...............................................................................149
Table 9.6 — MSS-1 shelf LED indications ................................................................................150
Table 9.7 — Transport Card LED indications ...........................................................................151
Table 9.8 — Ethernet LED indications ...................................................................................152
Table 9.9 — MPT-HL transceiver LED alarm indications ..............................................................152
Table 9.10 — MPT-HLC transceiver LED alarm indications ...........................................................155
Table 9.11 — TMN network troubleshooting ...........................................................................158
10 — IXL-102 Support procedures ............................................................................ 161

Table 10.1 — Support procedures .......................................................................................161
11 — IXL-103 Equipment replacement procedures........................................................ 163

Table 11.1 — Equipment replacement procedures ....................................................................163
12 — IXL-104 Supporting information ........................................................................ 165

Table 12.1 — Supporting information ...................................................................................165
13 — RTL-100 Preventive maintenance procedures ...................................................... 167

Table 13.1 — Preventive maintenance procedures ...................................................................167
14 — TAP-100 Facility alarms .................................................................................. 169

Table 14.1 — Facility alarms .............................................................................................170
15 — TAP-101 Abnormal conditions .......................................................................... 189

Table 15.1 — Abnormal conditions ......................................................................................190
Table 15.2 — Abnormal conditions ......................................................................................204

16 — TAP-102 Power alarms ................................................................................... 219
Table 16.1 — Power Alarms ...............................................................................................220
17 — TAP-103 Equipment alarms.............................................................................. 227

Table 17.1 — Equipment alarms .........................................................................................228

ODU300, 9558HC) ................................................................................................ 245
Table 18.1 — Radio alarms ................................................................................................247
19 — TAP-105 Ethernet alarms (Core-E, EASv2, MPTACC, P8ETH, MSS-1 Shelf Core).............. 269
Table 19.1 — Ethernet alarms ............................................................................................269
20 — TAP-106 License/software mismatch.................................................................. 273

Table 20.1 — License/software mismatch alarms .....................................................................274
21 — TAP-107 Internal loss of communications ............................................................ 279

Table 21.1 — Internal communication problem alarms ..............................................................280
22 — TAP-108 Threshold crossing alarms (MOD300, MPT-HC, MPT-HL, MPT-HLC,

MPT-XP, 9558HC, P32E1DS1, MSS-1 shelf P32E1DS1) .................................................... 293
Table 22.1 — Threshold crossing alarms ................................................................................295

MPT-XP, P32E1DS1, SDHACC, 9558HC) ...................................................................... 303
Table 23.1 — Sync alarms .................................................................................................304

9558HC) ............................................................................................................ 315
Table 24.1 — ATPC loop conditions ......................................................................................316
25 — TAP-111 Cable LOS ........................................................................................ 321

Table 25.1 — Clear radio alarms .........................................................................................321
26 — TAP-112 Loss of alignment (MOD300, MPT-HC, MPT-HL, MPT-HLC, MPT-XP,

9558HC) ............................................................................................................ 327
Table 26.1 — Loss of alignment alarms .................................................................................328
27 — TAP-113 Loss of frame (MOD300, MPT-HC, MPT-HL, MPT-HLC, MPT-XP, 9558HC)........... 333
Table 27.1 — Loss of frame radio alarms ...............................................................................334
28 — TAP-114 RPS path fail (MPT-HC, MPT-HL, MPT-HLC, MPT-XP, 9558HC) ........................ 345
Table 28.1 — RPS path fail alarms .......................................................................................346
29 — TAP-115 Rx fail (MOD300) ............................................................................... 351

Table 29.1 — Rx fail alarms ...............................................................................................351

30 — TAP-116 Housekeeping alarms.......................................................................... 357
Table 30.1 — Housekeeping alarms ......................................................................................358

9558HC, MSS-1 shelf Core) ..................................................................................... 359
Table 31.1 — LAG alarms ..................................................................................................360
32 — TAP-118 Ethernet connectivity fault management alarms ....................................... 363

Table 32.1 — ECFM alarms ................................................................................................364
33 — TAP-119 Clock failure (MPT-HC, MPT-HL, MPT-HLC, MPT-XP, 9558HC) ........................ 367
Table 33.1 — Clock failure alarm ........................................................................................368
34 — TAP-120 Duplicate Address Detected alarms ........................................................ 375

Table 34.1 — Duplicate address detected alarms .....................................................................376
35 — TAP-121 Combiner loss of alignment (MPT-HLC).................................................... 383

Table 35.1 — Combiner loss of alignment alarm ......................................................................384
36 — TAP-122 Fan Fail .......................................................................................... 387

Table 36.1 — Fan fail alarm ..............................................................................................387
37 — TAP-123 RF Switch Fail (MPT-HLC) .................................................................... 391

Table 37.1 — Combiner loss of alignment alarm ......................................................................391
38 — TAP-124 Rx diversity missing (MPT-HLC) ............................................................. 395

Table 38.1 — Rx diversity missing alarm ................................................................................396
61 — DLP-122 RPS/XPIC module replacement .............................................................. 501

Table 61.1 — MPT ODU 1+1 module details ............................................................................502

Table 63.1 — MPT-HL L1 LAG bandwidth per service type ...........................................................510

Table 66.1 — Releases supporting software package rollback .....................................................523

1 — Preface
1.1 — About the 9500 MPR-A documentation

Table 1.1 describes the 9500 MPR-A documentation. See the Release Notice for part
numbers.
Table 1.1 — 9500 MPR-A documentation
Guide Description
Alcatel-Lucent Provides a general description of the radio, associated

9500 MPR-A components, applications, and some Engineering specifications
Product Information
Alcatel-Lucent Provides a detailed procedure for the initial installation of the
9500 MPR-A radio. Not intended for use during post initial installation
Installation Practices activities.
Alcatel-Lucent Provides task-oriented procedures describing how to perform
9500 MPR-A system operations including; provisioning, performance
Operation and monitoring, protection switching, and administration activities.
Administration This guide is intended to describe how-to provision, operate, and
monitor the radio.
Alcatel-Lucent Provides task-oriented procedures for system installation
9500 MPR-A Turn- verification, provisioning, turn-up, and acceptance testing. The
up guide is to be 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).
Alcatel-Lucent Provides task-oriented procedures that are related to the
9500 MPR-A maintenance of the radio including how to clear alarms, and
Maintenance and abnormal conditions, replace equipment. This guide is intended to
Trouble Clearing be used after the equipment has been installed and tested by the
installation and test teams.

1 — Preface
Table 1.1 — 9500 MPR-A documentation (Continued)
Guide Description
Alcatel-Lucent Provides information about the MSS-1c shelf including product

9500 MPR MSS-1c information, installation, turn-up, operation, and maintenance.
User Manual Intended to be used as the reference for all MSS-1c applications
Alcatel-Lucent 9500 Provides details for the MPR-e including: product information,
MPR MPR-e User installation, turn-up, operation, and maintenance. Intended to be
Manual used as the reference for all MPR-e applications.
Note: Unless otherwise stated in the guide, MPT-HC implies MPT-HC v2.
Note: Unless otherwise stated in the guide, the term EAS refers to both the P8ETH and
EASv2 cards.
1.1.1 — Related documentation

Table 1.2 describes the 9500 MPR-A related documentation. See the Release Notice for
part numbers.

1 — Preface
Table 1.2 — 9500 MPR-A 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 other information. TRDS tabs serve as
Results Data Sheet records of completion of indicated steps in a DLP. Not all DLPs
require entries in the TRDS.
Alcatel-Lucent Provides transmit power specifications
9500 MPR-A MPT-
HL Engineering
Specifications
Alcatel-Lucent
9500 MPR-A MPT-
HC/MPT-XP/MPR-e
Engineering
Specifications
Alcatel-Lucent
9500 MPR-A
ODU300
Engineering
Specifications
Alcatel-Lucent Provides part number and tuning information for MPT-HC/XP
9500 MPR radios with and without external diplexers
Frequency Plan for
MPT-HC/XP/
9558HC
1.2 — 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.

1 — Preface
1.3 — 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.
Table 1.3 describes the symbols that are contained in the 9500 MPR-A documentation.
Table 1.3 — Information symbols
Symbol Meaning Description
Danger 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 Warning indicates that the described activity or situation may, or will, cause
equipment damage or serious performance problems.
Caution Caution indicates that the described activity or situation may, or will, cause
service interruption.
Note Note provides information that is, or may be, of special interest.
1.4 — Contact information
1.4.1 — Technical support

If you purchased a service agreement for your 9500 MPR-A 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:

1 — Preface
Web: http://support.alcatel-lucent.com
1.4.2 — Documentation
If you have questions or comments about this documentation, please contact:
documentation.feedback@alcatel-lucent.com

1 — Preface

2 — FCC part 15 subpart B
2.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.
2.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.

2 — FCC part 15 subpart B
2.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: Possibility of service interruption. 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: Possibility of service interruption. 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.

3 — Introduction
3.1 — Overview
This manual provides step-by-step procedures to enable the user to perform a task. Each
procedure contains important introductory information that is essential to understanding
and completing the task properly. Procedures must be started at step 1, and steps must be
performed in the order given. Failure to do so may cause unforeseen hazardous conditions.
3.2 — Writing conventions

Boldface characters indicate commands or parameters the user must enter or keys the user
must press. Enter input parameters exactly as shown in the examples.
3.3 — Admonishments
To avoid hazardous conditions, observe the following admonishments:
Danger: Possibility of personal injury.
Caution: Possibility of service interruption.
Warning: Possibility of equipment damage.

3 — Introduction
3.4 — Related documentation

For additional system information, refer to the following related documents:
• Alcatel-Lucent 9500 MPR-A Product Information

• Alcatel-Lucent 9500 MPR-A Installation Practices
• Alcatel-Lucent 9500 MPR-A Operation and Administration
• Alcatel-Lucent 9500 MPR-A Turn-up
• Alcatel-Lucent 9500 MPR-A Engineering Support Documentation
• Alcatel-Lucent 9500 MPR MPR-e User Manual
• Alcatel-Lucent 9500 MPR MSS-1c User Manual
3.5 — Document types

The documentation contains all instructions needed to perform a task. This manual consists
of the following types of documents:
• Task Index List (IXL)

• Routine Task List (RTL)
• Trouble Analysis Procedure (TAP)
• Detailed Level Procedure (DLP)
3.5.1 — Task index list (IXL)

IXLs group procedures by function. Each IXL lists procedures alphabetically by name and
refers the user to the appropriate procedure number.
3.5.2 — Routine task list (RTL)

The RTL is a list of preventive maintenance procedures which recommends a schedule
(monthly, semiannual, or annual) for the performance of each procedure.
3.5.3 — Trouble analysis procedure (TAP)

3 — Introduction
TAPs contain sequential steps required to perform trouble clearing. Trouble clearing
involves clearing and repairing malfunctions in the system. Trouble clearing may be done
to answer a customer complaint or to respond to an office alarm, a trouble report, or an
abnormal display. Steps can refer to other procedures.
3.5.4 — Detailed level procedure (DLP)

DLPs contain detailed steps and supporting information required to complete tasks. When
a DLP is referenced from another part of the manual, perform the DLP, then return to the
point where the DLP was referenced.

3 — Introduction

4 — 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.
4.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 TAP is
referenced in the IXL.

• 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 DLPs.
• 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 DLPs.
• 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 DLPs.
• 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 TAPs fail to clear the fault, an obscure or multiple fault is assumed to exist.
4.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-A 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-A 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-A, rather than in 9500
MPR-A? Are there alarms on other, connected equipment?
• 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-A 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-A 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.
4.3 — Troubleshooting basics

This section provides general guidance on 9500 MPR-A troubleshooting:
Check front-panel LED indications. These provide summary alarm indications, which can
help narrow down the location and type of failure. See addresses IXL-101 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-A with Craft Terminal, the opening
screen is the Main Screen. Use the information provided to check for severity and problem
type. See Table 9.3 for probable cause and recommended action.
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-A 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.
4.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.

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

4.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.
4.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.
4.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
4.5.1 — Incorrect antenna alignment

One or both antennas incorrectly aligned. Refer to Alcatel-Lucent 9500 MPR-A Turn-up
manual, Antenna Polarization Verification (DLP-105) Antenna Feedhorn Verification -
XPD Procedure.
4.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.
4.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.
4.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.
4.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
4.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.
4.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).
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-A network, beginning at the node closest to the node applying
the BER test.
4.6.3 — Incorrect ID naming and commissioning

All traffic-carrying circuits must have a unique flow ID for the cross-connect capability to
operate.
4.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.
4.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 9.8 for
LEDs that are locally at the alarmed site.
In order for the green Link LED to light:
• Cable must be connected to Ethernet port

• Ethernet port must be enabled (provisioned Enabled on Core Settings Screen)
• 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.
4.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 9.11 for information about TMN network troubleshooting.


5 — Safety awareness
5.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
5.2 — Safety rules
5.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
5.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.

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,
inscriptions etc.
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, i.e., 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:
5.3 — Labels indicating danger, forbiddance, 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 handbook refers to.
5.3.1 — Dangerous electrical voltages
5.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 to it will state that
the equipment will have to be grounded before connecting it to the power supply voltage,
e.g.:
5.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.
5.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 gasses
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.

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

5.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.
5.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-A 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, i.e. 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 5.1 — Compliance boundaries for 9500 MPR-A transceivers with 1ft (30 cm)
antenna:
5.3.7 — Electromagnetic compatibility (EMC norms)

The equipment's EMC norms depend on the type of installation being carried out (cable
termination, grounding etc.,) and on the operating conditions (equipment, setting options of
the electrical/electronic units, presence of dummy covers, etc.).
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:
• 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 (contact springs and connection points, etc.)
• Screw fasten the units to the subrack.
• To correctly install EMC compatible equipment follow the instructions given.
• 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
(dummy covers, ESD connector protections, etc.)
• To properly use EMC compatible equipment observe the information given
• 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 (contact springs and
connection points, etc.)
• Clean the dummy covers of the spare units as well.
• Screw fasten the units to the subrack.
5.3.8 — Equipment protection against electrostatic discharges

Before removing the ESD protections from the monitors, connectors etc., 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 5.2.
5.3.8.1 — Cautions to avoid equipment damage
5.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 5.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 5.2 — Anti static protection device kit
5.3.8.3 — Screw fixing
In normal operation conditions, all screws (for unit box closing, cable fixing, etc.) 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.
5.3.8.4 — MSS-ODU300 cable disconnection / connection

To avoid equipment damage, always unplug the MOD300 card first before disconnecting
the MSS-ODU300 cable (at MSS or ODU300 side).
5.3.9 — Fan, equipment rack, and equipment cabinet

precautions
When installing the equipment observe the following:
Danger: Possibility of personal injury. 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.
Danger: Possibility of personal injury. The 9500 MPR-A 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.
Danger: Possibility of personal injury. The 9500 MPR-A requires at least three people
to lift and carry an equipment rack populated with 9500 MPR-A equipment. To
prevent equipment damage or personal injury, make sure you have enough help or
the appropriate lifting and transporting equipment.
Danger: Possibility of personal injury. The 9500 MPR-A requires at least two people to
align and secure an equipment rack populated with 9500 MPR-A equipment. To
prevent equipment damage or personal injury, make sure you have enough help.
Danger: Possibility of personal injury. 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-A in it. For approved methods of securing
the equipment rack, read the equipment-rack installation instructions or contact the
equipment-rack manufacturer.
5.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: Possibility of personal injury. Install the t 9500 MPR-A 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.
Danger: Possibility of personal injury. 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-A. 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.
Danger: Possibility of personal injury. 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.
Danger: Possibility of personal injury. 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-A before you connect any other wires to the node.
Danger: Possibility of personal injury. 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-A. 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.
5.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: Possibility of personal injury. The use of controls and/or adjustments, or the
performance of procedures other than those specified herein may result in hazardous
infrared radiation exposure.
Danger: Possibility of personal injury. 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.
Danger: Possibility of personal injury. Never look directly into an unterminated

fiber-optic connector unless it is absolutely known that no optical power is being
emitted by the connector.
Danger: Possibility of personal injury. Never look into a broken optical fiber cable
unless it is absolutely known that no laser radiation is present.
Danger: Possibility of personal injury. 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.
Danger: Possibility of personal injury. 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.
Danger: Possibility of personal injury. 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.
Danger: Possibility of personal injury. 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:
• Always remove electrical power from fiber-optic transmitters before disconnecting

fiber-optic connectors in the path between the transmitter and the receiver.
• 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.

6 — Electrostatic-sensitive devices
6.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: Possibility of equipment damage. 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 6.1.
Figure 6.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

6 — Electrostatic-sensitive devices
• JFET (Junction Field Effect Transistors)

• IGFET (Insulated Gate Field Effect Transistors)
6.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: Possibility of equipment damage. 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.

7 — Product support information
7.1 — Telephone and email support
7.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/
7.2 — Product documentation and training
7.2.1 — Product documentation

Product documentation is available through Alcatel-Lucent’s OnLine Customer Support
(OLCS) web site at:
http://www.alcatel-lucent.com/myaccess
At Alcatel-Lucent’s OnLine Customer Support web site, follow the on-screen instructions
to register for access and obtain a login 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)
7.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 to call the Technical Assistance Center. 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:
Table 7.1 — Alcatel-Lucent addresses
IN USA: IN CANADA:
Alcatel-Lucent USA Alcatel-Lucent Canada

3400 W. Plano Pkwy. Network Services Division
Plano, Texas 75075 P.O. Box 13600
ATTN: Training M/S 1206-553 Ottawa, Ontario K2K 2E6
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
7.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.
7.3.1 — After-hours emergency telephone support

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
7.3.2 — After-hours non emergency 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.
7.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,
the age of the product, etc.
7.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.
7.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.
7.5.1 — Return for credit or warranty exchange procedure

Returned equipment must have a Parts Request (PR) number. Obtain an PR number by
calling Alcatel-Lucent.
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
7.6 — 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.

7.6.1 — Return for repair procedure

See the Return for credit or warranty exchange procedure section 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
7.6.2 — Shipping instructions for repair, credit, or

warranty exchange
Return equipment or parts prepaid to the address provided when the PR number was issued.
The PR number must be prominently marked on the shipping label, the packing list, and
any correspondence regarding the order.
• 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.
7.7 — Installation and maintenance services

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

8 — IXL-100 Task index list
Table 8.1 lists the type of procedure or information needed to perform maintenance and
trouble clearing on the system.
Table 8.1 — Task Index List
Type of procedure/information
IXL-101 Alarm and abnormal condition clearing procedures

IXL-102 Support procedures
IXL-103 Equipment replacement procedures
IXL-104 Supporting information
RTL-100 Preventive maintenance procedures

8 — IXL-100 Task index list

9 — IXL-101 Alarm and abnormal
condition clearing procedures
See Table 9.3 to identify alarms reported by the Alarm Manager and the corresponding
procedure, which describes how to clear the alarm.
See Table 9.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 9.5 to identify Core-E card LED alarm indications and the corresponding
procedure, which describes how to clear the condition type.
See Table 9.6 to identify MSS-1 shelf CORE LED alarm indications and the corresponding
procedure, which describes how to clear the condition type.
See Table 9.7 to identify Transport card status LED alarm indications and the
corresponding procedure, which describes how to clear the condition type.
See Table 9.8 to identify Ethernet LED alarm indications and the corresponding procedure,
which describes how to clear the condition type.
See Table 9.9 to identify MPT-HL Transceiver LED alarm indications and the
See Table 9.10 to identify MPT-HLC Transceiver LED alarm indications and the
See Table 9.11 to identify TMN Network Trouble conditions and troubleshooting
techniques, which describes how to clear the condition type.
This manual supports alarm naming conventions for the Alarm Monitor.
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:

9 — IXL-101 Alarm and abnormal condition clearing procedures
Diagnosis>Abnormal Condition List
9.1 — Alarm manager / craft terminal
9.1.1 — Equipment / facility column

The EQUIPMENT/FACILITY column in Table 9.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
• EASv2: 8-Port Ethernet Access Switch, second generation
• FAN: MSS-4/8 Fan card
• MOD300: Radio Modem card
• MPTACC: MPT Access card
• MSS: MSS-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
• 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

• DS3: DS3 facility supported by P2E3DS3 card
• DS1: DS1 facility supported by P32E1DS1 card
• EASv2: Ethernet facility supported by the EASv2 card
• MOD300: IF facility supported by MOD300 card

• MPT-HC: RF facility supported by MPT-HC/MPT-XP/9558HC (MPT ODU) outdoor

unit
• MPT-HL: RF facility supported by MPT-HL Transceiver card
• MPT-HLC: RF facility supported by MPT-HLC Transceiver card
• MSS/CORE: Ethernet facility supported by the MSS-1 shelf
• MSS/DS1:DS1 facility supported by the MSS-1 shelf
• OC-3: OC-3 facility supported by SDHACC card
• P8ETH: Ethernet facility supported by the P8ETH card
9.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 9.1.
Table 9.1 — Equipment friendly name syntax definitions
Location Syntax Values Description
Rack r r01 Rack number

Table 9.1 — Equipment friendly name syntax definitions (Continued)
Subrack s s1 Subrack number for MSS-1, MSS-4, and MSS-8 shelves

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 card
(P8ETH 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/CORE (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/CORE (Core-E slot number
and Ethernet port number associated with MPT-HL
Transceiver)
s[3-8] Subrack number for ODU300 connected to MOD300 card
(MOD300 slot number associated with ODU300)
Board b board#[1-9] 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/CORE
daughter#[03-04] Daughter SFP port number of equipment in alarm associated
with MPTACC card
with EASv2 or P8ETH card
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 9.2.
Table 9.2 — Friendly name syntax definitions
Facility f DS-1-in, out DS1 facility and direction

Name
DS-3-in, out DS3 facility and direction
EleSdh-in OC-3 facility and direction (supported by electrical SFP)
OptSdh-in 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/CORE (Core-E slot number and port
number)
Dir#[3-8].[5-8] Radio direction of MPT-HL and MPT-HLC radio channel in
alarm connected to EASv2 or P8ETH card (EASv2/P8ETH slot
number and port number)
Dir#1.[5-6] Radio direction of MPT-HL and MPT-HLC radio channel in
alarm connected to Core-E card or MSS/CORE (Core-E slot
number and port number)
Dir#[3-8] Radio direction of ODU300 radio channel in alarm connected
to MOD300 card (MOD300 slot 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 9.2 — Friendly name syntax definitions (Continued)
Port p Port#[1-16] DS1 port number of facility in alarm on MSS-1 shelf

Number
Port#[1-32] DS1 port number of facility in alarm on P32E1DS1
Port#[1-2] DS3 port number of facility in alarm
Port#[1-2] OC-3 port number of facility in alarm
Port#[1-6] Ethernet port number of facility in alarm associated with
Core-E card or MSS/CORE
Port#[1-8] Ethernet port number of facility in alarm associated with
EASv2 and P8ETH card
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 ODU300 #6
channel #0 (spare) associated with MOD300 card in slot #6]
Table 9.3 describes the alarms that are reported by the Alarm Manager and the
corresponding procedure to clear the alarm.
Table 9.3 — Alarm monitor alarm types
Probable cause Friendly name/entity Facility/ Description See

equipment
AIS DS1-in/MSS/DS1/Port#[1- DS1 on AIS detected incoming to TAP-100

16] MSS-1 shelf the PDH card from the Facility alarms
demarcation panel for the
DS1-in/Slot#[3-8]/Port#[1- DS1 on DS1 or DS3 facility.
32] P32E1DS1
DS3-in/Slot#[3-8]/Port#[1- DS3
2]

Table 9.3 — Alarm monitor alarm types (Continued)

equipment
AIS EleSdh-in/slot#[3-8]/Port[1- OC-3 AIS detected incoming to TAP-100

2] the SDHACC card from Facility alarms
the demarcation panel for
OptSdh-in/slot#[3-8]/ the OC-3 facility.
Port[1-2]
AIS DS1-out/MSS/DS1/Port# DS1 on AIS detected from the TAP-100
[1-16] MSS-1 shelf Core-E switch matrix for Facility alarms
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]
AIS EleSdh-out/slot#[3-8]/ OC-3 AIS detected from the TAP-100
Port[1-2] Core-E switch matrix for Facility alarms
the OC-3 facility,
OptSdh-out/slot#[3-8]/ indicating an upstream
Port[1-2] failure.
ATPC loop Radio/Dir#1.[1-6]/ MPT ODU Reported for a ATPC High TAP-100
problem Slot#1/Port#[1-6]/Ch#[0-1] connected to Power Time-out. When Facility alarms
Core-E ATPC is enabled, the local
transmitter was operating
continuously at full power
for 5 minutes, and the
transmitter was reduced to
its minimum 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.


equipment
ATPC loop Radio/Dir#1.[1-6]/MSS/ MPT ODU Reported for a ATPC High TAP-100
problem CORE/Port#[1-6]/Ch#[0-1] connected to Power Time-out. When Facility alarms
(continued) MSS/CORE ATPC is enabled, the local
transmitter was operating
Radio/Dir#[3-8].[1-4]/ MPT ODU continuously at full power
Slot#[3-8]/Port#[1-4]/ connected to for 5 minutes, and the
Ch#[0-1] MPTACC transmitter was reduced to
Radio/Dir#[3-8].[5-8]/ MPT ODU
and this condition
Slot#[3-8]/Port#[5-8]/Ch#1 connected to
notification was
P8ETH
Radio/Dir#[3-8].1-4]/ MPT ODU will remain active until a
Slot#[3-8]/Port#[1-4]/ connected to message is received that
Ch#[1] EASv2 the active receiver at the
Radio/Dir#[3-8].[5-8]/ MPT ODU longer requesting
Slot#[3-8]/Port#[5-8]/ connected to additional transmitter
Ch#[0-1] EASv2 power.
Radio/Dir#1.[5-6]/ MPT-HL
Slot#1/Port#[5-6]/Ch#1 connected to
Core-E
Radio/Dir#1.[5-6]/MSS/ MPT-HL
CORE/Port#[5-6]/Ch#1 connected to
MSS/CORE
Radio/Dir#[3-8].[5-8]/ MPT-HL
Slot#[3-8]/Port#[5-8]/ connected to
Ch#[0-1] EASv2,
P8ETH
Radio/Dir#1.[5-6]/ MPT-HLC
Slot#1/Port#[5-6]/Ch#[0-1] connected to
Core-E
Radio/Dir#1.[5-6]/MSS/ MPT-HLC
CORE/Port#[5-6]/Ch#[0-1] connected to
MSS/CORE


equipment
ATPC loop Radio/Dir#[3-8].[5-8]/ MPT-HLC Reported for a ATPC High TAP-100

problem Slot#[3-8]/Port#[5-8]/ connected to Power Time-out. When Facility alarms
(continued) Ch#[0-1] EASv2, ATPC is enabled, the local
P8ETH transmitter was operating
continuously at full power
Radio/Dir#[3-8]/Ch#[0-1] MOD300 for 5 minutes, and the
transmitter was reduced to
and this condition
notification was
will remain active until a
message is received that
the active receiver at the
longer requesting
additional transmitter
power.
Bandwidth ERP#[1-2]#[1-2] Core-E An ERPS Instance has TAP-105
degrade for entered a Protection state. Ethernet alarms
protection (Core-E, EASv2,
switch MPTACC,
P8ETH, MSS-1
Shelf Core)


equipment
Bandwidth over Radio/Dir#1.[1-6]/ MPT ODU While the MPT ODU/ TAP-104 Radio
flow Slot#1/Port#[1-6]/Ch#[0-1] connected to MPT-HL was not alarms
Core-E communicating with the (MPT-HC,
Core-E, EASv2, P8ETH, MPT-HL,
Radio/Dir#1.[1-6]/MSS/ MPT ODU or MSS/CORE, TDM/ MPT-HLC,
CORE/Port#[1-6]/Ch#[0-1] connected to SDH cross-connections MPT-HLC,
MSS/CORE were provisioned with a MPT-XP,
Radio/Dir#[3-8].[1-4]/ MPT ODU total bandwidth which MOD300,
connected to exceeds the net bandwidth ODU300,
Slot#[3-8]/Port#[1-4]/
MPTACC capacity of the radio 9558HC)
Ch#[0-1]
profile.
P8ETH
Radio/Dir#[3-8].1-4]/ MPT ODU
Ch#[1] EASv2

Ch#[0-1] EASv2
Core-E
MSS/CORE
Ch#[0-1] EASv2,
P8ETH
Core-E
MSS/CORE


equipment
Battery failure • r01/subrack#1 MSS-1/4/8 An A battery feed failed or TAP-102 Power

is missing. alarms
Cable LOS Radio/Dir#[3-8]/Ch#[0-1] MOD300 Bad cable connection at IF TAP-111 Cable
in/out connector on LOS
MOD300 card.
CLA Radio/Dir#1.[1-6]/ MPT ODU The standby transmitter TAP-104 Radio
Slot#1/Port#[1-6]/Ch#[0-1] connected to has/had a silent failure alarms
Core-E which caused the far end (MPT-HC,
to request a HSB switch. MPT-HL,
Radio/Dir#1.[1-6]/MSS/ MPT ODU MPT-HLC,
CORE/Port#[1-6]/Ch#[0-1] connected to MPT-HLC,
MSS/CORE MPT-XP,
Radio/Dir#[3-8].[1-4]/ MPT ODU MOD300,
connected to ODU300,
Slot#[3-8]/Port#[1-4]/
MPTACC 9558HC)
Ch#[0-1]
Ch#[0-1] EASv2
Ch#[0-1] EASv2,
P8ETH
Core-E
MSS/CORE
Radio/Dir#[3-8].[5-8]/ MPT-HLC
Ch#[0-1] EASv2
Radio/Dir#[3-8]/Ch#[0-1] MOD300


equipment
Clock failure Radio/Dir#1.[1-6]/ MPT ODU The MPT ODU/MPT-HL TAP-119 Clock
Slot#1/Port#[1-6]/Ch#[0-1] connected to is not able to lock the air failure
Core-E Tx symbol rate to the NE (MPT-HC,
clock. MPT-HL,
CORE/Port#[1-6]/Ch#[0-1] connected to MPT-XP,
MSS/CORE 9558HC)
Ch#[0-1] MPTACC

P8ETH
Ch#[1] EASv2

Ch#[0-1] EASv2
Core-E
MSS/CORE
Ch#[0-1] EASv2,
P8ETH
Core-E
MSS/CORE


equipment
Combiner Loss r01/subrack#1[5-6] MPT-HLC Non-alignment status TAP-121

of alignment connected to detected between main Combiner loss of
Core-E, and diversity flows in alignment
MSS/CORE configurations with (MPT-HLC)
combiner
r01/subrack#[3-8][5-8] MPT-HLC
connected to
EASv2
Degrade SyncSource/Sync-in/Port#1 Core-E Frequency of the source TAP-109
signal is degraded. Synchronization
SyncSource/ETH/slot#1/ Core-E User Managed only if the alarms (Core-E,
Port#[1-6] Ethernet Port interface has been MOD300,
configured as a primary or MPT-HC,
SyncSource/ETH/MSS/ MSS-1 User
secondary MPT-HL,
CORE/Port#[1-6] Ethernet Port
synchronization source. MPT-HLC,
SyncSource/ETH/ EASv2 User MPT-XP,
Ethernet Port P32E1DS1,
slot#[3-8]/Port#[1-8]
SDHACC,
SyncSource/Radio/Dir# MOD300 9558HC)
[3-8]/Ch#[0-1]
SyncSource/Radio/Dir#1. MPT ODU
[1-6]/Slot#1/Port#[1-6]/ connected to
Ch#1 Core-E
SyncSource/Radio/Dir#1. MPT ODU

[1-6]/MSS/CORE/ connected to
MSS/CORE
Port#[1-6]/Ch#1
SyncSource/Radio/ MPT ODU
Dir#[3-8].[1-4]/Slot#[3-8]/ connected to
EASv2,
Port#[1-4]/Ch#1
MPTACC
SyncSource/Radio/ MPT ODU
Dir#[3-8].[5-8]/Slot#[3-8]/ connected to
EASv2,
Port#[5-8]/Ch#1
P8ETH


equipment
Degrade SyncSource/Radio/ MPT-HL, Frequency of the source TAP-109

(continued) Dir#[3-8].[5-8]/Slot#[3-8]/ MPT-HLC signal is degraded. Synchronization
connected to Managed only if the alarms (Core-E,
Port#[5-8]/Ch#[0-1]
P8ETH interface has been MOD300,
configured as a primary or MPT-HC,
SyncSource/Radio/ MPT-HL, secondary MPT-HL,
Dir#1.[5-6]/Slot#1/ MPT-HLC synchronization source. MPT-HLC,
connected to MPT-XP,
Port#[5-6]/Ch#1
Core-E P32E1DS1,
SyncSource/Radio/ MPT-HL, SDHACC,
MPT-HLC 9558HC)
Dir#1.[5-6]/MSS/CORE/
connected to
Port#[5-6]/Ch#1
MSS/CORE
SyncSource/ MPT ODU,
RadioLAG#[1-14] MPT-HL,
MPT-HLC
connected to
EASv2,
P8ETH
SyncSource/E1DS1-in/ P32E1DS1
Slot#[3-8]/Port#[1-32]
SyncSource/E1DS1in/ MSS/DS1
MSS/DS1/Port#[1-16]
SyncSource/EleSdh-in/ OC-3
slot#[3-8]/Port[1-2]
SyncSource/OptSdh-in/
slot#[3-8]/Port[1-2]
Degrade SyncSource/RadioLAG# ODU Signal on the Radio LAG TAP-117 LAG
[1-14] interface is degraded. alarms (Core-E,
MPT-HC,
MPT-HL,
MPT-HLC,
MPT-XP,
ODU300,
9558HC, MSS-1
shelf Core)


equipment
Degrade SyncSource/EthLAG#[1- Core-E, A member(s) of an TAP-117 LAG

14] MSS/CORE Ethernet or Radio LAG alarms (Core-E,
group has no activity. MPT-HC,
Degrade is declared when MPT-HL,
SyncSource/RadioLAG#[1- MPT ODU, the number of active ports MPT-HLC,
14] MPT-HL, in the LAG are greater MPT-XP,
MPT-HLC, than zero and less than the ODU300,
ODU300 LAG size. 9558HC, MSS-1
shelf Core)
DemXPIC LOS r01s1b1[1-6]/daughter#04 MPT ODU Bad or missing cable/ TAP-111 Cable
connected to cable connection at XPIC LOS
Core-E, connector on MPT ODU.
MSS/CORE
r01s1/b[3-8][1-4]/ MPT ODU
daughter#04 connected to
MPTACC
r01s[3-8][5-8]b1/ MPT ODU
P8ETH
connected to
EASv2
r01/subrack#1[5-6] MPT-HLC
connected to
Core-E,
MSS/CORE


equipment
Demodulator Radio/Dir#1.[1-6]/ MPT ODU Loss of receive signal, bad TAP-104 Radio
fail Slot#1/Port#[1-6]/Ch#[0-1] connected to receive signal, or internal alarms
Core-E receive circuit failure. (MPT-HC,
MPT-HL,
MSS/CORE MPT-XP,
Slot#[3-8]/Port#[1-4]/
MPTACC 9558HC)
Ch#[0-1]
P8ETH
Ch#[1] EASv2

Ch#[0-1] EASv2
Core-E
MSS/CORE
Ch#[0-1] EASv2,
P8ETH


equipment
Demodulator Radio/Dir#1.[5-6]/ MPT-HLC Loss of receive signal, bad TAP-104 Radio

fail (conitnued) Slot#1/Port#[5-6]/Ch#[0-1] connected to receive signal, or internal alarms
Core-E receive circuit failure. (MPT-HC,
MPT-HL,
Radio/Dir#1.[5-6]/MSS/ MPT-HLC MPT-HLC,
MSS/CORE MPT-XP,
Radio/Dir#[3-8].[5-8]/ MPT-HLC MOD300,
Slot#[3-8]/Port#[5-8]/
EASv2, 9558HC)
Ch#[0-1]
P8ETH
Dialog failure r01/subrack#1[1-6] MPT ODU Temporary Loss of TAP-107
connected to communication with Internal loss of
Core-E, MPT ODU/MPT-HL/ communications
MSS/CORE MPT-HLC
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
connected to
EASv2,
P8ETH
r01/subrack#1[5-6] MPT-HL,
MPT-HLC
connected to
Core-E,
MSS/CORE


equipment
Duplicate TMNEthernet/MngtPort Core-E/TMN Duplication of IPv6 TAP-120

address detected MGMT Port Global Unicast address Duplicate
detected on TMN Address
TMNEthernet/Port#4 Core-E/TMN management port, Port#4, Detected alarms
Port#4 In-Band port 1-2
TMNInBand#[1-2] Core-E/TMN
In-Band Port
[1-2]
Duplicate PPP-IP/RF#[3-8] MOD300 Duplication of IPv6 TAP-120
address detected Global Unicast address Duplicate
PPP-IP/RF#1[1-6] MPT ODU detected on TMN-RF over Address
connected to PPP Detected alarms
Core-E,
MSS/CORE
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
connected to
EASv2,
P8ETH
PPP-IP/RF#1[5-6] MPT-HL,
MPT-HLC
connected to
Core-E,
MSS/CORE
PPP-IP/RF/LAG#[1-14] MPT ODU,
MPT-HL,
MPT-HLC,
ODU300


equipment
Early warning Radio/Dir#1.[1-6]/ MPT ODU 10E-9 BER detected TAP-104 Radio
indication Slot#1/Port#[1-6]/Ch#[0-1] connected to alarms
Core-E (MPT-HC,
MPT-HL,
MSS/CORE MPT-XP,
Slot#[3-8]/Port#[1-4]/
MPTACC 9558HC)
Ch#[0-1]
P8ETH
Ch#[1] EASv2

Ch#[0-1] EASv2
Core-E
MSS/CORE
Ch#[0-1] EASv2,
P8ETH
Core-E
MSS/CORE


equipment
Early warning Radio/Dir#[3-8].[5-8]/ MPT-HLC 10E-9 BER detected TAP-104 Radio

indication Slot#[3-8]/Port#[5-8]/ connected to alarms
(continued) Ch#[0-1] EASv2, (MPT-HC,
P8ETH MPT-HL,
MPT-HLC,
Radio/Dir#[3-8]/Ch#[0-1] MOD300 MPT-HLC,
MPT-XP,
MOD300,
ODU300,
9558HC)
Eth OAM loss MEP#MDID[1-16]#MA ID Core-E, MEP received no CCM TAP-118
of continuity [1-512]#MEPID[1-8191] MSS/CORE frames from a peer MEP Ethernet
during an interval equal to connectivity
3.5 times the CCM fault
transmission interval management
configured at the MEP. alarms
Eth OAM MEP#MDID[1-16]#MA ID Core-E, MEP received a CCM TAP-118
MisMerge [1-512]#MEPID[1-8191] MSS/CORE frame with correct MD Ethernet
condition Level but incorrect MA connectivity
ID. fault
management
alarms
remote defect [1-512]#MEPID[1-8191] MSS/CORE frame with the RDI field Ethernet
indication set. connectivity
fault
management
alarms
unexpected [1-512]#MEPID[1-8191] MSS/CORE frame with the incorrect Ethernet
level MD Level. connectivity
fault
management
alarms


equipment
Eth OAM MEP#MDID[1-16]#MA ID Core-E, Received MEPID value is TAP-118

unexpectedMEP [1-512]#MEPID[1-8191] MSS/CORE different than the expected Ethernet
ID MEPID. connectivity
fault
management
alarms
Eth OAM MEP#MDID[1-16]#MA ID Core-E, Received MEP Time-Out TAP-118
unexpected [1-512]#MEPID[1-8191] MSS/CORE period value is different Ethernet
period than the expected MEP connectivity
Time-Out period. fault
management
alarms
Excessive r01/subrack#[3-8][5-8] MPT-HL, Excessive temperature on TAP-103
environmental MPT-HLC MPT-HL Transceiver Equipment
temperature connected to alarms
EASv2,
P8ETH
MPT-HLC
connected to
Core-E,
MSS/CORE
r01/subrack#[3-8][5-8] MPT-HL Failure or Missing TAP-103
connected to MPT-HL Transceiver Fan Equipment
EASv2, Unit detected alarms
P8ETH
r01/subrack#1[5-6] MPT-HL
connected to
Core-E,
MSS/CORE


equipment
Fan Fail Radio/Dir#1.[5-6]/ MPT-HLC Failure of at least one TAP-122 Fan

Slot#1/Port#[5-6]/Ch#[0-1] connected to MPT-HLC Transceiver Fail
Core-E Fan Unit detected
MSS/CORE
Ch#[0-1] EASv2,
P8ETH


equipment
Firmware r01s1/board#[8] AUX Download Status. A No action

Download download of an FPGA or required.
r01s1/board#[1-2] Core-E other software unit on the
On Going
r01s1/MSS/CORE MSS/Core addressed card.
r01s1/board#[3-8] EASv2,
MOD300,
MPTACC,
P2E3DS3,
P8ETH,
P32E1DS1,
SDHACC
r01/subrack#[3-8] ODU300
r01/subrack#1[1-6] MPT ODU
connected to
Core-E,
MSS/CORE
connected to
EASv2,
MPTACC
connected to
EASv2,
P8ETH
MPT-HLC
connected to
Core-E,
MSS/CORE
MPT-HLC
connected to
EASv2,
P8ETH


equipment
Flash Card r01/subrack#1 Core-E, An indication that the Call CTAC

Failure MSS/Core SNMPv3 agent had a
failure writing the set-up
file to the flash card.
Indicates a failed flash
card on the Core-E or
MSS-1 MSS/CORE.
Flash Card r01s1/board#[1-2] Core-E Flash Card realignment of No action
Realignment in Standby Core in progress required
Progress
High BER Radio/Dir#1.[1-6]/ MPT ODU Bit Error Rate threshold TAP-104 Radio
Slot#1/Port#[1-6]/Ch#[0-1] connected to (10E-4) exceeded on alarms
Core-E receiver input circuits on (MPT-HC,
MOD300, MPT ODU, MPT-HL,
connected to MPT-HL, MPT-HLC
CORE/Port#[1-6]/Ch#[0-1] tranceiver. MPT-HLC,
MSS/CORE MPT-XP,
Slot#[3-8]/Port#[1-4]/
MPTACC 9558HC)
Ch#[0-1]
P8ETH
Ch#[1] EASv2

Ch#[0-1] EASv2
Core-E
MSS/CORE


equipment
High BER Radio/Dir#[3-8].[5-8]/ MPT-HL Bit Error Rate threshold TAP-104 Radio
(continued) Slot#[3-8]/Port#[5-8]/ connected to (10E-4) exceeded on alarms
Ch#[0-1] EASv2, receiver input circuits on (MPT-HC,
P8ETH MOD300, MPT ODU, MPT-HL,
MPT-HL, MPT-HLC MPT-HLC,
Radio/Dir#1.[5-6]/ MPT-HLC MPT-HLC,
connected to tranceiver.
Slot#1/Port#[5-6]/Ch#[0-1] MPT-XP,
Core-E MOD300,
Radio/Dir#1.[5-6]/MSS/ MPT-HLC ODU300,
connected to 9558HC)
CORE/Port#[5-6]/Ch#[0-1]
MSS/CORE
Ch#[0-1] EASv2,
P8ETH
High BER EleSdh-in/slot#[3-8]/Port[1- SDHACC Bit Error Rate threshold TAP-100
2] (OC-3) (10E-5) exceeded on Facility alarms
receiver input circuits on
SDHACC card from
OptSdh-in/slot#[3-8]/ demarcation panel for the
Port[1-2] OC-3 facility.
High BER EleSdh-out/slot#[3-8]/ SDHACC Bit Error Rate threshold TAP-100
Port[1-2] (OC-3) (10E-5) exceeded on Facility alarms
transmit output circuits on
OptSdh-out/slot#[3-8]/ SDHACC card to the
Port[1-2] demarcation panel for the
OC-3 facility.
Housekeeping ExtPt/Input#[1-6] AUX Housekeeping alarm input TAP-116
alarm is active. Housekeeping
ExtPt/Input#[11-14] Fan alarms
ExtPt/Input#[11-14] MSS-1


equipment
Incompatible Radio/Dir#1.[1-6]/ MPT ODU Configured frequency is TAP-104 Radio

frequency Slot#1/Port#[1-6]/Ch#[0-1] connected to outside of the supported alarms
Core-E frequency range. (MPT-HC,
MPT-HL,
MSS/CORE MPT-XP,
Slot#[3-8]/Port#[1-4]/
MPTACC 9558HC)
Ch#[0-1]
P8ETH
Ch#[1] EASv2

Ch#[0-1] EASv2
Core-E
MSS/CORE
Ch#[0-1] EASv2,
P8ETH
Core-E
MSS/CORE


equipment
Incompatible Radio/Dir#[3-8].[5-8]/ MPT-HLC Configured frequency is TAP-104 Radio

frequency Slot#[3-8]/Port#[5-8]/ connected to outside of the supported alarms
(continued) Ch#[0-1] EASv2, frequency range. (MPT-HC,
P8ETH MPT-HL,
MPT-HLC,
Radio/Dir#[3-8]/Ch#[0-1] ODU300 MPT-HLC,
MPT-XP,
MOD300,
ODU300,
9558HC)


equipment
Incompatible Radio/Dir#1.[1-6]/ MPT ODU Configured modulation is TAP-104 Radio

modulation Slot#1/Port#[1-6]/Ch#[0-1] connected to not supported by alarms
Core-E MPT ODU or MPT-HLC. (MPT-HC,
MPT-HL,
MSS/CORE MPT-XP,
Slot#[3-8]/Port#[1-4]/
MPTACC 9558HC)
Ch#[0-1]
P8ETH
Ch#[1] EASv2

Ch#[0-1] EASv2
Core-E
MSS/CORE
Ch#[0-1] EASv2,
P8ETH


equipment
Incompatible Radio/Dir#1.[1-6]/ MPT ODU Incorrectly configured or TAP-104 Radio

protection Slot#1/Port#[1-6]/Ch#[0-1] connected to missing RPS/XPIC alarms
Core-E module on MPT ODU. (MPT-HC,
MPT-HL,
MSS/CORE MPT-XP,
Slot#[3-8]/Port#[1-4]/
MPTACC 9558HC)
Ch#[0-1]
Ch#[0-1] EASv2
Incompatible Radio/Dir#1.[1-6]/ MPT ODU Configured shifter value TAP-104 Radio

shifter Slot#1/Port#[1-6]/Ch#[0-1] connected to not supported by alarms
Core-E MPT ODU, MPT-HL, (MPT-HC,
MPT-HLC, or ODU300. MPT-HL,
MSS/CORE MPT-XP,
Slot#[3-8]/Port#[1-4]/
MPTACC 9558HC)
Ch#[0-1]
P8ETH
Ch#[1] EASv2

Ch#[0-1] EASv2
Core-E


equipment
Incompatible Radio/Dir#1.[5-6]/MSS/ MPT-HL Configured shifter value TAP-104 Radio

shifter CORE/Port#[5-6]/Ch#1 connected to not supported by alarms
(continued) MSS/CORE MPT ODU, MPT-HL, (MPT-HC,
MPT-HLC, or ODU300. MPT-HL,
Radio/Dir#[3-8].[5-8]/ MPT-HL MPT-HLC,
Slot#[3-8]/Port#[5-8]/ connected to MPT-HLC,
Ch#[0-1] EASv2, MPT-XP,
P8ETH MOD300,
Radio/Dir#1.[5-6]/ MPT-HLC ODU300,
connected to 9558HC)
Slot#1/Port#[5-6]/Ch#[0-1]
Core-E
MSS/CORE
Ch#[0-1] EASv2,
P8ETH
Radio/Dir#[3-8]/Ch#[0-1] ODU300
Incompatible Radio/Dir#1.[1-6]/ MPT ODU Configured RTPC/ATPC TAP-104 Radio
power Slot#1/Port#[1-6]/Ch#[0-1] connected to Tx power value or ATPC alarms
Core-E Rx power threshold value (MPT-HC,
not supported by MPT-HL,
Radio/Dir#1.[1-6]/MSS/ MPT ODU MPT-HL, MPT-HLC, or MPT-HLC,
CORE/Port#[1-6]/Ch#[0-1] connected to MPT ODU. MPT-HLC,
MSS/CORE MPT-XP,
Slot#[3-8]/Port#[1-4]/
MPTACC 9558HC)
Ch#[0-1]
P8ETH
Ch#[1] EASv2


equipment
Incompatible Radio/Dir#[3-8].[5-8]/ MPT ODU Configured RTPC/ATPC TAP-104 Radio

power Slot#[3-8]/Port#[5-8]/ connected to Tx power value or ATPC alarms
(contiued) Ch#[0-1] EASv2 Rx power threshold value (MPT-HC,
Radio/Dir#1.[5-6]/ MPT-HL MPT-HL, MPT-HLC, or MPT-HLC,
Slot#1/Port#[5-6]/Ch#1 connected to MPT ODU. MPT-HLC,
Core-E MPT-XP,
MOD300,
ODU300,
9558HC)
MSS/CORE
Ch#[0-1] EASv2,
P8ETH
Core-E
MSS/CORE
Ch#[0-1] EASv2,
P8ETH
Incompatible Radio/Dir#[3-8]/Ch#[0-1] ODU300 Configured RTPC/ATPC TAP-104 Radio
power Tx power value or ATPC alarms
Rx power threshold value (MPT-HC,
ODU300. MPT-HLC,
MPT-HLC,
MPT-XP,
MOD300,
ODU300,
9558HC)


equipment
Internal r01/subrack#1[1-6] MPT ODU Loss of communications TAP-107

communication connected to with MPT ODU, Internal loss of
problem Core-E, MPT-HL, MPT-HLC, or communications
MSS/CORE ODU300.
connected to
EASv2,
MPTACC
connected to
EASv2,
P8ETH
MPT-HLC
connected to
EASv2,
P8ETH
MPT-HLC
connected to
Core-E,
MSS/CORE


equipment
Link identifier AirFrame/Dir#1.[1-6]/ MPT ODU Link identifier number TAP-104 Radio
mismatch Slot#1/Port#[1-6]/Ch#1, connected to provisioned on MOD300/ alarms
Core-E MPT ODU/MPT-HL/ (MPT-HC,
AirFrame/Dir#1.[1-6]/
MPT-HLC card settings MPT-HL,
Slot#1/Port#[1-6] screen is different from MPT-HLC,
AirFrame/Dir#1.[1-6]/MSS/ MPT ODU link identifier number MPT-HLC,
connected to provisioned at far end of MPT-XP,
CORE/Port#[1-6]/Ch#1,
MSS/CORE hop. MOD300,
AirFrame/Dir#1.[1-6]/MSS/ ODU300,
CORE/Port#[1-6] 9558HC)
AirFrame/Dir#[3-8].[1-4]/ MPT ODU
Slot#[3-8]/Port#[1-4]/Ch#1, connected to
MPTACC
AirFrame/Dir#[3-8].[1-4]/
Slot#[3-8]/Port#[1-4]
EASv2,
P8ETH
Slot#[3-8]/Port#[5-8]
EASv2
AirFrame/Dir#1.[5-6]/ MPT-HL
Core-E
AirFrame/Dir#1.[5-6]/MSS/ MPT-HL
MSS/CORE
AirFrame/Dir#[3-8].[5-8]/ MPT-HL
EASv2,
P8ETH
Slot#[3-8]/Port#[5-8]


equipment
Link identifier AirFrame/Dir#1.[5-6]/ MPT-HLC Link identifier number TAP-104 Radio

mismatch Slot#1/Port#[5-6]/Ch#1, connected to provisioned on MOD300/ alarms
(continued) Core-E MPT ODU/MPT-HL/ (MPT-HC,
MPT-HLC card settings MPT-HL,
Slot#1/Port#[5-6] screen is different from MPT-HLC,
AirFrame/Dir#1.[5-6]/MSS/ MPT-HLC link identifier number MPT-HLC,
connected to provisioned at far end of MPT-XP,
CORE/Port#[5-6]/Ch#1,
MSS/CORE hop. MOD300,
irFrame/Dir#1.[5-6]/MSS/ ODU300,
CORE/Port#[5-6] 9558HC)
AirFrame/Dir#[3-8].[5-8]/ MPT-HLC
EASv2,
P8ETH
Slot#[3-8]/Port#[5-8]
AirFrame/Dir#[3-8]/Ch#1, MOD300
AirFrame/Dir#[3-8]


equipment
Loop problem Radio/Dir#1.[1-6]/ MPT ODU Loss of ATPC command TAP-110 ATPC
Slot#1/Port#[1-6]/Ch#[0-1] connected to path between far end loop conditions
Core-E transmitter and local (MOD300,
receiver. MPT-HC,
Radio/Dir#1.[1-6]/MSS/ MPT ODU MPT-HL,
MSS/CORE MPT-XP,
Radio/Dir#[3-8].[1-4]/ MPT ODU 9558HC)
Ch#[0-1] MPTACC

P8ETH
EASv2
Ch#[0-1] EASv2
Core-E
MSS/CORE
Ch#[0-1] EASv2,
P8ETH
Core-E
MSS/CORE


equipment
Loop problem Radio/Dir#[3-8].[5-8]/ MPT-HLC Loss of ATPC command TAP-110 ATPC

(continued) Slot#[3-8]/Port#[5-8]/ connected to path between far end loop conditions
Ch#[0-1] EASv2, transmitter and local (MOD300,
P8ETH receiver. MPT-HC,
MPT-HL,
MPT-HLC,
MPT-XP,
9558HC)
Loss of Hitless/Dir#1.[1-6] MPT ODU Delay/loss of alignment TAP-112 Loss
alignment connected to between main and protect of alignment
Core-E, RPS RF paths detected. (MOD300,
MSS/CORE MPT-HC,
MPT-HL,
Hitless/Dir#[3-8].[1-4] MPT ODU MPT-HLC,
MPTACC 9558HC)
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
connected to
Core-E,
MSS/CORE
Hitless/Dir#[3-8].[5-8] MPT-HLC
connected to
EASv2,
P8ETH
Hitless/Dir#[3-8] MOD300


equipment
Loss Ethernet MAU/Slot#[1-2]/Port#[1-6] Core-E Reported if there is a loss TAP-109

synchronization of the Ethernet Synchronization
messaging MAU/MSS/CORE/Port#[1- MSS/CORE Synchronization Message alarms (Core-E,
channel 6] Channel. The alarm is MOD300,
MAU/Slot#[3-8]/Port#[1-8] EASv2 applicable to Core-E, MPT-HC,
EASv2, and MSS-1 MPT-HL,
Radio/Dir#[3-8]/Ch#[0-1] MOD300 Ethernet ports and Radio MPT-HLC,
interfaces (MPT ODU, MPT-XP,
RadioLAG#[1-14] MPT ODU,
MPT-HL, MPT-HLC, or P32E1DS1,
MPT-HL,
MOD300) configured SDHACC,
MPT-HLC with SSM support enabled 9558HC)
Radio/Dir#1.[1-6]/ MPT ODU and is assigned as a
connected to synchronous clock source
Slot#1/Port#[1-6]/Ch#[0-1]
Core-E input.
Radio/Dir#1.[1-6]/MSS/ MPT ODU

MSS/CORE
Ch#[0-1] MPTACC

P8ETH
EASv2
Ch#[0-1] EASv2
Core-E
MSS/CORE


equipment
Loss Ethernet Radio/Dir#[3-8].[5-8]/ MPT-HL Reported if there is a loss TAP-109

synchronization Slot#[3-8]/Port#[5-8]/ connected to of the Ethernet Synchronization
messaging Ch#[0-1] EASv2, Synchronization Message alarms (Core-E,
channel P8ETH Channel. The alarm is MOD300,
(continued) applicable to Core-E, MPT-HC,
Radio/Dir#1.[5-6]/ MPT-HLC EASv2, and MSS-1 MPT-HL,
Slot#1/Port#[5-6]/Ch#[0-1] connected to Ethernet ports and Radio MPT-HLC,
Core-E interfaces (MPT ODU, MPT-XP,
Radio/Dir#1.[5-6]/MSS/ MPT-HLC MPT-HL, MPT-HLC, or P32E1DS1,
connected to MOD300) configured SDHACC,
CORE/Port#[5-6]/Ch#[0-1]
MSS/CORE with SSM support enabled 9558HC)
and is assigned as a
Radio/Dir#[3-8].[5-8]/ MPT-HLC synchronous clock source
Slot#[3-8]/Port#[5-8]/ connected to input.
Ch#[0-1] EASv2,
P8ETH
Loss Of CircuitTDM/MSS/DS1/ DS1 on Packets are not being TAP-100
CESoETH Port#[1-16] MSS-1 shelf received by the DS1, DS3, Facility alarms
frame or OC-3 emulation circuits
CircuitTDM/Slot#[3-8]/ DS1 on on the receive circuits
Port#[1-32] P32E1DS1 from the switch matrix.
CircuitTDM/Slot#[3-8]/ DS3
Port#[1-2]
CircuitTDM/Slot#[3-8]/ OC-3
Port#[1-2]
Loss Of Frame DS1-in/MSS/DS1/Port#[1- DS1 on Loss of DS1, DS3, or TAP-100
16] MSS-1 shelf OC-3 frame detected Facility alarms
incoming to the PDH/
DS1-in/Slot#[3-8]/Port#[1- DS1 on SDH card from the
32] P32E1DS1 demarcation panel for the
DS1, DS3, or OC-3
facility.
2]
EleSdh-in/slot#[3-8]/Port[1- OC-3
2]
OptSdh-in/slot#[3-8]/
Port[1-2]


equipment
Loss of frame DS1-out/MSS/DS1/ DS1 on Loss of DS1, DS3, or TAP-100

Port#[1-16] MSS-1 shelf OC-3 frame detected from Facility alarms
the Core-E switch matrix
DS1-out/Slot#[3-8]/ DS1 on for the DS1, DS3, or OC-3
Port#[1-32] P32E1DS1 facility
DS3-out/Slot#[3-8]/ DS3
Port#[1-2]
EleSdh-out/slot#[3-8]/ OC-3
Port[1-2]
OptSdh-out/slot#[3-8]/
Port[1-2]


equipment
Loss of frame Radio/Dir#1.[1-6]/ MPT ODU Far end TX problems, RF TAP-113 Loss
Slot#1/Port#[1-6]/Ch#[0-1] connected to path problems, or local of frame
Core-E circuit failures have (MOD300,
caused BER to increase to MPT-HC,
Radio/Dir#1.[1-6]/MSS/ MPT ODU the point that frames are MPT-HL,
CORE/Port#[1-6]/Ch#[0-1] connected to being lost. MPT-HLC,
MSS/CORE MPT-XP,
Ch#[0-1] MPTACC

P8ETH
EASv2
Ch#[0-1] EASv2
Core-E
MSS/CORE
Ch#[0-1] EASv2,
P8ETH
Core-E
MSS/CORE


equipment
Loss of frame Radio/Dir#[3-8].[5-8]/ MPT-HLC Far end TX problems, RF TAP-113 Loss

(continued) Slot#[3-8]/Port#[5-8]/ connected to path problems, or local of frame
Ch#[0-1] EASv2, circuit failures have (MOD300,
P8ETH caused BER to increase to MPT-HC,
the point that frames are MPT-HL,
Radio/Dir#[3-8]/Ch#[0-1] MOD300 being lost. MPT-HLC,
MPT-XP,
9558HC)
Loss of Radio/Dir#[3-8]/Ch#1 MOD300 The radio direction is TAP-104 Radio
protection affected by a failure that alarms
Radio/Dir#1.[1-6]/ MPT ODU radio protection (RPS) (MPT-HC,
Slot#1/Port#[1-6]/Ch#1 connected to can’t recover. Only MPT-HL,
Core-E reported if RPS is MPT-HLC,
Radio/Dir#1.[1-6]/MSS/ MPT ODU provisioned. MPT-HLC,
CORE/Port#[1-6]/Ch#1
MSS/CORE MOD300,
ODU300,
MPTACC
EASv2
Core-E
MSS/CORE
EASv2,
P8ETH


equipment
Loss of signal DS1-in/MSS/DS1/Port#[1- DS1 on No DS1, DS3, or OC-3 TAP-100

16] MSS-1 shelf input signal detected. Facility alarms
DS1-in/Slot#[3-8]/Port#[1- DS1 on
32] P32E1DS1
2]
2]
Port[1-2]
Loss of signal TMNEthernet/MngtPort Core-E/TMN Loss of Signal is declared TAP-105
MGMT Port when either: Ethernet alarms
no Ethernet input signal (Core-E, EASv2,
TMNEthernet/MngtPort#4 Core-E/TMN MPTACC,
Port#4 detected on the Ethernet
port P8ETH, MSS-1
MAU/Slot#[1-2]/Port#[1-6] Core-E Shelf Core)
a communication problem
MAU/MSS/CORE/Port#[1- MSS/CORE with the remote peer (i.e. a
6] link down condition)
MAU/Slot#[3-8]/Port#[1-4] MPTACC
MAU/Slot#[3-8]/Port#[1-8] EASv2,
P8ETH
Loss of signal r01s1[1-6]b1/daughter#03 RPS SFP on Loss of Signal detected on TAP-104 Radio
MPT ODU an MPT ODU/MPT-HL alarms
connected to Ethernet Coupler Port. (MPT-HC,
Core-E, Only reported when RPS MPT-HL,
MSS/CORE is provisioned. MPT-HLC,
MPT-HLC,
r01s1[3-8][1-4]b1/ MPT ODU MPT-XP,
daughter#03 connected to MOD300,
MPTACC ODU300,
9558HC)
MAU/subrack[#3-8].[5-8] MPT-HL
Port#n connected to
EASv2,
P8ETH


equipment
Loss of signal Sync-in/Port#1 Core-E Generated when no signal TAP-109

is present on the incoming Synchronization
Sync-In port. alarms (Core-E,
MOD300,
MPT-HC,
MPT-HL,
MPT-HLC,
MPT-XP,
P32E1DS1,
SDHACC,
9558HC)
Loss of signal EthLAG#[1-14] Core-E, ALL members of an TAP-117 LAG
MSS/CORE Ethernet or Radio LAG alarms (Core-E,
group have no activity. MPT-HC,
RadioLAG#[1-14] MPT ODU, Loss of Signal is declared MPT-HL,
MPT-HL, when the number of active MPT-HLC,
MPT-HLC, ports in the LAG equals MPT-XP,
ODU zero. ODU300,
9558HC, MSS-1
shelf Core)
Power supply r01/subrack#[3-8][1-2] EASv2 MPT Power Supply TAP-102 Power
failure Failure detected, either an alarms
Open-Circuit or Over-
r01/subrack#[3-8][1-4] MPTACC Current condition on an
EASv2, MPTACC or
MSS-1 power supply port.
r01/subrack#1[1-2] MSS/Core


equipment
PPP fail PPP-IP/RF#1[1-6] MPT ODU TMN over PPP Fail TAP-104 Radio
connected to alarms
Core-E, (MPT-HC,
MSS/CORE MPT-HL,
MPT-HLC,
PPP-IP/RF#[3-8][1-4] MPT ODU MPT-HLC,
EASv2, MOD300,
MPTACC ODU300,
PPP-IP/RF#[3-8][5-8] MPT ODU 9558HC)
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/CORE
PPP-IP/RF#[3-8][5-8] MPT-HLC
connected to
EASv2,
P8ETH
PPP-IP/RF#1[5-6] MPT-HLC
connected to
Core-E,
MSS/CORE
PPP-IP/RF#[3-8] MOD300
Provisioning r01s1/board#[1-2] Core-E The wrong flash card is TAP-106
mismatch installed and the current License/
database is in conflict with software
r01s1/MSS/CORE MSS/CORE the license string on the mismatch
card.


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


equipment
Remote defect Radio/Dir#[3-8].[5-8]/ MPT-HLC Remote Defect Indication TAP-104 Radio

indication Slot#[3-8]/Port#[5-8]/ connected to (RDI) in a received Radio alarms
(continued) Ch#[0-1] EASv2, Direction. Alarm is (MPT-HC,
P8ETH reported when an RDI is MPT-HL,
received MPT-HLC,
Radio/Dir#[3-8]/Ch#[0-1] MOD300 MPT-HLC,
on a given radio direction
MPT-XP,
MOD300,
radio link.
ODU300,
9558HC)
Remote defect EleSdh-in/slot#[3-8]/Port[1- OC-3 Remote Defect Indication TAP-100
indication 2] (RDI) in a received OC-3 Facility alarms
Direction. Alarm is
reported when an RDI is
OptSdh-in/slot#[3-8]/ received
Port[1-2]
on a given OC-3 direction
OC-3 link.
Replaceable r01s1/board#[8] AUX Card/SFP is missing from TAP-103
unit missing slot (Only declared, if the Equipment
r01s1/board#[1-2] Core-E card/SFP has been alarms
r01s1/board#[5,9] FAN provisioned. Card/SFP
could be unreachable.).
MOD300,
MPTACC,
P2E3DS3,
P8ETH,
P32E1DS1,
SDHACC
r01s1b[1-2]/daughter#[5-6] SFP on
Core-E
r01s1b1/daughter#[5-6] SFP on MSS/
CORE
r01s1b[3-8]/daughter#[03- SFP on
04] MPTACC


equipment
Replaceable r01s1b[3-8]/daughter#[05- SFP on Card/SFP is missing from TAP-103

unit missing 08] EASv2, slot (Only declared, if the Equipment
(continued) P8ETH card/SFP has been alarms
provisioned. Card/SFP
r01s1b[3-8]/daughter#[01- SFP on could be unreachable.).
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,
P8ETH
r01s1[1-6]b1/daughter#03 RPS SFP on
MPT ODU
connected to
Core-E,
MSS/CORE


equipment
Replaceable r01s1/board#[8] AUX Card failed. TAP-103

unit problem Equipment
r01s1/board#[1-2] Core-E alarms
r01s1/MSS/CORE MSS-1
r01s1/board#[5,9] FAN
MOD300,
MPTACC,
P2E3DS3,
P8ETH,
P32E1DS1,
SDHACC
connected to
Core-E,
MSS/CORE
connected to
MPTACC
connected to
P8ETH
connected to
EASv2
r01/subrack#[3-8][5-8] MPT-HL
connected to
P8ETH
connected to
Core-E,
MSS/CORE
connected to
P8ETH


equipment
Replaceable r01/subrack#1[5-6] MPT-HLC Card failed. TAP-103

unit problem connected to Equipment
(continued) Core-E, alarms
MSS/CORE
06] Core-E
CORE
04] MPTACC
08] EASV2,
P8ETH
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
r01s1[1-6]b1/daughter#03 RPS SFP on
MPT ODU
connected to
Core-E,
MSS/CORE
r01s1[1-6]b1/daughter#04 RPS or XPIC
Module on
MPT ODU
connected to
Core-E,
MSS/CORE


equipment
Replaceable r01/subrack#[3-8][5-8]/ XPIC Card failed. TAP-103

unit problem daughter#04 Module on Equipment
(continued) MPT ODU alarms
connected to
P8ETH
r01s[3-8][1-4]b1/ RPS or XPIC
daughter#04 Module on
MPT ODU
connected to
MPTACC
r01s[3-8][1-4]b1/ XPIC
MPT ODU
connected to
EASV2
r01/subrack#[3-8][5-8]/ RPS or XPIC
MPT ODU
connected to
EASV2
r01s1[1-6]b1/daughter#04 Rx Diversity
Module on
MPT-HLC
connected to
Core-E,
MSS/CORE
r01/subrack#[3-8][5-8]/ Rx Diversity
MPT-HLC
connected to
EASv2
Replaceable r01s1/board#[8] AUX Card/ODU in slot does not TAP-103
unit type match card/ODU Equipment
mismatch r01s1/board#[1-2] Core-E configured in Core-E alarms
r01s1/board#[5,9] FAN memory


equipment
Replaceable r01s1/board#[3-8] EASv2, Card/ODU in slot does not TAP-103

unit type MOD300, match card/ODU Equipment
mismatch MPTACC, configured in Core-E alarms
(continued) P2E3DS3, memory
P8ETH,
P32E1DS1,
SDHACC
connected to
Core-E,
MSS/CORE
connected to
MPTACC
connected to
P8ETH
connected to
EASv2
connected to
EASv2,
P8ETH
connected to
Core-E,
MSS/CORE
connected to
EASV2,
P8ETH


equipment
Replaceable r01/subrack#1[5-6] MPT-HLC Card/ODU in slot does not TAP-103

unit type connected to match card/ODU Equipment
mismatch Core-E, configured in Core-E alarms
(continued) MSS/CORE memory
RF Switch Fail r01/subrack#1[5-6] MPT-HLC RF switch fail detected TAP-123 RF
connected to Switch Fail
Core-E, (MPT-HLC)
MSS/CORE
connected to
EASV2,
P8ETH


equipment
RPS path fail RadioProt/Dir#[3-8][1-4] MPT ODU A communication failure TAP-114 RPS
connected to is detected between path fail
MPTACC MPT ODUs. Only (MPT-HC,
reported for an MPT-HL,
RadioProt/Dir#1[1-6] MPT ODU MPT ODUs working in MPT-HLC,
connected to 1+1 configuration with MPT-XP,
Core-E, Virtual Protection. 9558HC)
MSS/CORE
RadioProt/Dir#[3-8][5-8] MPT ODU
connected to
EASv2
RadioProt/Dir#[3-8][5-8] MPT-HL Communication failure is
connected to detected between RPS
EASv2, coupler port between radio
P8ETH boards. Only reported if
RPS is provisioned.
RadioProt/Dir#1[5-6] MPT-HLC
connected to
Core-E
RadioProt/Dir#1[5-6] MPT-HLC
connected to
MSS/CORE
RadioProt/Dir#[3-8][5-8] MPT-HLC
connected to
EASv2,
P8ETH
Rx Diversity r01s1[5-6]b1/daughter#04 MPT-HLC Combiner function TAP-124 Rx
Missing connected to enabled but Rx Diversity diversity missing
Core-E, module Missing (MPT-HLC)
MSS/CORE
r01s[3-8][5-8]b1/ MPT-HLC
EASv2,
P8ETH
Rx fail Radio/Dir#[3-8]/Ch#[0-1] ODU300 Failure in receive TAP-115 Rx fail

direction of ODU300 RF (MOD300)
transceiver. Includes no
input signal.


equipment
Secondary r01/subrack#1 MSS-1/4/8 B battery feed failed or is TAP-102 Power

battery failure • missing. alarms
Standby version r01/subrack#1[1-6] MPT ODU Standby software version TAP-106

mismatch connected to on MPT ODU/MPT-HL/ License/
Core-E, MPT-HLC does not match software
MSS/CORE software version on mismatch
r01/subrack#[3-8][1-4] MPT ODU Core-E.
connected to
MPTACC
connected to
P8ETH
connected to
EASv2
connected to
Core-E,
MSS/CORE
connected to
EASv2,
P8ETH
connected to
Core-E,
MSS/CORE
connected to
EASv2,
P8ETH


equipment
Synchronization Sync-in/Port#1 Core-E Synchronization Signal TAP-109

signal fail Fail is reported if the Synchronization
SyncSource/ETH/ Core-E user received source signal is alarms (Core-E,
Slot#1/Port#[1-6] Ethernet Port not suitable as a Sync MOD300,
Source. Managed only if MPT-HC,
SyncSource/ETH/MSS/ MSS/CORE
the interface has been MPT-HL,
CORE/Port#[1-6] user Ethernet
configured as a primary or MPT-HLC,
Port
secondary MPT-XP,
SyncSource/ETH/ EASv2 user synchronization source. P32E1DS1,
Slot#[3-8]/Port#[1-8] Ethernet Port SDHACC,
9558HC)
Radio/Dir#1.[1-6]/ MPT ODU
Core-E
Radio/Dir#1.[1-6]/MSS/ MPT ODU
MSS/CORE
MPTACC
P8ETH
Ch#[1] EASv2
Core-E
MSS/CORE
P8ETH


equipment
Synchronization Radio/Dir#1.[1-6]/ MPT-HLC Synchronization Signal TAP-109

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


equipment
Threshold Hop/Dir#1[1-6]/Slot#1/ MPT ODU Threshold Crossing Alarm TAP-108

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


equipment
Threshold Hop/Dir#[3-8][5-8]/ MPT ODU Threshold Crossing Alarm TAP-108

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


equipment
Threshold Hop/Dir#[3-8][5-8]/ MPT-HL Threshold Crossing Alarm TAP-108

(continued) Port#[5-8]/Ch#[0-1]- EASv2, threshold has been crossing alarms
PM15min P8ETH exceeded. Applies to (MOD300,
performance monitor MPT-HC,
Hop/Dir#[3-8][5-8]/ parameters with an MPT-HL,
Slot#[3-8]/ accumulation period of 24 MPT-HLC,
Port#[5-8]/Ch#[0-1]- hours and 15 minutes. MPT-XP,
PM1day 9558HC,
P32E1DS1,
Link/Dir#[3-8][5-8]- MSS-1 shelf
PM15min P32E1DS1)
Link/Dir#[3-8][5-8]-
PM1day
Hop/Dir#1[5-6]/Slot#1/ MPT-HL
Port#[5-6]/Ch#1-PM15min connected to
Core-E
Hop/Dir#1[5-6]/Slot#1/
Hop/Dir#1[5-6]/MSS/ MPT-HL
CORE/ connected to
Port#[5-6]/Ch#1-PM15min MSS/CORE
Hop/Dir#1[5-6]/MSS/
CORE/
Hop/Dir#1[5-6]/Slot#1/ MPT-HLC
Core-E
Hop/Dir#1[5-6]/MSS/ MPT-HLC
CORE/ connected to
Hop/Dir#1[5-6]/MSS/
CORE/
Port#[5-6]/Ch#1-PM1dayer


equipment
Threshold Hop/Dir#[3-8][5-8]/ MPT-HLC Threshold Crossing Alarm TAP-108

(continued) Port#[5-8]/Ch#[0-1]- EASv2, threshold has been crossing alarms
PM15min P8ETH exceeded. Applies to (MOD300,
performance monitor MPT-HC,
Hop/Dir#[3-8][5-8]/ parameters with an MPT-HL,
Slot#[3-8]/ accumulation period of 24 MPT-HLC,
Port#[5-8]/Ch#[0-1]- hours and 15 minutes. MPT-XP,
PM1day 9558HC,
P32E1DS1,
PM15min P32E1DS1)
Link/Dir#[3-8][5-8]-
PM1day
Hop/Dir#[3-8]/Ch#[0-1]- MOD300
PM15min
Hop/Dir#[3-8]/Ch#[0-1]-
PM1day
Link/Dir#[3-8]-PM15min
Link/Dir#[3-8]-PM1day
DS1-in/Slot#[3-8]/ P32E1DS1
Port#[1-32]-PM15min
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
Threshold DS1-in/MSS/DS1/ DS1 on Threshold Crossing Alarm TAP-108

crossed Port#[1-16]-PM15min MSS-1 shelf (TCA) indicates alarm Threshold
(continued) threshold has been crossing alarms
DS1-in/MSS/DS1/ exceeded. Applies to (MOD300,
Port#[1-16]-PM1day performance monitor MPT-HC,
parameters with an MPT-HL,
DS1-out/MSS/DS1/ accumulation period of 24 MPT-HLC,
Port#[1-16]-PM15min hours and 15 minutes. MPT-XP,
9558HC,
DS1-out/MSS/DS1/
P32E1DS1,
Port#[1-16]-PM1day MSS-1 shelf
P32E1DS1)
Trace identifier EleSdh-in/slot#[3-8]/Port[1- OC-3 Trace Identifier Mismatch TAP-100
mismatch 2] condition indicates there is Facility alarms
a J0 Trace Mismatch
OptSdh-in/slot#[3-8]/ detected in the incoming
Port[1-2] signal from the
demarcation panel.
Unavailable Hop/Dir#1[1-6]/Slot#1/ MPT ODU A period of unavailable TAP-108
time Port#[1-6]/Ch#[0-1]- connected to time begins when 10 Threshold
PM15min Core-E consecutive SES events crossing alarms
are detected. Alarms are (MOD300,
Hop/Dir#1[1-6]/Slot#1/ associated to the MPT-HC,
Port#[1-6]/Ch#[0-1]- performance monitoring MPT-HL,
PM1day port. MPT-HLC,
MPT-XP,
Link/Dir#1[1-6]-PM15min 9558HC,
Link/Dir#1[1-6]-PM1day P32E1DS1,
MSS-1 shelf
Hop/Dir#1[1-6]/MSS/ MPT ODU P32E1DS1)
CORE/ connected to
Port#[1-6]/Ch#[0-1]- MSS/CORE
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 TAP-108

time (continued) Slot#[3-8]/ connected to time begins when 10 Threshold
Port#[1-4]/Ch#[0-1]- MPTACC consecutive SES events crossing alarms
PM15min are detected. Alarms are (MOD300,
associated to the MPT-HC,
Hop/Dir#[3-8][1-4]/ performance monitoring MPT-HL,
Slot#[3-8]/ port. MPT-HLC,
Port#[1-4]/Ch#[0-1]- MPT-XP,
PM1day 9558HC,
P32E1DS1,
PM15min P32E1DS1)
Link/Dir#[3-8][1-4]-
PM1day
Port#[5-8]/Ch#1-PM15min P8ETH
Hop/Dir#[3-8][5-8]/
Slot#[3-8]/
Port#[1-4]/Ch#1-PM15min EASv2
Hop/Dir#[3-8][1-4]/
Slot#[3-8]/


equipment
Unavailable Hop/Dir#[3-8][5-8]/ MPT ODU A period of unavailable TAP-108

time (continued) Slot#[3-8]/ connected to time begins when 10 Threshold
Port#[5-8]/Ch#1-PM15min EASv2 consecutive SES events crossing alarms
are detected. Alarms are (MOD300,
Hop/Dir#[3-8][5-8]/ associated to the MPT-HC,
Slot#[3-8]/ performance monitoring MPT-HL,
Port#[5-8]/Ch#1-PM1day port. MPT-HLC,
MPT-XP,
Link/Dir#[3-8][5-8]- 9558HC,
PM15min P32E1DS1,
PM1day P32E1DS1)
Hop/Dir#1[5-6]/Slot#1/ MPT-HL
Core-E
Hop/Dir#1[5-6]/MSS/ MPT-HL
CORE/ connected to
Hop/Dir#1[5-6]/MSS/
CORE/
Hop/Dir#[3-8][5-8]/ MPT-HL
Port#[5-8]/Ch#[0-1]- EASv2,
PM15min P8ETH
Hop/Dir#[3-8][5-8]/
Slot#[3-8]/
Port#[5-8]/Ch#[0-1]-
PM1day
Link/Dir#[3-8][5-8]-
PM15min
Link/Dir#[3-8][5-8]-
PM1day


equipment
Unavailable Hop/Dir#1[5-6]/Slot#1/ MPT-HLC A period of unavailable TAP-108

time (continued) Port#[5-6]/Ch#1-PM15min connected to time begins when 10 Threshold
Core-E consecutive SES events crossing alarms
Hop/Dir#1[5-6]/Slot#1/ er are detected. Alarms are (MOD300,
Port#[5-6]/Ch#1-PM1day associated to the MPT-HC,
performance monitoring MPT-HL,
Link/Dir#1[5-6]PM15min port. MPT-HLC,
Link/Dir#1[5-6]PM1day MPT-XP,
9558HC,
Hop/Dir#1[5-6]/MSS/ MPT-HLC P32E1DS1,
CORE/ connected to MSS-1 shelf
Port#[5-6]/Ch#1-PM15min MSS/CORE P32E1DS1)
Hop/Dir#1[5-6]/MSS/
CORE/
Link/Dir#1[5-6]PM15min
Link/Dir#1[5-6]PM1day
Hop/Dir#[3-8][5-8]/ MPT-HLC
Port#[5-8]/Ch#[0-1]- EASv2,
PM15min P8ETH
Hop/Dir#[3-8][5-8]/
Slot#[3-8]/ Port#[5-8]/
Ch#[0-1]-PM1day
Link/Dir#[3-8][5-8]-
PM15min
Link/Dir#[3-8][5-8]-
PM1day
Hop/Dir#[3-8]/Ch#[0-1] MOD300
PM15min
Hop/Dir#[3-8]/Ch#[0-1]-
PM1day


equipment
Unavailable DS1-in/Slot#[3-8]/Port#[1- P32E1DS1 A period of unavailable TAP-108

time 32]-PM15min time begins when 10 Threshold
(continuted) consecutive SES events crossing alarms
DS1-in/Slot#[3-8]/Port#[1- are detected. Alarms are (MOD300,
32]-PM1day associated to the MPT-HC,
DS1-out/Slot#[3-8]/ performance monitoring MPT-HL,
Port#[1-32]-PM15min port. MPT-HLC,
MPT-XP,
DS1-out/Slot#[3-8]/ 9558HC,
Port#[1-32]-PM1day P32E1DS1,
MSS-1 shelf
DS1-in/MSS/DS1/Port#[1- DS1 on
P32E1DS1)
16]-PM15min MSS-1 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
Unconfigured r01s1/board#[8] AUX Card in MSS shelf slot 2 TAP-103
equipment through 8 is not Equipment
present r01s1/board#[2] Core-E provisioned (enabled) but alarms
r01s1/board#[5,9] FAN is present in slot.
SFP is not provisioned
r01s1/board#[3-8] EASV2, (enabled) but is present in
MOD300, card.
MPTACC,
P2E3DS3,
P8ETH,
P32E1DS1,
SDHACC
06] Core-E
CORE
04] MPTACC


equipment
Unconfigured r01s1b[3-8]/daughter#[05- SFP on Card in MSS shelf slot 2 TAP-103

equipment 08] EASv2, through 8 is not Equipment
present P8ETH provisioned (enabled) but alarms
(continued) is present in slot.
02] SDHACC SFP is not provisioned
(enabled) but is present in
card.


equipment
Version r01s1/board#[1-2] Core-E Software version on TAP-106

mismatch Core-E, MSS-1 Core, License/
r01s1/MSS/CORE Core on ODU300, MPT ODU, software
MSS-1 shelf MPT-HL, or MPT-HLC mismatch
r01/subrack#1[1-6] MPT ODU does not match software
connected to version on Core-E.
Core-E,
MSS/CORE
connected to
EASv2
connected to
MPTACC
connected to
P8ETH
connected to
Core-E,
MSS/CORE
connected to
EASv2,
P8ETH
connected to
Core-E,
MSS/CORE
connected to
EASv2,
P8ETH

• 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 9.4 — Abnormal condition
Operation Name Type Description See

(equipment)
Core facing PDH DS1 Port#[1-16] Internal Loopback The associated entity has a TAP-101
loopback DS1 on MSS-1 core facing PDH (DS1 or Abnormal
shelf DS3) loopback activated at conditions
the near end.
DS1 Port#[1-32] Internal Loopback
DS3 Port#[1-2] Internal SLOT#[3-8]
Core facing SDH OC3 Port#[1-2] Internal Loopback The associated entity has a TAP-101
loopback SLOT#[3-8] core facing SDH (OC3) Abnormal
loopback activated at the conditions
near end.
Digital core Direction #1.[1-6] Loopback The associated entity has a TAP-101
facing loopback (MPT ODU loopback activated at the Abnormal
connected to near end. conditions
Core-E, MSS/
CORE)
Direction #[3-8].[1-4] Loopback
(MPT ODU
connected to
MPTACC)
(MPT ODU
connected to
P8ETH)
(MPT ODU
connected to
EASv2)

Table 9.4 — Abnormal condition (Continued)

(equipment)
Digital core Direction #1.[5-6] Loopback The associated entity has a TAP-101
facing loopback (MPT-HL loopback activated at the Abnormal
(continued) connected to near end. conditions
Core-E, MSS/
CORE)
(MPT-HL
connected to
EASv2,
P8ETH)
Direction #1.[5-6] Loopback
(MPT-HLC
connected to
Core-E, MSS/
CORE)
(MPT-HLC
connected to
EASv2,
P8ETH)
Forced adaptive Direction #[3-8] - Radio Manual Adaptive TAP-101
modulation Channel #1 (MOD300) Modulation command has Abnormal
been executed. conditions
Direction #1.[1-6] - Radio
Channel #1 (MPT ODU
connected to
Core-E, MSS/
CORE)
Direction #[3-8].[1-4] - Radio
Channel #1 (MPT ODU
connected to
MPTACC)
Channel #1 (MPT ODU
connected to
P8ETH)


(equipment)
Forced adaptive Direction #[3-8].[1-8] - Radio Manual Adaptive TAP-101

modulation Channel #1 (MPT ODU Modulation command has Abnormal
(continued) connected to been executed. conditions
EASv2)
Channel #1 (MPT-HL
connected to
Core-E, MSS/
CORE)
Channel #1 (MPT-HL
connected to
EASv2,
P8ETH)
Channel #1 (MPT-HLC
connected to
Core-E, MSS/
CORE)
Channel #1 (MPT-HLC
connected to
EASv2,
P8ETH)
Forced switch Main#1 Slot#1 Equipment A Forced Equipment TAP-101
EPS Protection Protection Switch (EPS) has Abnormal
(Core-E) been executed for the conditions
protection group.
Main#1 Slot#[3,5,7] Equipment
Protection
(MOD300,
P2E3DS3,
P32E1DS1,
SDHACC)


(equipment)
Forced switch Main#1 Slot #[3-8] Equipment A Forced Equipment TAP-101

EPS (continued) Port #[1-4] Protection Protection Switch (EPS) has Abnormal
(MPT ODU been executed for the conditions
connected to protection group.
MPTACC)
Main#1 Slot #1 Equipment
Port #[1,3,5] Protection
(MPT ODU
connected to
Core-E)
Main#1 MSS/CORE Equipment
(MPT ODU
connected to
MSS/CORE)
Main#1 Slot #[3,5,7] Equipment
Port #[5-8] Protection
(MPT ODU
connected to
EASv2)
Main#1 Slot #[3,5,7] Equipment
(MPT-HL
connected to
EASV2,
P8ETH)
Main#1 Slot #1 Equipment
(MPT-HLC
connected to
Core-E)
Main#1 MSS/CORE Equipment
(MPT-HLC
connected to
MSS/CORE)


(equipment)
Forced switch Main#1 Slot #[3,5,7] Equipment A Forced Equipment TAP-101

EPS (continued) Port #[5-8] Protection Protection Switch (EPS) has Abnormal
(MPT-HLC been executed for the conditions
connected to protection group.
EASv2,
P8ETH)
Forced switch Main#1 Slot#[3,5,7] Rx Radio A Forced Rx Protection TAP-101
RPS Protection Switch (RPS) has been Abnormal
(MOD300) executed for the protection conditions
group.
Main#1 Slot #1 Rx Radio
(MPT ODU
connected to
Core-E)
Main#1 MSS/CORE Rx Radio
(MPT ODU
connected to
MSS/CORE)
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)
(MPT-HL
connected to
EASV2,
P8ETH)


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

RPS (continued) Port #[1,3,5] Protection Switch (RPS) has been Abnormal
(MPT-HLC executed for the protection conditions
connected to group.
Core-E)
Main#1 MSS/CORE Rx Radio
(MPT-HLC
connected to
MSS/CORE)
(MPT-HLC
connected to
EASv2,
P8ETH)
Forced switch Main#1 Slot#[3,5,7] HSB A Forced Tx Protection TAP-101
TPS Protection Switch (TPS) has been Abnormal
(MOD300) executed for the protection conditions
group.
Main#1 Slot #[3-8] HSB
(MPT ODU
connected to
MPTACC)
Main#1 Slot #1 HSB
(MPT ODU
connected to
Core-E)
Main#1 MSS/CORE HSB
(MPT ODU
connected to
MSS/CORE)


(equipment)
Forced switch Main#1 Slot #[3,5,7] HSB A Forced Tx Protection TAP-101

TPS (continued) Port #[5-8] Protection Switch (TPS) has been Abnormal
(MPT ODU executed for the protection conditions
connected to group.
EASv2)
Main#1 Slot #[3,5,7] HSB
(MPT-HL
connected to
EASV2,
P8ETH)
Main#1 Slot #1 HSB
(MPT-HLC
connected to
Core-E)
Main#1 MSS/CORE HSB
(MPT-HLC
connected to
MSS/CORE)
Main#1 Slot #[3,5,7] HSB
(MPT-HLC
connected to
EASv2,
P8ETH)
IF cable loopback Direction #[3-8] Loopback The associated entity has a TAP-101
(MOD300) loopback activated at the Abnormal
near end. conditions


(equipment)
Line facing Direction #1.[1-6] Loopback The associated entity has a TAP-101
circuit loopback (MPT ODU loopback activated at the Abnormal
connected to near end. conditions
Core-E, MSS/
CORE)
(MPT ODU
connected to
MPTACC)
(MPT ODU
connected to
P8ETH)
(MPT ODU
connected to
EASv2)
(MPT-HL
connected to
Core-E, MSS/
CORE)
(MPT-HL
connected to
EASv2,
P8ETH)
(MPT-HLC
connected to
Core-E, MSS/
CORE)


(equipment)
Line facing Direction #[3-8].[5-8] Loopback The associated entity has a TAP-101
circuit loopback (MPT-HLC loopback activated at the Abnormal
(continued) connected to near end. conditions
EASv2,
P8ETH)
Line facing PDH DS1 Port#[1-16] External Loopback The associated entity has a TAP-101
loopback DS1 on MSS-1 line facing PDH (DS1 or Abnormal
shelf DS3) loopback activated at conditions
the near end.
DS1 Port#[1-32] External Loopback
DS3 Port#[1-2] External SLOT#[3-8]
Line facing SDH OC3 Port#[1-2] External Loopback The associated entity has a TAP-101
loopback SLOT#[3-8] line facing PDH (OC3) Abnormal
loopback activated at the conditions
near end.
Lockout switch Spare#0 Slot#2 Equipment A Lockout Equipment TAP-101
for EPS, RPS, Protection Protection Switch (EPS) has Abnormal
and TPS EPS (Core-E) been executed for the conditions
protection group.
Spare#0 Slot#[4,6,8] Equipment
Protection
(MOD300,
P2E3DS3,
P32E1DS1,
SDHACC)
Spare#0 Slot#[3-8] Equipment
(MPT ODU
connected to
MPTACC)
Spare#0 Slot #1 Equipment
(MPT ODU
connected to
Core-E)


(equipment)
Lockout switch Spare#0 MSS/CORE Equipment A Lockout Equipment TAP-101

for EPS, RPS, Port #[2,4,6] Protection Protection Switch (EPS) has Abnormal
and TPS EPS (MPT ODU been executed for the conditions
(continued) connected to protection group.
MSS/CORE)
(MPT ODU
connected to
EASv2)
(MPT-HL
connected to
EASv2,
P8ETH)
Spare#0 Slot #1 Equipment
(MPT-HLC
connected to
Core-E)
Spare#0 MSS/CORE Equipment
(MPT-HLC
connected to
MSS/CORE)
(MPT-HLC
connected to
EASv2,
P8ETH)
Lockout switch Spare#0 Slot#[4,6,8] Rx Radio A Lockout Rx Protection TAP-101
for EPS, RPS, Protection Switch (RPS) has been Abnormal
and TPS RPS (MOD300) executed for the protection conditions
group.


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

for EPS, RPS, Port #[2,4,6] Protection Switch (RPS) has been Abnormal
and TPS RPS (MPT ODU executed for the protection conditions
(continued) connected to group.
Core-E)
Spare#0 MSS/CORE Rx Radio
(MPT ODU
connected to
MSS/CORE)
Spare#0 Slot#[3-8] Rx Radio
(MPT ODU
connected to
MPTACC)
Spare#0 Slot#[4,6,8] Rx Radio
(MPT ODU
connected to
EASv2)
Spare#0 Slot#[4,6,8] Rx Radio
(MPT-HL
connected to
EASv2,
P8ETH)
Spare#0 Slot #1 Rx Radio
(MPT-HLC
connected to
Core-E)
Spare#0 MSS/CORE Rx Radio
(MPT-HLC
connected to
MSS/CORE)


(equipment)
Lockout switch Spare#0 Slot#[4,6,8] Rx Radio A Lockout Rx Protection TAP-101

for EPS, RPS, Port #[5-8] Protection Switch (RPS) has been Abnormal
and TPS RPS (MPT-HLC executed for the protection conditions
EASv2,
P8ETH)
Lockout switch Spare#0 Slot#[4,6,8] HSB A Lockout Tx Protection TAP-101
for EPS, RPS, Protection Switch (TPS) has been Abnormal
and TPS TPS (MOD300) executed for the protection conditions
group.
Spare#0 Slot #1 HSB
(MPT ODU
connected to
Core-E)
Spare#0 MSS/CORE HSB
(MPT ODU
connected to
MSS/CORE)
Spare#0 Slot#[3-8] HSB
(MPT ODU
connected to
MPTACC)
Spare#0 Slot#[4,6,8] HSB
(MPT ODU
connected to
EASv2)
(MPT-HL
connected to
EASv2,
P8ETH)


(equipment)
Lockout switch Spare#0 Slot #1 HSB A Lockout Tx Protection TAP-101

for EPS, RPS, Port #[2,4,6] Protection Switch (TPS) has been Abnormal
and TPS TPS (MPT-HLC executed for the protection conditions
Core-E)
Spare#0 MSS/CORE HSB
(MPT-HLC
connected to
MSS/CORE)
(MPT-HLC
connected to
EASv2,
P8ETH)
Rx Main squelch Direction #1.[5-6] - Radio Main receiver has been TAP-101
Channel #[0-1] (MPT-HLC squelched. Abnormal
connected to conditions
Core-E, MSS/
CORE)
Channel #[0-1] (MPT-HLC
connected to
EASv2,
P8ETH)
Rx Div squelch Direction #1.[5-6] - Radio Diversity receiver has been TAP-101
Channel #[0-1] (MPT-HLC squelched. Abnormal
connected to conditions
Core-E, MSS/
CORE)
connected to
EASv2,
P8ETH)


(equipment)
TXMute Direction #1.[1-6] - Radio Manual or automatic mute TAP-101

Channel #[0-1] (MPT ODU command has been Abnormal
connected to executed. conditions
Core-E, MSS/
CORE)
Channel #[0-1] (MPT ODU
connected to
MPTACC
Channel #1 (MPT ODU
connected to
P8ETH
Channel #1 (MPT ODU
connected to
EASv2
Channel #[0-1] (MPT ODU
connected to
EASv2
Channel #1 (MPT-HL
connected to
Core-E, MSS/
CORE)
Channel #[0-1] (MPT-HL
connected to
EASv2,
P8ETH)
connected to
Core-E, MSS/
CORE)


(equipment)
TXMute Direction #[3-8].[5-8] - Radio Manual or automatic mute TAP-101

(continued) Channel #[0-1] (MPT-HLC command has been Abnormal
connected to executed. conditions
EASv2,
P8ETH)
Direction #[3-8] - Radio
Channel #[0-1] (ODU300)
Table 9.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 PDU.
Not Equipped Verify 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 Card Mismatch Check alarms for replaceable unit type
Blinking mismatch, see
TAP-103 Equipment alarms.
Major Red At least one alarm with Critical or Retrieve alarms using the alarm monitor,
Alarm Major severity present in the NE. see Table 9.3, and troubleshoot
accordingly.

Table 9.5 — Core-E Card LED indications (Continued)
Minor Red At least one alarm with Minor severity Retrieve alarms using the alarm monitor,
Alarm present in the NE. see Table 9.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 9.3, and troubleshoot
accordingly.
Abnormal Yellow At least one abnormal condition Retrieve abnormal condition using
present in the NE. JSUM, see Table 9.4, and troubleshoot
accordingly.
Table 9.6 — 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.
MSS-1 shelf not Equipped Verify 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 9.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 9.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 9.3, and troubleshoot
accordingly.

Table 9.6 — MSS-1 shelf LED indications (Continued)
Abnormal Yellow At least one abnormal condition Retrieve abnormal condition using
present in the NE. JSUM, see Table 9.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 9.7 — Transport Card LED indications

Not Powered Verify MSS-4/8 shelf fuse is not blown
or missing.
Not Equipped Verify the card is properly installed.
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.
Red Card Fail Replace card
Red Blinking Card Mismatch Check alarms for replaceable unit type
mismatch, see
TAP-103 Equipment alarms.
PFoE Yellow Port is emitting power according to the —
configuration.
OFF Port is not emitting power according to
the configuration.

Table 9.8 — Ethernet LED indications
LED Indication Description Probable cause Corrective action
ETH Green LED Loss of Ethernet Cable between link partner Connect/repair cable.
Link 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 9.9 — MPT-HL transceiver LED alarm indications

Not Powered Verify MPT-HL Transceiver fuse is
not blown or missing.
Verify Power cable is properly
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 be software boot to complete.
used to identify each step of the startup
process.)

Table 9.9 — MPT-HL transceiver LED alarm indications (Continued)
Status Green Card Properly Equipped and Normal Operating condition. No

(continued) 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 or Check alarms.
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 far end
position: and set to ON ‘1’ position.
Yellow/Red Card Properly Equipped and —
Blinking Provisioned, TX or RX signal Fault,
EPS and RPS currently in Standby.
Traffic maybe affected:
Equipment problem at either near end or Check alarms.
far end: Check abnormal conditions.
Red Card Fail Replace MPT-HL Transceiver
Status Red Blinking MAP Communication Time-out: Check alarms for Internal
(continued) Communication between the MPT-HL Communication
Transceiver and the Core-E, EASv2, or Problem, if present, see
P8ETH card or MSS-1 shelf is lost.
TAP-107 Internal loss of
communications.

Table 9.9 — MPT-HL transceiver LED alarm indications (Continued)
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
currently in standby state. be in standby state.
Software booting or FPGA download in Wait for software booting or FPGA
progress download to complete

Table 9.10 — MPT-HLC transceiver LED alarm indications

Not Powered Verify MPT-HLC Transceiver fuse is
not blown or missing.
Verify Power cable is properly
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-HLC Transceiver.
Green/Red Card properly equipped and —
Blinking provisioned. RX 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.
PA switch at the far end is set to OFF Verify PA switch position at far end
‘0’ position: and set to ON ‘1’ position.

Table 9.10 — 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:
Equipment problem at either near end Check alarms.
or far end: Check abnormal conditions.
Red Card Fail Replace MPT-HLC Transceiver
Red Blinking MAP Communication Time-out: Check alarms for Internal
Communication between the Communication
MPT-HLC Transceiver and the Problem, if present, see
Core-E, EASv2, or P8ETH card or
TAP-107 Internal loss of
MSS-1 shelf is lost.
communications.

Table 9.10 — MPT-HLC transceiver LED alarm indications (Continued)
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 automute 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 Wait for software booting or FPGA
in progress download to complete

Table 9.11 — 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 channel. managed within a single region. Split the
network Polling radios for PM data or missed radio network management into
alarms too rapidly different regions and backhaul the traffic
for each region through separate
Multiple remote software downloads in
channels.
process
Poll the radios more slowly.
IP traffic other than network
management traffic being routed Download to fewer radios at a time.
through radio network Configure external routers to allow only
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.
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 If the TMN Interface is configured for Use the correct write community string.
SNMP 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 for
with the NE through the routing failure within the radio network. communication path or routing
radio network (unable to Incorrect IP address on the PC. problems.
‘ping’ the NE). Verify PC IP address, subnet, and
default route.

Table 9.11 — TMN network troubleshooting (Continued)
Problem Possible Cause Possible Solution
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.


10 — IXL-102 Support procedures
Table 10.1 lists the support procedures that are needed to perform maintenance and trouble
clearing on the system.
For more information about operation and administration, see the Alcatel-Lucent
9500 MPR-A Operation and Administration.
Table 10.1 — Support procedures
Support procedure See

Alarm and event reports, Retrieve Alcatel-Lucent 9500 MPR-A Operation and
Administration
Clean fiber-optic connectors DLP-112 Clean fiber-optic connectors
Clock reference and operation mode selections Alcatel-Lucent 9500 MPR-A Operation and
Administration
Log into system Alcatel-Lucent 9500 MPR-A Operation and
Administration
Loopback (Core Facing) Alcatel-Lucent 9500 MPR-A Operation and
Administration
Manage cross-connections Alcatel-Lucent 9500 MPR-A Operation and
Administration
MIB Database Management (Backup and Restore) Alcatel-Lucent 9500 MPR-A Operation and
Administration
Password change Alcatel-Lucent 9500 MPR-A Operation and
Administration
Performance monitoring Alcatel-Lucent 9500 MPR-A Operation and
Administration
Protection switching controls Alcatel-Lucent 9500 MPR-A Operation and
Administration
Provision equipment Alcatel-Lucent 9500 MPR-A Operation and
Administration

10 — IXL-102 Support procedures
Table 10.1 — Support procedures (Continued)
Provision or edit ports Alcatel-Lucent 9500 MPR-A Operation and

Administration
Preventive maintenance RTL-100 Preventive maintenance procedures
Protection upgrade and downgrade DLP-117 Protection upgrade and downgrade
procedures
Resolve WebEML/TCO Suite/NEtO startup issues DLP-129 Resolve WebEML/TCO Suite/NEtO startup
issues
Software package rollback DLP-127 Software package rollback
System power down and power up DLP-113 System power down and power up
Upgrade and downgrade radio profile DLP-118 Upgrade and downgrade radio profile
Upgrade unlicensed MPT-HL radio to lower 6 GHz DLP-119 Upgrade unlicensed MPT-HL radio to lower
radio 6 GHz radio
Upgrade MPT ODU to MPT ODU L1 LAG port DLP-123 Upgrade MPT ODU to MPT ODU L1 LAG
port
Upgrade MPT-HL to MPT-HL L1 LAG port DLP-124 Upgrade MPT-HL to MPT-HL L1 LAG port

11 — IXL-103 Equipment replacement
procedures
Table 11.1 lists where to find the detailed level procedure (DLP) for replacing or adding
each 9500 MPR-A replaceable unit.
Table 11.1 — Equipment replacement procedures
Equipment
DLP-120 +24/-48 volt converter replacement

DLP-116 Auxiliary (AUX) replacement
DLP-103 Core switching module (Core-E) replacement
DLP-104 Core switching module (Core-E) flash card replacement
DLP-105 Ethernet Access Switch replacement (EASv2 and P8ETH)
DLP-100 Mechanical card removal and installation
DLP-128 MSS-1 shelf replacement
DLP-106 MSS-4/8 shelf FAN replacement
DLP-101 MPT-HL/MPT-HLC transceiver air filter replacement
DLP-108 MPT-HL/MPT-HLC transceiver replacement
DLP-109 ODU300 replacement
DLP-107 MOD300 (radio modem) replacement
DLP-114 MPTACC (MPT Access) replacement
DLP-115 MPT ODU replacement (MPT-HC, MPT-XP, 9558HC)
DLP-125 MPT Power Unit replacement
DLP-110 P2E3DS3 (2-Port DS3) replacement
DLP-111 P32E1DS1 (32-Port DS1) replacement
DLP-121 Power injector replacement

11 — IXL-103 Equipment replacement procedures
Table 11.1 — Equipment replacement procedures (Continued)
Equipment
DLP-122 RPS/XPIC module replacement

DLP-126 SDHACC (2-Port OC-3) Replacement
DLP-102 SFP replacement

12 — IXL-104 Supporting information
Table 12.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, see the Alcatel-Lucent 9500 MPR-
A Operation and Administration.
• See the Alcatel-Lucent 9500 MPR-A Product Information to determine card location
and type.
Table 12.1 — Supporting information
Supporting information See
Alarm condition types Alcatel-Lucent 9500 MPR-A Operation and Administration

Card locations Alcatel-Lucent 9500 MPR-A Product Information
Product support information Introduction
Electrostatic-sensitive devices Introduction
How to use TOP documentation Introduction
Laser precautions Introduction
Maintenance philosophy Introduction
Operations support system Alcatel-Lucent 9500 MPR-A Operation and Administration
Safety awareness Introduction
Security/user authorization Alcatel-Lucent 9500 MPR-A Operation and Administration

12 — IXL-104 Supporting information

13 — RTL-100 Preventive maintenance
procedures
There are no preventive maintenance procedures associated with 9500 MPR-A, R5.1.0.
Table 13.1 lists the preventive maintenance procedure and the corresponding reference.
The frequency that is listed is recommended. Local conditions may require maintenance
procedures be performed more or less frequently.
Table 13.1 — Preventive maintenance procedures
Activity Frequency
DLP-101 MPT-HL/MPT-HLC transceiver air filter Every 6 months

replacement

13 — RTL-100 Preventive maintenance procedures

14 — TAP-100 Facility alarms
14.1 — Purpose
This procedure describes how to identify and clear Facility alarms.
14.2 — General
An AIS (on DS1/3-in) is an alarm indication signal on one or more DS1 or DS3 input
signals incoming to the NE on the P32E1DS1, P2E3DS3 cards, or MSS-1 shelf. The
problem is associated with the DS1 or DS3 input signal to the P32E1DS1, P2E3DS3 cards,
or MSS-1 shelf.
An AIS (on DS1/3-out) is alarm indication signal (AIS) detected by the receive circuit from
the radio link on one or more of the DS1 or DS3 lines, indicating an upstream failure.
An AIS (on Ele/OptSDH-in) is an alarm indication signal on one or more OC-3 input
signals incoming to the NE on the SDHACC card. The problem is associated with the OC-3
input signal to the SDHACC card.
An AIS (on Ele/OptSDH-out) is alarm indication signal (AIS) detected by the receive
circuit from the radio link on one or more of the 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 (DS1/3-in) indicates no DS1 or DS3 frame is detected on the input from
the client to the P32E1DS1, P2E3DS3 cards, or MSS-1 shelf.

A Loss Of Frame (DS1/3-out) indicates no DS1, DS3 frame is detected on a DS1 or DS3
facility from the switch matrix.
A Loss Of Signal (DS1/3-in) indicates no DS1 or DS3 signal detected on the input on the
P32E1DS1, P2E3DS3 cards, or MSS-1 shelf.
A Remote Defect Indication in a received OC-3 facility. Alarm is reported when an RDI is
received on a given OC-3 from the remote end of OC-3 facility.
A Trace Identifier Mismatch indicates a J0 byte value received on the OC-3 facility is
different than the provisioned expected value for the OC-3 facility.
See the Alcatel-Lucent 9500 MPR-A Product Information to determine card location and
address.
See the Alcatel-Lucent 9500 MPR-A Operation and Administration for information about
how to execute the commands that are described in this procedure.
14.3 — Procedure
1. Using the Alarm Monitor, retrieve all alarms.
2. Review the output. See Table 14.1 for information about facility alarms.
Table 14.1 — Facility alarms
Probable cause Friendly name/entity Facility type See
AIS DS1-in/MSS/DS1/Port#[1-16] DS1 (MSS/DS1) Step 3
DS1-in/Slot#[3-8]/Port#[1-32] DS1 (P32E1DS1)
DS3-in/Slot#[3-8]/Port#[1-2] DS3
AIS DS1-out/MSS/DS1/Port#[1-16] DS1 (MSS/DS1) Step 7
DS1-out/Slot#[3-8]/Port#[1-32] DS1 (P32E1DS1)
DS3-out/Slot#[3-8]/Port#[1-2] DS3
AIS EleSdh-in/slot#[3-8]/Port[1-2] OC-3 Step 10
OptSdh-in/slot#[3-8]/Port[1-2]
AIS EleSdh-out/slot#[3-8]/Port[1-2] OC-3 Step 14
OptSdh-out/slot#[3-8]/Port[1-2]
High BER EleSdh-in/slot#[3-8]/Port[1-2] OC-3 Step 17

Table 14.1 — Facility alarms (Continued)
High BER EleSdh-out/slot#[3-8]/ OC-3 Step 21

Port[1-2]
OptSdh-out/slot#[3-8]/
Port[1-2]
Loss Of CESoETH frame CircuitTDM/MSS/DS1/Port#[1-16] DS1 (MSS/DS1) Step 24
CircuitTDM/Slot#[3-8]/Port#[1-32] DS1 (P32E1DS1)
CircuitTDM/Slot#[3-8]/Port#[1-2] DS3
CircuitTDM/Slot#[3-8]/Port#[1-2] OC-3
Loss Of Frame DS1-in/MSS/DS1/Port#[1-16] DS1 (MSS/DS1) Step 77
Loss of frame DS1-out/MSS/DS1/Port#[1-16] DS1 (MSS/DS1) Step 108
DS1-out/Slot#[3-8]/Port#[1-32] DS1 (P32E1DS1)
DS3-out/Slot#[3-8]/Port#[1-2] DS3
Loss of frame EleSdh-in/slot#[3-8]/Port[1-2] OC-3 Step 77
Loss of frame EleSdh-out/slot#[3-8]/Port[1-2] OC-3OC-3 Step 108
OptSdh-out/slot#[3-8]/Port[1-2]
Loss of signal DS1-in/MSS/DS1/Port#[1-16] DS1 (MSS/DS1) Step 155
Loss of signal EleSdh-in/slot#[3-8]/Port[1-2] OC-3 Step 155
Remote defect indication EleSdh-in/slot#[3-8]/Port[1-2] OC-3 Step 178
Trace identifier mismatch EleSdh-in/slot#[3-8]/Port[1-2] OC-3 Step 182

Table 14.1 — Facility alarms (Continued)
None of the above — — IXL-101

Alarm and
abnormal
condition
clearing
procedures
3. AIS
on DS1/3-in on DS1 or DS3 facility
Troubleshoot the source of input that is associated with the DS1 or DS3 input signal to
the P32E1DS1, P2E3DS3 cards, or MSS-1 shelf.
4. Verify the cabling that is associated with the input DS1 or DS3 signal to the P32E1DS1,
P2E3DS3 cards, or MSS-1 shelf.
5. Retrieve the alarms using the Alarm Monitor.
6. Did AIS (on DS1/3-in) alarm clear?
a. If yes, go to step 190.
b. If no, go to step 189.
7. AIS
on DS1/3-out on DS1 or DS3 facility
Troubleshoot the upstream source of the incoming DS1 or DS3.
9. Did the AIS (on DS1/3-out) alarm clear?
10. AIS
on EleSdh/EleSDH-in on OC-3 facility
Troubleshoot the source of input that is associated with the OC-3 input signal to the
SDHACC card.
11. Verify the cabling that is associated with the input OC-3 signal to the SDHACC card.
13. Did AIS (on EleSdh/OptSdh-in) alarm clear?
14. AIS
on EleSdh/EleSDH-out on OC-3 facility
Troubleshoot the upstream source of the incoming OC-3.

16. Did the AIS (on EleSdh/OptSdh-out) alarm clear?

17. High BER
on EleSdh/EleSDH-in on OC-3 facility
Troubleshoot the source of input that is associated with the OC-3 input signal to the
SDHACC card from the demarcation panel.
18. Verify the cabling that is associated with the input OC-3 signal to the SDHACC card.
20. Did High BER (on EleSdh/OptSdh-in) alarm clear?
21. High BER
on EleSdh/EleSDH-out on OC-3 facility
Troubleshoot the upstream source of the incoming OC-3.
23. Did the High BER (on EleSdh/OptSdh-out) alarm clear?
24. Loss Of CESoETH frame
on DS1, DS3, or OC-3 facility
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.
25. Verify that the radio path PM is not taking errors to traffic.
26. Are there path or circuit alarms, or path PM errors at near end or far end NE?
a. If yes, clear the path or circuit alarms, or path PM errors, then go to step 27.
28. Did the Loss Of CESoETH Frame alarm clear?
29. Verify the circuit provisioning for near end, the far end, and all intermediate NEs:
a. Verify the Signal Mode is set the same and is correct.
b. Verify the Line Coding is set the same and is correct.
c. Verify the Flow ID is set the same and is correct.
d. Verify the Service Profile is set the same and is correct.

30. Is the Service Profile TDM2ETH?

31. Verify the TDM2ETH provisioning for the near end, far end, and all intermediate NEs:
a. Verify the Payload Size is set the same and is correct.
b. Verify the TDM Clock Source is set the same and is correct.
c. Verify the near end ECID Tx and far end ECID Rx are set the same and are correct.
d. Verify the far end ECID Tx and near end ECID Rx are set the same and are correct.
32. Verify the cross-connection provisioning for the near end, far end, and all intermediate
NEs:
35. Is the facility associated with a LAG?
36. Verify that there are no active LAG alarms at all NEs in the LAG associated with the
facility in alarm.
39. Is the facility associated with an ERP (Ring)?
40. Verify that there are no active RING alarms at all NEs in the ring associated with the
facility in alarm.
43. CAUTION: Possibility of service interruption. 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 appropriate maintenance window per local practices
and procedures.
Is it appropriate to proceed with Loss Of CESoETH Frame procedure?


44. Is the facility protected?
45. CAUTION: Possibility of service interruption. Reseating card in an unprotected
facility cause a loss of traffic on ALL facilities that are associated with the card
being reseated. Schedule appropriate maintenance window per local practices
and procedures.
46. For the P32E1DS1 or P2E3DS3 cards, reseat the card at 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.
49. CAUTION: Possibility of service interruption. Replacing card in an unprotected
being replaced. Schedule appropriate maintenance window per local practices
and procedures.
Which card reported the Loss Of CESoETH Frame alarm?
a. If MSS-1 shelf, see DLP-128 MSS-1 shelf replacement to replace near end MSS-1
shelf.
b. If P32E1DS1, see DLP-111 P32E1DS1 (32-Port DS1) replacement to replace near
end P32E1DS1 card.
c. If P2E3DS3, see DLP-110 P2E3DS3 (2-Port DS3) replacement to replace near end
P2E3DS3 card.
d. If SDHACC, see DLP-126 SDHACC (2-Port OC-3) Replacement to replace near
end SDHACC card.
and procedures.

53. For the P32E1DS1 or P2E3DS3 cards, reseat the card at far end. Physically remove the
card and reinsert.
For the MSS-1 shelf, locate the fuses protecting the A and B battery feeds to the far end
MSS-1 shelf and remove. Wait ten seconds. Then install the fuses protecting the A and
B battery feeds.
and procedures.
Which card reported the Loss Of CESoETH Frame alarm?
a. If MSS-1 shelf, see DLP-128 MSS-1 shelf replacement to replace far end MSS-1
shelf.
b. If P32E1DS1, see DLP-111 P32E1DS1 (32-Port DS1) replacement to replace far
end P32E1DS1 card.
c. If P2E3DS3, see DLP-111 P32E1DS1 (32-Port DS1) replacement to replace far
end P2E3DS3 card.
d. If SDHACC, see DLP-126 SDHACC (2-Port OC-3) Replacement to replace far
end SDHACC card.
59. CAUTION: Possibility of service interruption. Forced/Lockout switching traffic
causes a disruption to traffic.
60. Is the DS1/DS3/OC-3 facility in alarm associated with the main or spare?
a. If main, perform Forced EPS Switch at near end using Craft Terminal.
b. If spare, perform Lockout EPS Switch at near end using Craft Terminal.
61. Reseat the card in alarm at the near end. Physically remove the card and reinsert.
64. Which card reported the Loss Of CESoETH Frame?
a. If P32E1DS1, see DLP-111 P32E1DS1 (32-Port DS1) replacement to replace near
end P32E1DS1 card.

b. If P2E3DS3, see DLP-110 P2E3DS3 (2-Port DS3) replacement to replace near end
P2E3DS3 card.
c. If SDHACC, see DLP-126 SDHACC (2-Port OC-3) Replacement to replace near
end SDHACC card.
66. Did the Loss Of CESoETH Frame condition clear?
Is the card in alarm the main or spare?
a. If main, perform Forced EPS Switch at far end using Craft Terminal.
b. If spare, perform Lockout EPS Switch at far end using Craft Terminal.
68. Reseat the card in alarm at the far end. Physically remove the card and reinsert.
71. Which card reported the Loss Of CESoETH Frame?
a. If P32E1DS1, see DLP-111 P32E1DS1 (32-Port DS1) replacement to replace far
end P32E1DS1 card.
b. If P2E3DS3, see DLP-110 P2E3DS3 (2-Port DS3) replacement to replace far end
P2E3DS3 card.
c. If SDHACC, see DLP-126 SDHACC (2-Port OC-3) Replacement to replace far
end SDHACC card.
73. Did the Loss Of CESoETH Frame condition clear?
74. CAUTION: Possibility of service interruption. Releasing Forced/Lockout switch
may cause a disruption to traffic.
Release Forced/Lockout EPS Switch at far end using Craft Terminal.
Release Forced/Lockout EPS Switch at near end using Craft Terminal.
76. Go to step 190.
77. Loss Of Frame
on DS1/3-in on DS1 or DS3 or Ele/OptSdh-in on OC-3 facility

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.
78. 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 79.
80. Did the Loss Of Frame alarm the clear?
81. Verify the circuit provisioning for both the near end and client end of the facility in
alarm:
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.
e. Verify that the LBO setting is correct for the installation.
83. Did the Loss Of Frame alarm clear?
84. Verify that the Source Signal is error-free with a test set configured to match the
provisioning of the facility.
87. Verify the cabling:
a. Verify that 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 that the cabling from the patch panel to the module if appropriate. Confirm
that the connectors are correctly seated and secured.

traffic on ALL facilities that are supported by the card or MSS-1 shelf, associated
with the facility in alarm. Schedule appropriate maintenance window per local
practices and procedures.
Is it appropriate to proceed with Loss Of Frame procedure?
91. Is the facility protected?
facility causes a loss of traffic on ALL facilities that are associated with the card
and procedures.
93. For the P32E1DS1 or P2E3DS3 cards, reseat the card at near end. Physically remove
96. CAUTION: Possibility of service interruption. Replacing 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 appropriate maintenance
window per local practices and procedures.
Which card reported the Loss Of Frame alarm?
shelf.
end P32E1DS1 card.
P2E3DS3 card.
end SDHACC card.


Is the DS1/DS3/OC-3 facility in alarm associated with the main or spare?
100.Reseat the card in alarm at near end. Physically remove card and reinsert.
101.Retrieve the alarms using the Alarm Monitor.
102.Did the Loss Of Frame alarm clear?
103.Which card reported the Loss Of Frame?
end P32E1DS1 card.
P2E3DS3 card.
end SDHACC card.
105.Did the Loss Of Frame condition clear?
106.CAUTION: Possibility of service interruption. Releasing Forced/Lockout switch
107.Go to step 190.
108.Loss of frame
on DS1/3-out on DS1 or DS3 or Ele/OptSdh-out on OC-3 facility
Check the far end facility for Loss of Frame (DS1/3-in, Ele/OptSdh-in) that is
associated with the facility in alarm.
111.Verify that there are no active path or circuit alarms associated with the facility in
alarm for the near end or far end NE.
112.Verify that the radio path PM is not taking errors to traffic.
113.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 114.


116.Check the circuit provisioning for the near end and far end facility in alarm and that
they are correct, as required:
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.
117.Is the Service Profile TDM2ETH?
118.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.
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.
121.Check the cross-connection provisioning at 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.

124.CAUTION: Possibility of service interruption. 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 appropriate maintenance window per local practices
and procedures.
Is it appropriate to proceed with Loss Of Frame procedure?
125.Is the facility protected?
126.CAUTION: Possibility of service interruption. Reseating card in an unprotected
facility cause a loss of traffic on ALL facilities that are associated with the card or
MSS-1 shelf being reseated. Schedule appropriate maintenance window per local
For the P32E1DS1 or P2E3DS3 cards, reseat the card at near end. Physically remove
129.Replacing card in an unprotected facility cause a loss of traffic on ALL facilities
that are associated with the card being replaced. Schedule appropriate
maintenance window per local practices and procedures.
Which card reported the Loss Of Frame alarm?
shelf.
end P32E1DS1 card.
P2E3DS3 card.
end SDHACC card.


and procedures.
For the P32E1DS1 or P2E3DS3 cards, reseat the card at far end. Physically remove the
card and reinsert.
For the MSS-1 shelf, locate the fuses protecting the A and B battery feeds to the far end
MSS-1 shelf and remove. Wait ten seconds. Then install the fuses protecting the A and
B battery feeds.
135.CAUTION: Possibility of service interruption. Replacing card in an unprotected
and procedures.
Which card reporting Loss Of Frame alarm?
a. If MSS-1 shelf, see DLP-128 MSS-1 shelf replacement to replace far end MSS-1
shelf.
b. If P32E1DS1, see DLP-111 P32E1DS1 (32-Port DS1) replacement to replace far
end P32E1DS1 card.
c. If P2E3DS3, see DLP-110 P2E3DS3 (2-Port DS3) replacement to replace far end
P2E3DS3 card.
d. If SDHACC, see DLP-126 SDHACC (2-Port OC-3) Replacement to replace far
end SDHACC card.
138.CAUTION: Possibility of service interruption. Forced/Lockout switching traffic
Is DS1/DS3/OC-3 facility in alarm associated with main or spare?
139.Reseat card in alarm at near end. Physically remove card and reinsert.


142.Which card reporting Loss Of Frame?
end P32E1DS1 card.
P2E3DS3 card.
end SDHACC card.
Is card in alarm main or spare?
a. If main, perform Forced EPS Switch at far end using Craft Terminal.
b. If spare, perform Lockout EPS Switch at far end using Craft Terminal.
146.Reseat the card in alarm at the far end. Physically remove the card and reinsert.
149.Which card reporting Loss Of Frame?
a. If P32E1DS1, see DLP-111 P32E1DS1 (32-Port DS1) replacement to replace far
end P32E1DS1 card.
b. If P2E3DS3, see DLP-110 P2E3DS3 (2-Port DS3) replacement to replace far end
P2E3DS3 card.
end SDHACC card.
Release Forced/Lockout EPS Switch at far end using Craft Terminal.


154.Go to step 190.
155.Loss of signal
DS1/3-in on DS1, DS3, or OC-3 facility
Troubleshoot source of input to MSS-1 shelf, P32E1DS1, P2E3DS3, or SDHACC
card.
156.Verify cabling associated with the input signal to the MSS-1 shelf, P32E1DS1,
P2E3DS3, or SDHACC card.
157.Retrieve alarms using craft terminal.
158.Did the Loss Of Signal alarm clear?
159.Retrieve alarms using craft terminal. Determine if Loss Of Signal alarm is declared
against ALL facilities associated with the MSS-1 shelf, P32E1DS1, P2E3DS3, or
SDHACC card.
160.Are ALL facilities associated with the MSS-1 shelf, P32E1DS1, P2E3DS3, or
SDHACC card declaring Loss Of Signal?
161.Is the facility protected?
and procedures.
Reseat the card that declares the Loss Of Signal alarm. Physically remove the card and
reinsert.
164.Did declaring Loss Of Signal alarm clear?
165.CAUTION: Possibility of service interruption. Replacing card in an unprotected
and procedures.
Which card reported the Loss Of Signal alarm?
end P32E1DS1 card.

P2E3DS3 card.
end SDHACC card.
168.CAUTION: Possibility of service interruption. Forced EPS switching traffic
Is the card in alarm the main or spare?
169.Verify that the card in alarm status is Standby.
170.Reseat the card that declared the Loss Of Signal alarm. Physically remove the card and
reinsert.
172.Did the declaring Loss Of Signal alarm clear?
173.Which card reported the Loss Of Signal alarm?
end P32E1DS1 card.
P2E3DS3 card.
end SDHACC card.
176.CAUTION: Possibility of service interruption. Releasing EPS switch may cause a
disruption to traffic.
177.Go to step 190.
178.Remote defect indication
Retrieve the alarms for the far end of the OC-3 facility using the Alarm Monitor.

179.Determine all of the facility alarms that are declared against the far end OC-3 facility
associated with the OC-3 facility declaring the Remote Defect Indication (RDI) and
troubleshoot accordingly.
181.Did the RDI alarm clear?
182.Trace identifier mismatch
Using the Craft Terminal, retrieve the provisioned Trace Identifier values for the
alarmed OC-3 facility.
Note: The section trace identifier (J0) value is not generated within the 9500 MPR-A
network. The received J0 value is verified against the provisioned expected value. To
determine the provisioned J0 value the operator must query the originating OC-3
equipment.
183.Determine the origination of the OC-3 facility and retrieve the provisioned Trace
Identifier parameters.
184.Verify the desired Trace Identifier parameters of the OC-3 facility.
185.Determine which Trace Identifier parameters are incorrect.
186.Provision the Trace Identifier parameters according to the results of step 185.
188.Did the Trace Identifier Mismatch alarm clear?
189.Contact the next level of technical support for assistance.
190.STOP. This procedure is complete.


15 — TAP-101 Abnormal conditions
15.1 — Purpose
This procedure describes how to identify and clear a protection switch (Forcedand
Lockout), loopback, Forced Adaptive Modulation, Rx combiner squelch, and TxMute
abnormal conditions on Core-E, MOD300, MPT-HC/MPT-XP/9558HC (MPT ODU),
MPT-HL, MPT-HLC, ODU300, P2E3DS3, P32E1DS1, SDHACC cards or MSS-1 shelf.
15.2 — General
A Core Facing PDH Loopback indicates that PDH (DS1 or DS3) entity has a loopback
activated at the near end.
A Core Facing SDH Loopback indicates that SDH (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.
An IF Cable Loopback indicates that the MOD300/ODU300 has a loopback activated at the
near end.
A Line Facing Circuit Loopback indicates that the entity has a loopback activated at the
near end.
A Line Facing PDH Loopback indicates that PDH (DS1 or DS3) entity has a line facing
loopback activated at the near end.
A Line Facing SDH Loopback indicates that SDH (OC3) entity has a line facing loopback
activated at the near end.

A Lockout Switch EPS/RPS/TPS indicates that a lockout switch has been executed for the
protection group.
An Rx Main squelch or Rx Div squelch indicates that a squelch command has been
executed for an MPT-HLC combiner.
TxMute indicates that a manual or automatic mute command has been executed.
address.
15.3 — Procedure
1. Using the Craft Terminal, retrieve abnormal conditions.
2. Review the output. See Table 15.1 for information about abnormal conditions.
Table 15.1 — Abnormal conditions
Operation Name Type (equipment) See
Core facing PDH DS1 Port#[1-16] Internal Loopback Step 3

loopback MSS/DS1
Core facing SDH OC3 Port#[1-2] Internal Loopback Step 7

loopback SLOT#[3-8]

Table 15.1 — Abnormal conditions (Continued)
Digital core facing Direction #1.[1-6] Loopback Step 11

loopback (MPT ODU connected to
Core-E, MSS/CORE)
(MPT ODU connected to
MPTACC)
P8ETH)
EASv2)
(MPT-HL connected to
Core-E, MSS/CORE)
(EASv2. MPT-HL)
(MPT-HLC connected to
Core-E, MSS/CORE)
EASv2, P8ETH)

Forced adaptive Direction #[3-8] - Channel #1 Radio Step 15

modulation (MOD300)
Direction #1.[1-6] - Channel #1 Radio
Core-E, MSS/CORE)
Direction #[3-8].[1-4] - Channel #1 Radio
MPTACC)
P8ETH)
EASv2)
Core-E, MSS/CORE)
EASv2, P8ETH)
Core-E, MSS/CORE)
Direction #[3-8].[5-8] - Channel #1 Radio (MPT-HLC
connected to EASv2,
P8ETH)

Forced switch EPS Main#1 Slot#1 Equipment Protection Step 19

(Core-E)
Main#1 Slot#[3,5,7] Equipment Protection
(MOD300, P2E3DS3,
P32E1DS1, SDHACC)
Main#1 Slot #[3-8] Port #[1-4] Equipment Protection
MPTACC)
Main#1 Slot #1 Port #[1,3,5] Equipment Protection
Core-E)
Main#1 MSS/CORE Port #[1,3,5] Equipment Protection
MSS/CORE)
Main#1 Slot #[3,5,7] Equipment Protection
Port #[5-8] (MPT ODU connected to
EASv2)
Main#1 Slot #[3,5,7] Port #[5-8] Equipment Protection
EASV2, P8ETH)
Main#1 Slot #1 Equipment Protection
Port #[1,3,5] (MPT-HLC connected to
Core-E)
Main#1 MSS/CORE Equipment Protection
MSS/CORE)
Port #[5-8] (MPT-HLC connected to
EASv2, P8ETH)

Forced switch RPS Main#1 Slot#[3,5,7] Rx Radio Protection Step 19

(MOD300)
Main#1 Slot #1 Port #[1,3,5] Rx Radio Protection
Core-E)
Main#1 MSS/CORE Port #[1,3,5] Rx Radio Protection
MSS/CORE)
Main#1 Slot #[3-8] Port #[1-4] Rx Radio Protection
MPTACC)
Main#1 Slot #[3,5,7] Rx Radio Protection
EASv2)
Main#1 Slot #[3,5,7] Port #[5-8] Rx Radio Protection
EASv2, P8ETH)
Main#1 Slot #1 Rx Radio Protection
Core-E)
Main#1 MSS/CORE Rx Radio Protection
MSS/CORE)
EASv2, P8ETH)

Forced switch TPS Main#1 Slot#[3,5,7] HSB Protection Step 19

(MOD300)
Main#1 Slot #1 Port #[1,3,5] HSB Protection
Core-E)
Main#1 MSS/CORE Port #[1,3,5] HSB Protection
MSS/CORE)
Main#1 Slot #[3-8] Port #[1-4] HSB Protection
MPTACC)
Main#1 Slot #[3,5,7] HSB Protection
EASv2)
Main#1 Slot #[3,5,7] Port #[5-8] HSB Protection
EASv2, P8ETH)
Main#1 Slot #1 HSB Protection
Core-E)
Main#1 MSS/CORE HSB Protection
MSS/CORE)
EASv2, P8ETH)
IF cable loopback Direction #[3-8] Loopback Step 24
(MOD300)

Line facing circuit Direction #1.[1-6] Loopback Step 28

Core-E, MSS/CORE)
MPTACC)
P8ETH)
EASv2)
Core-E, MSS/CORE)
EASv2, P8ETH)
Core-E, MSS/CORE)
EASv2, P8ETH)
Line facing PDH DS1 Port#[1-16] External Loopback Step 32
loopback (DS1 on MSS-1 shelf:
MSS/DS1)
DS3 Port#[1-2] External (P2E3DS3, P32E1DS1:
SLOT#[3-8])
Line facing SDH OC3 Port#[1-2] External Loopback Step 36
loopback (SDHACC: SLOT#[3-8])

Lockout switch for Spare#0 Slot#2 Equipment Protection Step 40

EPS, RPS, and TPS (Core-E)
EPS
Spare#0 Slot#[4,6,8] Equipment Protection
(MOD30, P2E3DS3,
P32E1DS1, SDHACC)
Spare#0 Slot #1 Port #[2,4,6] Equipment Protection
Core-E)
Spare#0 MSS/CORE Port #[2,4,6] Equipment Protection
MSS/CORE)
Spare#0 Slot#[3-8] Port #[1-4] Equipment Protection
MPTACC)
EASv2)
Spare#0 Slot #[4,6,8] Port #[5-8] Equipment Protection
EASV2, P8ETH)
Spare#0 Slot #1 Equipment Protection
Core-E)
Spare#0 MSS/CORE Equipment Protection
MSS/CORE)
EASv2, P8ETH)

Lockout switch for Spare#0 Slot#[4,6,8] Rx Radio Protection Step 40

EPS, RPS, and TPS (MOD300)
RPS
Spare#0 Slot #1 Port #[2,4,6] Rx Radio Protection
Core-E)
Spare#0 MSS/CORE Port #[2,4,6] Rx Radio Protection
MSS/CORE)
Spare#0 Slot#[3-8] Port #[1-4] Rx Radio Protection
MPTACC)
Spare#0 Slot#[4,6,8] Rx Radio Protection
EASv2)
Spare#0 Slot #[4,6,8] Port #[5-8] Rx Radio Protection
MPT-HL connected to
EASV2, P8ETH
Spare#0 Slot #1 Rx Radio Protection
Core-E)
Spare#0 MSS/CORE Rx Radio Protection
MSS/CORE)
EASv2, P8ETH)

Lockout switch for Spare#0 Slot#[4,6,8] HSB Protection Step 40

TPS
Spare#0 Slot #1 Port #[2,4,6] HSB Protection
Core-E)
Spare#0 MSS/CORE Port #[2,4,6] HSB Protection
MSS/CORE)
Spare#0 Slot #[3-8] Port #[1-4] HSB Protection
MPTACC)
Spare#0 Slot#[4,6,8] HSB Protection
EASv2)
Spare#0 Slot #[4,6,8] Port #[5-8] HSB Protection
EASV2, P8ETH)
Spare#0 Slot #1 HSB Protection
Core-E)
Spare#0 MSS/CORE HSB Protection
MSS/CORE)
EASv2, P8ETH)
Rx Main squelch Direction #1.[5-6] - Radio (MPT-HLC Step 48
Channel #[0-1] connected to Core-E,
MSS/CORE)
Direction #[3-8].[5-8] - Radio (MPT-HLC
Channel #[0-1] connected to EASv2,
P8ETH)

Rx Div squelch Direction #1.[5-6] - Radio (MPT-HLC Step 52

MSS/CORE)
P8ETH)
TXMute Direction #1.[1-6] - Channel #[0-1] Radio Step 44
Core-E, MSS/CORE)
Direction #[3-8].[1-4] - Channel #[0-1] Radio
MPTACC)
P8ETH)
EASv2
EASv2
Core-E, MSS/CORE)
EASv2, P8ETH)
Direction #1.[5-6] - Radio (MPT-HLC
MSS/CORE)
P8ETH)
Direction #[3-8] - Channel #[0-1] Radio
(ODU300)


Alarm and
abnormal
condition
clearing
procedures
3. Core facing PDH loopback

Ready to release the Core Facing PDH Loopback?
4. Using the Craft Terminal, release the loopback.
5. Retrieve the Abnormal Condition List using the Craft Terminal.
6. Did the Core Facing PDH Loopback condition clear?
7. Core facing SDH loopback
Ready to release the Core Facing SDH Loopback?
10. Did the Core Facing SDH Loopback condition clear?
11. Digital core facing loopback
Ready to release the Digital Core Facing Loopback?
14. Did the Digital Core Facing Loopback condition clear?
15. Forced adaptive modulation

Ready for the Forced Adaptive Modulation to be released?

16. Using the Craft Terminal, release the Forced Adaptive Modulation.
18. Did the Forced Adaptive Modulation condition clear?
19. Forced switch
EPS, RPS, and TPS
Ready to release the Forced Switch EPS/RPS/TPS?
20. CAUTION: Possibility of service interruption. Releasing a Forced Switch causes
a disruption to traffic.
21. Using the Craft Terminal, release Forced Switch EPS/RPS/TPS.
23. Did the Forced Switch EPS/RPS/TPS condition clear?
24. IF cable loopback
Ready to release the IF Cable Loopback?
27. Did the IF Cable Loopback condition clear?
28. Line facing circuit loopback
Ready to release the loopback?
31. Did the Line Facing Circuit Loopback condition clear?


32. Line facing PDH loopback
Ready to release the Line Facing PDH Loopback?
35. Did the Line Facing PDH Loopback condition clear?
36. Line facing SDH loopback
Ready to release the Line Facing SDH Loopback?
39. Did the Line Facing SDH Loopback condition clear?
40. Lockout switch for EPS, RPS, and TPS
Ready to release the Lockout Switch EPS/RPS/TPS?
41. Using the Craft Terminal, release the lockout switch.
43. Did the Lockout Switch EPS/RPS/TPS condition clear?
44. TXMute
Ready for the TxMute to be released?
45. Using the Craft Terminal, release the TxMute.
47. Did the TxMute condition clear?


48. Rx Main squelch
Ready for the squelch to be released?
49. Using the Craft Terminal, release the squelch.
51. Did the Rx Main squelch condition clear?
52. Rx Div squelch
55. Did the Rx Div squelch condition clear?
56. Contact the next level of technical support for assistance.
57. STOP. This procedure is complete.
1. Using the Craft Terminal, retrieve abnormal conditions.
2. Review the output. See Table 15.1 for information about abnormal conditions.
Table 15.2 — Abnormal conditions
Core facing PDH DS1 Port#[1-16] Internal Loopback Step 3

loopback MSS/DS1
Core facing SDH OC3 Port#[1-2] Internal Loopback Step 7

loopback SLOT#[3-8]

Digital core facing Direction #1.[1-6] Loopback Step 11

Core-E, MSS/CORE)
MPTACC)
P8ETH)
EASv2)
Core-E, MSS/CORE)
(EASv2. MPT-HL)
Core-E, MSS/CORE)
EASv2, P8ETH)

Forced adaptive Direction #[3-8] - Channel #1 Radio Step 15

modulation (MOD300)
Core-E, MSS/CORE)
MPTACC)
P8ETH)
EASv2)
Core-E, MSS/CORE)
EASv2, P8ETH)
Core-E, MSS/CORE)
Direction #[3-8].[5-8] - Channel #1 Radio (MPT-HLC
connected to EASv2,
P8ETH)

Forced switch EPS Main#1 Slot#1 Equipment Protection Step 19

(Core-E)
Main#1 Slot#[3,5,7] Equipment Protection
(MOD300, P2E3DS3,
P32E1DS1, SDHACC)
Main#1 Slot #[3-8] Port #[1-4] Equipment Protection
MPTACC)
Main#1 Slot #1 Port #[1,3,5] Equipment Protection
Core-E)
Main#1 MSS/CORE Port #[1,3,5] Equipment Protection
MSS/CORE)
EASv2)
Main#1 Slot #[3,5,7] Port #[5-8] Equipment Protection
EASV2, P8ETH)
Main#1 Slot #1 Equipment Protection
Core-E)
Main#1 MSS/CORE Equipment Protection
MSS/CORE)
EASv2, P8ETH)

Forced switch RPS Main#1 Slot#[3,5,7] Rx Radio Protection Step 19

(MOD300)
Main#1 Slot #1 Port #[1,3,5] Rx Radio Protection
Core-E)
Main#1 MSS/CORE Port #[1,3,5] Rx Radio Protection
MSS/CORE)
Main#1 Slot #[3-8] Port #[1-4] Rx Radio Protection
MPTACC)
EASv2)
Main#1 Slot #[3,5,7] Port #[5-8] Rx Radio Protection
EASv2, P8ETH)
Main#1 Slot #1 Rx Radio Protection
Core-E)
Main#1 MSS/CORE Rx Radio Protection
MSS/CORE)
EASv2, P8ETH)

Forced switch TPS Main#1 Slot#[3,5,7] HSB Protection Step 19

(MOD300)
Main#1 Slot #1 Port #[1,3,5] HSB Protection
Core-E)
Main#1 MSS/CORE Port #[1,3,5] HSB Protection
MSS/CORE)
Main#1 Slot #[3-8] Port #[1-4] HSB Protection
MPTACC)
EASv2)
Main#1 Slot #[3,5,7] Port #[5-8] HSB Protection
EASv2, P8ETH)
Main#1 Slot #1 HSB Protection
Core-E)
Main#1 MSS/CORE HSB Protection
MSS/CORE)
EASv2, P8ETH)
IF cable loopback Direction #[3-8] Loopback Step 24
(MOD300)

Line facing circuit Direction #1.[1-6] Loopback Step 28

Core-E, MSS/CORE)
MPTACC)
P8ETH)
EASv2)
Core-E, MSS/CORE)
EASv2, P8ETH)
Core-E, MSS/CORE)
EASv2, P8ETH)
Line facing PDH DS1 Port#[1-16] External Loopback Step 32
loopback (DS1 on MSS-1 shelf:
MSS/DS1)
DS3 Port#[1-2] External (P2E3DS3, P32E1DS1:
SLOT#[3-8])
Line facing SDH OC3 Port#[1-2] External Loopback Step 36
loopback (SDHACC: SLOT#[3-8])

Lockout switch for Spare#0 Slot#2 Equipment Protection Step 40

EPS, RPS, and TPS (Core-E)
EPS
(MOD30, P2E3DS3,
P32E1DS1, SDHACC)
Spare#0 Slot #1 Port #[2,4,6] Equipment Protection
Core-E)
Spare#0 MSS/CORE Port #[2,4,6] Equipment Protection
MSS/CORE)
Spare#0 Slot#[3-8] Port #[1-4] Equipment Protection
MPTACC)
EASv2)
Spare#0 Slot #[4,6,8] Port #[5-8] Equipment Protection
EASV2, P8ETH)
Spare#0 Slot #1 Equipment Protection
Core-E)
Spare#0 MSS/CORE Equipment Protection
MSS/CORE)
EASv2, P8ETH)

Lockout switch for Spare#0 Slot#[4,6,8] Rx Radio Protection Step 40

RPS
Spare#0 Slot #1 Port #[2,4,6] Rx Radio Protection
Core-E)
Spare#0 MSS/CORE Port #[2,4,6] Rx Radio Protection
MSS/CORE)
Spare#0 Slot#[3-8] Port #[1-4] Rx Radio Protection
MPTACC)
EASv2)
Spare#0 Slot #[4,6,8] Port #[5-8] Rx Radio Protection
MPT-HL connected to
EASV2, P8ETH
Spare#0 Slot #1 Rx Radio Protection
Core-E)
Spare#0 MSS/CORE Rx Radio Protection
MSS/CORE)
EASv2, P8ETH)

Lockout switch for Spare#0 Slot#[4,6,8] HSB Protection Step 40

TPS
Spare#0 Slot #1 Port #[2,4,6] HSB Protection
Core-E)
Spare#0 MSS/CORE Port #[2,4,6] HSB Protection
MSS/CORE)
Spare#0 Slot #[3-8] Port #[1-4] HSB Protection
MPTACC)
EASv2)
Spare#0 Slot #[4,6,8] Port #[5-8] HSB Protection
EASV2, P8ETH)
Spare#0 Slot #1 HSB Protection
Core-E)
Spare#0 MSS/CORE HSB Protection
MSS/CORE)
EASv2, P8ETH)
Rx Main squelch Direction #1.[5-6] - Radio (MPT-HLC Step 48
MSS/CORE)
P8ETH)

Rx Div squelch Direction #1.[5-6] - Radio (MPT-HLC Step 52

MSS/CORE)
P8ETH)
TXMute Direction #1.[1-6] - Channel #[0-1] Radio Step 44
Core-E, MSS/CORE)
MPTACC)
P8ETH)
EASv2
EASv2
Core-E, MSS/CORE)
EASv2, P8ETH)
Direction #1.[5-6] - Radio (MPT-HLC
MSS/CORE)
P8ETH)
Direction #[3-8] - Channel #[0-1] Radio
(ODU300)


Alarm and
abnormal
condition
clearing
procedures
3. Core facing PDH loopback

Ready to release the Core Facing PDH Loopback?
6. Did the Core Facing PDH Loopback condition clear?
7. Core facing SDH loopback
Ready to release the Core Facing SDH Loopback?
10. Did the Core Facing SDH Loopback condition clear?
11. Digital core facing loopback
Ready to release the Digital Core Facing Loopback?
14. Did the Digital Core Facing Loopback condition clear?
15. Forced adaptive modulation

Ready for the Forced Adaptive Modulation to be released?

16. Using the Craft Terminal, release the Forced Adaptive Modulation.
18. Did the Forced Adaptive Modulation condition clear?
19. Forced switch
EPS, RPS, and TPS
Ready to release the Forced Switch EPS/RPS/TPS?
20. CAUTION: Possibility of service interruption. Releasing a Forced Switch causes
21. Using the Craft Terminal, release Forced Switch EPS/RPS/TPS.
23. Did the Forced Switch EPS/RPS/TPS condition clear?
24. IF cable loopback
Ready to release the IF Cable Loopback?
27. Did the IF Cable Loopback condition clear?
28. Line facing circuit loopback
Ready to release the loopback?
31. Did the Line Facing Circuit Loopback condition clear?


32. Line facing PDH loopback
Ready to release the Line Facing PDH Loopback?
35. Did the Line Facing PDH Loopback condition clear?
36. Line facing SDH loopback
Ready to release the Line Facing SDH Loopback?
39. Did the Line Facing SDH Loopback condition clear?
40. Lockout switch for EPS, RPS, and TPS
Ready to release the Lockout Switch EPS/RPS/TPS?
41. Using the Craft Terminal, release the lockout switch.
43. Did the Lockout Switch EPS/RPS/TPS condition clear?
44. TXMute
Ready for the TxMute to be released?
45. Using the Craft Terminal, release the TxMute.
47. Did the TxMute condition clear?


48. Rx Main squelch
51. Did the Rx Main squelch condition clear?
52. Rx Div squelch
55. Did the Rx Div squelch condition clear?

16 — TAP-102 Power alarms
16.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, and MSS-1 Core.
16.2 — General
A Battery Failure alarm indicates that the A battery feed has failed or is missing, when
battery protection is available.
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-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-1 Core 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 supported voltage range of the MSS-4/MSS-8 shelf is -40.8 VDC to -57.6 VDC.
The supported voltage range of the MSS-1 shelf is -24.0 VDC to -48.0 VDC.
The EASv2 card provides power to the MPT ODU using the PFoE supported RJ45
connectors.

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.
address.
See the Alcatel-Lucent 9500 MPR-A Operation and Administration for the procedures
about how to execute the commands that are described in this procedure.
16.3 — Procedure
2. Review the output. See Table 16.1 for information about the power alarms.
Table 16.1 — Power Alarms
Probable cause Friendly name/entity Equipment type See

Battery failure r01/subrack#1 MSS-1/4/8 Step 3
Power supply failure r01/subrack#[3-8][1-2] EASv2 Step 14
r01/subrack#[3-8][1-4] MPTACC
r01/subrack#[1][1-2] MSS/Core
Secondary battery failure r01/subrack#1 MSS-1/4/8 Step 96
None of the above — — IXL-101 Alarm and
abnormal condition
clearing procedures
3. Battery failure
Verify that there is no blown fuse providing power to the A-power feed.
4. Verify the shelf power cable connections between the MSS-1/4/8 and the PDU.
5. Verify the A-power connections between the BDFB and PDU.
6. Verify the A-power BDFB breakers are in the ON position.
8. Did the Battery Failure clear?

9. Measure the voltage of the A-power feed.
10. Is the measured voltage within the supported voltage range (MSS-4/8: -40.8 VDC to -
57.6 VDC, MSS-1: -24.0 VDC to -48.0 VDC)?
11. Troubleshoot the A-power feed voltage problem.
13. Did Battery Failure condition clear?
14. Power supply failure
Inspect the power supply cable connection for radio port in alarm:
a. For EASv2, verify RJ45 connector for PFoE port 1 or 2.
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.
15. Is the power supply cable damaged or improperly connected?
16. Terminate, repair, or replace power supply cable as required.
18. Did the Power Supply Failure alarm clear?
19. Which card is Power Supply Failure alarm declared?
a. If MPTACC, go to step 20.
b. If MSS-1 CORE, go to step 44.
c. If EASv2, go to step 55.
20. 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?
21. Verify the 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.
22. Is it appropriate to proceed with MPTACC Power Supply Failure procedure?


23. Is the MPTACC in alarm in a protected system?
24. CAUTION: Possibility of service interruption. 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.
25. CAUTION: Possibility of service interruption. 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.
26. CAUTION: Possibility of service interruption. 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 appropriate maintenance
window prior to MPTACC replacement per local practices and procedures.
27. Is the card in alarm main or spare?
a. If main, go to step 28.
b. If spare, go to step 33.
28. CAUTION: Possibility of service interruption. Forced EPS/HSB/RX Radio
switching traffic causes a disruption to traffic.
29. Perform the Forced EPS Switch using the Craft Terminal.
30. Perform the Forced HSB Switch using the Craft Terminal.
31. Perform the Forced Rx Radio Switch using the Craft Terminal.
32. Go to step 36.
33. Perform Lockout EPS Switch using the Craft Terminal.
34. Perform Lockout HSB Switch using the Craft Terminal.
35. Perform Lockout Rx Radio Switch using the Craft Terminal.
36. Verify card in alarm status is Standby.
unprotected link causes loss of traffic.
38. Physically reseat card in alarm and wait for the status LED to turn steady green or
amber.
41. See DLP-114 MPTACC (MPT Access) replacement to replace MPTACC.


44. Determine the MSS-1 configuration.
a. Does the MSS-1 support one or more radio channels?
b. Are DS1 ports configured and carrying traffic?
c. Are Ethernet ports configured and carrying traffic?
45. Based on the answers to step 44, verify the appropriate maintenance window is
scheduled per local practices and procedures.
46. Is it appropriate to proceed with MSS-1 CORE Power Supply Failure procedure?
47. CAUTION: Possibility of service interruption. Power cycling an in-service MSS-1
shelf WILL cause a loss of ALL traffic associated with the MSS-1 shelf.
48. Remove both the A and B fuses supplying power to the MSS-1 shelf in alarm.
49. Wait ten seconds and install both the A and B fuses removed in step 48. Then wait for
the status LED to turn steady green.
52. See DLP-128 MSS-1 shelf replacement to replace MSS-1 shelf.
55. Determine the EASv2 configuration.
a. Does the EASv2 support more than one radio direction?
b. Are the radio directions protected or unprotected?
56. Based on the answers to step 55, verify the appropriate maintenance window is
scheduled per local practices and procedures.
57. Is it appropriate to proceed with EASv2 Power Supply Failure procedure?
58. Is the radio in alarm in a protected system?


59. CAUTION: Possibility of service interruption. Removing an in-service radio in an
link requires switching the traffic onto the protect hop.
60. CAUTION: Possibility of service interruption. 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.
61. Is the radio in alarm main or spare?
66. Go to step 70.
67. Perform Lockout EPS Switch using the Craft Terminal.
68. Perform Lockout HSB Switch using the Craft Terminal.
69. Perform Lockout Rx Radio Switch using the Craft Terminal.
70. Verify radio in alarm status is Standby.
71. Repeat steps 61 through 70 for all radios supported by the EASv2 card.
72. CAUTION: Possibility of service interruption. Removing an in-service EASv2
card WILL cause a loss of ALL unprotected radio traffic and ALL Ethernet
traffic associated with the EASv2 card.
73. Physically reseat card in alarm and wait for the status LED to turn steady green or
amber.
76. See DLP-108 MPT-HL/MPT-HLC transceiver replacement to replace EASv2.
79. Inspect the power supply cable connection at MPT ODU.
80. Is power supply cable damaged or improperly connected?


81. Terminate, repair, or replace power supply cable as required.
84. Inspect the power supply cable run between the EASv2/MPTACC/MSS-1 CORE and
MPT ODU.
85. Is the power supply cable damaged?
86. Repair or replace the power supply cable as required.
89. Which card is Power Supply Failure alarm declared?
a. If EASv2/MPTACC, go to step 90.
b. If MSS-1 CORE, go to step 108.
90. Is EASv2/MPTACC in alarm in a protected system?
91. CAUTION: Possibility of service interruption. Releasing Forced EPS/HSB/RX
Radio switch causes a disruption to traffic.
92. Release the Forced/Lockout EPS Switch using the Craft Terminal.
93. Release the Forced/Lockout HSB Switch using the Craft Terminal.
94. Release the Forced/Lockout Rx Radio Switch using the Craft Terminal.
95. Go to step 108.
96. Secondary battery failure
Verify that there is no blown fuse providing power to the B-power feed.
97. Verify the shelf power cable connections between the MSS-1/4/8 and the PDU.
98. Verify the B-power connections between the BDFB and PDU.
99. Verify that the B-power BDFB breakers are in the ON position.
101.Did the Secondary Battery Failure clear?


102.Measure the voltage of the B-power feed.
103.Is the measured voltage within the supported voltage range (-40.8 VDC to -57.6
VDC)?
104.Troubleshoot the B-power feed voltage problem.
106.Did the Secondary Battery Failure condition clear?

17 — TAP-103 Equipment alarms
17.1 — Purpose
This procedure describes how to identify and clear Equipment alarms (Replaceable Unit
Problem, Replaceable Unit Missing, Replaceable Unit Type Mismatch, Excessive
Environmental Temperature, or Unconfigured Equipment Present) on Core-E, EASv2,
FAN, MOD300, MPTACC, MPT-HC/MPT-XP/9558HC (MPT ODU), MPT-HL,
MPT-HLC, ODU300, P2E3DS3, P8ETH, P32E1DS1, or SDHACC.
17.2 — General
An Excessive Environmental Temperature alarm indicates that excessive temperature on
MPT-HL, MPT-HLC card has been detected, or MPT-HL, MPT-HLC fan unit has failed,
or is missing.
Normal operating temperature of 5° to 40° C and short term operating temperature of -5°
to 50° C for a period not to exceed 72 hours is supported.
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 an ODU300 is present on a radio
channel provisioned for a different ODU300 type.
An Unconfigured Equipment Present alarm indicates that a card/SFP is present in an

unprovisioned slot.
address.

17.3 — Procedure
2. Review the output. See Table 17.1 for information about equipment alarms.
Table 17.1 — Equipment alarms
Operation Name Equipment type See
Excessive r01/subrack#[3-8][5-8] MPT-HL, MPT-HLC Step 3

environmental connected to EASv2,
temperature P8ETH
r01/subrack#1[5-6] MPT-HL, MPT-HLC
connected to Core-E,
MSS/CORE

Table 17.1 — Equipment alarms (Continued)
Replaceable unit r01s1/board#[8] AUX Step 14

missing
r01s1/board#[1-2] Core-E
r01s1/board#[3-8] EASv2, MOD300,
MPTACC, P2E3DS3,
P8ETH, P32E1DS1,
SDHACC
r01s1b[1-2]/daughter#[5-6] SFP on Core-E
r01s1b1/daughter#[5-6] SFP on MSS/CORE
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
r01s[3-8][5-8]b1/daughter#03 RPS SFP on MPT ODU
connected to EASv2,
P8ETH
r01s1[1-6]b1/daughter#03 RPS SFP on MPT ODU
MSS/CORE


problem
r01s1/MSS/CORE MSS-1
MPTACC, P2E3DS3,
P8ETH, P32E1DS1,
SDHACC
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/CORE
r01/subrack#[3-8][5-8] MPT-HLC connected to
P8ETH
r01/subrack#1[5-6] MPT-HLC connected to
Core-E, MSS/CORE
r01s1b[1-2]/daughter#[05-06] SFP on Core-E
r01s1b[3-8]/daughter#[01-02] SFP for SDHACC

Replaceable unit r01s[3-8][1-4]b1/daughter#03 RPS SFP on MPT ODU Step 24

problem connected to MPTACC
(continued) r01s[3-8][5-8]b1/daughter#03 RPS SFP on MPT ODU
connected to EASV2
r01s1[1-6]b1/daughter#03 RPS SFP on MPT ODU
MSS/CORE
r01s1[1-6]b1/daughter#04 RPS or XPIC Module on
MPT ODU connected to
Core-E, MSS/CORE
r01/subrack#[3-8][5-8]/daughter#04 XPIC Module on
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
EASV2
r01/subrack#[3-8][5-8]/ RPS or XPIC Module on
daughter#04 MPT ODU connected to
EASV2
r01s1[1-6]b1/daughter#04 Rx Diversity Module on
MPT-HLC connected to
Core-E, MSS/CORE
r01/subrack#[3-8][5-8]/ Rx Diversity Module on
daughter#04 MPT-HLC connected to
EASv2


type mismatch
MPTACC, P2E3DS3,
P8ETH, P32E1DS1,
SDHACC
r01/subrack#1[1-6] MPT ODU connected to
Core-E, MSS/CORE
MPTACC
P8ETH
EASv2
EASv2, P8ETH
Core-E, MSS/CORE
r01/subrack#[3-8][5-8] MPT-HLC connected to
EASV2, P8ETH
r01/subrack#1[5-6] MPT-HLC connected to
Core-E, MSS/CORE
Replaceable unit r01/subrack#[3-8] ODU300 Step 178
type mismatch -
ODU300

Unconfigured r01s1/board#[8] AUX Step 188

equipment present
r01s1/board#[2] Core-E
MPTACC, P2E3DS3,
P8ETH, P32E1DS1,
SDHACC
r01s1b[3-8]/daughter#[01-02] SFP on SDHACC
None of the above — — IXL-101 Alarm
and abnormal
condition
clearing
procedures
3. Excessive environmental temperature

Verify that the MPT-HL/MPT-HLC card fan is equipped and operating properly.
4. Is the MPT-HL/MPT-HLC fan equipped and operating properly?
5. Is the traffic affected?
6. Replace the MPT-HL. See DLP-108 MPT-HL/MPT-HLC transceiver replacement to
replace MPT-HL/MPT-HLC.
8. Did the Excessive Environmental Temperature alarm clear?
9. Verify that the building temperature is within acceptable temperature range (Normal
operating temperatute is 5° to 40° C. Short term operating temperature is -5° to 50° C
for a period not to exceed 72 hours).

10. Verify the condition of MPT-HL/MPT-HLC shelf air filter and replace if air filter
condition indicates that filter replacement is required. See DLP-101 MPT-HL/
MPT-HLC transceiver air filter replacement to replace the MPT-HL/MPT-HLC air
filter.
11. Verify that no obstruction occurred that prevents proper air flow through the MPT-HL/
MPT-HLC card.
13. Did the Excessive Environmental Temperature alarm clear?
14. Replaceable unit missing
Visually inspect the indicated slot location.
15. Is the slot location empty?
16. Install the card/SFP type corresponding to slot provisioning.
18. Did the Replaceable Unit Missing alarm clear?
19. CAUTION: Possibility of service interruption. Performing the Restart NE
command may cause a disruption to traffic.
20. 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.
21. Log into the NE.
23. Did the Replaceable Unit Missing alarm clear?
24. Replaceable unit problem
Caution: Possibility of service interruption. Core-E, 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
appropriate maintenance window prior to reseating or replacing cards per local
25. What equipment type is the Replaceable Unit Problem declared against?

a. If Core-E, P2E3DS3, or P32E1DS1 go to step 68.

b. If FAN, go to step 99.
c. If MPTACC go to step 77.
d. If EASv2, MOD300, MPT ODU, ODU300, or P8ETH go to step 85.
e. If MPT-HL or MPT-HLC go to step 26.
f. If SFP, go to step 113.
g. If RPS SFP on MPT ODU go to step 139.
h. If RPS or XPIC module on MPT ODU go to step 154.
26. Verify that the MPT-HL/MPT-HLC PA switch is in the ON ‘1’ position.
27. Is the MPT-HL/MPT-HLC PA switch in the ON ‘1’ position?
28. Ready to move the MPT-HL/MPT-HLC PA switch to the ON ‘1’ position?
29. When the MPT-HL//MPT-HLC 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, go to step 199.
30. Position the MPT-HL/MPT-HLC PA switch to the ON ‘1’ position.
32. Did the Replaceable Unit Problem alarm clear?
33. Is the MPT-HL/MPT-HLC in alarm in a protected system?
34. CAUTION: Possibility of service interruption. Performing Manual EPS/HSB/Rx
35. Is the MPT-HL/MPT-HLC in alarm main or spare?
40. Go to step 47.
41. Perform the Lockout EPS Switch using the Craft Terminal.

42. Perform the Lockout HSB Switch using the Craft Terminal.
43. Perform the Lockout Rx Radio Switch using the Craft Terminal.
45. Go to step 47.
47. See DLP-108 MPT-HL/MPT-HLC transceiver replacement to replace MPT-HL/
MPT-HLC.
49. Did the Replaceable Unit Problem alarm clear?
50. Is the MPT-HL/MPT-HLC in alarm in a protected system?
51. CAUTION: Possibility of service interruption. Releasing Forced EPS/HSB/Rx
55. Is the protection scheme configured as Not Revertive?
56. NOTE: To verify the replaced MPT-HL/MPT-HLC is capable of carrying traffic, the
replaced MPT-HL/MPT-HLC must be placed in the Active state.
57. CAUTION: Possibility of service interruption. Performing Manual EPS/HSB/Rx
58. Perform the Manual EPS Switch using the Craft Terminal.
59. Perform the Manual HSB Switch using the Craft Terminal.
60. Perform the Manual Rx Radio Switch using the Craft Terminal.
61. Verify that the replaced MPT-HL/MPT-HLC status is Active.
62. Verify that the local and far end radio direction are alarm free and error-free.
63. Are the local and far end alarm free and error-free?
64. Release the Manual EPS Switch using the Craft Terminal.
65. Release the Manual HSB Switch using the Craft Terminal.

66. Release the Manual Rx Radio Switch using the Craft Terminal.
67. Go to step 199.
68. Is the card in alarm in a protected system?
69. CAUTION: Possibility of service interruption. Forced EPS switching traffic
70. Is the card in alarm main or spare?
72. Verify that the card in the alarm status is Standby.
73. Go to step 99.
76. Go to step 99.
77. 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?
d. Is the power to the radio channels provided by the MPTACC card?
78. 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.
79. Is it appropriate to proceed with the MPTACC Replaceable Unit Problem procedure?
80. Is the MPTACC in alarm in a protected system?
radio configurations, the Main MPTACC card(s) resides in slots 3, 5, and/or 7.
The spare MPTACC card(s) resides in slots 4, 6, and/or 8.


supported by a single MPTACC card. Replacing an MPTACC card in this
configuration causes a loss of traffic. Schedule appropriate maintenance window
prior to MPTACC replacement per local practices and procedures.
84. Is the card in alarm the main or spare?
85. What equipment type is the Replaceable Unit Problem declared against?
a. If MPT ODU go to step 86.
b. If MOD300, ODU300, or P8ETH, go to step 87.
86. Is the MPT ODU in alarm supported by the Core-E card?
87. Is the MPT ODU in alarm in a protected system?
88. Is the MPT ODU in alarm the main or spare?
93. Go to step 97.
95. Perform the Lockout HSB Switch using the Craft Terminal.
96. Perform the Lockout Rx Radio Switch using the Craft Terminal.
99. Physically reseat the card in alarm and wait for the status LED to turn steady green or
amber.
101.Did the Replaceable Unit Problem alarm clear?

102.What equipment type is the Replaceable Unit Problem declared against?

a. If Core-E, see DLP-103 Core switching module (Core-E) replacement to replace
Core-E.
b. If FAN, see DLP-106 MSS-4/8 shelf FAN replacement to replace FAN.
c. If MOD300, see DLP-107 MOD300 (radio modem) replacement to replace
MOD300.
d. If MPT ODU see DLP-115 MPT ODU replacement (MPT-HC, MPT-XP,
9558HC) to replace MPT ODU.
e. If ODU300, see DLP-109 ODU300 replacement to replace ODU300.
f. If P2E3DS3, see DLP-110 P2E3DS3 (2-Port DS3) replacement to replace
P2E3DS3.
g. If EASv2 or P8ETH, see DLP-105 Ethernet Access Switch replacement (EASv2
and P8ETH) to replace EASv2 or P8ETH.
h. If P32E1DS1, see DLP-111 P32E1DS1 (32-Port DS1) replacement to replace
P32E1DS1.
i. If SDHACC, see DLP-126 SDHACC (2-Port OC-3) Replacement to replace
SDHACC.
105.CAUTION: Possibility of service interruption. Releasing EPS switch may cause a
106.Release the Forced/Lockout EPS Switch using the Craft Terminal.
107.Go to step 199.
108.CAUTION: Possibility of service interruption. Releasing Forced EPS/HSB/RX
110.Release the Forced/Lockout HSB Switch using the Craft Terminal.
111.Release the Forced/Lockout Rx Radio Switch using the Craft Terminal.
112.Go to step 199.
113.Is the SFP (Ethernet/OC-3/Radio equipment) in alarm protected?
115.Is the SFP in alarm the main or spare?


116.Perform the Forced EPS Switch using the Craft Terminal.
117.Perform the Forced HSB Switch using the Craft Terminal (radio SFP only).
118.Perform the Forced Rx Radio Switch using the Craft Terminal (radio SFP only).
119.Verify that the card in the alarm status is Standby.
120.Go to step 127.
121.Perform the Lockout EPS Switch using the Craft Terminal.
122.Perform the Lockout HSB Switch using the Craft Terminal (radio SFP only).
123.Perform the Lockout Rx Radio Switch using the Craft Terminal (radio SFP only).
124.Verify that the card in the alarm status is Standby.
125.Go to step 127.
126.CAUTION: Possibility of service interruption. Removing SFP in an unprotected
system causes a loss of traffic on ALL facilities that are associated with the SFP
removed. Schedule appropriate maintenance window per local practices and
procedures.
127.Physically reseat the SFP in alarm.
b. If no, go to step See DLP-102 SFP replacement to replace SFP in alarm..
130.See DLP-102 SFP replacement to replace SFP in alarm.
133.Is the SFP protected?
136.Release the Forced/Lockout HSB Switch using the Craft Terminal (radio SFP only).
137.Release the Forced/Lockout Rx Radio Switch using the Craft Terminal (radio SFP
only).
138.Go to step 199.
139.Physically reseat the RPS cable at both ends that are associated with RPS SFP in alarm.


142.Physically reseat the RPS SFP in alarm.
145.See DLP-102 SFP replacement to replace the RPS SFP in alarm.
148.Replace the RPS cable that is associated with the RPS SFP in alarm.
151.See DLP-115 MPT ODU replacement (MPT-HC, MPT-XP, 9558HC) to replace
MPT ODU associated with RPS SFP in alarm.
154.See DLP-122 RPS/XPIC module replacement to replace RPS/XPIC module in alarm.
157.See DLP-115 MPT ODU replacement (MPT-HC, MPT-XP, 9558HC) to replace
MPT ODU associated with RPS/XPIC module in alarm.
160.Go to step 199.

161.Replaceable unit type mismatch

Is the Replaceable Unit Type Mismatch alarm declared against an SFP?
162.Visually inspect the indicated slot location.
163.Is the card in indicated slot location the correct card type?
164.Replace the installed card with card type provisioned in Core-E memory.
Core-E.
b. If FAN, see DLP-106 MSS-4/8 shelf FAN replacement to replace FAN.
c. If MOD300, see DLP-107 MOD300 (radio modem) replacement to replace
MOD300.
d. If MPTACC, see DLP-114 MPTACC (MPT Access) replacement to replace
MPTACC.
e. If MPT ODU, see DLP-115 MPT ODU replacement (MPT-HC, MPT-XP,
9558HC) to replace MPT ODU.
f. If MPT-HL/MPT-HLC, see DLP-108 MPT-HL/MPT-HLC transceiver
replacement to replace MPT-HL/MPT-HLC.
g. If P2E3DS3, see DLP-110 P2E3DS3 (2-Port DS3) replacement to replace
P2E3DS3.
h. If EASv2/P8ETH, see DLP-105 Ethernet Access Switch replacement (EASv2 and
P8ETH) to replace EASv2/P8ETH.
i. If P32E1DS1, see DLP-111 P32E1DS1 (32-Port DS1) replacement to replace
P32E1DS1.
j. If SDHACC, see DLP-126 SDHACC (2-Port OC-3) Replacement to replace
SDHACC.
166.Did the Replaceable Unit Type Mismatch alarm clear?
167.Reprovision the slot to the correct card type.
170.Using the Craft Terminal, determine the SFP type in alarm.

171.Is the SFP in alarm the correct SFP type as described in the site engineering
documentation?
172.Replace the SFP with the type corresponding to the SFP card slot provisioning. See
DLP-102 SFP replacement to replace an SFP.
175.Reprovision the SFP slot to the correct SFP type.
178.Replaceable unit type mismatch - ODU300
Verify that the radio channel provisioning corresponding to the ODU300 in alarm is
correct as described in the site engineering documentation.
179.Is the radio channel provisioning correct?
180.Verify that the equipped ODU300 supports radio channel provisioning.
181.Is the ODU300 connected to the MOD300 the correct ODU300 type?
182.Replace the ODU300 with ODU300 type supporting radio channel provisioning that is
stored in Core-E memory. See DLP-109 ODU300 replacement to replace ODU300.
185.Reprovision the radio channel as described in the site engineering documentation.
188.Unconfigured equipment present

Visually inspect the indicated slot/SFP location.

189.Is the indicated slot location equipped with a card/SFP?
190.Is the card/SFP that is equipped in the slot location expected to be there?
191.Provision the slot to the correct the card/SFP type.
193.Did the Unconfigured Equipment Present alarm clear?
194.Remove the card/SFP from the slot.
195.Install the blank filler panel or face plate into the slot that the card was removed.
197.Did the Unconfigured Equipment Present alarm clear?

18 — TAP-104 Radio alarms (MPT-HC,
MPT-HL, MPT-HLC, MPT-HLC, MPT-XP,
MOD300, ODU300, 9558HC)
18.1 — Purpose
This procedure describes how to identify and clear radio alarms on MPT-HC/MPT-XP/
9558HC (MPT ODU), MPT-HL/MPT-HLC, MOD300, and ODU300.
18.2 — General
A Bandwidth Over Flow alarm indicates that while the MPT ODU/MPT-HL/MPT-HLC
was not communicating with the Core-E 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 in alarm.

ODU300, 9558HC)
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/ODU300.
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/ODU300.
A Link Identifier Mismatch alarm indicates that the link identifier number provisioned on
MPT ODU/MPT-HL/MPT-HLC/ODU300 settings screen is different than link identifier
number provisioned at 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 coupler port.
A PPP Fail alarm indicates that TMN over PPP fail.
A Remote Defect Indication in a received Radio Direction. Alarm is reported when an RDI
is received on a given radio direction from the remote end of radio link.
address.
18.3 — Procedure
2. Review the output. See Table 18.1 for information about radio alarms.

ODU300, 9558HC)
Table 18.1 — Radio alarms
Bandwidth over Radio/Dir#1.[1-6]/ MPT ODU connected Step 3

flow Slot#1/Port#[1-6]/Ch#[0-1] to Core-E
Radio/Dir#1.[1-6]/MSS/ MPT ODU connected

CORE/Port#[1-6]/Ch#[0-1] to MSS/CORE
Radio/Dir#[3-8].[1-4]/ MPT ODU connected

Slot#[3-8]/Port#[1-4]/Ch#[0-1] to MPTACC

Slot#[3-8]/Port#[5-8]/Ch#1 to P8ETH
Radio/Dir#[3-8].1-4]/ MPT ODU connected

Slot#[3-8]/Port#[1-4]/Ch#[1] to EASv2

Slot#[3-8]/Port#[5-8]/Ch#[0-1] to EASv2
Radio/Dir#1.[5-6]/ MPT-HL connected to

Slot#1/Port#[5-6]/Ch#1 Core-E
Radio/Dir#1.[5-6]/MSS/ MPT-HL connected to

CORE/Port#[5-6]/Ch#1 MSS/CORE
Radio/Dir#[3-8].[5-8]/ MPT-HL connected to

Slot#[3-8]/Port#[5-8]/Ch#[0-1] EASv2, P8ETH
Radio/Dir#1.[5-6]/ MPT-HLC connected

Slot#1/Port#[5-6]/Ch#[0-1] to Core-E
Radio/Dir#1.[5-6]/MSS/ MPT-HLC connected


ODU300, 9558HC)
Table 18.1 — Radio alarms (Continued)
CLA Radio/Dir#1.[1-6]/ MPT ODU connected Step 7







Radio/Dir#[3-8].[5-8]/ MPT-HLC connected

Demodulator fail Radio/Dir#1.[1-6]/ MPT ODU connected Step 24






ODU300, 9558HC)
Demodulator fail Radio/Dir#1.[5-6]/ MPT-HL connected to Step 24

(continued) Slot#1/Port#[5-6]/Ch#1 Core-E





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



Slot#[3-8]/Port#[5-8]/Ch#[0-1] to P8ETH





ODU300, 9558HC)
Early warning Radio/Dir#[3-8].[5-8]/ MPT-HL connected to Step 36

indication Slot#[3-8]/Port#[5-8]/Ch#[0-1] EASv2, P8ETH
(continued)


High BER Radio/Dir#1.[1-6]/ MPT ODU connected Step 38










ODU300, 9558HC)
High BER Radio/Dir#1.[5-6]/MSS/ MPT-HLC connected Step 38

(continued) CORE/Port#[5-6]/Ch#[0-1] to MSS/CORE

Incompatible Radio/Dir#1.[1-6]/ MPT ODU connected Step 51
frequency Slot#1/Port#[1-6]/Ch#[0-1] to Core-E












ODU300, 9558HC)
Incompatible Radio/Dir#[3-8]/Ch#[0-1] MOD300 Step 51

frequency
(continued)
modulation Slot#1/Port#[1-6]/Ch#[0-1] to Core-E









protection Slot#1/Port#[1-6]/Ch#[0-1] to Core-E




ODU300, 9558HC)
Incompatible shifter Radio/Dir#1.[1-6]/ MPT ODU connected Step 84













ODU300, 9558HC)
Incompatible power Radio/Dir#1.[1-6]/ MPT ODU connected Step 94

lot#1/Port#[1-6]/Ch#[0-1] to Core-E












ODU300, 9558HC)
Link identifier AirFrame/Dir#1.[1-6]/ MPT ODU connected Step 104

mismatch Slot#1/Port#[1-6]/Ch#1, to Core-E
Slot#1/Port#[1-6]
AirFrame/Dir#1.[1-6]/MSS/ MPT ODU connected
CORE/Port#[1-6]/Ch#1, to MSS/CORE
AirFrame/Dir#1.[1-6]/MSS/
CORE/Port#[1-6]
AirFrame/Dir#[3-8].[1-4]/ MPT ODU connected
Slot#[3-8]/Port#[1-4]/Ch#1, to MPTACC
Slot#[3-8]/Port#[1-4]
Slot#[3-8]/Port#[5-8]/Ch#1 to EASv2, P8ETH
Slot#[3-8]/Port#[5-8]
Slot#[3-8]/Port#[1-4]/Ch#1 to EASv2
AirFrame/Dir#1.[5-6]/ MPT-HL connected to

AirFrame/Dir#1.[5-6]/MSS/ MPT-HL connected to

AirFrame/Dir#[3-8].[5-8]/ MPT-HL connected to

Slot#[3-8]/Port#[5-8]/Ch#1, EASv2, P8ETH
Slot#[3-8]/Port#[5-8]
AirFrame/Dir#1.[5-6]/ MPT-HLC connected
Slot#1/Port#[5-6]/Ch#1, to Core-E
Slot#1/Port#[5-6]

ODU300, 9558HC)
Link identifier AirFrame/Dir#1.[5-6]/MSS/ MPT-HLC connected Step 104

mismatch CORE/Port#[5-6]/Ch#1, to MSS/CORE
(continued)
irFrame/Dir#1.[5-6]/MSS/
CORE/Port#[5-6]
AirFrame/Dir#[3-8].[5-8]/ MPT-HLC connected
Slot#[3-8]/Port#[5-8]/Ch#1, to EASv2, P8ETH
Slot#[3-8]/Port#[5-8]
AirFrame/Dir#[3-8]/Ch#1, MOD300
AirFrame/Dir#[3-8]
Loss of protection Radio/Dir#[3-8]/Ch#1 MOD300 Step 111
Radio/Dir#1.[1-6]/ MPT ODU connected
Slot#1/Port#[1-6]/Ch#1 to Core-E

CORE/Port#[1-6]/Ch#1 to MSS/CORE

Slot#[3-8]/Port#[1-4]/Ch#1 to MPTACC





ODU300, 9558HC)
Loss of signal r01s1[1-6]b1/daughter#03 RPS SFP on Step 119

MPT ODU
MSS/CORE
r01s1[3-8][1-4]b1/ daughter#03 MPT ODU connected
to MPTACC
MAU/subrack[#3-8].[5-8] Port#n MPT-HL connected to
EASv2, P8ETH
PPP fail PPP-IP/RF#1[1-6] MPT ODU connected Step 125
to Core-E, MSS/CORE
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/CORE
PPP-IP/RF#[3-8][5-8] MPT-HLC connected
to EASv2, P8ETH
PPP-IP/RF#1[5-6] MPT-HLC connected
to Core-E, MSS/CORE
PPP-IP/RF#[3-8] MOD300
Remote defect Radio/Dir#1.[1-6]/ MPT ODU connected Step 140
indication Slot#1/Port#[1-6]/Ch#[0-1] to Core-E




ODU300, 9558HC)
Remote defect Radio/Dir#[3-8].1-4]/ MPT ODU connected Step 140

indication Slot#[3-8]/Port#[1-4]/Ch#1 to EASv2
(continued)






and abnormal
condition clearing
procedures
3. 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.
4. 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.
5. Retrieve the alarms Using the Alarm Monitor.
6. Did the Bandwidth Over Flow alarm clear?

ODU300, 9558HC)

7. CLA
Attempt to Clear CLA alarm using the manual switch command?
8. CAUTION: Possibility of service interruption. Performing Clear CLA command
on MPT ODU, MPT-HL, MPT-HLC, or ODU300 will cause a loss of traffic on
ALL facilities associated with the MPT ODU, MPT-HL, MPT-HLC, or ODU300
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 appropriate maintenance window per local practices and
procedures.
9. Using the Craft Terminal, on the Protection Schemes tab for the local MPT ODU/
MPT-HL/MPT-HLC/ODU300, select HSB Protection for the channel declaring CLA
alarm.
10. On the Commands tab, from the New Value drop down, choose Clear CLA.
11. Click on the Apply button. The Switch confirmation window appears.
12. Click on the OK button.
13. Are both receivers at the far end in alarm and traffic affected?
14. Wait two minutes for the CLA alarm to be declared against the MPT ODU, MPT-HL,
MPT-HLC, or ODU300.
16. Is the CLA alarm declared against the MPT ODU, MPT-HL, MPT-HLC, or ODU300?
17. Replace the MPT ODU, MPT-HL, MPT-HLC, or ODU300 CLA declared against.
a. See DLP-115 MPT ODU replacement (MPT-HC, MPT-XP, 9558HC) to replace
MPT ODU.
b. See DLP-108 MPT-HL/MPT-HLC transceiver replacement to replace MPT-HL or
MPT-HLC,.
c. See DLP-107 MOD300 (radio modem) replacement to replace MOD300.

ODU300, 9558HC)
18. CAUTION: Possibility of service interruption. Performing Clear CLA command

on MPT ODU, MPT-HL, MPT-HLC, or ODU300 will cause a loss of traffic on
ALL facilities associated with the MPT ODU, MPT-HL, MPT-HLC, or ODU300
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 appropriate maintenance window per local practices and procedures.
19. Perform the Clear CLA command.
20. Are both receivers at the far end in alarm and traffic affected?
21. Wait two minutes for the CLA alarm to be declared against the MPT ODU, MPT-HL,
MPT-HLC, or ODU300.
23. Is the CLA alarm declared against the MPT ODU, MPT-HL, MPT-HLC, or ODU300?
24. Demodulator fail
Verify that there are no weather-related conditions.
25. Do weather-related conditions exist?
a. If yes, wait for the weather to clear and recheck alarms. Go to step 145.
26. Verify that the RF path is clear.
27. Is the RF path clear?
28. Verify that the RSL is above RX threshold.
29. Is the RSL above the RX threshold?
30. Check the upstream transmitter output power and troubleshoot accordingly.
32. Did the Demodulator Fail alarm clear?
33. Replace the MPT ODU, MPT-HL, MPT-HLC, or MOD300 Demodulator Fail declared
against.

ODU300, 9558HC)
a. See DLP-115 MPT ODU replacement (MPT-HC, MPT-XP, 9558HC) to replace

MPT ODU.
b. See DLP-108 MPT-HL/MPT-HLC transceiver replacement to replace MPT-HL,
MPT-HLC.
c. See DLP-107 MOD300 (radio modem) replacement to replace MOD300.
35. Did the Demodulator Fail alarm clear?
36. Early warning indication
No action is required at this time. Monitor the receive signal for increased degrading.
37. Go to step 145.
38. High BER
Verify that there are no weather-related conditions.
39. Do weather-related conditions exist?
a. If yes, wait for the weather to clear and recheck the alarms. Go to step 145.
42. Verify that the RSL is above the RX threshold.
46. Did the High BER alarm clear?
47. Verify that the antenna is aligned.
48. Is the antenna aligned?
b. If no, align the antenna. See Alcatel-Lucent 9500 MPR-A Turn-up, Antenna
Polarization Verification (DLP-105) Antenna Feedhorn Verification - XPD
Procedure.

ODU300, 9558HC)
50. Did the High BER alarm clear?

51. Incompatible frequency
Using the Craft Terminal, retrieve the provisioned frequency value and supported
frequency of the MPT ODU, MPT-HL, MPT-HLC, or ODU300.
52. Verify the required frequency of the microwave link.
53. Is the required microwave link frequency supported by the MPT ODU, MPT-HL,
MPT-HLC, or ODU300?
54. Reprovision the frequency of the MPT ODU, MPT-HL, MPT-HLC, or ODU300 to the
required frequency of the microwave link.
56. Did the Incompatible Frequency alarm clear?
57. CAUTION: Possibility of service interruption. Replacing the MPT ODU,
MPT-HL, MPT-HLC, or ODU300 in an unprotected facility causes a loss of
traffic on ALL facilities that are associated with the MPT ODU, MPT-HL,
MPT-HLC, or ODU300 being replaced. Schedule appropriate maintenance
58. Replace the MPT ODU, MPT-HL, MPT-HLC, or ODU300 with the version that
supports the required frequency of the microwave link.
a. For MPT ODU replacement, see DLP-115 MPT ODU replacement (MPT-HC,
MPT-XP, 9558HC).
b. For MPT-HL, MPT-HLC replacement, see DLP-108 MPT-HL/MPT-HLC
transceiver replacement.
c. For ODU300 replacement, see DLP-109 ODU300 replacement.
60. Did the Incompatible Frequency alarm clear?
61. Incompatible modulation
Using the Craft Terminal, retrieve the provisioned modulation value and supported
modulation of the MPT ODU/MPT-HLC.
62. Verify the required modulation of the microwave link.
63. Is the required microwave link modulation supported by the MPT ODU/MPT-HLC?

ODU300, 9558HC)

64. Reprovision the modulation of the MPT ODU/MPT-HLC to the required modulation
of the microwave link.
66. Did the Incompatible Modulation alarm clear?
67. CAUTION: Possibility of service interruption. Replacing the MPT ODU or
MPT-HLC in an unprotected facility causes a loss of traffic on ALL facilities that
are associated with the MPT ODU or MPT-HLC being replaced. Schedule
appropriate maintenance window per local practices and procedures.
68. Replace the MPT ODU/MPT-HLC with the version that supports the required
modulation of the microwave link.
For MPT ODU replacement, see DLP-115 MPT ODU replacement (MPT-HC,
MPT-XP, 9558HC).
For MPT-HLC replacement, see DLP-108 MPT-HL/MPT-HLC transceiver
replacement.
70. Did the Incompatible Modulation alarm clear?
71. Incompatible protection
Visually inspect the main and spare MPT ODU for missing the RPS/XPIC module.
72. Is the RPS/XPIC module missing?
73. See DLP-122 RPS/XPIC module replacement to install the appropriate RPS/XPIC
module.
75. Did the Incompatible Protection alarm clear?
76. Determine the required RPS/XPIC module type.
77. Are both MPT ODUs equipped with the correct RPS/XPIC module?

ODU300, 9558HC)
78. See DLP-122 RPS/XPIC module replacement to replace the incorrect RPS/XPIC
module.
81. See DLP-122 RPS/XPIC module replacement to replace the RPS/XPIC module in
alarm.
84. Incompatible shifter
Using the Craft Terminal, retrieve the provisioned shifter value and supported shifter
levels of the MPT ODU, MPT-HL, MPT-HLC, or ODU300.
85. Verify the required shifter value of the microwave link.
86. Is the required microwave link shifter level supported by the MPT ODU, MPT-HL,
MPT-HLC, or ODU300?
87. Reprovision the shifter value of the MPT ODU/MPT-HL/MPT-HLC/ODU300 to the
required shifter value of the microwave link.
89. Did the Incompatible Shifter alarm clear?
90. CAUTION: Possibility of service interruption. Replacing the MPT ODU/
MPT-HL/ODU300 in an unprotected facility causes a loss of traffic on ALL
facilities that are associated with the MPT ODU/MPT-HL/MPT-HLC/ODU300
and procedures.
91. Replace the MPT ODU/MPT-HL/MPT-HLC/ODU30 with version that supports the
required shifter value of the microwave link.
MPT-XP, 9558HC).
b. For MPT-HL/MPT-HLC replacement, see DLP-108 MPT-HL/MPT-HLC

ODU300, 9558HC)
93. Did the Incompatible Shifter alarm clear?

94. Incompatible power
Incompatible TX power
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/ODU300.
95. Verify the required transmit power level of the microwave link.
96. 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/ODU300?
97. Reprovision the RTPC/ATPC Tx power levels and/or ATPC Rx power threshold level
of the MPT ODU/MPT-HL/MPT-HLC/ODU300 to the required transmit power level
of the microwave link.
99. Did the Incompatible TX Power alarm clear?
100.CAUTION: Possibility of service interruption. Replacing the MPT ODU/
MPT-HL/ MPT-HLC/ODU300 in an unprotected facility causes a loss of traffic on
ALL facilities that are associated with the MPT ODU/MPT-HL/MPT-HLC/
ODU300 being replaced. Schedule appropriate maintenance window per local
101.Replace the MPT ODU/MPT-HL/MPT-HLC/ODU300 with the version that supports
the required transmit power level of the microwave link.
MPT-XP, 9558HC).
b. For MPT-HL/MPT-HLC replacement, see DLP-108 MPT-HL/MPT-HLC
103.Did the Incompatible TX Power alarm clear?
104.Link identifier mismatch

ODU300, 9558HC)
Note: Link Identifier Mismatch alarm failure signatures are different for MPT ODU/
MPT-HL/ MPT-HLC versus ODU300. For MPT ODU/MPT-HL/MPT-HLC Link Identifier
Mismatch alarm is declared and all link traffic is blocked. For ODU300 Link Identifier
Mismatch alarm is declared but all link traffic is passed downstream.
105.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/ODU300.
106.Verify the required Link Identifier value of the microwave hop.
107.Determine which Link Identifier values are incorrect.
108.Reprovision the Link Identifier values according to the results of step 107.
110.Did the Link Identifier Mismatch alarm clear?
111.Loss of protection
Retrieve the alarms for the local end of the radio direction using the Alarm Monitor.
112.Determine all of the radio alarms that are declared against the radio direction declaring
the Loss Of Protection and troubleshoot accordingly.
114.Did the Loss Of Protection alarm clear?
115.Retrieve the alarms for the far end of the radio direction using the Alarm Monitor.
116.Determine all of the radio alarms that are declared against the radio direction declaring
the Loss Of Protection and troubleshoot accordingly.
118.Did the Loss Of Protection alarm clear?
119.Loss of signal
Verify that the Core-E/EASv2/MPTACC/P8ETH card Ethernet port is operating
normally.

ODU300, 9558HC)
122.Verify the link cabling between the Core-E/EASv2/MPTACC/P8ETH card or MSS-1

shelf MSS/CORE Ethernet port and the MPT ODU/MPT-HL.
125.PPP fail
Retrieve the alarms using the Alarm Monitor, verify that no other radio path alarms
(such as Demodulator Fail) exist, and troubleshoot accordingly.
126.Did other radio path alarms exist and were cleared?
128.Did the PPP Fail alarm clear?
129.Check the provisioning of the far end radio card that is associated with card in alarm,
and verify that the PPP RF is enabled.
130.Is the far end radio card PPP RF disabled?
131.Enable the PPP RF at far end radio card.
134.Verify that the Link Identifiers match at the local and far end radio cards.
135.Do the local and far end Link Identifiers match?
136.Determine which Link Identifier is correct.
137.Reprovision the incorrect Link Identifier.
140.Remote defect indication

ODU300, 9558HC)
Retrieve the alarms for the far end of the radio direction using the Alarm Monitor.
141.Determine all of the radio alarms that are declared against the radio direction
associated with the radio direction declaring the Remote Defect Indication (RDI) and
143.Did the RDI alarm clear?

19 — TAP-105 Ethernet alarms (Core-E,
EASv2, MPTACC, P8ETH, MSS-1 Shelf Core)
19.1 — Purpose
This procedure describes how to identify and clear Loss Of Signal on Ethernet ports on the
Core-E/EASv2/ MPTACC/P8ETH/MSS-1 shelf MSS/CORE.
19.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.
address.
19.3 — Procedure
2. Review the output. See Table 19.1 for information about the Ethernet alarms.
Table 19.1 — Ethernet alarms

19 — TAP-105 Ethernet alarms (Core-E, EASv2, MPTACC, P8ETH, MSS-1 Shelf Core)
Table 19.1 — Ethernet alarms (Continued)
Loss of signal TMNEthernet/MngtPort Core-E Step 3

TMNEthernet/MngtPort#4 Core-E
MAU/Slot#[1-2]/Port#[1-6] Core-E
MAU/Slot#1/Port#[1-6] MSS/CORE
MAU/Slot#[3-8]/Port#[1-4] MPTACC
MAU/Slot#[3-8]/Port#[1-8] EASv2, P8ETH
Bandwidth degrade for ERP[1-2]#1-2] Core-E Step 10
protection switch
Alarm and
abnormal
condition
clearing
procedures
3. Loss of signal
Verify that the link partner is operating normally.
5. Did the Loss Of Signal alarm clear?
6. Verify the link partner cabling between the Core-E/EASv2/MPTACC/P8ETH card or
MSS-1 shelf Core and the link partner.
10. Bandwidth degrade for protection switch
Retrieve the alarms for the radio direction on one node of the Ethernet Ring reporting
the Bandwidth degrade using the Alarm Monitor.
11. Determine all of the radio alarms that are declared against the radio direction and
13. Did the Bandwidth degrade for protection switch alarm clear?


14. Have all nodes in the Ethernet Ring been verified?
b. If no, repeat steps 10 to 13 for the other nodes in the Ethernet Ring.


20 — TAP-106 License/software mismatch
20.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-E,
MPT-HC/MPT-XP/9558HC (MPT ODU), MPT-HL, MPT-HLC, ODU300, or MSS-1
Shelf Core.
20.2 — General
A Provisioning Mismatch alarm is declared against a Core-E indicates that has an incorrect
flash card installed on the Core-E.
A Standby Version Mismatch alarm indicates that the software version on MPT ODU/
MPT-HL/MPT-HLC does not match the software version on the Core-E.
A Version Mismatch alarm declared against a Core-E indicates that an incorrect Core-E
card is installed in the MSS-4 or MSS-8 slot or the software license string is not loaded on
the Core-E card.
A Version Mismatch alarm declared against the MPT ODU/MPT-HL/MPT-HLC/ODU300

indicates that software version on the MPT ODU/MPT-HL/MPT-HLC/ODU300 does not
match the software version on the Core-E.
address.
20.3 — Procedure

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

Provisioning mismatch r01s1/board#[1-2] Core-E Step 3
r01s1/MSS/CORE MSS/CORE
Standby version r01/subrack#1[1-6] MPT ODU connected Step 6
mismatch to Core-E, MSS/CORE
r01/subrack#[3-8][1-4] MPT ODU connected
to MPTACC
to P8ETH
to EASv2
Core-E, MSS/CORE
EASv2, P8ETH
r01/subrack#1[5-6] MPT-HLC connected
to Core-E, MSS/CORE
r01/subrack#[3-8][5-8] MPT-HLC connected
to EASv2, P8ETH

Table 20.1 — License/software mismatch alarms (Continued)
Version mismatch r01s1/board#[1-2] Core-E Step 12

r01s1/MSS/CORE Core on MSS-1 shelf Step 22
r01/subrack#1[1-6] MPT ODU connected Step 25
to Core-E, MSS/CORE
to EASv2
to MPTACC
to P8ETH
Core-E, MSS/CORE
P8ETH
to EASv2, P8ETH
to Core-E, MSS/CORE
and abnormal
condition
clearing
procedures
3. Provisioning mismatch
Replace the Core-E flash card with the correct flash card for the license. See DLP-104
Core switching module (Core-E) flash card replacement to replace the Core-E flash
card.
5. Did the Provisioning Mismatch alarm clear?
6. Standby version mismatch
Retrieve the alarms using the Alarm Monitor.

7. Verify that the Firmware Download On Going is declared against the MPT ODU/
MPT-HL/MPT-HLC.
8. Is the Firmware Download On Going declared against the MPT ODU/MPT-HL/
MPT-HLC?
9. A Firmware Download On Going alarm indicates that the MSS/Core-E is downloading
the correct software to the MPT ODU/MPT-HL/MPT-HLC. Wait at least 30 minutes
for the downloading process to complete.
11. Did the Standby Version Mismatch alarm clear?
12. Version mismatch
Verify the Core-E card type is installed in the slot declaring Version Mismatch alarm.
13. Is the Core-E card type Core-E?
14. Replace the Core-B card with the Core-E card. See DLP-103 Core switching module
(Core-E) replacement to replace the Core-E card.
16. Did the Version Mismatch alarm clear?
17. Verify the license string that is installed on the NE.
18. Is the license string correct?
19. Replace the Core-E card. See DLP-103 Core switching module (Core-E) replacement
to replace the Core-E card.
21. Did the Version Mismatch alarm clear?
23. Verify the license string that is installed on the NE.

24. Is the license string correct?

26. Verify that a Firmware Download On Going alarm is declared against the MPT ODU/
MPT-HL/MPT-HLC/ODU300.
27. Is the Firmware Download On Going declared against the MPT ODU/MPT-HL/
MPT-HLC/ ODU300?
28. A Firmware Download On Going alarm indicates the MSS/Core-E is downloading the
correct software to the MPT ODU/MPT-HL/MPT-HLC/ODU300. Wait at least 30
minutes for the downloading process to complete.
30. Did the Version Mismatch, Standby Version Mismatch alarm clear?


21 — TAP-107 Internal loss of
communications
21.1 — Purpose
This procedure describes how to identify and clear Dialog Failure and Internal
Communication Problem condition on the MPT-HC/MPT-XP/9558HC (MPT ODU),
MPT-HL, MPT-HLC, or ODU300.
21.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

21 — TAP-107 Internal loss of communications
An Internal Communication Problem condition indicates that a loss of communications

with the MPT ODU/MPT-HL/MPT-HLC/ODU300.
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.
address.
21.3 — Procedure
2. Review the output. See Table 21.1 for information about internal communication
problem alarms.
Table 21.1 — Internal communication problem alarms

Dialog failure r01/subrack#1[1-6] MPT ODU connected Step 3
to Core-E, MSS/CORE
to EASv2, MPTACC
r01/subrack#[3-8][[5-8] MPT ODU connected
to EASv2, P8ETH
r01/subrack#[3-8][5-8] MPT-HL, MPT-HLC
connected to P8ETH
MSS/CORE

Table 21.1 — Internal communication problem alarms (Continued)
Internal r01/subrack#1[1-6] MPT ODU connected Step 88

communication to Core-E, MSS/CORE
problem
to EASv2, MPTACC
to EASv2, P8ETH
r01/subrack#[3-8][5-8] MPT-HL, MPT-HLC
connected to P8ETH
MSS/CORE
and abnormal
condition
clearing
procedures
3. Dialog failure
Is the traffic affected?
4. Has the appropriate time-out period expired?
b. If no, wait for the appropriate time-out period to expire before proceeding to step 5.
6. Did the Dialog Failure alarm clear?
7. Is an Internal Communication Problem alarm declared?
a. If yes, go to step 88 to clear Internal Communication Problem.
8. CAUTION: Possibility of service interruption. 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 appropriate maintenance

9. Reseat the MPTACC card that is associated with the MPT ODU in alarm.
10. Wait for the status LED to turn steady green or amber.
13. Verify radio port provisioning against site documentation.
14. Is the radio port provisioned per site documentation?
15. Verify radio port fiber cabling per site documentation.
16. Is the radio port fiber cabling correct and connected to the correct MPT type?
17. Correct MPT fiber cable connections per site documentation.
20. Reprovision the radio port per site documentation.
24. Is a Replaceable Unit Problem alarm declared against the MPT ODU/MPT-HL/
MPT-HLC in the protection-pair?
a. If yes, see IXL-101 Alarm and abnormal condition clearing procedures to clear the
Replaceable Unit Problem.
25. Verify that power is properly supplied to the MPT ODU/MPT-HL/MPT-HLC in alarm.
Correct if required.
26. Was a power problem corrected?


29. Is the MPT ODU/MPT-HL/MPT-HLC in a protected system?
30. CAUTION: Possibility of service interruption. Forced EPS and HSB switching
traffic causes a disruption to traffic.
31. Is the MPT ODU/MPT-HL/MPT-HLC in alarm the main or spare?
32. Perform a Forced EPS Switch using the Craft Terminal.
33. Perform a Forced HSB Switch using the Craft Terminal.
34. Perform a Forced Rx Radio Switch using the Craft Terminal.
35. Go to step 39.
36. Perform a Lockout EPS Switch using the Craft Terminal.
37. Perform a Lockout HSB Switch using the Craft Terminal.
38. Perform a Lockout Rx Radio Switch using the Craft Terminal.
39. CAUTION: Possibility of service interruption. Unseating and reseating the
communication link between the MPT ODU/MPT-HL/MPT-HLC and the
Core-E/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 appropriate maintenance window per local practices and
procedures.
40. Reseat the RJ45/SFP at the Core-E/EASv2/MPTACC/P8ETH/MSS-1 shelf Core that
is associated with the MPT ODU/MPT-HL/MPT-HLC in alarm.
41. Reseat the SFP at the MPT-HL/MPT-HLC in alarm.
44. Which card type is declaring Dialog Failure?
a. If MPT ODU, go to step 45.
b. If MPT-HL/MPT-HLC, go to step 70.
45. Is the MPT ODU in alarm supported by the Core-E/P8ETH card or MSS-1 shelf Core?
46. Is there a second radio channel supported by the MPTACC associated with the
MPT ODU in alarm?


47. Is the second radio channel error-free and alarm free?
48. CAUTION: Possibility of service interruption. 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 appropriate
49. Power cycle the MPT ODU.
a. If powered using PFoE/QMA through the MPTACC, EASv2, 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.
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.
52. CAUTION: Possibility of service interruption. Physically replacing an MPT ODU
associated with the MPT ODU being replaced. Schedule appropriate maintenance
53. Replace the MPT ODU in alarm. See DLP-115 MPT ODU replacement (MPT-HC,
MPT-XP, 9558HC) to replace MPT ODU.

56. CAUTION: Possibility of service interruption. Physically removing an MPTACC/

P8ETH/EASv2/Core-E in an unprotected facility causes a loss of traffic on ALL
facilities that are associated with the MPTACC/P8ETH/EASv2/Core-E being
removed. Schedule appropriate maintenance window per local practices and
procedures.
57. Reseat the MPTACC/P8ETH/EASv2/Core-E card that is associated with the
MPT ODU in alarm.
61. CAUTION: Possibility of service interruption. Physically replacing an MPTACC/
P8ETH/EASv2/Core-E/MSS-1 MSS/CORE in an unprotected facility causes a
loss of traffic on ALL facilities that are associated with the MPTACC/P8ETH/
EASv2/Core-E/MSS-1 being replaced. Schedule appropriate maintenance
62. Which card is associated with the MPT ODU in alarm?
a. If MPTACC, see DLP-114 MPTACC (MPT Access) replacement to replace
MPTACC.
b. If EASv2 or P8ETH, see DLP-105 Ethernet Access Switch replacement (EASv2
c. If Core-E, see DLP-103 Core switching module (Core-E) replacement to replace
Core-E.
d. If MSS-1 shelf, see DLP-128 MSS-1 shelf replacement to replace MSS-1 shelf.
66. CAUTION: Possibility of service interruption. 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. Schedule appropriate maintenance window
per local practices and procedures.

70. CAUTION: Possibility of service interruption. Reseating an MPT-HL/MPT-HLC

associated with the MPT-HL/MPT-HLC reseat. Schedule appropriate
71. Position the MPT-HL/MPT-HLC PA switch to the OFF ‘0’ position.
72. Remove the fuse in the PDU that is suppling battery power to the MPT-HL/MPT-HLC.
73. Install the fuse in the PDU that is suppling battery power to the MPT-HL/MPT-HLC.
74. Position the MPT-HL/MPT-HLC PA switch to the ON ‘1’ position.
78. CAUTION: Possibility of service interruption. Replacing an MPT-HL/MPT-HLC
associated with the MPT-HL/MPT-HLC being replaced. Schedule appropriate
79. Replace the card in alarm. See DLP-108 MPT-HL/MPT-HLC transceiver replacement
to replace the MPT-HL/MPT-HLC.
83. Is the MPT ODU/MPT-HL/MPT-HLC in a protected system?
87. Go to step 174.
88. Internal communication problem
Is traffic affected?
89. Has the Internal Communication Problem alarm been active for more than five
minutes?

b. If no, wait five minutes, then go to step 90.

91. Did the Internal Communication Problem alarm clear?
92. Verify radio port provisioning against site documentation.
93. Is the radio port provisioned per site documentation?
94. Verify radio port fiber cabling per site documentation.
95. Is the radio port fiber cabling correct and connected to the correct MPT type?
96. Correct MPT fiber cable connections per site documentation.
98. Did the Internal Communication Problem alarm clear?
99. Reprovision the radio port per site documentation.
101.Did the Internal Communication Problem alarm clear?
102.Is the radio facility protected?
103.CAUTION: Possibility of service interruption. Forced switching traffic causes a
104.Is the MPT ODU/MPT-HL/MPT-HLC/ODU300 in alarm main or spare?
105.Perform a Forced EPS Switch using the Craft Terminal.
106.Perform a Forced HSB Switch using the Craft Terminal.
107.Perform a Forced Rx Radio Switch using the Craft Terminal.
108.Go to step 112.
109.Perform a Lockout EPS Switch using the Craft Terminal.

110.Perform a Lockout HSB Switch using the Craft Terminal.

111.Perform a Lockout Rx Radio Switch using the Craft Terminal.
112.Which card is in alarm?
a. If ODU300, go to step 113.
b. If MPT ODU, go to step 125.
c. If MPT-HL/MPT-HLC, go to step 150.
113.CAUTION: Possibility of service interruption. Physically removing an MOD300
associated with the MOD300 being removed. Schedule appropriate maintenance
114.Physically reseat the MOD300 that is associated with the ODU300 in alarm. Do not
remove the IF cable while reseating the MOD300 card.
116.Did Internal communication Problem alarm clear?
117.Physically replacing an MOD300 in an unprotected facility causes a loss of traffic
on ALL facilities that are associated with the MOD300 being replaced. Schedule
118.Replace the MOD300 that is associated with the ODU300. See DLP-107 MOD300
(radio modem) replacement to replace the MOD300.
120.Did the Internal communication Problem alarm clear?
121.CAUTION: Possibility of service interruption. Physically replacing an ODU in an
unprotected facility causes a loss of traffic on ALL facilities that are associated
with the ODU being replaced. Schedule appropriate maintenance window per
local practices and procedures.
122.Replace the ODU300 in alarm. See DLP-109 ODU300 replacement to replace the
ODU300.
124.Did the Internal communication Problem alarm clear?
125.Is MPT ODU in alarm supported by the Core-E/EASv2/P8ETH card or MSS-1 shelf
Core?

126.Is there a second radio channel supported by the MPTACC associated with the
MPT ODU in alarm?
127.Is the second radio channel error-free and alarm free?
128.CAUTION: Possibility of service interruption. Physically removing power to an
129.Power cycle the MPT ODU.
a. If powered through the EASv2, MPTACC 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/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.
131.Did Internal Communication Problem alarm clear?
132.CAUTION: Possibility of service interruption. Physically replacing an
133.Replace the MPT ODU in alarm. See DLP-115 MPT ODU replacement (MPT-HC,

136.CAUTION: Possibility of service interruption. Physically reseating an MPTACC

associated with the MPTACC reseat. Schedule appropriate maintenance window
137.Reseat the MPTACC card that is associated with the MPT ODU in alarm.
138.Wait for the status LED to turn steady green or amber.
a. If yes, go to step 168
141.CAUTION: Possibility of service interruption. Physically replacing an MPTACC
associated with the MPTACC being replaced. Schedule appropriate maintenance
142.Replace the MPTACC that is associated with MPT ODU in alarm. See DLP-114
MPTACC (MPT Access) replacement to replace the MPTACC.
143.Wait for the status LED to turn steady green or amber.
146.CAUTION: Possibility of service interruption. Physically replacing an
147.Replace the MPT ODU in alarm. See DLP-115 MPT ODU replacement (MPT-HC,
150.CAUTION: Possibility of service interruption. Unseating and reseating the
communication link between the MPT-HL/MPT-HLC and the P8ETH, Core-E,
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. Schedule
151.Unseat and reseat the communication link between the MPT-HL/MPT-HL and
P8ETH, Core-E, EASv2, or MSS-1 Shelf.


154.CAUTION: Possibility of service interruption. Replacing the communication link
between the MPT-HL/MPT-HLC 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. Schedule appropriate maintenance
155.Replace the communication link between the MPT-HL/MPT-HLC and P8ETH,
Core-E, EASv2, or MSS-1 Shelf.
158.CAUTION: Possibility of service interruption. Reseating an MPT-HL/MPT-HLC
associated with the MPT-HL/MPT-HLC reseat. Schedule appropriate
159.Position the MPT-HL/MPT-HLC PA switch to the OFF ‘0’ position.
160.Remove the fuse in the PDU suppling battery power to the MPT-HL/MPT-HLC.
161.Install the fuse in the PDU suppling battery power to the MPT-HL/MPT-HLC.
162.Position the MPT-HL/MPT-HLC PA switch to the ON ‘1’ position.
164.CAUTION: Possibility of service interruption. 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 being replaced. Schedule
165.Replace the MPT-HL/MPT-HLC in alarm. See DLP-108 MPT-HL/MPT-HLC
transceiver replacement to replace the MPT-HL/MPT-HLC.
168.Releasing Forced/Lockout switch may cause a disruption to traffic.
170.Release the Forced/Lockout HSB Switch using the Craft Terminal.
171.Release the Forced/Lockout Rx Radio Switch using the Craft Terminal.
172.Go to step 174.



22 — TAP-108 Threshold crossing alarms
(MOD300, MPT-HC, MPT-HL, MPT-HLC,
MPT-XP, 9558HC, P32E1DS1, MSS-1 shelf
P32E1DS1)
22.1 — Purpose
This procedure describes how to identify Threshold Crossing Alarms (TCA) Threshold
Crossed or Unavailable Time on the MPT-HC/MPT-XP/9558HC (MPT ODU), MPT-HL,
MPT-HLC, MOD300, or P32E1DS1 cards or MSS-1 shelf DS1.
22.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/MOD300/P32E1DS1/DS1 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/MOD300/P32E1DS1/DS1 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.

22 — TAP-108 Threshold crossing alarms (MOD300, MPT-HC, MPT-HL, MPT-HLC, MPT-XP,
9558HC, P32E1DS1, MSS-1 shelf P32E1DS1)
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/

MOD300/P32E1DS1/DS1 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/
MOD300/P32E1DS1/DS1 on MSS-1 shelf.
address.
22.3 — Procedure
2. Review the output. See Table 22.1 for information about TCA alarms.

Table 22.1 — Threshold crossing alarms
Threshold crossed Hop/Dir#1[1-6]/Slot#1/ MPT ODU connected to Step 3

Port#[1-6]/Ch#[0-1]-PM15min Core-E
Port#[1-6]/Ch#[0-1]-PM1day
Hop/Dir#1[1-6]/MSS/CORE/ MPT ODU connected to
Port#[1-6]/Ch#[0-1]-PM15min MSS/CORE
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
Link/Dir#[3-8][1-4]-PM1day
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

Table 22.1 — Threshold crossing alarms (Continued)
Threshold crossed Hop/Dir#[3-8][1-4]/Slot#[3-8]/ MPT ODU connected to Step 3

(continued) Port#[1-4]/Ch#[0-1]-PM15min EASv2
Hop/Dir#[3-8][1-4]/Slot#[3-8]/
Hop/Dir#1[5-6]/Slot#1/ MPT-HL connected to
Port#[5-6]/Ch#1-PM15min Core-E
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 connected to
Hop/Dir#1[5-6]/MSS/CORE/ MPT-HLC connected to
Port#[5-6]/Ch#1-PM1dayer
Hop/Dir#[3-8][5-8]/Slot#[3-8]/ MPT-HLC connected to
Hop/Dir#[3-8][5-8]/Slot#[3-8]/

Threshold crossed Link/Dir#[3-8][5-8]-PM15min MPT-HLC connected to Step 3

(continued) EASv2, P8ETH
Hop/Dir#[3-8]/Ch#[0-1]-PM15min MOD300
Hop/Dir#[3-8]/Ch#[0-1]-PM1day
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
Unavailable time Hop/Dir#1[1-6]/Slot#1/ MPT ODU connected to Step 12
Port#[1-6]/Ch#[0-1]-PM15min Core-E
Hop/Dir#1[1-6]/MSS/CORE/ MPT ODU connected to
Port#[1-6]/Ch#[0-1]-PM15min MSS/CORE

Unavailable time Hop/Dir#1[1-6]/MSS/CORE/ MPT ODU connected to Step 12

(continued) Port#[1-6]/Ch#[0-1]-PM1day MSS/CORE
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]/
Hop/Dir#1[5-6]/Slot#1/ MPT-HL connected to

Unavailable time Hop/Dir#1[5-6]/MSS/CORE/ MPT-HL connected to Step 12

(continued) Port#[5-6]/Ch#1-PM15min MSS/CORE
Hop/Dir#[3-8][5-8]/Slot#[3-8]/ MPT-HL connected to
Port#[5-8]/Ch#[0-1]-PM15min P8ETH
Hop/Dir#[3-8][5-8]/Slot#[3-8]/
Hop/Dir#1[5-6]/Slot#1/ MPT-HLC connected to
Hop/Dir#1[5-6]/MSS/CORE/ MPT-HLC connected to
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]/Ch#[0-1]-PM15min MOD300
Hop/Dir#[3-8]/Ch#[0-1]-PM1day

Unavailable time DS1-in/Slot#[3-8]/Port#[1-32]- DS1 on P32E1DS1 Step 12

(continued) PM15min
DS1-in/Slot#[3-8]/Port#[1-32]-PM1day
PM15min
PM1day
DS1-in/MSS/DS1/Port#[1-16]- DS1 on MSS-1 shelf
PM15min
DS1-in/MSS/DS1/Port#[1-16]-PM1day
PM15min
PM1day
and abnormal
condition
clearing
procedures
3. Threshold crossed
Verify the PM data using the Craft Terminal.
4. Verify the radio channel power levels.
6. Determine the local weather conditions that could affect radio performance.
7. Following local practices and procedures, determine whether corrective actions are
required.
8. Are corrective actions required?
9. Perform corrective actions per local practices and procedures.
11. Did the Threshold Crossed alarm clear?


12. Unavailable time
Verify the PM data using the Craft Terminal.
13. Verify the radio channel power levels.
15. Determine local weather conditions that could affect radio performance.
16. Following local practices and procedures, determine whether corrective actions are
required.
17. Are corrective actions required?
18. Perform corrective actions per local practices and procedures.
20. Did the Unavailable Time alarm clear?


23 — TAP-109 Synchronization alarms
(Core-E, MOD300, MPT-HC, MPT-HL,
MPT-HLC, MPT-XP, P32E1DS1, SDHACC,
9558HC)
23.1 — Purpose
This procedure describes how to identify and clear synchronization alarms on the Core-E,
MOD300, MPT-HC/MPT-XP/9558HC (MPT ODU), MPT-HL, MPT-HLC, P32E1DS1,
and SDHACC.
23.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 Ethernet
ports and Radio interfaces (MOD300/MPT ODU/MPT-HL//MPT-HLC) 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.
address.

MPT-XP, P32E1DS1, SDHACC, 9558HC)
23.3 — Procedure
2. Review the output. See Table 23.1 for information about synchronization alarms.
Table 23.1 — Sync alarms
Degrade SyncSource/Sync-in/Port#1 Core-E Step 3

SyncSource/ETH/slot#1/ Core-E User Ethernet
Port#[1-6] 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
SyncSource/Radio/Dir#[3-8]/Ch#[0-1] MOD300
SyncSource/Radio/Dir#1.[1-6]/ MPT ODU connected
SyncSource/Radio/Dir#1.[1-6]/ MPT ODU connected

MSS/CORE/Port#[1-6]/Ch#1 to MSS/CORE
SyncSource/Radio/Dir#[3-8].[1-4]/ MPT ODU connected

Slot#[3-8]/Port#[1-4]/Ch#1 to EASv2, MPTACC
SyncSource/Radio/Dir#[3-8].[5-8]/ MPT ODU connected


Table 23.1 — Sync alarms (Continued)
Degrade (continue) SyncSource/Radio/Dir#[3-8].[5-8]/ MPT-HL, MPT-HLC Step 3

Slot#[3-8]/Port#[5-8]/Ch#[0-1] connected to P8ETH
SyncSource/Radio/Dir#1.[5-6]/ MPT-HL, MPT-HLC

Slot#1/Port#[5-6]/Ch#1 connected to Core-E
SyncSource/Radio/Dir#1.[5-6]/MSS/ MPT-HL, MPT-HLC

CORE/Port#[5-6]/Ch#1 connected to MSS/
CORE
SyncSource/RadioLAG#[1-14] MPT ODU, MPT-HL,
MPT-HLC connected
to EASv2, P8ETH,
SyncSource/E1DS1-in/Slot#[3-8]/ P32E1DS1
Port#[1-32]
SyncSource/E1DS1-in/Slot#[3-8]/ MSS/DS1
Port#[1-16]
SyncSource/EleSdh-in/slot#[3-8]/ OC-3
Port[1-2]
SyncSource/OptSdh-in/slot#[3-8]/
Port[1-2]
Loss Ethernet MAU/Slot#[1-2]/Port#[1-6] Core-E Step 29
synchronization
messaging channel MAU/MSS/CORE/Port#[1-6] MSS/CORE
MAU/Slot#[3-8]/Port#[1-8] EASv2
RadioLAG#[1-14] MPT ODU, MPT-HL,
MPT-HLC



Loss Ethernet Radio/Dir#[3-8].[5-8]/ MPT ODU connected Step 29

synchronization Slot#[3-8]/Port#[5-8]/Ch#1 to P8ETH
messaging channel
(continued) Radio/Dir#[3-8].1-4]/ MPT ODU connected







Loss of signal Sync-in/Port#1 Core-E Step 38

Synchronization signal fail Sync-in/Port#1 Core-E Step 62
SyncSource/ETH/ Core-E user Ethernet
Slot#1/Port#[1-6] Port
SyncSource/ETH/MSS/ MSS/CORE user

CORE/Port#[1-6] Ethernet Port
SyncSource/ETH/ EASv2 user Ethernet

Slot#[3-8]/Port#[1-8] Port

Synchronization signal fail Radio/Dir#1.[1-6]/MSS/ MPT ODU connected Step 62

(continued) CORE/Port#[1-6]/Ch#1 to MSS/CORE

Slot#[3-8]/Port#[1-4]/Ch#1 to MPTACC





Slot#[3-8]/Port#[5-8]/Ch#1 P8ETH



Slot#[3-8]/Port#[5-8]/Ch#1 to EASv2,
P8ETH
MPT-HLC
DS1-in/Slot#[3-8]/Port#[1-32] DS1 on P32E1DS1
DS1-in/MSS/DS1/Port#[1-16] DS1 on MSS-1 shelf
EleSdh-in/slot#[3-8]/Port[1-2] OC-3


Alarm and
abnormal
condition
clearing
procedures
3. Degrade
What is the sync source?
a. If Degrade - Sync-In, go to step 4.
b. If Degrade - Radio port, go to step 9.
c. If Degrade - DS1 or OC-3 port, go to step 14.
4. Degrade - Sync-In
Verify that the Sync reference source (GPS or other sync source) is functioning
correctly.
5. Verify the Sync-In cabling and connections to the sync-in port on the Core-E card
(main and spare, if equipped).
6. Verify the Sync cabling and connections to the sync-out port on sync source.
8. Did the Degrade Defect alarm clear?
9. Degrade - Radio port
10. Verify that no other radio path alarms, such as Demodulator Fail. If radio path alarms
exist, troubleshoot accordingly.
11. Did the other radio path alarms exist and were they cleared?
14. Degrade - DS1 or OC-3 port

15. Verify that no LOS alarm exists on the sync reference DS1 or OC-3 port. If a LOS
alarm exists, troubleshoot accordingly.
16. Did the an LOS alarm exist on the sync reference DS1 or OC-3 port and was it cleared?
19. Verify that the sync reference DS1 or OC-3 port frequency is correct. If the sync
reference frequency is not correct, troubleshoot accordingly.
20. Was a sync reference DS1 port frequency problem identified and was it corrected?
23. Verify the sync source provisioning at both the sync source and the alarming card is
correct.
26. Which card is the Degrade Defect alarm declared against?
a. If Core-E, replace the Core-E. See DLP-103 Core switching module (Core-E)
replacement to replace Core-E.
b. If MOD300, replace the MOD300. See DLP-107 MOD300 (radio modem)
replacement to replace MOD300.
c. If MPT ODU replace the MPT ODU. See DLP-115 MPT ODU replacement
(MPT-HC, MPT-XP, 9558HC) to replace MPT ODU.
d. If MPT-HL/MPT-HLC, replace the MPT-HL. See DLP-108 MPT-HL/MPT-HLC
transceiver replacement to replace MPT-HL/MPT-HLC.
e. If P32E1DS1, replace the P32E1DS1. See DLP-111 P32E1DS1 (32-Port DS1)
replacement to replace P32E1DS1.
f. If MSS/DS1, go to step 95.
g. If SDHACC, replace the SDHACC. See DLP-126 SDHACC (2-Port OC-3)
Replacement to replace SDHACC.


29. Loss Ethernet synchronization messaging channel
30. Verify no radio or Ethernet alarms are declared against the radio direction declaring
Loss ESMC.
31. Are radio or Ethernet alarms declared against the radio direction or Ethernet port?
a. If yes, see IXL-101 Alarm and abnormal condition clearing procedures to clear
radio or Ethernet alarms declared against the radio direction or Ethernet port.
32. Using Craft Terminal retrieve the provisioned Synchronization SSM values for both
near end and far end of the hop for the alarmed Core-E/MOD300/MPT ODU/
MPT-HL/MPT-HLC.
33. Verify the desired Synchronization SSM value of the microwave hop.
34. Determine which Synchronization SSM value is correct.
35. Reprovision the Synchronization SSM value according to the results of step 34.
37. Did the Loss ESMC alarm clear?
38. Loss of signal
Verify Sync reference source (GPS or other sync source) is functioning properly.
39. Verify Sync-In cabling and connections to sync-in port on Core-E card (Main and
Spare if equipped).
b. f no, go to step 42.
42. Verify sync source provisioning at both the sync source and the alarming card.
45. Is traffic affected?


46. Is Core-E in a protected system?
47. Forced EPS switching Core-E will cause a hit to traffic.
48. Is Core-E card in alarm main or spare?
49. Perform Forced EPS Switch using Craft Terminal.
50. Go to step 52.
51. Perform Lockout EPS Switch using Craft Terminal.
52. CAUTION: Possibility of service interruption. Reseating an unprotected Core-E
card will cause a hit to traffic.
53. Reseat the Core-E card declaring Loss Of Signal.
56. CAUTION: Possibility of service interruption. Replacing an unprotected Core-E
card will cause a hit to traffic.
57. Replace the Core-E card declaring Loss Of Signal. See DLP-103 Core switching
module (Core-E) replacement to replace Core-E.
60. Is Core-E in a protected system?
61. Release Forced/Lockout EPS Switch using Craft Terminal.
62. Synchronization signal fail
63. Verify Degrade, Loss ESMC, or Loss of Signal are not also declared against Sync
source declaring Synchronization Signal Fail.
64. Are Degrade, Loss ESMC, or Loss of Signal also declared against synch source?
a. If yes, see Table 23.1 and clear other Sync alarms before proceeding to step 65.


66. Did the Synchronization Signal Fail alarm clear?
67. What is the sync source?
a. If Sync-in, go to step 68.
b. If Radio port, go to step 73.
c. If DS1 or OC-3 port, go to step 80.
68. Sync-in
Verify Sync reference source (GPS or other sync source) is functioning properly.
69. Verify Sync-In cabling and connections to sync-in port on Core-E card (Main and
Spare if equipped).
70. Verify Sync cabling and connections to sync-out port on sync source.
73. Radio port
74. Verify no radio alarms are declared against the radio direction declaring
Synchronization Signal Fail.
75. Are radio alarms declared against the radio direction?
a. If yes, see IXL-101 Alarm and abnormal condition clearing procedures to clear
radio alarms declared against the radio direction.
76. Verify no other radio path alarms (Demodulator Fail, etc.) exist. If radio path alarms
exist, troubleshoot accordingly.
77. Did the other radio path alarms exist and were they cleared?
80. DS1 or OC-3 port

81. Verify no LOS alarm exists on sync reference DS1 or OC-3 port. If LOS alarm exists,
82. Did the an LOS alarm exist on sync reference DS1 or OC-3 port and was it cleared?
85. Verify sync reference DS1 or OC-3 port frequency is correct. If sync reference
frequency is not correct, troubleshoot accordingly.
86. Was a sync reference DS1 or OC-3 port frequency problem identified and was it
corrected?
89. Verify sync source provisioning at both the sync source and the alarming card.
92. Which card is Synchronization Signal Fail alarm declared against?
a. If Core-E, replace the Core-E. See DLP-103 Core switching module (Core-E)
replacement to replace the Core-E.
b. If MOD300, replace the MOD300. See DLP-107 MOD300 (radio modem)
replacement to replace the MOD300.
c. If MPT ODU replace the MPT ODU. See DLP-115 MPT ODU replacement
(MPT-HC, MPT-XP, 9558HC) to replace the MPT ODU.
d. If MPT-HL/MPT-HLC, replace the MPT-HL/MPT-HLC. See DLP-108 MPT-HL/
MPT-HLC transceiver replacement to replace the MPT-HL/MPT-HLC.
e. If P32E1DS1, replace the P32E1DS1. See DLP-111 P32E1DS1 (32-Port DS1)
replacement to replace the P32E1DS1.
f. If MSS/DS1, go to step 95.
g. If SDHACC, replace the SDHACC. See DLP-126 SDHACC (2-Port OC-3)
Replacement to replace SDHACC.



24 — TAP-110 ATPC loop conditions
(MOD300, MPT-HC, MPT-HL, MPT-HLC,
MPT-XP, 9558HC)
24.1 — Purpose
This procedure describes how to identify and clear ATPC Loop conditions (ATPC Loop
Problem and Loop Problem) on MOD300, MPT-HC/MPT-XP/9558HC (MPT ODU),
MPT-HL, and MPT-HLC.
24.2 — General
An ATPC Loop Problem 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.
address.
24.3 — Procedure
1. Using the Alarm Monitor, retrieve all alarm.
2. Review the output. See Table 24.1 for information about ATPC Loop conditions.

9558HC)
Table 24.1 — ATPC loop conditions
ATPC loop problem Radio/Dir#1.[1-6]/ MPT ODU connected Step 3











ATPC loop problem Radio/Dir#[3-8].[5-8]/ MPT-HLC connected Step 3

(continued) Slot#[3-8]/Port#[5-8]/Ch#[0-1] to EASv2, P8ETH

9558HC)
Table 24.1 — ATPC loop conditions (Continued)
Loop problem Radio/Dir#1.[1-6]/ MPT ODU connected Step 8













abnormal condition
clearing procedures
3. ATPC loop problem

Using the Craft Terminal, determine whether the local transmit power is at minimum
power setting.
4. Is the local transmit power at its minimum power setting?

9558HC)
5. Troubleshoot the RF path from the near end transmitter to the far end receiver.
7. Did the ATPC Loop Problem alarm clear?
8. Loop problem
Is the system configured with protection?
11. Perform a Forced EPS Switch at the near end transmitter using the Craft Terminal.
12. Perform a Forced HSB Switch at the near end transmitter using Craft Terminal.
13. Perform a Forced Rx Radio Switch at the near end transmitter using Craft Terminal.
14. Go to step 18.
15. Perform a Lockout EPS Switch at the near end transmitter using the Craft Terminal.
16. Perform a Lockout HSB Switch at the near end transmitter using the Craft Terminal.
17. Perform a Lockout Rx Radio Switch at the near end transmitter using the Craft
Terminal.
19. Did the Loop Problem alarm clear?
and procedures.
21. Replace the MPT ODU, MPT-HL, or MPT-HLC in alarm at the near end.
a. Refer to DLP-115 MPT ODU replacement (MPT-HC, MPT-XP, 9558HC) to
replace MPT ODU.
b. Refer to DLP-108 MPT-HL/MPT-HLC transceiver replacement to replace
MPT-HL or MPT-HLC Transceiver.
22. Is the system configured with protection?

9558HC)

24. Release the Forced EPS Switch at the near end transmitter using the Craft Terminal.
25. Release the Forced HSB Switch at the near end transmitter using the Craft Terminal.
26. Release the Forced Rx Radio Switch at the near end transmitter using the Craft
Terminal.
27. Go to step 31.
28. Release the Lockout EPS Switch at the near end transmitter using the Craft Terminal.
29. Release the Lockout HSB Switch at the near end transmitter using the Craft Terminal.
30. Release the Lockout Rx Radio Switch at the near end transmitter using the Craft
Terminal.
32. Did the Loop Problem alarm return?
Is the card in alarm main or spare?
35. Perform a Forced EPS Switch at the far end transmitter using the Craft Terminal.
36. Perform a Forced HSB Switch at the far end transmitter using the Craft Terminal.
37. Perform a Forced Rx Radio Switch at the far end transmitter using the Craft Terminal.
38. Go to step 42.
39. Perform a Lockout EPS Switch at the far end transmitter using the Craft Terminal.
40. Perform a Lockout HSB Switch at the far end transmitter using the Craft Terminal.
41. Perform a Lockout Rx Radio Switch at the far end transmitter using the Craft Terminal.
43. Did the Loop Problem alarm clear?

9558HC)

and procedures.
45. Replace the MPT ODU, MPT-HL, or MPT-HLC at the far end.
a. Refer to DLP-115 MPT ODU replacement (MPT-HC, MPT-XP, 9558HC) to
replace MPT ODU.
b. Refer to DLP-108 MPT-HL/MPT-HLC transceiver replacement to replace
MPT-HL, or MPT-HLC Transceiver.
48. Release the Forced EPS Switch at the far end transmitter using the Craft Terminal.
49. Release the Forced HSB Switch at the far end transmitter using the Craft Terminal.
50. Release the Forced Rx Radio Switch at the far end transmitter using the Craft Terminal.
51. Go to step 55.
52. Release the Lockout EPS Switch at the far end transmitter using the Craft Terminal.
53. Release the Lockout HSB Switch at the far end transmitter using the Craft Terminal.
54. Release the Lockout Rx Radio Switch at the far end transmitter using the Craft
Terminal.
56. Did the Loop Problem alarm return?

25 — TAP-111 Cable LOS
25.1 — Purpose
This procedure describes how to identify and clear radio alarms on the MOD300.
25.2 — General
A Cable LOS alarm indicates that a bad cable or cable connection at the IF in/out connector
on the MOD300.
The DemXPIC LOS condition indicates that a bad or missing cable or cable connection at
the XPIC connector on the MPT-HC/MPT-XP/9558HC (MPT ODU).
address.
25.3 — Procedure
2. Review the output. See Table 25.1 for information about clear radio alarms.
Table 25.1 — Clear radio alarms
Cable LOS Radio/Dir#[3-8]/Ch#[0-1] MOD300 Step 3

Table 25.1 — Clear radio alarms (Continued)
DemXPIC LOS r01s1/b1[1-6]/daughter#04 MPT ODU connected Step 45

to Core-E, MSS/CORE
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 P8ETH
to EASv2
to Core-E, MSS/CORE
abnormal condition
clearing procedures
3. Cable LOS
Inspect the indoor IF cable is properly terminated, securely connected, and the run is
not damaged.
4. Was the indoor IF cable not properly terminated, connected, or the run was damaged?
5. Repair or replace the indoor IF cable.
7. Did the Cable LOS alarm clear?
9. Verify that the MOD300 card in alarm status is Standby.
10. Is the MOD300 card in alarm status Standby?

12. Is the MOD300 card in alarm main or spare?

16. Go to step 21.
20. CAUTION: Possibility of service interruption. Physically reseating the MOD300
in an unprotected radio hop causes a loss of traffic on ALL facilities that are
associated with the MOD300 reseat. Schedule appropriate maintenance window
21. Physically reseat the MOD300 card in alarm and wait for the status LED to turn steady
green or amber.
24. CAUTION: Possibility of service interruption. Replacing the MOD300 in an
unprotected radio hop causes a loss of traffic on ALL facilities that are associated
with the MOD300 being replaced. Schedule appropriate maintenance window per
25. Replace the MOD300. See DLP-107 MOD300 (radio modem) replacement to replace
MOD300.
26. CAUTION: Possibility of service interruption. Manually switching traffic causes
29. Inspect the outdoor IF cable is properly terminated, securely connected, and the run is
not damaged.
30. Was the outdoor IF cable not properly terminated, connected, or the run was damaged?
31. Repair or replace the outdoor IF cable.


35. CAUTION: Possibility of service interruption. Releasing Forced/Lockout
switching may cause a disruption to traffic.
36. Was the MOD300 declaring Cable LOS alarm the main or spare?
37. Release the Forced EPS Switch using the Craft Terminal.
38. Release the Forced HSB Switch using the Craft Terminal.
39. Release the Forced Rx Radio Switch using the Craft Terminal.
40. Go to step 75.
41. Release the Lockout EPS Switch using the Craft Terminal.
42. Release the Lockout HSB Switch using the Craft Terminal.
43. Release the Lockout Rx Radio Switch using the Craft Terminal.
44. Go to step 75.
45. DemXPIC LOS
Inspect the XPIC cable is properly terminated, securely connected, and the cable is not
damaged.
46. Is the XPIC cable not properly terminated, connected, or the cable is damaged?
47. Repair or replace the XPIC cable.
49. Did the DemXPIC LOS alarm clear?
50. Reseat the XPIC cable on the horizontal and vertical MPT ODU/MPT-HLC.

53. Replace the XPIC cable between the horizontal and vertical MPT ODU/MPT-HLC.
56. Reseat the XPIC module on horizontal MPT ODU. See DLP-122 RPS/XPIC module
replacement to reseat the XPIC module.
59. Reseat the XPIC module on the vertical MPT ODU. See DLP-122 RPS/XPIC module
replacement to reseat the XPIC module.
62. Replace the XPIC module on the horizontal MPT ODU. See DLP-122 RPS/XPIC
module replacement to replace the XPIC module.
65. Replace the XPIC module on vertical MPT ODU. See DLP-122 RPS/XPIC module
replacement to replace the XPIC module.
68. Replace the horizontal MPT ODU. See DLP-115 MPT ODU replacement (MPT-HC,
MPT-XP, 9558HC) to replace the MPT ODU.
71. Replace the vertical MPT ODU. See DLP-115 MPT ODU replacement (MPT-HC,



26 — TAP-112 Loss of alignment (MOD300,
MPT-HC, MPT-HL, MPT-HLC, MPT-XP,
9558HC)
26.1 — Purpose
This procedure describes how to identify and clear Loss Of Alignment alarm on the
MOD300, MPT-HC/MPT-XP/9558HC (MPT ODU), MPT-HL, and MPT-HLC.
26.2 — General
A Loss Of Alignment alarm indicates that a delay/loss of alignment between the main and
protect RF paths is detected.
address.
26.3 — Procedure
2. Review the output. See Table 26.1 for information about Loss of Alignment alarms.

26 — TAP-112 Loss of alignment (MOD300, MPT-HC, MPT-HL, MPT-HLC, MPT-XP, 9558HC)
Table 26.1 — Loss of alignment alarms
Loss of alignment Hitless/Dir#1.[1-6] MPT ODU connected Step 3

to Core-E, MSS/CORE
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 connected
to Core-E, MSS/CORE
Hitless/Dir#[3-8].[5-8] MPT-HLC connected
to EASv2, P8ETH
Hitless/Dir#[3-8] MOD300
abnormal condition
clearing procedures
3. Loss of alignment
Verify that the MPT ODU/MPT-HL/MPT-HLC/ODU300 in alarm status is Standby.
4. Is the MPT ODU/MPT-HL/MPT-HLC/ODU300 in alarm status Standby?
6. Is the MPT ODU/MPT-HL/MPT-HLC/ODU300 in alarm main or spare?
10. Go to step 14.


14. Which card is in alarm?
a. If MPT ODU go to step 15.
b. If MPT-HL, go to step 30.
c. If MOD300, go to step 41.
15. MPT ODU
Remove power to the MPT ODU. If powered through the EASv2, MPTACC or MSS-1
shelf MSS/CORE, 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.
17. Did the Loss Of Alignment alarm clear?
traffic on ALL facilities supported by the Core-E, EASv2, MPTACC, P8ETH
card or MSS-1 shelf, associated with the facility in alarm. Schedule appropriate
19. Reseat the Core-E, EASv2, MPTACC, P8ETH card, or MSS-1 shelf MSS/CORE that
is associated with MPT ODU in alarm.
For the MSS-1 shelf, locate the fuses protecting the A and B battery feeds to the MSS-1
shelf and remove. Wait ten seconds. Then install the fuses protecting the A and B
battery feeds.
20. Wait for the status LED to turn steady amber.
23. Which card reported the Loss Of Alignment alarm?
Core-E card.
b. If EASv2, see DLP-105 Ethernet Access Switch replacement (EASv2 and P8ETH)
to replace EASv2 card.
c. If MPTACC, see DLP-114 MPTACC (MPT Access) replacement to replace
MPTACC card.
d. If P8ETH, see DLP-105 Ethernet Access Switch replacement (EASv2 and P8ETH)
to replace P8ETH card.
e. If MSS-1 shelf MSS/CORE, see DLP-128 MSS-1 shelf replacement to replace
MSS-1 shelf.


30. MPT-HL/MPT-HLC
Position the MPT-HL/MPT-HLC Transceiver PA switch to the OFF ‘0’ position.
31. Remove the fuse in the PDU that supplies battery power to the MPT-HL/MPT-HLC
transceiver.
32. Install the fuse in the PDU that supplies battery power to the MPT-HL/MPT-HLC
transceiver.
33. Position the MPT-HL/MPT-HLC Transceiver PA switch to the ON ‘1’ position.
37. Replace the MPT-HL/MPT-HLC in alarm. See DLP-108 MPT-HL/MPT-HLC
transceiver replacement to replace the MPT-HL/MPT-HLC.
41. MOD300
Physically reseat the MOD300 card in alarm.

45. Replace the MOD300 card in alarm. See DLP-107 MOD300 (radio modem)
replacement to replace the MOD300.
49. Replace the ODU300 that is associated with MOD300 in alarm. See DLP-109 ODU300
replacement to replace the ODU300.
55. Go to step 57.


27 — TAP-113 Loss of frame (MOD300,
9558HC)
27.1 — Purpose
This procedure describes how to identify and clear Loss of Frame radio alarms on the
MOD300, MPT-HC/MPT-XP/9558HC (MPT ODU), MPT-HL, and MPT-HLC.
27.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.
address.
27.3 — Procedure
2. Review the output. See Table 27.1 for information about Loss of Frame radio alarms.

27 — TAP-113 Loss of frame (MOD300, MPT-HC, MPT-HL, MPT-HLC, MPT-XP, 9558HC)
Table 27.1 — Loss of frame radio alarms
Loss of frame Radio/Dir#1.[1-6]/ MPT ODU connected Step 3












and abnormal
condition clearing
procedures
3. Loss of frame

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. Go to step 140.
13. Unprotected radio configuration
Is the traffic affected?
a. If MOD300, go to step 40.
15. MPT ODU
Is the MPT ODU in alarm supported by the Core-E, EASv2, P8ETH card or MSS-1
Shelf MSS/Core?
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?


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 DLP-
114 MPTACC (MPT Access) replacement to replace the MPTACC.
30. Replace the far end MPTACC that is associated with the MPT ODU in alarm. See
DLP-114 MPTACC (MPT Access) replacement to replace the MPTACC.
34. Replace the local MPT ODU in alarm. See DLP-115 MPT ODU replacement

37. Replace the far end MPT ODU in alarm. See DLP-115 MPT ODU replacement
40. MOD300
Reseat the local MOD300 card.
42. Reseat the far end MOD300 card.
44. Replace the local MOD300. See DLP-107 MOD300 (radio modem) replacement to
replace the MOD300.
46. Replace the far end MOD300. See DLP-107 MOD300 (radio modem) replacement to
replace the MOD300.
48. Replace the local ODU300. See DLP-109 ODU300 replacement to replace the
ODU300.
50. Replace the far end ODU300. See DLP-109 ODU300 replacement to replace the
ODU300.
52. MPT-HL/MPT-HLC
Position the local MPT-HL/MPT-HLC Transceiver PA switch to the OFF ‘0’ position.

53. Remove fuse in PDU suppling battery power to local MPT-HL/MPT-HLC

Transceiver.
54. Install fuse in PDU suppling battery power to local MPT-HL/MPT-HLC Transceiver.
55. Position the local MPT-HL/MPT-HLC Transceiver PA switch to the ON ‘1’ position.
57. Position the far end MPT-HL/MPT-HLC Transceiver PA switch to the OFF ‘0’
position.
58. Remove fuse in PDU suppling battery power to far end MPT-HL/MPT-HLC
Transceiver.
59. Install fuse in PDU suppling battery power to far end MPT-HL/MPT-HLC
Transceiver.
60. Position the far end MPT-HL/MPT-HLC Transceiver PA switch to the ON ‘1’ position.
62. Replace the local MPT-HL/MPT-HLC. See DLP-108 MPT-HL/MPT-HLC transceiver
replacement to replace the MPT-HL/MPT-HLC Transceiver.
64. Replace the far end MPT-HL. See DLP-108 MPT-HL/MPT-HLC transceiver
66. Protected radio configuration
Determine the status of the MPT ODU/MPT-HL/MPT-HLC/MOD300 declaring the
Loss Of Frame alarm.
a. If Active, go to step 67.
b. If Standby, go to step 68.
68. Is the MPT ODU/MPT-HL/MPT-HLC/MOD300 declaring the Loss Of Frame alarm
the main or spare?


69. Perform a Forced Rx Radio Switch using the Craft Terminal on the local MPT ODU/
MPT-HL/MPT-HLC/MOD300.
70. Perform a Forced Equipment Switch using the Craft Terminal on the local MPT ODU/
71. Perform a Forced HSB Switch using the Craft Terminal on the far end MPT ODU/
72. Perform a Forced Equipment Switch using the Craft Terminal on the far end
MPT ODU/MPT-HL/MPT-HLC/MOD300.
73. Go to step 78.
74. Perform a Lockout Rx Radio Switch using the Craft Terminal on the local MPT ODU/
75. Perform a Lockout Equipment Switch using the Craft Terminal on the local
76. Perform Lockout HSB Switch using the Craft Terminal on the far end MPT ODU/
77. Perform a Lockout Equipment Switch using the Craft Terminal on the far end
a. If MOD300, go to step 79.
79. MOD300
Reseat the local MOD300 card that is declaring the Loss Of Frame alarm.
81. Reseat far end MOD300 card.
83. Replace the local MOD300 that is declaring the Loss Of Frame alarm. See DLP-107
MOD300 (radio modem) replacement to replace the MOD300.

85. Replace the far end MOD300 associated with the MOD300 that is declaring the Loss
Of Frame alarm. See DLP-107 MOD300 (radio modem) replacement to replace the
MOD300.
87. Replace the local ODU300 associated with the MOD300 that is declaring Loss Of
Frame alarm. See DLP-109 ODU300 replacement to replace the ODU300.
89. Replace the far end ODU300 associated with the MOD300 that is declaring the Loss
Of Frame alarm. See DLP-109 ODU300 replacement to replace the ODU300.
91. MPT ODU
Is the MPT ODU in alarm supported by the Core-E, EASv2, P8ETH card or MSS-1
Shelf MSS/Core?
92. 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?
93. Is the second radio channel, at the local or at the far end, error-free and alarm free?
94. Reseat the local MPTACC that is associated with the MPT ODU in alarm.
98. Reseat the far end MPTACC that is associated with MPT ODU in alarm.


102.Replace the local MPTACC that is associated with MPT ODU in alarm. See DLP-114
MPTACC (MPT Access) replacement to replace the MPTACC.
103.Wait for the status LED to turn steady amber.
106.Replace the far end MPTACC that is associated with MPT ODU in alarm. See DLP-
114 MPTACC (MPT Access) replacement to replace the MPTACC.
107.Wait for the status LED to turn steady amber.
110.Replace the local MPT ODU in alarm. See DLP-115 MPT ODU replacement
113.Replace the far end MPT ODU in alarm. See DLP-115 MPT ODU replacement
116.MPT-HL/MPT-HLC
Position the local MPT-HL/MPT-HLC Transceiver PA switch to the OFF ‘0’ position.
117.Remove the fuse in the PDU that is suppling battery power to the local MPT-HL/
MPT-HLC transceiver.
118.Install the fuse in the PDU that is suppling battery power to the local MPT-HL/
119.Position the local MPT-HL/MPT-HLC Transceiver PA switch to the ON ‘1’ position.


121.Position the far end MPT-HL/MPT-HLC Transceiver PA switch to the OFF ‘0’
position.
122.Remove the fuse in the PDU that is suppling battery power to the far end MPT-HL/
123.Install the fuse in the PDU that is suppling battery power to the far end MPT-HL/
124.Position the far end MPT-HL/MPT-HLC Transceiver PA switch to the ON ‘1’
position.
126.Replace the local MPT-HL. See DLP-108 MPT-HL/MPT-HLC transceiver
128.Replace the far end MPT-HL. See DLP-108 MPT-HL/MPT-HLC transceiver
130.Verify antenna is aligned.
131.Is the antenna aligned?
b. If no, align the antenna. See Alcatel-Lucent 9500 MPR-A Turn-up, Antenna
Procedure.
134.Release the Forced/Lockout Rx Radio Switch using the Craft Terminal on the local
MPT ODU/MPT-HL/MOD300.
135.Release the Forced/Lockout Equipment Switch using the Craft Terminal on the local

136.Release the Forced/Lockout HSB Switch using the Craft Terminal on the far end
137.Release the Forced/Lockout Equipment Switch using the Craft Terminal on the far end
138.Go to step 140.


28 — TAP-114 RPS path fail (MPT-HC,
MPT-HL, MPT-HLC, MPT-XP, 9558HC)
28.1 — Purpose
This procedure describes how to identify and clear an RPS Path Fail alarm on the MPT-HC/
MPT-XP/9558HC (MPT ODU), MPT-HL, and MPT-HLC.
28.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.
address.
28.3 — Procedure
2. Review the output. See Table 28.1 for RPS Path Fail alarms.

28 — TAP-114 RPS path fail (MPT-HC, MPT-HL, MPT-HLC, MPT-XP, 9558HC)
Table 28.1 — RPS path fail alarms
RPS path fail RadioProt/Dir#[3-8][1-4] MPT ODU connected Step 3

to MPTACC
RadioProt/Dir#1[1-6] MPT ODU connected

to Core-E, MSS/CORE
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
RadioProt/Dir#1[5-6] MPT-HLC connected
to MSS/CORE
RadioProt/Dir#[3-8][5-8] MPT-HLC connected
to EASv2, P8ETH
abnormal condition
clearing procedures
3. RPS path fail

Using the Craft Terminal, determine which MPT ODU/MPT-HL/MPT-HLC status is
Standby.
5. MPT ODU
Retrieve the alarms for the local end of the radio direction 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?
9. Retrieve the alarms for the far end of the radio direction using Alarm Monitor.

10. Determine all radio alarms declared against the radio direction declaring RPS Path Fail
and troubleshoot accordingly.
12. Did the RPS Path Fail alarm clear?
13. MPT-HL
Is the MPT-HL/MPT-HLC card in alarm main or spare?
17. Go to step 21.
21. On the MPT-HL/MPT-HLC with status of Standby, position the PA switch to the OFF
‘0’ position.
22. Remove the fuse in the PDU that is suppling battery power to the MPT-HL/MPT-HLC
with a status of Standby.
23. Install the fuse in the PDU that is suppling battery power to MPT-HL/MPT-HLC with
a status of Standby.
24. On the MPT-HL/MPT-HLC with status of Standby, position the PA switch to the ON
‘1’ position.
28. Replace the MPT-HL/MPT-HLC with status of Standby. See DLP-108 MPT-HL/
MPT-HLC transceiver replacement to replace MPT-HL/MPT-HLC.


33. Is the MPT-HL/MPT-HLC card in alarm main or spare?
37. Go to step 41.
41. On the MPT-HL/MPT-HLC with status of Standby, position the PA switch to the OFF
‘0’ position.
42. Remove the fuse in the PDU that is suppling the battery power to the MPT-HL/
MPT-HLC with a status of Standby.
43. Install the use in the PDU that is suppling battery power to the MPT-HL/MPT-HLC
with a status of Standby.
44. On the MPT-HL/MPT-HLC with status of Standby, position the PA switch to the ON
‘1’ position.
48. Replace MPT-HL/MPT-HLC with status of Standby. See DLP-108 MPT-HL/
MPT-HLC transceiver replacement to replace the MPT-HL/MPT-HLC.
56. Go to step 58.




29 — TAP-115 Rx fail (MOD300)
29.1 — Purpose
This procedure describes how to identify and clear Rx Fail alarms on MOD300.
29.2 — General
An Rx Fail alarm indicates that a failure is detected in the receive direction of the MOD300
RF receiver and includes no input signal.
address.
29.3 — Procedure
2. Review the output. See Table 29.1 for information about Rx Fail alarms.
Table 29.1 — Rx fail alarms
Rx fail Radio/Dir#[3-8]/Ch#[0-1] MOD300 Step 3

abnormal condition
clearing procedures
3. Rx fail

Verify there are no weather-related problems existing.

4. Do weather-related problems exist?
a. If yes, wait for weather to clear and recheck alarms. Go to step 72.
8. Is RSL above RX threshold?
11. Did the Rx Fail alarm clear?
14. Is the MOD300 in alarm the main or spare?
15. Perform a Forced EPS Switch using the Craft Terminal on the local MOD300.
16. Perform a Forced HSB Switch using the Craft Terminal on the local MOD300.
17. Perform a Forced Rx Radio Switch using the Craft Terminal on the local MOD300.
18. Go to step 24.
19. Perform Lockout EPS Switch using the Craft Terminal on the local MOD300.
20. Perform Lockout HSB Switch using the Craft Terminal on the local MOD300.
21. Perform Lockout Rx Radio Switch using the Craft Terminal on the local MOD300.
22. Go to step 24.
23. CAUTION: Possibility of service interruption. Reseat the MOD300 in an
with the MOD300 reseat. Schedule appropriate maintenance window per local

24. Reseat the MOD300 card in alarm. Physically remove the card and reinsert.
28. Forced/Lockout switching traffic causes a disruption to traffic.
29. Is the MOD300 in alarm main or spare?
30. Perform a Forced EPS Switch using the Craft Terminal on the far end MOD300.
31. Perform a Forced HSB Switch using the Craft Terminal on the far end MOD300.
32. Perform a Forced Rx Radio Switch using the Craft Terminal on the far end MOD300.
33. Go to step 38.
34. Perform Lockout EPS Switch using the Craft Terminal on the far end MOD300.
35. Perform Lockout HSB Switch using the Craft Terminal on the far end MOD300.
36. Perform Lockout Rx Radio Switch using the Craft Terminal on the far end MOD300.
37. CAUTION: Possibility of service interruption. Reseating the MOD300 in an
with the MOD300 reseat. Schedule appropriate maintenance window per local
38. Reseat the far end MOD300 card associated with the card in alarm. Physically remove
42. Replace the near end MOD300. See DLP-107 MOD300 (radio modem) replacement to
replace the MOD300.


46. Replace the far end MOD300. See DLP-107 MOD300 (radio modem) replacement to
replace the MOD300.
49. Replace the near end ODU300. See DLP-109 ODU300 replacement to replace the
ODU300.
51. Did Rx Fail alarm clear?
52. Replace the far end ODU300. See DLP-109 ODU300 replacement to replace the
ODU300.
54. Did Loss Of Frame alarm clear?
55. Verify antenna is aligned.
56. Is antenna aligned?
b. If no, align the antenna. See the Alcatel-Lucent 9500 MPR-A Turn-up, Antenna
Procedure.

61. Release the Forced/Lockout EPS Switch using the Craft Terminal on the far end
MOD300.
62. Release the Forced/Lockout HSB Switch using the Craft Terminal on the far end
MOD300.
63. Release the Forced/Lockout Rx Radio Switch using the Craft Terminal on the far end
MOD300.
64. Go to step 66.
67. Release the Forced/Lockout EPS Switch using the Craft Terminal on the local
MOD300.
68. Release the Forced/Lockout HSB Switch using the Craft Terminal on the local
MOD300.
69. Release the Forced/Lockout Rx Radio Switch using the Craft Terminal on the local
MOD300.
70. Go to step 72.


30 — TAP-116 Housekeeping alarms
30.1 — Purpose
This procedure describes how to identify and clear Housekeeping alarms (External Point
Input) on AUX card.
30.2 — General
Housekeeping Alarm inputs are external alarms that are monitored by the NE.
Housekeeping alarms are provisionable for alarm state active low or high.
Housekeeping Alarm Input [1-6] indicates that the external alarm point is active,
improperly configured, or improperly provisioned.
address.
30.3 — Procedure
2. Review the output. See Table Table 30.1 for information about Housekeeping alarms.

30 — TAP-116 Housekeeping alarms
Table 30.1 — Housekeeping alarms
Housekeeping alarm ExtPt/Input#[1-6] AUX Step 3

ExtPt/Input#[11-14] Fan
ExtPt/Input#[11-14] MSS-1
abnormal condition clearing
procedures
3. Housekeeping alarm
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 Input [1-6] 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.

31 — TAP-117 LAG alarms (Core-E,
ODU300, 9558HC, MSS-1 shelf Core)
31.1 — Purpose
This procedure describes how to identify and clear LAG alarms on the Core-E, MPT-HC/
MPT-XP/9558HC (MPT ODU), MPT-HL, MPT-HLC, ODU300, and MSS-1 shelf Core.
31.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 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.
address.
31.3 — Procedure
1. Using the Alarm Monitor, retrieve ALL alarms.
2. Review the output. See Table 31.1 for information about LAG alarms.

9558HC, MSS-1 shelf Core)
Table 31.1 — LAG alarms
Degrade EthLAG#[1-14] Core-E, MSS/CORE Step 3

MPT-HLC, ODU300
Loss of signal EthLAG#[1-14] Core-E, MSS/CORE Step 8
MPT-HLC, ODU300
None of the — — IXL-101 Alarm and
above abnormal condition clearing
procedures
3. Degrade
4. Identify the alarms that are declared against members of the LAG group. If alarms
exists, see IXL-101 Alarm and abnormal condition clearing procedures and
5. Did the alarms exist on the LAG group members and were they cleared?
7. Did the Degrade alarm clear?
8. Loss of signal
9. Identify the alarms that are declared against members of the LAG group. If alarms
exists, see IXL-101 Alarm and abnormal condition clearing procedures and
10. Did the alarms exist on the LAG members and were they cleared?
12. Did the Loss of Signal alarm clear?




32 — TAP-118 Ethernet connectivity fault
management alarms
32.1 — Purpose
This procedure describes how to identify and clear Ethernet Connectivity Fault
Management (ECFM) alarms.
32.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.

32 — TAP-118 Ethernet connectivity fault management alarms
address.
See the Alcatel-Lucent 9500 MPR-A Operation and Administration, WT CLI Tool
Reference Guide for information about how to execute the commands that are described in
this procedure.
32.3 — Procedure
2. Review the output. See Table 32.1 for information about ECFM alarms.
Table 32.1 — ECFM alarms
Eth OAM loss of MEP#MDID[1-16]#MA ID Core-E, MSS/CORE Step 3

continuity [1-512]#MEPID[1-8191]
Eth OAM MEP#MDID[1-16]#MA ID Core-E, MSS/CORE Step 7
MisMerge [1-512]#MEPID[1-8191]
condition
Eth OAM remote MEP#MDID[1-16]#MA ID Core-E, MSS/CORE Step 12
defect indication [1-512]#MEPID[1-8191]
unexpected level [1-512]#MEPID[1-8191]
unexpectedMEPID [1-512]#MEPID[1-8191]
unexpected period [1-512]#MEPID[1-8191]
abnormal condition
clearing procedures
3. Eth OAM loss of continuity

Locate the failure in the network.
a. If MIPs were created on the MEP, use the Link Trace command using WT CLI
Tool. See Alcatel-Lucent 9500 MPR-A Operation and Administration, 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.
4. Were the alarms identified and cleared between the local and far end of the MEP?
6. Did the Eth OAM Loss of Continuity Condition alarm clear?
7. Eth OAM MisMerge condition
Retrieve MA ID for both ends of the MEP using WT CLI Tool. See Alcatel-Lucent
9500 MPR-A Operation and Administration, WT CLI Tool Reference Guide for more
information.
8. Determine which MA ID value(s) are incorrect.
9. Reprovision the MA ID value(s) according to the results of step 8.
11. Did the Eth OAM MisMerge Condition alarm clear?
12. Eth OAM remote defect indication
Retrieve the alarms on the far end of the MEP using Alarm Monitor.
13. Check the far end for the one or more of the above RDI set conditions and troubleshoot
accordingly.
14. Were the RDI set condition cleared at the far end of the MEP?
16. Did the Eth OAM Remote Defect Indication Level alarm clear?
17. Eth OAM unexpected level
Retrieve the MD Level for both ends of the MEP using WT CLI Tool. See Alcatel-
Lucent 9500 MPR-A Operation and Administration, WT CLI Tool Reference Guide
for more information.
18. Determine which MD Level values are incorrect.
19. Reprovision the MD Level values according to the results of step 18.

21. Did the Eth OAM Unexpected Level alarm clear?

22. Eth OAM unexpectedMEPID
Retrieve MEPID for both ends of the MEP using WT CLI Tool. See Alcatel-Lucent
9500 MPR-A Operation and Administration, WT CLI Tool Reference Guide for more
information.
23. Determine which MEPID value(s) are incorrect.
24. Reprovision the MEPID value(s) according to the results of step 23.
26. Did the Eth OAM UnexpectedMEPID alarm clear?
27. Eth OAM unexpected period
Retrieve the MEP Transmission Interval for both ends using WT CLI Tool. See
Alcatel-Lucent 9500 MPR-A Operation and Administration, WT CLI Tool Reference
Guide for more information.
28. Determine which MEP Transmission Interval values are incorrect.
29. Reprovision the MEP Transmission Interval according to the results of step 28.
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.

31. Did the Eth OAM Unexpected Period alarm clear?

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

33 — TAP-119 Clock failure (MPT-HC, MPT-HL, MPT-HLC, MPT-XP, 9558HC)
Table 33.1 — Clock failure alarm
Clock failure Radio/Dir#1.[1-6]/ MPT ODU connected Step 3












and abnormal
condition clearing
procedures
3. Clock failure
Is the system configured with protection?
4. Clock failure - Unprotected Radio Configuration

Caution: Possibility of service interruption. Power Cycling an in-service MPT ODU,

MPT-HL, or MPT-HLC in an unprotected link causes a loss of traffic on ALL facilities
that are associated with the MPT ODU, MPT-HL, or MPT-HLC in alarm. Schedule
Caution: Possibility of service interruption. Replacing the MPT ODU, MPT-HL, or

MPT-HLC in an unprotected link causes a loss of traffic on ALL facilities that are
associated with the MPT ODU, MPT-HL, or MPT-HLC in alarm. Schedule appropriate

6. Verify that it is appropriate to proceed with clear Clock Failure procedure or
appropriate maintenance window is scheduled per local practices and procedures.
7. Is it appropriate to proceed with clear Clock Failure procedure?
9. CAUTION: Possibility of service interruption. 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. Schedule appropriate maintenance window per
10. Power cycle the MPT ODU.
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.If MPT ODU is powered through a power injector card/power injector box,
disconnect the Ethernet+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.
c. If MPT ODU is powered with connection to direct office power, locate the fuse
11. Dialog Failure is declared against the MPT ODU. Wait for Dialog Failure condition to
clear before proceeding.


13. Did the Clock Failure alarm clear?
14. CAUTION: Possibility of service interruption. 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 appropriate maintenance window per local
18. MPT-HL/MPT-HLC
Caution: Possibility of service interruption. 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 appropriate maintenance window per local
19. Position the MPT-HL/MPT-HLC Transceiver PA switch to the OFF ‘0’ position.
transceiver.
21. Install the fuse in PDU that is suppling battery power to the MPT-HL/MPT-HLC
transceiver.
25. CAUTION: Possibility of service interruption. 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 appropriate
26. Replace the local MPT-HL/MPT-HLC. See DLP-108 MPT-HL/MPT-HLC transceiver
replacement to replace the MPT-HL/MPT-HLC transceiver.


28. Protected radio configuration
Caution: Possibility of service interruption. Forced EPS/HSB/RX Radio switching traffic

29. Determine the status of MPT ODU/MPT-HL/MPT-HLC declaring Clock Failure

alarm.
a. If Active, go to step 30.
b. If Standby, go to step 31.
32. Is the MPT ODU/MPT-HL/MPT-HLC declaring Clock Failure alarm the main or
spare?
34. Perform a Forced Equipment Switch using the Craft Terminal.
36. Go to step 40.
38. Perform a Lockout Equipment Switch using the Craft Terminal.
41. MPT ODU
Power cycle the MPT ODU.
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 Ethernet+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.
42. Dialog Failure is declared against the MPT ODU. Wait for Dialog Failure condition to
clear before proceeding.
48. MPT-HL/MPT-HLC
Position the MPT-HL/MPT-HLC Transceiver PA switch to the OFF ‘0’ position.
transceiver.
50. Install the fuse in the PDU thatis suppling battery power to the MPT-HL/MPT-HLC
transceiver.
54. Replace the MPT-HL/MPT-HLC. See DLP-108 MPT-HL/MPT-HLC transceiver
replacement to replace MPT-HL/MPT-HLC Transceiver.
57. CAUTION: Possibility of service interruption. Releasing Forced/Lockout EPS/
HSB/RX Radio switch causes a disruption to traffic.
59. Release the Forced/Lockout Equipment Switch using the Craft Terminal.

61. Go to step 63.
63. STOP. This procedure is complete


34 — TAP-120 Duplicate Address Detected
alarms
34.1 — Purpose
This procedure describes how to identify and clear Duplicate Address Detected alarms.
34.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.
address.

34 — TAP-120 Duplicate Address Detected alarms
34.3 — Procedure
2. Review the output. See Table Table 34.1 for information about Duplicate address
detected alarms.
Table 34.1 — Duplicate address detected alarms
Duplicate address TMNEthernet/MngtPort Core-E/TMN MGMT Port Step 3

detected
TMNEthernet/Port#4 Core-E/TMN Port#4 Step 25
TMNInBand#[1-2] Core-E/TMN In-Band Port [1- Step 47
2]
Duplicate address PPP-IP/RF#[3-8] MOD300 Step 63
detected
PPP-IP/RF#1[1-6] MPT ODU connected to
Core-E, MSS/CORE
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
connected to EASv2, P8ETH
PPP-IP/RF#1[5-6] MPT-HL, MPT-HLC
connected to Core-E, MSS/
CORE
PPP-IP/RF/LAG#[1-14] MPT ODU, MPT-HL,
MPT-HLC, ODU
abnormal condition
clearing procedures
3. Duplicate address detected

TMN Ethernet MGMT Port

Using the Craft Terminal, retrieve the provisioned IPv6 TMN Ethernet Configuration
value for the NE declaring duplicate address detected alarm.
4. Verify the desired IPv6 TMN Ethernet Configuration value for the NE according to site
engineering documentation.
5. Is the provisioned IPv6 TMN Ethernet value correct?
a. If no, go to step 6.
b. If yes, go to step 16.
6. CAUTION: Possibility of service interruption. 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.
7. CAUTION: Possibility of service interruption. 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.
8. Reprovision IPv6 TMN Ethernet Configuration value for the NE according to site
9. Was the IPv6 address changed on-site?
10. Disconnect the TMN Ethernet interface and reconnect.
11. Go to step 14
12. Disable TMN Ethernet Configuration port in alarm.
13. Enable TMN Ethernet Configuration port in alarm.
15. Did the duplicate address detected alarm clear?
16. Verify the desired IPv6 TMN Ethernet Configuration value for the far end NE
according to site engineering documentation.
17. Reprovision the far end NE with the correct IPv6 address.
18. Was the IPv6 address changed on-site at the near end or far end NE?
20. Go to step 23
21. Disable TMN Ethernet Configuration port in alarm.

22. Enable TMN Ethernet Configuration port in alarm.

25. Port #4 TMN Ethernet
Using the Craft Terminal, retrieve the provisioned IPv6 Port #4 TMN Ethernet
Configuration value for the NE declaring duplicate address detected alarm.
26. Verify the desired IPv6 Port #4 TMN Ethernet Configuration value for the NE
27. Is the provisioned IPv6 Port #4 TMN Ethernet value correct?
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.
30. Reprovision IPv6 Port #4 TMN Ethernet Configuration value for the NE according to
site engineering documentation.
31. Was the IPv6 address changed on-site?
32. Disconnect the Port #4 TMN Ethernet interface and reconnect.
33. Go to step 36.
34. Disable Port #4 TMN Ethernet Configuration port in alarm.
35. Enable Port #4 TMN Ethernet Configuration port in alarm.
38. Verify the desired IPv6 Port #4 TMN Ethernet Configuration value for the far end NE

40. Was the IPv6 address changed on-site at the near end or far end NE?
42. Go to step 45.
43. Disable Port #4 TMN Ethernet Configuration port.
44. Enable Port #4 TMN Ethernet Configuration port.
47. TMN In-Band Port #1/2
Using the Craft Terminal, retrieve the provisioned IPv6 TMN In-Band Port #1/2 value
for the NE declaring duplicate address detected alarm.
48. Verify the desired IPv6 TMN In-Band Port #1/2 value for the NE according to site
49. Is the provisioned IPv6 TMN In-Band Port #1/2 value correct?
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.
52. Reprovision IPv6 TMN In-Band Port #1/2 value for the NE according to site
53. Disable TMN In-Band Port #1/2.
54. Enable TMN In-Band Port #1/2.
57. Verify the desired IPv6 TMN In-Band Port #1/2 Ethernet Configuration value for the
far end NE according to site engineering documentation.

59. Disable TMN In-Band Port #1/2.
60. Enable TMN In-Band Port #1/2.
63. Duplicate address detected
PPP IP/RF Port
Using the Craft Terminal, retrieve the provisioned Local IPv6 Address value for the NE
declaring duplicate address detected alarm.
64. Verify the desired Local IPv6 Address value for the NE according to site engineering
documentation.
65. Is the provisioned Local IPv6 Address value correct?
66. Reprovision Local IPv6 Address value for the NE according to site engineering
documentation.
69. Verify the desired Local IPv6 Address value for the far end NE according to site
70. 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.

73. Verify the near end PPP-RF port provisioning.
74. Was the near end PPP-RF port provisioned correctly?


75. Reprovision near end PPP-RF port provisioning.
76. Disable near end PPP RF port.
77. Enable near end PPP RF port.
80. Verify the far end PPP-RF port provisioning.
81. CAUTION: Possibility of service interruption. 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.
82. Was the far end PPP-RF port provisioned correctly?
83. Reprovision far end PPP-RF port provisioning.
84. Disable far end PPP RF port.
85. Enable far end PPP RF port.


35 — TAP-121 Combiner loss of alignment
(MPT-HLC)
35.1 — Purpose
This procedure describes how to identify and clear Combiner Loss Of Alignment alarm on
the MPT-HLC.
35.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.
address.
35.3 — Procedure
2. Review the output. See Table 35.1 for information about Combiner Loss of Alignment
alarms.

35 — TAP-121 Combiner loss of alignment (MPT-HLC)
Table 35.1 — Combiner loss of alignment alarm
Combiner Loss of r01/subrack#1[5-6] MPT-HLC connected to Step 3

alignment Core-E, MSS/CORE
r01/subrack#[3-8][5-8] MPT-HLC connected to EASv2
abnormal condition
clearing procedures
3. Combiner Loss of alignment

Is the radio direction in a protected configuration?
4. Verify that the MPT-HLC in alarm status is Standby.
5. Is the MPT-HLC in alarm status Standby?
7. Is the MPT-HLC in alarm main or spare?
11. Go to step 17.
15. Go to step 17.
16. CAUTION: Possibility of service interruption. The following steps on an
unprotected radio direction will cause a loss of traffic associated with the radio
direction in alarm. Schedule appropriate maintenance window per local practices
and procedures.
17. Inspect the RF cabling to the main and diversity receiver.
Correct ALL issues identified.


19. Did the Combiner Loss Of Alignment alarm clear?
20. Disconnect the data cable connection at the MPT-HLC in alarm. Then reconnect the
cable.
21. Wait for the status LED to turn steady amber or green.
24. Position the MPT-HLC Transceiver PA switch to the OFF ‘0’ position.
25. Remove the fuse in the PDU that supplies battery power to the MPT-HLC transceiver.
26. Install the fuse in the PDU that supplies battery power to the MPT-HLC transceiver.
27. Position the MPT-HLC Transceiver PA switch to the ON ‘1’ position.
31. Replace the MPT-HLC in alarm. See DLP-108 MPT-HL/MPT-HLC transceiver
replacement to replace the MPT-HLC.
35. CAUTION: Possibility of service interruption. Physically removing an MPTACC/
P8ETH/EASv2/Core-E/MSS-1 MSS/CORE will cause a loss of traffic on ALL
unprotected facilities that are supported by the MPTACC/P8ETH/EASv2/
Core-E/MSS-1 MSS/CORE, associated with the radio direction in alarm.
36. Is it appropriate to proceed with Combiner Loss Of Alignment procedure?
37. For the Core-E, EASv2, MPT Access, or P8ETH cards, reseat the card. Physically
remove the card and reinsert.

For the MSS-1 shelf, locate the fuses protecting the A and B battery feeds to the MSS-1
shelf and remove. Wait ten seconds. Then install the fuses protecting the A and B
battery feeds.
41. CAUTION: Possibility of service interruption. Physically replacing an MPTACC/
P8ETH/EASv2/Core-E/MSS-1 MSS/CORE in an unprotected facility causes a
loss of traffic on ALL facilities that are associated with the MPTACC/P8ETH/
EASv2/Core-E/MSS-1 being replaced. Schedule appropriate maintenance
42. Is it appropriate to proceed with Combiner Loss Of Alignment procedure?
43. Which card is associated with the MPT ODU in alarm?
a. If MPTACC, see DLP-114 MPTACC (MPT Access) replacement to replace
MPTACC.
b. If EASv2 or P8ETH, see DLP-105 Ethernet Access Switch replacement (EASv2
c. If Core-E, see DLP-103 Core switching module (Core-E) replacement to replace
Core-E.
d. If MSS-1 shelf, see DLP-128 MSS-1 shelf replacement to replace MSS-1 shelf.
47. Is the radio direction in a protected configuration?
51. Go to step 53.

36 — TAP-122 Fan Fail
36.1 — Purpose
This procedure describes how to identify and clear Fan Fail alarm on MPT-HLC.
36.2 — General
A Fan Fail alarm indicates that MPT-HLC card has detected a MPT-HLC fan unit has
failed.
address.
36.3 — Procedure
2. Review the output. See Table 36.1 for information about equipment alarms.
Table 36.1 — Fan fail alarm
Fan Fail r01/subrack#1[5-6] MPT-HLC connected to Core-E, Step 3

MSS/CORE
r01/subrack#[3-8][5-8] MPT-HLC connected to EASv2,
P8ETH(Not supported in R5.1
but introduced in R5.2)

Table 36.1 — Fan fail alarm (Continued)

abnormal condition
clearing procedures
3. Fan Fail
Verify that ALL the MPT-HLC fans are equipped and operating properly.
5. Is it appropriate to proceed with Fan Fail procedure?
14. Go to step 20.
18. Go to step 20.

19. CAUTION: Possibility of service interruption. Physically replacing an

unprotected MPT-HLC will causes a loss of traffic on ALL facilities that are
associated with the MPT-HLC being replaced. Schedule appropriate
20. Replace the MPT-HLC. See DLP-108 MPT-HL/MPT-HLC transceiver replacement to
replace MPT-HLC.
23. Did the Fan Fail alarm clear?
28. Go to step 30.


37 — TAP-123 RF Switch Fail (MPT-HLC)
37.1 — Purpose
This procedure describes how to identify and clear RF Switch Fail alarm on the MPT-HLC.
37.2 — General
A RF Switch Fail alarm indicates that a failure is detected on the transmit RF switch.
address.
37.3 — Procedure
2. Review the output. See Table 37.1 for information about Combiner Loss of Alignment
alarms.
Table 37.1 — Combiner loss of alignment alarm
RF Switch Fail r01/subrack#1[5-6] MPT-HLC connected to Core-E, Step 3

MSS/CORE
abnormal condition
clearing procedures

3. RF Switch Fail
Inspect the cabling to/from the transmit RF switch:
a. MPT-HL shelf switch power connection
b. MPT-HL shelf TX main and Tx spare connections
c. Transmit RF switch antenna port connection
4. Were issue identified with the cabling to/from the transmit RF switch?
5. CAUTION: Possibility of service interruption. Muting both the main and spare
MPT-HLC will causes a loss of traffic on ALL facilities that are associated with
the MPT-HLC with RF Switch Fail alarm. Schedule appropriate maintenance
6. Mute both the main and spare transmitters.
7. Correct ALL cable and cable connections as required.
9. Did the RF Switch Fail alarm clear?
10. CAUTION: Possibility of service interruption. Muting both the main and spare
MPT-HLC will causes a loss of traffic on ALL facilities that are associated with
the MPT-HLC in alarm. Schedule appropriate maintenance window per local
11. Mute both the main and spare transmitters.
12. Replace the transmit RF switch.
14. Did the RF Switch Fail alarm clear?
15. Unmute the main transmitter.
16. Verify that the main MPT-HLC switch status is Active
17. Verify traffic is running error free at the far end associated with the main transmitter.
18. Unmute the spare transmitter.
20. Verify that the spare MPT-HLC switch status is Active
21. Verify traffic is running error free at the far end associated with the spare transmitter.
22. Did traffic run error-free on both the main and spare transmitters and is the direction
operating normally?


23. Release the Forced HSB Switch using the Craft Terminal
24. Go to step 26.


38 — TAP-124 Rx diversity missing
(MPT-HLC)
38.1 — Purpose
This procedure describes how to identify and clear Rx Diversity Missing alarm on the
MPT-HLC.
38.2 — General
A Rx Diversity Missing alarm indicates that the MPT-HLC has been configured for a
diversity receiver configuration but the system does not detect the diversity/combiner
module on the MPT-HLC.
address.
38.3 — Procedure
2. Review the output. See Table 38.1 for information about Rx Diversity Missing alarms.

38 — TAP-124 Rx diversity missing (MPT-HLC)
Table 38.1 — Rx diversity missing alarm
Rx Diversity r01/subrack#1[5-6] MPT-HLC connected to Core-E, Step 3

Missing MSS/CORE
abnormal condition
clearing procedures
3. Rx Diversity Missing
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 type.
10. Is it appropriate to proceed with Rx Diversity Missing alarm procedure?


19. Go to step 25.
23. Go to step 25.
24. CAUTION: Possibility of service interruption. Physically replacing an
unprotected MPT-HLC will causes a loss of traffic on ALL facilities that are
associated with the MPT-HLC being replaced. Schedule appropriate
25. Replace the MPT-HLC. Verify the replacement MPT-HLC type supports the diversity
receiver as described in site engineering documentation. See DLP-108 MPT-HL/
MPT-HLC transceiver replacement to replace the MPT-HLC.
28. Did the Rx Diversity Missing alarm clear?
33. Go to step 35.


39 — DLP-100 Mechanical card removal
and installation
39.1 — Purpose
This procedure describes how to remove and install cards mechanically in the 9500 MPR-
A.
39.2 — General
This procedure addresses only mechanical card removal and installation.
type.
39.3 — Procedure
1. DANGER: Possibility of personal injury. Modules can be installed or removed
with bay power on. Hazardous electrical potentials are present; use extreme care
when installing or removing cards with power on.
unprotected link causes loss of traffic. Removing an Active card in a protected
link requires switching the traffic onto the Standby card. Do applicable trouble
clearing and logical replacement procedures before proceeding with this
procedure.
3. WARNING: Possibility of equipment damage. Modules contain static-sensitive
devices. These devices can be damaged by static discharge. See Introduction for
special handling instructions.

39 — DLP-100 Mechanical card removal and installation
4. Which procedure to perform?

a. If card removal, go to step 5.
b. If card installation, go to step 9.
5. Card removal
Loosen the screws on the front of the card to be replaced.
6. Unlock the extraction tabs on the front of the card to be replaced.
7. Remove the card from the slot.
8. Go to step 16.
9. Card installation
Install the new card in the slot.
10. Lock the extraction tabs on the front of the new card.
11. Align the retaining screws.
12. Start both screws before tightening
13. WARNING: Possibility of equipment damage. Failure to start both screws prior to
tightening may cause screws to be cross threaded and possibly resulting in broken
retaining screws.
14. Tighten the screws on the front of the new card.
15. Return to the point in the DLP that referenced this procedure.

40 — DLP-101 MPT-HL/MPT-HLC
transceiver air filter replacement
40.1 — Purpose
This procedure describes how to check and replace a dust filter on the MPT-HL/MPT-HLC
Transceiver.
40.2 — General
type.
40.3 — RECOMMENDED MATERIALS

MPT-HL
• MPT-HL Fan Filter, Alcatel-Lucent PN: 3EM22518AA
MPT-HLC
• MPT-HLC Fan Filter, Alcatel-Lucent PN: 3DB80367AA
40.4 — RECOMMENDED TOOLS

MPT-HL
• flathead screwdriver
MPT-HLC

40 — DLP-101 MPT-HL/MPT-HLC transceiver air filter replacement
• #1 Phillips head screwdriver
40.5 — Procedure
1. WARNING: Possibility of equipment damage. Possibility of damage to
equipment. Modules contain static-sensitive devices. These devices can be
damaged by static discharge. See the Introduction for special handling
instructions.
2. Loosen the screws securing the dust filter and cover to the front of the MPT-HL/
MPT-HLC Transceiver.
3. Remove the filter assembly from the MPT-HL/MPT-HLC Transceiver.
4. Is the dust filter dirty?
a. If the dust filter is dirty, go to step 5.
b. If the dust filter is clean, go to step 6.
5. Replace filter assembly with a clean filter assembly.
6. Install the filter and cover on to the MPT-HL/MPT-HLC transceiver.
7. Tighten the screws securing the dust filter and cover to the MPT-HL/MPT-HLC
transceiver.

41 — DLP-102 SFP replacement
41.1 — Purpose
This procedure describes how to replace an SFP on a Core-E, EASv2, P8ETH, SDHACC
cards, MPT-HC/MPT-XP/9558HC (MPT ODU), MPT-HL, MPT-HLC Transceiver, or
MSS-1 shelf.
41.2 — General
address.
41.3 — Procedure
1. WARNING: Possibility of equipment damage. Modules contain static-sensitive
devices. These devices can be damaged by static discharge. See the Introduction for
2. Ensure that the extractor for the SFP, PN 3AL 81424 AAAA, is available.
3. Is the equipment protected?
4. Is the SFP port to be replaced in the Standby state?

41 — DLP-102 SFP replacement
6. Is the SFP port to be replaced the main or spare?

8. Go to step 11.
10. CAUTION: Possibility of service interruption. Replacing SFP in an unprotected
system causes a loss of traffic on ALL facilities that are associated with the SFP
and procedures.
11. Remove the fibers from the SFP to be replaced.
12. Insert the extractor into the SFP to be replaced. The extractor locks into place when it
is secure.
13. Push the lever in on the left side of the extractor to unlock the SFP from the socket.
14. Gently pull the SFP out of the slot and remove it from the card.
15. Place the new SFP into the appropriate SFP slot.
16. Reconnect the fibers to the new SFP.
17. Ensure that there are no alarms declared against the SFP or its associated equipment.
a. If there are alarms, see IXL-101 Alarm and abnormal condition clearing
procedures.
b. If there are no alarms, go to step 18.
18. Ensure that traffic is running.
a. If traffic is running, go to step 19.
b. If traffic is not running, go to step 23.
19. Is equipment protected?
22. Go to step 24.

42 — DLP-103 Core switching module
(Core-E) replacement
42.1 — Purpose
This procedure describes how to replace a Core Switching Module (Core-E) in an MSS-4/
MSS-8 shelf.
42.2 — Perquisites
Although this procedure is typically used to replace a failed (inactive) component, always
verify the component state before removal.
42.3 — General
On the Core-E flash card(s) the NE configuration and license key data is stored.
When replacing the Core-E card on an NE in the protected core configuration, and the
active Core-E card is operating properly, the flash card on the replacement Core-E card will
synchronize to the NE database stored on the active Core-E card. In this configuration a
flash card from another shelf type or Core position could be used on the replacement
Core-E card if necessary.
When replacing the Core-E card on an NE in the unprotected core configuration, it is

mandatory to transfer the flash card from the replaced Core-E card to the replacement
Core-E card. Failure to transfer the flash card will result in a loss of the NE database and a
system that may not boot up properly. At a minimum ALL NE configuration will be lost
and the NE configuration previously stored on the flash card will be applied to the NE.
In this procedure, the MSS-4/MSS-8 shelf main Core-E is resident in slot 1. The protect
Core-E is resident in slot 2 if equipped.

42 — DLP-103 Core switching module (Core-E) replacement
All MSS-4/MSS-8 shelf plug-ins can be removed and installed with power applied.
A mixture of 1+0 unprotected and/or 1+1 protected MPT-HL, MPT-HLC, or MPT ODU
radio directions are supported.
Unprotected radio configurations are supported on the Core-E card as follows:
• MPT ODU radio ports on Ethernet ports 1 through 6

• MPT-HL radio ports on Ethernet ports 5 and 6
• MPT-HLC radio ports on Ethernet ports 5 and 6
In protected radio configurations the main radio direction is supported by Core-E Ethernet
ports 1, 3, and 5. The spare (protect) radio direction is supported by Core-E Ethernet ports
2, 4, and 6 respectively. Protected radio configurations are supported on the Core-E card as
follows:
• MPT ODU radio:

• Main radio port on Ethernet ports 1, 3, and 5
• Spare radio port on Ethernet ports 2, 4, and 6
• MPT-HL protected radio ports are not supported on the Core-E
• MPT-HLC radio:
• Main radio port on Ethernet port 5
• Spare radio port on Ethernet port 6
Understand fully ALL radio direction configurations before removing the Core-E card
from the MSS-4/8 shelf.
All other Core-E user Ethernet traffic may or may not be protected within the 9500 MPR-
A or outside the 9500 MPR-A. If no protection is available, user Ethernet traffic is lost after
a failure or removal of the Core-E.
Understand fully ALL user Ethernet traffic configurations before removing the Core-E card
type.
42.4 — Procedure

1. DANGER: Possibility of personal injury. Circuit packs can be installed or

removed with the bay power on. Hazardous electrical potentials are present; use
extreme care when installing or removing circuit packs with the power on.
2. CAUTION: Possibility of service interruption. All slots must be filled with a
peripheral plug-in card or a blank panel. Failure to do so compromises the EMC
integrity and cooling air from the fan.
link requires switching the traffic onto the Standby card.
4. CAUTION: Possibility of service interruption. If the Main Core-E in slot 1 fails,
traffic/services protection and control platform protection switches to the
protected (spare) Core-E in slot 2. Loopbacks and all other manual operations,
such as Forced/Lockout switch and Tx Mute, is lost (deactivated). Alarms
previously active are newly detected and reported using notification, with a new
time stamp.
5. CAUTION: Possibility of service interruption. If the main Core-E fails, traffic
and platform data will switch to the protected Core-E automatically. Do not
remove the power from the NE during the removal and replacement of the failed
main Core-E.
6. CAUTION: Possibility of service interruption. Removing the Main Core-E in slot
1 will cause a loss of traffic on ALL radio ports, 1+0unprotected and 1+1 protected
radio ports.
7. WARNING: Possibility of equipment damage. Do not swap the main Core-E flash card
with the protect Core-E flash card which results in a system that cannot properly
boot-up.
8. WARNING: Possibility of equipment damage. Circuit packs contain static-sensitive
9. WARNING: Possibility of equipment damage. When installing a plug-in, ensure its
backplane connector is correctly engaged before applying sufficient pressure to bring
the plug-in panel flush with the front panel. Improper alignment can result in damaged
pins on the backplane connector and/or damage to the plug-in connector.
10. WARNING: Possibility of equipment damage. Plug-ins must be withdrawn and
inserted using their finger-grip fastener pulls. Never withdraw or insert using attached
cables. Pulling on the cables may damage the cable, plug-in connector, and/or plug-in
card connector attachment.
retaining screws.
12. Core-E replacement procedures
Determine Core-E configuration.
a. Does the Core-E support one or more radio directions?

b. Does the Core-E support one or more user Ethernet ports?

c. Is protection available for ALL user Ethernet ports?
13. Verify that radio protection is available for ALL radio traffic supported by the Core-E
or an appropriate maintenance window is scheduled per local practices and procedures.
14. If user Ethernet ports are provisioned, verify that protection is available for ALL user
Ethernet ports or an appropriate maintenance window is scheduled per local practices
and procedures.
15. Is it appropriate to proceed with Core-E replacement procedure?
16. Is the Core-E that is to be replaced in a protected system?
17. Protected Core-E replacement procedures
Is the power still applied to the MSS-4/MSS-8 shelf where the Core-E is to be replaced
is equipped?
18. Shelf power still applied to MSS-4/MSS-8 shelf
Verify the status of the other Core-E card (the Core-E card not being replaced) is
normal and communicates properly.
19. Is the status of the other Core-E card normal and communicates properly?
20. Is the Core-E to be replaced the main or spare?
21. CAUTION: Possibility of service interruption. Forced EPS switch may cause a hit
to traffic.
22. On the Protection Schemes tab, perform a Forced EPS Switch Main Core-E.
23. Go to step 26.
24. Lockout EPS switch may cause a hit to traffic.
25. On the Protection Schemes tab, perform a Lockout of Spare Core-E.
26. Verify that the Core-E to be replaced status is Standby.
27. Remove the Core-E to be replaced. See DLP-100 Mechanical card removal and
installation for information about how to remove the card.
28. Remove the flash card from the Core-E card removed in step 27 and install into the
replacement Core-E card.

retaining screws.
30. Install the replacement Core-E into shelf. See DLP-100 Mechanical card removal and
installation for information about how to install the card.
32. Verify the communication with the replacement Core-E using the Craft Terminal.
33. Verify the replacement Core-E status using the Craft Terminal.
34. Does the replacement Core-E communicate properly and is the status is normal?
35. Is replaced Core-E the main or spare?
36. CAUTION: Possibility of service interruption. Releasing Forced EPS switch may
cause a disruption to traffic.
37. On the Protection Schemes tab, release the Forced Switch Main Core-E.
38. Go to step 70.
39. CAUTION: Possibility of service interruption. Releasing Lockout EPS switch
40. On the Protection Schemes tab, release Lockout of Spare Core-E.
41. Go to step 70.
42. Shelf power has been turned off
Remove the Core-E to be replaced. See DLP-100 Mechanical card removal and
43. CAUTION: Possibility of service interruption. Do not swap the active Core-E
flash card (i,e, the Core-E card which is not being replaced) with a flash card from
another Core-E card.
45. Turn on shelf power and wait for the installed Core-E status LED to turn steady green.
retaining screws.

51. Does replacement Core-E communicate properly and is the status is normal?
52. Unprotected Core-E replacement procedure
Is power still applied to MSS-4/MSS-8 shelf where the Core-E to be replaced is
equipped?
53. Shelf power still applied to MSS-4/MSS-8 shelf
Caution: Possibility of service interruption. Removing an in-service card in an

unprotected system causes loss of traffic.
54. Remove Core-E to be replaced. See DLP-100 Mechanical card removal and installation
for information about how to remove the card.
Caution: Possibility of service interruption. Do not swap the main Core-E flash card
with a flash card from a different Core-E card.
Warning: Possibility of equipment damage. Failure to start both screws prior to

retaining screws.
57. Wait for the status LED to turn steady green.
60. Does the replacement Core-E communicate properly and is the status is normal?
Remove the Core-E to be replaced. See DLP-100 Mechanical card removal and

with the a flash card from a different Core-E card.

retaining screws.
installationfor information about how to install the card.
64. Turn on the shelf power.
65. Wait for the replaced Core-E status LED to turn steady green.
68. Does the replacement Core-E communicate properly and is the status normal?


43 — DLP-104 Core switching module
(Core-E) flash card replacement
43.1 — Purpose
This procedure describes how to replace a Flash Card located on the Core Switching
Module (Core-E).
43.2 — Prerequisites
verify component state before removal.
43.3 — General
In this procedure, the main Core-E is resident in slot 1. The protect Core-E is resident in
slot 2 if equipped.
For a Non Protected system, reboot for the Main Flash Card which can take up to three
minutes.
Record the MAC Address and License String using the Craft Terminal.
Note: The MAC Address can be retrieved from the Systems Setting screen and in the
configuration file, see Bridge Address. If the MAC Address information is not accessible
using the Craft Terminal, it is also located on the label adhered to the flash card being
replaced.

43 — DLP-104 Core switching module (Core-E) flash card replacement
Note: The License String can be retrieved from the Supervision/SW License screen and in
the configuration file.
After the flash card has been replaced, ALL connections in the 9500 MPR network using
the MAC Address recorded MUST be re-provisioned. The following connections types are
affected:
• L1 radio LAG (The new MAC address is collected automatically by the NE and used
to establish the cross-connections.)
• ERPS (The new MAC address is collected automatically by the NE and used to
establish the cross-connections.)
• TDM2TDM cross-connections to Ethernet ports (These cross-connections use operator
entered MAC address.)
• PDH to ETH ports
• Radio to ETH ports
• ETH to Ring ports
• TDM2ETH cross-connections to Ethernet ports (These cross-connections use operator
entered MAC address.)
Verify the following that are loaded on the replacement flash card meet the following
compatibility rules:
• The replacement flash card must be loaded with the same software version that was on
the failed flash card.
• In protected Core-E configuration, the main flash card (Core-E slot 1) and the spare
flash card (Core-E slot 2) must be loaded with the same software version.
• In an unprotected Core-E configuration the replacement flash card must be loaded
with the same software version that is running on the system. If the same version
is not available, migration rules apply; see Alcatel-Lucent 9500 MPR-A Product
Information.
• License string/capacity must be loaded with the same license string/capacity or an
updated License String which supports the current configuration.
Do not swap the main Core-E flash card with the protect Core-E flash card which results in
a system that cannot properly boot-up.
All plug-ins can be removed and installed with power applied.

type.
43.4 — Procedure
removed with bay power on. Hazardous electrical potentials are present; use
extreme care when installing or removing circuit packs with power on.
3. CAUTION: Possibility of service interruption. Removing an In-Service card in an
4. CAUTION: Possibility of service interruption. If the Main Core-E in slot 1 fails,
traffic/services protection and control platform protection switches to the
protected (spare) Core-E in slot 2. Loopbacks and all other manual operations,
such as Forced/Lockout switch and Tx Mute and tx mute, are lost (deactivated).
Alarms previously active are newly detected and reported using notification, with
a new time stamp.
5. CAUTION: Possibility of service interruption. If the main Core-E fails, traffic
and platform data switches to the protected Core-E automatically. Do not remove
power from the NE during the removal and replacement of the failed main
Core-E.
6. CAUTION: Possibility of service interruption. In a Protected system, reboot for
both Main and Spare Flash Cards can take up to 15 minutes. The flashing status
green LED indicates that a reboot is in progress. Status LED turns solid green at
completion of reboot.
7. CAUTION: Possibility of service interruption. Do not swap the main Core-E flash
card with the protect Core-E flash card which results in a system that cannot
properly boot-up.
8. CAUTION: Possibility of service interruption. Replacing the Flash Card with one
which is not correctly programmed with the correct SW version and License
String may result in a loss of traffic. STOP this procedure immediately. Perform
this procedure in its entirety after an appropriate replacement Flash Card is
available.


retaining screws.
13. Verify that the replacement Flash Card and the Flash Card to be replaced are loaded
with the same Software Version and correct License string:
• Software Version (located on the Software Download/SW Status screen and in the
configuration file)
• License string (located on the SW License screen)
14. Does the Software Version and License string match?
15. Record the Software Version and License string. Use this information to obtain an
appropriate replacement Flash Card.
16. CAUTION: Possibility of service interruption. Replacing the Flash Card with one
which is not programmed with the correct Software Version and LICENSE String
results in a loss of traffic. Perform the following activities:
a. STOP this procedure immediately.
b. Procure a replacement Flash Card loaded with the correct Software Version
and LICENSE String.
c. Perform this procedure in its entirety after an appropriate replacement Flash
Card is available.
17. Is the flash card on the Core-E to be replaced in a protected system?
18. Flash card replacement on protected Core-E configuration
Is the power still applied to MSS-4/8 shelf where flash card on the Core-E to be
replaced is equipped?

19. Shelf power still applied to MSS-4/8 shelf

Verify that the status of the other Core-E card (the Core-E card on which the flash card
is not being replaced) is normal and communicates properly.
20. Is status of the other Core-E card normal and communicates properly?
21. Is the Core-E equipped with flash card to be replaced the main or spare?
a. If Main, go to step 22.
b. If Spare, go to step 25.
22. Forced EPS switch may cause a disruption to traffic.
23. On the Protection Schemes tab, perform a Forced EPS Switch Main Core-E.
24. Go to step 26.
25. On the Protection Schemes tab, perform a Lockout EPS of Spare Core-E.
26. Verify the Core-E that is equipped with flash card to be replaced status is Standby.
27. Remove the Core-E that is equipped with flash card to be replaced. See DLP-100
Mechanical card removal and installation for information about how to remove the
card.
28. Remove the flash card from the Core-E.
card with the protect Core-E flash card which results in a system that cannot
properly boot-up.
30. Install the replacement flash card onto the Core-E.
31. WARNING: Possibility of equipment damage. Failure to start both screws prior
to tightening may cause screws to be cross threaded and possibly resulting in
broken retaining screws.
32. Install the Core-E into shelf. See DLP-100 Mechanical card removal and installation
for information about how to install the card.
34. Verify the communication with the Core-E with replacement flash card using the Craft
Terminal.
35. Verify the Core-E with replacement flash card status using the Craft Terminal.
36. Does the Core-E with replacement flash card communicate properly and status normal?
37. Is replaced Core-E the main or spare?

38. CAUTION: Possibility of service interruption. Releasing Forced EPS switch may
cause a disruption to traffic.
39. On the Protection Schemes tab, release the Forced EPS Switch Main Core-E.
40. Go to step 73.
41. On the Protection Schemes tab, release Lockout EPS of Spare Core-E.
42. Go to step 73.
Remove the Core-E equipped with flash card to be replaced. See DLP-100 Mechanical
card removal and installation for information about how to remove the card.
card with the protect Core-E flash card. This will result in a system that will not
properly boot-up.
46. Install replacement flash card onto the Core-E.
47. Turn on shelf power and wait for installed Core-E status LED to turn steady green
48. WARNING: Possibility of equipment damage. Failure to start both screws prior
to tightening may cause screw(s) to be cross threaded and possibly resulting in
broken retaining screws.
49. Install Core-E into shelf. See DLP-100 Mechanical card removal and installation for
information about how to remove the card.
51. Verify communication with the Core-E with replacement flash card using the Craft
Terminal.
52. Verify Core-E with replacement flash card status using the Craft Terminal.
53. Does Core-E with replacement flash card communicate properly and status normal?
54. Unprotected Core-E replacement procedure
Is power still applied to MSS-4/8 shelf where flash card on Core-E to be replaced is
equipped?
55. Shelf power still applied to MSS-8 shelf
Caution: Possibility of service interruption. Removing an in-service card in an

unprotected link will cause loss of traffic.

56. Remove Core-E equipped with flash card to be replaced. See DLP-100 Mechanical
card removal and installation for detailed steps to remove card.
with the protect Core-E flash card. This will result in a system that will not properly
boot-up.
58. Install replacement flash card onto the Core-E.

tightening may cause screw(s) to be cross threaded and possibly resulting in broken
retaining screws.
59. Install Core-E into shelf. See DLP-100 Mechanical card removal and installation for
61. Verify communication with the Core-E with replacement flash card using the Craft
Terminal.
63. Does Core-E with replacement flash card communicate properly and status normal?
Remove Core-E equipped with flash card to be replaced. See DLP-100 Mechanical
card removal and installation for information about how to remove the card.
with the protect Core-E flash card. This will result in a system that will not properly
boot-up.
66. Install the replacement flash card onto the Core-E.

tightening may cause screw(s) to be cross threaded and possibly resulting in broken
retaining screws.

67. Install the Core-E into shelf. See DLP-100 Mechanical card removal and installation
for information about how to remove the card.
68. Turn on the shelf power and wait for the status LED to turn steady green.
69. Verify the communication with the Core-E with replacement flash card using the Craft
Terminal.
71. Does the Core-E with replacement flash card communicate properly and status normal?
72. Re-provision Cross-Connections
With the flash card replaced and the Core-E card is communicating properly and it’s
status is normal, L1 radio LAGs, ERPS, and ALL connections in the 9500 MPR
network using the MAC Address recorded earlier in the procedure, MUST be
re-provisioned on the appropriate node(s) in the 9500 MPR network.
• L1 radio LAG (The new MAC address is collected automatically by the NE and
used to establish the cross-connections.)
• ERPS (The new MAC address is collected automatically by the NE and used to
establish the cross-connections.)
• TDM2TDM cross-connections to Ethernet ports (These cross-connections use
operator entered MAC address.)
• TDM2ETH cross-connections to Ethernet ports (These cross-connections use
operator entered MAC address.)
To re-provision L1 Radio LAG cross-connections, the L1 Radio LAG
cross-connections MUST be deleted and re-provisioned. For detailed steps to delete
and provision a L1 Radio LAG cross-connections, refer to Alcatel-Lucent 9500 MPR-
A Operation and Administration, DLP-140.
73. Re-provision ALL L1 Radio LAG cross-connections at the node the flash card was
replaced.
To re-provision ERPS cross-connections, the ERPS cross-connections MUST be
deleted and re-provisioned. For detailed steps to delete and provision ERPS
cross-connections, refer to Alcatel-Lucent 9500 MPR-A Operation and Administration,
DLP-142.
74. Re-provision ALL ERPS cross-connections at the node the flash card was replaced.

To re-provision cross-connections, the cross-connection must be deleted and

re-provisioned using the new MAC address of the replacement flash card as the
Destination MAC address. These cross-connections are located at the entry point of the
PDH signal whose destination is the node where the flash card was replaced. For
detailed steps to delete and provision cross-connections refer to Alcatel-Lucent
9500 MPR-A Operation and Administration, DLP-112, DLP-126, DLP-142, DLP-151,
and DLP-152.
75. Re-provision ALL TDM2TDM, PDH to ETH cross-connections on ALL affected
nodes in the 9500 MPR network with the new MAC address of the replacement flash
card.
76. Re-provision ALL TDM2TDM, RADIO to ETH cross-connections on ALL affected
card.
77. Re-provision ALL TDM2TDM, ETH to Ring cross-connections on ALL affected
card.
78. Re-provision ALL TDM2ETH, PDH to ETH cross-connections on ALL affected nodes
in the 9500 MPR network with the new MAC address of the replacement flash card.
79. Re-provision ALL TDM2ETH, RADIO to ETH cross-connections on ALL affected
card.
80. Re-provision ALL TDM2ETH, ETH to Ring cross-connections on ALL affected nodes
in the 9500 MPR network with the new MAC address of the replacement flash card.
81. Verify ALL affected traffic within the 9500 MPR network are operating properly.
82. Go to step 84.


44 — DLP-105 Ethernet Access Switch
replacement (EASv2 and P8ETH)
44.1 — Purpose
This procedure describes how to replace an Ethernet Access Switch (EASv2 and P8ETH)
circuit pack.
Within this procedure the EASv2 and P8ETH cards will be referred to as “EAS”.
44.3 — General
The EAS is supported in MSS-8 slots 3 to 8 and MSS-4 slots 3 and 4. The EAS does not
support equipment protection.
A mixture of 1+0 unprotected and/or 1+1 protected MPT-HL, MPT-HLC, or MPT ODU
radio directions are supported.
In unprotected radio configurations the EAS card is supported in any of the transport
MSS-4/8 slots, up to four radio directions per EAS card.
In protected radio configurations the main radio direction is supported by a EAS equipped
in slots 3, 5, and/or 7. The spare (protect) radio direction is supported by a EAS equipped
in the slots directly across from the main (slots 4, 6, and/or 8).
Understand fully ALL radio direction configurations before removing the EAS card from
the MSS-4/8 shelf.

44 — DLP-105 Ethernet Access Switch replacement (EASv2 and P8ETH)
All other EAS user Ethernet traffic is unprotected within the EAS. User Ethernet traffic
switching is controlled/performed outside the 9500 MPR-A if available. If no protection is
available, user Ethernet traffic is lost after a failure or removal of the EAS.
Understand fully ALL user Ethernet traffic configurations before removing the EAS card
type.
44.4 — Procedure
2. CAUTION: Possibility of service interruption. All slots must be filled with either
a peripheral plug-in card or a blank panel. Failure to do so compromises the EMC
3. CAUTION: Possibility of service interruption. Removing an In-Service radio port
in an unprotected direction causes loss of traffic. Removing an Active radio port
in a 1+1 protected direction requires switching the traffic onto the Standby radio
port.
4. CAUTION: Possibility of service interruption. 1+1 protected MPT-HL,
MPT-HLC, and MPT ODU directions may be protected within the EAS. All other
Ethernet traffic is unprotected within the 9500 MPR-A. Ethernet traffic switching
is controlled/performed outside the 9500 MPR-A if available. If no protection is
available, Ethernet traffic is lost after a failure or removal of the EAS.
5. CAUTION: Possibility of service interruption. In 1+1 protected MPT-HL,
MPT-HLC, and MPT ODU radio direction configurations, the MPT-HL,
MPT-HLC, and MPT ODU Ethernet traffic switching is controlled by the 9500
MPR-A. Main and spare MPT-HL, MPT-HLC, and MPT ODU hops are
provisioned on a per direction basis. If the EAS card in slot 3, 5, or 7 fails, Active
MPT-HL, MPT-HLC, and MPT ODU switches to the spare radio hop in slot 4, 6,
or 8. If the EAS card in slot 4, 6, or 8 fails, Active MPT-HL, MPT-HLC, and MPT
ODU switches to the main radio hop in slot 3, 5, or 7.

6. CAUTION: Possibility of service interruption. In unprotected Ethernet

configurations, Ethernet traffic switching is controlled/performed outside the
9500 MPR-A if available. If no protection is available, Ethernet traffic is lost after
a failure or removal of the EAS.
retaining screws.
11. EAS replacement procedures
Determine EAS configuration.
a. Does the EAS support one or more radio directions?
b. Are the radio directions protected?
c. Does the EAS support one or more user Ethernet ports?
d. Is external protection available for ALL user Ethernet ports?
e. Is protection available for ALL radio directions?
12. Verify that radio protection is available for ALL radio traffic supported by the EAS or
an appropriate maintenance window is scheduled per local practices and procedures.
13. If user Ethernet ports are provisioned, verify that external protection is available for
ALL user Ethernet ports or an appropriate maintenance window is scheduled per local
14. Is it appropriate to proceed with EAS replacement procedure?
15. Does the EAS to be replaced support protected radio directions?
16. Protected radio directions EAS replacement procedure

Caution: Possibility of service interruption. 1+1 protected MPT-HL, MPT-HLC, or MPT

ODU directions may be protected within the 9500 MPR-A. ALL other EAS Ethernet
traffic is unprotected within the 9500 MPR-A. Unprotected Ethernet traffic switching
is controlled/performed outside the 9500 MPR-A if available. If no protection is
available, Ethernet traffic will be lost upon a failure or removal of the EAS.
Caution: Possibility of service interruption. For any unprotected MPT-HL, MPT-HLC, or

MPT ODU direction supported by the EAS card being replaced, its Ethernet traffic is
lost after a failure or removal of the EAS.
17. In which slot does the EAS card being replaced reside?
a. If 3, 5, or 7, go to step 18.
b. If 4, 6, or 8, go to step Caution:.
18. Forced EPS/HSB/Rx Radio switching traffic may cause a hit to traffic.
19. In protected radio configurations configured with 1+1 revertive operation, inserting the
EAS card in slot 3, 5, or 7, may cause a disruption to the protected traffic. To prevent
a larger impact to protect traffic, always perform a Forced EPS, HSB, and RX Radio to
spare before inserting the EAS card in slot 3, 5, or 7.
20. Perform a Forced EPS Switch Main, MPT-HL/MPT-HLC/MPT ODU radio hop to
Spare MPT-HL/MPT-HLC/MPT ODU hop port.
21. Perform a Forced HSB Switch Main, MPT-HL/MPT-HLC/MPT ODU radio hop to
Spare MPT-HL/MPT-HLC/MPT ODU radio hop.
22. Perform a Forced RX Radio Switch Main, MPT-HL/MPT-HLC/MPT ODU radio hop
to Spare MPT-HL/MPT-HLC/MPT ODU radio hop.
23. Repeat steps 20 to 22 until all of the MPT-HL/MPT-HLC/MPT ODU radio directions
are Forced Switch to Spare, then go to step 28.
Caution: Possibility of service interruption Lockout EPS/HSB/Rx Radio switching traffic

may cause a hit to traffic.
24. Perform a Lockout EPS of Spare MPT-HL/MPT-HLC/MPT ODU radio direction.

25. Perform a Lockout HSB of Spare MPT-HL/MPT-HLC/MPT ODU radio direction.
26. Perform a Lockout Rx Radio of Spare MPT-HL/MPT-HLC/MPT ODU radio direction.
27. Repeat steps 24 to 26 until all MPT-HL/MPT-HLC/MPT ODU radio direction are
Lockout of Spare, then go to step 28.
28. For the 1+1 protected radio hops supported by the EAS being replaced, verify that all
MPT-HL/MPT-HLC/MPT ODU radio hops status is Standby.
29. Verify that all cable connections to the EAS card to be replaced are properly labeled.

30. Disconnect all cables that are connected to the front of the EAS.
31. Remove EAS to be replaced. See DLP-100 Mechanical card removal and installation
for information about how to remove card.
32. Remove the SFPs from the EAS.
33. Install the SFPs into the replacement EAS.
Caution: Possibility of service interruption. Failure to perform steps 20 to 23 on

protected radio directions configured with 1+1 revertive operation, may cause a
larger disruption to the traffic upon inserting the EAS card in slot 3, 5, or 7.
Caution: Possibility of service interruption. Failure to start both screws prior to

retaining screws.
34. Install the replacement EAS into the shelf. See DLP-100 Mechanical card removal and
36. Connect all cables to the front of the EAS that were disconnected in step 30.
37. Verify the communication with the replacement EAS using the Craft Terminal.
38. Verify that the status is normal for the replacement EAS.
39. Verify that the Links are up for all Ethernet ports that are associated with the
replacement EAS.
40. Does the replacement EAS communicate properly? Is the status normal? Are all
Ethernet port Links up?
41. Verify the replacement EAS alarms and capable of carrying Ethernet traffic using the
Alarm Monitor and Craft Terminal.
42. Is the replacement EAS status normal and is it capable of carrying Ethernet traffic?
43. In which slot does the EAS card being replaced reside?
a. If 3, 5, or 7, go to step 44.
b. If 4, 6, or 8, go to step 48.
44. Release the Forced EPS Switch Main, MPT-HL/MPT-HLC/MPT ODU radio hop to
45. Release the Forced HSB Switch Main, MPT-HL/MPT-HLC/MPT ODU radio hop to

46. Release the Forced Rx Radio Switch Main, MPT-HL/MPT-HLC/MPT ODU radio hop
to Spare MPT-HL/MPT-HLC/MPT ODU radio hop.
47. Repeat steps 44 to 46 until all MPT-HL/MPT-HLC/MPT ODU radio directions
Forced Switch Main are released, then go to step 67.
48. Release the Lockout EPS Spare MPT-HL/MPT-HLC/MPT ODU radio direction.
49. Release the Lockout HSB Spare MPT-HL/MPT-HLC/MPT ODU radio direction.
50. Release the Lockout Rx Radio Spare MPT-HL/MPT-HLC/MPT ODU radio direction.
51. Repeat steps 48 to 50 until all MPT-HL/MPT-HLC/MPT ODU radio directions
Lockout of Spare are released, then go to step 67.
52. Unprotected EAS radio direction(s) replacement procedure
Caution: Possibility of service interruption. In unprotected EAS radio direction

configurations, ALL Ethernet traffic is lost upon removal of the SFP connection to the
EAS.
Caution: Possibility of service interruption. All other EAS Ethernet traffic is

unprotected within the 9500 MPR-A. All other Ethernet traffic switching is controlled/
performed outside the 9500 MPR-A if available. If no protection is available, Ethernet
traffic is lost after removal of the Ethernet cabling.
Caution: Possibility of service interruption. All 1+0 unprotected MPT-HL, MPT-HLC, or

MPT ODU traffic is unprotected within the 9500 MPR-A. Their Ethernet traffic
supported by a failed or removed EAS is lost upon a failure or removal of the EAS.
53. Verify that all cable connections to the EAS card to be replaced are properly labeled.
54. Disconnect the Ethernet cables, one at a time.
55. Remove the EAS to be replaced. See DLP-100 Mechanical card removal and
installation for information about how to remove card.
56. Remove the SFPs from EAS to be replaced.
57. Install the SFPs into the replacement EAS.

retaining screws.
58. Install the replacement EAS into the shelf. See DLP-100 Mechanical card removal and

60. Connect all cables to the front of the EAS that you disconnected in step 54.
61. Verify the communication with the replacement EAS using the Craft Terminal.
62. Verify the status is normal for the replacement EAS.
63. Verify the Link is up for all Ethernet/radio ports associated with the replacement EAS.
a. Does the replacement EAS communicate properly? Is the status normal? Are all
Ethernet/radio port Links up?
c. If no, go to step 66.
64. Verify the replacement EAS alarms and capable of carrying Ethernet traffic using the
Alarm Monitor and Craft Terminal.
65. Is the replacement EAS status normal, and capable of carrying Ethernet traffic?


45 — DLP-106 MSS-4/8 shelf FAN
replacement
45.1 — Purpose
This procedure describes how to replace a MSS-4/8 shelf FAN card.
A replacement FAN card must be available on-site before starting this procedure.
45.3 — General
type.
45.4 — Procedure

45 — DLP-106 MSS-4/8 shelf FAN replacement

retaining screws.
4. Confirm the replacement MSS-4/8 FAN card is available and of the same type installed
in the MSS-4/8 shelf.
5. Disconnect the housekeeping alarm and Control cable if present.
6. Remove the FAN card. See DLP-100 Mechanical card removal and installation for
retaining screws.
8. Install the replacement FAN card. See DLP-100 Mechanical card removal and
9. Connect housekeeping alarm and Control cable if removed in step 5.
10. Verify that the FAN card is operating properly.
11. Verify the communication with the replacement FAN card.
12. Does the FAN card operate properly, communicate properly, and the status is normal?
a. If yes, go to step 14

46 — DLP-107 MOD300 (radio modem)
replacement
46.1 — Purpose
This procedure describes how to replace a MOD300.
46.3 — General
The Radio (MOD300) cards can be installed in any of the universal slots (3 to 8).
The MSS-8 can be configured with a maximum of six optional MOD300 cards; three
protected cards, six non-protected cards, or a combination of protected and non-protected
cards.
In protected radios, the main MOD300 is resident in slots 3, 5, and/or 7. The protect
MOD300 is resident in slots 4, 6, and/or 8. The main and protected cards must be plugged
in side-by-side.
In an unprotected radio, performing the MOD300 removal and replacement procedure

causes loss of traffic. In a protected system, the procedure is an in-service but not a hitless
procedure.
Disconnecting the MOD300 from the MSS-8 backplane removes power to the ODU300,
and can cause a disruption on traffic.

46 — DLP-107 MOD300 (radio modem) replacement
type.
46.4 — Procedure
4. CAUTION: Possibility of service interruption. In protected radio configurations,
the Main MOD300 cards reside in slots 3, 5, and/or 7. The spare MOD300 cards
reside in slots 4, 6, and/or 8.
6. WARNING: Possibility of equipment damage. Possibility of damage to equipment.
Circuit packs contain static-sensitive devices. These devices can be damaged by static
discharge. See the Introduction for special handling instructions.
9. MOD300 replacement procedures
Is the MOD300 to be replaced in a protected system?
10. Forced EPS switching traffic causes a disruption to traffic.
11. Is MOD300 to be replaced the main or spare?


15. Go to step 19.
19. Verify that the MOD300 to be replaced status is Standby.
21. Remove the MOD300 to be replaced.
22. Disconnect the IF in/out cable.
23. Install the replacement MOD300 into shelf but do not seat the card at this time.
24. Connect the IF in/out cable.
25. Seat the replacement MOD300 into shelf and wait for the status LED to turn steady
green or amber.
26. Verify the replacement MOD300 is free of alarms using the Alarm Monitor.
27. Is the replacement MOD300 status LED to turn steady green or amber and free of
alarms?
28. Is the replacement MOD300 in a protected system?
29. Releasing Forced EPS switch causes a disruption to traffic.
30. Release the Forced/Lockout EPS Switch using Craft the Terminal.
33. Go to step 35.


47 — DLP-108 MPT-HL/MPT-HLC
transceiver replacement
47.1 — Purpose
This procedure describes how to replace a Microwave Packet Transport (MPT-HL/
MPT-HLC) transceiver.
47.3 — General
The MPT-HL/MPT-HLC transceiver card can be installed in either MPT-HL shelf slots 1
or 2.
The MPT-HL shelf can be configured with a maximum of two MPT-HL/MPT-HLC

Transceiver cards; one protected pair, or two unprotected MPT-HL/MPT-HLC transceiver
cards.
In protected radios, the main MPT-HL/MPT-HLC transceiver is resident in slot 1. The

spare MPT-HL/MPT-HLC Transceiver is resident in slot 2.
In an unprotected radio, performing a MPT-HL/MPT-HLC transceiver removal and

replacement procedure causes loss of traffic. In a protected system, the procedure is an in-
service but not a hitless procedure.
type.

47 — DLP-108 MPT-HL/MPT-HLC transceiver replacement
47.4 — Procedure
2. CAUTION: Possibility of service interruption. Removing an in-service MPT-HL/
MPT-HLC transceiver in an unprotected link causes loss of traffic. Removing an
in-service card in a protected MPT-HL/MPT-HLC transceiver requires switching
the traffic onto the spare channel.
3. CAUTION: Possibility of service interruption. In protected MPT-HL/MPT-HLC
Transceiver configurations, the Main MPT-HL/MPT-HLC transceiver reside in
slot 1. The spare MPT-HL/MPT-HLC transceiver reside in slot 2.
4. CAUTION: Possibility of service interruption. This is an out of service procedure
for unprotected configurations. To avoid disruption of traffic on protected
configurations, switch traffic to Standby MPT-HL/MPT-HLC transceiver.
retaining screws.
9. MPT-HL/MPT-HLC transceiver replacement procedures
Is the MPT-HL/MPT-HLC transceiver to be replaced in a protected system?
10. CAUTION: Possibility of service interruption. Forced EPS and HSB switching
traffic causes a disruption to traffic.
11. Is the MPT-HL/MPT-HLC transceiver to be replaced the main or spare?


15. Go to step 19.
19. Verify that the MPT-HL/MPT-HLC Transceiver to be replaced status is Standby.
20. CAUTION: Possibility of service interruption. Removing power to an in-service
MPT-HL/MPT-HLC transceiver in an unprotected link causes a loss of traffic.
21. Position the MPT-HL/MPT-HLC transceiver PA switch to the OFF ‘0’ position.
22. Verify that all cable connections to the MPT-HL/MPT-HLC transceiver to be replaced
are properly labeled.
23. Disconnect the GigE cable (optical or Molex) from the SFP port on the MPT-HL/
24. Remove SFP from MPT-HL/MPT-HLC transceiver, if required.
25. Disconnect all remaining cables.
26. Loosen the screws securing the MPT-HL/MPT-HLC transceiver to the MPT-HL shelf.
See DLP-100 Mechanical card removal and installation for information about how to
remove the card.
27. Pull out on the MPT-HL/MPT-HLC transceiver to disconnect from the shelf backplane
connectors.
28. Remove the MPT-HL/MPT-HLC transceiver from the shelf.
29. Insert the replacement MPT-HL/MPT-HLC transceiver in the shelf but do not seat it at
this time.
30. Connect the power cable to the replacement MPT-HL/MPT-HLC Transceiver and
apply power.
31. Slowly push the replacement MPT-HL/MPT-HLC Transceiver into the shelf until
contact is made with the alignment pins/backplane connectors. See DLP-100
Mechanical card removal and installation for information about how to install the card.
32. Apply steady pressure and push in on the replacement MPT-HL/MPT-HLC transceiver
until the MPT-HL/MPT-HLC Transceiver is seated in the backplane connectors.
tightening may cause screws to be cross threaded and possibly result in broken
retaining screws.
34. Tighten the screws securing MPT-HL/MPT-HLC Transceiver to MPT-HL shelf.

35. Verify that the RF cables on shelf backplane connectors on rear of shelf have not been
loosened by installation of the MPT-HL/MPT-HLC Transceiver. Tighten cables to no
more than 19 in lbs, if required.
36. Install the SFP into SFP receptacle (if required).
37. (Optional) Wait until the status LED on the MPT-HL/MPT-HLC Transceiver is
blinking red. Blinking red indicates that software is loaded but the Transceiver is not
communicating with the EAS card.
38. Connect the GigE cable (optical or Molex) into the SFP port on MPT-HL/MPT-HLC
transceiver.
39. Connect all cables to the front of the MPT-HL/MPT-HLC transceiver that were
disconnected in step 25.
40. Verify that the MPT-HL/MPT-HLC transceiver PA switch is in the OFF ‘0’ position.
41. Position the MPT-HL/MPT-HLC transceiver PA switch to the ON ‘1’ position.
42. Ensure that the MPT-HL/MPT-HLC transceiver PA (Power Amplifier) switch is in the
“On” (1) position.
43. Wait for the MPT-HL/MPT-HLC transceiver to finish booting.
44. Verify that the replacement MPT-HL/MPT-HLC transceiver status LED turns steady
green or yellow.
45. Verify that the replacement MPT-HL/MPT-HLC transceiver is alarm free using the
Alarm Monitor.
46. Is replacement MPT-HL/MPT-HLC transceiver status LED steady green or yellow,
and alarm free?
47. Is the replacement MPT-HL/MPT-HLC transceiver in a protected system?
48. CAUTION: Possibility of service interruption. Releasing Forced EPS and HSB
switch causes a disruption to traffic.
52. Go to step 54.

48 — DLP-109 ODU300 replacement
48.1 — Purpose
This procedure describes how to replace a Outdoor Unit (ODU300).
Before starting, verify that the replacement ODU300 matches the failed ODU300 using the
following procedure.
1. Obtain part number of failed ODU300 on inventory screen.

2. Verify part number of replacement ODU300, located on identification label, matches
part number of failed ODU300.
48.3 — General
In protected radios, the associated main MOD300 is resident in slots 3, 5, and/or 7. The
associated protect MOD300 is resident in slots 4, 6, and/or 8. The main and protected cards
must be plugged in side-by-side.
Disconnecting the MOD300 from the MSS-8 backplane removes power to the ODU300,
and can cause a disruption on traffic.
In an unprotected radio, removing MOD300 causes loss of traffic. In a protected radio,

removing MOD300 can cause a disruption on traffic.

type.
See the Alcatel-Lucent 9500 MPR-A Installation Practices Charts 10 and 11 for
information about how to physically remove and install the ODU300 to be replaced in this
procedure.
48.4 — Procedure
1. DANGER: Possibility of personal injury. Exposure to energy radiated at
microwave frequencies can cause eye injury and eventual blindness. Do not look
directly into any unterminated waveguide port.
3. CAUTION: Possibility of service interruption. In an unprotected radio,
performing the ODU300 removal and replacement procedure will cause loss of
traffic. In a protected system the procedure is an in-service but not a hitless
procedure. Disconnecting the MOD300 from the MSS-8 backplane to remove
power to the ODU300 can cause a disruption on traffic.
4. WARNING: Possibility of equipment damage. Failure to disconnect power to the
ODU300 by disconnecting the associated MOD300 card from the MSS-8 backplane
can result in damage to the MOD300 card and can cause damage to the ODU300.
6. Is the ODU300 to be replaced in a protected system?
7. Is the MOD300 associated with the ODU300 to be replaced the main or spare?
9. Go to step 11.
10. Perform Lockout EPS Switch using Craft Terminal.
11. Verify that the MOD300 card, associated with the failed ODU300 status is Standby.

12. On the MSS-8, pull out on the MOD300 card, associated with the failed ODU300, to
disconnect the MOD300 card from the MSS-8 backplane.
13. Disconnect the IF in/out cable.
Note: The procedure to Remove an ODU300 is dependent on the ODU300 mounting and
how the ODU300 is configured. The procedure to remove an ODU300 is the reverse of
ODU300 installation. See Alcatel-Lucent 9500 MPR-A Installation Practices, Charts 10 and
11 for information about how to physically install an ODU300.
14. Disconnect and remove the failed ODU300. See Alcatel-Lucent 9500 MPR-A
Installation Practices for more information.
15. Install the replacement ODU300. See Alcatel-Lucent 9500 MPR-A Installation
Practices for more information.
16. Connect the IF in/out cable.
17. Reinstall the MOD300 card to restore power to the MOD300 and replacement
ODU300.
18. On the MOD300 card front panel, verify that there are no alarms.
19. Open the WebEML Measurements screens for the MOD300 card that is connected to
the replaced ODU300.
20. On the Measurements window, enter 15 minutes Measurement Interval.
21. On the Measurements window, select 2 sec Sample Time.
22. On the Measurements window, click on the Start button to start measurements. The
Graphics window appears.
23. On Measurement graphics window, check the Details box. The Tx and Rx dBm Power
Levels Details table appears.
24. On Tx and Rx dBmPower Levels Details table, verify the Tx Local End and Rx Far End
power levels.
25. Is the replacement ODU300 status normal and capable of carrying traffic?
26. Is the replacement ODU300 in a protected system?
27. Releasing Forced/Lockout switch may cause a disruption to traffic.
29. Go to step 31.


49 — DLP-110 P2E3DS3 (2-Port DS3)
replacement
49.1 — Purpose
This procedure describes how to replace a P2E3DS3 card.
49.3 — General
The DS3 P2E3DS3 card can be installed in any of the universal MSS-8 slots (3 through 8).
The MSS-8 can be configured with a maximum of six optional P2E3DS3 cards; three
protected pairs, six unprotected cards, or a combination of protected pairs and unprotected
cards.
In protected DS3 configurations, the main P2E3DS3 is resident in slots 3, 5, and/or 7. The
spare P2E3DS3 is resident in slots 4, 6, and/or 8 respectively. The main and spare cards
In unprotected DS3 configurations, performing the P2E3DS3 removal and replacement

procedure causes loss of traffic. In a protected system the procedure is an in-service but not
a disruptionless procedure.
type.

49 — DLP-110 P2E3DS3 (2-Port DS3) replacement
49.4 — Procedure
3. CAUTION: Possibility of service interruption. In protected DS3 configurations,
the Main P2E3DS3 cards reside in slots 3, 5, and/or 7. The Spare P2E3DS3 cards
retaining screws.
9. P2E3DS3 replacement procedures
Is the P2E3DS3 to be replaced in a protected system?
11. Is the P2E3DS3 to be replaced the main or spare?


13. Go to step 15.
15. Verify that the P2E3DS3 to be replaced status is Standby.
unprotected configuration causes a loss of traffic.
17. Verify that all cable connections to the P2E3DS3 card to be replaced are properly
labeled.
18. Remove the P2E3DS3 to be replaced. See DLP-100 Mechanical card removal and
19. Disconnect the DS3 input and output cables.
20. Install the replacement P2E3DS3 into the shelf, but do not seat the card at this time. See
DLP-100 Mechanical card removal and installation for information about how to install
card.
21. Connect the DS3 input and output cables.
retaining screws.
23. Install the replacement P2E3DS3 into the shelf.
25. Verify the replacement P2E3DS3 alarms, that the status is normal, and capable of
carrying traffic using the Alarm Monitor and Craft Terminal.
26. Is the replacement P2E3DS3 status normal and capable of carrying traffic?
27. Is the replacement P2E3DS3 in a protected system?
30. Go to step 32.


50 — DLP-111 P32E1DS1 (32-Port DS1)
replacement
50.1 — Purpose
This procedure describes how to replace a P32E1DS1 card.
50.3 — General
The DS1 P32E1DS1 card can be installed in any of the universal MSS-8 slots (3 to 8).
The MSS-8 can be configured with a maximum of six optional P32E1DS1 cards; three
protected cards, six unprotected cards, or a combination of protected and unprotected cards.
In protected DS1 configurations, the main P32E1DS1 is resident in slots 3, 5, and/or 7. The
spare P32E1DS1 is resident in slots 4, 6, and/or 8 respectively. The main and spare cards
In unprotected DS1 configurations, performing the P32E1DS1 removal and replacement

a hitless procedure.
type.

50.4 — Procedure
a peripheral plug-in card or a blank panel. Failure to do so will compromise EMC
3. CAUTION: Possibility of service interruption. In protected DS1 configurations,
the Main P32E1DS1 cards reside in slots 3, 5, and/or 7. The spare P32E1DS1 cards
retaining screws.
9. P32E1DS1 replacement procedures
Is the P32E1DS1 to be replaced in a protected system?
10. Forced EPS switching traffic causes a disruption to traffic.
11. Is the P2E3DS3 to be replaced main or spare?


13. Go to step 15.
15. Verify that the P32E1DS1 to be replaced status is Standby.
17. Verify that all cable connections to the P32E1DS1 card to be replaced are properly
labeled.
18. Remove the P32E1DS1 to be replaced. See DLP-100 Mechanical card removal and
installation for information about how to remove card.
19. Disconnect DS1 cables.
20. Install the replacement P32E1DS1 into shelf but do not seat the card at this time. See
DLP-100 Mechanical card removal and installation for information about how to
remove card.
21. Connect the DS1 input and output cables.
retaining screws.
23. Seat the replacement P32E1DS1 into the shelf.
25. Verify the replacement P32E1DS1 alarms, that the status is normal, and capable of
26. Is the replacement P32E1DS1 status normal, and capable of carrying traffic?
27. Is the replacement P32E1DS1 in a protected system?
30. Go to step 32.


51 — DLP-112 Clean fiber-optic
connectors
51.1 — Purpose
This procedure describes the recommended instructions to clean fiber-optic connectors
found in Alcatel-Lucent equipment.
Anyone who performs this procedure must be familiar with cleaning fiber-optic connectors
and with the specific system on which the procedure is to be performed.
This procedure must not be performed on traffic-carrying equipment. If a system is in

service, traffic must be removed from equipment to be cleaned.
51.3 — Recommended Tools

The following tools must be available for this procedure:
• Optical power meter with standard accessories

• Inspection microscope, 200X to 400X—Aerotech World Trade Ltd. AWT200 or
AWT300
• Anti-static lint-free swab—Texwipe PN TX757E
• CLETOP fiber-optic cleaner, Aerotech World Trade Ltd. PN 14100500 for all
fiber-optic connectors except bulkhead type
• CLETOP 2.5mm Stick-Type cleaner- Aerotech World Trade Ltd. PN 14100400, box
of 200
• CLETOP 1.25mm Stick-Type cleaner - Aerotech World Trade Ltd. PN 14100401 box
of 200

51 — DLP-112 Clean fiber-optic connectors
• Optical removal and cleaning tool—Alcatel-Lucent PN 3EM07060AAAA

• Penlight (pocket-style flashlight)
• Laser safety glasses
51.4 — General
If the cleaning method described in this procedure does not produce acceptable results, the
connector may need to be replaced.
type.
51.5 — Procedure
1. DANGER: Possibility of personal injury. DO NOT LOOK INTO FIBER-OPTIC
CONNECTOR. Laser infrared radiation is present when fiber-optic connector is
open and optical interface is installed. Laser infrared radiation is not visible to
naked eye or with laser safety glasses.
2. DANGER: Possibility of personal injury. Ensure no optical power is connected to
fiber being tested. An optical power meter must be used to ensure all optical
power has been removed.
3. WARNING: Possibility of equipment damage. Do not disassemble cards to clean
fibers. Disassembling card could cause damage to optical splice and could void
warranty.
4. WARNING: Possibility of equipment damage. To preserve integrity of fiber-optic
connectors, observe the following precautions:
• Do not use cleaning swabs more than once.
• Do not use alcohol or any type of liquid to clean fiber-optic connectors.
• Do not use canned air to clean fiber-optic connectors. Canned air propellant leaves
residue that clouds fiber-optic connectors.
• Do not touch polished optical surface of fiber-optic connector. Oil from skin can
degrade performance of fiber-optic connector and attract dust particles.
• Always use protective covers to protect disconnected fiber-optic connectors. When
protective covers are not in use, store them in a clean container. Do not store
protective covers in clothes pocket.

Figure 51.1 — Fiber-optic connector inspection
PARTICLES
OIL FILM AND PARTICLES

ON CLADDING AND IN
CORE AREA
FIBER CONTAMINATED FIBER CONTAMINATED

WITH SOLID PARTICLES FIBER WITH OIL (FINGERPRINT)
CLADDING CORE
FERRULE
(SHAPE CAN VARY
BY CONNECTOR TYPE)
CLEAN FIBER
129-1280-1
021607
5. Use an optical power meter to determine if light is coming out of fiber-optic connector.
6. Does the optical power meter detect light coming out of fiber-optic connector?
7. Find a laser transmission source and disable it.
8. Remove the fiber-optic connector from receptacle, if necessary.
9. Use an inspection microscope to inspect fiber-optic connector. See Figure 51.1 for
examples of clean and contaminated fibers. Use the following criteria to determine
clean fiber:
a. Fiber core must have no contaminants or defects.
b. Fiber cladding must have no contaminants. Minor defects (pits and scratches) are
acceptable.
c. Fiber ferrule may not have contaminants or defects that interfere with fiber-optic
connector mating.
10. Is the fiber-optic connector clean?
11. Select the type of connector to clean. See Figure 51.2 and Figure 51.3 for connector
types.

a. If FC, SC, MU, LC, or ST/STII fiber-optic connector, go to step 12.

b. If bulkhead connectors, go to step 16.
Figure 51.2 — Fiber-optic connector types, illustrations
FC CONNECTOR SC CONNECTOR ST CONNECTOR
MU FIBER CONNECTOR LC FIBER CONNECTOR

No3016
Figure 51.3 — Fiber-optic connector types, photographs
SC CONNECTOR FC CONNECTOR
ST/STII CONNECTOR
No3017
12. FC, SC, MU, LC, or ST/STII fiber-optic connector

Holding the CLETOP fiber-optic cleaner with one hand, use metal lever to open metal
slide and expose the cleaning surface. Do not release the lever.
13. Place the fiber ferrule firmly against the CLETOP fiber-optic cleaner cleaning surface,
rotate the ferrule 90 degrees, then gently wipe the ferrule along cleaning surface one
time in one direction only.
14. Release the metal lever.
15. Go to step 19.

16. Bulkhead connectors

Select the appropriate CLETOP Stick-Type to clean bulkhead connector for fiber optic
connection.
a. For FC, SC, and ST bulkhead connectors use the CLETOP 2.5mm Stick-Type
cleaner.
b. For LC and MU bulkhead connectors use the CLETOP 1.25mm Stick-Type
cleaner.
17. Insert the CLETOP swab into the optical bulkhead adapter and gently twist/wipe to
clean fiber-optic interface. Discard the swab after each use.
18. Are there more fiber optic bulkheads to clean?
19. Inspect connector
Use an inspection microscope to inspect fiber-optic connector. See Figure 51.1 for
examples of clean and contaminated fibers. Use the following criteria to determine
clean fiber:
a. Fiber core must have no contaminants or defects.
b. Fiber cladding must have no contaminants. Minor defects (pits and scratches) are
acceptable.
c. Fiber ferrule may not have contaminants or defects that interfere with fiber-optic
connector mating.
21. Clean and inspect the fiber-optic connector up to five more times.
b. If no, contact the next level of support.
23. Remove the permanent plastic cap retainer, if applicable. Follow customer practices.
24. Are there more fiber-optic connectors to clean?


52 — DLP-113 System power down and
power up
52.1 — Purpose
This procedure describes how to power down and power up a 9500 MPR-A system.
52.2 — General
When powering down the system, you must shut down the transmitters first, remove power
from the MPT-HC/MPT-XP/9558HC (MPT ODU)s, MPT-HL/MPT-HLC transceivers,
and MOD300s before you remove power from the MSS-1/4/8 shelf.
When powering up the system, you must power up the MSS-1/4/8 shelf first, power up the
MPT ODUs, MPT-HL/MPT-HLC transceivers, and MOD300s, before bringing up the
transmitters.
All cards can be removed and installed with power applied.
type.
52.3 — Procedure

52 — DLP-113 System power down and power up

5. Select an action?
a. If the system power is down, go to step 6.
b. If the system power is up, go to step 13.
6. System power down procedure
Caution: Possibility of service interruption. Removing power on a traffic barring

system causes a loss of traffic.
7. Remove all MOD300 cards from the system.

8. Position all MPT-HL/MPT-HLC transceiver PA switches to the OFF ‘0’ position.
9. Remove fuses in the PDU that are suppling battery power to all MPT-HL/MPT-HLC
transceivers in the system.
10. Remove power to the MPT ODU. Depending upon the configuration, perform one of
the following for each MPT ODU:
a. If power is provided by the MPTACC card, use the Craft Terminal and disable
power source.
b. If power is provided by the MSS-1 shelf Core, use the Craft Terminal and disable
power source.
c. If MPT ODU is powered through a power injector card/power injector box,
disconnect the Ethernet+Data cable connection to the MPT ODU at the power
injector card/box.
d. If MPT ODU is powered with connection to MPT Extended Power Unit,
DC+ODU Data connection, disconnect the Ethernet+Data cable connection to the
MPT ODU at the MPT Extended Power Unit.
e. If MPT ODU is powered with connection to MPT Power Unit or MPT Extended
Power Unit DC (Type N) connection, disconnect the power cable connection to the
MPT ODU at the MPT Power Unit/MPT Extended Power Unit.
f. If MPT ODU is powered with connection to direct office power, locate the fuse
protecting the MPT ODU and remove.

g. If power is provided by an external source, disconnect power appropriately.

11. Remove the fuses in PDU that are suppling battery power to the MSS-1/4/8 shelf.
12. Go to step 20.
13. System power up procedure
Install the fuses in PDU that are suppling battery power to the MSS-1/4/8 shelf.
14. Install all MOD300 cards into the system.
15. Install the fuses in PDU that are suppling battery power to all MPT-HL/MPT-HLC
transceivers in the system.
16. Position all MPT-HL/MPT-HLC transceiver PA switches to the ON ‘1’ position.
17. Apply power to all MPT ODUs. Depending upon the configuration.
19. Verify that there are no unexpected alarms and conditions on the system.


53 — DLP-114 MPTACC (MPT Access)
replacement
53.1 — Purpose
This procedure describes how to replace an MPTACC.
53.3 — General
The MPTACC is supported in MSS-8 slots 3 to 8 and MSS-4 slots 3 and 4.
In unprotected radio configurations the main MPTACC card is supported in any of the
transport MSS-4/8 slots, two radio directions per MPTACC card for a maximum of twelve
MPTACC MPT-HC/MPT-XP/9558HC (MPT ODU) radio directions per MSS-8 shelf and
four radio directions per MSS-4 shelf.
In protected radio configurations, two arrangements are available. The first arrangement
utilizes one interface on a MPTACC card configured as main and the second interface as
spare for a single protected radio direction. This arrangement is supported in MSS-8 slots
3 to 8 and MSS-4 slots 3 and 4.
The second arrangement utilizes a main MPTACC card and a spare MPTACC card. The
main MPTACCs are equipped in slots 3, 5, and/or 7 and the protect (spare) MPTACCs are
equipped in the slots directly across from the main (slots 4, 6, and/or 8).
Disconnecting the MPTACC from the MSS backplane may remove power to the
MPT ODU, and may cause a disruption to traffic.

53 — DLP-114 MPTACC (MPT Access) replacement
type.
See the Alcatel-Lucent 9500 MPR-A Operation and Administration for detailed procedures
to execute the commands included in this procedure.
53.4 — Procedure
a peripheral plug-in card or a blank panel. Failure to do so will compromise EMC
link requires switching the traffic onto the protected hop.
radio configurations, the Main MPTACC cards resides in slots 3, 5, and/or 7. The
spare MPTACC cards resides in slots 4, 6, and/or 8.
the plug-in pane flush with the front panel. Improper alignment can result in damaged
9. MPTACC replacement procedures
Determine MPTACC configuration.
a. Does the MPTACC support one or two radio directions?

b. Are the radio directions protected?

c. Is protection available for both radio directions?
d. Is the power to the radio directions provided by the MPTACC card?
10. Verify that 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.
11. Is it appropriate to proceed with MPTACC replacement procedure?
link requires switching the traffic onto the protected hop.
radio configurations, the Main MPTACC cards resides in slots 3, 5, and/or 7. The
spare MPTACC cards resides in slots 4, 6, and/or 8.
15. Are any radio directions supported by the MPTACC in a protected system?
a. If yes, perform steps 16 through 24 for each protected radio direction supported by
the MPTACC to be replaced.
17. Is the MPTACC to be replaced main or spare?
21. Go to step 25.
25. Verify that the MPTACC to be replaced status is Standby.

27. Verify that all cable connections to the MPTACC to be replaced are properly labeled.
28. Disconnect all cables connected to the front of the MPTACC.
29. Remove the MPTACC to be replaced. See DLP-100 Mechanical card removal and
retaining screws.
31. Install the replacement MPTACC into the shelf. See DLP-100 Mechanical card
removal and installation for information about how install the card.
32. Connect all cables to the front of the MPTACC that you disconnected in step 28.
34. Verify that the replacement MPTACC is free of alarms using the Alarm Monitor.
35. Verify that the radio directions that are supported by the MPTACC are error free.
36. Is the replacement MPTACC status LED steady green or amber, error free, and free of
alarms?
37. Is the replacement MPTACC in a protected system?
a. If yes, perform steps 38 through 41 for each radio direction supported by the
MPTACC to be replaced.
38. Releasing Forced/Lockout EPS/HSB/RX Radio switch causes a disruption to traffic.
42. Go to step 44.

54 — DLP-115 MPT ODU replacement
(MPT-HC, MPT-XP, 9558HC)
54.1 — Purpose
This procedure describes how to replace an Outdoor Unit, MPT-HC/MPT-XP/9558HC
(MPT ODU).
Before starting, verify that the replacement MPT ODU matches the failed MPT ODU using
the following procedure.
1. Obtain part number of failed MPT ODU on inventory screen.

2. Verify part number of replacement MPT ODU, located on identification label, matches
part number of failed MPT ODU.
54.3 — General
The MPT ODU is supported in numerous configurations, protected and unprotected radio
configurations. The MPT ODU may be associated with an MSS shelf or stand-alone.
Connectivity to the MSS-4/8 shelf may be achieved through an MPTACC, P8ETH, or
Core-E card. Connectivity to the MSS-1 shelf may be achieved through the MSS/CORE
Ethernet ports.

54 — DLP-115 MPT ODU replacement (MPT-HC, MPT-XP, 9558HC)
Office power may be provided by the MPTACC card (coaxial or through PFoE) and by the
MSS-1 shelf MSS/CORE ports 1 and 2 (through PFoE). For P8ETH, Core-E cards and
MSS-1 shelf MSS/CORE ports 3 through 6, office power is provided by connectivity to
Power Injector Card, Power Injector Box, MPT Power Unit, MPT Extended Power Unit, or
through direct connection to office power. For ALL MPT-XP configurations, office power
MUST be provided by MPT Extended Power Unit. Fully understand the MPT ODU
configuration prior to starting MPT ODU replacement procedure.
In unprotected radio configurations, the associated radio port is supported in the following:
• main Core-E card in MSS-4/8 slot 1

• main MPTACC card in any of the transport MSS-8 slots 3 through 8 and MSS-4 slots
3 and 4
• main P8ETH card in any of the transport MSS-8 slots 3 through 8 and MSS-4 slots 3
and 4
• MSS-1 shelf MSS/CORE Ethernet ports 1 through 6
In protected radio configurations, the associated radio port is supported in the following:
• one interface on a MPTACC card configured as main and the second interface as spare
for a single protected radio channel. This arrangement is supported in MSS-8 slots 3
through 8 and MSS-4 slots 3 and 4.
• the main interface on main MPTACC card and the spare interface on spare MPTACC
card. The main MPTACCs are equipped in slots 3, 5, and/or 7 and the protect (spare)
MPTACCs are equipped in the slots directly across from the main, slots 4, 6, and/or 8.
• the main and spare interfaces are connected to MSS-4/8 Core-E and MSS-1 shelf MSS/
CORE radio ports. Protected radio configurations are configured with the main MPT
ODU connected to Core-E and MSS/CORE ports 1, 3, and/or 5 and the protect (spare)
is connected to Core-E and MSS/CORE ports 2, 4, and/or 6, respectively.
type.
See the Alcatel-Lucent 9500 MPR-A Installation Practices Charts 10 for information about
how to physically remove and install the MPT ODU to be replaced in this procedure.
54.4 — Procedure


microwave frequencies can cause eye injury and eventual blindness. Do not look
directly into any unterminated waveguide port.
3. CAUTION: Possibility of service interruption. In an unprotected radio,
performing the MPT ODU removal and replacement procedure causes loss of
traffic. In a protected system the procedure is an in-service but not a hitless
procedure. Disconnecting the MPTACC from the MSS-8 backplane to remove
power to the MPT ODU can cause a disruption on traffic.
5. Is the radio channel associated with the MPT ODU to be replaced in a protected
system?
7. Is the radio channel associated with the MPT ODU to be replaced the main or spare?
11. Go to step 15.
15. Mute the radio channel associated with the MPT ODU to be replaced.
16. Remove power to the MPT ODU. Depending upon the configuration, perform one of
the following for each MPT ODU:
a. If power is provided by the MPTACC card, use the Craft Terminal and disable
power source.
b. If power is provided by the MSS-1 shelf MSS/CORE ports 1 and 2, use the Craft
Terminal and disable power source.
c. If MPT ODU is powered with connection to Power Injector Card/Power Injector
Box, disconnect the Ethernet+Data cable connection to the MPT ODU at the
Power Injector Card/Box.

d. If MPT ODU is powered with connection to MPT Extended Power Unit,

DC+ODU Data connection, disconnect the DC+ODU cable connection to the
MPT ODU at the MPT Extended Power Unit.
e. If MPT ODU is powered with connection to MPT Power Unit or MPT Extended
Power Unit DC (Type N) connection, disconnect the power cable connection to the
MPT ODU at the MPT Power Unit/MPT Extended Power Unit.
f. If MPT ODU is powered with connection to direct office power, locate the fuse
protecting the MPT ODU and remove.
g. If power is provided by an external source, disconnect power appropriately.
17. Verify that all cable connections to the MPT ODU to be replaced are properly labeled.
18. Disconnect all cables that are connected to the MPT ODU.
Note: The procedure to Remove an MPT ODU is dependent on the MPT ODU mounting,
power configuration, and how the MPT ODU is configured. The procedure to remove an
MPT ODU is the reverse of MPT ODU installation. See Alcatel-Lucent 9500 MPR-A
Installation Practices, Charts 10 for information about how to physically install an
MPT ODU.
19. Remove the failed MPT ODU. See Alcatel-Lucent 9500 MPR-A Installation Practices
20. Install replacement MPT ODU. See Alcatel-Lucent 9500 MPR-A Installation Practices
21. Connect all cables to the MPT ODU that you disconnected in step 18.
22. Apply power to the MPT ODU that was removed in step 16.
23. Unmute the radio channel associated with the replaced MPT ODU.
24. Using the Craft Terminal, verify that there are no alarms associated with the
replacement MPT ODU.
25. Open WebEML Measurements windows for the radio channel that is associated with
the replaced MPT ODU.
26. On Measurements window, enter 15 minutes Measurement Interval.
27. On Measurements window, select 2 sec Sample Time.
28. On Measurements window, click on the Start button to start the measurements. The
29. On Measurement graphics window, check the Details box. Tx and Rx dBm Power
Levels Details table appears.
30. On Tx and Rx dBm Power Levels Details table, verify the Local and Far End Tx and
Rx power levels.
31. Is the replacement MPT ODU status normal and capable of carrying traffic?

32. Is the replacement MPT ODU in a protected system?

37. Go to step 39.


55 — DLP-116 Auxiliary (AUX)
replacement
55.1 — Purpose
This procedure describes how to replace an AUX card.
55.3 — General
The AUX card can be installed in MSS-8 slot 8 and MSS-4 slot 4.
type.
55.4 — Procedure

55 — DLP-116 Auxiliary (AUX) replacement
retaining screws.
7. AUX replacement procedures
CAUTION: Possibility of service interruption. Removing an AUX card may
isolate a portion of the network being supervised on a service channel supported
by the AUX card.
8. Verify that all cable connections to the AUX card to be replaced are properly labeled.
9. Disconnect the cables that are connected to the front of the AUX card.
10. Remove the AUX to be replaced. See DLP-100 Mechanical card removal and
retaining screws.
12. Install replacement AUX into shelf. See DLP-100 Mechanical card removal and
installation for detailed steps to install AUX card.
13. Connect all cables to the front of the AUX card that you disconnected in step 9.
15. Verify the replacement AUX alarms, that the status is normal using the Alarm Monitor
and Craft Terminal.
16. Is the replacement AUX status normal and functioning properly?
b. TagIf no, go to step 17.

56 — DLP-117 Protection upgrade and
downgrade procedures
56.1 — Purpose
These procedures describes how to upgrade and downgrade protection configuration on the
9500 MPR-A system.
56.2 — General
The protection upgrade and downgrade procedures provide the general steps and sequence
required to change protection scheme. The number of possible configuration scenarios
prevents covering all upgrade and downgrade possibilities.
56.3 — PDH protection

PDH protection upgrade applies when converting from 1+0 not protected to 1+1 EPS
protection configuration.
PDH protection downgrade applies when converting from 1+1 EPS protection to 1+0 not
protected configuration.
56.4 — Radio protection

Radio protection upgrade applies when converting from 1+0 not protected to 1+1 HSB,
HSB SD, or FD radio protection configuration.

56 — DLP-117 Protection upgrade and downgrade procedures
Radio protection downgrade applies when converting from 1+1 HSB, HSB SD, or FD
protection to 1+0 not protected radio configuration. Radio protection downgrade requires a
power cycle of the NE.
There are no steps included to account for the required changes to the MPT-HL shelf
diplexer configuration or outside plant configuration, such as ODU/antenna configuration,
RF coupler, waveguide, and grounding.
56.5 — Modulation scheme

The modulation scheme conversion applies when converting from static to adaptive radio
profile and the reverse.
To change modulation scheme, ATPC must be disabled, radio configuration must be 1+0
not protected, and license key must support adaptive modulation.
Converting from static to adaptive radio profile, all existing TDM2TDM and TDM2ETH
cross-connections must be supported by the lowest adaptive modulation profile (4 QAM).
When all existing TDM2TDM and TDM2ETH cross-connections are supported by the
lowest adaptive modulation profile (4 QAM), all the existing TDM2TDM and TDM2ETH
cross-connections are kept and the residual bandwidth for new TDM2TDM and TEM2ETH
cross-connections will be recomputed. When all the existing TDM2TDM and TDM2ETH
cross-connections can not be supported by the lowest adaptive modulation profile (4
QAM), the request to change modulation scheme is rejected. Some existing TDM2TDM
and/or TEM2ETH cross-connections must be deleted to achieve a bandwidth which is
supported by the lowest adaptive modulation profile.
Converting from adaptive to static radio profile, the new static radio profile is the one that
corresponds to the largest supported radio profile configured (16 QAM or 64 QAM). all
existing TDM2TDM and TDM2ETH cross-connections are preserved and the residual
bandwidth for new TDM2TDM or TEM2ETH cross-connections are recalculated.
All cards can be removed and installed with power applied.
type.
56.6 — Procedure


a. To Upgrade PDH 1+0 to 1+1 EPS protection configuration, go to step 6.
b. To Downgrade PDH 1+1 EPS to 1+0 not protected configuration, go to step 13.
c. To Upgrade 1+0 to 1+1 protected radio configuration, go to step 20.
d. To Downgrade 1+1 to 1+0 not protected radio configuration, go to step Caution:.
e. To Upgrade fixed modulation to adaptive modulation configuration, go to step 40.
f. To Downgrade adaptive modulation to fixed modulation configuration, go to
step 57.
6. Upgrade PDH 1+0 to 1+1 EPS protection configuration
Caution: Possibility of service interruption. This is an In-Service but not a hitless

procedure.
7. Install spare P32E1DS1/P2E3DS3 card in spare slot 4, 6, or 8 associated with main

P32E1DS1/P2E3DS3 card. An Unconfigured Equipment Present alarm displays.
8. Connect the DS1 or DS3 cables to spare the P32E1DS1/P2E3DS3 card that you
installed in step 7.
9. On CT settings window, enable the spare P32E1DS1/P2E3DS3 card that you installed
in step 7.
10. On CT settings window, configure the P32E1DS1/P2E3DS3 cards for 1+1 EPS
protection type.
Note: To complete the upgrade to 1+1 EPS protection, all TDM2ETH and TDM2TDM
cross-connections MAC address affected by this system upgrade, must be changed from
‘unicast’ to ‘multicast’ at the remote NEs.

11. Reprovision all of the TDM2ETH and TDM2TDM cross-connections MAC address
from ‘unicast’ to ‘multicast’ at the remote NEs. For more information about how to
configure cross-connections, see the Alcatel-Lucent 9500 MPR-A Operation and
Administration.
12. Go to step 72.
13. Downgrade PDH 1+1 EPS to 1+0 not protected configuration
Caution: Possibility of service interruption. Downgrading from 1+1 EPS to 1+0 Not
protected configuration is an In-Service procedure. all traffic including sync source
must be Active on the main PDH card before starting this procedure.
14. On CT settings window, set the P32E1DS1/P2E3DS3 cards protection type to No

Protection.
15. On CT settings window, set the spare P32E1DS1/P2E3DS3 card equipment type to
Empty.
16. Disconnect the DS1 or DS3 cables from spare the P32E1DS1/P2E3DS3 card.
17. Remove the spare P32E1DS1/P2E3DS3 card in spare slot 4, 6, or 8.
Note: To complete the downgrade to 1+0 Not Protected configuration, all TDM2ETH and
TDM2TDM cross-connections MAC address affected by this system downgrade, must be
changed from ‘multicast’ to ‘unicast’ at the remote NEs.
18. Reprovision all of the affected TDM2ETH and TDM2TDM cross-connections MAC
address from ‘multicast’ to ‘unicast’ at the remote NEs. For more information about
how to configure cross-connections, see the Alcatel-Lucent 9500 MPR-A Operation
and Administration.
19. Go to step 72.
20. Upgrade 1+0 to 1+1 protected radio configuration
Caution: Possibility of service interruption. This is an In-Service but not a hitless

procedure.
21. NOTE: To achieve expected radio operation the upgrade from 1+0 not protected
to 1+1 protected radio configuration must be performed at both ends of the radio
hop.
22. For an ODU300 radio, install the MOD300 card in the adjacent slot 4, 6, or 8. Do NOT
seat the card at this time. Connect the IF coax cable to MOD300 card.
For a radio that equipped with the MOD300 card, seat the card into slot 4, 6, or 8.

For a MPT-HL/MPT-HLC transceiver radio connected to an EASv2 or P8ETH card, a

second EASv2 or P8ETH card must be installed in the adjacent slot if not already
equipped. Install the MPT-HL/MPT-HLC transceiver in slot 2 of the MPT-HL shelf.
For a MPT-HL/MPT-HLC transceiver radio connected to a Core-E card port 5 or
MSS-1 shelf port 5, port 6 must be available to support the spare MPT-HL/MPT-HLC
transceiver. Install the MPT-HL/MPT-HLC transceiver in slot 2 of the MPT-HL shelf.
For MPT ODU radio that is equipped with a MPTACC card, the spare radio hop is
supported on port 2 of the same MPTACC card or from an MPTACC card installed in
adjacent slot to the main MPTACC card, slots 4, 6, or 8. Install the MPTACC as
required, as described in the site documentation.
For MPT ODU radio connected to an EASv2 optical port equipped in slot 3, 5, or 7, a
second EASv2 card must be installed in the adjacent slot 4, 6, or 8 if not already
equipped.
For MPT ODU radio connected to a Core-E card port 5 or MSS-1 shelf port 5, port 6
must be available to support the spare MPT ODU radio.
23. Install the appropriate radio/transport card in adjacent slot 4, 6, or 8 that is associated
with main radio direction. An Unconfigured Equipment Present condition is raised.
24. On the CT settings window, enable the card as required. Enable the appropriate radio,
MD300/MPT ODU/MPT-HL/MPT-HLC transceiver that you installed in step 23.
25. On the CT settings window, configure the radio direction protection type as 1+1
HSB(SD) or 1+1 FD. Local station and remote station observes 2 second sync loss.
26. Connect the new radio direction cables to the spare radio card that you installed in
step 23, as described in the site documentation.
a. For a radio that is equipped with MPT-HL/MPT-HLC transceiver, install the SFP
into the appropriate Core-E/EASv2/P8ETH/MSS-1 SFP port and the MPT-HL/
MPT-HLC transceiver SFP port. Connect the fiber optic cable between the SFP
port and MPT-HL/MPT-HLC transceiver SFP port. Connect the MPT-HL/
MPT-HLC transceiver power cable, as described in the site documentation.
b. For a MPT ODU radio that is equipped with a Core-E/EASv2/MPTACC/MSS-1,
connect the radio cables, as described in the site documentation (optical Ethernet
and power coaxial cable, electrical Ethernet and power coaxial cable, or electrical
Ethernet W/PFoE connectivity).
27. If radio protection is configured as 1+1 FD, configure the spare radio direction.
Note: If unexpected radio alarms are present on the radio channel associated with
protection upgrade, a system restart is required to clear the alarms.
Caution: Possibility of service interruption. Performing a system restart to clear

unexpected radio alarms causes disruption to traffic.

Note: To complete the upgrade to 1+1 radio protection, all TDM2ETH and TDM2TDM
cross-connections MAC address affected by this system upgrade, must be changed
from ‘unicast’ to ‘multicast’ at the remote NEs.
address from ‘unicast’ to ‘multicast’ at the remote NEs. For more information about
how to configure cross-connections, see the Alcatel-Lucent 9500 MPR-A Operation
and Administration.
29. Go to step 72.
30. Downgrade 1+1 to 1+0 not protected radio configuration
Caution: Possibility of service interruption. Downgrading from 1+1 HSB, HSB SD, or FD
to 1+0 configuration is an Out-Of-Service procedure. All traffic including sync source
must be Active on the main channel before starting this procedure.
Caution: Possibility of service interruption. Downgrading from 1+1 HSB, HSB SD, or FD
to 1+0 configuration is an Out-Of-Service procedure. To complete the downgrade
procedure, the NE must be power cycled off and back on again. The power cycle takes
approximately 15 minutes complete.
Note: To achieve expected radio operation the downgrade from 1+1 protected to 1+0
not protected radio configuration must be performed at both ends of the radio hop.
31. On CT settings window for radio channel, enable the Local Tx Mute for channel #1 and
#0.
32. On CT settings window, set the radio channel protection type to No Protection.
33. On CT settings window for radio channel, disable the Local Tx Mute for channel #1
only.
34. Disconnect the channel#0 radio direction cables to the spare radio cards.
a. For a radio that is equipped with a MOD300 card, unseat the MOD300 card from
the shelf, then disconnect the IF coax cable from the MOD300 card.
b. For a radio that is equipped with a MPT-HL/MPT-HLC transceiver, disconnect the
fiber optic cable between the SFP port and MPT-HL transceiver, as described in
the site documentation.
c. For a MPT ODU radio that is equipped with a Core-E/EASv2/MPTACC/MSS-1,
disconnect the radio cables, as described in the site documentation (optical
Ethernet and power coaxial cable, electrical Ethernet and power coaxial cable, or
electrical Ethernet W/PFoE connectivity).

Note: In the case of 1+1 FD configuration, local AIS will remain active throughout
remainder of the procedure.
35. On CT settings window, set the radio direction equipment type to Empty.
36. Remove the appropriate radio/transport card as described in the site documentation.
a. For an ODU300 radio, remove the MOD300 card from slot 4, 6, or 8.
b. For an MPT-HL/MPT-HLC transceiver radio, remove the appropriate Core-E/
EASv2/P8ETH/MSS-1 SFP port as described in the site documentation. Remove
the MPT-HL/MPT-HLC transceiver SFP. Remove the MPT-HL/MPT-HLC
transceiver in slot 2 of the MPT-HL shelf.
c. For an MPT ODU radio direction that was supported with a EASv2/MPTACC,
remove the EASv2/MPTACC ONLY if described in the site documentation.
37. CAUTION: Possibility of service interruption. Downgrading from 1+1 HSB, HSB
SD, or FD to 1+0 configuration is an Out-Of-Service procedure. To complete the
downgrade procedure the NE must be power cycled off and back on again. The
power cycle takes approximately 15 minutes complete.
38. Power down and then power up the NE. See DLP-113 System power down and power
up for information about the power cycles of the NE.
Note: To complete the downgrade to 1+0 radio configuration, all TDM2ETH and
TDM2TDM cross-connections MAC address affected by this system downgrade, must be
changed from ‘multicast’ to ‘unicast’ at the remote NEs.
address from ‘multicast’ to ‘unicast’ at the remote NEs. For more information about
how configure cross-connections, see the Alcatel-Lucent 9500 MPR-A Operation and
Administration, DLP-112.
40. Upgrade fixed modulation to adaptive modulation configuration
Caution: Possibility of service interruption. This is an Out-of-Service procedure.

41. Verify that the system license key supports adaptive modulation. For more information
about how to display and update the system license key, see the Alcatel-Lucent
9500 MPR-A Operation and Administration, DLP-120.
42. Open the radio channel view. Take a screen capture to save all radio channel
provisioning information.
43. Which type of radio direction configuration?
a. If 1+0 Not protected, go to step 46.

b. If 1+1 protected, go to step 44.

44. Mute the spare radio channel (channel #0).
45. Set the radio direction Protection Type to No Protection.
46. Is the ATPC enabled?
47. Disable the ATPC (unchecked) and click on the Apply button.
48. From the radio direction Mode drop-down menu, choose Adaptive Modulation and
click on the Apply button.
49. NOTE: If the sum of all TDM2TDM and TDM2ETH cross-connections exceed the
supported capacity for the reference channel at 4 QAM, the request to change
modulation mode is rejected.
51. Set the radio direction Protection Type to 1+1 HSB(SD) or 1+1 FD.
52. Unmute the spare radio channel (channel #0).
53. NOTE: To complete the upgrade from fixed modulation to adaptive modulation both
ends of the radio hop must be upgraded.
54. Verify that the radio direction is alarm free.
55. Verify that the radio direction is error free and operating as expected.
56. Go to step 72.
57. Downgrade adaptive modulation to fixed modulation configuration

60. Mute the spare radio channel (channel #0).
61. Set the radio direction Protection Type to No Protection.
62. From the radio direction Mode drop-down menu, choose Presetting and click on the
Apply button.


64. Set the radio direction Protection Type to 1+1 HSB(SD) or 1+1 FD.
65. Unmute the spare radio channel (channel #0).
66. Provision the ATPC?
67. Enable the ATPC (checked) and click on the Apply button.
68. Configure the local ATPC Tx range, remote ATPC Rx threshold, and click on the
Apply button.
69. NOTE: To complete the upgrade from adaptive modulation to fixed modulation both
ends of the radio hop must be downgraded.
71. Verify that they radio direction is error free and operating as expected.


57 — DLP-118 Upgrade and downgrade
radio profile
57.1 — Purpose
These procedures describes how to upgrade and downgrade radio profile on the 9500 MPR-
A system.
57.2 — General
The radio profile upgrade and downgrade procedures provide the general steps and
sequence required to change protection scheme. The number of possible radio profile
scenarios prevents covering all upgrade and downgrade possibilities.
57.3 — Radio profile

Radio profile upgrade applies when the new radio profile has a capacity which is larger than
the existing profile. In this case all the existing TDM2TDM or TDM2ETH
cross-connections are kept and the residual bandwidth for new TDM2TDM or TEM2ETH
cross-connections are calculated.
Radio profile downgrade applies when the new radio profile has a capacity which is smaller
than the existing profile. When all the existing TDM2TDM and TDM2ETH
cross-connections are supported by the new profile, all the existing TDM2TDM and
TDM2ETH cross-connections are kept and the residual bandwidth for new TDM2TDM
and TEM2ETH cross-connections will be recomputed. When all the existing TDM2TDM
and TDM2ETH cross-connections can not be supported by the new profile, the request to
change radio profile are rejected. Some existing TDM2TDM and/or TEM2ETH
cross-connections must be deleted to achieve a bandwidth which is supported by the new
radio profile.

57 — DLP-118 Upgrade and downgrade radio profile
type.
57.4 — Procedure
a. To Upgrade radio profile, go to step 2.
b. To Downgrade radio profile, go to step 12.
2. Upgrade radio profile

3. Verify that the system license key supports the new radio profile. For information about
how to display and upgrade the system license key, see the Alcatel-Lucent 9500 MPR-
A Operation and Administration, DLP-120.
4. From the radio direction Reference Channel Spacing drop-down menu, select new
channel bandwidth.
5. From the radio direction Modulation drop-down menu, select the new modulation
value.
7. Verify the Tx power provisioning and adjust, as described in the site documentation.
8. NOTE: To complete an upgrade of a radio profile, both ends of the radio hop must be
upgraded.
11. Go to step 22.
12. Downgrade radio profile


14. From the radio direction Reference Channel Spacing drop-down menu, select the new
channel bandwidth.
15. From the radio direction Modulation drop-down menu, select the new modulation
value.
17. NOTE: If the sum of all TDM2TDM and TDM2ETH cross-connections exceed the
supported capacity for the new radio channel, the request to change radio profile will
be rejected.
18. Verify the Tx power provisioning and adjust, as described in the site documentation.
19. NOTE: To complete downgrade of radio profile both ends of the radio hop must be
downgraded.


58 — DLP-119 Upgrade unlicensed
MPT-HL radio to lower 6 GHz radio
58.1 — Purpose
This procedure describes how to upgrade a MPT-HL unlicensed radio hop to a lower 6 GHz
radio hop on the 9500 MPR-A system.
58.2 — General
This upgrade procedure provides general steps and the sequence required to upgrade a
MPT-HL unlicensed radio hop to a lower 6 GHz radio hop. The number of possible radio
configurations precludes covering all possible radio configurations.
A site survey and site documentation must be provided to ensure that facilities that are not
associated with the upgrade radio direction are not impacted by this upgrade procedure.
This procedure describes the steps required for a protected radio direction. For not
protected radio directions, disregard the references to the spare radio channel.
Before starting this procedure, read and fully understand this procedure and all referenced
procedures in their entirety.
type.
58.3 — Procedure

58 — DLP-119 Upgrade unlicensed MPT-HL radio to lower 6 GHz radio

2. CAUTION: Possibility of service interruption. This is an Out-of-Service
procedure. The radio direction being upgraded must be taken Out-of Service to
complete this procedure. All remaining facilities that are not associated with the
radio direction scheduled for upgrade, should not be impacted by this upgrade
procedure. Schedule appropriate maintenance window per local practices and
procedures.
retaining screws.
7. Verify that the system license key supports the new radio profile. For information about
how to display and update the system license key, see the Alcatel-Lucent 9500 MPR-A
Operation and Administration, DLP-120.
8. CAUTION: Possibility of service interruption. Removing power to an In-Service
MPT-HL Transceiver in an unprotected link causes loss of traffic.
9. Position the local MPT-HL transceiver PA switch to the OFF ‘0’ position for the main
and spare channel.
10. Position the far end MPT-HL transceiver PA switch to the OFF ‘0’ position for the
main and spare channel.
11. Remove the fuse in PDU that is supplying battery power to the main and spare
MPT-HL transceiver.
12. Loosen the screws that are securing the MPT-HL transceivers to MPT-HL shelf. See
DLP-100 Mechanical card removal and installation for information about how to
remove the MPT-HL transceiver.
13. Unseat the MPT-HL transceivers to disconnect from shelf backplane connectors. Do
not remove the MPT-HL transceivers from the shelf.
14. Verify that all of the cable connections on the rear of the MPT-HL shelf to the MPT-HL
filter are properly labeled per site documentation.
15. Disconnect all of the cables that are connected to the MPT-HL Filter end only.

16. Remove the MPT-HL filter.

17. Install the new MPT-HL filter.
18. Connect all of the cables to the MPT-HL Filter that you disconnected in step 15.
Tighten the connectors to 7.1 in-lbs.
19. Verify that the cable ends are properly secured to the MPT-HL shelf and Tx switch.
Tighten the connectors to 7.1 in-lbs.
20. Seat the MPT-HL transceivers into the shelf.
21. Verify that the MPT-HL transceiver PA switch is in the OFF ‘0’ position for the main
and spare channel.
22. Install the fuse in the PDU that is suppling battery power to the main and spare
MPT-HL transceiver.
23. Using the Craft Terminal, provision the new radio profile as described in the site
documentation. For information about how to configure the radio profile, see the
Alcatel-Lucent 9500 MPR-A Operation and Administration, DLP-109.
Note: If one or more of the radio parameters is determined to be out of range, it must
be provisioned first before provisioning continues on the radio direction.
a. Set the new Channel #1 Shifter (MHz) shifter value.

b. Enter the TX Frequency within the allowed range. The Rx Freq (KHz) displays the
Rx RF Frequency.
c. Click on the Apply button.
d. Configure the new Reference Channel Spacing.
e. Configure the new Modulation scheme.
f. Configure the new gain configuration.
g. Click on the Apply button.
h. Which Tx Power management is configured?
a. If ATPC, go to step i.
b. If RTPC, go to step m.
i. Configure the new Minimum and Maximum transmit power values.
j. Configure the new remote ATPC Rx Threshold.
k. Click on the Apply button.
l. Go to step 24.
m. Configure the new RTPC Tx Power.
24. NOTE: To complete the upgrade of the radio profile, both ends of the radio hop must
be upgraded.
25. Position the local MPT-HL transceiver PA switch to the ON ‘1’ position for the main
and spare channel.

26. Position the far end MPT-HL transceiver PA switch to the ON ‘1’ position for the main
and spare channel.

59 — DLP-120 +24/-48 volt converter
replacement
59.1 — Purpose
This procedure describes how to replace a +24/-48 volt Converter.
59.3 — General
The +24/-48 volt Converter is supported in the MSS-8 slots 4, 6, or 8 and MSS-4 slot 4.
In unprotected power configurations, one +24/-48 volt Converter is equipped in the left
converter chassis location.
In protected power configurations, the main +24/-48 volt Converter is equipped in the left
converter chassis location. The spare +24/-48 volt Converter is equipped in the right
converter chassis location.
Removing the +24/-48 volt Converter from the MSS shelf does not remove power to the
+24/-48 volt Converter. Power from the PDU or battery must be turned off before removing
the converter from the chassis.
The +24/-48 volt Converter can not be removed and installed with power applied.
type.

59 — DLP-120 +24/-48 volt converter replacement
59.4 — Procedure
1. DANGER: Possibility of personal injury. The +24/-48 Volt Converter must NOT
be installed or removed with bay power on. Hazardous electrical potentials are
present. Do NOT install or remove the +24/-48 Volt Converter card from the
chassis with power applied to the converter.
3. CAUTION: Possibility of service interruption. Removing an in-service +24/-48
Volt Converter in an unprotected MSS-4/8 shelf causes loss of traffic.
4. CAUTION: Possibility of service interruption. In redundant power
configurations, the Main +24/-48 Volt Converter resides in left chassis location.
The spare +24/-48 Volt Converter resides in right chassis location.
7. +24/-48 Volt converter replacement procedure
Verify the status of the MSS-4/8 shelf.
a. Is traffic affected?
b. Is the shelf configured with unprotected or redundant power arrangement?
c. Is the appropriate maintenance window schedule per local practices and
procedures?
8. Is it appropriate to proceed with the +24/-48 Volt Converter replacement procedure?
9. CAUTION: Possibility of service interruption. Removing an In-Service +24/-48
Volt Converter in an unprotected MSS-4/8 shelf causes loss of traffic.

Figure 59.1 — +24/-48 Volt converter cabling diagram
Cable Assemblies:
3DB18766AA
Main
(A-Side)
Power
Protect
(B-Side)
Power
Main Power Protect Power

Cable Assemblies: Converter Converter
3DB18271AA
No3014
10. Remove the PDU/battery fuse supplying power to the converter to be replaced.
11. Verify that the two cables connected to the front of the converter are clearly identified.
12. Disconnect the two cables that are connected to the front of the converter.
13. Remove the converter to be replaced from the chassis. See DLP-100 Mechanical card
removal and installation for information about how to remove the converter.
retaining screws.
15. Install the replacement converter into the chassis. See DLP-100 Mechanical card
removal and installation for information about how to install the converter.
16. Connect the two cables to the front of the converter that you disconnected in step 12.
17. Install the PDU/battery fuse that you removed in step 10.
18. Verify that there are no power-related alarms using the Alarm Monitor.
19. Is the replacement +24/-48 Volt Converter status normal and capable of carrying
traffic?


60 — DLP-121 Power injector
replacement
60.1 — Purpose
This procedure describes how to replace a Power Injector card and Power Injector box.
60.2 — Perquisites
60.3 — General
The Power Injector Box/Card supports up to two 1+0 MPT ODU based radio channels. The
MPT ODU radio channels may be connected to MSS-4/8 Core-E or P8ETH cards, or
MSS-1 shelf Core.
The Power Injector card is supported in MSS-8 slots 3 to 8 and MSS-4 slots 3 and 4.
The Power Injector box is a stand-alone unit.
Power Injector replacement affects traffic on both radio channels that are associated with
the Power Injector Box/Card. Fully understand the ramifications to both radio channels
before beginning the Power Injector Replacement Procedure. Verify that radio protection
is available for all traffic that is supported by the Power Injector to be replaced or
appropriate maintenance window is scheduled per local practices and procedures.
The Power Injector card can be removed and installed with power applied to the MSS-4 and
MSS-8 shelf.
The Power Injector box must be powered down during the replacement procedure.

60 — DLP-121 Power injector replacement
type.
60.4 — Procedure
3. CAUTION: Possibility of service interruption. Replacing an in-service Power
Injector causes loss of traffic on both radio channels that are associated with the
Power Injector.
5. WARNING: Possibility of equipment damage. When installing a Power Injector card,
ensure its backplane connector is correctly engaged before applying sufficient
pressure to bring the plug-in pane flush with the front panel. Improper alignment can
result in damaged pins on the backplane connector and/or damage to the plug-in
connector.
7. Power injector replacement procedure
Determine the Power Injector box/card configuration.
a. Does the Power Injector support one or two radio channels?
b. Is traffic supported on one or both radio channels?
8. Verify that the appropriate maintenance window is scheduled per local practices and
procedures.
9. Is it appropriate to proceed with Power Injector replacement procedure?


Injector causes loss of traffic on both radio channels associated with the Power
Injector.
11. Verify that all cable connections to the Power Injector to be replaced are properly
labeled.
12. Which Power Injector is to be replaced?
a. If Power Injector box, go to step 13.
b. If Power Injector card, go to step 20.
13. Locate the fuses protecting the A and B battery feeds to the Power Injector box and
remove.
14. Disconnect all of the cables that re connected to the front of the Power Injector box.
15. Remove the Power Injector box to be replaced from the bracket.
16. Install the Power Injector box onto the bracket.
17. Connect all of the cables to the front of the Power Injector box that you disconnected
in step 14.
18. Install the fuses protecting the A and B battery feeds removed in step 13.
19. Go to step 25.
20. Remove the Power Injector card to be replaced. See DLP-100 Mechanical card removal
and installation for information about how to remove the card.
21. Disconnect all of the cables that are connected to the front of the Power Injector card.
retaining screws.
23. Install the replacement Power Injector card into shelf. See DLP-100 Mechanical card
removal and installation for information about how to install the card.
24. Connect all of the cables to the front of the Power Injector card that you disconnected
in step 21.
25. Retrieve the alarms using the Alarm Monitor. A Dialog Failure is declared against the
MPT ODUs. Wait for Dialog Failure condition to clear before proceeding.
26. Verify the MPT ODUs that are associated with the replacement Power Injector are free
of alarms using Alarm Monitor.
27. Verify the radio channels that are supported by the Power Injector are error free.
28. Are the MPT ODUs that are associated with the replacement Power Injector error free
and free of alarms?


61 — DLP-122 RPS/XPIC module
replacement
61.1 — Purpose
This procedure describes how to replace a RPS and XPIC module on the MPT-HC/
MPT-XP/9558HC (MPT ODU).
Before starting, verify that the replacement RPS or XPIC module type matches the failed
RPS or XPIC using the following procedure.
1. Obtain the part number of the failed RPS or XPIC on the remote inventory screen.
2. Verify the part number of the replacement RPS or XPIC, located on the identification
label, matches the part number of the failed RPS or XPIC.
61.3 — General
The RPS/XPIC module is installed on the MPT ODU.
Appropriate personnel are required to replace the RPS/XPIC module.
You can replace the MPT ODU with the replacement RPS/XPIC module already installed
per local practices and procedures. If the MPT ODU replacement is preferred, see DLP-115
MPT ODU replacement (MPT-HC, MPT-XP, 9558HC).

61 — DLP-122 RPS/XPIC module replacement
Table 61.1 — MPT ODU 1+1 module details
ITEM DESCRIPTION Part Number
XPIC Module 3DB20116BA/BB
RPS Module 3DB20117BA
type.
See the Alcatel-Lucent 9500 MPR-A Installation Practices Charts 10 for information about
how to physically remove and install the RPS/XPIC module to be replaced in this
procedure.
61.4 — Procedure
microwave frequencies. Observe all safety instruction per local practices and
procedures during RPS/XPIC replacement procedure.
2. DANGER: Possibility of personal injury. RPS/XPIC replacement should not be
performed with power applied. Hazardous electrical potentials are present; use
extreme care when installing or removing RPS/XPIC module.
4. CAUTION: Possibility of service interruption. 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 appropriate maintenance window per local
5. CAUTION: Possibility of service interruption. Forced EPS/HSB/Rx Radio
6. What is the radio configuration that is associated with the RPS/XPIC module to be
replaced?
a. If 1+1 XPIC or 1+1 protected, go to step 7.
b. If co-channel XPIC, go to step 17.
c. If 1+0 unprotected, go to step 19.
7. CAUTION: Possibility of service interruption. Forced EPS/HSB/Rx Radio
switching traffic causes a disruption to traffic

8. Is the radio channel that is associated with the RPS/XPIC to be replaced the main or
spare?
12. Go to step 20.
16. Go to step 20.
17. CAUTION: Possibility of service interruption. Replacing the MPT ODU RPS/
XPIC module in an unprotected XPIC link (horizontal or vertical) may cause a
disruption to traffic on the other polarization radio channel (vertical or
horizontal) which is a member of the XPIC configuration.
18. Go to step 20.
19. CAUTION: Possibility of service interruption. Replacing the MPT ODU RPS/
XPIC module in an unprotected link causes a loss of traffic on ALL facilities that
are associated with the MPT ODU. Schedule appropriate maintenance window
20. Mute the radio channel that is associated with the RPS/XPIC to be replaced.
21. Remove power to the MPT ODU housing the RPS/XPIC; module to be replaced. Use
the Craft Terminal and disable power source.
Note: The procedure to remove an RPS/XPIC is the reverse of RPS/XPIC installation. See
Alcatel-Lucent 9500 MPR-A Installation Practices, Charts 10 for information about how
to physically install an MPT ODU.
22. Remove the solar shield from the MPT ODU.

23. Verify that all cable connections to the MPT ODU are properly labeled.
24. Disconnect all of the cables that are connected to the MPT ODU RPS/XPIC module.
See the Alcatel-Lucent 9500 MPR-A Installation Practices for more information.
25. Remove the external RPS/XPIC cover.
26. Remove the cap from the replacement RPS/XPIC module.
27. Verify that the gasket is in good condition and installed properly.
28. Install the replacement RPS/XPIC module onto the MPT ODU and lock the four
screws. Pay attention to the correct position of the screws.

29. Connect all of the cables to the MPT ODU RPS/XPIC module that you disconnected
in step 24.
30. Install the solar shield onto the MPT ODU.
31. Apply power to the MPT ODU.
32. Unmute the radio channel that is associated with the replaced MPT ODU RPS/XPIC
module.
33. Using the Craft Terminal, verify that there are no alarms associated with the MPT ODU
associated with the RPS/XPIC module replacement.
34. Open WebEML Measurements windows for the radio channel that is associated with
the MPT ODU RPS/XPIC module replacement.
35. On the Measurements window, enter 15 minutes Measurement Interval.
36. On the Measurements window, select 2 sec Sample Time.
37. On the Measurements window, click on the Start button to start measurements. The
38. On the Measurement graphics window, check on the Details box.Tx and Rx dBm
Power Levels Details table appears.
39. On Tx and Rx dBm Power Levels Details table, verify the Local and Far End Tx and
Rx power levels.
40. Is the MPT ODU status normal and capable of carrying traffic?
41. What is the radio configuration that is associated with the RPS/XPIC module to be
replaced?
a. If 1+1 XPIC or 1+1 protected, go to step 42.
b. If co-channel XPIC, go to step 48.
c. If 1+0 unprotected, go to step 48.
46. Go to step 48.

62 — DLP-123 Upgrade MPT ODU to
MPT ODU L1 LAG port
62.1 — Purpose
This procedure describes how to upgrade an Out-of-Service MPT-HC/MPT-XP/9558HC
(MPT ODU) radio hop to an MPT ODU configured as the L1 LAG Master Port.
62.2 — General
This upgrade procedure provides general steps and the sequence required to upgrade an
MPT ODU radio interface supported on an MPTACC card to an MPT ODU radio interface
supported on an P8ETH card and configured as the L1 LAG Master Port.
The L1 LAG Master Port must be located in P8ETH card Ethernet port 5 or 7.
The number of possible radio configurations precludes covering all possible radio
configurations.
MPT ODU connected to an P8ETH card requires power provided by one of the following
methods:
• MPT Power Unit

• MPT Extended Power Unit (required for MPT-XP)
• Power Injector Card
• Power Injector Box
• Direct connection to office power
• MPTACC card
A site survey and site documentation must be provided to ensure that facilities that are NOT
associated with the upgrade MPT ODU radio direction are not impacted by this upgrade
procedure.

62 — DLP-123 Upgrade MPT ODU to MPT ODU L1 LAG port
Before the L1 LAG port is ready to carry traffic, this procedure must be performed at both
ends of the radio hop.
type.
62.3 — Procedure
procedures.
procedure. The radio direction being upgraded must be taken Out-of Service to
complete this procedure. All remaining facilities that are not associated with the
radio direction scheduled for upgrade, should not be impacted by this upgrade
procedures.
retaining screws.
8. Verify the NE is running R3.4.0 or higher software version.

9. Install power source as required per site documentation including running any new
cabling between the power source and the MPT ODU.
10. Install optical Ethernet fiber from MSS-4/8 shelf to MPT ODU as required per site
documentation.
11. Verify that the MPT ODU radio interface is NOT associated with the following:
a. Cross-Connection
b. VLAN
c. Port Segregation
d. PPP RF enabled
e. Synchronization reference
f. SSM
12. Perform a database backup. See the Alcatel-Lucent 9500 MPR-A Operation and
Administration, DLP-131 for a detailed procedure to perform a database backup.
13. If MPT ODU radio interface is configured for 1+1 HSB/FD/SD, downgrade radio
protection to 1+0. Refer to Alcatel-Lucent 9500 MPR-A Maintenance and Trouble
Clearing, DLP-117 Protection upgrade and downgrade procedures for a detailed
procedure.
14. Disable MPT ODU radio port from MPTACC card. See the Alcatel-Lucent 9500 MPR-
A Operation and Administration, DLP-105 for a detailed procedure.
15. If MPTACC PFoE is the power source for the MPT ODU, verify the power source is
still configured for PFoE.
16. If MPTACC card is to be replaced with P8ETH card to support L1 LAG port. Perform
the following actions:
a. Verify no radio interfaces are supported on the remaining MPTACC radio
interface. If there is a radio interface connected to the remaining MPTACC radio
port, STOP this procedure immediately and contact the next level of support!
b. Disable MPTACC card. See the Alcatel-Lucent 9500 MPR-A Operation and
Administration, DLP-105 for a detailed procedure.
c. Remove the MPTACC card from the MSS-4/8 shelf.
d. Install the P8ETH card into the MSS-4/8 shelf.
17. Verify/enable P8ETH card to support L1 LAG port.
Note: Electrical SFPs are NOT supported for interconnection between P8ETH SFP port and
MPT ODU.
18. Install SFP into the P8ETH radio port and connect fiber cable to SFP. L1 LAG Master
port must reside in P8ETH Ethernet port 5 or 7.
19. Install SFP into the MPT ODU data port and connect the fiber cable to the SFP per site
documentation.

20. Provision MPT ODU radio interface.

21. If MPTACC PFoE/SMA connector is the power source for the MPT ODU, the
Ethernet/coax cable remains connected and will be used to power the MPT ODU.
22. If MPTACC PFoE is the power source for the MPT ODU, perform one of the
following:
a. Disable the power source. Then provision the power source for PFoE. See the
Alcatel-Lucent 9500 MPR-A Operation and Administration, DLP-109 for a
detailed procedure to provision MPT ODU power scheme.
b. Unplug and reinsert the PFoE Ethernet cable on the MPTACC card.
23. Create L1 LAG port. See the Alcatel-Lucent 9500 MPR-A Operation and
Administration, DLP-140 for a detailed procedure to create L1 LAG port.
24. Add MPT ODU radio interface to L1 LAG port. See the Alcatel-Lucent 9500 MPR-A
Operation and Administration, DLP-140 for a detailed procedure to create L1 LAG
port.
25. NOTE: To complete the upgrade to MPT ODU L1 LAG Port, this procedure must be
performed on both ends of the radio hop.

63 — DLP-124 Upgrade MPT-HL to MPT-HL
L1 LAG port
63.1 — Purpose
This procedure describes how to upgrade an In-Service MPT-HL radio hop to an MPT-HL
configured as an L1 LAG Lowest Index Port.
63.2 — General
This upgrade procedure provides general steps and the sequence required to upgrade an
MPT-HL radio port In-Service to an MPT-HL configured as an L1 LAG Lowest Index Port.
Supported configurations are as follows:
• 1+0 to 1+0 L1 LAG Port

• 1+1 HSB to 1+1 HSB L1 LAG Port
• 1+1 FD to 1+1 L1 LAG Ports
Upgrade from an 1+1 FD to 2+0 L1 LAG Ports is not supported. To accomplish this
upgrade perform the following steps:
• Down grade the 1+1 FD to 1+0 not protected.upgrade, see DLP-117 Protection upgrade
and downgrade procedures for a detailed procedure to download.
• Perform this procedure in its entirety
• Add the second MPT-HL radio port to the L1 LAG port
The MPT-HL radio ports to be upgraded to L1 LAG port(s) must reside in P8ETH card
Ethernet port 5 or 7 to be a candidate for this upgrade procedure.
The L1 LAG Lowest Index Port must be located in P8ETH card Ethernet port 5 or 7.
During this procedure the following parameters are re-provisioned to the L1 LAG port:

63 — DLP-124 Upgrade MPT-HL to MPT-HL L1 LAG port
• Cross-Connections
• VLANs
• Port Segregation
• PPP-RF
• Synchronization
The Max User Bandwidth available for a radio port configured as an L1 LAG port member
is ninety-five percent of the pre-migration MPT-HL radio port capacity. The reduction in
Max User Bandwidth must be accounted for prior to migration to an L1 LAG port. Failure
to account for this reduction in Max User Bandwidth may result in a loss of ALL
cross-connected traffic after the migration to the L1 LAG port.
TDM2TDM and TDM2ETH services supported by the L1 LAG port require a different
amount of bandwidth then when supported by an MPT-HL radio port. The required
bandwidth for cross-connected services must be recalculated to ensure that the
cross-connected services do not exceed the Max User Bandwidth of the new L1 LAG port.
Failure to confirm that all services are supported by the new L1 LAG port may result in a
loss of ALL cross-connected traffic after the migration to the L1 LAG port. For information
regarding bandwidth required based upon type of service, see Table 63.1. To calculate the
required bandwidth for cross-connected services, use the following equation:
Required Bandwidth = (# DS1 TDM2TDM x 2080) + (# DS1 TDM2ETH

x 1882) +
(# DS3 TDM2TDM x 60264) + (# DS3 TDM2ETH x 46571)
Table 63.1 — MPT-HL L1 LAG bandwidth per service type
Type of service L1 LAG bandwidth used [Kbps] MPT-HL bandwidth used [Kbps]
DS1 TDM2TDM 2080 1683
DS1 TDM2Eth 1882 1694
DS3 TDM2TDM 60264 48756
DS3 TDM2Eth 46571 45574
Caution: Possibility of service interruption: Migration to L1 LAG port impacts

TDM2TDM and TDM2ETH traffic on a per flow-id basis. Typical impact to traffic is less
than 10 seconds for each cross-connection.
The time required for the system to migrate the MPT-HL radio port to the L1 LAG port
is dependent upon radio port provisioning (synchronization, PPP RF, number of; port
segregations, VLANs, and cross-connections). Typical migration duration is less than
two minutes. Allow up to five minutes for the system to migrate all services from the
MPT-HL radio port to the L1 LAG port.

The number of possible radio configurations precludes covering all possible radio
configurations.
A site survey and site documentation must be provided to ensure that facilities that are NOT
associated with the upgrade MPT-HL radio direction are not impacted by this upgrade
procedure.
To complete the migration to an L1 LAG port, both ends of the MPT-HL radio direction
must be migrated.
See the Alcatel-Lucent 9500 MPR-A Product Information for a detailed description of the
L1 LAG feature and to determine card location and type.
63.3 — Procedure
2. CAUTION: Possibility of service interruption. Upgrading an MPT-HL radio port
to a L1 LAG port with cross-connections in excess of the supported Max User
Bandwidth will result in a loss of services on ALL cross-connected services
associated with the L1 LAG port.
3. CAUTION: Possibility of service interruption. Migration to L1 LAG port impacts
TDM2TDM and TDM2ETH traffic on a per flow-id basis. Typical impact to
traffic is less than 10 seconds for each cross-connection.
4. CAUTION: Possibility of service interruption. This is an In-Service procedure.


retaining screws.
9. Verify the NE is running R3.4.0 or higher software version.
10. Verify the MPT-HL radio channel is alarm/condition free and error free on both the
near and far ends of the radio hop.
11. Verify there are no unexpected and unexplained alarm/abnormal conditions declared
on the MSS-4/8 shelf supporting both the near and far ends of the radio direction.
12. Verify that ninety-five percent of the MPT-HL radio channel bandwidth is sufficient to
support the existing cross-connected services when configured in an L1 LAG port.
13. Perform a database backup. See the Alcatel-Lucent 9500 MPR-A Operation and
Administration, DLP-131 for a detailed procedure to perform a database backup.
14. If radio channel is configured in 1+1 HSB/FD configuration, verify that the radio link
is active on the main radio hop on both the near and far ends of the radio link for the
following:
• Equipment Protection Switching (EPS)
• Hot StandBy (HSB)
• Rx Radio (RPS)
15. If radio channel is configured in 1+1 HSB/FD configuration, perform Lockout
protection switch for the following:
• Rx Radio (RPS)
16. If MPT-HL radio interface is configured for 1+1 FD, and the desired configuration is
2+0 L1 LAG port, downgrade radio protection to 1+0. See the Alcatel-Lucent
9500 MPR-A Maintenance and Trouble Clearing, DLP-117 Protection upgrade and
downgrade procedures for a detailed procedure.
17. Download and save the Current Configuration file. See the Alcatel-Lucent 9500 MPR-
A Operation and Administration, DLP-116 for a detailed procedure to download and
save the current configuration file.
18. Create L1 LAG port. See the Alcatel-Lucent 9500 MPR-A Operation and
Administration, DLP-140 for a detailed procedure to create L1 LAG port.
19. CAUTION: Possibility of service interruption. Upgrading an MPT-HL radio port
to an L1 LAG port with cross-connections in excess of the supported Max User
Bandwidth will result in a loss of traffic on ALL cross-connected services
associated with the L1 LAG port.
20. CAUTION: Possibility of service interruption. Migration to L1 LAG port impacts
TDM2TDM and TDM2ETH traffic on a per flow-id basis. Typical impact to
traffic is less than 10 seconds for each cross-connection.

21. Add MPT-HL radio interface to L1 LAG port. See the Alcatel-Lucent 9500 MPR-A
Operation and Administration, DLP-140 for a detailed procedure to create L1 LAG
port.
When you add the radio port to the L1 LAG port, the following message will display.
Figure 63.1 — MPT-HL to L1 LAG information message
22. Click on the OK button.

After you click on the OK button, the following warning message will display.
Figure 63.2 — MPT-HL to L1 LAG warning message
23. Click on the Yes button.

24. Wait for the system to migrate services to the L1 LAG port.
The time required for the system to migrate the MPT-HL radio port to the L1 LAG port
is dependent upon radio port provisioning (synchronization, PPP RF, number of; port
segregations, VLANs, and cross-connections provisioned). Typical migration duration
is two minutes or less. Allow up to five minutes for the system to migrate all services
from the MPT-HL radio port to the L1 LAG port. When the system has completed
migrating to the L1 LAG port you will be prompted to close the Craft Terminal.
25. Close the Craft Terminal.
26. Reopen the Craft Terminal and log in to the NE.
29. Download and save the Current Configuration file.
30. Using the Current Configuration files downloaded in steps 17 and 29, verify that the
following provisioning parameters were re-provisioned correctly:
• Cross-Connections
• VLANs

• Port Segregation
• PPP-RF
• Synchronization
31. If radio channel is configured in 1+1 HSB/FD configuration, release Lockout
protection switch for the following:
• Rx Radio (RPS)
32. NOTE: To complete the upgrade to MPT-HL L1 LAG Port, this procedure must be
performed on both ends of the radio direction.

64 — DLP-125 MPT Power Unit
replacement
64.1 — Purpose
This procedure describes how to replace a MPT Power Unit or MPT Extended Power Unit.
64.3 — General
The MPT Power Unit and MPT Extended Power Unit are stand-alone units.
The MPT Power Unit provides power for up to four MPT-HC/MPT-XP/9558HC

(MPT ODU) based radio channels.
The MPT Extended Power Unit provides power for up to two MPT ODU based radio
channels.
Power Unit replacement affects traffic on ALL radio channels that are associated with the
Power Unit. Fully understand the ramifications to ALL radio channels before beginning the
Power Unit Replacement Procedure. Verify that radio protection is available for all traffic
that is supported by the Power Unit to be replaced or an appropriate maintenance window
is scheduled per local practices and procedures.
The Power Unit must be powered down during the replacement procedure.
type.

64 — DLP-125 MPT Power Unit replacement
64.4 — Procedure
3. CAUTION: Possibility of service interruption. Replacing an in-service MPT
Power Unit causes loss of traffic on ALL radio channels that are associated with
the MPT Power Unit.
6. MPT power unit replacement procedure
Determine the Power Unit configuration.
a. Does the Power Unit support one, two, or more radio channels?
b. Is traffic supported on one, two, or more radio channels?
procedures.
8. Is it appropriate to proceed with Power Unit replacement procedure?
Unit causes loss of traffic on ALL radio channels associated with the Power Unit.
10. Verify that all cable connections to the Power Unit to be replaced are properly labeled.
11. Locate the fuses protecting the A and B battery feeds to the Power Unit and remove.
12. Disconnect all of the cables that are connected to the front of the Power Unit.
13. Remove the Power Unit to be replaced from the bracket.
14. Install the Power Unit onto the bracket.
15. Connect all of the cables to the front of the Power Unit that you disconnected in step 12.

MPT ODUs. Wait for Dialog Failure condition to clear before proceeding.
18. Verify all the MPT ODUs that are associated with the replacement Power Unit are free
of alarms using Alarm Monitor.
19. Verify all the radio channels that are supported by the Power Unit are error free.
20. Are ALL the MPT ODUs that are associated with the replacement Power Unit error
free and free of alarms?


65 — DLP-126 SDHACC (2-Port OC-3)
Replacement
65.1 — PURPOSE
This procedure describes how to replace a SDHACC card.
65.2 — PREREQUISITES
65.3 — GENERAL
The OC-3 SDHACC card can be installed in any of the universal MSS-8 slots (3 through
8) and MSS-4 slots (3 through 4).
The MSS-8 can be configured with a maximum of six optional SDHACC cards; three
protected pairs, six unprotected cards, or a combination of protected pairs and unprotected
cards.
The MSS-4 can be configured with a maximum of two optional SDHACC cards; one
protected pair or two unprotected cards.
In protected OC-3 configurations, the main SDHACC is resident in slots 3, 5, and/or 7. The
spare SDHACC is resident in slots 4, 6, and/or 8 respectively. The main and spare cards
In unprotected OC-3 configurations, performing the SDHACC removal and replacement

a disruptionless procedure.

65 — DLP-126 SDHACC (2-Port OC-3) Replacement
type.
65.4 — Procedure
3. CAUTION: Possibility of service interruption. In protected OC-3 configurations,
the Main SDHACC cards reside in slots 3, 5, and/or 7. The Spare SDHACC cards
retaining screws.
9. SDHACC Replacement Procedures
Is the SDHACC to be replaced in a protected system?


11. Is the SDHACC to be replaced the main or spare?
13. Go to step 15.
15. Verify that the SDHACC to be replaced status is Standby.
17. Verify that all cable connections to the SDHACC card to be replaced are properly
labeled.
18. Remove the SDHACC to be replaced. See DLP-100 Mechanical card removal and
19. Disconnect the OC-3 input and output cables.
20. Install the replacement SDHACC into the shelf, but do not seat the card at this time.
See DLP-100 Mechanical card removal and installation for information about how to
install card.
21. Connect the OC-3 input and output cables.
retaining screws.
23. Install the replacement SDHACC into the shelf.
25. Verify the replacement SDHACC alarms, that the status is normal, and capable of
26. Is the replacement SDHACC status normal and capable of carrying traffic?
27. Is the replacement SDHACC in a protected system?
28. CAUTION: Possibility of service interruption. Releasing the Forced/Lockout EPS
Switch using the Craft Terminal.
29. Release the Forced/Lockout EPS Switch using the Craft Terminal..
30. Go to step 32.


66 — DLP-127 Software package rollback
66.1 — Purpose
This procedure describes how to rollback to the previous software package version on a
9500 MPR-A system.
66.2 — General
The system supports software package rollback to the previous committed software
version. Software package rollback is supported when the software package and the MSS
database for the previous committed software version are both still present on the Core-E
flash card.
All configuration changes applied to the NE after the software version upgrade will be lost
during the software package rollback operation.
Caution: Possibility of service interruption: The software package rollback operation

WILL impact traffic including a possible long out-of service period. For this reason
software package rollback should be considered as a critical operation to be
performed as a last resort only after all other alternatives have been explored.
Software package rollback functionality was added in R4.0.0 and is available for software
upgrades from R4.0.0 and greater. Table 66.1 provides a list of supported software package
rollbacks:
Table 66.1 — Releases supporting software package rollback
Initial software Upgrade software Software package

release version release version rollback support
(Current Status: ‘Stand by’) (Current Status: ‘Committed’)
R3.2.0, R3.3.0, or R3.4.0 R4.0.0 No
R3.4.0 R4.1.0 or greater No

Table 66.1 — Releases supporting software package rollback (Continued)
Initial software Upgrade software Software package

release version release version rollback support
(Current Status: ‘Stand by’) (Current Status: ‘Committed’)
R4.0.0 or greater R4.1.0 or greater Yes
For a full description of the software package rollback feature, see the Alcatel-Lucent
9500 MPR-A Product Information.
66.3 — Procedure
• CAUTION: Possibility of service interruption. The software package rollback
operation WILL impact traffic including a possible long out-of service period. For
this reason software package rollback should be considered as a critical operation
to be performed as a last resort only after all other alternatives have been
explored.
33. Have all alternative been explored to resolve the system problem?
34. Have all appropriate levels of support been notified and all are in agreement that a
software package rollback is the appropriate next step?
35. Contact ALL appropriate levels of support and obtain all appropriate approvals as
required per local practices and procedures.
36. Have all appropriate levels of support been notified and are in agreement that a
software package rollback is the appropriate next step?
37. Software package rollback procedure
Caution: Possibility of service interruption. The software package rollback operation

WILL impact traffic including a possible long out-of service period. For this reason
software package rollback should be considered as a critical operation to be
performed as a last resort only after all other alternatives have been explored.
38. Open the NE Software Status Detail window.

From the Main Menu Bar select, SW Download>SW Status.

39. On the software bank with the Current Status Committed, verify the software version
matches that of the upgraded software package. See Figure 66.1.
Figure 66.1 — Software bank with upgrade software version Committed status
40. On the software bank with the Current Status Standby, verify the software version
matches that of the initial software package. See Figure 66.2.
Figure 66.2 — Software bank with Initial software version Standby status

41. Are the committed (upgrade) and standby (initial) software version verified and correct
as expected?
42. On the software bank for the standby software version, select from the Software
Management Action drop-down menu Forced Activation. See Figure 66.3.
Figure 66.3 — Software Management Action - Forced Activation
43. Select the Apply Action button. See Figure 66.3.

44. Communication with the NE will be lost. Wait until the Core-E card status LED is solid
green before proceeding to step 45.
45. Log in to the NE.
46. Open the NE Software Status Detail window.
From the Main Menu Bar select, SW Download>SW Status.
47. On the software bank with the Current Status Committed, verify the software version
matches that of the initial software package. See Figure 66.4.
48. On the software bank with the Current Status Standby, verify the software version
matches that of the upgrade software package. See Figure 66.5.

Figure 66.4 — Software bank with initial software version Committed status
Figure 66.5 — Software bank with upgrade software version Standby status
49. Are the committed (initial) and standby (upgrade) software version verified and correct
as expected?
50. Contact the next level of support for assistance.


67 — DLP-128 MSS-1 shelf replacement
67.1 — Purpose
This procedure describes how to replace a MSS-1 shelf.
67.3 — General
The MSS-1 shelf is a stand-alone unit.
The MSS-1 shelf supports up to four electrical Ethernet ports and up to two optical Ethernet
ports.
Each Ethernet port (electrical or optical) may support an MPT-HC/MPT-XP/9558HC

(MPT ODU) radio channel.
Each optical Ethernet port may support an MPT-HL/MPT-HLC radio channel.
Electrical Ethernet ports 1 and 2 may provide power to MPT ODU based radio channels.
The MSS-1 shelf supports up to sixteen DS1 ports.
MSS-1 shelf replacement affects traffic on ALL Ethernet ports, radio channels, and DS1
ports that are associated with the MSS-1 shelf. Fully understand the ramifications to ALL
Ethernet and DS1 ports, and radio channels before beginning the MSS-1 shelf Replacement
Procedure. Verify that an appropriate maintenance window is scheduled per local practices
and procedures.
The MSS-1 shelf must be powered down during the replacement procedure.

See the Alcatel-Lucent 9500 MPR-A Product Information to determine port location and
type.
67.4 — Procedure
1. CAUTION: Possibility of service interruption. Replacing an in-service MSS-1
shelf causes loss of traffic on ALL radio channels, Ethernet Ports, and DS1 ports
that are associated with the MSS-1 shelf.
MSS-1 shelf contain static-sensitive devices. These devices can be damaged by static
3. MSS-1 shelf replacement procedure
Determine the MSS-1 shelf configuration.
a. Does the MSS-1 support one or more radio channels?
b. Are DS1 ports configured and carrying traffic?
procedures.
5. Is it appropriate to proceed with MSS-1 shelf replacement procedure?
6. CAUTION: Possibility of service interruption. Replacing an in-service MSS-1
shelf causes loss of traffic on ALL radio channels, Ethernet Ports, and DS1 ports
associated with the MSS-1 shelf.
7. Verify that all cable connections to the MSS-1 shelf to be replaced are properly labeled.
8. TxMute all radio channels associated with MSS-1 shelf to be replaced.
9. Locate the fuses protecting the A and B battery feeds to the MSS-1 shelf and remove.
10. Disconnect all of the cables that are connected to the front of the MSS-1 shelf.
11. Remove the MSS-1 shelf to be replaced from the bracket.
12. Install the MSS-1 shelf onto the bracket.
13. Connect all of the cables to the front of the MSS-1 shelf that you disconnected in
step 10.

MPT ODUs and/or MPT-HL/MPT-HLCs. Wait for Dialog Failure condition to clear
before proceeding.
16. Verify the MPT ODUs and/or MPT-HL/MPT-HLCs that are associated with the
replacement MSS-1 shelf are free of alarms using Alarm Monitor.
17. Verify the radio channels that are supported by the MSS-1 shelf are error free.
18. Are ALL the MPT ODUs and/or MPT-HL/MPT-HLCs that are associated with the
replacement MSS-1 shelf error free and free of alarms?
19. Troubleshoot the MSS-1 shelf MPT ODU alarms.
21. Are the MSS-1 shelf MPT ODU alarms clear?
22. Are ALL the Ethernet ports that are associated with the replacement MSS-1 shelf error
free and free of alarms?
23. Troubleshoot the MSS-1 shelf Ethernet port alarms.
25. Are the MSS-1 shelf Ethernet port alarms clear?
26. Are ALL the MSS-1 shelf DS1 ports that are associated with the replacement MSS-1
shelf error free and free of alarms?
27. Troubleshoot the MSS-1 shelf DS1 port alarms.
29. Are the MSS-1 shelf DS1 port alarms clear?


68 — DLP-129 Resolve WebEML/TCO
Suite/NEtO startup issues
68.1 — Purpose
This procedure describes how to resolve WebEML/TCO Suite/NEtO startup issues.
This procedure also describes how to remove all previous versions of WebEML/TCO Suite
to prevent future startup issues.
Verify that ALL required R5.0 WebEML/TCO Suite versions of JUSM/MCT are loaded to
support ALL NEs within the network.
68.3 — General
A potential conflict may occur when running previous versions of the WebEML/TCO Suite
applications and the R5.0 applications.
If startup issues are encountered including “Fatal Error: RMI resources not available” or
“NEtO RMI Registry Error”, perform step 2 to resolve startup issues.
It is recommended to remove ALL previous versions of WebEML/TCO Suite applications

after the R5.0 version has been installed to prevent potential startup issues.
If previous versions of the WebEML/TCO suite are loaded on the user’s PC in addition to
R5.0 version, it is recommended to remove all previous versions (R4.10 and Prior) to
prevent potential startup issues. Perform step 9 to remove previous versions to the
WebEML/TCO suite.

68 — DLP-129 Resolve WebEML/TCO Suite/NEtO startup issues
68.4 — Procedure
1. Are you experiencing WebEML/TCO Suite application start up issues?
2. Resolve WebEML/TCO Suite application start up procedure
Turn “OFF” the FTP and/or the SFTP Servers if provisioned “ON”.
3. Close ALL open WebEML/TCO Suite applications, which include the following:
• NEtO
• JUSM
• Alarm Monitor
• Performance Monitoring Tool
• Event Log Browser
• Ethernet Feature Shell
• MCT
• NEtO Server Manager (NEtO Server Manager should close automatically. If it
does not automatically close, the user MUST manually close the NEtO Server
Manager.)
4. Using the Windows Task Manager, verify that none of the following processes are
running:
• NEtO.exe
• JAVA.exe
• RMIRegistry.exe
5. If any of the listed processes are running, select the listed process, then select End
Process.
6. Repeat step 5 until NO listed processes are running.
7. Restart R5.0 WebEML MPR TCO suite.
8. Did the WebEML/TCO Suite application(s) start properly?
9. Remove ALL previous versions of WebEML/TCO Suite procedure

Verify that ALL required software release versions are loaded on the user’s PC in the
WebEML MPR TCO R5.0 directory. If required software versions are not present, Load
all required versions prior to proceeding with this procedure. To load specific release
versions, refer to Alcatel-Lucent 9500 MPR-A Operation and Administration,
DLP-132 for a detailed procedure.
The default location for the WebEML/TCO suite is:
C:\ALCATEL\
10. Select ALL previous versions of WebEML MPR TCO Rx.y directories (R4.10 and
prior) and delete the folder(s).
11. Go to step 13.


Customer documentation and product
support
Customer documentation
http://www.alcatel-lucent.com/myaccess
Product manuals and documentation updates are available at alcatel-lucent.com. If you are
a new user and require access to this service, please contact your Alcatel-Lucent sales
representative.
Technical support
http://support.alcatel-lucent.com
Documentation feedback
documentation.feedback@alcatel-lucent.com
© 2014 Alcatel-Lucent. All rights reserved.
3EM 23956 AO Edition 01

9500 MPR-A R5 1 0 Maintenance - TroubleClearing 3EM23956AOAA - 01

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-A R5 1 0 Maintenance - TroubleClearing 3EM23956AOAA - 01

Uploaded by

Copyright:

Available Formats

Maintenance and Trouble Clearing 3EM23956AO Edition 01

Copyright 2014 Alcatel-Lucent.

All rights reserved.

2 — FCC part 15 subpart B ....................................................................................... 27

4 — Maintenance philosophy ..................................................................................... 33

9500 MPR-A Maintenance and Trouble Clearing 3EM23956AO Edition 01 5

6 — Electrostatic-sensitive devices ............................................................................. 57

7 — Product support information ............................................................................... 59

6 9500 MPR-A Maintenance and Trouble Clearing 3EM23956AO Edition 01

8 — IXL-100 Task index list ....................................................................................... 65

9 — IXL-101 Alarm and abnormal condition clearing procedures ........................................ 67

10 — IXL-102 Support procedures ............................................................................ 161

11 — IXL-103 Equipment replacement procedures........................................................ 163

12 — IXL-104 Supporting information ........................................................................ 165

13 — RTL-100 Preventive maintenance procedures ...................................................... 167

14 — TAP-100 Facility alarms .................................................................................. 169

15 — TAP-101 Abnormal conditions .......................................................................... 189

16 — TAP-102 Power alarms ................................................................................... 219

17 — TAP-103 Equipment alarms.............................................................................. 227

18 — TAP-104 Radio alarms (MPT-HC, MPT-HL, MPT-HLC, MPT-HLC, MPT-XP, MOD300,

9500 MPR-A Maintenance and Trouble Clearing 3EM23956AO Edition 01 7

20 — TAP-106 License/software mismatch.................................................................. 273

21 — TAP-107 Internal loss of communications ............................................................ 279

22 — TAP-108 Threshold crossing alarms (MOD300, MPT-HC, MPT-HL, MPT-HLC,

23 — TAP-109 Synchronization alarms (Core-E, MOD300, MPT-HC, MPT-HL, MPT-HLC,

24 — TAP-110 ATPC loop conditions (MOD300, MPT-HC, MPT-HL, MPT-HLC, MPT-XP,

25 — TAP-111 Cable LOS ........................................................................................ 321

26 — TAP-112 Loss of alignment (MOD300, MPT-HC, MPT-HL, MPT-HLC, MPT-XP,

8 9500 MPR-A Maintenance and Trouble Clearing 3EM23956AO Edition 01

29 — TAP-115 Rx fail (MOD300) ............................................................................... 351

30 — TAP-116 Housekeeping alarms.......................................................................... 357

31 — TAP-117 LAG alarms (Core-E, MPT-HC, MPT-HL, MPT-HLC, MPT-XP, ODU300,

32 — TAP-118 Ethernet connectivity fault management alarms ....................................... 363

34 — TAP-120 Duplicate Address Detected alarms ........................................................ 375

35 — TAP-121 Combiner loss of alignment (MPT-HLC).................................................... 383

36 — TAP-122 Fan Fail .......................................................................................... 387

9500 MPR-A Maintenance and Trouble Clearing 3EM23956AO Edition 01 9

37 — TAP-123 RF Switch Fail (MPT-HLC) .................................................................... 391

38 — TAP-124 Rx diversity missing (MPT-HLC) ............................................................. 395

39 — DLP-100 Mechanical card removal and installation ................................................ 399

40 — DLP-101 MPT-HL/MPT-HLC transceiver air filter replacement ................................... 401

41 — DLP-102 SFP replacement ............................................................................... 403

42 — DLP-103 Core switching module (Core-E) replacement ........................................... 405

10 9500 MPR-A Maintenance and Trouble Clearing 3EM23956AO Edition 01

46 — DLP-107 MOD300 (radio modem) replacement...................................................... 433

47 — DLP-108 MPT-HL/MPT-HLC transceiver replacement .............................................. 437

48 — DLP-109 ODU300 replacement ......................................................................... 441

49 — DLP-110 P2E3DS3 (2-Port DS3) replacement ........................................................ 445

50 — DLP-111 P32E1DS1 (32-Port DS1) replacement ..................................................... 449

51 — DLP-112 Clean fiber-optic connectors ................................................................ 453

52 — DLP-113 System power down and power up ......................................................... 459

9500 MPR-A Maintenance and Trouble Clearing 3EM23956AO Edition 01 11

54 — DLP-115 MPT ODU replacement (MPT-HC, MPT-XP, 9558HC) .................................... 467

55 — DLP-116 Auxiliary (AUX) replacement ................................................................ 473

56 — DLP-117 Protection upgrade and downgrade procedures......................................... 475

57 — DLP-118 Upgrade and downgrade radio profile ..................................................... 485

59 — DLP-120 +24/-48 volt converter replacement....................................................... 493

60 — DLP-121 Power injector replacement................................................................. 497

12 9500 MPR-A Maintenance and Trouble Clearing 3EM23956AO Edition 01

62 — DLP-123 Upgrade MPT ODU to MPT ODU L1 LAG port.............................................. 505

63 — DLP-124 Upgrade MPT-HL to MPT-HL L1 LAG port.................................................. 509

64 — DLP-125 MPT Power Unit replacement ............................................................... 515

65 — DLP-126 SDHACC (2-Port OC-3) Replacement ....................................................... 519