Loopstar 800 Series: System Administration Manual

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

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

01 October 22, 2004 Initial Release
02 November 8, 2004 Replaced iManager with Element
Management System (EMS) - globally.
03 July 27, 2005 Updated with LPS-800 Release 2 and
LPS-810 Release 1.
This manual is available online at ADC’s website (www.adc.com/documentationlibrary/) or you can order copies
of the manual by contacting your sales representative. Please ask for document LPS800-UM-ADMN-03.
Copyright
©2005 ADC Telecommunications, Inc. All rights reserved.
Trademark Information
ADC and LoopStar are registered trademarks of ADC Telecommunications, Inc. No right, license, or interest to such trade-
marks is granted hereunder, and you agree that no such right, license, or interest shall be asserted by you with respect to
such trademark.
Other product names mentioned in this practice are used for identification purposes only and may be trademarks or regis-
tered trademarks of their respective companies.
Disclaimer of Liability
Information contained in this document is company private to ADC Telecommunications, Inc. and shall not be modified,
used, copied, reproduced or disclosed in whole or in part without the written consent of ADC.
Contents herein are current as of the date of publication. ADC reserves the right to change the contents without prior notice.
In no event shall ADC be liable for any damages resulting from loss of data, loss of use, or loss of profits, and ADC further
disclaims any and all liability for indirect, incidental, special, consequential or other similar damages. This disclaimer of
liability applies to all products, publications and services during and after the warranty period.
Table of Contents
About This Manual ........................................................................................................xiii
Introduction ............................................................................................................................. xiii
Related Manuals ..................................................................................................................... xiii
Organization ............................................................................................................................ xiii
Intended Audience .................................................................................................................. xiv
Conventions ............................................................................................................................ xiv
Inspecting Your Shipment ........................................................................................................xv
Chapter 1: System Turn-Up ........................................................................................... 1-1
Before You Begin ..................................................................................................................... 1-1
Checking the Hardware Installation Enviroment ................................................................ 1-1
Environment for EMS Installation ....................................................................................... 1-2
Power and Grounding ........................................................................................................ 1-2
Unit Swapping .................................................................................................................... 1-4
Setting NE IP Address ....................................................................................................... 1-5
Logging into the NE .................................................................................................................. 1-6
Sending a Command to the NE ............................................................................................... 1-8
Using the GUI to Send a Command to the NE .................................................................. 1-8
Displaying Command Help ................................................................................................. 1-9
Chapter 2: User Administration .................................................................................... 2-1
User Accounts Types ............................................................................................................... 2-1
Retrieving User Information ..................................................................................................... 2-1
Configuration Command .................................................................................................... 2-2
Example ............................................................................................................................. 2-2
Creating User Accounts ........................................................................................................... 2-3
Example ............................................................................................................................. 2-3
Modifying a User’s Attributes ................................................................................................... 2-4
Example ............................................................................................................................. 2-4
Deleting a User ......................................................................................................................... 2-6
Example ............................................................................................................................. 2-6
Modifying User Passwords ....................................................................................................... 2-7
Disabling and Enabling User Accounts .................................................................................... 2-8
Example ............................................................................................................................. 2-8
LPS800-UM-ADMN-03 iii
Table of Contents July 27, 2005
Chapter 3: System Level Provisioning ......................................................................... 3-1

Provisioning NE IP Addresses ................................................................................................. 3-1
Retrieving an NE IP Address ............................................................................................. 3-1
Setting an NE IP Address .................................................................................................. 3-1
Retrieving an NE Subnet Mask .......................................................................................... 3-3
Setting an NE Subnet Mask ............................................................................................... 3-4
Provisioning Static Route for IP over DCC ............................................................................... 3-4
Creating a Static Route ...................................................................................................... 3-4
Deleting Static Route .......................................................................................................... 3-5
Retrieving a Static Route .................................................................................................... 3-6
Setting Date and Time .............................................................................................................. 3-6
Setting System Date and Time .......................................................................................... 3-6
Retrieving System Time ..................................................................................................... 3-7
Retrieving Time of Day ....................................................................................................... 3-8
Provisioning the Target Identifier (TID) ..................................................................................... 3-9
Retrieving TID .................................................................................................................... 3-9
Setting TID ......................................................................................................................... 3-9
Provisioning NE System Attributes ........................................................................................ 3-10
Editing NE Extended Attributes ........................................................................................ 3-10
Retrieving NE Extended Attributes ................................................................................... 3-10
Resetting a Unit .......................................................................................................................3-11
Retrieving NE Software Version ............................................................................................. 3-13
Retrieving Unit Version ........................................................................................................... 3-14
Timing ..................................................................................................................................... 3-15
Retrieve All Existing Clock Sources ................................................................................. 3-17
Setting the Reference Clock Priority Table ...................................................................... 3-17
Editing General NE Clock Attributes (Including Setting the SSM Protocol) ..................... 3-18
Setting Clock Source Attributes ....................................................................................... 3-20
Setting User Clock Source Switching ............................................................................... 3-22
Locking Out a Clock Source ............................................................................................. 3-23
Chapter 4: Protections ................................................................................................... 4-1
XO Unit Protection .................................................................................................................... 4-1
Fundamental Commands ................................................................................................... 4-1
Switching Operations ......................................................................................................... 4-3
Example ............................................................................................................................. 4-3
DSn Protection ......................................................................................................................... 4-4
Overview ............................................................................................................................ 4-4
Switching Operations ......................................................................................................... 4-6
Example ............................................................................................................................. 4-7
1+1 SONET Protection ............................................................................................................. 4-8
iv LPS800-UM-ADMN-03
July 27, 2005 Table of Contents
Overview ............................................................................................................................ 4-8

Switching Operations ....................................................................................................... 4-10
Example ........................................................................................................................... 4-10
UPSR Protection .................................................................................................................... 4-12
Fundamental Commands ................................................................................................. 4-12
Switching Operations ....................................................................................................... 4-16
Chapter 5: Cross-Connection ........................................................................................ 5-1
SONET Connections ................................................................................................................ 5-1
Before You Begin ............................................................................................................... 5-1
Before You Delete a Node .................................................................................................. 5-1
Retrieving Cross-Connections ................................................................................................. 5-2
Creating Unidirectional Cross-Connection ............................................................................... 5-3
Creating Unidirectional DS1 Traffic .................................................................................... 5-3
Creating Unidirectional DS3 Traffic .................................................................................... 5-4
Creating Unidirectional STS-N Traffic ................................................................................ 5-5
Creating Bidirectional Cross-Connection ................................................................................. 5-6
Creating Broadcast Traffic ........................................................................................................ 5-7
Deleting Uni-Directional Cross-Connection ............................................................................. 5-8
Deleting Unidirectional DS1 Traffic .................................................................................... 5-8
Deleting Unidirectional DS3 Traffic .................................................................................... 5-9
Deleting Unidirectional STS-N Traffic ............................................................................... 5-10
Deleting Bidirectional Traffic ....................................................................................................5-11
Deleting Bidirectional Cross-Connection Traffic ................................................................5-11
Deleting Broadcast Traffic ...................................................................................................... 5-13
Deleting Broadcast Cross-Connection Traffic .................................................................. 5-13
Chapter 6: Performance Monitoring ............................................................................. 6-1
Overview .................................................................................................................................. 6-1
Handling Performance Event ................................................................................................... 6-1
Before You Begin ............................................................................................................... 6-1
Handling Current Data ........................................................................................................ 6-2
Handling History Data ........................................................................................................ 6-3
Handling Thresholds .......................................................................................................... 6-4
Other Attribute Setting Commands .................................................................................... 6-5
Setting Performance Thresholds ........................................................................................ 6-6
Handling Ethernet ROM ........................................................................................................... 6-8
Retrieving RMON Performance State ................................................................................ 6-8
Enabling/Disabling RMON on Ethernet Port .....................................................................6-11
Handling RMON Parameters ............................................................................................6-11
Handling RMON History Data .......................................................................................... 6-13
LPS800-UM-ADMN-03 v
Chapter 7: Alarm Monitoring and Management .......................................................... 7-1

Retrieving Alarms and Conditions ............................................................................................ 7-1
Retrieving Alarms ............................................................................................................... 7-1
Retrieving History Alarms ................................................................................................... 7-3
Retrieving Conditions ......................................................................................................... 7-3
Setting and Receiving Attribute Alarms .................................................................................... 7-5
Setting Attribute Alarms ..................................................................................................... 7-5
Receiving Attribute of Alarms ............................................................................................. 7-6
Autonomous Reporting of Alarms ............................................................................................ 7-6
Allow Autonomous Messages Report ................................................................................ 7-7
Inhibit autonomous messages report ................................................................................. 7-8
Alarm Indication ........................................................................................................................ 7-8
Unit Indicator ...................................................................................................................... 7-8
Equipment-Level Indicator ................................................................................................. 7-8
Chapter 8: Unit Configuration ....................................................................................... 8-1
Before You Begin ..................................................................................................................... 8-1
Common Equipment Configuration .......................................................................................... 8-1
Retrieving Unit .................................................................................................................... 8-1
Retrieving Software Version ............................................................................................... 8-1
Creating Unit ...................................................................................................................... 8-2
Deleting Unit ....................................................................................................................... 8-2
Resetting Equipment .......................................................................................................... 8-3
DSn Facility Configuration ........................................................................................................ 8-4
Editing Path Parameters .................................................................................................... 8-4
Configuring Path Frame Format ......................................................................................... 8-4
Configuring IS/OOS ........................................................................................................... 8-5
Configuring Loopback of a Tributary Path .......................................................................... 8-6
OC-N Facility Configuration ..................................................................................................... 8-7
Bit Error Threshold ............................................................................................................. 8-7
Configuring J1 Byte ............................................................................................................ 8-8
Configuring C2 Byte ........................................................................................................... 8-9
Configuring Loopback for OC-N facilities ......................................................................... 8-10
Performing Laser Operations ............................................................................................8-11
vi LPS800-UM-ADMN-03
July 27, 2005 Table of Contents
Ethernet Facility Configuration ............................................................................................... 8-12

Configuring FE Port .......................................................................................................... 8-12
Configuring VCG .............................................................................................................. 8-14
Configuring Committed Access Rate (CAR) .................................................................... 8-15
Configuring Flow Control .................................................................................................. 8-16
Configuring Ethernet Link ................................................................................................. 8-16
Label Switch Path (LSP) .................................................................................................. 8-18
Appendix A: Product Support ..................................................................................... A-1
Glossary ......................................................................................................................GL-1
Certification and Warranty ..............................................................................................1
LPS800-UM-ADMN-03 vii
viii LPS800-UM-ADMN-03
List of Figures
Figure 1-1. PIU faceplate .................................................................................................... 1-3
Figure 1-2. Grounding flag .................................................................................................. 1-3
Figure 1-3. Input NE Management Tool IP Address ........................................................... 1-6
Figure 1-4. Input NE Management Tool username and password ..................................... 1-7
Figure 1-5. NE Management Tool connection prompt ........................................................ 1-7
Figure 3-1. IP address example for a simple network with chain ....................................... 3-2
Figure 3-2. IP address example for two networks interconnected by routers ..................... 3-3
Figure 3-3. LPS-8xx timing example ................................................................................. 3-15
Figure 3-4. BITS interface ................................................................................................. 3-16
Figure 7-1. System status panel ......................................................................................... 7-9
Figure 8-1. A typical unit configuration ................................................................................ 8-1
LPS800-UM-ADMN-03 ix
List of Figures July 27, 2005
x LPS800-UM-ADMN-03
List of Tables
Table 1-1. Requirement for temperature and humidity ........................................................ 1-1
Table 2-1. Default UIDs ........................................................................................................ 2-1
Table 3-1. Parameter description ....................................................................................... 3-13
Table 3-2. Parameter description ....................................................................................... 3-14
Table 3-3. List of user defined levels (RES) ....................................................................... 3-19
Table 3-4. The message of SSM generation 1 ................................................................... 3-21
Table 3-5. The message of SSM generation 2 ................................................................... 3-22
Table 4-1. The description of output parameter about active/standby state of XCS unit ..... 4-1
Table 4-2. The description of output parameter ................................................................... 4-2
Table 4-3. Description of external switching levels ............................................................ 4-18
Table 5-1. Cross-connection capacity .................................................................................. 5-1
Table 6-1. Fast Ethernet (FE) performance from RMON ..................................................... 6-9
Table 7-1. Alarm types and commands ................................................................................ 7-1
Table 7-2. Description of alarm parameters ......................................................................... 7-2
Table 7-3. Description of alarm severity levels ..................................................................... 7-2
Table 7-4. Condition retrieval commands ............................................................................. 7-3
Table 7-5. Description of condition parameters .................................................................... 7-4
Table 7-6. Description of alarm attribute parameters ........................................................... 7-5
Table 7-7. Autonomous message components .................................................................... 7-6
Table 7-8. Alarm codes ........................................................................................................ 7-7
LPS800-UM-ADMN-03 xi
List of Tables July 27, 2005
xii LPS800-UM-ADMN-03
ABOUT THIS MANUAL
INTRODUCTION
This manual applies to LoopStar® 800 Series hardware and software.
RELATED MANUALS
The following table lists the manuals in the LoopStar 800 Series (LPS-800/LPS-810) suite of documents. In this
document, the LoopStar 800 Series is designated as “LPS-8xx.” The current manual is highlighted.
Manual Usage
LoopStar® 800 Series System Administration Describes how to implement and use the LoopStar 800 for in a
Manual network management system (NMS).
LoopStar® 800 Series Installation Manual Describes how to install the LoopStar 800.
LoopStar® 800 Series Application and Acquaints you with the LoopStar 800 and describes how to build
Engineering Manual the required network using the LoopStar 800.
LoopStar® 800 Series Hardware Description Describes the LoopStar 800 system hardware including chassis,
Manual power interface module, fan tray assembly, plug-in units, and
the interfaces.
LoopStar® 800 Series TL1 Commands Detailed introduction to the TL1 commands used in the
Manual LoopStar 800.
LoopStar® 800 Series Maintenance Manual Describes how to perform routine maintenance and how to
troubleshoot the LoopStar 800 system.
LoopStar® 800 Series Alarm and Performance Describes alarm and performance monitoring.
Reference Manual
LoopStar® 800 Series Ordering Manual Provides a list of LoopStar 800 system hardware available
to order.
LoopStar® 800 Series EMS Description Introduces the application, functional characteristics, system
architecture, and networking mode of the LoopStar 800 EMS
appended with standards that the LoopStar 800 EMS complies
with, abbreviations and performance indices.
LoopStar® 800 Series EMS Installation Introduces installation procedures and FAQs of the LoopStar 800
Manual EMS running on Windows 2000 and Solaris 8 platforms.
LoopStar® 800 Series EMS Operations Introduces configuration and maintenance operations of
Manual LoopStar 800 EMS.
ORGANIZATION
This manual includes the following chapters:
Chapter Description
Chapter 1: System Turn-Up Explains how to log in to the LoopStar 800 and turn it up
for service.
Chapter 2: User Administration Explains how to manage the LoopStar 800 Series user
accounts, the software, and its database.
LPS800-UM-ADMN-03 xiii
About This Manual July 27, 2005
Chapter Description
Chapter 3: System Level Provisioning Describes how to provision system-level attributes, such as
IP addresses, target identifiers (TID), system date/time,
and timing.
Chapter 4: Protections Introduces how to provision SONET line protection, DSn
protection, and UPSR.
Chapter 5: Cross-Connection Explains how to provision the unidirectional connection,
bidirectional connection, and broadcast traffic.
Chapter 6: Performance Monitoring Offers the following operations: on-line monitoring of multiple
managed NEs, collecting performance data of network and
equipment, generating historical data of performance
monitoring, threshold setting and threshold-crossing
notification and performance data reporting, and so on.
Chapter 7: Alarm Monitoring and Management Introduces how to monitor and manage alarms.
Chapter 8: Unit Configuration Explains how to configure the LoopStar 800, including
common equipment, DSn facility, OC-N facility, and the
Ethernet facility.
INTENDED AUDIENCE
This manual is intended for:
• System Administrators
CONVENTIONS
The following style conventions and terminology are used throughout this guide.
Element Meaning
Bold font Text that you must input exactly as shown (e.g., type 1 for card 1), menu buttons
(e.g., ACCEPT SHELF OPTIONS) or menu screen options (e.g., ALARMS screen) that
you must select
Italic font Variables that you must determine before inputting the correct value (e.g., Password )
Monospace font References to screen prompts (e.g., Invalid Password...Try Again:.)
Reader Alert Meaning

Alerts you to supplementary information
IMPORTANT Alerts you to supplementary information that is essential to the completion of a task
!
Alerts you to possible equipment damage from electrostatic discharge
ATTENTION
CAUTION Alerts you to possible data loss, service-affecting procedures, or other similar type
problems
xiv LPS800-UM-ADMN-03
July 27, 2005 About This Manual
Reader Alert Meaning

Alerts you that failure to take or avoid a specific action might result in hardware damage or
WARNING
loss of service
DANGER
Alerts you that failure to take or avoid a specific action might result in personal harm
INSPECTING YOUR SHIPMENT

Upon receipt of the equipment:
• Unpack each container and visually inspect the contents for signs of damage. If the equipment has been dam-
aged in transit, immediately report the extent of damage to the transportation company and to ADC. Order
replacement equipment, if necessary.
• Check the packing list to ensure complete and accurate shipment of each listed item. If the shipment is short
or irregular, contact ADC as described in Appendix A: Product Support on page A-1. If you must store the
equipment for a prolonged period, store the equipment in its original container.
LPS800-UM-ADMN-03 xv
About This Manual July 27, 2005
xvi LPS800-UM-ADMN-03
Chapter 1
SYSTEM TURN-UP
This chapter describes how to turn-up the LPS-8xx system. It consists of the following components:
• Before You Begin
• Logging into the NE
• Sending a Command to the NE
• Creating User Accounts (see “Creating User Accounts” on page 2-3).
BEFORE YOU BEGIN

Checking the Hardware Installation Enviroment
Purpose To specify the hardware installation environment

Required tools/equipment None
Prerequisite procedures None
Required/as needed None
Location Onsite
As precise electronic apparatus, communication equipment can provide long term normal operation only in a dust-
proof, water-proof and antistatic environment that is within the specified temperature and humidity ranges. So the
communication equipment room is required to be equipped with appropriate devices (such as air conditioner and
humidifier) to maintain temperature and humidity within specifications.
It is also required to provide a dust-proof, water-proof and antistatic facility with reliable grounding devices.
The basic environment requirements for the equipment operation are given below:
• The working DC voltage for the LPS-8xx is –48 V +/– 20% (the permitted voltage range is –38.4V
to –57.6V).
The DC power distribution system should be protected against power failure by equipping the storage battery.
A diesel generator should be provided as the standby power source to protect against power failure for longer
periods of time.
• Good grounding of the equipment.
• Requirements for the temperature and humidity are listed in Table 1-1.
Table 1-1. Requirement for temperature and humidity

Working condition Temperature Relative humidity
Long term operation 0°C to 45°C (32°F to 113°F) 10% to 90%
Short term operation –5°C to 50°C (23°F to 131°F) 5% to 95%
LPS800-UM-ADMN-03 1-1
Chapter 1: System Turn-Up July 27, 2005
According to the indices in Table 1-1 on page 1-11, air conditioning is required in the communication equipment
room and all the fans installed in the LPS-8xx system should be in operation. It is recommended that the
temperature of the equipment room be kept at about 20°C, and the humidity at about 60%.
• Good ventilation of the equipment
Fans are required to run normally (except during fan cleaning) when the equipment works normally. Turning
off the fans will result in rising temperatures of the equipment and possibly damage the unit.
• Do not block the ventilation openings and remember to clean/replace the air filter periodically.
Environment for EMS Installation
Purpose To define element management system (EMS)

