9500 mpr-a r4 2 0 maintenance_troubleclearing 3em23956amaa_01.pdf

Alcatel-Lucent 9500MICROWAVE PACKET RADIO for ANSI | RELEASE 4.2.0Indoor: MSS-8/MSS-4/MSS-1/MPT-HLOutdoor: ODU300/MPT-HC/MPT-XP/9558HC

Alcatel-Lucent ProprietaryThis document contains proprietary information of Alcatel-Lucent and is not to be disclosedor used except in accordance with applicable agreements.Copyright 2013 © Alcatel-Lucent. All rights reserved.

Main Documentation

Maintenance and Trouble Clearing

Maintenance and Trouble Clearing3EM23956AMAA Edition 01

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 2013 Alcatel-Lucent.

All rights reserved.

Disclaimers

Alcatel-Lucent products are intended for commercial uses. Without the appropriate network design engineering, they must not be sold, licensed or otherwise distributed for use in any hazardous environments requiring fail-safe performance, such as in the operation of nuclear facilities, aircraft navigation or communication systems, air traffic control, direct life-support machines, or weapons systems, in which the failure of products could lead directly to death, personal injury, or severe physical or environmental damage. The customer hereby agrees that the use, sale, license or other distribution of the products for any such application without the prior written consent of Alcatel-Lucent, shall be at the customer's sole risk. The customer hereby agrees to defend and hold Alcatel-Lucent harmless from any claims for loss, cost, damage, expense or liability that may arise out of or in connection with the use, sale, license or other distribution of the products in such applications.

This document may contain information regarding the use and installation of non-Alcatel-Lucent products. Please note that this information is provided as a courtesy to assist you. While Alcatel-Lucent tries to ensure that this information accurately reflects information provided by the supplier, please refer to the materials provided with any non-Alcatel-Lucent product and contact the supplier for confirmation. Alcatel-Lucent assumes no responsibility or liability for incorrect or incomplete information provided about non-Alcatel-Lucent products.

However, this does not constitute a representation or warranty. The warranties provided for Alcatel-Lucent products, if any, are set forth in contractual documentation entered into by Alcatel-Lucent and its customers.

This document was originally written in English. If there is any conflict or inconsistency between the English version and any other version of a document, the English version shall prevail.

© Alcatel-Lucent 2013 - All Rights ReservedPrinted in U.S.A.

THIS PRODUCT COMPLIES WITH D.H.H.S. RADIATION PERFORMANCE STANDARDS 21CFR, 1040.10, FOR A CLASS 1 LASER PRODUCT.

DANGER

Invisible laser radiation is present when the optic connector is open. AVOID DIRECTEXPOSURE TO BEAM.

WARNING

This equipment has been tested and found to comply with the limits for a Class A digital device, pursuantto Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmfulinterference 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 theinstruction manual, may cause harmful interference to radio communications. Operation of this equipmentin a residential area is likely to cause harmful interference in which case users will be required to correct theinterference at their own expense.

NOTICE

This manual applies to 9500 MPR-A R4.2.0 software. Release notes describing revisions to this softwaremay impact operations described in this manual.

This transfer of commodities, technology, or software, if from the United States, is an export in accordancewith the U.S. Export Administration Regulations. Diversion contrary to U.S. law is prohibited. The export orre-export (further transfer) of such commodities, technology, software or products made from suchtechnology is prohibited without proper authorization(s) from the U.S. Department of Commerce or otherappropriate U.S. government agency(s).

All rights reserved. No part of this manual may be reproduced, translated, stored in a retrieval system, ortransmitted or distributed by any means, electronic or mechanical, by photocopying, recording, or otherwise,without the written permission of Alcatel-Lucent. Preparing derivative works or providing instruction basedon the material is prohibited unless agreed to in writing by Alcatel-Lucent.

The product specification and/or performance levels contained in this document are for informationpurposes only and are subject to change without notice. They do not represent any obligation on the part ofAlcatel-Lucent. Such obligations will only be committed to in a written sales agreement signed byAlcatel-Lucent.

3EM23956AMIssue 01, February 2013

© Alcatel-Lucent 2013 - All Rights Reserved i

ALCATEL-LUCENT PRACTICEStandard

Table of Contents

FCC part 15 subpart B

1. 9500 MPR-A unlicensed radio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1FCC Class B compliance statement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1FCC Class B requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Introduction

1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Writing conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Admonishments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Related documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Document types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

2. Maintenance philosophy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5Before going to site checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6Troubleshooting basics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8Path problems on a commissioned link . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10Path problems on a new link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11Troubleshooting configuration problems . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12Troubleshooting ethernet problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13

3. Safety awareness. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15Safety EMC-EMF-ESD norms and equipment labeling . . . . . . . . . . . . . . . 1-15Safety rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15General rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15Labels indicating danger, forbiddance, command . . . . . . . . . . . . . . . . . . . 1-16

4. Electrostatic-sensitive devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-29Electrostatic-sensitivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-29Handling circuit packs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-30

5. Product support information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-31Telephone support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-31Product documentation and training. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-31Technical support center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-33Repair and return services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-34Spare parts and replacement cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-34Service center. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-35Installation and maintenance services . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-36


Table of Contentsii

Index Task Lists (IXLs)

IXL-100 Task index list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

IXL-101 Alarm and abnormal condition clearing procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

IXL-102 Support procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-57

IXL-103 Equipment replacement procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-59

IXL-104 Supporting information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-61

Routine Task Lists (RTLs)

RTL-100 Preventive maintenance procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Trouble Analysis Procedures (TAPs)

TAP-100 Facility alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

TAP-101 Abnormal conditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-23

TAP-102 Power alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-31

TAP-103 Equipment alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-39

TAP-104 Radio alarms (MPT-HC, MPT-HL, MPT-XP, MOD300, ODU300, 9558HC) . . . . . . . . 8-57

TAP-105 Ethernet alarms (Core-E, MPTACC, P8ETH, MSS-1 Shelf Core) . . . . . . . . . . . . . . . . 8-77

TAP-106 License/software mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-79

TAP-107 Internal loss of communications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-83

TAP-108 Threshold crossing alarms (MOD300, MPT-HC, MPT-HL, MPT-XP,9558HC, P32E1DS1, MSS-1 shelf P32E1DS1). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-99

TAP-109 Synchronization alarms (Core-E, MOD300, MPT-HC, MPT-HL, MPT-XP,P32E1DS1, SDHACC, 9558HC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-105

TAP-110 ATPC loop conditions (MOD300, MPT-HC, MPT-HL, MPT-XP, 9558HC). . . . . . . . . 8-117

TAP-111 Cable LOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-123

TAP-112 Loss of alignment (MOD300, MPT-HC, MPT-HL, MPT-XP, 9558HC) . . . . . . . . . . . . 8-129

TAP-113 Loss of frame (MOD300, MPT-HC, MPT-HL, MPT-XP, 9558HC) . . . . . . . . . . . . . . . 8-135


Table of Contents iii

TAP-114 RPS path fail (MPT-HC, MPT-HL, MPT-XP, 9558HC). . . . . . . . . . . . . . . . . . . . . . . . 8-147

TAP-115 Rx fail (MOD300) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-153

TAP-116 Housekeeping alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-159

TAP-117 LAG alarms (Core-E, MPT-HC, MPT-HL, MPT-XP, ODU300, 9558HC,MSS-1 shelf Core) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-161

TAP-118 Ethernet connectivity fault management alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-163

TAP-119 Clock failure (MPT-HC, MPT-HL, MPT-XP, 9558HC) . . . . . . . . . . . . . . . . . . . . . . . . 8-167

TAP-120 Duplicate Address Detected alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-175

Detailed Level Procedures (DLPs)

DLP-100 Mechanical card removal and installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

DLP-101 MPT-HL transceiver air filter replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3

DLP-102 SFP replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5

DLP-103 Core switching module (Core-E) replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7

DLP-104 Core switching module (Core-E) flash card replacement. . . . . . . . . . . . . . . . . . . . . . . 9-13

DLP-105 Ethernet access switch (P8ETH) replacement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-21

DLP-106 MSS-4/8 shelf FAN replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-27

DLP-107 MOD300 (radio modem) replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-29

DLP-108 MPT-HL transceiver replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-33

DLP-109 ODU300 replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-37

DLP-110 P2E3DS3 (2-Port DS3) replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-41

DLP-111 P32E1DS1 (32-Port DS1) replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-45

DLP-112 Clean fiber-optic connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-49

DLP-113 System power down and power up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-55

DLP-114 MPTACC (MPT Access) replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-59


Table of Contentsiv

DLP-115 MPT ODU replacement (MPT-HC, MPT-XP, 9558HC) . . . . . . . . . . . . . . . . . . . . . . . . 9-65

DLP-116 Auxiliary (AUX) replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-71

DLP-117 Protection upgrade and downgrade procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-73

DLP-118 Upgrade and downgrade radio profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-83

DLP-119 Upgrade unlicensed MPT-HL radio to lower 6 GHz radio . . . . . . . . . . . . . . . . . . . . . . 9-87

DLP-120 +24/-48 volt converter replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-91

DLP-121 Power injector replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-95

DLP-122 RPS/XPIC module replacement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-99

DLP-123 Upgrade MPT ODU to MPT ODU L1 LAG port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-105

DLP-124 Upgrade MPT-HL to MPT-HL L1 LAG port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-109

DLP-125 MPT Power Unit replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-115

DLP-126 SDHACC (2-Port OC-3) Replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-119

DLP-127 Software package rollback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-123

DLP-128 MSS-1 shelf replacement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-129


List of Figures v

List of FiguresFigure 3-1. Anti static protection device kit ..................................................................................... 1-25

Figure 4-1. Electrostatic-sensitive sign........................................................................................... 1-29

Figure 112-1. Fiber-optic connector inspection .................................................................................. 9-51

Figure 112-2. Fiber-optic connector types, illustrations...................................................................... 9-52

Figure 112-3. Fiber-optic connector types, photographs.................................................................... 9-53

Figure 120-1. +24/-48 Volt converter cabling diagram ....................................................................... 9-93

Figure 124-1. MPT-HL to L1 LAG information message .................................................................. 9-113

Figure 124-2. MPT-HL to L1 LAG warning message ....................................................................... 9-113

Figure 127-2. Software bank with upgrade software version Committed status .............................. 9-125

Figure 127-3. Software bank with Initial software version Standby status ....................................... 9-125

Figure 127-4. Software Management Action - Forced Activation ..................................................... 9-126

Figure 127-5. Software bank with initial software version Committed status ................................... 9-127

Figure 127-6. Software bank with upgrade software version Standby status................................... 9-127


List of Figuresvi


List of Tables vii

List of TablesTable 100-A. Task Index List ............................................................................................................... 2-1

Table 101-A. Equipment friendly name syntax definitions................................................................... 3-5

Table 101-B. Friendly name syntax definitions.................................................................................... 3-6

Table 101-C. Alarm monitor alarm types ............................................................................................. 3-8

Table 101-D. Abnormal condition ...................................................................................................... 3-40

Table 101-E. Core-E Card LED indications ....................................................................................... 3-50

Table 101-F. MSS-1 shelf LED indications........................................................................................ 3-51

Table 101-G. Transport Card LED indications ................................................................................... 3-52

Table 101-H. Ethernet LED indications.............................................................................................. 3-52

Table 101-I. MPT-HL transceiver LED alarm indications ................................................................. 3-53

Table 101-J. TMN network troubleshooting ...................................................................................... 3-54

Table 102-A. Support procedures...................................................................................................... 4-57

Table 103-A. Equipment replacement procedures ............................................................................ 5-59

Table 104-A. Supporting information ................................................................................................. 6-61

Table 100-A. Preventive maintenance procedures.............................................................................. 7-1

Table 100-A. Facility alarms ................................................................................................................ 8-2

Table 101-A. Abnormal conditions..................................................................................................... 8-24

Table 102-A. Power Alarms............................................................................................................... 8-32

Table 103-A. Equipment alarms ........................................................................................................ 8-40

Table 104-A. Radio alarms ................................................................................................................ 8-58

Table 105-A. Ethernet alarms............................................................................................................ 8-77


List of Tablesviii

Table 106-A. License/software mismatch alarms .............................................................................. 8-79

Table 107-A. Internal communication problem alarms ...................................................................... 8-84

Table 108-A. Threshold crossing alarms ......................................................................................... 8-100

Table 109-A. Sync alarms ............................................................................................................... 8-106

Table 110-A. ATPC loop conditions................................................................................................. 8-118

Table 111-A. Clear radio alarms...................................................................................................... 8-123

Table 112-A. Loss of alignment alarms ........................................................................................... 8-129

Table 113-A. Loss of frame radio alarms......................................................................................... 8-135

Table 114-A. RPS path fail alarms .................................................................................................. 8-147

Table 115-A. Rx fail alarms ............................................................................................................. 8-153

Table 116-A. Housekeeping alarms ................................................................................................ 8-159

Table 117-A. LAG alarms ................................................................................................................ 8-161

Table 118-A. ECFM alarms ............................................................................................................. 8-164

Table 119-A. Clock failure alarm ..................................................................................................... 8-167

Table 120-A. Duplicate address detected alarms............................................................................ 8-176

Table 122-A. MPT ODU 1+1 module details ..................................................................................... 9-99

Table 124-A. MPT-HL L1 LAG bandwidth per service type............................................................. 9-110

Table 127-A. Releases supporting software package rollback........................................................ 9-123


FCC part 15 subpart B 1-1

FCC part 15 subpart B

1. 9500 MPR-A unlicensed radio

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

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

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

1.4 The 9558HC 5.8 Unlicensed band (JF6-9558HC/6933B-9558HC) has been certified by the FCC and Industry Canada as of August 7, 2012.

FCC Class B compliance statement

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


FCC part 15 subpart B1-2

FCC Class B requirements

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

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

Regulatory compliance warning: Physical changes or modifications to the JF6-9558H/6933B-9500MPT and JF6-9558HC/6933B-9558HC (unlicensed) radio are strictly prohibited.


Introduction 1-1

Introduction

1. Overview

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

Writing conventions

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

Admonishments

1.3 To avoid hazardous conditions, observe the following admonishments:

DANGER Possibility of personal injury.

CAUTION Possibility of service interruption.

WARNING Possibility of equipment damage.

Related documentation

1.4 For additional system information, refer to the following related documents:

• 9500 MPR-A Product Information manual (PN 3EM23952AM)

• 9500 MPR-A Installation Practices manual (PN 3EM23953AM)

• 9500 MPR-A Operation and Administration manual (PN 3EM23954AM)

• 9500 MPR-A Turn-Up manual (PN 3EM23955AM)


Introduction1-2

• 9500 MPR-A Engineering Support Documentation (PN 3EM23957AM)

• 9500 MPR MPT-GC User Manual manual (PN 3DB19205AA)

• 9500 MPR MPR-e User Manual manual (PN 3DB19901EC)

• 9500 MPR MSS-1c User Manual manual (PN 3DB19901DC)

Document types

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

Task index list (IXL)

1.6 IXLs group procedures by function. Each IXL lists procedures alphabetically by name and refers the user to the appropriate procedure number.

Routine task list (RTL)

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

Trouble analysis procedure (TAP)

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


Introduction 1-3

Detailed level procedure (DLP)

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


Introduction1-4


Introduction 1-5

2. Maintenance philosophy

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

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

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

Troubleshooting

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

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


Introduction1-6

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

Before going to site checklist

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


Introduction 1-7

• 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?

• 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?

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.


Introduction1-8

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

Troubleshooting basics

2.7 This section provides general guidance on 9500 MPR-A troubleshooting:

2.8 Check front-panel LED indications. These provide summary alarm indications, which can help narrow down the location and type of failure. See IXL-101 for more information.

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

2.9 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 101-C for probable cause and recommended action.

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


Introduction 1-9

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

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

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

2.13 MSS before an ODU. If there is doubt about whether a fault is in the MSS or ODU, always troubleshoot the MSS first.

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

2.15 Plug-in restoration time. Ensure adequate time is allowed for services to resume when a plug-in is replaced.

Troubleshooting path problems

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


Introduction1-10

2.17 Normally a path problem is signalled by a reduced RSL, and depending on its severity, a high BER.

2.18 Only in worst case situations, such as an antenna knocked out of alignment, will a path fail completely, and stay that way.

2.19 For weather-related problems, such as rain or ducting, the path problem will disappear as the weather returns to normal.

Path problems on a commissioned link

2.20 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

Weather-related path degradation

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

A path extends from ODU or MPT-HL antenna port to ODU or MPT-HL antenna port.


Introduction 1-11

Changed antenna alignment or antenna feed problem

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

New path obstruction

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

Interference from other signal sources

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

Path problems on a new link

2.25 For a new link, potential problems can extend to also include:

• Incorrect antenna alignment

• Mismatching antenna polarizations

• Incorrect path calculations

• Reflections

Incorrect antenna alignment

2.26 One or both antennas incorrectly aligned. Refer to 9500 MPR-A Turn-Up manual (PN 3EM23955AM) Antenna Polarization Verification (DLP-105) Antenna Feedhorn Verification - XPD Procedure.

Mismatching antenna polarizations

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


Introduction1-12

Incorrect path calculations

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

Reflections

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

Troubleshooting configuration problems

2.30 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

Compatibility problems

2.31 The two alarms that may activate are Configuration Not Supported and SW/HW Incompatible:

2.32 Configuration Not Supported: The plug-in installed is not enabled or is incorrect for the configuration.

Incorrect circuit connections

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

2.34 Take extra care when configuring ring circuits.


Introduction 1-13

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

Incorrect ID naming and commissioning

2.36 All traffic-carrying circuits must have a unique flow ID for the cross-connect capability to operate.

Incorrect/incompatible trib settings

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

Troubleshooting ethernet problems

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

2.39 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

2.40 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 101-H for LEDs that are locally at the alarmed site.

2.41 In order for the green Link LED to light:

1. Cable must be connected to Ethernet port

2. Ethernet port must be enabled (provisioned Enabled on Core Settings Screen)

3. Speed and mode (on Core Settings Screen) must be provisioned the same as the link partner.


Introduction1-14

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

Troubleshooting TMN problems

2.43 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 sections 2.38 to 2.42.

2.44 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 101-J for information about TMN network troubleshooting.


Introduction 1-15

3. Safety awareness

Safety EMC-EMF-ESD norms and equipment labeling

3.1 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

Safety rules

General rules

3.2 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

Observe safety rules

3.3 When equipment is operating, do not access the equipment parts which are protected with Cover Plate Shields removable with tools.

3.4 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�.


Introduction1-16

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

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

3.6 It is recommended to use a slightly wet cleaning cloth.

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

3.8 Whenever the safety protection features have been impaired, REMOVE POWER.

3.9 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:

Labels indicating danger, forbiddance, command

3.10 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


Introduction 1-17

3.11 Pay attention to the information stated in the following, and proceed as instructed.

Dangerous electrical voltages

Labeling:

3.12 The following warning label is affixed next to dangerous voltages (>42.4 Vp; >60 VDC).

3.13 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.:

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.


Introduction1-18

Safety instructions:

DANGER! Possibility of personal injury:

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

Risks of explosions

Labeling:

3.15 This risk is present when batteries are used, and it is signaled by the following label:


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


Introduction 1-19

Moving mechanical parts

Labeling:

3.17 The following warning label is affixed next to fans or other moving mechanical parts:


3.18 Before carrying out any maintenance operation see that all the moving mechanical parts have been stopped.

Equipment connection to earth

Labeling:

3.19 Terminals for equipment connection to earth, to be done according to international safety standards, are pointed out by the suitable symbol:


Introduction1-20


3.20 The position of earth connection terminals is specified in the Hardware Installation section.

Heat-radiating mechanical parts

Labeling:

3.21 The presence of heat-radiating mechanical parts is indicated by the following warning label in compliancy with IEC 417 Norm, Fig.5041:

DANGER! Possibility of personal injury:


3.22 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:

3.23 Personal injury can be caused by heat. Avoid touching powered terminals with any exposed part of your body.


Introduction 1-21

Microwave radiations (EMF norms)

3.24 Equipment emitting RF power (Reminder from site preparation procedure):

3.25 The site must be compliant with ICNIRP guidelines or local regulation if more restrictive.


3.26 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 delimitating 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.

3.27 Always remember that someone standing in front of the 9500 MPR-A antenna may cause traffic shutdown.

3.28 Place the relevant stickers:

EMF emission warning sign


Introduction1-22

3.29 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�

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

3.31 On the antenna (rear side)

• EMF emission warning sign, placed on the antenna.

Compliance boundaries for 9500 MPR-A transceivers with 1ft (30 cm) antenna:

Electromagnetic compatibility (EMC norms)

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

3.33 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

System Modulation Worst Configuration A (m) B (m)


Introduction 1-23

3.34 The norms set down to guarantee EMC compatibility, are distinguished inside this Manual by the symbol and term:

1. EMC General Norms - Installation

• All connections (towards the external source of the equipment) made with shielded cables use only cables and connectors suggested in this Manual or in the relevant Plant Documentation, or those specified in the Customer's �Installation Norms� (or similar documents)

• Shielded cables must be suitably terminated

• Install filters outside the equipment as required

• Ground connect the equipment utilizing a conductor with proper diameter and impedance

• Mount shields (if utilized), previously positioned during the installation phase, but not before having cleaned and degrease it.

• Before inserting the shielded unit proceed to clean and degrease all peripheral surfaces (contact springs and connection points, etc.)

• Screw fasten the units to the subrack.

• To correctly install EMC compatible equipment follow the instructions given.

2. EMC General Norms - Turn-on, Tests & Operation

• Preset the electrical units as required to guarantee EMC compatibility

• Check that the equipment is operating with all the shields properly positioned (dummy covers, ESD connector protections, etc.)

• To properly use EMC compatible equipment observe the information given

3. EMC General Norms - Maintenance

• Before inserting the shielded unit, which will replace the faulty or modified unit, proceed to clean and degrease all peripheral surfaces (contact springs and connection points, etc.)

• Clean the dummy covers of the spare units as well.

EMC Norms


Introduction1-24

• Screw fasten the units to the subrack.

Equipment protection against electrostatic discharges

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

3.36 Most electronic devices are sensitive to electrostatic discharges, to this concern the following warning labels have been affixed:

3.37 Observe the precautionary measures stated when having to touch the electronic parts during the installation/maintenance phases.

3.38 Workers are supplied with anti static protection devices consisting of an elasticized band worn around the wrist and a coiled cord connected to the elasticized band and to the stud on the subrack. See Figure 3-1.

Cautions to avoid equipment damage

Anti static protection device kit

3.39 Whenever is necessary to handle spare parts and cards out of their own box, this kit, as shown in Figure 3-1, 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.


Introduction 1-25

Screw fixing

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

MSS-ODU300 cable disconnection / connection

3.41 To avoid equipment damage, always unplug the MOD300 card first before disconnecting the MSS-ODU300 cable (at MSS or ODU300 side).

Fan, equipment rack, and equipment cabinet precautions

3.42 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 Alcatel-Lucent 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.

Figure 3-1. Anti static protection device kit


Introduction1-26

DANGER Possibility of personal injury. The Alcatel-Lucent 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 Alcatel-Lucent 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 Alcatel-Lucent 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.

Electrical precautions

3.43 Take appropriate safety precautions when performing procedures on electrical equipment. Hazardous electrical potentials are present when system power is on.

3.44 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 Alcatel-Lucent 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 Alcatel-Lucent 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.


Introduction 1-27

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 Alcatel-Lucent 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.

Laser precautions

3.45 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, call the Alcatel-Lucent Technical Support Center (TSC).

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


Introduction1-28

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.

3.47 Laser safety goggles or eye shields are not required if the following work rules are strictly followed:

1. Always remove electrical power from fiber-optic transmitters before disconnecting fiber-optic connectors in the path between the transmitter and the receiver.

2. Never connect an unterminated optical cable to a fiber-optic transmitter. Always connect fiber-optic cables to fiber-optic receivers, test sets, or some other termination first.


Introduction 1-29

4. Electrostatic-sensitive devices

Electrostatic-sensitivity

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

4.2 Common plastics (synthetic insulating materials), clothing, and paper or cardboard are the most common sources of static charges.

4.3 Observe special precautions when the ESD sign is displayed. See Figure 4-1.

4.4 The following items are examples of ESDs:

• MOS (Metal Oxide Semiconductor) capacitors, transistors, Integrated Circuits (ICs)

• CMOS (Complementary Metal Oxide Semiconductor) transistors, ICs

• JFET (Junction Field Effect Transistors)

• IGFET (Insulated Gate Field Effect Transistors)

Figure 4-1. Electrostatic-sensitive sign

671-0592-1061405


Introduction1-30

Handling circuit packs

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

4.6 ESDs are protected when properly packaged in conductive or antistatic packaging. Acceptable packaging is marked as either conductive or antistatic.


Introduction 1-31

5. Product support information

Telephone support

Customer service telephone support

5.1 For telephone support for the customer services mentioned in this Product Support Information, call the Alcatel-Lucent North America Service Center at 1-(888) 252-2832 for details, 8:00 a.m. to 5:00 p.m., Central Time, Monday through Friday. Ask the operator for the appropriate service to be connected to a qualified representative or engineer.

5.2 After-hours emergency telephone support is also available by calling the Alcatel-Lucent North America Service Center at 1-(888) 252-2832. An emergency is defined as an out-of-service, traffic-affecting problem or a nonoperating alarm system on traffic-bearing systems.

Product documentation and training

Product documentation

5.3 Product documentation is available on CD-ROM. The documentation can also be accessed through Alcatel-Lucent�s OnLine Customer Support (OLCS) web site at:

https://support.alcatel-lucent.com/portal/olcsHome.do

Product documentation updates appear on Alcatel-Lucent�s OnLine Customer Support web site before they are available in any other format.

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


Introduction1-32

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

Training

5.5 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:

5.6 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

IN USA: IN CANADA:Alcatel-Lucent USA3400 W. Plano Pkwy.Plano, Texas 75075ATTN: Training M/S 1206-553

Alcatel-Lucent CanadaNetwork Services DivisionP.O. Box 13600Ottawa, Ontario K2K 2E6


Introduction 1-33

Technical support center

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

5.8 For technical assistance, call Alcatel-Lucent North America Service Center at 1-(888) 252-2832.

After-hours emergency telephone support

5.9 Emergency support is available after-hours for emergencies by calling 1-(888) 252-2832.

5.10 An emergency is defined as an out-of-service, traffic-affecting problem or a nonoperating alarm system on traffic-bearing systems.

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

5.12 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

After-hours non emergency telephone support

5.13 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 at 1-(888) 252-2832.


Introduction1-34

On-site technical support

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

Repair and return services

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

Spare parts and replacement cards

5.16 For spare parts, spare cards, card exchange, and in-warranty replacement on a routine or emergency basis, call customer service telephone support.

5.17 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

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


Introduction 1-35

Return for credit or warranty exchange procedure

5.19 Returned equipment must have a Parts Request (PR) number. Obtain an PR number by calling the Alcatel-Lucent Welcome Center at 1-866-582-3688.

5.20 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

Service center

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

Return for repair procedure

5.22 Refer to paragraph 5.19 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


Introduction1-36

• Special instruction/information

Shipping instructions for repair, credit, or warranty exchange

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

Installation and maintenance services

Engineering and installation service

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

Contract maintenance service

5.25 Field service from Alcatel-Lucent US and Canada offices are available. Alcatel-Lucent field service is well-suited for private networks of any size.


Introduction 1-37

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


Introduction1-38


Task index list 2-1

IXL-100

Index Task Lists (IXLs)IXL-100 Task index list

IXL-100Task index listTable 100-A lists the type of procedure or information needed to perform maintenance and trouble clearing on the system.

Table 100-A. Task Index ListType of procedure/information SeeAlarm and abnormal condition clearing procedures IXL-101Support procedures IXL-102Equipment replacement procedures IXL-103Supporting information IXL-104Preventive maintenance procedures RTL-100


Task index list2-2

IXL-100


Alarm and abnormal condition clearing procedures 3-3

IXL-101

IXL-101 Alarm and abnormal condition clearing procedures

IXL-101Alarm and abnormal condition clearing proceduresSee Table 101-C to identify alarms reported by the Alarm Manager and the corresponding procedure, which describes how to clear the alarm.

See Table 101-D 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 101-E to identify Core-E card LED alarm indications and the corresponding procedure, which describes how to clear the condition type.

See Table 101-F to identify MSS-1 shelf CORE LED alarm indications and the corresponding procedure, which describes how to clear the condition type.

See Table 101-G to identify Transport card status LED alarm indications and the corresponding procedure, which describes how to clear the condition type.

See Table 101-H to identify Ethernet LED alarm indications and the corresponding procedure, which describes how to clear the condition type.

See Table 101-I to identify MPT-HL Transceiver LED alarm indications and the corresponding procedure, which describes how to clear the condition type.

See Table 101-J 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:

Diagnosis>Abnormal Condition List

Alarm manager / craft terminal

Equipment / facility column

The EQUIPMENT/FACILITY column in Table 101-C lists the entities to which an alarm type can apply. Depending on the entities affected, some alarm types have more than one corresponding procedure.


Alarm and abnormal condition clearing procedures3-4

IXL-101

In the EQUIPMENT/FACILITY column, equipment entities are listed using the following definitions:

• AUX: Auxiliary card

• Core-E: Core Switching Module card

• 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

• 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

• 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

• OC-3: OC-3 facility supported by SDHACC card

• P8ETH: Ethernet facility supported by the P8ETH card

Friendly name / entity column

The FRIENDLY NAME/ENTITY column identifies the location of the alarming entity.



IXL-101

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 101-A.

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>

Table 101-A. Equipment friendly name syntax definitionsLocation Syntax Values DescriptionRack r r01 Rack numberSubrack 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 transceiver connected to P8ETH card (P8ETH slot number and Ethernet port number associated with MPT-HL Transceiver)

s1[1-6] Subrack number for MPT-HL 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 alarmb#[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

daughter#[05-08] Daughter SFP port number of equipment in alarm associated with P8ETH card

daughter#[01-02] Daughter SFP port number of equipment in alarm associated with SDHACC card



IXL-101

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 101-B.

Table 101-B. Friendly name syntax definitionsLocation Syntax Values DescriptionFacility Name

f DS-1-in, out DS1 facility and directionDS-3-in, out DS3 facility and directionEleSdh-in OC-3 facility and direction (supported by electrical SFP)OptSdh-in OC-3 facility and direction (supported by optical SFP)MAU Ethernet signalRadio Radio facility

Radio Direction

rd Dir#[3-8].[1-4] Radio direction of MPT ODU radio channel in alarm connected 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 radio channel in alarm connected to P8ETH card (P8ETH slot number and port number)

Dir#1.[5-6] Radio direction of MPT-HL 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 alarmb#[1-9]

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

Port Number

p Port#[1-16] DS1 port number of facility in alarm on MSS-1 shelfPort#[1-32] DS1 port number of facility in alarm on P32E1DS1Port#[1-2] DS3 port number of facility in alarmPort#[1-2] OC-3 port number of facility in alarmPort#[1-6] Ethernet port number of facility in alarm associated with

Core-E card or MSS/COREPort#[1-8] Ethernet port number of facility in alarm associated with

P8ETH card



IXL-101

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]

