lps800 810mtce maintenance

LoopStar® 800 Maintenance Manual

Document Number: LPS800-UM-MAIN-04

Product Catalog: LPS-FRM800-Lx

REVISION HISTORYThe Revision History provides a summary of any changes in this manual. Please make sure you are using thelatest revision of this manual.April 14, 2006

This manual is available online at ADC’s website (www.adc.com/documentationlibrary/) or you can order copiesof the manual by contacting your sales representative. Please ask for document LPS800-UM-MAIN-04.

Copyright©2009 ADC Telecommunications, Inc. All rights reserved.

Trademark InformationADC 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 tosuch 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 LiabilityInformation 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 furtherdisclaims any and all liability for indirect, incidental, special, consequential or other similar damages. This disclaimer ofliability applies to all products, publications and services during and after the warranty period.

Revision Release Date Revisions Made01 January 12, 2005 Initial release.

02 July 27, 2005 Updated with LPS-800 Release 2 and LPS-810 Release 1.

03 April 7, 2006 Misc. technical updates.

04 February 23, 2009 Technical Update.

Table of Contents

LPS800-UM-MAIN-04 iii

About This Document .......................................................................................................... xi

Chapter 1: Maintenance Overview ...................................................................................... 1-1Running Environment of LoopStar 800 .......................................................................................... 1-1Precautions of Maintenance Operations ........................................................................................ 1-2

Laser Precautions .................................................................................................................... 1-2Precautions of Electrical Safety ............................................................................................... 1-2Precautions of Other Personal Safety ...................................................................................... 1-3Precautions of Mechanical Safety ............................................................................................ 1-3Precautions of EMS System Maintenance ............................................................................... 1-3Precautions of Service Configuration ....................................................................................... 1-3

Chapter 2: Basic Operations ............................................................................................... 2-1Fan and Air Filter Maintenance ...................................................................................................... 2-1Plugging/Unplugging Fiber Jumper ................................................................................................ 2-2Inserting/Removing a Unit .............................................................................................................. 2-2

Inserting a Unit ......................................................................................................................... 2-2Removing a Unit ....................................................................................................................... 2-2

Audible Alarm Cut-Off .................................................................................................................... 2-3Checking Software Version ............................................................................................................ 2-3

Checking Software Version by EMS ........................................................................................ 2-3Checking Software Version by TL1 .......................................................................................... 2-3

Resetting ........................................................................................................................................ 2-5Cold Resetting .......................................................................................................................... 2-5Warm Resetting ........................................................................................................................ 2-5

Inspecting and Cleaning the Fiber-Optic Connectors .................................................................... 2-6Overview .................................................................................................................................. 2-6Inspecting Optical Connectors ................................................................................................. 2-7Cleaning Optical Fiber Connectors Using Cartridge Cleaners ................................................ 2-10Cleaning Optical Fiber Connectors Using Lens Tissue ........................................................... 2-12Cleaning Optical Adapters Using Optical Cleaning Sticks ....................................................... 2-13

Bit Error Rate Testing ..................................................................................................................... 2-16Online Testing Method ............................................................................................................. 2-16Offline Testing Method .............................................................................................................. 2-16

Transmitter/Receiver Optical Power Testing .................................................................................. 2-17Testing Transmitter Optical Power ........................................................................................... 2-17Testing Receiver Optical Power ............................................................................................... 2-18

Table of Contents

iv LPS800-UM-MAIN-04

Chapter 3: Routine Maintenance ......................................................................................... 3-1Overview ........................................................................................................................................ 3-1

Purpose .................................................................................................................................... 3-1Classification ............................................................................................................................ 3-1

Routine Maintenance Items ........................................................................................................... 3-2Audible Alarm Notification ........................................................................................................ 3-2Equipment Alarm Indicators ..................................................................................................... 3-2Unit Alarm Indicators ................................................................................................................ 3-4Temperature ............................................................................................................................. 3-12NE and Unit Status ................................................................................................................... 3-12Alarms ...................................................................................................................................... 3-12Performance Events ................................................................................................................. 3-12Protection Switching ................................................................................................................. 3-13Querying NE Time .................................................................................................................... 3-14Checking and Replacing Air Filter Periodically ........................................................................ 3-14Testing Bit Error Rate ............................................................................................................... 3-14

Chapter 4: Loopback and Network Test ............................................................................. 4-1Loopback ........................................................................................................................................ 4-1

Facility Loopback ...................................................................................................................... 4-1Terminal Loopback ................................................................................................................... 4-2Path Loopback ......................................................................................................................... 4-3FEAC Loopback ....................................................................................................................... 4-3FAC2 Loopback ........................................................................................................................ 4-4

Identifying Network Faults .............................................................................................................. 4-4Performing a Facility Loopback on NE-A’s DSn Processing Unit ............................................ 4-5Performing a Path Loopback on the NE-A ............................................................................... 4-7Performing a Terminal Loopback on NE-A’s Eastbound OC-N Interface Unit ......................... 4-8Performing a Facility Loopback on NE-B’s Westbound OC-N Interface Unit .......................... 4-10Performing a Terminal Loopback on NE-B’s Eastbound OC-N Interface Unit ......................... 4-11Performing a Facility Loopback on NE-C’s Westbound OC-N Interface Unit .......................... 4-13Performing a Path Loopback on the NE-C ............................................................................... 4-14Performing a Terminal Loopback on NE-C’s DSn Processing Unit ......................................... 4-16Performing a Facility Loopback on NE-C’s DSn Processing Unit ............................................ 4-17

Table of Contents

LPS800-UM-MAIN-04 v

Chapter 5: Replacing Hardware .......................................................................................... 5-1Overview ........................................................................................................................................ 5-1General Precautions ...................................................................................................................... 5-1

CLEI Code ................................................................................................................................ 5-1Manufacturing Code ................................................................................................................. 5-2Static Electricity ........................................................................................................................ 5-2Short Circuit .............................................................................................................................. 5-2Laser ........................................................................................................................................ 5-3Unit Swapping .......................................................................................................................... 5-3

Before Replacement ...................................................................................................................... 5-3Preparation for Replacing a Common Control Unit .................................................................. 5-3Preparation for Replacing an OC-N Unit .................................................................................. 5-4Preparation for Replacing a DSn Processing Unit ................................................................... 5-5Preparation for Replacing an Ethernet Unit ............................................................................. 5-5Preparation for Replacing a DSn Interface Unit ....................................................................... 5-5Preparation for Replacing a Power Interface Unit .................................................................... 5-6Preparation for Replacing a Fan Tray ...................................................................................... 5-6Preparation for Replacing an Air Filter ..................................................................................... 5-6

During Replacement ...................................................................................................................... 5-6After Replacement .......................................................................................................................... 5-7

Chapter 6: Troubleshooting ................................................................................................. 6-1Login ............................................................................................................................................... 6-1

User Cannot Log In The System Though The User Name and Password Are Correct .......... 6-1User Exits The System Automatically Though No Exit Command Is Issued ........................... 6-2

Timing ............................................................................................................................................. 6-3Line Source Cannot Be Configured Into Priority Table Symptom ............................................ 6-3Possible Cause ........................................................................................................................ 6-3Line Source Cannot Be Detected ............................................................................................. 6-3External Clock Source Cannot Be Detected ............................................................................ 6-4SSM Cannot Be Set Manually Symptom ................................................................................. 6-4Timing Source Priority Table Cannot Be Set Successfully Symptom ...................................... 6-5E1 Port Cannot Be Set As Timing Source ............................................................................... 6-5

Protection ....................................................................................................................................... 6-6TPS Protection Group Cannot Be Configured Successfully .................................................... 6-6Ethernet Protection Group Cannot Be Configured Successfully ............................................. 6-7Lots of Abnormal Phenomena Occur in SONET Line Protection ............................................ 6-7UPSR Protection Pair Cannot Be Configured Successfully Symptom .................................... 6-8Services Are Blocked After Switching When 1+1 SONET Line Protection Group Is Configured 6-8External Switching Clearing Command Does Not Function When External Switching Occurs in SONET Line Protection ............................................................................................................ 6-9How to Modify SONET Line Protection Recovery Mode ......................................................... 6-10SONET Line Protection Group Cannot Be Configured Successfully ....................................... 6-10

Table of Contents

vi LPS800-UM-MAIN-04

Switching Does Not Happen When Bit Error Occurs In Working Path Of SONET Line Protection ................................................................................................................................. 6-11SONET Line Switching Is Unsuccessful Symptom .................................................................. 6-12Switching Occurs for the Working Path Though It Is Locked ................................................... 6-12Failing To Deliver The Command For The Manual Switching Of The Clock Source ............... 6-13Failing To Configure The BLSR Protection .............................................................................. 6-14Failing To Configure The BLSR Switching ............................................................................... 6-15Failing To Create RingMap After The Full-Ring BLSR Protection Is Created .......................... 6-15Interrupted Services Caused By The BLSR Switching ............................................................ 6-16

Connection ..................................................................................................................................... 6-16Services Are Blocked Symptom ............................................................................................... 6-16Some NEs Cannot Be Reached With Static Route .................................................................. 6-17Some NEs Cannot Be Reached With Dynamic Routes ........................................................... 6-18Faults in the SNMP Network .................................................................................................... 6-19NMS Cannot Receive the Trap Message Symptom ................................................................ 6-19

Performance Monitoring ................................................................................................................. 6-19Some Of The Records Display INVALID When Querying History Performance ..................... 6-19

Alarm Monitoring and Management ............................................................................................... 6-20Alarms Cannot Be Queried Using The Command RTRV-ALM-ALL ........................................ 6-20

Unit Configuration ........................................................................................................................... 6-21Cross-connection Cannot Be Configured Successfully ........................................................... 6-21Physical Slot For An In-Service Unit Is NULL When Querying Symptom ................................ 6-22

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

Daily Maintenance and Operation Guide ....................................................................................... A-2Monthly Maintenance and Operation Guide .................................................................................. A-3Quarterly Maintenance and Operation Guide ................................................................................ A-4Annual Maintenance and Operation Guide .................................................................................... A-4Daily Maintenance Record ............................................................................................................. A-5Monthly (Quarterly) Maintenance Record ...................................................................................... A-7Annual Maintenance Record .......................................................................................................... A-8Emergency Troubleshooting Record .............................................................................................. A-8Unit Replacement Record .............................................................................................................. A-9Data Modification Record ............................................................................................................... A-9

Table of Contents

LPS800-UM-MAIN-04 vii

Appendix B: Serious Failure Processing Flow ........................................... B-1Flow Chart of Serious Fault Handling ............................................................................................ B-1Flow Description and Precautions .................................................................................................. B-2Recommendation ........................................................................................................................... B-2

Appendix C: LoopStar 800 Glossary ........................................................... C-1

Appendix D: LoopStar 800 Acronyms and Abbreviations ......................... D-1

Appendix E: Product Support ...................................................................... E-1

Table of Contents

viii LPS800-UM-MAIN-04

List of Figures

LPS800-UM-MAIN-04 vii

Figure 2-1. The Air Filter ...................................................................................................................... .. 2-1Figure 2-2. Fiber Jumper with LC Optical Interface ............................................................................. .. 2-2Figure 2-3. Optical Adapter .................................................................................................................. .. 2-6Figure 2-4. Optical Fiber Connector ..................................................................................................... .. 2-6Figure 2-5. Recommended Protective Caps ........................................................................................ .. 2-7Figure 2-6. Non-recommended Protective Caps ................................................................................. .. 2-7Figure 2-7. An Intact Fiber .................................................................................................................... .. 2-8Figure 2-8. Damaged or Questionable Fibers ...................................................................................... .. 2-9Figure 2-9. An Intact Fiber .................................................................................................................... 2-10Figure 2-10. Acceptable Fibers with Imperfections .............................................................................. 2-10Figure 2-11. Unacceptable Fibers with Imperfections .......................................................................... 2-10Figure 2-12. CLETOP Cassette Cleaner .............................................................................................. .2-11Figure 2-13. Using the CLETOP Cleaner ............................................................................................. .2-11Figure 2-14. Dragging Fiber Tip Lightly on One Cleaning Area ........................................................... 2-12Figure 2-15. Dragging Fiber Tip Lightly on the Other Cleaning Area ................................................... 2-12Figure 2-16. Cleaning the Fiber Tip With the Lens Tissue On the Desk .............................................. 2-13Figure 2-17. Cleaning the Fiber Tip With the Lens Tissue On the Hand ............................................. 2-13Figure 2-18. Cleaning Stick for the SC and FC Optical Interface (Reference Only) ............................ 2-14Figure 2-19. Cleaning Stick for the LC Optical Interface (Reference Only) ......................................... 2-14Figure 2-20. Using a Cleaning Stick ..................................................................................................... 2-15Figure 2-21. Bit Error Rate Test ........................................................................................................... 2-17Figure 3-1. System Status Panel .......................................................................................................... .. 3-3Figure 4-1. Perform a Facility Loopback on NE-A’s DSn Processing Unit ........................................... .. 4-5Figure 4-2. Perform a Path Loopback on the NE-A ............................................................................. .. 4-7Figure 4-3. Perform a Terminal Loopback on NE-A’s Eastbound OC-N Interface Unit ........................ .. 4-8Figure 4-4. Perform a Facility Loopback on NE-B’s Westbound OC-N Interface Unit ......................... 4-10Figure 4-5. Perform a Terminal Loopback on NE-B’s Eastbound OC-N Interface Unit ....................... .4-11Figure 4-6. Perform a Facility Loopback on NE-C’s Westbound OC-N Interface Unit ......................... 4-13Figure 4-7. Perform a Path Loopback on the NE-C ............................................................................. 4-14Figure 4-8. Perform a Terminal Loopback on NE-C’s DSn Processing Unit ........................................ 4-16Figure 4-9. Perform a Facility Loopback on NE-C’s DSn Processing Unit .......................................... 4-17Figure 5-1. Specification Mark of the Unit ............................................................................................ .. 5-1Figure 5-2. Specifications of the Manufacturing Code ......................................................................... .. 5-2Figure B-1. Flow Chart of Serious Fault Handling ............................................................................... ..B-1

List of Figures

viii LPS800-UM-MAIN-04

List of Tables

LPS800-UM-MAIN-04 ix

Table 3-1. Typical Routine Maintenance Item ...................................................................................... .. 3-2Table 3-2. System Status Indicators ..................................................................................................... .. 3-3Table 3-3. XO/TO Unit Indicators ......................................................................................................... .. 3-4Table 3-4. OCN Unit Indicators ............................................................................................................ .. 3-5Table 3-5. LPS-ELS4 Unit Indicators .................................................................................................... .. 3-6Table 3-6. LPS-EFS8 Unit Indicators ................................................................................................... .. 3-7Table 3-7. LPS-EGT2 Unit Indicators ................................................................................................... .. 3-8Table 3-8. LPS-EGS4 Unit Indicators ................................................................................................... .. 3-9Table 3-9. LPS-ET4GS Unit Indicators ................................................................................................ 3-10Table 3-10. DSn Unit Indicators ........................................................................................................... .3-11Table 3-11. Ambient Temperature Requirements for Equipment Operation ........................................ 3-12

List of Tables

x LPS800-UM-MAIN-04

LPS800-UM-MAIN-04 xi

ABOUT THIS DOCUMENT

PURPOSEThe LoopStar 800 Maintenance Manual provides tha analysis and torubleshooting of common faults.

INTENDED AUDIENCEThis manual is intended for:

• Operation groups• Maintenance engineers

RELATED MANUALSThe related manuals are listed in the following table.

Manual Usage

LoopStar 800 WebLCT Manual Introduces configuration and maintenance operations of LoopStar 800 Series LCT.

LoopStar 800/LoopStar 1600/LoopStar 3600 Operations Manual

Introduces configuration and maintenance operations of LoopStar 800/1600/3600 Series EMS.

LoopStar 800 Application and Engineering Manual

Acquaints you with the LoopStar 800 and describes how to build the required network using the LoopStar 800.

LoopStar 800 Hardware Description Manual Describes the LoopStar 800 Series system hardware including chassis, power interface module, fan tray assembly, plug-in units, and the interfaces.

LoopStar 800/LoopStar 1600/LoopStar 3600 TL1 Commands Manual

Detailed introduction to the TL1 commands used in the LoopStar 800/1600/3600 Series.

LoopStar 800 Installation Manual Describes how to install the LoopStar 800 Series.

LoopStar 800 Alarm and Performance Reference Manual

Describes alarm and performance monitoring.

LoopStar 800 Ordering Manual Describes slot assignments, engineering details and ordering information on hardware and software.

xii LPS800-UM-MAIN-04

ORGANIZATIONThe manual is organized as follows:

Chapter Description

Chapter 1: Maintenance Overview Describes the hardware structure of the LoopStar 800 subrack and the relations between slots and units.

Chapter 2: Basic Operations Provides detailed information of all the units of the LoopStar 800, including the functions, faceplate, specifications, principles and signal flow.

Chapter 3: Routine Maintenance Provides information on all the interfaces of the LoopStar 800 and related information about the cables.

Chapter 4: Loopback and Network Test Describes a complete procedure to install the units in the chassis.

Chapter 5: Replacing Hardware Describes how to connect the power supply and the ground to the LoopStar 800 chassis.

Chapter 6: Troubleshooting Explains how to install Ethernet, RS-232, fiber, DS-1, DS-3, alarm and BITS cables.

Appendix A: Regular Maintenance Recommendation

Provides recommendations of daily maintenance work and gives some tables for your reference.

Appendix B: Serious Failure Processing Flow

Recommends treatment strategy for serious failure.

Appendix C: LoopStar 800 Glossary Defines abbreviations, acronyms, and terms for the LoopStar 800 series product line.

Appendix D: LoopStar 800 Acronyms and Abbreviations

Defines acronyms and abbreviations for the LoopStar 800/1600/3600 series product line.

Appendix E: Product Support Provides information on how to contact the ADC Technical Support group.

LPS800-UM-MAIN-04 xiii

CONVENTIONSThe 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

ATTENTION

Alerts you to possible equipment damage from electrostatic discharge

CAUTION Alerts you to possible data loss, service-affecting procedures, or other similar type problems

WARNINGAlerts you that failure to take or avoid a specific action might result in hardware damage or loss of service

DANGER Alerts you that failure to take or avoid a specific action might result in personal harm

xiv LPS800-UM-MAIN-04

LPS800-UM-MAIN-04 1-1

1ChapterMAINTENANCE OVERVIEW

RUNNING ENVIRONMENT OF LOOPSTAR 800Communication 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:

Test the Power Supply of -48 V DC for the LoopStar 800.

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.

The Maximum Power Consumption is 190 W.

Ensure Equipment is Grounded.

Good grounding is the basis of equipment running reliably. For detailed grounding requirements, refer to the LoopStar 800 Installation Manual.

Requirements for Temperature and HumidityThe LoopStar 800 conforms to the environmental requirements defined in Telcordia Technologies GR-63-CORE. In addition, the LoopStar 800 conforms to the Rate of Change requirements defined in Telcordia Technologies GR-3028.

The LoopStar 800 has the following temperature and humidity specifications:

• Operating temperature: -40 to 149°F (–40 to 65°C) • Operating relative humidity: 5% to 85% • Storage temperature: –40 to 158°F (–40 to 70°C) • Storage relative humidity: less than 95%

Ensure Good Ventilation of EquipmentDuring the normal running of the LoopStar 800, 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.

Chapter 1: Maintenance Overview

1-2 LPS800-UM-MAIN-04

PRECAUTIONS OF MAINTENANCE OPERATIONSTo 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

Handling Optical Interface of OC-N Unit and Fiber Jumper ConnectorCover any unused optical interface fiber connectors on the OC-N units with dust covers.

By doing so, invisible 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.

Precautions for Loopback Operation of OC-N UnitDuring hardware loop back testing of any OC-N unit with a fiber jumper, an attenuator must be used to prevent the transmitted optical power from saturating or even damaging the optical receiving module.

Precautions for Replacing OC-N UnitsWhenever 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

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.

Precautions for Unit Electrical SafetyAny 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.

Pay attention to the impact of environmental temperatures and humidity on the storage of the backup units. Desiccant should be placed inside antistatic bags to absorb any moisture and keep the bag dry.

When the unit encapsulated in an antistatic enclosure is taken from a cold, 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.

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 The static produced by the human body can damage the sensitive components on the unit (i.e., large integrated circuits).



Precautions for Power Supply MaintenanceNever 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.

Precautions of Other Personal Safety• Keep the site area clean and dust-free. • Keep tools and equipment away from walk areas. • Avoid wearing loose apparel. • Do not attempt to lift heavy equipment without help.

Precautions of Mechanical SafetyAvoid shocks during the transportation of units which may cause damage.

Pay attention when seating or unseating any unit into the chassis. Follow the steps outlined in the LoopStar 800 Installation Manual.

Precautions of EMS System MaintenanceDo not shut down the Element Management System (EMS) when its software is working normally. Although shutting down the network management system will not interrupt the services 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 ConfigurationDo not configure services until you are well prepared. Do not groom services during peak hour. Perform it while traffic is at minimum.


2ChapterBASIC OPERATIONS

FAN AND AIR FILTER MAINTENANCEThe main task of cleaning the fan is to replace the air filter.

To ensure normal ventilation of the LoopStar 800 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.

