Loopstar 800 Series: Maintenance Manual

LoopStar® 800 Series
Maintenance Manual
LPS-800 LPS-810
Product Catalog: LPS-FRM8xx-Lx

Document Number: LPS800-UM-MAIN-02
REVISION HISTORY
The Revision History provides a summary of any changes in this manual. Please make sure you are using the
latest revision of this manual.
July 27, 2005
Revision Release Date Revisions Made

01 January 12, 2005 Initial Release
02 July 27, 2005 Updated with LPS-800 Release 2 and
LPS-810 Release 1.
This manual is available online at ADC’s website (www.adc.com/documentationlibrary/) or you can order copies
of the manual by contacting your sales representative. Please ask for document LPS800-UM-MAIN-02.
Copyright
©2005 ADC Telecommunications, Inc. All rights reserved.
Trademark Information
ADC and LoopStar are registered trademarks of ADC Telecommunications, Inc. No right, license, or interest to such trade-
marks is granted hereunder, and you agree that no such right, license, or interest shall be asserted by you with respect to
such trademark.
Other product names mentioned in this practice are used for identification purposes only and may be trademarks or regis-
tered trademarks of their respective companies.
Disclaimer of Liability
Information contained in this document is company private to ADC Telecommunications, Inc. and shall not be modified,
used, copied, reproduced or disclosed in whole or in part without the written consent of ADC.
Contents herein are current as of the date of publication. ADC reserves the right to change the contents without prior notice.
In no event shall ADC be liable for any damages resulting from loss of data, loss of use, or loss of profits, and ADC further
disclaims any and all liability for indirect, incidental, special, consequential or other similar damages. This disclaimer of
liability applies to all products, publications and services during and after the warranty period.
Table of Contents
About This Manual ..........................................................................................................ix
Introduction ...............................................................................................................................ix
Related Manuals .......................................................................................................................ix
Organization ...............................................................................................................................x
Intended Audience .....................................................................................................................x
Conventions ..............................................................................................................................xi
Inspecting Your Shipment .........................................................................................................xi
Chapter 1: Maintenance Overview ................................................................................ 1-1
Running Environment of LoopStar 800 Series ......................................................................... 1-1
Precautions of Maintenance Operations .................................................................................. 1-2
Chapter 2: Basic Operations ......................................................................................... 2-1
Fan Maintenance ..................................................................................................................... 2-1
Plug/Unplug Fiber Jumpers ...................................................................................................... 2-2
Plug/Unplug Units ..................................................................................................................... 2-2
Audible Alarm Cut-Off .............................................................................................................. 2-3
Resets ...................................................................................................................................... 2-3
Cleaning Fiber Connectors ...................................................................................................... 2-3
Bit Error Rate Testing ............................................................................................................... 2-4
Transmitter/Receiver Optical Power Testing ............................................................................ 2-5
Chapter 3: Routine Maintenance ................................................................................... 3-1
Overview .................................................................................................................................. 3-1
Routine Maintenance Items ..................................................................................................... 3-2
Chapter 4: Loopback and Network Test ....................................................................... 4-1
Loopbacks ................................................................................................................................ 4-1
Identifing Network Faults .......................................................................................................... 4-3
Chapter 5: Replace Hardware ........................................................................................ 5-1
Overview .................................................................................................................................. 5-1
General Precautions ................................................................................................................ 5-2
Chapter 6: FAQ ................................................................................................................ 6-1
Login ......................................................................................................................................... 6-1
Timing ....................................................................................................................................... 6-3
Protection ................................................................................................................................. 6-5
Connection ............................................................................................................................. 6-10
Performance Monitoring ..........................................................................................................6-11
Alarm Mornitoring and Management ...................................................................................... 6-12
Unit Configuration ................................................................................................................... 6-13
LPS800-UM-MAIN-02 iii
Table of Contents July 27, 2005
Appendix A: Regular Maintenance Recommendation .............................................. A-1

Daily Maintenance and Operation Guide ................................................................................ A-2
Monthly Maintenance and Operation Guide ........................................................................... A-4
Quarterly Maintenance and Operation Guide ......................................................................... A-5
Annual Maintenance and Operation Guide ............................................................................. A-5
Daily Maintenance Record ....................................................................................................... A-6
Monthly (Quarterly) Maintenance Record ................................................................................ A-8
Annual Maintenance Record .................................................................................................... A-9
Emergency Troubleshooting Record ........................................................................................ A-9
Unit Replacement Record ..................................................................................................... A-10
Data Modification Record ...................................................................................................... A-10
Appendix B: Serious Failure Processing Flow .......................................................... B-1
Flow Chart of Serious Fault Handling ...................................................................................... B-1
Flow Description and Precautions ............................................................................................ B-3
Recommendation ..................................................................................................................... B-3
Appendix C: Product Support ..................................................................................... C-1
Glossary ......................................................................................................................GL-1
iv LPS800-UM-MAIN-02
List of Figures
Figure 2-1. Install the Fan Tray and Air Filter (LPS-810) .................................................... 2-1
Figure 2-2. Fiber jumper with LC optical interface .............................................................. 2-2
Figure 2-3. Bit error test ...................................................................................................... 2-4
Figure 3-1. LPS-800 System status panel .......................................................................... 3-3
Figure 3-2. LPS-810 System status panel .......................................................................... 3-3
Figure 4-1. Perform a facility loopback on NE-A’s DSn processing unit ............................. 4-3
Figure 4-2. Perform a path loopback on the NE-A .............................................................. 4-5
Figure 4-3. Perform a terminal loopback on NE-A’s OC-N interface unit ........................... 4-7
Figure 4-4. Perform a facility loopback on NE-B’s westward OC-N interface unit .............. 4-8
Figure 4-5. Perform a terminal loopback on NE-B’s eastward OC-N interface unit .......... 4-10
Figure 4-6. Perform a facility loopback on NE-C’s westward OC-N interface unit ............ 4-11
Figure 4-7. Perform a path loopback on the NE-C ........................................................... 4-13
Figure 4-8. Perform a terminal loopback on NE-C’s DSn processing unit ........................ 4-15
Figure 4-9. Perform a facility loopback on NE-C’s DSn processing unit .......................... 4-17
Figure 5-1. Specification mark of the unit ........................................................................... 5-2
Figure B-1. Flow chart of serious fault handling ..................................................................B-2
LPS800-UM-MAIN-02 v
List of Figures July 27, 2005
vi LPS800-UM-MAIN-02
List of Tables
Table 1-1. Temperature and humidity requirements ............................................................. 1-1
Table 3-1. Typical routine maintenance item ........................................................................ 3-2
Table 3-2. Indicators and their meanings ............................................................................. 3-4
Table 3-3. Ambient temperature requirements for equipment operation ............................. 3-5
Table 5-1. Operation and Precautions of Unit Replacement ................................................ 5-1
Table A-1.Instruction ............................................................................................................A-1
Table A-1.Attached: machine room cleanliness requirement .............................................A-3
LPS800-UM-MAIN-02 vii
List of Tables July 27, 2005
viii LPS800-UM-MAIN-02
ABOUT THIS MANUAL
INTRODUCTION
This manual applies to LoopStar® 800 Series Maintenance Manual.
RELATED MANUALS
The following table lists the manuals in the LoopStar 800 Series (LPS-800/LPS-810) suite of documents. In this
document, the LoopStar 800 Series is designated as LPS-8xx. The current manual is highlighted.
Manual Usage
LoopStar® 800 Series Maintenance Manual Describes how to perform routine maintenance and how to
troubleshoot the LoopStar 800 Series system.
LoopStar® 800 Series System Application and Acquaints you with the LoopStar 800 Series and describes how
Engineering Guide to build the required network using the LoopStar 800 Series.
LoopStar® 800 Series WebLCT Introduces configuration and maintenance operations of

LoopStar 800 Series WebLCT.
LoopStar® 800 Series EMS Operations Introduces configuration and maintenance operations of
LoopStar 800 Series EMS.
LoopStar® 800 Series EMS System Introduces the application, functional characteristics, system
Description architecture, and networking mode of the LoopStar 800 Series
EMS, appended with standards that the LoopStar 800 Series
EMS complies with, abbreviations and performance indices.
LoopStar® 800 Series EMS Installation Introduces installation procedures and FAQs of the LoopStar 800
Manual Series EMS running on Windows 2000 and Solaris 8 platforms.
LoopStar® 800 Series Installation Manual Describes how to install the LoopStar 800 Series.
LoopStar® 800 Series Hardware Description Describes the LoopStar 800 Series system hardware including
Manual chassis, power interface module, fan tray assembly, plug-in units,
and the interfaces.
LoopStar® 800 Series System Administration Describes how to implement and use the LoopStar 800 Series in
Manual a network management system (NMS).
LoopStar® 800 Series TL1 Commands Manual Detailed introduction to the TL1 commands used in the LoopStar
800 Series.
LoopStar® 800 Series Alarm and Performance Describes alarm and performance monitoring.
Reference Manual
LPS800-UM-MAIN-02 ix
About This Manual July 27, 2005
ORGANIZATION
This manual includes the following chapters:
Chapter Description
Chapter 1: “Maintenance Overview” Introduces the running environment of the equipment and
precautions of maintenance operations.
Chapter 2: “Basic Operations” Introduces the contents and procedures of the basic
maintenance of the LoopStar 800.
Chapter 3: “Routine Maintenance” Introduces the contents and procedures of the routine
maintenance of the LoopStar 800, offering basic methods and
references which may help the user in making routine
maintenance schemes.
Chapter 4: “Loopback and Network Test” Introduces the methods of fault localization.
Chapter 5: “Replace Hardware” Introduces the operation as well as events requiring attention
during unit replacement.
Chapter 6: “FAQ” Covers the common problems you may come across and the
corresponding troubleshooting methods.
Appendix A: “Regular Maintenance Provides recommendations of daily maintenance work and gives
Recommendation” some tables for your reference.
Appendix B: “Serious Failure Processing Recommends treatment strategy for serious failure.
Flow”
Appendix C: “Product Support” Provides information on how to contact the ADC Technical
Support group.
Glossary Defines abbreviations, acronyms, and terms for the LoopStar 800
product line.
INTENDED AUDIENCE
This manual is intended for:
• Operations groups
• Maintenance engineers
x LPS800-UM-MAIN-02
July 27, 2005 About This Manual
CONVENTIONS
The following style conventions and terminology are used throughout this guide.
Element Meaning
Bold font Text that you must input exactly as shown (e.g., type 1 for card 1), menu buttons
(e.g., ACCEPT SHELF OPTIONS) or menu screen options (e.g., ALARMS screen) that
you must select
Italic font Variables that you must determine before inputting the correct value (e.g., Password )
Monospace font References to screen prompts (e.g., Invalid Password...Try Again:.)
Reader Alert Meaning

Alerts you to supplementary information
IMPORTANT Alerts you to supplementary information that is essential to the completion of a task
!
Alerts you to possible equipment damage from electrostatic discharge
ATTENTION
CAUTION Alerts you to possible data loss, service-affecting procedures, or other similar type
problems
Alerts you that failure to take or avoid a specific action might result in hardware damage or
WARNING
loss of service
DANGER
Alerts you that failure to take or avoid a specific action might result in personal harm
INSPECTING YOUR SHIPMENT

Upon receipt of the equipment:
• Unpack each container and visually inspect the contents for signs of damage. If the equipment has been dam-
aged in transit, immediately report the extent of damage to the transportation company and to ADC. Order
replacement equipment, if necessary.
• Check the packing list to ensure complete and accurate shipment of each listed item. If the shipment is short
or irregular, contact ADC as described in Appendix C: Product Support on page C-1. If you must store the
equipment for a prolonged period, store the equipment in its original container.
LPS800-UM-MAIN-02 xi
About This Manual July 27, 2005
xii LPS800-UM-MAIN-02
Chapter 1
MAINTENANCE OVERVIEW
RUNNING ENVIRONMENT OF LOOPSTAR 800 SERIES
Communication equipment is precise electronic equipment, which can run reliably for a long time in a maintained
environment of appropriate temperatures, humidity, proper dust filtering and antistatic precautions are exercised.
The basic environment requirements for operating equipment are introduced as follows:
1. Test the Power Supply of -48 V DC for the LPS-8xx. Use a Voltmeter to Verify That It Ranges Between -40
V DC and -56.7 V DC.
The DC power distribution system should be able to provide power during abnormal power failures. Usually,
it should be equipped with an alternate battery source.
2. Ensure Equipment Is Grounded.
Good grounding is the basis of equipment running reliably. For detailed grounding requirements, please
refer to the Installation Manual.
3. Requirements for Temperature and Humidity (Table 1-1).
Table 1-1. Temperature and humidity requirements

Operating Ambient temperature Relative humidity
Long term operation o o
41 – 113 F (5 – 45 C) 10 – 90%
Short term operation o o
23 – 131 F (-5 – 55 C) 5 – 95%
Short-term working condition means that the successive working time does not exceed 72 hours and the
accumulated time every year does not exceed 15 days.
4. Ensure Good Ventilation of Equipment