Channel Number

c Ch#1 Main radio channel in alarmCh#0 Spare radio channel in alarm

ERPS ERP ERP[1-2]#[1-2] Ethernet Ring Protection Switch

Table 101-B. Friendly name syntax definitions (cont.)Location Syntax Values Description



IXL-101

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 101-C describes the alarms that are reported by the Alarm Manager and the corresponding procedure to clear the alarm.

Table 101-C. Alarm monitor alarm typesProbable cause

Friendly name/entity Facility/equipment

Description See

AIS DS1-in/MSS/DS1/Port#[1-16] DS1 on MSS-1 shelf

AIS detected incoming to the PDH card from the demarcation panel for the DS1 or DS3 facility.

TAP-100

DS1-in/Slot#[3-8]/Port#[1-32] DS1 on P32E1DS1

DS3-in/Slot#[3-8]/Port#[1-2] DS3



IXL-101

AIS EleSdh-in/slot#[3-8]/Port[1-2] OC-3 AIS detected incoming to the SDHACC card from the demarcation panel for the OC-3 facility.

TAP-100

OptSdh-in/slot#[3-8]/Port[1-2]

AIS DS1-out/MSS/DS1/Port#[1-16]

DS1 on MSS-1 shelf

AIS detected from the Core-E switch matrix for the DS1 or DS3 facility, indicating an upstream failure.

TAP-100

DS1-out/Slot#[3-8]/Port#[1-32]

DS1 on P32E1DS1

DS3-out/Slot#[3-8]/Port#[1-2] DS3AIS EleSdh-out/slot#[3-8]/

Port[1-2]OC-3 AIS detected from the

Core-E switch matrix for the OC-3 facility, indicating an upstream failure.

TAP-100

OptSdh-out/slot#[3-8]/Port[1-2]

ATPC loop problem

Radio/Dir#1.[1-6]/Slot#1/Port#[1-6]/Ch#[0-1]

MPT ODU connected to Core-E

Reported for a ATPC High Power Time-out. When 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.

TAP-110

Radio/Dir#1.[1-6]/MSS/CORE/Port#[1-6]/Ch#[0-1]

MPT ODU connected to MSS/CORE

Radio/Dir#[3-8].[1-4]/Slot#[3-8]/Port#[1-4]/Ch#[0-1]

MPT ODU connected to MPTACC

Radio/Dir#[3-8].[5-8]/Slot#[3-8]/Port#[5-8]/Ch#1

MPT ODU connected to P8ETH


MPT-HL connected to P8ETH

Radio/Dir#1.[5-6]/Slot#1/Port#[5-6]/Ch#1

MPT-HL connected to Core-E

Radio/Dir#1.[5-6]/MSS/CORE/Port#[5-6]/Ch#1

MPT-HL connected to MSS/CORE

Radio/Dir#[3-8]/Ch#[0-1] MOD300Bandwidth degrade for protection switch

ERP#[1-2]#[1-2] Core-E An ERPS Instance has entered a Protection state.

TAP-105

Table 101-C. Alarm monitor alarm types (cont.)Probable cause


Description See



IXL-101

Bandwidth over flow



While the MPT ODU/ MPT-HL was not communicating with the Core-E, EAS, or MSS/CORE, TDM/SDH cross-connections were provisioned with a total bandwidth which exceeds the net bandwidth capacity of the radio profile.

TAP-104













Battery failure r01/subrack#1 MSS-1/4/8 A battery feed failed or is missing.

TAP-102

Cable LOS r01s1/board#[3-8] MOD300 Bad cable connection at IF in/out connector on MOD300 card.

TAP-111

CLA Radio/Dir#[3-8].[1-4]/Slot#[3-8]/Port#[1-4]/Ch#[0-1]


The standby transmitter has/had a silent failure which caused the far end to request a HSB switch.

TAP-104







Radio/Dir#[3-8]/Ch#[0-1] MOD300



Description See



IXL-101

Clock failure Radio/Dir#1.[1-6]/Slot#1/Port#[1-6]/Ch#[0-1]


The MPT ODU/MPT-HL is not able to lock the air Tx symbol rate to the NE clock.

TAP-119













Degrade Sync-in/Port#1 Core-E Frequency of the source signal is degraded. Managed only if the interface has been configured as a primary or secondary synchronization source.

TAP-109Radio/Dir#[3-8]/Ch#[0-1] MOD300Radio/Dir#1.[1-6]/Slot#1/Port#[1-6]/Ch#1










Description See



IXL-101

Degrade (cont.)



TAP-109





RadioLAG#[1-14] MPT ODU connected to P8ETH, MPT-HL connected to P8ETH

DS1-in/Slot#[3-8]/Port#[1-32] P32E1DS1EleSdh-in/slot#[3-8]/Port[1-2] OC-3

OptSdh-in/slot#[3-8]/Port[1-2]Degrade RadioLAG#[1-14] ODU Signal on the Radio LAG

interface is degraded.TAP-117

Degrade EthLAG#[1-14] Core-E, MSS/CORE

A member(s) of an Ethernet or Radio LAG group has no activity. Degrade is declared when the number of active ports in the LAG are greater than zero and less than the LAG size.

TAP-117

RadioLAG#[1-14] MPT ODU, MPT-HL, ODU

DemXPIC LOS r01s1b1[1-6]/daughter#04 MPT ODU connected to Core-E, MSS/CORE

Bad or missing cable/cable connection at XPIC connector on MPT ODU.

TAP-111

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



Description See



IXL-101

Demodulator fail



Loss of receive signal, bad receive signal, or internal receive circuit failure.

TAP-104











Dialog failure r01/subrack#1[1-6] MPT ODU connected to Core-E, MSS/CORE

Temporary Loss of communication with MPT ODU/MPT-HL

TAP-107

r01/subrack#[3-8][1-4] MPT ODU connected to MPTACC

r01/subrack#[3-8][5-8] MPT ODU connected to P8ETH

r01/subrack#[3-8][5-8] MPT-HL connected to P8ETH

r01/subrack#1[5-6] MPT-HL connected to Core-E, MSS/CORE



Description See



IXL-101

Duplicate address detected

TMNEthernet/MngtPort Core-E/TMN MGMT Port

Duplication of IPv6 Global Unicast address detected on TMN management port, Port#4, In-Band port 1-2

TAP-120

TMNEthernet/Port#4 Core-E/TMN Port#4

TMNInBand#[1-2] Core-E/TMN In-Band Port [1-2]


PPP-IP/RF#[3-8] MOD300 Duplication of IPv6 Global Unicast address detected on TMN-RF over PPP

TAP-120PPP-IP/RF#1[1-6] MPT ODU

connected to Core-E, MSS/CORE

PPP-IP/RF#[3-8][1-4] MPT ODU connected to MPTACC

PPP-IP/RF#[3-8][5-8] MPT ODU connected to P8ETH

PPP-IP/RF#[3-8][5-8] MPT-HL connected to P8ETH

PPP-IP/RF#1[5-6] MPT-HL connected to Core-E, MSS/CORE

PPP-IP/RF/LAG#[1-14] MPT ODU, MPT-HL, ODU



Description See



IXL-101

Early warning indication



10E-9 BER detected TAP-104













Radio/Dir#[3-8]/Ch#[0-1] MOD300Eth OAM loss of continuity

MEP#MDID[1-16]#MA ID[1-512]#MEPID[1-8191]

Core-E, MSS/CORE

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.

TAP-118

Eth OAM MisMerge condition


Core-E, MSS/CORE

MEP received a CCM frame with correct MD Level but incorrect MA ID.

TAP-118

Eth OAM remote defect indication


Core-E, MSS/CORE

MEP received a CCM frame with the RDI field set.

TAP-118

Eth OAM unexpected level


Core-E, MSS/CORE

MEP received a CCM frame with the incorrect MD Level.

TAP-118

Eth OAM unexpectedMEPID


Core-E, MSS/CORE

Received MEPID value is different than the expected MEPID.

TAP-118



Description See



IXL-101

Eth OAM unexpected period


Core-E, MSS/CORE

Received MEP Time-Out period value is different than the expected MEP Time-Out period.

TAP-118

Excessive environmental temperature


Excessive temperature on MPT-HL Transceiver

TAP-103



Failure or Missing MPT-HL Transceiver Fan Unit detected

TAP-103




Description See



IXL-101

FirmwareDownloadOn Going

r01s1/board#[8] AUX Download Status. A download of an FPGA or other software unit on the addressed card.

Noactionrequired.

r01s1/board#[1-2] Core-Er01s1/board#[3-8] MOD300,

MPTACC, P2E3DS3, P8ETH, P32E1DS1, SDHACC

r01/subrack#[3-8] ODU300r01/subrack#1[1-6] MPT ODU

connected to Core-E



r01/subrack#1[5-6] MPT-HL connected to Core-E




Description See



IXL-101

High BER Radio/Dir#[3-8].[1-4]/Slot#[3-8]/Port#[1-4]/Ch#[0-1]


Bit Error Rate threshold (10E-4) exceeded on receiver input circuits on MOD300/ MPT ODU/MPT-HL card.

TAP-104













Radio/Dir#[3-8]/Ch#[0-1] MOD300High BER EleSdh-in/slot#[3-8]/Port[1-2] OC-3 Bit Error Rate threshold

(10E-5) exceeded on receiver input circuits on SDHACC card from demarcation panel for the OC-3 facility.

TAP-100


High BER EleSdh-out/slot#[3-8]/Port[1-2]

OC-3 Bit Error Rate threshold (10E-5) exceeded on transmit output circuits on SDHACC card to the demarcation panel for the OC-3 facility.

TAP-100


Housekeeping alarm

ExtPt/Input#[1-6] AUX Housekeeping alarm input is active.

TAP-116ExtPt/Input#[11-14] FanExtPt/Input#[11-14] MSS-1



Description See



IXL-101

Incompatible frequency



Configured frequency is outside of the supported frequency range.

TAP-104













Radio/Dir#[3-8]/Ch#[0-1] ODU300



Description See



IXL-101

Incompatible modulation



Configured modulation is not supported by MPT ODU, MPT-HL, or ODU300.

TAP-104













Incompatible protection



Incorrectly configured or missing RPS/XPIC module on MPT ODU.

TAP-104







Description See



IXL-101

Incompatible shifter



Configured shifter value not supported by MPT ODU, MPT-HL, or ODU300.

TAP-104













Radio/Dir#[3-8]/Ch#[0-1] ODU300Incompatible power



Configured Tx power value not supported by MPT-HL.

TAP-104







Description See



IXL-101

Incompatible TX power



Configured Tx power value not supported by MPT ODU or ODU300.

TAP-104







Radio/Dir#[3-8]/Ch#[0-1] ODU300Internal communication problem

r01/subrack#1[1-6] MPT ODU connected to Core-E, MSS/CORE

Loss of communications with MPT ODU, MPT-HL, or ODU300.

TAP-107





r01/subrack#[3-8] ODU300



Description See



IXL-101

Link identifier mismatch

AirFrame/Dir#[3-8].[1-4]/Slot#[3-8]/Port#[1-4]/Ch#1,AirFrame/Dir#[3-8].[1-4]/Slot#[3-8]/Port#[1-4]


Link identifier number provisioned on MOD300/ MPT ODU/MPT-HL card settings screen is different from link identifier number provisioned at far end of hop.

TAP-104

AirFrame/Dir#1.[1-6]/Slot#1/Port#[1-6]/Ch#1,AirFrame/Dir#1.[1-6]/Slot#1/Port#[1-6]


AirFrame/Dir#1.[1-6]/MSS/CORE/Port#[1-6]/Ch#1,AirFrame/Dir#1.[1-6]/MSS/CORE/Port#[1-6]


AirFrame/Dir#[3-8].[5-8]/Slot#[3-8]/Port#[5-8]/Ch#1




AirFrame/Dir#1.[5-6]/Slot#1/Port#[5-6]


AirFrame/Dir#1.[5-6]/MSS/CORE/Port#[5-6]


AirFrame/Dir#[3-8]/Ch#1, AirFrame/Dir#[3-8]

MOD300



Description See



IXL-101

Loop problem Radio/Dir#1.[1-6]/Slot#1/Port#[1-6]/Ch#[0-1]


Loss of ATPC command path between far end transmitter and local receiver.

TAP-110













Loss of alignment

Hitless/Dir#[3-8].[1-4] MPT ODU connected to MPTACC

Delay/loss of alignment between main and protect RPS RF paths detected.

TAP-112

Hitless/Dir#1.[1-6] MPT ODU connected to Core-E, MSS/CORE

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

Hitless/Dir#[3-8] MOD300



Description See



IXL-101

Loss Ethernet synchronization messaging channel

MAU/Slot#[1-2]/Port#[1-6] Core-E Reported if there is a loss of the Ethernet Synchronization Message Channel. The alarm is applicable to Core-E Ethernet ports and Radio interfaces (MPT ODU, MPT-HL, or MOD300) configured with SSM support enabled and is assigned as a synchronous clock source input.

TAP-109Radio/Dir#[3-8]/Ch#[0-1] MOD300RadioLAG#[1-14] MPT ODU,

MPT-HLRadio/Dir#1.[1-6]/Slot#1/Port#[1-6]/Ch#[0-1]














Loss Of CESoETH frame

CircuitTDM/MSS/DS1/Port#[1-16]

DS1 on MSS-1 shelf

Packets are not being received by the DS1, DS3, or OC-3 emulation circuits on the receive circuits from the switch matrix.

TAP-100

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

DS1 on P32E1DS1


DS3


OC-3



Description See



IXL-101

Loss Of Frame DS1-in/MSS/DS1/Port#[1-16] DS1 on MSS-1 shelf

Loss of DS1, DS3, or OC-3 frame detected incoming to the PDH/SDH card from the demarcation panel for the DS1, DS3, or OC-3 facility.

TAP-100

DS1-in/Slot#[3-8]/Port#[1-32] DS1 onP32E1DS1

DS3-in/Slot#[3-8]/Port#[1-2] DS3EleSdh-in/slot#[3-8]/Port[1-2] OC-3OptSdh-in/slot#[3-8]/Port[1-2]

Loss of frame DS1-out/Slot#[3-8]/Port#[1-32]

DS1/P32E1DS1

Loss of DS1, DS3, or OC-3 frame detected from the Core-E switch matrix for the DS1, DS3, or OC-3 facility

TAP-100

DS3-out/Slot#[3-8]/Port#[1-2] DS3EleSdh-out/slot#[3-8]/Port[1-2]

OC-3


Loss of frame Radio/Dir#1.[1-6]/Slot#1/Port#[1-6]/Ch#[0-1]


Far end TX problems, RF path problems, or local circuit failures have caused BER to increase to the point that frames are being lost.

TAP-113
















Description See



IXL-101

Loss of protection

Radio/Dir#[3-8]/Ch#1 MOD300 The radio direction is affected by a failure that radio protection (RPS) can�t recover. Only reported if RPS is provisioned.

TAP-104Radio/Dir#[3-8].[1-4]/Slot#[3-8]/Port#[1-4]/Ch#1






Loss of signal DS1-in/MSS/DS1/Port#[1-16] DS1 on MSS-1 shelf

No DS1, DS3, or OC-3 input signal detected.

TAP-100

DS1-in/Slot#[3-8]/Port#[1-32] DS1 on P32E1DS1

DS3-in/Slot#[3-8]/Port#[1-2] DS3EleSdh-in/slot#[3-8]/Port[1-2] OC-3OptSdh-in/slot#[3-8]/Port[1-2]

Loss of signal ETHInterface#100 Core-E/TMN MGMT Port

Loss of Signal is declared when either:• no Ethernet input signal

detected on the Ethernet port

• a communication problem with the remote peer (i.e. a link down condition)

TAP-105

ETHInterfaceonCore#4 Core-E/TMN Port#4

MAU/Slot#[1-2]/Port#[1-6] Core-EMAU/MSS/CORE/Port#[1-6] MSS/COREMAU/Slot#[3-8]/Port#[1-4] MPTACC MAU/Slot#[3-8]/Port#[1-8] P8ETHr01s1[1-6]b1/daughter#03 RPS SFP on

MPT ODUconnected to Core-E, MSS/CORE