The air filter of the LoopStar 800 is connected to the faceplate of the fan tray. Pull out the air filter together with the faceplate (seel 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.

For installation of the fan and air filter, refer to the LoopStar 800 System Installation Manual.

Figure 2-1. The Air Filter

Chapter 2: Basic Operations


PLUGGING/UNPLUGGING FIBER JUMPER

Optical units for the LoopStar 800 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.

INSERTING/REMOVING A UNITThe chassis backplane of the LoopStar 800 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.

Inserting a UnitFor the installation of front slot units and rear slot units, refer to Chapter 4, “Module Installation" and “Installing a DSn Interface Unit” sections in the LoopStar 800 Installation Manual.

For installation of PIU, refer to “Installing Power Interface Unit" in the LoopStar 3600 Installation Manual.

Removing a Unit

When removing a unit, first loosen the left and right retaining screws of the faceplate on the unit, and then pull the ejector levers at both sides of faceplate outward simultaneously until the unit is pulled out completely.

For removing DSn interface unit, refer to Chapter 4, “Installing a DSn Interface Unit” section in the LoopStar 800 Installation Manual.

WARNING When no fiber is connected, invisible laser radiation can be emitted from the optical interfaces on the optical units. Do not stare into the open interface.To avoid exposure to laser radiation, cover the optical interface with a dustproof plug when no fiber is connected.

CAUTION The static the human body generates may damage the static sensitive components on the unit. Always wear an ESD wrist strap or glove when touching a unit.

Forcibly inserting a unit in an improper position will do permanent damage to the equipment. Pull out the fiber (cable) on the faceplate of the unit and then insert/remove the unit. Never insert/remove the unit with fiber (cable) connected.



AUDIBLE ALARM CUT-OFFThe LoopStar 800 provides an audible alarm notification. If an alarm occurs, the LoopStar 800 will illuminate the alarm indicator and report the alarm to the Element Management System (EMS).

At the same time, the LoopStar 800 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.

There are two ways to cut off the audible alarm notification:

• ACO button – Depress the Alarm Cut-Off (ACO) button on the faceplate of the system status panel. If there are any new alarms reported, the LoopStar 800 will drive the central monitoring system and another audible alarm will be generated.

• OPR-ACO-ALL:::100; – This command instructs an NE to cut off the office audible alarm indications without changing the local alarm indications. This command should not have any effect on future alarms at the NE, but rather should direct the NE to provide conditioning only on those alarms that are currently active.

CHECKING SOFTWARE VERSIONThis check can be conducted for all the software versions during maintenance.

Checking Software Version by EMSWhen the EMS terminal computer is in normal connection with the NE, you can check through the EMS system whether the unit software version, FPGA software version, NE software version and BIOS version match one another.

The following is an example of how to check the NE software version:

Select the objects in the [Report–Board Information Report] window, click >>, and click Refresh to start query. Soon you will get the version information you want.

In addition, you can see the difference between the version of an NE and that of another at a glance. Similarly, you can also apply this method in other operations (e.g., to query the software versions of other units). After the query operation, you can click Save As to save the version information.

After querying the unit’s version information and NE version information, check these versions against the packing list and the attached software version table. If the entire version checked, save the version information as a text file for archive; otherwise, make a timely report. The version information in the Equipment Archive should be based on the data actually obtained through the query operation.

On the View Details tab page, you can view the manufacturing information of a unit, including full name of the unit and the unit barcode.

Checking Software Version by TL1The query method by using TL1 command is as follows:

Unit Software and FPGAIn the LoopStar 800, you can query the unit software and FPGA version information by means of the TL1 command RTRV-EQPT::SLOT-N:100; without removing the unit and viewing the label on the chip.



This command returns the following information:

Parameters Description

<AID> The equipment unit identifier. It is an access identifier from the section "EQPT" of Chapter 25 TL1 Parameters in the LoopStar 800/1600/3600 TL1 Reference Manual.

<CARDTYPE> The AID unit type. Valid values are shown in the section "CARDTYPE" of Chapter 25 TL1 Parameters in the LoopStar 800/1600/3600 TL1 Reference Manual. PROVTYPE means the logical unit type provisioned by user; ACTTYPE means the physical unit type inserted in the slot.

<INTFTYPE> The AID unit interface type. Valid values are shown in the section "INTFTYPE" of Chapter 25 TL1 Parameters in the LoopStar 800/1600/3600 TL1 Reference Manual. This parameter is optional and can be used only for the DSn processing units.

<BANDWIDTH> The available bandwidth of the unit when it is provisioned in the slot. It is displayed when the Ethernet unit, the OC-N unit or the DSn processing unit is provisioned. It is the minimum value of the slot bus bandwidth and bandwidth of the unit.

<TPSPRI> The priority of the AID unit if the unit is a working unit of a DSn (TPS) protection group. For any other units, this parameter is not available. This attribute will be used when multi-units fault in a DSn (TPS) protection group. Valid values are shown in the section "TPS_PRIORITY" of Chapter 25 TL1 Parameters in the LoopStar 800/1600/3600 TL1 Reference Manual.

<SWITCHSTATE> The switch state of the AID unit if the unit is a unit of a DSn (TPS) protection group. Valid values are shown in the section "SWITCH STATE OF OPTICAL PORT" of Chapter 25 TL1 Parameters in the LoopStar 800/1600/3600 TL1 Reference Manual.

<SN> The serial number for the equipment. Valid value is a string and is optional.

<CLEI> The CLEI code for the equipment. Valid value is a string and is optional.

<PARTNUM> Part number of the unit. Valid value is a unique 8-digit number for the unit.

<DOM> The date when the unit was manufactured and is optional.

<PCBVER> The PCB version for the equipment. Valid value is a string and is optional.

<SWVER> The NE software/platform/unit software version for the unit. Valid value is a string and is optional.

<FPGAVER> The FPGA version for the equipment. Valid value is a string and is optional.

As there are three FPGA in the common control unit, there will be three FPGA versions for the common control unit.

<EPLDVER> The EPLD version for the equipment. Valid value is a string and is optional.

<BIOSVER> The BIOS/extended BIOS version for the unit. Valid value is a string and is optional.

<MAC> The MAC address of a common control unit. Valid value is a string like 00-B0-D0-E3-4C-DE and is optional.

<PST> <PST> means the primary state of the entity. Valid values are shown in the section "PST_STATE" of Chapter 25 TL1 Parameters in the LoopStar 800/1600/3600 TL1 Reference Manual.

<SST> <SST> means the secondary state of the entity. Valid values are shown in the section "SST_STATE" of Chapter 25 TL1 Parameters in the LoopStar 800/1600/3600 TL1 Reference Manual.



For the detailed information, refer to the LoopStar 800/1600/3600 TL1 Reference Manual.

NE Software and BIOS SoftwareThe LoopStar 800 has two software running modes: NE software running mode and BIOS software running mode.

In addition to the basic BIOS, the LoopStar 800 also includes the extended BIOS. As the basic BIOS is embedded in the chip, it is difficult to upgrade, while the extended BIOS can be conveniently downloaded by means of FTP.

Normally the NE equipment works under the NE software running mode, which is the default mode. If this is not the case, check whether the NE software is lost. If it is lost, download the NE software again.

You can also use the command RTRV-EQPT as described in the previous table to query the version information.

RESETTINGThe LoopStar 800 provides two reset modes for all units: cold reset and warm reset. To reset the unit, use the command INIT-SYS:[<TID>]:<AID>:<CTAG>::<TYPE>;. The input parameters are:

Cold ResettingA cold reset reloads FPGA. It can be executed by the EMS sending a command.

To cold reset the unit by TL1 command, use the TL1 command: INIT-SYS:[<TID>]:<AID>:<CTAG>::COLD;.

Warm Resetting

A warm reset does not reload FPGA. It resets the CPU inside a unit without affecting other modules (e.g., an LPS-OC12A is performing a warm reset; the service being processed by the unit will not be interrupted).

To warm reset the unit by TL1 command, use the TL1 command: INIT-SYS:[<TID>]:<AID>:<CTAG>::WARM;.

A warm reset can be executed by the EMS sending a command. However the LPS-XO12, LPS-XO12D, LPS-XO3, LPS-XO3D, LPS-TO12D and LPS-TO3D units can be reset by depressing the RESET button on the faceplate.

Parameter Description

<AID> Valid value is SLOT-N or SLOT-ALL. SLOT-ALL means the entire system. For SWDL/SWDLALL, usually only SLOT-ALL can be used.

<TYPE> Identifies the reboot type. Valid values are:• COLD: Cold reset, reload FPGA.• WARM: Warm reset, do not reload FPGA.• DBERASE: Erase databases, then do cold reset. This value is available only when the

<AID> is active XCS unit.• SWDL: Only used for SWDL, reset unit at least one of its SW/INI/EXTBIOS/FPGA has

been downloaded. If FPGA is changed, it should do cold reset; otherwise, warm reset. <AID> is SLOT-ALL while activate the entire system. Before that you can activate a spec-ified unit using <AID>.

• SWDLALL: Only used for SWDL, reset each unit whose software has been downloaded. The services on the units will be interrupted.

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.



INSPECTING AND CLEANING THE FIBER-OPTIC CONNECTORS

OverviewIt is very important that every optical fiber connector is inspected and cleaned before mating. This chapter provides the basic procedures required to inspect and clean fiber connectors, optical adapters, optical attenuators and flanges used in fiber optic connections. Figure 2-3 and Figure 2-4 show the optical adapter and the optical fiber connector.

Figure 2-3. Optical Adapter

Figure 2-4. Optical Fiber Connector

Clean fiber optic components are required for quality connections between fiber optic equipment. Cleaning the fiber optic connections is one of the most basic and important procedures for maintaining optical systems.

Any contamination in the fiber connection can cause failure of the component or failure of the entire system. Even microscope dust particles can cause a variety of problems to optical connections.

A particle that partially or completely blocks the core generates strong back reflections which can cause instability in the laser system. Dust particles trapped between two fiber faces can scratch the glass surfaces. Even if a particle is only situated on the cladding or edge of the endface, it can cause an air gap or misalignment between the fiber cores which will significantly degrade the optical signal.

• A 1-micrometer dust particle on a single-mode core can block up to 1% of the light, which causes a loss of 0.05 dB.• A 9-micrometer speck of dust is too small to be seen without a microscope, but could completely block the fiber

core. Therefore, even though dust may not be visible, it is still present in the air and can deposit onto the connector.

In addition to dust, other types of contamination must also be cleaned off the endface. These types of contamination include:

• Oils (frequently from human hands) • Film residues (condensed from vapors in the air)

Powdery coatings (left after water or other solvents evaporate)

These types of contamination can be more difficult to remove than dust particles and can also cause damage to equipment if not removed.

Always follow the procedures carefully when cleaning fiber components. The goal is to eliminate any dust or contamination and to provide a clean environment for the fiber-optic connection. Remember that inspection, cleaning and re-inspection are critical steps which must be taken before you make any fiber-optic connection.



Protection of Optical Connectors• Optical interface units need to be transmitted and stored in reliable packaging. This is to avoid mechanical dam-

ages and electrostatic damages and to reduce vibration. • Remember to store the protective caps in an antistatic bag. • Cover the optical interfaces of the replaced units with protective caps in time. Store them in proper packages to

keep the optical interfaces clean. • Protective caps that ADC recommends (Figure 2-5).

Figure 2-5. Recommended Protective Caps

• Protective caps that ADC does not recommend (Figure 2-6).

Figure 2-6. Non-recommended Protective Caps

General Procedure

Inspecting Optical ConnectorsThis procedure provides the steps required to inspect the optical connectors.

Recommended Tools and Test Equipment• Optical power meter • Optical fiberscope with 20x magnification (a video fiberscope is recommended)

WARNING Laser is dangerous. The light is invisible to the eyes with or without laser protective glasses. Do not look into optical connectors and optical interfaces. Failure to follow this warning can cause damage to your eyes, or even blindness.

Step Action1 Complete “Inspecting Optical Connectors” on page 2-7.2 Complete “Cleaning Optical Fiber Connectors Using Cartridge Cleaners” on page 2-10 if necessary.3 Complete “Cleaning Optical Fiber Connectors Using Lens Tissue” on page 2-12 if necessary.4 Complete “Cleaning Optical Adapters Using Optical Cleaning Sticks” on page 2-13 if necessary.



Procedure

Use a fiberscope equipped with a safety device that can eliminate the optical path to the eye or a desktop video fiberscope when inspecting the optical connectors. If one is not available, turn off the lasers and disconnect both ends of the fiber before inspecting the optical connectors.

Figure 2-7. An Intact Fiber

WARNING Laser is dangerous. The light is invisible to the eyes with or without laser protective glasses. Do not look into optical connectors and optical interfaces. Failure to follow this warning can cause damage to your eyes or even blindness.

CAUTION Electrostatic discharge is hazardous to electronic equipment. Use proper handling techniques to prevent damage to electronic equipment. Failure to follow this caution can result in equipment damage and/or loss of traffic.

Step Action1 Turn off the lasers before the inspection.

Disconnect both ends of the fiber to be inspected.2 Test the optical power using a power meter.

Ensure that no laser light is present on the optical connector.3 Using a fiberscope, inspect optical fiber to check if there is any contamination or damage. Refer to the

examples shown in Figure 2-7 through Figure 2-11.• If any decontamination is detected, clean the optical connector. Refer to “Cleaning Optical Fiber Con-

nectors Using Cartridge Cleaners” on page 2-10 and “Cleaning Optical Fiber Connectors Using Lens Tissue” on page 2-12.

• If any damage is detected, replace the optical fiber or unit. – For an image of the intact fiber optic surface through a fiberscope that can be used successfully

in the equipment, see Figure 2-7.– For images of fibers through a fiberscope with imperfections that can impair the function of the

assembly, see Figure 2-8. The image on the left shows clearly a damaged fiber. Severely damaged fibers must not be used in the system equipment or permanent and severe damage to the assembly can occur. The image on the right shows a fiber that is questionable. If the output power is within an acceptable range, the fiber might not cause any damage to the assembly. However, if the output power is unstable or falls outside the acceptable range, the fiber can cause damage to the assembly and must not be used.



Figure 2-8. Damaged or Questionable FibersDamage Fiber (Burned) Questionable Fiber

The views shown do not represent the entire surface of the fiber optic. Much of the surface is the metal connector and only the 800-micron core is the actual optical fiber. For details on acceptable and unacceptable fibers, see Figure 2-9, Figure 2-10 and Figure 2-11.



Figure 2-9. An Intact Fiber

Figure 2-10. Acceptable Fibers with Imperfections

Figure 2-11. Unacceptable Fibers with Imperfections

Cleaning Optical Fiber Connectors Using Cartridge CleanersBefore performing the cleaning procedure, inspect the fiber optic surface with a fiberscope or magnifier to determine the extent to which the fiber might be damaged or contaminated. Perform the cleaning procedure only in the case that there are imperfections on the fiber optic surface. If there are no imperfections, do not conduct the cleaning procedure because the procedure itself may introduce dust, dirt, or potentially cause damage to the fiber optic.

The following procedure provides the steps required to clean the optical fiber connectors using cartridge type cleaners. There are several types of cartridge cleaners available. The following describes one type of CLETOP cassette cleaners.

PurposeThis procedure is used to clean the fiber connectors.



Recommended Tools and Test Equipment• CLETOP cassette cleaner • Optical power meter • Optical fiberscope with 20x magnification (a video fiberscope is recommended)

Procedure




Disconnect both ends of the fiber to be inspected.2 Using a power meter, to ensure that no laser light is present on the optical connector.3 Press down and hold the lever.

The shutter will slide back and expose a new cleaning area (Figure 2-12 and Figure 2-13).

Figure 2-12. CLETOP Cassette Cleaner Figure 2-13. Using the CLETOP Cleaner

Step Action4 Position the fiber tip lightly against the cleaning area so that the end face is flat on the cleaning area.5 Drag the fiber tip lightly on one cleaning area in the direction of the arrow once (Figure 2-14).

Do it again on the other cleaning area in the same direction as the first time once (Figure 2-15).

CAUTION Do not scrub the fiber against fabric or clean over the same cleaning area more than once. Otherwise, the connector can be contaminated or damaged.

6 Release the lever to close the cleaning area.7 Inspect the optical fiber and repeat the procedure if fiber is still dirty.8 Connect the optical fiber connector to the unit.9 Turn on the lasers after you finish connecting the fiber to the unit.



Cleaning Optical Fiber Connectors Using Lens TissueBefore performing the cleaning procedure, inspect the fiber optic surface with a fiberscope or magnifier to determine the extent to which the fiber might be damaged or contaminated. Perform the cleaning procedure only if there are imperfections on the fiber optic surface. If there are no imperfections, do not conduct the cleaning procedure because the procedure itself may introduce dust, dirt, or potentially cause damage to the fiber optic.

The following procedure provides the steps required to clean the fiber optic connectors using lens tissue. Only use materials specifically designed for cleaning fiber optic connectors. Refer to local site practices.

PurposeThis procedure is used to clean the fiber connectors.

Recommended Tools and Test Equipment• Optical fiberscope with 20x magnification (a video fiberscope is recommended) • Optical power meter • Clean solvent. Isoamylol is preferred, propyl can be used (alcohol or formalin is never used) • Non-woven lens tissue, lint-free wipes or fiber cleaning tissue (Non-woven lens tissue is recommended) • Special compressed gas • Special cleaning roll

Procedure

Figure 2-14. Dragging Fiber Tip Lightly on One Cleaning Area

Figure 2-15. Dragging Fiber Tip Lightly on the Other Cleaning Area





Cleaning Optical Adapters Using Optical Cleaning SticksOptical adapters must be cleaned with special cleaning tools and materials. These tools and materials are available from optical fiber cable and connector manufacturers.

The following procedure provides the steps required to clean optical adapters using optical cleaning sticks. There are several types of optical cleaning sticks and cotton swabs that can be used. Refer to local site practices.


Disconnect both ends of the fiber to be inspected.2 Using a power meter, to ensure that no laser light is present on the optical connector.3 Place a small amount of cleaning solvent on the lens tissue.4 Clean the fiber tip on the lens tissue (Figure 2-16 and Figure 2-17).

CAUTION Do not scrub the fiber against fabric or clean over the same cleaning area more than once. Failure to comply can result in connector contamination or damage the connector.

Figure 2-16. Cleaning the Fiber Tip With the Lens Tissue On the Desk

Figure 2-17. Cleaning the Fiber Tip With the Lens Tissue On the Hand

Step Action5 Repeat Step 4 several times on the areas of the lens tissue that have not been used.6 Using compressed gas, blow off the fiber tip.

– When using compressed gas, keep the injector nozzle as close as possible to the connector surface without touching it.

– When using compressed gas, first spray into the air as the initial spray of compressed air can contain some condensation or propellant. Such condensation leaves behind a filmy deposit.

– If compressed gas is not available, a clean roll can be used. 7 Inspect the optical fiber and repeat the procedures if the fiber is still dirty.8 Do not touch the fiber optic connector after cleaning.

Connect it to the optical interface unit at once. (If it is not used for the time being, put a protective cap on it.)

The lens tissue cannot be used repeatedly.

9 Turn on the lasers after you finish connecting the fiber to the unit.



PurposeThis procedure is used to clean the optical adapters.

Recommended Tools and Test Equipment• Optical fiberscope with 20x magnification (a video fiberscope is recommended) • Optical power meter • Clean solvent. Isoamylol is preferred, propyl can be used (alcohol or formalin is never used) • Special compressed gas • Optical cleaning sticks used for optical connectors or cotton swabs (medical cotton or long fiber cotton)

Procedure

Figure 2-18. Cleaning Stick for the SC and FC Optical Interface (Reference Only)

Figure 2-19. Cleaning Stick for the LC Optical Interface (Reference Only)




Disconnect both ends of the fiber to be inspected.2 Using a power meter, to ensure that no laser light is present on the optical interface.3 Select the cleaning stick with a proper diameter for a particular type of the adapter.

For the SC and FC optical interface, use the cleaning stick with a diameter of 2.5 mm; for the LC optical interface, use the cleaning stick with a diameter of 1.25 mm (Figure 2-18 and Figure 2-19).

Step Action4 Place a small amount of cleaning solvent on the optical cleaning stick.5 Place the optical cleaning stick lightly on the optical adapters so that cleaning solvent is against the fiber

tip.Hold the stick straight out from the adapter and turn the stick clockwise four to five times.

Make sure that there is direct contact between the stick tip and fiber tip (Figure 2-20).



Figure 2-20. Using a Cleaning Stick

6 Using compressed gas, blow off the fiber tip.

– When using compressed gas, keep the injector nozzle as close as possible to the connector surface without touching it.

– When using compressed gas, first spray into the air as the initial spray of compressed air can contain some condensation or propellant. Such condensation leaves behind a filmy deposit.

7 Repeat the procedure if the optical adapter is still dirty.8 Connect the fiber to the unit or put a protective cap on the interface.9 Turn on the lasers after you finish connecting the fiber to the unit.

Step Action



BIT ERROR RATE TESTINGWhen performing bit error rate tests, the testing point is the service access point (e.g., the interface of DS1/DS3/OC-3). You may select two testing methods: online or offline.

Online Testing Method

Offline Testing MethodThis is a more frequently used testing method.

Step Action1 Select a service channel in use (e.g., DS1, DS3, OC-3, etc.) and find the port corresponding to it on Digital

Distribution Frame (DDF).2 Connect one end of the testing wire to the online testing connector of that port in DDF and the other end

to the online testing interface of the tester. Then test it.

– Normally, there is no bit error within 24 hours. – For instructions on how to set the bit error tester, refer to its manual. Note that the bit error tester

must be set to online testing.

The bit error tester should be grounded properly. It is suggested that other electric appliances not be switched on/off during the testing.

Step Action1 Select one service channel (e.g., DS1, DS3, OC-3, etc.).2 Connect the transmitting and receiving port of the Bit Error Rate (BER) tester, to the transmitting and

receiving port of the interface to be tested in local Network Element (NE).

Pay attention to the corresponding relation of transmitting and receiving ports between the tester and the LoopStar 800.

3 At the terminal NE of the service, make a loopback of interfaces (e.g., hardware self-loop at DDF or make a software inner loopback by NE).

4 Set the BER tester and start testing.

– For the operations of BER tester, refer to its instructions. – There should be no bit error within 24 hours under normal conditions.



Figure 2-21 shows a block diagram of the BER testing connection.

Figure 2-21. Bit Error Rate Test

TRANSMITTER/RECEIVER OPTICAL POWER TESTING

Testing Transmitter Optical Power

The testing operation is as follows:

• To do this test, you have to keep the fiber connector clean and well connected. Also keep the ring flange of the faceplate 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 wavelength of the optical power meter should be the same as the tested optical

wavelength.

Step Action1 Set the receiving optical wavelength of the optical power meter to the same as the tested optical

wavelength.2 Connect one end of the fiber jumper to the TX interface of the optical interface unit to be tested.3 Connect the other end of the fiber jumper to the interface of the optical power meter.4 When the receiving optical power is stable, read the optical power value that is the transmitting optical

power of the optical interface unit.



Testing Receiver Optical Power

The testing operation is as follows:

• To do this test, you have to keep the fiber connector clean and well connected. Also keep the ring flange of the faceplate on the optical unit connected and clean.

• Different fiber jumpers should be used for single-mode and multi-mode optical interfaces. • The optical wavelength of the optical power meter should be the same as the tested optical

wavelength.

Step Action1 Set the receiving optical wavelength of the optical power meter to the same as the tested optical

wavelength.2 In the local NE, connect the port of the optical power meter with the fiber which pulled out from the RX port

of the optical interface to be tested.3 After the receiving optical power is stable, read the optical power which is the actual receiving optical

power of the optical interface unit.


3ChapterROUTINE MAINTENANCE

OVERVIEWPurposeThe 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 for the LoopStar 800. It offers basic methods and references that may help the user in making routine maintenance schemes.

ClassificationAccording to the maintenance periods, maintenance can be divided into the following types:

Emergency MaintenanceEmergency maintenance refers to the maintenance task executed due to equipment failure and network adjustments (i.e., the user-claimed failure, equipment damage, and line failure). Refer to Appendix B: “Serious Failure Processing Flow” on page B-1.

Daily Routine MaintenanceDaily routine maintenance refers to the maintenance which must be performed every day. Through it, you can learn the running status of the equipment at any time. If any faults occur, correct them.

During routine maintenance, make detailed records on the specific physical position of the fault, as well as phenomenon and process of the fault. Perform timely maintenance and troubleshooting. Refer to Appendix A: “Regular Maintenance Recommendation” on page A-1.

Periodical Routine MaintenancePeriodical routine maintenance refers to the maintenance performed periodically. Through it, you can learn the long-term running status of the equipment.

Periodical routine maintenance falls into quarterly maintenance and yearly maintenance. Refer to Appendix A: “Regular Maintenance Recommendation” on page A-1.

Chapter 3: Routine Maintenance


ROUTINE MAINTENANCE ITEMSTable 3-1 shows the typical routine maintenance items.

Table 3-1. Typical Routine Maintenance Item

Audible Alarm NotificationAn audible alarm can easily catch the attention of the maintenance personnel than other types of equipment alarms, so the alarm channel must be kept unblocked during routine maintenance.

As the audible alarm of the LoopStar 800 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 IndicatorsThe LED alarm indicators 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.

The LEDs located on the system status panel will warn of any alarms present on the system.

The alarm indicators on the system status panel are shown in Figure 3-1.

Maintenance Test Item Period

Audible alarm system Daily

Equipment and unit alarm indicator Daily

Temperature Daily

NE and unit status Daily

Alarms Daily

Performance event monitoring Daily

Protection switching Daily

Querying NE time Daily

Checking the air filter periodically Monthly

Testing bit error rate Monthly

Modifying the login password of EMS users periodically Monthly

Backup and dump of EMS system database Monthly



Figure 3-1. System Status Panel

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

Table 3-2. System Status Indicators

IndicatorsColor/Flashing

Status Description

CRIT On (red) Critical alarm exists.

Off No critical alarm.

MAJ On (red) Major alarm exists.

Off No major alarm.

MIN On (yellow) Minor alarm exists.

Off No minor alarm.

FAN On (red) Fan failure.

Off Fan is normal.

PWRA On (green) Power supply of PIU A is working normally.

On (red) Power supply of PIU A is failure (e.g., under-voltage, PIU A hardware failure or PIU A power supply has been cut off).

Off All power supply of NE has been cut off.

PWRB On (green) Power supply of PIU B is working normally.

On (red) Power supply of PIU B failed (e.g., under-voltage, PIU B hardware failure or PIU B power supply has been cut off).

Off All power supply of NE has been cut off.



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

Unit Alarm IndicatorsThe LED alarm indicators on the unit can tell the maintenance personnel about the unit running status and part of the 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.

The specific meaning of all the unit indicators is shown in Table 3-3 through Table 3-10.

Table 3-3. XO/TO Unit Indicators

ACO On (green) Current audible/visual alarm has been closed. If alarm is not cleared, LED will still light green until the next new audible/visual alarm occurs.

Off Current audible/visual alarm has not been closed (alarm LED is on). There are no alarms or no power supply.

Indicators State Description

STAT On (green) Normal active state.

On (red) Major or critical equipment alarm on the unit.

On (yellow) Minor equipment alarm or temperature alarm on the unit.

Blinking (red) Mismatch between user-defined unit and physical unit.

Off Inactive state/In OOS-MA state/In unit uncreated state.

ACT On (green) The unit is in working status.

Off The unit is in standby status.

Blinking (green) 100 ms on and 100 ms off.

XO unit backups database.

PROG On (green) Unit software is initializing the hardware.

Blinking quickly (green)

100 ms on and 100 ms off.

Writing FLASH (i.e., loading software).

Blinking slowly (green)


BIOS booting/Loading FPGA/Loading unit software.

On (red) Memory check failed/Loading unit software failed/FPGA file was lost/Unit software was lost.

Blinking (red) 100 ms on and 100 ms off.

BOOTROM check failed.

Off Power off/CPU failure/Loading and running unit software was successful.

IndicatorsColor/Flashing

Status Description



Table 3-4. OCN Unit Indicators

SYNC On (green) Clock synchronized successfully/Non-configured and in free-run mode.

Blinking (green) In the synchronization processing/In the fast-tracing mode.

On (red) Configured synchronization clock and in free-run mode.

On (yellow) Holdover mode.

SRV-N On (green) The corresponding optical port is normal and no service alarm is generated.

On (red) The corresponding optical port has critical or major alarm.

On (yellow) The corresponding optical port has minor alarm.

Off The corresponding optical port has no service or is in OOS-MA state.






Off Inactive state/In OOS-MA state /In unit uncreated state.

SRV-N On (green) The corresponding optical port is normal and no service alarm is generated.

On (red) The corresponding optical port has critical or major alarm.

On (yellow) The corresponding optical port has minor alarm.

Off The corresponding optical port has no service, or is in OOS-MA state.















Table 3-5. LPS-ELS4 Unit Indicators










Writing FLASH (i.e, loading software).







Off Power off/CPU failure/Loading and running unit software is successful.

SRV On (green) In-service state and no other traffic alarm.

On (red) In-service state and having critical/major alarm.

On (yellow) In-service state and having minor alarm.

Off Out of service.

LINK/ACT1 LINK/ACT2

On (green) Successfully link the service of the corresponding optical interface.

LINK/ACT3 LINK/ACT4

Blinking (orange) The corresponding optical interface is transceiving data.

Off The corresponding optical interface disabled/power off/unsuccessfully link the service.



Table 3-6. LPS-EFS8 Unit Indicators





















Off Out of service.

LINK On (green) Successfully link the service of the corresponding FE electrical interface.

Off The corresponding FE electrical interface disabled/power off/unsuccessfully link the service.

ACT Blinking (orange) The corresponding FE electrical interface is transceiving data.

Off The corresponding FE electrical interface is idle.



Table 3-7. LPS-EGT2 Unit Indicators





















Off Out of service.

ACTY-1 Blinking (orange) The corresponding GE optical interface is transceiving data.

ACTY-2 Off The corresponding GE optical interface is idle.

LINK-1 On (green) Successfully link the service of the corresponding GE optical interface.

LINK-2 Off The corresponding GE optical interface disabled/power off/unsuccessfully link the service.



Table 3-8. LPS-EGS4 Unit Indicators



On (red) Unit hardware failure.

On (yellow) Minor equipment alarms or temperature alarms occurs on the unit.

Blinking (red) Mismatch between the user-defined unit and the physical unit.

Off Inactive state/In the OOS-MA state/In unit uncreated state.



100ms on and 100ms off.

Writing FLASH.



BIOS booting/loading FPGA/loading unit software.

On (red) Memory check failed/loading unit software failed/The FPGA file is lost/The unit software is lost.

Blinking (red) 100ms on and 100ms off The self-check of BOOTROM fails.

Off Loading and running unit software is successful.

ACT On (green) If Then

Ethernet TPS protection mode... the unit is in the working mode.

Non- Ethernet TPS protection mode...

service is configured.

Off If Then

Ethernet TPS protection mode... in the protection mode.

Non- Ethernet TPS protection mode...

service is not configured.


Blinking (red) 100ms on and 100ms off Optical module mismatched.



Off Out of service.

LINK/ACTY1 On (green) Successfully link the service of the corresponding GE optical interface.

LINK/ACTY2 LINK/ACTY3 LINK/ACTY4

Off The corresponding GE optical interface disabled/Unsuccessfully link the service.

Blinking (green) The corresponding GE optical interface is transceiving data.



Table 3-9. LPS-ET4GS Unit Indicators


















GE-ACT Blinking (orange) The corresponding GE optical interface is transceiving data.

Off The corresponding GE optical interface is idle.

GE-LINK On (green) Successfully link the service of the corresponding GE optical interface.

Off The corresponding GE optical interface disabled/power off/unsuccessfully link the service.



Table 3-10. DSn Unit Indicators




On (yellow) Minor equipment alarms or temperature alarms occurs on the unit.

Blinking (red) Mismatch between the user-defined unit and the physical unit/Mismatch between DSn processing unit and DSn interface unit.

Off Inactive state/In the OOS-MA state/In unit uncreated state.








On (red) Memory check failed/Loading unit software failed/The FPGA file is lost/The unit software is lost.

Blinking (red) 100ms on and 100ms off.



ACT On (green) If Then

DSn protection mode... the unit is in the working mode.

Non- DSn protection mode... service is configured.

Off If Then

DSn protection mode... in the protection mode.

Non- DSn protection mode... service is not configured.

SRV On (green) The corresponding DSn port is normal and no service alarm is generated.

On (red) The corresponding DSn port has critical or major alarm.

On (yellow) The corresponding DSn port has minor or remote alarm.

Off The corresponding DSn port has no service, or is in OOS-MA state.

TAP1TAP2

On (green) The test access port is working.

Off The test access port is not working.



TemperatureTable 3-11 shows the ambient temperature requirements for proper equipment operation.

Table 3-11. Ambient Temperature Requirements for Equipment Operation

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 faceplate 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 StatusAll Network Elements (NEs) in the management domain should be logged in normally through the transmission Element Management System (EMS).

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.

AlarmsThe LoopStar 800 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 9 in the LoopStar 800/1600/3600 User Operation Manual.

It is recommended to browse the alarms once a day.

Performance EventsThe LoopStar 800 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.

Performance Monitoring ConfigurationPerformance monitoring configuration allows provisioning of monitoring time, monitored objects and threshold settings.

Monitoring Time ConfigurationIn TL1, you can set the start time (the fixed time is 24 hours). In the LoopStar EMS, you can set the time to either 15 minutes or 24 hours.

Operational Condition Temperature (ºC)

Long-term working condition –40 to 149°F (–40 to 65°C)

Short-term working condition –40 to 158°F (–40 to 70°C)



Monitored Object SelectionIn TL1, all performance events are monitored by the system by default, while in the LoopStar EMS, you can select the objects to be monitored.

Threshold ProvisioningBoth TL1 and the LoopStar 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.

Performance Data ViewingIt is indispensable to view such NE performance data as bit error, pointer justification. In routine maintenance, a variety of latent failures of the equipment operation can be detected.

Viewing Performance DataBit 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 (i.e., service interruption in the future).

Viewing Performance Threshold-crossing DataOne 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 EMS 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 to Chapter 6 in the LoopStar 800/1600/3600 User Operation Manual.

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

Protection SwitchingIn view of the importance of protection switching, the checking of protection switching alarm will be listed independently. In routine maintenance, the protection switching alarms WKSWPR and WKSWBK must be checked periodically through the EMS 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 EMS system once a day.



Querying NE TimeThe NE time should be kept consistent with the current computer time and the actual time. Otherwise, the EMS system will display incorrect alarm generation and termination times which could result in misleading alarm information.

Checking and Replacing Air Filter PeriodicallyGood 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. It results 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 every three months.

Testing Bit Error RateBit 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), you can test this channel 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, temporarily disconnect the service protection channel. This action is to perform bit error test when the traffic is comparatively light. Then, the test result may tell you the quality of the service channel between the two stations.