installation requirements
Prerequisite procedures None
Location Onsite
Acquire an appropriately sized computer desk to hold the computer, keyboard, mouse, and printer.
• Select a place away from any heat source, dampness, and dust for installing the system and do not expose
the computer to direct sunlight. Preserve a space of at least 8 cm between the back of the computer and other
objects for good ventilation. Smoke is not allowed in the equipment room.
• Configure the UPS
The workstation must be equipped with UPS to prevent damages to the operation system during accidental
power failure. UPS is recommended for the PC to prevent loss of any alarm and performance event data due
to power failure of the computer. Both the computer and the UPS system shell should be grounded.
• The computer should be positioned away from other electronic equipment which could cause electromagnetic
interference.
• For additional requirements for the computer system, refer to the attached manual.
Power and Grounding
Purpose Ensure power access and grounding mode of the

equipment are correct.
Prerequisite procedures Hardware installation has been done
Location Onsite
Ensure that the equipment is connected to the proper power supply source to avoid damage due to inappropriate
voltage.
The power interface unit (PIU) of the LPS-8xx is installed at the rear panel of the chassis. The faceplate of the PIU is
shown in Figure 1-1. The equipment supports two PIUs for redundancy. The “–48 V” accesses the –48 V power and
“RTN” connects with the power ground.
Before accessing the power, the external voltage should be measured to see whether it is –48 V or not. If the power
supply is connected improperly, equipment cannot be powered on or work normally.
1-2 LPS800-UM-ADMN-03
July 27, 2005 Chapter 1: System Turn-Up
Figure 1-1. PIU faceplate
To avoid electrostatic inference during equipment operation, a grounding flag is provided at the right side of the
chassis, as shown in Figure 1-2.
Figure 1-2. Grounding flag
Any one of the above three round wire posts can be used for grounding. However, the grounding cable is required to
prevent service interruption due to electrostatic interference during the operation.
Unit Swapping
Purpose Making sure the user can insert or remove the

unit into/from the chassis correctly
Required tools/equipment ESD wrist strap, Phillips screwdriver
Required/as needed Unit hardware
Location Onsite
Removing the Unit
CAUTION Always use the supplied ESD wrist strap when working with any LPS-8xx units. Plug the wrist
strap cable into the ESD jack located on the system status panel.
Step Action
1 Loosen the fastening screws on both sides of the faceplate.
2 Open the ejectors.
3 Grasp the ejectors and gently pull the unit out of the slot.
Inserting the Unit
Step Action
1 Make sure the slot is correct for the unit.
2 If there are several units to be installed, insert them from top to bottom and from left to right. If the blank
filler faceplate obstructs your view, you can uninstall and then reinstall it after the units are inserted
properly.
3 When you insert the unit, push it along the left and right guide rails to the bottom of the slot with the flutes
of the ejectors aligning with both edges of the chassis. Now, the unit is partially inserted.
Note: Partial insertion means that the unit is already in the appropriate slot, but its connector has
no contact with the backplane socket. In fact, the unit is still unplugged.
4 Make sure the unit connector aligns with the backplane socket, and then push the unit faceplate with
moderate force to seat it in the slot. If hindrance is felt during insertion, do not force it; instead, adjust its
position and try again.
5 When the unit connector matches that of the backplane perfectly, close the ejectors of the faceplate until
the unit is installed properly. Then, fasten the locking screws.
Setting NE IP Address
Purpose Setting the IP address of the NE

Required/as needed Unit hardware
Location Onsite
For applicable commands, refer to Chapter 3: System Level Provisioning in this manual and the LPS-800 Series
TL1 Commands Manual, catalog number LPS800-UM-COMM.
Note: After modifying the IP Address, the NE should be restarted manually.
LOGGING INTO THE NE

Purpose Ensuring the user can access the NE and
perform simple configuration
Required tools/equipment NE management tool
Prerequisite procedures IP address of the NE is set and the NM is
connected with the NE through network cable
Required/as needed Making sure the NM is connected with the NE
Location Onsite/Remote
Step Action
1 Run the NE management tool.
2 Fill in the local and NE IP and port number (see Figure 1-3). The Local IP Address is the computer’s IP
address, set up by the user before making a connection with the NE. The NE IP Address is the IP
address known or set up in “Setting NE IP Address” on page 1-5. It also should be set by the user prior to
making connection with the NE. The port number is 23. If you do not know the NE IP address, click
Search to find it.
Figure 1-3. Input NE Management Tool IP Address
Step Action
3 Click Connect. The prompt “Connection Succeed” is returned. Input the Username and Password to log
on to the NE.
Figure 1-4. Input NE Management Tool username and password

4 Click OK. The following prompt is returned. You now can operate the equipment.
Figure 1-5. NE Management Tool connection prompt
SENDING A COMMAND TO THE NE

Purpose Enabling the user to send command to
NE for service management
Prerequisite procedures Log into the NE
Required/as needed Configuration file is ready
Using the GUI to Send a Command to the NE

Input the command in the input windows and press ENTER; the command will be sent to the NE. The command
will take effect at the NE side and be issued to the corresponding unit.
For example: ACT-USER::SONET:100::SONET
A command is processed successfully if a “COMPLD” response is returned:
>ACT-USER::SONET:100::SONET
SONET-NE 2004-12-06 13:58:30
M 100 COMPLD
"Last log time : 2004-12-06 13:43:05"
;
A command is not processed successfully if a “DENY” response plus error message is returned:
>RTRV-USER:::100;
SONET-NE 2004-12-06 14:02:19
M 100 DENY
ICNV
/*COMMAND NOT VALID,UNSUPPORTED COMMAND:RTRV-USER*/
;
Note: Do not forget to enter a semicolon (;) at the end of each command; otherwise the command will not
be executed.
Displaying Command Help

The LPS-8xx provides a help command to display command syntax.
Command
RTRV-INMSG-ALL:[<TID>]::<CTAG>::[<MsgCategory>];
Significant parameter
MsgCategory: KeyWord Type, Default Value:ALL
Example
RTRV-INMSG-ALL:::100::ALL;
If you only know the command name but not the specific parameters, add a semicolon (;) at the end of the
command and the correct command format together with an example of the command will be displayed.
For example, the parameter of ACT-USER is unknown. Perform the following operation:
ACT-USER:;
The information returned will present you with the correct command format:
SONET-NE 2004-12-06 14:10:31
M 0 DENY
IISP
/*INVALID SYNTAX OR PUNCTUATION*/
/*Format:ACT-USER:[<TID>]:<UID>:<
UID: string, max length is 16.
PID: string, max length is 16;
SAMPLE:
ACT-USER::USERNAME:100::PASSWORD;
*/;
Chapter 2
USER ADMINISTRATION
This chapter describes how to create and manage user accounts. It consists of the following components:
• User account types
• Creating user accounts
• Modifying user account attributes
• Deleting user accounts
• Modifying user passwords
• Obtaining user account information
• Disabling and enabling user accounts
USER ACCOUNTS TYPES

The default user identifiers (UID) are listed in Table 2-1:
Table 2-1. Default UIDs

UID Description Security level
root The default user of the network management system (NM) and super user
can only be used to log in to the NE through the NM.
SONET The default user of TL1 and can be only used to log in to the super user
NE through the TL1 terminal.
Four security levels of user accounts are listed below from low to high: retrieving, provisioning, maintenance, and
super user.
The security level defines a user’s authority. The user name is not case sensitive, and the default UIDs cannot be
changed.
RETRIEVING USER INFORMATION

Purpose Retrieving information on all users in the NE
Prerequisite procedures Connect and log in to the NE as a super user
Required/as needed User with security level of “retrieving”
Chapter 2: User Administration July 27, 2005
Configuration Command
The information about all NE users can be retrieved. The command is as follows.
Command
RTRV-USER-SECU:[<TID>]:[<UID>]:<CTAG>;
Important parameter
UID: If UID is specified only that user’s information will be retrieved.
If no user identifier is given, the data of all the users will be retrieved (you should
operate as the supper user, otherwise the error message will be returned).
Example
Step Action
1 Log into the NE as an existing user. For example, log in as user SONET:
ACT-USER::SONET:100::SONET;
2 Enter the command:
RTRV-USER-SECU:::100;
If the following response is received, modification was successful:
LOOPSTAR800 2004-12-06 14:20:51
M 100 COMPLD
"root:,SUPER:TMOUTEN=ENABLE,TMOUTLN=60,PAGE=0,UAGE=0,USTATE=I
NACT&ALW&UIDUNEXP&PIDUNEXP"
"lct:,SUPER:TMOUTEN=ENABLE,TMOUTLN=60,PAGE=0,UAGE=0,USTATE=IN
ACT&ALW&UIDUNEXP&PIDUNEXP"
"snmpuser:,SUPER:TMOUTEN=ENABLE,TMOUTLN=60,PAGE=0,UAGE=0,USTA
TE=INACT&ALW&UIDUNEXP&PIDUNEXP"
"sonet:,SUPER:TMOUTEN=ENABLE,TMOUTLN=60,PAGE=0,UAGE=0,USTATE=
ACT&ALW&UIDUNEXP&PIDUNEXP"
"T2000:,SUPER:TMOUTEN=ENABLE,TMOUTLN=60,PAGE=0,UAGE=0,USTATE=
INACT&ALW&UIDUNEXP&PIDUNEXP"
July 27, 2005 Chapter 2: User Administration
CREATING USER ACCOUNTS

Purpose Creating a user account
Required/as needed Authority of an existing user satisfies the
requirement for creating a user.
Use the following command to create a user account in the LPS-8xx:
Command
ENT-USER-SECU:[<TID>]:<UID>:<CTAG>::<PID>,,<UPC>:[TMOUTEN=
<TMOUTEN>],[TMOUTLN=<TMOUTLN>],[PAGE=<PAGE>],[UAGE=<UAGE>];
Important parameter
Please refer to the LoopStar 800 Series TL1 Commands Manual, catalog number
LPS800-UM-COMM, for a detailed description of this command.
Example
Create a user “ADC” with password “PASS_WORD” and a security level of maintenance.
Step Action
1 Log in to the NE as an existing user.
For example, log in the NE as user SONET and enter:
ACT-USER::SONET:100::SONET
Note: If using port 23, the login process will be interactive.
2 Enter the following command:

ENT-USER-SECU::ADC:123::PASS_WORD,,MAINT;
If the following response is received, the user name has been created successfully:
LOOPSTAR800 2003-01-27 11:54:19
M 123 COMPLD
;
3 To verify if the user account name has been created, use the following command:
If successful, the returned information will include the newly created user.
MODIFYING A USER’S ATTRIBUTES

Purpose Modifying user attributes
Required/as needed User to be modified already exists
Note: You cannot change the UID and other attributes at the same time. You cannot change the name,
valid time, and user level of a default UID. You also cannot change the online UID.
Sometimes a user’s attributes need to be modified. The following command shows how:
Command
ED-USER-SECU:[<TID>]:<UID>:<CTAG>::[NEWUID=<NEWUID>],[NEWPID=
<NEWPID>],[UPC=<UPC>]:TMOUTEN=[<TMOUTEN>],TMOUTLN=
[<TMOUTLN>],PAGE=[<PAGE>],UAGE=[<UAGE>];
Important parameter
Refer to the LoopStar 800 Series TL1 Commands Manual, catalog number
Example
Modify the user name ADC to TESTUSER.
Step Action
1 Log in to the NE as user SONET and enter:
Step Action
2 Verify the user ADC exists. Enter the following command:
The following will be displayed:
LOOPSTAR800 2003-01-27 11:59:52
M 60 COMPLD
“ROOT:,SUPER:TMOUTEN=ENABLE,TMOUTLN=60,PAGE=0,UAGE=0,USTATE=
INACT&ALW&UIDUNEXP&PIDUNEXP”
“SNMPUSER:,SUPER:TMOUTEN=ENABLE,TMOUTLN=60,PAGE=0,UAGE=0,
USTATE=INACT&ALW&UIDUNEXP&PIDUNEXP”
“SONET:,SUPER:TMOUTEN=ENABLE,TMOUTLN=60,PAGE=0,UAGE=0,USTATE=
ACT&ALW&UIDUNEXP&PIDUNEXP”
“ADC:,MAINT:TMOUTEN=ENABLE,TMOUTLN=60,PAGE=0,UAGE=0,
USTATE=INACT&ALW&UIDUNEXP&PIDUNEXP”
;
It indicates that the user ADC does exist.
ED-USER-SECU::ADC:100::NEWUID=TESTUSER;
If the following response is received, modification is successful:
LOOPSTAR800 2003-01-27 14:20:03
M 100 COMPLD
;
4 The following can be used to verify the whether the modification was successful:
Retrieve the user.
Note:
• Step 2 and Step 4 in the above operations are not mandatory, but are recommended to ensure the
successful modification. The new password is a string; its length is from 6 to 16, and it must include at
least one alphabetical character (A to Z) and one non-alpha character (such as, ], &, *, and so on).
• You cannot modify the user name, the time in which the user’s name is in effect, or the user’s level if
the target user is the default user for the NE.
• The command cannot modify the current user’s PID. To modify the current user’s (your own)
password, use the ED-PID command.
• The user name, with a length from 4 to 16, must include at least one alphabetical character, and
cannot include commas (,), colons (:), or semi-colons (;). Further, it cannot be the same as the name
which already exists for the NE.
DELETING A USER
Purpose Delete a user
Required/as needed User to be deleted exists
Deleting a user can only be done by a super user.
Command
DLT-USER-SECU:[<TID>]:<UID>:<CTAG>;
Important parameter
UID: User name, no more than sixteen characters in length.
Note: You cannot delete the default user and the online user.
Example
To delete an existing user TESTUSER, perform the following procedure:
Step Action
For example, log in the NE as user SONET and enter:
DLT-USER-SECU::TESTUSER:100;
If the following response is received, deletion was successful:
LOOPSTAR800 2003-01-06 14:40:49
M 100 COMPLD
;
To verify whether the user has been deleted, go to Step 3.
3 Use the following command to verify whether deletion was successful.
If deletion was successful, the deleted user will not be listed in the response.
MODIFYING USER PASSWORDS

Purpose Modify user password
Required/as needed User with password to be modified exists
Two commands are provided to change passwords. The first can be used when a user changes his own password.
The second can be used when a super user changes another user’s password.
Command
A user changes his own password:
ED-PID:[<TID>]:<UID>:<CTAG>::[<PID>],<NEWPID>;
Note: When the user changes his password, he must input the
original password.
Modify another user’s password:

ED-USER-SECU:[<TID>]:<UID>:<CTAG>::[<NEWUID>],[<NEW
PID>],,[<UPC>]:TMOUTEN=[<TMOUTEN>],TMOUTLN=[<TMOUTLN>],PA
GE=[<PAGE>],UAGE=[<UAGE>];
Note: When the administrator (super user) changes another
user’s password, he need not input the original password to set
a new password. But the administrator cannot change the
password of an online user.
Important parameter
LPS800-UM-COMM, for detailed description of these commands.
Example
Modify the password of SONET to 800PASS:
Step Action
ED-PID:::100::SONET,800PASS;
If the following response is received, modification was successful:
LOOPSTAR800 2003-01-27 14:43:07
M 100 COMPLD
;
Modify the password of user ADC to HAPPY_NEW_YEAR as user SONET:
Step Action
ED-USER-SECU::ADC:123::NEWPID=HAPPY_NEW_YEAR;
If the following response is received, modification is successful:
LOOPSTAR800 2003-01-27 15:32:07
M 123 COMPLD
;
DISABLING AND ENABLING USER ACCOUNTS

Purpose Disabling/Enabling the user accounts
Required/as needed User accounts to be operated do exist
The command is as follows:
Command
Disable the user accounts:
INH-USER-SECU:[<TID>]::<CTAG>::<UID>;
Enable the user accounts:
ALW-USER-SECU:[<TID>]::<CTAG>::<UID>;
Important parameter
Null
Example
Disable the accounts of user ADC:
Step Action
INH-USER-SECU:::100::ADC;
If the following response is received, operation was successful:
LOOPSTAR800 2003-01-06 17:30:23
M 100 COMPLD
;
Enable the accounts of user ADC:
Step Action
ALW-USER-SECU:::100::ADC;
If the following response is received, operation was successful:
LOOPSTAR800 2003-01-06 17:33:04
M 100 COMPLD
;
Chapter 3
SYSTEM LEVEL PROVISIONING
This chapter describes basic provisioning at the system level. It consists of the following components:
• Provisioning NE IP addresses
• Provisioning a static route for an IP over DCC
• Setting the date and time
• Provisioning the TID
• Provisioning NE extended attributes
• Software reset of an XO unit
• Retrieving a unit version
• Timing
PROVISIONING NE IP ADDRESSES
This section describes how to determine the IP addresses and provision them.
Retrieving an NE IP Address
Purpose Retrieve the current IP address of the NE.

Prerequisite procedures Connect and log in to the NE
Required/as needed As needed
To retrieve the NE IP address in the LPS-8xx, use the following command.
Command
RTRV-LAN:[<TID>]:[<AID>]:<CTAG>;
Important parameter
Null
Example
RTRV-LAN:::100;
Setting an NE IP Address
Purpose Set the IP address of the NE

Prerequisite procedures Connect and log into the NE as a maintenance
user or a higher level user
Chapter 3: System Level Provisioning July 27, 2005
To set the NE IP address in the LPS-8xx, use the following command.
Command
ED-LAN:[<TID>]:<AID>:<CTAG>:::[IP=<IPADDR>,][MASK=<SUBNETMASK>,]
[ENABLE=<ENABLE>];
Important parameter
IPADDR: IP address of the network element. 32-bit address consisting of four
dot-separated decimal numbers ranging from 0 to 255.
SUBNETMASK: The subnet mask.
Example
ED-LAN::LAN-1:100:::IP=129.9.0.53,MASK=255.255.0.0,ENABLE=Y;
Note: Before setting the IP address, make sure the IP address of your operating terminal (usually a PC) is
different from that of the NE to be set.
Before modifying the IP address on NE side, make sure the IP over DCC route for this NE is deleted
(refer to “Deleting Static Route” on page 3-5).
If the NEs are in the same simple transport network (Figure 3-1), set different IP addresses for the
different NEs. NEs. Incorrect settings may make communication of these NEs abnormal.
If NEs are in different transport network, for example two networks interconnected by routers
(Figure 3-2), set different IP address for the different networks. Incorrect settings may make communication
of these NEs abnormal.
After modifying the IP Address, it is recommended to restart the NE manually.
Figure 3-1. IP address example for a simple network with chain
July 27, 2005 Chapter 3: System Level Provisioning
Figure 3-2. IP address example for two networks interconnected by routers
Retrieving an NE Subnet Mask
Purpose Retrieve the current subnet mask of the NE.

To retrieve the NE subnet mask in the LPS-8xx, use the following command.
Command
RTRV-LAN:[<TID>]:[<AID>]:<CTAG>;
Important parameter
Null
Example
RTRV-LAN:::100;
Note: You can retrieve the IP address and subnet mask with the same command: RTRV-LAN:::100;
Setting an NE Subnet Mask
Purpose Set the current subnet of the NE

Prerequisite procedures Connect and log in to the NE as a maintenance
To set the NE subnet mask in the LPS-8xx, use the following command.
Command
ED-LAN:[<TID>]:<AID>:<CTAG>:::[IP=<IPADDR>,][MASK=
<SUBNETMASK>,][ENABLE=<ENABLE>];
Important parameter
SUBNETMASK: Subnet mask of the network element. 32-bit address consisting of
four, dot-separated decimal numbers ranging from 0 to 255.
Example
ED-LAN::LAN-1:100:::mask=255.255.0.0;
Note: You can set the IP address and subnet mask with the same command:
ED-LAN::LAN-1:100:::IP=129.9.0.53,MASK=255.255.0.0,ENALBE=Y;
Note: The subnet mask must match the IP address, otherwise the set operation will not be effective and the
command denied. This dependency between the IP address and mask complies with the TCP/IP standards
on network segment restriction (refer to the relevant technical documentation for details).
Generally, the LPS-8xx is assigned a default IP address and a subnet mask at delivery, which are
respectively 129.9.255.250 and 255.255.0.0 (0xFFFF0000). The default values do not have any special
function, and a method to restore the default settings is not provided.
PROVISIONING STATIC ROUTE FOR IP OVER DCC