During the normal running of the LPS-8xx, it is required to keep the fans running normally. Turning off the
fans may raise the equipment temperature or even damage units.
Ensure that there are no foreign objects blocking the ventilation openings of the equipment.
It is recommended to replace the air filter in every three months.
LPS800-UM-MAIN-02 1-1
Chapter 1: Maintenance Overview July 27, 2005
PRECAUTIONS OF MAINTENANCE OPERATIONS

To ensure the safety of the maintenance personnel and that of the equipment, some basic rules are recommended
to be followed in the course of equipment maintenance.
Laser Precautions
WARNING
The laser emitted by the optical interface is invisible infrared ray, which may cause permanent
damage to the human eyes. DO NOT LOOK DIRECTLY AT THE LASER EMITTING PORTS AND
THE OPTICAL FIBER CONNECTORS ON THE OC-N UNITS WITHOUT ANY PROTECTION.
1. Handling Optical Interface of OC-N Unit and Fiber Jumper Connector

Cover any unused optical interface fiber connectors on the OC-N units with dust covers. By doing so, invisi-
ble rays sent by laser will not reach human eyes, dust can be prevented, and the optical interface of the fiber
jumper connector will not get dirty.
2. Precautions for Loopback Operation of OC-N Unit
During hardware loop back testing of any OC-N unit with a fiber jumper, an attenuator must be used to
avoid the transmitted optical power from saturating or even damaging the optical receiving module.
3. Precautions for Replacing OC-N Units
Whenever replacing any OC-N unit, be sure to disconnect any optical fibers from the
unit first, prior to removing/inserting the unit. Never remove or insert a unit with the
optical fibers connected.
Precautions of Electrical Safety

1. Antistatic Precautions
In the cases of body movements, clothes friction, the friction between the shoes and ground, and plastics
held in the hand, the human body might generate static and retain it for a long time.
Always wear an antistatic wrist strap when touching the equipment or holding the units.
CAUTION The static produced by the human body can damage the sensitive components on the unit, such
as large integrated circuits.
2. Precautions for Unit Electrical Safety

Any unit should be kept in the antistatic bag when it is not used. Wear an antistatic wristband and make
sure the wristband is well grounded before holding any unit.
Please pay attention to the impact of environmental temperatures and humidity on the storage of the
backup units. Desiccant should be placed inside antistatic protection bags to absorb any moisture and
keep the bag dry.
When the unit encapsulated in an antistatic enclosure is taken from a cool, dry place to a hot, humid place,
wait for at least 30 minutes before opening it. Otherwise, the moisture will condense on the surface of the
unit and may damage the elements.
3. Precautions for Power Supply Maintenance
Never connect or disconnect the power line with the power on.
Never install or remove the equipment power cable with the power on.
When a power cable touches a conductor, electric sparks or arcs will be produced, which can cause fire or
injury to personnel.
Before power cables are connected, you must make sure that cable and cable label are in compliance with
the practical installation.
1-2 LPS800-UM-MAIN-02
July 27, 2005 Chapter 1: Maintenance Overview
Precautions of Mechanical Safety

Avoid shocks during the transportation of units, which may cause damage. Pay close attention when seating or
unseating any unit into the chassis. Follow the steps outlined in the LoopStar 800 Series Installation Manual,
catalog number LPS800-UM-INST.
Precautions of NM System Maintenance

Do not shut down the network management (NM) system when its software is working normally. Although shutting
down the network management system will not interrupt the service on the network, it will disable the network
management's ability to monitor the equipment during the shutdown period and jeopardize the continuity of
equipment monitoring.
Do not run any software irrelevant to equipment maintenance.
Precautions of Service Configuration

Do not configure services until you are well prepared. Do not groom services during peak hour. Please do it while
traffic is at minimum.
Chapter 1: Maintenance Overview July 27, 2005
Chapter 2
BASIC OPERATIONS
FAN MAINTENANCE
The main task of cleaning the fan is to replace the air filter. To ensure normal ventilation of theLPS-8xx and prevent
it from exceeding normal operating temperatures, check the fans periodically for normal operation. If the air filter
becomes blocked, this will result in poor ventilation. Once the air filter is blocked, replace it immediately.
LPS-800
The air filter of the LPS-800 is connected to the front panel of the fan tray. Pull out the air filter together with the front
panel. Replace the old air filter with a new one, and dispose the old one. It is recommended to replace the air filter in
every three months.
LPS-810
The air filter of the LPS-810 is installed as shown in Figure 2-1. Replace the old air filter with a new one, and dispose
the old one. It is recommended to replace the air filter in every three months.
Figure 2-1. Install the Fan Tray and Air Filter (LPS-810)
Chapter 2: Basic Operations July 27, 2005
PLUG/UNPLUG FIBER JUMPERS

Optical units for the LPS-8xx are standard with one type of interface: LC (Figure 2-2).
Figure 2-2. Fiber jumper with LC optical interface
When connecting a fiber jumper into an LC interface, carefully align the head of the fiber jumper to the optical
interface, and push it in with proper force until you hear a click. The jumper is now secure. To remove a fiber jumper
from the LC interface, depress the clip slightly and then pull out the plug.
PLUG/UNPLUG UNITS
The chassis backplane of the LPS-8xx is for electrical connections between units and electrical interfaces. Each slot
position on the chassis backplane has pins for making connections between units and interfaces. Those are the
connecting plugs of units. Be very careful when inserting or removing units so as not to bend pins or even cause the
system to be short-circuited.
CAUTION The static the human body generates may damage the static sensitive components on the unit.
Always wear an ESD wrist strap when touching a unit.
1. Correct Way of Inserting a Unit

Refer to “Unit Installation” in the LoopStar 800 Series Installation Manual, catalog number LPS800-UM-
INST.
2. Correct Way of Removing a Unit
When removing a unit, first loosen the left and right retaining screws of the front panel on the unit, and then
pull the ejectors at both sides of front panel outward simultaneously till the unit is pulled out completely.
Forcibly inserting a unit in an improper position will do permanent damage to the equipment. Pull out the
fiber (cable) on the front panel of the unit, and then insert/remove the unit. Never insert/remove the unit with
fiber (cable) connected.
July 27, 2005 Chapter 2: Basic Operations
AUDIBLE ALARM CUT-OFF

The LPS-8xx provides an audible alarm notification. If an alarm occurs, the LPS-8xx will illuminate the alarm
indicator and report the alarm to the network management system (NMS). At the same time, the LPS-8xx will send
driving signal to the centralized monitoring system in the equipment room. The centralized monitoring system will
generate an audible alarm notification, reminding the user of the alarm.
To cut off the audible alarm notification, depress the Alarm Cut-Off “ACO” button on the faceplate of the System
Status Panel. If there are any new alarms reported, the LPS-8xx will drive the central monitoring system and another
audible alarm will be generated.
RESETS
The LPS-8xx provides two reset modes for all units: cold reset and hot reset.
1. Cold Reset
Cold reset is to power off, insert or remove the units.
2. Hot Reset
A hot reset resets the CPU inside a unit without affecting other modules. For example, an OC12 is per-
forming a hot reset, the service being processed by other units will not be interrupted.
A hot reset can be executed by the NMS sending a command. However the XO12 and XO3 units can be
reset by depressing the “RESET” button on the faceplate.
The unit reset is a potential service affecting operation and should be avoided unless special conditions
exist. If it is indeed necessary to reset a unit, ask ADC engineer for acknowledgement before proceeding.
CLEANING FIBER CONNECTORS

The optical fiber connectors and the optical fiber interface of the laser on the optical interface units must be cleaned
with special cleaning tools and materials. These tools and materials are available from optical fiber cable and
connector manufacturers.
To clean the optical interface of an optical interface unit, pull out the optical fiber connected to the unit first, and then
pull out the unit. These operations are suggested to be completed under the guidance of the maintenance engineers
of ADC Telecommunications, Inc., to avoid improper operation and not to damage the optical interface unit.
WARNING
The laser emitted by the optical interface is invisible infrared ray, which may cause permanent
damage to the human eyes. DO NOT LOOK DIRECTLY AT THE LASER EMITTING PORTS AND
THE OPTICAL FIBER CONNECTORS ON THE OC-N UNITS WITHOUT ANY PROTECTION.
CAUTION Do not use any cleaning tools or materials that are not suitable for cleaning optical fiber
connectors and the laser on the optical interface unit!
Using unqualified tools or materials will destroy the optical fiber connectors and the interfaces.
BIT ERROR RATE TESTING

When performing bit error rate tests, the testing point is the service access point, for example, the interface of
DS1/DS3/OC-3. You may select two testing methods: online or offline.
1. Online Testing Method

Select a service channel (for example: DS1, DS3, OC-3 and otherwise) in use, and find the port correspond-
ing to it on digital distribution frame (DDF). Connect one end of the testing wire to the “online testing connec-
tor” of that port in DDF, and the other end to the online testing interface of the tester, and then test.
Normally, there is no bit error within 24 hours.
For instructions on how to set the instrument, please refer to its manual. Note that the instrument must be
set to “online testing”.
2. Offline Testing Method
This is a more frequently used testing method. Select one service channel (for example: DS1, DS3, OC-3
and otherwise), connect the transmitting and receiving port of the bit error tester, to the transmitting and
receiving port of the interface to be tested in local Network Element (NE). Pay attention to the correspond-
ing relation of transmitting and receiving ports between the tester and the LPS-8xx. Then at the terminal
NE of the service, make a loopback of interfaces (for example, hardware self-loop at DDF, or make a soft-
ware loopback by NE). Set the bit error tester and then start testing. For the operations of bit error tester,
please refer to its instructions. There should be no bit error within 24 hours under normal conditions.
Figure 2-3 shows the block diagram of bit error testing connection.
Figure 2-3. Bit error test
The test meter should be grounded properly. It is suggested that other electric appliances not be switched
on/off during the testing.
July 27, 2005 Chapter 2: Basic Operations
TRANSMITTER/RECEIVER OPTICAL POWER TESTING

1. Test Transmitter Optical Power
The testing operation is as follows:
Set the receiving optical wavelength of the optical power meter to the same as the tested optical wave-
length.
Connect one end of the fiber jumper to the OUT interface of the optical interface unit to be tested. Connect
the other end of the fiber jumper to the test input interface of the optical power meter, wait until the receiving
optical power is stable, read the optical power value, that is, the transmitting optical power of the optical
interface unit.
• To do this test, you have to keep the fiber connector clean and well connected, also keep the ring
flange of the front panel on the optical unit connected and clean.
• Test the attenuation of the tail fiber in advance.
• Different tail fibers should be used for single-mode and multi-mode optical interfaces.
• The optical power meter should work under the mode of Root Mean Square.
2. Test Receiver Optical Power

The testing operation is as follows:
Set the receiving optical wavelength of the optical power meter to the same as the tested optical wave-
length.
In the local NE, connect the fiber jumper at the input (IN) port of the optical interface to be tested to the
testing input port of the optical power meter. After the receiving optical power is stable, read the optical
power, which is the actual receiving optical power of the optical interface unit.
The precautions are the same as those of “Test Transmitter Optical Power” in this section.
Chapter 3
ROUTINE MAINTENANCE
OVERVIEW
Purpose
The purpose of routine maintenance is to find potential problems and take appropriate measures to correct them
before they become actual problems.
This chapter introduces the contents and procedures of the routine maintenance of the LPS-8xx, offering basic
methods and references that may help the user in making routine maintenance schemes.
Classification
According to the maintenance periods, maintenance can be divided into the following types:
1. Emergency Maintenance
Emergency maintenance refers to the maintenance task executed due to equipment failure and network
adjustments, including the user-claimed failure, equipment damage and line failure, and so on.
2. Daily Routine Maintenance
Daily routine maintenance refers to the maintenance which must be performed every day. Through it, the
maintenance personnel can learn the running status of the equipment at any time and take measures to
correct faults if there are any. During routine maintenance, detailed records should be made on the specific
physical position of the fault, as well as phenomenon and process of the fault, so as to perform timely
maintenance and troubleshooting.
3. Periodical Routine Maintenance
Periodical routine maintenance refers to the maintenance performed periodically. Through it, the mainte-
nance personnel can learn the long-term running status of the equipment.
Periodical routine maintenance falls into quarterly maintenance and yearly maintenance.
Chapter 3: Routine Maintenance July 27, 2005
ROUTINE MAINTENANCE ITEMS

Table 3-1 shows the typical routine maintenance items.
Table 3-1. Typical routine maintenance item

Maintenance test item Period
Audio alarm system Daily
Equipment alarm indicator Daily
Temperature Daily
NE and unit status Daily
Alarms Daily
Performance event monitoring Daily
Protection switching Daily
Querying NE time Daily
Checking and replacing air filter periodically 2 weeks
Bit error test Monthly
Modifying the login password of NM system users Monthly
Backup and dump of NM system database Monthly
Audible Alarm Notification