Approach 3: If both the above two approaches are not available, monitor the quality of the service channel through the performance and alarms. These alarms are reported by the EMS system.

For the service channel selected for BER test, operate as following:

• Perform terminal loopback at the corresponding service channel on the electrical interface unit at the remote NE.

• Perform BER testing at the corresponding service channel at the local NE. The test time is 24 hours and the bit error rate in the test result should be zero.

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, do not turn on/off other electric appliances during the test.

• When performing loopback to the service channel of the electrical interface unit, first consider to per-form hardware loopback on the Digital Distribution Frame (DDF) outside the equipment. If the test result is abnormal, perform the loopback at the DSn port of the chassis.

• If the fault remains after the hardware loopback, perform loopback to the service channel of the electri-cal interface unit. Remember to clear the loopback setting at the electrical interface unit after the test.



It is recommended to perform bit error test once a month as part of routine maintenance.

For detailed operation of terminal loopback, refer to Chapter 4 in this manual.

Steps for creating a terminal loopback: • Set the port to maintenance state with TL1 command: RMV-<OCN/EC1/T3/T1/

STS_PATH>:[<TID>]:<AID>:<CTAG>;.• Create the loopback with TL1 command: OPR-LPBK-<OCN/EC1/T3/T1/

STS_PATH>:[<TID>]:<AID>:<CTAG>::,,,<LPBKTYPE>;. Steps for clearing the terminal loopback:

• Clear the loopback: RLS-LPBK-<OCN/EC1/T3/T1/STS_PATH>:[<TID>]:<AID>:<CTAG>;.• Clear the maintenance state: RST-<OCN/EC1/T3/T1/STS_PATH>:[<TID>]:<AID>:<CTAG>;.


4ChapterLOOPBACK AND NETWORK TEST

LOOPBACKLoopback are one of the most popular test methods used to isolate faults in the network. The LoopStar 800 provides perfect loopback modes, including facility loopback, terminal loopback, path loopback, FEAC loopback and FAC2 loopback.

Facility LoopbackThe OC-N interface units, DSn processing units and Ethernet units support terminal loopback.

After creating facility loopback 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.

• Before initiating the loopback, the corresponding port state should be MT. • Before changing one loopback mode to another mode, the former loopback should be canceled firstly

and then change to another loopback mode.

The facility loopback, terminal loopback, path loopback, FEAC loopback and FAC2 loopback are also called software loopback, because they are usually implemented with WebLCT, LoopStar EMS or TL1 command. Correspondingly, hardware loopback usually inserts a loopback fiber or cable into the optical or electrical ports. You can loopback the optical or electrical signals outside the LoopStar 800 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.

OC-N Interface Unit Inside the optical interface unit (OC3 or OC12), loop back the signals from the optical receiving module to the optical transmitting module.

There are two loopback modes for the signals: loopback in path (e.g., STS1, STS3c, STS6c, STS9c or STS12c) and loopback in port (loop back all paths that access signals).

DSn Processing Unit Inside the DSn processing unit (LPS-PLT3, LPS-PQT3A, LPS-PQT3B, LPS-PDLTM, LPS-PDM3, LPS-PQM3, OC-N DSn Cross-connect unit LPS-PDT1 or LPS-PLT1), send the signal from the receiving port back to the corresponding transmitting port of the signal.

EGT2 Unit (MAC layer)

Used to check if the Ethernet unit and Ethernet unit cross-connect unit are well interconnected. Also, it is used to check if the MAC layer is normal.

Chapter 4: Loopback and Network Test


Terminal LoopbackThe OC-N interface units, DSn processing units and Ethernet units support terminal loopback.

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.

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.

OC-N Interface Unit Inside the optical interface unit (OC3 or OC12), send the signal from the cross-connect OC-N DSn Cross-connect unit unit back to the cross-connect unit.

There are two loopback modes for the signals: individual path loopback (e.g., STS1, STS3c, STS6c, STS9c or STS12c) and loopback in port.

DSn Processing Unit Inside the DSn processing unit (LPS-PLT3, LPS-PQT3A, LPS-PQT3B, LPS-PDLTM, LPS-PDM3, LPS-PQM3, OC-N DSn Cross-connect unit LPS-PDT1 or LPS-PLT1), send the signal from the cross-connect unit back to the cross-connect unit. The signal here is of DSn level.

ELS4/EFS8/EGT2/EGS4/ET4GS Unit (PHY layer)

This loopback does not cause loss of packet, Ethernet unit Cross-connect so it is used to check if the cable or fiber is damaged or if the optical power is at the critical point.

Also, it is used to check if the PHY layer is normal.

Note to enable the port.EFS8/ELS4/ET4GS/EGT 2 Unit (MAC layer)

Used to check if the Ethernet unit and Ethernet unit cross-connect unit are well interconnected.



Path LoopbackPath loopback (also called cross-connection loopback) can only be conducted inside the cross-connect unit.

FEAC LoopbackFEAC loopback is available when you are limited and cannot perform any operations on a remote NE (e.g., two equipments from different vendors are interconnected). Equipment from vendor A is on the left side of the figure, and that from vendor B is on the right side of the figure. Vendor A may want to know the signal condition of the equipment from vendor B, but vendor A cannot perform any operations on the equipment from vendor B.

FEAC loopback is used to send FEAC loopback codes from the near end to the far end for a remote loopback. So vendor A sends the remote loopback command and can see the signal conditions of the equipment from vendor B. If vendor A sends the FEAC loopback command at the DSn port in NE1, vendor A can see the signal conditions the equipment from vendor B in NE2.

As the LoopStar 800 only provides a higher order cross-connect unit currently, STS-1 is the lowest service level currently available for loopback.

XO/TO Unit Inside the cross-connect unit, send the service of cross-connect unit from the DSn processing unit, OC-N interface unit or the STS path of the Ethernet unit to loop back according to the service level.

FEAC loopback is supported by the transmux service processing/ protection unit LPS-PDM3 and LPS-PQM3.

DS3FEAC Loopback It means the Far End Alarm and Control (FEAC) loopback provisioning for DS3 port. The DS3FEAC cannot be used when the value of Loopback Enable is DISABLE.

DS1FEAC Loopback It means the FEAC loopback provisioning for DS1 port.



FAC2 LoopbackFAC2 loopback provides loopback response function for DS1 remote loopback from SONET side. Only the LPS-PDT1, LPS-PDLTM and LPS-PLT1 units support FAC2 loopback.

IDENTIFYING NETWORK FAULTSFacility loopback, terminal loopback and path loopback are usually used together in network fault localization. When network fault and service interruption occur, performing these three types 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 LoopStar 800, the signal can be traced along the service trail and the fault located. The test steps can be as follows:

LPS-PDT1/LPS-PLT1/LPS-PDLTM Unit

When some faults exist in the network connecting PDH Equipment B and A, perform the FAC2 loopback on Equipment B. The SONET NE1 responds to the loopback and returns the signal.

If the signal detected by Equipment B is good, it indicates there is nothing wrong with the SONET network and the fault lies between SONET NE1 and Equipment A.

If the signal detected by Equipment B is bad, it indicates some faults lie in the SONET network.

Before performing the FAC2 loopback, issue the TL1 command for loopback response on SONET NE1: ALW-LPBK-T1. After the test, there are two methods to release the loopback:

• Issue the command of releasing the loop-back on Equipment B.

• Issue the TL1 command on NE1: RLS-LPBK-T1.

The step sequence of the test depends on the specific network topology structure and service routes. You can use the software loopback described above, electrical cable or optical fiber to loopback DSn or OC-N directly outside the LoopStar 800.

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.



Performing a Facility Loopback on NE-A’s DSn Processing UnitCreate 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

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

Testing the Facility Loopback

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.

Step Action1 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 pair of ports. Adjust the test set accordingly.

2 Use TL1 or EMS to create the facility loopback on the port being tested.• Set the port to maintenance state with TL1 command:

RMV-<OCN/EC1/T3/T1/STS_PATH>:[<TID>]:<AID>:<CTAG>;.• Create the loopback with TL1 command:

OPR-LPBK-<OCN/EC1/T3/T1/STS_PATH>:[<TID>]:<AID>:<CTAG>::,,,<LPBKTYPE>;. 3 Proceed to “Testing the Facility Loopback” below.

Step Action1 Run the electrical BER tester.

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.



Checking the DSn Cable

Testing the DSn Processing Unit

Testing the DSn Interface Unit

3 If the test result is normal:• Clear the loopback with TL1 command: RLS-LPBK-<OCN/T1/T3/EC1/STS_PATH>;.• Proceed to “Performing a Path Loopback on the NE-A” on page 4-7.

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 Digital Distribution Frame (DDF)).

4 Proceed to “Checking the DSn Cable” below.

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

• Clear the loopback with TL1 command: RLS-LPBK-<OCN/T1/T3/EC1/STS_PATH>;.• Proceed to “Performing a Path Loopback on the NE-A” on page 4-7.

If the bit errors remain, the problem may be with the DSn processing unit or the DSn interface unit. 4 Proceed to “Testing the DSn Processing Unit” below.

Step Action1 Replace the DSn processing unit. See Chapter 5: “Replacing Hardware” on page 5-1 for details.2 Resend the test service to the loopback circuit.3 If the test result is normal, it indicates the problem is with the replaced DSn processing unit.

• Replace the faulty unit.• Clear the loopback with TL1 command: RLS-LPBK-<OCN/T1/T3/EC1/STS_PATH>;.• Contact ADC technical support center for unit replacement and technical support.• Proceed to “Performing a Path Loopback on the NE-A” on page 4-7.

If bit errors occur, the problem may be with the DSn interface unit.4 Proceed to “Testing the DSn Interface Unit” below.

Step Action1 Replace the DSn processing unit. See Chapter 5: “Replacing Hardware” on page 5-1 for details.2 Resend the test service to the loopback circuit.3 If the test result is normal, it indicates the problem is with the replaced DSn interface unit.


4 If bit errors occur, contact ADC technical support center or repeat the above steps.

Step Action



Performing a Path Loopback on the NE-ACreate 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

Creating a Path Loopback on the NE-A

Testing the Path Loopback


• If you just complete the steps of “Performing a Facility Loopback on NE-A’s DSn Processing Unit” on page 4-5, 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 Trans-mit (Tx) and Receive (Rx) terminals connect to the same pair of ports. Adjust the test set accordingly.

2 Use TL1 or EMS to create the path loopback on the port being tested. • Set the port to maintenance state with TL1 command:

RMV-<OCN/EC1/T3/T1/STS_PATH>:[<TID>]:<AID>:<CTAG>;. • Create the loopback with TL1 command:

OPR-LPBK-<OCN/EC1/T3/T1/STS_PATH>:[<TID>]:<AID>:<CTAG>::,,,<LPBKTYPE>;.3 Proceed to “Testing the Path Loopback” below.


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:

• Clear the loopback with TL1 command: RLS-LPBK-<OCN/T1/T3/EC1/STS_PATH>;. • Proceed to “Performing a Terminal Loopback on NE-A’s Eastbound OC-N Interface Unit” on page 4-8.

If bit errors occur, the problem may be with the cross-connect unit.4 Proceed to “Testing the Standby Cross-Connect Unit” on page 4-8.



Testing the Standby Cross-Connect Unit

Retesting the Original Active Cross-Connect Unit

Performing a Terminal Loopback on NE-A’s Eastbound OC-N Interface UnitCreate a terminal loopback for the eastbound 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 Eastbound OC-N Interface Unit

Step Action1 Manually switch the service from the active cross-connect unit to the standby cross-connect unit through

TL1 or EMS.2 The TL1 command is as follows:

SW-DX-EQPT:[<TID>]:<EQPT>:<CTAG>::<HSCSWMODE>;. 3 Run the electrical BER tester and send the test service to the loopback circuit.4 Observe the service received by the electrical BER tester and check for errors or other information. If the

test result is normal:a. The fault is at the original cross-connect unit.b. Clear the loopback with TL1 command: RLS-LPBK-<OCN/T1/T3/EC1/STS_PATH>;.c. Proceed to “Retesting the Original Active Cross-Connect Unit” below.

5 If bit errors occur, the problem may be caused by other faults. Contact ADC technical support center.

Step Action1 Manually switch the service from the active cross-connect unit to the standby cross-connect unit through

TL1 or EMS.2 The TL1 command is as follows:

SW-DX-EQPT:[<TID>]:<EQPT>:<CTAG>::<HSCSWMODE>;.3 Run the electrical BER tester and send the test service to the loopback circuit.4 If the test result is abnormal, it indicates the fault is with the original cross-connect unit.

• Replace the faulty unit.• Clear the loopback with TL1 command: RLS-LPBK-<OCN/T1/T3/EC1/STS_PATH>;.• Contact ADC technical support center for unit replacement and technical support.• Proceed to “Performing a Terminal Loopback on NE-A’s Eastbound OC-N Interface Unit” on page 4-8.

5 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 or contacting ADC technical support center.

• Clear the loopback with TL1 command: RLS-LPBK-<OCN/T1/T3/EC1/STS_PATH>;.• Proceed to “Performing a Terminal Loopback on NE-A’s Eastbound OC-N Interface Unit” on page 4-8.



Creating a Terminal Loopback on NE-A’s Eastbound OC-N Interface Unit

Testing the Terminal Loopback

Testing the OC-N Interface Unit




2 Use TL1 or EMS to create the terminal loopback on the port being tested.• Set the port to maintenance state with TL1 command:


OPR-LPBK-<OCN/EC1/T3/T1/STS_PATH>:[<TID>]:<AID>:<CTAG>::,,,<LPBKTYPE>;. 3 Proceed to “Testing the Terminal Loopback” below.



• Clear the loopback with TL1 command RLS-LPBK-<OCN/T1/T3/EC1/STS_PATH>;.• Proceed to “Performing a Facility Loopback on NE-B’s Westbound OC-N Interface Unit” on page 4-10.

If bit errors occur, the problem may be with the cross-connect unit.4 Proceed to “Testing the OC-N Interface Unit” below.

Step Action1 Replace the OC-N interface unit. See Chapter 5: “Replacing Hardware” on page 5-1 for details.2 Resend the test service to the loopback circuit.3 If the test result is normal, it indicates the problem is with the replaced OC-N interface unit. Then:

• Replace the faulty unit.• Clear the loopback with TL1 command: RLS-LPBK-<OCN/T1/T3/EC1/STS_PATH>;.• Contact ADC technical support center for unit replacement and technical support.• Proceed to “Performing a Facility Loopback on NE-B’s Westbound OC-N Interface Unit” on page 4-10.




Performing a Facility Loopback on NE-B’s Westbound OC-N Interface UnitCreate a facility loopback on the westbound OC-N 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 blocked.

Figure 4-4. Perform a Facility Loopback on NE-B’s Westbound OC-N Interface Unit

Creating a Facility Loopback on NE-B’s Westbound OC-N Interface Unit





2 Use TL1 or EMS to create the facility loopback on the port being tested. • Set the port to maintenance state with TL1 command:





