Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Alcatel-Lucent 9500
MICROWAVE PACKET RADIO for ANSI | RELEASE 4.2.0
Indoor: MSS-8/MSS-4/MSS-1/MPT-HL
Outdoor: ODU300/MPT-HC/MPT-XP/9558HC
Alcatel-Lucent Proprietary
This document contains proprietary information of Alcatel-Lucent and is not to be disclosed
or used except in accordance with applicable agreements.
Copyright 2013 Alcatel-Lucent. All rights reserved.
Alcatel-Lucent assumes no responsibility for the accuracy of the information presented, which is subject to change
without notice.
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks
are the property of their respective owners.
Copyright 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 AlcatelLucent, 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.
NOTICE
This manual applies to 9500 MPR-A R4.2.0 software. Release notes describing revisions to this software
may impact operations described in this manual.
This transfer of commodities, technology, or software, if from the United States, is an export in accordance
with the U.S. Export Administration Regulations. Diversion contrary to U.S. law is prohibited. The export or
re-export (further transfer) of such commodities, technology, software or products made from such
technology is prohibited without proper authorization(s) from the U.S. Department of Commerce or other
appropriate U.S. government agency(s).
All rights reserved. No part of this manual may be reproduced, translated, stored in a retrieval system, or
transmitted 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 based
on 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 information
purposes only and are subject to change without notice. They do not represent any obligation on the part of
Alcatel-Lucent. Such obligations will only be committed to in a written sales agreement signed by
Alcatel-Lucent.
ALCATEL-LUCENT PRACTICE
Standard
3EM23956AM
Issue 01, February 2013
Table of Contents
FCC part 15 subpart B
1. 9500 MPR-A unlicensed radio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
FCC Class B compliance statement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
FCC Class B requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Introduction
1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Writing conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Admonishments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Related documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Document types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
2. Maintenance philosophy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Before going to site checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Troubleshooting basics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Path problems on a commissioned link . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Path problems on a new link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
Troubleshooting configuration problems . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
Troubleshooting ethernet problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
3. Safety awareness. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15
Safety EMC-EMF-ESD norms and equipment labeling . . . . . . . . . . . . . . . 1-15
Safety rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15
General rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15
Labels indicating danger, forbiddance, command . . . . . . . . . . . . . . . . . . . 1-16
4. Electrostatic-sensitive devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-29
Electrostatic-sensitivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-29
Handling circuit packs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-30
5. Product support information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-31
Telephone support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-31
Product documentation and training. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-31
Technical support center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-33
Repair and return services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-34
Spare parts and replacement cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-34
Service center. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-35
Installation and maintenance services . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-36
3EM23956AM
Issue 01, February 2013
IXL-101
IXL-102
IXL-103
IXL-104
TAP-101
TAP-102
TAP-103
TAP-104
TAP-105
TAP-106
TAP-107
TAP-108
TAP-109
TAP-110
TAP-111
TAP-112
TAP-113
ii
Table of Contents
3EM23956AM
Issue 01, February 2013
TAP-114
TAP-115
TAP-116
TAP-117
TAP-118
TAP-119
TAP-120
DLP-101
DLP-102
DLP-103
DLP-104
DLP-105
DLP-106
DLP-107
DLP-108
DLP-109
DLP-110
DLP-111
DLP-112
DLP-113
DLP-114
Table of Contents
iii
3EM23956AM
Issue 01, February 2013
DLP-115
DLP-116
DLP-117
DLP-118
DLP-119
DLP-120
DLP-121
DLP-122
DLP-123
DLP-124
DLP-125
DLP-126
DLP-127
DLP-128
iv
Table of Contents
3EM23956AM
Issue 01, February 2013
List of Figures
Figure 3-1.
Figure 4-1.
List of Figures
3EM23956AM
Issue 01, February 2013
vi
List of Figures
3EM23956AM
Issue 01, February 2013
List of Tables
Table 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.
List of Tables
vii
3EM23956AM
Issue 01, February 2013
viii
List of Tables
3EM23956AM
Issue 01, February 2013
1-1
3EM23956AM
Issue 01, February 2013
CAUTION
1-2
3EM23956AM
Issue 01, February 2013
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
To avoid hazardous conditions, observe the following admonishments:
1.3
DANGER
CAUTION
WARNING
Related documentation
1.4
For additional system information, refer to the following related
documents:
Introduction
1-1
3EM23956AM
Issue 01, February 2013
Document types
1.5
The documentation contains all instructions needed to perform a task.
This manual consists of the following types of documents:
1-2
Introduction
3EM23956AM
Issue 01, February 2013
Introduction
1-3
3EM23956AM
Issue 01, February 2013
1-4
Introduction
3EM23956AM
Issue 01, February 2013
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:
2.5
The following guidelines and information should be observed during
troubleshooting:
Introduction
1-5
3EM23956AM
Issue 01, February 2013
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.
When replacing a circuit card does not clear the trouble, remove the
replacement circuit card and return the original circuit card to service.
2.6
1-6
Introduction
3EM23956AM
Issue 01, February 2013
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:
Could the weather (rain, ice, high wind, temperature) be a factor in the
reported fault?
Introduction
Does the fault history for the link indicate a likely cause?
1-7
3EM23956AM
Issue 01, February 2013
Toolkit.
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.
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
1-8
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
3EM23956AM
Issue 01, February 2013
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:
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.
Introduction
1-9
3EM23956AM
Issue 01, February 2013
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.
1-10
Introduction
3EM23956AM
Issue 01, February 2013
2.25
Reflections
Introduction
1-11
3EM23956AM
Issue 01, February 2013
Compatibility Problems
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
1-12
Introduction
3EM23956AM
Issue 01, February 2013
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 crossconnect 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.
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.
In order for the green Link LED to light:
2.41
Introduction
1.
2.
3.
Speed and mode (on Core Settings Screen) must be provisioned the
same as the link partner.
1-13
3EM23956AM
Issue 01, February 2013
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:
1-14
Introduction
3EM23956AM
Issue 01, February 2013
3.
Safety awareness
Safety rules
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
Introduction
1-15
3EM23956AM
Issue 01, February 2013
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.
It is recommended to use a slightly wet cleaning cloth.
3.6
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
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:
1-16
Risks of explosions
Laser precautions
Introduction
3EM23956AM
Issue 01, February 2013
3.11
Pay attention to the information stated in the following, and proceed
as instructed.
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.:
Introduction
1-17
3EM23956AM
Issue 01, February 2013
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:
Risks of explosions
Labeling:
3.15
This risk is present when batteries are used, and it is signaled by the
following label:
Safety instructions:
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-IEC5641 Norm. compliant label is affixed next to it indicating that the openings
must not be covered up.
1-18
Introduction
3EM23956AM
Issue 01, February 2013
Safety instructions:
3.18
Before carrying out any maintenance operation see that all the moving
mechanical parts have been stopped.
Introduction
1-19
3EM23956AM
Issue 01, February 2013
Safety instructions:
3.20
The position of earth connection terminals is specified in the
Hardware Installation section.
1-20
Introduction
3EM23956AM
Issue 01, February 2013
3.26
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).
3.27
Always remember that someone standing in front of the 9500 MPR-A
antenna may cause traffic shutdown.
3.28
Introduction
1-21
3EM23956AM
Issue 01, February 2013
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)
3.30
3.31
Compliance boundaries for 9500 MPR-A transceivers with 1ft (30 cm) antenna:
System Modulation
Worst Configuration
A (m)
B (m)
1-22
Hardware Installation
Introduction
3EM23956AM
Issue 01, February 2013
3.34
The norms set down to guarantee EMC compatibility, are
distinguished inside this Manual by the symbol and term:
EMC Norms
Introduction
1.
Before inserting the shielded unit proceed to clean and degrease all
peripheral surfaces (contact springs and connection points, etc.)
2.
Check that the equipment is operating with all the shields properly
positioned (dummy covers, ESD connector protections, etc.)
3.
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.)
1-23
3EM23956AM
Issue 01, February 2013
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.
1-24
Introduction
3EM23956AM
Issue 01, February 2013
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.
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
Introduction
1-25
3EM23956AM
Issue 01, February 2013
DANGER
DANGER
DANGER
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.
1-26
DANGER
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 dcrated 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
3EM23956AM
Issue 01, February 2013
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 sites 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
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
DANGER
DANGER
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
Introduction
1-27
3EM23956AM
Issue 01, February 2013
DANGER
DANGER
DANGER
1-28
1.
2.
Introduction
3EM23956AM
Issue 01, February 2013
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
671-0592-1
061405
4.4
Introduction
1-29
3EM23956AM
Issue 01, February 2013
WARNING
Handle all circuit packs as ESDs unless they are known not to contain
electrostatic-sensitive parts.
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.
4.6
ESDs are protected when properly packaged in conductive or
antistatic packaging. Acceptable packaging is marked as either conductive or
antistatic.
1-30
Introduction
3EM23956AM
Issue 01, February 2013
5.
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.
Introduction
Application notes
Configuration notes
Data collections
1-31
3EM23956AM
Issue 01, February 2013
Installation documents
Technical bulletins
Training documents
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:
IN USA:
IN CANADA:
Alcatel-Lucent USA
3400 W. Plano Pkwy.
Plano, Texas 75075
ATTN: Training M/S 1206-553
Alcatel-Lucent Canada
Network Services Division
P.O. Box 13600
Ottawa, Ontario K2K 2E6
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
1-32
Introduction
3EM23956AM
Issue 01, February 2013
5.12
Company name
Caller name
Introduction
1-33
3EM23956AM
Issue 01, February 2013
5.17
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.
1-34
Introduction
3EM23956AM
Issue 01, February 2013
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.
Introduction
Modification required
1-35
3EM23956AM
Issue 01, February 2013
Special instruction/information
1-36
Introduction
3EM23956AM
Issue 01, February 2013
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.
Introduction
1-37
3EM23956AM
Issue 01, February 2013
1-38
Introduction
IXL-100
3EM23956AM
Issue 01, February 2013
IXL-100
Task index list
Table 100-A lists the type of procedure or information needed to perform maintenance and trouble
clearing on the system.
Table 100-A. Task Index List
Type of procedure/information
See
IXL-101
Support procedures
IXL-102
IXL-103
Supporting information
IXL-104
RTL-100
2-1
3EM23956AM
Issue 01, February 2013
2-2
IXL-100
IXL-101
3EM23956AM
Issue 01, February 2013
IXL-101
Alarm and abnormal condition clearing procedures
See 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
3-3
IXL-101
3EM23956AM
Issue 01, February 2013
In the EQUIPMENT/FACILITY column, equipment entities are listed using the following
definitions:
In the EQUIPMENT/FACILITY column, facility entities are listed using the following definitions:
3-4
IXL-101
3EM23956AM
Issue 01, February 2013
The syntax for equipment Friendly Names / Entities is described in Table 101-A.
Table 101-A. Equipment friendly name syntax definitions
Location
Syntax
Values
Description
Rack
r01
Rack number
Subrack
s1
s[3-8][1-4]
s[3-8][5-8]
s1[1-6]
s[3-8][5-8]
s1[1-6]
s[3-8]
board#[1-9]
Board
b#[1-9]
Slot#[1-9]
Daughter
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>
3-5
IXL-101
3EM23956AM
Issue 01, February 2013
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 definitions
Location
Syntax
Values
Description
Facility
Name
DS-1-in, out
DS-3-in, out
EleSdh-in
OptSdh-in
MAU
Ethernet signal
Radio
Radio facility
Dir#[3-8].[1-4]
Dir#1.[1-6]
Dir#[3-8].[5-8]
Dir#1.[5-6]
Dir#[3-8]
board#[1-9]
Radio
Direction
Board
rd
b#[1-9]
Slot#[1-9]
MSS/CORE
MSS/DS1
Port
Number
3-6
Port#[1-16]
Port#[1-32]
Port#[1-2]
Port#[1-2]
Port#[1-6]
Port#[1-8]
IXL-101
3EM23956AM
Issue 01, February 2013
Syntax
Values
Description
Channel
Number
Ch#1
Ch#0
ERPS
ERP
ERP[1-2]#[1-2]
The following are examples to illustrate how to interpret the probable cause and friendly name
combinations:
Example: Probable Cause: Replaceable Unit Missing
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]
3-7
IXL-101
3EM23956AM
Issue 01, February 2013
Translation: DS1-input, slot #5, Port #22 [Loss Of incoming DS1 Signal, on
P32E1DS1 card in slot #5, port #22]
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)]
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 types
Probable
cause
Friendly name/entity
Facility/
equipment
AIS
DS1-in/MSS/DS1/Port#[1-16] DS1 on
MSS-1 shelf
DS1-in/Slot#[3-8]/Port#[1-32] DS1 on
P32E1DS1
DS3-in/Slot#[3-8]/Port#[1-2]
3-8
Description
See
DS3
IXL-101
3EM23956AM
Issue 01, February 2013
Friendly name/entity
Facility/
equipment
AIS
EleSdh-in/slot#[3-8]/Port[1-2] OC-3
OptSdh-in/slot#[3-8]/Port[1-2]
AIS
DS1-out/MSS/DS1/Port#[116]
DS1 on
MSS-1 shelf
DS1-out/Slot#[3-8]/Port#[132]
DS1 on
P32E1DS1
DS3-out/Slot#[3-8]/Port#[1-2] DS3
AIS
EleSdh-out/slot#[3-8]/
Port[1-2]
OC-3
OptSdh-out/slot#[3-8]/
Port[1-2]
ATPC loop
problem
Bandwidth
degrade for
protection
switch
Description
See
TAP-100
TAP-100
TAP-110
MPT ODU
Reported for a ATPC High
connected to Power Time-out. When
Core-E
ATPC is enabled, the local
transmitter was operating
Radio/Dir#1.[1-6]/MSS/
MPT ODU
CORE/Port#[1-6]/Ch#[0-1]
connected to continuously at full power for
MSS/CORE 5 minutes, and the
transmitter was reduced to its
Radio/Dir#[3-8].[1-4]/
MPT ODU
minimum power setting and
Slot#[3-8]/Port#[1-4]/Ch#[0-1] connected to this condition notification was
MPTACC
generated. This condition will
Radio/Dir#[3-8].[5-8]/
MPT ODU
remain active until a
Slot#[3-8]/Port#[5-8]/Ch#1
connected to message is received that the
P8ETH
active receiver at the other
end of the link is no longer
Radio/Dir#[3-8].[5-8]/
MPT-HL
Slot#[3-8]/Port#[5-8]/Ch#[0-1] connected to requesting additional
transmitter power.
P8ETH
Radio/Dir#1.[1-6]/
Slot#1/Port#[1-6]/Ch#[0-1]
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]
MOD300
ERP#[1-2]#[1-2]
Core-E
TAP-105
3-9
IXL-101
3EM23956AM
Issue 01, February 2013
Friendly name/entity
Facility/
equipment
Description
See
MPT-HL
connected to
Core-E
Radio/Dir#1.[5-6]/MSS/
CORE/Port#[5-6]/Ch#1
MPT-HL
connected to
MSS/CORE
Battery failure
r01/subrack#1
MSS-1/4/8
Cable LOS
r01s1/board#[3-8]
MOD300
CLA
Radio/Dir#[3-8].[1-4]/
MPT ODU
The standby transmitter
TAP-104
Slot#[3-8]/Port#[1-4]/Ch#[0-1] connected to has/had a silent failure which
MPTACC
caused the far end to request
a HSB switch.
Radio/Dir#1.[1-6]/
MPT ODU
Slot#1/Port#[1-6]/Ch#[0-1]
connected to
Core-E
Radio/Dir#1.[1-6]/MSS/
CORE/Port#[1-6]/Ch#[0-1]
MPT ODU
connected to
MSS/CORE
TAP-102
Radio/Dir#[3-8].[5-8]/
MPT-HL
Slot#[3-8]/Port#[5-8]/Ch#[0-1] connected to
P8ETH
Radio/Dir#[3-8]/Ch#[0-1]
3-10
MOD300
IXL-101
3EM23956AM
Issue 01, February 2013
Friendly name/entity
Facility/
equipment
Description
See
Clock failure
Radio/Dir#1.[1-6]/
Slot#1/Port#[1-6]/Ch#[0-1]
MPT ODU
The MPT ODU/MPT-HL is
TAP-119
connected to not able to lock the air Tx
Core-E
symbol rate to the NE clock.
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]/
MPT ODU
Slot#[3-8]/Port#[1-4]/Ch#[0-1] connected to
MPTACC
Radio/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#1
MPT ODU
connected to
P8ETH
MPT-HL
Radio/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#[0-1] connected to
P8ETH
Degrade
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
Sync-in/Port#1
Core-E
Radio/Dir#[3-8]/Ch#[0-1]
Radio/Dir#1.[1-6]/
Slot#1/Port#[1-6]/Ch#1
Radio/Dir#1.[1-6]/MSS/
CORE/Port#[1-6]/Ch#1
Radio/Dir#[3-8].[1-4]/
Slot#[3-8]/Port#[1-4]/Ch#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
3-11
IXL-101
3EM23956AM
Issue 01, February 2013
Friendly name/entity
Facility/
equipment
Degrade
(cont.)
Radio/Dir#[3-8].[5-8]/
MPT-HL
Slot#[3-8]/Port#[5-8]/Ch#[0-1] 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
RadioLAG#[1-14]
MPT ODU
connected to
P8ETH,
MPT-HL
connected to
P8ETH
Description
See
TAP-109
DS1-in/Slot#[3-8]/Port#[1-32] P32E1DS1
EleSdh-in/slot#[3-8]/Port[1-2] OC-3
OptSdh-in/slot#[3-8]/Port[1-2]
Degrade
RadioLAG#[1-14]
ODU
Degrade
EthLAG#[1-14]
Core-E,
MSS/CORE
RadioLAG#[1-14]
MPT ODU,
MPT-HL,
ODU
MPT ODU
Bad or missing cable/cable
connected to connection at XPIC
Core-E,
connector on MPT ODU.
MSS/CORE
TAP-117
TAP-111
3-12
IXL-101
3EM23956AM
Issue 01, February 2013
Friendly name/entity
Facility/
equipment
Demodulator
fail
Radio/Dir#[3-8].[1-4]/
MPT ODU
Loss of receive signal, bad
Slot#[3-8]/Port#[1-4]/Ch#[0-1] connected to receive signal, or internal
MPTACC
receive circuit failure.
Radio/Dir#1.[1-6]/
Slot#1/Port#[1-6]/Ch#[0-1]
MPT ODU
connected to
Core-E
Radio/Dir#1.[1-6]/MSS/
CORE/Port#[1-6]/Ch#[0-1]
MPT ODU
connected to
MSS/CORE
Description
See
TAP-104
Radio/Dir#[3-8].[5-8]/
MPT-HL
Slot#[3-8]/Port#[5-8]/Ch#[0-1] connected to
P8ETH
Dialog failure
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
r01/subrack#1[1-6]
MPT ODU
Temporary Loss of
connected to communication with
Core-E,
MPT ODU/MPT-HL
MSS/CORE
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
TAP-107
3-13
IXL-101
3EM23956AM
Issue 01, February 2013
Friendly name/entity
Facility/
equipment
Duplicate
address
detected
TMNEthernet/MngtPort
Duplicate
address
detected
3-14
TMNEthernet/Port#4
TMNInBand#[1-2]
Core-E/TMN
In-Band Port
[1-2]
PPP-IP/RF#[3-8]
MOD300
PPP-IP/RF#1[1-6]
Description
See
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
IXL-101
3EM23956AM
Issue 01, February 2013
Friendly name/entity
Facility/
equipment
Description
Early warning
indication
Radio/Dir#1.[1-6]/
Slot#1/Port#[1-6]/Ch#[0-1]
MPT ODU
10E-9 BER detected
connected to
Core-E
Radio/Dir#1.[1-6]/MSS/
CORE/Port#[1-6]/Ch#[0-1]
MPT ODU
connected to
MSS/CORE
See
TAP-104
Radio/Dir#[3-8].[1-4]/
MPT ODU
Slot#[3-8]/Port#[1-4]/Ch#[0-1] connected to
MPTACC
Radio/Dir#[3-8].[5-8]/
MPT ODU
Slot#[3-8]/Port#[5-8]/Ch#[0-1] connected to
P8ETH
Radio/Dir#[3-8].[5-8]/
MPT-HL
Slot#[3-8]/Port#[5-8]/Ch#[0-1] 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]
MOD300
Core-E,
MSS/CORE
Eth OAM
MisMerge
condition
MEP#MDID[1-16]#MA ID
[1-512]#MEPID[1-8191]
Core-E,
MSS/CORE
Eth OAM
remote defect
indication
MEP#MDID[1-16]#MA ID
[1-512]#MEPID[1-8191]
Core-E,
MSS/CORE
Eth OAM
unexpected
level
MEP#MDID[1-16]#MA ID
[1-512]#MEPID[1-8191]
Core-E,
MSS/CORE
Eth OAM
unexpectedME
PID
MEP#MDID[1-16]#MA ID
[1-512]#MEPID[1-8191]
Core-E,
MSS/CORE
TAP-118
3-15
IXL-101
3EM23956AM
Issue 01, February 2013
Friendly name/entity
Facility/
equipment
Description
Eth OAM
unexpected
period
MEP#MDID[1-16]#MA ID
[1-512]#MEPID[1-8191]
Core-E,
MSS/CORE
Excessive
environmental
temperature
r01/subrack#[3-8][5-8]
MPT-HL
Excessive temperature on
connected to MPT-HL Transceiver
P8ETH
r01/subrack#1[5-6]
MPT-HL
connected to
Core-E,
MSS/CORE
r01/subrack#[3-8][5-8]
MPT-HL
Failure or Missing MPT-HL
connected to Transceiver Fan Unit
P8ETH
detected
r01/subrack#1[5-6]
MPT-HL
connected to
Core-E,
MSS/CORE
3-16
See
TAP-103
TAP-103
IXL-101
3EM23956AM
Issue 01, February 2013
Friendly name/entity
Facility/
equipment
Description
See
Firmware
Download
On Going
r01s1/board#[8]
AUX
r01s1/board#[1-2]
Core-E
r01s1/board#[3-8]
MOD300,
MPTACC,
P2E3DS3,
P8ETH,
P32E1DS1,
SDHACC
Download Status. A
download of an FPGA or
other software unit on the
addressed card.
No
action
required.
r01/subrack#[3-8]
ODU300
r01/subrack#1[1-6]
MPT ODU
connected to
Core-E
r01/subrack#[3-8][1-4]
MPT ODU
connected to
MPTACC
r01/subrack#[3-8][5-8]
MPT ODU
connected to
P8ETH
r01/subrack#1[5-6]
MPT-HL
connected to
Core-E
r01/subrack#[3-8][5-8]
MPT-HL
connected to
P8ETH
3-17
IXL-101
3EM23956AM
Issue 01, February 2013
Friendly name/entity
Facility/
equipment
High BER
TAP-104
Radio/Dir#[3-8].[1-4]/
MPT ODU
Bit Error Rate threshold
Slot#[3-8]/Port#[1-4]/Ch#[0-1] connected to (10E-4) exceeded on receiver
MPTACC
input circuits on MOD300/
MPT ODU/MPT-HL card.
Radio/Dir#1.[1-6]/
MPT ODU
Slot#1/Port#[1-6]/Ch#[0-1]
connected to
Core-E
Radio/Dir#1.[1-6]/MSS/
CORE/Port#[1-6]/Ch#[0-1]
MPT ODU
connected to
MSS/CORE
Radio/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#1
MPT ODU
connected to
P8ETH
Description
See
Radio/Dir#[3-8].[5-8]/
MPT-HL
Slot#[3-8]/Port#[5-8]/Ch#[0-1] connected to
P8ETH
High BER
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]
MOD300
EleSdh-in/slot#[3-8]/Port[1-2] OC-3
OptSdh-in/slot#[3-8]/Port[1-2]
High BER
OC-3
TAP-100
Bit Error Rate threshold
-5
(10E ) exceeded on transmit
output circuits on SDHACC
card to the demarcation
panel for the OC-3 facility.
ExtPt/Input#[1-6]
AUX
ExtPt/Input#[11-14]
Fan
ExtPt/Input#[11-14]
MSS-1
EleSdh-out/slot#[3-8]/
Port[1-2]
OptSdh-out/slot#[3-8]/
Port[1-2]
Housekeeping
alarm
3-18
TAP-100
Bit Error Rate threshold
-5
(10E ) exceeded on receiver
input circuits on SDHACC
card from demarcation panel
for the OC-3 facility.
IXL-101
3EM23956AM
Issue 01, February 2013
Friendly name/entity
Facility/
equipment
Description
Incompatible
frequency
Radio/Dir#1.[1-6]/
Slot#1/Port#[1-6]/Ch#[0-1]
MPT ODU
Configured frequency is
connected to outside of the supported
Core-E
frequency range.
Radio/Dir#1.[1-6]/MSS/
CORE/Port#[1-6]/Ch#[0-1]
MPT ODU
connected to
MSS/CORE
See
TAP-104
Radio/Dir#[3-8].[1-4]/
MPT ODU
Slot#[3-8]/Port#[1-4]/Ch#[0-1] connected to
MPTACC
Radio/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#1
MPT ODU
connected to
P8ETH
MPT-HL
Radio/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#[0-1] 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]
ODU300
3-19
IXL-101
3EM23956AM
Issue 01, February 2013
Friendly name/entity
Facility/
equipment
Incompatible
modulation
Radio/Dir#[3-8].[1-4]/
MPT ODU
Configured modulation is not TAP-104
Slot#[3-8]/Port#[1-4]/Ch#[0-1] connected to supported by MPT ODU,
MPTACC
MPT-HL, or ODU300.
Radio/Dir#1.[1-6]/
Slot#1/Port#[1-6]/Ch#[0-1]
MPT ODU
connected to
Core-E
Radio/Dir#1.[1-6]/MSS/
CORE/Port#[1-6]/Ch#[0-1]
MPT ODU
connected to
MSS/CORE
Radio/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#1
MPT ODU
connected to
P8ETH
Description
See
MPT-HL
Radio/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#[0-1] connected to
P8ETH
Incompatible
protection
3-20
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].[1-4]/
MPT ODU
Incorrectly configured or
Slot#[3-8]/Port#[1-4]/Ch#[0-1] connected to missing RPS/XPIC module
MPTACC
on MPT ODU.
Radio/Dir#1.[1-6]/
Slot#1/Port#[1-6]/Ch#[0-1]
MPT ODU
connected to
Core-E
Radio/Dir#1.[1-6]/MSS/
CORE/Port#[1-6]/Ch#[0-1]
MPT ODU
connected to
MSS/CORE
TAP-104
IXL-101
3EM23956AM
Issue 01, February 2013
Friendly name/entity
Facility/
equipment
Incompatible
shifter
Radio/Dir#[3-8].[1-4]/
MPT ODU
Configured shifter value not
Slot#[3-8]/Port#[1-4]/Ch#[0-1] connected to supported by MPT ODU,
MPTACC
MPT-HL, or ODU300.
Radio/Dir#1.[1-6]/
Slot#1/Port#[1-6]/Ch#[0-1]
MPT ODU
connected to
Core-E
Radio/Dir#1.[1-6]/MSS/
CORE/Port#[1-6]/Ch#[0-1]
MPT ODU
connected to
MSS/CORE
Radio/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#1
MPT ODU
connected to
P8ETH
Description
See
TAP-104
MPT-HL
Radio/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#[0-1] connected to
P8ETH
Incompatible
power
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]
ODU300
Radio/Dir#[3-8].[5-8]/
MPT-HL
Configured Tx power value
Slot#[3-8]/Port#[5-8]/Ch#[0-1] connected to not supported by MPT-HL.
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
TAP-104
3-21
IXL-101
3EM23956AM
Issue 01, February 2013
Friendly name/entity
Facility/
equipment
Description
Incompatible TX Radio/Dir#[3-8].[1-4]/
MPT ODU
Configured Tx power value
power
Slot#[3-8]/Port#[1-4]/Ch#[0-1] connected to not supported by MPT ODU
MPTACC
or ODU300.
Radio/Dir#1.[1-6]/
Slot#1/Port#[1-6]/Ch#[0-1]
MPT ODU
connected to
Core-E
Radio/Dir#1.[1-6]/MSS/
CORE/Port#[1-6]/Ch#[0-1]
MPT ODU
connected to
MSS/CORE
Radio/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#1
MPT ODU
connected to
P8ETH
Radio/Dir#[3-8]/Ch#[0-1]
ODU300
Internal
r01/subrack#1[1-6]
communication
problem
3-22
See
TAP-104
MPT ODU
Loss of communications with TAP-107
connected to MPT ODU, MPT-HL, or
Core-E,
ODU300.
MSS/CORE
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
r01/subrack#[3-8]
ODU300
IXL-101
3EM23956AM
Issue 01, February 2013
Friendly name/entity
Facility/
equipment
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]
MPT ODU
Link identifier number
TAP-104
connected to provisioned on MOD300/
MPTACC
MPT ODU/MPT-HL card
settings screen is different
from link identifier number
MPT ODU
connected to provisioned at far end of hop.
AirFrame/Dir#1.[1-6]/
Slot#1/Port#[1-6]/Ch#1,
AirFrame/Dir#1.[1-6]/
Slot#1/Port#[1-6]
See
Core-E
AirFrame/Dir#1.[1-6]/MSS/
CORE/Port#[1-6]/Ch#1,
AirFrame/Dir#1.[1-6]/MSS/
CORE/Port#[1-6]
MPT ODU
connected to
MSS/CORE
AirFrame/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#1
MPT ODU
connected to
P8ETH
AirFrame/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#1,
AirFrame/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]
MPT-HL
connected to
P8ETH
AirFrame/Dir#1.[5-6]/
Slot#1/Port#[5-6]
MPT-HL
connected to
Core-E
AirFrame/Dir#1.[5-6]/MSS/
CORE/Port#[5-6]
MPT-HL
connected to
MSS/CORE
AirFrame/Dir#[3-8]/Ch#1,
AirFrame/Dir#[3-8]
MOD300
Description
3-23
IXL-101
3EM23956AM
Issue 01, February 2013
Friendly name/entity
Facility/
equipment
Description
See
Loop problem
Radio/Dir#1.[1-6]/
Slot#1/Port#[1-6]/Ch#[0-1]
MPT ODU
Loss of ATPC command path TAP-110
connected to between far end transmitter
Core-E
and local receiver.
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]/
MPT ODU
Slot#[3-8]/Port#[1-4]/Ch#[0-1] connected to
MPTACC
Radio/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#1
MPT ODU
connected to
P8ETH
MPT-HL
Radio/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#[0-1] connected to
P8ETH
Loss of
alignment
3-24
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
Hitless/Dir#[3-8].[1-4]
MPT ODU
Delay/loss of alignment
connected to between main and protect
MPTACC
RPS RF paths detected.
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
TAP-112
IXL-101
3EM23956AM
Issue 01, February 2013
Friendly name/entity
Loss Ethernet
MAU/Slot#[1-2]/Port#[1-6]
synchronization Radio/Dir#[3-8]/Ch#[0-1]
messaging
RadioLAG#[1-14]
channel
Radio/Dir#1.[1-6]/
Slot#1/Port#[1-6]/Ch#[0-1]
Radio/Dir#1.[1-6]/MSS/
CORE/Port#[1-6]/Ch#[0-1]
Facility/
equipment
Description
See
Core-E
Radio/Dir#[3-8].[1-4]/
MPT ODU
Slot#[3-8]/Port#[1-4]/Ch#[0-1] connected to
MPTACC
Radio/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#1
MPT ODU
connected to
P8ETH
Radio/Dir#[3-8].[5-8]/
MPT-HL
Slot#[3-8]/Port#[5-8]/Ch#[0-1] connected to
P8ETH
Loss Of
CESoETH
frame
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
CircuitTDM/MSS/DS1/
Port#[1-16]
DS1 on
MSS-1 shelf
CircuitTDM/Slot#[3-8]/
Port#[1-32]
DS1 on
P32E1DS1
CircuitTDM/Slot#[3-8]/
Port#[1-2]
DS3
CircuitTDM/Slot#[3-8]/
Port#[1-2]
OC-3
3-25
IXL-101
3EM23956AM
Issue 01, February 2013
Friendly name/entity
Facility/
equipment
Loss Of Frame
DS1-in/MSS/DS1/Port#[1-16] DS1 on
MSS-1 shelf
DS1-in/Slot#[3-8]/Port#[1-32] DS1 on
P32E1DS1
DS3-in/Slot#[3-8]/Port#[1-2]
DS3
Description
See
TAP-100
TAP-100
EleSdh-in/slot#[3-8]/Port[1-2] OC-3
OptSdh-in/slot#[3-8]/Port[1-2]
Loss of frame
DS1-out/Slot#[3-8]/
Port#[1-32]
DS1/
P32E1DS1
DS3-out/Slot#[3-8]/Port#[1-2] DS3
EleSdh-out/slot#[3-8]/
Port[1-2]
OC-3
OptSdh-out/slot#[3-8]/
Port[1-2]
Loss of frame
Radio/Dir#1.[1-6]/
Slot#1/Port#[1-6]/Ch#[0-1]
Radio/Dir#1.[1-6]/MSS/
CORE/Port#[1-6]/Ch#[0-1]
TAP-113
MPT ODU
Far end TX problems, RF
connected to path problems, or local circuit
Core-E
failures have caused BER to
increase to the point that
MPT ODU
connected to frames are being lost.
MSS/CORE
Radio/Dir#[3-8].[1-4]/
MPT ODU
Slot#[3-8]/Port#[1-4]/Ch#[0-1] connected to
MPTACC
Radio/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#1
MPT ODU
connected to
P8ETH
Radio/Dir#[3-8].[5-8]/
MPT-HL
Slot#[3-8]/Port#[5-8]/Ch#[0-1] connected to
P8ETH
3-26
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]
MOD300
IXL-101
3EM23956AM
Issue 01, February 2013
Friendly name/entity
Facility/
equipment
Loss of
protection
Radio/Dir#[3-8]/Ch#1
MOD300
Radio/Dir#[3-8].[1-4]/
Slot#[3-8]/Port#[1-4]/Ch#1
Radio/Dir#1.[1-6]/
Slot#1/Port#[1-6]/Ch#1
Radio/Dir#1.[1-6]/MSS/
CORE/Port#[1-6]/Ch#1
Loss of signal
Description
See
DS1-in/MSS/DS1/Port#[1-16] DS1 on
MSS-1 shelf
DS1-in/Slot#[3-8]/Port#[1-32] DS1 on
P32E1DS1
DS3-in/Slot#[3-8]/Port#[1-2]
DS3
EleSdh-in/slot#[3-8]/Port[1-2] OC-3
OptSdh-in/slot#[3-8]/Port[1-2]
Loss of signal
ETHInterface#100
ETHInterfaceonCore#4
MAU/Slot#[1-2]/Port#[1-6]
MAU/MSS/CORE/Port#[1-6]
MAU/Slot#[3-8]/Port#[1-4]
MAU/Slot#[3-8]/Port#[1-8]
Loss of signal
r01s1[1-6]b1/daughter#03
RPS SFP on
MPT ODU
connected to
Core-E,
MSS/CORE
MAU/subrack[#3-8].[1-4]
daughter#03
MPT ODU
Loss of Signal detected on an TAP-104
connected to MPT ODU/MPT-HL Ethernet
MPTACC
Coupler Port. Only reported
when RPS is provisioned.
MPT-HL
MAU/subrack[#3-8].[5-8]
Port#n
Loss of signal
Sync-in/Port#1
connected to
P8ETH
Core-E
3-27
IXL-101
3EM23956AM
Issue 01, February 2013
Friendly name/entity
Facility/
equipment
Description
Loss of signal
EthLAG#[1-14]
Core-E,
MSS/CORE
RadioLAG#[1-14]
MPT ODU,
MPT-HL,
ODU
r01/subrack#[3-8][1-4]
MPTACC
r01/subrack#1[1-2]
MSS/Core
PPP-IP/RF#1[1-6]
MPT ODU
TMN over PPP Fail
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#[3-8]
MOD300
r01s1/board#[1-2]
Core-E
r01s1/board#1
MSS/CORE
Power supply
failure
PPP fail
Provisioning
mismatch
3-28
See
TAP-102
TAP-104
IXL-101
3EM23956AM
Issue 01, February 2013
Friendly name/entity
Facility/
equipment
Description
See
Replaceable
unit missing
r01s1/board#[8]
AUX
r01s1/board#[1-2]
Core-E
r01s1/board#[5,9]
FAN
r01s1/board#[3-8]
MOD300,
MPTACC,
P2E3DS3,
P8ETH,
P32E1DS1,
SDHACC
r01s1b[1-2]/daughter#[5-6]
SFP on
Core-E
r01s1b1/daughter#[5-6]
SFP on
MSS/CORE
r01s1b[3-8]/daughter#[03-04] SFP on
MPTACC
r01s1b[3-8]/daughter#[05-08] SFP on
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 ODU
connected to
Core-E,
MSS/CORE
3-29
IXL-101
3EM23956AM
Issue 01, February 2013
Friendly name/entity
Facility/
equipment
Description
See
Replaceable
unit problem
r01s1/board#[8]
AUX
Card failed.
TAP-103
r01s1/board#[1-2]
Core-E
r01s1/board#[5,9]
FAN
r01s1/board#[3-8]
MOD300,
MPTACC,
P2E3DS3,
P8ETH,
P32E1DS1,
SDHACC
r01/subrack#1[1-6]
MPT ODU
connected to
Core-E,
MSS/CORE
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
r01/subrack#[3-8]
ODU300
r01/subrack#[3-8][1-4]
MPT ODU
connected to
MPTACC
r01s1b[1-2]/daughter#[05-06] SFP on
Core-E
r01s1b1/daughter#[05-06]
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
3-30
IXL-101
3EM23956AM
Issue 01, February 2013
Friendly name/entity
Facility/
equipment
Replaceable
unit problem
(cont.)
RPS SFP on
MPT ODU
connected to
Core-E,
MSS/CORE
r01s1[1-6]b1/daughter#04
RPS or XPIC
Module on
MPT ODU
connected to
Core-E,
MSS/CORE
r01/subrack#[3-8][5-8]/
daughter#04
XPIC Module
on MPT ODU
connected to
P8ETH
Description
See
TAP-103
3-31
IXL-101
3EM23956AM
Issue 01, February 2013
Friendly name/entity
Facility/
equipment
Description
Replaceable
unit type
mismatch
r01s1/board#[8]
AUX
r01s1/board#[1-2]
Core-E
r01s1/board#[5,9]
FAN
r01s1/board#[3-8]
MOD300,
MPTACC,
P2E3DS3,
P8ETH,
P32E1DS1,
SDHACC
r01/subrack#1[1-6]
MPT ODU
connected to
Core-E,
MSS/CORE
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
r01/subrack#[3-8]
ODU300
3-32
See
IXL-101
3EM23956AM
Issue 01, February 2013
Friendly name/entity
Remote defect
indication
TAP-104
Radio/Dir#[3-8].[1-4]/
MPT ODU
Remote Defect Indication
Slot#[3-8]/Port#[1-4]/Ch#[0-1] connected to (RDI) in a received Radio
MPTACC
Direction. Alarm is reported
when an RDI is received
Radio/Dir#1.[1-6]/
MPT ODU
Slot#1/Port#[1-6]/Ch#[0-1]
connected to on a given radio direction
from the remote end of radio
Core-E
link.
Radio/Dir#1.[1-6]/MSS/
MPT ODU
CORE/Port#[1-6]/Ch#[0-1]
connected to
MSS/CORE
Radio/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#1
Facility/
equipment
Description
See
MPT ODU
connected to
P8ETH
Radio/Dir#[3-8].[5-8]/
MPT-HL
Slot#[3-8]/Port#[5-8]/Ch#[0-1] connected to
P8ETH
Remote defect
indication
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]
MOD300
EleSdh-in/slot#[3-8]/Port[1-2] OC-3
OptSdh-in/slot#[3-8]/Port[1-2]
RadioProt/Dir#[3-8][1-4]
RadioProt/Dir#1[1-6]
TAP-100
Remote Defect Indication
(RDI) in a received OC-3
Direction. Alarm is reported
when an RDI is received
on a given OC-3 direction
from the remote end of OC-3
link.
MPT ODU
A communication failure is
TAP-114
connected to detected between
MPTACC
MPT ODUs. Only reported
for an MPT ODUs working in
MPT ODU
connected to 1+1 configuration with Virtual
Protection.
Core-E,
MSS/CORE
RadioProt/Dir#[3-8][5-8]
MPT-HL
Communication failure is
connected to detected between RPS
P8ETH
coupler port between radio
boards. Only reported if RPS
is provisioned.
3-33
IXL-101
3EM23956AM
Issue 01, February 2013
Friendly name/entity
Facility/
equipment
Description
Rx fail
Radio/Dir#[3-8]/Ch#[0-1]
ODU300
Secondary
battery failure
r01/subrack#1
MSS-1/4/8
MPT ODU
connected to
Core-E,
MSS/CORE
3-34
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
See
TAP-102
IXL-101
3EM23956AM
Issue 01, February 2013
Friendly name/entity
Synchronization Sync-in/Port#1
signal fail
Radio/Dir#[3-8]/Ch#[0-1]
Radio/Dir#1.[1-6]/
Slot#1/Port#[1-6]/Ch#1
Radio/Dir#1.[1-6]/MSS/
CORE/Port#[1-6]/Ch#1
Facility/
equipment
Description
See
Core-E
Radio/Dir#[3-8].[1-4]/
Slot#[3-8]/Port#[1-4]/Ch#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
Radio/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#1
MPT-HL
connected to
P8ETH
Radio/Dir#1.[1-6]/
Slot#1/Port#[1-6]/Ch#1
MPT-HL
connected to
Core-E
Radio/Dir#1.[1-6]/MSS/
CORE/Port#[1-6]/Ch#1
MPT-HL
connected to
MSS/CORE
RadioLAG#[1-14]
MPT ODU,
MPT-HL
DS1-in/Slot#[3-8]/Port#[1-32] P32E1DS1
EleSdh-in/slot#[3-8]/Port[1-2] OC-3
OptSdh-in/slot#[3-8]/Port[1-2]
3-35
IXL-101
3EM23956AM
Issue 01, February 2013
Friendly name/entity
Facility/
equipment
Description
Threshold
crossed
Hop/Dir#1[1-6]/Slot#1/
MPT ODU
Threshold Crossing Alarm
Port#[1-6]/Ch#[0-1]-PM15min connected to (TCA) indicates alarm
Core-E
threshold has been
Hop/Dir#1[1-6]/Slot#1/
exceeded. Applies to
Port#[1-6]/Ch#[0-1]-PM1day
performance monitor
Link/Dir#1[1-6]-PM15min
parameters with an
Link/Dir#1[1-6]-PM1day
accumulation period of 24
hours and 15 minutes.
Hop/Dir#1[1-6]/MSS/CORE/ MPT ODU
Port#[1-6]/Ch#[0-1]-PM15min connected to
Hop/Dir#1[1-6]/MSS/CORE/ MSS/CORE
See
TAP-108
Port#[1-6]/Ch#[0-1]-PM1day
Link/Dir#1[1-6]-PM15min
Link/Dir#1[1-6]-PM1day
Hop/Dir#[3-8][1-4]/Slot#[3-8]/ MPT ODU
Port#[1-4]/Ch#[0-1]-PM15min connected to
Hop/Dir#[3-8][1-4]/Slot#[3-8]/ MPTACC
Port#[1-4]/Ch#[0-1]-PM1day
Link/Dir#[3-8][1-4]-PM15min
Link/Dir#[3-8][1-4]-PM1day
Hop/Dir#[3-8][5-8]/Slot#[3-8]/ MPT ODU
Port#[5-8]/Ch#1-PM15min
connected to
Hop/Dir#[3-8][5-8]/Slot#[3-8]/ P8ETH
Port#[5-8]/Ch#1-PM1day
Hop/Dir#[3-8][5-8]/Slot#[3-8]/ MPT-HL
Port#[5-8]/Ch#[0-1]-PM15min connected to
Hop/Dir#[3-8][5-8]/Slot#[3-8]/ P8ETH
Port#[5-8]/Ch#[0-1]-PM1day
Link/Dir#[3-8][5-8]-PM15min
Link/Dir#[3-8][5-8]-PM1day
Hop/Dir#1[5-6]/Slot#1/
Port#[5-6]/Ch#1-PM15min
Hop/Dir#1[5-6]/Slot#1/
Port#[5-6]/Ch#1-PM1day
Hop/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
3-36
MPT-HL
connected to
Core-E
MPT-HL
connected to
MSS/CORE
IXL-101
3EM23956AM
Issue 01, February 2013
Friendly name/entity
Facility/
equipment
Description
See
Threshold
crossed
(cont.)
Hop/Dir#[3-8]/Ch#[0-1]PM15min
MOD300
TAP-108
Hop/Dir#[3-8]/Ch#[0-1]PM1day
Link/Dir#[3-8]-PM15min
Link/Dir#[3-8]-PM1day
DS1-in/Slot#[3-8]/
Port#[1-32]-PM15min
P32E1DS1
DS1-in/Slot#[3-8]/
Port#[1-32]-PM1day
DS1-out/Slot#[3-8]/
Port#[1-32]-PM15min
DS1-in/MSS/DS1/
Port#[1-16]-PM15min
DS1 on
MSS-1 shelf
DS1-in/MSS/DS1/
Port#[1-16]-PM1day
DS1-out/MSS/DS1/
Port#[1-16]-PM15min
DS1-out/MSS/DS1/
Port#[1-16]-PM1day
Trace identifier
mismatch
EleSdh-in/slot#[3-8]/Port[1-2] OC-3
OptSdh-in/slot#[3-8]/Port[1-2]
3-37
IXL-101
3EM23956AM
Issue 01, February 2013
Friendly name/entity
Facility/
equipment
Description
See
Unavailable
time
Hop/Dir#1[1-6]/Slot#1/
MPT ODU
A period of unavailable time TAP-108
Port#[1-6]/Ch#[0-1]-PM15min connected to begins when 10 consecutive
Core-E
SES events are detected.
Hop/Dir#1[1-6]/Slot#1/
Alarms are associated to the
Port#[1-6]/Ch#[0-1]-PM1day
performance monitoring port.
Link/Dir#1[1-6]-PM15min
Link/Dir#1[1-6]-PM1day
Hop/Dir#1[1-6]/MSS/CORE/ MPT ODU
Port#[1-6]/Ch#[0-1]-PM15min connected to
Hop/Dir#1[1-6]/MSS/CORE/ MSS/CORE
Port#[1-6]/Ch#[0-1]-PM1day
Link/Dir#1[1-6]-PM15min
Link/Dir#1[1-6]-PM1day
Hop/Dir#[3-8][1-4]/Slot#[3-8]/ MPT ODU
Port#[1-4]/Ch#[0-1]-PM15min connected to
Hop/Dir#[3-8][1-4]/Slot#[3-8]/ MPTACC
Port#[1-4]/Ch#[0-1]-PM1day
Link/Dir#[3-8][1-4]-PM15min
Link/Dir#[3-8][1-4]-PM1day
Hop/Dir#[3-8][5-8]/Slot#[3-8]/ MPT ODU
Port#[5-8]/Ch#1-PM15min
connected to
Hop/Dir#[3-8][5-8]/Slot#[3-8]/ P8ETH
Port#[5-8]/Ch#1-PM1day
Hop/Dir#[3-8][5-8]/Slot#[3-8]/ MPT-HL
Port#[5-8]/Ch#[0-1]-PM15min connected to
Hop/Dir#[3-8][5-8]/Slot#[3-8]/ P8ETH
Port#[5-8]/Ch#[0-1]-PM1day
Link/Dir#[3-8][5-8]-PM15min
Link/Dir#[3-8][5-8]-PM1day
Hop/Dir#1[5-6]/Slot#1/
Port#[5-6]/Ch#1-PM15min
Hop/Dir#1[5-6]/Slot#1/
Port#[5-6]/Ch#1-PM1day
Hop/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
3-38
MPT-HL
connected to
Core-E
MPT-HL
connected to
MSS/CORE
IXL-101
3EM23956AM
Issue 01, February 2013
Friendly name/entity
Facility/
equipment
Description
Unavailable
time
(cont.)
Hop/Dir#[3-8]/Ch#[0-1]PM15min
MOD300
Hop/Dir#[3-8]/Ch#[0-1]PM1day
Link/Dir#[3-8]-PM15min
See
Link/Dir#[3-8]-PM1day
DS1-in/Slot#[3-8]/Port#[1-32]- P32E1DS1
PM15min
DS1-in/Slot#[3-8]/Port#[1-32]PM1day
DS1-out/Slot#[3-8]/Port#[132]-PM15min
DS1-out/Slot#[3-8]/Port#[132]-PM1day
DS1-in/MSS/DS1/Port#[116]-PM15min
DS1 on
MSS-1 shelf
DS1-in/MSS/DS1/Port#[116]-PM1day
DS1-out/MSS/DS1/Port#[116]-PM15min
DS1-out/MSS/DS1/Port#[116]-PM1day
Unconfigured
equipment
present
r01s1/board#[8]
AUX
r01s1/board#[2]
Core-E
r01s1/board#[5,9]
FAN
r01s1/board#[3-8]
MOD300,
MPTACC,
P2E3DS3,
P8ETH,
P32E1DS1,
SDHACC
TAP-103
r01s1b[1-2]/daughter#[05-06] SFP on
Core-E
r01s1b1/daughter#[05-06]
SFP on
MSS/CORE
r01s1b[3-8]/daughter#[03-04] SFP on
MPTACC
3-39
IXL-101
3EM23956AM
Issue 01, February 2013
Friendly name/entity
Facility/
equipment
Unconfigured
equipment
present
(cont.)
r01s1b[3-8]/daughter#[05-08] SFP on
P8ETH
Version
mismatch
r01/subrack#1[1-6]
MPT ODU
connected to
Core-E,
MSS/CORE
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
r01/subrack#[3-8]
ODU300
r01s1/board#[1-2]
Core-E
r01s1b[3-8]/daughter#[01-02] SFP on
SDHACC
Description
See
TAP-103
Name
3-40
Type
(equipment)
Description
See
Loopback
The associated entity has a TAP-101
DS1 on MSS-1 core facing PDH (DS1 or
shelf
DS3) loopback activated at
the near end.
Loopback
SLOT#[3-8]
IXL-101
3EM23956AM
Issue 01, February 2013
Name
Type
(equipment)
Description
Digital core
facing loopback
Direction #1.[1-6]
Loopback
(MPT ODU
connected to
Core-E,
MSS/CORE)
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)
See
3-41
IXL-101
3EM23956AM
Issue 01, February 2013
Name
Type
(equipment)
Description
See
Forced adaptive
modulation
Direction #[3-8]
Radio
(MOD300)
TAP-101
Direction #1.[1-6]
Radio
(MPT ODU
connected to
Core-E,
MSS/CORE)
Manual Adaptive
Modulation command has
been executed.
Direction #[3-8].[1-4]
Radio
(MPT ODU
connected to
MPTACC)
Direction #[3-8].[5-8]
Radio
(MPT ODU
connected to
P8ETH)
Radio
(MPT-HL
connected to
P8ETH)
Direction #1.[5-6]
Loopback
(MPT-HL
connected to
Core-E,
MSS/CORE)
3-42
IXL-101
3EM23956AM
Issue 01, February 2013
Name
Type
(equipment)
Description
Forced switch
EPS
Main#1 Slot#1
Equipment
Protection
(Core-E)
Main#1 Slot#[3,5,7]
Equipment
Protection
(MOD300,
P2E3DS3,
P32E1DS1,
SDHACC)
A Forced Equipment
TAP-101
Protection Switch (EPS) has
been executed for the
protection group.
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)
Equipment
Protection
(MPT-HL
connected to
P8ETH)
See
3-43
IXL-101
3EM23956AM
Issue 01, February 2013
Name
Type
(equipment)
Description
See
Forced switch
RPS
Main#1 Slot#[3,5,7]
Rx Radio
Protection
(MOD300)
TAP-101
Rx Radio
Protection
(MPT ODU
connected to
MPTACC)
A Forced Rx Protection
Switch (RPS) has been
executed for the protection
group.
Main#1 Slot #1
Port #[1,3,5]
Rx Radio
Protection
(MPT ODU
connected to
Core-E)
Main#1 MSS/CORE
Port #[1,3,5]
Rx Radio
Protection
(MPT ODU
connected to
MSS/CORE)
Rx Radio
Protection
(MPT-HL
connected to
P8ETH)
3-44
IXL-101
3EM23956AM
Issue 01, February 2013
Name
Type
(equipment)
Description
See
Forced switch
TPS
Main#1 Slot#[3,5,7]
HSB
Protection
(MOD300)
TAP-101
HSB
Protection
(MPT ODU
connected to
MPTACC)
A Forced Tx Protection
Switch (TPS) has been
executed for the protection
group.
Main#1 Slot #1
Port #[1,3,5]
HSB
Protection
(MPT ODU
connected to
Core-E)
Main#1 MSS/CORE
Port #[1,3,5]
HSB
Protection
(MPT ODU
connected to
MSS/CORE)
HSB
Protection
(MPT-HL
connected to
P8ETH)
Loopback
(MOD300)
Loopback
(MPT ODU
connected to
Core-E,
MSS/CORE)
Direction #[3-8].[1-4]
Loopback
(MPT ODU
connected to
MPTACC)
Direction #[3-8].[5-8]
Loopback
(MPT ODU
connected to
P8ETH)
3-45
IXL-101
3EM23956AM
Issue 01, February 2013
Name
Type
(equipment)
Loopback
The associated entity has a TAP-101
DS1 on MSS-1 line facing PDH (DS1 or
shelf
DS3) loopback activated at
the near end.
Loopback
SLOT#[3-8]
Spare#0 Slot#2
Equipment
Protection
(Core-E)
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)
Lockout switch
EPS
3-46
Description
See
A Lockout Equipment
TAP-101
Protection Switch (EPS) has
been executed for the
protection group.
IXL-101
3EM23956AM
Issue 01, February 2013
Name
Type
(equipment)
Description
See
Lockout switch
RPS
Spare#0 Slot#[4,6,8]
Rx Radio
Protection
(MOD300)
TAP-101
Spare#0 Slot#[3-8]
Port #[1-4]
Rx Radio
Protection
(MPT ODU
connected to
MPTACC)
A Lockout Rx Protection
Switch (RPS) has been
executed for the protection
group.
Spare#0 Slot #1
Port #[2,4,6]
Rx Radio
Protection
(MPT ODU
connected to
Core-E)
Spare#0 MSS/CORE
Port #[2,4,6]
Rx Radio
Protection
(MPT ODU
connected to
MSS/CORE)
Spare#0 Slot#[4,6,8]
Port #[5-8]
Rx Radio
Protection
(MPT-HL
connected to
P8ETH)
3-47
IXL-101
3EM23956AM
Issue 01, February 2013
Name
Type
(equipment)
Description
See
Lockout switch
TPS
Spare#0 Slot#[4,6,8]
HSB
Protection
(MOD300)
TAP-101
Spare#0 Slot#[3-8]
Port #[1-4]
HSB
Protection
(MPT ODU
connected to
MPTACC)
A Lockout Tx Protection
Switch (TPS) has been
executed for the protection
group.
Spare#0 Slot #1
Port #[2,4,6]
HSB
Protection
(MPT ODU
connected to
Core-E)
Spare#0 MSS/CORE
Port #[2,4,6]
HSB
Protection
(MPT ODU
connected to
MSS/CORE)
Spare#0 Slot#[4,6,8]
Port #[5-8]
HSB
Protection
(MPT-HL
connected to
P8ETH)
3-48
IXL-101
3EM23956AM
Issue 01, February 2013
Name
Type
(equipment)
Description
See
TXMute
Radio
(MPT ODU
connected to
Core-E,
MSS/CORE)
TAP-101
Radio
(MPT ODU
connected to
MPTACC
Radio
(MPT ODU
connected to
P8ETH
Radio
(MPT-HL
connected to
P8ETH)
Radio
(MPT-HL
connected to
Core-E,
MSS/CORE)
Radio
(ODU300)
3-49
IXL-101
3EM23956AM
Issue 01, February 2013
Indication
Probable cause
Corrective action
Status
OFF
Provision card
Not Powered
Not Equipped
Green
Blinking
Configuration Downloading, SW
Booting, or flash card realignment.
Green
Yellow
Red
Card Fail
Replace card
Major
Alarm
Red
Minor
Alarm
Red
At least one alarm with Minor severity Retrieve alarms using the alarm
present in the NE.
monitor, see IXL-101 Table 101-C,
and troubleshoot accordingly.
Warning
Yellow
Abnormal Yellow
3-50
IXL-101
3EM23956AM
Issue 01, February 2013
Indication
Probable cause
Corrective action
Status
OFF
Green
Blinking
Configuration Downloading, SW
Booting.
Green
Red
Major
Alarm
Red
Minor
Alarm
Red
At least one alarm with Minor severity Retrieve alarms using the alarm
present in the NE.
monitor, see IXL-101 Table 101-C,
and troubleshoot accordingly.
Warning
Yellow
Abnormal Yellow
PFoE
Yellow
OFF
3-51
IXL-101
3EM23956AM
Issue 01, February 2013
Indication
Probable cause
Corrective action
Status
OFF
Provision card
Not Powered
Not Equipped
Green
Blinking
Configuration Downloading, SW
Booting, or flash card realignment.
Green
Yellow
Red
Card Fail
Replace card
Indication
Description
Probable cause
Corrective action
Connect/repair cable.
2. Speed/Mode
1. Check local Ethernet
provisioning mismatch
provisioning screen.
between link partner and 2. Check link partner
Ethernet port.
provisioning.
3-52
IXL-101
3EM23956AM
Issue 01, February 2013
Indication
Probable cause
Corrective action
Status
OFF
Provision card
Not Powered
Invalid Configuration
Green
Blinking
Configuration Downloading, or SW
Booting. (Different blink rates should
be used to identify each step of the
startup process.)
Green
Yellow
Green/Red
Blinking
PA switch at the far end is set to OFF 1. Verify PA switch position at far end
0 position:
and set to ON 1 position.
Yellow/Red
Blinking
3-53
IXL-101
3EM23956AM
Issue 01, February 2013
Indication
Probable cause
Corrective action
Status
(cont.)
Red
Card Fail
Power
Green LED
Emission ON
Green LED
Blinking
Green LED
OFF
1. TX mute active
Release TX mute
Possible Cause
Possible Solution
Unusually slow
communication in radio
network
3-54
IXL-101
3EM23956AM
Issue 01, February 2013
Possible Cause
Possible Solution
Unable to operate
controls using SNMP
3-55
3EM23956AM
Issue 01, February 2013
3-56
IXL-101
IXL-102
3EM23956AM
Issue 01, February 2013
IXL-102
Support procedures
Table 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 procedures
Support procedure
See
DLP-112
Manage cross-connections
Password change
Performance monitoring
Provision equipment
RTL-100
DLP-117
DLP-127
DLP-113
DLP-118
DLP-119
Support procedures
4-57
IXL-102
3EM23956AM
Issue 01, February 2013
DLP-123
DLP-124
4-58
Support procedures
IXL-103
3EM23956AM
Issue 01, February 2013
IXL-103
Equipment replacement procedures
Table 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 procedures
Equipment
See
DLP-120
DLP-116
DLP-103
DLP-104
DLP-105
DLP-100
DLP-128
DLP-106
DLP-101
DLP-108
ODU300 replacement
DLP-109
DLP-107
DLP-114
DLP-115
DLP-125
DLP-110
DLP-111
DLP-121
DLP-122
DLP-126
SFP replacement
DLP-102
5-59
3EM23956AM
Issue 01, February 2013
5-60
IXL-103
IXL-104
3EM23956AM
Issue 01, February 2013
IXL-104
Supporting information
Table 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 information
Supporting information
See
Card locations
Introduction
Electrostatic-sensitive devices
Introduction
Introduction
Laser precautions
Introduction
Maintenance philosophy
Introduction
Safety awareness
Introduction
Security/user authorization
Supporting information
6-61
3EM23956AM
Issue 01, February 2013
6-62
IXL-104
Supporting information
RTL-100
3EM23956AM
Issue 01, February 2013
RTL-100
Preventive maintenance procedures
There 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 procedures
Activity
Frequency
See
Every 6 months
DLP-101
7-1
3EM23956AM
Issue 01, February 2013
7-2
RTL-100
TAP-100
3EM23956AM
Issue 01, February 2013
TAP-100
Facility alarms
Purpose
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 alarms
8-1
TAP-100
3EM23956AM
Issue 01, February 2013
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
Review the output. See Table 100-A for information about facility alarms.
Table 100-A. Facility alarms
Probable cause
Friendly name/entity
Facility type
See
AIS
DS1-in/MSS/DS1/Port#[1-16]
DS1 (MSS/DS1)
Step 3
DS1-in/Slot#[3-8]/Port#[1-32]
DS1 (P32E1DS1)
DS3-in/Slot#[3-8]/Port#[1-2]
DS3
DS1-out/MSS/DS1/Port#[1-16]
DS1 (MSS/DS1)
DS1-out/Slot#[3-8]/Port#[1-32]
DS1 (P32E1DS1)
DS3-out/Slot#[3-8]/Port#[1-2]
DS3
EleSdh-in/slot#[3-8]/Port[1-2]
OC-3
Step 10
OC-3
Step 14
OC-3
Step 17
OC-3
Step 21
DS1 (MSS/DS1)
Step 24
AIS
AIS
Step 7
OptSdh-in/slot#[3-8]/Port[1-2]
AIS
EleSdh-out/slot#[3-8]/Port[1-2]
OptSdh-out/slot#[3-8]/Port[1-2]
High BER
EleSdh-in/slot#[3-8]/Port[1-2]
OptSdh-in/slot#[3-8]/Port[1-2]
High BER
EleSdh-out/slot#[3-8]/
Port[1-2]
OptSdh-out/slot#[3-8]/
Port[1-2]
Loss Of Frame
Loss of frame
Loss of frame
CircuitTDM/Slot#[3-8]/Port#[1-32]
DS1 (P32E1DS1)
CircuitTDM/Slot#[3-8]/Port#[1-2]
DS3
CircuitTDM/Slot#[3-8]/Port#[1-2]
OC-3
DS1-in/MSS/DS1/Port#[1-16]
DS1 (MSS/DS1)
DS1-in/Slot#[3-8]/Port#[1-32]
DS1 (P32E1DS1)
DS3-in/Slot#[3-8]/Port#[1-2]
DS3
DS1-out/MSS/DS1/Port#[1-16]
DS1 (MSS/DS1)
DS1-out/Slot#[3-8]/Port#[1-32]
DS1 (P32E1DS1)
DS3-out/Slot#[3-8]/Port#[1-2]
DS3
EleSdh-in/slot#[3-8]/Port[1-2]
OC-3
Step 77
Step 108
Step 77
OptSdh-in/slot#[3-8]/Port[1-2]
8-2
Facility alarms
TAP-100
3EM23956AM
Issue 01, February 2013
EleSdh-out/slot#[3-8]/Port[1-2]
OC-3OC-3
Step 108
DS1-in/MSS/DS1/Port#[1-16]
DS1 (MSS/DS1)
Step 155
DS1-in/Slot#[3-8]/Port#[1-32]
DS1 (P32E1DS1)
DS3-in/Slot#[3-8]/Port#[1-2]
DS3
EleSdh-in/slot#[3-8]/Port[1-2]
OC-3
Step 155
OC-3
Step 178
OC-3
Step 182
IXL-101
OptSdh-out/slot#[3-8]/Port[1-2]
Loss of signal
Loss of signal
OptSdh-in/slot#[3-8]/Port[1-2]
Remote defect indication EleSdh-in/slot#[3-8]/Port[1-2]
OptSdh-in/slot#[3-8]/Port[1-2]
Trace identifier mismatch EleSdh-in/slot#[3-8]/Port[1-2]
OptSdh-in/slot#[3-8]/Port[1-2]
None of the above
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.
Verify the cabling that is associated with the input DS1 or DS3 signal to the
P32E1DS1, P2E3DS3 cards, or MSS-1 shelf.
AIS
On DS1/3-out on DS1 or DS3 facility
7
Facility alarms
8-3
TAP-100
3EM23956AM
Issue 01, February 2013
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.
12
13
AIS
On EleSdh/EleSDH-out on OC-3 facility
14
15
16
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.
19
20
8-4
Facility alarms
TAP-100
3EM23956AM
Issue 01, February 2013
High BER
On EleSdh/EleSDH-out on OC-3 facility
21
22
23
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
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.
27
28
29
30
Verify the circuit provisioning for near end, the far end, and all intermediate NEs:
a.
b.
c.
d.
Facility alarms
8-5
TAP-100
3EM23956AM
Issue 01, February 2013
31
Verify the TDM2ETH provisioning for the near end, far end, and all intermediate NEs:
a.
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:
33
34
35
36
Verify that there are no active LAG alarms at all NEs in the LAG associated with the
facility in alarm.
37
38
39
40
Verify that there are no active RING alarms at all NEs in the ring associated with the
facility in alarm.
41
8-6
Facility alarms
TAP-100
42
3EM23956AM
Issue 01, February 2013
43
44
45
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.
47
48
49
Facility alarms
8-7
TAP-100
3EM23956AM
Issue 01, February 2013
51
52
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.
54
55
56
57
58
8-8
Facility alarms
TAP-100
3EM23956AM
Issue 01, February 2013
59
60
61
Reseat the card in alarm at the near end. Physically remove the card and reinsert.
62
63
64
65
66
67
68
Reseat the card in alarm at the far end. Physically remove the card and reinsert.
69
70
Facility alarms
8-9
TAP-100
3EM23956AM
Issue 01, February 2013
71
72
73
74
75
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.
79
80
8-10
Facility alarms
TAP-100
81
3EM23956AM
Issue 01, February 2013
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.
d.
Verify that the Service Profile is set the same and is correct.
e.
82
83
84
Verify that the Source Signal is error-free with a test set configured to match the
provisioning of the facility.
85
86
87
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.
88
89
Facility alarms
8-11
TAP-100
3EM23956AM
Issue 01, February 2013
90
91
92
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.
94
95
96
97
8-12
Facility alarms
TAP-100
98
3EM23956AM
Issue 01, February 2013
99
100
Reseat the card in alarm at near end. Physically remove card and reinsert.
101
102
103
104
105
106
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
Facility alarms
Check the far end facility for Loss of Frame (DS1/3-in, Ele/OptSdh-in) that is
associated with the facility in alarm.
8-13
TAP-100
3EM23956AM
Issue 01, February 2013
109
110
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
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.
114
115
116
117
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.
d.
Verify that the Service Profile is set the same and is correct.
8-14
Facility alarms
TAP-100
118
3EM23956AM
Issue 01, February 2013
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.
119
120
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.
b.
Verify that the MAC address is set the same and is correct.
c.
d.
122
123
124
Facility alarms
8-15
TAP-100
3EM23956AM
Issue 01, February 2013
125
126
127
128
129
130
131
8-16
Facility alarms
TAP-100
132
3EM23956AM
Issue 01, February 2013
133
134
135
136
137
138
139
Reseat card in alarm at near end. Physically remove card and reinsert.
140
Facility alarms
8-17
TAP-100
3EM23956AM
Issue 01, February 2013
141
142
143
144
145
146
Reseat the card in alarm at the far end. Physically remove the card and reinsert.
147
148
149
150
151
8-18
Facility alarms
TAP-100
152
3EM23956AM
Issue 01, February 2013
153
154
Go to step 190.
Loss of signal
DS1/3-in on DS1, DS3, or OC-3 facility
155
156
Verify cabling associated with the input signal to the MSS-1 shelf, P32E1DS1,
P2E3DS3, or SDHACC card.
157
158
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?
If yes, go to step 161.
If no, go to step 189.
161
Facility alarms
8-19
TAP-100
3EM23956AM
Issue 01, February 2013
162
163
164
165
166
167
168
169
170
Reseat the card that declared the Loss Of Signal alarm. Physically remove the card
and reinsert.
171
8-20
Facility alarms
TAP-100
172
3EM23956AM
Issue 01, February 2013
173
174
175
176
177
Go to step 190.
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.
180
181
Facility alarms
8-21
TAP-100
3EM23956AM
Issue 01, February 2013
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
185
186
Provision the Trace Identifier parameters according to the results of step 185.
187
188
189
190
8-22
Facility alarms
TAP-101
3EM23956AM
Issue 01, February 2013
TAP-101
Abnormal conditions
Purpose
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.
See the 9500 MPR-A Product Information (PN 3EM23952AM) to determine card location and
address.
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
Review the output. See Table 101-A for information about abnormal conditions.
Abnormal conditions
8-23
TAP-101
3EM23956AM
Issue 01, February 2013
Name
Type (equipment)
See
Loopback
MSS/DS1
Step 3
Loopback
SLOT#[3-8]
Forced adaptive
modulation
Direction #1.[1-6]
Loopback
Step 7
(MPT ODU connected to
Core-E, MSS/CORE)
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)
Direction #[3-8]
Radio
(MOD300)
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)
Step 11
8-24
Radio
(MPT-HL connected to
Core-E, MSS/CORE)
Abnormal conditions
TAP-101
3EM23956AM
Issue 01, February 2013
Name
Type (equipment)
See
Main#1 Slot#1
(Core-E)
Step 15
Main#1 Slot#[3,5,7]
(MOD300, P2E3DS3,
P32E1DS1, SDHAC)
MPT-HL connected to
P8ETH
MPT-HL connected to
P8ETH
Main#1 Slot#[3,5,7]
MOD300
MPT-HL connected to
P8ETH
Main#1 Slot#[3,5,7]
MOD300
IF cable loopback
Direction #[3-8]
MOD300
Direction #1.[1-6]
Loopback
Step 24
(MPT ODU connected to
Core-E, MSS/CORE)
Direction #[3-8].[1-4]
Loopback
(MPT ODU connected to
MPTACC)
Direction #[3-8].[5-8]
Loopback
(MPT ODU connected to
P8ETH)
Abnormal conditions
Step 15
Step 15
Step 20
8-25
TAP-101
3EM23956AM
Issue 01, February 2013
Name
Type (equipment)
See
Loopback
MSS/DS1]
Step 28
Loopback
SLOT#[3-8]
Spare#0 Slot#2
Core-E
Spare#0 Slot#[4,6,8]
MOD30, P2E3DS3,
P32E1DS1, SDHACC
MPT-HL connected to
P8ETH
MPT-HL connected to
P8ETH
Spare#0 Slot#[4,6,8]
MOD300
MPT-HL connected to
P8ETH
Spare#0 Slot#[4,6,8]
MOD300
8-26
Step 32
Step 32
Step 32
Abnormal conditions
TAP-101
3EM23956AM
Issue 01, February 2013
Name
Type (equipment)
See
TXMute
Step 36
MPT-HL connected to
Core-E, MSS/CORE
ODU300
IXL-101
10
Abnormal conditions
8-27
TAP-101
3EM23956AM
Issue 01, February 2013
12
13
14
Forced switch
EPS, RPS, and TPS
15
16
17
18
19
IF cable loopback
20
21
22
8-28
Abnormal conditions
TAP-101
23
3EM23956AM
Issue 01, February 2013
25
26
27
29
30
31
Lockout switch
EPS, RPS, and TPS
32
33
34
Abnormal conditions
8-29
TAP-101
3EM23956AM
Issue 01, February 2013
35
TXMute
36
37
38
39
40
41
8-30
Abnormal conditions
TAP-102
3EM23956AM
Issue 01, February 2013
TAP-102
Power alarms
Purpose
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:
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 Product Information (PN 3EM23952AM) to determine card location and
address.
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
Review the output. See Table 102-A for information about the power alarms.
Power alarms
8-31
TAP-102
3EM23956AM
Issue 01, February 2013
Friendly name/entity
Equipment type
See
Battery failure
r01/subrack#1
MSS-1/4/8
Step 3
r01/subrack#[3-8][1-4]
MPTACC
Step 14
r01/subrack#[1][1-2]
MSS/Core
r01/subrack#1
MSS-1/4/8
Step 72
IXL-101
Battery failure
3
Verify that there is no blown fuse providing power to the A-power feed.
Verify the shelf power cable connections between the MSS-1/4/8 and the PDU.
9
10
11
12
13
8-32
Power alarms
TAP-102
3EM23956AM
Issue 01, February 2013
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
16
17
18
19
20
b.
c.
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
23
Power alarms
8-33
TAP-102
3EM23956AM
Issue 01, February 2013
24
25
26
27
28
29
30
31
32
Go to step 36.
33
34
35
36
37
38
Physically reseat card in alarm and wait for the status LED to turn steady green or
amber.
39
8-34
Power alarms
TAP-102
40
3EM23956AM
Issue 01, February 2013
41
42
43
44
b.
c.
45
Based on the answers to step 44, verify the appropriate maintenance window is
scheduled per local practices and procedures.
46
47
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.
50
51
52
53
Power alarms
8-35
TAP-102
3EM23956AM
Issue 01, February 2013
54
55
56
57
58
59
60
Inspect the power supply cable run between the MPTACC/MSS-1 CORE and
MPT ODU.
61
62
63
64
65
66
8-36
Power alarms
TAP-102
3EM23956AM
Issue 01, February 2013
67
68
69
70
71
Go to step 84.
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
75
76
77
78
79
Is the measured voltage within the supported voltage range (-40.8 VDC to -57.6 VDC)?
If yes, go to step 83.
If no, go to step 80.
80
81
82
83
84
Power alarms
8-37
3EM23956AM
Issue 01, February 2013
TAP-102
8-38
Power alarms
TAP-103
3EM23956AM
Issue 01, February 2013
TAP-103
Equipment alarms
Purpose
This procedure describes how to identify and clear Equipment alarms (Replaceable Unit Problem,
Replaceable Unit Missing, Replaceable Unit Type Mismatch, Excessive Environmental
Temperature, or Unconfigured Equipment Present) on Core-E, 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 Product Information (PN 3EM23952AM) to determine card location and
address.
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
Review the output. See Table 103-A for information about equipment alarms.
Equipment alarms
8-39
TAP-103
3EM23956AM
Issue 01, February 2013
Name
8-40
Equipment type
See
MPT-HL connected to
P8ETH
Step 3
MPT-HL connected to
Core-E, MSS/CORE
Step 14
AUX
r01s1/board#[1-2]
Core-E
r01s1/board#[5,9]
FAN
r01s1/board#[3-8]
MOD300, MPTACC,
P2E3DS3, P8ETH,
P32E1DS1, SDHACC
r01s1b[1-2]/daughter#[5-6]
SFP on Core-E
r01s1b1/daughter#[5-6]
SFP on MSS/CORE
r01s1b[3-8]/daughter#[03-04]
SFP on MPTACC
r01s1b[3-8]/daughter#[05-08]
SFP on P8ETH
r01s1b[3-8]/daughter#[01-02]
SFP on SDHACC
r01s[3-8][1-4]b1/daughter#03
r01s1[1-6]b1/daughter#03
Equipment alarms
TAP-103
3EM23956AM
Issue 01, February 2013
Name
Equipment alarms
Equipment type
See
AUX
Step 24
r01s1/board#[1-2]
Core-E
r01s1/board#[5,9]
FAN
r01s1/board#[3-8]
MOD300, MPTACC,
P2E3DS3, P8ETH,
P32E1DS1, SDHACC
r01/subrack#1[1-6]
r01/subrack#[3-8][1-4]
r01/subrack#[3-8][5-8]
r01/subrack#[3-8][5-8]
MPT-HL connected to
P8ETH
r01/subrack#1[5-6]
MPT-HL connected to
Core-E, MSS/CORE
r01/subrack#[3-8]
ODU300
r01s1b[1-2]/daughter#[05-06]
SFP on Core-E
r01s1b1/daughter#[05-06]
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]
r01s[3-8][1-4]b1/daughter#03
r01s1[1-6]b1/daughter#03
r01s1[1-6]b1/daughter#04
r01/subrack#[3-8][5-8]/daughter#04
XPIC Module on
MPT ODU connected to
P8ETH
r01s[3-8][1-4]b1/daughter#04
8-41
TAP-103
3EM23956AM
Issue 01, February 2013
Name
Equipment type
See
r01s1/board#[8]
AUX
Step 161
r01s1/board#[1-2]
Core-E
r01s1/board#[5,9]
FAN
r01s1/board#[3-8]
MOD300, MPTACC,
P2E3DS3, P8ETH,
P32E1DS1, SDHACC
r01/subrack#1[1-6]
r01/subrack#[3-8][1-4]
r01/subrack#[3-8][5-8]
r01/subrack#[3-8][5-8]
MPT-HL connected to
P8ETH
r01/subrack#1[5-6]
MPT-HL connected to
Core-E, MSS/CORE
r01/subrack#[3-8]
ODU300
Step 178
AUX
Step 188
Core-E
r01s1/board#[5,9]
FAN
r01s1/board#[3-8]
MOD300, MPTACC,
P2E3DS3, P8ETH,
P32E1DS1, SDHACC
r01s1b[1-2]/daughter#[05-06]
SFP on Core-E
r01s1b1/daughter#[05-06]
SFP on MSS/CORE
r01s1b[3-8]/daughter#[03-08]
SFP on MPTACC
r01s1b[3-8]/daughter#[05-08]
SFP on P8ETH
r01s1b[3-8]/daughter#[01-02]
SFP on SDHACC
IXL-101
Verify that the MPT-HL card fan is equipped and operating properly.
8-42
Equipment alarms
TAP-103
5
3EM23956AM
Issue 01, February 2013
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.
12
13
15
16
17
Equipment alarms
8-43
TAP-103
3EM23956AM
Issue 01, February 2013
18
19
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
22
23
25
26
27
8-44
Equipment alarms
TAP-103
28
3EM23956AM
Issue 01, February 2013
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
31
32
33
34
35
36
37
38
39
40
Go to step 47.
41
42
43
44
Equipment alarms
8-45
TAP-103
3EM23956AM
Issue 01, February 2013
45
Go to step 47.
46
47
48
49
50
51
52
53
54
55
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
58
59
60
61
62
Verify that the local and far end radio direction are alarm free and error-free.
8-46
Equipment alarms
TAP-103
63
3EM23956AM
Issue 01, February 2013
Are the local and far end alarm free and error-free?
If yes, go to step 64.
If no, go to step 198.
64
65
66
67
Go to step 199.
68
69
70
71
72
73
Go to step 99.
74
75
76
Go to step 99.
77
b.
c.
d.
Equipment alarms
8-47
TAP-103
3EM23956AM
Issue 01, February 2013
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
80
81
82
83
84
85
86
87
8-48
Equipment alarms
TAP-103
88
3EM23956AM
Issue 01, February 2013
89
90
91
92
93
Go to step 97.
94
95
96
97
98
99
Physically reseat the card in alarm and wait for the status LED to turn steady green
or amber.
100
101
102
Equipment alarms
8-49
TAP-103
3EM23956AM
Issue 01, February 2013
103
104
105
106
107
Go to step 199.
108
109
110
111
112
Go to step 199.
113
114
115
116
117
Perform the Forced HSB Switch using the Craft Terminal (radio SFP only).
118
Perform the Forced Rx Radio Switch using the Craft Terminal (radio SFP only).
119
120
Go to step 127.
8-50
Equipment alarms
TAP-103
3EM23956AM
Issue 01, February 2013
121
122
Perform the Lockout HSB Switch using the Craft Terminal (radio SFP only).
123
Perform the Lockout Rx Radio Switch using the Craft Terminal (radio SFP only).
124
125
Go to step 127.
126
127
128
129
130
131
132
133
134
135
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).
Equipment alarms
8-51
TAP-103
3EM23956AM
Issue 01, February 2013
138
Go to step 199.
139
Physically reseat the RPS cable at both ends that are associated with RPS SFP in
alarm.
140
141
142
143
144
145
146
147
148
Replace the RPS cable that is associated with the RPS SFP in alarm.
149
150
151
See DLP-115 to replace MPT ODU associated with RPS SFP in alarm.
152
153
8-52
Equipment alarms
TAP-103
3EM23956AM
Issue 01, February 2013
154
155
156
157
See DLP-115 to replace MPT ODU associated with RPS/XPIC module in alarm.
158
159
160
Go to step 199.
162
163
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.
165
Equipment alarms
8-53
TAP-103
3EM23956AM
Issue 01, February 2013
166
167
168
169
170
171
Is the SFP in alarm the correct SFP type as described in the site engineering
documentation?
If yes, go to step 175.
If no, go to step 172.
172
Replace the SFP with the type corresponding to the SFP card slot provisioning. See
DLP-102 to replace an SFP.
173
174
175
176
177
8-54
Verify that the radio channel provisioning corresponding to the ODU300 in alarm is
correct as described in the site engineering documentation.
Equipment alarms
TAP-103
179
3EM23956AM
Issue 01, February 2013
180
181
182
Replace the ODU300 with ODU300 type supporting radio channel provisioning that is
stored in Core-E memory. See DLP-109 to replace ODU300.
183
184
185
186
187
189
190
191
192
Equipment alarms
8-55
TAP-103
3EM23956AM
Issue 01, February 2013
193
194
195
Install the blank filler panel or face plate into the slot that the card was removed.
196
197
198
199
8-56
Equipment alarms
TAP-104
3EM23956AM
Issue 01, February 2013
TAP-104
Radio 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.
8-57
TAP-104
3EM23956AM
Issue 01, February 2013
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.
See the 9500 MPR-A Product Information (PN 3EM23952AM) to determine card location and
address.
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
Review the output. See Table 104-A for information about radio alarms.
Table 104-A. Radio alarms
Probable cause
Friendly name/entity
Equipment type
Radio/Dir#[3-8].[1-4]/
Slot#[3-8]/Port#[1-4]/Ch#[0-1]
Radio/Dir#1.[1-6]/
Slot#1/Port#[1-6]/Ch#[0-1]
Radio/Dir#1.[1-6]/MSS/
CORE/Port#[1-6]/Ch#[0-1]
Radio/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#1
Radio/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#[0-1]
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
8-58
See
TAP-104
3EM23956AM
Issue 01, February 2013
Friendly name/entity
Equipment type
CLA
Radio/Dir#[3-8].[1-4]/
Slot#[3-8]/Port#[1-4]/Ch#[0-1]
Radio/Dir#1.[1-6]/
Slot#1/Port#[1-6]/Ch#[0-1]
Radio/Dir#1.[1-6]/MSS/
CORE/Port#[1-6]/Ch#[0-1]
Radio/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#[0-1]
MPT-HL connected to
P8ETH
Radio/Dir#[3-8]/Ch#[0-1]
MOD300
Radio/Dir#[3-8].[1-4]/
Slot#[3-8]/Port#[1-4]/Ch#[0-1]
Radio/Dir#1.[1-6]/
Slot#1/Port#[1-6]/Ch#[0-1]
Radio/Dir#1.[1-6]/MSS/
CORE/Port#[1-6]/Ch#[0-1]
Radio/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#1
Radio/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#[0-1]
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]
MOD300
Radio/Dir#[3-8].[1-4]/
Slot#[3-8]/Port#[1-4]/Ch#[0-1]
Radio/Dir#1.[1-6]/
Slot#1/Port#[1-6]/Ch#[0-1]
Radio/Dir#1.[1-6]/MSS/
CORE/Port#[1-6]/Ch#[0-1]
Radio/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#[0-1]
Radio/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#[0-1]
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]
MOD300
Demodulator fail
See
8-59
TAP-104
3EM23956AM
Issue 01, February 2013
Friendly name/entity
Equipment type
High BER
Radio/Dir#[3-8].[1-4]/
Slot#[3-8]/Port#[1-4]/Ch#[0-1]
Radio/Dir#1.[1-6]/
Slot#1/Port#[1-6]/Ch#[0-1]
Radio/Dir#1.[1-6]/MSS/
CORE/Port#[1-6]/Ch#[0-1]
Radio/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#1
Radio/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#[0-1]
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]
MOD300
Radio/Dir#[3-8].[1-4]/
Slot#[3-8]/Port#[1-4]/Ch#[0-1]
Radio/Dir#1.[1-6]/
Slot#1/Port#[1-6]/Ch#[0-1]
Radio/Dir#1.[1-6]/MSS/
CORE/Port#[1-6]/Ch#[0-1]
Radio/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#1
Radio/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#[0-1]
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]
MOD300
Incompatible frequency
8-60
See
TAP-104
3EM23956AM
Issue 01, February 2013
Friendly name/entity
Incompatible protection
Incompatible shifter
Equipment type
See
Radio/Dir#1.[1-6]/
Slot#1/Port#[1-6]/Ch#[0-1]
Radio/Dir#1.[1-6]/MSS/
CORE/Port#[1-6]/Ch#[0-1]
Radio/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#1
Radio/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#[0-1]
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].[1-4]/
Slot#[3-8]/Port#[1-4]/Ch#[0-1]
Radio/Dir#1.[1-6]/
Slot#1/Port#[1-6]/Ch#[0-1]
Radio/Dir#1.[1-6]/MSS/
CORE/Port#[1-6]/Ch#[0-1]
Radio/Dir#[3-8].[1-4]/
Slot#[3-8]/Port#[1-4]/Ch#[0-1]
Radio/Dir#1.[1-6]/
Slot#1/Port#[1-6]/Ch#[0-1]
Radio/Dir#1.[1-6]/MSS/
CORE/Port#[1-6]/Ch#[0-1]
Radio/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#1
Radio/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#[0-1]
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]
ODU300
8-61
TAP-104
3EM23956AM
Issue 01, February 2013
Friendly name/entity
Equipment type
Incompatible power
Radio/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#[0-1]
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].[1-4]/
Slot#[3-8]/Port#[1-4]/Ch#[0-1]
Radio/Dir#1.[1-6]/
Slot#1/Port#[1-6]/Ch#[0-1]
Radio/Dir#1.[1-6]/MSS/
CORE/Port#[1-6]/Ch#[0-1]
Radio/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#1
Radio/Dir#[3-8]/Ch#[0-1]
ODU300
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]
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#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#1,
AirFrame/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]
MPT-HL connected to
P8ETH
AirFrame/Dir#1.[5-6]/
Slot#1/Port#[5-6]
MPT-HL connected to
Core-E
AirFrame/Dir#1.[5-6]/MSS/
CORE/Port#[5-6]
MPT-HL connected to
MSS/CORE
AirFrame/Dir#[3-8]/Ch#1,
AirFrame/Dir#[3-8]
MOD300
Incompatible TX power
8-62
See
TAP-104
3EM23956AM
Issue 01, February 2013
Friendly name/entity
Equipment type
See
Loss of protection
Radio/Dir#[3-8]/Ch#1
MOD300
Step 111
Radio/Dir#[3-8].[1-4]/
Slot#[3-8]/Port#[1-4]/Ch#1
Radio/Dir#1.[1-6]/
Slot#1/Port#[1-6]/Ch#1
Radio/Dir#1.[1-6]/MSS/
CORE/Port#[1-6]/Ch#1
Loss of signal
PPP fail
MPT-HL connected to
P8ETH
PPP-IP/RF#1[1-6]
PPP-IP/RF#[3-8][1-4]
PPP-IP/RF#[3-8][5-8]
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#[3-8]
MOD300
Radio/Dir#1.[1-6]/
Slot#1/Port#[1-6]/Ch#[0-1]
Radio/Dir#1.[1-6]/MSS/
CORE/Port#[1-6]/Ch#[0-1]
Radio/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#1
Radio/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#[0-1]
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]
MOD300
IXL-101
8-63
TAP-104
3EM23956AM
Issue 01, February 2013
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.
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.
CLA
7
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
12
13
Are both receivers at the far end in alarm and traffic affected?
If yes, go to step 17.
If no, go to step 14.
8-64
TAP-104
3EM23956AM
Issue 01, February 2013
14
Wait two minutes for the CLA alarm to be declared against the MPT ODU, MPT-HL,
or ODU300.
15
16
Is the CLA alarm declared against the MPT ODU, MPT-HL, or ODU300?
If yes, go to step 17.
If no, go to step 145.
17
18
19
20
Are both receivers at the far end in alarm and traffic affected?
If yes, go to step 144.
If no, go to step 21.
21
Wait two minutes for the CLA alarm to be declared against the MPT ODU, MPT-HL,
or ODU300.
22
23
Is the CLA alarm declared against the MPT ODU, MPT-HL, or ODU300?
If yes, go to step 144.
If no, go to step 145.
Demodulator fail
24
8-65
TAP-104
3EM23956AM
Issue 01, February 2013
25
26
27
28
29
30
31
32
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.
34
35
No action is required at this time. Monitor the receive signal for increased degrading.
37
Go to step 145.
8-66
TAP-104
3EM23956AM
Issue 01, February 2013
High BER
38
39
40
41
42
43
44
45
46
47
48
49
50
8-67
TAP-104
3EM23956AM
Issue 01, February 2013
Incompatible frequency
51
Using the Craft Terminal, retrieve the provisioned frequency value and supported
frequency of the MPT ODU, MPT-HL, or ODU300.
52
53
Is the required microwave link frequency supported by the MPT ODU, MPT-HL, or
ODU300?
If yes, go to step 54.
If no, go to step 57.
54
Reprovision the frequency of the MPT ODU, MPT-HL, or ODU300 to the required
frequency of the microwave link.
55
56
57
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.
59
60
Incompatible modulation
61
Using the Craft Terminal, retrieve the provisioned modulation value and supported
modulation of the MPT ODU/MPT-HL.
62
8-68
TAP-104
63
3EM23956AM
Issue 01, February 2013
64
65
66
67
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.
69
70
Incompatible protection
71
Visually inspect the main and spare MPT ODU for missing the RPS/XPIC module.
72
73
74
8-69
TAP-104
3EM23956AM
Issue 01, February 2013
75
76
77
Are both MPT ODUs equipped with the correct RPS/XPIC module?
If yes, go to step 81.
If no, go to step 78.
78
79
80
81
82
83
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
86
Is the required microwave link shifter level supported by the MPT ODU, MPT-HL, or
ODU300?
If yes, go to step 87.
If no, go to step 90.
87
88
8-70
TAP-104
89
3EM23956AM
Issue 01, February 2013
90
91
Replace the MPT ODU/MPT-HL/ODU30 with version that supports the required
shifter value of the microwave link.
For MPT ODU replacement, see DLP-115.
For MPT-HL replacement, see DLP-108.
For ODU300 replacement, see DLP-109.
92
93
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
96
97
98
99
8-71
TAP-104
3EM23956AM
Issue 01, February 2013
100
101
Replace the MPT ODU/MPT-HL/ODU300 with the version that supports the required
transmit power level of the microwave link.
For MPT ODU replacement, see DLP-115.
For MPT-HL replacement, see DLP-108.
For ODU300 replacement, see DLP-109.
102
103
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
107
108
Reprovision the Link Identifier values according to the results of step 107.
109
110
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.
8-72
TAP-104
3EM23956AM
Issue 01, February 2013
113
114
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.
117
118
Loss of signal
119
120
121
122
Verify the link cabling between the Core-E/MPTACC/P8ETH card Ethernet port and
the MPT ODU/MPT-HL.
123
124
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.
8-73
TAP-104
3EM23956AM
Issue 01, February 2013
126
127
128
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
131
132
133
134
Verify that the Link Identifiers match at the local and far end radio cards.
135
136
137
138
139
8-74
TAP-104
3EM23956AM
Issue 01, February 2013
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.
142
143
144
145
8-75
3EM23956AM
Issue 01, February 2013
8-76
TAP-104
TAP-105
3EM23956AM
Issue 01, February 2013
TAP-105
Ethernet 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.
See the 9500 MPR-A Product Information (PN 3EM23952AM) to determine card location and
address.
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
Review the output. See Table 105-A for information about the Ethernet alarms.
Table 105-A. Ethernet alarms
Probable cause
Friendly name/entity
Facility type
See
Loss of signal
ETHInterface#100
Core-E
Step 3
ETHInterfaceonCore#4
Core-E
MAU/Slot#[1-2]/Port#[1-6]
Core-E
MAU/Slot#1/Port#[1-6]
MSS/CORE
MAU/Slot#[3-8]/Port#[1-4]
MPTACC
MAU/Slot#[3-8]/Port#[1-8]
P8ETH
r01s1[1-6]b1/daughter#03
ERP[1-2]#1-2]
Core-E
Step 10
IXL-101
Loss of signal
3
8-77
TAP-105
3EM23956AM
Issue 01, February 2013
Verify the link partner cabling between the Core-E/MPTACC/P8ETH card or MSS-1
shelf Core and the link partner.
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.
12
13
14
15
16
8-78
TAP-106
3EM23956AM
Issue 01, February 2013
TAP-106
License/software mismatch
Purpose
This procedure describes how to identify and clear License/Software Mismatch alarms (Provisioning
Mismatch or Version Mismatch, Standby Version mismatch) on the Core-E,
MPT-HC/MPT-XP/9558HC (MPT ODU), MPT-HL, 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.
See the 9500 MPR-A Product Information (PN 3EM23952AM) to determine card location and
address.
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
Review the output. See Table 106-A for information about License/Software Mismatch
alarms.
Table 106-A. License/software mismatch alarms
Probable cause
Friendly name/entity
Facility type
See
Provisioning mismatch
r01s1/board#[1-2]
Core-E
Step 3
r01s1/board#1
MSS/CORE
License/software mismatch
8-79
TAP-106
3EM23956AM
Issue 01, February 2013
Version mismatch
r01/subrack#1[1-6]
r01/subrack#[3-8][1-4]
r01/subrack#[3-8][5-8]
r01/subrack#[3-8][5-8]
MPT-HL connected to
P8ETH
r01/subrack#1[5-6]
MPT-HL connected to
Core-E, MSS/CORE
r01s1/board#[1-2]
Core-E
r01/subrack#1[1-6]
r01/subrack#[3-8][1-4]
r01/subrack#[3-8][5-8]
r01/subrack#[3-8][5-8]
MPT-HL connected to
P8ETH
r01/subrack#1[5-6]
MPT-HL connected to
Core-E, MSS/CORE
r01/subrack#[3-8]
ODU300
Step 12
IXL-101
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.
8-80
License/software mismatch
TAP-106
3EM23956AM
Issue 01, February 2013
10
11
Version mismatch
12
Verify the Core-E card type is installed in the slot declaring Version Mismatch alarm.
13
14
Replace the Core-B card with the Core-E card. See DLP-103 to replace the Core-E
card.
15
16
17
18
19
Replace the Core-E card. See DLP-103 to replace the Core-E card.
20
License/software mismatch
8-81
TAP-106
3EM23956AM
Issue 01, February 2013
21
Version mismatch
22
23
24
25
26
27
28
29
8-82
License/software mismatch
TAP-107
3EM23956AM
Issue 01, February 2013
TAP-107
Internal loss of communications
Purpose
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
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.
See the 9500 MPR-A Product Information (PN 3EM23952AM) to determine card location and
address.
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
Review the output. See Table 107-A for information about internal communication
problem alarms.
8-83
TAP-107
3EM23956AM
Issue 01, February 2013
Friendly name/entity
Facility type
Dialog failure
r01/subrack#1[1-6]
r01/subrack#[3-8][1-4]
r01/subrack#[3-8][[5-8]
r01/subrack#[3-8][5-8]
MPT-HL connected to
P8ETH
r01/subrack#1[5-6]
MPT-HL connected to
Core-E, MSS/CORE
r01/subrack#1[1-6]
r01/subrack#[3-8][1-4]
r01/subrack#[3-8][5-8]
r01/subrack#[3-8][5-8]
MPT-HL connected to
P8ETH
r01/subrack#1[5-6]
MPT-HL connected to
Core-E, MSS/CORE
r01/subrack#[3-8]
ODU300
Internal communication
problem
See
IXL-101
Dialog failure
3
8-84
TAP-107
6
3EM23956AM
Issue 01, February 2013
Reseat the MPTACC card that is associated with the MPT ODU in alarm.
10
11
12
13
14
15
16
Is the radio port fiber cabling correct and connected to the correct MPT type?
If yes, go to step 23.
If no, go to step 17.
17
18
19
8-85
TAP-107
3EM23956AM
Issue 01, February 2013
20
21
22
23
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
27
28
29
30
CAUTION: Possibility of service interruption. Forced EPS and HSB switching traffic
causes a disruption to traffic.
31
32
33
8-86
TAP-107
3EM23956AM
Issue 01, February 2013
34
35
Go to step 39.
36
37
38
39
40
41
42
43
44
45
Is the MPT ODU in alarm supported by the Core-E/P8ETH card or MSS-1 shelf Core?
If yes, go to step 48.
If no, go to step 46.
46
Is there a second radio channel supported by the MPTACC associated with the
MPT ODU in alarm?
If yes, go to step 47.
If no, go to step 56.
47
8-87
TAP-107
3EM23956AM
Issue 01, February 2013
48
49
50
51
52
53
Replace the MPT ODU in alarm. See DLP-115 to replace MPT ODU.
54
55
56
8-88
TAP-107
3EM23956AM
Issue 01, February 2013
57
Reseat the MPTACC/P8ETH/Core-E card that is associated with the MPT ODU in
alarm.
58
59
60
61
62
Replace the MPTACC/P8ETH/Core-E that is associated with the MPT ODU in alarm.
See DLP-114 to replace the MPTACC.
63
64
65
66
67
Replace the MPT ODU in alarm. See DLP-115 to replace MPT ODU.
68
69
70
8-89
TAP-107
3EM23956AM
Issue 01, February 2013
71
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.
74
75
76
77
78
79
80
81
82
83
84
85
86
87
Go to step 174.
8-90
TAP-107
3EM23956AM
Issue 01, February 2013
Is traffic affected?
If yes, go to step 92.
If no, go to step 89.
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.
90
91
92
93
94
95
Is the radio port fiber cabling correct and connected to the correct MPT type?
If yes, go to step 102.
If no, go to step 96.
96
97
98
99
100
8-91
TAP-107
3EM23956AM
Issue 01, February 2013
101
102
103
104
105
106
107
108
Go to step 112.
109
110
111
112
113
114
Physically reseat the MOD300 that is associated with the ODU300 in alarm. Do not
remove the IF cable while reseating the MOD300 card.
115
8-92
TAP-107
116
3EM23956AM
Issue 01, February 2013
117
118
Replace the MOD300 that is associated with the ODU300. See DLP-107 to replace the
MOD300.
119
120
121
122
123
124
125
Is MPT ODU in alarm supported by the Core-E/P8ETH card or MSS-1 shelf Core?
If yes, go to step 128.
If no, go to step 126.
126
Is there a second radio channel supported by the MPTACC associated with the
MPT ODU in alarm?
If yes, go to step 127.
If no, go to step 136.
8-93
TAP-107
3EM23956AM
Issue 01, February 2013
127
128
129
130
131
132
133
Replace the MPT ODU in alarm. See DLP-115 to replace MPT ODU.
134
135
8-94
TAP-107
3EM23956AM
Issue 01, February 2013
136
137
Reseat the MPTACC card that is associated with the MPT ODU in alarm.
138
139
140
141
142
Replace the MPTACC that is associated with MPT ODU in alarm. See DLP-114 to
replace the MPTACC.
143
144
145
146
147
Replace the MPT ODU in alarm. See DLP-115 to replace MPT ODU.
148
149
8-95
TAP-107
3EM23956AM
Issue 01, February 2013
150
151
Unseat and reseat the communication link between the MPT-HL and P8ETH, Core-E,
or MSS-1 Shelf.
152
153
154
155
Replace the communication link between the MPT-HL and P8ETH, Core-E, or MSS-1
Shelf.
156
157
158
159
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.
162
163
8-96
TAP-107
3EM23956AM
Issue 01, February 2013
164
165
166
167
168
169
170
171
172
Go to step 174.
173
174
8-97
3EM23956AM
Issue 01, February 2013
8-98
TAP-107
TAP-108
3EM23956AM
Issue 01, February 2013
TAP-108 Threshold crossing alarms (MOD300, MPT-HC, MPT-HL, MPT-XP, 9558HC, P32E1DS1, MSS-1 shelf P32E1DS1)
TAP-108
Threshold 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.
See the 9500 MPR-A Product Information (PN 3EM23952AM) to determine card location and
address.
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
1
PROCEDURE
Using the Alarm Monitor, retrieve all alarms.
8-99
TAP-108
3EM23956AM
Issue 01, February 2013
Review the output. See Table 108-A for information about TCA alarms.
Table 108-A. Threshold crossing alarms
Probable cause
Friendly name/entity
Facility type
See
Threshold crossed
Hop/Dir#1[1-6]/Slot#1/
Port#[1-6]/Ch#[0-1]-PM15min
Step 3
Hop/Dir#1[1-6]/Slot#1/
Port#[1-6]/Ch#[0-1]-PM1day
Link/Dir#1[1-6]-PM15min
Link/Dir#1[1-6]-PM1day
Hop/Dir#1[1-6]/MSS/CORE/
Port#[1-6]/Ch#[0-1]-PM15min
Hop/Dir#1[1-6]/MSS/CORE/
Port#[1-6]/Ch#[0-1]-PM1day
Link/Dir#1[1-6]-PM15min
Link/Dir#1[1-6]-PM1day
Hop/Dir#[3-8][1-4]/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]-PM1day
Link/Dir#[3-8][1-4]-PM15min
Link/Dir#[3-8][1-4]-PM1day
Hop/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-PM1day
Hop/Dir#[3-8][5-8]/Slot#[3-8]/
Port#[5-8]/Ch#[0-1]-PM15min
MPT-HL connected to
P8ETH
Hop/Dir#[3-8][5-8]/Slot#[3-8]/
Port#[5-8]/Ch#[0-1]-PM1day
Link/Dir#[3-8][5-8]-PM15min
Link/Dir#[3-8][5-8]-PM1day
Hop/Dir#1[5-6]/Slot#1/
Port#[5-6]/Ch#1-PM15min
MPT-HL connected to
Core-E
Hop/Dir#1[5-6]/Slot#1/
Port#[5-6]/Ch#1-PM1day
Hop/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
8-100
TAP-108
3EM23956AM
Issue 01, February 2013
Friendly name/entity
Facility type
See
Threshold crossed
continued
Hop/Dir#[3-8]/Ch#[0-1]-PM15min
MOD300
Step 3
Hop/Dir#[3-8]/Ch#[0-1]-PM1day
Link/Dir#[3-8]-PM15min
Link/Dir#[3-8]-PM1day
DS1-in/Slot#[3-8]/Port#[1-32]PM15min
DS1 on P32E1DS1
DS1-in/Slot#[3-8]/Port#[1-32]PM1day
DS1-out/Slot#[3-8]/Port#[1-32]PM15min
DS1-out/Slot#[3-8]/Port#[1-32]PM1day
DS1-in/MSS/DS1/Port#[1-16]PM15min
DS1-in/MSS/DS1/Port#[1-16]PM1day
DS1-out/MSS/DS1/Port#[1-16]PM15min
DS1-out/MSS/DS1/Port#[1-16]PM1day
Unavailable time
Hop/Dir#1[1-6]/Slot#1/
Port#[1-6]/Ch#[0-1]-PM15min
Step 12
Hop/Dir#1[1-6]/Slot#1/
Port#[1-6]/Ch#[0-1]-PM1day
Link/Dir#1[1-6]-PM15min
Link/Dir#1[1-6]-PM1day
Hop/Dir#1[1-6]/MSS/CORE/
Port#[1-6]/Ch#[0-1]-PM15min
Hop/Dir#1[1-6]/MSS/CORE/
Port#[1-6]/Ch#[0-1]-PM1day
Link/Dir#1[1-6]-PM15min
Link/Dir#1[1-6]-PM1day
Hop/Dir#[3-8][1-4]/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]-PM1day
Link/Dir#[3-8][1-4]-PM15min
Link/Dir#[3-8][1-4]-PM1day
8-101
TAP-108
3EM23956AM
Issue 01, February 2013
Friendly name/entity
Facility type
See
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-PM1day
Hop/Dir#[3-8][5-8]/Slot#[3-8]/
Port#[5-8]/Ch#[0-1]-PM15min
MPT-HL connected to
P8ETH
Hop/Dir#[3-8][5-8]/Slot#[3-8]/
Port#[5-8]/Ch#[0-1]-PM1day
Link/Dir#[3-8][5-8]-PM15min
Link/Dir#[3-8][5-8]-PM1day
Hop/Dir#1[5-6]/Slot#1/
Port#[5-6]/Ch#1-PM15min
MPT-HL connected to
Core-E
Hop/Dir#1[5-6]/Slot#1/
Port#[5-6]/Ch#1-PM1day
Hop/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
Hop/Dir#[3-8]/Ch#[0-1]-PM15min
MOD300
Hop/Dir#[3-8]/Ch#[0-1]-PM1day
Link/Dir#[3-8]-PM15min
Link/Dir#[3-8]-PM1day
DS1-in/Slot#[3-8]/Port#[1-32]PM15min
DS1 on P32E1DS1
DS1-in/Slot#[3-8]/Port#[1-32]PM1day
DS1-out/Slot#[3-8]/Port#[1-32]PM15min
DS1-out/Slot#[3-8]/Port#[1-32]PM1day
DS1-in/MSS/DS1/Port#[1-16]PM15min
DS1-in/MSS/DS1/Port#[1-16]PM1day
DS1-out/MSS/DS1/Port#[1-16]PM15min
DS1-out/MSS/DS1/Port#[1-16]PM1day
None of the above
8-102
IXL-101
TAP-108
3EM23956AM
Issue 01, February 2013
Threshold crossed
3
Determine the local weather conditions that could affect radio performance.
Following local practices and procedures, determine whether corrective actions are
required.
10
11
Unavailable time
12
13
14
15
16
Following local practices and procedures, determine whether corrective actions are
required.
17
18
19
8-103
TAP-108
3EM23956AM
Issue 01, February 2013
20
21
22
8-104
TAP-109
3EM23956AM
Issue 01, February 2013
TAP-109 Synchronization alarms (Core-E, MOD300, MPT-HC, MPT-HL, MPT-XP, P32E1DS1, SDHACC, 9558HC)
TAP-109
Synchronization 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.
See the 9500 MPR-A Product Information (PN 3EM23952AM) to determine card location and
address.
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
Review the output. See Table 109-A for information about synchronization alarms.
8-105
TAP-109
3EM23956AM
Issue 01, February 2013
Friendly name/entity
Equipment type
See
Degrade
Sync-in/Port#1
Core-E
Step 3
Radio/Dir#[3-8]/Ch#[0-1]
MOD300
Radio/Dir#1.[1-6]/
Slot#1/Port#[1-6]/Ch#1
Radio/Dir#1.[1-6]/MSS/CORE
/Port#[1-6]/Ch#1
Radio/Dir#[3-8].[1-4]/
Slot#[3-8]/Port#[1-4]/Ch#1
Radio/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#1
Radio/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#[0-1]
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
RadioLAG#[1-14]
DS1-in/Slot#[3-8]/Port#[1-32]
P32E1DS1
EleSdh-in/slot#[3-8]/Port[1-2]
OC-3
OptSdh-in/slot#[3-8]/Port[1-2]
Loss Ethernet
synchronization
messaging channel
8-106
MAU/Slot#[1-2]/Port#[1-6]
Core-E
Radio/Dir#[3-8]/Ch#[0-1]
MOD300
RadioLAG#[1-14]
Radio/Dir#1.[1-6]/
Slot#1/Port#[1-6]/Ch#[0-1]
Radio/Dir#1.[1-6]/MSS/
CORE/Port#[1-6]/Ch#[0-1]
Radio/Dir#[3-8].[1-4]/
Slot#[3-8]/Port#[1-4]/Ch#[0-1]
Radio/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#1
Radio/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#[0-1]
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
Step 29
TAP-109
3EM23956AM
Issue 01, February 2013
Friendly name/entity
Equipment type
See
Loss of signal
Sync-in/Port#1
Core-E
Step 38
Synchronization signal
fail
Sync-in/Port#1
Core-E
Step 62
Radio/Dir#[3-8]/Ch#[0-1]
MOD300
Radio/Dir#1.[1-6]/
Slot#1/Port#[1-6]/Ch#1
Radio/Dir#1.[1-6]/MSS/
CORE/Port#[1-6]/Ch#1
Radio/Dir#[3-8].[1-4]/
Slot#[3-8]/Port#[1-4]/Ch#1
Radio/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#1
Radio/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#1
MPT-HL connected to
P8ETH
Radio/Dir#1.[1-6]/
Slot#1/Port#[1-6]/Ch#1
MPT-HL connected to
Core-E
Radio/Dir#1.[1-6]/MSS/
CORE/Port#[1-6]/Ch#1
RadioLAG#[1-14]
DS1-in/Slot#[3-8]/Port#[1-32]
P32E1DS1
EleSdh-in/slot#[3-8]/Port[1-2]
OC-3
OptSdh-in/slot#[3-8]/Port[1-2]
None of the above
IXL-101
Degrade
3
Verify that the Sync reference source (GPS or other sync source) is functioning
correctly.
Verify the Sync-In cabling and connections to the sync-in port on the Core-E card
(main and spare, if equipped).
Verify the Sync cabling and connections to the sync-out port on sync source.
8-107
TAP-109
3EM23956AM
Issue 01, February 2013
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?
If yes, go to step 12.
If no, go to step 23.
12
13
14
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?
If yes, go to step 17.
If no, go to step 19.
17
18
19
8-108
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
3EM23956AM
Issue 01, February 2013
Was a sync reference DS1 port frequency problem identified and was it corrected?
If yes, go to step 21.
If no, go to step 23.
21
22
23
Verify the sync source provisioning at both the sync source and the alarming card is
correct.
24
25
26
27
28
30
Verify no radio or Ethernet alarms are declared against the radio direction declaring
Loss ESMC.
8-109
TAP-109
3EM23956AM
Issue 01, February 2013
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
34
35
Reprovision the Synchronization SSM value according to the results of step 34.
36
37
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).
40
41
42
Verify sync source provisioning at both the sync source and the alarming card.
43
44
8-110
TAP-109
45
3EM23956AM
Issue 01, February 2013
Is traffic affected?
If yes, go to step 46.
If no, go to step 95.
46
47
48
49
50
Go to step 52.
51
52
53
54
55
56
57
Replace the Core-E card declaring Loss Of Signal. See DLP-103 to replace Core-E.
58
59
8-111
TAP-109
3EM23956AM
Issue 01, February 2013
60
61
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.
65
66
67
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
71
8-112
TAP-109
72
3EM23956AM
Issue 01, February 2013
73
74
Verify no radio alarms are declared against the radio direction declaring
Synchronization Signal Fail.
75
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?
If yes, go to step 78.
If no, go to step 89.
78
79
80
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?
If yes, go to step 83.
If no, go to step 85.
83
8-113
TAP-109
3EM23956AM
Issue 01, February 2013
84
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?
If yes, go to step 87.
If no, go to step 89.
87
88
89
Verify sync source provisioning at both the sync source and the alarming card.
90
91
92
93
94
8-114
TAP-109
3EM23956AM
Issue 01, February 2013
95
96
8-115
3EM23956AM
Issue 01, February 2013
8-116
TAP-109
TAP-110
3EM23956AM
Issue 01, February 2013
TAP-110
ATPC 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.
See the 9500 MPR-A Product Information (PN 3EM23952AM) to determine card location and
address.
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
Review the output. See Table 110-A for information about ATPC Loop conditions.
8-117
TAP-110
3EM23956AM
Issue 01, February 2013
Friendly name/entity
Equipment type
Radio/Dir#1.[1-6]/
Slot#1/Port#[1-6]/Ch#[0-1]
Radio/Dir#1.[1-6]/MSS/
CORE/Port#[1-6]/Ch#[0-1]
Radio/Dir#[3-8].[1-4]/
Slot#[3-8]/Port#[1-4]/Ch#[0-1]
Radio/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#1
Radio/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#[0-1]
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]
MOD300
Radio/Dir#1.[1-6]/
Slot#1/Port#[1-6]/Ch#[0-1]
Radio/Dir#1.[1-6]/MSS/
CORE/Port#[1-6]/Ch#[0-1]
Radio/Dir#[3-8].[1-4]/
Slot#[3-8]/Port#[1-4]/Ch#[0-1]
Radio/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#1
Radio/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#[0-1]
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
Loop problem
See
IXL-101
Using the Craft Terminal, determine whether the local transmit power is at minimum
power setting.
8-118
TAP-110
3EM23956AM
Issue 01, February 2013
Troubleshoot the RF path from the near end transmitter to the far end receiver.
Loop problem
8
10
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.
18
19
8-119
TAP-110
3EM23956AM
Issue 01, February 2013
20
21
22
23
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.
31
32
8-120
TAP-110
33
3EM23956AM
Issue 01, February 2013
34
35
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.
43
44
45
46
8-121
TAP-110
3EM23956AM
Issue 01, February 2013
47
48
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.
56
57
58
59
8-122
TAP-111
3EM23956AM
Issue 01, February 2013
TAP-111
Cable LOS
Purpose
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).
See the 9500 MPR-A Product Information (PN 3EM23952AM) to determine card location and
address.
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
Review the output. See Table 111-A for information about clear radio alarms.
Table 111-A. Clear radio alarms
Probable cause
Friendly name/entity
Equipment type
See
Cable LOS
r01s1/board#[3-8]
MOD300
Step 3
DemXPIC LOS
r01s1/b1[1-6]/daughter#04
r01s1/b[3-8][1-4]/daughter#04
r01s[3-8][5-8]b1/daughter#04
IXL-101
Cable LOS
3
Cable LOS
Inspect the indoor IF cable is properly terminated, securely connected, and the run is
not damaged.
8-123
TAP-111
3EM23956AM
Issue 01, February 2013
Was the indoor IF cable not properly terminated, connected, or the run was damaged?
If yes, go to step 5.
If no, go to step 6.
9
10
11
12
13
14
15
16
Go to step 21.
17
18
19
8-124
Cable LOS
TAP-111
3EM23956AM
Issue 01, February 2013
20
21
Physically reseat the MOD300 card in alarm and wait for the status LED to turn
steady green or amber.
22
23
24
25
26
27
28
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?
If yes, go to step 31.
If no, go to step 32.
31
32
Cable LOS
8-125
TAP-111
3EM23956AM
Issue 01, February 2013
33
34
35
36
Was the MOD300 declaring Cable LOS alarm the main or spare?
If main, go to step 37.
If spare, go to step 41.
37
38
39
40
Go to step 75.
41
42
43
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?
If yes, go to step 47.
If no, go to step 50.
47
48
8-126
Cable LOS
TAP-111
49
3EM23956AM
Issue 01, February 2013
50
Reseat the XPIC cable on the horizontal and vertical MPT ODU.
51
52
53
Replace the XPIC cable between the horizontal and vertical MPT ODU.
54
55
56
Reseat the XPIC module on horizontal MPT ODU. See DLP-122 to reseat the XPIC
module.
57
58
59
Reseat the XPIC module on the vertical MPT ODU. See DLP-122 to reseat the XPIC
module.
60
61
62
Replace the XPIC module on the horizontal MPT ODU. See DLP-122 to replace the
XPIC module.
63
Cable LOS
8-127
TAP-111
3EM23956AM
Issue 01, February 2013
64
65
Replace the XPIC module on vertical MPT ODU. See DLP-122 to replace the XPIC
module.
66
67
68
Replace the horizontal MPT ODU. See DLP-115 to replace the MPT ODU.
69
70
71
Replace the vertical MPT ODU. See DLP-115 to replace the MPT ODU.
72
73
74
75
8-128
Cable LOS
TAP-112
3EM23956AM
Issue 01, February 2013
TAP-112
Loss 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.
See the 9500 MPR-A Product Information (PN 3EM23952AM) to determine card location and
address.
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
Review the output. See Table 112-A for information about Loss of Alignment alarms.
Table 112-A. Loss of alignment alarms
Probable cause
Friendly name/entity
Equipment type
Loss of alignment
Hitless/Dir#[3-8].[1-4]
Hitless/Dir#1.[1-6]
Hitless/Dir#[3-8].[5-8]
MPT-HL connected to
P8ETH
Hitless/Dir#[3-8]
MOD300
See
IXL-101
Loss of alignment
3
8-129
TAP-112
3EM23956AM
Issue 01, February 2013
10
Go to step 14.
11
12
13
14
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.
16
17
8-130
TAP-112
3EM23956AM
Issue 01, February 2013
18
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
21
22
23
24
25
26
27
Replace the MPT ODU in alarm. See DLP-115 to replace MPT ODU.
28
29
30
8-131
TAP-112
3EM23956AM
Issue 01, February 2013
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
34
35
36
37
38
39
40
41
42
43
44
45
Replace the MOD300 card in alarm. See DLP-107 to replace the MOD300.
46
47
8-132
TAP-112
48
3EM23956AM
Issue 01, February 2013
49
Replace the ODU300 that is associated with MOD300 in alarm. See DLP-109 to
replace the ODU300.
50
51
52
53
54
55
Go to step 57.
56
57
8-133
3EM23956AM
Issue 01, February 2013
8-134
TAP-112
TAP-113
3EM23956AM
Issue 01, February 2013
TAP-113
Loss 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.
See the 9500 MPR-A Product Information (PN 3EM23952AM) to determine card location and
address.
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
Review the output. See Table 113-A for information about Loss of Frame radio alarms.
Table 113-A. Loss of frame radio alarms
Probable cause
Friendly name/entity
Equipment type
Loss of frame
Radio/Dir#1.[1-6]/
Slot#1/Port#[1-6]/Ch#[0-1]
Radio/Dir#1.[1-6]/MSS/
CORE/Port#[1-6]/Ch#[0-1]
Radio/Dir#[3-8].[1-4]/
Slot#[3-8]/Port#[1-4]/Ch#[0-1]
Radio/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#1
Radio/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#[0-1]
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]
MOD300
See
IXL-101
8-135
TAP-113
3EM23956AM
Issue 01, February 2013
Loss of frame
3
10
11
12
13
8-136
TAP-113
14
3EM23956AM
Issue 01, February 2013
15
Is the MPT ODU in alarm supported by the Core-E or P8ETH card or MSS-1 Shelf
MSS/Core?
If yes, go to step 139.
If no, go to step 16.
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?
If yes, go to step 17.
If no, go to step 18.
17
Is the second radio channel, at the local or at the far end, error-free and alarm free?
If yes, go to step 139.
If no, go to step 18.
18
Reseat the local MPTACC that is associated with the MPT ODU in alarm.
19
20
21
22
Reseat the far end MPTACC that is associated with the MPT ODU in alarm.
23
24
25
8-137
TAP-113
3EM23956AM
Issue 01, February 2013
26
Replace the local MPTACC that is associated with the MPT ODU in alarm. See
DLP-114 to replace the MPTACC.
27
28
29
30
Replace the far end MPTACC that is associated with the MPT ODU in alarm. See
DLP-114 to replace the MPTACC.
31
32
33
34
Replace the local MPT ODU in alarm. See DLP-115 to replace the MPT ODU.
35
36
37
Replace the far end MPT ODU in alarm. See DLP-115 to replace the MPT ODU.
38
39
40
8-138
TAP-113
41
3EM23956AM
Issue 01, February 2013
42
43
44
45
46
Replace the far end MOD300. See DLP-107 to replace the MOD300.
47
48
49
50
Replace the far end ODU300. See DLP-109 to replace the ODU300.
51
52
53
54
8-139
TAP-113
3EM23956AM
Issue 01, February 2013
55
56
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
61
62
Replace the local MPT-HL. See DLP-108 to replace the MPT-HL Transceiver.
63
64
Replace the far end MPT-HL. See DLP-108 to replace the MPT-HL Transceiver.
65
66
67
8-140
TAP-113
68
3EM23956AM
Issue 01, February 2013
Is the MPT ODU/MPT-HL/MOD300 declaring the Loss Of Frame alarm the main or
spare?
If main, go to step 69.
If spare, go to step 74.
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.
78
79
Reseat the local MOD300 card that is declaring the Loss Of Frame alarm.
80
81
8-141
TAP-113
3EM23956AM
Issue 01, February 2013
82
83
Replace the local MOD300 that is declaring the Loss Of Frame alarm. See DLP-107 to
replace the MOD300.
84
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.
86
87
Replace the local ODU300 associated with the MOD300 that is declaring Loss Of
Frame alarm. See DLP-109 to replace the ODU300.
88
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.
90
91
Is the MPT ODU in alarm supported by the Core-E or P8ETH card or MSS-1 Shelf
MSS/Core?
If yes, go to step 139.
If no, go to step 92.
8-142
TAP-113
92
3EM23956AM
Issue 01, February 2013
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?
If yes, go to step 93.
If no, go to step 94.
93
Is the second radio channel, at the local or at the far end, error-free and alarm free?
If yes, go to step 139.
If no, go to step 94.
94
Reseat the local MPTACC that is associated with the MPT ODU in alarm.
95
96
97
98
Reseat the far end MPTACC that is associated with MPT ODU in alarm.
99
100
101
102
Replace the local MPTACC that is associated with MPT ODU in alarm. See DLP-114
to replace the MPTACC.
103
104
105
106
Replace the far end MPTACC that is associated with MPT ODU in alarm. See
DLP-114 to replace the MPTACC.
8-143
TAP-113
3EM23956AM
Issue 01, February 2013
107
108
109
110
Replace the local MPT ODU in alarm. See DLP-115 to replace the MPT ODU.
111
112
113
Replace the far end MPT ODU in alarm. See DLP-115 to replace the MPT ODU.
114
115
116
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
120
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.
8-144
TAP-113
3EM23956AM
Issue 01, February 2013
123
Install the fuse in the PDU that is suppling battery power to the far end MPT-HL
transceiver.
124
125
126
Replace the local MPT-HL. See DLP-108 to replace the MPT-HL Transceiver.
127
128
Replace the far end MPT-HL. See DLP-108 to replace the MPT-HL Transceiver.
129
130
131
132
133
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.
8-145
TAP-113
3EM23956AM
Issue 01, February 2013
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.
139
140
8-146
TAP-114
3EM23956AM
Issue 01, February 2013
TAP-114
RPS 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.
See the 9500 MPR-A Product Information (PN 3EM23952AM) to determine card location and
address.
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
Review the output. See Table 114-A for RPS Path Fail alarms.
Table 114-A. RPS path fail alarms
Probable cause
Friendly name/entity
Equipment type
RadioProt/Dir#[3-8][1-4]
RadioProt/Dir#1[1-6]
RadioProt/Dir#[3-8][5-8]
MPT-HL connected to
P8ETH
See
IXL-101
Using the Craft Terminal, determine which MPT ODU/MPT-HL status is Standby.
8-147
TAP-114
3EM23956AM
Issue 01, February 2013
Retrieve the alarms for the local end of the radio direction using the Alarm Monitor.
Determine all radio alarms that are declared against the radio direction declaring RPS
Path Fail and troubleshoot accordingly.
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.
11
12
13
14
15
16
17
Go to step 21.
18
8-148
TAP-114
3EM23956AM
Issue 01, February 2013
19
20
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.
25
26
27
28
Replace the MPT-HL with status of Standby. See DLP-108 to replace MPT-HL.
29
30
31
32
33
34
35
36
8-149
TAP-114
3EM23956AM
Issue 01, February 2013
37
Go to step 41.
38
39
40
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.
45
46
47
48
Replace MPT-HL with status of Standby. See DLP-108 to replace the MPT-HL.
49
50
51
52
53
54
55
8-150
TAP-114
3EM23956AM
Issue 01, February 2013
56
Go to step 58.
57
58
8-151
3EM23956AM
Issue 01, February 2013
8-152
TAP-114
TAP-115
3EM23956AM
Issue 01, February 2013
TAP-115
Rx 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.
See the 9500 MPR-A Product Information (PN 3EM23952AM) to determine card location and
address.
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
Review the output. See Table 115-A for information about Rx Fail alarms.
Table 115-A. Rx fail alarms
Probable cause
Friendly name/entity
Equipment type
See
Rx fail
Radio/Dir#[3-8]/Ch#[0-1]
MOD300
Step 3
IXL-101
Rx fail
3
Rx fail (MOD300)
8-153
TAP-115
3EM23956AM
Issue 01, February 2013
10
11
12
13
14
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.
8-154
Rx fail (MOD300)
TAP-115
3EM23956AM
Issue 01, February 2013
23
24
Reseat the MOD300 card in alarm. Physically remove the card and reinsert.
25
26
27
28
29
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
38
Reseat the far end MOD300 card associated with the card in alarm. Physically remove
the card and reinsert.
Rx fail (MOD300)
8-155
TAP-115
3EM23956AM
Issue 01, February 2013
39
40
41
42
Replace the near end MOD300. See DLP-107 to replace the MOD300.
43
44
45
46
Replace the far end MOD300. See DLP-107 to replace the MOD300.
47
48
49
Replace the near end ODU300. See DLP-109 to replace the ODU300.
50
51
52
Replace the far end ODU300. See DLP-109 to replace the ODU300.
53
8-156
Rx fail (MOD300)
TAP-115
54
3EM23956AM
Issue 01, February 2013
55
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.
57
58
59
60
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.
65
66
Rx fail (MOD300)
8-157
3EM23956AM
Issue 01, February 2013
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.
71
72
8-158
Rx fail (MOD300)
TAP-116
3EM23956AM
Issue 01, February 2013
TAP-116
Housekeeping alarms
Purpose
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.
See the 9500 MPR-A Product Information (PN 3EM23952AM) to determine card location and
address.
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
Review the output. See Table 116-A for information about Housekeeping alarms.
Table 116-A. Housekeeping alarms
Operation
Name
Equipment type
See
Housekeeping alarm
ExtPt/Input#[1-6]
AUX
Step 3
ExtPt/Input#[11-14]
Fan
ExtPt/Input#[11-14]
MSS-1
IXL-101
Housekeeping alarm
3
Verify the equipment that is associated with housekeeping alarm input which is in the
alarm state.
Housekeeping alarms
8-159
TAP-116
3EM23956AM
Issue 01, February 2013
Is the equipment that is associated with housekeeping alarm input [1-6] in the alarm
state?
If yes, go to step 5.
If no, go to step 7.
Resolve the problem with external equipment generating the housekeeping alarm.
Verify the Housekeeping Alarm Input provisioning for housekeeping alarm input in
alarm.
10
11
Verify the Housekeeping Alarm Input configuration for housekeeping alarm input in
alarm.
12
13
14
15
16
8-160
Housekeeping alarms
TAP-117
3EM23956AM
Issue 01, February 2013
TAP-117 LAG alarms (Core-E, MPT-HC, MPT-HL, MPT-XP, ODU300, 9558HC, MSS-1 shelf Core)
TAP-117
LAG 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.
See the 9500 MPR-A Product Information (PN 3EM23952AM) to determine card location and
address.
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
Review the output. See Table 117-A for information about LAG alarms.
Table 117-A. LAG alarms
Probable cause
Friendly name/entity
Equipment type
See
Degrade
EthLAG#[1-14]
Core-E, MSS/CORE
Step 3
RadioLAG#[1-14]
EthLAG#[1-14]
Core-E, MSS/CORE
RadioLAG#[1-14]
Loss of signal
Step 8
IXL-101
Degrade
3
LAG alarms (Core-E, MPT-HC, MPT-HL, MPT-XP, ODU300, 9558HC, MSS-1 shelf Core)
8-161
TAP-117
3EM23956AM
Issue 01, February 2013
Identify the alarms that are declared against members of the LAG group. If alarms
exists, see IXL-101 and troubleshoot accordingly.
Did the alarms exist on the LAG group members and were they cleared?
If yes, go to step 6.
If no, go to step 13.
Loss of signal
8
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?
If yes, go to step 11.
If no, go to step 13.
11
12
13
14
8-162
LAG alarms (Core-E, MPT-HC, MPT-HL, MPT-XP, ODU300, 9558HC, MSS-1 shelf Core)
TAP-118
3EM23956AM
Issue 01, February 2013
TAP-118
Ethernet connectivity fault management alarms
Purpose
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 Product Information (PN 3EM23952AM) to determine card location and
address.
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
Review the output. See Table 118-A for information about ECFM alarms.
8-163
TAP-118
3EM23956AM
Issue 01, February 2013
Friendly name/entity
Equipment type
See
MEP#MDID[1-16]#MA ID
[1-512]#MEPID[1-8191]
Core-E, MSS/CORE
Step 3
MEP#MDID[1-16]#MA ID
[1-512]#MEPID[1-8191]
Core-E, MSS/CORE
Step 7
MEP#MDID[1-16]#MA ID
[1-512]#MEPID[1-8191]
Core-E, MSS/CORE
Step 12
MEP#MDID[1-16]#MA ID
[1-512]#MEPID[1-8191]
Core-E, MSS/CORE
Step 17
Eth OAM
unexpectedMEPID
MEP#MDID[1-16]#MA ID
[1-512]#MEPID[1-8191]
Core-E, MSS/CORE
Step 22
MEP#MDID[1-16]#MA ID
[1-512]#MEPID[1-8191]
Core-E, MSS/CORE
Step 27
IXL-101
Were the alarms identified and cleared between the local and far end of the MEP?
If yes, go to step 5.
If no, go to step 32.
Retrieve MA ID for both ends of the MEP using WT CLI Tool. See WT CLI Tool
Reference Guide for more information.
8-164
TAP-118
9
3EM23956AM
Issue 01, February 2013
10
11
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?
If yes, go to step 15.
If no, go to step 32.
15
16
Did the Eth OAM Remote Defect Indication Level alarm clear?
If yes, go to step 33.
If no, go to step 32.
Retrieve the MD Level for both ends of the MEP using WT CLI Tool. See WT CLI Tool
Reference Guide for more information.
18
19
20
21
Retrieve MEPID for both ends of the MEP using WT CLI Tool. See WT CLI Tool
Reference Guide for more information.
8-165
TAP-118
3EM23956AM
Issue 01, February 2013
23
24
25
26
Retrieve the MEP Transmission Interval for both ends using WT CLI Tool. See WT
CLI Tool Reference Guide for more information.
28
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 10min, the alarm requires 35 minutes to clear.
30
31
32
33
8-166
TAP-119
3EM23956AM
Issue 01, February 2013
TAP-119
Clock 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.
See the 9500 MPR-A Product Information (PN 3EM23952AM) to determine card location and
address.
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
Review the output. See Table 119-A for information about Clock Failure alarms.
Table 119-A. Clock failure alarm
Probable cause
Friendly name/entity
Equipment type
Clock failure
Radio/Dir#1.[1-6]/
Slot#1/Port#[1-6]/Ch#[0-1]
Radio/Dir#1.[1-6]/MSS/
CORE/Port#[1-6]/Ch#[0-1]
Radio/Dir#[3-8].[1-4]/
Slot#[3-8]/Port#[1-4]/Ch#[0-1]
Radio/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#1
Radio/Dir#[3-8].[5-8]/
Slot#[3-8]/Port#[5-8]/Ch#[0-1]
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
See
IXL-101
8-167
TAP-119
3EM23956AM
Issue 01, February 2013
Clock failure
3
10
Is the MPT ODU in alarm associated with the Core-E/P8ETH card or MSS-1 shelf
Core?
If yes, go to step 11.
If no, go to step 20.
MPT ODU connected to Core-E/P8ETH card or MSS-1 shelf Core
11
8-168
TAP-119
12
3EM23956AM
Issue 01, February 2013
13
Dialog Failure is declared against the MPT ODU. Wait for Dialog Failure condition to
clear before proceeding.
14
15
16
17
Replace the MPT ODU in alarm. See DLP-115 to replace MPT ODU.
18
19
20
8-169
TAP-119
3EM23956AM
Issue 01, February 2013
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.
22
Dialog Failure is declared against the MPT ODU. Wait for Dialog Failure condition to
clear before proceeding.
23
24
25
26
Replace the MPT ODU in alarm. See DLP-115 to replace MPT ODU.
27
28
29
30
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.
33
34
8-170
TAP-119
35
3EM23956AM
Issue 01, February 2013
36
37
Replace the local MPT-HL. See DLP-108 to replace the MPT-HL transceiver.
38
39
40
41
42
43
Is the MPT ODU/MPT-HL declaring Clock Failure alarm the main or spare?
If main, go to step 44.
If spare, go to step 48.
44
45
46
47
Go to step 51.
8-171
TAP-119
3EM23956AM
Issue 01, February 2013
48
49
50
51
52
53
Dialog Failure is declared against the MPT ODU. Wait for Dialog Failure condition to
clear before proceeding.
54
55
56
Replace the MPT ODU in alarm. See DLP-115 to replace the MPT ODU.
57
8-172
TAP-119
58
3EM23956AM
Issue 01, February 2013
59
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.
62
63
64
65
66
67
68
69
70
71
72
Go to step 74.
73
74
8-173
3EM23956AM
Issue 01, February 2013
8-174
TAP-119
TAP-120
3EM23956AM
Issue 01, February 2013
TAP-120
Duplicate Address Detected alarms
Purpose
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:
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.
See the 9500 MPR-A Product Information (PN 3EM23952AM) to determine card location and
address.
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
Review the output. See Table 120-A for information about Duplicate address detected
alarms.
8-175
TAP-120
3EM23956AM
Issue 01, February 2013
Friendly name/entity
Equipment type
See
Duplicate address
detected
TMNEthernet/MngtPort
Core-E/TMN MGMT
Port
Step 3
TMNEthernet/Port#4
Core-E/TMN Port#4
Step 25
TMNInBand#[1-2]
Core-E/TMN In-Band
Port [1-2]
Step 47
PPP-IP/RF#[3-8]
MOD300
Step 63
PPP-IP/RF#1[1-6]
PPP-IP/RF#[3-8][1-4]
PPP-IP/RF#[3-8][5-8]
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]
Duplicate address
detected
IXL-101
Using the Craft Terminal, retrieve the provisioned IPv6 TMN Ethernet Configuration
value for the NE declaring duplicate address detected alarm.
Verify the desired IPv6 TMN Ethernet Configuration value for the NE according to
site engineering documentation.
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.
8-176
TAP-120
3EM23956AM
Issue 01, February 2013
Reprovision IPv6 TMN Ethernet Configuration value for the NE according to site
engineering documentation.
10
11
Go to step 14
12
13
14
15
16
Verify the desired IPv6 TMN Ethernet Configuration value for the far end NE
according to site engineering documentation.
17
18
Was the IPv6 address changed on-site at the near end or far end NE?
If yes, go to step 19.
If no, go to step 21.
19
20
Go to step 23
21
22
23
8-177
TAP-120
3EM23956AM
Issue 01, February 2013
24
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
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.
29
30
Reprovision IPv6 Port #4 TMN Ethernet Configuration value for the NE according to
site engineering documentation.
31
32
33
Go to step 36
34
35
36
8-178
TAP-120
37
3EM23956AM
Issue 01, February 2013
38
Verify the desired IPv6 Port #4 TMN Ethernet Configuration value for the far end NE
according to site engineering documentation.
39
40
Was the IPv6 address changed on-site at the near end or far end NE?
If yes, go to step 41.
If no, go to step 43.
41
42
Go to step 45
43
44
45
46
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
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.
8-179
TAP-120
3EM23956AM
Issue 01, February 2013
51
52
Reprovision IPv6 TMN In-Band Port #1/2 value for the NE according to site
engineering documentation.
53
54
55
56
57
Verify the desired IPv6 TMN In-Band Port #1/2 Ethernet Configuration value for the
far end NE according to site engineering documentation.
58
59
60
61
62
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.
8-180
TAP-120
65
3EM23956AM
Issue 01, February 2013
66
Reprovision Local IPv6 Address value for the NE according to site engineering
documentation.
67
68
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.
71
72
73
74
75
76
77
78
8-181
TAP-120
3EM23956AM
Issue 01, February 2013
79
80
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
83
84
85
86
87
88
89
8-182
DLP-100
3EM23956AM
Issue 01, February 2013
DLP-100
Mechanical card removal and installation
Purpose
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.
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
Card removal
5
Go to step 16.
9-1
DLP-100
3EM23956AM
Issue 01, February 2013
Card installation
9
10
11
12
13
14
15
16
9-2
DLP-101
3EM23956AM
Issue 01, February 2013
DLP-101
MPT-HL transceiver air filter replacement
Purpose
This procedure describes how to check and replace a dust filter on the MPT-HL Transceiver.
General
See the 9500 MPR-A Product Information (PN 3EM23952AM) to determine card location and type.
STEP
PROCEDURE
Loosen the screws securing the dust filter and cover to the front of the MPT-HL
Transceiver.
Tighten the screws securing the dust filter and cover to the MPT-HL transceiver.
9-3
3EM23956AM
Issue 01, February 2013
9-4
DLP-101
DLP-102
3EM23956AM
Issue 01, February 2013
DLP-102
SFP replacement
Purpose
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
See the 9500 MPR-A Product Information (PN 3EM23952AM) to determine card location and
address.
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
Ensure that the extractor for the SFP, PN 3AL 81424 AAAA, is available.
Go to step 11.
SFP replacement
9-5
DLP-102
3EM23956AM
Issue 01, February 2013
10
11
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
16
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
19
Is equipment protected?
If yes, go to step 20.
If no, go to step 24.
20
21
22
Go to step 24.
23
24
9-6
SFP replacement
DLP-103
3EM23956AM
Issue 01, February 2013
DLP-103
Core switching module (Core-E) replacement
Purpose
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.
See the 9500 MPR-A Product Information (PN 3EM23952AM) to determine card location and type.
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
9-7
DLP-103
3EM23956AM
Issue 01, February 2013
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.
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.
10
11
9-8
DLP-103
3EM23956AM
Issue 01, February 2013
Is the power still applied to the MSS-4/MSS-8 shelf where the Core-E is to be replaced
is equipped?
If yes, go to step 13.
If no, go to step 35.
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?
If yes, go to step 15.
If no, go to step 66.
15
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
20
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.
23
24
Install the replacement Core-E into shelf. See DLP-100 for information about how to
install the card.
25
9-9
DLP-103
3EM23956AM
Issue 01, February 2013
26
Verify the communication with the replacement Core-E using the Craft Terminal.
27
28
Does the replacement Core-E communicate properly and is the status is normal?
If yes, go to step 29.
If no, go to step 66.
29
30
31
On the Protection Schemes tab, release the Forced Switch Main Core-E.
32
Go to step 67.
33
34
Go to step 67.
Remove the Core-E to be replaced. See DLP-100 for information about how to remove
the card.
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.
37
Remove the flash card from the Core-E card removed in step 35 and install into the
replacement Core-E card.
38
Turn on shelf power and wait for the installed Core-E status LED to turn steady green.
39
40
Install the replacement Core-E into shelf. See DLP-100 for information about how to
install the card.
41
9-10
DLP-103
3EM23956AM
Issue 01, February 2013
42
Verify the communication with the replacement Core-E using the Craft Terminal.
43
44
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.
49
Remove the flash card from the Core-E card removed in step 47 and install into the
replacement Core-E card.
50
51
Install the replacement Core-E into shelf. See DLP-100 for information about how to
install the card.
52
53
Verify the communication with the replacement Core-E using the Craft Terminal.
54
55
Does the replacement Core-E communicate properly and is the status is normal?
If yes, go to step 67.
If no, go to step 66.
9-11
DLP-103
3EM23956AM
Issue 01, February 2013
Remove the Core-E to be replaced. See DLP-100 for information about how to remove
the card.
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.
58
Remove the flash card from the Core-E card removed in step 56 and install into the
replacement Core-E card.
59
60
Install the replacement Core-E into shelf. See DLP-100 for information about how to
install the card.
61
62
Wait for the replaced Core-E status LED to turn steady green.
63
Verify the communication with the replacement Core-E using the Craft Terminal.
64
65
Does the replacement Core-E communicate properly and is the status normal?
If yes, go to step 67.
If no, go to step 66.
66
67
9-12
DLP-104
3EM23956AM
Issue 01, February 2013
DLP-104
Core switching module (Core-E) flash card replacement
Purpose
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)
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.
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.
9-13
3EM23956AM
Issue 01, February 2013
DLP-104
See the 9500 MPR-A Product Information (PN 3EM23952AM) to determine card location and type.
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
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.
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.
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.
9-14
DLP-104
3EM23956AM
Issue 01, February 2013
10
11
12
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)
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
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.
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.
9-15
DLP-104
3EM23956AM
Issue 01, February 2013
17
Is the power still applied to MSS-4/8 shelf where flash card on the Core-E to be
replaced is equipped?
If yes, go to step 19.
If no, go to step 43.
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
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
23
On the Protection Schemes tab, perform a Forced EPS Switch Main Core-E.
24
Go to step 26.
25
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
29
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.
9-16
DLP-104
3EM23956AM
Issue 01, February 2013
30
31
32
Install the Core-E into shelf. See DLP-100 for information about how to install the
card.
33
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?
If yes, go to step 37.
If no, go to step 76.
37
38
39
On the Protection Schemes tab, release the Forced EPS Switch Main Core-E.
40
Go to step 77.
41
42
Go to step 77.
Remove the Core-E equipped with flash card to be replaced. See DLP-100 for
information about how to remove the card.
44
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.
9-17
DLP-104
3EM23956AM
Issue 01, February 2013
46
47
Turn on shelf power and wait for installed Core-E status LED to turn steady green
48
49
Install Core-E into shelf. See DLP-100 for information about how to remove the card.
50
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?
If yes, go to step 77.
If no, go to step 76.
Is power still applied to MSS-4/8 shelf where flash card on Core-E to be replaced is
equipped?
If yes, go to step 55.
If no, go to step 66.
56
Remove Core-E equipped with flash card to be replaced. See DLP-100 for detailed
steps to remove card.
57
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
9-18
DLP-104
3EM23956AM
Issue 01, February 2013
60
61
Install Core-E into shelf. See DLP-100 for information about how to remove the card.
62
63
Verify communication with the Core-E with replacement flash card using the Craft
Terminal.
64
Verify Core-E with replacement flash card status using the Craft Terminal.
65
Does Core-E with replacement flash card communicate properly and status normal?
If yes, go to step 77.
If no, go to step 76.
Remove Core-E equipped with flash card to be replaced. See DLP-100 for information
about how to remove the card.
67
68
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.
69
70
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.
74
Verify Core-E with replacement flash card status using the Craft Terminal.
9-19
DLP-104
3EM23956AM
Issue 01, February 2013
75
Does the Core-E with replacement flash card communicate properly and status
normal?
If yes, go to step 77.
If no, go to step 76.
76
77
9-20
DLP-105
3EM23956AM
Issue 01, February 2013
DLP-105
Ethernet access switch (P8ETH) replacement
Purpose
This procedure describes how to replace an Ethernet Access Switch (P8ETH) circuit pack.
Prerequisites
Although this procedure is typically used to replace a failed (inactive) component, always verify the
component state before removal.
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.
All plug-ins can be removed and installed with power applied.
See the 9500 MPR-A Product Information (PN 3EM23952AM) to determine card location and type.
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
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.
9-21
DLP-105
3EM23956AM
Issue 01, February 2013
10
11
12
13
9-22
DLP-105
3EM23956AM
Issue 01, February 2013
15
16
What is the role of P8ETH card being replaced the main or spare?
If main, go to step 17.
If spare, go to step 23.
17
18
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
24
25
26
Repeat steps 23 to 25 until all MPT-HL Transceiver ports are Lockout of Spare, then
go to step 27.
9-23
DLP-105
3EM23956AM
Issue 01, February 2013
27
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
32
33
34
35
Install the replacement P8ETH into the shelf. See DLP-100 for information about how
to install the card.
36
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
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?
If yes, go to step 42.
If no, go to step 71.
42
9-24
Verify the replacement P8ETH alarms and capable of carrying Ethernet traffic using
the Alarm Monitor and Craft Terminal.
DLP-105
43
3EM23956AM
Issue 01, February 2013
Is the replacement P8ETH status normal and is it capable of carrying Ethernet traffic?
If yes, go to step 44.
If no, go to step 71.
44
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
50
51
52
Repeat steps 49 to 51 until all MPT-HL Transceiver ports are released Lockout of
Spare, then go to step 72.
54
55
56
Verify that all cable connections to the P8ETH card to be replaced are properly
labeled.
9-25
DLP-105
3EM23956AM
Issue 01, February 2013
57
58
Remove the P8ETH to be replaced. See DLP-100 for information about how to remove
card.
59
60
61
62
Install the replacement P8ETH into the shelf. See DLP-100 for information about how
to install the card.
63
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
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?
If yes, go to step 69.
If no, go to step 71.
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?
If yes, go to step 72.
If no, go to step 71.
71
72
9-26
DLP-106
3EM23956AM
Issue 01, February 2013
DLP-106
MSS-4/8 shelf FAN replacement
Purpose
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
See the 9500 MPR-A Product Information (PN 3EM23952AM) to determine card location and type.
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
Confirm the replacement MSS-4/8 FAN card is available and of the same type
installed in the MSS-4/8 shelf.
Remove the FAN card. See DLP-100 for information about how to remove the card.
Install the replacement FAN card. See DLP-100 for information about how to install
the card.
9-27
DLP-106
3EM23956AM
Issue 01, February 2013
10
11
12
Does the FAN card operate properly, communicate properly, and the status is normal?
If yes, go to step 14.
If no, go to step 13.
13
14
9-28
DLP-107
3EM23956AM
Issue 01, February 2013
DLP-107
MOD300 (radio modem) replacement
Purpose
This procedure describes how to replace a MOD300.
Prerequisites
Although this procedure is typically used to replace a failed (inactive) component, always verify
component state before removal.
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.
All plug-ins can be removed and installed with power applied.
See the 9500 MPR-A Product Information (PN 3EM23952AM) to determine card location and type.
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
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.
9-29
DLP-107
3EM23956AM
Issue 01, February 2013
10
11
12
13
14
9-30
DLP-107
3EM23956AM
Issue 01, February 2013
15
Go to step 19.
16
17
18
19
20
21
22
23
Install the replacement MOD300 into shelf but do not seat the card at this time.
24
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?
If yes, go to step 28.
If no, go to step 34.
28
29
30
31
32
33
Go to step 35.
9-31
DLP-107
3EM23956AM
Issue 01, February 2013
34
35
9-32
DLP-108
3EM23956AM
Issue 01, February 2013
DLP-108
MPT-HL transceiver replacement
Purpose
This procedure describes how to replace a Microwave Packet Transport (MPT-HL) transceiver.
Prerequisites
Although this procedure is typically used to replace a failed (inactive) component, always verify
component state before removal.
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.
See the 9500 MPR-A Product Information (PN 3EM23952AM) to determine card location and type.
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
9-33
DLP-108
3EM23956AM
Issue 01, February 2013
10
CAUTION: Possibility of service interruption. Forced EPS and HSB switching traffic
causes a disruption to traffic.
11
12
13
14
15
Go to step 19.
16
9-34
DLP-108
3EM23956AM
Issue 01, February 2013
17
18
19
20
21
22
Remove the fuse in PDU that is suppling battery power to the MPT-HL transceiver.
23
24
Disconnect the GigE cable (optical or Molex) from the SFP port on the MPT-HL
transceiver.
25
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
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
31
32
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
9-35
DLP-108
3EM23956AM
Issue 01, February 2013
35
Connect the GigE cable (optical or Molex) into the SFP port on MPT-HL transceiver.
36
37
38
Install the fuse in the PDU that is suppling battery power to MPT-HL transceiver.
39
40
Ensure that the MPT-HL transceiver PA (Power Amplifier) switch is in the On (1)
position.
41
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?
If yes, go to step 45.
If no, go to step 51.
45
46
CAUTION: Possibility of service interruption. Releasing Forced EPS and HSB switch
causes a disruption to traffic.
47
48
49
50
Go to step 52.
51
52
9-36
DLP-109
3EM23956AM
Issue 01, February 2013
DLP-109
ODU300 replacement
Purpose
This procedure describes how to replace a Outdoor Unit (ODU300).
Prerequisites
Although this procedure is typically used to replace a failed (inactive) component, always verify the
component state before removal.
Before starting, verify that the replacement ODU300 matches the failed ODU300 using the following
procedure.
1.
2.
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.
All plug-ins can be removed and installed with power applied.
See the 9500 MPR-A Product Information (PN 3EM23952AM) to determine card location and type.
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.
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
1
PROCEDURE
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 replacement
9-37
DLP-109
3EM23956AM
Issue 01, February 2013
Is the MOD300 associated with the ODU300 to be replaced the main or spare?
If main, go to step 8.
If spare, go to step 10.
Go to step 11.
10
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
9-38
ODU300 replacement
DLP-109
3EM23956AM
Issue 01, February 2013
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
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
21
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
26
27
28
29
30
ODU300 replacement
9-39
3EM23956AM
Issue 01, February 2013
9-40
DLP-109
ODU300 replacement
DLP-110
3EM23956AM
Issue 01, February 2013
DLP-110
P2E3DS3 (2-Port DS3) replacement
Purpose
This procedure describes how to replace a P2E3DS3 card.
Prerequisites
Although this procedure is typically used to replace a failed (inactive) component, always verify
component state before removal.
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.
All plug-ins can be removed and installed with power applied.
See the 9500 MPR-A Product Information (PN 3EM23952AM) to determine card location and type.
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
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.
9-41
DLP-110
3EM23956AM
Issue 01, February 2013
10
11
12
13
Go to step 15.
14
15
16
9-42
DLP-110
3EM23956AM
Issue 01, February 2013
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
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
22
23
24
25
Verify the replacement P2E3DS3 alarms, that the status is normal, and capable of
carrying traffic using the Alarm Monitor and Craft Terminal.
26
27
28
29
30
Go to step 32.
31
32
9-43
3EM23956AM
Issue 01, February 2013
9-44
DLP-110
DLP-111
3EM23956AM
Issue 01, February 2013
DLP-111
P32E1DS1 (32-Port DS1) replacement
Purpose
This procedure describes how to replace a P32E1DS1 card.
Prerequisites
Although this procedure is typically used to replace a failed (inactive) component, always verify
component state before removal.
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.
All plug-ins can be removed and installed with power applied.
See the 9500 MPR-A Product Information (PN 3EM23952AM) to determine card location and type.
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
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.
9-45
DLP-111
3EM23956AM
Issue 01, February 2013
10
11
12
13
Go to step 15.
14
15
16
9-46
DLP-111
3EM23956AM
Issue 01, February 2013
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
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
22
23
24
25
Verify the replacement P32E1DS1 alarms, that the status is normal, and capable of
carrying traffic using the Alarm Monitor and Craft Terminal.
26
27
28
29
30
Go to step 32.
31
32
9-47
3EM23956AM
Issue 01, February 2013
9-48
DLP-111
DLP-112
3EM23956AM
Issue 01, February 2013
DLP-112
Clean fiber-optic connectors
Purpose
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:
CLETOP1 fiber-optic cleaner, Aerotech World Trade Ltd. PN 14100500 for all
fiber-optic connectors except bulkhead type
General
If the cleaning method described in this procedure does not produce acceptable results, the connector
may need to be replaced.
9-49
3EM23956AM
Issue 01, February 2013
DLP-112
See the 9500 MPR-A Product Information (PN 3EM23952AM) to determine card location and type.
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
9-50
DLP-112
3EM23956AM
Issue 01, February 2013
PARTICLES
FIBER CONTAMINATED
WITH SOLID PARTICLES
FIBER
CLADDING
FIBER CONTAMINATED
WITH OIL (FINGERPRINT)
CORE
FERRULE
(SHAPE CAN VARY
BY CONNECTOR TYPE)
CLEAN FIBER
129-1280-1
021607
Use an optical power meter to determine if light is coming out of fiber-optic connector.
Does the optical power meter detect light coming out of fiber-optic connector?
If yes, go to step 7.
If no, go to step 8.
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.
9-51
DLP-112
3EM23956AM
Issue 01, February 2013
10
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.
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
FC CONNECTOR
MU FIBER CONNECTOR
SC CONNECTOR
ST CONNECTOR
LC FIBER CONNECTOR
950-0151-1
092109
9-52
DLP-112
3EM23956AM
Issue 01, February 2013
FC CONNECTOR
SC CONNECTOR
ST/STII CONNECTOR
950-0150-1
092109
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
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.
9-53
DLP-112
3EM23956AM
Issue 01, February 2013
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
Inspect connector
19
20
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.
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
22
23
Remove the permanent plastic cap retainer, if applicable. Follow customer practices.
24
25
9-54
DLP-113
3EM23956AM
Issue 01, February 2013
DLP-113
System power down and power up
Purpose
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.
See the 9500 MPR-A Product Information (PN 3EM23952AM) to determine card location and type.
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
9-55
DLP-113
3EM23956AM
Issue 01, February 2013
Select an action?
If the system power is down, go to step 6.
If the system power is up, go to step 13.
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 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.
11
Remove the fuses in PDU that are suppling battery power to the MSS-1/4/8 shelf.
12
Go to step 20.
9-56
DLP-113
3EM23956AM
Issue 01, February 2013
Install the fuses in PDU that are suppling battery power to the MSS-1/4/8 shelf.
14
15
Install the fuses in PDU that are suppling battery power to all MPT-HL transceivers
in the system.
16
17
18
19
Verify that there are no unexpected alarms and conditions on the system.
20
9-57
3EM23956AM
Issue 01, February 2013
9-58
DLP-113
DLP-114
3EM23956AM
Issue 01, February 2013
DLP-114
MPTACC (MPT Access) replacement
Purpose
This procedure describes how to replace an MPTACC.
Prerequisites
Although this procedure is typically used to replace a failed (inactive) component, always verify
component state before removal.
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.
All plug-ins can be removed and installed with power applied.
See the 9500 MPR-A Product Information (PN 3EM23952AM) to determine card location and type.
See the 9500 MPR-A Operation and Administration (PN 3EM23954AM) for detailed procedures to
execute the commands included in this procedure.
STEP
1
PROCEDURE
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.
9-59
DLP-114
3EM23956AM
Issue 01, February 2013
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.
9-60
b.
c.
d.
DLP-114
3EM23956AM
Issue 01, February 2013
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
12
13
14
15
16
17
18
19
20
21
Go to step 25.
22
23
9-61
DLP-114
3EM23956AM
Issue 01, February 2013
24
25
26
27
Verify that all cable connections to the MPTACC to be replaced are properly labeled.
28
29
Remove the MPTACC to be replaced. See DLP-100 for information about how to
remove the card.
30
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.
33
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?
If yes, go to step 37.
If no, go to step 43.
37
38
39
40
9-62
DLP-114
3EM23956AM
Issue 01, February 2013
41
42
Go to step 44.
43
44
9-63
3EM23956AM
Issue 01, February 2013
9-64
DLP-114
DLP-115
3EM23956AM
Issue 01, February 2013
DLP-115
MPT 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
Although this procedure is typically used to replace a failed (inactive) component, always verify the
component state before removal.
Before starting, verify that the replacement MPT ODU matches the failed MPT ODU using the
following procedure.
1.
2.
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 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
In protected radio configurations, the associated radio port is supported in the following:
9-65
DLP-115
3EM23956AM
Issue 01, February 2013
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.
PROCEDURE
9-66
DLP-115
5
3EM23956AM
Issue 01, February 2013
Is the radio channel associated with the MPT ODU to be replaced in a protected
system?
If yes, go to step 6.
If no, go to step 15.
Is the radio channel associated with the MPT ODU to be replaced the main or spare?
If main, go to step 8.
If spare, go to step 12.
10
11
Go to step 15.
12
13
14
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 MPT Extended Power Unit, DC+ODU
Data connection, disconnect the DC+ODU cable connection to the MPT ODU at
the MPT Extended Power Unit.
9-67
DLP-115
3EM23956AM
Issue 01, February 2013
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.
17
Verify that all cable connections to the MPT ODU to be replaced are properly labeled.
18
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
27
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.
9-68
DLP-115
31
3EM23956AM
Issue 01, February 2013
Is the replacement MPT ODU status normal and capable of carrying traffic?
If yes, go to step 32.
If no, go to step 37.
32
33
34
35
36
37
38
9-69
3EM23956AM
Issue 01, February 2013
9-70
DLP-115
DLP-116
3EM23956AM
Issue 01, February 2013
DLP-116
Auxiliary (AUX) replacement
Purpose
This procedure describes how to replace an AUX card.
Prerequisites
Although this procedure is typically used to replace a failed (inactive) component, always verify
component state before removal.
General
The AUX card can be installed in MSS-8 slot 8 and MSS-4 slot 4.
All plug-ins can be removed and installed with power applied.
See the 9500 MPR-A Product Information (PN 3EM23952AM) to determine card location and type.
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
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.
9-71
DLP-116
3EM23956AM
Issue 01, February 2013
Verify that all cable connections to the AUX card to be replaced are properly labeled.
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.
11
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.
14
15
Verify the replacement AUX alarms, that the status is normal using the Alarm
Monitor and Craft Terminal.
16
17
18
9-72
DLP-117
3EM23956AM
Issue 01, February 2013
DLP-117
Protection upgrade and downgrade procedures
Purpose
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
9-73
DLP-117
3EM23956AM
Issue 01, February 2013
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.
See the 9500 MPR-A Product Information (PN 3EM23952AM) to determine card location and type.
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
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
9-74
DLP-117
3EM23956AM
Issue 01, February 2013
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
Connect the DS1 or DS3 cables to spare the P32E1DS1/P2E3DS3 card that you
installed in step 7.
On CT settings window, enable the spare P32E1DS1/P2E3DS3 card that you installed
in step 7.
10
11
12
Go to step 75.
14
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.
On CT settings window, set the P32E1DS1/P2E3DS3 cards protection type to No
Protection.
15
16
Disconnect the DS1 or DS3 cables from spare the P32E1DS1/P2E3DS3 card.
17
9-75
3EM23956AM
Issue 01, February 2013
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
19
Go to step 75.
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.
9-76
DLP-117
3EM23956AM
Issue 01, February 2013
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
29
30
Go to step 75.
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
9-77
DLP-117
3EM23956AM
Issue 01, February 2013
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
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.
9-78
DLP-117
42
3EM23956AM
Issue 01, February 2013
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
47
48
49
50
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.
53
54
Set the radio direction Protection Type to 1+1 HSB(SD) or 1+1 FD.
55
9-79
DLP-117
3EM23956AM
Issue 01, February 2013
56
NOTE: To complete the upgrade from fixed modulation to adaptive modulation both ends of
the radio hop must be upgraded.
57
58
Verify that the radio direction is error free and operating as expected.
59
Go to step 75.
61
Open the radio channel view. Take a screen capture to save all radio channel
provisioning information.
62
63
64
65
From the radio direction Mode drop-down menu, choose Presetting and click on the
Apply button.
66
67
Set the radio direction Protection Type to 1+1 HSB(SD) or 1+1 FD.
68
69
70
71
Configure the local ATPC Tx range, remote ATPC Rx threshold, and click on the Apply
button.
9-80
DLP-117
3EM23956AM
Issue 01, February 2013
72
NOTE: To complete the upgrade from adaptive modulation to fixed modulation both ends of
the radio hop must be downgraded.
73
74
Verify that they radio direction is error free and operating as expected.
75
9-81
3EM23956AM
Issue 01, February 2013
9-82
DLP-117
DLP-118
3EM23956AM
Issue 01, February 2013
DLP-118
Upgrade and downgrade radio profile
Purpose
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.
See the 9500 MPR-A Product Information (PN 3EM23952AM) to determine card location and type.
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
1
PROCEDURE
Select an action?
To Upgrade radio profile, go to step 2.
To Downgrade radio profile, go to step 12.
9-83
DLP-118
3EM23956AM
Issue 01, February 2013
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.
From the radio direction Reference Channel Spacing drop-down menu, select new
channel bandwidth.
From the radio direction Modulation drop-down menu, select the new modulation
value.
Verify the Tx power provisioning and adjust, as described in the site documentation.
NOTE: To complete an upgrade of a radio profile, both ends of the radio hop must be
upgraded.
10
Verify that the radio direction is error free and operating as expected.
11
Go to step 22.
13
Open the radio channel view. Take a screen capture to save all radio channel
provisioning information.
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
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.
20
9-84
DLP-118
3EM23956AM
Issue 01, February 2013
21
Verify that the radio direction is error free and operating as expected.
22
9-85
3EM23956AM
Issue 01, February 2013
9-86
DLP-118
DLP-119
3EM23956AM
Issue 01, February 2013
DLP-119
Upgrade unlicensed MPT-HL radio to lower 6 GHz radio
Purpose
This procedure describes how to upgrade a MPT-HL unlicensed radio hop to a lower 6 GHz radio hop
on the 9500 MPR-A system.
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.
See the 9500 MPR-A Product Information (PN 3EM23952AM) to determine card location and type.
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
9-87
3EM23956AM
Issue 01, February 2013
DLP-119
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.
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
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
17
9-88
DLP-119
3EM23956AM
Issue 01, February 2013
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
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.
b.
Enter the TX Frequency within the allowed range. The Rx Freq (KHz) displays the
Rx RF Frequency.
c.
d.
e.
f.
g.
h.
i.
j.
k.
l.
Go to step 24.
9-89
DLP-119
3EM23956AM
Issue 01, February 2013
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.
27
28
Verify that the radio direction is error free and operating as expected.
29
9-90
DLP-120
3EM23956AM
Issue 01, February 2013
DLP-120
+24/-48 volt converter replacement
Purpose
This procedure describes how to replace a +24/-48 volt Converter.
Prerequisites
Although this procedure is typically used to replace a failed (inactive) component, always verify
component state before removal.
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.
See the 9500 MPR-A Product Information (PN 3EM23952AM) to determine card location and type.
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
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.
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.
9-91
DLP-120
3EM23956AM
Issue 01, February 2013
Is traffic affected?
b.
c.
9-92
DLP-120
3EM23956AM
Issue 01, February 2013
Main
(A-Side)
Power
Protect
(B-Side)
Power
Main Power
Converter
Cable Assemblies:
3DB18271AA
Protect Power
Converter
950-0152-1
101910
10
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.
14
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
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?
If yes, go to step 21.
If no, go to step 20.
9-93
DLP-120
3EM23956AM
Issue 01, February 2013
20
21
9-94
DLP-121
3EM23956AM
Issue 01, February 2013
DLP-121
Power injector replacement
Purpose
This procedure describes how to replace a Power Injector card and Power Injector box.
Perquisites
Although this procedure is typically used to replace a failed (inactive) component, always verify
component state before removal.
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.
See the 9500 MPR-A Product Information (PN 3EM23952AM) to determine card location and type.
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
9-95
DLP-121
3EM23956AM
Issue 01, February 2013
b.
Verify that the appropriate maintenance window is scheduled per local practices and
procedures.
10
11
Verify that all cable connections to the Power Injector to be replaced are properly
labeled.
12
9-96
DLP-121
3EM23956AM
Issue 01, February 2013
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
16
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.
22
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?
If yes, go to step 30.
If no, go to step 29.
9-97
3EM23956AM
Issue 01, February 2013
29
30
9-98
DLP-121
DLP-122
3EM23956AM
Issue 01, February 2013
DLP-122
RPS/XPIC module replacement
Purpose
This procedure describes how to replace a RPS and XPIC module on the MPT-HC/MPT-XP/9558HC
(MPT ODU).
Prerequisites
Although this procedure is typically used to replace a failed (inactive) component, always verify
component state before removal.
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.
Table 122-A. MPT ODU 1+1 module details
ITEM DESCRIPTION
Part Number
XPIC Module
3DB20116BA/BB
RPS Module
3DB20117BA
See the 9500 MPR-A Product Information (PN 3EM23952AM) to determine card location and type.
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.
See the 9500 MPR-A Operation and Administration (PN 3EM23954AM) for information about how
to execute the commands that are described in this procedure.
9-99
DLP-122
3EM23956AM
Issue 01, February 2013
STEP
PROCEDURE
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.
Is the radio channel that is associated with the RPS/XPIC to be replaced the main or
spare?
If main, go to step 9.
If spare, go to step 13.
10
11
12
Go to step 20.
9-100
DLP-122
3EM23956AM
Issue 01, February 2013
13
14
15
16
Go to step 20.
17
18
Go to step 20.
19
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
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
26
27
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.
9-101
DLP-122
3EM23956AM
Issue 01, February 2013
30
31
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
36
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
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.
42
43
44
45
9-102
DLP-122
3EM23956AM
Issue 01, February 2013
46
47
9-103
3EM23956AM
Issue 01, February 2013
9-104
DLP-122
DLP-123
3EM23956AM
Issue 01, February 2013
DLP-123
Upgrade MPT ODU to MPT ODU L1 LAG port
Purpose
This procedure describes how to upgrade an Out-of-Service MPT-HC/MPT-XP/9558HC (MPT ODU)
radio hop to an MPT ODU configured as the L1 LAG Master Port.
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:
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.
Before starting this procedure, read and fully understand this procedure and all referenced
procedures in their entirety.
See the 9500 MPR-A Product Information (PN 3EM23952AM) to determine card location and type.
See the 9500 MPR-A Operation and Administration (PN 3EM23954AM) for information about how
to execute the commands that are described in this procedure.
9-105
DLP-123
3EM23956AM
Issue 01, February 2013
STEP
PROCEDURE
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.
9-106
Cross-Connection
DLP-123
3EM23956AM
Issue 01, February 2013
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:
17
a.
b.
Disable MPTACC card. See the 9500 MPR-A Operation and Administration
Manual, DLP-105 for a detailed procedure.
c.
d.
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
9-107
DLP-123
3EM23956AM
Issue 01, February 2013
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.
26
27
Verify that the radio direction is error free and operating as expected.
28
9-108
DLP-124
3EM23956AM
Issue 01, February 2013
DLP-124
Upgrade MPT-HL to MPT-HL L1 LAG port
Purpose
This procedure describes how to upgrade an In-Service MPT-HL radio hop to an MPT-HL configured
as an L1 LAG Lowest Index Port.
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:
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.
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
9-109
DLP-124
3EM23956AM
Issue 01, February 2013
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)
DS1 TDM2TDM
2080
1683
DS1 TDM2Eth
1882
1694
DS3 TDM2TDM
60264
48756
DS3 TDM2Eth
46571
45574
CAUTION: Possibility of service interruption: Migration to L1 LAG port impacts TDM2TDM and TDM2ETH
traffic on a per flow-id basis. Typical impact to traffic is less than 10 seconds for each cross-connection.
The time required for the system to migrate the MPT-HL radio port to the L1 LAG port is dependent upon
radio port provisioning (synchronization, PPP RF, number of; port segregations, VLANs, and
cross-connections). Typical migration duration is less than two minutes. Allow up to five minutes for the
system to migrate all services from the MPT-HL radio port to the L1 LAG port.
The number of possible radio configurations precludes covering all possible radio configurations.
A site survey and site documentation must be provided to ensure that facilities that are NOT
associated with the upgrade MPT-HL radio direction are not impacted by this upgrade procedure.
To complete the migration to an L1 LAG port, both ends of the MPT-HL radio direction must be
migrated.
Before starting this procedure, read and fully understand this procedure and all referenced
procedures in their entirety.
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.
9-110
DLP-124
3EM23956AM
Issue 01, February 2013
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
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
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.
9-111
3EM23956AM
Issue 01, February 2013
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:
14
Rx Radio (RPS)
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
19
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.
9-112
DLP-124
3EM23956AM
Issue 01, February 2013
21
22
23
24
25
26
27
Verify that the radio direction is error free and operating as expected.
28
29
Using the Current Configuration files downloaded in steps 16 and 28, verify that the
following provisioning parameters were re-provisioned correctly:
9-113
3EM23956AM
Issue 01, February 2013
30
Cross-Connections
VLANs
Port Segregation
PPP-RF
Synchronization
DLP-124
Rx Radio (RPS)
31
NOTE: To complete the upgrade to MPT-HL L1 LAG Port, this procedure must be
32
9-114
DLP-125
3EM23956AM
Issue 01, February 2013
DLP-125
MPT Power Unit replacement
Purpose
This procedure describes how to replace a MPT Power Unit or MPT Extended Power Unit.
Prerequisites
Although this procedure is typically used to replace a failed (inactive) component, always verify
component state before removal.
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.
See the 9500 MPR-A Product Information (PN 3EM23952AM) to determine card location and type.
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
9-115
DLP-125
3EM23956AM
Issue 01, February 2013
Does the Power Unit support one, two, or more radio channels?
b.
Verify that the appropriate maintenance window is scheduled per local practices and
procedures.
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
14
15
Connect all of the cables to the front of the Power Unit that you disconnected in
step 12.
16
Install the fuses protecting the A and B battery feeds removed in step 11.
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.
9-116
DLP-125
3EM23956AM
Issue 01, February 2013
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?
If yes, go to step 22.
If no, go to step 21.
21
22
9-117
3EM23956AM
Issue 01, February 2013
9-118
DLP-125
DLP-126
3EM23956AM
Issue 01, February 2013
DLP-126
SDHACC (2-Port OC-3) Replacement
PURPOSE
This procedure describes how to replace a SDHACC card.
PREREQUISITES
Although this procedure is typically used to replace a failed (inactive) component, always verify
component state before removal.
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.
All plug-ins can be removed and installed with power applied.
See the 9500 MPR-A Product Information (PN 3EM23952AM) to determine card location and type.
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
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.
9-119
DLP-126
3EM23956AM
Issue 01, February 2013
10
11
12
13
Go to step 15.
14
9-120
DLP-126
3EM23956AM
Issue 01, February 2013
15
16
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
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
22
23
24
25
Verify the replacement SDHACC alarms, that the status is normal, and capable of
carrying traffic using the Alarm Monitor and Craft Terminal.
26
27
28
29
30
Go to step 32.
9-121
DLP-126
3EM23956AM
Issue 01, February 2013
31
32
9-122
DLP-127
3EM23956AM
Issue 01, February 2013
DLP-127
Software package rollback
Purpose
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:
Table 127-A. Releases supporting software package rollback
Initial software
release version
(Current Status: Stand by)
Upgrade software
release version
(Current Status: Committed)
Software package
rollback support
R4.0.0
No
R3.4.0
R4.1.0
No
R4.0.0 or greater
R4.1.0 or greater
Yes
For a full description of the software package rollback feature, see the 9500 MPR-A Product
Information (PN 3EM23952AM).
STEP
1
PROCEDURE
CAUTION: Possibility of service interruption. The software package rollback operation
WILL impact traffic including a possible long out-of service period. For this reason
software package rollback should be considered as a critical operation to be performed
as a last resort only after all other alternatives have been explored.
9-123
DLP-127
3EM23956AM
Issue 01, February 2013
Have all appropriate levels of support been notified and all are in agreement that a
software package rollback is the appropriate next step?
If yes, go to step 6.
If no, go to step 4.
Contact ALL appropriate levels of support and obtain all appropriate approvals as
required per local practices and procedures.
Have all appropriate levels of support been notified and are in agreement that a
software package rollback is the appropriate next step?
If yes, go to step 6.
If no, go to step 19.
On the software bank with the Current Status Committed, verify the software version
matches that of the upgraded software package. See figure 127-2
9-124
DLP-127
3EM23956AM
Issue 01, February 2013
Figure 127-2. Software bank with upgrade software version Committed status
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-3. Software bank with Initial software version Standby status
9-125
DLP-127
3EM23956AM
Issue 01, February 2013
10
Are the committed (upgrade) and standby (initial) software version verified and
correct as expected?
If yes, go to step 11.
If no, go to step 19.
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
Figure 127-4. Software Management Action - Forced Activation
12
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
15
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
9-126
DLP-127
3EM23956AM
Issue 01, February 2013
Figure 127-5. Software bank with initial software version Committed status
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-6. Software bank with upgrade software version Standby status
9-127
DLP-127
3EM23956AM
Issue 01, February 2013
18
Are the committed (initial) and standby (upgrade) software version verified and
correct as expected?
If yes, go to step 20.
If no, go to step 19.
19
20
9-128
DLP-128
3EM23956AM
Issue 01, February 2013
DLP-128
MSS-1 shelf replacement
Purpose
This procedure describes how to replace a MSS-1 shelf.
Prerequisites
Although this procedure is typically used to replace a failed (inactive) component, always verify
component state before removal.
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.
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
1
PROCEDURE
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.
9-129
DLP-128
3EM23956AM
Issue 01, February 2013
b.
c.
Verify that the appropriate maintenance window is scheduled per local practices and
procedures.
Verify that all cable connections to the MSS-1 shelf to be replaced are properly labeled.
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
12
13
Connect all of the cables to the front of the MSS-1 shelf that you disconnected in
step 10.
14
Install the fuses protecting the A and B battery feeds removed in step 9.
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.
9-130
DLP-128
3EM23956AM
Issue 01, February 2013
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?
If yes, go to step 22.
If no, go to step 19.
19
20
21
22
Are ALL the Ethernet ports that are associated with the replacement MSS-1 shelf
error free and free of alarms?
If yes, go to step 26.
If no, go to step 23.
23
24
25
26
Are ALL the MSS-1 shelf DS1 ports that are associated with the replacement MSS-1
shelf error free and free of alarms?
If yes, go to step 31.
If no, go to step 27.
27
28
9-131
DLP-128
3EM23956AM
Issue 01, February 2013
29
30
31
9-132
Technical support
http://support.alcatel-lucent.com
Documentation feedback
documentation.feedback@alcatel-lucent.com