An audible alarm can more easily catch the attention of the maintenance personnel than other kinds of equipment
alarms, so the alarm channel must be kept unblocked during routine maintenance.
As the audible alarm of the LPS-8xx is externally connected to the centralized alarm control system of the
equipment room, it is necessary to check the switch and wiring of the system periodically.
It is recommended to check the audible alarm once a day.
Equipment Alarm Indicators

The LED alarm indicator can tell the maintenance personnel about the equipment running status and part of the
equipment alarm information. The flashing status of the alarm indicator should be given enough concern to find out
the working status of the equipment during routine maintenance. LEDs located on the system status panel will warn
of any alarms present on the system.
July 27, 2005 Chapter 3: Routine Maintenance
The alarm indicators on the system status panel for the LPS-800 are shown in Figure 3-1.
Figure 3-1. LPS-800 System status panel
The alarm indicators on the system status panel for the LPS-810 are shown in Figure 3-2.
Figure 3-2. LPS-810 System status panel
The specific meaning of all the indicators is shown in Table 3-2.
Table 3-2. Indicators and their meanings

Color or Flashing
Indicators Status Description
CRIT Red on Critical alarm
Off No critical alarm
MAJ Red on Major alarm
Off No major alarm
MIN Yellow on Minor alarm
Off No minor alarm
FAN Red on Fan failure
Off Fan is normal
Green on Power A is normal
Red on Power A failure. For example:
over-voltage, under-voltage, or
PWRA
hardware failure
Off Power supply has been cut off
Green on Power B is normal
Red on Power B failure. For example:
over-voltage, under-voltage, or
PWRB
hardware failure
Off Power supply has been cut off
Green on Current audio/light alarm has
been closed. If the alarm does
not disappear, the alarm
indicator will still light green,
ACO until the next new audio/light
alarm occurs.
Off Current audio/light alarm has
not been closed (that is, alarm
indicator is lighting), or there is
not any alarm occurs, or no
power supply.
It is recommended to observe the equipment alarm indicators once a day.
Temperature
Table 3-3 shows the ambient temperature requirements for proper equipment operation.
Table 3-3. Ambient temperature requirements for equipment operation

Operating Ambient temperature
Long term operation 41 – 113oF (5 – 45oC)
Short term operation 23 – 131oF (-5 – 55oC)
Short-term working condition means that the successive working time does not exceed 72 hours and the
accumulated working time every year does not exceed 15 days.
Observe the temperature of the equipment room everyday, and touch the front panel of the unit to see whether the
temperature of the unit is too high.
It is recommended to check the temperature of the equipment room once a day.
NE and Unit Status

All Network Elements (NEs) in the management domain should be logged in normally through the transmission
network management (NM) system.
Query the working status of all NEs in the network, as well as that of the respective units in the NEs.
It is recommended to check the NE and unit status once a day.
Alarms
The LPS-8xx provides comprehensive alarm management. As part of routine maintenance, network management
personnel should check the alarm information of all NEs daily to prevent latent problems in time.
For detailed operation of alarm management, refer to “Chapter 7 Alarm Monitoring” in the LoopStar 800 Series
System Administration Manual, catalog number LPS800-UM-ADMN.
It is recommended to browse the alarms once a day.
Performance Events
The LPS-8xx provides comprehensive performance management as well as multiple means for on-line monitoring of
network services.
Performance management includes collection of bit error pointer justification performance and defects as well as
various monitoring item data; deriving statistics for performance data in 24 hour cycles and automatically recording
statistics data for 15 minute intervals; setting of the performance threshold and notification of threshold-crossing
events; performance data analysis, and so on.
1. Performance Monitoring Configuration

Performance monitoring configuration allows provisioning of monitoring time, monitored objects and thresh-
old settings.
•Monitoring time configuration
In TL1, you can set the start time (the fixed time is 24 hours). In the EMS, you can set the time to either 15
minutes or 24 hours.
•Monitoring object selection
In TL1, all performance events are monitored by the system by default, while in the EMS, you can select the
objects to be monitored.
•Threshold provisioning
Both TL1 and the EMS support setting threshold values and enabling/disabling threshold crossing alarms.
For routine maintenance the performance monitoring settings should support monitoring the system
operation status in a long-term and comprehensive manner. It is recommended that threshold crossing
alarms be enabled and threshold values set to defaults.
2. Performance Data Viewing

It is indispensable to view such NE performance data as bit error, pointer justification, and so on. In routine
maintenance, through which a variety of latent failures of the equipment operation can be detected.
•View performance data

Bit error-related performance and pointer justification events are of extreme importance and deserve careful
consideration. When the system is in normal condition, there should be no or very few performance events
(some performance values such as that of the temperature cannot be 0). Large amounts of performance
data indicate that the transmission signal quality in the system is degraded or the network clock is not
synchronized, all of which are latent faults of the system. Never treat such cases lightly. Although the
service is still in normal operation these problems should be removed to prevent more serious problems
such as service interruption in the future.
•Viewing performance threshold-crossing data

One important function of performance management is threshold crossing alarms. After a project, engineers
will uniformly set the performance data threshold. When the performance data exceeds the threshold, the
NM system will display an alarm, indicating performance has deteriorated. The recorded performance data
can be retrieved for more detail on the causes.
For detailed operation of the performance event management, refer torefer to “Chapter 6 Performance
Monitoring” in the LoopStar 800 Series System Administration Manual, catalog number LPS800-UM-
ADMN.
It is recommended to browse the performance events once a day.
Protection Switching
In view of the importance of protection switching, the checking of protection switching alarm will be listed
independently. In routine maintenance, the protection switching alarms APS_INDI and TPS_INDI must be checked
periodically through the NM system.
Suppose protection switching occurs in the system for some reason, and service is kept in normal operation as the
protection functions normally. However, the equipment or the external optical fiber may have failed which could
cause problems in the long-term. In addition, protection switching of equipment is designed to provide short-term
protection for service which will be left in an unsafe situation if a protection switch exists for a long time. Any
subsequent faults to equipment or optical fiber can easily cause service interruption. Hence, regular checking of the
protection switching alarm is indispensable.
It is recommended to check relevant protection switching alarms through the NM system once a day.
Querying NE Time
The NE time should be kept consistent with the current computer time and the actual time. Otherwise the NM
system will display incorrect alarm generation and termination times which could result in misleading alarm
information.
Checking and Replacing Air Filter Periodically

Good heat dissipation is the key to ensure the long-term and efficient operation of the equipment. In case the
environment of the equipment room cannot satisfy the requirement for cleanliness, the air filter under the fan will be
easily blocked, resulting in poor ventilation and even damage to the equipment. Thus operation and ventilation of the
fan should be checked regularly. When the fans are in normal operation, the FAN indicator on the system status
panel will light green. The fans should always be kept in normal operation.
It is recommended to replace the air filter of the fan at least twice a month.
Bit Error Rate Test