• Clear the loopback with TL1 command: RLS-LPBK-<OCN/T1/T3/EC1/STS_PATH>;. • Proceed to “Performing a Facility Loopback on NE-B’s Westbound OC-N Interface Unit” on page 4-10.

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.

4 Proceed to “Checking the Connection of Optical Fiber” on page 4-11.



Checking the Connection of Optical Fiber


Performing a Terminal Loopback on NE-B’s Eastbound OC-N Interface UnitCreate 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 Eastbound OC-N Interface Unit

Step Action1 Change the optical fiber connection with a standby optical connection.2 Resend the test service to the loopback circuit.3 If the test result is normal:

• Change to the original optical connection.• Clear the loopback with TL1 command: RLS-LPBK-<OCN/T1/T3/EC1/STS_PATH>;. • Proceed to “Performing a Facility Loopback on NE-B’s Westbound OC-N Interface Unit” on page 4-10.

If the bit errors remain, the problem may be with the OC-N interface unit.4 Proceed to “Testing the OC-N Interface Unit” below.

Step Action1 Replace the OC-N interface unit. See Chapter 5: “Replacing Hardware” on page 5-1 for details.2 Resend the test service to the loopback circuit.3 If the test result is normal, it indicates the problem is with the replaced OC-N interface unit.

• Replace the faulty unit.• Clear the loopback with TL1 command: RLS-LPBK-<OCN/T1/T3/EC1/STS_PATH>;.• Contact ADC technical support center for unit replacement and technical support.• Proceed to “Performing a Facility Loopback on NE-B’s Westbound OC-N Interface Unit” on page 4-10.

4 If bit errors occur, contact ADC technical support center.



Creating a Terminal Loopback on NE-B’s Eastbound OC-N Interface Unit




• If you just complete the steps of “Performing a Facility Loopback on NE-B’s Westbound OC-N Inter-face Unit” on page 4-10, keep the connection of the electrical BER tester and the DSn processing unit unchanged.




OPR-LPBK-<OCN/EC1/T3/T1/STS_PATH>:[<TID>]:<AID>:<CTAG>::,,,<LPBKTYPE>;. 3 Proceed to “Testing the Terminal Loopback” below.



• Clear the loopback with TL1 command: RLS-LPBK-<OCN/T1/T3/EC1/STS_PATH>;. • Proceed to “Performing a Facility Loopback on NE-C’s Westbound OC-N Interface Unit” on page 4-13.

If bit errors are found, the problem may be with the OC-N interface unit or a faulty cross-connect unit.4 Proceed to “Testing the OC-N Interface Unit” below.


• Replace the faulty unit.• Clear the loopback with TL1 command: RLS-LPBK-<OCN/T1/T3/EC1/STS_PATH>;.• Contact ADC technical support center for unit replacement and technical support.• Proceed to “Performing a Facility Loopback on NE-C’s Westbound OC-N Interface Unit” on page 4-13.

4 If the bit errors remain, the problem may be with the cross-connect unit of NE-B. Test the unit according to “Performing a Path Loopback on the NE-A” on page 4-7.



Performing a Facility Loopback on NE-C’s Westbound OC-N Interface UnitCreate a facility loopback to the westbound OC-N 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 Westbound OC-N Interface Unit

Creating a Facility Loopback on NE-C’s Westbound OC-N Interface Unit



• If you just complete the steps of “Performing a Terminal Loopback on NE-B’s Eastbound OC-N Inter-face Unit” on page 4-11, keep the connection of the electrical BER tester and the DSn processing unit unchanged.



RMV-<OCN/EC1/T3/T1/STS_PATH>:[<TID>]:<AID>:<CTAG>;. • Create the loopback with TL1:




• Clear the loopback with TL1 command: RLS-LPBK-<OCN/T1/T3/EC1/STS_PATH>;. • Proceed to “Performing a Path Loopback on the NE-C” on page 4-14.

If bit errors are found, the problem may be with the OC-N interface unit or the optical fiber connection between NE-C and NE-B.

4 Proceed to “Checking the Connection of Optical Fiber” on page 4-14.



Checking the Connection of Optical Fiber


Performing a Path Loopback on the NE-CCreate 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

Step Action1 Change the optical fiber connection with a standby optical connection.2 Resend the test service to the loopback circuit.3 If the test result is normal:

• Change to another optical connection.• Clear the loopback with TL1 command: RLS-LPBK-<OCN/T1/T3/EC1/STS_PATH>;. • Proceed to “Performing a Path Loopback on the NE-C” on page 4-14.

If the bit errors remain, the problem may be with the OC-N interface unit.4 Proceed to “Testing the OC-N Interface Unit” below.


• Replace the faulty unit.• Clear the loopback with TL1 command: RLS-LPBK-<OCN/T1/T3/EC1/STS_PATH>;.• Contact ADC technical support center for unit replacement and technical support.• Proceed to “Performing a Path Loopback on the NE-C” on page 4-14.




Creating a Path Loopback on the NE-C

Testing the Path Loopback

Testing the Standby Cross-Connect Unit


• If you just complete the steps of “Performing a Facility Loopback on NE-C’s Westbound OC-N Inter-face Unit” on page 4-13, 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. • Set the port to maintenance state with TL1 command:


OPR-LPBK-<OCN/EC1/T3/T1/STS_PATH>:[<TID>]:<AID>:<CTAG>::,,,<LPBKTYPE>;.3 Proceed to “Testing the Path Loopback” below.



• Clear the loopback with TL1 command: RLS-LPBK-<OCN/T1/T3/EC1/STS_PATH>;.• Proceed to “Performing a Terminal Loopback on NE-C’s DSn Processing Unit” on page 4-16.

If bit errors occur, the problem may be with the cross-connect unit.4 Proceed to “Testing the Standby Cross-Connect Unit”.

Step Action1 Switch the service from the active cross-connect unit to the standby cross-connect unit manually through

TL1 or EMS. The TL1 command is as follows:

SW-DX-EQPT:[<TID>]:<EQPT>:<CTAG>::<HSCSWMODE>;. 2 Run the electrical BER tester.


• The fault is caused by the original cross-connect unit.• Clear the loopback with TL1 command: RLS-LPBK-<OCN/T1/T3/EC1/STS_PATH>;. • Proceed to “Retesting the Original Cross-Connect Unit” on page 4-16.

5 If bit errors are found, the problem may be caused by other faults. Contact ADC technical support center.



Retesting the Original Cross-Connect Unit

Performing a Terminal Loopback on NE-C’s DSn Processing UnitCreate 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

Creating a Terminal Loopback on NE-C’s DSn Processing Unit

Step Action1 Manually switch the service back to the original active cross-connect unit through TL1 or EMS. The TL1

command is as follows:

SW-DX-EQPT:[<TID>]:<EQPT>:<CTAG>::<HSCSWMODE>;2 Run the electrical BER tester.

Send the test service to the loopback circuit.3 If the test result is abnormal, it indicates the fault is with the original cross-connect unit.

• Replace the faulty unit.• Clear the loopback with TL1 command: RLS-LPBK-<OCN/T1/T3/EC1/STS_PATH>;. • Contact ADC technical support center for unit replacement and technical support• Proceed to “Performing a Terminal Loopback on NE-C’s DSn Processing Unit” below.

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.

• Clear the loopback with TL1 command: RLS-LPBK-<OCN/T1/T3/EC1/STS_PATH>;. • Proceed to “Performing a Terminal Loopback on NE-C’s DSn Processing Unit” below.


• If you just complete the step of “Performing a Path Loopback on the NE-C” on page 4-14, keep the connection of the electrical BER tester and the DSn processing unit unchanged.


2 Use TL1 or EMS to create the terminal loopback on the port being tested. • Set the port to maintenance state with TL1 command:


OPR-LPBK-<OCN/EC1/T3/T1/STS_PATH>:[<TID>]:<AID>:<CTAG>::,,,<LPBKTYPE>;.3 Proceed to “Testing the Terminal Loopback” on page 4-17.





Performing a Facility Loopback on NE-C’s DSn Processing UnitCreate 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.

Figure 4-9. Perform a Facility Loopback on NE-C’s DSn Processing Unit



• Clear the loopback with TL1 command: RLS-LPBK-<OCN/T1/T3/EC1/STS_PATH>;. • Proceed to “Performing a Facility Loopback on NE-C’s DSn Processing Unit” below.

If bit errors are found, the problem may be with the DSn processing unit.4 Proceed to “Testing the DSn Processing Unit” below.


• Replace the faulty unit.• Clear the loopback with TL1 command: RLS-LPBK-<OCN/T1/T3/EC1/STS_PATH>;.• Contact ADC technical support center for unit replacement and technical support.• Proceed to “Performing a Facility Loopback on NE-C’s DSn Processing Unit” below.


This test can be performed at the near end NE-C only.



Creating a Facility Loopback on NE-C’s DSn Processing Unit


Checking the DSn Cable

Step Action1 Connect an electrical BER tester to the port to be tested. 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 pair of ports. Adjust the test set accordingly.



OPR-LPBK-<OCN/EC1/T3/T1/STS_PATH>:[<TID>]:<AID>:<CTAG>::,,,<LPBKTYPE>;.3 Proceed to “Testing the Facility Loopback” below.


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 clear the loopback with TL1 command:

RLS-LPBK-<OCN/T1/T3/EC1/STS_PATH>;. 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.

4 Proceed to “Checking the DSn Cable” below.

Step Action1 Replace the cable from the DSn interface unit to the electrical BER tester.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.

• Clear the loopback with TL1 command: RLS-LPBK-<OCN/T1/T3/EC1/STS_PATH>;.

So far a complete DSn service trail has passed a series loopback tests and can be loaded with actual services.

If the bit errors remain, the problem may be with the DSn processing unit or the DSn interface unit.4 Proceed to the “Testing the DSn Processing Unit” on page 4-19.




Testing the DSn Interface Unit

Step Action1 Replace the DSn processing unit. See Chapter 5: “Replacing Hardware” on page 5-1 for details.2 Resend the test service to the loopback circuit.3 If the test result is normal, it indicates the problem is with the replaced DSn processing unit.

• Replace the faulty unit.• Clear the loopback with TL1 command: RLS-LPBK-<OCN/T1/T3/EC1/STS_PATH>;.• Contact ADC technical support center for unit replacement and technical support.

So far a complete DSn service trail has passed a series loopback tests and can be loaded with actual services.

If bit errors occur, the problem may be with the DSn interface unit.4 Proceed to “Testing the DSn Interface Unit” below.

Step Action1 Replace the DSn processing unit. See Chapter 5: “Replacing Hardware” on page 5-1 for details.2 Resend the test service to the loopback circuit.3 If the test result is normal, it indicates the problem is with the replaced DSn interface unit.




5ChapterREPLACING HARDWARE

OVERVIEWAdding or replacing units are required operations during capacity expansion and equipment maintenance. However, accidents easily occur when such operations are conducted improperly.

This chapter focuses on the operation as well as the precaution for replacing a unit.

GENERAL PRECAUTIONSPay attention to the following aspects when you are performing hardware replacement:

• Common Language Equipment Identification (CLEI) code • Manufacturing code • Static electricity • Short circuit • Laser • Unit swapping

CLEI Code

The CLEI code is on the right unit ejector (Figure 5-1).

Figure 5-1. Specification Mark of the Unit

The CLEI code of the substitute unit must be the same as that of the unit to be replaced.

Chapter 5: Replacing Hardware


Manufacturing CodeThe manufacturing code is on the left unit ejector (Figure 5-1).

The manufacturing code includes the Bill Of Materials (BOM) and the unit name (Figure 5-2).

Figure 5-2. Specifications of the Manufacturing Code

Static Electricity

The human body can generate static electromagnetic field and keep it for a long time in the following cases:

• Body movements • Clothes friction • Friction between the shoes and ground • Plastic held in the hand

When you touch the equipment or hold units and IC chips, always wear an ESD wrist strap and keep it 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.

Short CircuitDuring the maintenance, try to avoid short circuit caused by metal objects (e.g., short circuit may be caused by improper use and placement of the operation tools).

When loosening the captive screw on the faceplate of the unit with tools (i.e., screwdriver), place the metal tools as far away from the equipment as possible after they are used.

Pay attention to the toppled pins on the backplane when demounting or installing the DSn interface unit. Never touch the toppled pins with metal objects so as not to cause short circuit.

The BOM of the substitute unit must be the same as that of the unit to be replaced.

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



Laser

It is hazardous to approach or stare into the optical interface or the optical fiber connector when installing or maintaining the optical interface unit.

Unit SwappingNote that swapping the units carrying services may cause a service interruption. Perform the hot swapping of the units when there is a small amount of traffic flow.

After the substitute unit is seated on the backplane, wait for about two minutes for it to boot into normal operation.

BEFORE REPLACEMENTPreparation for Replacing a Common Control Unit

Preparation for Replacing a Standby Common Control Unit

WARNING Laser is dangerous. The light is invisible to the eyes with or without laser protective glasses. Do not look into optical connectors and optical interfaces. Failure to follow this warning can cause damage to your eyes, or even blindness.

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 try not to contact the components on the unit to avoid short circuit. When holding the unit, never touch the circuit, components, connector and wiring trough of the unit.

Step Action1 Check the BOM on the ejector of the standby Common Control Unit (the first six digits).

Make sure the BOM of the new Common Control Unit is consistent with that of the one to be replaced.2 Query the PCB version (or issue number) of the standby Common Control Unit to be replaced

(TL1 command: RTRV-EQPT). Make sure the PCB version (or issue number) of the new Common Control Unit is consistent with that of the one to be replaced.

3 Query the NE software version (TL1 command: RTRV-EQPT) and software package version (TL1 command: RTRV-PKGVER) of the standby Common Control Unit to be replaced. Make sure the versions of the new Common Control Unit are consistent with those of the one to be replaced.

4 Check whether the optical interface of the standby Common Control Unit to be replaced has been configured with services.If no, replace the unit.

• If yes, make sure that: • The optical interface has been configured with the protection group. • The protection group is not on the same unit. • There is no abnormal alarm.

Otherwise, replacing the standby Common Control Unit will interrupt services.



Preparation for Replacing an Active Common Control Unit

Preparation for Replacing an OC-N Unit

Step Action1 Check the BOM on the ejector of the active Common Control Unit (the first six digits).

Make sure the BOM of the new Common Control Unit is consistent with that of the one to be replaced.2 Query the PCB version (or issue number) of the active Common Control Unit to be replaced

(TL1 command: RTRV-EQPT). Make sure the PCB version (or issue number) of the new Common Control Unit is consistent with that of the one to be replaced.

3 Query the NE software version (TL1 command: RTRV-EQPT) and software package version (TL1 command: RTRV-PKGVER) of the active Common Control Unit to be replaced. Make sure the versions of the new Common Control Unit are consistent with those of the one to be replaced.

4 Check whether the optical interface of the active Common Control Unit to be replaced has been configured with services.If no, replace the unit.


Otherwise, replacing the active Common Control Unit will interrupt services.5 Issue the TL1 command RTRV-BACKUP-INFO to query the backup status of both of the active and

standby common control units. Make sure the backup status is COMPLETE.6 Make sure that the standby common control unit operates normally and that there is no abnormal alarm.

Step Action1 Check the BOM on the ejector of the OC-N Unit (the first six digits).

Make sure the BOM of the new OC-N Unit is consistent with that of the one to be replaced.2 Query the PCB version (or issue number) of the OC-N Unit to be replaced (TL1 command: RTRV-EQPT).

Make sure the PCB version (or issue number) of the new OC-N Unit is consistent with that of the one to be replaced.

3 Check whether the optical interface of the OC-N Unit to be replaced has been configured with services.If no, replace the unit.


Otherwise, replacing the OC-N Unit will interrupt services.



Preparation for Replacing a DSn Processing Unit

Preparation for Replacing an Ethernet Unit

Preparation for Replacing a DSn Interface Unit

Step Action1 Check the BOM on the ejector of the DSn Processing Unit (the first six digits).

Make sure the BOM of the new DSn Processing Unit is consistent with that of the one to be replaced.2 Query the PCB version (or issue number) of the DSn Processing Unit to be replaced (TL1 command:

RTRV-EQPT). Make sure the PCB version (or issue number) of the new DSn Processing Unit is consistent with that of the one to be replaced.

3 Make sure: • The DSn Processing Unit has been configured with the TPS protection. • There is no abnormal alarm

Otherwise, replacing the DSn Processing Unit will interrupt services.

As the Ethernet Unit has no protection function, replacing the unit will interrupt services.

Step Action1 Check the BOM on the ejector of the Ethernet Unit (the first six digits).

Make sure the BOM of the new Ethernet Unit is consistent with that of the one to be replaced.2 Query the PCB version (or issue number) of the Ethernet Unit to be replaced (TL1 command:

RTRV-EQPT). Make sure the PCB version (or issue number) of the new Ethernet Unit is consistent with that of the one to be replaced.

3 For LPS-EGS4 make sure: • It has been configured with the Ethernet TPS protection. • There is no abnormal alarm.

Otherwise, replacing the Ethernet Unit will interrupt services.

As the DSn Interface Unit has no protection function, replacing the unit will interrupt services.

Step Action1 Check the BOM on the ejector of the DSn Interface Unit (the first six digits).

Make sure the BOM of the new DSn Interface Unit is consistent with that of the one to be replaced.2 Query the PCB version (or issue number) of the DSn Interface Unit to be replaced (TL1 command:

RTRV-EQPT). Make sure the PCB version (or issue number) of the new DSn Interface Unit is consistent with that of the one to be replaced.



Preparation for Replacing a Power Interface Unit

Preparation for Replacing a Fan Tray

Preparation for Replacing an Air FilterPrepare a new air filter. Make sure the new air filter matches the product.

DURING REPLACEMENT

• Remove the fibers and cables from the faceplate of the unit if there are any, and re-install them after the unitreplacement.

• Correctly swap the unit according to “Inserting/Removing a Unit” on page 2-2. • For the common control unit after the standby unit is replaced, make the active/standby units switch, and then

replace the active unit. After the active unit is replaced, switch again. Issue the TL1 command RTRV-BACKUP-INFO to query the backup status of both the active and standby common control units. Make sure the backupstatus is COMPLETE.

• For the unit with protection function after the protection unit is replaced, switch the service to the protection unit,then replace the original working unit. After the unit is replaced, switch the service back. Check whether it canperform switching normally.

Step Action1 Check the BOM on the ejector of the Power Interface Unit (the first six digits).

Make sure the BOM of the new Power Interface Unit is consistent with that of the one to be replaced.2 Query the PCB version (or issue number) of the Power Interface Unit to be replaced (TL1 command:

RTRV-EQPT). Make sure the PCB version (or issue number) of the new Power Interface Unit is consistent with that of the one to be replaced.

3 Make sure another power interface unit (not the one to be replaced) operates normally.Otherwise, replacing the Power Interface Unit will will cause power failure on the NE.

Step Action1 Check the BOM on the ejector of the Fan Tray (the first six digits).

Make sure the BOM of the new Fan Tray is consistent with that of the one to be replaced.2 Query the PCB version (or issue number) of the Fan Tray to be replaced (TL1 command: RTRV-EQPT).

Make sure the PCB version (or issue number) of the new Fan Tray is consistent with that of the one to be replaced.


CAUTION Avoid short circuit of a unit. Wear an ESD wrist strap.



AFTER REPLACEMENT• Check the flashing status of the unit indicator and make sure the unit is working normally. For details, refer to

“Unit Alarm Indicators” on page 3-4. • Query relevant alarms and performance events through the EMS to make sure there are no abnormal alarms. • Attach maintenance tag (marked with the name of this NE as well as the fault phenomena) to the replaced unit,

and then place the faulty unit into an antistatic bag. • Make sure the fiber and cable connection is correct.

For the unit without the alarm reporting function, check the operation status of the equipment connecting with it.


6ChapterTROUBLESHOOTING

LOGIN

User Cannot Log In The System Though The User Name and Password Are Correct

SymptomA user cannot log in to the system, though both the user ID and password are correct.

Possible Cause• The user ID has expired. • The user password has expired. • The account is inhibited by the system administrator. • The user ID has been used to logging into the system.

Solutions

Approach 1

Several TL1 commands are mentioned in this chapter; therefore, refer to the LoopStar 800/1600/3600 TL1 Reference Manual for detailed information.

Step Action1 Log into the system as the default user.

The default user is SONET/sonet and the password is SONET.2 Query all user information with the following TL1 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=INA CT&ALW&UIDUNEXP&PIDUNEXP,LASTLOGINTM=2005-08-28 12-19-35,SHOWHELP=YIn 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.

Chapter 6: Troubleshooting


Approach 2

Approach 3

User Exits The System Automatically Though No Exit Command Is Issued

SymptomUser exits the system though no exit command is issued.

Possible Cause• The current user performs no operation during the period for automatic exit. When this period expires, the user

exits automatically. • The user id or the password has expired. • The user id is forced to logout by another user.

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>]:TMO UTEN=[<TMOUTEN>],TMOUTLN=[<TMOUTLN>],PAGE=[<PAGE>],UAGE=[<UAGE> ];. <PAGE>: The time in which the password is in effect. The unit of the time is day and it ranges from 25-999, but 0 express the password is always in effect.

<UAGE>: The time in which the user’s name is in effect. The unit of the time is day and it ranges from 1 to 999, but 0 express the user is always in effect.

For example:

ED-USER-SECU::USERNAME:100::,,,:TMOUTEN=ENABLE,TMOUTLN=60,PAGE=0,UAGE=0;.5 If the account is inhibited, enable it with the account enabling command:

ALW-USER-SECU:[<TID>]::<CTAG>::<UID>;.


The default user is SONET/sonet and the password is SONET.2 Create a new NE user account with the following command:

ENT-USER-SECU:[<TID>]:<UID>:<CTAG>::<PID>,,<UPC>:[TMOUTEN=<TMOUTEN>],[TMOUTLN=<TMOUTLN>],[PAGE=<PAGE>],[UAGE=<UAGE>],[SHOWHELP=<SHO WHELP>];.

3 Log into the system with the newly created NE user account.


The default user is SONET/sonet and the password is SONET.2 If the user ID has been used to logging into the system, you can logout the user ID with TL1 command:

CANC-USER:[<TID>]:<UID>:<CTAG>;. For example: CANC-USER::USERNAME:100;.

3 Log into the system with the NE user ID.

Step Action



Solutions

TIMING

Line Source Cannot Be Configured Into Priority Table SymptomThe line source cannot be configured into the priority table.

Possible CauseThe logical unit is not created.

SolutionsCheck whether the corresponding logical unit has been created with the following command: RTRV-EQPT:::100;. If not, create it.

Line Source Cannot Be Detected

SymptomThe line source cannot be detected.

Possible CauseThe LOS, LOF, AIS_L or optical interface inloop alarm may occur upon the input signals.

SolutionsCheck whether the LOS, LOF, AIS_L or optical interface inloop alarm exists at the corresponding optical interface. If any alarm exists, clear the alarm according to the corresponding solution to the alarm.

• LOS may result from fault in fiber, fault in optical interface or no signal output at the transmitting end. Replace the fiber, change the optical input interface or connect a meter to confirm whether the problem lies here.

• LOF may result from optical interface rate mismatch or optical power mismatch. Retrieve the type of the fiber-connected units at both sides or performance event at the receiving end to confirm whether the problem lies here.

• AIS_L may result from the LOS or LOF alarm. Retrieve the alarms at the receiving and transmitting end to con-firm whether the problem lies here.

• For optical interface inloop, retrieve the alarm to confirm whether the problem lies here, and clear the alarm by using the command for releasing the loopback.

Step Action1 Log into the system again with the following TL1 command:

ACT-USER:[<TID>]:<UID>:<CTAG>::<PID>;.2 If the password expires, modify the corresponding attributes through the user attribute modification