Loss of signal MAU/subrack[#3-8].[1-4] daughter#03


Loss of Signal detected on an MPT ODU/MPT-HL Ethernet Coupler Port. Only reported when RPS is provisioned.

TAP-104

MAU/subrack[#3-8].[5-8] Port#n


Loss of signal Sync-in/Port#1 Core-E Generated when no signal is present on the incoming Sync-In port.

TAP-109



Description See



IXL-101

Loss of signal EthLAG#[1-14] Core-E, MSS/CORE

ALL members of an Ethernet or Radio LAG group have no activity. Loss of Signal is declared when the number of active ports in the LAG equals zero.

TAP-117

RadioLAG#[1-14] MPT ODU, MPT-HL, ODU

Power supply failure

r01/subrack#[3-8][1-4] MPTACC MPT Power Supply Failure detected, either an Open-Circuit or Over-Current condition on a MPTACC or MSS-1 shelf (PFoE) power supply port.

TAP-102

r01/subrack#1[1-2] MSS/Core

PPP fail PPP-IP/RF#1[1-6] MPT ODU connected to Core-E, MSS/CORE

TMN over PPP Fail TAP-104





PPP-IP/RF#[3-8] MOD300Provisioning mismatch

r01s1/board#[1-2] Core-E The wrong flash card is installed and the current database is in conflict with the license string on the card.

TAP-106

r01s1/board#1 MSS/CORE



Description See



IXL-101

Replaceable unit missing

r01s1/board#[8] AUX Card/SFP is missing from slot (Only declared, if the card/SFP has been provisioned. Card/SFP could be unreachable.).

TAP-103r01s1/board#[1-2] Core-Er01s1/board#[5,9] FANr01s1/board#[3-8] MOD300,


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

r01s1[1-6]b1/daughter#03 RPS SFP on MPT ODUconnected to Core-E, MSS/CORE



Description See



IXL-101

Replaceable unit problem

r01s1/board#[8] AUX Card failed. TAP-103r01s1/board#[1-2] Core-Er01s1/board#[5,9] FANr01s1/board#[3-8] MOD300,







r01/subrack#[3-8] ODU300r01/subrack#[3-8][1-4] MPT ODU

connected to MPTACC








Description See



IXL-101

Replaceable unit problem (cont.)

r01s[3-8][1-4]b1/daughter#03 RPS SFP on MPT ODU connected to MPTACC

Card failed. TAP-103

r01s1[1-6]b1/daughter#03 RPS SFP on MPT ODUconnected to Core-E, 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 MPT ODU connected to P8ETH

r01s[3-8][1-4]b1/daughter#04 RPS or XPIC Module on MPT ODU connected to MPTACC



Description See



IXL-101

Replaceable unit type mismatch

r01s1/board#[8] AUX Card/ODU in slot does not match card/ODU configured in Core-E memory

TAP-103r01s1/board#[1-2] Core-Er01s1/board#[5,9] FANr01s1/board#[3-8] MOD300,






r01/subrack#1[5-6] MPT-HLconnected to Core-E, MSS/CORE

r01/subrack#[3-8] ODU300



Description See



IXL-101

Remote defect indication



Remote Defect Indication (RDI) in a received RadioDirection. Alarm is reported when an RDI is receivedon a given radio direction from the remote end of radio link.

TAP-104













Radio/Dir#[3-8]/Ch#[0-1] MOD300Remote defect indication

EleSdh-in/slot#[3-8]/Port[1-2] OC-3 Remote Defect Indication (RDI) in a received OC-3Direction. Alarm is reported when an RDI is receivedon a given OC-3 directionfrom the remote end of OC-3link.

TAP-100


RPS path fail RadioProt/Dir#[3-8][1-4] MPT ODU connected to MPTACC

A communication failure is detected between MPT ODUs. Only reported for an MPT ODUs working in 1+1 configuration with Virtual Protection.

TAP-114

RadioProt/Dir#1[1-6] MPT ODU connected to Core-E, MSS/CORE

RadioProt/Dir#[3-8][5-8] MPT-HL connected to P8ETH

Communication failure is detected between RPS coupler port between radio boards. Only reported if RPS is provisioned.



Description See



IXL-101

Rx fail Radio/Dir#[3-8]/Ch#[0-1] ODU300 Failure in receive direction of ODU300 RF transceiver. Includes no input signal.

TAP-115

Secondary battery failure

r01/subrack#1 MSS-1/4/8 B battery feed failed or is missing.

TAP-102

Standby version mismatch


Standby software version on MPT ODU/MPT-HL does not match software version on Core-E.

TAP-106







Description See



IXL-101

Synchronization signal fail

Sync-in/Port#1 Core-E Synchronization Signal Fail is reported if the received source signal is not suitable as a Sync Source. Managed only if the interface has been configured as a primary or secondary synchronization source.

TAP-109Radio/Dir#[3-8]/Ch#[0-1] MOD300Radio/Dir#1.[1-6]/Slot#1/Port#[1-6]/Ch#1














RadioLAG#[1-14] MPT ODU, MPT-HL

DS1-in/Slot#[3-8]/Port#[1-32] P32E1DS1EleSdh-in/slot#[3-8]/Port[1-2] OC-3OptSdh-in/slot#[3-8]/Port[1-2]



Description See



IXL-101

Threshold crossed

Hop/Dir#1[1-6]/Slot#1/Port#[1-6]/Ch#[0-1]-PM15min


Threshold Crossing Alarm (TCA) indicates alarm threshold has been exceeded. Applies to performance monitor parameters with an accumulation period of 24 hours and 15 minutes.

TAP-108

Hop/Dir#1[1-6]/Slot#1/Port#[1-6]/Ch#[0-1]-PM1dayLink/Dir#1[1-6]-PM15minLink/Dir#1[1-6]-PM1dayHop/Dir#1[1-6]/MSS/CORE/Port#[1-6]/Ch#[0-1]-PM15min

MPT ODU connected to MSS/CORE Hop/Dir#1[1-6]/MSS/CORE/

Port#[1-6]/Ch#[0-1]-PM1dayLink/Dir#1[1-6]-PM15minLink/Dir#1[1-6]-PM1dayHop/Dir#[3-8][1-4]/Slot#[3-8]/Port#[1-4]/Ch#[0-1]-PM15min

MPT ODU connected to MPTACCHop/Dir#[3-8][1-4]/Slot#[3-8]/

Port#[1-4]/Ch#[0-1]-PM1dayLink/Dir#[3-8][1-4]-PM15minLink/Dir#[3-8][1-4]-PM1dayHop/Dir#[3-8][5-8]/Slot#[3-8]/Port#[5-8]/Ch#1-PM15min

MPT ODU connected to P8ETHHop/Dir#[3-8][5-8]/Slot#[3-8]/

Port#[5-8]/Ch#1-PM1dayHop/Dir#[3-8][5-8]/Slot#[3-8]/Port#[5-8]/Ch#[0-1]-PM15min

MPT-HL connected to P8ETHHop/Dir#[3-8][5-8]/Slot#[3-8]/

Port#[5-8]/Ch#[0-1]-PM1dayLink/Dir#[3-8][5-8]-PM15minLink/Dir#[3-8][5-8]-PM1dayHop/Dir#1[5-6]/Slot#1/Port#[5-6]/Ch#1-PM15min

MPT-HL connected to Core-EHop/Dir#1[5-6]/Slot#1/

Port#[5-6]/Ch#1-PM1dayHop/Dir#1[5-6]/MSS/CORE/Port#[5-6]/Ch#1-PM15min

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

Port#[5-6]/Ch#1-PM1day



Description See



IXL-101

Threshold crossed (cont.)

Hop/Dir#[3-8]/Ch#[0-1]-PM15min

MOD300 Threshold Crossing Alarm (TCA) indicates alarm threshold has been exceeded. Applies to performance monitor parameters with an accumulation period of 24 hours and 15 minutes.

TAP-108

Hop/Dir#[3-8]/Ch#[0-1]-PM1dayLink/Dir#[3-8]-PM15minLink/Dir#[3-8]-PM1dayDS1-in/Slot#[3-8]/Port#[1-32]-PM15min

P32E1DS1

DS1-in/Slot#[3-8]/Port#[1-32]-PM1dayDS1-out/Slot#[3-8]/Port#[1-32]-PM15minDS1-in/MSS/DS1/Port#[1-16]-PM15min

DS1 on MSS-1 shelf

DS1-in/MSS/DS1/Port#[1-16]-PM1dayDS1-out/MSS/DS1/Port#[1-16]-PM15minDS1-out/MSS/DS1/Port#[1-16]-PM1day

Trace identifier mismatch

EleSdh-in/slot#[3-8]/Port[1-2] OC-3 Trace Identifier Mismatch condition indicates there is a J0 Trace Mismatch detected in the incoming signal from the demarcation panel.

TAP-100OptSdh-in/slot#[3-8]/Port[1-2]



Description See



IXL-101

Unavailable time

Hop/Dir#1[1-6]/Slot#1/Port#[1-6]/Ch#[0-1]-PM15min


A period of unavailable time begins when 10 consecutive SES events are detected. Alarms are associated to the performance monitoring port.

TAP-108


MPT ODU connected to MSS/COREHop/Dir#1[1-6]/MSS/CORE/

Port#[1-6]/Ch#[0-1]-PM1dayLink/Dir#1[1-6]-PM15minLink/Dir#1[1-6]-PM1dayHop/Dir#[3-8][1-4]/Slot#[3-8]/Port#[1-4]/Ch#[0-1]-PM15min

MPT ODU connected to MPTACCHop/Dir#[3-8][1-4]/Slot#[3-8]/

Port#[1-4]/Ch#[0-1]-PM1dayLink/Dir#[3-8][1-4]-PM15minLink/Dir#[3-8][1-4]-PM1dayHop/Dir#[3-8][5-8]/Slot#[3-8]/Port#[5-8]/Ch#1-PM15min

MPT ODU connected to P8ETHHop/Dir#[3-8][5-8]/Slot#[3-8]/

Port#[5-8]/Ch#1-PM1dayHop/Dir#[3-8][5-8]/Slot#[3-8]/Port#[5-8]/Ch#[0-1]-PM15min

MPT-HL connected to P8ETHHop/Dir#[3-8][5-8]/Slot#[3-8]/

Port#[5-8]/Ch#[0-1]-PM1dayLink/Dir#[3-8][5-8]-PM15minLink/Dir#[3-8][5-8]-PM1dayHop/Dir#1[5-6]/Slot#1/Port#[5-6]/Ch#1-PM15min

MPT-HL connected to Core-EHop/Dir#1[5-6]/Slot#1/

Port#[5-6]/Ch#1-PM1dayHop/Dir#1[5-6]/MSS/CORE/Port#[5-6]/Ch#1-PM15min

MPT-HL connected to MSS/COREHop/Dir#1[5-6]/MSS/CORE/

Port#[5-6]/Ch#1-PM1day



Description See



IXL-101

Unavailable time (cont.)

Hop/Dir#[3-8]/Ch#[0-1]-PM15min

MOD300 A period of unavailable time begins when 10 consecutive SES events are detected. Alarms are associated to the performance monitoring port.

TAP-108

Hop/Dir#[3-8]/Ch#[0-1]-PM1dayLink/Dir#[3-8]-PM15minLink/Dir#[3-8]-PM1dayDS1-in/Slot#[3-8]/Port#[1-32]-PM15min

P32E1DS1

DS1-in/Slot#[3-8]/Port#[1-32]-PM1dayDS1-out/Slot#[3-8]/Port#[1-32]-PM15minDS1-out/Slot#[3-8]/Port#[1-32]-PM1dayDS1-in/MSS/DS1/Port#[1-16]-PM15min

DS1 on MSS-1 shelf


Unconfigured equipment present

r01s1/board#[8] AUX Card in MSS shelf slot 2 through 8 is not provisioned (enabled) but is present in slot.SFP is not provisioned (enabled) but is present in card.

TAP-103r01s1/board#[2] Core-Er01s1/board#[5,9] FANr01s1/board#[3-8] MOD300,







Description See



IXL-101

Unconfigured equipment present(cont.)


Card in MSS shelf slot 2 through 8 is not provisioned (enabled) but is present in slot.SFP is not provisioned (enabled) but is present in card.

TAP-103


Version mismatch


Software version on ODU, MPT ODU/MPT-HL does not match software version on Core-E.

TAP-106





r01/subrack#[3-8] ODU300r01s1/board#[1-2] Core-E

Table 101-D. Abnormal conditionOperation Name Type

(equipment)Description See

Core facing PDH loopback

DS1 Port#[1-16] Internal LoopbackDS1 on MSS-1 shelf

The associated entity has a core facing PDH (DS1 or DS3) loopback activated at the near end.

TAP-101

DS1 Port#[1-32] Internal LoopbackSLOT#[3-8]DS3 Port#[1-2] Internal



Description See



IXL-101

Digital core facing loopback

Direction #1.[1-6] Loopback(MPT ODU connected to Core-E, MSS/CORE)

The associated entity has a loopback activated at the near end.

TAP-101

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

Direction #[3-8].[5-8] Loopback(MPT ODU connected to P8ETH)

Direction #[3-8].[5-8] Loopback(MPT-HL connected to P8ETH)

Direction #1.[5-6] Loopback(MPT-HL connected to Core-E, MSS/CORE)





IXL-101

Forced adaptive modulation

Direction #[3-8] Radio (MOD300)

Manual Adaptive Modulation command has been executed.

TAP-101

Direction #1.[1-6] Radio(MPT ODU connected to Core-E, MSS/CORE)

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

Direction #[3-8].[5-8] Radio(MPT ODU connected to P8ETH)

Direction #[3-8].[5-8] - Channel #[0-1]

Radio (MPT-HL connected to P8ETH)

Direction #1.[5-6] Loopback(MPT-HL connected to Core-E, MSS/CORE)





IXL-101

Forced switch EPS

Main#1 Slot#1 Equipment Protection (Core-E)

A Forced Equipment Protection Switch (EPS) has been executed for the protection group.

TAP-101

Main#1 Slot#[3,5,7] Equipment Protection (MOD300, P2E3DS3,P32E1DS1, SDHACC)

Main#1 Slot #[3-8] Port #[1-4]

Equipment Protection (MPT ODU connected to MPTACC)

Main#1 Slot #1 Port #[1,3,5]

Equipment Protection (MPT ODU connected to Core-E)

Main#1 MSS/CORE Port #[1,3,5]

Equipment Protection (MPT ODU connected to MSS/CORE)

Main#1 Slot #[3,5,7]Port #[5-8]

Equipment Protection (MPT-HL connected to P8ETH)





IXL-101

Forced switch RPS

Main#1 Slot#[3,5,7] Rx Radio Protection (MOD300)

A Forced Rx Protection Switch (RPS) has been executed for the protection group.

TAP-101

Main#1 Slot #[3-8]Port #[1-4]

Rx Radio Protection (MPT ODU connected to MPTACC)


Rx Radio Protection (MPT ODU connected to Core-E)


Rx Radio Protection (MPT ODU connected to MSS/CORE)

Main#1 Slot #[3,5,7]Port #[5-8]

Rx Radio Protection (MPT-HL connected to P8ETH)





IXL-101

Forced switch TPS

Main#1 Slot#[3,5,7] HSB Protection (MOD300)

A Forced Tx Protection Switch (TPS) has been executed for the protection group.

TAP-101

Main#1 Slot #[3-8] Port #[1-4]

HSB Protection (MPT ODU connected to MPTACC)


HSB Protection (MPT ODU connected to Core-E)


HSB Protection (MPT ODU connected to MSS/CORE)

Main#1 Slot #[3,5,7]Port #[5-8]

HSB Protection (MPT-HL connected to P8ETH)

IF cable loopback Direction #[3-8] Loopback(MOD300)


TAP-101

Line facing circuit loopback



TAP-101







IXL-101

Line facing PDH loopback

DS1 Port#[1-16] External LoopbackDS1 on MSS-1 shelf

The associated entity has a line facing PDH (DS1 or DS3) loopback activated at the near end.

TAP-101

DS1 Port#[1-32] External LoopbackSLOT#[3-8]DS3 Port#[1-2] External

Lockout switch EPS

Spare#0 Slot#2 Equipment Protection (Core-E)

A Lockout Equipment Protection Switch (EPS) has been executed for the protection group.

TAP-101

Spare#0 Slot#[4,6,8] Equipment Protection (MOD300, P2E3DS3, P32E1DS1, SDHACC)

Spare#0 Slot#[3-8] Port #[1-4]

Equipment Protection (MPT ODU connected to MPTACC)

Spare#0 Slot #1 Port #[2,4,6]

Equipment Protection (MPT ODU connected to Core-E)

Spare#0 MSS/CORE Port #[2,4,6]

Equipment Protection (MPT ODU connected to MSS/CORE)

Spare#0 Slot#[4,6,8]Port #[5-8]

Equipment Protection (MPT-HL connected to P8ETH)





IXL-101

Lockout switch RPS

Spare#0 Slot#[4,6,8] Rx Radio Protection (MOD300)

A Lockout Rx Protection Switch (RPS) has been executed for the protection group.

TAP-101


Rx Radio Protection (MPT ODU connected to MPTACC)


Rx Radio Protection (MPT ODU connected to Core-E)


Rx Radio Protection (MPT ODU connected to MSS/CORE)


Rx Radio Protection (MPT-HL connected to P8ETH)





IXL-101

Lockout switch TPS

Spare#0 Slot#[4,6,8] HSB Protection(MOD300)

A Lockout Tx Protection Switch (TPS) has been executed for the protection group.

TAP-101


HSB Protection(MPT ODU connected to MPTACC)


HSB Protection (MPT ODU connected to Core-E)


HSB Protection (MPT ODU connected to MSS/CORE)


HSB Protection(MPT-HL connected to P8ETH)





IXL-101

TXMute Direction #1.[1-6] - Channel #[0-1]

Radio (MPT ODU connected to Core-E, MSS/CORE)

Manual or automatic mute command has been executed.

TAP-101


Radio (MPT ODU connected to MPTACC

Direction #[3-8].[5-8] - Channel #1

Radio (MPT ODU connected to P8ETH


Radio (MPT-HL connected to P8ETH)

Direction #1.[5-6] - Channel #1

Radio (MPT-HL connected to Core-E, MSS/CORE)

Direction #[3-8] - Channel #1

Radio (ODU300)





IXL-101

Table 101-E. Core-E Card LED indicationsLED Indication Probable cause Corrective actionStatus 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 Blinking

Configuration Downloading, SW Booting, or flash card realignment.

Wait for configuration download or software boot to complete.

Green Card Properly Equipped and Provisioned. currently In-Service/Active.

Normal Operating condition. No Action required.

Yellow Card Properly Equipped and Provisioned as EPS. Currently in Standby.

Normal operating condition for Standby card.No Action required.

Red Card Fail Replace cardRed Blinking Card Mismatch Check alarms for replaceable unit

type mismatch, see TAP-103.

Major Alarm

Red At least one alarm with Critical or Major severity present in the NE.

Retrieve alarms using the alarm monitor, see IXL-101 Table 101-C, and troubleshoot accordingly.

Minor Alarm

Red At least one alarm with Minor severity present in the NE.


Warning Yellow At least one alarm with Warning severity present in the NE.


Abnormal Yellow At least one abnormal condition present in the NE.

Retrieve abnormal condition using JSUM, see IXL-101 Table 101-D, and troubleshoot accordingly.



IXL-101

Table 101-F. MSS-1 shelf LED indicationsLED Indication Probable cause Corrective actionStatus 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.Verify Power cable(s) are properly terminated at both ends.Verify voltage level at the PDU.

MSS-1 shelf not Equipped Verify the MSS-1 shelf is properly installed.

Green Blinking

Configuration Downloading, SW Booting.


Green MSS-1 shelf Properly Equipped and Provisioned. currently In-Service.


Red MSS-1 shelf Fail Replace MSS-1 shelfMajor Alarm

Red At least one alarm with Critical or Major severity present in the NE.


Minor Alarm

Red At least one alarm with Minor severity present in the NE.


Warning Yellow At least one alarm with Warning severity present in the NE.


Abnormal Yellow At least one abnormal condition present in the NE.

Retrieve abnormal condition using JSUM, see IXL-101 Table 101-D, and troubleshoot accordingly.

PFoE Yellow Port is emitting power according to the configuration.

OFF Port is emitting power according to the configuration.



IXL-101

Table 101-G. Transport Card LED indicationsLED Indication Probable cause Corrective actionStatus 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 Blinking

Configuration Downloading, SW Booting, or flash card realignment.


Green Card Properly Equipped and Provisioned. currently In-Service/Active.


Yellow Card Properly Equipped and Provisioned as EPS. Currently in Standby.

Normal operating condition for Standby card.No Action required.

Red Card Fail Replace cardRed Blinking Card Mismatch Check alarms for replaceable unit

type mismatch, see TAP-103.

Table 101-H. Ethernet LED indicationsLED Indication Description Probable cause Corrective actionETH Link Green LED

Not LitLoss of Ethernetcommunicationwith link partner.

1. Cable between link partner and Ethernet port is disconnected/broken.

Connect/repair cable.

2. Speed/Mode provisioning mismatch between link partner and Ethernet port.

1. Check local Ethernet provisioning screen.

2. Check link partner provisioning.



IXL-101

Table 101-I. MPT-HL transceiver LED alarm indicationsLED Indication Probable cause Corrective actionStatus OFF Card Not Provisioned Provision card

Not Powered Verify MPT-HL Transceiver fuse is not blown or missing.Verify Power cable is properly terminated at both ends.Verify voltage level at the PDU.

Invalid Configuration Verify configuration provisioning and correct as required.

Green Blinking

Configuration Downloading, or SW Booting. (Different blink rates should be used to identify each step of the startup process.)


Green Card Properly Equipped and Provisioned. EPS or RPS currently In-Service/Active.


Yellow Card Properly Equipped and Provisioned. EPS and RPS currently in Standby.

Normal operating condition for Standby MPT-HL Transceiver.No Action required.

Green/Red Blinking

Card Properly Equipped and 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 far end:

1. Check alarms.2. Check abnormal conditions.3. Check protection schemes.

Path related problem: 1. Check RSL levels2. Check equipment alarms.3. Verify no weather related issue.

PA switch at the far end is set to OFF �0� position:

1. Verify PA switch position at far end and set to ON �1� position.

Yellow/Red Blinking

Card Properly Equipped and Provisioned, TX or RX signal Fault, EPS and RPS currently in Standby. Traffic maybe affected:Equipment problem at either near end or far end:

1. Check alarms.2. Check abnormal conditions.3. Check protection schemes.

Path related problem: 1. Check RSL levels2. Check equipment alarms.3. Verify no weather related issue.



IXL-101

Status(cont.)

Red Card Fail Replace MPT-HL TransceiverRed Blinking MAP Communication Time-out:

Communication between the MPT-HL Transceiver and the P8ETH cards is lost.

Check alarms for Internal CommunicationProblem, if present, see TAP-107.

Power Emission

Green LEDON

MPT-HL Transceiver is emitting power as expected according to the known configuration.

No Action required

Green LED Blinking

MPT-HL Transceiver is not emitting power due to a forced squelch condition.Most probable causes:1. TX mute active Release TX mute2. PA switch is positioned Off Position PA switch to On position

Green LED OFF

MPT-HL Transceiver is not emitting power for reasons other than �forced squelch�.1. Transmit Protection Switch (TPS)

is currently in standby state.Verify MPT-HL Transceiver should be in standby state.

2. Software booting or FPGA download in progress

Wait for software booting or FPGA download to complete

Table 101-J. TMN network troubleshootingProblem Possible Cause Possible SolutionUnusually slow communication in radio network

1. Normal network management traffic is saturating the communications channel.

2. Polling radios for PM data or missed alarms too rapidly

3. Multiple remote software downloads in process

4. IP traffic other than network management traffic being routed through radio network

1. There may be too many radios being managed within a single region. Split the radio network management into different regions and backhaul the traffic for each region through separate channels.

2. Poll the radios more slowly.3. Download to fewer radios at a

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

Table 101-I. MPT-HL transceiver LED alarm indications (cont.)LED Indication Probable cause Corrective action



IXL-101

Unable to operate controls using SNMP

To perform control operations, the Manager must be registered as a craft device.

Register the Manager as a craft device. Manager registration type can be changed as needed to type �ct� to allow control operation and then be changed back to �nml� for normal operation.

Can Read SNMP objects but cannot Write to SNMP objects

1. Incorrect community string2. If the TMN Interface is configured

for SNMPv2, the write community string is probably wrong.

1. Use the correct community string.2. Use the correct write community

string.

No traps being received from NE

1. Manager not registered in NE to receive traps

2. Communication failure in network3. Traps are blocked by firewall

1. Register Manager with NE.2. Check network connectivity.

Check redundant network paths and routing. Traceroute (tracert) is useful for locating path or routing faults.

3. Check firewall provisioning to allow trap UDP ports.

Unable to communicate with the NE through the radio network (unable to �ping� the NE).

1. Possible communication path failure or routing failure within the radio network.

2. Incorrect IP address on the PC.

1. Use traceroute (tracert) to help locate for communication path or routing problems.

2. Verify PC IP address, subnet, and default route.

Can �ping� the TMN Interface but cannot communicate with the NE using SNMP, or can only see a few SNMP objects in the NE.

1. If using SNMPv2, using the wrong community string, username, or passphrase.

2. Manager not registered or properly registered with the NE. The objects visible to an unregistered manager are generally: the 'system' MIB, a few objects under 'tsdimSnmpNEMibObject', the 'opticsIMMgrPollingInfoTable', the 'snmpUsmMib', and 'snmpVacmMib' objects.

1. Verify community string, username, and passphrase.

2. Verify Manager registration with the NE and register or correct registration.

Table 101-J. TMN network troubleshooting (cont.)Problem Possible Cause Possible Solution



IXL-101


Support procedures 4-57

IXL-102

IXL-102 Support procedures

IXL-102Support proceduresTable 102-A 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 9500 MPR-A Operation and Administration Manual (PN 3EM23954AM).

Table 102-A. Support proceduresSupport procedure SeeAlarm and event reports, Retrieve Operation and Administration

manualClean fiber-optic connectors DLP-112Clock reference and operation mode selections Operation and Administration

manualLog into system Operation and Administration

manual Loopback (Core Facing) Operation and Administration

manual Manage cross-connections Operation and Administration

manual MIB Database Management (Backup and Restore) Operation and Administration

manual Password change Operation and Administration

manual Performance monitoring Operation and Administration

manual Protection switching controls Operation and Administration

manual Provision equipment Operation and Administration

manual Provision or edit ports Operation and Administration

manual Preventive maintenance procedures RTL-100Protection upgrade and downgrade procedures DLP-117Software package rollback DLP-127System power down and power up DLP-113Upgrade and downgrade radio profile DLP-118Upgrade unlicensed MPT-HL radio to lower 6 GHz radio DLP-119


Support procedures4-58

IXL-102

Upgrade MPT ODU to MPT ODU L1 LAG port DLP-123Upgrade MPT-HL to MPT-HL L1 LAG port DLP-124

Table 102-A. Support procedures (cont.)


Equipment replacement procedures 5-59

IXL-103

IXL-103 Equipment replacement procedures

IXL-103Equipment replacement proceduresTable 103-A lists where to find the detailed level procedure (DLP) for replacing or adding each 9500 MPR-A replaceable unit.

Table 103-A. Equipment replacement proceduresEquipment See+24/-48 volt converter replacement DLP-120Auxiliary (AUX) replacement DLP-116Core switching module (Core-E) replacement DLP-103Core switching module (Core-E) flash card replacement DLP-104Ethernet access switch (P8ETH) replacement DLP-105Mechanical card removal and installation DLP-100MSS-1 shelf replacement DLP-128MSS-4/8 shelf FAN replacement DLP-106MPT-HL transceiver air filter replacement DLP-101MPT-HL transceiver replacement DLP-108ODU300 replacement DLP-109MOD300 (radio modem) replacement DLP-107MPTACC (MPT Access) replacement DLP-114MPT ODU replacement (MPT-HC, MPT-XP, 9558HC) DLP-115MPT Power Unit replacement DLP-125P2E3DS3 (2-Port DS3) replacement DLP-110P32E1DS1 (32-Port DS1) replacement DLP-111Power injector replacement DLP-121RPS/XPIC module replacement DLP-122SDHACC (2-Port OC-3) Replacement DLP-126SFP replacement DLP-102


Equipment replacement procedures5-60

IXL-103


Supporting information 6-61

IXL-104

IXL-104 Supporting information

IXL-104Supporting informationTable 104-A 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 9500 MPR-A Operation and Administration Manual (PN 3EM23954AM).

• See the 9500 MPR-A Product Information (PN 3EM23952AM) to determine card location and type.

Table 104-A. Supporting informationSupporting information SeeAlarm condition types Operation and Administration manualCard locations Product Information ManualProduct support information IntroductionElectrostatic-sensitive devices IntroductionHow to use TOP documentation IntroductionLaser precautions IntroductionMaintenance philosophy IntroductionOperations support system Operation and Administration manualSafety awareness IntroductionSecurity/user authorization Operation and Administration manual


Supporting information6-62

IXL-104


Preventive maintenance procedures 7-1

RTL-100

Routine Task Lists (RTLs)RTL-100 Preventive maintenance procedures

RTL-100Preventive maintenance proceduresThere are no preventive maintenance procedures associated with 9500 MPR-A, R4.2.0.

Table 100-A 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 100-A. Preventive maintenance proceduresActivity Frequency SeeMPT-HL transceiver air filter replacement Every 6 months DLP-101


Preventive maintenance procedures7-2

RTL-100


Facility alarms 8-1

TAP-100

Trouble Analysis Procedures (TAPs)TAP-100 Facility alarms

TAP-100Facility alarmsPurpose

This procedure describes how to identify and clear Facility alarms.

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 9500 MPR-A Product Information (PN 3EM23952AM) to determine card location and address.


Facility alarms8-2

TAP-100

See the 9500 MPR-A Operation and Administration (PN 3EM23954AM) for information about how to execute the commands that are described in this procedure.

STEP PROCEDURE

1 Using the Alarm Monitor, retrieve all alarms.

2 Review the output. See Table 100-A for information about facility alarms.

Table 100-A. Facility alarmsProbable cause Friendly name/entity Facility type SeeAIS 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 7DS1-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 10OptSdh-in/slot#[3-8]/Port[1-2]

AIS EleSdh-out/slot#[3-8]/Port[1-2] OC-3 Step 14OptSdh-out/slot#[3-8]/Port[1-2]

High BER EleSdh-in/slot#[3-8]/Port[1-2] OC-3 Step 17OptSdh-in/slot#[3-8]/Port[1-2]

High BER EleSdh-out/slot#[3-8]/Port[1-2]

OC-3 Step 21


Loss Of CESoETH frame CircuitTDM/MSS/DS1/Port#[1-16] DS1 (MSS/DS1) Step 24CircuitTDM/Slot#[3-8]/Port#[1-32] DS1 (P32E1DS1)CircuitTDM/Slot#[3-8]/Port#[1-2] DS3CircuitTDM/Slot#[3-8]/Port#[1-2] OC-3

Loss Of Frame DS1-in/MSS/DS1/Port#[1-16] DS1 (MSS/DS1) Step 77DS1-in/Slot#[3-8]/Port#[1-32] DS1 (P32E1DS1)DS3-in/Slot#[3-8]/Port#[1-2] DS3

Loss of frame DS1-out/MSS/DS1/Port#[1-16] DS1 (MSS/DS1) Step 108DS1-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 77OptSdh-in/slot#[3-8]/Port[1-2]


Facility alarms 8-3

TAP-100

AIS

On DS1/3-in on DS1 or DS3 facility

3 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?

If yes, go to step 190.If no, go to step 189.

AIS

On DS1/3-out on DS1 or DS3 facility

7 Troubleshoot the upstream source of the incoming DS1 or DS3.


9 Did the AIS (on DS1/3-out) alarm clear?


Loss of frame EleSdh-out/slot#[3-8]/Port[1-2] OC-3OC-3 Step 108OptSdh-out/slot#[3-8]/Port[1-2]

Loss of signal DS1-in/MSS/DS1/Port#[1-16] DS1 (MSS/DS1) Step 155DS1-in/Slot#[3-8]/Port#[1-32] DS1 (P32E1DS1)DS3-in/Slot#[3-8]/Port#[1-2] DS3

Loss of signal EleSdh-in/slot#[3-8]/Port[1-2] OC-3 Step 155OptSdh-in/slot#[3-8]/Port[1-2]

Remote defect indication EleSdh-in/slot#[3-8]/Port[1-2] OC-3 Step 178OptSdh-in/slot#[3-8]/Port[1-2]

Trace identifier mismatch EleSdh-in/slot#[3-8]/Port[1-2] OC-3 Step 182OptSdh-in/slot#[3-8]/Port[1-2]

None of the above � � IXL-101

Table 100-A. Facility alarms (cont.)


Facility alarms8-4

TAP-100

AIS

On EleSdh/EleSDH-in on OC-3 facility

10 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?


AIS

On EleSdh/EleSDH-out on OC-3 facility

14 Troubleshoot the upstream source of the incoming OC-3.


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


High BER

On EleSdh/EleSDH-in on OC-3 facility

17 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?



Facility alarms 8-5

TAP-100

High BER

On EleSdh/EleSDH-out on OC-3 facility

21 Troubleshoot the upstream source of the incoming OC-3.


23 Did the High BER (on EleSdh/OptSdh-out) alarm clear?


Loss Of CESoETH frame

on DS1, DS3, or OC-3 facility

24 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?

If yes, clear the path or circuit alarms, or path PM errors, then go to step 27.If no, go to step 29.


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?



Facility alarms8-6

TAP-100

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.



Facility alarms 8-7

TAP-100



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 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 CESoETH Frame alarm?

If MSS-1 shelf, see DLP-128 to replace near end MSS-1 shelf.If P32E1DS1, see DLP-111 to replace near end P32E1DS1 card.


Facility alarms8-8

TAP-100

If P2E3DS3, see DLP-110 to replace near end P2E3DS3 card.If SDHACC, see DLP-126 to replace near end SDHACC card.





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.





Which card reported the Loss Of CESoETH Frame alarm?

If MSS-1 shelf, see DLP-128 to replace far end MSS-1 shelf.If P32E1DS1, see DLP-111 to replace far end P32E1DS1 card.If P2E3DS3, see DLP-110 to replace far end P2E3DS3 card.If SDHACC, see DLP-126 to replace far end SDHACC card.





Facility alarms 8-9

TAP-100

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?

If main, perform Forced EPS Switch at near end using Craft Terminal.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?

If P32E1DS1, see DLP-111 to replace near end P32E1DS1 card.If P2E3DS3, see DLP-110 to replace near end P2E3DS3 card.If SDHACC, see DLP-126 to replace near end SDHACC card.


66 Did the Loss Of CESoETH Frame condition clear?



Is the card in alarm the main or spare?

If main, perform Forced EPS Switch at far end using Craft Terminal.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.





Facility alarms8-10

TAP-100

71 Which card reported the Loss Of CESoETH Frame?

If P32E1DS1, see DLP-111 to replace far end P32E1DS1 card.If P2E3DS3, see DLP-110 to replace far end P2E3DS3 card.If SDHACC, see DLP-126 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.

Loss Of Frame

On DS1/3-in on DS1 or DS3 or Ele/OptSdh-in on OC-3 facility

77 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?

If yes, clear circuit alarms, then go to step 79.If no, go to step 81.


80 Did the Loss Of Frame alarm the clear?



Facility alarms 8-11

TAP-100

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.





Facility alarms8-12

TAP-100

90 CAUTION: Possibility of service interruption. The following steps cause a loss of traffic on ALL facilities that are supported by the card or MSS-1 shelf, associated with the facility in alarm. Schedule appropriate maintenance window per local practices and procedures.

Is it appropriate to proceed with Loss Of Frame procedure?




92 CAUTION: Possibility of service interruption. Reseating card in an unprotected facility causes a loss of traffic on ALL facilities that are associated with the card being reseated. Schedule appropriate maintenance window per local practices and procedures.

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




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?

If MSS-1 shelf, see DLP-128 to replace near end MSS-1 shelf.If P32E1DS1, see DLP-111 to replace near end P32E1DS1 card.If P2E3DS3, see DLP-110 to replace near end P2E3DS3 card.If SDHACC, see DLP-126 to replace near end SDHACC card.




TAP-100




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.




103 Which card reported the Loss Of Frame?

If P32E1DS1, see DLP-111 to replace near end P32E1DS1 card.If P2E3DS3, see DLP-110 to replace near end P2E3DS3 card.If SDHACC, see DLP-126 to replace far end SDHACC card.


105 Did the Loss Of Frame condition clear?




107 Go to step 190.

Loss of frame

On DS1/3-out on DS1 or DS3 or Ele/OptSdh-out on OC-3 facility

108 Check the far end facility for Loss of Frame (DS1/3-in, Ele/OptSdh-in) that is associated with the facility in alarm.


Facility alarms8-14

TAP-100




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?

If yes, clear path or circuit alarms or path PM errors, then go to step 114.If no, go to step 116.




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?




TAP-100

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?



Facility alarms8-16

TAP-100



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 practices and procedures.

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.





Which card reported the Loss Of Frame alarm?

If MSS-1 shelf, see DLP-128 to replace near end MSS-1 shelf.If P32E1DS1, see DLP-111 to replace near end P32E1DS1 card.If P2E3DS3, see DLP-110 to replace near end P2E3DS3 card.If SDHACC, see DLP-126 to replace near end SDHACC card.






TAP-100


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.





Which card reporting Loss Of Frame alarm?

If MSS-1 shelf, see DLP-128 to replace far end MSS-1 shelf.If P32E1DS1, see DLP-111 to replace far end P32E1DS1 card.If P2E3DS3, see DLP-110 to replace far end P2E3DS3 card.If SDHACC, see DLP-126 to replace far end SDHACC card.





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.



Facility alarms8-18

TAP-100



142 Which card reporting Loss Of Frame?






Is card in alarm main or spare?

If main, perform Forced EPS Switch at far end using Craft Terminal.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?

If P32E1DS1, see DLP-111 to replace far end P32E1DS1 card.If P2E3DS3, see DLP-110 to replace far end P2E3DS3 card.If SDHACC, see DLP-126 to replace far end SDHACC card.






TAP-100


Release Forced/Lockout EPS Switch at far end using Craft Terminal.



154 Go to step 190.

Loss of signal

DS1/3-in on DS1, DS3, or OC-3 facility

155 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?





Facility alarms8-20

TAP-100


Reseat the card that declares the Loss Of Signal alarm. Physically remove the card and reinsert.


164 Did declaring Loss Of Signal alarm clear?



Which card reported the Loss Of Signal alarm?





168 CAUTION: Possibility of service interruption. Forced EPS switching traffic causes a disruption to 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.




TAP-100

172 Did the declaring Loss Of Signal alarm clear?


173 Which card reported the Loss Of Signal alarm?





176 CAUTION: Possibility of service interruption. Releasing EPS switch may cause a disruption to traffic.


177 Go to step 190.


178 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?



Facility alarms8-22

TAP-100

Trace identifier mismatch

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


Abnormal conditions 8-23

TAP-101

TAP-101 Abnormal conditions

TAP-101Abnormal conditionsPurpose

This procedure describes how to identify and clear a protection switch (Forced and Lockout), loopback, Forced Adaptive Modulation, and TxMute abnormal conditions on Core-E, MOD300, MPT-HC/MPT-XP/9558HC (MPT ODU), MPT-HL ODU300, P2E3DS3, P32E1DS1, SDHACC cards or MSS-1 shelf.

General

A Core Facing PDH Loopback indicates that PDH (DS1 or DS3) 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 Lockout Switch EPS/RPS/TPS indicates that a lockout switch has been executed for the protection group.

TxMute indicates that a manual or automatic mute command has been executed.



STEP PROCEDURE

1 Using the Craft Terminal, retrieve abnormal conditions.

2 Review the output. See Table 101-A for information about abnormal conditions.


Abnormal conditions8-24

TAP-101

Table 101-A. Abnormal conditionsOperation Name Type (equipment) SeeCore facing PDH loopback

DS1 Port#[1-16] Internal LoopbackMSS/DS1

Step 3

DS1 Port#[1-32] Internal LoopbackSLOT#[3-8]DS3 Port#[1-2] Internal



Step 7



Direction #[3-8].[5-8] Loopback(MPT-HL)


Direction #[3-8] Radio (MOD300)

Step 11

Direction #1.[1-6] Radio(MPT ODU connected to Core-E, MSS/CORE)

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

Direction #[3-8].[5-8] Radio(MPT ODU connected to P8ETH)

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

Direction #1.[5-6] Radio(MPT-HL connected to Core-E, MSS/CORE)



TAP-101

Forced switch EPS Main#1 Slot#1 (Core-E) Step 15Main#1 Slot#[3,5,7] (MOD300, P2E3DS3,

P32E1DS1, SDHAC)Main#1 Slot #[3-8] Port #[1-4] MPT ODU connected to

MPTACCMain#1 Slot #1 Port #[1,3,5] MPT ODU connected to

Core-EMain#1 MSS/CORE Port #[1,3,5] MPT ODU connected to

MSS/COREMain#1 Slot #[3,5,7] Port #[5-8] MPT-HL connected to

P8ETHForced switch RPS Main#1 Slot #[3-8] Port #[1-4] MPT ODU connected to

MPTACCStep 15

Main#1 Slot #1 Port #[1,3,5] MPT ODU connected to Core-E

Main#1 MSS/CORE Port #[1,3,5] MPT ODU connected to MSS/CORE

Main#1 Slot #[3,5,7] Port #[5-8] MPT-HL connected to P8ETH

Main#1 Slot#[3,5,7] MOD300Forced switch TPS Main#1 Slot #[3-8] Port #[1-4] MPT ODU connected to

MPTACCStep 15

Main#1 Slot #1 Port #[1,3,5] MPT ODU connected to Core-E

Main#1 MSS/CORE Port #[1,3,5] MPT ODU connected to MSS/CORE

Main#1 Slot #[3,5,7] Port #[5-8] MPT-HL connected to P8ETH

Main#1 Slot#[3,5,7] MOD300IF cable loopback Direction #[3-8] MOD300 Step 20Line facing circuit loopback


Step 24



Table 101-A. Abnormal conditionsOperation Name Type (equipment) See



TAP-101


DS1 Port#[1-16] External LoopbackMSS/DS1]

Step 28

DS1 Port#[1-32] External LoopbackSLOT#[3-8]DS3 Port#[1-2] External

Lockout switch EPS Spare#0 Slot#2 Core-E Step 32Spare#0 Slot#[4,6,8] MOD30, P2E3DS3,

P32E1DS1, SDHACCSpare#0 Slot#[3-8] Port #[1-4] MPT ODU connected to

MPTACCSpare#0 Slot #1 Port #[2,4,6] MPT ODU connected to

Core-ESpare#0 MSS/CORE Port #[2,4,6] MPT ODU connected to

MSS/CORESpare#0 Slot #[4,6,8] Port #[5-8] MPT-HL connected to

P8ETHLockout switch RPS Spare#0 Slot#[3-8] Port #[1-4] MPT ODU connected to

MPTACCStep 32

Spare#0 Slot #1 Port #[2,4,6] MPT ODU connected to Core-E

Spare#0 MSS/CORE Port #[2,4,6] MPT ODU connected to MSS/CORE

Spare#0 Slot #[4,6,8] Port #[5-8] MPT-HL connected to P8ETH

Spare#0 Slot#[4,6,8] MOD300Lockout switch TPS Spare#0 Slot #[3-8] Port #[1-4] MPT ODU connected to

MPTACCStep 32

Spare#0 Slot #1 Port #[2,4,6] MPT ODU connected to Core-E

Spare#0 MSS/CORE Port #[2,4,6] MPT ODU connected to MSS/CORE

Spare#0 Slot #[4,6,8] Port #[5-8] MPT-HL connected to P8ETH

Spare#0 Slot#[4,6,8] MOD300




TAP-101

Core facing PDH loopback

3 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 Ready to release the Digital Core Facing Loopback?




10 Did the Digital Core Facing Loopback condition clear?


TXMute Direction #1.[1-6] - Channel #[0-1] MPT ODU connected to Core-E, MSS/CORE

Step 36

Direction #[3-8].[1-4] - Channel #[0-1] MPT ODU connected to MPTACC

Direction #[3-8].[5-8] - Channel #1 MPT ODU connected to P8ETH

Direction #[3-8].[5-8] - Channel #[0-1] MPT-HL connected to P8ETH

Direction #1.[5-6] - Channel #1 MPT-HL connected to Core-E, MSS/CORE

Direction #[3-8] - Channel #[0-1] ODU300None of the above � � IXL-101




TAP-101


11 Ready for the Forced Adaptive Modulation to be released?


12 Using the Craft Terminal, release the Forced Adaptive Modulation.


14 Did the Forced Adaptive Modulation condition clear?


Forced switch

EPS, RPS, and TPS

15 Ready to release the Forced Switch EPS/RPS/TPS?


16 CAUTION: Possibility of service interruption. Releasing a Forced Switch causes a disruption to traffic.

17 Using the Craft Terminal, release Forced Switch EPS/RPS/TPS.


19 Did the Forced Switch EPS/RPS/TPS condition clear?


IF cable loopback

20 Ready to release the IF Cable Loopback?






TAP-101

23 Did the IF Cable Loopback condition clear?


Line facing circuit loopback

24 Ready to release the loopback?




27 Did the Line Facing Circuit Loopback condition clear?



28 Ready to release the Line Facing PDH Loopback?




31 Did the Line Facing PDH Loopback condition clear?


Lockout switch

EPS, RPS, and TPS

32 Ready to release the Lockout Switch EPS/RPS/TPS?


33 Using the Craft Terminal, release the lockout switch.




TAP-101

35 Did the Lockout Switch EPS/RPS/TPS condition clear?


TXMute

36 Ready for the TxMute to be released?


37 Using the Craft Terminal, release the TxMute.


39 Did the TxMute condition clear?





Power alarms 8-31

TAP-102

TAP-102 Power alarms

TAP-102Power alarmsPurpose

This procedure describes how to identify and clear power alarms that are associated with the MSS-1/MSS-4/MSS-8 shelf, MPTACC card, and MSS-1 Core.

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


See the 9500 MPR-A Operation and Administration (PN 3EM23954AM) for the procedures about how to execute the commands that are described in this procedure.

STEP PROCEDURE


2 Review the output. See Table 102-A for information about the power alarms.


Power alarms8-32

TAP-102

Battery failure

3 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?


Table 102-A. Power AlarmsProbable cause Friendly name/entity Equipment type SeeBattery failure r01/subrack#1 MSS-1/4/8 Step 3Power supply failure r01/subrack#[3-8][1-4] MPTACC Step 14

r01/subrack#[1][1-2] MSS/CoreSecondary battery failure r01/subrack#1 MSS-1/4/8 Step 72None of the above � � IXL-101


Power alarms 8-33

TAP-102

Power supply failure

14 Inspect the power supply cable connection for radio port in alarm:

For MPTACC, verify RJ45 connector for PFoE port or Coax connector for QMA port.For MSS-1 CORE, verify RJ45 connector for PFoE port.

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?

If MPTACC, go to step 20.If MSS-1 CORE, go to step 44.

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?



Power alarms8-34

TAP-102

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?

If main, go to step 28.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.

37 CAUTION: Possibility of service interruption. Removing an in-service card in an unprotected link causes loss of traffic.

38 Physically reseat card in alarm and wait for the status LED to turn steady green or amber.



Power alarms 8-35

TAP-102



41 See DLP-114 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 to replace MSS-1 shelf.



Power alarms8-36

TAP-102



55 Inspect the power supply cable connection at MPT ODU.

56 Is power supply cable damaged or improperly connected?


57 Terminate, repair, or replace power supply cable as required.




60 Inspect the power supply cable run between the MPTACC/MSS-1 CORE and MPT ODU.

61 Is the power supply cable damaged?


62 Repair or replace the power supply cable as required.




65 Which card is Power Supply Failure alarm declared?

If MPTACC, go to step 66.If MSS-1 CORE, go to step 84.

66 Is MPTACC in alarm in a protected system?



Power alarms 8-37

TAP-102

67 CAUTION: Possibility of service interruption. Releasing Forced EPS/HSB/RX Radio switch causes a disruption to traffic.

68 Release the Forced/Lockout EPS Switch using the Craft Terminal.

69 Release the Forced/Lockout HSB Switch using the Craft Terminal.

70 Release the Forced/Lockout Rx Radio Switch using the Craft Terminal.

71 Go to step 84.

Secondary battery failure

72 Verify that there is no blown fuse providing power to the B-power feed.

73 Verify the shelf power cable connections between the MSS-1/4/8 and the PDU.

74 Verify the B-power connections between the BDFB and PDU.

75 Verify that the B-power BDFB breakers are in the ON position.


77 Did the Secondary Battery Failure clear?


78 Measure the voltage of the B-power feed.

79 Is the measured voltage within the supported voltage range (-40.8 VDC to -57.6 VDC)?


80 Troubleshoot the B-power feed voltage problem.


82 Did the Secondary Battery Failure condition clear?





Power alarms8-38

TAP-102


Equipment alarms 8-39

TAP-103

TAP-103 Equipment alarms

TAP-103Equipment alarmsPurpose

This procedure describes how to identify and clear Equipment alarms (Replaceable Unit Problem, Replaceable Unit Missing, Replaceable Unit Type Mismatch, Excessive EnvironmentalTemperature, or Unconfigured Equipment Present) on Core-E, FAN, MOD300, MPTACC, MPT-HC/MPT-XP/9558HC (MPT ODU), MPT-HL, ODU300, P2E3DS3, P8ETH, P32E1DS1, or SDHACC.

General

An Excessive Environmental Temperature alarm indicates that excessive temperature on MPT-HL card has been detected, or MPT-HL 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.


See the 9500 MPR-A Operation and Administration (PN 3EM23954AM) for the procedures about how to execute the commands that are described in this procedure.

STEP PROCEDURE


2 Review the output. See Table 103-A for information about equipment alarms.


Equipment alarms8-40

TAP-103

Table 103-A. Equipment alarmsOperation Name Equipment type SeeExcessive environmental temperature


Step 3


Replaceable unit missing r01s1/board#[8] AUX Step 14r01s1/board#[1-2] Core-Er01s1/board#[5,9] FANr01s1/board#[3-8] MOD300, MPTACC,

P2E3DS3, P8ETH, P32E1DS1, SDHACC

r01s1b[1-2]/daughter#[5-6] SFP on Core-Er01s1b1/daughter#[5-6] SFP on MSS/COREr01s1b[3-8]/daughter#[03-04] SFP on MPTACCr01s1b[3-8]/daughter#[05-08] SFP on P8ETHr01s1b[3-8]/daughter#[01-02] SFP on SDHACCr01s[3-8][1-4]b1/daughter#03 RPS SFP on MPT ODU

connected to MPTACCr01s1[1-6]b1/daughter#03 RPS SFP on MPT ODU




TAP-103

Replaceable unit problem r01s1/board#[8] AUX Step 24r01s1/board#[1-2] Core-Er01s1/board#[5,9] FANr01s1/board#[3-8] MOD300, MPTACC,







r01/subrack#[3-8] ODU300r01s1b[1-2]/daughter#[05-06] SFP on Core-Er01s1b1/daughter#[05-06] SFP on MSS/COREr01s1b[3-8]/daughter#[03-04] SFP on MPTACCr01s1b[3-8]/daughter#[05-08] SFP on P8ETHr01s1b[3-8]/daughter#[01-02] SFP for SDHr01s[3-8][1-4]b1/daughter#03 RPS SFP on MPT ODU

connected to MPTACCr01s1[1-6]b1/daughter#03 RPS SFP on MPT ODU


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 MPT ODU connected to P8ETH

r01s[3-8][1-4]b1/daughter#04 RPS or XPIC Module on MPT ODU connected to MPTACC

Table 103-A. Equipment alarms (cont.)Operation Name Equipment type See



TAP-103

Excessive environmental temperature

3 Verify that the MPT-HL card fan is equipped and operating properly.

4 Is the MPT-HL fan equipped and operating properly?



r01s1/board#[8] AUX Step 161r01s1/board#[1-2] Core-Er01s1/board#[5,9] FANr01s1/board#[3-8] MOD300, MPTACC,







Replaceable unit type mismatch - ODU300

r01/subrack#[3-8] ODU300 Step 178


r01s1/board#[8] AUX Step 188r01s1/board#[2] Core-Er01s1/board#[5,9] FANr01s1/board#[3-8] MOD300, MPTACC,


r01s1b[1-2]/daughter#[05-06] SFP on Core-Er01s1b1/daughter#[05-06] SFP on MSS/COREr01s1b[3-8]/daughter#[03-08] SFP on MPTACCr01s1b[3-8]/daughter#[05-08] SFP on P8ETHr01s1b[3-8]/daughter#[01-02] SFP on SDHACC


Table 103-A. Equipment alarms (cont.)Operation Name Equipment type See



TAP-103

5 Is the traffic affected?


6 Replace the MPT-HL. See DLP-108 to replace MPT-HL.


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 shelf air filter and replace if air filter condition indicates that filter replacement is required. See DLP-101 to replace the MPT-HL air filter.

11 Verify that no obstruction occurred that prevents proper air flow through the MPT-HL card.


13 Did the Excessive Environmental Temperature alarm clear?


Replaceable unit missing

14 Visually inspect the indicated slot location.

15 Is the slot location empty?


16 Install the card/SFP type corresponding to slot provisioning.




TAP-103

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?


Replaceable unit problem

24 CAUTION: Possibility of service interruption. Core-E, P2E3DS3, P32E1DS1, MPTACC, P8ETH 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 practices and procedures.

25 What equipment type is the Replaceable Unit Problem declared against?

If Core-E, P2E3DS3, or P32E1DS1 go to step 68.If FAN, go to step 99.If MPTACC go to step 77.If MOD300, MPT ODU, ODU300, or P8ETH go to step 85.If MPT-HL, go to step 26.If SFP, go to step 113.If RPS SFP on MPT ODU go to step 139.If RPS or XPIC module on MPT ODU go to step 154.

26 Verify that the MPT-HL PA switch is in the ON �1� position.

27 Is the MPT-HL PA switch in the ON �1� position?




TAP-103

28 Ready to move the MPT-HL PA switch to the ON �1� position?


29 When the MPT-HL 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 PA switch to the ON �1� position.


32 Did the Replaceable Unit Problem alarm clear?


33 Is the MPT-HL in alarm in a protected system?


34 CAUTION: Possibility of service interruption. Performing Manual EPS/HSB/Rx Radio switch causes a disruption to traffic.

35 Is the MPT-HL 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.




TAP-103

45 Go to step 47.


47 See DLP-108 to replace MPT-HL.




50 Is the MPT-HL in alarm in a protected system?


51 CAUTION: Possibility of service interruption. Releasing Forced EPS/HSB/Rx Radio switch causes a disruption to traffic.




55 Is the protection scheme configured as Not Revertive?


56 NOTE: To verify the replaced MPT-HL is capable of carrying traffic, the replaced MPT-HL must be placed in the Active state.

57 CAUTION: Possibility of service interruption. Performing Manual EPS/HSB/Rx Radio switch causes a disruption to traffic.

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 status is Active.

62 Verify that the local and far end radio direction are alarm free and error-free.



TAP-103

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?






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.




d. Is the power to the radio channels provided by the MPTACC card?



TAP-103

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?



82 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 card(s) resides in slots 4, 6, and/or 8.

83 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. 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?



If MPT ODU go to step 86.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?




TAP-103

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.





If Core-E, see DLP-103 to replace Core-E.If FAN, see DLP-106 to replace FAN.If MOD300, see DLP-107 to replace MOD300.If MPT ODU see DLP-115 to replace MPT ODU.If ODU300, see DLP-109 to replace ODU300.If P2E3DS3, see DLP-110 to replace P2E3DS3.If P8ETH, see DLP-105 to replace P8ETH.If P32E1DS1, see DLP-111 to replace P32E1DS1.If SDHACC, see DLP-126 to replace SDHACC.



TAP-103




105 CAUTION: Possibility of service interruption. Releasing EPS switch may cause a disruption to traffic.


107 Go to step 199.

108 CAUTION: Possibility of service interruption. Releasing Forced EPS/HSB/RX Radio switch causes a disruption to traffic.




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?



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


120 Go to step 127.



TAP-103


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


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.




130 See DLP-102 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).



TAP-103

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 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 to replace MPT ODU associated with RPS SFP in alarm.






TAP-103

154 See DLP-122 to replace RPS/XPIC module in alarm.




157 See DLP-115 to replace MPT ODU associated with RPS/XPIC module in alarm.




160 Go to step 199.


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

If Core-E, see DLP-103 to replace Core-E.If FAN, see DLP-106 to replace FAN.If MOD300, see DLP-107 to replace MOD300.If MPTACC, see DLP-114 to replace MPTACC.If MPT ODU, see DLP-115 to replace MPT ODU.If MPT-HL, see DLP-108 to replace MPT-HL.If P2E3DS3, see DLP-110 to replace P2E3DS3.If P8ETH, see DLP-105 to replace P8ETH.If P32E1DS1, see DLP-111 to replace P32E1DS1.If SDHACC, see DLP-126 to replace SDHACC.




TAP-103

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 to replace an SFP.




175 Reprovision the SFP slot to the correct SFP type.




Replaceable unit type mismatch - ODU300

178 Verify that the radio channel provisioning corresponding to the ODU300 in alarm is correct as described in the site engineering documentation.



TAP-103

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 to replace ODU300.




185 Reprovision the radio channel as described in the site engineering documentation.





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




TAP-103

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?





Radio alarms (MPT-HC, MPT-HL, MPT-XP, MOD300, ODU300, 9558HC) 8-57

TAP-104

TAP-104 Radio alarms (MPT-HC, MPT-HL, MPT-XP, MOD300, ODU300, 9558HC)

TAP-104Radio alarms (MPT-HC, MPT-HL, MPT-XP, MOD300, ODU300, 9558HC)Purpose

This procedure describes how to identify and clear radio alarms on MPT-HC/MPT-XP/9558HC (MPT ODU), MPT-HL, MOD300, and ODU300.

General

A Bandwidth Over Flow alarm indicates that while the MPT ODU/MPT-HL 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 in alarm.

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/ODU300.

An Incompatible Power/Incompatible TX Power alarm indicates that the configured transmit power value is not supported by the MPT ODU/MPT-HL/ODU300.

A Link Identifier Mismatch alarm indicates that the link identifier number provisioned on MPT ODU/MPT-HL/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.


Radio alarms (MPT-HC, MPT-HL, MPT-XP, MOD300, ODU300, 9558HC)8-58

TAP-104

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.



STEP PROCEDURE


2 Review the output. See Table 104-A for information about radio alarms.

Table 104-A. Radio alarmsProbable cause Friendly name/entity Equipment type SeeBandwidth over flow Radio/Dir#[3-8].[1-4]/

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

Step 3















TAP-104

CLA Radio/Dir#[3-8].[1-4]/Slot#[3-8]/Port#[1-4]/Ch#[0-1]


Step 7







Radio/Dir#[3-8]/Ch#[0-1] MOD300Demodulator fail Radio/Dir#[3-8].[1-4]/


Step 24













Radio/Dir#[3-8]/Ch#[0-1] MOD300Early warning indication Radio/Dir#[3-8].[1-4]/


Step 36














Table 104-A. Radio alarmsProbable cause Friendly name/entity Equipment type See



TAP-104

High BER Radio/Dir#[3-8].[1-4]/Slot#[3-8]/Port#[1-4]/Ch#[0-1]


Step 38













Radio/Dir#[3-8]/Ch#[0-1] MOD300Incompatible frequency Radio/Dir#[3-8].[1-4]/


Step 51

















TAP-104

Incompatible modulation Radio/Dir#[3-8].[1-4]/Slot#[3-8]/Port#[1-4]/Ch#[0-1]


Step 61













Incompatible protection Radio/Dir#[3-8].[1-4]/Slot#[3-8]/Port#[1-4]/Ch#[0-1]


Step 71





Incompatible shifter Radio/Dir#[3-8].[1-4]/Slot#[3-8]/Port#[1-4]/Ch#[0-1]


Step 84













Radio/Dir#[3-8]/Ch#[0-1] ODU300




TAP-104

Incompatible power Radio/Dir#[3-8].[5-8]/Slot#[3-8]/Port#[5-8]/Ch#[0-1]


Step 94





Incompatible TX power Radio/Dir#[3-8].[1-4]/Slot#[3-8]/Port#[1-4]/Ch#[0-1]


Step 94







Radio/Dir#[3-8]/Ch#[0-1] ODU300Link identifier mismatch AirFrame/Dir#[3-8].[1-4]/

Slot#[3-8]/Port#[1-4]/Ch#1,AirFrame/Dir#[3-8].[1-4]/Slot#[3-8]/Port#[1-4]


Step 104

AirFrame/Dir#1.[1-6]/Slot#1/Port#[1-6]/Ch#1,AirFrame/Dir#1.[1-6]/Slot#1/Port#[1-6]


AirFrame/Dir#1.[1-6]/MSS/CORE/Port#[1-6]/Ch#1,AirFrame/Dir#1.[1-6]/MSS/CORE/Port#[1-6]


AirFrame/Dir#[3-8].[5-8]/Slot#[3-8]/Port#[5-8]/Ch#1




AirFrame/Dir#1.[5-6]/Slot#1/Port#[5-6]


AirFrame/Dir#1.[5-6]/MSS/CORE/Port#[5-6]


AirFrame/Dir#[3-8]/Ch#1, AirFrame/Dir#[3-8]

MOD300




TAP-104

Loss of protection Radio/Dir#[3-8]/Ch#1 MOD300 Step 111Radio/Dir#[3-8].[1-4]/Slot#[3-8]/Port#[1-4]/Ch#1






Loss of signal MAU/subrack[#3-8].[1-4]daughter#03 MPT ODU connected to MPTACC

Step 119

MAU/subrack[#3-8].[5-8] Port#n MPT-HL connected to P8ETH

PPP fail PPP-IP/RF#1[1-6] MPT ODU connected to Core-E, MSS/CORE

Step 125





PPP-IP/RF#[3-8] MOD300Remote defect indication Radio/Dir#[3-8].[1-4]/


Step 140













Radio/Dir#[3-8]/Ch#[0-1] MOD300None of the above � � IXL-101




TAP-104

Bandwidth over flow

3 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?


CLA

7 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, or ODU300 will cause a loss of traffic on ALL facilities associated with the MPT ODU, MPT-HL, 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/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?




TAP-104

14 Wait two minutes for the CLA alarm to be declared against the MPT ODU, MPT-HL, or ODU300.


16 Is the CLA alarm declared against the MPT ODU, MPT-HL, or ODU300?


17 Replace the MPT ODU, MPT-HL, or ODU300 CLA declared against.

See DLP-115 to replace MPT ODU.See DLP-108 to replace MPT-HL.See DLP-107 to replace MOD300.

18 CAUTION: Possibility of service interruption. Performing Clear CLA command on MPT ODU, MPT-HL, or ODU300 will cause a loss of traffic on ALL facilities associated with the MPT ODU, MPT-HL, 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, or ODU300.


23 Is the CLA alarm declared against the MPT ODU, MPT-HL, or ODU300?


Demodulator fail

24 Verify that there are no weather-related conditions.



TAP-104

25 Do weather-related conditions exist?

If yes, wait for the weather to clear and recheck alarms. Go to step 145.If no, go to step 26.

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, or MOD300 Demodulator Fail declared against.

See DLP-115 to replace MPT ODU.See DLP-108 to replace MPT-HL.See DLP-107 to replace MOD300.


35 Did the Demodulator Fail alarm clear?


Early warning indication

36 No action is required at this time. Monitor the receive signal for increased degrading.

37 Go to step 145.



TAP-104

High BER

38 Verify that there are no weather-related conditions.

39 Do weather-related conditions exist?

If yes, wait for the weather to clear and recheck the alarms. Go to step 145.If no, go to step 40.




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?

If yes, go to step 144.If no, align the antenna. See the 9500 MPR-A Turn-Up Manual (PN 3EM23955AM) Antenna Polarization Verification (DLP-105) Antenna Feedhorn Verification - XPD Procedure.


50 Did the High BER alarm clear?




TAP-104

Incompatible frequency

51 Using the Craft Terminal, retrieve the provisioned frequency value and supported frequency of the MPT ODU, MPT-HL, 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, or ODU300?


54 Reprovision the frequency of the MPT ODU, MPT-HL, 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, or ODU300 in an unprotected facility causes a loss of traffic on ALL facilities that are associated with the MPT ODU, MPT-HL, or ODU300 being replaced. Schedule appropriate maintenance window per local practices and procedures.

58 Replace the MPT ODU, MPT-HL, or ODU300 with the version that supports the required frequency of the microwave link.

For MPT ODU replacement, see DLP-115.For MPT-HL replacement, see DLP-108.For ODU300 replacement, see DLP-109.


60 Did the Incompatible Frequency alarm clear?


Incompatible modulation

61 Using the Craft Terminal, retrieve the provisioned modulation value and supported modulation of the MPT ODU/MPT-HL.

62 Verify the required modulation of the microwave link.



TAP-104

63 Is the required microwave link modulation supported by the MPT ODU/MPT-HL?


64 Reprovision the modulation of the MPT ODU/MPT-HL 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/MPT-HL in an unprotected facility causes a loss of traffic on ALL facilities that are associated with the MPT ODU/MPT-HL being replaced. Schedule appropriate maintenance window per local practices and procedures.

68 Replace the MPT ODU/MPT-HL with the version that supports the required modulation of the microwave link.

For MPT ODU replacement, see DLP-115.For MPT-HL replacement, see DLP-108.


70 Did the Incompatible Modulation alarm clear?


Incompatible protection

71 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 to install the appropriate RPS/XPIC module.




TAP-104

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?


78 See DLP-122 to replace the incorrect RPS/XPIC module.




81 See DLP-122 to replace the RPS/XPIC module in alarm.




Incompatible shifter

84 Using the Craft Terminal, retrieve the provisioned shifter value and supported shifter levels of the MPT ODU, MPT-HL, 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, or ODU300?


87 Reprovision the shifter value of the MPT ODU/MPT-HL/ODU300 to the required shifter value of the microwave link.




TAP-104

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/ODU300 being replaced. Schedule appropriate maintenance window per local practices and procedures.

91 Replace the MPT ODU/MPT-HL/ODU30 with version that supports the required shifter value of the microwave link.



93 Did the Incompatible Shifter alarm clear?


Incompatible power

Incompatible TX power

94 Using the Craft Terminal, retrieve the provisioned transmit power value and supported transmit power level of the MPT ODU/MPT-HL/ODU300.

95 Verify the required transmit power level of the microwave link.

96 Is the required microwave link transmit power level supported by the MPT ODU/MPT-HL/ODU300?


97 Reprovision the transmit power level of the MPT ODU/MPT-HL/ODU300 to the required transmit power level of the microwave link.


99 Did the Incompatible TX Power alarm clear?




TAP-104

100 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/ODU300 being replaced. Schedule appropriate maintenance window per local practices and procedures.

101 Replace the MPT ODU/MPT-HL/ODU300 with the version that supports the required transmit power level of the microwave link.



103 Did the Incompatible TX Power alarm clear?


Link identifier mismatch

104 NOTE: Link Identifier Mismatch alarm failure signatures are different for MPT ODU/MPT-HL versus ODU300. For MPT ODU/MPT-HL 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/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?


Loss of protection

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



TAP-104


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?


Loss of signal

119 Verify that the Core-E/MPTACC/P8ETH card Ethernet port is operating normally.




122 Verify the link cabling between the Core-E/MPTACC/P8ETH card Ethernet port and the MPT ODU/MPT-HL.




PPP fail

125 Retrieve the alarms using the Alarm Monitor, verify that no other radio path alarms (such as Demodulator Fail) exist, and troubleshoot accordingly.



TAP-104

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.






TAP-104


140 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 troubleshoot accordingly.


143 Did the RDI alarm clear?






TAP-104


Ethernet alarms (Core-E, MPTACC, P8ETH, MSS-1 Shelf Core) 8-77

TAP-105

TAP-105 Ethernet alarms (Core-E, MPTACC, P8ETH, MSS-1 Shelf Core)

TAP-105Ethernet alarms (Core-E, MPTACC, P8ETH, MSS-1 Shelf Core)Purpose

This procedure describes how to identify and clear Loss Of Signal on Ethernet ports on the Core-E/MPTACC/P8ETH.

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.



STEP PROCEDURE


2 Review the output. See Table 105-A for information about the Ethernet alarms.

Loss of signal

3 Verify that the link partner is operating normally.

Table 105-A. Ethernet alarmsProbable cause Friendly name/entity Facility type SeeLoss of signal ETHInterface#100 Core-E Step 3

ETHInterfaceonCore#4 Core-EMAU/Slot#[1-2]/Port#[1-6] Core-EMAU/Slot#1/Port#[1-6] MSS/COREMAU/Slot#[3-8]/Port#[1-4] MPTACCMAU/Slot#[3-8]/Port#[1-8] P8ETHr01s1[1-6]b1/daughter#03 RPS SFP on MPT

ODU connected to Core-E, MSS/CORE

Bandwidth degrade for protection switch

ERP[1-2]#1-2] Core-E Step 10



Ethernet alarms (Core-E, MPTACC, P8ETH, MSS-1 Shelf Core)8-78

TAP-105




6 Verify the link partner cabling between the Core-E/MPTACC/P8ETH card or MSS-1 shelf Core and the link partner.





Bandwidth degrade for protection switch

10 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 troubleshoot accordingly.


13 Did the Bandwidth degrade for protection switch alarm clear?


14 Have all nodes in the Ethernet Ring been verified?

If yes, go to step 15.If no, repeat steps 10 to 13 for the other nodes in the Ethernet Ring.




License/software mismatch 8-79

TAP-106

TAP-106 License/software mismatch

TAP-106License/software mismatchPurpose

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, ODU300, or MSS-1 Shelf Core.

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 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/ODU300 indicates that software version on the MPT ODU/MPT-HL/ODU300 does not match the software version on the Core-E.



STEP PROCEDURE


2 Review the output. See Table 106-A for information about License/Software Mismatch alarms.

Table 106-A. License/software mismatch alarmsProbable cause Friendly name/entity Facility type SeeProvisioning mismatch r01s1/board#[1-2] Core-E Step 3

r01s1/board#1 MSS/CORE


License/software mismatch8-80

TAP-106

Provisioning mismatch

3 Replace the Core-E flash card with the correct flash card for the license. See DLP-104 to replace the Core-E flash card.


5 Did the Provisioning Mismatch alarm clear?






Step 6





Version mismatch r01s1/board#[1-2] Core-E Step 12r01/subrack#1[1-6] MPT ODU connected

to Core-E, MSS/CORE

Step 22





r01/subrack#[3-8] ODU300None of the above � � IXL-101

Table 106-A. License/software mismatch alarms (cont.)


License/software mismatch 8-81

TAP-106

7 Verify that the Firmware Download On Going is declared against the MPT ODU/MPT-HL.

8 Is the Firmware Download On Going declared against the MPT ODU/MPT-HL?


9 A Firmware Download On Going alarm indicates that the MSS/Core-E is downloading the correct software to the MPT ODU/MPT-HL. Wait at least 30 minutes for the downloading process to complete.


11 Did the Standby Version Mismatch alarm clear?


Version mismatch

12 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 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 to replace the Core-E card.



License/software mismatch8-82

TAP-106

21 Did the Version Mismatch alarm clear?


Version mismatch


23 Verify that a Firmware Download On Going alarm is declared against the MPT ODU/MPT-HL/ODU300.

24 Is the Firmware Download On Going declared against the MPT ODU/MPT-HL/ODU300?


25 A Firmware Download On Going alarm indicates the MSS/Core-E is downloading the correct software to the MPT ODU/MPT-HL/ODU300. Wait at least 30 minutes for the downloading process to complete.


27 Did the Version Mismatch, Standby Version Mismatch alarm clear?





Internal loss of communications 8-83

TAP-107

TAP-107 Internal loss of communications

TAP-107Internal loss of communicationsPurpose

This procedure describes how to identify and clear an Internal Communication Problem alarm on the MPT-HC/MPT-XP/9558HC (MPT ODU), MPT-HL, or ODU300.

General

A Dialog Failure alarm indicates that temporary loss of communication between the MSS shelf and MPT ODU/MPT-HL. A Dialog Failure alarm is declared until communications are reestablished or a time-out period expires.

After the time-out period is reached, a Dialog Failure alarm is cleared and an Internal Communication Problem alarm is declared.

The Dialog Failure time-out durations varies based on the system configuration. The time-out durations are:

• 1+0: 20 minutes

• 1+1 HSB: 5 minutes

• 1+1 FD: 20 minutes

An Internal Communication Problem alarm indicates that a loss of communications with the MPT ODU/MPT-HL/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.



STEP PROCEDURE


2 Review the output. See Table 107-A for information about internal communication problem alarms.


Internal loss of communications8-84

TAP-107

Dialog failure



4 Has the appropriate time-out period be reached?

If yes, go to step 5.If no, wait for the appropriate time-out period to expire before proceeding to step 5.


Table 107-A. Internal communication problem alarmsProbable cause Friendly name/entity Facility type SeeDialog failure r01/subrack#1[1-6] MPT ODU connected

to Core-E, MSS/CORE

Step 3


r01/subrack#[3-8][[5-8] MPT ODU connected to P8ETH



Internal communication problem


Step 88





r01/subrack#[3-8] ODU300None of the above � � IXL-101



TAP-107

6 Did the Dialog Failure alarm clear?


7 Is an Internal Communication Problem alarm declared?

If yes, go to step 88 to clear Internal Communication Problem.If no, go to step 173.

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 window per local practices and procedures.

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.






TAP-107

20 Reprovision the radio port per site documentation.





24 Is a Replaceable Unit Problem alarm declared against the MPT ODU/MPT-HL in the protection-pair?

If yes, see IXL-101 to clear the Replaceable Unit Problem.If no, go to step 25.

25 Verify that power is properly supplied to the MPT ODU/MPT-HL in alarm. Correct if required.

26 Was a power problem corrected?





29 Is the MPT ODU/MPT-HL 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 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.



TAP-107

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 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. Schedule appropriate maintenance window per local practices and procedures.

40 Reseat the RJ45/SFP at the Core-E/MPTACC/P8ETH/MSS-1 shelf Core that is associated with the MPT ODU/MPT-HL in alarm.

41 Reseat the SFP at the MPT-HL in alarm.




44 Which card type is declaring Dialog Failure?

If MPT ODU, go to step 45.If MPT-HL, 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?




TAP-107

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 maintenance window per local practices and procedures.

49 Power cycle the MPT ODU.

If powered using PFoE/QMA through the MPTACC or MSS-1 shelf Core, use the craft terminal to disable power, and then reprovision power.

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.

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.

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

53 Replace the MPT ODU in alarm. See DLP-115 to replace MPT ODU.




56 CAUTION: Possibility of service interruption. Physically removing an MPTACC/P8ETH/Core-E in an unprotected facility causes a loss of traffic on ALL facilities that are associated with the MPTACC being removed. Schedule appropriate maintenance window per local practices and procedures.



TAP-107

57 Reseat the MPTACC/P8ETH/Core-E card that is associated with the MPT ODU in alarm.





61 CAUTION: Possibility of service interruption. Physically replacing an MPTACC/P8ETH/Core-E in an unprotected facility causes a loss of traffic on ALL facilities that are associated with the MPTACC/P8ETH/Core-E being replaced. Schedule appropriate maintenance window per local practices and procedures.

62 Replace the MPTACC/P8ETH/Core-E that is associated with the MPT ODU in alarm. See DLP-114 to replace the MPTACC.





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 in an unprotected facility causes a loss of traffic on ALL facilities that are associated with the MPT-HL reseat. Schedule appropriate maintenance window per local practices and procedures.



TAP-107

71 Position the MPT-HL PA switch to the OFF �0� position.

72 Remove the fuse in the PDU that is suppling battery power to the MPT-HL.

73 Install the fuse in the PDU that is suppling battery power to the MPT-HL.






78 CAUTION: Possibility of service interruption. Replacing an MPT-HL in an unprotected facility causes a loss of traffic on ALL facilities that are associated with the MPT-HL being replaced. Schedule appropriate maintenance window per local practices and procedures.

79 Replace the card in alarm. See DLP-108 to replace the MPT-HL.





83 Is the MPT ODU/MPT-HL in a protected system?





87 Go to step 174.



TAP-107

Internal communication problem

88 Is traffic affected?


89 Has the Internal Communication Problem alarm been active for more than five minutes?

If yes, go to step 92.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.




99 Reprovision the radio port per site documentation.




TAP-107



102 Is the radio facility protected?


103 CAUTION: Possibility of service interruption. Forced switching traffic causes a disruption to traffic.

104 Is the MPT ODU/MPT-HL/ODU300 in alarm main or spare?





108 Go to step 112.




112 Which card is in alarm?

If ODU300, go to step 113.If MPT ODU, go to step 125.If MPT-HL, go to step 150.

113 CAUTION: Possibility of service interruption. Physically removing an MOD300 in an unprotected facility causes a loss of traffic on ALL facilities that are associated with the MOD300 being removed. Schedule appropriate maintenance window per local practices and procedures.

114 Physically reseat the MOD300 that is associated with the ODU300 in alarm. Do not remove the IF cable while reseating the MOD300 card.




TAP-107

116 Did Internal communication Problem alarm clear?


117 CAUTION: Possibility of service interruption. 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 appropriate maintenance window per local practices and procedures.

118 Replace the MOD300 that is associated with the ODU300. See DLP-107 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 to replace the ODU300.


124 Did the Internal communication Problem alarm clear?


125 Is MPT ODU in alarm supported by the Core-E/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?




TAP-107

127 Is the second radio channel error-free and alarm free?


128 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 maintenance window per local practices and procedures.


If powered through the MPTACC or MSS-1 shelf Core, use the craft terminal to disable power, and then reprovision power.

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.

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?









TAP-107

136 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 reseat. Schedule appropriate maintenance window per local practices and procedures.

137 Reseat the MPTACC card that is associated with the MPT ODU in alarm.





141 CAUTION: Possibility of service interruption. Physically replacing an MPTACC in an unprotected facility causes a loss of traffic on ALL facilities that are associated with the MPTACC being replaced. Schedule appropriate maintenance window per local practices and procedures.

142 Replace the MPTACC that is associated with MPT ODU in alarm. See DLP-114 to replace the MPTACC.












TAP-107

150 CAUTION: Possibility of service interruption. Unseating and reseating the communication link between the MPT-HL and the P8ETH, 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. Schedule appropriate maintenance window per local practices and procedures.

151 Unseat and reseat the communication link between the MPT-HL and P8ETH, Core-E, or MSS-1 Shelf.




154 CAUTION: Possibility of service interruption. Replacing the communication link between the MPT-HL and the P8ETH, 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. Schedule appropriate maintenance window per local practices and procedures.

155 Replace the communication link between the MPT-HL and P8ETH, Core-E, or MSS-1 Shelf.




158 CAUTION: Possibility of service interruption. reseating an MPT-HL in an unprotected facility causes a loss of traffic on ALL facilities that are associated with the MPT-HL reseat. Schedule appropriate maintenance window per local practices and procedures.

159 Position the MPT-HL PA switch to the OFF �0� position.

160 Remove the fuse in the PDU suppling battery power to the MPT-HL.

161 Install the fuse in the PDU suppling battery power to the MPT-HL.






TAP-107

164 CAUTION: Possibility of service interruption. Replacing an MPT-HL in an unprotected facility causes a loss of traffic on ALL facilities that are associated with the MPT-HL being replaced. Schedule appropriate maintenance window per local practices and procedures.

165 Replace the MPT-HL in alarm. See DLP-108 to replace the MPT-HL.








172 Go to step 174.





TAP-107


Threshold crossing alarms (MOD300, MPT-HC, MPT-HL, MPT-XP, 9558HC, P32E1DS1, 8-99

TAP-108

TAP-108 Threshold crossing alarms (MOD300, MPT-HC, MPT-HL, MPT-XP, 9558HC, P32E1DS1, MSS-1 shelf P32E1DS1)

TAP-108Threshold crossing alarms (MOD300, MPT-HC, MPT-HL, MPT-XP, 9558HC, P32E1DS1, MSS-1 shelf P32E1DS1) 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, MOD300, or P32E1DS1 cards or MSS-1 shelf DS1.

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

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/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/MOD300/P32E1DS1/DS1 on MSS-1 shelf.



STEP PROCEDURE



Threshold crossing alarms (MOD300, MPT-HC, MPT-HL, MPT-XP, 9558HC, P32E1DS1,8-100

TAP-108

2 Review the output. See Table 108-A for information about TCA alarms.

Table 108-A. Threshold crossing alarmsProbable cause Friendly name/entity Facility type SeeThreshold crossed Hop/Dir#1[1-6]/Slot#1/

Port#[1-6]/Ch#[0-1]-PM15minMPT ODU connected to Core-E

Step 3



Hop/Dir#1[1-6]/MSS/CORE/Port#[1-6]/Ch#[0-1]-PM1dayLink/Dir#1[1-6]-PM15minLink/Dir#1[1-6]-PM1dayHop/Dir#[3-8][1-4]/Slot#[3-8]/Port#[1-4]/Ch#[0-1]-PM15min


Hop/Dir#[3-8][1-4]/Slot#[3-8]/Port#[1-4]/Ch#[0-1]-PM1dayLink/Dir#[3-8][1-4]-PM15minLink/Dir#[3-8][1-4]-PM1dayHop/Dir#[3-8][5-8]/Slot#[3-8]/Port#[5-8]/Ch#1-PM15min


Hop/Dir#[3-8][5-8]/Slot#[3-8]/Port#[5-8]/Ch#1-PM1dayHop/Dir#[3-8][5-8]/Slot#[3-8]/Port#[5-8]/Ch#[0-1]-PM15min


Hop/Dir#[3-8][5-8]/Slot#[3-8]/Port#[5-8]/Ch#[0-1]-PM1dayLink/Dir#[3-8][5-8]-PM15minLink/Dir#[3-8][5-8]-PM1dayHop/Dir#1[5-6]/Slot#1/Port#[5-6]/Ch#1-PM15min


Hop/Dir#1[5-6]/Slot#1/Port#[5-6]/Ch#1-PM1dayHop/Dir#1[5-6]/MSS/CORE/Port#[5-6]/Ch#1-PM15min


Hop/Dir#1[5-6]/MSS/CORE/Port#[5-6]/Ch#1-PM1day



TAP-108

Threshold crossed continued

Hop/Dir#[3-8]/Ch#[0-1]-PM15min MOD300 Step 3Hop/Dir#[3-8]/Ch#[0-1]-PM1dayLink/Dir#[3-8]-PM15minLink/Dir#[3-8]-PM1dayDS1-in/Slot#[3-8]/Port#[1-32]-PM15min

DS1 on P32E1DS1


DS1 on MSS-1 shelf


Unavailable time Hop/Dir#1[1-6]/Slot#1/Port#[1-6]/Ch#[0-1]-PM15min

MPT ODU connected to Core-E, MSS/CORE

Step 12



Hop/Dir#1[1-6]/MSS/CORE/Port#[1-6]/Ch#[0-1]-PM1dayLink/Dir#1[1-6]-PM15minLink/Dir#1[1-6]-PM1dayHop/Dir#[3-8][1-4]/Slot#[3-8]/Port#[1-4]/Ch#[0-1]-PM15min


Hop/Dir#[3-8][1-4]/Slot#[3-8]/Port#[1-4]/Ch#[0-1]-PM1dayLink/Dir#[3-8][1-4]-PM15minLink/Dir#[3-8][1-4]-PM1day

Table 108-A. Threshold crossing alarms (cont.)Probable cause Friendly name/entity Facility type See



TAP-108

Unavailable time continued

Hop/Dir#[3-8][5-8]/Slot#[3-8]/Port#[5-8]/Ch#1-PM15min


Step 12

Hop/Dir#[3-8][5-8]/Slot#[3-8]/Port#[5-8]/Ch#1-PM1dayHop/Dir#[3-8][5-8]/Slot#[3-8]/Port#[5-8]/Ch#[0-1]-PM15min


Hop/Dir#[3-8][5-8]/Slot#[3-8]/Port#[5-8]/Ch#[0-1]-PM1dayLink/Dir#[3-8][5-8]-PM15minLink/Dir#[3-8][5-8]-PM1dayHop/Dir#1[5-6]/Slot#1/Port#[5-6]/Ch#1-PM15min


Hop/Dir#1[5-6]/Slot#1/Port#[5-6]/Ch#1-PM1dayHop/Dir#1[5-6]/MSS/CORE/Port#[5-6]/Ch#1-PM15min


Hop/Dir#1[5-6]/MSS/CORE/Port#[5-6]/Ch#1-PM1dayHop/Dir#[3-8]/Ch#[0-1]-PM15min MOD300Hop/Dir#[3-8]/Ch#[0-1]-PM1dayLink/Dir#[3-8]-PM15minLink/Dir#[3-8]-PM1dayDS1-in/Slot#[3-8]/Port#[1-32]-PM15min

DS1 on P32E1DS1


DS1 on MSS-1 shelf



Table 108-A. Threshold crossing alarms (cont.)Probable cause Friendly name/entity Facility type See



TAP-108

Threshold crossed

3 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?


Unavailable time

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




TAP-108

20 Did the Unavailable Time alarm clear?





Synchronization alarms (Core-E, MOD300, MPT-HC, MPT-HL, MPT-XP, P32E1DS1, 8-105

TAP-109

TAP-109 Synchronization alarms (Core-E, MOD300, MPT-HC, MPT-HL, MPT-XP, P32E1DS1, SDHACC, 9558HC)

TAP-109Synchronization alarms (Core-E, MOD300, MPT-HC, MPT-HL, MPT-XP, P32E1DS1, SDHACC, 9558HC)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, P32E1DS1, and SDHACC.

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



STEP PROCEDURE


2 Review the output. See Table 109-A for information about synchronization alarms.


Synchronization alarms (Core-E, MOD300, MPT-HC, MPT-HL, MPT-XP, P32E1DS1,8-106

TAP-109

Table 109-A. Sync alarmsProbable cause Friendly name/entity Equipment type SeeDegrade Sync-in/Port#1 Core-E Step 3

Radio/Dir#[3-8]/Ch#[0-1] MOD300Radio/Dir#1.[1-6]/Slot#1/Port#[1-6]/Ch#1














RadioLAG#[1-14] MPT ODU connected to P8ETH, MPT-HL

DS1-in/Slot#[3-8]/Port#[1-32] P32E1DS1EleSdh-in/slot#[3-8]/Port[1-2] OC-3OptSdh-in/slot#[3-8]/Port[1-2]


MAU/Slot#[1-2]/Port#[1-6] Core-E Step 29Radio/Dir#[3-8]/Ch#[0-1] MOD300RadioLAG#[1-14] MPT ODU, MPT-HLRadio/Dir#1.[1-6]/Slot#1/Port#[1-6]/Ch#[0-1]
















TAP-109

Degrade

3 What is the sync source?

If Sync-In, go to step 4.If Radio port, go to step 9.If DS1 or OC-3 port, go to step 14.

Sync-In

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

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

Sync-in/Port#1 Core-E Step 62Radio/Dir#[3-8]/Ch#[0-1] MOD300Radio/Dir#1.[1-6]/Slot#1/Port#[1-6]/Ch#1














RadioLAG#[1-14] MPT ODU, MPT-HLDS1-in/Slot#[3-8]/Port#[1-32] P32E1DS1EleSdh-in/slot#[3-8]/Port[1-2] OC-3OptSdh-in/slot#[3-8]/Port[1-2]


Table 109-A. Sync alarmsProbable cause Friendly name/entity Equipment type See



TAP-109


8 Did the Degrade Defect alarm clear?


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?





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.



TAP-109

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?

If Core-E, replace the Core-E. See DLP-103 to replace Core-E.If MOD300, replace the MOD300. See DLP-107 to replace MOD300.If MPT ODU replace the MPT ODU. See DLP-115 to replace MPT ODU.If MPT-HL, replace the MPT-HL. See DLP-108 to replace MPT-HL.If P32E1DS1, replace the P32E1DS1. See DLP-111 to replace P32E1DS1.If SDHACC, replace the SDHACC. See DLP-126 to replace SDHACC.






30 Verify no radio or Ethernet alarms are declared against the radio direction declaring Loss ESMC.



TAP-109

31 Are radio or Ethernet alarms declared against the radio direction or Ethernet port?

If yes, see IXL-101 to clear radio or Ethernet alarms declared against the radio direction or Ethernet port.If no, go to step 32.

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.

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?


Loss of signal

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




42 Verify sync source provisioning at both the sync source and the alarming card.






TAP-109

45 Is traffic affected?


46 Is Core-E in a protected system?


47 CAUTION: Possibility of service interruption. 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 to replace Core-E.






TAP-109

60 Is Core-E in a protected system?


61 Release Forced/Lockout EPS Switch using Craft Terminal.

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?

If yes, See TAP-109 Table 109-A and clear other Sync alarms before proceeding to step 65.If no, go to step 67.


66 Did the Synchronization Signal Fail alarm clear?


67 What is the sync source?

If Sync-in, go to step 68.If Radio port, go to step 73.If DS1 or OC-3 port, go to step 80.

Sync-in

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




TAP-109



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?

If yes, see IXL-101 to clear radio alarms declared against the radio direction.If no, go to step 76.

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?





DS1 or OC-3 port


81 Verify no LOS alarm exists on sync reference DS1 or OC-3 port. If LOS alarm exists, troubleshoot accordingly.

82 Did the an LOS alarm exist on sync reference DS1 or OC-3 port and was it cleared?





TAP-109



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?

If Core-E, replace the Core-E. See DLP-103 to replace the Core-E.If MOD300, replace the MOD300. See DLP-107 to replace the MOD300.If MPT ODU replace the MPT ODU. See DLP-115 to replace the MPT ODU.If MPT-HL, replace the MPT-HL. See DLP-108 to replace the MPT-HL.If P32E1DS1, replace the P32E1DS1. See DLP-111 to replace the P32E1DS1.If SDHACC, replace the SDHACC. See DLP-126 to replace SDHACC.






TAP-109




ATPC loop conditions (MOD300, MPT-HC, MPT-HL, MPT-XP, 9558HC) 8-117

TAP-110

TAP-110 ATPC loop conditions (MOD300, MPT-HC, MPT-HL, MPT-XP, 9558HC)

TAP-110ATPC loop conditions (MOD300, MPT-HC, MPT-HL, MPT-XP, 9558HC)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), and MPT-HL.

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.



STEP PROCEDURE

1 Using the Alarm Monitor, retrieve all alarm.

2 Review the output. See Table 110-A for information about ATPC Loop conditions.


ATPC loop conditions (MOD300, MPT-HC, MPT-HL, MPT-XP, 9558HC)8-118

TAP-110

ATPC loop problem

3 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?


Table 110-A. ATPC loop conditionsProbable cause Friendly name/entity Equipment type SeeATPC loop problem Radio/Dir#1.[1-6]/

Slot#1/Port#[1-6]/Ch#[0-1]MPT ODU connected to Core-E

Step 3













Radio/Dir#[3-8]/Ch#[0-1] MOD300Loop problem Radio/Dir#1.[1-6]/


Step 8
















TAP-110

5 Troubleshoot the RF path from the near end transmitter to the far end receiver.


7 Did the ATPC Loop Problem alarm clear?


Loop problem

8 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?




TAP-110

20 CAUTION: Possibility of service interruption. Replacing card in an unprotected facility causes a loss of traffic on ALL facilities that are associated with the card being replaced. Schedule appropriate maintenance window per local practices and procedures.

21 Replace the MPT ODU or MPT-HL in alarm at the near end.

Refer to DLP-115 to replace MPT ODU.Refer to DLP-108 to replace MPT-HL Transceiver.





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?




TAP-110






36 Perform a Forced EPS Switch at the far end transmitter using the Craft Terminal.

37 Perform a Forced HSB Switch at the far end transmitter using the Craft Terminal.

38 Perform a Forced Rx Radio Switch at the far end transmitter using the Craft Terminal.

39 Go to step 43.

40 Perform a Lockout EPS Switch at the far end transmitter using the Craft Terminal.

41 Perform a Lockout HSB Switch at the far end transmitter using the Craft Terminal.

42 Perform a Lockout Rx Radio Switch at the far end transmitter using the Craft Terminal.


44 Did the Loop Problem alarm clear?


45 CAUTION: Possibility of service interruption. Replacing card in an unprotected facility causes a loss of traffic on ALL facilities that are associated with the card being replaced. Schedule appropriate maintenance window per local practices and procedures.

46 Replace the MPT ODU or MPT-HL at the far end.

Refer to DLP-115 to replace MPT ODU.Refer to DLP-108 to replace MPT-HL Transceiver.



TAP-110





49 Release the Forced EPS Switch at the far end transmitter using the Craft Terminal.

50 Release the Forced HSB Switch at the far end transmitter using the Craft Terminal.

51 Release the Forced Rx Radio Switch at the far end transmitter using the Craft Terminal.

52 Go to step 56.

53 Release the Lockout EPS Switch at the far end transmitter using the Craft Terminal.

54 Release the Lockout HSB Switch at the far end transmitter using the Craft Terminal.

55 Release the Lockout Rx Radio Switch at the far end transmitter using the Craft Terminal.


57 Did the Loop Problem alarm return?





Cable LOS 8-123

TAP-111

TAP-111 Cable LOS

TAP-111Cable LOSPurpose

This procedure describes how to identify and clear radio alarms on the MOD300.

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



STEP PROCEDURE


2 Review the output. See Table 111-A for information about clear radio alarms.

Cable LOS

3 Inspect the indoor IF cable is properly terminated, securely connected, and the run is not damaged.

Table 111-A. Clear radio alarmsProbable cause Friendly name/entity Equipment type SeeCable LOS r01s1/board#[3-8] MOD300 Step 3DemXPIC LOS r01s1/b1[1-6]/daughter#04 MPT ODU connected

to Core-E, MSS/CORE

Step 45

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



Cable LOS8-124

TAP-111

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.





Cable LOS 8-125

TAP-111

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 per local practices and procedures.

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 local practices and procedures.

25 Replace the MOD300. See DLP-107 to replace MOD300.

26 CAUTION: Possibility of service interruption. Manually switching traffic causes a disruption to traffic.




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.



Cable LOS8-126

TAP-111





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.

DemXPIC LOS

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



Cable LOS 8-127

TAP-111

49 Did the DemXPIC LOS alarm clear?


50 Reseat the XPIC cable on the horizontal and vertical MPT ODU.




53 Replace the XPIC cable between the horizontal and vertical MPT ODU.




56 Reseat the XPIC module on horizontal MPT ODU. See DLP-122 to reseat the XPIC module.




59 Reseat the XPIC module on the vertical MPT ODU. See DLP-122 to reseat the XPIC module.




62 Replace the XPIC module on the horizontal MPT ODU. See DLP-122 to replace the XPIC module.



Cable LOS8-128

TAP-111



65 Replace the XPIC module on vertical MPT ODU. See DLP-122 to replace the XPIC module.




68 Replace the horizontal MPT ODU. See DLP-115 to replace the MPT ODU.




71 Replace the vertical MPT ODU. See DLP-115 to replace the MPT ODU.







Loss of alignment (MOD300, MPT-HC, MPT-HL, MPT-XP, 9558HC) 8-129

TAP-112

TAP-112 Loss of alignment (MOD300, MPT-HC, MPT-HL, MPT-XP, 9558HC)

TAP-112Loss of alignment (MOD300, MPT-HC, MPT-HL, MPT-XP, 9558HC)Purpose

This procedure describes how to identify and clear Loss Of Alignment alarm on the MOD300, MPT-HC/MPT-XP/9558HC (MPT ODU), and MPT-HL.

General

A Loss Of Alignment alarm indicates that a delay/loss of alignment between the main and protect RF paths is detected.



STEP PROCEDURE


2 Review the output. See Table 112-A for information about Loss of Alignment alarms.

Loss of alignment

3 Verify that the MPT ODU/MPT-HL/ODU300 in alarm status is Standby.

Table 112-A. Loss of alignment alarmsProbable cause Friendly name/entity Equipment type SeeLoss of alignment Hitless/Dir#[3-8].[1-4] MPT ODU connected

to MPTACCStep 3

Hitless/Dir#1.[1-6] MPT ODU connected to Core-E, MSS/CORE

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

Hitless/Dir#[3-8] MOD300None of the above � � IXL-101


Loss of alignment (MOD300, MPT-HC, MPT-HL, MPT-XP, 9558HC)8-130

TAP-112

4 Is the MPT ODU/MPT-HL/ODU300 in alarm status Standby?



6 Is the MPT ODU/MPT-HL/ODU300 in alarm main or spare?





10 Go to step 14.





If MPT ODU go to step 15.If MPT-HL, go to step 30.If MOD300, go to step 41.

MPT ODU

15 Remove power to the MPT ODU. If powered through the 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?




TAP-112

18 CAUTION: Possibility of service interruption. The following steps cause a loss of traffic on ALL facilities supported by the Core-E, MPTACC card or MSS-1 shelf, associated with the facility in alarm. Schedule appropriate maintenance window per local practices and procedures.

19 Reseat the Core-E, MPTACC 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?

If MPTACC, see DLP-114 to replace MPTACC card.If Core-E, see DLP-103 to replace Core-E card.If MSS-1 shelf MSS/CORE, see DLP-128 to replace MSS-1 shelf.









MPT-HL

30 Position the MPT-HL Transceiver PA switch to the OFF �0� position.



TAP-112

31 Remove the fuse in the PDU that supplies battery power to the MPT-HL transceiver.

32 Install the fuse in the PDU that supplies battery power to the MPT-HL transceiver.

33 Position the MPT-HL Transceiver PA switch to the ON �1� position.





37 Replace the MPT-HL in alarm. See DLP-108 to replace the MPT-HL.





MOD300

41 Physically reseat the MOD300 card in alarm.





45 Replace the MOD300 card in alarm. See DLP-107 to replace the MOD300.





TAP-112



49 Replace the ODU300 that is associated with MOD300 in alarm. See DLP-109 to replace the ODU300.







55 Go to step 57.





TAP-112


Loss of frame (MOD300, MPT-HC, MPT-HL, MPT-XP, 9558HC) 8-135

TAP-113

TAP-113 Loss of frame (MOD300, MPT-HC, MPT-HL, MPT-XP, 9558HC)

TAP-113Loss of frame (MOD300, MPT-HC, MPT-HL, MPT-XP, 9558HC)Purpose

This procedure describes how to identify and clear Loss of Frame radio alarms on the MOD300, MPT-HC/MPT-XP/9558HC (MPT ODU), and MPT-HL.

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.



STEP PROCEDURE


2 Review the output. See Table 113-A for information about Loss of Frame radio alarms.

Table 113-A. Loss of frame radio alarmsProbable cause Friendly name/entity Equipment type SeeLoss of frame Radio/Dir#1.[1-6]/


Step 3













Radio/Dir#[3-8]/Ch#[0-1] MOD300None of the above � � IXL-101


Loss of frame (MOD300, MPT-HC, MPT-HL, MPT-XP, 9558HC)8-136

TAP-113

Loss of frame

3 Verify that there are no weather-related problems.

4 Do weather-related problems exist?

If yes, wait for the weather to clear and recheck alarms. Go to step 140.If no, go to step 5.













Unprotected radio configuration





TAP-113


If MOD300, go to step 40.If MPT ODU, go to step 15.If MPT-HL, go to step 52.

MPT ODU

15 Is the MPT ODU in alarm supported by the Core-E or 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.







TAP-113

26 Replace the local MPTACC that is associated with the MPT ODU in alarm. See DLP-114 to replace the MPTACC.





30 Replace the far end MPTACC that is associated with the MPT ODU in alarm. See DLP-114 to replace the MPTACC.





34 Replace the local MPT ODU in alarm. See DLP-115 to replace the MPT ODU.




37 Replace the far end MPT ODU in alarm. See DLP-115 to replace the MPT ODU.




MOD300

40 Reseat the local MOD300 card.



TAP-113



42 Reseat the far end MOD300 card.



44 Replace the local MOD300. See DLP-107 to replace the MOD300.



46 Replace the far end MOD300. See DLP-107 to replace the MOD300.



48 Replace the local ODU300. See DLP-109 to replace the ODU300.



50 Replace the far end ODU300. See DLP-109 to replace the ODU300.



MPT-HL

52 Position the local MPT-HL Transceiver PA switch to the OFF �0� position.

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

54 Install fuse in PDU suppling battery power to local MPT-HL Transceiver.



TAP-113

55 Position the local MPT-HL Transceiver PA switch to the ON �1� position.



57 Position the far end MPT-HL Transceiver PA switch to the OFF �0� position.

58 Remove fuse in PDU suppling battery power to far end MPT-HL Transceiver.

59 Install fuse in PDU suppling battery power to far end MPT-HL Transceiver.

60 Position the far end MPT-HL Transceiver PA switch to the ON �1� position.



62 Replace the local MPT-HL. See DLP-108 to replace the MPT-HL Transceiver.



64 Replace the far end MPT-HL. See DLP-108 to replace the MPT-HL Transceiver.



Protected radio configuration

66 Determine the status of the MPT ODU/MPT-HL/MOD300 declaring the Loss Of Frame alarm.

If Active, go to step 67.If Standby, go to step 68.





TAP-113

68 Is the MPT ODU/MPT-HL/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/MOD300.

70 Perform a Forced Equipment Switch using the Craft Terminal on the local MPT ODU/MPT-HL/MOD300.

71 Perform a Forced HSB Switch using the Craft Terminal on the far end MPT ODU/MPT-HL/MOD300.

72 Perform a Forced Equipment Switch using the Craft Terminal on the far end MPT ODU/MPT-HL/MOD300.

73 Go to step 78.

74 Perform a Lockout Rx Radio Switch using the Craft Terminal on the local MPT ODU/MPT-HL/MOD300.

75 Perform a Lockout Equipment Switch using the Craft Terminal on the local MPT ODU/MPT-HL/MOD300.

76 Perform Lockout HSB Switch using the Craft Terminal on the far end MPT ODU/MPT-HL/MOD300.

77 Perform a Lockout Equipment Switch using the Craft Terminal on the far end MPT ODU/MPT-HL/MOD300.


If MOD300, go to step 79.If MPT ODU, go to step 92.If MPT-HL, go to step 116.

MOD300

79 Reseat the local MOD300 card that is declaring the Loss Of Frame alarm.



81 reseat far end MOD300 card.



TAP-113



83 Replace the local MOD300 that is declaring the Loss Of Frame alarm. See DLP-107 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 to replace the MOD300.



87 Replace the local ODU300 associated with the MOD300 that is declaring Loss Of Frame alarm. See DLP-109 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 to replace the ODU300.



MPT ODU

91 Is the MPT ODU in alarm supported by the Core-E or P8ETH card or MSS-1 Shelf MSS/Core?




TAP-113

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 to replace the MPTACC.





106 Replace the far end MPTACC that is associated with MPT ODU in alarm. See DLP-114 to replace the MPTACC.



TAP-113





110 Replace the local MPT ODU in alarm. See DLP-115 to replace the MPT ODU.




113 Replace the far end MPT ODU in alarm. See DLP-115 to replace the MPT ODU.




MPT-HL

116 Position the local MPT-HL 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 transceiver.

118 Install the fuse in the PDU that is suppling battery power to the local MPT-HL transceiver.

119 Position the local MPT-HL Transceiver PA switch to the ON �1� position.



121 Position the far end MPT-HL 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 transceiver.



TAP-113

123 Install the fuse in the PDU that is suppling battery power to the far end MPT-HL transceiver.

124 Position the far end MPT-HL Transceiver PA switch to the ON �1� position.



126 Replace the local MPT-HL. See DLP-108 to replace the MPT-HL Transceiver.



128 Replace the far end MPT-HL. See DLP-108 to replace the MPT-HL Transceiver.



130 Verify antenna is aligned.

131 Is the antenna aligned?

If yes, go to step 139.If no, align the antenna. See 9500 MPR-A Turn-Up manual (PN 3EM23955AM) Antenna Polarization Verification (DLP-105) Antenna Feedhorn Verification - XPD 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 MPT ODU/MPT-HL/MOD300.

136 Release the Forced/Lockout HSB Switch using the Craft Terminal on the far end MPT ODU/MPT-HL/MOD300.



TAP-113

137 Release the Forced/Lockout Equipment Switch using the Craft Terminal on the far end MPT ODU/MPT-HL/MOD300.

138 Go to step 140.




RPS path fail (MPT-HC, MPT-HL, MPT-XP, 9558HC) 8-147

TAP-114

TAP-114 RPS path fail (MPT-HC, MPT-HL, MPT-XP, 9558HC)

TAP-114RPS path fail (MPT-HC, MPT-HL, MPT-XP, 9558HC)Purpose

This procedure describes how to identify and clear an RPS Path Fail alarm on the MPT-HC/MPT-XP/9558HC (MPT ODU) and MPT-HL.

General

An RPS Path Fail alarm that is declared against the MPT-HL indicates that a failure is detected on the RPS coupler port between the MPT-HL 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.



STEP PROCEDURE


2 Review the output. See Table 114-A for RPS Path Fail alarms.

RPS path fail

3 Using the Craft Terminal, determine which MPT ODU/MPT-HL status is Standby.

Table 114-A. RPS path fail alarmsProbable cause Friendly name/entity Equipment type SeeRPS path fail RadioProt/Dir#[3-8][1-4] MPT ODU connected

to MPTACCStep 3

RadioProt/Dir#1[1-6] MPT ODU connected to Core-E, MSS/CORE

RadioProt/Dir#[3-8][5-8] MPT-HL connected to P8ETH



RPS path fail (MPT-HC, MPT-HL, MPT-XP, 9558HC)8-148

TAP-114



MPT ODU

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


MPT-HL

13 Is the MPT-HL card in alarm main or spare?





17 Go to step 21.




TAP-114



21 On the MPT-HL 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 with a status of Standby.

23 Install the fuse in the PDU that is suppling battery power to MPT-HL with a status of Standby.

24 On the MPT-HL with status of Standby, position the PA switch to the ON �1� position.





28 Replace the MPT-HL with status of Standby. See DLP-108 to replace MPT-HL.






33 Is the MPT-HL card in alarm main or spare?







TAP-114

37 Go to step 41.




41 On the MPT-HL 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 with a status of Standby.

43 Install the use in the PDU that is suppling battery power to the MPT-HL with a status of Standby.

44 On the MPT-HL with status of Standby, position the PA switch to the ON �1� position.





48 Replace MPT-HL with status of Standby. See DLP-108 to replace the MPT-HL.











TAP-114

56 Go to step 58.





TAP-114


Rx fail (MOD300) 8-153

TAP-115

TAP-115 Rx fail (MOD300)

TAP-115Rx fail (MOD300)Purpose

This procedure describes how to identify and clear Rx Fail alarms on MOD300.

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.



STEP PROCEDURE


2 Review the output. See Table 115-A for information about Rx Fail alarms.

Rx fail

3 Verify there are no weather-related problems existing.

4 Do weather-related problems exist?

If yes, wait for weather to clear and recheck alarms. Go to step 72.If no, go to step 5.




Table 115-A. Rx fail alarmsProbable cause Friendly name/entity Equipment type SeeRx fail Radio/Dir#[3-8]/Ch#[0-1] MOD300 Step 3None of the above � � IXL-101


Rx fail (MOD300)8-154

TAP-115


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.



TAP-115

23 CAUTION: Possibility of service interruption. Reseat 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 per local practices and procedures.

24 Reseat the MOD300 card in alarm. Physically remove the card and reinsert.







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 unprotected radio hop causes a loss of traffic on ALL facilities that are associated with the MOD300 reseat. Schedule appropriate maintenance window per local practices and procedures.

38 Reseat the far end MOD300 card associated with the card in alarm. Physically remove the card and reinsert.



TAP-115





42 Replace the near end MOD300. See DLP-107 to replace the MOD300.





46 Replace the far end MOD300. See DLP-107 to replace the MOD300.




49 Replace the near end ODU300. See DLP-109 to replace the ODU300.


51 Did Rx Fail alarm clear?


52 Replace the far end ODU300. See DLP-109 to replace the ODU300.




TAP-115

54 Did Loss Of Frame alarm clear?


55 Verify antenna is aligned.

56 Is antenna aligned?

If yes, go to step 71.If no, align the antenna. See the 9500 MPR-A Turn-Up Manual (PN 3EM23955AM) Antenna Polarization Verification (DLP-105) Antenna Feedhorn Verification - XPD 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.






TAP-115

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.




Housekeeping alarms 8-159

TAP-116

TAP-116 Housekeeping alarms

TAP-116Housekeeping alarmsPurpose

This procedure describes how to identify and clear Housekeeping alarms (External Point Input) on AUX card.

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.



STEP PROCEDURE


2 Review the output. See Table 116-A for information about Housekeeping alarms.

Housekeeping alarm

3 Verify the equipment that is associated with housekeeping alarm input which is in the alarm state.

Table 116-A. Housekeeping alarmsOperation Name Equipment type SeeHousekeeping alarm ExtPt/Input#[1-6] AUX Step 3

ExtPt/Input#[11-14] FanExtPt/Input#[11-14] MSS-1



Housekeeping alarms8-160

TAP-116

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.







LAG alarms (Core-E, MPT-HC, MPT-HL, MPT-XP, ODU300, 9558HC, MSS-1 shelf Core) 8-161

TAP-117

TAP-117 LAG alarms (Core-E, MPT-HC, MPT-HL, MPT-XP, ODU300, 9558HC, MSS-1 shelf Core)

TAP-117LAG alarms (Core-E, MPT-HC, MPT-HL, MPT-XP, ODU300, 9558HC, MSS-1 shelf Core)Purpose

This procedure describes how to identify and clear LAG alarms on the Core-E, MPT-HC/MPT-XP/9558HC (MPT ODU), MPT-HL, ODU300, and MSS-1 shelf Core.

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.



STEP PROCEDURE

1 Using the Alarm Monitor, retrieve ALL alarms.

2 Review the output. See Table 117-A for information about LAG alarms.

Degrade


Table 117-A. LAG alarmsProbable cause Friendly name/entity Equipment type SeeDegrade EthLAG#[1-14] Core-E, MSS/CORE Step 3

RadioLAG#[1-14] MPT ODU, MPT-HL, ODU300

Loss of signal EthLAG#[1-14] Core-E, MSS/CORE Step 8RadioLAG#[1-14] MPT ODU, MPT-HL,

ODU300None of the above � � IXL-101


LAG alarms (Core-E, MPT-HC, MPT-HL, MPT-XP, ODU300, 9558HC, MSS-1 shelf Core)8-162

TAP-117

4 Identify the alarms that are declared against members of the LAG group. If alarms exists, see IXL-101 and troubleshoot accordingly.

5 Did the alarms exist on the LAG group members and were they cleared?



7 Did the Degrade alarm clear?


Loss of signal


9 Identify the alarms that are declared against members of the LAG group. If alarms exists, see IXL-101 and troubleshoot accordingly.

10 Did the alarms exist on the LAG members and were they cleared?



12 Did the Loss of Signal alarm clear?





Ethernet connectivity fault management alarms 8-163

TAP-118

TAP-118 Ethernet connectivity fault management alarms

TAP-118Ethernet connectivity fault management alarmsPurpose

This procedure describes how to identify and clear Ethernet Connectivity Fault Management (ECFM) alarms.

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.


See the 9500 MPR-A Operation and Administration (PN 3EM23954AM) WT CLI Tool Reference Guide for information about how to execute the commands that are described in this procedure.

STEP PROCEDURE


2 Review the output. See Table 118-A for information about ECFM alarms.


Ethernet connectivity fault management alarms8-164

TAP-118

Eth OAM loss of continuity

3 Locate the failure in the network.

If MIPs were created on the MEP, use the Link Trace command using WT CLI Tool. See WT CLI Tool Reference Guide for more information.

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 Retrieve MA ID for both ends of the MEP using WT CLI Tool. See WT CLI Tool Reference Guide for more information.

8 Determine which MA ID value(s) are incorrect.

Table 118-A. ECFM alarmsProbable cause Friendly name/entity Equipment type SeeEth OAM loss of continuity


Core-E, MSS/CORE Step 3


















Ethernet connectivity fault management alarms 8-165

TAP-118

9 Reprovision the MA ID value(s) according to the results of step 8.


11 Did the Eth OAM MisMerge Condition alarm clear?



12 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 Retrieve the MD Level for both ends of the MEP using WT CLI Tool. See 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 Retrieve MEPID for both ends of the MEP using WT CLI Tool. See WT CLI Tool Reference Guide for more information.


Ethernet connectivity fault management alarms8-166

TAP-118

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 Retrieve the MEP Transmission Interval for both ends using WT CLI Tool. See 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?





Clock failure (MPT-HC, MPT-HL, MPT-XP, 9558HC) 8-167

TAP-119

TAP-119 Clock failure (MPT-HC, MPT-HL, MPT-XP, 9558HC)

TAP-119Clock failure (MPT-HC, MPT-HL, MPT-XP, 9558HC)Purpose

This procedure describes how to identify and clear Clock Failure alarm on the MPT-HC/MPT-XP/9558HC (MPT ODU) and MPT-HL.

General

A Clock Failure alarm indicates that the MPT ODU or MPT-HL is unable to lock the air Tx symbol rate to the NE clock.



STEP PROCEDURE


2 Review the output. See Table 119-A for information about Clock Failure alarms.

Table 119-A. Clock failure alarmProbable cause Friendly name/entity Equipment type SeeClock failure Radio/Dir#1.[1-6]/


Step 3















Clock failure (MPT-HC, MPT-HL, MPT-XP, 9558HC)8-168

TAP-119

Clock failure



Unprotected Radio Configuration

4 CAUTION: Possibility of service interruption. Power Cycling an in-service MPT ODU or MPT-HL in an unprotected link causes a loss of traffic on ALL facilities that are associated with the MPT ODU or MPT-HL in alarm. Schedule appropriate maintenance window per local practices and procedures.

5 CAUTION: Possibility of service interruption. Replacing the MPT ODU or MPT-HL in an unprotected link causes a loss of traffic on ALL facilities that are associated with the MPT ODU or MPT-HL in alarm. Schedule appropriate maintenance window per local practices and procedures.



7 Verify that it is appropriate to proceed with clear Clock Failure procedure or appropriate maintenance window is scheduled per local practices and procedures.

8 Is it appropriate to proceed with clear Clock Failure procedure?




10 Is the MPT ODU in alarm associated with the Core-E/P8ETH card or MSS-1 shelf Core?


MPT ODU connected to Core-E/P8ETH card or MSS-1 shelf Core

11 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 local practices and procedures.



TAP-119


If MPT ODU is powered through 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.

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.


13 Dialog Failure is declared against the MPT ODU. Wait for Dialog Failure condition to clear before proceeding.


15 Did the Clock Failure alarm clear?


16 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 practices and procedures.





MPT ODU connected to MPTACC card

20 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 local practices and procedures.



TAP-119

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





25 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 practices and procedures.





MPT-HL

29 CAUTION: Possibility of service interruption. Power Cycling the MPT-HL in an unprotected link causes a loss of traffic on ALL facilities that are associated with the MPT-HL in alarm. Schedule appropriate maintenance window per local practices and procedures.


31 Remove the fuse in the PDU that is suppling battery power to the MPT-HL transceiver.

32 Install the fuse in PDU that is suppling battery power to the MPT-HL transceiver.





TAP-119



36 CAUTION: Possibility of service interruption. Replacing the MPT-HL in an unprotected link causes a loss of traffic on ALL facilities that are associated with the MPT-HL in alarm. Schedule appropriate maintenance window per local practices and procedures.

37 Replace the local MPT-HL. See DLP-108 to replace the MPT-HL transceiver.



Protected radio configuration


40 Determine the status of MPT ODU/MPT-HL declaring Clock Failure alarm.

If Active, go to step 41.If Standby, go to step 42.




43 Is the MPT ODU/MPT-HL declaring Clock Failure alarm the main or spare?



45 Perform a Forced Equipment Switch using the Craft Terminal.


47 Go to step 51.



TAP-119


49 Perform a Lockout Equipment Switch using the Craft Terminal.




MPT ODU


If MPT ODU is powered through 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/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.

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.






56 Replace the MPT ODU in alarm. See DLP-115 to replace the MPT ODU.




TAP-119



MPT-HL


60 Remove the fuse in the PDU that is suppling battery power to the MPT-HL transceiver.

61 Install the fuse in the PDU that is suppling battery power to the MPT-HL transceiver.





65 Replace the MPT-HL. See DLP-108 to replace MPT-HL Transceiver.




68 CAUTION: Possibility of service interruption. Releasing Forced/Lockout EPS/HSB/RX Radio switch causes a disruption to traffic.


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


72 Go to step 74.





TAP-119


Duplicate Address Detected alarms 8-175

TAP-120

TAP-120 Duplicate Address Detected alarms

TAP-120Duplicate Address Detected alarmsPurpose

This procedure describes how to identify and clear Duplicate Address Detected alarms.

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.



STEP PROCEDURE


2 Review the output. See Table 120-A for information about Duplicate address detected alarms.


Duplicate Address Detected alarms8-176

TAP-120


TMN Ethernet MGMT Port

3 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?

If no, go to step 6.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.

Table 120-A. Duplicate address detected alarmsProbable cause Friendly name/entity Equipment type SeeDuplicate address detected

TMNEthernet/MngtPort Core-E/TMN MGMT Port

Step 3

TMNEthernet/Port#4 Core-E/TMN Port#4 Step 25TMNInBand#[1-2] Core-E/TMN In-Band

Port [1-2]Step 47


PPP-IP/RF#[3-8] MOD300 Step 63PPP-IP/RF#1[1-6] MPT ODU connected

to Core-E, MSS/CORE





PPP-IP/RF/LAG#[1-14] MPT ODU, MPT-HL, ODU




TAP-120

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 engineering documentation.

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.




TAP-120



Port #4 TMN Ethernet

25 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 according to site engineering documentation.

27 Is the provisioned IPv6 Port #4 TMN Ethernet value correct?


28 CAUTION: Possibility of service interruption. If access to the NE with the incorrect IPv6 address is through the Port #4 TMN port in alarm, communication with the NE will be lost when the address is changed. The TMN address must be changed locally or a different TMN interface must be established to communicate with the NE.


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.




TAP-120



38 Verify the desired IPv6 Port #4 TMN Ethernet Configuration value for the far end NE according to site engineering documentation.


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.




TMN In-Band Port #1/2

47 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 engineering documentation.

49 Is the provisioned IPv6 TMN In-Band Port #1/2 value correct?


50 CAUTION: Possibility of service interruption. If access to the NE with the incorrect IPv6 address is through the TMN In-Band Port #1/2 in alarm, communication with the NE will be lost when the address is changed. The TMN In-Band Port #1/2 address must be changed locally or a different TMN interface must be established to communicate with the NE.



TAP-120


52 Reprovision IPv6 TMN In-Band Port #1/2 value for the NE according to site engineering documentation.

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.





PPP IP/RF Port

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



TAP-120

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 engineering documentation.

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.




TAP-120



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.







Mechanical card removal and installation 9-1

DLP-100

Detailed Level Procedures (DLPs)DLP-100 Mechanical card removal and installation

DLP-100Mechanical card removal and installationPurpose

This procedure describes how to remove and install cards mechanically in the 9500 MPR-A.

General

This procedure addresses only mechanical card removal and installation.

See the 9500 MPR-A Product Information (PN 3EM23952AM) to determine card location and type.


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

2 CAUTION: Possibility of service interruption. Removing an in-service card in an 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.

4 Which procedure to perform?

If card removal, go to step 5.If card installation, go to step 9.

Card removal

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


Mechanical card removal and installation9-2

DLP-100

Card installation

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



MPT-HL transceiver air filter replacement 9-3

DLP-101

DLP-101 MPT-HL transceiver air filter replacement

DLP-101MPT-HL transceiver air filter replacementPurpose

This procedure describes how to check and replace a dust filter on the MPT-HL Transceiver.

General


STEP 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 Transceiver.

3 Remove the filter from the MPT-HL Transceiver.

4 Is the dust filter dirty?

If the dust filter is dirty, go to step 5.If the dust filter is clean, go to step 6.

5 Replace filter with a clean filter.

6 Install the filter and cover on to the MPT-HL transceiver.

7 Tighten the screws securing the dust filter and cover to the MPT-HL transceiver.



MPT-HL transceiver air filter replacement9-4

DLP-101


SFP replacement 9-5

DLP-102

DLP-102 SFP replacement

DLP-102SFP replacementPurpose

This procedure describes how to replace an SFP on a Core-E, MPT-HC/MPT-XP/9558HC (MPT ODU), MPT-HL, P8ETH, SDHACC cards or MSS-1 shelf.

General



STEP PROCEDURE

1 WARNING: Possibility of equipment damage. Modules contain static-sensitive devices. These devices can be damaged by static discharge. See the introduction for special handling instructions.

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?



6 Is the SFP port to be replaced the main or spare?



8 Go to step 11.


SFP replacement9-6

DLP-102


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 being replaced. Schedule appropriate maintenance window per local practices 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.

If there are alarms, see IXL-101.If there are no alarms, go to step 18.

18 Ensure that traffic is running.

If traffic is running, go to step 19.If traffic is not running, go to step 23.

19 Is equipment protected?




22 Go to step 24.




Core switching module (Core-E) replacement 9-7

DLP-103

DLP-103 Core switching module (Core-E) replacement

DLP-103Core switching module (Core-E) replacementPurpose

This procedure describes how to replace a Core Switching Module (Core-E) in an MSS-4/MSS-8 shelf.

Perquisites

Although this procedure is typically used to replace a failed (inactive) component, always verify the component state before removal.

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.

All MSS-4/MSS-8 shelf plug-ins can be removed and installed with power applied.



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


Core switching module (Core-E) replacement9-8

DLP-103

3 CAUTION: Possibility of service interruption. Removing an in-service card in an unprotected link causes loss of traffic. Removing an Active card in a protected 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. 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.

7 WARNING: Possibility of equipment damage. Circuit packs contain static-sensitive devices. These devices can be damaged by static discharge. See the introduction for special handling instructions.

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

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


11 Is the Core-E that is to be replaced in a protected system?




DLP-103

Protected Core-E replacement procedures

12 Is the power still applied to the MSS-4/MSS-8 shelf where the Core-E is to be replaced is equipped?


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

13 Verify the status of the other Core-E card (the Core-E card not being replaced) is normal and communicates properly.

14 Is the status of the other Core-E card normal and communicates properly?


15 Is the Core-E to be replaced the main or spare?


16 CAUTION: Possibility of service interruption. Forced EPS switch may cause a hit to traffic.

17 On the Protection Schemes tab, perform a Forced EPS Switch Main Core-E.

18 Go to step 20.

19 On the Protection Schemes tab, perform a Lockout of Spare Core-E.

20 Verify that the Core-E to be replaced status is Standby.

21 Remove the Core-E to be replaced. See DLP-100 for information about how to remove the card.

22 Remove the flash card from the Core-E card removed in step 21 and install into the replacement Core-E card.


24 Install the replacement Core-E into shelf. See DLP-100 for information about how to install the card.




DLP-103

26 Verify the communication with the replacement Core-E using the Craft Terminal.

27 Verify the replacement Core-E status using the Craft Terminal.

28 Does the replacement Core-E communicate properly and is the status is normal?


29 Is replaced Core-E the main or spare?


30 CAUTION: Possibility of service interruption. Releasing Forced EPS switch may cause a disruption to traffic.

31 On the Protection Schemes tab, release the Forced Switch Main Core-E.

32 Go to step 67.

33 On the Protection Schemes tab, release Lockout of Spare Core-E.

34 Go to step 67.

Shelf power has been turned off


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


38 Turn on shelf power and wait for the installed Core-E status LED to turn steady green.






DLP-103



44 Does replacement Core-E communicate properly and is the status is normal?


Unprotected Core-E replacement procedure

45 Is power still applied to MSS-4/MSS-8 shelf where the Core-E to be replaced is equipped?


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

46 CAUTION: Possibility of service interruption. Removing an in-service card in an unprotected system causes loss of traffic.

47 Remove Core-E to be replaced. See DLP-100 for information about how to remove the card.

48 CAUTION: Possibility of service interruption. Do not swap the main Core-E flash card with a flash card from a different Core-E card.




52 Wait for the status LED to turn steady green.



55 Does the replacement Core-E communicate properly and is the status is normal?




DLP-103



57 CAUTION: Possibility of service interruption. Do not swap the main Core-E flash card with the a flash card from a different Core-E card.




61 Turn on the shelf power.

62 Wait for the replaced Core-E status LED to turn steady green.



65 Does the replacement Core-E communicate properly and is the status normal?





Core switching module (Core-E) flash card replacement 9-13

DLP-104

DLP-104 Core switching module (Core-E) flash card replacement

DLP-104Core switching module (Core-E) flash card replacementPurpose

This procedure describes how to replace a Flash Card located on the Core Switching Module (Core-E).

Prerequisites

Although this procedure is typically used to replace a failed (inactive) component, always verify component state before removal.

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.

Replacement Flash Card must be pre-loaded with the MAC Address and the RMU Serial Number associated with the NE.

Record the MAC Address and the RMU Serial Number using the Craft Terminal. Use this information to obtain a replacement Flash Card.

• MAC Address (located on the Systems Setting screen and in the configuration file, see Bridge Address)

• RMU Serial number (located on the SW License screen)

NOTE: If the MAC Address and RMU Serial Number information is not accessible using the Craft Terminal, it is also located on the label adhered to the flash card.

Verify that the RMU Serial Number loaded on the replacement flash card meets the following compatibility rules:

• Main flash card (Core-E slot 1) and spare flash card (Core-E slot 2) must be loaded with the same RMU Serial number.

• License capacity must be the same across a hop

• MAC Address of the replacement Flash Card must match the MAC Address of the Flash Card to be replaced

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.


Core switching module (Core-E) flash card replacement9-14

DLP-104



STEP PROCEDURE

1 DANGER: Possibility of personal injury. Circuit packs can be installed or 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 unprotected link causes loss of traffic. Removing an Active card in a protected 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 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.


8 CAUTION: Possibility of service interruption. Replacing the Flash Card with one which is not correctly programmed with the correct MAC Address and RMU serial number 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.



DLP-104





13 Verify that the replacement Flash Card and the Flash Card to be replaced are loaded with the correct MAC Address and RMU Serial number:

� MAC Address (located on the Systems Setting screen and in the configuration file, see Bridge Address)

� RMU Serial number (located on the SW License screen)

NOTE: If this information is not available using the Craft Terminal, it is also located on the label adhered to the flash card itself.

14 Does the MAC Address and RMU Serial numbers match?


15 Record the MAC Address and RMU Serial numbers. 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 MAC Address and RMU Serial number 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 MAC Address and RMU Serial number.

c. Perform this procedure in its entirety after an appropriate replacement Flash Card is available.



DLP-104

17 Is the flash card on the Core-E to be replaced in a protected system?


Flash card replacement on protected Core-E configuration

18 Is the power still applied to MSS-4/8 shelf where flash card on the Core-E to be replaced is equipped?


Shelf power still applied to MSS-4/8 shelf

19 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?

If Main, go to step 22.If Spare, go to step 25.

22 CAUTION: Possibility of service interruption. 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 for information about how to remove the card.

28 Remove the flash card from the Core-E.




DLP-104

30 Install the replacement flash card onto the Core-E.


32 Install the Core-E into shelf. See DLP-100 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 77.

41 On the Protection Schemes tab, release Lockout EPS of Spare Core-E.

42 Go to step 77.


43 Remove the Core-E equipped with flash card to be replaced. See DLP-100 for information about how to remove the card.


45 CAUTION: Possibility of service interruption. Do not swap the main Core-E flash card with the protect Core-E flash card. This will result in a system that will not properly boot-up.



DLP-104

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 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?


Unprotected Core-E replacement procedure

54 Is power still applied to MSS-4/8 shelf where flash card on Core-E to be replaced is equipped?


Shelf power still applied to MSS-8 shelf

55 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 for detailed steps to remove card.


58 CAUTION: Possibility of service interruption. Do not swap the main Core-E flash card with the protect Core-E flash card. This will result in a system that will not properly boot-up.

59 Install replacement flash card onto the Core-E.



DLP-104

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

61 Install Core-E into shelf. See DLP-100 for information about how to remove the card.


63 Verify communication with the Core-E with replacement flash card using the Craft Terminal.


65 Does Core-E with replacement flash card communicate properly and status normal?



66 Remove Core-E equipped with flash card to be replaced. See DLP-100 for information about how to remove the card.



69 Install the replacement flash card onto the Core-E.


71 Install the Core-E into shelf. See DLP-100 for information about how to remove the card.

72 Turn on the shelf power and wait for the status LED to turn steady green.

73 Verify the communication with the Core-E with replacement flash card using the Craft Terminal.




DLP-104

75 Does the Core-E with replacement flash card communicate properly and status normal?





Ethernet access switch (P8ETH) replacement 9-21

DLP-105

DLP-105 Ethernet access switch (P8ETH) replacement

DLP-105Ethernet access switch (P8ETH) replacementPurpose

This procedure describes how to replace an Ethernet Access Switch (P8ETH) circuit pack.

Prerequisites


General

In this procedure, the main P8ETH is resident in slots 3, 5, or 7. The spare P8ETH is resident in slots 4, 6, or 8 if equipped.




STEP 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 integrity and cooling air from the fan.


4 CAUTION: Possibility of service interruption. Only MPT-HL transceiver Ethernet traffic may be protected within the 9500 MPR-A. 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 P8ETH.


Ethernet access switch (P8ETH) replacement9-22

DLP-105

5 CAUTION: Possibility of service interruption. All MPT ODU traffic is unprotected within the 9500 MPR-A. All Ethernet traffic supported by an MPT ODU is lost after a failure or removal of the P8ETH.

6 CAUTION: Possibility of service interruption. In protected MPT-HL transceiver Ethernet configurations, MPT-HL transceiver Ethernet traffic switching is controlled by the 9500 MPR-A. Working and protect MPT-HL transceiver Ethernet signals are provisioned on a per channel basis. If the P8ETH card in slot 3, 5, or 7 fails, working MPT-HL transceiver Ethernet traffic switches to the protect P8ETH SFP port in slot 4, 6, or 8. If the P8ETH card in slot 4, 6, or 8 fails, working MPT-HL transceiver Ethernet traffic switches to the protect P8ETH SFP port in slot 3, 5, or 7.

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

8 CAUTION: Possibility of service interruption. In protected P8ETH configurations configured with 1+1 revertive operation, inserting the main P8ETH card, may cause a disruption to the protected traffic. To prevent an impact to protect traffic, always perform a Forced EPS, HSB, and RX Radio to spare before inserting the main P8ETH card.





13 Is the P8ETH to be replaced in a protected system?




DLP-105

Protected P8ETH replacement procedures

14 CAUTION: Possibility of service interruption. Only MPT-HL transceiver Ethernet traffic is protected within the 9500 MPR-A. All other P8ETH 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 will be lost upon a failure or removal of the P8ETH.


16 What is the role of P8ETH card being replaced the main or spare?


17 CAUTION: Possibility of service interruption. Forced EPS switching traffic will cause a hit to traffic.


19 Perform a Forced EPS Switch Main, MPT-HL transceiver port to Spare MPT-HL transceiver port.

20 Perform a Forced HSB Switch Main, MPT-HL transceiver port to Spare MPT-HL transceiver port.

21 Perform a Forced RX Radio Switch Main, MPT-HL transceiver port to Spare MPT-HL transceiver port.

22 Repeat steps 19 to 21 until all of the MPT-HL Transceiver ports are Forced Switch to Spare, then go to step 27.

23 Perform a Lockout EPS of Spare MPT-HL transceiver port.

24 Perform a Lockout HSB of Spare MPT-HL transceiver port.

25 Perform a Lockout Rx Radio of Spare MPT-HL transceiver port.

26 Repeat steps 23 to 25 until all MPT-HL Transceiver ports are Lockout of Spare, then go to step 27.



DLP-105

27 Verify that all MPT-HL transceiver ports status is Standby.

28 Verify that all cable connections to the P8ETH card to be replaced are properly labeled.

29 Disconnect all cables that are connected to the front of the P8ETH.

30 Remove P8ETH to be replaced. See DLP-100 for information about how to remove card.

31 Remove the SFPs from the P8ETH.

32 Install the SFPs into the replacement P8ETH.



35 Install the replacement P8ETH into the shelf. See DLP-100 for information about how to install the card.


37 Connect all cables to the front of the P8ETH that were disconnected in step 29.

38 Verify the communication with the replacement P8ETH using the Craft Terminal.

39 Verify that the status is normal for the replacement P8ETH.

40 Verify that the Links are up for all Ethernet ports that are associated with the replacement P8ETH.

41 Does the replacement P8ETH communicate properly? Is the status normal? Are all Ethernet port Links up?


42 Verify the replacement P8ETH alarms and capable of carrying Ethernet traffic using the Alarm Monitor and Craft Terminal.



DLP-105

43 Is the replacement P8ETH status normal and is it capable of carrying Ethernet traffic?


44 Is the replaced P8ETH �Main� or �Spare�?

If Main, go to step 45.If Spare, go to step 49.

45 Release the Forced EPS Switch Main, MPT-HL transceiver port to Spare MPT-HL transceiver port.

46 Release the Forced HSB Switch Main, MPT-HL transceiver port to Spare MPT-HL transceiver port.

47 Release the Forced Rx Radio Switch Main, MPT-HL transceiver port to Spare MPT-HL transceiver port.

48 Repeat steps 45 to 47 until all MPT-HL Transceiver ports are released Forced Switch Main, then go to step 72.

49 Release the Lockout EPS Spare MPT-HL transceiver port.

50 Release the Lockout HSB Spare MPT-HL transceiver port.

51 Release the Lockout Rx Radio Spare MPT-HL transceiver port.

52 Repeat steps 49 to 51 until all MPT-HL Transceiver ports are released Lockout of Spare, then go to step 72.

Unprotected P8ETH replacement procedure

53 CAUTION: Possibility of service interruption. In unprotected P8ETH configurations, ALL Ethernet traffic is lost upon removal of the SFP connection to the P8ETH.

54 CAUTION: Possibility of service interruption. All other P8ETH 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.


56 Verify that all cable connections to the P8ETH card to be replaced are properly labeled.



DLP-105

57 Disconnect the Ethernet cables, one at a time.

58 Remove the P8ETH to be replaced. See DLP-100 for information about how to remove card.

59 Remove the SFPs from P8ETH to be replaced.

60 Install the SFPs into the replacement P8ETH.


62 Install the replacement P8ETH into the shelf. See DLP-100 for information about how to install the card.


64 Connect all cables to the front of the P8ETH that you disconnected in step 57.

65 Verify the communication with the replacement P8ETH using the Craft Terminal.

66 Verify the status is normal for the replacement P8ETH.

67 Verify the Link is up for all Ethernet ports associated with the replacement P8ETH.

68 Does the replacement P8ETH communicate properly? Is the status normal? Are all Ethernet port Links up?


69 Verify the replacement P8ETH alarms and capable of carrying Ethernet traffic using the Alarm Monitor and Craft Terminal.

70 Is the replacement P8ETH status normal, and capable of carrying Ethernet traffic?





MSS-4/8 shelf FAN replacement 9-27

DLP-106

DLP-106 MSS-4/8 shelf FAN replacement

DLP-106MSS-4/8 shelf FAN replacementPurpose

This procedure describes how to replace a MSS-4/8 shelf FAN card.

Prerequisites

A replacement FAN card must be available on-site before starting this procedure.

General



STEP PROCEDURE




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 for information about how to remove the card.


8 Install the replacement FAN card. See DLP-100 for information about how to install the card.


MSS-4/8 shelf FAN replacement9-28

DLP-106

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?





MOD300 (radio modem) replacement 9-29

DLP-107

DLP-107 MOD300 (radio modem) replacement

DLP-107MOD300 (radio modem) replacementPurpose

This procedure describes how to replace a MOD300.

Prerequisites


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.




STEP PROCEDURE




MOD300 (radio modem) replacement9-30

DLP-107


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.



MOD300 replacement procedures

9 Is the MOD300 to be replaced in a protected system?



11 Is MOD300 to be replaced the main or spare?






MOD300 (radio modem) replacement 9-31

DLP-107

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 CAUTION: Possibility of service interruption. 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.


MOD300 (radio modem) replacement9-32

DLP-107




MPT-HL transceiver replacement 9-33

DLP-108

DLP-108 MPT-HL transceiver replacement

DLP-108MPT-HL transceiver replacementPurpose

This procedure describes how to replace a Microwave Packet Transport (MPT-HL) transceiver.

Prerequisites


General

The MPT-HL 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 Transceiver cards; one protected pair, or two unprotected MPT-HL transceiver cards.

In protected radios, the main MPT-HL transceiver is resident in slot 1. The spare MPT-HL Transceiver is resident in slot 2.

In an unprotected radio, performing a MPT-HL transceiver removal and replacement procedure causes loss of traffic. In a protected system, the procedure is an in-service but not a hitless procedure.



STEP PROCEDURE


2 CAUTION: Possibility of service interruption. Removing an in-service MPT-HL transceiver in an unprotected link causes loss of traffic. Removing an in-service card in a protected MPT-HL transceiver requires switching the traffic onto the spare channel.

3 CAUTION: Possibility of service interruption. In protected MPT-HL Transceiver configurations, the Main MPT-HL transceiver reside in slot 1. The spare MPT-HL transceiver reside in slot 2.


MPT-HL transceiver replacement9-34

DLP-108

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

5 WARNING: Possibility of equipment damage. Circuit packs contain static-sensitive devices. These devices can be damaged by static discharge. See the Introduction for special handling instructions.




MPT-HL transceiver replacement procedures

9 Is the MPT-HL 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 transceiver to be replaced the main or spare?





15 Go to step 19.



MPT-HL transceiver replacement 9-35

DLP-108



19 Verify that the MPT-HL Transceiver to be replaced status is Standby.

20 CAUTION: Possibility of service interruption. Removing power to an in-service card in an unprotected link causes loss of traffic.

21 Position the MPT-HL transceiver PA switch to the OFF �0� position.

22 Remove the fuse in PDU that is suppling battery power to the MPT-HL transceiver.

23 Disconnect the power cable.

24 Disconnect the GigE cable (optical or Molex) from the SFP port on the MPT-HL transceiver.

25 Remove SFP from MPT-HL transceiver, if required.

26 Loosen the screws securing the MPT-HL transceiver to the MPT-HL shelf. See DLP-100 for information about how to remove the card.

27 Pull out on the MPT-HL transceiver to disconnect from the shelf backplane connectors.

28 Remove the MPT-HL transceiver from the shelf.

29 Slowly push replacement MPT-HL transceiver into shelf until contact is made with alignment pins/backplane connectors. See DLP-100 for information about how to install the card.

30 Apply steady pressure and push in on replacement MPT-HL transceiver until MPT-HL transceiver is seated in backplane connectors.


32 Tighten the screws securing MPT-HL Transceiver to MPT-HL shelf.

33 Verify that the RF cables on shelf backplane connectors on rear of shelf have not been loosened by installation of the MPT-HL Transceiver. Tighten cables to no more than 19 in lbs, if required.

34 Install the SFP into SFP receptacle (if required).


MPT-HL transceiver replacement9-36

DLP-108

35 Connect the GigE cable (optical or Molex) into the SFP port on MPT-HL transceiver.

36 Connect the power cable.

37 Verify that the MPT-HL transceiver PA switch is in the OFF �0� position.

38 Install the fuse in the PDU that is suppling battery power to MPT-HL transceiver.

39 Position the MPT-HL transceiver PA switch to the ON �1� position.

40 Ensure that the MPT-HL transceiver PA (Power Amplifier) switch is in the �On� (1) position.

41 Wait for the MPT-HL transceiver to finish booting.

42 Verify that the replacement MPT-HL transceiver status LED turns steady green or amber.

43 Verify that the replacement MPT-HL transceiver is alarm free using the Alarm Monitor.

44 Is replacement MPT-HL transceiver status LED turns steady green or amber, and alarm free?


45 Is the replacement MPT-HL transceiver in a protected system?


46 CAUTION: Possibility of service interruption. Releasing Forced EPS and HSB switch causes a disruption to traffic.




50 Go to step 52.




ODU300 replacement 9-37

DLP-109

DLP-109 ODU300 replacement

DLP-109ODU300 replacementPurpose

This procedure describes how to replace a Outdoor Unit (ODU300).

Prerequisites


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.

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.



See the 9500 MPR-A Installation Practices (PN 3EM23953AM) Charts 10 and 11 for information about how to physically remove and install the ODU300 to be replaced in this procedure.


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


ODU300 replacement9-38

DLP-109


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 Installation Practices manual (PN 3EM23953AM) Charts 10 and 11 for information about how to physically install an ODU300.


ODU300 replacement 9-39

DLP-109

14 Disconnect and remove the failed ODU300. See the Installation Practices manual for more information.

15 Install the replacement ODU300. See the Installation Practices manual 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?







ODU300 replacement9-40

DLP-109


P2E3DS3 (2-Port DS3) replacement 9-41

DLP-110

DLP-110 P2E3DS3 (2-Port DS3) replacement

DLP-110P2E3DS3 (2-Port DS3) replacementPurpose

This procedure describes how to replace a P2E3DS3 card.

Prerequisites


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 must be plugged in side-by-side.

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.




STEP 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 reside in slots 4, 6, and/or 8.


P2E3DS3 (2-Port DS3) replacement9-42

DLP-110






P2E3DS3 replacement procedures

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

16 CAUTION: Possibility of service interruption. Removing an In-Service card in an unprotected configuration causes a loss of traffic.



DLP-110

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 for information about how to remove the card.

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 for information about how to install card.

21 Connect the DS3 input and output cables.


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.





DLP-110



DLP-111

DLP-111 P32E1DS1 (32-Port DS1) replacement

DLP-111P32E1DS1 (32-Port DS1) replacementPurpose

This procedure describes how to replace a P32E1DS1 card.

Prerequisites


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 must be plugged in side-by-side.

In unprotected DS1 configurations, performing the P32E1DS1 removal and replacement procedure causes loss of traffic. In a protected system the procedure is an in-service but not a hitless procedure.




STEP 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 will compromise EMC integrity and cooling air from the fan.

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 reside in slots 4, 6, and/or 8.



DLP-111






P32E1DS1 replacement procedures

9 Is the P32E1DS1 to be replaced in a protected system?



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.

16 CAUTION: Possibility of service interruption. Removing an in-service card in an unprotected configuration causes a loss of traffic.



DLP-111

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 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 for information about how to remove card.

21 Connect the DS1 input and output cables.


23 Seat the replacement P32E1DS1 into the shelf.


25 Verify the replacement P32E1DS1 alarms, that the status is normal, and capable of carrying traffic using the Alarm Monitor and Craft Terminal.

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.





DLP-111


Clean fiber-optic connectors 9-49

DLP-112

DLP-112 Clean fiber-optic connectors

DLP-112Clean fiber-optic connectorsPurpose

This procedure describes the recommended instructions to clean fiber-optic connectors found in Alcatel-Lucent equipment.

Prerequisites

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.

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®1 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

• Optical removal and cleaning tool�Alcatel-Lucent PN 3EM07060AAAA

• Penlight (pocket-style flashlight)

• Laser safety glasses

General

If the cleaning method described in this procedure does not produce acceptable results, the connector may need to be replaced.

1. CLETOP is a registered trademark of NTT International.


Clean fiber-optic connectors9-50

DLP-112



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



DLP-112

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

Figure 112-1. Fiber-optic connector inspection

129-1280-1

021607

FIBER CONTAMINATED

WITH SOLID PARTICLES

PARTICLES

FIBER CONTAMINATED

WITH OIL (FINGERPRINT)

OIL FILM AND PARTICLES

ON CLADDING AND IN

CORE AREA

CLEAN FIBER

FIBER

CLADDING CORE

FERRULE

(SHAPE CAN VARY

BY CONNECTOR TYPE)



DLP-112

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 Figures 112-2 and 112-3 for connector types.

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

Figure 112-2. Fiber-optic connector types, illustrations

950-0151-1

092109

ST CONNECTORFC CONNECTOR SC CONNECTOR

MU FIBER CONNECTOR LC FIBER CONNECTOR



DLP-112

FC, SC, MU, LC, or ST/STII fiber-optic connector

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

Bulkhead connectors

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

Figure 112-3. Fiber-optic connector types, photographs

SC CONNECTOR FC CONNECTOR

ST/STII CONNECTOR

950-0150-1092109



DLP-112

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?


Inspect connector

19 Use an inspection microscope to inspect fiber-optic connector. See Figure 112-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.


If yes, go to step 23.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?




System power down and power up 9-55

DLP-113

DLP-113 System power down and power up

DLP-113System power down and power upPurpose

This procedure describes how to power down and power up a 9500 MPR-A system.

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 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 transceivers, and MOD300s, before bringing up the transmitters.

All cards can be removed and installed with power applied.



STEP PROCEDURE






System power down and power up9-56

DLP-113

5 Select an action?

If the system power is down, go to step 6.If the system power is up, go to step 13.

System power down procedure

6 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 transceiver PA switches to the OFF �0� position.

9 Remove fuses in the PDU that are suppling battery power to all MPT-HL transceivers in the system.

10 Remove power to the MPT ODU. Depending upon the configuration, perform one of the following for each MPT ODU:

• If power is provided by the MPTACC card, use the Craft Terminal and disable power source.

• If power is provided by the MSS-1 shelf Core, use the Craft Terminal and disable 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.

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

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

• If MPT ODU is powered with connection to direct office power, locate the fuse protecting the MPT ODU and remove.

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


System power down and power up 9-57

DLP-113

System power up procedure

13 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 transceivers in the system.

16 Position all MPT-HL 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.



System power down and power up9-58

DLP-113


MPTACC (MPT Access) replacement 9-59

DLP-114

DLP-114 MPTACC (MPT Access) replacement

DLP-114MPTACC (MPT Access) replacementPurpose

This procedure describes how to replace an MPTACC.

Prerequisites


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 channels per MPTACC card for a maximum of twelve MPTACC MPT-HC/MPT-XP/9558HC (MPT ODU) radio channels per MSS-8 shelf and four radio channels 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 channel. 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.



See the 9500 MPR-A Operation and Administration (PN 3EM23954AM) for detailed procedures to execute the commands included in this procedure.

STEP PROCEDURE



MPTACC (MPT Access) replacement9-60

DLP-114

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 will compromise EMC integrity and cooling air from the fan.


4 CAUTION: Possibility of service interruption. In redundant MPTACC protected 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.



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


MPTACC replacement procedures

9 Determine MPTACC configuration.




d. Is the power to the radio channels provided by the MPTACC card?



DLP-114

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?



13 CAUTION: Possibility of service interruption. In redundant MPTACC protected 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 channels supported by the MPTACC in a protected system?

If yes, perform steps 16 through 24 for each protected radio channel supported by the MPTACC to be replaced.If no, go to step 26.


17 Is the MPTACC to be replaced main or spare?





21 Go to step 25.





DLP-114


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 for information about how to remove the card.


31 Install the replacement MPTACC into the shelf. See DLP-100 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 channels 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?

If yes, perform steps 38 through 41 for each radio channel supported by the MPTACC to be replaced.If no, go to step 44.

38 CAUTION: Possibility of service interruption. Releasing Forced/Lockout EPS/HSB/RX Radio switch causes a disruption to traffic.





DLP-114


42 Go to step 44.





DLP-114


MPT ODU replacement (MPT-HC, MPT-XP, 9558HC) 9-65

DLP-115

DLP-115 MPT ODU replacement (MPT-HC, MPT-XP, 9558HC)

DLP-115MPT ODU replacement (MPT-HC, MPT-XP, 9558HC)Purpose

This procedure describes how to replace an Outdoor Unit, MPT-HC/MPT-XP/9558HC (MPT ODU).

Prerequisites


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.

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.

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:


MPT ODU replacement (MPT-HC, MPT-XP, 9558HC)9-66

DLP-115

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



See the 9500 MPR-A Installation Practices (PN 3EM23953AM) Charts 10 for information about how to physically remove and install the MPT ODU to be replaced in this procedure.


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




DLP-115

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:

• If power is provided by the MPTACC card, use the Craft Terminal and disable power source.

• If power is provided by the MSS-1 shelf MSS/CORE ports 1 and 2, use the Craft Terminal and disable power source.

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

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



DLP-115

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

• If MPT ODU is powered with connection to direct office power, locate the fuse protecting the MPT ODU and remove.

• 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 Installation Practices manual (PN 3EM23953AM) Charts 10 for information about how to physically install an MPT ODU.

19 Remove the failed MPT ODU. See the Installation Practices manual for more information.

20 Install replacement MPT ODU. See the Installation Practices manual for more information.

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 Graphics window appears.

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.



DLP-115

31 Is the replacement MPT ODU status normal and capable of carrying traffic?


32 Is the replacement MPT ODU in a protected system?










DLP-115


Auxiliary (AUX) replacement 9-71

DLP-116

DLP-116 Auxiliary (AUX) replacement

DLP-116Auxiliary (AUX) replacementPurpose

This procedure describes how to replace an AUX card.

Prerequisites


General

The AUX card can be installed in MSS-8 slot 8 and MSS-4 slot 4.




STEP PROCEDURE






Auxiliary (AUX) replacement9-72

DLP-116



AUX replacement procedures

7 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 for information about how to remove the card.


12 Install replacement AUX into shelf. See DLP-100 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?





Protection upgrade and downgrade procedures 9-73

DLP-117

DLP-117 Protection upgrade and downgrade procedures

DLP-117Protection upgrade and downgrade proceduresPurpose

These procedures describes how to upgrade and downgrade protection configuration on the 9500 MPR-A system.

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.

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.

Radio protection

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

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 are 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, DC Extractor, waveguide, and grounding.

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


Protection upgrade and downgrade procedures9-74

DLP-117

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.



STEP PROCEDURE





5 Select an action?

To Upgrade PDH 1+0 to 1+1 EPS protection configuration, go to step 6.To Downgrade PDH 1+1 EPS to 1+0 not protected configuration, go to step 13.To Upgrade 1+0 to 1+1 protected radio configuration, go to step 20.To Downgrade 1+1 to 1+0 not protected radio configuration, go to step 31.To Upgrade fixed modulation to adaptive modulation configuration, go



DLP-117

to step 43.To Downgrade adaptive modulation to fixed modulation configuration, go to step 60.

Upgrade PDH 1+0 to 1+1 EPS protection configuration

6 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 9500 MPR-A Operation and Administration Manual.

12 Go to step 75.

Downgrade PDH 1+1 EPS to 1+0 not protected configuration

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



DLP-117

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 9500 MPR-A Operation and Administration Manual.

19 Go to step 75.

Upgrade 1+0 to 1+1 protected radio configuration

20 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 a radio that is equipped with a MOD300 card, install the MOD300 card in slot 4, 6, or 8 but do not seat the card at this time. Connect IF coax cable to MOD300 card.

23 Install the appropriate radio spare card in spare slot 4, 6, or 8 that is associated with main radio channel. An Unconfigured Equipment Present alarm appears.

For a radio that equipped with the MOD300 card, seat the card into slot 4, 6, or 8.

For a radio that equipped with a MPT-HL transceiver, the spare P8ETH card must be installed in slot 4 if not already equipped. Install the MPT-HL transceiver in slot 2 of the MPT-HL shelf.

For a radio that is equipped with a MPTACC card, the spare radio directions are 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.

24 On the CT settings window, enable the cards/MPT-HL transceiver that you installed in step 23.

25 On the CT settings window, configure the radio channel 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.



DLP-117

For a radio that is equipped with MPT-HL transceiver, install the SFP into the appropriate P8ETH SFP port. Connect the fiber optic cable between the SFP port and MPT-HL transceiver. Connect the MPT-HL transceiver power cable, as described in the site documentation.

For a radio that is equipped with a MPTACC card, 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.

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

29 Reprovision all of the affected 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 9500 MPR-A Operation and Administration Manual.

30 Go to step 75.

Downgrade 1+1 to 1+0 not protected radio configuration

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

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

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

34 On CT settings window for radio channel, enable the Local Tx Mute for channel #1 and #0.

35 On CT settings window, set the radio channel protection type to No Protection.



DLP-117

36 On CT settings window for radio channel, disable the Local Tx Mute for channel #1 only.

37 Disconnect the channel#0 radio direction cables to the spare radio cards.

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.

For a radio that is equipped with a MPT-HL transceiver, disconnect the fiber optic cable between the SFP port and MPT-HL transceiver, as described in the site documentation.

For a radio that is equipped with a MPTACC card, 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.

38 On CT settings window, set the radio channel equipment type to Empty.

39 Remove the appropriate radio spare card from the spare MSS slot 4, 6, or 8.

For a radio that is equipped with a MOD300 card, remove from slot 4, 6, or 8.

For a radio that is equipped with an MPT-HL transceiver, remove the P8ETH card from slot 4 only if described in the site documentation. Remove the SFP from the P8ETH SFP port. Remove the MPT-HL transceiver in slot 2 of the MPT-HL shelf.

For a radio that is equipped with an MPTACC card, spare radio directions are 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. Remove the MPTACC only if described in the site documentation.

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

41 Power down and then power up the NE. See DLP-113 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.



DLP-117

42 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 configure cross-connections, see the 9500 MPR-A Operation and Administration Manual, DLP-112.

Upgrade fixed modulation to adaptive modulation configuration

43 CAUTION: Possibility of service interruption. This is an Out-of-Service procedure. Schedule appropriate maintenance window per local practices and procedures.

44 Verify that the system license key supports adaptive modulation. For more information about how to display and update the system license key, see the 9500 MPR-A Operation and Administration Manual, DLP-120.

45 Open the radio channel view. Take a screen capture to save all radio channel provisioning information.

46 Which type of radio direction configuration?

If 1+0 Not protected, go to step 49.If 1+1 protected, go to step 47.

47 Mute the spare radio channel (channel #0).

48 Set the radio direction Protection Type to No Protection.

49 Is the ATPC enabled?


50 Disable the ATPC (unchecked) and click on the Apply button.

51 From the radio direction Mode drop-down menu, choose Adaptive Modulation and click on the Apply button.

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



54 Set the radio direction Protection Type to 1+1 HSB(SD) or 1+1 FD.

55 Unmute the spare radio channel (channel #0).



DLP-117

56 NOTE: To complete the upgrade from fixed modulation to adaptive modulation both ends of the radio hop must be upgraded.

57 Verify that the radio direction is alarm free.

58 Verify that the radio direction is error free and operating as expected.

59 Go to step 75.

Downgrade adaptive modulation to fixed modulation configuration





63 Mute the spare radio channel (channel #0).

64 Set the radio direction Protection Type to No Protection.

65 From the radio direction Mode drop-down menu, choose Presetting and click on the Apply button.



67 Set the radio direction Protection Type to 1+1 HSB(SD) or 1+1 FD.

68 Unmute the spare radio channel (channel #0).

69 Provision the ATPC?


70 Enable the ATPC (checked) and click on the Apply button.

71 Configure the local ATPC Tx range, remote ATPC Rx threshold, and click on the Apply button.



DLP-117

72 NOTE: To complete the upgrade from adaptive modulation to fixed modulation both ends of the radio hop must be downgraded.


74 Verify that they radio direction is error free and operating as expected.




DLP-117


Upgrade and downgrade radio profile 9-83

DLP-118

DLP-118 Upgrade and downgrade radio profile

DLP-118Upgrade and downgrade radio profilePurpose

These procedures describes how to upgrade and downgrade radio profile on the 9500 MPR-A system.

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.

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.



STEP PROCEDURE

1 Select an action?

To Upgrade radio profile, go to step 2.To Downgrade radio profile, go to step 12.

Upgrade radio profile



Upgrade and downgrade radio profile9-84

DLP-118

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 9500 MPR-A Operation and Administration Manual, 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.

6 Click on the Apply button.

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.

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.

16 Click on the Apply button.

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.



Upgrade and downgrade radio profile 9-85

DLP-118




Upgrade and downgrade radio profile9-86

DLP-118


Upgrade unlicensed MPT-HL radio to lower 6 GHz radio 9-87

DLP-119

DLP-119 Upgrade unlicensed MPT-HL radio to lower 6 GHz radio

DLP-119Upgrade unlicensed MPT-HL radio to lower 6 GHz radioPurpose

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.

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.



STEP PROCEDURE


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.



Upgrade unlicensed MPT-HL radio to lower 6 GHz radio9-88

DLP-119




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 9500 MPR-A Operation and Administration Manual, 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 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.


Upgrade unlicensed MPT-HL radio to lower 6 GHz radio 9-89

DLP-119

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 9500 MPR-A Operation and Administration Manual, 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?

If ATPC, go to step i.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.


Upgrade unlicensed MPT-HL radio to lower 6 GHz radio9-90

DLP-119

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.





+24/-48 volt converter replacement 9-91

DLP-120

DLP-120 +24/-48 volt converter replacement

DLP-120+24/-48 volt converter replacementPurpose

This procedure describes how to replace a +24/-48 volt Converter.

Prerequisites


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.



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


+24/-48 volt converter replacement9-92

DLP-120

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.



+24/-48 Volt converter replacement procedure

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


+24/-48 volt converter replacement 9-93

DLP-120

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 for information about how to remove the converter.


15 Install the replacement converter into the chassis. See DLP-100 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?


Figure 120-1. +24/-48 Volt converter cabling diagram

950-0152-1

101910

Cable Assemblies:

3DB18766AA

Cable Assemblies:

3DB18271AA

Protect

(B-Side)

Power

Main

(A-Side)

Power

Main Power

ConverterProtect Power

Converter


+24/-48 volt converter replacement9-94

DLP-120




Power injector replacement 9-95

DLP-121

DLP-121 Power injector replacement

DLP-121Power injector replacementPurpose

This procedure describes how to replace a Power Injector card and Power Injector box.

Perquisites


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.



STEP PROCEDURE




Power injector replacement9-96

DLP-121

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.


Power injector replacement procedure

7 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?


10 CAUTION: Possibility of service interruption. Replacing an in-service Power 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?

If Power Injector box, go to step 13.If Power Injector card, go to step 20.


Power injector replacement 9-97

DLP-121

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


23 Install the replacement Power Injector card into shelf. See DLP-100 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?



Power injector replacement9-98

DLP-121




RPS/XPIC module replacement 9-99

DLP-122

DLP-122 RPS/XPIC module replacement

DLP-122RPS/XPIC module replacementPurpose

This procedure describes how to replace a RPS and XPIC module on the MPT-HC/MPT-XP/9558HC (MPT ODU).

Prerequisites


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.

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.


See the 9500 MPR-A Installation Practices (PN 3EM23953AM) Charts 10 for information about how to physically remove and install the RPS/XPIC module to be replaced in this procedure.


Table 122-A. MPT ODU 1+1 module detailsITEM DESCRIPTION Part NumberXPIC Module 3DB20116BA/BBRPS Module 3DB20117BA


RPS/XPIC module replacement9-100

DLP-122

STEP PROCEDURE

1 DANGER: Possibility of personal injury. Exposure to energy radiated at 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 practices and procedures.

5 CAUTION: Possibility of service interruption. Forced EPS/HSB/Rx Radio switching traffic causes a disruption to traffic.

6 What is the radio configuration that is associated with the RPS/XPIC module to be replaced?

If 1+1 XPIC or 1+1 protected, go to step 7.If co-channel XPIC, go to step 17.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.



DLP-122




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 per local practices and procedures.

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 Installation Practices manual (PN 3EM23953AM) 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 Installation Practices Manual 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.



DLP-122

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 Graphics window appears.

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?

If 1+1 XPIC or 1+1 protected, go to step 42.If co-channel XPIC, go to step 47.If 1+0 unprotected, go to step 47.







DLP-122




Upgrade MPT ODU to MPT ODU L1 LAG port 9-105

DLP-123

DLP-123 Upgrade MPT ODU to MPT ODU L1 LAG port

DLP-123Upgrade MPT ODU to MPT ODU L1 LAG portPurpose

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.

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.

Before the L1 LAG port is ready to carry traffic, this procedure must be performed at both ends of the radio hop.





Upgrade MPT ODU to MPT ODU L1 LAG port9-106

DLP-123

STEP PROCEDURE



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





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


Upgrade MPT ODU to MPT ODU L1 LAG port 9-107

DLP-123

b. VLAN

c. Port Segregation

d. PPP RF enabled

e. Synchronization reference

f. SSM

12 Perform a database backup. See the 9500 MPR-A Operation and Administration Manual, 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 9500 MPR-A Maintenance and Trouble Clearing Manual, DLP-117 for a detailed procedure.

14 Disable MPT ODU radio port from MPTACC card. See the 9500 MPR-A Operation and Administration Manual, 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 9500 MPR-A Operation and Administration Manual, 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.


Upgrade MPT ODU to MPT ODU L1 LAG port9-108

DLP-123

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 9500 MPR-A Operation and Administration Manual, 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 9500 MPR-A Operation and Administration Manual, DLP-140 for a detailed procedure to create L1 LAG port.

24 Add MPT ODU radio interface to L1 LAG port. See the 9500 MPR-A Operation and Administration Manual, 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.





Upgrade MPT-HL to MPT-HL L1 LAG port 9-109

DLP-124

DLP-124 Upgrade MPT-HL to MPT-HL L1 LAG port

DLP-124Upgrade MPT-HL to MPT-HL L1 LAG portPurpose

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.

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 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:

• Cross-Connections

• VLANs

• Port Segregation

• PPP-RF

• Synchronization


Upgrade MPT-HL to MPT-HL L1 LAG port9-110

DLP-124

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

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 9500 MPR-A Product Information (PN 3EM23952AM) for a detailed description of the L1 LAG feature and to determine card location and type.

Table 124-A. MPT-HL L1 LAG bandwidth per service typeType of service L1 LAG bandwidth used

[Kbps]MPT-HL bandwidth used[Kbps]

DS1 TDM2TDM 2080 1683DS1 TDM2Eth 1882 1694DS3 TDM2TDM 60264 48756DS3 TDM2Eth 46571 45574



DLP-124


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





8 Verify the NE is running R3.4.0 or higher software version.

9 Verify the MPT-HL radio channel is alarm/condition free and error free on both the near and far ends of the radio hop.

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

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



DLP-124

12 Perform a database backup. See the 9500 MPR-A Operation and Administration Manual, DLP-131 for a detailed procedure to perform a database backup.

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

14 If radio channel is configured in 1+1 HSB/FD configuration, perform Lockout protection switch for the following:



• Rx Radio (RPS)

15 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 9500 MPR-A Maintenance and Trouble Clearing Manual, DLP-117 for a detailed procedure.

16 Download and save the Current Configuration file. See the 9500 MPR-A Operation and Administration Manual, DLP-116 for a detailed procedure to download and save the current configuration file.

17 Create L1 LAG port. See the 9500 MPR-A Operation and Administration Manual, DLP-140 for a detailed procedure to create L1 LAG port.

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

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

20 Add MPT-HL radio interface to L1 LAG port. See the 9500 MPR-A Operation and Administration Manual, 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.



DLP-124

21 Click on the OK button.

After you click on the OK button, the following warning message will display.

22 Click on the Yes button.

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

24 Close the Craft Terminal.

25 Reopen the Craft Terminal and log in to the NE.



28 Download and save the Current Configuration file.

29 Using the Current Configuration files downloaded in steps 16 and 28, verify that the following provisioning parameters were re-provisioned correctly:

Figure 124-1. MPT-HL to L1 LAG information message

Figure 124-2. MPT-HL to L1 LAG warning message



DLP-124

• Cross-Connections

• VLANs

• Port Segregation

• PPP-RF

• Synchronization

30 If radio channel is configured in 1+1 HSB/FD configuration, release Lockout protection switch for the following:



• Rx Radio (RPS)

31 NOTE: To complete the upgrade to MPT-HL L1 LAG Port, this procedure must be performed on both ends of the radio direction.



MPT Power Unit replacement 9-115

DLP-125

DLP-125 MPT Power Unit replacement

DLP-125MPT Power Unit replacementPurpose

This procedure describes how to replace a MPT Power Unit or MPT Extended Power Unit.

Prerequisites


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.



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


MPT Power Unit replacement9-116

DLP-125



MPT power unit replacement procedure

6 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?


8 Is it appropriate to proceed with Power Unit replacement procedure?


9 CAUTION: Possibility of service interruption. Replacing an in-service Power 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.


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


MPT Power Unit replacement 9-117

DLP-125

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?





MPT Power Unit replacement9-118

DLP-125


SDHACC (2-Port OC-3) Replacement 9-119

DLP-126

DLP-126 SDHACC (2-Port OC-3) Replacement

DLP-126SDHACC (2-Port OC-3) ReplacementPURPOSE

This procedure describes how to replace a SDHACC card.

PREREQUISITES


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 must be plugged in side-by-side.

In unprotected OC-3 configurations, performing the SDHACC removal and replacement procedure causes loss of traffic. In a protected system the procedure is an in-service but not a disruptionless procedure.




STEP PROCEDURE




SDHACC (2-Port OC-3) Replacement9-120

DLP-126

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 reside in slots 4, 6, and/or 8.






SDHACC Replacement Procedures

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



SDHACC (2-Port OC-3) Replacement 9-121

DLP-126

15 Verify that the SDHACC to be replaced status is Standby.

16 CAUTION: Possibility of service interruption. Removing an In-Service card in an unprotected configuration causes a loss of traffic.

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 for information about how to remove the card.

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 for information about how to install card.

21 Connect the OC-3 input and output cables.


23 Install the replacement SDHACC into the shelf.


25 Verify the replacement SDHACC alarms, that the status is normal, and capable of carrying traffic using the Alarm Monitor and Craft Terminal.

26 Is the replacement SDHACC status normal and capable of carrying traffic?


27 Is the replacement SDHACC in a protected system?




30 Go to step 32.


SDHACC (2-Port OC-3) Replacement9-122

DLP-126




Software package rollback 9-123

DLP-127

DLP-127 Software package rollback

DLP-127Software package rollbackPurpose

This procedure describes how to rollback to the previous software package version on a 9500 MPR-A system.

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 127-A provides a list of supported software package rollbacks:

For a full description of the software package rollback feature, see the 9500 MPR-A Product Information (PN 3EM23952AM).

STEP PROCEDURE

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

Table 127-A. Releases supporting software package rollback Initial softwarerelease version(Current Status: �Stand by�)

Upgrade softwarerelease version(Current Status: �Committed�)

Software package rollback support

R3.2.0, R3.3.0, or R3.4.0 R4.0.0 NoR3.4.0 R4.1.0 NoR4.0.0 or greater R4.1.0 or greater Yes


Software package rollback9-124

DLP-127

2 Have all alternative been explored to resolve the system problem?


3 Have all appropriate levels of support been notified and all are in agreement that a software package rollback is the appropriate next step?


4 Contact ALL appropriate levels of support and obtain all appropriate approvals as required per local practices and procedures.

5 Have all appropriate levels of support been notified and are in agreement that a software package rollback is the appropriate next step?


Software package rollback procedure

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

7 Open the NE Software Status Detail window.

From the Main Menu Bar select, SW Download>SW Status.

8 On the software bank with the Current Status Committed, verify the software version matches that of the upgraded software package. See figure 127-2



DLP-127

9 On the software bank with the Current Status Standby, verify the software version matches that of the initial software package. See figure 127-3

Figure 127-2. Software bank with upgrade software version Committed status

Figure 127-3. Software bank with Initial software version Standby status



DLP-127

10 Are the committed (upgrade) and standby (initial) software version verified and correct as expected?


11 On the software bank for the standby software version, select from the Software Management Action drop-down menu Forced Activation. See figure 127-4

12 Select the Apply Action button. See figure 127-4

13 Communication with the NE will be lost. Wait until the Core-E card status LED is solid green before proceeding to step 14.

14 Log in to the NE.

15 Open the NE Software Status Detail window.

From the Main Menu Bar select, SW Download>SW Status.

16 On the software bank with the Current Status Committed, verify the software version matches that of the initial software package. See figure 127-5

Figure 127-4. Software Management Action - Forced Activation



DLP-127

17 On the software bank with the Current Status Standby, verify the software version matches that of the upgrade software package. See figure 127-6

Figure 127-5. Software bank with initial software version Committed status

Figure 127-6. Software bank with upgrade software version Standby status



DLP-127

18 Are the committed (initial) and standby (upgrade) software version verified and correct as expected?


19 Contact the next level of support for assistance.



MSS-1 shelf replacement 9-129

DLP-128

DLP-128 MSS-1 shelf replacement

DLP-128MSS-1 shelf replacementPurpose

This procedure describes how to replace a MSS-1 shelf.

Prerequisites


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 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 9500 MPR-A Product Information (PN 3EM23952AM) to determine port location and type.


STEP 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 replacement9-130

DLP-128

2 WARNING: Possibility of equipment damage. Possibility of damage to equipment. MSS-1 shelf contain static-sensitive devices. These devices can be damaged by static discharge. See the Introduction for special handling instructions.

MSS-1 shelf replacement procedure

3 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?

c. Are Ethernet ports configured and carrying traffic?


5 Is it appropriate to proceed with Power Unit 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.


15 Retrieve the alarms using the Alarm Monitor. A Dialog Failure is declared against the MPT ODUs and/or MPT-HLs. Wait for Dialog Failure condition to clear before proceeding.


MSS-1 shelf replacement 9-131

DLP-128

16 Verify the MPT ODUs and/or MPT-HLs 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-HLs 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.



MSS-1 shelf replacement9-132

DLP-128

29 Are the MSS-1 shelf DS1 port alarms clear?




Customer documentation and productsupport

Customer documentationhttp://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 supporthttp://support.alcatel-lucent.com

Documentation [email protected]