This section describes how to provision IP over DCC route for NE communication.
Note: The operation of creating, deleting, and modifying the IP over DCC route must be performed on the
NE side. To set communication between the NM server and NEs, the route of the NM server and router (if
present) should be configured according to local site practices.
Creating a Static Route
Purpose Create an IP over DCC route

Prerequisite procedures Connect and log in to the NE; NE IP has been
configured correctly.
Location Onsite
To create an IP over DCC route, use the following command.
Command
ENT-IPROUTE-STATIC:<TID>::<CTAG>:::DESTIP=[DESTADDR],
GATEWAY=[GATEWAY],MASK=[MASK];
Important parameter
DESTADDR: Destination IP address. 32-bit address consisting of four dot-
separated decimal numbers ranging from 0 to 255. For example: 129.9.0.2
GATEWAY: Gateway IP address. 32-bit address consisting of four dot-
MASK: Subnet mask. 32-bit address consisting of four dot-separated decimal
numbers ranging from 0 to 255. For example: 255.255.0.0
Example
ENT-IPROUTE-STATIC:::100:::DESTIP=129.9.0.2,GATEWAY=
129.9.0.1,MASK=255.255.0.0;
Note: Before creating the route, make sure the IP address of your operating terminal (usually a PC) is
The destination IP address should be the EMS server. The static route must be recreated under the
following circumstances:
• NE IP address is changed.
• New NE is added in the network.
• The topology of network is changed.
Before recreating the static route of NE, you must delete the original static route.
Deleting Static Route
Purpose Delete an IP over DCC route

Location Onsite
To delete an IP over DCC route, use the following command.
Command
DLT-IPROUTE-STATIC:<TID>::<CTAG>:::DESTIP=<DESTIP>;
Important parameter
DESTIP: Destination IP address. 32-bit address consisting of four, dot-
Example
DLT-IPROUTE-STATIC:::100:::DESTIP=:129.9.0.2;
Note: Before deleting the route, make sure the IP address of your operating terminal (usually a PC) is
Retrieving a Static Route
Purpose Retrieve IP over DCC route

Location Onsite
To retrieve an IP over DCC route, use the following command.
Command
RTRV-IPROUTE:<TID>::<CTAG>;
Important parameter
None
Example
RTRV-IPROUTE:::100;
SETTING DATE AND TIME

Setting System Date and Time
Purpose Use this process to modify the system date and

time of the NE.
Prerequisite procedures Log in to the NE with the user level of
maintenance or higher.
To set the system time in the LPS-8xx, use the following command.
Command
ED-DAT:[<TID>]::<CTAG>::[<DATE>],[<TIME>],[<TMZONE>],
[<DSTIME>];
Important parameter
DATE: Year-Month-Day
TIME: Hour-Minute-Second
Please refer to the LoopStar 800 Series TL1 Commands Manual, catalog
number LPS800-UM-COMM, for a detailed description of this command.
To set the current date to April, 25, 2003 and the time to 2:31:50 pm, perform the following steps:
Step Action
For example, to log in to the NE as a SONET user, enter
2 ED-DAT:::100::2003-04-25,14-31-50;
Retrieving System Time
Purpose Use this process to retrieve the system time of

a specified NE
To retrieve the system time in the LPS-8xx, use the following command.
Command
RTRV-DAT:[<TID>]::<CTAG>;
Important parameter
Null
Example
RTRV-DAT:::100;
Returned information:
SONET-NE 2004-12-06 16:56:56
M 100 COMPLD
"2004-12-06,16-56-56,GMT+8,Y"
;
Note: Modifying the system date and time of the NE may make some of the performance monitoring values
unavailable.
Retrieving Time of Day
Purpose Use this command to retrieve the time of day.

To retrieve the date and time, use the following command. The time returned is in coordinated universal time (UTC).
Command
RTRV-TOD:[<TID>]::<CTAG>;
Important parameter
Null
Example
RTRV-TOD:::100;
SONET-NE 2005-01-31 16:45:15
M 100 COMPLD
"2005,01,31,16,45,15,UTC"
;
PROVISIONING THE TARGET IDENTIFIER (TID)

Retrieving TID
Purpose Retrieve the current target identifier(TID) of

the NE.
As with the NE label, the TID can be queried with every operation command. If required, the TID can be queried
using any TL1 command.
Setting TID
Purpose Use this process to set the TID of a local NE.

To set the local NE TID in the LPS-8xx, use the following command.
Command
SET-SID:[<TID>]::<CTAG>::<SID>;
Important parameter
SID: The new name of the target NE
Example
SET-SID:::100::SONET-NE;
PROVISIONING NE SYSTEM ATTRIBUTES

Editing NE Extended Attributes
Purpose Modify the NE extended attributes: equipment

label, equipment location, and other
descriptions.
user or a higher level user.
To edit the NE system attributes in the LPS-8xx, use the following command.
Command
ED-SYS:[<TID>]::<CTAG>:::[AUTOP=<AUTOP>,][LPBKSAVEFLAG=
<LPBKSAVEFLAG>,][NELOCATION=<NELOCATION>,][NEMEMO=
<NEMEMO>];
Important parameter
For example
Suppose there is an NE, located in Avenue 15, New York. The Maintenance Personnel is Jack Jiao.
Step Action
For example, to log into the NE as a SONET user, type:
2 ED-SYS:::100:::AUTOP=Y,LPBKSAVEFLAG=N,NELOCATION=NEW_YORK_15,
NEMEMO=Maintainer_Jack_Jiao;
Retrieving NE Extended Attributes
Purpose Use this process to retrieve the NE system

attributes.
To retrieve the NE extended attributes in the LPS-8xx, use the following command.
Command
RTRV-SYS:[<TID>]::<CTAG>;
Important parameter
Null
Example
To retrieve the NE extended attributes, perform the following operations:
Step Action
1 Log into the NE as an existing user.
For example, to log in the NE as a SONET user, type:
2 RTRV-SYS:::100;
RESETTING A UNIT
Purpose Reset a unit
It may be necessary to perform a software warm reset. For example, some settings are not effective until the unit is
reset. Maintenance and test operations sometimes require resetting.
CAUTION Resetting the unit may affect service and may initiate protection switching.
To reset the unit, use the following command.
Command
INIT-SYS:[<TID>]:<AID>:<CTAG>::<TYPE>;
Important parameter
<AID>: SLOT-N or SLOT-ALL, SLOT-ALL is whole system. <AID> is null while
activate the whole system, and before that, you can activate a specified card
using <AID>. If there is no file changed on that specified card, the command will
return DENIED.
<TYPE>:
COLD: Cold reset, reload FPGA.
WARM: Warm reset, do not reload FPGA.
DBERASE: Erase databases then do warm reset.
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.
Example
Warm reset the NE:
INIT-SYS::SLOT-ALL:100::WARM;
RETRIEVING NE SOFTWARE VERSION

Purpose Retrieve the NE software version.
To retrieve the NE software version of the LPS-8xx, use the following command.
Command
RTRV-NESOFT-VER:[<TID>]:[<AID>]:<CTAG>;
Important parameter
Please refer to the LoopStar 800 Series TL1 Commands Manual, catalog number LPS800-UM-COMM, for
a detailed description of this command.
Example
RTRV-NESOFT-VER:::100;
SONET-NE 2005-01-13 17:26:55
M 100 COMPLD
"SOFTNAME=NSF1,SOFTVER=5.16.02.21,SOFTVERDATE=20041231,SOFTSTATUS=active"
"SOFTNAME=BIOS,SOFTVER=8.06.09,SOFTVERDATE=20040809,SOFTSTATUS=inactive"
"SOFTNAME=ExtBIOS,SOFTVER=9.06.21,SOFTVERDATE=20041111,SOFTSTATUS=active"
"SOFTNAME=Logic,SOFTVER=(U2)130,SOFTVERDATE=,SOFTSTATUS="
"SOFTNAME=LogicE01,SOFTVER=(U7)210,SOFTVERDATE=,SOFTSTATUS="
"SOFTNAME=LogicE02,SOFTVER=(U3)130,SOFTVERDATE=,SOFTSTATUS="
;
The version information to be queried should include other unit related information in addition to the unit version
information, as described in Table 3-1.
Table 3-1. Parameter description

Description Meaning
NSF1 NE software version, date and status
BIOS BIOS version, date and status
ExtBIOS ExtBIOS version, date and status
Logic Logic version, date and status
LogicE01 LogicE01 version, date and status
RETRIEVING UNIT VERSION

Purpose Retrieve the unit version.
To retrieve the unit version of the LPS-8xx, use the following command.
Command
RTRV-EQPT:[<TID>]:[<AID>]:<CTAG>;
Important parameter
Please refer to the LoopStar 800 Series TL1 Commands Manual, catalog number LPS800-UM-
COMM, for a detailed description of this command.
Example
RTRV-EQPT::SLOT-1:100;
SONET-NE 2004-12-06 17:37:31
M 100 COMPLD
"SLOT-1::PROVTYPE=OC12Q,ACTTYPE=OC12Q,CLEI=SOOTAACAAA,PCBVER=1.A,
SWVER=2.10.10,FPGAVER=(U17)210,BIOSVER=2.21:IS-NR"
;
>
The version information to be queried should include other unit related information in addition to the unit version
information (Table 3-2).
Table 3-2. Parameter description

Description Meaning
AID Slot number
CARDTYPE The unit type
INTFTYPE The unit interface type
TPSPRI The priority of the unit if the unit is a working unit of a
TPS protection group. For any other units, this
parameter is not available.
SWITCHSTATE The switch state of the unit if the card is a unit of a TPS
protection group
SN The serial number for the equipment
CLEI The CLEI code for the equipment
VENDID The vendor ID for the equipment
Description Meaning
DOM The date when the unit was manufactured and is
optional
PCBVER The PCB version for the equipment
SWVER The software version for the equipment
FPGAVER The FPGA version for the equipment
EPLDVER The EPLD version for the equipment
BIOSVER The BIOS version for the equipment
MAC The MAC address for the equipment if it’s an
Ethernet unit
PST The primary state of the entity
SST The secondary state of the entity
TIMING
Before the LPS-8xx is put into operation, the clock synchronization attribute should be set for every NE in the
network topology. The LPS-8xx supports four timing modes: external, line, internal, or mixed. The typical clock
configuration environment is shown in Figure 3-3:
Figure 3-3. LPS-8xx timing example
There may be multiple types of NE reference clock sources, like building integrated timing supply system (BITS) and
line and internal. As shown in Figure 3-3, the synchronous communication equipment requires good clock quality.
The NE usually needs BITS or line, together with its internal, to form a clock source table.
In a general network topology, an NE accesses two BITSs (one of which is the backup). When both the BITSs are
faulty, the internal clock is put into use (Node A in the diagram). Other NEs in the network trace the reference clock
source of the line to get synchronized with a better clock source. Proper configuration of the NE timing should be
done to ensure that there are no timing loops in the network.
The LPS-8xx supports the SONET synchronization status message (SSM) protocol, including Generation 1 and
Generation 2 SSM protocols. With SSM transported over the S1 byte of the signal line layer, the equipment can
select the best clock source automatically according to the standard protocol to ensure the quality of synchronous
communication and avoid the “timing loop” in clock tracing.
The input BITS of the LPS-8xx is accessed on ATE (as shown in Figure 3-4). The clock source level of the internal
oscillator of the LPS-8xx is Stratum 3 (ST3), which is provided through the XCS/XCSH.
Figure 3-4. BITS interface
The general configuration procedures are described in the sections that follow.
Retrieve All Existing Clock Sources

Before configuring the clock synchronization attributes, you can use a retrieve command to get information about all
currently available clock sources. This information helps prepare for the subsequent configurations.
To retrieve the existing clock sources in the LPS-8xx, use the following command:
Command
RTRV-EXIST-SYNC:[<TID>]::<CTAG>;
Important parameter
Null
Note: The clock source priority table must be defined after the NE clock timing mode is set, that is after the
Setting Clock Source Attributes section below. And the setting of the clock source must rely on the timing
mode in use:
• In an external timing mode, only the external clock sources and the internal clock can be used.
• In a line timing mode, only the line clock sources and the internal clock can be used.
• In a mixed timing mode, the external clock sources, line clock sources, and the internal clock can
be used.
Setting the Reference Clock Priority Table

The clock priority table is used to define the priorities of the equipment clocks. In case of clock source failure, this
table is used to find the best available clock source by searching the table based on priorities and SSM quality
levels. For descriptions of the use of more of these commands, refer to the LoopStar 800 Series TL1 Commands
Manual, catalog number LPS800-UM-COMM.
To set the reference clock priority table in the LPS-8xx, use the following command.
Command
ED-SYNCLIST:[<TID>]:<AID>:<CTAG>::SYNCAID+;
Important parameter
Example
Set the reference clock priority table:
ED-SYNCLIST::SYNCCLOCK:100:: FAC-1-1,FAC-1-2;
To retrieve the reference clock priority table in the LPS-8xx, use the following command.
Command
RTRV-SYNCLIST:[<TID>]:<AID>:<CTAG>;
Important parameter
AID: Access identifier of synchronization reference list.
SYNCCLOCK: System clock reference list
SYNCOUT-1: BITS-1'S output clock reference list
Null for all three lists.
Editing General NE Clock Attributes (Including Setting the SSM Protocol)

In this step, you need to edit the general clock synchronization attributes of the NE. It includes:
• Clock timing mode.
• The type of the SSM protocol is generation 1 or generation 2.
• SSM enable
• The revertive switching mode and the restoration time.
• PNO (provisionable by the network) – the RES quality class that the user provisioned
It should be explained that setting the SSM protocol type does not mean the SSM protocol is started, and it should
be specified in the command parameter whether the protocol is to be started or not. RES (reserved for network
synchronization use) reflects the quality grades of the user defined clock sources; refer to Table 3-3. For operation
details, refer to the LoopStar 800 Series TL1 Commands Manual, catalog number LPS800-UM-COMM.
To edit the overall NE clock attribute in the OptiX Metro 800, use the following command.
Command
ED-SYNC:[<TID>]:<SYNC>:<CTAG>:::[TMGMODE=<TMGMODE>,]
[SSMMAP=<SSMMAP>,][SSMEN=<SSMEN>,][RVRTV=<RVRTV>,][RVTM=<
RVTM >,][PNO=<PNO>];
Important parameter
number LPS-800-UM-COMM, for a detailed description of this command.
To retrieve the NE clock attributes in the LPS-8xx, use the following command.
Command
RTRV-SYNC:[<TID>]:<AID>:<CTAG>;
Important parameter
Null
Table 3-3. List of user defined levels (RES)

Value Description
ABOVEPRS Better than Primary Reference
Source
PRS Equating to PRS
ABOVESTU Between STU and PRS
STU Equating to STU
ABOVEST2 Between ST2 and STU
ST2 Equating to ST2
ABOVETNC Between TNC and ST2, only for
GEN2
TNC Equating to TNC, only for GEN2
ABOVEST3E Between ST3E and TNC, only for
GEN2
ST3E Equating to ST3E, only for GEN2
ABOVEST3 Between ST3 and ST3E
ST3 Equating it ST3
DUS Disable the RES message
To obtain the SSM messages of all the current clock sources in a network with the SSM protocol started, use the
following command.
Command
RTRV-SYNC:[<TID>]:<AID>:<CTAG>;
Important parameter
AID: Identifier of the synchronization reference list. Valid value is:
SYNCCLOCK: System clock reference list
Setting Clock Source Attributes

Configuring the general equipment clock attributes was described in the previous section, “Editing General NE Clock
Attributes (Including Setting the SSM Protocol)” on page 3-18. The following steps are designed to set the attributes
of each clock source.
The BITS clock source attributes comply with the GR 253 requirements, with the following items supported: input
source code types B8ZS and AMI, the frame formats Extended Superframe Format (ESF) and Superframe Format
(SF), and the AIS threshold levels (When the SSM protocol is enabled, the external source frame format is ESF, and
when the SSM message of the BITS extraction source is lower than the AIS threshold, AIS will be inserted at the
corresponding port). When LOF or CODE VIOLATION OVER (CVOVER) occurs in the external input source,
insertion of AIS is supported (it is considered an external source failure).
To set the clock source attributes in the LPS-8xx, use the following command.
Command
To set the BITS clock source attributes:
ED-BITS:[<TID>]:<AID#BITSIN-1/BITSIN-2>:<CTAG>:::[LINECDE=
<LINECDE>,][FMT=<FMT>,][MANSSM=<MANSSM>,][SVTIMER=<SVTIMER
>][:<PST>[,<SST>]];
To set the BITSOUT clock source attributes:
ED-BITS:[<TID>]:<AID#BITSOUT-1/BITSOUT-2>:<CTAG>:::[LBO=
<LBO>,][LINECDE=<LINECDE>,][FMT=<FMT>,][AISTH=<AISTH>,]
[TSSM=<TSSM>,][MSGMODE=<MSGMODE>,][SVTIMER=<SVTIMER>]
[:<PST>[,<SST>]];
To set the line clock source attributes, use the following command:
ED-<OCN>:[<TID>]:<AID>:<CTAG>:::[BERSF=<BERSF>,][BERSD=
<BERSD>,][LSRSTAT=<LSRSTAT>,][MANSSM=<MANSSM>,][TSSM=
<TSMM>,][SVTIMER=<SVTIMER>,][PRI =<PRI>][:[<PST>][,<SST>]];
Important parameter
Example
Set the attribute of BITSIN-1 as follows, the DS-1 signal code type is AMI, the
frame format is ESF, and the AIS threshold is ST3:
ED-BITS::BITSIN-1:100:::LINECDE=AMI,FMT=ESF,AISTH=ST3;
Set the attribute of BITSOUT-1 as follows:
ED-BITS::BITSOUT-1:100:::LBO=1,LINECDE=B8ZS,FMT=EFS,
AISTH=PROS,MSGMODE=AIS,SVTIMER=05-00;
Set the attribute of line as follows:
ED-OC3::FAC-6-1:::TSSM=Y,MANSSM=CLEAR;
The command for obtaining the BITS clock source attribute is as follows:
RTRV-BITS::BITSIN-1:100;
RTRV-BITS::BITSOUT-1:100;
RTRV-OC3::FAC-6-1:100;
For line and external clock sources, it is supported to enable/disable output of SSM messages through the
corresponding line port and to manually set the SSM quality of the clock source input through the corresponding
port. Relevant command.
Command
ED-SYNC:[<TID>]:<SYNC>:<CTAG>:::[TMGMODE=<TMGMODE>,]
[SSMMAP=<SSMMAP>,][SSMEN=<SSMEN>,][RVRTV=<RVRTV>,]
[RVTM=< RVTM >,][PNO=<PNO>];
Important parameter
Example
Configure the priority attribute:
ED-SYNC::SYNCCLOCK:100:::TMGMODE=LINE,SSMMAP=Y,SSMEN=N,
PNO=ST3,RVRTV=Y,RVTM=5;
Note:
The command will change all the clock (SYNCCLOCK, SYNCOUT-1,
and SYNCOUT-2) attributes of NE at the same time.
To retrieve the priority attribute:
RTRV-SYNC::SYNCCLOCK:100;
For details, refer to the LoopStar 800 Series TL1 Commands Manual, catalog number LPS800-UM-COMM.
Table 3-4. The message of SSM generation 1

Value Description
PRS Primary reference source, Stratum1
STU Synchronization traceability unknown
ST2 Stratum2
ST3 Stratum3
SMC SONET minimum clock
ST4 Stratum 4, it is not support yet.
DUS Do not use for timing Synchronization
PNO Reserved: quality level set by user
CLEAR* Clear the manually SSM
Table 3-5. The message of SSM generation 2