command: ED-USER-SECU:[<TID>]:<UID>:<CTAG>::[<NEWUID>],[<NEWPID>],,[<UPC>]:TMO UTEN=[<TMOUTEN>],TMOUTLN=[<TMOUTLN>],PAGE=[<PAGE>],UAGE=[<UAGE> ];.

3 If the user id expires, create a new NE user with the following command: ENT-USER-SECU:[<TID>]:<UID>:<CTAG>::<PID>,,<UPC>:TMOUTEN=[<TMOUTEN> ], TMOUTLN=[<TMOUTLN>],PAGE=[<PAGE>],UAGE=[<UAGE>];.

4 If the User ID is forced to logout by another user, log in again.



External Clock Source Cannot Be Detected

SymptomExternal clock source cannot be detected.

Possible CauseThe LOS, LOF, AIS or CVOVER alarm may exist in the input signals of the external clock.

SolutionsCheck whether the LOS, LOF, AIS or CVOVER alarm exists in corresponding BITS. If any alarm exists, clear the alarm according to the corresponding solution to the alarm.

• LOS may result from fault in BITS cable, BITS input optical interface damaged or no signal output at the trans-mitting end. Replace the BITS cable or change the BITS optical input interface to confirm whether the problem lies here.

• LOF may be reported when the frame format at the transmitting is inconsistent with that at the receiving end. Retrieve the BITS attributes to confirm whether the problem lies here.

• AIS may be reported when the BITS output attribute at the transmitting end is configured in the "non pass-through" mode and the output SSM quality is equal to or under the set

• AIS threshold. Retrieve the BITS-OUT attribute at the transmitting end to confirm whether the problem lies here. • CVOVER may result from fault in BITS cable or output gain mismatch bringing on a great number of bit errors.

Replace the BITS cable or retrieve the output gain at the transmitting to confirm whether the problem lies here.

SSM Cannot Be Set Manually SymptomThe Synchronization Status Message (SSM) cannot be set manually.

Possible Cause• The timing source to be set is not in the priority table. • When the SSM protocol is under GEN1 conditions, SSM cannot be manually configured with clock quality of

GEN2.

Solutions

Step Action1 Check the source to be set is in the priority table. The TL1 commands are:

RTRV-SYNCLIST::SYNCCLOCK:100; RTRV-SYNCLIST::SYNCOUT-1:100; RTRV-SYNCLIST::SYNCOUT-2:100;

2 Check the version of the current SSM protocol. The TL1 command is:

RTRV-SYNC:::100; • When SSMMAP=Y, map the outgoing SSM to GEN1. • When SSMMAP=N, map the outgoing SSM to GEN2.



Timing Source Priority Table Cannot Be Set Successfully Symptom Setting of the timing source priority table is not successful.

Possible Cause• The line source or the external clock source is not correct. • The timing mode is not correct. • The external timing source priority table contains timing sources BITS1 and/or BITS2. • The timing sources exceeds 10.

Solutions

E1 Port Cannot Be Set As Timing Source

SymptomThe E1 port cannot be set as timing source.

Possible Cause• The timing source is not in external timing mode. • The port mode of BITS is not set as E1.

Solutions

Step Action1 Refer to “Line Source Cannot Be Configured Into Priority Table Symptom” on page 6-3, “Line Source

Cannot Be Detected” on page 6-3 or “External Clock Source Cannot Be Detected” on page 6-4 to see whether the line source or the external clock source is not correct. If they work normally, go to Step 2.

2 Query the timing mode with the following TL1 command: RTRV-SYNC::SYNCCLOCK:C;. • When TMGMODE=EXT, you are only allowed to edit the timing source BITS1/BITS2/INTERNAL into

the timing source table SYNC-NE. • When TMGMODE=LINE, you are only allowed to edit the line timing source into the timing source

table SYNC-NE. • When TMGMODE=MIXED, all timing sources can be edited into the timing source table SYNC-NE. • The timing source tables SYNCOUT-1 and SYNCOUT-2 are free from the above limitations. But the

timing sources BITS1 and BITS2 are not allowed into these two tables. 3 Modify the timing mode to a desired one with the following TL1 command:

ED-SYNC:[<TID>]:<AID>:<CTAG>:::[TMGMODE=<TMGMODE>,][SSMMAP=<SSMM AP>,] [SSMEN=<SSMEN>,][RVRTV=<RVRTV>,][RVTM=<RVTM>,][PNO=<PNO>];.

4 Set the timing source priority table with the following TL1 command: ED-SYNCLIST:[<TID>]:<AID>:<CTAG>::[<SYNCAID>]+;.

Step Action1 Modify the timing source to external timing mode.2 Modify the port mode of BITS to E1.



PROTECTION

TPS Protection Group Cannot Be Configured Successfully

SymptomThe TPS protection group cannot be configured successfully.

Possible Cause• The corresponding logical unit is not installed. • The protection unit and protected unit are not of DSn unit type. • The following requirements are not satisfied:

– If only LPS-PLT3/LPS-PQT3A/LPS-PDM3/LPS-PQM3 protection is provided, slot 3 is the protection slot, while slot 5 and slot 6 are the working slots.

– If only LPS-PLT1/LPS-PDT1 protection is provided, slot 3 is the protection slot, while slot 4, slot 5 and slot 6 are the working slots.

– If DS3+DS1 mixed protection is provided, slot 3 is limited to a LPS-PLT3/LPS-PQT3A/LPS-PDM3/LPS-PQM3 protection unit, slot 4 is limited to a LPS-PLT1/LPS-PDT1 protection unit, slot 5 is limited to a LPS-PLT1/LPS-PDT1 working unit, and slot 6 is limited to a LPS-PLT3/LPS-PQT3A/LPS-PDM3/LPS-PQM3 working unit.

• Use the DSn processing unit of lower capacity to protect the DSn processing unit of higher capacity. The follow-ing requirements are not satisfied:

– If the working unit is LPS-PLT1, the protection unit can be LPS-PLT1 and LPS-PDT1.– If the working unit is LPS-PDT1, the protection unit should also be LPS-PDT1.– If the working unit is LPS-PLT3, the protection unit can be LPS-PLT3, LPS-PQT3A, LPS-PQT3B. – If the working unit is LPS-PQT3A, the protection unit can be LPS-PQT3A, LPS-PQT3B. – If the working unit is LPS-PDM3, the protection unit can be LPS-PDM3, LPS-PDM3P, LPS-PQM3. – If the working unit is LPS-PDLTM, the protection unit should also be LPS-PDLTM.

• The rear DSn I/O unit does match the DSn protection type. LPS-PSI1 only supports DS1 protection; LPS-POI3 only supports DS3 protection, and LPS-PI13 supports DS1 + DS3 mixed protection. For detailed information about TPS protection, refer to the LoopStar 800 Hardware Description Manual.

Solutions

Step Action1 Delete the former logical unit.2 Re-install the correct logical unit in the designated slot. 3 Follow the configuration rules mentioned above to configure the TPS protection.

For detailed information about TPS protection, refer to the LoopStar 800 Hardware Description Manual. If the TPS protection group cannot be configured, go to Step 4.

4 Re-install the correct logical unit in the I/O slot.

For detailed information about TPS protection, refer to the LoopStar 800 Hardware Description Manual.



Ethernet Protection Group Cannot Be Configured Successfully

SymptomThe Ethernet protection group cannot be configured successfully.

Possible Cause• The corresponding logical unit is not installed. • The Ethernet processing unit is not LPS-EGS4. • The protection unit and working unit are not in the right slots.

When configuring Ethernet protection group for LPS-EGS4: the protection unit should not be configured in slot 3, while the working unit can be configured in either of the slots among slot 3, slot 4, slot 5, slot 6. For detailed information about Ethernet protection, refer to the LoopStar 800 Hardware Description Manual.

Solutions

Lots of Abnormal Phenomena Occur in SONET Line Protection

SymptomLots of abnormal phenomena occur in the SONET line protection.

Possible Cause• Protection cannot work normally. • The fiber connection is not correct. • The fiber of the protection optical interface breaks. • The laser is closed. Refer to Step 1 under Solutions below.

Solutions

For more information, see “Services Are Blocked After Switching When 1+1 SONET Line Protection Group Is Configured” on page 6-8.

Step Action1 Delete the former logical unit.2 Re-install the correct logical unit in the designated slot.3 Follow the slot configuration rules to configure the Ethernet protection.

For detailed information about Ethernet protection, refer to the LoopStar 800 Hardware Description Manual.

Step Action1 Query the alarm information.

If there is any alarm, clear it. For detailed information about Alarm information, refer to the LoopStar 800 Alarm and Performance Reference Manual.

2 Check the physical integrity of the connection to make sure the protection path can work normally.



UPSR Protection Pair Cannot Be Configured Successfully SymptomThe UPSR protection pair cannot be configured successfully.

Possible Cause• The pre-configured path acts as both protection path and working path. • The service is configured with multiple (more than two) sources and sole sink. • The configuration of cross-connection is not successful. • The source of the UPSR cannot be the DSn unit and Ethernet unit. • One path cannot be used as the working or the protection path of multiple UPSRs. But it is allowed that the two

UPSRs share the same working path and the same protection path. • The logical unit for creating the UPSR does not exist.

Solutions

Services Are Blocked After Switching When 1+1 SONET Line Protection Group Is Configured

SymptomThe services are blocked after switching when the 1+1 SONET line protection group is configured (the services are normal before the switching).

Possible Cause• The protection group protocol is not enabled. • The protection group is in locked status. • The cross-connection is not configured completely. • The optical interface of the OC-N unit which the protection optical interface locates is not in service. • The optical interface configured with the LAPS is used as the source of the UPSR.

Solutions

Step Action1 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 number of the first path satisfy the formula: 3 (or 6/9/12) × n + 1 and the consecutive paths to be

used are not occupied currently. For detailed information, see “Cross-connection Cannot Be Configured Successfully” on page 6-21.

4 Check the source of the UPSR with TL1 command: RTRV-EQPT. The source cannot be the DSn unit and Ethernet unit.

5 Check the cross-connect with the TL1 command: RTRV-CRS.6 Check the logical unit with TL1 command: RTRV-EQPT.

If the logical unit for creating the UPSR does not exist, create it with TL1 command: ENT-EQPT.

Step Action1 Check whether the switching protocol is started and query the status of the protection group with the

following TL1 command: RTRV-FFP-<OCN>:[<TID>]:[<AID>]:<CTAG>;. • If the protection group is locked, unlock it with the following TL1 command:

RLS-PROTNSW-<OCN>:[<TID>]:<AID>:<CTAG>::[<DIRN>];. • If the protection group is already in the switching status, go to Step 2.



External Switching Clearing Command Does Not Function When External Switching Occurs in SONET Line Protection

SymptomThe external switching clearing command does not function when external switching occurs in SONET line protection.

Possible Cause• The external switching is not launched by this end. • The optical AID is wrong.

Solutions

2 Query whether the cross-connection is configured correctly and completely with the following TL1 command: RTRV-CRS-<STS_PATH/VT_PATH>:[<TID>]:[<AID>]:<CTAG>;. 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 to Step 3.

3 Query whether the optical interface of the OC-N unit where the protection optical interface locates is in service. RTRV-<OCN>:[<TID>]:<AID>:<CTAG>;. If the optical interface is not opened, open it. ED-<OCN>:[<TID>]:<AID>:<CTAG>:::[LSRSTAT=<LSRSTAT>];.

4 Check whether the optical interface configured with the LAPS is set as the source of the UPSR. If it is, delete the UPSR.

5 If there is any alarm at the optical interface of the line, clear it. For detailed information about Alarm information, refer to the LoopStar 800 Alarm and Performance Reference Manual.

Step Action1 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 cannot clear the external switching launched by the opposite end.

The TL1 commands for clearing the external switching are: – For TPS: RLS-PROTNSW-EQPT:[<TID>]:<AID>:<CTAG>::[<DIRN>];. – For LAPS or BLSR: RLS-PROTNSW-<OCN>:[<TID>]:<AID>:<CTAG>;. – For UPSR: RLS-PROTNSW-<STS_PATH/VT_PATH>:[<TID>]:<AID>:<CTAG>::[<DIRN>];.

If the operation in the step does not work, proceed to Step 2.2 Query the protection status and check the optical AID of the external switching returned.

According to the optical AID you get, re-send the external switching clearing command for the corresponding optical AID.

Step Action



How to Modify SONET Line Protection Recovery Mode

Solutions

SONET Line Protection Group Cannot Be Configured Successfully

SymptomThe SONET line protection group cannot be configured successfully.

Possible Cause• The protection group already exists. • The port has been occupied. • The rate of the corresponding units does not match. • The number of the protection group is more than 12. • The logical unit has not been created or the logical unit is not of type of OC-N unit.

Step Action1 Change the state of protection group to OOS with the TL1 command: ED-FFP.

For example: ED-FFP-OC3::FAC-2-1:C::::OOS.2 Use the attribute modification command to modify the protection scheme (revertive or non-revertive).

ED-FFP-<OCN>:[<TID>]:<AID>:<CTAG>:::[FFPTYPE=<FFPTYPE>],[RVRTV=<RVRT V>],[RVTM=<RVTM>],[PSDIRN=<PSDIRN>],[TPLMODE=<TPLMODE>],[SQLMODE= <SQLMODE>],[RINGID=<RINGID>],[NODEID=<NODEID>]:[<FFPSTATE>];.

3 For BLSR, the recovery mode can be modified through the Wait To Restore time (WTR) modification parameter RVTM. Setting the RVTM to 99 indicates the non-revertive mode is selected, while setting the RVTM from 5 minutes to 12 minutes indicates the revertive mode is selected.

Modify the recovery mode of each node on the ring if you need to change the recovery mode of the ring.

For example: • Modify the recovery mode to non-revertive mode:

ED-FFP-<OCN>:[<TID>]:<AID>:<CTAG>:::FFPTYPE=<FFPTYPE>,RVTM=99;. • Modify the recovery mode to revertive mode:

ED-FFP-<OCN>:[<TID>]:<AID>:<CTAG>:::FFPTYPE=<FFPTYPE>,RVTM=5;. 4 For LAPS the recovery mode can be modified through the parameter RVRTV. Setting the RVRTV to N

indicates the non-revertive mode is selected, while setting the RVRTV to Y indicates the revertive mode is selected. The value of revertive time parameter RVTM is between 5 and 12.For example:

• Modify the recovery mode to non-revertive mode: ED-FFP-<OCN>:[<TID>]:<AID>:<CTAG>:::RVRTV=N;.

• Modify the recovery mode to revertive mode: ED-FFP-<OCN>:[<TID>]:<AID>:<CTAG>:::RVRTV=Y,RVTM=5;.

5 Change the state of protection group to IS with the TL1 command: ED-FFP.

For example: ED-FFP-OC12::FAC-5-1:C::::IS.



Solutions

Switching Does Not Happen When Bit Error Occurs In Working Path Of SONET Line Protection

SymptomBit errors occur in the working path, but no switching is performed.

Possible Cause• The protection path gets much more serious bit errors than the working path. • The work/protection path is locked manually. Refer to Step 2 under Solutions below. • In the 1:N LAPS or TPS protection group, the protection path is used by the other working path with higher prior-

ity. Refer to Step 3 under Solutions below.

Solutions

Step Action1 Query any existing protection groups.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.

3 Query whether the rate of the corresponding units mismatches. If it mismatches, change the unit which rate is matched.

4 Check the number of the protection groups. The number of the protection groups cannot be more than 12.5 Check the logical unit with the TL1 command: RTRV-EQPT.

For example: RTRV-EQPT:::C.

Step Action1 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.The TL1 commands to check the protection group are:

• RTRV-EQPT-PG:[<TID>]:[<AID>]:<CTAG>; • RTRV-FFP-ALL:[<TID>]::<CTAG>;

2 Release the lock of work/protection path by using the TL1 commands: • For LAPS: RLS-PROTNSW-<OCN>:[<TID>]:<AID>:<CTAG>;. • For TPS: RLS-PROTNSW-EQPT:[<TID>]:<AID>:<CTAG>;.

3 Modify the sequence of the priority. • For LAPS: Delete the protection group, recreate the protection group and modify the sequence of the

priority. • For TPS: Modify the sequence of the priority (to be higher) with the TL1 command:

ED-EQPT:[<TID>]:<AID>:<CTAG>:::[TPSPRI=<TPSPRI>],[PROVTYPE=<CARDT YPE>], [INTFTYPE=<INTFTYPE>]:[[<PST>],[<SST>]];.



SONET Line Switching Is Unsuccessful SymptomThe SONET line switching is unsuccessful.

Possible Cause• The protection path fails to work normally. • The switching request of the same or higher priority exists on the optical interface to be switched. Refer to

Step 3 under Solutions below.

• For 1:N protection group, if the switching request of higher priority exists on the other optical interfaces, the switching at this interface will not be carried out. Refer to Step 3 under Solutions below.

• If the SF alarm is reported at the protection optical interface, the switching from the working optical interface to protection optical interface will not be carried out. Refer to Step 4 under Solutions below.

Solutions

Switching Occurs for the Working Path Though It Is Locked

SymptomThough the working path of the SONET line protection group is locked, switching still occurs for it.

Possible CauseIf 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 on the working path of local end.

SolutionsCheck the switching status of the two ends with the following TL1 command: RTRV-FFP-<OCN>:[<TID>]:[<AID>]:<CTAG>;.

If only one end of the working path is locked, use the following TL1 command to lock the other end of the working path: OPR-PROTNSW-<OCN>:[<TID>]:<AID>:<CTAG>::LOCKOUT;.

The switching priority from higher to lower is: LP, FS, SF, SD, MAN, WTR, EXER, DNR/NR.

Step Action1 Check the status of the protection group with the TL1 command: RTRV-FFP-ALL:[<TID>]::<CTAG>;.

If the protection group does not work normally, go to step 2. 2 Check the physical wiring for correctness to make sure the protection path can work normally.3 Execute the TL1 command RTRV-<OCN> to retrieve the switching mode or execute the TL1 command

RTRV-COND-ALL to retrieve the switching alarm.If the working or protection optical interface is locked, release the locking as needed.

4 Execute the TL1 command RTRV-<OCN> to retrieve the switching mode of the protection optical interface.If the SF is reported, clear it first by replacing the fiber or other methods.



Failing To Deliver The Command For The Manual Switching Of The Clock Source

SymptomThe command for the Manual Switching is failed to deliver.

Possible Cause• Wrong command and parameters are delivered. • When the SSM protocol is started, the SSM quality actually processed by the switch source is lower than that

actually processed by the trace source. • A higher priority external command exists. • The switched clock source is invalid or its quality is DUS.

Solutions

Step Action1 Check whether the wrong command and parameters are delivered. The key parameters are the priority

table number and clock source number.2 When the SSM protocol is started, the priority of the manual switching is lower than that of SSM protocol

switching, so you can only perform the manual switching between the clock sources of the same SSM quality. Check whether the SSM protocol is started by using the TL1 command RTRV-SYNC for retrieving the attributes of the priority table. Retrieve the SSM quality actually processed by the switch source though the command for retrieving the content of the priority table.

3 Check whether the forced switching or lock exists. If the forced switching or lock exists in the priority table, the manual switching cannot be performed.

4 The manual switching cannot be performed if its switched clock source is invalid or its quality is DUS. Retrieve the detailed information by using the command for retrieving the content of the priority table.



Failing To Configure The BLSR Protection

SymptomThe BLSR protection is failed to configure.

Possible Cause• The levels of the optical interfaces for the BLSR protection are not the same. • The optical interface is used by other protection (i.e., LAPS or BLSR). • The values of the parameters are not in the specified range. • For the two-fiber BLSR, if the service across the working and protection channel of the BLSR to the created

exists, the BLSR cannot be created. • The NE can only support 12 BLSR protections at its maximum. • When you create the BLSR protection, the RVRTV=Y is wrongly input.

Solutions

Step Action1 Make sure all the optical interfaces (OC12) on the BLSR are at the same level.

A BLSR cannot be created for OC3.

2 Execute the TL1 command RTRV-FFP-ALL:<TID>::<CTAG> to retrieve whether the unit is configured with the line protection.

3 Configure the following parameters when creating the BLSR protection:

<FFPTYPE>: 2BLSR

<NODEID>: 0-15

<RINGID>: a string of up to 16 characters excluding the backslash and single quotes. It can be null.

<RVTM>: 5-12 and 99

LoopStar 800 does not support four-fiber BLSR.If the value of RVTM is 5-12, the BLSR protection is revertive. If the RVTM value is 99, the BLSR is non-revertive. Do not input the RVRTV=Y or the creation of the BLSR protection can fail.

4 Check whether the service across the working and protection channel exists with the TL1 command: RTRV-CRS:<TID>::<CTAG>.

Example for what is "service across the working and protection".There are two OC12 units with a STS9C service. The former six time slots are working slots, and the last six time slots are protection slots. As the STS9C service takes nine time slots, it uses both the working slots and the protection slots. Therefore, the configuration of BLSR fails.



Failing To Configure The BLSR Switching

SymptomThe BLSR switching is failed to configure.

Possible Cause• The BLSR protection group does not exist. • The networking environment is not consistent with the configuration (e.g., some fibers are wrongly connected). • After the full-ring BLSR protection is created, the switching occurs when RingMap is not normally created. • A switching alarm with higher order priority exists at the optical interface.

Solutions

Failing To Create RingMap After The Full-Ring BLSR Protection Is Created

SymptomThe RingMap failed to create after the Full-Ring BLSR Protection was Created.

Possible Cause• The networking environment is not consistent with the configuration (e.g., some fibers are wrongly connected). • Severe alarms (i.e., LOS or LOF) exist at the optical interface. • The NE DCC is in the pass-through mode. • Repetitive node number exists at the nodes on the BLSR ring. • On the BLSR ring, the RingMap mode at one node mismatches that at the other nodes. • On the BLSR ring, the RingMap mode at the nodes is the manual mode and the configuration is incorrect.

Solutions• Ensure the networking environment is consistent with the configuration. No fiber is wrongly connected. • Check the alarms at the optical interface and ensure no severe alarms (i.e., LOS or LOF) exist. • The NE DCC communication at each node on BLSR must be in the non-pass-through mode. Retrieve the DCC

channel protocol with the TL1 command: RTRV-DCC. Edit the DCC channel protocol to be PPP with the TL1 command: ED-DCC. If DCC channel protocol is TRANSPARENT, the optical interface is in the pass-through state.

• If the alarm of repetitive nodes on BLSR exists, it indicates repetitive nodes exist in the full-ring BLSR protection. Edit the BLSR node number to solve this problem. Retrieve the node ID with the TL1 command: RTRV-FFP-<OCN>. Modify the node ID with the TL1 command: ED-FFP-<OCN>.

The switching priority from higher to lower is: SF-P, LP-S, FS-S, FS-R, SF-S, SF-R, SD-S, SD-R, MAN-S, MAN-R,WTR, EXER-S, EXER-R, NR.

Step Action1 Ensure that the BLSR protection group exists with the TL1 command: RTRV-FFP-ALL:<TID>::<CTAG>.2 Ensure that the networking environment is consistent with the configuration and the fibers are correctly

connected.3 Ensure that RingMap is normally created. When the full-ring BLSR protection is created, you only can

perform the first switching after RingMap is normally created.4 Check the switching status with TL1 command: RTRV-FFP-<OCN>.



• If the alarm of TPLMODE mismatch, it indicates the TPLMODE mismatch exists in the full-ring BLSR protection. Edit the TPLMODE at the BLSR node to solve this problem. Check the TPLMODE with TL1 command: RTRV-FFP-<OCN>. Modify the TPLMODE with TL1 command: ED-FFP-<OCN>.