Bit error rate (BER) test is the test on the system working performance conducted for ensuring long-term and
efficient system operation. As part of routine maintenance, perform periodic sample tests to the service channel with
the normal service operation guaranteed. Through the test, it can be judged whether the performance of all service
channels is normal.
Depending on the situation, users can select one of the following approaches to perform the test.
Approach 1: if there is a configured but unused service channel between two Network Elements (NEs), unused
service channel can be tested to check the quality of the service channel between the two stations.
Approach 2: if there is no configured but unused service channel between two NEs, we can temporarily disconnect
the service protection channel to perform bit error test when the traffic is comparatively light, and judge the quality of
the service channel between the two stations based on the test result.
Approach 3: if both the above two approaches are not available, we can monitor the quality of the service channel
through the performance and alarms reported by the NM system.
For the service channel selected for BER test, generally, set terminal loopback at the corresponding service channel
on the electrical interface unit at the remote NE, and perform BER testing at the corresponding service channel at
the local NE. Generally, the test time is 24 hours and the bit error rate in the test result should be zero.
It is recommended to perform BER once a month as part of routine maintenance.
After the test is completed, remember to clear the terminal loopback at the electrical interface unit.
The BER tester must be well grounded during the test. To avoid interference, make every effort not to turn
on/off other electric appliances during the test.
When performing loopback to the service channel of the electrical interface unit, first consider to perform
hardware loopback on the digital distribution frame (DDF) outside the equipment. If the test result is
abnormal (for example, a great deal of bit errors are detected), do the loopback at the wiring area of the
chassis.
If the fault remains after the hardware loopback, perform loopback to the service channel of the electrical
interface unit. Remember to clear the loopback setting at the electrical interface unit after the test.
Modifying Login Password of NM System
User
To improve system security, the login password of the NM system user should be modified periodically. It is
recommended to make the modification once a month.
Chapter 4
LOOPBACK AND NETWORK TEST
LOOPBACKS
Loopbacks are one of the most popular test methods used to isolate faults in the network. The LPS-8xx provides
perfect loopback modes, including facility loopbacks, terminal loopbacks and path loopbacks (sometimes they are
also called software loopbacks).
Besides software loopbacks, you can also loop back the optical or electrical signals outside the LPS-8xx by
connecting the receiving end and transmitting end of the optical interface (OC-N) or electrical interface
(DSn) directly through the optical fiber or electrical cable. Use precautions to attenuate optical signals to a
proper level to avoid potential unit damage.
Facility Loopback
Both OC-N interface units and DSn processing units support facility loopbacks.
OC-N Inside the optical interface unit (OC3 or OC12,

interface etc...), loop back the signals from the optical
unit receiving module to the optical transmitting
module.
There are two loopback modes for the signals:
loopback in path (e.g., STS-1 or STS-3c) and
loopback in port (loop back all paths that access
signals.
DSn Inside the DSn processing unit (PLT3, PLT1 -
processing LPS-8xx), (PQT3, PDM3 - LPS-800 only), etc...,
unit send the signal from the receiving port back to
the corresponding transmitting port of the signal.
After creating facility loopbacks for the unit, determine whether the data processing module of the unit works
properly and whether the connection between the unit and the external electrical cables is normal from the test
result displayed by the bit error rate (BER) tester.
Chapter 4: Loopback and Network Test July 27, 2005
Terminal Loopback
Both the OC-N interface units and DSn processing units support terminal loopback.
OC-N Inside the optical interface unit (OC3 or OC12,

interface etc...), send the signal from the cross-connect
unit unit back to the cross-connect unit.
There are two loopback modes for the signals:
individual path loopback (e.g., STS-1 or
STS-3c), and all paths loopback.
DSn Inside the DSn processing unit (PLT3, PLT1 -

processing LPS-8xx), (PQT3, PDM3 - LPS-800 only), etc...,
unit send the signal from the cross-connect unit back
to the cross-connect unit. The signal here is of
DSn level.
Generally, the terminal loopback will pass the cross-connect unit to the tested unit. Then, the signal will be looped
back from the unit being tested before it gets to the data processing module.
A terminal loopback can test the cross-connect unit and the service trail other than the data processing module of
the unit. After creating terminal loopback for the unit, determine whether cross-connect unit and the service trail are
normal from the test result displayed by the BER tester.
Path Loopback
Path loopback can only be conducted inside the XO unit.
XO unit Inside the cross-connect unit, send the service

of the cross-connect unit from the DSn
processing unit or OC-N interface unit to loop
back according to the service level.
As the LPS-8xx only provides a higher order cross-connect unit at present, STS-1 is the lowest service level
currently available for loopback.
July 27, 2005 Chapter 4: Loopback and Network Test
IDENTIFING NETWORK FAULTS

Facility loopback, terminal loopback and path loopback are usually used together in network fault localization. When
network fault and service interruption occur, performing these three kinds of loopback at the respective NEs along
the service trail can help in finding the fault location.
The case contained in this section is to test a DS3 service trail in a unidirectional path switched ring (UPSR)
network. Only three nodes (NE-A, NE-B and NE-C) in the network are covered by this service trail. With the
loopback modes provided by the LPS-8xx, the signal can be traced along the service trail and the fault located. The
test steps can be as follows:
NE-A Create facility loopback for DSn processing unit.

Create path loopback for the cross-connect unit.
Create terminal loopback for the eastbound
OC-N interface unit.
NE-B Create facility loopback for the westbound OC-N interface unit.
Create terminal loopback for the eastbound OC-N interface unit.
NE-C Create facility loopback for the westbound OC-N interface unit.
Create path loopback for cross-connect unit.
Create terminal loopback for the DSn processing unit.
Create facility loopback for the DSn processing unit.
The step sequence of the test will depend on the specific network topology structure and service routes.
Besides using the path loopback described above, electrical cable or optical fiber can be used to loopback
DSn or OC-N directly outside the LPS-8xx.
Perform a Facility Loopback on NE-A’s DSn Processing Unit

Create a facility loopback for the DSn processing unit of NE-A (Figure 4-1). If the test result is normal, it is proved
that there is no problem with the DSn processing unit, DSn interface unit and cabling of NE-A.
Figure 4-1. Perform a facility loopback on NE-A’s DSn processing unit
1. Create a Facility Loopback on NE-A’s DSn Processing Unit
Step Action
1 Connect an electrical BER tester to the port to be tested.
Use appropriate electrical cable to attach the transmit (Tx) and receive (Rx) terminals of the electrical
BER tester to the DSn interface unit for the port you are testing. The transmit (Tx) and receive (Rx)
terminals connect to the same port. Adjust the test set accordingly.
2 Use TL1 or EMS to create the facility loopback on the port being tested.
3 Proceed to 2. Test the Facility Loopback.
2. Test the Facility Loopback
Step Action
1 Run the electrical BER tester, and send the test service to the loopback circuit.
2 Observe the service received by the electrical BER tester and check for errors or other information.
3 If the test result is normal:
a. Clear the loopback.
b. Proceed to Perform a Path Loopback on the NE-A on page 4-5.
4 If bit errors occur, the problem may be with the DSn processing unit, DSn interface unit, or the cable (from
the DSn interface unit to the electrical BER tester, or from the DSn interface unit to DDF).
5 Proceed to 3. Check the DSn Cable.
3. Check the DSn Cable
Step Action
1 Replace the cable (from the DSn interface unit to the electrical BER tester or from the DSn interface unit
to DDF).
2 Resend the test service to the loopback circuit.
3 If the test result is normal, it can be determined that the fault is at the cable.
a. Replace the faulty cable and redo the cabling.
b. Clear the loopback.
c. Proceed to Perform a Path Loopback on the NE-A on page 4-5.
4 It the bit errors remain, the problem may be with the DSn processing unit or the DSn interface unit.
Proceed to 4. Test the DSn Processing Unit on page 4-5.
4. Test the DSn Processing Unit
Step Action
1 Replace the DSn processing unit. See Replace Hardware on page 5-1 for details.
3 If the test result is normal, it indicates the problem is with the replaced DSn processing unit.
a. Replace the faulty unit.
c. Refer to Product Support on page C-1 for unit replacement and technical support.
d. Proceed to Perform a Path Loopback on the NE-A.

4 If errors occur, the problem may be with the DSn interface unit.
5 Proceed to 5. Test the DSn Interface Unit.
5. Test the DSn Interface Unit
Step Action
1 Replace the DSn interface unit. See Replace Hardware on page 5-1 for details.
3 If the test result is normal, it indicates the problem is with the replaced DSn interface unit.
a. Contact ADC technical support center for unit replacement and technical support.
b. Replace the faulty unit.
c. Clear the loopback.
d. Proceed to Perform a Path Loopback on the NE-A”.
4 If bit errors occur, refer to Product Support on page C-1 or repeat the above steps.
Perform a Path Loopback on the NE-A

Create a path loopback for the cross-connect unit of NE-A (Figure 4-2). If the test result is normal, it indicates the
cross-connect unit and service trail of the cross-connect unit of NE-A work properly.
Figure 4-2. Perform a path loopback on the NE-A
1. Create a Path Loopback on the NE-A
Step Action
If you just finished the step of Perform a Facility Loopback on NE-A’s DSn Processing Unit on page 4-3,
keep the connection of the electrical BER tester and the DSn processing unit unchanged.
If you start with this step, use appropriate electrical cable to attach the transmit (Tx) and receive (Rx)
terminals of the electrical BER tester to the DSn interface unit for the port you are testing. The transmit
(Tx) and receive (Rx) terminals connect to the same port. Adjust the test set accordingly.
2 Use TL1 or EMS to create the path loopback on the port being tested.
3 Proceed to 2. Test the Path Loopback.
2. Test the Path Loopback
Step Action
b. Proceed to Perform a Terminal Loopback on NE-A’s OC-N Interface Unit on page 4-7.
4 If bit errors occur, the problem may be with the cross-connect unit.
5 Proceed to 3. Test the Standby Cross-Connect Unit.
3. Test the Standby Cross-Connect Unit
Step Action
1 Hot reset the standby cross-connect unit.
2 Manually switch the service from the active cross-connect unit to the standby cross-connect unit through
TL1 or EMS.
a. The fault is at the original cross-connect unit.
c. Proceed to 4. Retest the Original Cross-Connect Unit on page 4-7.

6 If bit errors occur, the problem may be caused by other faults. Refer to Product Support on page C-1.
4. Retest the Original Cross-Connect Unit
Step Action
1 Manually switch the service from the currently active cross-connect unit to the currently standby cross-
connect unit through TL1 or EMS to make the original cross-connect unit the active unit.
3 If the test result is abnormal, it indicates the fault is with the original cross-connect unit.
d. Proceed to Perform a Terminal Loopback on NE-A’s OC-N Interface Unit.

4 If the test result is normal, a temporary problem may have occurred on the original cross-connect unit,
which can be solved by manual switching.
b. Proceed to Perform a Terminal Loopback on NE-A’s OC-N Interface Unit.
Perform a Terminal Loopback on NE-A’s OC-N Interface Unit

Create a terminal loopback for the OC-N interface unit of NE-A (Figure 4-3). With this loopback test, it can be
determined whether a complete service trail in NE-A is available.
Figure 4-3. Perform a terminal loopback on NE-A’s OC-N interface unit
1. Create a Terminal Loopback on NE-A’s OC-N Interface Unit
Step Action
1 Connect an electrical BER tester to the port to be tested.If you just finished the step of Perform a Path
Loopback on the NE-A, keep the connection of the electrical BER tester and the DSn processing unit
unchanged.
terminals of the electrical BER tester to the DSn interface unit for the port you are testing. The transmit (Tx)
and receive (Rx) terminals connect to the same port. Adjust the test set accordingly.
2 Use TL1 or EMS to create the terminal loopback on the port being tested.
3 Proceed to 2. Test the Terminal Loopback on page 4-8.
2. Test the Terminal Loopback
Step Action
b. Proceed to Perform a Facility Loopback on NE-B’s Westward OC-N Interface Unit.

4 If bit errors occur, the problem may be with the OC-N interface unit.
5 Proceed to 3. Test the OC-N Interface Unit.
3. Test the OC-N Interface Unit
Step Action
1 Replace the OC-N interface unit. See Replace Hardware on page 5-1 for details.
3 If the test result is normal, it indicates the problem is with the replaced OC-N interface unit.
d. Proceed to Perform a Facility Loopback on NE-B’s Westward OC-N Interface Unit.

4 If the bit errors remain, refer to Product Support on page C-1.
Perform a Facility Loopback on NE-B’s Westward OC-N Interface Unit

Create a facility loopback on the westward optical unit of NE-B (Figure 4-4). This test can help you to find out
whether this unit is available and whether the optical fiber connection between NE-A and NE-B is unblocked.
Figure 4-4. Perform a facility loopback on NE-B’s westward OC-N interface unit
1. Create a Facility Loopback on NE-B’s Westward OC-N Interface Unit
Step Action
If you just finished the step of Perform a Terminal Loopback on NE-A’s OC-N Interface Unit on page 4-7,
keep the connection of the electrical BER tester and the DSn processing unit unchanged.
Step Action
b. Proceed to Perform a Terminal Loopback on NE-B’s Eastward OC-N Interface Unit on page 4-10.
4 If bit errors are found, the problem may be with the OC-N interface unit or the optical fiber connection
between NE-A and NE-B.
5 Proceed to 3. Check the Connection of Optical Fiber.
3. Check the Connection of Optical Fiber
Step Action
1 Change the optical fiber connection with a standby optical connection.
a. Change to another optical connection.
c. Proceed to Perform a Terminal Loopback on NE-B’s Eastward OC-N Interface Unit on page 4-10.
4 If the bit errors remain, the problem may be with the OC-N interface unit.
5 Proceed to 4. Test the OC-N Interface Unit on page 4-10.
Step Action
d. Proceed to Perform a Terminal Loopback on NE-B’s Eastward OC-N Interface Unit.

Perform a Terminal Loopback on NE-B’s Eastward OC-N Interface Unit

Create terminal loopback for the OC-N interface unit of NE-B (Figure 4-5). This test will help you to find out whether
the service trail can pass NE-B properly.
Figure 4-5. Perform a terminal loopback on NE-B’s eastward OC-N interface unit
1. Create a Terminal Loopback on NE-B’s Westward OC-N Interface Unit
Step Action
If you just finished the step of Perform a Facility Loopback on NE-B’s Westward OC-N Interface Unit on
page 4-8, keep the connection of the electrical BER tester and the DSn processing unit unchanged.
3 Proceed to 2. Test the Terminal Loopback on page 4-11.
Step Action
b. Proceed to Perform a Facility Loopback on NE-C’s Westward OC-N Interface Unit.

4 If bit errors are found, the problem may be with the OC-N interface unit or a faulty cross-connect unit.
5 Proceed to 3. Test the OC-N Interface Unit.
Step Action
c. Refer to Product Support on page C-1 for unit replacement and technical support;
d. Proceed to Perform a Facility Loopback on NE-C’s Westward OC-N Interface Unit.

4 If the bit errors remain, the problem may be with the cross-connect unit of NE-B. Test the unit according to
Perform a Path Loopback on the NE-A on page 4-5.
Perform a Facility Loopback on NE-C’s Westward OC-N Interface Unit

Create a facility loopback to the westward optical unit of NE-C (Figure 4-6). This test can find out whether this unit is
available and whether the optical fiber connection between NE-C and NE-B is blocked.
Figure 4-6. Perform a facility loopback on NE-C’s westward OC-N interface unit
1. Create a Facility Loopback on NE-C’s Westward OC-N Interface Unit
Step Action
If you just finished the step of Perform a Terminal Loopback on NE-B’s Eastward OC-N Interface Unit on
page 4-10, keep the connection of the electrical BER tester and DSn processing unit unchanged.
Step Action
b. Proceed to Perform a Path Loopback on the NE-C on page 4-13.

4 If bit errors occur, the problem may be with the OC-N interface unit or the optical connection between NE-
C and NE-B.
5 Proceed to 3. Check the Connection of Optical Fiber.
3. Check the Connection of Optical Fiber
Step Action
1 Change the optical connection with a standby optical connection.
a. Change to another optical connection.
c. Proceed to Perform a Path Loopback on the NE-C on page 4-13.

4 If the bit error remains, the problem may be with the OC-N interface unit.
5 Proceed to 4. Test the OC-N Interface Unit on page 4-13.
Step Action
d. Proceed to Perform a Path Loopback on the NE-C.

4 It the bit errors remain, refer to Product Support on page C-1.
Perform a Path Loopback on the NE-C

Create path loopback for cross-connect unit of NE-C (Figure 4-7). This test can help you to find out whether the
cross-connect matrix of NE-C is available.
Figure 4-7. Perform a path loopback on the NE-C
1. Create a Path Loopback on the NE-C
Step Action
If you just finished the step of Perform a Facility Loopback on NE-C’s Westward OC-N Interface Unit on
page 4-11, keep the connection of the electrical BER tester and the DSn processing unit unchanged.
2 Use TL1 or EMS to create the path loopback on the port being tested.
3 Proceed to the 2. Test the Path Loopback on page 4-14.
4 If bit errors are found, the problem may be with the cross-connect unit.
5 Proceed to 3. Test the Standby Cross-Connect Unit on page 4-14.
2. Test the Path Loopback
Step Action
b. Proceed to Perform a Terminal Loopback on NE-C’s DSn Processing Unit on page 4-15.
4 If bit errors are found, the problem may be with the cross-connect unit.
5 Proceed to 3. Test the Standby Cross-Connect Unit.
3. Test the Standby Cross-Connect Unit
Step Action
1 Hot reset the cross-connect unit.
2 Switch the service from the active cross-connect unit to the standby cross-connect unit manually through
TL1 or EMS.
a. The fault is caused by the original cross-connect unit.
c. Proceed to 4. Retest the Original Cross-Connect Unit on page 4-15.

6 If bit errors are found, the problem may be caused by other faults. Refer to Product Support on page C-1.
4. Retest the Original Cross-Connect Unit
Step Action
1 Manually switch the service from the current active cross-connect unit to the current standby cross-
connect unit through TL1 or EMS to make the original cross-connect unit the active unit.
3 If the test result is abnormal, it indicates the fault is with the original cross-connect unit.
d. Proceed to Perform a Terminal Loopback on NE-C’s DSn Processing Unit.

4 If the test result is normal, a temporary problem may have occurred on the original cross-connect unit,
which can be solved by manual switching.
b. Proceed to Perform a Terminal Loopback on NE-C’s DSn Processing Unit.
Perform a Terminal Loopback on NE-C’s DSn Processing Unit

Create a terminal loopback for the DSn processing unit of NE-C (Figure 4-8). This test can help you to determine
whether the complete service trail is available.
Figure 4-8. Perform a terminal loopback on NE-C’s DSn processing unit
1. Create a Terminal Loopback on NE-C’s DSn Processing Unit
Step Action
If you just finished the step of Perform a Path Loopback on the NE-C on page 4-13, keep the connection of
the electrical BER tester and the DSn processing unit unchanged.
3 Proceed to 2. Test the Terminal Loopback.
Step Action
b. Proceed to Perform a Facility Loopback on NE-C’s DSn Processing Unit on page 4-17.
4 If bit errors are found, the problem may be with the DSn processing unit.
5 Proceed to 3. Test the DSn Processing Unit.
3. Test the DSn Processing Unit.
Step Action
d. Proceed to Perform a Facility Loopback on NE-C’s DSn Processing Unit on page 4-17.
Perform a Facility Loopback on NE-C’s DSn Processing Unit

Create facility loopback for the DSn interface unit of NE-C (Figure 4-9). This test can help determine whether the
DSn processing unit and DSn interface unit of NE-C are available.
This test can be performed at NE-C only.
Figure 4-9. Perform a facility loopback on NE-C’s DSn processing unit
1. Create a Facility Loopback on NE-C’s DSn Processing Unit
Step Action
Use appropriate cabling to attach the transmit (Tx) and receive (Rx) terminals of the electrical BER tester
to the DSn interface unit for the port you are testing. The transmit (Tx) and receive (Rx) terminals connect
to the same port. Adjust the test set accordingly.
Step Action
b. Proceed to the Perform a Path Loopback on the NE-A on page 4-5.

4 If bit errors occur, the problem may be with the DSn processing unit, the DSn interface unit, or the cable
from the DSn interface unit to the electrical BER tester.
5 Proceed to the 3. Check the DSn Cable on page 4-18.
3. Check the DSn Cable
Step Action
1 Replace the cable (from the DSn interface unit to the electrical BER tester).
2 Resend test service to the loopback circuit.
a. Replace the cable.
c. So far, a complete DSn service trail has passed a series loopback tests and can be loaded with actual
services.
4 If bit errors occur, the problem may be with the DSn processing unit, the DSn interface unit, or the cable
from the DSn interface unit to the electrical BER tester.
5 Proceed to the 4. Test the DSn Processing Unit.
4. Test the DSn Processing Unit
Step Action
2 Resend test service to the loopback circuit.
d. So far, a complete DSn service trail has passed a series loopback tests and can be loaded with actual
services.
4 If bit errors occur, the problem may be with the DSn interface unit.
5 Proceed to 5. Test the DSn Interface Unit on page 4-19.
5. Test the DSn Interface Unit
Step Action
1 Replace the DSn interface unit. See Replace Hardware on page 5-1 for details.
3 If the test result is normal, it indicates the problem is with the replaced DSn interface unit.
d. So far, a complete DSn service trail has passed a series of loopback tests and can be loaded with actual
services.
4 If bit errors occur, refer to Product Support on page C-1 or repeat the above steps.
Chapter 5
REPLACE HARDWARE
OVERVIEW
Adding and/or replacing units are sometimes required operations during capacity expansion and the maintenance of
equipment. However, accidents are easily caused when such operations are conducted improperly. This chapter
focuses on the operation as well as events requiring attention during unit replacement.
Table 5-1 shows the operation and precautions of unit replacement.
Table 5-1. Operation and Precautions of Unit Replacement

Operation Sequence Operation Precautions
Before replacement Check and record the Confirm the optical transmission distance of
specifications of the unit. the optical interface unit.
Make sure the specifications of Check whether the tags on the fibers and
the substitute unit are the same cables from the unit are complete. If not,
as those of the former one. make them complete.
Keep a record of the relevant

configuration of the unit.
Get the substitute unit and

relevant tools ready.
During replacement Wear an ESD wrist strap. Remove the fibers and cables from the front
panel of the unit if there are any, and re-
Correctly swap the unit install them after the unit replacement.
according to section Plug/
Unplug Units on page 2-2. Avoid causing a short circuit to the unit.
Prevent the laser from hurting your eyes.

After replacement Check the flashing status of the Make sure the fiber and cable connection is
unit indicator and make sure the correct.
unit is working normally.
If the XO unit is replaced, you need to send
Query relevant alarms and the configuration, set the performance
performance events through the monitoring and back up the database once
NMS to make sure there are no more.
abnormal alarms.
For unit with backup function, check whether
Attach maintenance tag (marked it can perform switching normally.
with the name of this NE as well
as the fault phenomena) to the For the unit with no alarm reporting function,
replaced unit, and then place the check the operation status of the equipment
faulty unit into the antistatic bag. connecting with it.
Chapter 5: Replace Hardware July 27, 2005
GENERAL PRECAUTIONS
The following are aspects that require your attention when replacing units or other hardware functional units of the
optical network equipment.
• Common Language Equipment Identification (CLEI) code

• Static electricity
• Short circuit
• Laser
• Unit swapping
CLEI Code
The CLEI code of the substitute unit should be the same as that of the unit being replaced.
The CLEI code is placed on the right unit ejector, and the manufacturing code is placed on the left unit ejector
(Figure 5-1).
Figure 5-1. Specification mark of the unit
Static Electricity
CAUTION The static electricity produced by the human body can damage the sensitive components on the
circuit unit, such as large-scaled integrated circuit (IC).
In the cases of body movements, clothes friction, the friction between the shoes and ground, and plastics held in the
hand, the human body can generate static electromagnetic field and keep it for a long time.
When touching the equipment or taking units and IC chips by hand, always keep an ESD wrist strap attached to your
wrist and well grounded to avoid the static electricity in the human body damaging the sensitive apparatus. The
replaced unit must be kept in the static shielding bag or vacuum formed box.
July 27, 2005 Chapter 5: Replace Hardware
Short Circuit
During the maintenance, try to avoid short circuit caused by metal objects. For example, short circuit may be caused
by improper use and placement of the operation tools.
When loosening the captive screw on the front panel of the unit with tools such as screwdriver, place the metal tools
as far away from the equipment as possible after they are used. In another word, standardize your operation.
Pay attention to the toppled pins on the backplane when demounting the DSn interface unit. Never touch the toppled
pins with metal objects so as not to cause short circuit.
Laser
WARNING The laser beam inside the optical interface unit may hurt your eyes.
It is hazardous to approach or stare into the optical interface or optical fiber connector when installing or maintaining
the optical interface unit.
Unit Swapping
It should be noted that swapping units bearing service may cause service interruption. It is recommended to perform
hot swapping of units when the traffic is light.
CAUTION Do not exert too much strength when inserting the unit to avoid distorting the pins on the backplane.
Slide the unit into the slot along the guide rail and avoid contacts of the components on the unit to avoid
short circuit.
When holding the unit by hand, never touch the circuit, components, connector and wiring trough of the
unit.
After the substitute unit is seated on the backplane, wait for about two minutes for it to boot into normal operation.
Chapter 5: Replace Hardware July 27, 2005
Chapter 6
FAQ
This chapter covers the common problems you may encounter and the corresponding troubleshooting methods.
LOGIN
User Can Not Log In the System Though the User Name and Password Are Correct
Symptom A user cannot log in the system though both the User ID and password are correct.
Possible Reason 1. The User ID has expired.
2. The user password has expired.
3. The account is inhibited by system administrator.
The following approaches can be used as solutions:
Chapter 6: FAQ July 27, 2005
Approach 1:
Step Action
1 Log in to the system as the default user.
2 Query all user information with the following command:
RTRV-USER-SECU:::100;
3 Find the desired user information from the querying result. Check whether the User ID or password has
expired, or the account is inhibited.
For example, the information of user ADC can be as follows:
“ADC:,MAINT:TMOUTEN=ENABLE,TMOUTLN=60,PAGE=0,UAGE=0,USTATE=INACT&ALW&UIDUNEXP
&PIDUNEXP”
In “USTATE=INACT&ALW&UIDUNEXP&PIDUNEXP”,
INACT means this user has not logged in to the system.
ALW means this account is not inhibited.
INH means this account is inhibited.
UIDUNEXP means this account does not expire.
PIDUNEXP means this password does not expire.

4 If the User ID or password expires, modify the corresponding attributes through the user attribute
modification command:
ED-USER-SECU:
[<TID>]:<UID>:<CTAG>::[<NEWUID>],[<NEWPID>],,[<UPC>]:TMOUTEN=[<TMOUTEN>],
TMOUTLN=[<TMOUTLN>],PAGE=[<PAGE>],UAGE=[<UAGE>];
5 If the account is inhibited, enable it with the account enabling command:
ALW-USER-SECU:[<TID>]::<CTAG>::<UID>;
Approach 2:
Step Action
1 Log in to the system as the default user.
2 Create a new NE user account with the following command:
ENT-USER-SECU:
[<TID>]:<UID>:<CTAG>::<PID>,,<UPC>:TMOUTEN=[<TMOUTEN#ENABLE>],TMOUTLN=[<TMOUT
LN#60>],PAGE=[<PAGE#0>],UAGE=[<UAGE#0>];
3 Log in to the system with the newly created NE user account.
July 27, 2005 Chapter 6: FAQ
User Exits the System Automatically Though No Exit Command Is Issued
Symptom User exits the system though no exit command is issued.

Possible Reason 1. The current user performs no operation and the user timeout has expired. When
this period expires, the user exits automatically.
2. The current user is kicked out by other users.
The following steps can be used to solve the problem:
Step Action
1 Log in to the system again with the following command:
ACT-USER:[<TID>]:<UID>:<CTAG>::<PID>;
TIMING
Line Source Can Not Be Configured into Priority Table
Symptom The line source can not be configured into the priority table.
Possible Reason The logical unit is not created.
Step Action
1 Check whether the corresponding logical unit has been created with the following command:
RTRV-EQPT:::100;
If not, create it.
SSM Can Not Be Set Manually
Symptom The Synchronization Status Message (SSM) can not be set manually.
Possible Reason 1. The timing source to be set is not in the priority table.
2. When the SSM protocol is under GEN1 conditions, SSM can not be manually
configured with clock quality of GEN2.
Step Action
1 Check whether the source to be set is in the priority table.
RTRV-SYNCLIST::SYNC-NE:100;
RTRV-SYNCLIST::SYNC-BITS1:100;
RTRV-SYNCLIST::SYNC-BITS2:100;
2 Check the version of the current SSM protocol.
RTRV-NE-SYNC:::100;
Timing Source Priority Table Can Not Be Set Successfully
Symptom Setting of the timing source priority table is not successful.

Possible Reason 1. The timing mode is not correct.
2. The line timing source priority table contains timing sources BITS1 and/or
BITS2.
Step Action
1 Query the timing mode with the following command:
RTRV-NE-SYNC:ADC::100;
When TMMD=EXTERNAL, you are only allowed to edit the timing source BITS1/BITS2/INTERNAL into
the timing source table SYNC-NE.
When TMMD=LINE, you are only allowed to edit the line timing source into the timing source table
SYNC-NE.
When TMMD=MIXED, all timing sources can be edited into the timing source table SYNC-NE.
The timing source tables SYNC-BITS1 and SYNC-BITS2 are free from the above limitations. But the
timing sources BITS1 and BITS2 are not allowed into these two tables.
2 Modify the timing mode to a desired one with the following command:
ED-NE-SYNC:[<TID>]::<CTAG>:::MODE=[<TMMD>];
3 Set the timing source priority table with the following command:
ED-SYNCLIST:
[<TID>]:<SYNCTBID>:<CTAG>:::SYNCNUM=[<SYNCNUM#1>],FIRST=[<SYNC1#INTERNAL>],
SECOND=[<SYNC2#NONE>],THIRD=[<SYNC3#NONE>],FOURTH=[<SYNC4#NONE>];
SSMs of INTERNAL Are Inconsistent When Querying Through the Commands “RTRV-REAL-SSM” and
“RTRV-CUR-SYNC”
Symptom The SSMs of INTERNAL are inconsistent when querying through the commands
RTRV-REAL-SSM:[<TID>]:<SYNCTBID>:<CTAG>; and RTRV-CUR-
SYNC:[<TID>]:<SYNCTBID>:<CTAG>;.
Possible Reason The SSM retrieved by the command RTRV-REAL-
SSM:[<TID>]:<SYNCTBID>:<CTAG>; is one in actual and cannot be modified
manually. For example, the INTERNAL is default to ST3.
Before enabling the SSM protocol, the SSM level can be retrieved by the
command RTRV-CUR-SYNC:[<TID>]:<SYNCTBID>:<CTAG>, and is given by
the system. It is default that the SSM quality level for all timing sources in the
system is STU. Therefore, the quality information of INTERNAL is STU.
After enabling the SSM protocol, if the SSM of the timing source is set manually,
the SSM level can be retrieved by the command RTRV-CUR-
SYNC:[<TID>]:<SYNCTBID>:<CTAG>.
If the SSM of the timing source is not set manually, the SSMs will be the same
when querying through the commands:
RTRV-CUR-SYNC:[<TID>]:<SYNCTBID>:<CTAG>; and
RTRV-REAL-SSM:[<TID>]:<SYNCTBID>:<CTAG>;.
PROTECTION
TPS Protection Group Can Not Be Configured Successfully (LPS-800 only)
Symptom The TPS protection group can not be configured successfully.

Possible Reason 1. The corresponding logical unit is not installed.
2. The protection unit and protected unit are of line unit type.
3. The following requirements are not satisfied: When configuring TPS protection
group for PLT1/PDT1 unit, the slot for its protection unit is Slot 4 of the NE. When
configuring TPS protection group for PLT3/PQT3 unit, the slot for its protection unit
is Slot 3 of the NE.
4. When configuring two 1: 1 protection groups (one is for PLT1, the other is for
PLT3) at the same time, the following requirements are not satisfied: Slot 3 has
PLT3, Slot 4 has PLT1; Slot 5 has PLT1, Slot 6 has PLT3.
5. Use the DSn processing unit of lower capacity to protect the DSn processing
unit of higher capacity. For example, use PLT1 to protect PDT1, and use PLT3 to
protect PQT3.
Step Action
1 Delete the former logical unit.
2 Re-install the correct logical unit in the designated slot.
3 When Slot 4 is used as protection slot, install the unit PLT1/PDT1. The protected unit is PLT1/PDT1, too.
4 When configuring two 1:1 protection groups, seat PLT3/PQT3 in Slot 3, PLT1/PDT1 in Slot 4, PLT1/PDT1
in Slot 5, and PLT3/PQT3 in Slot 6.
5 Use PDT1 to protect PDT1 and PLT1, and use PQT3 to protect PQT3 and PLT3.
Lots of Abnormal Phenomena Occur in SONET Line Protection
Symptom Lots of abnormal phenomena occur in the SONET line protection.

Possible Reason 1. Protocol cannot work normally.
Step Action
1 Check the physical integrity of the connection to make sure the protection path can work normally.
UPSR Protection Pair Can Not Be Configured Successfully
Symptom The UPSR protection pair can not be configured successfully.

Possible Reason 1. The pre-configured path acts as both protection path and working path.
2. The service is configured with multiple sources and sole sink.
3. When configuring the concatenated service STS-3C or STS-12C, the No. of the
first path does not satisfy the formula: 3 (or 12)×n+1, or part of the consecutive
paths to be used are occupied.
Step Action
1 Make sure the path in use functions only as protection path or working path in the NE.
2 Make sure not all service sinks are configured to the same path.
3 Make the No. of the first path satisfy the formula: 3 (or 12)×n+1, and the consecutive paths to be used are
not occupied currently.
Services Are Blocked After Switching When 1+1 SONET Line Protection Group Is Configured
Symptom The services are blocked after switching when the 1+1 SONET line protection
group is configured (the services are normal before the switching).
Possible Reason 1. The protection group does not exist.
2. The protection group protocol is not enabled.
3. The protection group is in locked status.
4. The cross-connection is not configured completely.
5. The optical interface of the line unit where the protection optical interface locates
is not in service.
Step Action
1 Query whether the protection group exists with the following command:
RTRV-FFP:::100;
If not, create it.
If the protection group already exists, go on with the next step.

2 Check whether the switching protocol is started and query the status of the protection group with the
following command:
RTRV-FFP-STATE:[<TID>]:<FFPPGID>:<CTAG>;
If the protocol is not started (the protection group is in the status STOP or STARTING), start it with the
following command:
STA-FFP:[<TID>]:<FFPPGID>:<CTAG>;
If the protection group is locked, unlock it.
If the protection group is already in the switching status, go on with the next step.
3 Query whether the cross-connection is configured correctly and completely.
Pay attention to whether the service on the protection trail has been configured.
If nothing is wrong with the configuration of the cross-connection, go on with the next step.
4 Query whether the optical interface of the line unit where the protection optical interface locates is in
service.
<OC12 example:>
RTRV-LASER-OC12:[<TID>]:<FAC>:<CTAG>;
If the optical interface is not opened, open it.
<OC12 example:>
ED-LASER-OC12::[<TID>]:<FAC>:<CTAG>:::LASERSWITCH=OPEN;.
External Switching Clearing Command Does Not Function When External Switching Occurs in SONET Line
Protection
Symptom The external switching clearing command does not function when external
switching occurs in SONET line protection.
Possible Reason 1. The external switching is not launched by this end.
2. The PUID is wrong.
Step Action
1 Send the external switching clearing command from NE of another end.
This command can clear the external switching launched by the only end that sends the command. It can
not clear the external switching launched by the opposite end.
If the operation in the step does work, proceed to the next step.
2 Query the protection status and check the PUID of the external switching returned.
According to the PUID you get, re-send the external switching clearing command for the corresponding
PUID.
How to Modify SONET Line Protection Recovery Mode

Follow the steps below:
Step Action
1 Use the attribute modification command to modify the protection scheme (revertive or non-revertive).
ED-FFP:
[<TID>]:<FFPPGID>:<CTAG>:::TYPE=<FFPTYPE>,PSDIRN=<PSDIRN>,RVTM=[<RVTM>],
SDFLA G=[<SDFLAG>];
2 The recovery mode can be modified through the Wait to Restore Time (WTR) modification parameter
RVTM. Setting the RVTM to 9999 indicates the non-revertive mode is selected, while setting the RVTM
from 6 to 720 indicates the revertive mode is selected.
For example:
Modify the recovery mode to non-revertive mode:
ED-FFP:[<TID>]:<FFPPGID>:<CTAG>:::RVTM=9999;
Modify the recovery mode to revertive mode:
ED-FFP:[<TID>]:<FFPPGID>:<CTAG>:::RVTM=10;.
SONET Line Protection Group Can Not Be Configured Successfully
Symptom The SONET line protection group can not be configured successfully.
Possible Reason 1. The protection group number already exists.
2. The channel has been occupied.
Step Action
1 Query whether the protection group number to be created belongs to any of the existing protection groups.
If so, modify the protection group number to be created to one that has not been used. The protection
group number cannot be more than 12.
2 Query whether the channels currently use by all protection groups conflicts with the working channel or
protection channel of the protection group to be created. If they conflict, select a channel that has not been
used to create protection group.
Switching Does Not Happen When Bit Error Occurs in Working Path of SONET Line Protection
Symptom Bit errors occur in the working path, but no switching is performed.
Possible Reason 1. The SDFLAG attribute of the protection group is DISABLE.
2. The protection path also gets bit errors.
Step Action
1 Query the attributes of the protection group and check whether its SDFLAG attribute is DISABLE. When
SDFLAG=DISABLE, no Signal Degrade (SD) switching will occur. Set SDFLAG to ENABLE and then
observe whether switching can be performed.
2 When SDFLAG=ENABLE, check whether the current status of the protection group is
“PU-0:SF,SWITCH”.If it is, it indicates bit errors also occur to the protection path, and the working path is
used in priority. Therefore, no switching will occur.
SONET Line Switching Is Unsuccessful
Symptom The SONET line switching is unsuccessful.

Possible Reason 1. The protocol is stopped.
2. The protection path fails to work normally.
Step Action
1 Check the status of the protection group. If the status is STOP, start the protocol.
2 Check the integrity of the physical wiring to make sure the protection path can work normally.
Switching Occurs for the Working Path Though It Is Locked
Symptom Though the working path of the SONET line protection group is locked, switching
still occurs for it.
Possible Reason If one end of the working path of the SONET line protection group is locked, only
the switching launched by this end is locked. When the switching is launched by
the remote end, it will occur for the working path of local end, too.
Step Action
1 Check the switching status of the two ends with the following command:
RTRV-FFP-STATE::FFP-1:154;
If only one end of the working path is locked, use the following command to lock the other end of the
working path:
OPR-FFP-SW::FFP-1:198::PU-1,LOCK;.
CONNECTION
Services Are Blocked
Symptom Services are blocked.

Possible Reason 1. The working optical fiber is damaged in the event that the network is not
protected.
2. The laser of the working path is shut down in the event that the network is not
protected.
3. When the network is configured as SONET line protection and its protection
mode is modified to non-revertive mode, the services are forcedly switched to the
working path.
4. When the network is configured as UPSR and its protection mode is modified to
non-revertive mode, the services are forcedly switched to the working path.
5. When the network is configured as UPSR and its locked working paths have
failures.
6. Unit is reset.
7. Hardware reset the XO unit.
8. The configuration is lost.
9. The software works abnormally.
Step Action
1 Configure corresponding protection scheme or replace the optical fiber.
2 Configure corresponding protection scheme or start the laser.
Some NEs Cannot Be Reached
Symptom When fiber is broken somewhere in the network, NM server cannot communicate
to some NEs.
Possible Reason 1. The NM server uses IP over DCC function to communicate to the NEs. A set of
static routes are used to communicate between NM server and LPS-8xxs. If fiber is
broken somewhere, the static routes cannot be regenerated automatically.
2. The static routes are not recreated in the following circumstance:
• NE IP address is changed.
• New NE is added in the network.
• The topology of network is changed.
Step Action
1 Check for a fiber break and repair if a break is discovered.
2 Recreate the static route at NE side.
PERFORMANCE MONITORING
Some of the Records Display INVALID When Querying History Performance
Symptom Some of the records display INVALID when querying the history performance.
Possible Reason 1. The host is resetting.
2. The unit is resetting.
3. The user is sending command INIT-REG.
4. The user is sending command SET-PMDAY.
5. The user is modifying the NE time and date.
6. The port is in out-of-service (OOS) status in the corresponding cycle.
ALARM MORNITORING AND MANAGEMENT

Command RTRV-ALM-ALL Dose Not Work When Used for Querying Alarms
Symptom Alarms can not be queried with the command
RTRV-ALM-ALL:::100;.
Possible Reason 1. The attribute of the port is OOS instead of IS.
2. No service is configured to this port, no alarm is monitored accordingly.
3. The level of this alarm is NR or NA. Alarms only with levels of CR, MJ or MN can
be queried through the command
RTRV-ALM-ALL:::100;.
Step Action
1 Use the command RTRV-OC12 to query the attribute of this port. If it is OOS, use the command ED-OC12
to modify it to IS.
2 Query whether this port is configured with any service. If there is no service configured, no service alarm
will be generated.
3 If the alarm is of NR or NA level, use the command RTRV-COND-ALL:::100; for querying.
UNIT CONFIGURATION
Cross-connection Can Not Be Configured Successfully
Symptom The configuration of cross-connection is not successful.

Possible Reason 1. Configuration of dual-received cross-connection is not allowed.
2. The STS number is not correct.
3. The unit does not support the type of the cross-connection configured.
Step Action
1 Check whether the existing cross-connection has the same sink with that configured currently. Dual-
received cross-connection cannot be configured for the LPS-8xx equipment.
2 Check the STS number for correctness.
1. The STS-1 connection can use all paths with any number.
2. The STS-3C cross-connection can use the path numbered (3×N+1) (N>=0) only.
3. The STS-12C cross-connection can use the path numbered (12×N+1) (N>=0) only.
LPS-800
4. The maximum number for paths of the unit is as follows: 24 for OC12D, 12 for OC3Q, 3 for PLT3,
12 for PQT3, 6 for PDM3.
3 Check the type of the cross-connection and unit configured.
LPS-800
The OC12D unit can be configured with STS-1, STS-3C, STS-12C or VT1 cross-connection.
The OC3Q unit can be configured with STS-1, STS-3C or VT1 cross-connection.
The PLT3/PQT3/PDM3 unit can be configured with STS-1 cross-connection.
The PLT1/PDT1 unit can be configured with VT1 cross-connection.
LPS-810
The PLT3 unit can be configured with STS-1 cross-connection.
The PLT1 unit can be configured with VT1 cross-connection.

4 Check the representation of the cross-connection configured.
STS is represented as STS-Bid-STSid, where the first parameter is the slot number, and the second
parameter is the STS number.
VT is represented as VT1-BID-STSID-VTGID-VTID, where the first parameter is the slot number, the
second parameter is the STS number, the third parameter is the VTG number, and the forth parameter is
the VT number.
Physical Slot for an In-Service Unit Is NULL When Querying
Symptom The unit is in-service, but its physical slot displays NULL when querying.
Possible Reason The unit software is not started.
Step Action
1 Reset the unit.
The Unit Software Uploading Is Paused Caused by XO Reset
Symptom During uploading the unit software (except for the XO12/XO3 unit), the XO12/XO3
unit is reset. When the XO12/XO3 is recovered, the uploading is paused, and the
uploaded files cannot be deleted.
Possible Reason The uploaded file is protected. After about ten minutes, system will release the
protection state automatically.
Step Action
1 Wait for about ten minutes.
2 Delete the uploaded file.
3 Re-upload the unit software.
Appendix A
REGULAR MAINTENANCE RECOMMENDATION
In order to maintain the normal and stable running of the equipment, follow the recommendations in Table A-1 for
daily maintenance.
To make equipment maintenance more convenient and efficient, some tables are given below for reference.
Table A-1. Instruction

Section Description
Daily Maintenance and Operation Guide on page Used as reference for daily maintenance.
A-2
Monthly Maintenance and Operation Guide on Used as reference for monthly
page A-4 maintenance.
Quarterly Maintenance and Operation Guide on Used as reference for quarterly
page A-5 maintenance.
Annual Maintenance and Operation Guide on Used as reference for annual maintenance.
page A-5
Daily Maintenance Record on page A-6 Such records are made by the
maintenance personnel in the machine
room to describe the environment of the
machine room and the running of the
equipment on a daily basis.
Monthly (Quarterly) Maintenance Record on page Records describing maintenance made on
A-8 monthly (quarterly) basis.
Annual Maintenance Record on page A-9 A maintenance record made on annual
basis.
Emergency Troubleshooting Record on page A-9 Records describing the emergencies and
the associated measures already taken,
serving as the basis for future maintenance
and inquiry.
Unit Replacement Record on page A-10 Records describing the replacement of
units.
Data Modification Record on page A-10 Records describing the modification of
configuration data.
You can modify the maintenance record according to the local site practice.
LPS800-UM-MAIN-02 A-1
Appendix A: Regular Maintenance Recommendation July 27, 2005
DAILY MAINTENANCE AND OPERATION GUIDE

Types Items Operation Guide Referential Standards
Power supply in equipment Check the power monitoring Output voltage is normal, no
room system or test the output alarm indicating power
voltage. abnormality.
External Cleanliness in equipment Test the cleanliness of machine Refer to the attached table.
environment room room.
temperature
Temperature in equipment Test the temperature. Temperature range: 0oC to
check
room 45oC; the recommended
temperature range: 15oC to
30oC.
Humidity in equipment room Test the relative humidity. Relative humidity: 10% to 90%;
the recommended humidity:
40% to 65%.
Status of unit indicator Observe unit indicator. Refer to the LoopStar 800
Series Hardware Description
Manual, catalog number
LPS800-UM-HARD for
Equipment indicator explanation.
running status
check Temperature of equipment Test the temperature of The highest equipment
surface equipment surface. temperature detected by NM is
not allowed to exceed 40oC.
Status of fan (check it on Watch the fan indicator and the When the fans are running
the first day and the fifth day running of the fans. normally, only the green
every month) indicator illuminates.
A-2 LPS800-UM-MAIN-02
July 27, 2005 Appendix A: Regular Maintenance Recommendation

NM log-in Log in to the NM as junior user. Log-in to NM is normal.
An account for every
maintenance person is
recommended.
NE status check Log in to every NE through NM All NEs are in running status
to check its status. and log-in to all NEs is normal.
Unit status check Check the presence and According to slot diagram, the
running of units via the slot units should be properly seated
diagram in NM. and in running status.
Alarm check View current alarms and history There is no untraceable alarm
alarms by using the alarm in the system.
NM Maintenance inquiry and browsing function
offered by NM.
Performance event View current performance data Performance events reported
monitoring and history data by using the normal; all performance data of
performance data inquiry and bit error and pointer adjustment
browsing function offered by comply with Telcordia
NM. recommendations; no
performance data has crossed
threshold.
Protection switching check Check switching status and

switching alarm.
Log record query Use the operation log inquiry There is no attempt to log in to
function offered by NM. NM, and there is no
unidentified data modification.
Equipment environmental Check the temperature alarm There is no temperature alarm
variable check and voltage alarm of PMU unit and voltage alarm; temperature
via NM, and its temperature related performance data are
related performance data. normal.
Attached: machine room cleanliness requirement

Maximum 0.05 1 3 5
diameter (µm)
Maximum density 1.4 x 106 7 x 105 2.4 x 105 1.3 x 105
(particles/m3)
MONTHLY MAINTENANCE AND OPERATION GUIDE

Service check Idle channel 24-hour bit Test bit errors in the idle For DS1 channel, amount of bit
error measuring channels with 24 hours as a errors within 24 hours should
cycle by using meter. be 0.
NM activation and Activate and shutdown NM NM activation and shutdown
shutdown check software and computers. should be normal.
NE time query Query NE time through NM. NE time is consistent with the
current time, all NEs time
consistent.
Unit configuration data Check configuration data of Configuration data are
query. clock unit, overhead unit, consistent with the actual
tributary unit and line unit. requirements, and comply with
last record modifications.
NM maintenance Modify NM log-in password Modify NM log-in password Modify password every month.
item once every month.
NM database transferring Transfer NM database files, Such operations should be
and reorganization. and compress and repair them taken regularly. NM running
once every month. normal.
NM database backup Such operation should be taken
every month. NM and database
normal.
NM computer maintenance For PC, directories and files are
in normal status; there is no
illegal file (such as game file);
the hard disk can provide
sufficient space.
For working station, there is no

illegal file, the database running
normal.
Hardware interface status Check the working status of In good conditions.
check mouse, keyboard, monitor and
printer.
QUARTERLY MAINTENANCE AND OPERATION GUIDE

Remote Remote maintenance Log in to the NE from far end. NE log-in is normal, remote
maintenance function test maintenance function works
function test normally.
Rack cleanliness Rack cleanliness check Examine the interior and The rack surface is clean; there
check exterior of rack. is no excessive dust inside the
rack.
ANNUAL MAINTENANCE AND OPERATION GUIDE

Grounding resistance check Measure the grounding The total grounding resistance
resistance by using earth is less than 1 ohm.
resistance tester.
Grounding cable connection Check the reliability of (1) All connections are safe and
check connection of grounding cable reliable, and free of corrosion.
Grounding cable with grounding bar in machine
and power cable room. (2) Grounding bars not aged.
connection check
(3) Groundings well treated
with anti-corrosion measure,
and is free of corrosion.
Power cable connection Check the reliability of the (1) All connections are safe and
check connection of power cable with reliable, and free of corrosion.
power source in machine room.
(2) Power cable not aged.
DAILY MAINTENANCE RECORD

Date: __________(Year)__________(Month)__________(Day)
Shift time: From__________To__________
Person off duty: __________Person on duty: ___________
Types Items Status Remarks Maintained by

External environment (power Normal
supply, fire alarm, smoke,
thunder, etc) Abnormal
Temperature (normal, 15°C to Normal

30°C)
Equipment Abnormal
running
Humidity (normal, 40% to 65%) Normal
environment
Abnormal
Equipment room cleanliness Good
(good, bad)
Bad
Status of unit indicator Normal
Equipment Abnormal
running status
Equipment surface temperature Normal
check
Abnormal
Equipment fan status (check it Normal
on the first day and the fifth day
each month) Abnormal

NM log-in Normal
Abnormal
NE status check Normal
Abnormal
Unit status check Normal
Abnormal
Alarm check Normal
Abnormal
NM maintenance
Performance event monitoring Normal
Abnormal
Protection switching check Normal
Abnormal
Log query Normal
Abnormal
Equipment environment Normal
variable check
Abnormal
Fault description
and handling
Unsolved
problems
Checked by team
leader
MONTHLY (QUARTERLY) MAINTENANCE RECORD

Maintenance cycle: __________(Year)__________(Month)__________(Day) to
__________(Year)__________(Month)__________(Day)

Traffic check Selectively test channel 24- Normal
hour bit error
Abnormal
NM activation and shutdown Normal
check
Abnormal
NE time query Normal
Abnormal
Unit configuration information Normal
query
Abnormal
NM log-in password Normal
Modification
Abnormal
NM maintenance
NM database transferring and Normal
reorganization
Abnormal
Network management Normal
database backup
Abnormal
NM computer maintenance Normal
Abnormal
Hardware interface status Normal
Abnormal
Remote maintenance function Normal
test
Quarterly Abnormal
maintenance
Rack cleanliness check Normal
Abnormal
Problem
description and
troubleshooting
Unsolved
problems
Checked by team
leader
ANNUAL MAINTENANCE RECORD

Maintenance cycle: __________(Year)__________(Month)__________(Day) to
__________(Year)__________(Month)__________(Day)

Earth resistance check Normal
Abnormal
Grounding cable Grounding cable connection Normal

and power cable check
Abnormal
connection check
Power cable connection Normal
Abnormal
Problem
description and
troubleshooting
Unsolved
problems
Checked by team
leader
EMERGENCY TROUBLESHOOTING RECORD

Time of occurrence: Time of solution:
Person on duty: Handler:
Type of problem:
Power supply problem NM software problem

Trunk cable problem or distribution frame \problem Grounding problem or power connection problem
NM computer problem Data setting problem
Unit problem Operation problem
Software problem Other problems (temperature, humidity, rat,
electromagnetic interference, etc...)
Fault description:
Troubleshooting method and result:
UNIT REPLACEMENT RECORD

Name
Original Type
unit Slot
Name
New unit Type

Slot
Reason
Date
Person
DATA MODIFICATION RECORD

Modifier Time of Modication Cause of Modication Modification Description
Appendix B
SERIOUS FAILURE PROCESSING FLOW
FLOW CHART OF SERIOUS FAULT HANDLING
Serious failure refers to a failure that causes service interruption. Such a failure should be handled timely and
effectively. That is why the flow for a serious failure processing is made as shown in the following diagram. This can
also be used as the guide to the procedures and steps for the equipment room maintenance personnel to maintain
the equipment.
LPS800-UM-MAIN-02 B-1
Appendix B: Serious Failure Processing Flow July 27, 2005
Figure B-1. Flow chart of serious fault handling
B-2 LPS800-UM-MAIN-02
July 27, 2005 Appendix B: Serious Failure Processing Flow
FLOW DESCRIPTION AND PRECAUTIONS

• Make a factual and detailed record about the whole process of a fault whenrecording the fault. Such important
information as the occurring time of the fault, operations performed before and after the fault occurrence
should be recorded in detail. Alarm information and performance events in the NMS should also be saved
and observed.
• When it is found that the fault is obviously caused by external factors, such as cable problem, terminal equip-
ment (such as switch) problem, enter into other corresponding processing flow in time so as to solve the
fault as soon as possible.
• Follow the principle of recovering the service as early as possible when handling such faults. At the same time
when you are locating the fault, contact our engineers via the ADC’s customer service hotline (24 hours in
service). Our engineers will help you to analyze and locate the fault and work out an appropriate solution
together in a shortest time.
• When solving the problem, follow the operation specifications strictly when performing operations on the
equipment, for example, to wear the anti-static wrist strap. In this way, new problems can be avoided and
the fault range will not be enlarged.
• After service is recovered, the running status of the equipment and network must be traced and observed for
at least 24 hours to make sure the fault has been removed.
• After the fault is removed, fill in the relevant processing reports and forms in Regular Maintenance Recom-
mendation on page A-1, and close the fault handling flow.
RECOMMENDATION
• Implement the special-person maintenance system of NMS and equipment; accomplish software and hard-
ware maintenance level management as well as personnel training.
• After the fault is removed, it is recommended to write down the case in detail for later compilation accumulat-
ing experiences for future maintenance.
• It is recommended to read the relevant manuals delivered with the equipment from time to time and gain more
knowledge about the equipment.
• You may visit the relevant websites of ADC at any time: Refer to Product Support on page C-1.
LPS800-UM-MAIN-02 B-3
Appendix B: Serious Failure Processing Flow July 27, 2005
B-4 LPS800-UM-MAIN-02
Appendix C
PRODUCT SUPPORT
ADC Customer Service Group provides expert pre-sales support and training for all of its products. Technical
support is available 24 hours a day, 7 days a week by contacting the ADC Technical Assistance Center.
Sales Assistance: 800.366.3891 Quotation Proposals, Ordering and Delivery General,

and Product Information
Systems Integration: 800.366.3891 Complete Solutions (from concept to installation),
Network Design and Integration Testing, System Turn-
Up and Testing, Network Monitoring (upstream or
downstream), Power Monitoring and Remote
Surveillance, Service/Maintenance Agreements, and
Systems Operation
ADC Technical Assistance Center: Technical Information, System/Network Configuration,
800.366.3891 Product Specification and Application, Training
(product-specific), Installation and Operation
Email: wsd.support@adc.com Assistance, and Troubleshooting and Repair/Field
Assistance
Online Technical Support: www.adc.com/Knowledge_Base/index.jsp
Online Technical Publications: www.adc.com/documentationlibrary/
technicalpublications/
Product Return Department: 800.366.3891 ADC Return Material Authorization (RMA) number and
instructions must be obtained before returning products.
Email: repair.return@adc.com
LPS800-UM-MAIN-02 C-1
Appendix C: Product Support July 27, 2005
C-2 LPS800-UM-MAIN-02
GLOSSARY
A
ABR – Available Bit Rate
ACE – Adaptive Communication Environment
ADM – Add/Drop Multiplexer
ADSL – Asymmetric Digital Subscriber Line
AIS – Alarm Indication Signal
ALS – Automatic Laser Shutdown
AM – Administration Module
AMI – Alternate Mark Inversion Code
ANSI – American National Standard Institute
AP – Span-Powered Access Point
APS – Automatic Protection Switching
ASCII – American Standard Code for Information Interchange
ASN.1 – Abstract Syntax Notation One
ATM – Asynchronous Transfer Mode
AWG – American Wire Gauge
B
B-DCS – Broadband digital cross connects
BER – Bit Error Rate
BIOS – Basic Input/Output System
BIP – Bit Interleaved Parity
BITS – Building Integrated Timing Supply
BLSR – Bi-directional Line Switched Ring
BML – Business Management Layer
BOM – Bill of Materials
C
CA – Certificate Authority
CAR – Committed Access Rate
CD – CD/CD-ROM
CDE – Common Desktop Environment
CM – Communication Module
CMISE – Common Management Information Service Element
CO – Central Office
CORBA – Common Object Request Broker Architecture
CoS – Class of Service
CPU – Central Processing Unit
CR – Carriage Return
CTS – Clear To Send
CUI – Code User Interface
LPS800-UM-MAIN-02 GL-1
Glossary July 27, 2005
D
DBCHG – Database Changed
DC – Direct Current
DCN – Data Communication Network
DDN – Digital Data Network
DHCP – Dynamic Host Configuration Protocol
DLC – Digital Loop Carrier
DN – Distinguished Name
DNI – Dual Node Interconnection
DNS – Domain Naming System
DRI – Dual Ring Interconnection
DSL – Digital Subscriber Loop
DSLAM – Digital Subscriber Line Access Multiplexer
DSSS – Direct Sequence Spread Spectrum
DUS – Do not use for timing synchronization
DWDM – Dense Wavelength Division Multiplexing
DXC – Digital Cross Connect System
E
ECC – Embedded Control Channel
EC-1 – Electrical Carrier Level 1
EFS – Error-free second
EMC – Electro Magnetic Compatibility
EML – Element Management Layer
EMI – Electro Magnetic Interference
EMS – Element Management System
EPL – Ethernet Private Line
EPLAN – Ethernet Private LAN
EPS – Equipment Protection Switch
ES – Errored second
ESCON – Enterprise System Connection
ESD – Electrostatic Discharge
EVPL – Ethernet Virtual Private Line
EVPLAN – Ethernet Virtual Private LAN
F
FAQ – Frequently Asked Questions
FCAPS – Fault Management, Configuration Management, Accounting Management, Performance Management,
Security Management
FE – Fast Ethernet
FEAC – Far-End Alarm Control
FICON – Fiber Connection
FLASH – FLASH memory
FSVP – Fiber Share Virtual Path
FTP – File Transfer Protocol
GL-2 LPS800-UM-MAIN-02
July 27, 2005 Glossary
G
GCM – Global Cluster Manager
GE – Gigabit Ethernet
GFP – Generic Framing Procedure
GNE – Gateway Network Element
G.SHDSL – Single-pair High-speed Digital Subscriber Line
GUI – Graphic User Interface
H
HA – High-Availability
HDLC – High-level Data Link Control
HTTP – Hypertext Transfer Protocol
HTTPS – Hypertext Transfer Protocol Secure
I
IC – Integrated Circuit
IGMP – Internet Group Management Protocol
iMAP – Integrated Management Application Platform
IP – Internet Protocol
IR – Intermediate Reach
ISDN – Integrated Services Digital Network
ITU-T – International Telecommunication Union-Telecommunication Standardization Sector
L
LAG – Link Aggregation Group
LAN – Local Area Nertwork
LAPS – Line Automatic Protection Switching
LBO – Line Build-Out
LCAS – Link Capacity Adjustment Scheme
LCS – Leased Circuit Service
LCT – Local Craft Terminal
LED – Light Emitting Diode
LLC – Logical Link Control
LOF – Loss Of Frame
LOP – Loss Of Pointer
LOS – Loss Of Signal
LPT – Link Pass Through
LR – Long Reach
LSP – Label Switch Path
M
MAC – Media Access Control
MADM – Multiple Add/Drop Multiplexer
MCF – Message Communication Function
MDI – Multi-Document Interface
MDP – Message Dispatch Process
Mgr – Manager
MIB – Management Information Base
MIT – Managed Object Instance Tree
MLM – Multi-Longitudinal Mode (laser)
MLT – Mechanized Loop Testing
MML – Man Machine Language
MO – Managed Object
MPLS – Multiprotocol Label Switching
MPPE – Microsoft Point-to-Point Encryption Protocol
MS – Multiplex Section
MTIE – Maximum Time Interval Error
MUX – Multiplexer
N
NE – Network Element
NEL – Network Element Level
NEBS – Network Equipment Building System
NIC – Network Interface Card
NM – Network Management
NML – Network Management Layer
NMS – Network Management System
NP – Network Processor
NT1 – Network Termination Type-1
O
OAM – Operation Administration and Maintenance
OAM&P – Operation, Administration, Maintenance and Provisioning
OC-1 – Optical Carrier Level 1
OC-N – Optical Carrier Level N
OEM – Original Equipment Manufacturer
OH – Overhead
OIF – Optical Internetworking Forum
ORL – Optical Return Loss
OSF – Operation System Function
OSI – Open Systems Interconnection
OSP – Outside Plant
OSPF – Open Shortest Path First
P
PC – Personal Computer
PDH – Plesiochronous Digital Hierarchy
PE – Provider Edge
PGND – Protection Ground
PIU – Power Interface Unit
PLM – Payload Label Mismatch
PM – Performance Management
POH – Path Overhead
POTS – Plain Old Telephone Service
PP – Path Protection
PRS – Primary reference source
PST – Primary State
PSTN – Public Switched Telephone Network
PTP – Point-to-Point
Q
QoS – Quality of Service
R
RADIUS – Remote Authentication Dial-In Service
RAM – Remote Access Multiplexer
RAS – Remote Access Server
RDI – Remote Defect Indication
RDMS – Relational Database Management System
REG – Regenerators
RES – Reserved for Network Synchronization Use
RMA – Return Material Authorization
RMS – Root-Mean-Square
RMON – Remote Monitoring
RPR – Resilient Packet Ring
RS – Regenerator Section
RTS – Request To Send
RUP – Rational Unified Process
S
SCB – Serial Communication Bus
SCC – System Control and Communication Mode
SCSI – Small Computer Systems Interface
SD – Signal Degradation
SDBER – Signal Degrade Bit Error Ratio
SDH – Synchronous Digital Hierarchy
SEFS – Severely errored frame second
SEMF – Synchronous Equipment Management Function
SES – severely errored second
SF – Signal Failure
SIF – SONET Interoperability Forum
SLM – Single Longitudinal Mode
SMC – SONET minimum clock
SML – Service Management Layer
SMS – Service Management System
SMTP – Simple Mail Transfer Protocol
SN – Sequence Number
SNCMP – Sub-Network Connection Multiple Protection
SNCP – Sub-Network Connection Protection
SNML – Sub-Network Management Layer
SNMP – Simple Network Management Protocol
SNMS – Sub-Network Management System
SOH – Section Overhead
SONET – Synchronous Optical Network
SPE – Synchronous Payload Envelope
SSID – Service Set Identifier (Wireless Network Name)
SSL – Secure Sockets Layer
SSM – Synchronization Status Marker
SSR – Side-mode Suppression Ratio
SST – Secondary State
STP – Spanning Tree Protocol
STS – Synchronous Transport Signal
STS-1 – Synchronous Transport Signal Level 1
STU – Sync traceability unknown
T
TCM – Tandem Connection Measurement
TC-PAM – Trellis Coded Pulse Amplitude Modulation
TCP/IP – Transmission Control Protocol/Internet Protocol
TDEV – Time Deviation
TDM – Time Division Multiplex
TKIP – Temporary Key Integrity Protocol
TL1 – Transaction Language 1
TM – Terminal Multiplex
TMF – Telecommunication Management Forum
TMN – Telecommunication Management Network
TNC – Transit node clock
TOH – transport overhead
TPS – Tributary Protection Switching
TTL – Time To Live
TU – Tributary Unit
U
UAS – Unavailable Seconds
UBR – Unspecified Bit Rate
UML – Unified Modeling Language
UNEQ – Unequipped
UPS – Uninterrupted Power Supply
UPSR – Unidirectional Path Switched Ring
V
VC – Virtual Circuit
VCI – Virtual Circuit Identifier
VCS – Veritas Cluster Server
VLAN – Virtual Local Area Network
VOD – Video On Demand
VPI – Virtual Path Identifier
VPN – Virtual Private Network
VT – Virtual Tributary
VVR – Veritas Volume Replication
VxVM – Veritas Volume Manager
W
WAN – Wide Area Network
WDM – Wavelength Division Multiplexing
WECA – Wireless Ethernet Compatibility Alliance
WEP – Wired Equivalent Privacy
WLAN – Wireless Local Area Network
WPA – WiFi Protected Access
WSF – Workstation Function
WTR – Wait-to-Restore
Certification and Warranty
FCC Class A Compliance
This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15
of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when
the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio
frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful
interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful
interference in which case the user will be required to correct the interference at his own expense.
Limited Warranty
Product warranty is determined by your service agreement. Refer to the ADC Warranty/Software Handbook for
additional information, or contact your sales representative or Customer Service for details.
Modifications
The FCC requires the user to be notified that any changes or modifications made to this device that are not
expressly approved by ADC voids the user’s warranty.
All wiring external to the products should follow the provisions of the current edition of the National Electrical Code.
Safety Standards Compliance
This equipment has been tested and verified to comply with the applicable sections of the following safety stan-
dards:
• GR 63-CORE - Network Equipment-Building System (NEBS) Requirements
• GR 1089-CORE - Electromagnetic Compatibility and Electrical Safety
• Binational Standard, UL-60950 3rd Edition/CSA1459 C22.2 No. 60950-00: Safety of Information Technology
Equipment
For technical assistance, refer to “Appendix C: Product Support” on page C-1.
World Headquarters
ADC Telecommunications, Inc.
PO Box 1101
Minneapolis, MN 55440-1101 USA
For Technical Assistance
Tel: 800.366.3891
LoopStar® 800 Series

Maintenance Manual
Product Catalog: LPS-FRM8xx-Lx

Document Number: LPS800-UM-MAIN-02
´-@M¶5ß¨
1332455

Loopstar 800 Series: Maintenance Manual

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Loopstar 800 Series: Maintenance Manual

Uploaded by

Copyright:

Available Formats

LoopStar® 800 Series

Product Catalog: LPS-FRM8xx-Lx

Revision Release Date Revisions Made

Appendix A: Regular Maintenance Recommendation .............................................. A-1

LoopStar® 800 Series WebLCT Introduces configuration and maintenance operations of

Reader Alert Meaning

INSPECTING YOUR SHIPMENT

Table 1-1. Temperature and humidity requirements

4. Ensure Good Ventilation of Equipment

PRECAUTIONS OF MAINTENANCE OPERATIONS

1. Handling Optical Interface of OC-N Unit and Fiber Jumper Connector

Precautions of Electrical Safety

2. Precautions for Unit Electrical Safety

Precautions of Mechanical Safety

Precautions of NM System Maintenance

Do not run any software irrelevant to equipment maintenance.

Precautions of Service Configuration

PLUG/UNPLUG FIBER JUMPERS

Figure 2-2. Fiber jumper with LC optical interface

1. Correct Way of Inserting a Unit

AUDIBLE ALARM CUT-OFF

CLEANING FIBER CONNECTORS

BIT ERROR RATE TESTING

1. Online Testing Method

Figure 2-3. Bit error test

TRANSMITTER/RECEIVER OPTICAL POWER TESTING

2. Test Receiver Optical Power

ROUTINE MAINTENANCE ITEMS

Table 3-1. Typical routine maintenance item

Audible Alarm Notification

It is recommended to check the audible alarm once a day.

Equipment Alarm Indicators

Figure 3-1. LPS-800 System status panel

Figure 3-2. LPS-810 System status panel

The specific meaning of all the indicators is shown in Table 3-2.

Table 3-2. Indicators and their meanings

It is recommended to observe the equipment alarm indicators once a day.

Table 3-3. Ambient temperature requirements for equipment operation

It is recommended to check the temperature of the equipment room once a day.

NE and Unit Status

It is recommended to check the NE and unit status once a day.

It is recommended to browse the alarms once a day.

1. Performance Monitoring Configuration

2. Performance Data Viewing

•View performance data

•Viewing performance threshold-crossing data

It is recommended to browse the performance events once a day.

Checking and Replacing Air Filter Periodically

Bit Error Rate Test

It is recommended to perform BER once a month as part of routine maintenance.

Modifying Login Password of NM System

OC-N Inside the optical interface unit (OC3 or OC12,

OC-N Inside the optical interface unit (OC3 or OC12,

DSn Inside the DSn processing unit (PLT3, PLT1 -

XO unit Inside the cross-connect unit, send the service

IDENTIFING NETWORK FAULTS

NE-A Create facility loopback for DSn processing unit.

Perform a Facility Loopback on NE-A’s DSn Processing Unit

Figure 4-1. Perform a facility loopback on NE-A’s DSn processing unit

1. Create a Facility Loopback on NE-A’s DSn Processing Unit

2. Test the Facility Loopback

3. Check the DSn Cable

4. Test the DSn Processing Unit