Value Description
PRS Primary reference source, Stratum1
STU Synchronization traceability unknown
ST2 Stratum2
TNC Transit note clock
ST3E Stratum3E
ST3 Stratum3
SMC SONET minimum clock
ST4 Stratum 4, it is not support yet.
DUS Do not use for timing Synchronization
PNO* Reserved: quality level set by user
CLEAR* Clear the manually SSM
Setting User Clock Source Switching

The user switching operation switches the currently traced source to other specified clock sources. During
equipment maintenance or failure conditions, it may be necessary to force the clock source to be switched to other
clock sources. The LPS-8xx provides a special command for switching the clock source.
Use the following command to switch clock sources.
Command
OPR-SYNCNSW:[<TID>]:[<AID>]:<CTAG>::SYNCAID,SWMODE;
Important parameter
Example
OPR-SYNCNSW::SYNCCLOCK:100::FAC-1-1,FRCD;
Note: To switch the currently traced clock source, you should make sure the new clock source to be
switched is of good quality, exists in the corresponding priority table and is not locked.
To restore to the automatic clock source selection mode, use the following command.
Command
RLS-SYNCNSW:[<TID>]:[<AID>]:<CTAG>::SYNCAID;
Important parameter
Null
Example
RLS-SYNCNSW::SYNCCLOCK:100::FAC-1-1;
Note: Manual switching is different from forced manual switching. Manual switching must meet these
conditions:
• When the SSM protocol is not stated, the source to be manually switched to must exist in the corre-
sponding priority table and cannot be locked or in forced switching state.
• When the SSM protocol is started, the SSM message priority of the source must be the highest.
• In addition, manual switching is only used in the case when no priority table is used and its switch
priority is lower than that under any other switching conditions, such as source status change, SSM
message degradation, forced switching and locking operation, and so on.
Locking Out a Clock Source

A lock out request for a specific clock source in the clock priority table means that it is no longer an available clock
source of the equipment. It essentially excludes a specific clock source from the priority table. When it is necessary
to switch the equipment clock source, the locked clock source is no longer a possible candidate during clock source
selection.
If a clock source currently being traced by the equipment is locked, the equipment will select another clock source of
the highest priority and perform a lock out of the current clock source.
The command for clock locking on LPS-8xx is:
Command
OPR-SYNCNSW:[<TID>]:[<AID>]:<CTAG>::SYNCAID,SWMODE;
Important parameter
LPS800-UM-COMM-01, for a detailed description of this command.
Example
The locking operation: Lock out of the line clock source of optical port 1
of unit 3:
OPR-SYNCNSW::SYNCCLOCK:100::FAC-1-1,LOCKOUT;
The command for clock unlocking on LPS-8xx is:
Command
RLS-SYNCNSW:[<TID>]:[<AID>]:<CTAG>::SYNCAID;
Important parameter
LPS800-UM-COMM-01, for a detailed description of this command.
Example
The unlocking operation: Unlock the line clock source of optical port 1 of unit 3:
RLS-SYNCNSW::SYNCCLOCK:100::FAC-1-1;
Chapter 4
PROTECTIONS
XO UNIT PROTECTION
Fundamental Commands
Retrieve the Active/Standby State of XO Unit
Command
Important parameter
Null
Example
"SLOT-1::PROVTYPE=XO12,ACTTYPE=XO12,SWITCHSTATE=IDLE,
CLEI=0000000000,PCBVER=1.A,SWVER=5.16.2.21,FPGAVER=(U2)130
(U7)210,EPLDVER=200,BIOSVER=9.6.21:IS-NR,ACT"
Table 4-1. The description of output parameter about active/standby state of XCS unit
Value Description
SWITCHSTATE IDLE: Idle
LOCKOUT: Lock to the working unit
FRCD: Forced switch.
MAN: Manual switch
SST ACT: Active
STBYH: Standby-Hot
Retrieve the Backup State of Two XO Units
Command
RTRV-BACKUP-INFO:[<TID>]::<CTAG>;
Important parameter
Null
Chapter 4: Protections July 27, 2005
Table 4-2. The description of output parameter

Value Description
BACKUP_INFO IDLE: means that there are no messages between
two units;
SHAKE HANDS: means that the two units have finished
shaking hands, but didn’t start backup;
IN PROGRESS: memory data or database files are being
backuped, or database files are being recovered ,
COMPLETED: backup successfully, only in this state,
XCS switch is safe;
SMOOTHDATA: smoothing data for integrity and
harmony;
Allowing the Protection Switch of XO unit
Command
ALW-SWDX-EQPT:[<TID>]:<EQPT>:<CTAG>;
Important parameter
EQPT: The target slot which will be allowed, such as SLOT-1 or SLOT-2.
Example
Allow the protection switch of XO unit in slot 1.
ALW-SWDX-EQPT::SLOT-1:100;
Inhibiting the Protection Switch of XO unit
Command
INH-SWDX-EQPT:[<TID>]:<EQPT>:<CTAG>;
Important parameter
EQPT: The target slot which will be allowed, such as SLOT-1 or SLOT-2.
Example
Inhibit the protection switch of XCS unit in slot 1.
INH-SWDX-EQPT::SLOT-1:100;
July 27, 2005 Chapter 4: Protections
Switching Operations
Executing Protection Switching of XO unit
Command
SW-DX-EQPT:[<TID>]:<EQPT>:<CTAG>::<HSCSWMODE>;
Important parameter
EQPT: The slot identifier of XO unit. It should be the standby slot.
HSCSWMODE: XO switch mode. Valid values are MANUAL (manual switch),
FORCE (forced switch), and CLEAR (clear switch).
Example
Execute the manual switching:
SW-DX-EQPT::SLOT-1:100::MANUAL;(the slot 1 is the active slot)
Execute the forced switching:
SW-DX-EQPT::SLOT-1:100::FORCE;(the slot 1 is the active slot)
Clear the forced switching:
SW-DX-EQPT::SLOT-1:100::CLEAR;
Example
The following gives a full description of various XO unit protection operations using examples.
Step Action
1 User named SONET logs into Metro 800 NE with the password of SONET:
2 Retrieve the active/standby state of XCS unit:
3 If the SWITCHSTATE=LOCKOUT, you should use the following command to enable the protection
switch of XCS. Otherwise go to Step 4.
ALW-SWDX-EQPT::SLOT-1:100;
4 Execute the manual switching:
SW-DX-EQPT::SLOT-1:100::MANUAL; (the slot 1 is the active slot)
Or execute the forced switching:
SW-DX-EQPT::SLOT-1:100::FORCE; (the slot 1 is the active slot)
Note: When you execute the protection switch, you will lose the connection to NE. When the unit
is in FRCD state, before you execute another switching, you must clear the force switch first.
5 Clear the forced switching:

SW-DX-EQPT::SLOT-1:100::CLEAR;
DSN PROTECTION
Overview
DSn protection is an equipment protection scheme provided by the LPS-8xx. It is also called tributary protection
switching (TPS). For details, refer to the LoopStar 800 Series Application and Engineering Manual, catalog number
LPS800-UM-APPL.
Retrieve DSn Protection Group
Command
RTRV-EQPT-PG:[<TID>]:[<AID>]:<CTAG>;
Important parameter
Null
Example
Retrieve all the created DSn protection groups:
RTRV-EQPT-PG:::100;
Create DSn Protection Group
Command
ENT-EQPT-PG:[<TID>]:<AID>:<CTAG>:::[RVRTV=<RVRTV>,]
[RVTM=<RVTM>,][PSTYPE=<PSTYPE>,]WORK=<WORK>;
Important parameter
Example
Create 1:1 DSn protection group for protection group 1. Here, unit in slot 3
protects that in slot 6:
ENT-EQPT-PG::SLOT-3:100:::RVRTV=Y,RVTM=5,WORK=SLOT-6;
Edit DSn Protection Group Attributes
Command
ED-EQPT-PG:[<TID>]:<AID>:<CTAG>:::[RVRTV=<RVRTV>][RVTM=
<RVTM>][,WORK=<WORK>];
Important parameter
If the RVRTV is Y, the RVTM values range from 0 to 12 (min).
Default value is 5 min.
Example
Set the WTR of DSn protection group to 10 minutes:
ED-EQPT-PG::SLOT-3:100:::RVRTV=Y,RVTM=10,WORK=SLOT-6;
Delete DSn Protection Group
Command
DLT-EQPT-PG:[<TID>]:<AID>:<CTAG>;
Important parameter
AID: AID of any equipment in a protection group.
Example
Delete DSn protection group:
DLT-EQPT-PG::SLOT-3:100;
Execute DSn Protection
Command
OPR-PROTNSW-EQPT:[<TID>]:<AID>:<CTAG>::<SC>;
Important parameter
SC: The switch command that is to be initiated. Valid <SC> is one of the
following:
LOCKOUT, FRCD, MAN.
Example
Execute protection of DSn:
OPR-PROTNSW-EQPT::SLOT-3:100::MAN;
Release DSn Protection
Command
RLS-PROTNSW-EQPT:[<TID>]:<AID>:<CTAG>;
Important parameter
Null
Example
Release protection of DSn:
RLS-PROTNSW-EQPT::SLOT-3:100;
Retrieve Priorities of Units in a DSn Protection Group
Command
Important parameter
TPSPRI: The priority of the AID card if the card is a working unit of a TPS
protection group.
Example
Retrieve the unit priority of DSn protection group 1.
Set Unit Priority in a DSn Protection Group
Command
ED-EQPT:[<TID>]:<AID>:<CTAG>:::[TPSPRI=<TPSPRI>],[PROVTYPE=
<CARDTYPE>],[INTFTYPE=<INTFTYPE>]:[[<PST>],[<SST>]];
Important parameter
TPSPRI: The priority of the AID card if the card is a working unit of a TPS
protection group. TPS priority, range from 1 to 4. 1 is the highest value and 4 are
the lowest. Default is 4, the lowest.
Example
Set the switching priority 2 for the unit in slot 6 of DSn protection:
ED-EQPT::SLOT-6:100:::TPSPRI=2;
Retrieve Switching State of DSn Protection Group
Command
Important parameter
SWITCHSTATE: The switch state of the AID card if the card is a unit of a TPS
protection group.
Example
Retrieve the switching state of DSn protection:
RTRV-EQPT:::100;
Execute DSn Protection External Switching
Command
OPR-PROTNSW-EQPT:[<TID>]:<AID>:<CTAG>::<SC>;
Important parameter
SC: The switch command that is to be initiated. Valid <SC> is one of the
following: LOCKOUT, FRCD, MAN.
Example
Start protection of DSn protection:
OPR-PROTNSW-EQPT::SLOT-8:100::MAN;
Release DSn Protection External Switching
Command
RLS-PROTNSW-EQPT:[<TID>]:<AID>:<CTAG>;
Important parameter
Null
Example
Stop protection protocol of DSn protection:
Example
The following examples provide a full description of the various DSn protection operations.
Step Action
1 User named SONET logs into Metro 800 NE with the password of SONET:
2 Create PDT3 units in slot 3 and slot 6:
ENT-EQPT: :SLOT-3:100::PDT3;
ENT-EQPT: :SLOT-6:100::PDT3;
3 Retrieve the created units:
RTRV-EQPT:::100;
4 Create DSn protection group of 1:1 type. PDT3 in slot 3 protects PDT3 in slot 6. Set the revertive time of
DSn protection group to 5 minutes.
ENT-EQPT-PG::SLOT-3:100:::RVRTV=Y,RVTM=5,WORK=SLOT-6;
5 Set the switching priority 2 for the unit in slot 6 of DSn protection group:
ED-EQPT::SLOT-6:100:::TPSPRI=2;
6 Retrieve the unit priority of DSn protection groups:
7 Force switch the service of PDT3 unit in slot 6 to protection unit:
OPR-PROTNSW-EQPT::SLOT-6:100::FRCD;
8 Retrieve the switching state of DSn protection groups:
RTRV-EQPT:::100;
9 Release the switch of the PDT3 unit in slot 3 to working unit:
10 Delete DSn protection groups:
DLT-EQPT-PG::SLOT-3:100;
11 User exits Metro 800 NE:
CANC-USER::SONET:100;
1+1 SONET PROTECTION

Overview
1+1 SONET line protection is an optical interface-level protection scheme. That is, one protection optical interface is
used to protect one working optical interface of the same specifications. When the working optical interface detects
that the signal deterioration has crossed a certain threshold, the system will switch the service of the working optical
interface to the protection optical interface. The switch completion time is less than 50ms.
1+1 SONET line protection can be sub-classified into revertive and non-revertive modes. 1+1 SONET line protection
works in unidirectional switching mode or bidirectional switching mode.
In revertive mode, the traffic signal always returns to the working optical interface when the working trail has
recovered from the defect or a manual switch request is cleared.
In non-revertive mode, the traffic signal does not return to the working optical interface when the working trail has
recovered from the defect or a manual switch request is cleared.
Unidirectional switching refers to a protection switching method which takes switching action only at the affected
destination end in case the system detects signal transmission failure on the working fiber.
Retrieving Attributes and Switching State of Protection Group
Command
RTRV-FFP-<OCN>:[<TID>]:[<AID>]:<CTAG>;
OR
RTRV-FFP-ALL:[<TID>]::<CTAG>;
Important parameter
AID: the access identifier of the OC-N port, which is in a SONET line protection.
It is an optional parameter. If it is not given, the default value is “ALL”, which
means all the facility protection groups for the given OC-N are retrieved.
Example
Retrieve the attribute and switching state of protection group:
RTRV-FFP-OC12::FAC-6-2:100;
RTRV-FFP-ALL:::100;
Creating SONET Line Protection Group
Command
ENT-FFP-<OCN>:[<TID>]:<PROTECT>,<WORK>:<CTAG>:::FFPTYPE=
<FFPTYPE>,[RVRTV=<RVRTV>][,RVTM=<RVTM>],[PSDIRN=<PSDIRN>].
[RINGID=<RINGID>],[NODEID=<NODEID>],[TPLMODE=<TPLMODE>],
[SQLMODE=<SQLMODE>];
Important parameter
Example
Create revertive unidirectional 1+1 protection group. Here, optical interface 2 in
slot 6 serves as working interface, and optical interface 1 in slot 6 serves as
protection interface:
ENT-FFP-OC12::FAC-6-1,FAC-6-2:100:::FFPTYPE=1+1,RVRTV=Y,
RVTM=5,PSDIRN=UNI;
Edit SONET Line Protection Group Attributes
Command
ED-FFP-<OCN>:[<TID>]:<AID>:<CTAG>:::[FFPTYPE=<FFPTYPE>],
[RVRTV=<RVRTV>],[RVTM=<RVTM>],[PSDIRN=<PSDIRN>],
[TPLMODE=<TPLMODE>],[SQLMODE=<SQLMODE>],[RINGID=<RINGID>],[
NODEID=<NODEID>];
Important parameter
Example
Edit protection group to be unidirectional, and the revertive time is 10 minutes:
ED-FFP-OC12::FAC-6-2:100:::FFPTYPE=1+1,RVRTV=Y,RVTM=10,
PSDIRN=UNI;
Delete SONET Line Protection Group
Command
DLT-FFP-<OCN>:[<TID>]:<AID>:<CTAG>;
Important parameter
AID: The facility AID of any OC-N that is part of the protection group.
Example
Delete the 1+1 protection group, in which optical interface 2 in slot 6 serves as
working interface, and optical interface 1 in slot 6 serves as protection interface:
DLT-FFP-OC12::FAC-6-2:100;
Execute External Switching
Command
OPR-PROTNSW-<OCN>:[<TID>]:<AID>:<CTAG>::<SC>:[<ST>];
Important parameter
AID: The facility AID of any OC-N that is part of the protection group.
SC: The switching type that is to be initiated.
• LOCKOUT(lockout of switching),
• FRCD (forced switch)
• MAN (manual switch)
• EXERCISE (exercise switch)
• LP (BLSR only),
• LOW (BLSR only),
• LKALL (BLSR only)
ST: Only used for BLSR. Valid value can be RING or SPAN.
Example
Force switch the service of the working interface to the protection interface:
OPR-PROTNSW-OC12::FAC-6-2:100::FRCD;
Release Protection Switching
Command
RLS-PROTNSW-<OCN>:[<TID>]:<AID>:<CTAG>;
Important parameter
AID: the facility AID of any OC-N that is part of the protection group.
Example
Release the switch to the working interface in slot 6.
RLS-PROTNSW-OC12::FAC-6-1:100;
Example
The following examples provide a full description of the various protection operations.
Note: The configuration files below may be slightly different from the ones in an actual configuration.
Specific configuration commands should be selected according to the actual situation.
Step Action
1 Log into the NE:
Note: If using port 23, the logging in process will be interactive.
2 Create the line unit:

ENT-EQPT::SLOT-6:100::OC12D;
3 Create the protection group:
ENT-FFP-OC12::FAC-6-2,FAC-6-1:100:::FFPTYPE=1+1,RVRTV=Y,RVTM=5,PSDIRN=UNI;
4 Retrieve the attribute and status of protection group:
RTRV-FFP-OC12::FAC-6-1:100;
5 Modify the attribute:
ED-FFP-OC12::FAC-6-1:100:::FFPTYPE=1+1,RVRTV=Y,RVTM=9,PSDRIN=UNI;
6 Various switching commands for the equipment:
Force switch:
OPR-PROTNSW-OC12::FAC-6-1:100::FRCD;
Exercise switch (not available to unidirectional switching mode):
OPR-PROTNSW-OC12::FAC-6-1:100::EXERCISE;
Manual switch:
OPR-PROTNSW-OC12::FAC-6-1:100::MAN;
Release switch:
RLS-PROTNSW-OC12::FAC-6-1:100;
7 Delete the protection group:
DLT-FFP-OC12::FAC-6-1:100;
UPSR PROTECTION
Create a UPSR Service
Command
Create UPSR protection connection pair services of STS-1, STS-3c, STS-6c,
STS-9c, STS-12c level:
ENT-CRS-<STS_PATH/VT_PATH>:[<TID>]:<FROM>,<TO>:<CTAG>::
[<CCT>]:[PREFERREDPATH=<PREFERREDPATH>,][CKTID=<CKTID>]:
[,<SST>];
Important parameter
FROM: working source and protection source of UPSR protection connection
pair service. (Support “&” notation).
TO: UPSR protection connection pair service sink
PREFERREDPATH: Set the preferred path.
Example
Create the UPSR protection connection pair, the working source is STS-1 path 1
of the unit in slot 1, and the protection source is STS-1 path 1 of the unit in slot 2
and whose sink is STS-1 path 1 of the unit in slot 3:
ENT-CRS-STS1::STS-1-1-1&STS-2-1-1,STS-3-1-1:100:::
PREFERREDPATH=STS-1-1-1;
Create one UPSR protection connection pair service of STS-3c level, whose
working source is STS-3c path 1 of the unit in slot 1, whose protection source is
STS-3c path 1 of the unit in slot 2, and whose sink is STS-3c path 1 of the unit
in slot 3:
ENT-CRS-STS3C::STS-1-1-1&STS-2-1-1,STS-3-1-1:100:::
Create one UPSR protection connection pair service of STS-12c, whose working
source is STS-12c path 1 of the unit in slot 1, whose protection source is STS-
12c path 1 of the unit in slot 2, and whose sink is STS-12c path 1 of the unit
in slot 3:
ENT-CRS-STS12C::STS-1-1-1&STS-2-1-1,STS-3-1-1:100:::
Note: Corresponding to the UPSR protection connection pair service,