• If TPLMODE is in the manual mode, users need to edit RingMap manually and ensure RingMap is correctly edited. Check the TPL with TL1 command: RTRV-TPL-<OCN>. Modify the TPL with TL1 command: ED-TPL-<OCN>.

Interrupted Services Caused By The BLSR Switching

SymptomServices are interrupted by the BLSR Switching.

Possible Cause• The cross-connect configuration is not under the protection of BLSR. • The interrupted services are extra services or the working services that need to be suppressed. • The switching with the same or higher priority or switching lock exists on the BLSR ring.

Solutions

CONNECTIONServices Are Blocked SymptomServices are blocked.

Possible Cause• The working optical fiber is damaged in the event that the network is not protected. • The laser of the working path is shut down in the event that the network is not protected. The optical power is too

higher or too lower. • 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. (The working path does not work.) • When the network is configured as UPSR and its protection mode is modified to non-revertive mode, the ser-

vices are forcedly switched to the working path. (The working path does not work.) • When the network is configured as UPSR and its locked working paths have failures. • Unit is cold reset. • Cold reset the common control unit. • The configuration is lost.

Step Action1 Execute the TL1 command RTRV-CRS:::<CTG> to retrieve the cross-connect configuration.2 When the switching occurs, the extra services in some sections will be suppressed. When node isolation

or ring segmentation occurs, the normal services with source/sink node lost will be suppressed. • Check the alarm about suppressed with TL1 command: RTRV-COND-ALL.• Check the squelch table with TL1 command: RTRV-SQL-<STS_PATH>. • Edit the mode of the squelch mode to be manual with TL1 command: ED-FFP-<OCN>. • Edit the squelch table with TL1 command: ED-SQL-<STS_PATH>.

3 Check whether the switching of the same or higher priority or switching lock exists on the BLSR ring. • Check the switching status with TL1 command: RTRV-FFP-<OCN>.



Solutions

Some NEs Cannot Be Reached With Static Route

SymptomWhen fiber is broken somewhere in the network, the EMS server cannot communicate with some NEs.

Possible Cause• The EMS server uses IP over DCC function to communicate to the NEs. A set of static routes are used to com-

municate between EMS server and equipment. If fiber is broken somewhere, the static routes cannot be regen-erated automatically.

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

• The DCC communications break because of following cause:– The CRC check codes mismatch. – The DCC bit errors. – The D bytes of NEs at the both ends mismatch (e.g., the D bytes at one NE are D1–D3, but those at the

opposite NE are D4–D12). • Perform the self-loop on the same optical port.

Solutions

Step Action1 Configure corresponding protection scheme or replace the optical fiber.2 Configure corresponding protection scheme or start the laser.

Check the optical power with an optical power meter. Use an attenuator as needed.3 Check the cross connection with TL1 command: RTRV-CRS-<STS_PATH>.

Create cross connection as needed, with TL1 command: ENT-CRS-<STS_PATH>.4 Check the working path alarms of the UPSR with TL1 command: RTRV-COND-<STS_PATH>.5 Check the status of the working path with TL1 command: RTRV-<STS_PATH>.6 Unlock the working path with TL1 command: RLS-PROTNSW-<STS_PATH>.

Step Action1 Check for a fiber break and repair if a break is discovered.2 Recreate the static route at NE side:

• Check the static route with the TL1 command: RTRV-IPROUTE-STATIC. • Create the static route with the TL1 command: ENT-IPROUTE-STATIC.

3 Check the alarms. If there is a DCC-FAIL alarm, check if the fibers are correctly connected. Recover DCC connection of the NE by using theTL1 command: ED-DCC.



Some NEs Cannot Be Reached With Dynamic Routes

SymptomWhen fiber is broken somewhere in the network, EMS server cannot communicate with some NEs.

Possible Cause• The dynamic routes are not recreated in the following circumstances:

– NE OSPF protocol does not start. Refer to Step 1 under Solutions below. – NE OSPF protocol’s parameter of TIMER does not match with other NEs. Refer to Step 2 under Solutions

below. – The corresponding interface (Optical or Ethernet) of NE OSPF does not open. Refer to Step 3 under

Solutions below.– The fiber is broken. Refer to Step 4 under Solutions below.

• The DCC communications break because of following cause. Refer to Step 5 under Solutions below. – The CRC check codes mismatch. – The DCC bit errors. – The D bytes of NEs at the both ends mismatch (e.g., the D bytes at one NE are D1–D3, but those at the

opposite NE are D4–D12). • Perform the self-loop on the same optical port.

Solutions

Step Action1 Start the NE OSPF protocol with the TL1 command:

ED-OSPF-SYS:[<TID>]::<CTAG>:::[ENABLE=<OSPF_ENABLE>],[AREA=<AREA>],[S TUB=<STUB_FLAG>],[NSSA=<NSSA_FLAG>],[IMPORTRIP=<IMPORTRIP_FLAG>],[ IMPORTSTATIC=<IMPORTSTATIC_FLAG>],[IMPORTDIRECT=<IMPORTDIRECT_F LAG>];.

2 Make the NE’s parameter of TIMER matched with other NEs.• Check the NE OSPF protocol with the TL1 command: RTRV-OSPF-ALL. • Modify the NE OSPF protocol with the TL1 command: ED-OSPF-SYS.

3 Open the corresponding interface of NE OSPF with the TL1 command: ED-OSPF-SYS:[<TID>]::<CTAG>:::[ENABLE=<OSPF_ENABLE>],[AREA=<AREA>],[S TUB=<STUB_FLAG>],[NSSA=<NSSA_FLAG>],[IMPORTRIP=<IMPORTRIP_FLAG>],[ IMPORTSTATIC=<IMPORTSTATIC_FLAG>],[IMPORTDIRECT=<IMPORTDIRECT_F LAG>].

4 Check whether an alarm such as LOS occurred against the optical interfaces connecting the NEs, with the TL1 command RTRV-ALM-<OCN>.

5 Check the alarms. If there is a DCC-FAIL alarm, check if the fibers are correctly connected. Recover DCC connection of the NE by using thecommand ED-DCC.



Faults in the SNMP Network

SymptomThe managed NE cannot be accessed by the NMS correctly.

Possible Cause• The current NE software does not support SNMP. • The managed NE is wrongly configured.

Solutions

NMS Cannot Receive the Trap Message SymptomThe NMS cannot receive the trap message.

Possible CauseThe IP address and the port number of the managed NE are not correctly set.

Solutions

PERFORMANCE MONITORINGSome Of The Records Display INVALID When Querying History Performance

SymptomSome of the records display INVALID when querying the history performance.

Possible Cause• The host is hot/cold resetting. • The unit is hot/cold resetting. • The user is sending TL1 command: SET-PMDAY. • The user is modifying the NE time and date. • The port is in Out-of-Service (OOS) state in the corresponding cycle.

Step Action1 The NE software is encapsulated for sale with the corresponding SNMP MIB. Check whether the version

of NE software supports SNMP. Use the TL1 command: RTRV-EQPT:[<TID>]:[<AID>]:<CTAG>;. 2 If the NE software version is correct, check whether the IP address configured in the NE agent is the IP

address of the current NMS computer. Use the TL1 command: RTRV-SNMP-ACCESSIP:[<TID>]:<IPAddress >:<CTAG>;.

3 If you need to add new SNMP access information, check the number of the existing SNMP information records in the agent first. The managed device is only allowed to store a maximum of 32 records.

Step Action1 Retrieve the trap message of the NE to check if the IP address and port number are the same as those of

the NMS computer. Use the TL1 command: RTRV-SNMP-TRAPINFO.2 If the IP address and the port number are wrongly configured, edit the trap information by using the TL1

command: ED-SNMP-TRAPINFO. 3 If the IP address and the port number are not configured, add the trap information to the SNMP agent by

using the TL1 command: ENT-SNMP-TRAPINFO.



ALARM MONITORING AND MANAGEMENT

Alarms Cannot Be Queried Using The Command RTRV-ALM-ALL

SymptomAlarms cannot be queried with the TL1 command RTRV-ALM-ALL:::100;.

Possible Cause• The attribute of the port or the NE is in the OOS state instead of IS, and the alarms of this port cannot be que-

ried. • No service is configured to this port and no alarm is monitored accordingly. • The level of this alarm is NR or NA. Alarms only with levels of CR, MJ or MN can be queried through the TL1

command RTRV-ALM-ALL:::100;.

Solutions

Step Action1 Use the TL1 command RTRV-<OCN> to query the attribute of this port.

If it is OOS, use the TL1 command ED-<OCN> to change 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 TL1 command RTRV-COND-ALL:::100; for querying.



UNIT CONFIGURATION

Cross-connection Cannot Be Configured Successfully

SymptomThe configuration of cross-connection is not successful.

Possible Cause• Configuration of dual-received cross-connection is not correct. • The STS number is not correct. • The unit does not support the type of the cross-connection configured. • The path is used or the cross-connection is already configured.

Solutions

Step Action1 Check whether the existing cross-connection has the same sink with that configured currently (UPSR

excluded).2 Check the STS number for correctness.

All the start path number except that for STS-1 minus 1 can be divided by 3 exactly. The bandwidth must be limited to 622M.

• The STS-1 connection can use all paths with any number. • The STS-3c cross-connection can use the path number ranging from (12 % N+1) to (12 % N+10)

(N>=0) only. (The path number of STS-3c is started with 3 % N+1, 0=N=15.) • The STS-6C cross-connection can use the path number ranging from (12 % N+1) to (12 % N+7)

(N>=0) only. (The path number of STS-6c is started with 6 % N+1, 0=N=7.) • The STS-9C cross-connection can use the path number ranging from (12 % N+1) to (12 % N+4)

(N>=0) only. (The path number of STS-9c is started with 12 % N+1, 0=N=3.) • The STS-12C cross-connection can use the path numbered (12×N+1) (N>=0) only. (The path number

of STS-12c is started with 12 % N+1, 0=N=3.) • The maximum number for paths of the unit is as follows: 24 for LPS-OC12D/LPS-OC3O/LPS-OC12A,

12 for LPS-OC12/LPS-OC3A/LPS-OC3Q, 6 for LPS-OC3D, 3 for LPS-OC3, 12 for LPS-PQT3A, 6 for LPS-OC3D, 3 for LPS-OC3.

3 Check the type of the cross-connection and unit configured. • The LPS-OC12A/LPS-OC12D/LPS-OC12 unit can be configured with STS-1, STS-3c, STS-6c,

STS-9c or STS-12c cross-connection. • The LPS-OC3A/LPS-OC3Q/LPS-OC3D/LPS-OC3O/LPS-OC3 unit can be configured with STS-1 or

STS-3c cross-connection. • The LPS-PQT3A/LPS-PDM3/LPS-PQM3/LPS-PDLTM/LPS-PLT3/LPS-PDT1/LPS-PLT1 unit can be

configured with STS-1 cross-connection. • When the common control unit is LPS-TO3D/LPS-TO12D, the LPS-OC12A/LPS-OC12D/LPS-OC12/

LPS-OC3A/LPS-OC3Q/LPS-OC3D/LPS-OC3O/LPS-OC3 unit and LPS-PLT1/LPS-PDT1/LPS-PDM3/ LPS-PQM3/LPS-PQT3A/LPS-PDLTM unit can be configured with VT1 cross-connection.

• The LPS-EGT2 unit can be configured with STS-1, STS-3c, STS-6c, STS-9c, STS-12c or STS-24c cross-connection.

• The LPS-EFS8 and LPS-ELS4 units can be configured with STS-1 and VT1 cross-connection. • The LPS-EGS4 unit can be configured with STS-1, VT1, STS-3c, STS-12c cross-connection. • The LPS-ET4GS unit can be configured with STS-1 cross-connection.



Physical Slot For An In-Service Unit Is NULL When Querying SymptomThe unit is in-service, but its physical slot displays NULL when querying.

Possible CauseThe unit software is not started.

SolutionsWarm reset the unit.

4 Check the representation of the cross-connection configured. • STS is represented as: RTRV-CRS-<STS_PATH/VT_PATH>:[<TID>]:[<AID>]:<CTAG>;. • VT is represented as: RTRV-CRS-<STS_PATH/VT_PATH>:[<TID>]:[<AID>]:<CTAG>;.• All cross connections are represented as: RTRV-CRS:[<TID>]::<CTAG>;.

Step Action

LPS800-UM-MAIN-04 A-1

AAppendixREGULAR MAINTENANCE RECOMMENDATIONIn order to maintain the normal and stable running of the equipment, follow the recommendations below for daily maintenance.

To make equipment maintenance more convenient and efficient, some tables are given below for reference.

INSTRUCTION

You can modify the maintenance record according to the local site practice.

Number Name Description

A-1 Daily Maintenance and Operation Guide

Used as reference for daily maintenance.

A-2 Monthly Maintenance and Operation Guide

A-3 Quarterly Maintenance and Operation Guide

A-4 Annual Maintenance and Operation Guide

A-5 Daily Maintenance Record 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.

A-6 Monthly (Quarterly) Maintenance Record

Records describing maintenance made on monthly (quarterly) basis.

A-7 Annual Maintenance Record

A maintenance record made on annual basis

A-8 Emergency Troubleshooting Record

Records describing the emergencies and the associated measures already taken, serving as the basis for future maintenance and inquiry.

A-9 Unit Replacement Record Records describing the replacement of units.

A-10 Data Modification Record Records describing the modification of configuration data.


A-2 LPS800-UM-MAIN-04

A-1 DAILY MAINTENANCE AND OPERATION GUIDE

Types Items Operation Guide Referential Standard

External environment temperature check

Power supply in equipment room

Check the power monitoring system or test the output voltage.

Output voltage is normal, no alarm indicating power abnormality.

Cleanliness in equipment room

Test the cleanliness of machine room.

Refer to the attached table.

Temperature in equipment room

Test the temperature. Temperature range: 0°C to 45°C; the recommended temperature range: 15°C to 30°C.

Humidity in equipment room

Test the relative humidity. Relative humidity: 10% to 90%; the recommended humidity: 40% to 65%.

Equipment running status check

Status of unit indicator

Observe unit indicator. Refer to the LoopStar 800 Hardware Description Manual for indicator explanation

Temperature of equipment surface

Test the temperature of equipment surface.

The highest equipment temperature detected by EMS is not allowed to exceed 40°C.

Status of fan (check it on the first day and the fifth day every month)

Watch the fan indicator and the running of the fans.

When the fans are running normally, only the green indicator illuminates.

EMS Maintenance EMS login Log into the EMS as junior user. An account for every maintenance person is recommended.

Log into EMS is normal.

NE status check Log into every NE through EMS to check its status.

All NEs are in running status and login to all NEs is normal.

Unit status check Check the presence and running of units via the slot diagram in EMS.

According to slot diagram, the units should be properly seated and in running status.

EMS Maintenance Alarm check View current alarms and history alarms by using the alarm inquiry and browsing function offered by EMS.

There is no untraceable alarm in the system.

Performance event monitoring

View current performance data and history data by using the performance data inquiry and browsing function offered by EMS.

Performance events reported normal; all performance data of bit error and pointer adjustment comply with Telcordia recommendations; no performance data has crossed threshold.



Attached: machine room cleanliness requirement

A-2 MONTHLY MAINTENANCE AND OPERATION GUIDE

EMS Maintenance Protection switching check

Check switching status and switching alarm.

The protection switching works normally.

Log record query Use the operation log inquiry function offered by EMS.

There is no attempt to log into EMS, and there is no unidentified data modification.

Equipment environmental variable check

Check the temperature alarm and voltage alarm of PMU unit via EMS, and its temperature related performance data.

There is no temperature alarm and voltage alarm; temperature related performance data are normal.

Maximum diameter (µm) 0.05 1 3 5

Maximum density (particles/m3) 1.4×106 7×105 2.4×105 1.3×105

Types Items Operation guide Referential standard

Service check Idle channel 24-hour bit error measuring

Test bit errors in the idle channels with 24 hours as a cycle by using meter.

For DS1 channel, amount of bit errors within 24 hours should be 0.

EMS maintenance item

EMS activation and shutdown check

Activate and shutdown EMS software and computers.

EMS activation and shutdown should be normal.

NE time query Query NE time through EMS. NE time is consistent with the current time, all NEs time consistent.

Unit configuration data query

Check configuration data of clock unit, overhead unit, DSn processing unit and optical interface unit.

Configuration data are consistent with the actual requirements, and comply with last record modifications.

Modify EMS log-in password

Modify EMS login password once every month.

Modify password every month.

EMS database transferring and reorganization

Transfer EMS database files, and compress and repair them once every month.

Such operations should be taken regularly. EMS running normal.

EMS database backup

Such operation should be taken every month. EMS and database normal.

EMS computer maintenance

For PC, directories and files are in normal status; there is no illegal file (i.e., game file); the hard disk can provide sufficient space. For working station, there is no illegal file, the database running normal.




A-3 QUARTERLY MAINTENANCE AND OPERATION GUIDE

A-4 ANNUAL MAINTENANCE AND OPERATION GUIDE

Hardware interface status check

Check the working status of mouse, keyboard, monitor and printer.

In good conditions.

NE configuration data backup

Such operation should be taken every month.

Air filter checking and replacing

Check and replace the air filter. Such operation should be taken twice a month.


Remote maintenance function test


Log into the NE from far end. NE login is normal, remote maintenance function works normally.

Rack cleanliness check

Rack cleanliness check

Examine the interior and exterior of rack.

The rack surface is clean; there is no excessive dust inside the rack.


Grounding cable and power cable connection check

Grounding resistance check

Measure the grounding resistance by using earth resistance tester.

The total grounding resistance is less than 1 ohm.

Grounding cable connection check.

Check the reliability of connection of grounding cable with grounding bar in machine room.

• All connections are safe and reliable, and free of corrosion.

• Grounding bars not aged. • Groundings well treated with

anti-corrosion measure and is free of corrosion.

Power cable connection check

Check the reliability of the connection of power cable with power source in machine room.

• All connections are safe and reliable and free of corrosion.

• Power cable not aged.

Types Items Operation guide Referential standard



A-5 DAILY MAINTENANCE RECORDDate: ______________ (Year) ______________ (Month) ______________ (Day)

Shift time: From______________ To______________

Person off duty: ____________________ Person on duty: ____________________

Type Item Status Remarks Maintained By

Equipment running environment

External environment (power supply, fire alarm, smoke, thunder, etc)

Normal Abnormal

Temperature (normal, 15°C to 30°C)

Normal Abnormal

Humidity (normal, 40% to 65%) Normal Abnormal

Equipment room cleanliness Good Bad

Equipment running status check

The status of unit indicator Normal Abnormal

Equipment surface temperature Normal Abnormal

Equipment fan status (check it on the first day and the fifth day each month)

Normal Abnormal

EMS maintenance EMS login Normal Abnormal

NE status check Normal Abnormal

Unit status check Normal Abnormal

Alarm check Normal Abnormal

Performance event monitoring Normal Abnormal

EMS maintenance Protection switching check Normal Abnormal



EMS maintenance Log query Normal Abnormal

Equipment environment variable check

Normal Abnormal

Audio alarm notification Normal Abnormal

Fault description and handling

Unsolved problems

Checked by team leader




A-6 MONTHLY (QUARTERLY) MAINTENANCE RECORDMaintenance cycle: ______________(Year)______________(Month)______________(Day) to

______________(Year)______________(Month)______________(Day)


Traffic check Selectively test channel 24-hour bit error

Normal Abnormal

EMS maintenance EMS activation and shutdown check

Normal Abnormal

NE time query Normal Abnormal

Unit configuration information query

Normal Abnormal

EMS login password Modification

Normal Abnormal

EMS database transferring and reorganization

Normal Abnormal

Network management database backup

Normal Abnormal

EMS computer maintenance Normal Abnormal

Hardware interface status check

Normal Abnormal

NE configuration data check Normal Abnormal

Quarterly maintenance


Normal Abnormal

Rack cleanliness check Normal Abnormal

Problem description and troubleshooting

Unsolved problems




A-7 ANNUAL MAINTENANCE RECORDMaintenance cycle: ______________(Year)______________(Month)______________(Day) to

______________(Year)______________(Month)______________(Day)

A-8 EMERGENCY TROUBLESHOOTING RECORD


Grounding cable and power cable connection check

Earth resistance check Normal Abnormal

Grounding cable connection check

Normal Abnormal

Power cable connection check Normal Abnormal

Problem description and troubleshooting

Unsolved problem


Time of occurrence: Time of solution:

Person on duty: Handler:

Type of problem:

Power supply problem EMS software problem

Trunk cable problem or distribution frame problem Grounding problem or power connection problem.

EMS computer problem Data setting problem

Unit problem Operation problem

Software problem Other problems (i.e., temperature, humidity, rat, electromagnetic interference)

Fault description:

Troubleshooting method and result:



A-9 UNIT REPLACEMENT RECORD

A-10 DATA MODIFICATION RECORD

Original unit Name:

Type:

Slot:

New unit Name:

Type:

Slot:

The reason:

Date:

Person:

ModifierTime of

Modification Cause of Modification Modification Description



ModifierTime of

Modification Cause of Modification Modification Description

LPS800-UM-MAIN-04 B-1

BAppendixSERIOUS FAILURE PROCESSING FLOW

FLOW CHART OF SERIOUS FAULT HANDLINGSerious 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.

Figure B-1. Flow Chart of Serious Fault Handling

Start

Record Fault Phenomenon and

Equipment Statement

ExternalCauses

Dial Local Customer Service Hotline of ADC

Analyze and Locate Fault

Work Out the Solutions Together

Try to Solve

ServiceRecovery

24-Hour Observation

RemoveFault

Fill In Report, Sum Up and Archive Case

End

Other Solution FlowYes

No

Yes

No

Yes

No

Appendix B: Serious Failure Processing Flow

B-2 LPS800-UM-MAIN-04

FLOW DESCRIPTION AND PRECAUTIONS• Make a factual and detailed record about the whole process of a fault when recording 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 EMS should also be saved and observed.

• When it is found that the fault is obviously caused by external factors (i.e., cable problem, terminal equipment (switch problem)), enter into other corresponding processing flow in time so as to solve the fault as soon as pos-sible.

• 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 ser-vice). 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 equip-ment (e.g., 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 Appendix A on page A-1, and close the fault handling flow.

RECOMMENDATION• Implement the special-person maintenance system of EMS and equipment; accomplish software and hardware

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 accumulating

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:

http://www.adc.com

LPS800-UM-MAIN-04 C-1

CAppendixLOOPSTAR 800 GLOSSARY

1+1 Protection A 1+1 protection architecture has one normal traffic signal, one working SNC/trail, one protection SNC/trail and a permanent bridge.

1+1 Protection A 1+N protection architecture has N normal traffic signal, N working SNC/trail, and N protection SNC/trail.

100BASE-T Physical Layer specification for a 100 Mbit/s CSMA/CD local area network.

100BASE-TX Physical Layer specification for a 100 Mbit/s CSMA/CD local area network over two pairs of Category 5 Unshielded Twisted-Pair (UTP) or Shielded Twisted-Pair (STP) wire.

AAccess Identifier An access code contains information needed to access or address object entities

within the target NE.

Add/Drop Multiplexer A multiplexer capable of extracting and inserting lower-rate signals from a higher-rate multiplexed signal without completely demultiplexing the signal.

ADM Add/Drop Multiplexer (see Add/Drop Multiplexer).

Administrator A user who has authority to access all the Management Domains of the EMLCore product. He has access to the whole network and to all the management functionalities.

Agent An entity that represents the certain attributes and behavior of a resource. The agent allows the interactions between the various resources and the management and control functions. More than one agent may represent a resource.

AID Access Identifier. It is an access code containing information needed to access or address object entities within the target NE/NS.

AIS Alarm Indication Signal. A signal sent downstream in a digital network if an upstream failure has been detected and persists for a certain time.

AIS-L Line Alarm Indication Signal. An AIS-L code is generated by a Section Terminating Equipment (STE) upon loss of input signal or loss of frame. The AIS-L signal will maintain operation of the downstream Section Terminating Equipment, and therefore, prevent generation of unnecessary alarms. At the same time, data and orderwire communication is retained between the Section Terminating Equipment and the downstream Line Terminating Equipment (LTE).

Alarm A visible or an audible indication to notify the person concerned that a failure or an emergency has occurred.

Alarm Cable The cable which is used to transmit alarm signals.

Alarm Indication On the cabinet of an NE, there are three indicators with different colors indicating the current status of the NE. You can stop the NE alarm indication through the LoopStar EMS.

Appendix C: LoopStar 800 Glossary

C-2 LPS800-UM-MAIN-04

Alarm Severity According to ITU-T recommendations, the alarm is classified into four severities: Critical, Major, Minor, and Warning.

Alarm Type Alarms are classified into six categories based on the network management standard: Communication, Processing, Equipment, Service, Environment, and Security.

AMI Alternate Mark Inversion. The line-coding format in transmission systems where successive ones (marks) are alternatively inverted (sent with polarity opposite that of the preceding mark).

Antistatic Floor The floor which is ESD preventive.

Asynchronous A network where transmission system payloads are not synchronized and each network terminal runs on its own clock.

ATM Asynchronous Transfer Mode. A transfer mode in which the information is organized into cells. It is asynchronous in the sense that the recurrence of cells containing information from an individual user is not necessarily periodic. It is a protocol within the OSI layer 1. An ATM cell consists of a 5 octet header followed by 48 octets of data.

Attenuation Reduction of signal magnitude or signal loss usually expressed in decibels.

Attenuator A passive component that attenuates an electrical or optical signal.

Attribute Property of an object.

Automatic Alarm Reporting

A function that is used to report the alarm to the LoopStar EMS as soon as it is generated at the equipment side. The LoopStar EMS pops up the alarm panel. The user can view this alarm information in the alarm panel without active query.

Automatic Protection Switching

The ability of a network element to detect a failed working line and switch the service to a spare (protection) line. 1+1 APS pairs a protection line with each working line. 1:n APS provides one protection line for every n working lines.

Auto Negotiation The algorithm that allows two devices at either end of a link segment to negotiate common data service functions.

The rate/work mode of the communication party set as self-negotiation is specified through negotiation according to the transmission rate of the opposite party.

Availability The foundation for many Bellcore reliability criteria is an end-to-end two-way availability of objective of 99.98% for interoffice applications (0.02% unavailability or 105 minutes/year down time). The objective for loop transport between the central office and the customer premises is 99.99%. For interoffice transport, the objective refers to a two-way broadband channel (e.g., SONET OC-N, over a 250-mile path). For loop applications, the objective refers to a two-way narrowband channel (e.g., DS0 or equivalent).

BBackplane A PCB circuit board in the subrack which is connected to all the units in position.

Back Up A method to copy the important data into a backing storage in case the original is damaged or corrupted.



Bandwidth Information-carrying capacity of a communication channel. Analog bandwidth is the range of signal frequencies that can be transmitted by a communication channel or network.

Bidirectional Line Switched Ring

A bidirectional ring that uses the line level status and performance parameters to initiate APS.

Bidirectional Ring A ring in which all nodes send and receive duplex traffic by traversing the same set of nodes for both directions of transmission under normal conditions. Thus, if a traffic from node "1" to node "2" is traveling clockwise, the traffic from "2" to "1" travels counterclockwise.

Binding In virtual concatenated payload configuration to specify one binding number to identify the VC4s of the same virtual concatenated payload. If a fault occurs to one of the bound services, all bound services will switch as a whole.

BIP BIP-X code is defined as a method of error monitoring. With even parity, an X-bit code is generated by the transmitting equipment over a specified portion of the signal in such a manner that the first bit of the code provides even parity over the first bit of all X-bit sequences in the covered portion of the signal, the second bit provides even parity over the second bit of all X-bit sequences within the specified portion, etc. Even parity is generated by setting the BIP-X bits so that there is an even number of 1s in each monitored partition of the signal. A monitored partition comprises all bits which are in the same bit position within the X-bit sequences in the covered portion of the signal. The covered portion includes the BIP-X.

Bit Error An error occurs to some bits in the digital code stream after being received, judged, and regenerated, thus damaging the quality of the transmitted information.

Bit Error Rate The number of coding violations detected in a unit of time, usually one second. Bit Error Rate (BER) is calculated with this formula:

BER = errored bits received/total bits sent.

BITS Building Integrated Timing Supply. A building timing supply that minimizes the number of synchronization links entering an office. Sometimes referred to as a synchronization supply unit.

BLSR Bidirectional Line Switched Ring. A bidirectional ring that uses the line level status and performance parameters to initiate APS.

Bound Path Also referred to as VC Trunk. The 2 Mbit/s paths which are bound together to transmit Ethernet data. The VC Trunk is an entity between the Ethernet port and the 2 M path.

Bridge The action of transmitting identical traffic (SPE contents) on both the working and protection channels.

Bridging Function The function residing in an ADM that adds traffic to a UPSR by which the ADM sends an identical copy of the added traffic in the same time slot on each outgoing fiber (in each direction around the ring). The ADM is said to be bridging the traffic.

Broadcast The act of sending a frame addressed to all stations on the network.



CCable Tie The tape usd to bind the cables.

Cabling The methods to route the cables or fibers.

Chain Network One type of network that all network nodes are connected one after one to be in series.

Channel The smallest subdivision of a circuit that provides a type of communication service; usually a path with only one direction.

Circuit A communications path or network; usually a pair of channels providing bi-directional communication.

CLEI Code Common Language Equipment Identification (CLEI) code. CLEI is trademark of Telcordia. A CLEI code list for each circuit pack or plug-in unit affixed to the modified product. The format of a CLEI code consists of ten alphanumeric characters apportioned to five data elements, Family, Subfamily, Features, Reference and Complemental.

Client A kind of terminal (PC or workstation) connected to a network that can send instructions to a server and get results through a user interface.

Clock Tracing The method to keep the time on each node being synchronized with a clock source in a network.

Coding Violation A transmission error detected by the difference between the transmitted and the locally calculated bit-interleaved parity.

Concatenate The linking together of various data structures (e.g., two bandwidths joined to form a single bandwidth).

Configuration Data The data that configures the NE hardware for coordination between this NE and other NEs in the entire network and for operation of specified services. Configuration data is the instruction file of NEs and it is a key element to ensure that the network runs efficiently. The typical configuration data includes board configuration, clock configuration and protection relationship.

Configure To set the basic parameters of an operation object.

Congestion The condition that exists in a network if the capacity needed for the instantaneous traffic exceeds the bandwidth available in the network.

Connection A “transport entity” which consists of an associated pair of “unidirectional connections” capable of simultaneously transferring information in opposite directions between their respective inputs and outputs.

Connection Point A reference point where the output of a trail termination source or a connection is bound to the input of another connection, or where the output of a connection is bound to the input of a trail termination sink or another connection. The connection point is characterized by the information which passes across it. A bidirectional connection point is formed by the association of a contradirectional pair.

Convergence The process of developing a model of the echo path which will be used in the echo estimator to produce the estimate of the circuit echo.



Conversion In the context of message handling, a transmittal event in which an MTA transforms parts of a message content from one encoded information type to another or alters a probe so it appears that the described messages were so modified.

CoS Class of Service. CoS keeps the priority mapping rules. It works in internal ports. CoS is even more important when there is congestion. The services at different levels are processed according to the corresponding priorities. The service with higher priority is processed first and the service with lower priority is discarded when the bandwidth is insufficient.

CTAG Correlation Tag. Limited to six ASCII characters that correlates an input command with its output response(s). Its value may be an identifier or a decimal numeral.

Current Alarms Alarms that have not been cleared or those that have been cleared, but are not acknowledged.

Current Performance Data

The performance data stored in the current register is called current performance data. The current 15-minute or 24-hour register (only one for each) is applied to collect the performance data in the current monitoring period. The performance data changed within the monitor period.

DDCF Dispersion Compensation Fiber. A kind of fiber which uses negative dispersion to

compensate for the positive dispersion of transmitting fiber to maintain the original shape of the signal pulse.

DCN Data Communication Network. A communication network within a TMN or between TMNs which supports the Data Communication Function (DCF).

DDF Digital Distribution Frame. A frame that is used to transfer cables.

Defect A limited interruption in the ability of an item to perform a required function.

Demultiplexing A process applied to a multiplex signal for recovering signals combined within it and for restoring the distinct individual channels of the signals.

Dense Wavelength Division Multiplexing

The higher capacity version of WDM, which is a means of increasing the capacity of fiber-optic data transmission systems through the multiplexing of multiple wavelengths of light. Commercially available DWDM systems support the multiplexing of from 8 to 40 wavelengths of light.

Digital Cross-Connect An electronic cross-connect which has access to lower-rate channels in higher-rate multiplexed signals and can electronically rearrange (cross connect) those channels.

Domain The domain of the LoopStar EMS specifies the scope of address or functions which are available to a certain user.

Drop The port on a network element where the service to an end customer may be connected (e.g., a tributary card on a SONET ADM). For example, a drop for a DS1 customer service may be provided by a VT1.5 card terminating a VT1.5 trail.

Drop and Continue The ability of a SONET add/drop multiplex to pass the same signal (STS/VT) that is being dropped onto the outgoing OC-N signal.



Drop-and-Continue Feature

A feature that allows traffic in a given time slot to enter the selector function at a node, and simultaneously be passed through the node in the same time slot without any alteration of the signal. This feature is required for broadcast services, dual-homed services, and protected ring interconnections. When used for protected ring interconnection, an add signal is simultaneously connected to the "non-continued" path without being bridged.

Dual-Fed A description of a ring that has entry nodes that add traffic to the ring via the bridging function.

DWDM Dense Wavelength Division Multiplexing. The technology utilizes the characteristics of broad bandwidth and low attenuation of single mode optical fiber, employs multiple wavelengths with specific frequency spacing as carriers, and allows multiple channels to transmit simultaneously in the same fiber.

EEC-1 Electrical Carrier level 1 (EC–1) – One designation for the electrical interface signal

that is the counterpart to the basic module in SONET, the STS–1.

EC-N Electrical Carrier level N.

Ejector Level A component at the two ends of the faceplate of a board which is used for inserting or removing the board.

Electrical Carrier Level 1

One designation for the electrical interface signal that is the counterpart to the basic module in SONET, the STS-1. In this document, the term "STS-1 electrical" is used instead of "EC-1".

Encapsulation In 1000BASE-X, the process by which a MAC packet is enclosed within a PCS code-group stream.

EPL Ethernet Private Line. An EPL service is a point-to-point interconnection between two UNIs without SDH bandwidth sharing.Transport bandwidth is never shared between different customers.

ESCON Enterprise System Connection. A path protocol which connects the host with various control units in an storage system. It is a serial bit stream transmission protocol. The transmission rate is 200 Mbit/s.

ESD Electrostatic Discharge. The phenomena the energy being produced by electrostatic resource discharge instantly.

ESD Jack Electrostatic discharge jack. A hole in the cabinet or subrack, which connect the subrack or cabinet to the insertion of ESD wrist strap.

Ethernet A data link level protocol comprising the OSI model’s bottom two layers. It is a broadcast networking technology that can use several different physical media, including twisted pair cable and coaxial cable. Ethernet usually uses CSMA/CD. TCP/IP is commonly used with Ethernet networks.

EVPL Ethernet Virtual Private Line. An EVPL service is a service that is both a line service and a virtual private service.

Exercise Switching This command tests whether a switching protocol can work normally without completing the actual switching operation.



Extra Traffic Unprotected traffic that is carried over the protection channels when not occupied by working traffic. The extra traffic may be preempted to provide transport capacity for protected or highly protected transport entities in the event of failure.

Eye Pattern A graphic presentation formed by the superimposition of the waveforms of all possible pulse sequences.

FFan Tray Assembly A module which contains fans used for heat dissipation.

Fault A fault is the inability of a function to perform a required action. This does not include an inability due to preventive maintenance, lack of external resources, or planned actions.

FC Fiber Channel. A standard of data storage network for transmitting signals at 100 Mbit/s to 4.25 Gbit/s over fiber or copper.

Fiber Cable The general name of an optical fiber and cable. The optical fiber transmits optical signals while the cable transmits electrical signal.

Fiber Connector A device mounted on the end of a fiber-optic cable, light source, receiver, or housing that mates to a similar device to couple light into and out of optical fibers. A connector joins two fiber ends, or one fiber end and a light source or detector.

Fiber Jumper The fiber which is used to connect the subrack with the ODF.

FICON Fiber Connect. A new generation connection protocol which connects the host with various control units. It carries single byte command protocol through the physical path of fiber channel and provides higher rate and better performance than ESCON.

Floating Mode A virtual tributary mode that allows the VT synchronous payload envelope to begin anywhere in the VT. Pointers identify the starting location of the VT SPE. VT SPEs in different superframes may begin at different locations.

Flow An aggregation of packets that have the same characteristics. On the LoopStar EMS or NE software, flow is a group of classification rules. On boards, it is a group of packets that have the same Quality of Service (QoS) operation. Currently, two flows are supported: port flow and port+VLAN flow. Port flow is based on port ID and port+VLAN flow is based on port ID and VLAN ID. The two flows cannot coexist in the same port.

Forced Switch This command performs ring switching from working channels to the protection channels. This switch occurs regardless of the state of the protection channels, unless the protection channels are satisfying a higher priority bridge request.

Frame A cyclic set of consecutive time slots in which the relative position of each time slot can be identified.



Free-Run Mode An operating condition of a clock, the output signal of which is strongly influenced by the oscillating element and not controlled by servo phase-locking techniques. In this mode, the clock has never had a network reference input or the clock has lost external reference and has no access to stored data that could be acquired from a previously connected external reference. Free-run begins when the clock output no longer reflects the influence of a connected external reference or transition from it. Free-run terminates when the clock output has achieved lock to an external reference.

Full Duplex Pertaining to both parties that can send and receive data at the same time on the communication link.

GGain The ratio between the optical power from the input optical interface of the optical

amplifier and the optical power from the output optical interface of the jumper fiber (expressed in dB).

Grooming Consolidating or segregating traffic for efficiency.

Grounding Resistance The resistance of the grounding bar.

Guide Rail A groove in the subrack which ensures the correct connection of a board to the backplane.

HHalf Duplex Pertaining to both parties that only one party can send data, while the other party can

only receive data on the communication link.

Hardware Loopback A method to use a fiber to connect the receiving optical interface with the transmitting one on a board. It performs transmission tests, which method usually does not require the assistance of personnel at the served terminal.

History Alarms Alarms that have been cleared and acknowledged.

IInput Jitter Tolerance For STS-N electrical interfaces, input jitter tolerance is the maximum amplitude of

sinusoidal jitter at a given jitter frequency, which when modulating the signal at an equipment input port results in no more than two errored seconds cumulative, where these errored seconds are integrated over successive 30 second measurement intervals.

IP over DCC The IP Over DCC follows TCP/IP telecommunications standards and controls the remote NEs through the Internet. The IP Over DCC means that the IP over DCC uses overhead DCC byte (the default is D1-D3) for communication.

Isolated Node A type of special logical system which does not belong to any protection subnet or SDH NNI. It is the node that has been configured on the NE side but cannot form (or has not formed) a corresponding protection subnet with other nodes. This node may be either an NE or a logical system on the NE.

Isolation A non-reciprocal optical device intended to suppress backward reflections along an optical fiber transmission line while having minimum insertion loss in the forward direction.



JJitter Short waveform variations caused by vibration, voltage fluctuations, control system

instability, etc.

Jitter Tolerance For STS-N electrical interfaces, input jitter tolerance is the maximum amplitude of sinusoidal jitter at a given jitter frequency, which results in no more than two errored seconds cumulative when the signal is modulated at an equipment input port. These errored seconds are integrated over successive 30 second measurement intervals. Requirements on input jitter tolerance as just stated are specified in terms of compliance with a jitter mask which represents a combination of points. Each point corresponds to a minimum amplitude of sinusoidal jitter at a given jitter frequency which results in two or fewer errored seconds in a 30 second measurement interval when the signal is modulated at the equipment input port. For the OC-N optical interface, it is defined as the amplitude of the peak-to-peak sinusoidal jitter applied at the input of an OC-N interface that causes a 1 dB power penalty.

LLabel A mark on a cable, a subrack or a cabinet for identification.

Laser The device that generates the directional light covering a narrow range of wavelengths. Laser light is more coherent than ordinary light. Semiconductor diode lasers are the used light source in fiber-optic system.

Layer A concept used to allow the transport network functionality to be described hierarchically as successive levels; each layer being solely concerned with the generation and transfer of its characteristic information.

LCAS Link Capacity Adjustment Scheme. A solution features flexible bandwidth and dynamic adjustment. In addition, it provides a failure tolerance mechanism which enhances the viability of virtual concatenations and enables the dynamic adjustment to bandwidth (non-service affecting).

Link A “topological component” that provides transport capacity between two endpoints in different subnetworks via a fixed (i.e., inflexible routing) relationship. The endpoints are “subnetwork termination point pools” for SONET and link termination points for ATM. Multiple links may exist between a pair of subnetworks. A link also represents a set of “link connections”.

Loopback The fault of each path on the optical fiber can be located by setting loopback for each path of the line.

LoopStar EMS The LoopStar EMS is a Subnet Management System (SNMS). In the telecommunication management network architecture, the LoopStar EMS is located between the NE level and network level which supports all NE level functions and part of the network level management functions.



MMAC Media Access Control. The data link sublayer that is responsible for transferring data to

and from the Physical Layer.

MAN Metropolitan Area Network. An IEEE-approved network that supports high speeds over a metropolitan area.

Management Information Base

The specification and formal description of a set of objects and variables that can be read and possibly written using the SNMP protocol. Various standard MIBs are defined by the IETF.

Manual Switch A type of protection switching. When the protection channel is efficient and there is no higher-level switching request, this mode switches the service from the working channel to the protection channel, thus testing whether network still has the protection capability.

Map/Demap A term for multiplexing, implying more visibility inside the resultant multiplexed bit stream than available with conventional asynchronous techniques.

Mapping A procedure by which tributaries are adapted into virtual containers at the boundary of an SDH network.

Mean Launched Power

The average power of a pseudo-random data sequence coupled into the fiber by the transmitter.

Mounting Bracket A component on the side of a subrack or a frame, which is used to install the subrack or frame in a cabinet.

MPLS Multiprotocol Label Switching. Multi-protocol label switching. It is a standard routing and switching technology platform, capable of supporting various high level protocols and services. The data transmission over an MPLS network is independent of route calculating. MPLS as a connection-oriented transmission technology guarantees QoS effectively, supports various network level technologies, and is independent of the link layer.

Multicast Transmission of a frame to stations specified by a group address.

Multiplex To transmit two or more signals over a single channel.

Multiplex Section Overhead

The multiplex section overhead comprises rows 5 to 9 of the SOH of the STM-N signal.

Multiplexer An equipment which combines a number of tributary channels onto a fewer number of aggregate bearer channels, the relationship between the tributary and aggregate channels being fixed.

Multiplexing A procedure by which multiple lower order path layer signals are adapted into a higher order path or the multiple higher order path layer signals are adapted into a multiplex section.



NNetwork Segment The range of IP addresses in which the gateway NE will operate.

Non-Revertive In non-revertive mode when a protection switch occurs, the working service will be switched to the protection service and the status will remain after it returns normal.

NRZ Non Return to Zero. A digital code in which the signal level is low for a 0 bit and high for a 1 bit and dose not return to 0 between successive 1 bits.

OOAM&P Operation, Administration, Maintenance and Provisioning (OAM&P) is a group of

management functions that provides system or network fault indication, performance monitoring, security management, diagnostic functions, configuration and user provisioning.

OC-1 The optical equivalent of an STS-1 signal.

OC-N The optical equivalent of an STS-N signal.

ONE Optical Network Element. A stand-alone physical entity in an optical transmission network that supports at least network element functions.

Optical Connector A component normally attached to an optical cable or piece of apparatus for the purpose of providing frequent optical interconnection/disconnection of optical fibers or cables.

Optical Interface A device to allow two or more corresponding optical transmitting units to be connected.

Overhead Extra bits in a digital stream used to carry traffic signals and other information. Orderwire, for example, would be considered overhead information.

Overhead Information Auxiliary Channel Overhead Information is information that may be transferred by an optical network layer but which does not by necessity have to be associated with a particular connection. An example of such an auxiliary channel is a data communications channel for the purposes of transferring management data between management entities. NOTE - These management entities are not trail termination and adaptation functions.

PPane A major separate area of a window or dialog box, usually used for display rather than

data entry.

Pass-Through The action of transmitting by a node exactly what is received by that node for any given direction of transmission. A pass-through can be unidirectional or bidirectional. For BLSRs, a pass-through refers to the K1 and the K2 bytes and the protection channels. Three types of pass-throughs are used in BLSRs: K byte pass-through, unidirectional full pass-through, and bidirectional full pass-through.

Path A logical connection between the point at which a standard frame format for the signal at the given rate is assembled and the point at which the standard frame format for the signal is disassembled.



Path Overhead Overhead accessed, generated, and processed by path-terminating equipment. Path overhead includes nine bytes of STS Path Overhead and when the frame is VT-structured, five bytes of VT Path Overhead.

Path Protection The working principle of path protection: When the system works in path protection mode, the PDH path uses the dual-fed and signal selection mode. Through the tributary unit and cross-connect unit, the tributary signal is sent simultaneously to the east and west lines. Meanwhile, the cross-connect matrix sends the signal dually sent from the opposite end to the tributary board through the active and standby buses, and the hardware of the tributary board automatically and selectively receive the signal from the two groups of buses automatically according to the AIS number of the lower order path.

Path Terminating Equipment

Network elements (i.e., fiber-optic terminating systems) which can access, generate, and process Path Overhead.

Payload The portion of the SONET signal available to carry service signals (i.e., DS1 and DS3). The contents of an STS SPE or VT SPE.

PDH Plesiochronous Digital Hierarchy. PDH is the digital networking hierarchy that was used before the advent of Sonet/SDH.

Performance Threshold

Performance events usually have upper and lower thresholds. When the performance event count value exceeds the upper threshold, a performance threshold-crossing event is generated; when the performance event count value is below the upper threshold for a period of time, the performance threshold-crossing event is ended. In this way, performance jitter caused by some sudden events can be shielded.

PIN PIN Photodiode. A semiconductor detector with an intrinsic (i) region separating the p and n-doped regions. It has fast linear response and is used in fiber-optic receivers.

PMU Power Monitor Unit. One type of power and environmental monitoring unit.

POH Path OverHead (see Path Overhead).

Pointer An indicator whose value defines the frame offset of a virtual container with respect to the frame reference of the transport entity on which it is supported.

Private Line Both communication parties are connected permanently.

Procedure A generic term for an action.

Process A generic term for a collection of actions.

Protection Path A specific path that is part of a protection group and is labeled protection.

Protection Service A specific service that is part of a protection group and is labeled protection.



Provisioning The process of making available various telecommunications resources (i.e., switching systems and transport facilities) for telecommunication services. Provisioning includes forecasting the demand for services, determining the additions or changes to the network that will be needed, determining where and when they will be needed, and installing all the necessary network elements to provide such services.

PVC Permanent Virtual Connection. Traditional ATM Permanent Virtual Connection that is established/released upon a request initiated by a management request procedure (that is all nodes supporting the connections need to be instructed by the network management).

RRAI Remote Alarm Indication. A code sent upstream in a DSn network as a notification that

a failure condition has been declared downstream. (RAI signals were previously referred to as Yellow signals.)

Receiver Overload Receiver overload is the maximum acceptable value of the received average power at point R to achieve a 1 x 10-10 BER.

Receiver Sensitivity Receiver sensitivity is defined as the minimum acceptable value of average received power at point R to achieve a 1 x 10-10 BER.

Reference Clock A clock of very high stability and accuracy that may be completely autonomous and whose frequency serves as a basis of comparison for the frequency of other clocks.

REG A device that performs regeneration.

Regeneration The process of receiving and reconstructing a digital signal so that the amplitudes, waveforms and timing of its signal elements are constrained within specified limits.

Revertive Switching In revertive switching, there is a working and protection line or unit. Services always revert back to the original working line or unit if the switch requests are terminated. When the working line or unit has recovered from the fault or the external request is cleared.

Ring Network One type of network that all network nodes are connected one after one to be a cycle.

Ring Segmentation When multiple ring switches are performed in response to multiple protection switch initiations, the original ring can be divided into two or more smaller rings. If more than a single pair of ring switches are performed on the original ring, the ring is said to be segmented.

Route The path a trail takes.

RS-232 In the asynchronous transfer mode, there is no hand-shaking signal. It can communicate with RS-232 and RS-422 of other stations in point-to-point mode and the transmission is transparent. Its highest speed is 19.2 kbps.



SS1 Byte The byte defined in ITU-T to transmit the network synchronization status information.

SD Signal Degrade (see Signal Degrade).

SDH Synchronous Digital Hierarchy. A hierarchical set of digital transport structures, standardized for the transport of suitably adapted payloads over physical transmission networks.

Section The portion of a SONET transmission facility including terminating points between (i) a terminal network element and a regenerator or (ii) two regenerators. A terminating point is the point after signal regeneration at which performance monitoring is (or may be) done.

Section Overhead Nine bytes of overhead accessed, generated, and processed by section terminating equipment. This overhead supports functions such as framing the signal and performance monitoring.

Section Terminating Equipment

Equipment that terminates the SONET Section layer. STE interprets and modifies or creates the Section Overhead.

Self-Healing Establishment of a replacement connection by network without the NMC function. When a connection failure occurs, the replacement connection is found by the network elements and rerouted depending on network resources available at that time.

Service Protection The measures to make sure the service transmitting is not to be damaged or corrupted.

Settings Parameters of an operation that can be selected by the user.

SF Signal fail (see Signal Fail).

SFP Small form-factor pluggable (see Small Form-Factor Pluggable).

Short Reach Short Reach (SR) optical interfaces refer to optical sections having system loss budgets from 0 db to 7 db. Depending on the SONET hierarchical level, SR transmitters may be either LEDs or low power Multi-Longitudinal Mode (MLM) lasers.

Signal Degrade A signal indicating the associated data has degraded in the sense that a Degraded Defect (dDEG) condition is active.

Signal Fail A signal indicating the associated data has failed in the sense that a near-end defect condition (not being the degraded defect) is active.

Simple Network Management Protocol

An IETF protocol for monitoring and managing systems and devices in a network. The data being monitored and managed is defined by a Management Information Base (MIB). The functions supported by the protocol are the request and retrieval of data, the setting or writing of data, and traps that signal the occurrence of events.



Small Form-Factor Pluggable

A specification for a new generation of optical modular transceivers. The devices are designed for use with Small Form-Factor (SFF) connectors and offer high speed and physical compactness, and are hot-swappable. SFP transceivers are expected to perform at data speeds of up to five gigabits per second (5 Gbit/s) and possibly higher. Because SFP modules can be easily interchanged, electro-optical or fiber optic networks can be upgraded and maintained more conveniently than has been the case with traditional soldered-in modules. Rather than replacing an entire circuit board containing several soldered-in modules, a single module can be removed and replaced for repair or upgrading. This can result in a substantial cost savings, both in maintenance and in upgrading efforts.

SONET Add-Drop Multiplexer

A Network Element that provides either one or two "high-speed" SONET interfaces, as well as "tributary" interfaces at one or more of the various rates supported in the digital network.

Span The set of SONET lines between two adjacent nodes on a ring.

Span Switching In a 4-fiber BLSR, the working and protection channels are carried over different lines. Thus a 4-fiber ring may allow protection similar to 1:1 point-to-point protection switching on individual spans. For failures that affect only the working channels (e.g., a single fiber cut), the restoration can be performed by switching the working channels to a different line carrying protection channels on the same span. Hereafter, when used in context with ring architectures, this type of switching is called span switching to avoid confusion. The actual protocol for span switching is part of the BLSR protocol and differs from the protocol used in point-to-point APS systems. Span switching is not applicable for 2-fiber BLSRs.

Squelching Traffic Replacing traffic by the appropriate path AIS to prevent misconnections. STS level squelching occurs only into and out of the protection channels (working channels are never squelched).

SSM Synchronization Status Message. ITU-T defines S1 byte to transmit the network synchronization status information. It uses the lower four bits of the multiplex section overhead S1 byte to indicate 16 types of synchronization quality grades.

STM-N Synchronous Transport Module. An STM is the information structure used to support section layer connections in the SDH. It consists of information payload and Section Overhead (SOH) information fields organized in a block frame structure which repeats every 125 ms. The information is suitably conditioned for serial transmission on the selected media at a rate which is synchronized to the network. A basic STM is defined at 155.520kbit/s.

Stratum Level of clock source used to categorize accuracy.

STS Path Overhead Nine evenly distributed Path Overhead bytes per 125 ms starting at the first byte of the STS SPE. STS POH provides for communication between the point of creation of an STS SPE and its point of disassembly.

STS-1 Synchronous Transport Signal Level 1 (see Synchronous Transport Signal Level 1).

STS-N Synchronous Transport Signal Level N (see Synchronous Transport Signal Level N).

STS-N Electrical Signal

The electrical interface signal that is the counterpart to an STS-N. An STS-N electrical signal may also be referred to as an EC-N signal.



Subnet The logical entity in the transmission network and comprises a group of network management objects. A subnet can contain NEs and other subnets. A subnet planning can enhance the organization of a network view.

Subnet Mask Also referred to as the network mask off code. It is used to define network segments so that only the computers in the same network segment can communicate with one another, thus suppressing broadcast storm between different network segments.

Support The frame on the bottom of a cabinet when installing the cabinet on the antistatic floor.

Switching Priority The rule that should be set when several protected boards need to be switched. If the switching priority of each board is set the same, the tributary board that fails later cannot be switched. The board with higher priority can preempt the switching of that with lower priority.

Synchronous A network where transmission system payloads are synchronized to a master (network) clock and traced to a reference clock.

Synchronous Digital Hierarchy

A hierarchical set of digital transport structures standardized for the transportation of suitably adapted payloads over physical (primarily optical) transmission networks.

Synchronous Payload Envelope

The major portion of the SONET frame format used to transport payload and STS path overhead. A SONET structure that carries the payload (service) in a SONET frame or virtual tributary. The STS SPE may begin anywhere in the frame’s payload envelope. The VT SPE may begin anywhere in a floating mode VT, but begins at a fixed location in a locked-mode VT.

Synchronous Transport Signal Level 1

The basic (functional) module used to build SONET signals. An STS-1 has a bit rate of 51.84 Mb/s, and may be converted to an OC-1 or STS-1 electrical interface signal, multiplexed with other modules to form a higher rate (STS-N) signal, or combined with other STS-1s to form an STS-Nc.

Synchronous Transport Signal Level N

A (functional) module used to build SONET signals. An STS-N has a bit rate of N’51.84 Mb/s, and may be converted to an OC-N or STS-N electrical interface signal, or multiplexed with other modules to form a higher rate signal (in which case it is referred to as an STS-M).

TTCP/IP Transmission Control Protocol/Internet Protocol. Common name for the suite of

protocols developed to support the construction of worldwide internetworks.

Test Access Test Access usually refers to DS1 and DS3 Test Access. Test access, a traditional DCS function, allows the user visibility into any VT1.5/STS-1 signal in the network. Test access aids users in turning up connections and in identifying faults in existing service connections. DMX supports two different types of test access. The non-intrusive method simply taps the VT1.5/STS-1 channel as it passes through the system and routes it to an external testing device. The more intrusive mode splits the VT1.5/STS-1 from the incoming signal and sends it to an external testing device. Test access facilitates DMX functioning in a DCS application.

TID Target Identifier. It is a destination code in the form of a valid simple or compound TL1 identifier or text string, limited to 20 characters, including the CLLI code.

Timeslot Single timeslot on an E1 digital interface (a 64-kbps, synchronous, full-duplex data channel) typically used for a single voice connection.



TL1 Transaction Language 1.A Telcordia Technologies machine-to-machine communications language that is a subset of ITU-TSS, formerly CCITT’s, human-machine language.

TMN Telecommunications Management Network. The entity which provides the means used to transport and process information related to management functions for the telecommunications network.

TPS Tributary Protection Switching. A function provided by the equipment is intended to protect N tributary processing boards through a standby tributary processing board.

Trail A type of transport entity mainly engaged in transferring signal from the input of the trail source to the output of the trail sink and monitoring the integrality of the transferred signal.

Tray A discal component in the cabinet which is used to place the chassis or other equipment.

Tributary Unit An information structure which provides adaptation between the lower order path layer and the higher order path layer. It consists of an information payload (the lower order VC) and a TU pointer which indicates the offset of the payload frame start relative to the higher order VC frame start.

UUID User Identifier (same as User-ID). It is the non-confidential identifier of a user

(i.e., a name, used to initiate a session).

Upper Threshold The critical value that can induce unexpected events if exceeded.

User The user of the LoopStar EMS client, and the user and password define the corresponding authority of operation and management of the LoopStar EMS.

User Group The set of NM users with the same management authorities. The default user group includes: system administrator, system maintainer, system operator and system supervisor. The attributes of user set include name and detailed description.

VVC Virtual Container (VC).

Virtual Concatenation The payload whose transmission bandwidth is bigger than VC4. Virtual concatenation combines multiple VC4 payloads (successive or non-successive) to form a virtual large structure VC4-Xv in cascade mode for transmission. The transmission of the broadband cascaded payload is implemented via the virtual cascade, thus improving the SDH transmission payload bandwidth capability from VC4 to VC4-4C.

VLAN Virtual local area network. A subset of the active topology of a Bridged Local Area Network. Associated with each VLAN is a VLAN Identifier (VID).

VT Path Remote Failure Indication

A signal applicable only to a VT1.5 with the byte-synchronous DS1 mapping, which is returned to the transmitting VT PTE upon declaring certain failures. The RFI-V signal was previously known as the VT Path Yellow signal.



WWavelength A means of increasing the capacity of fiber-optic data transmission systems through

the Division multiplexing of multiple wavelengths of light. WDM systems support the multiplexing Multiplexing of as many as four wavelengths.

WDM Wavelength Division Multiplexing (WDM). WDM technology utilizes the characteristics of broad bandwidth and low attenuation of single mode optical fiber, employs multiple wavelengths as carriers, and allows multiple channels to transmit simultaneously in a single fiber.

Working Path A specific path that is part of a protection group and is labeled working.

Working Service A specific service that is part of a protection group and is labeled working.

WTR Wait to Restore. This command is issued when working channels meet the restoral threshold after an SD or SF condition. It is used to maintain the state during the WTR period unless it is pre-empted by a higher priority bridge request.

WTR Time A period of time that must elapse before a – from a fault recovered – trail/connection can be used again to transport the normal traffic signal and/or to select the normal traffic signal from.

LPS800-UM-MAIN-04 D-1

DAppendixLOOPSTAR 800 ACRONYMS AND ABBREVIATIONS

A ABR Available Bit RateACE Adaptive Communication EnvironmentADM Add/Drop MultiplexerADSL Asymmetric Digital Subscriber LineAIC Application Identification ChannelAID Access IdentifierAIS Alarm Indication SignalAIS-L Line Alarm Indication SignalALS Automatic Laser ShutdownAM Administration ModuleAMI Alternate Mark Inversion CodeANSI American National Standard InstituteAP Span-Powered Access PointAPS Automatic Protection SwitchingASCII American Standard Code for

Information InterchangeASN.1 Abstract Syntax Notation OneATE ATM Terminating Equipment (SONET)ATM Asynchronous Transfer ModeAWG American Wire Gauge

B B-DCS Broadband Digital Cross ConnectsBER Bit Error RateBIOS Basic Input/Output SystemBIP Bit Interleaved ParityBITS Building Integrated Timing SupplyBLSR Bi-directional Line Switched RingBML Business Management LayerBOM Bill of MaterialsBPV Bipolar Violation

C CA Certificate AuthorityCAR Committed Access RateCD CD/CD-ROM or Carrier DetectCDE Common Desktop EnvironmentCLEI Common Language Equipment

Identifier (CLEI) code

CLNS Connectionless Network SystemCM Communication ModuleCMISE Common Management Information

Service ElementCO Central OfficeCORBA Common Object Request Broker

ArchitectureCoS Class of ServiceCPU Central Processing UnitCR Critical AlarmCSMA/CD Carrier Sense Multiple Access with

Collision DetectionCTS Clear To SendCUI Code User Interface

D DBCHG Database ChangedDC Direct CurrentDCBS Delta Committed Burst SizeDCC Data Communication ChannelDCF Data Communication Function or

Dispension Compensation FiberDCN Data Communication NetworkDDN Digital Data NetworkDHCP Dynamic Host Configuration ProtocolDLC Digital Loop CarrierDMBS Delta Maximum Burst SizeDN Distinguished NameDNI Dual Node InterconnectionDNS Domain Naming SystemDRI Dual Ring InterconnectionDSL Digital Subscriber LoopDSLAM Digital Subscriber Line Access

MultiplexerDSP Domain Specific Part FormatDSR Data Set ReadyDSSS Direct Sequence Spread SpectrumDTR Data Terminal ReadyDUS Do not use for timing synchronization


D-2 LPS800-UM-MAIN-04

DWDM Dense Wavelength Division Multiplexing

DXC Digital Cross Connect System

E EC-1 Electrical Carrier Level 1ECC Embedded Control ChannelEC-N Electrical Carrier Level NEFI Engineering, Furnishing, and

InstallationEFS Error-Free SecondEMC Electro Magnetic CompatibilityEMI Electro Magnetic InterferenceEML Element Management LayerEMS Element Management SystemEOS Ethernet Over SONETEPL Ethernet Private LineEPLAN Ethernet Private LANEPS Equipment Protection SwitchES Errored secondESCON Enterprise System ConnectionESD Electrostatic DischargeeSFP enhanced Small-Form Factor

PluggableEVPL Ethernet Virtual Private LineEVPLAN Ethernet Virtual Private LAN

F FAQ Frequently Asked QuestionsFCAPS Fault Management, Configuration

Management, Accounting Management, Performance Management, Security Management

FCS Frame Check SequenceFE Fast EthernetFEAC Far-End Alarm ControlFICON Fiber ConnectionFLASH FLASH memoryFPGA Field Programmable Gate ArrayFSVP Fiber Share Virtual PathFTP File Transfer Protocol

G GCM Global Cluster ManagerGE Gigabit Ethernet

GFP Generic Framing ProcedureGNE Gateway Network ElementGR Telcordia Generic RequirementsG.SHDSL Single-pair High-speed Digital

Subscriber LineGUI Graphic User Interface

H HA High-AvailabilityHDLC High-level Data Link ControlHTTP Hypertext Transfer ProtocolHTTPS Hypertext Transfer Protocol Secure

I IC Integrated CircuitIEEE Institute of Electrical and Electronics

EngineersIGMP Internet Group Management ProtocoliMAP Integrated Management Application

PlatformIP Internet ProtocolIR Intermediate ReachISDN Integrated Services Digital NetworkITU-T International Telecommunication

Union-Telecommunication Standardization Sector

IVL Independent Virtual Local Area Network Learning

L LAG Link Aggregation GroupLAN Local Area NertworkLAPS Line Automatic Protection SwitchingLBO Line Build-OutLCAS Link Capacity Adjustment SchemeLCS Leased Circuit ServiceLCT Local Craft TerminalLED Light Emitting DiodeLinear APS

Linear Automatic Protection Switching

LLC Logical Link ControlLOF Loss Of FrameLOP Loss Of PointerLOS Loss Of SignalLPBK LoopbackLPT Link Pass Through



LR Long ReachLSP Label Switch PathLTE Line Terminating Equipment

M MAC Media Access ControlMADM Multiple Add/Drop MultiplexerMAINT MaintenanceMAN Metropolitan Area NetworkMCF Message Communication FunctionMDI Multi-Document InterfaceMDP Message Dispatch ProcessMgr ManagerMIB Management Information BaseMIT Managed Object Instance TreeMJ MajorMLM Multi-Longitudinal Mode (laser)MLT Mechanized Loop TestingMML Man Machine LanguageMN MinorMO Managed ObjectMPLS Multiprotocol Label SwitchingMPPE Microsoft Point-to-Point Encryption

ProtocolMS Multiplex SectionMT Maintenance StateMTBF Mean Time Between FailuresMTIE Maximum Time Interval ErrorMUX Multiplexer

N NA Non-AlarmedNC Normal CloseNE Network ElementNEL Network Element LevelNEBS Network Equipment Building SystemNIC Network Interface CardNM Network ManagementNML Network Management LayerNMS Network Management SystemNO Normal Open

NP Network ProcessorNR Not ReportedNRZ Non Return to ZeroNSAP Network Services Access PointNT1 Network Termination Type-1

O OAM Operation Administration and Maintenance

OAM&P Operation, Administration, Maintenance and Provisioning

OC-1 Optical Carrier Level 1OC-N Optical Carrier Level NOEM Original Equipment ManufacturerOH OverheadOIF Optical Internetworking ForumONE Optical Network ElementORL Optical Return LossOSF Operation System FunctionOSI Open Systems InterconnectionOSP Outside PlantOSPF Open Shortest Path First

P PC Personal ComputerPDH Plesiochronous Digital HierarchyPE Provider EdgePGND Protection GroundPIR Peak Information RatePIU Power Interface UnitPLM Payload Label MismatchPM Performance ManagementPOH Path OverheadPOTS Plain Old Telephone ServicePP Path ProtectionPRBS Psuedo-Random Binary SequencePROV ProvisioningPRS Primary Reference SourcePST Primary StatePSTN Public Switched Telephone NetworkPTP Point-to-Point

Q QoS Quality of Service



R RADIUS Remote Authentication Dial-In ServiceRAM Remote Access MultiplexerRAI Remote Alarm IndicationRAS Remote Access ServerRDI Remote Defect IndicationRDMS Relational Database Management

SystemREG RegeneratorsRES Reserved for Network Synchronization

UseRIP Routing Information ProtocolRMA Return Material AuthorizationRMON Remote MonitoringRMS Root-Mean-SquareRPR Resilient Packet RingRS Regenerator SectionRTRV RetrieveRTS Request To SendRUP Rational Unified Process

S SCB Serial Communication BusSCC System Control and CommunicationSCSI Small Computer Systems InterfaceSD Signal DegradationSDBER Signal Degrade Bit Error RatioSDH Synchronous Digital HierarchySEFS Severely errored frame secondSEMF Synchronous Equipment Management

FunctionSES Severely Errored SecondSF Signal FailureSFF Small Form-FactorSFP Small Form-Factor PluggableSIF SONET Interoperability ForumSLM Single Longitudinal ModeSMC SONET Minimum ClockSML Service Management LayerSMS Service Management SystemSMTP Simple Mail Transfer ProtocolSN Sequence Number

SNCMP Sub-Network Connection Multiple Protection

SNCP Sub-Network Connection ProtectionSNML Sub-Network Management LayerSNMP Simple Network Management ProtocolSNMS Sub-Network Management SystemSOH Section OverheadSONET Synchronous Optical NETworkSPE Synchronous Payload EnvelopeSSC System Control and CommunicationSSID Service Set Identifier (Wireless

Network Name)SSL Secure Sockets LayerSSM Synchronization Status MarkerSSM Synchronization Status MessageSSR Side-mode Suppression RatioSST Secondary StateSTE Section Terminating EquipmentSTM Synchronous Transport ProtocolSTP Spanning Tree Protocol or Shielded

Twisted PairSTS Synchronous Transport SignalSTS-1 Synchronous Transport Signal Level 1STS-N Synchronous Transport Signal Level NSTU Sync Traceability UnknownSUPER SuperuserSVL Shared Virtual Local Area Network

Learning

T TACC Test AccessTAP Test Access PortTCM Tandem Connection MeasurementTC-PAM Trellis Coded Pulse Amplitude

ModulationTCP/IP Transmission Control Protocol/Internet

ProtocolTDEV Time DeviationTDM Time Division MultiplexTH Temperature HardenTID Target IdentifierTKIP Temporary Key Integrity ProtocolTL1 Transaction Language 1



TM Terminal MultiplexTMF Telecommunication Management

ForumTMN Telecommunication Management

NetworkTNC Transit Node ClockTOH Transport OverheadTPS Tributary Protection SwitchingTSGR Transport Systems Generic

RequirementsTTL Time To LiveTU Tributary Unit

U UAS Unavailable SecondsUBR Unspecified Bit RateUDP User Datagram ProtocolUID User IdentifierUML Unified Modeling LanguageUNEQ UnequippedUPS Uninterrupted Power SupplyUPSR Unidirectional Path Switched RingUTP Unshielded Twisted Pair

V VB Virtual BridgeVBLP Virtual Bridge Logical PortVC Virtual Circuit or Virtual ContainerVCG Virtual Concatenation GroupVCI Virtual Circuit IdentifierVCS Veritas Cluster ServerVID VLAN IdentifierVLAN Virtual Local Area NetworkVOD Video On DemandVPI Virtual Path IdentifierVPN Virtual Private NetworkVT Virtual TributaryVVR Veritas Volume ReplicationVxVM Veritas Volume Manager

W WAN Wide Area NetworkWDM Wavelength Division MultiplexingWECA Wireless Ethernet Compatibility

Alliance

WEP Wired Equivalent PrivacyWLAN Wireless Local Area NetworkWPA WiFi Protected AccessWSF Workstation FunctionWTR Wait-to-Restore

LPS800-UM-MAIN-04 E-1

EAppendixPRODUCT SUPPORTADC 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: 800.366.3891

Email: [email protected]

Technical Information, System/Network Configuration, Product Specification and Application, Training (product-specific), Installation and Operation Assistance, and Troubleshooting and Repair/Field Assistance

Online Technical Support: www.adc.com/Knowledge_Base/index.jspOnline Technical Publications: www.adc.com/documentationlibrary/

technicalpublications/Product Return Department: 800.366.3891

Email: [email protected]

ADC Return Material Authorization (RMA) number and instructions must be obtained before returning products.

Appendix E: Product Support

E-2 LPS800-UM-MAIN-04

Certification and WarrantyLimited WarrantyProduct warranty is determined by your service agreement. Refer to the ADC Warranty/Software Handbook foradditional information, or contact your sales representative or Customer Service for details.

ModificationsThe FCC requires the user to be notified that any changes or modifications made to this device that are notexpressly 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.

FCC Class A ComplianceThis equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference whenthe equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radiofrequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful inter-ference to radio communications. Operation of this equipment in a residential area is likely to cause harmful inter-ference in which case the user will be required to correct the interference at his own expense.

Safety Standards ComplianceThis 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

World HeadquartersADC Telecommunications, Inc.PO Box 1101Minneapolis, MN 55440-1101 USA

For Technical AssistanceTel: 800.366.3891

LoopStar® 800 Maintenance Manual

Document Number:

Product Catalog: LPS-FRM800-Lx

LPS800-UM-MAIN-04

´.Z$¶9S¨

1458049

lps800 810mtce maintenance

Documents