the dual-fed service needs manual creation.
Delete a UPSR Service
Command
Delete UPSR protection connection pair services of STS-1, STS-3c, STS-6c,
STS-9c, STS-12c level:
DLT-CRS-<STS_PATH/VT_PATH>:[<TID>]:<FROM>,<TO>:<CTAG>:::
[INCL=<INCL>]
;
Important parameter
FROM: working source and protection source of UPSR protection connection
pair services. (Support “&” denotation.)
INCL: Inclusive red-lined circuits, valid value is Y or N, default value is N.
Example
Delete the UPSR protection connection pair service of STS-1 level, whose
working source is STS path 1 of the unit in slot 1, whose protection source is
STS path 1 of the unit in slot 2 and whose sink is STS path 1 of the unit in slot 3:
DLT-CRS-STS1::STS-1-1-1&STS-2-1-1,STS-3-1-1:100:::INCL=Y;
Delete the UPSR protection connection pair service of STS-3c level, whose
STS-3c path 1 of the unit in slot 2 and whose sink is STS-3c path 1 of the unit in
slot 2, and whose sink is STS-3c path 1 of the unit in slot 3:
DLT-CRS-STS3C::STS-1-1-1&STS-2-1-1,STS-3-1-1:100:::INCL=Y;
Delete the UPSR protection connection pair service of STS-12c level, whose
STS-12c path 1 of the unit in slot 2, and whose sink is STS-12c path 1 of the unit
in slot 3:
DLT-CRS-STS12C::STS-1-1-1&STS-2-1-1,STS-3-1-1:100:::INCL=Y;
Note: Corresponding to the UPSR protection connection pair service,

the dual-fed service needs manual creation.
Editing Ordinary Service to the UPSR Service
Command
The following command is used for changing ordinary service to the UPSR
service of STS-1, STS-3c, STS-6c, STS-9c, STS-12c level:
ED-CRS-<STS_PATH/VT_PATH>:[<TID>]:<FROM>,<TO>:<CTAG>:::
[PREFERREDPATH=<PREFERREDPATH>,][CKTID=<CKTID>]:[,<SST>];
Important parameter
FROM: working source and protection source of the UPSR protection connection
pair service. (Support “&” notation.)
Example
Edit the ordinary service from STS-1 path 1 of the unit in slot 1 to STS-1 path 1 of
the unit in slot 2 into the UPSR protection connection pair service whose working
source is STS-1 path 1 of the unit in slot 1, whose protection source is STS-1
path 1 of the unit in slot 2, and whose sink is STS-1 path 1 of the unit in slot 3:
ED-CRS-STS1::STS-1-1-1&STS-2-1-1,STS-3-1-1:100::::
PREFERREDPATH=STS-1-1-1,CKTID=CHANGETOUPSR:,RDLD;
Edit the ordinary service from STS-3c path 1 of the unit in slot 1 to STS-3c path 1
of the unit in slot 2 into the UPSR protection connection pair service whose
STS-3c path 1 of the unit in slot 2 and whose sink is STS-3c path 1 of the unit
in slot 3:
ED-CRS-STS3C::STS-1-1-1&STS-2-1-1,STS-3-1-1:100::::
Edit the ordinary service from STS-12c path 1 of the unit in slot 1 to STS-12c
path 1 of the unit in slot 2 into the UPSR protection connection pair service
whose working source is STS-12c path 1 of the unit in slot 1, whose protection
source is STS-12c path 1 of the unit in slot 2 and whose sink is STS-12c path 1
of the unit in slot 3:
ED-CRS-STS12::STS-1-1-1&STS-2-1-1,STS-3-1-1:100::::
Editing UPSR Service to Ordinary Cross-Connect Service
Command
The following command is used for changing the UPSR service to ordinary
service of VT1.5, STS-1, STS-3c, STS-6c, STS-9c, STS-12c, STS-24c, STS-48c,
STS-192c level:
ED-CRS-<STS_PATH/VT_PATH>:[<TID>]:<FROM>,<TO>:<CTAG>:::
Important parameter
FROM: working source and protection source of the UPSR protection connection
pair service. (Support “&” notation.)
Example
Edit the UPSR protection connection pair service into ordinary service from STS-
1 path 1 of the unit in slot 1 to STS-1 path 1 of the unit in slot 2. The working
source of the UPSR service is STS-1 path 1 of the unit in slot 1, the protection
source is STS-1 path 1 of the unit in slot 2 and the sink is STS-1 path 1 of the unit
in slot 3:
ED-CRS-STS1::STS-1-1-1,STS-2-1-1:100;
Edit the UPSR protection connection pair service whose working source is STS-
3c path 1 of the unit in slot 1, whose protection source is STS-3c path 1 of the
unit in slot 2 and whose sink is STS-3c path 1 of the unit in slot 3 into ordinary
service from STS-3c path 1 of the unit in slot 1 to STS-3c path 1 of the unit
in slot 2:
ED-CRS-STS3C::STS-1-1-1,STS-2-1-1:100;
Edit the UPSR protection connection pair service whose working source is STS-
12c path 1 of the unit in slot 1, whose protection source is STS-12c path 1 of the
unit in slot 2 and whose sink is STS-12c path 1 of the unit in slot 3 into ordinary
service from STS-12c path 1 of the unit in slot 1 to STS-12c path 1 of the unit
in slot 2:
ED-CRS-STS12C::STS-1-1-1,STS-2-1-1:100;
Retrieving Created UPSR Service
Command
The following commands are used for retrieving the UPSR services:
RTRV-CRS-<STS_PATH/VT_PATH>:[<TID>]:[<AID>]:<CTAG>;
RTRV-CRS:[<TID>]::<CTAG>;
Important parameter
STS_PATH/VT_PATH: The modifier that identifies the type of STS. Valid value
can be STS1, STS3C, STS6C, STS9C, STS12C.
Example
Suppose there is one UPSR protection connection pair service of STS-1 level,
whose working source is STS-1-1-1, and whose protection source is STS-2-1-1,
and whose sink is STS-3-1-1.
Execute:
RTRV-CRS-STS1::STS-1-1-1:100;
RTRV-CRS-STS1::STS-3-1:100;
RTRV-CRS:::100;
Retrieving UPSR Switching State
Command
To get the protection switching state (manual, lockout, force), use the following
command.
RTRV-<STS_PATH>:[<TID>]:<AID>:<CTAG>;
Important parameter
Null
Example
There is one UPSR protection connection pair service of STS-12c level whose
working source is STS-1-1-1, whose protection source is STS-2-1-1 and whose
sink is STS-3-1-1. An external lockout switch request is pending for this
protection connection pair service.
Execute:
RTRV-STS1::STS-1-1-1:100;
Return:
SONET-NE 2004-12-21 16:44:37
M S COMPLD
"STS-1-1-1::RVRTV=N,SWPDIP=N,DELAYTIME=0,BERSF=1E-
4,BERSD=1E-6,J1TRC
MODE=OFF,EXPTRCJ1=123123124545,INCTRCJ1=,EXPTRCC2=EQPD,I
NCTRCC2=UNEQ
,SQL=NO,SWITCHSTATE=AUTO_SW:IS-NR"
;
Executing External Switching of UPSR
Command
The following command is used for executing external switching of UPSR:
OPR-PROTNSW-<STS_PATH/VT_PATH>:[<TID>]:<AID>:<CTAG>::<SC>;
Important parameter
STS_PATH/VT_PATH: Valid value can be STS1, STS3C, STS6C, STS9C or
STS12C.
SC: external switching level. For detailed parameters, refer to Table 4-3.
Example
If there is one UPSR protection connection pair service of STS-12c level whose
sink is STS-3-1-1:
OPR-PROTNSW-STS12C:: STS-1-1-1:100::MANUAL; (represents manual
switching to protection path)
OPR-PROTNSW-STS12C::STS-2-1-1:100::MANUAL; (represents manual
switching to working path)
OPR-PROTNSW-STS12C::STS-1-1-1:100::LOCKOUT; (represents locking out
working path)
OPR-PROTNSW-STS12C::STS-2-1-1:100::LOCKOUT; (represents locking out
protection path)
OPR-PROTNSW-STS12C::STS-1-1-1:100::FORCE; (represents forced
switching to protection path)
OPR-PROTNSW-STS12C::STS-2-1-1:100::FORCE; (represents forced
switching to working path)
Table 4-3. Description of external switching levels

External switching level Meaning
LOCKOUT Lock out protection path
FORCE For working source, it means forced
switching to protection path. For
protection source, it means forced
switching to working path.
MANUAL For working source, it means manual
switching to protection path. For
protection source, it means manual
switching to working path.
Release External Switching Command of UPSR Protection Connection Pair Service
Command
The following command is used for releasing external switching of UPSR.
RLS-PROTNSW-<STS_PATH/VT_PATH>:[<TID>]:<AID>:<CTAG>;
Important parameter
STS_PATH/VT_PATH : Valid value can be STS1, STS3C, STS6C, STS9C,
STS12C.
AID: Must be working path or protecting path
Example
There is one UPSR protection connection pair service of STS-12c level whose
sink is STS-3-1-1. This protection connection pair service has an external switch
request pending.
Execute:
RLS-PROTNSW-STS1::STS-1-1-1:100;
This releases any external switching request of the UPSR protection connection
pair service.
Chapter 5
CROSS-CONNECTION
This chapter describes how to set and manage cross-connection traffic. It consists of the following components:
• SONET Connections
• Creating unidirectional cross-connection
• Creating bidirectional cross-connection
• Creating broadcast cross-connection
• Deleting cross-connection
• Deleting broadcast cross-connection
• Querying cross-connection
SONET CONNECTIONS
Before You Begin
The LoopStar 800 provides high order cross-connect capacity of 192 x 192 STS-1s.
The LoopStar 800 also supports virtually concatenated mapping with STS-1 granularity.
Cross-connections supported by the LoopStar 800 are described in Table 5-1.
Table 5-1. Cross-connection capacity

Unit Ports STS-1s
PDM3 6 6
PQT3 12 12
PLT3 3 3
PDT1 28 1
PLT1 14 1
EFS8 8 12
OC12D 2 12 (per port)
OC12 1 12
OC3Q 4 3 (per port)
OC3D 2 3 (per port)
OC3 1 3
Before You Delete a Node

Delete all the traffic of the node. Complete the following procedures in this chapter according to the local site plan.
• “Deleting Uni-Directional Cross-Connection” on page 5-8
• “Deleting Bidirectional Cross-Connection Traffic” on page 5-11
• “Deleting Broadcast Cross-Connection Traffic” on page 5-13
Chapter 5: Cross-Connection July 27, 2005
RETRIEVING CROSS-CONNECTIONS
Purpose Retrieve cross-connections (including STS-1, STS-3c,

STS-12c)
Prerequisite procedures The user has logged into the NE and created the
required unit
To retrieve cross-connections, use the command:
Command
RTRV-CRS-<STS_PATH/VT_PATH>:[<TID>]:[<AID>]:<CTAG>;
RTRV-CRS:[<TID>]::<CTAG>;
Important parameter
STS_PATH/VT_PATH: STS1, STS3C, STS6C, STS9C, STS12C.
AID: path number.
Format: STS-Slot number-port number-STS path number or VT1-Slot number-
port number-STS path number-VT group number-VT path number
Example
Step Action
1 Create the following one cross-connection:
ENT-CRS-STS1::STS-5-1-1,STS-1-1-1:100;
The query result is:
LOOPSTAR800 2003-01-06 11:39:39
M 100 COMPLD
;
July 27, 2005 Chapter 5: Cross-Connection
CREATING UNIDIRECTIONAL CROSS-CONNECTION

Creating Unidirectional DS1 Traffic
Purpose Create a one-way DS1 cross-connection

Prerequisite procedures The user has logged in to the NE and created the required unit
To create a one-way DS1 cross-connection, use the following command:
Command
ENT-CRS-VT1:[<TID>]:<FROM>,<TO>:<CTAG>::[<CCT>]:
Important parameter
FROM: VT traffic source. Format: VT1-Slot number-port number-STS path
number-VT group number-VT path number
TO: VT traffic sink. Format: VT1-Slot number-port number-STS path number-VT
group number-VT path number
Example
To create a one-way DS1 cross-connection from the first DS1 of the PDT1 unit in slot 5 to the first VT in the first VT
Group of the first STS of the XO12D unit in slot 1, perform the following operations:
Step Action
ENT-CRS-VT1::VT1-5-1-1-1,VT1-1-1-1-1-1:100::1WAY:,CKTID=1:,RDLD;
If the following response is received, creation is successful:
LOOPSTAR800 2003-01-06 11:39:39
M 100 COMPLD
;
2 To view whether the creation is successful or not, use the command:
RTRV-CRS-VT1::VT1-5-1-1-1:100;
If the creation is successful, the newly created cross-connection should be included in the response.
Creating Unidirectional DS3 Traffic
Purpose Create a one-way DS3 cross-connection.

Prerequisite procedures The user has logged in to the NE and created the
required unit
To create a one-way DS3 cross-connection, use the following command:
Command
ENT-CRS-STS1:[<TID>]:<FROM>,<TO>:<CTAG>::[<CCT>]:
Important parameter
FROM: STS traffic source. Format: STS-Slot number-port number-STS
path number
TO: STS traffic sink. Format: STS-Slot number-port number-STS path number
Example
To create a one-way DS3 cross-connection from the first DS3 of the PQT3 unit in slot 6 to the first STS of the
XO12D unit in slot 1, perform the following operations.
Step Action
ENT-CRS-STS1::STS-6-1,STS-3-1-1:100::1WAY:,CKTID=1:,RDLD;
LOOPSTAR800 2003-01-06 11:39:39
M 100 COMPLD
;
Creating Unidirectional STS-N Traffic
Purpose Create one-way STS-N cross-connections

(STS-N includes STS-1, STS-3c, STS-6c,
STS-9c, STS-12c)
Prerequisite procedures The user has logged in to the NE and created
the required unit
To create one-way STS-N cross-connections, use the following command:
Command
[,<SST>];
Important parameter
STS_PATH/VT_PATH: STS1, STS3C, STS6C, STS9C, STS12C
FROM: STS traffic source. Format: STS-Slot number-port-number-STS path
number
TO: STS traffic sink. Format: STS-Slot number-port number-STS path number
Example
To create a one-way STS-3c cross-connection from the first STS of the LPS-OC3Q01 unit in slot 3 to the first STS of
the LPS-XO1201 unit in slot 1, perform the following operations:
Step Action
ENT-CRS-STS3C::STS-3-1-1,STS-1-1-1:100::1WAY:,CKTID=1:,RDLD;
LOOPSTAR800 2003-01-06 11:39:39
M 100 COMPLD
;
RTRV-CRS-STS3C::STS-3-1-1:100;
CREATING BIDIRECTIONAL CROSS-CONNECTION
Purpose Create two-way cross-connections (including

STS-1, STS-3c, STS-12c and VT1.5)
the required unit
To create a bidirectional cross-connection, use the following commands:
Command
[,<SST>];
Important parameter
STS_PATH/VT_PATH Identifies the type of STS and VT path. Valid value
can be STS1, STS3C, STS6C, STS9C, STS12C
and VT1.5.
FROM: STS traffic source. Format: STS-Slot number-Port
number-STS path number;
VT traffic source. Format: VT1-Slot number-Port
number-STS path number-VT group number-VT
path number.
TO: STS traffic sink. Format: STS-Slot number-Port
VT traffic sink. Format: VT1-Slot number-Port
path number.
Example
To create a bidirectional STS-3c cross-connection from the first STS of the LPS-OC3Q01 unit in slot 3 to the first
STS of the LPS-XO1201 unit in slot 1, perform the following operations:
Step Action
ENT-CRS-STS3C::STS-3-1-1,STS-1-1-1:100::2WAY;
If the following prompt appears, the creation is successful:
LOOPSTAR800 2003-01-06 11:39:39
M 100 COMPLD
;
If the creation is successful, the two newly created cross-connections should be included in the response.
CREATING BROADCAST TRAFFIC
Purpose Create broadcast cross-connections (including

STS-1, STS-3c, STS-12c and VT1)
the required unit
To create a broadcast cross-connection, use the following commands:
Command
[,<SST>];
Important parameter
and VT1.5.
path number.

path number.
Example
To create a STS-3c broadcast cross-connection from the first STS of the LPS-OC3Q01 unit in slot 3 to the first STS
of the LPS-XO1201 unit in slot 1 and the first STS of the LPS-XO1201 unit in slot 2, perform the following
operations:
Step Action
ENT-CRS-STS3C::STS-3-1-1,STS-1-1-1&STS-2-1-1:100::1WAY;
If the following message appears, the creation is successful:
LOOPSTAR800 2003-01-06 11:39:39
M 100 COMPLD
;
2 To view whether the creation is successful, use the command:
If the creation is successful, the two newly created cross-connections should be included in response.
DELETING UNI-DIRECTIONAL CROSS-CONNECTION

Deleting Unidirectional DS1 Traffic
Purpose Delete a one-way DS1 cross-connection

the required unit. The cross-connection to be
deleted exists.
To delete a one-way DS1 cross-connection, use the following command:
Command
[INCL=<INCL>];
Important parameter
STS_PATH/VT_PATH: VT1
FROM: VT traffic source. Format: VT1-Slot number-Port number-STS path
number-VT group number-VT path number
TO: VT traffic sink. Format: VT1-Slot number-Port number-STS path number-VT
group number-VT path number
Example
To delete a one-way DS1 cross-connection from the first DS1 of the LPS-PDT101 unit in slot 5 to the first VT in the
first VTG of the first STS of the LPS-XO1201 unit in slot 1, perform the following operations:
Step Action
DLT-CRS-VT1::VT1-5-1-1-1 ,VT1-1-1-1-1-1:100;
If the following response is received, deletion is successful:
LOOPSTAR800 2003-01-06 11:39:39
M 100 COMPLD
;
2 To view whether the deletion is successful, use the command:
RTRV-CRS-VT1::VT1-5-1-1-1:100;
If the deletion is successful, the deleted cross-connection should not be listed in the response.
Deleting Unidirectional DS3 Traffic
Purpose Deleting one-way DS3 cross-connections.

deleted exists
To delete a one-way DS3 cross-connection, use the following command:
Command
[INCL=<INCL>];
Important parameter
STS_PATH/VT_PATH: STS1
FROM: STS traffic source. Format: STS-Slot number-Port number-STS path
number
TO: STS traffic sink. Format: STS-Slot number- Port number-STS path number
Example
To delete a one-way DS3 cross-connection from the first DS3 of the LPS-PQT301 unit in slot 6 to the first STS of the
LPS-XO1201 unit in slot 1, perform the following operations:
Step Action
DLT-CRS-STS1::STS-6-1,STS-1-1-1:100;
If the following response is received, deletion is successful:
LOOPSTAR800 2003-01-06 11:39:39
M 100 COMPLD
;
If the deletion is successful, the deleted cross-connection should not be included in the response.
Deleting Unidirectional STS-N Traffic
Purpose Delete one-way STS-N cross-connections

(STS-N includes STS1, STS3C and STS12C)
deleted exists
To delete a one-way STS-N cross-connection, use the following command:
Command
LT-CRS-<STS_PATH/VT_PATH>:[<TID>]:<FROM>,<TO>:<CTAG>:::
[INCL=<INCL>];
Important parameter
STS_PATH/VT_PATH: STS-N includes STS1, STS3C, STS12C
FROM: STS traffic source. Format: STS-Slot number-Port number-STS path
number
TO: STS traffic sink. Format: STS-Slot number-Port number-STS path number
Example
To delete a one-way STS-3c cross-connection from the first STS of the LPS-OC3Q01 unit in slot 3 to the first STS of
Step Action
DLT-CRS-STS3C::STS-3-1-1,STS-1-1-1:100;
LOOPSTAR800 2003-01-06 11:39:39
M 100 COMPLD
;
2 To view whether the deletion was successful, use the following command:
If the deletion was successful, the deleted cross-connection should not be listed in the response.
DELETING BIDIRECTIONAL TRAFFIC

Deleting Bidirectional Cross-Connection Traffic
Purpose Delete two-way cross-connections (including

STS1, STS3C, STS12C and VT1)
deleted exists.
To delete two-way STS-N cross-connections, use the following commands:
Command
[INCL=<INCL>];
Important parameter
and VT1.5.
path number.
number-STS path number; VT traffic sink. Format:
VT1-Slot number-Port number-STS path number-
VT group number-VT path number.
Example
To delete a two-way STS-3c cross-connection from the first STS of the LPS-OC3Q01 unit in slot 3 to the first STS of
Step Action
DLT-CRS-STS3C::STS-3-1-1,STS-1-1-1:100;
LOOPSTAR800 2003-01-06 11:39:39
M 100 COMPLD
;
If the deletion is successful, the deleted cross-connection should not be listed in the response.
DELETING BROADCAST TRAFFIC

Deleting Broadcast Cross-Connection Traffic
Purpose Delete broadcast cross-connections (including

STS1, STS3C, STS12C and VT1.5)
the required unit
To delete broadcast cross-connections, use the commands:
Command
[INCL=<INCL>];
Important parameter
and VT1.5.
path number.
path number.
Example
To delete an STS-3c broadcast cross-connection from the first STS of the LPS-OC3Q01 unit in slot 3 to the first STS
of the LPS-XO12 unit in slot 1 and the first STS of the LPS-XO1201 unit in slot 2, perform the following operations:
Step Action
DLT-CRS-STS3C::STS-3-1-1,STS-1-1-1&STS-2-1-1:100;
LOOPSTAR800 2003-01-06 11:39:39
M 100 COMPLD
;
2 To view whether the deletion was successful, use the following command:
If the deletion was successful, the two deleted cross-connections should not be listed in the response.
Chapter 6
PERFORMANCE MONITORING
OVERVIEW
Performance monitoring deals with the monitoring and managing the various parameters that measure the
performance of an NE or a network.
Its main function is to collect, store, and report performance data, thereby providing a means for network
management to evaluate, analyze and predict network performance.
Performance monitoring offers the following operations: on-line monitoring of multiple managed NEs, collecting
performance data (including bit errors at various levels, and so on.) of network and equipment, generating historical
data of performance monitoring, threshold setting and threshold-crossing notification and performance data
reporting, and so on.
HANDLING PERFORMANCE EVENT

Before You Begin
Before issuing any TL1 commands related to performance monitoring, perform the following procedure:
Command
Configure the unit:
ENT-EQPT:[<TID>]:<AID>:<CTAG>::<CARDTYPE>:[INTFTYPE=
<INTFTYPE>]:[[<PST>],[<SST>]];
Retrieve the unit attributes:
Configure the cross connect:
[,<SST>];
Important parameter
LPS800-UM-COMM, for a detailed description of these commands.
Chapter 6: Performance Monitoring July 27, 2005
Example
Step Action
For example, to log in to the NE as a SONET user, enter:
2 Configure the unit:
ENT-EQPT::SLOT-7:100::OC3Q::OOS;
3 Retrieve the unit attribute:
RTRV-EQPT::SLOT-ALL:100;
4 Configure the cross connect:
ENT-CRS-STS1::STS-7-1-1,STS-7-2-1:C::1WAY:CKTID=A1:,RDLD;
Handling Current Data
Command
Retrieve the current data:
RTRV-PM-<MOD2>:[<TID>]:[<AID>]::<CTAG>::[<MONTYPE],
[<MONLEV>],[<LOCN>],[<DIRN>],[<TMPER>],[<MONDAT>]
[,<MONTM>];
Clear the current data:
INIT-REG-<MOD2>:[<TID>]:[<AID>]::<CTAG>::<MONTYPE>,
[<MONVAL>],[<LOCN>],[<DIRN>],[<TMPER>],[<MONDAT>]
[,<MONTM>];
Important parameter
July 27, 2005 Chapter 6: Performance Monitoring
Example
Step Action
1 Retrieve the current near-end data:
RTRV-PM-OC3::FAC-3-1:100::,0-UP,NEND,,15-MIN;
Retrieve the current far-end data:
RTRV-PM-OC3::FAC-3-1:100::,0-UP,FEND,,15-MIN;
Retrieve the current near-end and far-end data:
RTRV-PM-OC3::FAC-3-1:100::,0-UP,,,15-MIN;
2 Clear the current data:
INIT-REG-OC3::FAC-3-1:100::ALL;
3 Retrieve the current data again:
RTRV-PM-OC3::FAC-3-1:100::,0-UP,NEND,,15-MIN;
Handling History Data
Command
Retrieve the history data:
RTRV-PM-<MOD2>:[<TID>]:[<AID>]::<CTAG>::[<MONTYPE],
[<MONLEV>],[<LOCN>],[<DIRN>],[<TMPER>],[<MONDAT>]
[,<MONTM>];
Clear the history data:
INIT-REG-<MOD2>:[<TID>]:[<AID>]::<CTAG>::<MONTYPE>,
[<MONVAL>],[<LOCN>],[<DIRN>],[<TMPER>],[<MONDAT>]
[,<MONTM>];
Important parameter
Example
Step Action
1 Retrieve the history data:
RTRV-PM-OC3::FAC-3-1:100::ALL,0-UP,,,15-MIN,04-08,00-00;
2 Clear the history data:
INIT-REG-OC3::FAC-3-1:100::ALL,0,,,15-MIN,04-08,00-00;
3 Retrieve the history data again after a while; there should be a returned value:
RTRV-PM-OC3::FAC-3-1:100::ALL,0-UP,,,15-MIN,04-08,00-00;
Handling Thresholds
Command
Retrieve threshold value:
RTRV-TH-<MOD2>:[<TID>]:[<AID>]:<CTAG>[::[<MONTYPE>],
[<LOCN>],[<TMPER>]];
Set threshold value:
SET-TH-<MOD2>:[<TID>]:[<AID>]::<CTAG>::<MONTYPE>,<THLEV>,
[<LOCN>],[<DIRN>],[<TMPER>];
Important parameter
Example
Step Action
1 Retrieve the threshold:
RTRV-TH-OC3::FAC-1-2:100::CV-L,NEND,15-MIN;
Response:
LOOPSTAR800 2003-01-13 09:23:46
M 100 COMPLD
“FAC-1-2,OC3:CV-L,NEND,RCV,1500,15-MIN”
;
2 Set the threshold:
SET-TH-OC3::FAC-1-2:100::CV-L,1000,NEND,15-MIN;
3 Retrieve the threshold again:
RTRV-TH-OC3::FAC-1-2:100::CV-L,NEND,15-MIN;
Response:
LOOPSTAR800 2003-01-13 09:24:09
M 100 COMPLD
“FAC-1-2,OC3:CV-L,NEND,RCV,1000,15-MIN”
;
Here the threshold has been changed.
Other Attribute Setting Commands
Set Start Time for 24-hour Cycle
Command
SET-PMDAY:[<TID>]:<CTAG>::<PM-DAY-START>;
Important parameter
PM-DAY-START: The hour of day, ranging from 0 to 23.
Example
Input:
SET-PMDAY:::100::13;
Response:
LOOPSTAR800 2003-01-13 11:49:28
M 100 COMPLD
;
>
Retrieve Start Time for 24-hour Cycle
Command
RTRV-PMDAY:[<TID>]::<CTAG>;
Important parameter
Null
Example
Input:
RTRV-PMDAY::: 100;
Response:
LOOPSTAR800 2003-01-13 11:49:35
M 100 COMPLD
“13”
;
Set Whether to Display Automatic Report
Command
ALW-PMREPT-ALL:[<TID>]::<CTAG>;
Important parameter
Null
Example
ALW-PMREPT-ALL:::100;
Inhibit Automatic Report
Command
INH-PMREPT-ALL:[<TID>]::<CTAG>;
Important parameter
Null
Example
INH-PMREPT-ALL:::100;
Setting Performance Thresholds

Take the LPS-OC3Q01 unit in slot 3 as an example to describe how to set threshold.
Command
Retrieve the threshold:
RTRV-TH-<MOD2>:[<TID>]:[<AID>]:<CTAG>[::[<MONTYPE>],
[<LOCN>],[<TMPER>]];Set the threshold:
SET-TH-<MOD2>:[<TID>]:[<AID>]::<CTAG>::<MONTYPE>,
<THLEV>,[<LOCN>],[<DIRN>],[<TMPER>];
Important parameter
Example
Step Action
1 Retrieve the threshold:
RTRV-TH-OC3::FAC-3-1:100;
Response:
LOOPSTAR800 2003-01-13 09:23:46
M 100 COMPLD
"FAC-3-1,OC3:CV-S,NEND,RCV,1500,15-MIN"
"FAC-3-1,OC3:ES-S,NEND,RCV,50,15-MIN"
"FAC-3-1,OC3:SES-S,NEND,RCV,50,15-MIN"
"FAC-3-1,OC3:CV-L,NEND,RCV,1500,15-MIN"
"FAC-3-1,OC3:CV-L,FEND,RCV,1500,15-MIN"
"FAC-3-1,OC3:ES-L,NEND,RCV,87,15-MIN"
"FAC-3-1,OC3:ES-L,FEND,RCV,87,15-MIN"
"FAC-3-1,OC3:SES-L,NEND,RCV,1,15-MIN"
"FAC-3-1,OC3:SES-L,FEND,RCV,1,15-MIN"
"FAC-3-1,OC3:UAS-L,NEND,RCV,10,15-MIN"
"FAC-3-1,OC3:UAS-L,FEND,RCV,10,15-MIN"
2 Set the threshold:
SET-TH-OC3::FAC-3-1:100::ALL,1000,NEND,,15-MIN;
3 Retrieve the threshold again:
RTRV-TH-OC3::FAC-3-1:100::CV-L,NEND,,15-MIN;
Response:
LOOPSTAR800 2003-01-13 09:24:09
M 100 COMPLD
"FAC-1-2,OC3:CV-L,NEND,RCV,1000,15-MIN"
;
Here the threshold has been changed.
HANDLING ETHERNET ROM

Retrieving RMON Performance State
Before issuing any TL1 commands related to performance monitoring, perform the following procedure:
Retrieving Command
Command
RTRV-RMONSTAT-<MOD2>:[<TID>]:[<AID>]:<CTAG>::[<MONTYPE>],
[<MONLEVEL>];
Important parameter
MONTYPE is all the RMON parameters supported, default value is ALL.
MONLEVEL is 1-up or 0-up, show counters only equal or above 1 or zero,
default is 1-up
Example
Retrieve performance identifier of the channel 1, FE port 1 of the EFS8 in slot 6. Input:
RTRV-RMONSTAT-GETH::FAC-6-1:100::PERALL,0-UP;
Response:
"FAC-6-1,FETH:TXMULCAST,2004-12-17,14-24-45,0"
"FAC-6-1,FETH:TXBRDCAST,2004-12-17,14-24-45,0"
"FAC-6-1,FETH:RXPAUSE,2004-12-17,14-24-45,0"
"FAC-6-1,FETH:TXPAUSE,2004-12-17,14-24-45,0"
"FAC-6-1,FETH:ETHDROP,2004-12-17,14-24-45,0"
"FAC-6-1,FETH:ETHUNDER,2004-12-17,14-24-45,0"
"FAC-6-1,FETH:ETHOVER,2004-12-17,14-24-45,0"
"FAC-6-1,FETH:ETHFRG,2004-12-17,14-24-45,0"
"FAC-6-1,FETH:ETHJAB,2004-12-17,14-24-45,0"
"FAC-6-1,FETH:ETHFCS,2004-12-17,14-24-45,0"
"FAC-6-1,FETH:PKT64,2004-12-17,14-24-45,0"
"FAC-6-1,FETH:PKT65,2004-12-17,14-24-45,0"
"FAC-6-1,FETH:PKT128,2004-12-17,14-24-45,0"
"FAC-6-1,FETH:PKT256,2004-12-17,14-24-45,0"
"FAC-6-1,FETH:PKT512,2004-12-17,14-24-45,0"
"FAC-6-1,FETH:PKT1024,2004-12-17,14-24-45,0"
"FAC-6-1,FETH:RXOCTETS,2004-12-17,14-24-45,0"
Table 6-1 lists the Ethernet performance types from RMON.
Table 6-1. Fast Ethernet (FE) performance from RMON

PM type Description
ETHALI A count of frames received on a particular interface that are not an
integral number of octets in length and do not pass the FCS check.
ETHCARERR The times of carrier collision detection received.
ETHEXCCOL A count of frames for which transmission on a particular interface fails
due to excessive collisions.
ETHFCS A count of frames received on a particular interface that are an integral
number of octets in length but do not pass the FCS check.
ETHFRG The number of fragment received.
ETHJAB The total number of fuzzy packets received.
ETHLATECOL The total times of carrier collision detection in a slot time, after the last
packet is transmitted.
ETHMULCOL A count of successfully transmitted frames on a particular interface for
which transmission is inhibited by more than one collision.
ETHOVER The total number of packets received that are longer than 1518 octets
(excluding framing bits, but including FCS octets) and are otherwise
well formed.
ETHUNICOL A count of successfully transmitted frames on a particular interface for
which transmission is inhibited by exactly one collision.
ETHUNDER The total number of packets received that are shorter.
RXBRDCAST The total number of good packets received that are directed to the
broadcast address.
RXMULCAST The total number of good packets received that are directed to a
multicast address.
RXOCTETS The total number of octets of data (including those in bad packets)
received on the network (excluding framing bits but including FCS
octets).
RXPKTS The total number of packets received including those bad packets
RXPKT64 The total number of packets (including bad packets) received that are
64 octets in length (excluding framing bits but including FCS octets).
between 65 and 127 octets in length inclusive (excluding framing bits
but including FCS octets).
PM type Description
between 512 and 1023 octets in length inclusive (excluding framing
bits but including FCS octets).
between 1024 and 1518 octets in length inclusive (excluding framing
RXUNICAST The total number of good packets received that are directed to a
unicast address.
TXBRDCAST The total number of good packets transmitted that are directed to the
broadcast address.
TXDEFFRM The total number of delayed frame transmitted.
TXMULCAST The total number of good packets transmitted that are directed to a
multicast address.
TXPAUSE A count of MAC Control frames transmitted on this interface with an
OPCODE indicating the PAUSE operation.
TXPKT64 The total number of packets (including bad packets) transmitted that
are 64 octets in length (excluding framing bits but including FCS
octets).
are between 65 and 127 octets in length inclusive (excluding framing
are between 1024 and 1518 octets in length inclusive (excluding
framing bits but including FCS octets).
Enabling/Disabling RMON on Ethernet Port
Command
ED-RMONALMCTRL-<MOD2>:[<TID>]:[<AID>]:<CTAG>::[<MONTYPE>],
[RPTMODE=<RPTMODE>],[INTERVAL=<INTERVAL>],[RTHR=<RTHR>],
[FTHR=<FTHR>],[ENFLAG=<ENFLAG>];
Important parameter
<ENFLAG> is the states flag. Valid value is ENABLE or DISABLE.
Example
Enable the “RXBBAD” performance of FE port 1 of the EFS8 in slot 3. Input:
ED-RMONALMCTRL-GETH::FAC-3-1:100::RXBBAD,RPTALL,10,,,ENABLE;
Handling RMON Parameters
Command
ED-RMONALMCTRL-<MOD2>:[<TID>]:[<AID>]:<CTAG>::[<MONTYPE>],
[RPTMODE=<RPTMODE>],[INTERVAL=<INTERVAL>],[RTHR=<RTHR>],
[FTHR=<FTHR>],[ENFLAG=<ENFLAG>];
Important parameter
<RPTMODE> is the event report mode.
<INTERVAL> is the alarm sample interval.
<RTHR> is the rising threshold.
<FTHR> is the falling threshold.
Example
Step Action
1 Retrieve the current RMON parameters:
RTRV-RMONALMCTRL-ALL:::100::;
Response:
"FAC-6-1,FETH:ETHUNDER,RPTALL,10,9,0,DISABLE"
"FAC-6-1,FETH:ETHOVER,RPTALL,10,9,0,DISABLE"
"FAC-6-1,FETH:ETHFRG,RPTALL,10,9,0,DISABLE"
"FAC-6-1,FETH:ETHJAB,RPTALL,10,10,0,DISABLE"
"FAC-6-1,FETH:RXBBAD,RPTALL,10,7590,0,DISABLE"
"FAC-6-1,FETH:TXBBAD,RPTALL,10,7590,0,DISABLE"
"FAC-6-1,FETH:ETHCOL,RPTALL,10,1000,0,DISABLE"
"FAC-6-1,FETH:ETHALI,RPTALL,10,9,0,DISABLE"
"FAC-6-1,FETH:ETHFCS,RPTALL,10,9,0,DISABLE"
"FAC-6-1,FETH:ETHLATECOL,RPTALL,10,100,0,DISABLE"
"FAC-6-1,FETH:ETHEXCCOL,RPTALL,10,10,0,DISABLE"
"FAC-6-1,FETH:TXDEFFRM,RPTALL,10,9,0,DISABLE"
"FAC-6-1,FETH:ETHCARERR,RPTALL,10,1000,0,DISABLE"
"FAC-6-1,FETH:ETHCRCALI,RPTALL,10,18,0,DISABLE"
2 Change the parameters:
ED-RMONALMCTRL-FETH::FAC-6-1:100::RXBBAD,RPTALL,10,,,ENABLE;
3 Retrieve again the parameters, the threshold value has been changed:
RTRV-RMONALMCTRL-FETH::FAC-6-1:100::RXBBAD;
Response:
"FAC-6-1,FETH:RXBBAD,RPTALL,10,7590,0,DISABLE"
Handling RMON History Data
Command
ED-RMONHISTCTRL-<MOD2>:[<TID>]:[<AID>]:<CTAG>::
Intervaltype=<PRDTP>,[RECNUM=<RECNUM>],
[interval=<PRD>],[ENABLE=<ENFLAG>];
RTRV-RMONHISTCTRL-<MOD2>:[<TID>]:[<AID>]:<CTAG>::
[<PRDTP>];
Important parameter
< AID> is the access identifier of remote network monitoring. It has the format of
“FAC-<slot ID>-<port ID>”.
<PRDTP> is the period time.
Example
Step Action
1 Enable the history sampling of RMON:
ED-RMONALMCTRL-FETH::FAC-3-1:100::RXBBAD,RPTALL,10,,,ENABLE;
2 Retrieve the history sampling attributes of RMON:
RTRV-RMONHISTCTRL-FETH::FAC-3-1:100::;
Response:
"FAC-3-1,FETH:30S,50,30,ENABLE"
"FAC-3-1,FETH:30M,50,1800,ENABLE"
"FAC-3-1,FETH:PRDVAR,50,3600,DISABLE"
;
Chapter 7
ALARM MONITORING AND MANAGEMENT
This chapter describes how to monitor and manage the LoopStar 800 alarms. It consists of the following
components:
• Retrieving Alams and conditions
• Setting and retrieving alarm attributes
• Autonomous reporting of alarms
• Alarm Indication
For more information, refer to the LoopStar 800 Series Alarm and Performance Reference Manual, catalog number
LPS800-UM-PERF.
RETRIEVING ALARMS AND CONDITIONS

Several methods to retrieve alarms are described below.
Retrieving Alarms
The user can retrieve current system alarms including facility alarms and equipment alarms.
If alarm information is found, it indicates that a service path, unit or NE is faulty and that user intervention is needed.
If no alarm information is found, it indicates that all system functions are normal, and no user intervention is needed.
Alarm Retrieve Commands

Table 7-1 contains common alarm types and TL1 commands for retrieving these alarms.
Table 7-1. Alarm types and commands

Alarm type TL1 command for alarm retrieval
All alarms RTRV-ALM-ALL:[<TID>]:[<AID>]:<CTAG>:
[<NTFCNCDE>],[<CONDTYPE>],[<SRVEFF>],
[<LOCN>],[<DIRN>];
Equipment type RTRV-ALM-EQPT:[<TID>]:[<AID>]:<CTAG>:
[<LOCN>],[<DIRN>];
Signal related type RTRV-ALM-<MOD2>:[<TID>]:<AID>:<CTAG>::
[<NTFCNCDE>],[<CONDTYPE>],[<SRVEFF>];
BITS related type RTRV-ALM-BITS:[<TID>]:[<AID>]:<CTAG>:
[<LOCN>],[<DIRN>];
Synchronization type RTRV-ALM-SYNC:[<TID>]:[<AID>]:<CTAG>:
[<LOCN>],[<DIRN>];
RTRV-ALM-SYNCALL:[<TID>]:[<AID>]:<CTAG>
::[<NTFCNCDE>],[<CONDTYPE>],[<SRVEFF>],[
<LOCN>],[<DIRN>];
RTRV-ALM-SYNCFAC:[<TID>]:[<AID>]:<CTAG>
::[<NTFCNCDE>],[<CONDTYPE>],[<SRVEFF>],[
<LOCN>],[<DIRN>];
Chapter 7: Alarm Monitoring and Management July 27, 2005
Alarm Information
After an alarm retrieve command is issued, information for every alarm is returned. Alarm parameters are described
in Table 7-2.
Table 7-2. Description of alarm parameters

Parameters Description
MOD2 The second modifier of the retrieve command which identifies
the type of the entity that is retrieved. Valid value can be: ALL,
OC3, OC12, EC1, FETH, VCG, T1, T3, STS1, STS3C, STS6C,
STS9C, STS12C, VT1, EQPT, DS1, DS3, SYNC, SYNCALL,
SYNCFAC, or BITS.
AID Object, such as path and equipment components. TL1 access
identifier (AID) for the alarmed object.
AIDTYPE Object type, such as unit type, clock type and environment
type.
NTFCNCDE Alarm severity level: CR, MJ, MN, NA, NR, and CL.
CONDTYPE Error message/alarm name.
SRVEFF Service affecting/not service affecting (SA/NSA)
OCRDAT Occurrence date
OCRTM Occurrence time
LOCN The single location for which an alarm condition is being
reported.
DIRN The direction of the alarm condition.
CONDDESCR The text message associated with the alarm condition.
AIDDET The supplementary equipment identification used to identify the
location of the reported trouble.
Table 7-3 defines the alarm severity levels of the LoopStar 800.
Table 7-3. Description of alarm severity levels

Severity level Description
CR Critical
MJ Major
MN Minor
NA Not alarmed
NR Not reported
CL Cleared alarm
July 27, 2005 Chapter 7: Alarm Monitoring and Management
Example
Input
RTRV-ALM-OC12::FAC-1-1:100;
Output
LOOPSTAR800 2001-5-21 18:20:00
M 100 COMPLD
"FAC-1-1,OC12:CR,LOS,SA,2004-12-14,11-01-53,NEND,
RCV,,,:\"LOSS OF SIGNAL\","
;
Retrieving History Alarms

To retrieve history alarm, use the following command.
Command
RTRV-AO:[<TID>]::<CTAG>:::[ATAGSEQ=<ATAGSEQ>],
[MSGTYPE=<MSGTYPE>],[DBCHGSEQ=<DBCHGSEQ>];
Important Parameters
Example
RTRV-AO:::100:::MSGTYPE=ALM;
Retrieving Conditions
By retrieving conditions users can get a general idea of the various alarms and conditions in the system.
The LoopStar 800 supports a small amount of condition information, which is not required in the standards. The
condition information helps the user to use and maintain the LoopStar 800.
The command for retrieving the conditions also retrieves all the alarms simultaneously.
Condition Retrieve Commands

Table 7-4 gives common retrieval commands for conditions.
Table 7-4. Condition retrieval commands

Condition
information type Example
All RTRV-COND-ALL:::100::;
Equipment type RTRV-COND-EQPT::SLOT-1:100::;
Signal related type RTRV-COND-<MOD2>:[<TID>]:[<AID>]:
<CTAG>::[<TYPEREP>],[<LOCN>],[<DIRN>];
Examples:
RTRV-COND-STS1::STS-3-1:100::;
RTRV-COND-OC12::FAC-1-1:100::;
Condition
information type Example
BITS related type RTRV-COND-BITS::BITS-1:100::R_LOS;
Synchronization type RTRV-COND-SYNC:::100;
Condition Parameters
Table 7-5 shows the condition parameters.
Table 7-5. Description of condition parameters

the type of the entity that is retrieved. Valid value can be: ALL
SYNCFAC, or BITS.
AID Object, such as path and equipment components. TL1 access
identifier (AID) for the alarmed object.
AIDTYPE Object type, such as facility type, environment type, clock type
and equipment type.
SRVEFF SA – Service affecting; NSA – not service affecting
OCRDAT Occurrence date
OCRTM Occurrence time
reported.
CONDDESCR Condition description
Example
Input
RTRV-COND-OC12::FAC-1-1:1::LOS,NEND,RCV;
Output
LOOPSTAR800 2001-11-15 09:36:50
M 229 COMPLD
"FAC-1-1,OC12:NR,LOS,SA,2004-12-03,14-44-54,NEND,
RCV,,,:\"LOSS OF SIGNAL\","
;
SETTING AND RECEIVING ATTRIBUTE ALARMS

Setting Attribute Alarms
Purpose Set the attributes of an alarm

Prerequisite procedures Connect and log into the NE
To set the attributes of the alarm, use the following command.
Command
SET-ATTR-<MOD2>:[<TID>]:[<AID>]:<CTAG>::[<NTFCNCDE>],
[<CONDTYPE>],[<LOCN>],[<DIRN>],,[<SRVEFF>];
Example
SET-ATTR-OC12::FAC-1-1:100::CR.LOS,NEND,RCV,,SA;
Condition Parameters
Table 7-6 shows the condition parameters.
Table 7-6. Description of alarm attribute parameters

the type of the entity that is provisioned. Valid value can be:
SYNCFAC, or BITS. It must not be ALL.
AID Access identifier. Must be null.
reported.
SRVEFF Service affecting/not service affecting (SA/NSA).
Receiving Attribute of Alarms
Purpose Retrieve the attributes of an alarm

Prerequisite procedures Connect and log into the NE
To retrieve the attributes of the alarm, use the following command.
Command
RTRV-ATTR-<MOD2>:[<TID>]:[<AID>]:<CTAG>::[<NTFCNCDE>],
[<CONDTYPE>],[<LOCN>],[<DIRN>],,[<SRVEFF>];
Refer to Table 7-6.
Example
RTRV-ATTR-OC12::FAC-1-1:100::CR,LOS,NEND,RCV,,SA;
AUTONOMOUS REPORTING OF ALARMS

Alarms and conditions will be reported to the user autonomously at the time the system detects them.
Autonomous messages can be classified into signal related type, equipment type, environment type,
synchronization type and clock type.
Autonomous Messages
Table 7-7 gives the autonomous message components and Table 7-8 gives the alarm codes.
Table 7-7. Autonomous message components

AID Object, such as line, path and equipment
components.TL1 access identifier (AID) for the
alarmed object.
SRVEFF Service affecting/ not service affecting.
OCRDAT Occurrence date.
OCRTM Occurrence time.
LOCN The single location for which an alarm condition is
being reported.
CONDDESCR The text message associated with the alarm
condition.
Table 7-8. Alarm codes

Alarm Code Description
*C Critical alarm
** Major alarm
*^ Minor alarm
A^ Non-alarm message
Example
Autonomous message of equipment condition information

LOOPSTAR800 2002-04-17 11:41:24
** 186 REPT ALM EQPT
“SLOT-6:MJ,BDSTATUS,SA,2003-04-17,11:41:23,,,,,:\”Card
offline\””
;
Autonomous message of signal related alarm (LPS-OC1201)
LOOPSTAR800 2002-04-17 11:59:52
*C 390 REPT ALM OC12
“FAC-1-1:CR,R_LOS,SA,2002-04-17,11:59:50,,,,,:\”Loss of
Signal\””
;
Allow Autonomous Messages Report
Purpose Allow autonomous messages report. When a

user logins, the REPT ALM and REPT EVT
messages are allowed by default.
Prerequisite procedures Connect and log into the NE.
To allow autonomous messages report, use the following command.
Command
ALW-MSG-ALL:[<TID>]::<CTAG>;
Example
ALW-MSG-ALL:::100;
Inhibit autonomous messages report
Purpose Inhibit autonomous messages report. This

command inhibits all REPT ALM and REPT
EVT autonomous messages from being
transmitted.
Prerequisite procedures Connect and log into the NE.
To inhibit autonomous messages report, use the following command.
Command
INH-MSG-ALL:[<TID>]::<CTAG>;
Example
INH-MSG-ALL:::100;
ALARM INDICATION
Note: Please refer to the LoopStar 800 Series Hardware Description Manual, catalog number LPS800-UM-
HARD, for detailed information about the alarm indicators.
Alarm indication takes shape in the form of audible alarms and visual (LED) indications.
LED indications visually reflect the fault conditions of a certain unit, NE, or multiple NEs. According to GR-474, alarm
indication of the LoopStar 800 includes equipment-level indication and unit indication. Centralized indication for
several NEs is also provided to the central office (CO).
Unit Indicator
The unit indicator reflects the faulty condition of a single unit. If a signal alarm occurs on a certain unit, the SRV
indicator on the unit will be on.
Equipment-Level Indicator
Equipment-level indicators reflect the faulty condition of the NE. The equipment-level indicator for the LoopStar 800
is located on the system status panel, as shown in Figure 7-1.
LAMP
Replace Air Filter
TEST
Periodically
ACO
F XO-A1 SLOT4
A XO-B2 SLOT5
N SLOT3 SLOT6
CRIT
System Status
Panel MAJ
MIN
FAN
ESD PWR A
PWR B
ACO
Figure 7-1. System status panel
If any unit in the LoopStar 800 has a critical, major, or minor alarm, the CRIT, MAJ, or MIN indicator will light on the
system status panel. The CRIT, MAJ, and MIN indicators all reflect faulty conditions of the local equipment.
When the fans are faulty, the FAN indicator will light.
When the power interface unit (PIU) is faulty, the PWRA or PWRB indicator will light.
Chapter 8
UNIT CONFIGURATION
BEFORE YOU BEGIN
The element management system (EMS) should communicate normally with the NE with no alarms reported by the
NE. All units should be in their correct slots.
COMMON EQUIPMENT CONFIGURATION

Examples given in this section describe operations involving the units.
Retrieving Unit
Purpose Retrieve the already installed unit

Required Tools/Equipment NE management tool (for example, Navigator)
Prerequisite Procedures The user has logged into the NE.
Required/As Needed As needed
This chapter assumes that the following units are inserted: LPS-XO3D in slot 1 and 2, LPS-OC12 in slot 5,
LPS-EFS8 in slot 4, and LPS-PQT3 in slot 3 and 6, see Figure 8-1.
Figure 8-1. A typical unit configuration
Retrieving Software Version
Purpose Retrieve versions of the unit software

Prerequisite Procedures The unit has been created successfully. That is,
the unit is in service, and the unit software has
been loaded successfully. The user has logged
in to the NE.
Chapter 8: Unit Configuration July 27, 2005
Example
The following command retrieves the software version of the unit in slot 1:
LOOPSTAR 2005-02-02 10:09:59
M 100 RTRV
"SLOT-1::PROVTYPE=XO3D,ACTTYPE=XO3D,CLEI=0000000000,PCBVER=1.B,SWVER=5.25.02.11,
FPGAVER=(U2)120,BIOSVER=08.10.22:IS-NR"
Creating Unit
Purpose Create a unit

Prerequisite Procedures The user has logged into the NE. Before you create
a unit, there is no logic unit in the slot.
Example
The following command creates unit OC-12 in slot 5 and sets the state of the unit to “IS”:
ENT-EQPT::SLOT-5:100::OC12::IS;
LOOPSTAR 2003-01-17 10:02:48
M 100 COMPLD
To verify the unit has been created, retrieve all equipment. It should be listed in response. The command is as
follows:
LOOPSTAR 2005-02-02 10:09:59
M 100 RTRV
"SLOT-5::PROVTYPE=OC12,ACTTYPE=OC12,CLEI=SOOTAAGAAA,PCBVER=1.A,SWVER=2.11,
FPGAVER=(U17)220,BIOSVER=2.22:IS-NR"
Deleting Unit
Purpose Deleting an already installed unit

Prerequisite Procedures The user has logged into the NE. The state of
the interface/port/path is in OOS.
July 27, 2005 Chapter 8: Unit Configuration
Example
The following command deletes the unit in slot 3:
DLT-EQPT::SLOT-3:100;
LOOPSTAR 2003-01-17 10:05:40
M 100 COMPLD
To verify the unit has been deleted, retrieve slot 3. It should not be listed in the response. The commands are
as follows:
LOOPSTAR 2004-12-08 10:33:37
M 100 COMPLD
"SLOT-3:::OOS-AUMA,UEQ&UAS";
Resetting Equipment
Purpose Resetting the unit (including warm and cold

resets)
Prerequisite Procedures The user has logged into the NE. There is a unit
in the slot.
Example: Warm (“Soft”) Reset

INIT-SYS::SLOT-6:100::WARM;
SONET-NE 2004-12-08 10:40:22
M 100 COMPLD
Note: A warm reset will not interrupt service.
Example: Cold (“Hard”) Reset

INIT-SYS::SLOT-6:100::COLD;
SONET-NE 2004-12-08 10:40:22
M 100 COMPLD
CAUTION A cold reset will initialize all registers and various chips on the unit, thus interrupting service.
DSN FACILITY CONFIGURATION

This section describes the provisioning of the DSn facilities. Except where noted, this section takes the
LPS-PQT301 as an example. Refer to LoopStar 800 Series TL1 Commands Manual, catalog number
LPS800-UM-COMM, for detailed information of the corresponding commands.
Editing Path Parameters
Purpose Editing the input for each path.

Required Tools/Equipment NE management tool (for example, Navigator).
Prerequisite Procedures The user has logged into the NE.
The DSn processing unit has been created and
is in OOS state.
Step Action
1 Set output parameters of the path:
ED-T3::FAC-6-1:100:::REQ=HIGH,LBO=2,FMT=CBIT,TACC=1,SVTIMER=00-25:IS;
2 Retrieve output parameters of the path:
RTRV-T3::FAC-6-1:100;
Information retrieved:
"FAC-6-1::REQ=HIGH,LBO=2,LINECDE=B3ZS,FMT=CBIT,SVTIMER=00-25:OOS-AU,AINS&FAF"
Configuring Path Frame Format
Purpose Configure the frame format of each path.

Prerequisite Procedures The user has logged into the NE. The DSn
processing unit has been created and is in
OOS state.
Step Action
1 Set the path frame format as CBIT:
ED-T3::FAC-6-1:100:::FMT=CBIT;
2 Retrieve the path frame format:
RTRV-T3::FAC-6-1:100;
"FAC-6-1::REQ=HIGH,LBO=1,LINECDE=B3ZS,FMT=CBIT,SVTIMER=00-01:OOS-AU,AINS&FAF"
Configuring IS/OOS
Purpose Configure the current overall service condition of an entity.

Prerequisite Procedures The user has logged into the NE. The DSn processing unit
has been created.
Step Action
1 Set the current overall service condition of DS3 as in service (IS):
ED-T3::FAC-6-1:100::::IS;
2 Retrieve the service condition:
RTRV-T3::FAC-6-1:100;
"FAC-6-1::REQ=HIGH,LBO=1,LINECDE=B3ZS,FMT=CBIT,SVTIMER=00-01:IS-NR"
Configuring IS/OOS
Purpose Configure the current overall service condition of an entity.

Prerequisite Procedures The user has logged into the NE. The DSn processing unit
has been created.
Step Action
1 Set the current overall service condition of DS3 as in service (IS):
ED-T3::FAC-6-1:100::::IS;
2 Retrieve the service condition:
RTRV-T3::FAC-6-1:100;
"FAC-6-1::REQ=HIGH,LBO=1,LINECDE=B3ZS,FMT=CBIT,SVTIMER=00-01:IS-NR"
Configuring Loopback of a Tributary Path
Purpose Configure or cancel loopback of a tributary path.

Prerequisite Procedures The user has logged into the NE. XO and DSn units have
already been created.
Step Action
1 When you configure loopback of the DSn facilities, you should change the service state of the port to out
of service (OOS) first.
RMV-T3::FAC-6-1:100;
2 Set the DS3 path to facility mode:
OPR-LPBK-T3::FAC-6-1:100::,,, FACILITY;
3 Retrieve the loopback mode of the DS3 path:
RTRV-LPBK-T3::FAC-6-1:100;
"FAC-6-1::LPBKTYPE=NO_LOOP"
"FAC-6-1:LPBKTYPE=FACILITY"
4 Set the DS3 path to terminal mode:
OPR-LPBK-T3::FAC-6-1:100::,,,TERMINAL;
5 Retrieve loopback mode of DS3 path:
RTRV-LPBK-T3::FAC-6-1:100;
"FAC-6-1:LPBKTYPE=TERMINAL"
6 Release a loopback mode of DS3 path:
RLS-LPBK-T3::FAC-6-1:100;
7 Change the DS3 path from a maintenance state to the original state:
RST-T3::FAC-6-1:100;
OC-N FACILITY CONFIGURATION

The LoopStar 800 provides optical interface units of different levels such as OC-3, and OC-12. Common
configurations are described below, with the OC-12 unit used as an example. Commands for other optical interface
units are the same. Refer to the LoopStar 800 Series TL1 Commands Manual, catalog number LPS800-UM-
COMM, for detailed information.
Bit Error Threshold
Purpose Configure the bit error threshold-crossing/

degradation of B2
Prerequisite Procedures The user has logged into the NE. The OC12
unit has been created.
Step Action
1 Set the B2 bit error threshold-crossing/degradation:
ED-OC12::FAC-5-1:100:::BERSF=1E-4,BERSD=1E-6:IS;
2 Retrieve the B2 bit error threshold-crossing/degradation:
RTRV-OC12::FAC-5-1:100;
"FAC-5-1::BERSF=1E-4,BERSD=1E-6,LSRSTAT=OPEN,TSSM=Y,MANSSM=CLEAR,
SSMIN=STU,SVTIMER=00-01:IS-NR"
Facility must be OOS-MA or OOS-AUMA before traffic affecting parameters (LSRSTAT) can be edited.
Only following combinations of PST and SST are valid: IS/OOS/AINS.
The threshold of section (B1) SFBER on a facility is fixed to 1E-5, SDBER is fixed to 1E-6 and can’t be edited.
The above is to set individual bit error threshold-crossing/degradation values for B2. The settings can also be
changed with a single command:
Step Action
1 Set the bit error threshold-crossing/degradation threshold for B2:
ED-OC12::FAC-5-1:C:::BERSF=1E-4,BERSD=1E-6,TSSM=Y,SVTIMER=00-01:IS;
2 Retrieve the bit error threshold-crossing/degradation values for B2:
RTRV-OC12::FAC-5-1:100;
"FAC-5-1::BERSF=1E-4,BERSD=1E-6,LSRSTAT=OPEN,WVLEN=1560.06(NM),WVFREQ=
192.30(THZ),TSSM=Y,MANSSM=CLEAR,SSMIN=DUS,SVTIMER=00-01:OOS-AU,AINS&FAF"
Configuring J1 Byte
Purpose Configure and retrieve the J1 byte.

Prerequisite Procedures The user has logged into and the OC12 unit has been
created.
This command is available only if cross-connect and
service have been created.
Bidirectional traffic from OC-N unit to DSn unit has
been created.
Step Action
1 Set the J1 path tracing mode to AUTO:
ED-STS1::STS-5-1-1:100:::J1TRCMODE=AUTO:IS;
2 Retrieve the J1 path tracing mode:
"STS-5-1-1::BERSF=1E-4,BERSD=1E-6,J1TRCMODE=AUTO,EXPTRCJ1=SONET,TRCJ1=SONET,
INCTRCJ1=ADC,EXPTRCC2=LOAD,TRCC2=LOAD,INCTRCC2=UNLOAD:IS-NR";
3 Set the J1 byte to be transmitted:
ED-STS1::STS-5-1-1:100:::TRCJ1=ADC;
4 Retrieve the J1 byte to be transmitted:
"STS-5-1-1::BERSF=1E-4,BERSD=1E-6,J1TRCMODE=AUTO,EXPTRCJ1=SONET,TRCJ1=ADC,
INCTRCJ1=ADC,EXPTRCC2=LOAD,TRCC2=LOAD,INCTRCC2=UNLOAD:IS-NR";
5 Set the J1 byte to be received:
ED-STS1::STS-5-1-1:100:::EXPTRCJ1=ADC;
6 Retrieve the J1 byte to be received:
"STS-5-1-1::BERSF=1E-4,BERSD=1E-6,J1TRCMODE=AUTO,EXPTRCJ1=ADC,
TRCJ1=ADC,INCTRCJ1=ADC,EXPTRCC2=LOAD,TRCC2=LOAD,INCTRCC2=UNLOAD:IS-NR";
Configuring C2 Byte
Purpose Configure and retrieve the C2 byte.

Prerequisite Procedures The user has logged into and the OC12 unit has
already been created.
Bidirectional traffic from OC-N unit to DSn unit has
been created.
Step Action
1 Set the C2 byte to be transmitted as VT-STS1:
ED-STS1::STS-5-1-1:100:::TRCC2=VT-STS1;
2 Retrieve the C2 byte to be transmitted:
"STS-5-1-1::BERSF=1E-4,BERSD=1E-6,J1TRCMODE=OFF,EXPTRCJ1=ADC,TRCJ1=ADC,
INCTRCJ1=ADC,EXPTRCC2=LOAD,TRCC2=VT-STS1,INCTRCC2=UNLOAD:IS-NR";
3 Set the C2 byte to be received:
ED-STS1::STS-5-1-1:100::: EXPTRCC2=VT-STS1;
4 Retrieve the C2 byte to be received:
"STS-5-1-1::BERSF=1E-4,BERSD=1E-6,J1TRCMODE=OFF,EXPTRCJ1=ADC,TRCJ1=ADC,
INCTRCJ1=ADC,EXPTRCC2=VT-STS1,TRCC2=VT-STS1,INCTRCC2=UNLOAD:IS-NR";
Configuring IS/OOS
Purpose Configure and retrieve IS/OOS states.

Required Tools/Equipment NE management tool (for example: Navigator)
Prerequisite Procedures The user has logged in to and the OC12 unit
has been created.
Step Action
1 Set status of the optical interface to In Service:
ED-OC12::FAC-5-1:100::::IS;
2 Retrieve status of the optical interface IS/OOS:
RTRV-OC12::FAC-5-1:100;
"FAC-5-1::BERSF=1E-4,BERSD=1E-6,TSSM=Y,MANSSM=CLEAR,SSMIN=DUS,
SVTIMER=00-01:IS-NR"
3 Set status of the optical interface as Out Of Service:
ED-OC12::FAC-5-1:100::::OOS;
4 Retrieve status of the optical interface IS/OOS:
RTRV-OC12::FAC-5-1:100;
"FAC-5-1::BERSF=1E-4,BERSD=1E-6,TSSM=Y,MANSSM=CLEAR,SSMIN=DUS,
SVTIMER=00-01:OOS-MA,SGEO"
Configuring Loopback for OC-N facilities
Purpose Looping back the optical interface

Prerequisite Procedures The user has logged into and the OC12 unit
has been created.
Step Action
1 When you configure loopback of the OC-N facilities, you should change the service state of the port to out
of service (OOS) first.
RMV-OC12::FAC-5-1:100;
2 Set the port to facility mode:
OPR-LPBK-OC12::FAC-5-1:100::,,,FACILITY;
3 Retrieve the loopback mode of the port:
RTRV-LPBK-OC12::FAC-5-1:100;
"FAC-5-1:LPBKTYPE=FACILITY"
4 Set the port loopback to terminal mode:
OPR-LPBK-OC12::FAC-5-1:100::,,,TERMINAL;
Step Action
5 Retrieve the port loopback mode:
RTRV-LPBK-OC12::FAC-5-1:100;
"FAC-5-1:LPBKTYPE=TERMINAL"
6 Release a loopback mode of OC-N:
RLS-LPBK-OC12::FAC-5-1:100;
7 Change the OC-N from a maintenance state to the original state:
RST-OC12::FAC-5-1:100;
Note: The loopback of STS facilities are similar to the loopback for OC-N.
Performing Laser Operations
Purpose Perform common operations on the laser

Prerequisite Procedures The user has logged into and the OC12 unit has
been created.
Step Action
1 When you perform laser operation, you should change the service state of the port to out of service
(OOS) first.
RMV-OC12::FAC-5-1:100;
2 Start/shut down the laser:
ED-OC12::FAC-5-1:100:::LSRSTAT=CLOSE:OOS;
3 Retrieve the OPEN/CLOSE status of the laser:
RTRV-OC12::FAC-5-1:100;
“FAC-5-1::BERSF=1E-3,BERSD=1E-6,LSRSTATE=CLOSE,TSSM=N,MANSSM=CLEAR,
SSMIN=DUS,SVTIMER=00-01:IS-NR”
ETHERNET FACILITY CONFIGURATION

Configuring FE Port
Purpose Configure the following attributes of fast

Ethernet port:
• Work mode
• Flow control attribute
• The maximum packet length
• Port enable status
• Tag type of the port
• VLAN ID of the port (PVID)
• Priority of the default VLAN for the port
• Service VLAN ID of the port (PSVID)
• Priority of the default service VLAN for the
port (PSVPRI)
• Service VLAN tag attribute of the port
(STAGTYPE)
• Service VLAN enable attribute of the port
(SVENABLE)
• Primary state of the port
• Loopback mode of the port on MAC layer
• Loopback mode of the port on physical
layer
Required Tools/Equipment NE management tool (for example: Navigator)
Prerequisite Procedures The user has logged in. The LPS-XO unit and
LPS-EFS8 have already been created.
Before editing the attribute of the port or
operating a loopback, the state of the port
should be OOS-MA.
List of Values Refer to the LoopStar 800 Series TL1
Commands Manual, catalog number LPS800-
UM-COMM, for the values of each parameter.
Step Action
1 Set the work mode of the Fast Ethernet port to auto-negotiation mode:
ED-FETH::FAC-4-1:100:::WORKMODE=AUTO;
2 Disable the flow control of the port:
ED-FETH::FAC-4-1:100:::FLOWCTRLAUTO=DISABLE;
3 Set the maximum packet length to 1522:
ED-FETH::FAC-4-1:100:::MTU=1522;
4 Enable the port:
ED-FETH::FAC-4-1:100:::PORTENABLE=Y;
5 Set the tag type of port to ACCESS:
ED-FETH::FAC-4-1:100:::TAGTYPE=ACCESS;
6 Set the PVID to 22, and set the PVPRI to 2:
ED-FETH::FAC-4-1:100:::PVID=22,PVPRI=2;
Step Action
7 Set the service VLAN tag type of port to TAGAWARE:
ED-FETH::FAC-4-1:100:::STAGTYPE=TAGAWARE;
8 Set the PSVID to 1000, and set the PSVPRI to 7:
ED-FETH::FAC-4-1:100:::PSVID=1000,PSVPRI=7;
9 Disable the service VLAN attribute of the port:
ED-FETH::FAC-4-1:100:::SVENABLE=Y;
10 Set the Ethernet port state to IS:
ED-FETH::FAC-4-1:100::::IS;
Note: Step 1 through Step 10 can be accomplished using one command:

ED-FETH::FAC-4-1:100:::WORKMODE=AUTO,FLOWCTRL=DISABLE,
MTU=1522,PORTENABLE=Y,TAGTYPE=ACCESS,PVID=22,PVPRI=2,
PSVID=1000,PSVPRI=7,STAGTYPE=TAGAWARE,SVENABLE=N:IS;
Note: When setting multiple attributes through one command, if an error message is retrieved, it
does not mean that all the attributes fails to be set. The attributes with correct parameter will be
set and remained until next modification. Check for the wrong parameter and reconfigure it. If
“SVENABLE=Y”, then the STAGTYPE must be “TAGWARE”.
11 Retrieve the configuration result of the fast Ethernet port::

RTRV-FETH::FAC-4-1:100;
"FAC-4-1::WORKMODE=AUTO,ACTWORKMODE=FULL100M,FLOWCTRL=DISABLE,
ACTFLOWCTRL=DISABLE,MACLPBK=RLB,PHYLPBK=NOLB,MTU=1522,PORTENABLE=Y,
ACTPORTENABLE=Y,TAGTYPE=ACCESS,PVID=22,PVPRI=2,PSVID=1000,PSVPRI=7,
STAGTYPE=TAGAWARE,SVENABLE=Y:IS-NR"
12 Set the loopback mode on MAC layer to loopback:
OPR-LPBK-FETH::FAC-4-2:100::FACILITY:LPBKMODE=MAC;
13 Set the loopback mode on MAC layer to no loopback:
RLS-LPBK-FETH::FAC-4-1:100;
14 Set the loopback mode on physical layer to loopback:
OPR-LPBK-FETH::FAC-4-2:100::FACILITY:LPBKMODE=PHY;
15 Set the loopback mode on physical layer to no loopback:
RLS-LPBK-FETH::FAC-4-1:100;
Configuring VCG
Purpose Configure the following attributes of VC

group port:
• Path type, the time slot number of up
direction and the time slot number of down
direction.
• Encapsulation protocol and its attributes
• Tag type of the port
• VLAN ID of the port (PVID)
• Priority of the default VLAN for the port
• Service VLAN ID of the port (PSVID)
• Priority of the default service VLAN for the
port (PSVPRI)
• Service VLAN tag attribute of the port
(STAGTYPE)
• Service VLAN enable attribute of the port
(SVENABLE)
• Primary state of the port
Prerequisite Procedures The user has logged into. The XO unit and
EFS8 have already been created.
Before edit the attribute of the port, the state of
the port should be in OOS-MA.
Commands Manual, catalog number
LPS800-UM-COMM, for the values of each
parameter.
Step Action
1 Set the path type of VCG to STS1V, the UPPATH to 1, the DOWNPATH to 1:
ED-VCG::VCG-4-1:100::: PATHTYPE=STS1V,UPPATH=1,DOWNPATH=1
2 Set the protocol to GFP and its attributes:
ED-VCG::VCG-4-1:100:::PROTOCOL=GFP,SCRAMBLER=X43,FCSTYPE=FCS32,
ENDIAN=LITTLE,EXTHDR=Y;
3 Set the tag type of port to TAGWARE:
ED-VCG::VCG-4-1:100:::TAGTYPE=TAGWARE;
4 Set the PVID to 1, and set the PVPRI to 0:
ED-VCG::VCG-4-1:100:::PVID=1,PVPRI=0;
5 Set the service VLAN tag type of port to TAGAWARE:
ED-VCG::VCG-4-1:100:::STAGTYPE=TAGAWARE;
6 Set the PSVID to 1000, and set the PSVPRI to 7:
ED-VCG::VCG-4-1:100:::PSVID=1000,PSVPRI=7;
Step Action
7 Disable the service VLAN attribute of the port:
ED-VCG::VCG-4-1:100:::SVENABLE=Y;
8 Set the VCG state to IS:
ED-VCG::VCG-4-1:100::::IS;
Note: Step 1 to Step 8 can be accomplished via one command:

ED-VCG::VCG-4-1:100:::PATHTYPE=STS1V,UPPATH=1,DOWNPATH=1,
PROTOCOL=GFP,SCRAMBLER=X43,FCSTYPE=FCS32,ENDIAN=LITTLE,
EXTHDR=Y,TAGTYPE=TAGAWARE,PVID=1,PVPRI=0,PSVID=1000,
PSVPRI=7,STAGTYPE=TAGAWARE:OOS;
Note: When setting multiple attributes through one command, an error message does not mean
all the attributes failed to be set. The attributes with correct parameters will be set and remain
until the next modification. Check for the wrong parameter and reconfigure it.
9 Retrieve the configuration result of the Fast Ethernet port:

RTRV-VCG::VCG-4-1:100;
"VCG-4-1::PATHTYPE=STS1V,UPPATH=1,ACTUPPATH=1,DOWNPATH=1,ACTDOWNPATH=1,
PROTOCOL=GFP,SCRAMBLER=X43,FCSTYPE=FCS32,ENDIAN=LITTLE,EXTHDR=Y,
TAGTYPE=TAGAWARE,PVID=1,PVPRI=0,PSVID=1000,PSVPRI=7,
STAGTYPE=TAGAWARE,SVENABLE=Y:IS-NR"
Configuring Committed Access Rate (CAR)
Purpose Create, edit, retrieve, and delete a CAR entry of

the Ethernet unit
Prerequisite Procedures The user has logged into. The LPS-XO unit and
LPS-EFS8 have already been created.
Commands Manual, catalog number LPS800-
UM-COMM, for the values of each parameter.
Step Action
1 Create and enable a CAR entry. The committed information rate is 10240 Kbps; the peak information rate
is 20480 Kbps; the delta committed burst size is 10 Kbps; the delta maximum burst size is 15 Kbps:
ENT-CAR::CAR-4-10:100:::ENABLE=Y,CIR=10240,DELTACBS=10,PIR=20480,DELTAMBS=15;
2 Retrieve this CAR entry:
RTRV-CAR::CAR-4-10:100;
“CAR-1-10:ENABLE=Y,CIR=10240,DELTACBS=10,PIR=20480,DELTAMBS=15”
3 Disable this CAR:
ED-CAR::CAR-4-10:100:::ENABLE=N;
4 Delete this CAR entry:
DLT-CAR::CAR-4-10:100;
Configuring Flow Control
Purpose Create, retrieve, and delete a flow entry of the

Ethernet unit
Required Tools/Equipment Telnet tool (HyperTerminal of Microsoft
Windows) and TL1.
Prerequisite Procedures The user has logged in to. The LPS-XO unit and
LPS-ET4GS have already been created. VLAN
ID and CAR entry has been created and
enabled.
List of Values Refer to the LoopStar 800 TL1 Commands
Manual, catalog number LPS800-UM-COMM-
01, for the values of each parameter.
Step Action
1 Create and enable a VLAN flow entry based on “CAR-4-10”. The forwarding priority based on VLAN ID
and its priority is 1 (“0” means the lowest priority):
ENT-FLOW::VCG-4-1-1:100:::CARID=CAR-4-10,PRIMODE=VLANID,FWDPRI=1;
2 Retrieve this flow entry:
RTRV-FLOW::VCG-4-1-1:100;
“VCG-4-1-1:CARID=CAR-4-10,PRIMODE=VLANID,FWDPRI=1”
3 Delete this flow entry:
DLT-FLOW::VCG-4-1-1:100;
Configuring Ethernet Link
Purpose Create, retrieve, and delete a link entry of the

Ethernet unit

Windows) and TL1
Prerequisite Procedures The user has logged in to. The LPS-XO unit and
LPS-ET4GS have already been created. VLAN
ID has been created and enabled.
Step Action
1 Create and enable a link entry:
ENT-LINK:LINK-4-10:100:::FROM=VCG-4-1-1,TO=VCG-4-2;
2 Retrieve this link entry:
RTRV-LINK::LINK-4-10:100;
“LINK-4-10:FROM=VCG-4-1-1,TO=VCG-4-2,CTYPE=1WAY”
3 Delete this flow entry:
DLT-LINK::LINK-4-10:100;
Label Switch Path (LSP)

Purpose Create, retrieve, and delete a label switch path
of the Ethernet unit.
Windows) and TL1.
Prerequisite Procedures The user has logged in to. The LPS-XO unit
and LPS-ET4GS have already been created.
VLAN ID has been created and enabled.
Step Action
1 Create and enable an ingress label switch path:
ENT-LSP:LSP-4-10:100:::FROM=FAC-4-2,TO=VCG-4-4,OUTTNLABEL=20,OUTVCLABEL=30;
2 Retrieve the attribute of this label switch path:
RTRV-LSP::LSP-4-10:100;
“LSP-4-10:FROM=FAC-4-2,TO=VCG-4-4,OUTTNLABEL=20,OUTVCLABEL=30,CTYPE=1WAY”
3 Delete this label switch path:
DLT-LSP::LSP-4-10:100;
Appendix A
PRODUCT SUPPORT
ADC Customer Service Group provides expert pre-sales support and training for all of its products. Technical
support is available 24 hours a day, 7 days a week by contacting the ADC Technical Assistance Center.
Sales Assistance: 800.366.3891 Quotation Proposals, Ordering and Delivery General,

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

System Administration Manual
Product Catalog: LPS-FRM8xx-Lx

Document Number: LPS800-UM-ADMN-03
´-@M¶2v¨
1332452

Loopstar 800 Series: System Administration Manual

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Loopstar 800 Series: System Administration Manual

Uploaded by

Copyright:

Available Formats

LoopStar® 800 Series

System Administration Manual

Product Catalog: LPS-FRM8xx-Lx

Revision Release Date Revisions Made

Chapter 3: System Level Provisioning ......................................................................... 3-1

Overview ............................................................................................................................ 4-8

Chapter 7: Alarm Monitoring and Management .......................................................... 7-1

Ethernet Facility Configuration ............................................................................................... 8-12

Reader Alert Meaning

Reader Alert Meaning

INSPECTING YOUR SHIPMENT

BEFORE YOU BEGIN

Purpose To specify the hardware installation environment

Table 1-1. Requirement for temperature and humidity

Environment for EMS Installation

Purpose To define element management system (EMS)

Power and Grounding

Purpose Ensure power access and grounding mode of the

Figure 1-1. PIU faceplate

Figure 1-2. Grounding flag

Purpose Making sure the user can insert or remove the

Removing the Unit

Inserting the Unit

Purpose Setting the IP address of the NE

Note: After modifying the IP Address, the NE should be restarted manually.

LOGGING INTO THE NE

Figure 1-3. Input NE Management Tool IP Address

Figure 1-4. Input NE Management Tool username and password

Figure 1-5. NE Management Tool connection prompt

SENDING A COMMAND TO THE NE

Using the GUI to Send a Command to the NE

Displaying Command Help

SONET-NE 2004-12-06 14:10:31

/*INVALID SYNTAX OR PUNCTUATION*/

UID: string, max length is 16.

PID: string, max length is 16;

USER ACCOUNTS TYPES

Table 2-1. Default UIDs

RETRIEVING USER INFORMATION

CREATING USER ACCOUNTS

Note: If using port 23, the login process will be interactive.

2 Enter the following command:

MODIFYING A USER’S ATTRIBUTES

MODIFYING USER PASSWORDS

Modify another user’s password:

Modify the password of user ADC to HAPPY_NEW_YEAR as user SONET:

DISABLING AND ENABLING USER ACCOUNTS

Enable the accounts of user ADC:

Purpose Retrieve the current IP address of the NE.

To retrieve the NE IP address in the LPS-8xx, use the following command.

Purpose Set the IP address of the NE

To set the NE IP address in the LPS-8xx, use the following command.

After modifying the IP Address, it is recommended to restart the NE manually.

Figure 3-1. IP address example for a simple network with chain

Figure 3-2. IP address example for two networks interconnected by routers

Retrieving an NE Subnet Mask

Purpose Retrieve the current subnet mask of the NE.

Setting an NE Subnet Mask

Purpose Set the current subnet of the NE

PROVISIONING STATIC ROUTE FOR IP OVER DCC

Creating a Static Route

Purpose Create an IP over DCC route

To create an IP over DCC route, use the following command.

/INVALID SYNTAX OR PUNCTUATION/