323-1801-190

Nortel Networks
OPTera Long Haul 1600
Optical Line System
TL1 Interface Description

Rel 3 Standard July 2000

What’s inside...
Interface configurations
Administrative interface
Surveillance interface
TL1 commissioning
Copyright  2000 Nortel Networks, All Rights Reserved.

The information contained herein is the property of Nortel Networks and is strictly confidential. Except as expressly authorized in
writing by Nortel Networks, the holder shall keep all information contained herein confidential, shall disclose it only to its employees
with a need to know, and shall protect it, in whole or in part, from disclosure and dissemination to third parties with the same degree
of care it uses to protect its own confidential information, but with no less than reasonable care. Except as expressly authorized in
writing by Nortel Networks, the holder is granted no rights to use the information contained herein.

Nortel Networks, the Nortel Networks logo, the Globemark, How the World Shares Ideas, S/DMS TransportNode, OPTera, Preside,
and Unified Networks are trademarks of Nortel Networks.

UNIX is a trademark of X/Open Company, Ltd.

VT100 is a trademark of Digital Equipment Corporation.

Printed in Canada and in the United Kingdom

 iii

Contents 0
About this document vii

Introduction to TL1 1-1

TL1 overview 1-1
OPTera Long Haul 1600TransportNode TL1 interface 1-1
Standards compliance 1-4
TL1 interface types 1-4
TL1 connectivity 1-5
TL1 message overview 1-7
Setting an identification parameter 1-11
List of procedures
1-1 Setting and retrieving a TL1 TID from an operations system 1-12
1-2 Setting a TL1 TID through the OPC user interface 1-17

Interface configurations 2-1

TL1 configuration 2-1
TL1 configuration requirements 2-1
TL1 default operation 2-2
X.25 configuration 2-2
X.25 configuration requirements 2-2
X.25 default configuration 2-4
X.25 communications 2-5
X.25 troubleshooting guidelines 2-6
TARP support for interoperability in mixed networks 2-7
Application layer protocols 2-7
TARP 2-7
List of procedures
2-1 Defining and enabling TCP/IP communications 2-9

Administrative interface 3-1

Non-autonomous administrative messages 3-2
ACT-USER (activate user session) 3-3
CANC-USER (cancel user session) 3-4
DLT-USER-SECU (delete user security) 3-5
ED-USER-SECU (edit user security) 3-6
ENT-USER-SECU (enter user security) 3-7
RTRV-USER-SECU (retrieve user security) 3-8

TL1 Interface Description 323-1801-190 Rel 3 July 2000

iv Contents

Administering user accounts on the active OPC through TL1 3-9

User privileges 3-9
UserID and password formats 3-12
TL1 message notation 3-12
Error responses 3-13
List of procedures
3-1 Opening a TL1 administration session 3-16
3-2 Closing a TL1 administration session 3-18
3-3 Retrieving security parameters for a CUA user 3-20
3-4 Adding a user account to the CUA 3-22
3-5 Editing security parameters for a CUA user 3-24
3-6 Deleting a CUA user account 3-28

Surveillance interface 4-1

TL1 message notation 4-2
Message parameters 4-2
ACTID 4-3
AID 4-4
AIDTYPE 4-5
ALMCDE 4-5
ALMMSG 4-6
ALMTYPE 4-6
ATAG 4-6
CONDDESCR 4-7
CONDEFF 4-7
CONDTYPE 4-7
CTAG 4-10
Date 4-10
DATE 4-11
DIRN 4-11
DUR 4-12
ERRCDE 4-12
LOCN 4-12
MODE 4-13
MODETYPE 4-13
MONDAT 4-13
MONLEV 4-14
MONTM 4-14
MONTYPE 4-15
MONVAL 4-15
NTFCNCDE 4-17
OCRDAT 4-17
OCRTM 4-17
PMSTATE 4-18
REF 4-18
SCCM 4-19
SID 4-19
SRVEFF 4-20
STATE 4-20
STBYID 4-20

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Contents v

THLEV 4-20
TID 4-20
Time 4-21
TIME 4-21
TMPER 4-21
TYPEREQ 4-22
VLDTY 4-22
TL1 acknowledgment responses and error codes 4-23
Acknowledgment responses 4-23
Error codes 4-24
Alarm summary 4-25
Message types 4-25
Message intervals and PM considerations 4-28
Autonomous messages 4-30
REPT ALM (report alarm) 4-30
REPT ALM ENV (report alarm environment) 4-33
REPT COND (report condition) 4-34
REPT EVT (report event) 4-36
REPT PM (report performance monitoring) 4-39
REPT SW (report switch) 4-43
Non-autonomous messages 4-45
ALW-MSG (allow messages) 4-45
ALW-PMREPT (allow performance monitoring report) 4-46
ED-DAT (change OPC date and time) 4-48
INHIBIT-MSG (inhibit messages) 4-51
INH-PMREPT (inhibit performance monitoring report) 4-53
INIT-REG (initialize register) 4-55
OPR-EXT-CONT (operate external controls) 4-58
OPR-SYNCNSW (Operate Synchronization Switch) 4-60
RLS-EXT-CONT (release external controls) 4-62
RLS-SYNCNSW (release synchronization switch) 4-64
RTRV-ALM (retrieve alarm) 4-66
RTRV-ALM-ENV (retrieve alarm environment) 4-69
RTRV-COND (retrieve condition) 4-71
RTRV-HDR (retrieve header) 4-75
RTRV-PM (retrieve performance monitoring) 4-77
RTRV-PMMODE (retrieve performance monitoring) 4-79
RTRV-TH (retrieve performance monitoring threshold) 4-81
SET-PMMODE (set performance monitoring mode) 4-84
SET-SID (set source identifier) 4-86
SET-TH (set performance monitoring threshold) 4-88
Message associations 4-91
Alarm tables 4-91

TL1 commissioning 5-1

Configuring and accessing TL1 interfaces 5-1
Configuring the TL1 Interface Router Service 5-2
TL1 Interface Merge 5-2
List of procedures
5-1 Completing an X.25 worksheet 5-5

TL1 Interface Description 323-1801-190 Rel 3 July 2000

vi Contents

5-2 Defining and enabling X.25 communications on the OPC X.25 port 5-17
5-3 Configuring virtual circuit profiles 5-34
5-4 Restarting the TL1 Session Manager 5-40
5-5 Querying active TL1 sessions 5-42
5-6 Accessing and exiting TL1 interfaces through the UNIX shell tool 5-44
5-7 Configuring and enabling the TL1 Interface Router Service over X.25 or
TCP/IP 5-46
5-8 Configuring TL1 over TCP/IP 5-71

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 vii

About this document 0

This document contains TL1 interface descriptions for the Nortel Networks
OPTera Long Haul 1600 Optical Line System (formerly OPTera LH) Repeater,
Combiner, and 1600G Amplifier network elements. Topics covered include:
• features and common behavior of the TL1 interface
• non-autonomous and autonomous surveillance message types
• interface configuration
• TL1 parameters

Audience
This document is for the following members of the operating company:
• planners
• provisioners
• network administrators
• transmission standards engineers
• maintenance personnel

TL1 Interface Description 323-1801-190 Rel 3 July 2000

viii About this document

OPTera Long Haul 1600 NTP Library (NTCA65EA)

The following figure shows the documentation structure of the OPTera Long
Haul 1600 NTP Library
OTP1152

Network

16 OR r
Applications

00
G Plu
M
Supported

C
R

om r

Am s
ep
ea

bi

pl
ne

ifi
te

er
Library Introduction, List of Terms, and Master Topical Index

323-1801-091 About the OPTera Long Haul 1600 Library

Engineering and Planning

NTY311AX Repeater Network Application Guide

NTY312AX Combiner Network Application Guide
NTY314AX 1600G Amplifier Network Application Guide
NTY312DX 100 GHz MOR Plus 2 to 32-λ Optical Layer Applications Guide
NTY311DX 200 GHz MOR/MOR Plus 2 to 16-λ Optical Layer Applications Guide
NTY313DX MOR Plus Optical Add/Drop Applications Guide
NTY314DX MOR Plus Optical Layer OAM&P Guide
NTY315DX 1600G Amplifier Optical Layer Applications Guide
NTY317DX 1600G Amplifier Optical Layer OAM&P Guide
NTCA66CA SONET Orderwire User Guide
NTCA66DA SDH Orderwire User Guide
323-1801-190 TL1 Interface Description
323-1801-195 Network Element User Interface Description
323-1801-196 OPC User Interface Description
323-1801-197 1600G Amplifier Fiber Assist Tool Description

Installation, Commissioning, and Testing

323-1801-201 Installation Procedures

323-1801-220 Powering Up and Commissioning Procedures
323-1801-221 Site Testing Procedures
323-1801-222 System Commissioning and Testing Procedures
323-1801-225 MOR Plus SLAT and Upgrade Procedures
323-1801-226 1600G Amplifier SLAT and Upgrade Procedures

Operations, Administration, and Provisioning

323-1801-301 User Interface Connection Procedures

323-1801-302 External Interface Configuration Procedures
323-1801-303 Software Administration Procedures
323-1801-304 Data Administration Procedures
323-1801-305 Security Management Procedures
323-1801-310 Provisioning and Operations Procedures
323-1801-311 Protection Switching Procedures
323-1801-315 MOR Plus Provisioning Procedures
323-1801-316 1600G Amplifier Provisioning Procedures

-continued-

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 About this document ix

OTP1153

Network

16
Applications

00 R P
G
M
Supported

C
R

O
om r

Am s
ep
ea

bi

pl
ne

lu

ifi
te

er
r
Maintenance

323-1801-520 Performance Monitoring Procedures

323-1801-541 Fault Detection
323-1801-542 Alarm Reference Guide
323-1801-543 Trouble Clearing and Module Replacement
323-1801-545 MOR Plus Alarm Clearing and Module Replacement
323-1801-546 1600G Amplifier Alarm Clearing and Module Replacement
323-1801-840 Log Reference

Supporting Documentation to the OPTera Long Haul 1600 Library (not part of this library)
323-1301-XXX OC-192 NTP Library
323-1321-XXX TN-64X NTP Library
323-1201-XXX OC-48 NTP Library
323-1211-XXX TN-16X NTP Library
450-3101-XXX Preside Documentation
NTR710AM Optical Networks Data Communications Planning Guide
NTCA65DA OPTera Connect DX NTP Library (OPTera Connect DX SONET platform)
NTCA65FA OPTera Connect DX NTP Library (OC-192 platform)
NTCA65GA OPTera Connect DX NTP Library (OPTera Connect DX SONET & OC-192 platforms)
NTCA65JA OPTera Connect DX NTP Library (OPTera Connect DX SDH platform)
NTCA65AC TN-64X Rel 3 NTP Library
NTCA65KA OPTera Connect DX NTP Library (OPTera Connect DX SDH & TN-64X platforms)

References
This document refers to the following Nortel Networks technical publications
(NTP) that are specific to the OPTera Long Haul 1600 Library:
• Powering Up and Commissioning Procedures, 323-1801-220
• Performance Monitoring Procedures, 323-1801-520
• Fault Detection, 323-1801-541
• Trouble Clearing and Module Replacement, 323-1801-543
• OPC User Interface Description, 323-1801-196
• User Interface Connection Procedures, 323-1801-301
• External Interface Configuration Procedures, 323-1801-302
• Data Administration Procedures, 323-1801-304
• Security Management Procedures, 323-1801-305
• Log Reference, 323-1801-840

TL1 Interface Description 323-1801-190 Rel 3 July 2000

x About this document

TL1 Procedures Summary

Main tasks
• Setting, changing or retrieving a TID or OPCTID from an operations system (Procedure 1-1)
— Establish a connection to the TL1 interface of the OPC
— Set, change or retrieve the TID by issuing the corresponding message
— Issue a message to confirm or display the new TID

• Setting, changing or retrieving a TID using the OPC interface (Procedure 1-2)
— Have the user id and password for OPC
— Log into the OPC
— Open the Unix shell tool, in the OPC Admin section
— View the table with the current NEid, NEname, OPCTID and TID for all NEs in the span of control
— Issue a message to define or change the TID or OPCTID
— Exit the Unix shell tool

• Defining and enabling TCP/IP communications to access TL1 surveillance (Procedure 2-1)
— Use a terminal connected to an OPC (User Interface Connection Procedures, 323-1801-301)
— Log into the OPC and display the user session manager
— Create a user with the Centralized User Administration (CUA) tool
— Log out of the user session manager
— Select the TL1 surveillance interface or enhanced TL1 surveillance interface from the OPC prompt
— Enter the password file
— Make a copy of the password file
— Log out of OPC

• Opening and closing a TL1 administration session (Procedure 3-1)

— Obtain a password and user id for admin or root user groups
— Establish a connection to the TL1 interface of the OPC
— Issue a message to open a TL1 administration session
— Issue a message to close a TL1 administration session

• Retrieving security parameters for a CUA user (Procedure 3-3)

— Open a TL1 administration session (Procedure 3-1)
— Issue a message to retrieve security parameters

• Adding a user account to the CUA (Procedure 3-4)

— Obtain the user id of the existing user account
— Have the password for new user account
— Open a TL1 administration session (Procedure 3-1)
— Issue a message to add a user account

—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 About this document xi

• Editing security parameters for a CUA user (Procedure 3-5)

— Obtain the user id of the existing user account
— Have the password for new user account
— Open a TL1 administration session (Procedure 3-1)
— Issue the message to edit security parameters

• Deleting CUA user account (Procedure 3-6)

— Open a TL1 administration session (Procedure 3-1)
— Obtain the user id of the account you want to delete
— Issue the message to delete security parameters

• Completing an X.25 worksheet (Procedure 5-1)

— Obtain the listing of the X.25 parameters for your connection
— Determine the speed of service you want for your receiver and transmitter
— Determine which facilities you require
— Determine if you require any specific values for the rest of the X.25 parameters
— Determine which facilities you require
— Contact service provider and request an X.25 connection

• Defining and enabling X.25 communications on the OPC X.25 port (Procedure 5-2)
— Obtain a userID and password, at the root or admin class level
— Complete X.25 worksheet
— Log into OPC
— Open a TL1 configuration tool
— Select to configure an X.25 port
— View X.25 parameters
— Accept or change X.25 parameters
— Create the configuration file from the X.25 menu
— Enable X.25 from the configure menu

• Configuring virtual circuit profiles (Procedure 5-3)

— Obtain a userID and password that allows you to access the OPC at the root level
— Configure a virtual circuit profile from the TL1 Configuration Main Menu
— Select to add a virtual circuit profile, delete a virtual circuit profile, define a protocol id

• Restarting the TL1 session manager (Procedure 5-4)

— Obtain a userID and password that allows you to access the OPC at the root level
— Log into the OPC as root
— Open the TL1 configuration tool
— Select to restart the TL1 session manager

—continued—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

xii About this document

• Querying active TL1 sessions (Procedure 5-5)

— Obtain a userID and password that allows you to access the OPC at the root level
— Log into the OPC as root
— Open the TL1 configuration tool
— Select to query the TL1 session manager

• Accessing and exiting TL1 interfaces through the Unix shell tool (Procedure 5-6)
— Obtain a userID and password that allows you to access the OPC at the root level
— Use a terminal connected to the OPC (User Interface Connection Procedures, 323-1801-301)
— Log into the OPC as root
— Issue a message to access the TL1 interface
— Issue a message to exit the TL1 interface

• Configuring and enabling the TL1 interface Router Service over X.25 or TCP/IP (Procedure 5-7)
— Obtain a userID and password that accesses the TL1 Configuration tool from the User Session Manager
— Determine and configure the X.121 address of the OSS into the virtual circuit profile of both the gateway
OPC and into remote OPCs. For more details see Procedure 5-3
— Configure the gateway OPC port B for X.25. For more information see Procedure 5-2
— Determine the RemoteOPCNames, TIDs, IP address of the OSS, OSS type, and port number for primary
router service over TCP/IP.
— Ensure the OPTera Long Haul 1600 PID is not set to NULL. If it is go to Procedure 5-3 to change it.
— Log into the OPC using the admin userID
— Open the TL1 configuration tool from the User Session Manager
— Configure the TL1 interface router over X.25 or TCP/IP
— For X.25 configure and enable primary and backup router
— For TCP/IP configure and enable primary and backup router
— Establish or disable a TL1 session over the TL1 Interface Router Service

• Configuring TL1 over TCP/IP (Procedure 5-8)

— Obtain a userID and password that accesses the TL1Configuration tool from the User Session Manager
— Choose one of the following actions from the table: Configure TL1 over TELNET/TCP/IP, Configure TL1
over TRUE TCP/IP, Unconfigure TL1 over TRUE TCP/IP, Unconfigure TL1 over TELNET/TCP/IP
— Issue the corresponding message
— Display TL1 TCP/IP port configurations

—end—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 About this document xiii

High-level procedure introduction

This document contains high-level procedure introductions that provide
information necessary for a qualified user to perform a procedure. You can find
an overview of the requirements, the main procedure tasks, and the expected
results on a single page. The step numbers in parentheses provide hypertext
links to specific procedure steps in the complete procedure.

Some detailed procedures can include warning, caution, or danger messages

included between detailed steps. You can find precautionary message icons
included next to specific steps in the following high-level introduction. To read
the full precautionary message in the complete procedure look for the
equivalent step as indicated in parentheses after the procedure task.

Example of a high-level procedure introduction

Before you start

• Log in to the network element user interface.

Procedure tasks
• Access the main menu of the NEUI with admin or read/write privileges (step 1).
• Put the associated facility OOS if you are taking a CPG OOS (step 4).
• Put the corresponding output facility OOS if you are taking the protection ESI CPG OOS (step 10).
• Put the protection ESI CPG OOS (step 14).
• Put the output facility for the working ESI CPG OOS (step 18).
• Set the target filter mode to freerun if you are taking the working ESI CPG OOS (step 20).

Expected results
• The primary state of the CPG changes.
• If the expected results do not occur:
— Perform the procedure again.
— Contact your next level of support.

TL1 Interface Description 323-1801-190 Rel 3 July 2000

xiv About this document

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 1-1

Introduction to TL1 1-
TL1 overview
Transaction Language 1 (TL1) is an industry-recognized common language
protocol for messages exchanged between network elements and an operations
system (OS). OPTera Long Haul 1600 supports TL1 messages for the network
administrative and surveillance functions. TL1 allows an OS to communicate
with different vendor’s equipment through the common language protocol.
TL1 eliminates the need to support vendor-specific interfaces.

OPTera Long Haul 1600TransportNode TL1 interface

The TransportNode TL1 interface for OPTera Long Haul 1600 allows the
operations system to monitor and control a group of network elements under
the span of control of an operations controller (OPC). There are two kinds of
OPCs: the legacy OPC and the partitioned OPC. The OPC communicates with
the network elements through an X.25 connection to the OPC. You can use the
OPC as a gateway for the TL1 messages to and from the network elements.
When you use the OPC X.25 connection, you do not need a separate X.25 link
to each network element. The OPC X.25 port is accessible on the OPC
interface circuit pack faceplate. You can provision OPC X.25 port as an X.25
port to provide the required connectivity to the operations system without the
need of additional hardware.

A Transmission Control Protocol/Internet Protocol (TCP/IP) telnet session

also provides the required connectivity. This protocol uses the Ethernet port on
the OPC interface circuit pack. See Figure 1-1 to see TL1 connectivity, with
TCP/IP. See Figure 1-2 to see TL1 connectivity, with X.25.

You can provision a redundant TL1 connection to provide complete system

visibility in the event of system failures through the backup OPC. Examples of
system failures include fiber outages or network element failures.

The TL1 implementation on TransportNode equipment for OPTera Long Haul

1600 allows the operations system to perform the following functions:
• network surveillance
• fault management
• user administration

TL1 Interface Description 323-1801-190 Rel 3 July 2000

1-2 Introduction to TL1

Figure 1-1
Example of TL1 connection by TCP/IP (route diverse linear system shown)
OTP0677.eps

Operations
system

LAN/WAN

OPTera Long Haul 1600

Repeater
Regenerator Regenerator
Primary Primary
Router TL1/TCPIP OPC OPC
site

Backup
Backup TL1/TCPIP
OPC OPC Router
site
Regenerator Regenerator OPTera Long Haul 1600
Repeater

Legend:

LAN = Local Area Network

OPC = Operations Controller
TCP/IP = Transmission Control Protocol/ Internet Protocol
TL1 = Transaction Language 1
WAN = Wide Area Network

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Introduction to TL1 1-3

Figure 1-2
Example of two systems that interface through TL1 to a remote operations system by X.25
OTP0678.eps

Operations
system

DCE X.25 DCE

Packet switched
Modem network Modem

Modem Modem
DCE DCE

Primary Backup
X.25/TL1 X.25/TL1
link link
OPTera OPTera
Long Haul Long Haul
1600 1600
Repeater Repeater
Regenerator Regenerator
Primary Backup
OPC OPC OPC OPC
site site
DTE DTE

Primary Backup
X.25/TL1 Regenerator X.25/TL1
link link
Ethernet SONET SDCC bridge

Primary OPTera Long OPTera Long Backup

OPC OPC Haul 1600 Haul 1600 OPC OPC
site Combiner Combiner site

OPTera OPTera
Long Haul OC-192 Long Haul
1600 Terminal 1600
Repeater Repeater

Legend:

DCE = Data communication equipment

DTE = Data terminal equipment
SONET = Synchronous optical network
SDCC = Section data communications channel
OPC = Operations controller
TL1 = Transaction Language 1

TL1 Interface Description 323-1801-190 Rel 3 July 2000

1-4 Introduction to TL1

Standards compliance
The OPTera Long Haul 1600 TransportNode TL1 surveillance interface
complies with the following Telcordia standards:
• GR-833-CORE Issue 2: Network Maintenance - Network Element and
Transport Surveillance Messages
• TA-TSY-200 Issue 4: Specification of System Maintenance Messages at
the OS/NE Interface
• SR-OPT-001665 Issue 2: NMA Generic Transport Element Interface
Support
The X.25 interface is compliant with the following standards:
• ITU-T (previously CCITT) Recommendation X.25, ITU-T (previously
CCITT) Blue Book 1988
• ISO/IEC 8208 X.25 Packet Layer Protocol 1990
The TransportNode equipment is compliant with the Telcordia NMA OS
standard, releases 2.4 and 3.2.

TL1 interface types

TransportNode products support two logical TL1 interfaces: the surveillance
interface and the provisioning interface.

The surveillance interface allows surveillance functions such as:

• real-time alarm reports
• event reports
• threshold crossing alerts
• logs
• performance statistic reports
You can also perform control functions such as manual and forced switch
capabilities on both the transport and tributary channels.

Note: Refer to Fault Detection, 323-1801-541 for the hierarchy of

equipment and facility alarms. This NTP describes how alarms are related
to each other, and the order in which alarms of higher severity can mask
alarms with lower severity. Also refer to Trouble Clearing and Module
Replacement, 323-1801-543 for a description of alarm classes, types,
alarm text, and for alarm clearing procedures.

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Introduction to TL1 1-5

The provisioning interface supports these provisioning functions on various

facilities and equipment:
• retrieve
• add
• edit
• delete
The provisioning interface does not support autonomous messages. Both
interfaces provide user administration commands.

TL1 connectivity
TL1 over X.25
The OPC and the operations system can send TL1 messages between them
with an X.25 packet layer protocol. The OPC X.25 port is accessible on the
legacy OPC, or on the OPC Interface circuit pack faceplate on a partitioned
OPC. You can provision the OPC X.25 port as an X.25 port. With the
appropriate X.25 cable and a link to an X.25 data packet network, the X.25 port
becomes the TransportNode OPTera LH TL1 gateway to the operations
system. To configure X.25 port for TL1 use, refer to Chapter 5, “TL1
commissioning”.

An X.3 PAD (Packet Assembler/Disassembler) can also be enabled on the

X.25 port. The OPC uses the Protocol ID (PID) parameter in the X.25 call
request packet to determine which incoming X.25 calls will go to the TL1
server. In order for the OPC to determine when calls will go to the server, both
the TL1 and X.3 PAD must be enabled on the X.25 port. For information on
X.25 configuration and troubleshooting X.25 communication problems, refer
to Chapter 2, “Interface configurations”.

Note: Make sure the X.25 port is not connected in order to configure it as
an X.25/TL1 interface. To configure the X.25 port for X.25 use, establish
a terminal session through the OPC Ethernet port or log in from a network
element.
TL1 over TCP/IP
You can access the TL1 interface:
• over X.25
• through TRUE TCP/IP
• over TELNET TCP/IP with a telnet session
When you access TL1 over TRUE TCP/IP, there is no need for telnet. You need
a telnet session to use the tl1shell and when you log in as an “nma” or “ops”
user. If you access TL1 with a telnet session, establish the telnet session with
the Ethernet port on the OPC faceplate. The functionality and messages

TL1 Interface Description 323-1801-190 Rel 3 July 2000

1-6 Introduction to TL1

supported by the Ethernet TL1 interface are identical to that of the X.25 TL1
interface. The Ethernet allows for a faster rate of transmission and also frees
port B on the legacy OPC. You can use port B as a printer port or terminal port.

The advantages of TL1 over TCP/IP are:

• lower costs because it eliminates the need for end-to-end X.25 circuits
• significant increase in bandwidth
• multiple login capabilities for users in remote locations
There are two TL1 interface types: network monitoring analysis (NMA) and
operations provisioning system (OPS). Each TL1 interface type has a specific
userID and is password protected. To start a TL1 interface, open a telnet
session to connect to the OPC. After you open the telnet session, log in with
the appropriate userID to specify the type of TL1 interface. For information on
how to configure TL1 over Ethernet, refer to Chapter 2, “Interface
configurations”.
OPC TID
The tidmap tool displays the OPC target identifier (TID) of the OPC that tool
is used on. The OPC TID of the backup OPC cannot be set by the primary
OPC, nor will it be displayed. When the backup OPC becomes active, the OPC
TID is set using its own tidmap tool. The OPC TID is different for the primary
and backup OPC. The OPC TID follows the same guidelines as the NE TID.
If the OPC TID is left blank, the OPC name is the default value. The OPC TID
can only be set using the SET-SID command or with the tidmap tool.
Backup/redundant TL1
You can provision a redundant TL1 connection to provide complete system
visibility in the event of system failures through the backup OPC. Examples of
system failures include: fiber outages or network element failures.

The redundant connection originates at either the X.25 port or the Ethernet port
of the backup OPC. This connection becomes activated only when the backup
OPC is active. For example, when a fiber cut between the network elements
that contains the primary and backup OPCs occurs, both the primary and
standby TL1 interfaces are active. This kind of fiber cut results in a loss of
communication between OPCs.

The redundant TL1 interface ensures the maintenance of full operations

system-to-network element communications and offers warm standby TL1
capability. The inactive backup link issues no TL1 messages. TL1 requests
sent to the inactive backup TL1 connection returns a “No Acknowledgment”
(NA) response.

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Introduction to TL1 1-7

When the backup OPC and the backup TL1 connection become active, the
operations system receives an autonomous Report Switch (REPT-SW)
message. The message indicates that the TL1 link is now active. If the backup
OPC becomes active before the establishment of the TL1 connection to the
backup OPC, the system does not send the REPT-SW message.

You must manually synchronize the TID used by TL1 between the primary
OPC and the backup OPC. When a new TID is set, perform OPC
synchronization. For the procedure to transfer data between OPCs, refer to
Data Administration Procedures, 323-1801-304.
Loss of communication
Use the Retrieve Header (RTRV-HDR) TL1 surveillance interface message to
detect a loss of communication to the network elements or the OPC. After you
issue the RTRV-HDR request to the OPC or the selected network element, you
should receive the TL1 response message within three minutes. Three minutes
is the worst case estimate. If you do not receive the TL1 response within three
minutes then there is a link failure or loss of communications to that network
element or OPC. The RTRV-HDR message is useful when troubleshooting
network element link failures.
Simultaneous TL1 sessions
See Table 1-1 for the number of sessions that can occur simultaneously on the
TL1 OS and the OPC user interface. The maximum number of simultaneous
TL1 sessions is four (whether you are using X.25 or TCP/IP). Of the four, all
can be surveillance sessions. Only one TL1 provisioning interface session can
occur at a time. If four TL1 sessions are active, then a maximum of two OPC
user interface sessions can occur.
l

Table 1-1
TL1 operations system sessions

Maximum quantity of simultaneous Maximum quantity of OPC user

TL1 OS sessions interface sessions

0 4

1 4

2 3

3 3

4 2

TL1 message overview

This section describes the TL1 messages types, common elements present in
all TL1 messages, and the responses to TL1 non-autonomous requests.

TL1 Interface Description 323-1801-190 Rel 3 July 2000

1-8 Introduction to TL1

TL1 message types

There are two types of TL1 messages: autonomous and non-autonomous.

The OPC generates autonomous messages as a result of activity on the network

elements. These activities include alarms, threshold alerts, and warnings. The
operations system receives autonomous messages automatically. The
surveillance interface generates autonomous messages.

Non-autonomous messages consist of a request message from the operations

system and a response message from the OPC. For example, the operations
system message can be a user request for any outstanding minor alarms for a
specified network element, and the OPC will output the appropriate response
message.
TL1 response header
The first two lines of all TL1 message responses have a common format.

The first line contains the source identifier (SID), the date and time. The date
and time indicate when the TL1 response was sent to the operations system.
An example of the first line is:

SID Date and time of message

West_Ch2 97-05-15 13:39:32

The second line of the TL1 message differs for autonomous messages and
non-autonomous messages. For autonomous messages, the second line in
non-alarm messages begins with an A. The second line in alarm messages
begins with an alarm code, such as an asterisk (which represents a minor
alarm) as shown in Figure 1-3. The second line of autonomous messages also
contains:
• a numerical alarm tag (ATAG), the ATAG is automatically generated
• the TL1 message type
For non-autonomous messages, the second line always begins with an M,
followed by the correlation tag (CTAG) used in the original TL1 request. The
CTAG is in turn followed by either the word COMPLD to indicate a normal
response, or DENY to indicate an error response.

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Introduction to TL1 1-9

See Figure 1-3 for three examples of TL1 message headers.

Figure 1-3
TL1 message header examples

Non-autonomous message example

TL1 request rtrv-hdr:West_Ch1::Steve3;

TL1 response WEST_CH1 97-05-15 13:38:57

(non-autonomous) M STEVE3 COMPLD
COMPLD (normal)
DENY (error)
Message tag (CTAG)
M tag
Autonomous message examples
Alarm type autonomous message response header
TL1 response WEST_CH2 97-05-15 13:39:32
header * 49173 REPT ALM ENV
(autonomous)
Autonomous message type
(report alarm environmental)
Message tag (ATAG)
Alarm code (minor alarm)

Non-alarm type autonomous message response header

TL1 response WEST_CH3 97-05-15 13:44:57
header A 49181 REPT COND
(autonomous)
Autonomous message type
(report condition)
Message tag (ATAG)
A tag (non-alarm)

TL1 case sensitivity

Case sensitivity means that the use and position of uppercase and lowercase
letters in the parameter is important. Unless specified otherwise in the
descriptions of individual commands, all TL1 parameters are case insensitive.
TL1 message acknowledgment
When you send a TL1 non-autonomous message to an OPC, the operations
system receives an acknowledgment message before it receives the TL1
non-autonomous response. This acknowledgment indicates to the operations
system that the OPC received the TL1 request.

TL1 Interface Description 323-1801-190 Rel 3 July 2000

1-10 Introduction to TL1

There are two possible acknowledgment messages, Table 1-2 describes these
messages:
Table 1-2
Acknowledgment messages

Acknowledgment Description

PF crlf Printout Follows

< Indicates that the TL1 request was received and a TL1
response message will follow.

NA crlf No Acknowledgment
< Indicates that the TL1 request was received, but the selected
OPC is not active so no TL1 response will be sent back to the
operations system.

Legend:
cr = carriage return
lf = line feed

TL1 network element identification

A non-autonomous TL1 message is routed to the target network element by
means of the value of a target identification code (TID) parameter block. The
TID value is equivalent to the source identifier (SID) used in TL1 autonomous
messages. Both the TID and the SID have the same possible values.

There are three possible values for the TID parameter block: a defined target
identifier (TID), the NE name (NEname), or the NE identification number
(NEid). The list below provides a summary of the TID block parameter values:
• The value of the TID parameter block can be a defined TID of up to 20
characters (letters, digits, hyphens [-], underscores [_], and periods [.]).
This name is set through the TL1 connection as a TL1 message (set-sid) or
through an OPC Session Manager UNIX command (tidmap). Refer to
“Setting an identification parameter” later in this chapter.
• The value of the TID parameter block can be the NEname (providing it
meets TL1 requirements) if a TID is not set. The NEname allows a user to
provide a designation for the NE that reflects the needs of the application.
The NEname is set from the NE user interface (NE UI).
• The value of the TID parameter block can be the NEid if the NEname is
not valid and if a TID is not set. The assignment of the NEid is the first step
in the commissioning of a new network element. This NEid can be up to
five numeric characters long (that is, the values 1 through 65534 inclusive).
The OPC uses the NEid to uniquely identify a particular NE. You must
assign an NEid to each NE. Instructions for setting the NEid are in the
Powering up and Commissioning Procedures, 323-1801-220.

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Introduction to TL1 1-11

Table 1-3 summarizes the NMA (Network Monitoring Analysis, or

surveillance interface) and OPS (Operations Processing System, or
provisioning interface) significance of each identifier.

Table 1-3
TL1 network element identification for NMA and OPS

Value of the target identification code NMA and OPS applications

(TID) parameter block

defined name TID

NEname Default for TL1 TID if TID is not set.

NEid Default for TL1 TID if NEname does not

exist or is invalid, and TID is not set.

You must manually synchronize the defined name between the primary OPC
and the backup OPC. Perform an OPC synchronization when a new target
identifier is set. Each network element can have only one TID.

Setting an identification parameter

You can set, change, or confirm an identification parameter. Refer to the
chapter procedure list.

Chapter procedure list

Perform one of the procedures in Table 1-4 to set, change, or confirm the TL1
TID parameter value from either an operations system or OPC.

Table 1-4

Action Details

Setting and retrieving a TL1 TID from an operations system Procedure 1-1

Setting a TL1 TID through the OPC user interface Procedure 1-2

TL1 Interface Description 323-1801-190 Rel 3 July 2000

1-12 Introduction to TL1

Procedure 1-1
Setting and retrieving a TL1 TID from an operations
system
Use this procedure to set, change, or confirm a target identifier (TID) from an
operations system such as a network monitoring and analysis (NMA) system.

The TID is applicable in TL1 surveillance applications. The TID defines a TL1
target identifier and fully supports the format defined by Telcordia standards
for the naming of network elements.

The TID can be up to 20 characters. Supported characters include:

• alphanumeric characters (A-Z, 0-9)
• special characters: hyphen (-), underscore (_), and period (.)
Unsupported characters include:
• semi-colon (;)
• colon (:)
• ampersand (&)
• greater than (>)
• less than (<)
• back-slash (\)
• double quote (“)
• comma (,)
• any control characters
You cannot use spaces in the TID. You can use lowercase letters in the TID,
however, the system interprets and returns the alphabetical characters in
uppercase only.
—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Introduction to TL1 1-13

Procedure 1-1 (continued)

Setting and retrieving a TL1 TID from an operations system

Before you start

• Know the current TID. If a TID has not been set, the current TID takes the default value of the NEname
if the NEname is set and does not contain unsupported characters. If the NEname is not set, or if it
contains unsupported characters, then the NEid becomes the default TID.
• Obtain the new value for the TID.

Procedure tasks
• Establish a connection to the TL1 interface of the OPC (step 1).
• Set or retrieve the TID (step 2).
• Set or change the OPCTID (step 5).

Expected results
• The TID and OPCTID are set and retrieved.
• If the expected results do not occur:
— Check that you have a connection to the TL1 interface of the OPC.
— Check that you have correctly typed the required messages.
— Check that you have the correct input parameters for TID and OPCTID.

—continued—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

1-14 Introduction to TL1

Procedure 1-1 (continued)

Setting and retrieving a TL1 TID from an operations system

Action
Step Action

1 Establish a connection to the TL1 interface of the OPC according to standard

operations system procedures.
2 Select an action:

If you want to Then go to

set or change the TID step 3
confirm or display a TID step 4

TID operations
3 To set or change the TID for a network element, issue the following message:
set-sid:<current tid>::<ctag>::<new tid>;crlf
If the command successfully executes, you receive this message:
crlf
lf
^^^<new tid>^<date>^<time> crlf
M^^<ctag>^COMPLD crlf
;
If there is an error, you receive this message:
crlf
lf
^^^<current tid>^<date>^<time> crlf
M^^<ctag>^DENY crlf
^^^<errcde> crlf
[^^^/*error text*/ crlf]
;
4 To confirm the new TID or to display the TID, issue the following message:
rtrv-hdr:<tid>::<ctag>;crlf
If the command successfully executes, you receive this message:
crlf
lf
^^^<current tid>^<date>^<time> crlf
M^^<ctag>^COMPLD crlf
;
—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Introduction to TL1 1-15

Procedure 1-1 (continued)

Setting and retrieving a TL1 TID from an operations system

Step Action

If there is an error, you receive this message:

crlf
lf
^^^<tid>^<date>^<time> crlf
M^^<ctag>^DENY crlf
^^^<errcde> crlf
[^^^/*error text*/ crlf]
;
If the TID for a network element is unknown, issue the following message:
rtrv-hdr:<NE ID>::<ctag>; crlf
A successful response returns the current TID for that network element.
crlf
lf
^^^<current tid>^<date>^<time> crlf
M^^<ctag>^COMPLD crlf
;
Note: If TID is already set, the rtrv-hdr message will not be accepted.
OPCTID operations
5 To set or change the OPCTID for an OPC, issue the following message:
set-sid:<current OPCTID>::<ctag>::<new OPCTID>;crlf
If the command successfully executes, you receive this message:
crlf
lf
^^^<new OPCTID>^<date>^<time> crlf
M^^<ctag>^COMPLD crlf
;
If there is an error, you receive this message:
crlf
lf
^^^<current OPCTID>^<date>^<time> crlf
M^^<ctag>^DENY crlf
^^^<errcde> crlf
[^^^/*<error text>*/ crlf]
;
—continued—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

1-16 Introduction to TL1

Procedure 1-1 (continued)

Setting and retrieving a TL1 TID from an operations system

Step Action

6 To confirm the new OPCTID or to display the OPCTID, issue the following
message:
rtrv-hdr:<OPCTID>::<ctag>;crlf
If the command successfully executes, you receive this message:
crlf
lf
^^^<current OPCTID>^<date>^<time> crlf
M^^<ctag>^COMPLD crlf
;
If there is an error, you receive this message:
crlf
lf
^^^<OPCTID>^<date>^<time> crlf
M^^<ctag>^DENY crlf
^^^<errcde> crlf
[^^^/*<error text>*/ crlf]
;
If the OPCTID for an OPC is unknown, issue the following message:
rtrv-hdr:<OPCNAME>::<ctag>; crlf
A successful response returns the current OPCTID for that OPC.
crlf
lf
^^^<current tid>^<date>^<time> crlf
M^^<ctag>^COMPLD crlf
;
—end—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Introduction to TL1 1-17

Procedure 1-2
Setting a TL1 TID through the OPC user interface
Use this procedure to define, change, or display TID through an OPC interface.

The TID is applicable in TL1 surveillance applications. The TID defines a TL1
target identifier and fully supports the format defined by Telcordia standards
for the naming of network elements.

The TID can be up to 20 characters. Supported characters include:

• alphanumeric characters (A-Z, 0-9)
• special characters: hyphen (-), underscore (_), and period(.)
Unsupported characters include:

• semi-colon (;)
• colon (:)
• ampersand (&)
• greater than (>)
• less than (<)
• back-slash (\)
• double quote (“)
• comma (,)
• any control characters
You cannot use spaces in the TID. You can use lowercase lettering in the TID,
however, the system interprets and returns the alphabetical characters in
uppercase only.

Note: This procedure uses the tidmap command. To obtain help for the
tidmap command enter tidmap -h ↵.
—continued—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

1-18 Introduction to TL1

Procedure 1-2 (continued)

Setting a TL1 TID through the OPC user interface

Before you start

• Know the current TID. If a TID has not been set, the current TID takes the default value of the NEname
if the NEname is set and does not contain unsupported characters. If the NEname is not set, or if it
contains unsupported characters, then the NEid becomes the default TID.
• Obtain the new value for the TID.
• Have a userID and password that allow you to access the OPC at the root or admin levels.
• Read the command conventions described in OPC User Interface Description, 323-1801-196.

Procedure tasks
• Log in to the OPC (step 1).
• Open the UNIX shell tool, in the OPC Admin section (step 2).
• Display a table of current values for NEid, NEname, and TID (step 3).
• Define or change a TID and OPCTID (step 5).

Expected results
• The TID and OPCTID are set and retrieved.
• If the expected results do not occur:
— Make sure you log onto the system as admin user or root user.
— Check that you have the correct input parameters for the command.

—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Introduction to TL1 1-19

Procedure 1-2 (continued)

Setting a TL1 TID through the OPC user interface

Action
Step Action

1 Log in to the OPC.

If you do not know how to do this, see User Interface Connection Procedures,
323-1801-301.
The “OPC>” prompt appears.

If you are logging on as Then

admin user complete the entire “Logging in to the OPC”
procedure in User Interfaces Connection
Procedures, 323-1801-301, then go to step 2 of
this procedure
root user follow “Logging in to the OPC” in User
Interfaces Connection Procedures,
323-1801-301 until the UNIX prompt “OPC>”
appears, then go to step 3 of this procedure

2 With the User Session Manager displayed, open the UNIX shell tool (in the
OPC Admin section).
If you do not know how to open the UNIX shell tool, see User Interface
Connection Procedures, 323-1801-301.
The UNIX prompt “OPC>” appears.
—continued—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

1-20 Introduction to TL1

Procedure 1-2 (continued)

Setting a TL1 TID through the OPC user interface

Step Action

3 To display a table of the current values for NEid, NEname, OPCTID, and TID
for all NEs in the OPC span of control, type the following command:
tidmap ↵
A table similar to the table below appears:
TID NE NAME NE ID
============ ========= ======
TLITID000123 NENAME123 10001
NENAME234 NENAME234 20002
30003 30003

OPCTID OPCNAME
========= =========
OPCP1967P OPC00001P
OPC00001B OPC00001B

Note: Entries under TID, OPCTID, NEname, or OPCNAME appear only if

they are set. If there is no value in the column, then the default provides the
current value.
In the example above:
• The first line shows the case where the TID, NEname, and NEid are all
set.
• The second line shows the case where only the NEname and NEid are
set. The TID defaults to the NEname in this case.
• In the third line, only the NEid is set. In this case, the TID defaults to the
NEid.
• In the fourth line, the OPCTID and the OPCNAME are both set.
• In the last line, only the OPCNAME is set. The OPCTID defaults to the
OPCNAME.

4 Select your next step

If you want to Then go to
set or modify a TID step 5
set or modify an OPCTID step 6
exit step 8
—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Introduction to TL1 1-21

Procedure 1-2 (continued)

Setting a TL1 TID through the OPC user interface

Step Action

Define or change the TID

5 To define or change a TID, type the following command:
tidmap -a <NE ID> <TID>
where
<NE ID> is the value of the NEid
<TID> is the new value for the TID

Go to step 7.
Define or change an OPCTID
6 To define or change an OPCTID, type the following command:
tidmap -a <OPCNAME> <OPCTID> ↵
where
<OPCNAME> is the value of the NEid
<OPCTID> is the new value for the OPCTID

7 To check the changes, display the table of NEids, NEnames, OPCNAMEs,

OPCTIDs and TIDs, enter this command:
tidmap ↵
Exit from the UNIX shell
8 To exit from the UNIX shell tool, enter this command:
exit ↵
The User Session Manager appears.
—end—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

1-22 Introduction to TL1

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 2-1

Interface configurations 2-
To make the TL1 interface operational with an X.25 connection you must
configure the X.25 port for X.25 communications and configure virtual circuit
profiles. Before you use the TL1 interface initialize the X.25 communications.
To make the TL1 interface operational with a telnet connection you must
configure the appropriate user accounts. To use the TL1 interface over telnet
the appropriate user accounts must be set up first.
Before the TL1 interface on the S/DMS TransportNode systems becomes
operational, you must perform certain steps to make sure the TL1 interface is
functioning correctly. This chapter describes the configuration requirements
for the TL1 sessions via X.25 and telnet.

Note: The procedure in this chapter is specific to a partitioned operations

controller (OPC). The legacy OPC can have X.25 configured on port B.

TL1 configuration
This section describes the configuration requirements for both the primary and
backup TL1 interfaces.

TL1 configuration requirements

The following list describes the requirements you must meet in order for TL1
communications to occur. These requirements are in the order in which they
should occur.
Configuration requirements include:
• the network has been successfully commissioned and tested
• the configuration for either the X.25 or telnet TL1 connection is complete
• the OPC is active and can communicate with the network elements, and
that there is no loss of association with any network elements in the span
of control (SOC)
See Chapter 5, “TL1 commissioning” and Procedure 2-1, “Defining and
enabling TCP/IP communications” in this chapter for configuration
procedures.

Issue the RTRV-HDR command from any interface to confirm that the TL1
interface is working correctly.

TL1 Interface Description 323-1801-190 Rel 3 July 2000

2-2 Interface configurations

Note: You can use the same TL1 requirements to configure the backup
TL1 interface. The backup interface cannot transport any TL1 messages
while the backup OPC is inactive. Send a non-autonomous message, such
as a RTRV-HDR message, to the OPC to check the TL1 connection. If the
operations system receives an “NA” acknowledgment response (as
explained in Chapter 1, “Introduction to TL1”), then the backup TL1
interface is operational upon activation of the backup OPC. If the
operations system receives no response, use the TL1 checklist to locate the
trouble area.

TL1 default operation

After the establishment of the TL1 connection the surveillance interface
automatically reports messages. The entire TL1 message set is available to the
operations system.

X.25 configuration
X.25 is an international telecommunications standard for data packet
switching. The International Telecommunications
Union-Telecommunications (ITU-T, formerly CCITT) defines the X.25
standard. The X.25 standard ensures that the information sent from data
terminal equipment (DTE) can be understood when the remote operations
system receives it over the data packet network. The TL1 interface on the OPC
is an example of DTE. The purpose of the X.25 packet protocol is to allow TL1
messaging between the OPC and the operations system. The ISO/IEC 8208
X.25 Packet Layer Protocol for Data Terminal Equipment document defines
this protocol.

Set the X.25 configuration before you verify the TL1 interface. After you
configure the X.25 communications, add the valid X.121 user addresses into
the OPC. Refer to the procedures in Chapter 5, “TL1 commissioning”, of this
document to define and enable X.25 communications on the X.25 port.

X.25 configuration requirements

The following list describes the X.25 configuration requirements essential for
X.25 communications to occur. These requirements are in the order in which
they should occur.
• Make sure that the appropriate X.25 and TL1 equipment and services are
available and connected. These can include TL1 cables (NT7E44QA/QB),
synchronous modems, modem eliminators, X.25 data lines, OPTera Long
Haul 1600 software, and protocol analyzers.
• Use the X.25 interface worksheet in Chapter 5, “TL1 commissioning”, to
determine the X.25 parameters required on both the OPC and the
operations system. For details on completing the X.25 worksheet see
Procedure 5-1, “Completing an X.25 worksheet”. For the default
configuration parameters see “X.25 default configuration” on page 2-4.

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Interface configurations 2-3

• The X.25 parameters on the OPC, such as the X.121 address, must be
configured (refer to Chapter 5, “TL1 commissioning”, of this document).
• The X.25 port on the OPC Interface circuit pack must be available for use.
• The X.25 port must be configured as an X.25 port (refer to Chapter 5, “TL1
commissioning”, of this document)
Note: After configuring the X.25 port, restart the TL1 session manager as
described in Chapter 5, “TL1 commissioning”, of this document.

• One end of the TL1 cable must be connected to the X.25 port and other end
to the data communication equipment (modem, data line, or modem
eliminator).
• The link access protocol B (LAPB) must be initialized. Use a protocol
analyzer to verify the initialization.
• The operations system X.121 addresses must be added to the OPC virtual
circuit profile configuration file. This provides user security. If the
operations system X.121 address is not entered in the OPC, the X.25 call
request from the operations system is refused.
Note: The X.121 parameter must be defined for the OPC and it can be an
assigned number from the data packet network administrator. The device
and name parameters should not be modified. The t1, t3, t4, framesize, n2,
and l2window level 2 parameters are all configurable. The network type
parameter can be either DTE 84 (data terminal equipment) or DCE 84
(data communication equipment). Only switched virtual circuits (SVC)
can be provisioned under the circuit table definition with a maximum
number of 16 for the maximum parameter. All the other parameters are
configurable. Ensure that you match the X.25 parameters on the OPC to
those on the operations system.

• The operations system must issue a call request to the OPC and establish
the X.25 SVC.

TL1 Interface Description 323-1801-190 Rel 3 July 2000

2-4 Interface configurations

X.25 default configuration

The default OPC X.25 parameters are as follows:
# X.25 Initialization File
#
# Global Parameters
x.121
device /dev/x25_0
name scc0
#
# Level 2 Parameters
#
t1 3000
t3 60000
t4 0
framesize 263
n2 20
l2window 7
#
# Level 3 Parameters
#
networktype DTE_84
#
# Circuit Table Definition
#
# LCI TYPE HOW MANY
lci 1 svc 8
max_circuits 8
#
# Flow Control, Throughput Class, Fast Select and Reverse
Charge Settings
#
flowcontrol off
thruputclass off
fast_select_accept disabled
reverse_charge disabled
def_inpacketsize 128
def_outpacketsize 128
def_inwindow 2
def_outwindow 2
def_inthruputclass 11
def_outthruputclass 11
neg_inpacketsize 128
neg_outpacketsize 128
neg_inwindow 2
neg_outwindow 2
neg_inthruputclass 11
neg_outthruputclass 11

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Interface configurations 2-5

X.25 communications
In X.25 communications there are both data circuit-terminating equipment
(DCE) and data terminating equipment (DTE) at the physical level and at the
handshaking and flow-control levels. The OPC X.25 port is a DTE device
which should be connected to a synchronous modem (DCE). In the case of a
direct connection (no modems) to an operations system, which is also a DTE,
a synchronous modem eliminator is needed. Both configurations are shown in
Figure 2-1.
Figure 2-1
X.25 communication between OPC and operations system
F2412

Packet
Synchronous switched Synchronous Operations
OPC data System (OS)
modem modem
network
Hardware: DCE Hardware: DCE
Hardware: DTE Hardware: DTE
Control: DTE Control: DCE

Synchronous modem Operations

OPC eliminator System (OS)

Hardware: DCE-DCE
Hardware: DTE Hardware: DTE
Control: DTE Control: DCE

The OPC is normally configured as DTE for flow-control purposes with the
operations system configured as DCE. The X.29/X.3 PAD facilities can be
specified in the call request packet originated from the operations system. The
X.29/X.3 PAD facilities are normally required for asynchronous access such
as using a VT100 terminal and they can be used in an operations system
environment. The OPC accepts the incoming X.25 call if the X.29/X.3
facilities have been defined.

The OPC supports only switched virtual circuits (SVC) and not permanent
virtual circuits (PVC). The SVC connections require call establishment
handshaking (call request and call acceptance packets) between the OPC and
the operations system, whereas PVC connections do not require call control.

TL1 Interface Description 323-1801-190 Rel 3 July 2000

2-6 Interface configurations

Think of SVC as a regular phone line over which user A dials a number to start
a conversation with user B, and PVC as a direct phone line that user A just
picks up and talks to user B.

X.25 troubleshooting guidelines

The following guidelines require the user to understand the X.25 protocol and
to have a protocol analyzer available. If a problem arises, check that the X.25
cable is the correct part number (NT7E44QA or NT7E44QB), and that it is
connected to the correct port (X.25 port on the OPC Interface circuit pack).

If a problem persists after the above has been checked, connect a protocol
analyzer between the OPC and the DCE device to monitor the packet
exchanges. Verify that:
• the X.25 connection is an SVC and not a PVC
• call request packets are received by the OPC
• the protocol id (PID) in the call request packet matches the OPC user
defined PID
• the calling and caller’s X.121 addresses are specified in the call request
packet
• the X.29/X.3 PAD facility bit is set in the call request packet
• SABM or UA packets are continuously received or transmitted
Note: If so, there is a problem at the LAPB layer 2 level.

• the OPC issues a call acceptance packet and then a clear request packet
Note: If so, there is a problem with vcpinfo (the user X.121 address is not
defined in the OPC) or the facilities requested.
Ethernet configuration
The TL1 interfaces can also be accessed by way of telnet sessions to the OPC.
Ensure that:
• the Ethernet port on the OPC is enabled
• the network monitoring and analysis (NMA) users have been created on
the OPC (see Procedure 2-1, “Defining and enabling TCP/IP
communications”)
• the appropriate Ethernet cable has been plugged into the OPC
• the operations system has a telnet session to the OPC and is logged in

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Interface configurations 2-7

TARP support for interoperability in mixed networks

The Target Identifier Address Resolution Protocol (TARP) is used by TL1
managed network elements to convert TL1 target identifiers (TIDs) into
network service access points (NSAPs).

Application layer protocols

Within SONET networks there are network elements which support different
application layer protocols for interactive class communication, for example:
• Nortel Networks OC-3 Express network elements only support TL1 as the
application layer protocol. These network elements use TIDs to address
and identify other network elements.
• Nortel Networks OPTera Long Haul 1600 network elements support
Common Management Information Service (CMISE) as the application
layer protocol. These network elements use NSAPs to address and identify
other network elements.
Real world networks often consist of a mix of the above network elements and
third party vendor equipment (see Figure 2-2).

Note: OC-3 Express network elements are Nortel Networks only SONET
network elements that support TL1 as the application layer protocol. All
other Nortel Networks SONET network elements, such as the OC-12,
OC-48, OC-192, and OPTera Long Haul 1600 network elements, support
CMISE as the application layer protocol.

TARP
Target Identifier Address Resolution Protocol (TARP) is a propagation
protocol allowing network elements to translate between TID values and
NSAP addresses. The TARP feature provides a mapping of TID values to
NSAP addresses, so that TL1 messages reach the proper network element
regardless of the application layer protocol (TL1 or CMISE).
Full TARP services
Nortel Networks OC-3 Express network elements support TL1 as the
application layer protocol. These network elements require full TARP
services.
TARP transparency
Nortel Networks OPTera Long Haul 1600 network elements support CMISE
as the application layer protocol. These network elements do not require TARP
services, but they do provide minimal TARP support. By providing minimal
TARP support, these network elements do not disrupt the operations of
network elements that support TL1 as the application layer protocol (such as
Nortel Networks OC-3 Express network elements). Nortel Networks CMISE
network elements do not originate TARP messages but do propagate them.
This type of support is known as TARP transparency (see Figure 2-2).

TL1 Interface Description 323-1801-190 Rel 3 July 2000

2-8 Interface configurations

TARP transparency is required for operations, administration, and

maintenance (OAM) interoperability between CMISE-based network
elements and TL1-based network elements. TARP transparency is supported
on all tributaries with data communications channel (DCC) capabilities.
Figure 2-2
Target identifier address resolution protocol transparency
F4607-192_R60

OS

TL1 messages

NE NE NE NE

OC-3 Express Nortel Nortel OC-3 Express

or other Networks Networks or other
TL1-managed OC-12, OC-12, TL1-managed
NE OC-48, OC-48, NE
OC-192 OC-192
OPTera OPTera
Long Haul CMISE-based network Long Haul
1600 1600
Legend:
NE = Network Element
OC = Optical Carrier
OS = Operating System
TL1 = Transaction Language 1
TARP = Target Identifier Address Resolution Protocol

Chapter procedure list

Perform the procedure in Table 2-1 to configure direct TL1 login sessions over
Ethernet.

Table 2-1

Action Details

Defining and enabling TCP/IP communications Procedure 2-1

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Interface configurations 2-9

Procedure 2-1
Defining and enabling TCP/IP communications
Use this procedure to access TL1 surveillance interfaces on the operations
controller (OPC) with the Transmission Control Protocol/Internet Protocol
(TCP/IP) telnet session. This procedure allows you to directly log in to the
NMA interface.

Before you start

• Read the command conventions described in OPC User Interface Description, 323-1801-196.
• Use a terminal connected to the OPC. The procedure to connect a terminal to an OPC is in User
Interface Connection Procedures, 323-1801-301. TL1 interfaces are not accessible through the UNIX
shell tool in the User Session Manager. Protocols not supported include X.3 PAD and X.11.

Procedure tasks
• Create a user with the OPC Central User Administration (CUA) tool (step 2).
• Select the appropriate interface (step 5).
• Make a backup copy of the password file (step 8).

Expected results
• You establish a TL1 surveillance session over TCP/IP.
• If the expected results do not occur:
— Check that you created a user called NMA with the OPC CUA tool.
— Check that you entered the right commands at the OPC prompt.
— Check that you were able to telnet to the OPC and log in as nma.

—continued—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

2-10 Interface configurations

Procedure 2-1 (continued)

Defining and enabling TCP/IP communications

Action
Step Action

1 Log in to the OPC as root, and display the User Session Manager by typing
“opcui” at the prompt. If you do not know how to do this, see User Interface
Connection Procedures, 323-1801-301.
2 Create a user with the OPC Centralized User Administration (CUA) tool. If you
do not know how to do this, see Security Management Procedures,
323-1801-305.
Call the user NMA and place in the slat group.
3 Press the Esc key to close the CUA tool.
4 Log out of the User Session Manager.
The “opc>” prompt appears.
5 Select the appropriate interface from the following table:
If you want to access the Then go to
TL1 Surveillance interface (NMA) step 6
Enhanced TL1 Surveillance interface (NMA) step 7

6 At the OPC prompt, enter:

tl1usrsh nma ↵
The following message appears:
Do you wish to make a backup copy of the passwd file (y/n):
Go to step 8.
7 At the OPC prompt, enter:
tl1usrsh -e nma ↵
The following message appears:
Do you wish to make a backup copy of the passwd file (y/n):
Go to step 8.
—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Interface configurations 2-11

Procedure 2-1 (continued)

Defining and enabling TCP/IP communications

Step Action

8 Select the appropriate option from the following table:

If you Then go to
want to make a backup copy of the passwd file step 9
do not want to make a backup copy of the step 10
passwd file

9 At the prompt, enter:

y↵

The following message appears:

Making a backup as /etc/passwd.backup

Go to step 11.
10 At the prompt, enter:
n↵

The following message appears:

No backup made
11 Log out of the OPC.
12 To establish a TL1 surveillance session over TCP/IP, telnet to the OPC and
log in as “nma”.
—end—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

2-12 Interface configurations

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 3-1

Administrative interface 3-
This chapter describes S/DMS TransportNode OPTera Long Haul 1600
network element user administration through the TL1 administrative interface.
It contains definitions of the non-autonomous messages and respective
parameters.

The administrative interface allows security functions such as:

• activate and cancel TL1 user administration sessions
• add and delete user accounts
• retrieve and edit user security information
There are two major sections in this chapter: the Non-autonomous
administrative messages section and the Administering user accounts on the
active OPC through TL1 section.

Chapter procedure list

The procedures shown in Table 3-1 support the tasks of the administrative
interface.

Table 3-1

Action Details

Opening a TL1 administration session Procedure 3-1

Closing a TL1 administration session Procedure 3-2

Retrieving security parameters for a CUA user Procedure 3-3

Adding a user account to the CUA Procedure 3-4

Editing security parameters for a CUA user Procedure 3-5

Deleting a CUA user account Procedure 3-6

TL1 Interface Description 323-1801-190 Rel 3 July 2000

3-2 Administrative interface

Non-autonomous administrative messages

Non-autonomous administrative messages consist of a request message from
the operations system and a response message from the OPC.
Non-autonomous messages have a bidirectional flow between the operations
system and the OPC. An example of bidirectional flow is the user sends a
request for all alarms on a network element, and the OPC acknowledges
whether or not it received the request.

Table 3-2 lists the non-autonomous administrative message types that exist for
user administration.

Table 3-2
Non-autonomous administrative message types

Message type Purpose

ACT-USER (activate user Used by admin and root users to activate a TL1 user administration
session) session.

CANC-USER (cancel user Used to cancel a TL1 user administration session.

session)

DLT-USER-SECU (delete user Used, during a user administration session, to delete a user from the
security) OPC user list.

ED-USER-SECU (edit user Used, during a user administration session, to change the parameters
security) associated with the user.

ENT-USER-SECU (enter user Used, during a user administration session, to add a user to the OPC
security) user list.

RTRV-USER-SECU (retrieve Used, during a user administration session, to retrieve the parameters
user security) associated with the user.

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Administrative interface 3-3

ACT-USER (activate user session)

Purpose
The ACT-USER command activates the TL1 user administration session. It
allows access to other user administration commands. Admin and root users
can activate the ACT-USER command.

See Procedure 3-1, “Opening a TL1 administration session”, for syntax and
usage.
Examples
An example of the ACT-USER command with a normal output response:
ACT-USER:NE_TID:admin:CTAG20::admin;

NE_TID 96-05-22 09:50:04

M CTAG20 COMPLD
"admin"
;

An example of the ACT-USER command with an error output response:

ACT-USER:NE_TID:nouser:CTAG21::PASSWORD;

NE_TID 96-05-22 09:49:58

M CTAG21 DENY
PIUI
/* Privilege, Illegal User Identity */
;

TL1 Interface Description 323-1801-190 Rel 3 July 2000

3-4 Administrative interface

CANC-USER (cancel user session)

Purpose
The CANC-USER command cancels the TL1 user administration session.

See Procedure 3-2, “Closing a TL1 administration session”, for syntax and
usage.
Examples
An example of the CANC-USER command with a normal output response:
CANC-USER:NE_TID::CTAG30;

NE_TID 96-05-22 09:50:52

M CTAG30 COMPLD
"admin"
;

An example of the CANC-USER command with an error output response:

CANC-USER;

92013 96-05-22 09:50:49

M 0 DENY
IISP
/* Invalid Correlation Tag */
;

Note: These examples illustrate the behavior over an X.25 interface; you
can use this command to terminate a TL1 shell interface.

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Administrative interface 3-5

DLT-USER-SECU (delete user security)

Purpose
Use the DLT-USER-SECU command to delete a user from the OPC user list.
Only admin users can activate the DLT-USER-SECU command.

See Procedure 3-6, “Deleting a CUA user account”, for syntax and usage.
Examples
An example of the DLT-USER-SECU command with normal output
responses:
DLT-USER-SECU:NE_TID:newuser:CTAG28;

NE_TID 96-05-22 09:50:40

M CTAG28 COMPLD
;

92013 96-05-22 09:50:42

A 31723 REPT EVT COM

":MISC,,05-22,09-50-41:\"NAD642 User "newuser" deleted.
Result: Success.
OPC Group = "adm\""
;

An example of the DLT-USER-SECU command with an error output response:

DLT-USER-SECU:NE_TID:nouser:CTAG29;

NE_TID 96-05-22 09:50:45

M CTAG29 DENY
PIUI
/* Data Not Valid: UID */
;

TL1 Interface Description 323-1801-190 Rel 3 July 2000

3-6 Administrative interface

ED-USER-SECU (edit user security)

Purpose
The ED-USER-SECU command is used to edit user security information from
the OPC user list. You can edit the user’s ID, group, password, and access
privileges. Only admin users can activate the ED-USER-SECU command.

See Procedure 3-5, “Editing security parameters for a CUA user” for syntax
and usage.
Examples
An example of the ED-USER-SECU command with normal output responses:
ED-USER-SECU:NE_TID:newuser:CTAG24::,SECRET12;

NE_TID 96-05-22 09:50:22

M CTAG24 COMPLD
"newuser:RW:admin"
;

92013 96-05-22 09:50:24

A 31722 REPT EVT COM

":MISC,,05-22,09-50-24:\"NAD645 User "newuser" NE access list
modified.
Result: Success.\""
;

An example of the ED-USER-SECU command with an error output response:

ED-USER-SECU:NE_TID:newuser:CTAG25::,LongPassWord1;

NE_TID 96-05-22 09:50:28

M CTAG25 DENY
PIUI
/* Data Not Valid: PID */
;

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Administrative interface 3-7

ENT-USER-SECU (enter user security)

Purpose
Use the ENT-USER-SECU command to add a user to the OPC user list. You
must specify the user’s ID, group, and access privileges. Only admin users can
activate the ENT-USER-SECU command.

See Procedure 3-4, “Adding a user account to the CUA”, for syntax and usage.
Examples
An example of the ENT-USER-SECU command with normal output
responses:
ENT-USER-SECU:NE_TID:newuser:CTAG22:admin:SECRET12,,RW;

NE_TID 96-05-22 09:50:10

M CTAG22 COMPLD
"newuser:SECRET12:RW"
;

92013 96-05-22 09:50:12

A 31721 REPT EVT COM

":MISC,,05-22,09-50-12:\"NAD641 User "newuser" created.
Result: Success.
OPC Group = "adm\""
;

An example of the ENT-USER-SECU command with an error output

response:
ENT-USER-SECU:NE_TID:newuser2:CTAG23:NoGroup:SECRET12,,R;

NE_TID 96-05-22 09:50:16

M CTAG23 DENY
PIRC
/* Data Not Valid: GRP */
;

TL1 Interface Description 323-1801-190 Rel 3 July 2000

3-8 Administrative interface

RTRV-USER-SECU (retrieve user security)

Purpose
Use the RTRV-USER-SECU command to retrieve user security information
from the OPC user list. This information includes the user’s ID, group, and
access privileges. Only admin users can activate the RTRV-USER-SECU
command.

See Procedure 3-3, “Retrieving security parameters for a CUA user” for syntax
and usage.
Examples
An example of the RTRV-USER-SECU command and a normal output
response:
RTRV-USER-SECU:NE_TID:newuser:CTAG26;

NE_TID 96-05-22 09:50:33

M CTAG26 RTRV
"newuser:,RW:admin"
;

An example of the RTRV-USER-SECU command and an error output

response:
RTRV-USER-SECU:NE_TID:nouser:CTAG27;

NE_TID 96-05-22 09:50:36

M CTAG27 DENY
PIUI
/* Data Not Valid: UID */
;

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Administrative interface 3-9

Administering user accounts on the active OPC through TL1

You can create and manage user accounts and user groups through the
Centralized User Administration (CUA) tool located in the OPC User
Interface. The CUA also allows network element access privileges, userIDs
(for network elements), and user password administration. This section
describes how you can use the CUA administration functionality through a
TL1 connection. For information on the use of the CUA tool, refer to External
Interface Configuration Procedures, 323-1801-302.

See Table 3-3 for the maximum number of user accounts allowed:

Table 3-3
Maximum quantity of CUA user accounts

User account allocation Maximum quantity

User accounts for an NE 128

User accounts in a user group 100

User accounts for all NEs in an OPC span of control 200

User privileges
An OPC defines users that have read, write, and administrative privileges for
each of the network elements in its span of control. Each of these users belongs
to a defined user group on the OPC. Users in the admin and root user groups
are seen as administrators and can perform user administration through the
CUA interface. These admin and root users have the same administration
privileges available through TL1. Users who do not belong to these two groups
do not have administrative privileges.

A user profile is made up of several parameters. Each user defined in the CUA
belongs to a user group. Each user group has Read, Read/Write,
Read/Write/Admin, or no privileges for each network element in its span of
control. Table 3-4 identifies the TL1 syntax of the network element privileges
and the CUA equivalent meanings.

TL1 Interface Description 323-1801-190 Rel 3 July 2000

3-10 Administrative interface

Table 3-4
CUA user privileges
TL1 syntax CUA equivalent meaning

UAP user access privileges of R (read), R/W (read/write),

and R/W/A (read/write/admin)

GRP user group

UID user identification

PID password (password identifier)

Note: The UAPs are the same as user access class on the CUA.

Figure 3-1 is an example CUA user profile window, and shows how a user has
UAPs for each network element. A user with no privileges for a given network
element has the ‘Accessibility’ column set to ‘No’. A user with no accessibility
corresponds to having a UAP value of “NULL” when specified in the TL1
interface.
Figure 3-1
Example CUA user profile window

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Administrative interface 3-11

Table 3-5 shows the relationship between CUA accessibility and access
classes, and the TL1 UAP.

In order for the first TL1 administrator to open a TL1 administration session,
that user must belong to an existing admin or root user account. The first user
can add, modify or delete TL1 administrators through both the TL1 interface
with the commands described in this section, and the CUA tool.
Table 3-5
CUA accessibility and access classes mapped to TL1 UAPs
Accessibility Access class UAP

Yes Read R

Yes Read/Write RW

Yes Read/Write/Admin RWA

No Read NULL

No Read/Write NULL

No Read/Write/Admin NULL

Note: If an OPC CUA session is in progress you cannot add, delete, or

modify user accounts through the TL1 interface. Any TL1 administration
command sent after a CUA session becomes active receives the DENY
error response.

TL1 Interface Description 323-1801-190 Rel 3 July 2000

3-12 Administrative interface

UserID and password formats

UserID and password formats must follow the rules defined by the CUA. See
Table 3-6 for syntax rules.
Table 3-6
UserID and password syntax

UserID • minimum length is one character

• maximum length is eight characters
• alphabetic characters supported include a through z
and A through Z (upper and lower case)
• numeric characters supported include 0 to 9
• the first character must be alphabetic

Password • must be exactly eight characters in length

• alphabetic characters supported include a through z
and A through Z (upper and lower case)
• numeric characters supported include 0 to 9
• special characters supported include $ and _
(underscore)
• the first character must be alphabetic
• passwords must contain at least one numeric or one
special character
• passwords must not contain the associated UserID
• do not reuse an old password unless it is older than
the obsolete password

TL1 message notation

Table 3-7 shows the notation used to define the syntax of the TL1 messages:
Table 3-7
TL1 message notation

Symbol Meaning

↵ keyboard return or enter key

cr ASCII carriage return

lf ASCII line feed

^ ASCII space

[] optional expression

<> variable expression

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Administrative interface 3-13

Error responses
If a TL1 administration command is unsuccessful, a DENY response with a
TL1 error is returned. Table 3-8 lists the error codes that are reported, with a
description of the situation which causes the problem. The error response for
TL1 administration commands follows the syntax:
crlf
lf
^^^<sid>^<date>^<time> crlf
M^^<ctag>^DENY crlf
^^^<errcde> crlf
^^^”<error text>” crlf
;

Table 3-8
TL1 administration session error codes

Err Usage Error text Description

cde

IDNV ent-user-secu Input, Data Not Valid: GRP GRP syntax is invalid.

ed-user-secu Input, Data Not Valid: GRP New GRP syntax is invalid.

ent-user-secu Input, Data Not Valid: GRP GRP does not exist in CUA.

ed-user-secu Input, Data Not Valid: GRP User group specified by NGRP does not
exist in CUA. Use an existing user group.

ent-user-secu Input, Data Not Valid: UAP UAP is something other than {NULL, R, RW,
RWA}.

ed-user-secu Input, Data Not Valid: UAP New UAP is something other than {NULL,
R, RW, RWA}.

act-user Input, Data Not Valid: PID PID syntax is invalid.

ent-user-secu

act-user Input, Data Not Valid: PID PID does not match the actual password.

ent-user-secu Input, Data Not Valid: PID PID is not acceptable to CUA. Possibly due
ed-user-secu to improper syntax. Check the password
format rules for the CUA.

ed-user-secu Input, Data Not Valid: PID New PID syntax is invalid.

act-user Input, Data Not Valid: UID UID does not exist.
ed-user-secu

canc-user Input, Data Not Valid: UID UID syntax is invalid. The UID syntax is
dlt-user-secu incorrect or the UID does not exist.
—continued—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

3-14 Administrative interface

Table 3-8 (continued)

TL1 administration session error codes

Err Usage Error text Description

cde

IDNV ent-user-secu Input, Data Not Valid: UID UID syntax is incorrect.
ed-user-secu

ent-user-secu Input, Data Not Valid: UID UID is not acceptable to CUA. Possibly due
to improper syntax. Check the user id format
rules for the CUA.

rtrv-user-secu Input, Data Not Valid: UID UID syntax was invalid or no such user
found.

IICM ent-user-secu Input, Invalid Command No administration session is active. Use the
dlt-user-secu ACT-USER command first.
rtrv-user-secu
ed-user-secu

IICT act-user Input, Invalid Correlation Tag CTAG is invalid.

canc-user
ent-user-secu
dlt-user-secu
rtrv-user-secu
ed-user-secu

IISP act-user Input, Invalid Syntax or Incorrect number of blocks specified.

canc-user Punctuation
ent-user-secu
dlt-user-secu
rtrv-user-secu
ed-user-secu

IITA act-user Input, Invalid TArget Identifier No such TID was in the OPC span of
canc-user control.
ent-user-secu
dlt-user-secu
rtrv-user-secu
ed-user-secu

INUP act-user Input, Non-null Unimplemented Second-last block must be empty.

Parameter

ent-user-secu Input, Non-null Unimplemented Second parameter in the last block must be
Parameter left blank.

ed-user-secu Input, Non-null Unimplemented Third parameter in the last block must be left
Parameter blank.
—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Administrative interface 3-15

Table 3-8 (continued)

TL1 administration session error codes

Err Usage Error text Description

cde

SARB act-user CUA interface is in use CUA tool is open in the OPC User Session
canc-user Manager. You cannot send TL1
ent-user-secu administration commands until you close
dlt-user-secu the CUA tool.
rtrv-user-secu
ed-user-secu

SROF act-user User has no admin privileges User was not a member of the admin or root
user groups and does not have
administrative privileges.

ent-user-secu User ID already exists UID already exists on the OPC.

—end—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

3-16 Administrative interface

Procedure 3-1
Opening a TL1 administration session
Use this procedure to open a TL1 administration session to use the
administrator TL1 commands. Only users from the admin and root user groups
can open a TL1 administration session. To open a TL1 administration session
use the activate user (act-user) command.

After you use the ACT-USER command, no other user can activate a session
on that TL1 connection. The current user must cancel the session with the
cancel user (canc-user) command. Refer to Procedure 3-2, “Closing a TL1
administration session”.

Note: If you attempt to execute a TL1 administration command without

first opening a TL1 administration session, you get an ‘Invalid Command’
response.

Open a TL1 administration session from the surveillance TL1 interfaces.

Before you start

• Obtain a user identifier that belongs to either the admin or root user groups. If the user identifier belongs
to the admin or root user groups, then you can execute any of the TL1 commands in the TL1 interface
message set as well as the TL1 administration commands. If the user identifier does not belong to the
admin or root user groups, then none of the administration commands are functional.
• Obtain a private identifier or a password. It is the responsibility of the operations system or the application
to hide the password from view.

Procedure tasks
• Establish a connection to a TL1 interface of the OPC (step 1).
• Open a TL1 administration session (step 2).

Expected results
• You open a TL1 administrative session.
• If the expected results do not occur:
— Refer to “Error responses” on page 3-13 for error responses.

—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Administrative interface 3-17

Procedure 3-1 (continued)

Opening a TL1 administration session

Action
Step Action

1 Establish a connection to a TL1 interface of the OPC according to standard

operations system procedures.
2 To open a TL1 administration session, issue the following message:
act-user:[tid]:<uid>:<ctag>::<pid>;crlf

where
<tid> is the optional target identifier
Note: The tid must be a valid identifier in the OPC span of
control.
<uid> is the user identifier of a user in either the admin or root user
groups. See Table 3-6 for syntax information.
<ctag> is the correlation tag
<pid> is the private identifier, or password. See Table 3-6 for syntax.

If the command successfully executes, you receive this message:

crlf
lf
^^^<sid>^<date>^<time> crlf
M^^<ctag>^COMPLD crlf
^^^”<uid>” crlf
;

where
<sid> is the source identifier
<ctag> is the correlation tag
<uid> is the user identifier
—end—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

3-18 Administrative interface

Procedure 3-2
Closing a TL1 administration session
Use this procedure to close a TL1 administration session. The activate user
(act-user) command opens the session. Refer to Procedure 3-1, “Opening a
TL1 administration session”.

Before you start

• Note that only users from the admin and root user groups can close a TL1 administration session. Close
a TL1 administration session with the cancel user (canc-user) command.

Procedure tasks
• Close a TL1 administration session by issuing a TL1 message (step 1).

Expected results
• The TL1 administration session closes.
• If the expected results do not occur:
— Refer to “Error responses” on page 3-13 for error responses.

—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Administrative interface 3-19

Procedure 3-2 (continued)

Closing a TL1 administration session

Action
Step Action

1 To close a TL1 administration session, issue the following message:

canc-user:[tid]:[uid]:<ctag>;crlf

where
<tid> is the optional target identifier
Note: The tid must be a valid identifier in the OPC span of
control.
<uid> is the optional user identifier
See Table 3-6 for syntax information.
Note: If you enter the uid specify the current user. If you do
not enter the uid, the system assumes it is the current user.
<ctag> is the correlation tag

If the command successfully executes, you receive this message:

crlf
lf
^^^<sid>^<date>^<time> crlf
M^^<ctag>^COMPLD crlf
^^^”<uid>” crlf
;

where
<sid> is the source identifier
<ctag> is the correlation tag
<uid> is the user identifier
—end—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

3-20 Administrative interface

Procedure 3-3
Retrieving security parameters for a CUA user
Use this procedure during a TL1 administration session to retrieve the security
parameters associated with a Centralized User Administration (CUA) user.

Note 1: You can not retrieve a user’s password.

Note 2: If you attempt to execute a TL1 administration command without
first opening a TL1 administration session, you get an ‘Invalid Command’
response. Refer to Procedure 3-1,“Opening a TL1 administration session”.
If you issue a request to retrieve all users from the CUA for a specified network
element, there is no distinction between user accounts that are active and those
that have expired. All expired user accounts appear in the TL1 response.

Before you start

• Begin or continue an active TL1 administration session.

Procedure tasks
• Retrieve security parameters by issuing a TL1 message (step 1).

Expected results
• Security parameters are retrieved.
• If the expected results do not occur:
— Refer to “Error responses” on page 3-13 for error responses.

—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Administrative interface 3-21

Procedure 3-3 (continued)

Retrieving security parameters for a CUA user

Action
Step Action

1 To retrieve security parameters, issue the following message:

rtrv-user-secu:<tid>:[uid]:<ctag>;crlf

where
<tid> is the target identifier (not optional)
Note: The user access privileges for the specified target
identifier are in the TL1 response.
<uid> is the optional user identifier
See Table 3-6 for syntax information.
Note: If you enter a specified uid, the security parameters for
that specified user are retrieved. If you do not specify a uid, the
security parameters for all user accounts are retrieved.
<ctag> is the correlation tag

If the command successfully executes, you receive this message:

crlf
lf
^^^<sid>^<date>^<time> crlf
M^^<ctag>^RTRV crlf
[^^^”<uid>:,<uap>:<grp>” cr lf]+
;

where
<sid> is the source identifier
<ctag> is the correlation tag
<uid> is the user identifier
<uap> is the user access privilege for the listed user account
Options include:
R (read access only)
RW (read/write access only)
RWA (read/write/admin access)
NULL (no access)
<grp> is the user group that contains the listed user account
Note: Example groups include admin, netsurv and slat.

Note: This line appears for each user account.

—end—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

3-22 Administrative interface

Procedure 3-4
Adding a user account to the CUA
Use this procedure during a TL1 administration session to add a user account
to the Centralized User Administration (CUA). The parameters that you need
to specify are:
• user id
• group (grp)
• password (pid)
• user access privilege (uap)
Note 1: The uap applies to each network element in the span of control.
Note 2: You cannot add user accounts through TL1 if an OPC CUA
session is in progress. If you issue a ent-user-secu command after a CUA
session becomes active you get a DENY error response.
Note 3: If you attempt to execute a TL1 administration command without
first opening a TL1 administration session, you get an ‘Invalid Command’
response. Refer to Procedure 3-1, “Opening a TL1 administration session”.

Before you start

• Begin or continue an active TL1 administration session.
• Acquire the user id of the new user account.
• Have the user group contain the new user account.
• Have the user access privileges for the new user account.
• Have the password for the new user account. It is the responsibility of the operations system or the
application to hide this password from view.

Procedure tasks
• Add a user account to the CUA by issuing a TL1 message (step 1).

Expected results
• A new user account is added. The parameters of the new user account appear in a response message.
• If the expected results do not occur:
— Refer to “Error responses” on page 3-13 for error responses.

—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Administrative interface 3-23

Procedure 3-4 (continued)

Adding a user account to the CUA

Action
Step Action

1 To add a user account to the CUA, issue the following message:

ent-user-secu:[tid]:<uid>:<ctag>:<grp>:<pid>,,<uap>;crlf

where
<tid> is the optional target identifier
Note: If you use the tid, make sure it is valid in the OPC span
of control. The tid has no significance when used with this
command.
<uid> is the user identifier for the new user
See Table 3-6 for syntax information.
Note: This user identifier must be unique to the CUA.
<ctag> is the correlation tag
<grp> is the group to contain the added user
Note: This must be a group known to the CUA, for example,
admin.
<pid> is the password for the added user account
See Table 3-6 for syntax information.
Note: It is the responsibility of the operations system or the
application to hide this password from view.
<uap> is the user access privilege for the added user account
Options include:
R (read access only)
RW (read/write access only)
RWA (read/write/admin access)
NULL (no access)
Note: These privileges apply to each NE in the OPC span of
control as a default for the new user. If new user requires
different privileges for each NE, use the ed-user-secu
command. See Procedure 3-5, “Editing security parameters
for a CUA user”.

If the command successfully executes, you receive this message:

crlf
lf
^^^<sid>^<date>^<time> crlf
M^^<ctag>^COMPLD crlf
^^^”<uid>:<pid>:<uap>” crlf
;
—end—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

3-24 Administrative interface

Procedure 3-5
Editing security parameters for a CUA user
Use this procedure during a TL1 administration session to modify a
Centralized User Administration (CUA) user account. Parameters that you can
change are user id (uid), group (grp), password (pid), and user access privilege
(uap).
If you change the access privilege to NULL for one or more network elements,
that account will no longer exist on those network elements. If the user is on
an active session when the access privilege changes to NULL, the user session
can continue unaffected. After the user logs out of the network elements, their
password expires and the user will not be able to log on to those network
elements again. After the Centralized User Administration audit, user accounts
with NULL access privileges no longer exist on the network elements.

Note 1: The uap applies to each NE in the span of control.

Note 2: You cannot modify user accounts through TL1 if an OPC CUA
session is in progress. If you issue a ed-user-secu command after a CUA
session becomes active you get a DENY error response.
Note 3: If you attempt to execute a TL1 administration command without
first opening a TL1 administration session, you get an ‘Invalid Command’
response. Refer to Procedure 3-1, “Opening a TL1 administration session”.
—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Administrative interface 3-25

Procedure 3-5 (continued)

Editing security parameters for a CUA user

Before you start

• Begin or continue an active TL1 administration session.
• Get the user id of the existing user account.
• Have the new user group contain the existing user account.
• Have the new user access privileges for the existing user account.
• Have the new password for the existing user account. It is the responsibility of the operations system or
the application to hide this password from view.

Procedure tasks
• Modify a CUA user account by issuing a TL1 message (step 1).

Expected results
• The following security parameters will change to your new values: user id (uid), group (grp), password
(pid), and user access privilege (uap).
• If the expected results do not occur:
— Refer to “Error responses” on page 3-13 for error responses.

—continued—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

3-26 Administrative interface

Procedure 3-5 (continued)

Editing security parameters for a CUA user

Action
Step Action

1 To modify a CUA user account, issue the following message:

ed-user-secu:<tid>:<uid>:<ctag>:[ngrp]:,[npid],,[nuap];
crlf

where
<tid> is the target identifier, which is not optional
Note: The command still executes when the TID value is null.
<uid> is the user identifier
See Table 3-6 for syntax information.
<ctag> is the correlation tag
<ngrp> is the optional new group to contain the user
Note: If specified, this must be a group known to the CUA, for
example, admin. If not specified, the user’s group does not
change.
<npid> is the optional new password for the user account
See Table 3-6 for syntax information.
Note: The operations system is responsible for hiding this
password from view. If not specified, the password does not
change.
<nuap> is the optional new user access privilege for the user account
Options include:
R (read access only)
RW (read/write access only)
RWA (read/write/admin access)
NULL (no access)
The privileges apply to the NE specified by the tid.
—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Administrative interface 3-27

Procedure 3-5 (continued)

Editing security parameters for a CUA user

Step Action

If the command successfully executes, you receive this message:

crlf
lf
^^^<sid>^<date>^<time> crlf
M^^<ctag>^COMPLD crlf
^^^”<uid>:<uap>:<grp>” crlf
;

where
<uap> is the new value, if changed
<grp> is the new value, if changed
—end—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

3-28 Administrative interface

Procedure 3-6
Deleting a CUA user account
Use this procedure during a TL1 administration session to delete a user
account from the Centralized User Administration (CUA). Deletion of user
accounts must conform to the CUA rules. It is not possible to delete the admin
user account. See External Interface Configuration Procedures,
323-1801-302, for the CUA rules.

Note 1: You cannot delete user accounts through TL1 if an OPC CUA
session is in progress. If you issue a dlt-user-secu command after a CUA
session becomes active you get a DENY error response.
Note 2: If you attempt to execute a TL1 administration command without
first opening a TL1 administration session, you get an ‘Invalid Command’
response. Refer to Procedure 3-1, “Opening a TL1 administration session”.
Note 3: If the user is on an active session on the OPC when their account
gets deleted the user can continue in the session unaffected. After the user
logs out of the session, the user is not able to log in again.
Note 4: If the user is on an active session on a network element when their
account gets deleted, the user can continue in the session unaffected. After
the user logs out of the network element their user password expires and
the user is not able to log on to that network element again. After the
Centralized User Administration audit, that user account no longer exists
on network elements where the account was deleted.

Before you start

• Begin or continue an active TL1 administration session.
• Get the user id of the user account that you want to delete.

Procedure tasks
• Delete a CUA user account by issuing a TL1 message (step 1).

Expected results
• The CUA user account gets deleted and a TL1 message appears.
• If the expected results do not occur:
— Refer to “Error responses” on page 3-13 for error responses.

—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Administrative interface 3-29

Procedure 3-6 (continued)

Deleting a CUA user account

Action
Step Action

1 To delete a CUA user account, issue the following message:

dlt-user-secu:[tid]:<uid>:<ctag>; crlf

where
<tid> is the optional target identifier
Note: If you use the tid, make sure it is valid in the OPC span
of control. The tid has no significance when used with this
command.
<uid> is the user identifier
<ctag> is the correlation tag

If the command successfully executes, you receive this message:

crlf
lf
^^^<sid>^<date>^<time> crlf
M^^<ctag>^COMPLD crlf
;
—end—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

3-30 Administrative interface

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 4-1

Surveillance interface 4-
This chapter describes OPTera Long Haul 1600 network element alarm
surveillance through the TL1 surveillance interface. It provides the association
between the alarms and their equivalent TL1 messages. This chapter also
provides definitions of messages and parameters.

Chapter summary
See Table 4-1 for the sections provided in this chapter.

Table 4-1
Major sections in this chapter

Section

TL1 message notation

Message parameters

TL1 acknowledgment responses and error codes

Alarm summary

Autonomous messages

Non-autonomous messages

Message associations

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-2 Surveillance interface

TL1 message notation

The following notation defines the syntax of TL1 messages:

Symbol Meaning

cr ASCII carriage return

lf ASCII line feed

^ ASCII space

[] optional expression

<> variable expression

Message parameters
This section describes the surveillance message parameters listed in Table 4-2.

Table 4-2
TL1 surveillance message parameters

Parameter Description

ACTID Identification of the active Operations Controller (OPC)

AID Access identifier / Identification of the equipment/facility

AIDTYPE Type of access identifier

ALMCDE Identification of the alarm severity

ALMMSG Alarm message text

ALMTYPE Identification of the environmental alarm

ATAG Automatic transaction identifier

CONDDESCR Condition text description

CONDEFF Indication of the condition

CONDTYPE Type of event

CTAG Correlation identifier

Date Date of origination of the message

DATE The new date for the OPC

DIRN Direction of the event

DUR Duration

ERRCDE Error code

—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-3

Table 4-2
TL1 surveillance message parameters (continued)

Parameter Description

LOCN Location of the event

MODE Switch mode

MODETYPE Performance monitoring mode type

MONDAT Month and day of the beginning of the performance

monitoring (PM) period

MONLEV Monitor level

MONTM Time of origination of the message

MONTYPE PM type of the monitored parameter

MONVAL PM value of the monitored parameter

NTFCNCDE Alarm code

OCRDAT Date of the event occurrence

OCRTM Time of the event occurrence

PMSTATE Performance monitoring state

REF Timing reference number

SCCM Second command code modifier

SID NE or OPC identifier which originated the message

SRVEFF Service effect

STATE Service state

STBYID Identification of the standby OPC

THLEV Crossed threshold value

TID Target NE identifier

Time Time of origination of the message

TIME The new time for the OPC time of day clock

TMPER PM accumulation time period

TYPEREQ Types of condition to retrieve

VLDTY Indicates the validity of the PM counts in a day bin

ACTID
The ACTID parameter indicates the name of the active OPC module.

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-4 Surveillance interface

Format
The ACTID parameter format consists of up to 20 characters of ASCII text that
follow the syntax restrictions of the AID parameter.

AID
The AID parameter indicates the identification of the access point at the
network element or OPC to which terminations are made. See Table 4-3 for
AID parameters and the modified formats in which they appear.
Format
The AID parameter format consists of up to three fields, separated by hyphens,
that describe the physical location of the target for the TL1 request.

This is the format of the AID parameter:

<frame>-<circuit pack group>-[<port-id>]

Table 4-3
AID formats

SCCM parameter AID format

ALL NULL

COM NULL

ENV <Eqid>
<Eqid>-<Fan_id>
<Eqid>-<Battery_id>
<Eqid>-<CPGname>-<Scan_point_id>

EQPT <Eqid-<CPGname>-[<Slot_id>]

OC48 <Eqid>-<CPGname>

OC192 <Eqid>-<CPGname>

T1 <Eqid>-<ESI_Fac_id>-[<member_name>]

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-5

AIDTYPE
The AIDTYPE parameter indicates the access identifier type. This parameter
appears in the response to a Retrieve Alarm message. This parameter has the
same value as the second command code modifier (SCCM) of the
corresponding autonomous Report Alarm message. See Table 4-4 for the
AIDTYPE parameter domains.

Table 4-4
AIDTYPE parameter domains

AIDTYPE domains Description

ALL All facilities and equipments

COM Common

EQPT Equipment unit

ENV Environmental

OC48 OC-48 facility

OC192 OC-192 facility

T1 External Synchronization Interface (ESI) related

ALMCDE
The ALMCDE parameter indicates the alarm severity code. See Table 4-5 for
the ALMCDE parameter domains.

Note: If multiple alarms are reported, the ALMCDE parameter assumes

the highest severity of the alarms reported. The parameter takes the value
A^ only when the value of the NTFCNCDE is CL (cleared).

Table 4-5
ALMCDE parameter domains

ALMCDE domains Description

*C Critical alarm

** Major alarm

*^ Minor alarm

A^ Autonomous message

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-6 Surveillance interface

ALMMSG
The ALMMSG parameter indicates the alarm text description.
Format
The ALMMSG parameter format consists of up to 40 characters of ASCII text
as seen on the alarms screen, enclosed within escaped quotes (\”).

ALMTYPE
The ALMTYPE parameter indicates alarm indication type. The value of the
parameter determines the format of the AID parameter for all messages related
to environmental alarms. When the ALMTYPE parameter has a null value, the
AID parameter has no meaning. See Table 4-6 for the ALMTYPE parameter
domains.

Note: The null value is meaningful only in the Retrieve Alarm

Environment message.

Table 4-6
ALMTYPE parameter domains

ALMTYPE domains Description

NULL All environmental alarms

BATTERY Battery failure

CLFAN Cooling fan failure

HITEMP Shelf over temperature

MISC Miscellaneous environmental alarm

FUSE SATT fuse

PWR Low shelf voltage

ATAG
The ATAG parameter is a numeric transaction identifier, similar to the CTAG
identifier. The TL1 software in the OPC module generates the value of the
ATAG automatically. The ATAG parameter is a sequence number that appears
in autonomous messages only.

The number by which the ATAG parameter increments, in the REPT COND
message, is dependent on the SCCM parameter. If the SCCM value is ALL, the
ATAG parameter increases by 10. If there are no standing alarms, the ATAG
parameter increases by one.

The REPT PM TL1 message increments the ATAG parameter by one for each
of the PM values reported.

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-7

Format
The ATAG parameter format consists of an integer number, of up to six
characters, ranging from 1 to 999999. The ATAG identifies the generated TL1
messages. It is an automatic message counter which increments by one or 10
for each autonomous message. The ATAG value of the first TL1 autonomous
message is a random number and it wraps around from 999999 to 1.

CONDDESCR
The CONDDESCR parameter indicates the condition text description.
Format
The CONDDESCR parameter format consists of up to 64 characters of ASCII
text of the log text seen in the OPC Event Browser, enclosed within escaped
quotes (\”).

CONDEFF
The CONDEFF parameter indicates the effect of the event on the condition of
the network element. See Table 4-7 for the CONDEFF parameter domains.

Table 4-7
CONDEFF parameter domains

CONDEFF domains Description

CL Clear standing condition

SC Standing condition

TC Transient condition

CONDTYPE
The CONDTYPE parameter indicates the condition event type. See Table 4-8
for the CONDTYPE parameter domains.

Table 4-8
CONDTYPE parameter domains
CONDTYPE domains Description
ACCESSDENY Access is denied
ACTLPBK Active loopback in effect
AIS Alarm indication signal detected
APSB Automatic protection switching byte failure
BKUPMEMP Primary non-volatile backup memory failure
BKUPMEMS Secondary non-volatile backup memory failure
BUERR Bus error
CCBPV Composite clock bipolar violation density error
—continued—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-8 Surveillance interface

Table 4-8
CONDTYPE parameter domains (continued)
CONDTYPE domains Description
CONTBUS Control bus failure
CONTCOM Control communications equipment failure
CONTEQPT Control equipment failure
CONTR Control processor failure
DATAFLT Data integrity fault
DBMEMTRF Database synchronization failure
DISKERR Hard disk error
DISKFULL Hard disk full
EOC Embedded operations channel failure
FAILTOSW Switch to protection failure
FERF Line far end receive failure
FRCDWKSWPR Forced switch to protection channel/equipment
FRD Fraud detected
FRNGSYNCCG Free running synchronization mode
FSTSYNC Fast start synchronization mode
HLDOVRSYNC Holdover synchronization mode
INCFAD Incoming failure due to fading
INHSWPR Protection switch inhibited
INIT Initialization executed
INTRUDER Intrusion attempt
INTSFT Internal software fault
IMPROPRMVL Improper removal
LOCKOUTOFPR Lockout of protection
LOCKOUTOWK Lockout of working
LOF Loss of frame
LOP Loss of pointer
LOS Loss of signal
LOTRI Loss of timing reference input
MA Multiple access problem
MISC Miscellaneous condition (used with logs)
MISC-1 Miscellaneous condition
MISC-2 Miscellaneous condition
MANWKSWPR Manual switch to protection channel/equipment
MANSWTOPRI Manual switch to primary synchronization reference
—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-9

Table 4-8
CONDTYPE parameter domains (continued)
CONDTYPE domains Description
MANSWTOSEC Manual switch to secondary synchronization
reference
MSGTHRTLACT Message throttling active
NTTST Network termination returns to no test mode
OC48TERM OC-48 facility termination equipment failure
OC192TERM OC-192 facility termination equipment failure
ORDRWR Orderwire channel failure
PAINTGRT Path integrity failure
RCVR Receiver failure
SFI Rx AIS
SWEQPT Protection switching equipment failure
SYNC Oscillating synchronization status
SYNCCLK Synchronization unit failure
SYNCPRI Synchronization to primary reference failure
SYNCSEC Synchronization to secondary reference failure
TDTERM Timing Distribution Card (TDC) equipment failure
T-AIS Section alarm indication signal threshold exceeded
T-AISSP Path alarm indication signal second
T-BCVL Line bipolar coding violation
T-BESL Line bipolar errored seconds
T-BIPS Section bit interleaved parity threshold exceeded
T-BSESL Line bipolar severely errored seconds
T-GPMLSD Group PM line section day
T-GPMLS1MIN Group PM line section 1 minute
T-GPMLSM Group PM line section minutes
T-GPMIPD Group PM path day
T-GPMIPM Group PM path minutes
T-CVL Line code violation threshold exceeded
T-CVP Path code violation threshold exceeded
T-CVS Section code violation threshold exceeded
T-ESL Line errored seconds threshold exceeded
T-ESP Path errored seconds threshold exceeded
T-ESS Section errored seconds threshold exceeded
T-LBCL Laser bias current level threshold exceeded
—continued—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-10 Surveillance interface

Table 4-8
CONDTYPE parameter domains (continued)
CONDTYPE domains Description
T-LPR Laser power receive threshold exceeded
T-LPT Laser power transmit threshold exceeded
T-OOF Threshold exceeded-out of frame
T-SASP Path severely errored frame second/alarm indication
signal second
T-SEFSP Path severely errored frame seconds
T-SEFSS Section severely errored frame seconds
T-SESL Line severely errored seconds threshold exceeded
T-SESP Path severely errored seconds threshold exceeded
T-SESS Section severely errored seconds threshold
exceeded
T-UASL Line unavailable seconds threshold exceeded
T-UASP Path unavailable seconds threshold exceeded
TRMT Transmitter failure
WKSWPR Working facility/equipment switch to protection
WTR Wait to restore mechanism
YEL Yellow signal received

CTAG
The CTAG parameter is a correlation identifier generated by the operations
system (OS) and used to correlate non-autonomous command and response
messages. It can contain mixed numeric or alphabetic characters. If the first
character is numeric, the remaining characters must be numeric. The TL1
software in the OPC keeps track of correlation identifiers for outstanding
non-autonomous requests.
Format
The CTAG parameter format consists of up to 6 ASCII characters.

Date
The Date parameter indicates the TL1 message translation date. See Table 4-9
for the Date parameter domains.
Format
This is the format of the Date parameter:

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-11

<yy>-<mm>-<dd>

Table 4-9
Date parameter domains

Date domains Description

yy Last two digits of the year (00 to 99)

mm Month (01 to 12)

dd Day of the month (01 to 31)

DATE
The DATE parameter indicates the new date to which the OPC time of day
clock will change to. See Table 4-10 for the DATE parameter domains.
Format
This is the format of the Date parameter:
<yy>-<mm>-<dd>

Table 4-10
DATE parameter domains

DATE domains Description

yy Last two digits of the year (00 to 99)

mm Month (01 to 12)

dd Day of the month (01 to 31)

DIRN
The DIRN parameter indicates the direction of the event. See Table 4-11 for
the DIRN parameter domains.

Table 4-11
DIRN parameter domains

DIRN domains Description

AZ From A office to Z office (Transmit)

ZA From Z office to A office (Receive)

BTH Both directions (Transmit and Receive)

NA Not applicable

NULL Direction is not relevant

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-12 Surveillance interface

DUR
The DUR parameter indicates the duration of the contact operation.
Continuous latching of the relay contacts is possible from the surveillance
operations system. See Table 4-12 for a description of the DUR parameter
domains.

Table 4-12
DUR parameter domains

DUR domains Description

CONTS Releases or operates a parallel external output

permanently

MNTRY Releases or operates a parallel external output for a

1-second interval

ERRCDE
The ERRCDE parameter indicates the associated error code of the message.
See Table 4-28 on page 4-24 for a listing of error codes and their respective
descriptions.

LOCN
The LOCN parameter indicates the location of the event. See Table 4-13 for
the LOCN parameter domains.

Table 4-13
LOCN parameter domains

LOCN domains Description

FEND Far end

NEND Near end

1 Fan #1 (environmental alarm only)

2 Fan #2 (environmental alarm only)

3 Fan #3 (environmental alarm only)

A Battery A or Breaker Filter A

(environmental alarm only)

B Battery B or Breaker Filter B

(environmental alarm only)

FA Breaker Filter A (environmental alarm only)

FB Breaker Filter B (environmental alarm only)

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-13

MODE
The MODE parameter indicates the switch mode of the event. See Table 4-14
for the MODE parameter domains.

Table 4-14
MODE parameter domains

MODE domains Description

NORM Manual switch, linear system

Manual ring switch, ring system

FRCD Forced switch, linear system

Forced ring switch, ring system

MODETYPE
The MODETYPE parameter indicates the performance monitoring parameters
which will be retrieved or set. See Table 4-15 for MODETYPE parameter
domains.
Table 4-15
MODETYPE parameter domains

MODETYPE domains Description

ALL All parameters which apply to the specified SCCM

P All path parameters

L All line parameters

S All section parameters

PROT-L All line protection switching parameters

PROT-R All ring protection switching parameters

PROT-S All section protection switching parameters

PROT All protection switching parameters

PHYS All physical performance monitoring parameters

MONDAT
The MONDAT parameter indicates the month and day of the start of the PM
monitoring period specified by TMPER. This parameter has the format
MONTH-DAY. MONTH and DAY should be the Greenwich mean time
equivalent of the local OPC time. If null, the default is the current date. To
retrieve several daily counts use parameter grouping with this parameter. See
Table 4-16 for MONDAT parameter domains.

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-14 Surveillance interface

The date associated with the first bin is specified in the MONTM field. When
you request 15-minute bins for the previous day (that is, prior to midnight), the
date must not be null. Put the previous day’s date into the field if MONTM is
not set to ALL. If MONTM is set to ALL, MONDAT must be null.
Format
This is the format of the MONDAT parameter:
<mm>-<dd>

Table 4-16
MONDAT parameter domains

MONDAT domains Description

mm Month (01 to 12)

dd Day of the month (01 to 31)

MONLEV
The MONLEV parameter indicates the monitor level of the PM data to report.
See Table 4-17 for the MONLEV parameter domains. A null value defaults to
1-UP.
Format
The MONLEV parameter format consists of two fields separated by a hyphen.
This is the format of the MONLEV parameter:
<lev>-<dir>

Table 4-17
MONLEV parameter domains

MONLEV Description
domains

lev Decimal number (level)

dir Either the value UP indicating that monitored parameters with a

value equal to or greater than the value of <lev> is reported; or the
value DN indicating that monitored parameters with a value lower
than the value of <lev> is reported.

MONTM
The MONTM parameters indicate the hour and minute of the start of the PM
monitoring period specified by TMPER. This parameter has the format
HOUR-MINUTE. A null value defaults to the start of the last 15-minute bin
collected at the OPC. Note that these last 15-minute bins can not all align to
the same time period for all termination classes collected. The alignment of the

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-15

time periods depends on the actual time when the collection of PM counts took
place on the OPC. You must explicitly enter the time range or single interval if
all bins need to align to the same time period.

If you specify ALL for the MONTM parameter, the date parameter
(MONDAT) must be null. When you specify MONTM as ALL, all 15-minute
bins with non-zero counts are retrieved. The 15-minute bins will have the
correct time stamp, regardless of whether the 8-hour interval falls within the
same day or across two days.

If you have not run PM collection or updated the PM database for several hours
or days, use the RTRV-PM command with MONTM=ALL to retrieve these
stale records with their correct time stamps. Use parameter grouping with this
parameter to retrieve several 15-minute counts. See Table 4-18 for the
MONTM parameter domains.
Format
The MONTM parameter format consists of two fields separated by a hyphen.
This is the format of the MONTM parameter:
<hh>-<mm>

Table 4-18
MONTM parameter domains

MONTM domains Description

hh Hour of the day (00 to 23)

mm Minute of the hour (00 to 59)

MONTYPE
The MONTYPE parameter indicates the performance monitor (PM) type of
the monitored PM parameter. See Table 4-19 for the MONTYPE parameter
domains.

MONVAL
The MONVAL parameter indicates the performance monitor value of the
monitored PM parameter. See Table 4-19 for the MONVAL parameter
domains.

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-16 Surveillance interface

Note: Integer-1 is an integer number restricted to less than 10 digits long.

Decimal-2 is a decimal number without restrictions.

Table 4-19
MONTYPE and MONVAL parameter domains

MONTYPE MONVAL Description

domains domains

CVL integer-1 Coding violation count - Line

CVP integer-1 Coding violation count - Path

CVS integer-1 Coding violation count - Section

ESL integer-1 Errored second count - Line

ESP integer-1 Errored second count - Path

—continued—

ESS integer-1 Errored second count - Section

FCL integer-1 Failure counts - Line

FCP integer-1 Failure counts - Path

FECL integer-1 Forward error correction - Line

PSC integer-1 Protection switch complete

PSCL integer-1 Protection switch complete - Line

PSCR integer-1 Protection switch complete - Ring

PSCS integer-1 Protection switch complete - Span

PSD integer-1 Protection switch duration-seconds

PSDL integer-1 Protection switch duration - Line

PSDR integer-1 Protection switch duration - Ring

PSDS integer-1 Protection switch duration - Span

SEFSS integer-1 Severe errored frame seconds - Section

SESL integer-1 Severely errored second count - Line

SESP integer-1 Severely errored second count - Path

SESS integer-1 Severely errored second count - Section

UASP integer-1 Unavailable second count - Path

UASL integer-1 Unavailable second count - Line

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-17

NTFCNCDE
The NTFCNCDE parameter indicates the notification code of the message.
See Table 4-20 for the NTFCNCDE parameter domains.

Note: The CL value does not appear in the Report Condition, Retrieve
Alarm, and Retrieve Alarm Environment messages.

Table 4-20
NTFCNCDE parameter domains

NTFCNCDE domains Description

CR Critical alarm

MJ Major alarm

MN Minor alarm

CL Cleared alarm

OCRDAT
The OCRDAT parameter indicates the date of the event occurrence. See Table
4-21 for the OCRDAT parameter domains.
Format
The OCRDAT parameter format consists of two fields separated by a hyphen.
This is the format of the OCRDAT parameter:
<mm>-<dd>

Table 4-21
OCRDAT parameter domains

OCRDAT domains Description

mm Month (01 to 12)

dd Day of the month (01 to 31)

OCRTM
The OCRTM parameter indicates the time of the event occurrence. See Table
4-22 for the OCRTM parameter domains.
Format
The OCRTM parameter format consists of three fields separated by hyphens.
This is the format of the OCRTM parameter:
<hh>-<mm>-<ss>

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-18 Surveillance interface

Note 1: When you put an entity with an alarm against it out of service
(OOS), the alarm clears. When you put this same entity back in service (IS)
without correcting the cause of the alarm, the alarm raises again. The
timestamp of the alarm has the same value as the timestamp when the
alarm was first raised.
Note 2: When you provision an entity with an alarm against it as ‘not
reported’, the alarm clears. When you provision this same entity back to
‘reported’ without correcting the cause of the alarm, the alarm raises again.
The timestamp of the alarm has the same value as the timestamp when the
alarm was first raised
Table 4-22
OCRTM parameter domains

OCRTM domains Description

hh Hour of the day (00 to 23)

mm Minute of the hour (00 to 59)

ss Seconds of the minute (00 to 59)

PMSTATE
The PMSTATE parameter indicates the performance monitoring collection
state. The possible domains for this parameter are:

• ON
• OFF
REF
The timing reference number is for synchronization switching commands.
There can be up to six references with integer values of 1, 2, 3, 4, 5, and 6. The
integers correspond to the actual timing references. Provision the actual timing
reference in the timing reference protection user interface screen. See Table
4-23 for the REF parameter domains.

Table 4-23
REF parameter domains

Integers Actual timing references can be

1 BITSA, BITSB, OCA, OCB, OCC, or OCD

2 BITSA, BITSB, OCA, OCB, OCC, or OCD

3 BITSA, BITSB, OCA, OCB, OCC, or OCD

4 BITSA, BITSB, OCA, OCB, OCC, or OCD

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-19

SCCM
The SCCM parameter indicates the SONET second command code modifier
(SCCM) values specifying the administrative view of a given TL1 message.
The value ALL is meaningful only in the Retrieve Alarm message. See Table
4-24 for the SCCM parameter domains.

Table 4-24
SCCM parameter domains

SCCM domains Description

ALL All facilities and equipment

COM Common equipment and event report logs

COMFA Common equipment first occurrence

ENV Environmental

EQPT Equipment

OC48 OC-48 facility

OC192 OC-192 facility

OS Output Signal

OSC Optical Service Channel

STS1 OC-48/OC-192 facility

T1 ESI related

SID
The SID parameter indicates the NE or OPC originating the TL1 message.
Format
The SID parameter format is identical to the target identifier (TID) parameter,
and consists of either an SID name, the NE name (NEname), or the NE identity
(NEid).
• The format can be a 20-character name of ASCII text programmed for use
as the SID. The SID can consist of letters, digits, hyphens (-),
underscores (_), and periods (.).
• The format can be the 13-character NE name, if it meets TL1 requirements.
• The format can be the 5-digit NE identity (that is, the values 1 through
65534 inclusive). The system uses the NEid if the NEname is invalid.
• The SID format for the primary OPC is OPCxxxxxP, where xxxxx consists
of five letters and or digits.
• The SID format for the backup OPC is OPCxxxxxB, where xxxxx consists
of five letters and or digits.

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-20 Surveillance interface

SRVEFF
The SRVEFF parameter indicates the effect on service. Possible values are:
• service affecting (SA)
• non-service affecting (NSA)
STATE
The STATE parameter indicates the service state. The valid value is out of
service (OOS).

STBYID
The STBYID parameter indicates the name of the standby OPC (always NA).
Format
The STBYID parameter format consists of up to 20 characters of ASCII text
that meet the syntax restrictions of the AID parameter.

THLEV
The THLEV parameter provides crossed threshold values. This parameter has
the same syntax as the MONVAL parameter. See Table 4-19 for an example of
the MONVAL parameter domains.

TID
The TID parameter indicates the target of a TL1 message.
Format
The TID parameter format is identical to the source identifier (SID) parameter,
and consists of either a TID name, the NE name (NEname), or the NE identity
(NEid).
• The format can be a 20-character name of ASCII text programmed for use
as the TID. The TID can consist of letters, digits, hyphens (-),
underscores (_), and periods (.).
• The format can be the 13-character NE name, if it meets TL1 requirements.
• The format can be the 5-digit NE identity (that is, the values 1 through
65534 inclusive). The system uses the NEid if the NEname is invalid.
• The TID format for the primary OPC is OPCxxxxxP, where xxxxx consists
of five letters and or digits.
• The TID format for the backup OPC is OPCxxxxxB, where xxxxx consists
of five letters and or digits.

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-21

Time
The Time parameter indicates the translation time of the TL1 message. See
Table 4-25 for the Time parameter domains.
Format
The Time parameter format consists of three fields separated by colons. This
is the format of the Time parameter:

<hh>:<mm>:<ss>

Table 4-25
Time parameter domains

Time domains Description

hh Hour of the day [00 to 23]

mm Minute of the hour [00 to 59]

ss Seconds of the minute [00 to 59]

TIME
The TIME parameter indicates the new time to which the OPC time of day
clock changes. See Table 4-26 for the TIME parameter domains.
Format
The TIME parameter format consists of three fields separated by hyphens.
This is the format of the TIME parameter:

<hh>-<mm>-<ss>

Table 4-26
TIME parameter domains

TIME domains Description

hh Hour of the day [00 to 23]

mm Minute of the hour [00 to 59]

ss Seconds of the minute [00 to 59]

TMPER
The PM accumulation time period. The possible values are the following:
• 15-MIN
• 1-DAY

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-22 Surveillance interface

TYPEREQ
The TYPEREQ parameter indicates the required types of conditions to
retrieve. Valid types of condition types are:
• NULL (specifying all condition types)
• Specific condition types such as LOS and LOF. See Table 4-8 for a
complete list of the CONDTYPE values.
VLDTY
The PM validity measurement indicates the validity of the PM counts in a day
bin (24 hour period). If all 15-minute bins have their validity flag set to
COMPLD, then the validity flag for the day bin is set to COMPLD. If any of
the 15-minute bins has its validity flag set to PRTL, the corresponding day bin
is also set to PRTL. See Table 4-27 for the VLDTY parameter domains.

The validity flag on a 15-minute bin as well as the day bin is set to PRTL for
one of the following reasons:
• a restart occurs at a network element
• a network element detects a time change of 10 seconds or more
• PM data clears on the network element
• a time switchover occurs (for example, from daylight savings time to
standard time)
• a loss of communication between the OPC and the NE (the OPC cannot
retrieve PM counts from the network element during PM collection)
Table 4-27
VLDTY parameter domains

VLDTY domains Description

COMPL The data accumulated over the complete period is valid

PRTL The data accumulated over a portion of the time period

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-23

TL1 acknowledgment responses and error codes

This section defines acknowledgments, error responses and error codes
supported by the TL1 surveillance interface.

Acknowledgment responses
The surveillance interface uses two acknowledgment responses:
• Printout Follows
• Not Acknowledged
The Acknowledgment responses indicate that the TL1 request was received by
the OPC. You receive an Acknowledgment response before a TL1 response.
Printout Follows
A response is sent to the originator of the TL1 command within two seconds
after it receives the command. If it is not possible to send a response to the TL1
request in two seconds, then the TL1 task sends a ‘printout follows’
acknowledgment in the following format:
PF^crlf
<

The angle bracket (<) after the lf is a special character that is part of the
message.

Note: ‘PF’ returned with no other information indicates that the

association between the OPC and NEs is down.
Not Acknowledged
If the TL1 task receives a TL1 request before complete initialization it sends
the ‘NA response’. The NA response indicates it is not ready to process the
TL1 request:
NA^crlf
<

The angle bracket (<) after the lf is a special character that is part of the
message.

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-24 Surveillance interface

Error codes
The error codes that can appear in the ‘errcde’ parameter are in Table 4-28.

Table 4-28
Error codes

ERRCDE Description
parameter

ENPM Equipment not equipped with performance monitoring

ENPS Equipment not equipped with protection switching

ENRI Equipment not equipped for retrieving specified information

ENSS Equipment not equipped with synchronization switching

IDNC Input data not consistent

IDNV Input data not valid

IDRG Input data range error

IIAC Input, invalid access identifier

IICM Input, invalid command, invalid command-verb, invalid second

command code modifier, system error

IICT Input, invalid correlation tag

IIDT Input, invalid data parameter

ALMTYPE, CONDTYPE, DIRN, LOCN, MODE, MONDAT,
MONLEV, MONTM, MONTYPE, NFTCNDE, SRVEFF, TMPER

IISP Input, invalid syntax or punctuation

IITA Input, invalid target identified

INUP Input, non-null unimplemented parameter

IPNV Input parameter not valid

IPMS A required parameter is missing from the input command

ITTA Invalid target identifier

RALB Resource, all units busy

SAAL Status, already allowed

SAIN Status, already inhibited

SARB Status, all resources busy

SSRD Status, (reference or high speed optic) switch request denied

SROF Status, requested operation failed

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-25

Alarm summary
This section summarizes the message types available through the surveillance
interface and discusses message intervals.

Message types
There are two types of TL1 surveillance messages: autonomous and
non-autonomous.
Autonomous messages
The OPC generates autonomous messages as a result of activity on the network
elements, such as alarms, threshold alerts, and warnings. The OPC sends these
messages to the operations system automatically. You do not need to make a
request to receive autonomous messages. Autonomous messages have a
unidirectional data flow between the OPC and the operations system. Only the
surveillance interface generates autonomous messages. The autonomous
message types listed in Table 4-29 exist for alarms and events.

Table 4-29
Autonomous message types

Message type Purpose

REPT ALM (report alarm) Reports non-environmental alarms with severities of critical, major,
minor, and clear. All other alarms such as warnings, event logs, and PM
threshold crossings are reported with Report Event messages.

REPT ALM ENV (report alarm Reports environmental alarms. Environmental alarms include scan
environment) points, shelf temperature, 48V battery supply, and fan alarms.

REPT COND (report Reports the current standing condition or state associated with
condition) equipments or facilities once per hour. Standing conditions are alarms
of any severity. OPC event logs are not standing conditions and are
therefore not retrieved. Environmental alarms are also not retrieved.
If a network element gets added or deleted, the existing Report
Condition schedule gets cancelled and rescheduled. The new schedule
is based on the new quantity of network elements and the time of the
changes.

REPT EVT (report event) Reports event logs, alarms of severity warning or indeterminate, and
PM threshold alerts. There are two possible formats for this message;
one for alarms/alerts, and the other for event logs.

REPT PM (report Reports PM counts every 15 minutes. Only the non-zero PM counts are
performance monitoring) reported for each network element.

REPT SW (report switch) Reports that an OPC module has switched from an inactive state to an
active state. This switch message occurs in situations such as fiber
cuts, which cause the primary and backup OPCs to lose communication
with each other. This message also reports manual OPC switchover.

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-26 Surveillance interface

Non-autonomous messages
Non-autonomous messages consist of a request message from the operations
system and a response message from the OPC. These messages have a
bidirectional flow between the operations system and the OPC. For example,
the operations system message can be a user request for minor alarms on a
network element, the OPC sends a response message. The non-autonomous
message types in Table 4-30 exist for alarm and event monitoring.

Table 4-30
Non-autonomous message types

Message type Purpose

ALW-MSG (allow messages) Used to resume the transmission of autonomous messages after they
have been in the inhibit-message mode.

ALW-PMREPT (allow Used to resume autonomous reporting of performance statistics

performance monitoring through the Report Performance Monitoring message. You can control
report) the reporting of the PM counts selectively by network element or by
facility type.

ED-DAT (change OPC date Used to change OPC time, allowing an OS to keep the OPC and NE
and time) time-of-day (TOD) clocks in synchronization with the OS time-of-day
clock.

INHIBIT-MSG (inhibit Used to instruct an NE to enter a mode in which certain automatic

messages) messages associated with a specific equipment, facility, subscriber
line, trunk, link, packet link, or signaling link are prevented from being
transmitted to the operations system.

INH-PMREPT (inhibit Used to disallow autonomous reporting of performance statistics

performance monitoring through the Report Performance Monitoring message. You can control
report) the reporting of the PM counts selectively by network element or by
facility type.

INIT-REG (initialize register) Used to initialize all of the registers (also referred to as bins) that
contain current, history, or both current and history performance
monitoring (PM) counts.

OPR-EXT-CONT (operate Used to instruct the target network element to operate the specified
external controls) parallel relay output.

OPR-SYNCNSW (Operate Used to switch synchronization references when the specified

Synchronization Switch) reference is not usable. The Operate Synchronization Switch is a forced
and non-revertive switch.

RLS-EXT-CONT (release Used to instruct the target network element to release the specified
external controls) parallel relay output.

RLS-SYNCNSW (release Used to enable a synchronization reference and make it a valid

synchronization switch) candidate reference. The Release Synchronization Switch is a forced
switch and non-revertive.
—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-27

Table 4-30
Non-autonomous message types (continued)

Message type Purpose

RTRV-ALM (retrieve alarm) Used to retrieve active alarms with a higher severity than warning. The
response message provides information similar to the Report Alarm
message.

RTRV-ALM-ENV (retrieve Used to retrieve active environmental alarms. Environmental alarms

alarm environment) include scan points, shelf temperature, 48V battery supply, and fan
alarms. The response message provides information similar to the
Report Alarm Environment message.

RTRV-COND (retrieve Used to instruct a network element to return the current standing
condition) condition or state associated with one or more specified equipments or
facilities in the target network element. Standing conditions are alarms
of any severity, or threshold crossing alerts provisioned as Warning
alarms. Threshold crossing events and OPC event logs are standing
conditions and therefore not retrieved. Environmental alarms are also
not retrieved.

RTRV-HDR (retrieve header) Used to verify the identifier (name) of the network element specified in
the input message. If you do not specify the source identifier (SID) of
the active network element, you get an error message.

RTRV-PM (retrieve Used to retrieve non-zero PM counts. The response message provides
performance monitoring) information similar to the Report Performance Monitoring message.

RTRV-PMMODE (retrieve Used to retrieve the state of PM collection on the OPC.

performance monitoring)

RTRV-TH (retrieve Used to instruct the target network element to report the current
performance monitoring threshold level of one or more monitored parameters. The RTRV-TH
threshold) command does not recognize or retrieve “Untimed” intervals.

SET-PMMODE (set Used to set or change the state of PM collection on the OPC.
performance monitoring
mode)

SET-SID (set source identifier) Used to set or change the target identifier of a network element.

SET-TH (set performance Used to instruct the target network element to change
monitoring threshold) performance-monitoring (PM) parameter threshold levels. The OS
receives an autonomous message when a threshold exceeds its set
value.

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-28 Surveillance interface

Message intervals and PM considerations

This section describes:
• the reporting intervals for the REPT COND and REPT PM autonomous
messages
• how to allow and inhibit PM reports
• the RTRV-PM message
REPT COND message interval
Report condition (REPT COND) messages are reported every hour for each
network element. The message automatically reports the standing alarms of
any severity from the network elements to the operations system. Although the
interval between REPT COND messages from a network element is set to be
one hour, the actual time of the REPT COND message depends on both the
time of the TL1 connection and the quantity of network elements in the system.

If the system contains N network elements, the operations system does not
receive N REPT COND messages on the hour. Instead, the operations system
receives N REPT COND messages spread out over the hour with an interval of
60/N minutes. The REPT COND message uses the TL1 connection
establishment time as T0, the time to begin counting towards the next hour.
The REPT COND messages are not based on the actual hour (for example, 12
pm and 1 pm) intervals but on T0 + 1 hour intervals.

Note: If a network element gets added or deleted, the existing Report

Condition schedule gets cancelled and rescheduled. The new schedule is
based on the new quantity of network elements and the time of the changes.
REPT PM message interval
The PM collector initiates report performance monitoring (REPT PM)
messages. The PM collector, collects data from all network elements within
the OPC span of control every 15 minutes.

From each network element, the PM collector requests the latest 15-minute
counts for each termination class for each network element.

As soon as the PM collector receives the requested data, it stores the data in a
database on the OPC. The PM collector notifies a TL1 process that it has PM
counts for a particular termination class for a specific network element. The
non-zero counts from the 15-minute period are then retrieved from the OPC
database. The operations system then receives the non-zero counts in the form
of the REPT PM message.

The time the PM reports get sent to the operations system depends on several
factors. These factors include the quantity of network elements in the span of
control, the quantity of facilities provisioned, the quantity of non-zero counts,
and the line rate of the connection.

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-29

Allow and inhibit PM reports

You can enable or disable TL1 performance monitoring reports with the
ALW-PMREPT and INH-PMREPT messages. You can selectively control the
autonomous REPT PM messages for each network element and for each PM
parameter facility type. The status of the PM reports (allowed or inhibited) is
unique for each TL1 connection to the OPC. Refer to Performance Monitoring
Procedures, 323-1801-520, for more details.
RTRV-PM message
Use the Retrieve Performance Monitoring message to retrieve selected
historical PM counts. The PM database on the OPC stores counts for the last
eight hours in 15-minute bins (registers), and for the last seven days in daily
bins. The OPC database also stores daily counts for the current day.

The parameters you enter in the RTRV-PM command form the search criteria.
These search parameters can request one of the following:
• specific facility type (such as OC-48)
• circuit pack
• port (such as G2 port 1)
• PM parameter (such as PathCV)
• value (such as higher than 10)
• direction (Rx or Tx)
• time period (15-MIN or 1-DAY)
• date
• time
Although most parameters specified can use only a single value, date and time,
you can group parameters to retrieve several bins, which need not be
consecutive. For example, you can retrieve bins whose start times were 10:15,
11:45 and 13:30. You can also request a range of bins such as all bins between
10:15 and 11:45 inclusive.

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-30 Surveillance interface

Autonomous messages
This section describes TL1 autonomous messages and the most relevant
parameters of each autonomous message type. Refer to “Message parameters”
and Table 4-2 for a general description of all message parameters.

Refer to “Message associations” later on in this chapter for the entire suite of
network element alarm messages and their TL1 equivalents. Refer also to
Trouble Clearing and Module Replacement, 323-1801-543, for procedures to
clear these alarms.

REPT ALM (report alarm)

Purpose
The REPT ALM message is an autonomous message used to report
non-environmental alarms with severities of critical, major, minor, and clear on
the network element. Each alarm is reported in a separate REPT ALM
message. All other alarms (such as warnings), event logs, and performance
monitoring threshold crossings are reported using REPT EVT messages.
Alarm report — network element down
TL1 does not report the alarms raised on a network element (NE) if the
association to that NE is down. Alarm reporting for the NE will continue once
the association to the NE comes up again. The alarms that were raised on the
NE when the association to that NE was down will not be reported by TL1,
even after the association to the NE comes up.
Output format
The syntax of the REPT ALM message is:
crlf
lf
^^^<sid>^<date>^<time>crlf
<almcde>^<atag>^REPT^ALM^<sccm> crlf
^^^“[<aid>]:<ntfcncde>,<condtype>,<srveff>,<ocrdat>,<ocrtm>,
[<locn>],<dirn>:”\<conddescr>\””crlf
;

Parameter description
Refer to “Message parameters” and Table 4-2 for a general description of all
parameters. See Table 4-31 for a listing of all valid SCCM and AID values.

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-31

Table 4-31
Valid SCCM and AID values for the REPT ALM message

SCCM Description AID range

COM Common equipment, event report logs NULL

OC48 2.5G WT transport facility at an OPTera Long Haul 1-48G[4..19]

1600 Repeater

OC-48 TR transport facility at an OPTera Long Haul 1-48G[5,6,8,9,10,11,13,14,15,16,

1600 Combiner 18,19]

OC192 10G WT transport facility at an OPTera Long Haul 1-[D..S]

1600 Repeater

OC-192 XR transport facility at an OPTera Long Haul 1-D[E,W], 1-E[E,W], 1-F[E,W]

1600 Repeater in a regenerator capacity 1-G[E,W], 1-H[E,W], 1-I[E,W]
1-J[E,W], 1-K[E,W]

OC-192 TR transport facility at an OPTera Long Haul 1-G,1-L, 1-Q

1600 Combiner

OSC OSC facility at an OPTera Long Haul Amplifier NE 1-OTRG[0,5,10,15]-[1,2]

type

OS AMP facility at an OPTera Long Haul Amplifier NE 1-OTRG[0,5,10,15]-[1A,1B,1C,2A,2B,

type 2C]

EQPT ESI module 1-ESIG1-S7

1-ESIG2-S8

Filler card 1-FC-S[1..10]

Maintenance interface 1-MIU-S9

Message exchange 1-MXG[1-S10, 2-S11]

Shelf controller 1-SCP-S6

Orderwire 1-OWIG

MOSAIC CPG on an OPTera Long Haul Amplifier NE 1-OTRG0-S[1..5], 1-OTRG5-S[6..10]

type 1-OTRG10-S[11..15],
1-OTRG15-S[16..20]

2.5G WT transport facility at an OPTera Long Haul 1-48G[4..19]-S[5..20]

1600 Repeater

OC-48 TR transport facility at an OPTera Long Haul 1-48G[5,6,8,9]-S[6,7,9,10]

1600 Combiner 1-48G[10,11,13,14]-S[11,12,14,15]
1-48G[15,16,18,19]-S[16,17,19,20]
—continued—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-32 Surveillance interface

Table 4-31
Valid SCCM and AID values for the REPT ALM message (continued)

SCCM Description AID range

10G WT transport interface at an OPTera Long Haul 1-D-S5, 1-E-S6, 1-F-S7,

1600 Repeater 1-G-S8,1-H-S9, 1-I-S10, 1-J-S11,
1-K-S12, 1-L-S13, 1-M-S14, 1-N-S15,
1-O-S16, 1-P-S17, 1-Q-S18, 1-R-S19,
1-S-S20

OC-192 XR transport interface at an OPTera Long 1-D[E,W]-S[5,6], 1-E[E,W]-S[7,8],

Haul 1600 Repeater in a regenerator capacity 1-F[E,W]-S[9,10], 1-G[E,W]-S[11,12],
1-H[E,W]-S[13,14], 1-I[E,W]-S[15,16],
1-J[E,W]-S[17,18], 1-K[E,W]-S[19,20],

OC-192 TR transport interface at an OPTera Long 1-G-S8, 1-L-S13, 1-Q-S18

Haul 1600 Combiner

EQPT MOR 1-MORG0-S1

1-MORG1-S2
1-MORG2-S3
1-MORG3-S4

Parallel Telemetry CPG 1-PTG1-S13, 1-PTG2-S14

OPC 1-OPC, 1-OPC-S[3,5,12]

Timing Distribution Cards 1-TDCG1-S4A

1-TDCG2-S4B

T1 ESI facility 1-BITS[A,B]

Timing Reference Facilities 1-TRG[1,2]-[1,2]

ESI Reference 1-REF[1..6]

Note: AID Table 4-3 shows the relationship between the position of a circuit pack on the shelf and the
AID for the related equipment and facilities.

Example
Examples of the REPT ALM message are:
92013 96-05-10 04:23:25
A 14449 REPT ALM EQPT
"1-ESIG1-S7:CL,IMPROPRMVL,NSA,05-10,04-23-21,,NA:
\"Circuit pack missing\""
;PF

92013 96-05-10 04:25:14

* 14458 REPT ALM COM
":MN,CONTEQPT,NSA,05-10,04-25-10,,NA:
\"Autoprovisioning mismatch\""
;

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-33

REPT ALM ENV (report alarm environment)

Purpose
The REPT ALM ENV message is an autonomous message used to report
environmental alarms. Environmental alarms include scan points, shelf
temperature, 48V battery supply, and fan alarms. Each alarm is reported in a
separate REPT ALM ENV message.

Design information for the entire suite of network element environmental

alarm messages and their TL1 equivalents is unavailable. Refer to Trouble
Clearing and Module Replacement, 323-1801-543, for procedures to clear
these alarms.
Output format
The syntax of the REPT ALM ENV message is:
crlf
lf
^^^<sid>^<date>^<time>crlf
<almcde>^<atag>^REPT^ALM^ENV crlf
^^^“<aid>:<ntfcncde>,<almtype>,<ocrdat>,<ocrtm>,
“\<almmsg>\”crlf
;

Parameter description
Refer to “Message parameters” and Table 4-2 for a general description of all
parameters. See Table 4-32 for a listing of all valid SCCM and AID values.
Table 4-32
Valid SCCM and AID values for the REPT ALM ENV message

SCCM Description AID range

ENV 48V battery 1-B[A,B]

Bay 1

Breaker filter 1-BF[A,B]

Fan 1-F[1..3]

Telemetry input 1-PTG1-S[1..32], 1-PTG2-S[1..32]

Note: AID Table 4-3 shows the relationship between the position of a circuit pack on the shelf and the
AID for the related equipment and facilities.

Example
An example of the REPT ALM ENV message is:
92013 96-05-10 04:09:14
* 14412 REPT ALM ENV
"1:MN,HITEMP,05-10,04-09-10,\"High shelf temperature\""
;

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-34 Surveillance interface

REPT COND (report condition)

Purpose
The Report Condition message is an autonomous message used to report
standing alarms with any severity from the network element. The environment
alarms are not reported in this message. A REPT COND message is sent every
hour for each network element.

No action is required when receiving REPT COND messages since they are
mainly status messages: the standing alarms will have already been reported
(using the REPT ALM message).

Note: If a network element is either added or deleted the existing

REPT COND schedule is cancelled. A new schedule is established based
on the new quantity of network elements and the time the changes were
made.
Output format
The syntax of the REPT COND message is:
crlf
lf
^^^<sid>^<date>^<time>crlf
A^^<atag>^REPT^COND^<sccm>crlf
[^^^“[<aid>]:<ntfcncde>,<condtype>,<srveff>,<ocrdat>,<ocrtm>,
[<locn>],<dirn>”]crlf
;

Parameter description
Refer to “Message parameters” and Table 4-2 for a general description of all
parameters. See 4-33 for a listing of all valid SCCM and AID values.

Table 4-33
Valid SCCM and AID values for the REPT COND message

SCCM Description AID range

COM Common equipment, event report logs NULL

OC48 2.5G WT transport facility at an OPTera Long Haul 1-48G[4..19]

1600 Repeater

OC-48 TR transport facility at an OPTera Long Haul 1-48G[5,6,8,9,10,11,13,14,15,16,18,

1600 Combiner. 19]

OC192 10G WT transport facility at an OPTera Long Haul 1-[D..S]

1600 Repeater

OC-192 XR transport facility at an OPTera Long Haul 1-D[E,W], 1-E[E,W], 1-F[E,W]

1600 Repeater in a regenerator capacity 1-G[E,W], 1-H[E,W], 1-I[E,W]
1-J[E,W], 1-K[E,W]
—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-35

Table 4-33
Valid SCCM and AID values for the REPT COND message (continued)

SCCM Description AID range

OC192 OC-192 TR transport facility at an OPTera Long Haul 1-G,1-L, 1-Q

1600 Combiner

OSC OSC facility at an OPTera Long Haul Amplifier NE type 1-OTRG[0,5,10,15]-[1,2]

OS AMP facility at an OPTera Long Haul Amplifier NE type 1-OTRG[0,5,10,15]-[1A,1B,1C,2A,

2B,2C]

T1 ESI Facility 1-BITS[A, B]

ESI Reference 1-REF[1..6]
Timing Reference Facilities 1-TRG[1,2]-[1,2]
EQPT 2.5G WT transport facility at an OPTera Long Haul 1-48G[4..19]-S[5..20]
1600 Repeater

OC-48 TR transport facility at an OPTera Long Haul 1-48G[5,6,8,9]-S[6,7,9,10]

1600 Combiner 1-48G[10,11,13,14]-S[11,12,14,15]
1-48G[15,16,18,19]-S[16,17,19,20]

10G WT transport interface at an OPTera Long Haul 1-D-S5, 1-E-S6, 1-F-S7,

1600 Repeater 1-G-S8,1-H-S9, 1-I-S10, 1-J-S11,
1-K-S12, 1-L-S13, 1-M-S14,
1-N-S15, 1-O-S16, 1-P-S17,
1-Q-S18, 1-R-S19, 1-S-S20

OC-192 XR transport interface at an OPTera Long 1-D[E,W]-S[5,6]

Haul 1600 Repeater in a regenerator capacity 1-E[E,W]-S[7,8]
1-F[E,W]-S[9,10]
1-G[E,W]-S[11,12]
1-H[E,W]-S[13,14]
1-I[E,W]-S[15,16]
1-J[E,W]-S[17,18]
1-K[E,W]-S[19,20]

OC-192 TR transport interface at an OPTera Long 1-G-S8, 1-L-S13, 1-Q-S18

Haul 1600 Combiner

OPC 1-OPC, 1-OPC-S[3,5,12]

Timing Distribution Cards 1-TDCG1-S4A
1-TDCG2-S4B

Shelf controller 1-SCP-S6

Parallel Telemetry CPG 1-PTG1-S13
1-PTG2-S14
—continued—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-36 Surveillance interface

Table 4-33
Valid SCCM and AID values for the REPT COND message (continued)

SCCM Description AID range

EQPT ESI Module 1-ESIG1-S7

1-ESIG2-S8

Orderwire 1-OWIG
MOSAIC CPG on an OPTera Long Haul Amplifier NE 1-OTRG0-S[1..5], 1-OTRG5-S[6..10]
type 1-OTRG10-S[11..15],
1-OTRG15-S[16..20]

Maintenance interface 1-MIU-S9

Message Exchange 1-MXG[1-S10, 2-S11]
Filler Card 1-FC-S[1..10]
Note: AID Table 4-3 shows the relationship between the position of a circuit pack on the shelf and the
AID for the related equipment and facilities.

Example
An example of the REPT COND message is:
92013 96-05-10 04:27:41
A 14474 REPT COND OC192
"1:MN,T-AISSP,NSA,05-10,03-45-02,NEND,NA"
;

REPT EVT (report event)

Purpose
The REPT EVT message is an autonomous message used to report event logs
and alarms of warning or indeterminate severity, and performance monitoring
threshold alerts from the network element. Each event is reported in a separate
REPT EVT message. There are two possible formats for this message: one for
alarms/alerts and the other for event logs.

Note 1: Descriptions of event logs can be found in Log Reference,

323-1801-840.
Note 2: Event logs reported through TL1 are the same as the logs that can
be viewed through the OPC Event Browser tool.
Alarm reporting — network element down
TL1 does not report the alarms or events raised on a network element if the
association to that NE is down. Alarm or event reporting for the NE will
continue once the association to the NE comes up again. However, the alarms
or events that were raised on the NE when the association to that NE was down
will not be reported by TL1, even after the association to the NE comes up.

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-37

Output format
The syntax of the REPT EVT alarm/alert message is:
crlf
lf
^^^<sid>^<date>^<time>crlf
A^^<atag>^REPT^EVT^<sccm>crlf
^^^”[<aid>]:<condtype>,<condeff>,<ocrdat>,<ocrtm>,[<locn>],
<dirn>,[<monval>],[<thlev>][,<tmper>]:”\<almmsg>\””crlf
;

The syntax of the REPT EVT log message is:

crlf
lf
^^^<sid>^<date>^<time>crlf
A^^<atag>^REPT^EVT^<sccm> crlf
^^^“:<condtype>,,<ocrdat>,<ocrtm>:“\<conddescr>\””crlf
;

Parameter description
Refer to “Message parameters” and Table 4-2 for a general description of all
parameters. See Table 4-34 for specific parameter details and Table 4-35 for a
listing of all valid SCCM and AID values.

Table 4-34
Specific parameter details

Parameter Details

almmsg For REPT EVT alarm/alert messages, the alarm message value is the first 40
characters of the alarm text as seen on the NE alarm screen.

condtype For REPT EVT log messages, the condition type value is always MISC.

conddescr For REPT EVT log messages, the condition description value is the first 64
characters of the log text as seen in the OPC Event Browser.

Example
An example of the REPT EVT alarm/alert message (warning/indeterminate)
is:
92013 96-05-10 04:28:56
A 14480 REPT EVT EQPT
"1-ESIG1:SYNCCLKA,SC,05-10,04-28-52,,NA,0,0,15-MIN:
\"Timing generation entry to acquire\""
;

An example of the REPT EVT log message is:

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-38 Surveillance interface

Table 4-35
Valid SCCM and AID values for the REPT EVT message

SCCM Description AID range

COM Common equipment, event report logs NULL

OC48 2.5G WT transport facility at an OPTera Long Haul 1-48G[4..19]

1600 Repeater

OC-48 TR transport facility at an OPTera Long Haul 1-48G[5,6,8,9,10,11,13,14,15,16,

1600 Combiner 18,19]

OC192 10G WT transport facility at an OPTera Long Haul 1-[D..S]

1600 Repeater

OC-192 XR transport facility at an OPTera Long 1-D[E,W], 1-E[E,W], 1-F[E,W]

Haul 1600 Repeater in a regenerator capacity 1-G[E,W], 1-H[E,W], 1-I[E,W]
1-J[E,W], 1-K[E,W]

OC-192 TR transport facility at an OPTera Long 1-G,1-L, 1-Q

Haul 1600 Combiner

EQPT ESI module 1-ESIG1-S7

1-ESIG2-S8

EQPT Maintenance interface 1-MIU-S9

Message exchange 1-MXG[1-S10, 2-S11]

2.5G WT transport facility at an OPTera Long Haul 1-48G[4..19]-S[5..20]

1600 Repeater

OC-48 TR transport facility at an OPTera Long Haul 1-48G[5,6,8,9]-S[6,7,9,10]

1600 Combiner 1-48G[10,11,13,14]-S[11,12,14,15]
1-48G[15,16,18,19]-S[16,17,19,20]

10G WT transport interface at an OPTera Long Haul 1-D-S5, 1-E-S6, 1-F-S7,

1600 Repeater 1-G-S8,1-H-S9, 1-I-S10, 1-J-S11,
1-K-S12, 1-L-S13, 1-M-S14, 1-N-S15,
1-O-S16, 1-P-S17, 1-Q-S18, 1-R-S19,
1-S-S20

OC-192 XR transport interface at an OPTera Long 1-D[E,W]-S[5,6]

Haul 1600 Repeater in a regenerator capacity 1-E[E,W]-S[7,8]
1-F[E,W]-S[9,10]
1-G[E,W]-S[11,12]
1-H[E,W]-S[13,14]
1-I[E,W]-S[15,16]
1-J[E,W]-S[17,18]
1-K[E,W]-S[19,20]

OC-192 TR transport interface at an OPTera Long 1-G-S8, 1-L-S13, 1-Q-S18

Haul 1600 Combiner
—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-39

Table 4-35
Valid SCCM and AID values for the REPT EVT message (continued)

SCCM Description AID range

OPC 1-OPC, 1-OPC-S[3,5,12]

Orderwire 1-OWIG

Shelf controller 1-SCP-S6

Parallel Telemetry CPG 1-PTG1-S13, 1-PTG2-S14

Timing Distribution Cards 1-TDCG1-S4A

1-TDCG2-S4B

T1 ESI Facility 1-BITS[A, B]

ESI reference 1-REF[1..6]

Timing reference facilities 1-TRG[1,2]-[1,2]

Note: AID Table 4-3 shows the relationship between the position of a circuit pack on the shelf and the
AID for the related equipment and facilities.

92013 96-05-10 05:25:35

A 14696 REPT EVT COM
":MISC,,05-10,05-25-35:\"GEN618 Log/Alarm database updated
for NE 9213.\""
;

REPT PM (report performance monitoring)

Purpose
The REPT PM message is an autonomous message used to report PM counts
starting every 15, 30, 45, and 60 minutes past the hour. Only the non-zero PM
counts are reported. A REPT PM message is sent for each network element.
See the performance monitoring tables 4-98, 4-99, 4-112, and 4-113 for the
performance monitoring measurements and the TL1 equivalent messages.
Output format
The syntax of the REPT PM message is:
crlf
lf
^^^<sid>^<date>^<time>crlf
A^^<atag>^REPT^PM^<sccm>crlf
[^^^“<aid>:<montype>,<monval>,<vldty>,<locn>,<dirn>,<tmper>,
<mondat>,<montm>”crlf]
;

Example
An example of the REPT PM message is:

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-40 Surveillance interface

NE1 93-04-14 11:40:08

A 37185 REPT PM OC12
"1-12G1:CVP,4469,COMPL,NEND,ZA,15-MIN,05-18,13-00”
“1-12G1:CVP,2262,COMPL,NEND,AZ,15-MIN,05-18,13-00”
;

Parameter description
Refer to “Message parameters” and Table 4-2 for a general description of all
parameters. See Tables 4-36, 4-37, 4-38, 4-39, and 4-40 for the range of values
for the various parameters.

Table 4-36
Range of values for REPT PM, ALW-PMREPT, INH-PMREPT, RTRV-PM, and RTRV-TH messages

Field Valid values for OPTera Long Haul 1600

SCCM refer to Table 4-33

AID <frame>-<cpgname>-[<port>]
port is only applicable to STS1 path
refer to Table 4-37

DIRN refer to Table 4-38 (default is ZA)

MONTYPE refer to Table 4-38 (default is all)

LOCN NEND (default is NEND)

TMPER refer to Table 4-39 (default is 15-min)

MONDAT refer to Table 4-39 (default is current date)

MONTM refer to Table 4-39 (default is start of the Last 15-min bin which has been collected by OPC)

MONLEV refer to Table 4-40

MONVAL refer to Table 4-40

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-41

Table 4-37
AID values for REPT PM, ALW-PMREPT, INH-PMREPT, RTRV-PM and RTRV-TH messages

SCCM Description frame cpgname port/

payload

ALL ALL — — —

OC48 2.5G WT transport facility at an OPTera Long Haul 1 48G[4..19] —

1600 Repeater

OC-48 TR transport facility at an OPTera Long 1 48G[5,6,8,9,10,11, __

Haul 1600 Combiner 13,14,15,16,18,19]

OC192 10G WT transport interface at an OPTera Long 1 [D..S] —

Haul 1600 Repeater

OC-192 XR transport interface at an OPTera Long 1 D[E,W], E[E,W], —

Haul 1600 Repeater in a regenerator capacity F[E,W], G[E,W],
H[E,W], I[E,W]
J[E,W], K[E,W]

OC-192 TR transport interface at an OPTera Long 1 G —

Haul 1600 Combiner L
Q

STS1 OC-48 tributary facility at an OPTera Long Haul 1 48G[4..19] [1...48]

1600 terminal

STS1 intermediate path PM’s on OC-192 transport 1 192G [D..S] [1...192]

at an OPTera Long Haul 1600 terminal

EQPT 2.5G WT transport facility at an OPTera Long Haul 1 48G[4..19] —

1600 Repeater

OC-48 TR transport facility at an OPTera Long 1 48G[5,6,8,9] __

Haul 1600 Combiner 48G[10,11,13,14]
48G[15,16,18,19]

10G WT transport interface at an OPTera Long 1 D..S —

Haul 1600 Repeater

OC-192 XR transport interface at an OPTera Long 1 D[E,W], E[E,W], —

Haul 1600 Repeater in a regenerator capacity F[E,W], G[E,W],
H[E,W], I[E,W],
J[E,W], K[E,W]

OC-192 TR transport interface at an OPTera Long 1 G __

Haul 1600 Combiner L
Q

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-42 Surveillance interface

Table 4-38
MONTYPE values for REPT PM, ALM-PMREPT, INH-PMREPT, RTRV-PM and RTRV-TH messages

MONTYPE MONTYPE
Description SCCM (DIRN=ZA) (DIRN=AZ)

2.5G WT, OC-48 TR line OC48 CVL, ESL, SESL, UASL, —

facility FCL, FECL

2.5G WT, OC-48 TR OC48 CVS, ESS, SESS, —

section facility SEFSS

10G WT, OC-192 TR OC192 CVL, ESL, SESL, UASL, —

line facility FCL, FECL

10G WT, OC-192 TR OC192 CVS, ESS, SESS, —

section facility SEFSS

OC-192 XR section OC192 CVS, ESS, SESS, —

facility SEFSS

STS-1 path facility OC48, OC192 CVP, ESP, SESP, —

UASP, FCL

All facilities ALL — —

Equipment protection EQPT (OC-48, OC-192) (DIR = NA) —

switching counts and PSC, PSD, LBC, LPT,
physical parameters LPR,
OPR (only for OC-192)

Table 4-39
MONDAT, MONTM, AND TMPER values for REPT PM and RTVR-PM messages

Requirement TMPER MONDAT value MONTM value

One specific daily 1-DAY MM_DD ignored

count Note: current date - MM-DD ≤7

Several discrete 1-DAY MM1-DD1&MM2-DD2...&MMn-DDn ignored

daily counts Note 1: MM1-DD1<MM2-DD2<MMn-DDn
Note 2: MMn-DDn - MMn-MM1-DD1 ≤7

Range of daily 1-DAY MM1-DD1&&MM2-DD2 ignored

counts Note 1: MM1-DD1<MM2-DD2
Note 2: MM2-DD - MMJ1-DD1 ≤7

All daily counts 1-DAY ALL must be null

One specific 15-min current day’s or yesterday’s date, HR-MIN

15-minute count corresponding to the time (MONTM) is set MIN = 00, 15, 30, or 45
Note: current hour - HR ≤8

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-43

Table 4-39 (continued)

MONDAT, MONTM, AND TMPER values for REPT PM and RTVR-PM messages

Requirement TMPER MONDAT value MONTM value

Several 15-min current day’s or yesterday’s date HR1-MIN1&HR2MIN2..HRn-

15-minute counts corresponding HR1-MIN1 in MONTM list MINn
(the first value in the grouped parameter MIN = 00, 15, 30 or 45
list) Note: current time - (either
HR1 - MIN1 or
HRn-MINn ≤ 7-45)

Range of 15-min current day’s or yesterday’s date HR1-MIN1&&HR2-MIN2

15-minute counts corresponding to HR1-MIN1 in MONTM list MIN = 00, 15, 30 && 45
(the start of range) Note: current time - (either
HR1-MIN1 or HR2-MIN2)

All 15-minute 15-min must be null all

counts

Table 4-40
MONLEV and MONVAL values for REPT PM and RTRV-PM messages

Parameter Details

MONLEV The PM level has format LEVEL-DIRECTION where LEVEL is a decimal number
and DIRECTION is UP or DOWN. The PM counts must be greater than or equal
to LEVEL (for up) and less than or equal to LEVEL (for down) before they are
reported. A null value defaults to 1-UP.

MONVAL This is the actual PM count value for the specified time frame sent in response.

REPT SW (report switch)

Purpose
The REPT SW message is an autonomous message used to indicate that an
OPC module has switched from an inactive state to an active state. This switch
message occurs in situations such as fiber cuts and manual OPC switchover.

Note: REPT SW messages are not reported to a TL1 interface accessed

through the OPC UNIX shell tool.
Output format
The syntax of the REPT SW message is:
crlf
lf
^^^<sid>^<date>^<time>crlf
A^^<atag>^REPT^SW crlf
^^^“<actid>,[<stbyid>]”crlf
;

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-44 Surveillance interface

Parameter description
Refer to “Message parameters” and Table 4-2 for a general description of all
parameters.The parameters listed in Table 4-41 have restricted values.

Table 4-41
Specific parameter details

Parameter Details

actid The active OPC value is the name of the active OPC as defined during
system commissioning.

stbyid The standby OPC value is always NA given that the active OPC does
not know the status of the inactive OPC.

Example
An example of the REPT SW message is:
92013 96-05-10 05:25:48
A 14696 REPT SW
“OPCM001P,NA”
;

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-45

Non-autonomous messages
TL1 non-autonomous messages are described in this section. Refer to
“Message parameters” and Table 4-2 for a general description of all message
parameters. See Table 4-28 for a listing of all error codes.

ALW-MSG (allow messages)

The ALW-MSG is a non-autonomous message which you use to enable
autonomous reporting of alarms after having been in the INHIBIT-MESSAGE
mode. Automatic messages resume toward any operations system designated
to receive these messages. Unreported alarms in existence at the time of
restoration are transmitted to the operations system with the report alarm
message (REPT ALM) or the report alarm environment message
(REPT ALM ENV).

Note: You must open an administrative session before you use this
message.
Input format
The syntax of the ALW-MSG input message is:
alw-msg-all:<tid>::<ctag>:[<ntfcncde>];crlf

Normal response output format

The syntax of the ALW-MSG normal response output message is:
crlf
lf
^^^<sid>^<date>^<time>crlf
M^^<ctag>^COMPLD crlf
;

Parameter description
Refer to “Message parameters” and Table 4-2 for a general description of all
parameters. See Table 4-42 for specific parameter details.

See Table 4-28 for a listing of all error codes.

Table 4-42
Specific parameter details

Parameter Details

ntfcncde This indicates the severity of the alarm:

CR-Critical alarm- Allow the alarms with severity Critical
MJ-Major alarm- Allow the alarms with severity Major
MN-Minor alarm- Allow the alarms with severity Minor
CL-Clear alarm- Allow the alarms with severity Clear
NA- Not Alarmed- Inhibits alarms raised through Rept Event
messages

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-46 Surveillance interface

Example
An example ALW-MSG normal response output message is:
alw-msg-all:NE1::ctag01;

NE1 98-11-21 23:19:54

M ctag01 COMPLD
;

ALW-PMREPT (allow performance monitoring report)

Purpose
The ALW-PMREPT message is a non-autonomous message used to enable
autonomous reporting of facility performance monitoring counts through the
REPT PM message. Performance monitoring reporting can be selectively
enabled for each network element and for each facility type. To allow PM
reports on a specific NE, include the TID parameter in the ALW-PMREPT
message. The default status is to allow all PM reporting using the REPT PM
message. See the performance monitoring tables 4-98, 4-99, 4-112, and 4-113
for the correlation of performance monitoring measurements and the TL1
equivalent messages.

Note: Performance monitoring reporting status is not data synchronized

from the primary OPC to the backup OPC.
Input format
The syntax of the ALW-PMREPT input message is:
ALW-PMREPT-<sccm>:<tid>::<ctag>;crlf

Normal response output format

The syntax of the ALW-PMREPT normal response output message is:
crlf
lf
^^^<sid>^<date>^<time>crlf
M^^<ctag>^COMPLD crlf
;

Error response output format

The syntax of the ALW-PMREPT error response output message is:
crlf
lf
^^^<sid>^<date>^<time>crlf
M^^<ctag>^DENYcrlf
^^^<errcde>crlf
[^^^/*error text*/crlf]
;

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-47

Parameter description
Refer to “Message parameters” and Table 4-2 for a general description of all
parameters. See Tables 4-36, 4-37, and 4-38 for the range of values for the
various parameters.

See Table 4-28 for a listing of all error codes.

Examples
An example ALW-PMREPT normal response output message is:
ALW-PMREPT-STS1:ne1::1102;

NE1 92-09-23 15:10:23

M 1102 COMPLD
;

An example ALW-PMREPT error response output message is:

alw-pmrept-T3:West_Ch3::1235;

WEST_CH3 92-08-13 15:46:15

M 1235 DENY
SAAL
/*Status, Already ALlowed.*/
;

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-48 Surveillance interface

ED-DAT (change OPC date and time)

Purpose
The ED-DAT command allows the time on the OPC to be changed by a
surveillance operations system through the TL1 interface. This command
allows an operations system to keep the OPC and network element
Time-of-Day (TOD) clocks in synchronization with the operations system
Time-of-Day clock.

The ED-DAT command should be used with caution and only when absolutely
necessary. Changing the time affects other applications whose activities and
operations depend on the OPC time. To limit any side effects of changing the
OPC time, the change does not occur immediately after it has been requested.
Instead, the OPC time drifts gradually (at a rate of about 4% for each hour)
until the difference between the OPC Time-of-Day clock and the requested
time has been reduced to zero. A full 30-minute adjustment can take almost 12
hours to complete.

All network elements in the OPC span of control automatically and

periodically synchronize their time to that of the OPC. Network elements pick
up the time change according to their synchronization schedule.

When the command is successful, an event log is generated in the Event

Browser.

Note 1: When the TID parameter is used in the ED-DAT command, the
message is sent to the specified network element in the OPC span of
control. When the TID parameter is null, the ED-DAT command is sent to
the OPC.
Note 2: When the ED-DAT command is sent to any network element in an
OPC span of control or to the OPC, the time of day changes only on the
active OPC. The inactive OPC time cannot be changed.
Note 3: The time cannot be changed more than 30 minutes from the
current time.
Note 4: While there is a time change request in progress, no additional
time change requests are accepted.
Note 5: If the primary OPC is synchronized to a 1 Hz clock source, it is
not possible to change the OPC time. An attempt to change the OPC time
in this instance results in an error response.

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-49

Input format
The syntax of the ED-DAT input message is:
ED-DAT:<tid>::<ctag>::[DATE][,TIME];crlf

Normal response output format

The syntax of the ED-DAT normal response output message is:
crlf
lf
^^^<sid>^<date>^<time>crlf
M^^<ctag>^COMPLD crlf
;

Error response output format

The syntax of the ED-DAT error response output message is:
crlf
lf
^^^<sid>^<date>^<time>crlf
M^^<ctag>^DENY crlf
^^^<errcde>crlf
[^^^/*error_text*/crlf]*
;

Parameter description
Refer to “Message parameters”and Table 4-2 for a general description of all
parameters. The parameters listed in Table 4-43 have restricted values.

See Table 4-28 for a listing of all error codes.

Table 4-43
Specific parameter details

Parameter Details

DATE This is the date to which the OPC is to be changed in the form
YY-MM-DD. The year can range from 00 to 99, the month from
00 to 12, and the day from 00 to 31.

TIME This is the time to which the OPC is to be changed in the form
HH-MM-SS. The time is in 24 hour format. The hours can range
from 00 to 23, the minutes from 00 to 59, and the seconds from
00 to 59.

Note: DATE and TIME are optional parameters. If you do not specify the DATE
parameter, the system uses the current date value. If you do not specify the time
parameter, the system uses the current time. When the time change falls into the
next day, you should specify the value of the DATE parameter.

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-50 Surveillance interface

Examples
An example of the ED-DAT normal output response is:
ED-DAT:NE_TID::CTAG12::05-22,09-45;

NE_TID 96-05-22 09:49:19

M CTAG12 COMPLD
;

An example of the ED-DAT error output response is:

ED-DAT:NE_TID::CTAG13::96-05-22,09-45;

NE_TID 96-05-22 09:49:44

M CTAG13 DENY
IICM
/* The Requested Operation Already in Progress*/
;

Note: In this example the ED-DAT command response is “DENY”

because a previously sent ED-DAT command is in progress.

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-51

INHIBIT-MSG (inhibit messages)

Purpose
The INHIBIT-MSG message is a non-autonomous message which disables the
autonomous reporting of alarms through REPT ALM and REPT EVT
messages. You can selectively disable alarms and event reports for each
network element or OPC (using the tid parameter) and for each severity using
the notification code (nftcncde) parameter. This command does not have any
effect on indicators in the office where the NE resides or on the NE itself.
During the entire period of message inhibition, the NE responds to the
RETREIVE-ALARM and RETREIVE-CONDITION requests with a message
INHMSG-<condtype> for alarms which have not been reported to the
operation system. The condition is restored to normal with the ALLOW
MESSAGE command or by the automatic timeout duration (30 minutes).

Note 1: You must open an administrative session before you use this
command.
Note 2: The timeout is 30 minutes from the last Inhibit command with a
different notification code.
Note 3: Inhibited alarms are reported with an INHMSG prefix in response
to report alarm messages (RTRV-ALM) and retrieve condition
(RTRV-COND) messages.
Input format
The syntax of the INH-MSG input message is:
inh-msg-all:<tid>::<ctag>:[<ntfcncde>];crlf

Normal response output format

The syntax of the INH-MSG normal response output message is:
crlf
lf
^^^<sid>^<date>^<time>crlf
M^^<ctag>^COMPLDcrlf
;

Parameter description
Refer to “Message parameters” and Table 4-2 for a general description of all
parameters. See Table 4-44 for specific parameter details.

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-52 Surveillance interface

See Table 4-28 for a listing of all error codes.

Table 4-44
Specific parameter details

Parameter Details

ntfcncde This indicates the severity of the alarm:

CR-Critical alarm- inhibit the alarms with severity Critical
MJ-Major alarm- inhibit the alarms with severity Major
MN-Minor alarm- inhibit the alarms with severity Minor
CL-Clear alarm- inhibit the alarms with severity Clear
NA- Not Alarmed- inhibits alarms raised through Rept Event
messages

Example
An example INH-MSG normal response output message is:
inh-msg-all:NE1::ctag01;

NE1 98-11-21 23:24:41

M ctag01 COMPLD
;

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-53

INH-PMREPT (inhibit performance monitoring report)

Purpose
The INH-PMREPT message is a non-autonomous message used to disable
autonomous reporting of facility performance monitoring counts through the
REPT PM message. Performance monitoring reporting can be selectively
disabled for each network element (using the TID parameter) and for each
facility type. The default status is to allow all PM reporting using the
REPT PM message. Refer to performance monitoring tables 4-98, 4-99,
4-112, and 4-113 for the correlation of performance monitoring measurements
and the TL1 equivalent messages.

Note: Performance monitoring status is not data synchronized from the

primary OPC to the backup OPC.
Input format
The syntax of the INH-PMREPT input message is:
INH-PMREPT-<sccm>:<tid>::<ctag>;crlf

Normal response output format

The syntax of the INH-PMREPT normal response output message is:
crlf
lf
^^^<sid>^<date>^<time>crlf
M^^<ctag>^COMPLDcrlf
;

Error response output format

The syntax of the INH-PMREPT error response output message is:
crlf
lf
^^^<sid>^<date>^<time>crlf
M^^<ctag>^DENY crlf
^^^<errcde>crlf
[^^^/*error text*/crlf]
;

Parameter description
Refer to “Message parameters” and Table 4-2 for a general description of all
parameters. See Tables 4-36, 4-37, and 4-38 for the range of values for the
various parameters.

See Table 4-28 for a listing of all error codes.

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-54 Surveillance interface

Examples
An example INH-PMREPT normal response output message is:
INH-PMREPT-ALL:NE1::102;

NE1 92-08-23 15:10:23

M 102 COMPLD
;

An example INH-PMREPT error response output message is:

INH-PMREPT-ALL:EAST_Ch3::123;

EAST_CH3 92-08-13 15:46:15

M 123 DENY
SAIN
/*Status, Already INhibited.*/
;

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-55

INIT-REG (initialize register)

Purpose
The INIT-REG command allows a surveillance operations system to instruct
the target network element to initialize all of the registers (also referred to as
bins) containing current, history, or both current and history performance
monitoring (PM) counts.
Input format
The syntax of the INIT-REG input message is:
INIT-REG-<sccm>:<tid>:<aid>:<ctag>::,,,,[<tmper>];crlf

Include the commas before the optional TMPER parameter as this is a

positional parameter block. The commas are place holders for parameters not
required in this command.
Normal response output format
The syntax of the INIT-REG normal response output message is:
crlf
lf
^^^<sid>^<date>^<time>crlf
M^^<ctag>^COMPLD crlf
;

Error response output format

The syntax of the INIT-REG error response output message is:
crlf
lf
^^^<sid>^<date>^<time>crlf
M^^<ctag>^DENYcrlf
^^^<errcde>crlf
^^^/*<error description>*/crlf
;

Parameters
Refer to “Message parameters” and Table 4-2 for a general description of all
parameters. See Table 4-45 for a description of specific parameter details. See
Table 4-46 for a listing of all valid AID values.

See Table 4-28 for a listing of all error codes.

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-56 Surveillance interface

Table 4-45
Specific parameter details

Parameter Details

tmper The valid values of the time period register or bin to be reset are HIS (history), CNT
(current), and BTH (both history and current).
CNT resets the current 15-minute and current day bins on the network element to zero
for all PM types for the specified AID.
HIS resets all history 15-minute and day bins to zero.
BTH resets all bins, current as well as history, to zero.
A null value is taken to mean BTH.

Table 4-46
SCCM and AID values for the INIT-REG command

SCCM Description AID

COM Common equipment, event report logs NULL

OC48 2.5G WT transport facility at an OPTera Long Haul 1-48G[4..19]

1600 Repeater

OC-48 TR transport facility at an OPTera Long Haul 1-48G[5,6,8,9,10,11,13,14,15,16,1

1600 Combiner 8,19]

OC192 10G WT transport facility at an OPTera Long Haul 1-[D..S]

1600 Repeater

OC-192 XR transport facility at an OPTera Long Haul 1-D[E,W], 1-E[E,W], 1-F[E,W]

1600 Repeater in a regenerator capacity 1-G[E,W], 1-H[E,W], 1-I[E,W]
1-J[E,W], 1-K[E,W]

OC-192 TR transport facility at an OPTera Long Haul 1-G,1-L, 1-Q

1600 Combiner

OC-48 TR transport facility at an OPTera Long Haul 1-48G[5,6,8,9]-S[6,7,9,10]

1600 Combiner 1-48G[10,11,13,14]-S[11,12,14,15]
1-48G[15,16,18,19]-S[16,17,19,20]

OC-192 TR transport interface at an OPTera Long 1-G-S8, 1-L-S13, 1-Q-S18

Haul 1600 Combiner

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-57

Examples
An example of the INIT-REG normal response output message to zero all
15-minute PM counts for OPTera Long Haul 1600 [NE1] channel G2) is:
INIT-REG-OPTera LH:NE1:1-B:STEVE1::,,,,BTH;

NE1 93-08-13 15:23:27

M STEVE1 COMPLD
;

An example of the INIT-REG error response output message is:

INIT-REG-OPTera LH:NE1:1-F:STEVE1::,,,,BTH;

NE1 93-08-13 15:23:27

M STEVE1 DENY
SROF
/*Facility specified does not exist.*/
;

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-58 Surveillance interface

OPR-EXT-CONT (operate external controls)

Purpose
The OPR-EXT-CONT command allows a surveillance operations system to
instruct the target network element to operate the parallel relay outputs on the
network element. See RLS-EXT-CONT for the surveillance operations system
command to release the parallel relay outputs.

The relay contact to operate is determined by the AID value in the command.
Since only one relay contact is implied by a given AID, the contact type
(parameter CONTTYPE) is not supported. The default value of the DUR
parameter is conts.
Input format
The syntax of the OPR-EXT-CONT message is:
OPR-EXT-CONT:<tid>:<aid>:<ctag>::[,<dur>];crlf

Include the comma before the optional DUR parameter as this is a positional
parameter block. The comma is a place holder for a parameter (conttype) not
required in this command.
Normal response output format
The syntax of the OPR-EXT-CONT normal response output message is:
crlf
lf
^^^<sid>^<date>^<time>crlf
M^^<ctag>^COMPLDcrlf
;

Error response output format

The syntax of the OPR-EXT-CONT error response output message is:
crlf
lf
^^^<sid>^<date>^<time>crlf
M^^<ctag>^DENYcrlf
^^^<errcde>crlf
[^^^/*error_text*/crlf]*
;

Parameter description
Refer to “Message parameters” and Table 4-2 for a general description of all
parameters. See Table 4-47 for a listing of all valid AID and DUR values.

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-59

See Table 4-28 for a listing of all error codes.

Table 4-47
Valid AID and DUR values for OPR-EXT-CONT messages

Field Valid values

AID 1-PTG2-X[1..8], 1-PTG3-X[1..8]

DUR CONTS (continue)

MNTRY (momentary)
If no value is specified, the default is CONTS.

Example
An example of the OPR-EXT-CONT normal response is:
OPR-EXT-CONT:9214:1-ptg2-X2:jps6::,CONTS;

9214 05-07-08 10:10:22

M JPS6 COMPLD
;

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-60 Surveillance interface

OPR-SYNCNSW (Operate Synchronization Switch)

Purpose
The OPR-SYNCNSW command makes the specified timing reference invalid.
If you specify an active reference in the command, an alternate reference
becomes the active reference. The OPR-SYNCNSW command uses the ESI
forced switch mode. You can configure up to six references. The ESI selects
the best time reference when a switch is necessary.
Input format
The syntax of the OPR-SYNCNSW input message is:
OPR-SYNCNSW:<tid>::<ctag>::<ref>;crlf

Normal response output format

The syntax of the OPR-SYNCNSW normal response output message is:
crlf
lf
^^^<sid>^<date>^<time>crlf
M^^<ctag>^COMPLDcrlf
;

Error response output format

The syntax of the OPR-SYNCNSW error response output message is:
crlf
lf
^^^<sid>^<date>^<time>crlf
M^^<ctag>^DENYcrlf
^^^<errcde>crlf
^^^/*error text*/crlf
;

Parameter description
Refer to “Message parameters” and Table 4-2 for a general description of the
ref parameter. The ref parameter listed in Table 4-48 has restricted values.

See Table 4-28 for a listing of all error codes.

Table 4-48
Specific parameter details

Parameter Details

ref The value of the time reference number is an integer. Up to six

references (1, 2, 3, 4, 5, and 6) can be configured. The integers
correspond to BITSA, BITSB, OC192G1, OC192G2, OC192G3, and
OC192G4. The configuration can be any combination of the six.

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-61

Example
An example of the OPR-SYNCNSW normal response output message is:
OPR-SYNCNSW:WEST_CH1::123::1;

WEST_CH1 97-04-24 19:35:54

M 123 COMPLD
;

An example of the OPR-SYNCNSW error response output message is:

OPR-SYNCNSW:West_Ch1::1234::1;

WEST_CH1 97-04-24 20:59:17

M 1234 DENY
ENSS
/*Equipage, Not Equipped with Synchronization Switching*/
;

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-62 Surveillance interface

RLS-EXT-CONT (release external controls)

Purpose
The RLS-EXT-CONT command allows a surveillance operations system to
instruct the target network element to release the parallel relay outputs on the
network element. See OPR-EXT-CONT for the surveillance operations system
command to operate the parallel relay outputs.

The relay contact to operate is determined by the AID value in the command.
Since only one relay contact is implied by a given AID, the contact type
(parameter CONTTYPE) is not supported. The default value of the DUR
parameter is conts.
Input format
The syntax of the RLS-EXT-CONT message is:
RLS-EXT-CONT:<tid>:<aid>:<ctag>::[,<dur>];crlf

Include the comma before the optional DUR parameter as this is a positional
parameter block. The comma is a place holder for a parameter (conttype) not
required in this command.
Normal response output format
The syntax of the RLS-EXT-CONT normal response output message is:
crlf
lf
^^^<sid>^<date>^<time>crlf
M^^<ctag>^COMPLDcrlf
;

Error response output format

The syntax of the RLS-EXT-CONT error response output message is:
crlf
lf
^^^<sid>^<date>^<time>crlf
M^^<ctag>^DENYcrlf
^^^<errcde>crlf
[^^^/*error_text*/crlf]*
;

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-63

Parameter description
Refer to “Message parameters” and Table 4-2 for a general description of all
parameters. See Table 4-49 for a listing of all valid AID and DUR values. See
Table 4-28 for a listing of all error codes.
Table 4-49
Valid AID and DUR values for the RLS-EXT-CONT message

Field Valid values

AID 1-PTG2-X[1..8], 1-PTG3-X[1..8]

DUR CONTS (continue)

MNTRY (momentary)
If no value is specified, the default is CONTS.

Example
An example RLS-EXT-CONT normal message response is:
RLS-EXT-CONT:9214:1-ptg2-X2:jps5::,mntry;

9214 05-07-08 10:09:46

M JPS5 COMPLD
;

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-64 Surveillance interface

RLS-SYNCNSW (release synchronization switch)

Purpose
The RLS-SYNCNSW command is used to enable a timing reference and make
it valid. A valid reference is not necessarily the active reference. The
RLS-SYNCNSW command uses the ESI forced switch mode. Up to six
references can be configured. The ESI time reference chooses the best time
reference when a switch is necessary. The RLS-SYNCNSW command is
nonrevertive.
Input format
The syntax of the RLS-SYNCNSW input message is:
RLS-SYNCNSW:<tid>::<ctag>::<ref>;crlf

Normal response output format

The syntax of the RLS-SYNCNSW normal response output message is:
crlf
lf
^^^<sid>^<date>^<time>crlf
M^^<ctag>^COMPLDcrlf
;

Error response output format

The syntax of the RLS-SYNCNSW error response output message is:
crlf
lf
^^^<sid>^<date>^<time>crlf
M^^<ctag>^DENYcrlf
^^^<errcde>crlf
^^^/*error text*/crlf
;

Parameter description
Refer to “Message parameters” and Table 4-2 for a general description of all
parameters. The ref parameter listed in Table 4-50 has restricted values.

See Table 4-28 for a listing of all error codes.

Table 4-50
Specific parameter details

Parameter Details

ref The value of the time reference number is an integer. Up to six

references (1, 2, 3, 4, 5, and 6) can be configured. The integers
correspond to BITSA, BITSB, OC192G1, OC192G2, OC192G3, and
OC192G4. The configuration can be any combination of the six.

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-65

Examples
An example of the RLS-SYNCNSW normal response output message is:
RLS-SYNCNSW:WEST_CH1::123::1;

WEST_CH1 97-04-24 19:35:54

M 123 COMPLD
;

An example of the RLS-SYNCNSW error response output message is:

RLS-SYNCNSW:West_Ch1::1234::1;

WEST_CH1 97-04-24 20:59:17

M 1234 DENY
ENSS
/*Equipage, Not Equipped with Synchronization
Switching*/
;

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-66 Surveillance interface

RTRV-ALM (retrieve alarm)

Purpose
The RTRV-ALM message is a non-autonomous message used on demand to
retrieve active alarms with a severity higher than warning from network
elements. The response message provides information similar to the
autonomous REPT ALM message. All alarms autonomously reported by
means of the REPT ALM message can also be retrieved using the RTRV-ALM
message.

Note: To retrieve common alarms, use the RTRV-ALM-EQPT message.

This message returns all alarms, including common equipment alarms.

Refer to the “Message associations” section later in this chapter for the entire
suite of network element alarms and their TL1 equivalents. For procedures to
clear these alarms refer to Trouble Clearing and Module Replacement,
323-1801-543.
Input format
The syntax of the RTRV-ALM input message is:
RTRV-ALM-<sccm>:<tid>:[<aid>]:<ctag>[::[<ntfcncde>],
[<condtype>],[<srveff>],[<locn>],[<dirn>]];crlf

Normal response output format

The syntax of the RTRV-ALM normal response output message is:
crlf
lf
^^^<sid>^<date>^<time> crlf
M^^<ctag>^COMPLD crlf
[^^^“[<aid>][,<aidtype>]:<ntfcncde>,<condtype>,<srveff>,
<ocrdat>,<ocrtm>,[<locn>][,<dirn>]:\“almmsg\””]crlf
;

Error response output format

The syntax of the RTRV-ALM error response output message is:
crlf
lf
^^^<sid>^<date>^<time> crlf
M^^<ctag>^DENY crlf
^^^<errcde>crlf
[^^^ /*error text*/crlf]
;

Parameter description
Refer to “Message associations” and Table 4-2 for a general description of all
parameters.

See Table 4-28 for a listing of all error codes.

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-67

The access identifier is optional. Use a null value to request the retrieval of
states and conditions for all the AIDs of the type defined by the SCCM. When
the SCCM value is set to ALL, conditions and states are retrieved for all the
addressed entities. When the SCCM value is ALL or COM, the null value for
the AID must be used. Parameter grouping is not supported. See Table 4-51 for
a listing of all valid SCCMs and AIDs.

Table 4-51
Valid SCCM and AID values for the RTRV-ALM message

SCCM Description AID range

ALL All addressable equipment, facility, and common NULL

entities

COM Common equipment, shelf NULL

OC48 2.5G WT transport facility at an OPTera Long Haul 1-48G[4..19]

1600 Repeater

OC-48 TR transport facility at an OPTera Long Haul 1-48G[5,6,8,9,10,11,13,14,15,16,18,

1600 Combiner 19]

OC192 10G WT transport facility at an OPTera Long Haul 1-[D..S]

1600 Repeater

OC-192 XR transport facility at an OPTera Long Haul 1-D[E,W], 1-E[E,W], 1-F[E,W]

1600 Repeater in a regenerator capacity 1-G[E,W], 1-H[E,W], 1-I[E,W]
1-J[E,W], 1-K[E,W]

OC-192 TR transport facility at an OPTera Long Haul 1-G,1-L, 1-Q

1600 Combiner

OSC OSC facility at an OPTera Long Haul Amplifier NE type 1-OTRG[0,5,10,15]-[1,2]

OS AMP facility at an OPTera Long Haul Amplifier NE type 1-OTRG[0,5,10,15]-[1A,1B,1C,2A,

2B,2C]

EQPT ESI module 1-ESIG[1-S7, 2-S8]

Maintenance interface 1-MIU-S9

Message exchange 1-MXG[1-S10, 2-S11]

Shelf controller 1-SCP-S6

2.5G WT transport facility at an OPTera Long Haul 1-48G[4..19]-S[5..20]

1600 Repeater

OC-48 TR transport facility at an OPTera Long Haul 1-48G[5,6,8,9]-S[6,7,9,10]

1600 Combiner 1-48G[10,11,13,14]-S[11,12,14,15]
1-48G[15,16,18,19]-S[16,17,19,20]
—continued—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-68 Surveillance interface

Table 4-51
Valid SCCM and AID values for the RTRV-ALM message (continued)

SCCM Description AID range

10G WT transport interface at an OPTera Long Haul 1-D-S5, 1-E-S6, 1-F-S7,

1600 Repeater 1-G-S8,1-H-S9, 1-I-S10, 1-J-S11,
1-K-S12, 1-L-S13, 1-M-S14,
1-N-S15, 1-Q-S16, 1-P-S17,
1-Q-S18, 1-R-S19, 1-S-S20

EQPT OC-192 XR transport interface at an OPTera Long 1-D[E,W]-S[5,6]

Haul 1600 Repeater in a regenerator capacity 1-E[E,W]-S[7,8]
1-F[E,W]-S[9,10]
1-G[E,W]-S[11,12]
1-H[E,W]-S[13,14]
1-I[E,W]-S[15,16]
1-J[E,W]-S[17,18]
1-K[E,W]-S[19,20]

OC-192 TR transport interface at an OPTera Long 1-G-S8, 1-L-S13, 1-Q-S18

Haul 1600 Combiner

OPC 1-OPC, 1-OPC-S[3,5,12]

Parallel Telemetry 1-PTG2-S13, 1-PTG3-S14
MOR 1-MORG0-S1
1-MORG1-S2
1-MORG2-S3
1-MORG3-S4

Timing Distribution Cards 1-TDCG1-S4A

1-TDCG2-S4B

MOSAIC CPG on an OPTera Long Haul Amplifier NE 1-OTRG0-S[1..5], 1-OTRG5-S[6..10]

type 1-OTRG10-S[11..15],
1-OTRG15-S[16..20]

Note: AID Table 4-3 shows the relationship between the position of a circuit pack on the shelf and the
AID for the related equipment and facilities.

Examples
An example of the RTRV-ALM normal response output message is:
RTRV-ALM-OC192:NE_TID:1-A:CTAG06::MN;

NE_TID 96-05-22 09:48:30

M CTAG06 COMPLD
"1-A,OC192:MN,LOF,NSA,05-22,09-47-09,NEND,ZA:\"Section Rx
loss of frame\""
;

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-69

An example of the RTRV-ALM error response output message is:

RTRV-ALM-OC192:NE_TID:1-A:CTAG07::MN,,bend,;

NE_TID 96-05-22 09:48:36

M CTAG07 DENY
IIDT
/*Input, Invalid DaTa parameter SRVEFF.*/
;

RTRV-ALM-ENV (retrieve alarm environment)

Purpose
The RTRV-ALM-ENV message is a non-autonomous message used on
demand to retrieve active environmental alarms with a severity higher than
warning. Environmental alarms include scan points, shelf temperature, 48V
battery supply, and fan alarms. The response message provides information
similar to the REPT ALM ENV message.

Design information for the entire suite of network element environmental

alarm messages and their TL1 equivalents is unavailable. Refer to Trouble
Clearing and Module Replacement, 323-1801-543, for procedures to clear
these alarms.
Input format
The syntax of the RTRV-ALM-ENV input message is:
RTRV-ALM-ENV:<tid>:[<aid>]:<ctag>::[<ntfcncde>]
[,<almtype>];crlf

Normal response output format

The syntax of the RTRV-ALM-ENV normal response output message is:
crlf
lf
^^^<sid>^<date>^<time>crlf
M^^<ctag>^COMPLD>crlf
^^^“<aid>:<ntfcncde>,<almtype>,<ocrdat>,<ocrtm>,
/“<conddescr>/””crlf
[^^^“<aid>:<ntfcncde>,<almtype>,<ocrdat>,<ocrtm>,
/“<conddescr>/””crlf]
;

Error response output format

The syntax of the RTRV-ALM-ENV error response output message is:
crlf
lf
^^^<sid>^<date>^<time> crlf
M^^<ctag>^DENY crlf
^^^<errcde>crlf
[^^^ /*error text*/ crlf]
;

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-70 Surveillance interface

Parameter description
Refer to “Message parameters” and Table 4-2 for a general description of all
parameters. The access identifier is optional. Use a null value to request the
retrieval of states and conditions for all the environmental AIDs. Parameter
grouping is not supported. See Table 4-52 for a listing of all valid SCCMs and
AIDs.

See Table 4-28 for a listing of all error codes.

Table 4-52
Valid SCCM and AID values for the RTRV-ALM-ENV message

SCCM Description AID range

ENV 48V battery 1-B[A,B]

Bay 1

Fan 1-F[1..3]

Breaker filter 1-BF[A,B]

Telemetry input 1-PTG2-S[1..32], 1-PTG3[1..32]

Note: AID Table 4-3 shows the relationship between the position of a circuit pack on the shelf and the
AID for the related equipment and facilities.

Examples
An example of the RTRV-ALM-ENV normal response output message is:
RTRV-ALM-ENV:NE_TID::CTAG08;

NE_TID 96-05-22 09:48:41

M CTAG08 COMPLD
"1-F3:MN,CLFAN,05-22,09-48-03,\"Fan 3 fail\""
"1-PTG2-S3:MN,MISC,05-22,09-39-53,\"Telemetry input\""
;

An example of the RTRV-ALM-ENV error response output message is:

RTRV-ALM-ENV:NE_TID:1-FAN5:CTAG09;

NE_TID 96-05-22 09:48:45

M CTAG09 DENY
IIAC
/*Input, Invalid ACcess identifier.*/
;

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-71

RTRV-COND (retrieve condition)

Purpose
The RTRV-COND command allows a surveillance operations system to
instruct a network element to return the current standing condition or state
associated with one or more specified equipment or facilities in the target
network element. Standing conditions are alarms of any severity, or threshold
crossing alerts that have been manually provisioned as warning alarms. This
message is reported every hour for each network element.

Note: Threshold crossing events and OPC event logs are not considered
standing conditions and are not retrieved. Environmental alarms are also
not retrieved.
Input format
The syntax of the RTRV-COND message is:
RTRV-COND-<sccm>:<tid>:[<aid>]:<ctag>::[<typereq>],[<locn>],
[<dirn>][,<tmper>],;crlf

Normal response output format

The syntax of the RTRV-COND normal response output message if there are
no conditions to report is:
crlf
lf
^^^<sid>^<date>^<time>crlf
M^^<ctag>^COMPLDcrlf
;

The syntax of the RTRV-COND normal response output message if there is at

least one line of information to report is:
crlf
lf
^^^<sid>^<date>^<time>crlf
M^^<ctag>^COMPLDcrlf
[^^^”<aid>[,<aidtype>]:[<ntfcncde>],<typereq>,[<srveff>],
[<ocrdat>],[<ocrtm>],[<locn>],[<dirn>],
[”\<conddescr>\”]”crlf] (see note)
;

Note: This block occurs at least once, and it can contain multiples.

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-72 Surveillance interface

Error response output format

The syntax of the RTRV-COND error response output message is:
crlf
lf
^^^<sid>^<date>^<time>crlf
M^^<ctag>^DENYcrlf
^^^<errcode>crlf
[^^^/*error_text*/crlf]
;

Parameter description
Refer to “Message parameters” and Table 4-2 for a general description of all
parameters. The typereq parameter is detailed in Table 4-53.

The access identifier is optional. Use a null value to request the retrieval of
states and conditions for all the AIDs of the type defined by the SCCM. When
the SCCM is ALL, the retrieval of conditions and states for all the addressable
entities occurs. When the SCCM value is ALL or COM, the null value for the
AID must be used. Parameter grouping is not supported. See Table 4-54 for a
listing of all valid SCCMs and AIDs.

See Table 4-28 for a listing of all error codes.

Table 4-53
Specific parameter details

Parameter Details

tmper The value of tmper identifies the accumulation time period. The
format for this is VAL-UN, where VAL is value of time and UN is the
same unit. Parameter grouping is not supported.
The valid accumulation time periods for PM parameters are 1-DAY
and 15-MIN.

typereq The valid condition types to be retrieved are:

NULL (to specify all condition types) or the specific condition type
(CONDTYPE), such as LOS and LOF. See the “Message
associations” section later on in this chapter.
Parameter grouping is not supported.

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-73

Table 4-54
Valid SCCM and AID values for the RTRV-COND message

SCCM Description AID range

ALL All addressable equipment and facility entities NULL

COM Common equipment, shelf NULL

OC48 2.5G WT transport facility at an OPTera Long Haul 1600 1-48G[4..19]

Repeater

OC-48 TR transport facility at an OPTera Long Haul 1-48G[5,6,8,9,10,11,13,14,15,16,18

1600 Combiner ,19]

OC192 10G WT transport facility at an OPTera Long Haul 1600 1-[D..S]

Repeater

OC-192 XR transport facility at an OPTera Long Haul 1-D[E,W], 1-E[E,W], 1-F[E,W]

1600 Repeater in a regenerator capacity 1-G[E,W], 1-H[E,W], 1-I[E,W]
1-J[E,W], 1-K[E,W]

OC-192 TR transport facility at an OPTera Long Haul 1-G,1-L, 1-Q

1600 Combiner

OSC OSC facility at an OPTera Long Haul Amplifier NE type 1-OTRG[0,5,10,15]-[1,2]

OS AMP facility at an OPTera Long Haul Amplifier NE type 1-OTRG[0,5,10,15]-[1A,1B,1C,2A,

2B,2C]

EQPT 2.5G WT transport facility at an OPTera Long Haul 1600 1-48G[4..19]-S[5..20]

Repeater

OC-48 TR transport facility at an OPTera Long Haul 1-48G[5,6,8,9]-S[6,7,9,10]

1600 Combiner 1-48G[10,11,13,14]-S[11,12,14,15]
1-48G[15,16,18,19]-S[16,17,19,20]

10G WT transport interface at an OPTera Long Haul 1-D-S5, 1-E-S6, 1-F-S7,

1600 Repeater 1-G-S8,1-H-S9, 1-I-S10, 1-J-S11,
1-K-S12, 1-L-S13, 1-M-S14,
1-N-S15, 1-O-S16, 1-P-S17,
1-Q-S18, 1-R-S19, 1-S-S20

OC-192 XR transport interface at an OPTera Long Haul 1-D[E,W]-S[5,6]

1600 Repeater in a regenerator capacity 1-E[E,W]-S[7,8]
1-F[E,W]-S[9,10]
1-G[E,W]-S[11,12]
1-H[E,W]-S[13,14]
1-I[E,W]-S[15,16]
1-J[E,W]-S[17,18]
1-K[E,W]-S[19,20]
—continued—

OC-192 transport interface at a Combiner 1-G-S8, 1-L-S13, 1-Q-S18

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-74 Surveillance interface

Table 4-54
Valid SCCM and AID values for the RTRV-COND message (continued)

SCCM Description AID range

Shelf controller 1-SCP-S6

OPC 1-OPC, 1-OPC-S[3,5,12]

MOR 1-MORG0-S1
1-MORG1-S2
1-MORG2-S3
1-MORG3-S4

Timing Distribution Cards 1-TDCG1-S4A

1-TDCG2-S4B

MOSAIC CPG on an OPTera Long Haul Amplifier NE 1-OTRG0-S[1..5],1-OTRG5-S[6..10]

type 1-OTRG10-S[11..15],
1-OTRG15-S[16..20]

T1 ESI facilities 1-BITS[A, B]

Timing reference output 1-TRG[1,2]

ESI Reference 1-REF[1..6]

Note: AID Table 4-3 shows the relationship between the position of a circuit pack on the shelf and the
AID for the related equipment and facilities.

Examples
An example of the RTRV-COND normal response output message is:
RTRV-COND-ALL:NE_TID::CTAG10;

NE_TID 96-05-22 09:48:50

M CTAG10 COMPLD
"1-SCP-S6,EQPT:MJ,IMPROPRMVL,NSA,05-22,09-45-45,,NA,,
\"Circuit pack missing\""
"1-A,OC192:MN,LOF,NSA,05-22,09-47-09,NEND,ZA,,
\"Section Rx loss of frame\""
;

An example of the RTRV-COND error response output message is:

RTRV-COND-ALL:NE_TID:1-A:CTAG11::,,in,;

NE_TID 96-05-22 09:48:57

M CTAG11 DENY
IIAC
/*Input, Invalid ACcess identifier - AID must be null.*/
;

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-75

RTRV-HDR (retrieve header)

Purpose
The RTRV-HDR message is a non-autonomous message used to verify the
target identifier (TID) of the network element specified in the input message.
If no TID is specified, the TID of the network element containing the active
OPC is returned in an error response. If the network element number (NE ID)
is specified, the TID of that network element is returned.

Note: The TID of a network element does not necessarily correspond to

the NEname of a network element. Refer to Chapter 1,“Introduction to
TL1” for more information.
Input format
The syntax of the RTRV-HDR input message is:
RTRV-HDR:<tid>::<ctag>;crlf

Normal response output format

The syntax of the RTRV-HDR normal response output message is:
crlf
lf
^^^<sid>^<date>^<time>crlf
M^^<ctag>^COMPLD crlf
;

Error response output format

The syntax of the RTRV-HDR error response output message is:
crlf
lf
^^^<sid>^<date>^<time> crlf
M^^<ctag>^DENYcrlf
^^^<errcde>crlf
[^^^/*<optional free format text>*/crlf]
;

Parameter description
Refer to “Message parameters” and Table 4-2 for a general description of all
parameters.

See Table 4-28 for a listing of all error codes.

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-76 Surveillance interface

Examples
An example of the RTRV-HDR normal response output message is:
RTRV-HDR:NE_TID::CTAG03;

NE_TID 96-05-22 09:48:16

M CTAG03 COMPLD
;

An example of the RTRV-HDR error response output message are:

RTRV-HDR:92013::CTAG05;

92014 96-05-22 09:48:24

M CTAG05 DENY
IITA
/*Input, Invalid TArget identifier.*/
;

An example of the RTRV-HDR error response output message when the TID
value is a null value:
RTRV-HDR:::CTAG04;

92013 96-05-22 09:48:20

M CTAG04 DENY
IITA
/*Input, Invalid TArget identifier.*/
;

Note: This example illustrates that the OPC will use the TID which first
appears in the tidmap list. In this example, the TID 92013 applies to the
OPTera Long Haul 1600 network element and the OPC.

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-77

RTRV-PM (retrieve performance monitoring)

Purpose
The RTRV-PM message is a non-autonomous message used on demand to
retrieve non-zero PM counts. The response message provides information
similar to the autonomous REPT PM message. All performance monitoring
counts autonomously reported by way of the REPT PM message can also be
retrieved using the RTRV-PM message. See the performance monitoring tables
4-98, 4-99, 4-112, and 4-113 for the correlation of performance monitoring
measurements and the TL1 equivalent messages.

Note 1: If facilities use a non-revertive protection switching scheme, the

protection switch duration (PSD) parameter is not supported. A TL1
response to retrieve PSD counts would indicate that the RTRV-PM
command has been completed, but no counts are returned.
Note 2: The PM collection process does not take into account provisioning
information for facilities (if a facility is provisioned, unidirectional,
bidirectional or unprotected). If a parameter is supported in the software
but is not present at the network element, the count is set to zero.
Input format
The syntax of the RTRV-PM input message is:
RTRV-PM-<sccm>:<tid>:[<aid>]:<ctag>[::[<montype>],[<monlev>],
[<locn>],[<dirn>],[<tmper>],[<mondat>],[<montm>]];crlf

Normal response output format

The syntax for the RTRV-PM normal response output message is:
crlf
lf
^^^<sid>^<date>^<time>crlf
M^^<ctag>^COMPLDcrlf
^^^“<aid>[,<aidtype>]:<montype>,<monval>,[<vldty>],[<locn>],
[<dirn>],[<tmper>],[<mondat>],[<montm>]”crlf
;

Error response output format

The syntax of the RTRV-PM error response output message is:
crlf
lf
^^^<sid>^<date>^<time>crlf
M^^<ctag>^DENY crlf
^^^<errcde>crlf
^^^/*error text*/crlf
;

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-78 Surveillance interface

Parameter description
Refer to “Message parameters” and Table 4-2 for a general description of all
parameters. See Tables 4-36, 4-37, 4-38, 4-39, and 4-40 for the range of values
for the various parameters.

See Table 4-28 for a listing of all error codes.

Example
The command to retrieve all 15 minute path code violations (CVP) for OC48
(STS1) facility G1, STS channel 3 (1-48G1-3) in NE1, on August 13, between
8:00 and 9:30 am (08-00&&09-15) is:
RTRV-PM-STS1:NE1:1-48G1-3:Steve1::CVP,,NEND,ZA,15-MIN,8-13,
08-13,08-00&&09-15;

A normal response for this example is:

NE1 92-08-13 10:20:35;
M STEVE1 COMPLD
“1-48G1-3,OC48:CVP,1,COMPL,NEND,ZA,15-MIN,08-13,08-30”
“1-48G1-3,OC48:CVP,3,COMPL,NEND,ZA,15-MIN,08-13,08-00”
;

Note: As there were no path code violations for the time periods starting
08:15 and 09:00, these two time periods were not reported.

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-79

RTRV-PMMODE (retrieve performance monitoring)

Purpose
The RTRV-PMMODE command is a non-autonomous command used to
retrieve the state of PM collection on the OPC. The state of PM collection can
be set on the OPC by using the SET-PMMODE (set performance monitoring
mode) TL1 command or by using the PM Collection Filter tool available in the
OPCUI tool set.

Since the state of PM collection is set for all network elements in the entire
span of control, the TID and AID usually associated with TL1 commands have
no meaning and must be null. If the SCCM is specified as EQPT, the protection
switching parameters and/or physical PM parameters (laser bias current,
optical power) can be affected for all OCn (n = 12, 48, 192) and OPTera Long
Haul 1600 facility types which support such parameters. To distinguish
between the two cases, two modetypes, PROT and PHYS for the protection
switching counts and physical PM counts, respectively, have been defined.
These two modetypes have not been defined in Telcordia standards.
Input format
The syntax of the RTRV-PMMODE message is:
RTRV-PMMODE-<sccm>:::<ctag>::[<locn>],[<modetype>],
[<pmstate>];

Normal response output format

The syntax of the RTRV-PMMODE normal response output message is:
crlf
lf
^^^<sid>^<date>^<time>crlf
M^^<ctag>^COMPLDcrlf
<response block>+
;

The response block has the following format. The normal response must
contain at least one occurrence of such a block:
^^^“<aidtype>:<locn>,<modetype>,<pmstate>”crlf
;

Error response output format

The syntax of the RTRV-PMMODE error response output message is:
crlf
lf
^^^<sid>^<date>^<time>crlf
M^^<ctag>^DENYcrlf
^^^<errcode>crlf
^^^”<error description”crlf
;

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-80 Surveillance interface

Parameters
Refer to “Message parameters” and Table 4-2 for a general description of all
parameters. See Table 4-55 for specific parameter details.

See Table 4-28 for a listing of all error codes.

Table 4-55
Specific parameter details for RTRV-PMMODE

Parameter Details

locn The location is either:

NEND (near end)
FEND (far end)
BTH (both near and far end)
A null value defaults to all that apply.

modetype The PM type should be turned ON or OFF. The parameters supported are:
ALL all parameters which apply for the SCCM specified
P (all path parameters)
L (all line parameters)
S (all section parameters)
PROT (all protection switching parameters)
PROT-P (all path protection switching parameters)
PROT-L (all line protection switching parameters)
PROT-S (all ring protection switching parameters)
PHYS (all physical PM parameters)
A null value defaults to ALL.

pmstate The PM collection state is either:

ON
OFFA null value defaults to ON.

sccm The sccm can be one of the following:

STS1
OC192
OC48
EQPT
ALL

Example
An example of RTRV-PMMODE error output message is:
RTRV-PMMODE-oc48:::1234::nend,1,junk;

NE2 96-08-13 10:20:35

M 1234 DENY
IDNV
/*Input, Data not valid PMSTATE*/
;

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-81

RTRV-TH (retrieve performance monitoring threshold)

Purpose
The RTRV-TH command allows a surveillance operations system to instruct
the target network element to report the current threshold level of one or more
monitored parameters.

Note 1: The “Untimed” interval is not recognized by TL1 and cannot be

retrieved using the RTRV-TH command.
Note 2: If the receive (ZA) and transmit (AZ) facilities are provisioned on
the network element, and if the TMPER values of the threshold match the
value specified in the command, the RTRV-TH command will retrieve both
thresholds. If both facilities are provisioned and the TMPER matches for
only one direction, only the matching threshold will be returned. If neither
time period matches the TMPER requested in the command, the command
fails and a DENY message is returned. If only one facility (receive or
transmit) is provisioned on the network element, and the TMPER value of
the threshold matches the value specified in the command, the threshold
for the existing facility will be retrieved. If the actual TMPER does not
match the TMPER requested in the command, the command fails and a
DENY message is returned.
Input format
The syntax of the RTRV-TH message is:
RTRV-TH-<sccm>:<tid>:<aid>:<ctag>::<montype>,[<locn>],
[<tmper>];cflf

Normal response output format

The syntax of the RTRV-TH normal response output message is:
crlf
lf
^^^<sid>^<date>^<time> crlf
M^^<ctag>^COMPLD crlf
<response block>+
;

The response block has the following format. The normal response must
contain at least one occurrence of such a block:
^^^”<aid>,<aidtype>:<montype>,<locn>,<dirn>,<thlev>,
<tmper>”crlf

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-82 Surveillance interface

Error response output format

The syntax of the RTRV-TH error response output message is:
crlf
lf
^^^<sid>^<date>^<time>crlf
M^^<ctag>^DENY rlf
^^^<errcode>crlf
^^^”<error description”crlf
;

Parameter description
Refer to “Message parameters” and Table 4-2 for a general description of all
parameters. See Tables 4-36, 4-37, 4-38, 4-39, and 4-40 for the range of values
for the various parameters. See Table 4-56 for parameter details specific to the
RTRV-TH command.

Refer to Table 4-28 for a listing of all error codes.

Table 4-56
Specific parameter details

Parameter Details

dirn The direction parameter is sent only in the response and cannot be specified in the
request. The thresholds for both directions, transmit and receive, are sent in the
response if they are available. The receive and transmit directions are monitored only for
DS3 path PM parameters.

locn Only the NEND (near end) thresholds are retrieved. A null value defaults to NEND.

tmper The time period parameter is one of:

1-DAY
15-MIN
A null value specifies the default value of 15-MIN.

Note: The RTRV-TH command does not provide the option to select the direction (ZA
or AZ), and both are retrieved, provided that either direction has the same TMPER value.
If neither of the TMPER values matches the value specified in the command, the
command fails and a DENY message is returned.

Note: The “untimed” interval that is available on the network element is not supported by this command.

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-83

Examples
The command to retrieve the 15-minute path coding violation (CVP) of OC12
facility G4 STS channel 3 (12G4-3), near end (NEND) in NE1 is:
RTRV-TH-STS1:NE1:1-12G4-3:Steve1::CVP,NEND,15-MIN;

A normal response for this example is:

NE1 93-08-13 10:20:35
M STEVE1 COMPLD
“1-12G4-3,OC12:CVP,NEND,ZA,13000,15-MIN”
;

Since the direction (DIRN) is not specified in the command, for the OC12 path
both the transmit and receive threshold values are retrieved with a single
command. For example, the command to retrieve the daily path severe error
seconds (SESP) thresholds of OC12 facility G4 STS channel 2 (12G4-2), near
end (NEND) in NE1 is:
RTRV-TH-STS1:NE1::Steve1:1-12G4-2:SESP,NEND,1-DAY;

A normal response for this example is:

NE1 93-08-13 10:20:35
M STEVE1 COMPLD
“1-12G4-2,OC12:SESP,NEND,AZ,40,1-DAY”
“1-12G4-2,OC12:SESP,NEND,ZA,40,1-DAY”
;

If both time the transmit and receive thresholds are set to a time period other
than the one specified in the command, an error response is returned. In this
example, only if both thresholds are set to a time period other than 1-DAY, the
following error response is sent:
NE1 93-08-13 15:23:27
M STEVE1 DENY
SROF
/*Invalid TMPER set for 1-DAY threshold.*/

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-84 Surveillance interface

SET-PMMODE (set performance monitoring mode)

Purpose
The SET-PMMODE command is a non-autonomous command used to set the
state of PM collection on the OPC. The command allows TL1 to instruct the
PM collector to turn PM collection ON or OFF for the entire span of control
for certain facilities, locations, and layers. It serves the same purpose as the PM
Collection Filter tool available in the User Session Manager.

Since the state of PM collection is set for all network elements in the entire
span of control, the TID and AID usually associated with TL1 commands have
no meaning and must be null. If the SCCM is specified as EQPT, the protection
switching parameters and/or physical PM parameters (laser bias current,
optical power) can be affected for all OCn (n = 3, 12, 48, 192) and OPTera
Long Haul 1600 facility types which support such parameters. To distinguish
between the two cases, two modetypes, PROT and PHYS for the protection
switching counts and physical PM counts, respectively, have been defined.
These two modetypes have not been defined in Telcordia standards.
Input format
The syntax of the SET-PMMODE message is:
SET-PMMODE-<sccm>:::<ctag>::[<locn>],[<modetype>],[<pmstate>];

Normal response output format

The syntax of the SET-PMMODE normal response output message is:
crlf
lf
^^^<sid>^<date>^<time>crlf
M^^<ctag>^COMPLD crlf
;

Error response output format

The syntax of the SET-PMMODE error response output message is:
crlf
lf
^^^<sid>^<date>^<time>crlf
M^^<ctag>^DENY crlf
^^^<errcode>crlf
^^^”<error description”crlf
;

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-85

Parameter description
Refer to “Message parameters” and Table 4-2 for a general description of all
parameters. See Table 4-57 for a listing of all valid values.

See Table 4-28 for a listing of all error codes.

Table 4-57
Specific parameter details for SET-PMMODE

Parameters Details

locn The location is either NEND (near end), FEND (far end), or BTH (both near and far end).
A null value defaults to all that apply.

modetype The PM type should be turned ON or OFF. The parameters supported are:
ALL all parameters which apply for the SCCM specified
P (all path parameters)
L (all line parameters)
S (all section parameters)
PROT (all protection switching parameters)
PROT-P (all path protection switching parameters)
PROT-L (all line protection switching parameters)
PROT-S (all ring protection switching parameters)
PHYS (all physical PM parameters)
A null value defaults to ALL.

pmstate The PM collection state is either ON or OFF. A null value defaults to ON.

sccm The sccm can be one of the following:

STS1, OC192, OC48, EQPT, or ALL.

Examples
An example of a normal response message to turn PM collection on for a
OPTera Long Haul 1600 line, near end is:
SET-PMMODE-OC192:::1234::nend,l,on;

NE2 96-08-13 10:20:35

M 1234 COMPLD
;

An example SET-PMMODE error output message is:

SET-PMMODE-OC192::::1234::nend,l,on;

NE2 96-08-13 10:20:35

M 1234 DENY
IIDT
/*Input, Invalid DaTa parameter.*/
;

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-86 Surveillance interface

SET-SID (set source identifier)

Purpose
This command sets the source identifier (SID). The target identifier (TID)
value is the same as the SID value. The TID is used in the input messages. The
changed name is not reflected on the network element user interface, but is
reflected in the TL1 interface. If the source identifier specified in the command
is greater than 20 characters or contains invalid characters, the request is
denied and an error response is given.

Note: The procedure to set a TL1 TID for the surveillance or provisioning
interfaces from an operations system is described in Chapter 1,
“Introduction to TL1”.
Input format
The syntax of the Set Source Identifier input message is:
SET-SID:<tid>::<ctag>::<sid>;crlf

Normal response output format

The syntax of the Set Source Identifier normal output message is:
crlf
lf
^^^<sid>^<date>^<time> crlf
M^^<ctag>^COMPLD crlf
;

Error response output format

The syntax of the Set Source Identifier error output message is:
crlf
lf
^^^<sid>^<date>^<time> crlf
M^^<ctag>^DENY crlf
^^^<errcde> crlf
[^^^/*<optional free format text>*/ crlf]
;

Parameter description
Refer to “Message parameters” and Table 4-2 for a general description of all
parameters. The parameters listed in Table 4-58 have restricted values.

See Table 4-28 for a listing of all error codes.

Table 4-58
Specific parameter details

Parameter Details

sid the new target identifier of the network element

tid the current target identifier of the network element

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-87

Examples
An example of the Set Source Identifier normal output message is:
SET-SID:92013::CTAG01::NE_TID;

NE_TID 96-05-22 09:48:07

M CTAG01 COMPLD
;

An example of the Set Source Identifier error output message is:

SET-SID:92013::CTAG02::NE_TID;

92014 96-05-22 09:48:12

M CTAG02 DENY
IITA
/*Input, Invalid TArget identifier.*/
;

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-88 Surveillance interface

SET-TH (set performance monitoring threshold)

Purpose
The SET-TH command allows a surveillance operations system to instruct the
target network element to change performance-monitoring (PM) parameter
threshold levels on the target network element. If a threshold level is exceeded,
an autonomous message is sent to the operations system. This command
changes the threshold only at the network element: no threshold values are
stored in the PM database on the OPC.

Note 1: Threshold-crossing alerts or alarms cannot be turned on or off

using the SET-TH command.
Note 2: The manner in which threshold-crossings are reported (as alerts or
alarms) cannot be changed using the SET-TH command.
Note 3: The “Untimed” interval is not recognized by TL1 and cannot be
set using the SET-TH command.
Input format
The syntax of the SET-TH message is:
SET-TH-<sccm>:<tid>:<aid>:<ctag>::<montype>,<thlev>,
[<locn>],[<dirn>],[<tmper>];crlf

Normal response output format

The syntax of the SET-TH normal response output message is:
crlf
lf
^^^<sid>^<date>^<time>crlf
M^^<ctag>^COMPLD crlf
;

Error response output format

The syntax of the SET-TH error response output message is:
crlf
lf
^^^<sid>^<date>^<time>crlf
M^^<ctag>^DENYcrlf
^^^<errcode>crlf
^^^”<error description”crlf
;

Parameter description
Refer to “Message parameters” and Table 4-2 for a general description of all
parameters. See Table 4-59 for the SCCM and AID range of values.

See Table 4-28 for a listing of all error codes.

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-89

Table 4-59
Specific parameter details

Parameter Details

dirn The direction can be AZ (transmit) or ZA (receive). The value of DIRN depends on
MONTYPE. A null value defaults to ZA (receive).

locn Only the NEND (near end) PM counts are monitored. A null value defaults to NEND.

montype The PM type is used to specify which threshold should be set (for example, CVL and
SESS). MONTYPE must not be null.

sccm The second command code modifier cannot be set to ALL and it must not be null.

thlev The new threshold value (positive integer) for the target PM type (MONTYPE). THLEV
must not be null.

tmper The time period is either 15-MIN or 1-DAY. A null value defaults to 15-MIN. The
“untimed” interval is not supported by this command.
If TMPER is specified as 15-MIN, the “timed” interval is set for threshold 1 on the network
element, possibly changing the definition of the time period (day or untimed), which can
have been set by some other means (for example, on the NE UI), to “timed”.
If TMPER is specified as 1-DAY, the “day” interval is set for threshold 2 on the network
element, possibly changing the definition of the time period (timed or untimed), which
can have been set by some other means (for example, on the NE UI), to “day”.

Table 4-60
SCCM and AID values for the SET-TH command

SCCM Description AID

OC48 2.5G WT transport facility at an OPTera Long Haul 1-48G[4..19]

1600 Repeater

OC-48 TR transport facility at an OPTera Long Haul 1-48G[5,6,8,9,10,11,13,14,15,16,

1600 Combiner 18,19]

OC192 10G WT transport facility at an OPTera Long Haul 1-[D..S]

1600 Repeater

OC-192 XR transport facility at an OPTera Long Haul 1-D[E,W], 1-E[E,W], 1-F[E,W]

1600 Repeater in a regenerator capacity 1-G[E,W], 1-H[E,W], 1-I[E,W]
1-J[E,W], 1-K[E,W]

OC-192 TR transport facility at an OPTera Long Haul 1-G,1-L, 1-Q

1600 Combiner

STS1 OC-192 transport facility at an OPTera Long Haul 1600 1-192G[D..S]-[1...192]

terminal
—continued—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-90 Surveillance interface

Table 4-60
SCCM and AID values for the SET-TH command (continued)

SCCM Description AID

EQPT 2.5G WT transport facility at an OPTera Long Haul 1-48G[4..19]-S[5..20]

1600 Repeater

OC-48 TR transport facility at an OPTera Long Haul 1-48G[5,6,8,9]-S[6,7,9,10]

1600 Combiner 1-48G[10,11,13,14]-S[11,12,14,15]
1-48G[15,16,18,19]-S[16,17,19,20]

10G WT transport interface at an OPTera Long Haul 1-D-S5, 1-E-S6, 1-F-S7,

1600 Repeater 1-G-S8,1-H-S9, 1-I-S10, 1-J-S11,
1-K-S12, 1-L-S13, 1-M-S14,
1-N-S15, 1-O-S16, 1-P-S17,
1-Q-S18, 1-R-S19, 1-S-S20

OC-192 XR transport interface at an OPTera Long 1-D[E,W]-S[5,6]

Haul 1600 Repeater in a regenerator capacity 1-E[E,W]-S[7,8]
1-F[E,W]-S[9,10]
1-G[E,W]-S[11,12]
1-H[E,W]-S[13,14]
1-I[E,W]-S[15,16]
1-J[E,W]-S[17,18]
1-K[E,W]-S[19,20]

OC-192 TR transport interface at an OPTera Long 1-G-S8, 1-L-S13, 1-Q-S18

Haul 1600 Combiner

Example
The command to set the 15-minute line coding violation (CVL) of OC12
facility G4 near end (NEND), receive direction (ZA) in NE1 to 13000 is:
SET-TH-OC12:NE1:1-12G4:Steve1::CVL,13000,NEND,ZA,15-MIN;

A normal response for this example is:

NE1 93-08-13 15:23:27
M STEVE1 COMPLD
;

An error response for this example is:

NE1 93-08-13 15:23:27
M STEVE1 DENY
SROF
/*Facility specified does not exist.*/
;

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-91

Message associations
The tables in this part of the chapter permit the cross-reference of the
OPTera Long Haul 1600 network element alarm points to their TL1 equivalent
messages.

Alarm tables
The alarms listed in Table 4-61 provide the association and TL1 parameters of
NE alarms reported autonomously by means of REPT ALM,
REPT ALM ENV, REPT COND, and REPT EVT messages, and on demand
through RTRV-ALM, RTRV-ALM-ENV, and RTRV-COND commands.
Refer to Trouble Clearing and Module Replacement, 323-1801-543, for
procedures to clear these alarms.

REPT EVT messages with an SCCM value of COM and a condtype value of
MISC are reporting event logs. Event logs reported through TL1 are the same
as the logs that can be viewed through the OPC Event Browser tool. A
complete list and description of event logs can be found in Log Reference,
323-1801-840.

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-92 Surveillance interface

Table 4-61
List of TL1 alarm tables

Equipment alarms

Software equipment alarms Table 4-66

Common equipment alarms Table 4-68

Maintenance interface equipment alarms Table 4-70

Message exchange equipment alarms Table 4-72

Orderwire equipment alarms Table 4-74

OPC equipment alarms Table 4-76

Parallel telemetry equipment alarms Table 4-78

Shelf controller equipment alarms Table 4-80

External synchronization interface equipment alarms Table 4-82

Timing Distribution Card equipment alarms Table 4-84

OC-192 WT/XR/TR equipment alarms Table 4-85

OC-48 WT and TR equipment alarms Table 4-87

MOR Plus equipment alarms Table 4-89

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-93

Table 4-62
TL1 alarm table for facilities

Facility alarm type Table #

External synchronization interface facility alarms Table 4-91

OC-192 facility alarms Table 4-93

OC-48 facility alarms Table 4-95

MOR Plus facility alarms Table 4-97

Common equipment PM facility alarms Table 4-99

RLM facility alarms Table 4-101

Table 4-63
TL1 alarm table for equipment

Equipment alarm type Table #

Common equipment environmental alarms Table 4-103

Parallel telemetry environmental alarms Table 4-105

Table 4-64
TL1 alarm table for alerts

Alert type Table #

ESI alerts Table 4-107

Message exchange alerts Table 4-109

ESI facility alerts Table 4-111

Common equipment performance monitoring alerts Table 4-113

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-94 Surveillance interface

Software equipment alarms

Software equipment alarms indicate software problems affecting various
circuit packs in the system. The circuit packs affected are:
• external synchronization interface (ESI)
• orderwire (OW)
• shelf controller (SC)
• multiwavelength optical repeater plus (MOR Plus)
• 2.5G WT
• 10G WT
• OC-192 XR
• OC-48 T/R
• OC-192 T/R
• TDC
• MOSAIC

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-95

Table 4-65 lists SCCM and AID values for software equipment alarms. Table
4-66 correlates software equipment alarms to TL1 messages.

Table 4-65
SCCM and AID values for software equipment alarms

SCCM AID

EQPT 1-ESIG[1-S7,2-S8]
1-OWIG
1-SCP-S6
1-MORG0-S1, 1-MORG1-S2, 1-MORG2-S3, 1-MORG3-S4
1-48G[4..19]-S[5..20]
1-48G[5,6,8,9]-S[6,7,9,10]
1-48G[10,11,13,14]-S[11,12,14,15]
1-48G[15,16,18,19]-S[16,17,19,20]
1-[D..S]
1-D[E,W]-S[5,6]
1-E[E,W]-S[7,8]
1-F[E,W]-S[9,10]
1-G[E,W]-S[11,12]
1-H[E,W]-S[13,14]
1-I[E,W]-S[15,16]
1-J[E,W]-S[17,18]
1-K[E,W]-S[19,20]
1-G-S8
1-L-S13
1-Q-S181-L-S13
1-Q-S18
1-TDCG1-S4A
1-TDCG2-S4B
1-OTRG0-S[1..5]
1-OTRG5-S[6..10]
1-OTRG10-S[11..15]]
1-OTRG15-S[16..20]

Table 4-66
Software equipment alarms

Network element alarm TL1 representation of the network element alarm

Alarm text Sev Serv TL1 CONDTYPE NTFCN SRV DIRN

code messages CDE EFF

Software trap m nsa REPT ALM INTSFT MN NSA NA

Software trap m nsa REPT ALM ORDRWR MN NSA NA

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-96 Surveillance interface

Common equipment alarms

Common equipment alarms indicate trouble with the common equipment
circuit packs. Table 4-67 lists SCCM and AID values for common equipment
alarms. Table 4-68 correlates common equipment alarms to TL1 messages.

Table 4-67
SCCM and AID values for common equipment alarms

SCCM AID

COM NULL

EQPT 1-FC-S[1..10]

Table 4-68
Common equipment alarms

Network element alarm TL1 representation of the network element alarm

Alarm text Sev Serv TL1 CONDTYPE NTFCN SRV DIRN

code messages CDE EFF

Autoprovisioning mismatch m nsa REPT ALM CONTEQPT MN NSA NA

Commissioning MI present m nsa REPT ALM INT MN NSA NA

Duplicate NE name w nsa REPT EVT MISC SC NSA NA

Duplicate NE ID m SA REPT ALM MISC MN SA NA

Entry to 20 ppm freerun m nsa REPT ALM FRNGSYNCS MN NSA NA

Exerciser fail m nsa REPT ALM SWEX MN NSA NA

Filler card missing m nsa REPT ALM IMPROPRMVL MN NSA NA

LCAP port intrusion attempt m nsa REPT ALM INTRUDER MN NSA NA

Manual area address dropped for m nsa REPT ALM MANAADDRDRP MN NSA NA
area

MI port intrusion attempt m nsa REPT ALM INTRUDER MN NSA NA

NE approval required m nsa REPT ALM CONTEQPT MN NSA NA

Network port intrusion attempt m nsa REPT ALM INTRUDER MN NSA NA

Node in reconfiguration mode m nsa REPT ALM MISC MN NSA NA

Node in site test configuration m nsa REPT ALM TSA MN NSA NA

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-97

Table 4-68 (continued)

Common equipment alarms

Network element alarm TL1 representation of the network element alarm

Alarm text Sev Serv TL1 CONDTYPE NTFCN SRV DIRN

code messages CDE EFF

Protection path fail m nsa REPT ALM SWEX MN NSA NA

Reconfiguration failed w nsa REPT ALM INTSFT SC NSA NA

Serial number inconsistency M nsa REPT ALM INT MJ NSA NA

Shelf autoprovisioning mismatch m nsa REPT ALM NULL MN NSA NULL

Shelf mismatch m nsa REPT ALM OC192TERM MN NSA NA

Shelf missing m nsa REPT ALM IMPRPRMVL MN NSA NA

Software transfer fail M nsa REPT ALM CONTCOM MJ NSA NA

Unknown software release M nsa REPT ALM INT MJ NSA NA

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-98 Surveillance interface

Maintenance interface equipment alarms

Maintenance interface equipment alarms indicate trouble with the
maintenance interface circuit pack. Table 4-69 lists SCCM and AID values for
maintenance interface equipment alarms. Table 4-70 correlates maintenance
interface equipment alarms to TL1 messages.

Table 4-69
SCCM and AID values for maintenance interface equipment alarms

SCCM AID

EQPT 1-MIU-S9

Table 4-70
Maintenance interface equipment alarms

Network element alarm TL1 representation of the network element alarm

Alarm text Sev Serv TL1 CONDTYPE NTFCN SRV DIRN

code messages CDE EFF

Circuit pack fail m nsa REPT ALM CONTCOM MN NSA NA

Circuit pack mismatch m nsa REPT ALM CONTEQPT MN NSA NA

Circuit pack missing M nsa REPT ALM IMPROPRMVL MJ NSA NA

Circuit pack vintage mismatch m nsa REPT ALM CONTEQPT MN NSA NA

Intercard fail m nsa REPT ALM INT MN NSA NA

M nsa MJ NSA

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-99

Message exchange equipment alarms

Message exchange equipment alarms indicate trouble with the message
exchange circuit pack. Table 4-71 lists SCCM and AID values for message
exchange equipment alarms. Table 4-72 correlates message exchange
equipment alarms to TL1 messages.

Table 4-71
SCCM and AID values for message exchange equipment alarms

SCCM AID

EQPT 1-MXG[1-S10] [2-S11]

Table 4-72
Message exchange equipment alarms

Network element alarm TL1 representation of the network element alarm

Alarm text Sev Serv TL1 messages CONDTYPE NTFCN SRV DIRN
code CDE EFF

Circuit pack fail M nsa REPT ALM CONTEQPT MJ NSA NA

m nsa MN NSA

Circuit pack mismatch M nsa REPT ALM CONTEQPT MJ NSA NA

m nsa MN NSA

Circuit pack missing M nsa REPT ALM IMPROPRMVL MJ NSA NA

m nsa MN NSA

Circuit pack vintage m nsa REPT ALM CONTEQPT MN NSA NA

mismatch m nsa MN NSA

Equipment forced switch m nsa REPT ALM FRCDWKSWPR MN NSA NA

request

Equipment lockout request m nsa REPT ALM INHSWPR MN NSA NA

Equipment manual switch m nsa REPT ALM MANWKSWPR MN NSA NA

request

Exerciser fail (MX) m nsa REPT ALM SWEX MN NSA NA

Intercard fail M nsa REPT ALM INT MJ NSA NA

m nsa MN NSA

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-100 Surveillance interface

Orderwire equipment alarms

Orderwire equipment alarms indicate trouble with the orderwire circuit pack.
Table 4-73 lists SCCM and AID values for orderwire equipment alarms. Table
4-74 correlates orderwire equipment alarms and TL1 messages.
Table 4-73
SCCM and AID values for orderwire equipment alarms

SCCM AID

EQPT 1-OWIG

Table 4-74
Orderwire equipment alarms

Circuit pack fail m nsa REPT ALM OC192TERM MN NSA NA

Circuit pack mismatch m nsa REPT ALM ORDRWR MN NSA NA

Circuit pack missing m nsa REPT ALM ORDRWR MN NSA NA

Intercard fail M nsa REPT ALM BUERR MJ NSA NA

m nsa MN NSA

Auto orderwire seam active w nsa REPT ALM MISC SC NSA NA

Manual orderwire seam active w nsa REPT ALM MISC SC NSA NA

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-101

Operations controller equipment alarms

OPC equipment alarms indicate trouble with the partitioned OPC circuit
packs. Table 4-75 lists the SCCM and AID values for the OPC circuit packs.
Table 4-76 correlates OPC equipment alarms and TL1 messages.
Table 4-75
SCCM and AID values for OPC equipment alarms

SCCM AID

EQPT 1-OPC
1-OPC-S[3,5,12]

Table 4-76
OPC equipment alarms

Configuration audit fail m nsa REPT ALM DATAFLT MN NSA NA

Connection audit fail m nsa REPT ALM DATAFLT MN NSA NA

Connection services m nsa REPT ALM MISC MN NSA NA

disabled

Datasync fail m nsa REPT ALM DBMEMTRF MN NSA NA

Historical log data lost m nsa REPT ALM DATAFLT MN NSA NA

Lost peer OPC m nsa REPT ALM CONTCOM MN NSA NA

Manual shutdown in m nsa REPT ALM SYSBOOT MN NSA NA

process

OPC alarm(s) active m nsa REPT ALM AIS MN NSA NA

OPC controller circuit pack m nsa REPT ALM CONTR MN NSA NA

fail

OPC controller circuit pack m nsa REPT ALM OC192TERM MN NSA NA

mismatch

OPC controller circuit pack m nsa REPT ALM IMPRPRMVL MN NSA NA

missing

OPC controller circuit pack m nsa REPT ALM IMPRPRMVL MN NSA NA

unseated

OPC controller intercard M nsa REPT ALM CONTR MJ NSA NA

fail m nsa MN NSA

OPC interface circuit pack m nsa REPT ALM CONTR MN NSA NA

fail

Upgrade in progress m nsa REPT ALM SWFTDWN MN NSA NA

—continued—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-102 Surveillance interface

Table 4-76
OPC equipment alarms (continued)

OPC interface circuit pack m nsa REPT ALM OC192TERM MN NSA NA

mismatch

OPC interface circuit pack m nsa REPT ALM IMPRPRMVL MN NSA NA

missing

OPC interface intercard M nsa REPT ALM BUERR MJ NSA NA

fail

OPC storage circuit pack m nsa REPT ALM CONTR MN NSA NA

fail

OPC storage circuit pack m nsa REPT ALM OC192TERM MN NSA NA

mismatch

OPC storage circuit pack m nsa REPT ALM IMPRPRMVL MN NSA NA

missing

OPC storage circuit pack m nsa REPT ALM IMPRPRMVL MN NSA NA

unseated

OPC external Ethernet m nsa REPT ALM CONTCOM MN NSA NA

LOS

OPC internal Ethernet LOS m nsa REPT ALM CONTCOM MN NSA NA

OPC OAM software fail m nsa REPT ALM CONTCOM MN NSA NA

Primary/Backup: disk 95% m nsa REPT ALM DISKFULL MN NSA NA

full

Primary/Backup: disk bad m nsa REPT ALM DISKERR MN NSA NA

media detected

Primary/Backup: network m nsa REPT ALM INTRUDER MN NSA NA

port intrusion

Primary/Backup: serial port m nsa REPT ALM INTRUDER MN NSA NA

intrusion

Primary/Backup: TCP/IP M nsa REPT ALM ACCESSDENY MJ NSA NA

access violation

Removable media m nsa REPT ALM BKUPMEMS MN NSA NA

backup/restore fail

User profile audit fail m nsa REPT ALM DATAFLT MN NSA NA

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-103

Parallel telemetry equipment alarms

Parallel telemetry equipment alarms indicate trouble with the parallel
telemetry circuit pack. Table 4-77 lists SCCM and AID values for parallel
telemetry equipment alarms. Table 4-78 correlates parallel telemetry
equipment alarms to TL1 messages.

Table 4-77
SCCM and AID values for parallel telemetry equipment alarms

SCCM AID

EQPT 1-PTG1-S13
1-PTG2-S14

Table 4-78
Parallel telemetry equipment alarms

Network element alarm TL1 representation of the network element alarm

Alarm text Sev Serv TL1 messages CONDTYPE NTFCN SRV DIRN
code CDE EFF

Circuit pack fail m nsa REPT ALM CONTEQPT MN NSA NA

Circuit pack mismatch m nsa REPT ALM CONTEQPT MN NSA NA

Circuit pack missing m nsa REPT ALM IMPROPRMVL MN NSA NA

Circuit pack vintage m nsa REPT ALM CONTEQPT MN NSA NA

mismatch

Intercard fail M nsa REPT ALM CONTEQPT MJ NSA NA

m nsa MN NSA

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-104 Surveillance interface

Shelf controller equipment alarms

Shelf controller equipment alarms indicate trouble with the shelf controller
circuit pack. Table 4-79 lists SCCM and AID values for shelf controller
equipment alarms. Table 4-80 correlates shelf controller equipment alarms to
TL1 messages.

Table 4-79
SCCM and AID values for shelf controller equipment alarms

SCCM AID

EQPT 1-SCP-S6

Table 4-80
Shelf controller equipment alarms

Network element alarm TL1 representation of the network element alarm

Alarm text Sev Serv TL1 messages CONDTYPE NTFCN SRV DIRN
code CDE EFF

Circuit pack fail m nsa REPT ALM CONTEQPT MN NSA NA

Circuit pack mismatch m nsa REPT ALM CONTEQPT MN NSA NA

Circuit pack missing M nsa REPT ALM IMPROPRMVL MJ NSA NA

Circuit pack vintage M nsa REPT ALM CONTEQPT MJ NSA NA

mismatch

Intercard fail M nsa REPT ALM INT MJ NSA NA

m nsa MN NSA

Software Error m nsa REPT ALM INTSFT MN NSA NA

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-105

External synchronization interface equipment alarms

External synchronization interface (ESI) equipment alarms indicate trouble
with the ESI circuit pack. Table 4-81 lists SCCM and AID values for ESI
equipment alarms. Table 4-82 correlates ESI equipment alarms to TL1
messages.

Table 4-81
SCCM and AID values for external synchronization interfaces (ESI) equipment
alarms

SCCM AID

EQPT 1-ESIG1-S7
1-ESIG2-S8

Table 4-82
External synchronization interface equipment alarms

Network element alarm TL1 representation of the network element alarm

Alarm text Sev Serv TL1 CONDTYPE NTFCN SRV DIRN

code messages CDE EFF

Circuit pack fail M SA REPT ALM SYNCCLKF MJ SA NA

m nsa MN NSA

Circuit pack mismatch M SA REPT ALM SYNCCLK MJ SA NA

m nsa MN NSA

Circuit pack missing M SA REPT ALM IMPROPRMVL MJ SA NA

m nsa MN NSA

Circuit pack vintage m nsa REPT ALM SYNCCLK MN NSA NA

mismatch

End VCO range w nsa REPT EVT SYNCCLKV SC NSA NA

Equipment forced switch m nsa REPT ALM FRCDWKSWPR MN NSA NA

request

Equipment lockout request m nsa REPT ALM INHSWPR MN NSA NA

Equipment manual switch m nsa REPT ALM MANWKSWPR MN NSA NA

request

Failure to lock M SA REPT ALM SYNCCLKL MJ SA NA

m nsa MN NSA

Intercard fail M nsa REPT ALM BUERR MJ NSA NA

m nsa MN NSA

Software error m nsa REPT ALM INTSFT MN NSA NA

—continued—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-106 Surveillance interface

Table 4-82
External synchronization interface equipment alarms (continued)

Network element alarm TL1 representation of the network element alarm

Alarm text Sev Serv TL1 CONDTYPE NTFCN SRV DIRN

code messages CDE EFF

Timing generation entry to w nsa REPT EVT SYNCCLKA SC NSA NA

acquire

Timing generation entry to w nsa REPT EVT FRNGSYNCG SC NSA NA

freerun

Timing generation entry to w nsa REPT EVT FSTSYNC SC NSA NA

fast

Timing generation entry to w nsa REPT EVT HLDOVRSYNC SC NSA NA

holdover

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-107

OC-192 WT / XR / TR equipment alarms

OC-192 WT/XR/TR equipment alarms indicate trouble with the OC-192
WT/XR/TR circuit packs. Each alarm can apply to any one of the three circuit
packs. Table 4-83 lists the SCCM and AID values for OC-192 WT/XR/TR
equipment alarms. Table 4-85 correlates OC-192 WT/XR/TR equipment
alarms to TL1 messages.

Table 4-83
SCCM and AID values for OC-192 WT/XR/TR equipment alarms
Application SCCM AID

10G WT transport facility at an OPTera EQPT 1-D-S5, 1-E-S6, 1-F-S7, 1-G-S8,1-H-S9, 1-I-S10,
Long Haul 1600 Repeater 1-J-S11, 1-K-S12, 1-L-S13, 1-M-S14, 1-N-S15,
1-O-S16, 1-P-S17, 1-Q-S18, 1-R-S19, 1-S-S20

OC-192 XR transport facility at an EQPT 1-D[E,W]-S[5,6], 1-E[E,W]-S[7,8],

OPTera Long Haul 1600 Repeater in a 1-F[E,W]-S[9,10], 1-G[E,W]-S[11,12],
regenerator capacity 1-H[E,W]-S[13,14], 1-I[E,W]-S[15,16],
1-J[E,W]-S[17,18], 1-K[E,W]-S[19,20],

OC-192 TR transport facility at an EQPT 1-G-S8, 1-L-S13, 1-Q-S18

OPTera Long Haul 1600 Combiner.

Table 4-84
Timing Distribution Card equipment alarms
Network element alarm TL1 representation of the network element alarm

Alarm text Sev Serv TL1 CONDTYPE NTFCN SRV DIRN

code messages CDE EFF

Circuit pack fail C SA REPT ALM TDTERM CR SA NA

m nsa MN NSA

Circuit pack mismatch C SA REPT ALM TDTERM CR SA NA

m nsa MN NSA

Circuit pack missing C SA REPT ALM IMPROPRMVL CR SA NA

m nsa MN NSA

Circuit pack overheated C SA REPT ALM HITEMP CR SA NA

m nsa MN NSA

Circuit pack unseated C SA REPT ALM IMPROPRMVL CR SA NA

m nsa MN NSA

Circuit pack vintage C SA REPT ALM TDTERM CR NSA NA

mismatch m nsa MN

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-108 Surveillance interface

Network element alarm TL1 representation of the network element alarm

Alarm text Sev Serv TL1 CONDTYPE NTFCN SRV DIRN

code messages CDE EFF

Equipment forced switch m nsa REPT ALM FRCDWKSWPR MN NSA NA

request

Equipment lockout request m nsa REPT ALM INHSWPR MN NSA NA

Equipment manual switch m nsa REPT ALM MANWKSWPR MN NSA NA

request

Intercard fail M nsa REPT ALM BUERR MJ NSA NA

m nsa MN NSA

Software error m nsa REPT ALM INTSFT MN NSA NA

Table 4-85
OC-192 WT/XR/TR equipment alarms

Network element alarm TL1 representation of the network element alarm

Alarm text Sev Serv TL1 messages CONDTYPE NTFCN SRV DIRN
code CDE EFF

Circuit pack fail C SA REPT ALM OC192TERM CR SA NA

m nsa MN NSA

Circuit pack mismatch C SA REPT ALM OC192TERM CR SA NA

m nsa MN NSA

Circuit pack missing C SA REPT ALM IMPROPRMVL CR SA NA

m nsa MN NSA

Circuit pack overheated C SA REPT ALM HITEMP CR SA NA

m nsa MN NSA

Circuit pack unseated m nsa REPT ALM IMPROPRMVL MN NSA NA

m nsa MN NSA

Circuit pack provision m nsa REPT ALM OC192TERM MN NSA NA

mismatch

Circuit pack vintage C SA REPT ALM OC192TERM CR SA NA

mismatch m nsa MN NSA

Intercard fail m nsa REPT ALM BUERR MN NSA NA

M nsa MJ NSA

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-109

OC-48 WT/TR equipment alarms

Table 4-86 lists SCCM and AID values for OC-48 WT and TR equipment
alarms. Table 4-87 correlates OC-48 WT and TR equipment alarms to TL1
messages.
Table 4-86
SCCM and AID values for OC-48 WT and TR equipment alarms

SCCM AID

EQPT 1-48G[4..19]-S[5..20]
1-48G[5,6,8,9]-S[6,7,9,10]
1-48G[10,11,13,14]-S[11,12,14,15]
1-48G[15,16,18,19]-S[16,17,19,20]

Table 4-87
OC-48 WT and TR equipment alarms

Network element alarm TL1 representation of the network element alarm

Alarm Text Sev Serv TL1 CONDTYPE NTFCN SRV DIRN

code messages CDE EFF

Circuit pack fail C SA REPT ALM OC48TERM CR SA NA

m nsa MN NSA

Circuit pack mismatch C SA REPT ALM OC48TERM CR SA NA

m nsa MN NSA

Circuit pack missing C SA REPT ALM IMPROPRMVL CR SA NA

m nsa MN NSA

Circuit pack overheated C SA REPT ALM HITEMP CR SA NA

m nsa MN NSA

Circuit pack vintage mismatch C SA REPT ALM OC48TERM CR SA NA

m nsa MN NSA

Circuit pack unseated m nsa REPT ALM IMPROPRMVL MN NSA NA

C SA CR SA

Equipment lockout request m nsa REPT ALM INHSWPR MN NSA NA

Intercard fail m nsa REPT ALM BUERR MN NSA NA

M nsa MJ

Circuit pack provision C SA REPT ALM OC48TERM CR SA NA

mismatch m nsa MN NSA

OH bus multidrop link fail m nsa REPT ALM BUERR MN NSA NA

Software error m nsa REPT ALM INTSFT MN NSA NA

Tx laser fail C SA REPT ALM OC48TERM CR SA NA

m nsa MN NSA

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-110 Surveillance interface

Multiwavelength optical repeater (MOR Plus) equipment alarms

MOR Plus equipment alarms indicate trouble with the MOR Plus circuit
packs. Table 4-96 lists the SCCM and AID values for MOR Plus facility
alarms. Table 4-97 correlates MOR Plus equipment alarms to TL1 messages.
Table 4-88
SCCM and AID values for MOR Plus equipment alarms

SCCM Application AID

EQPT Repeater 1-MORG0-S1

Combiner 1-MORG1-S2
1-MORG2-S3
1-MORG3-S4

Table 4-89
MOR Plus equipment alarms
Network element alarm TL1 representation of the network element alarm

Alarm text Sev Serv TL1 CONDTYPE NTFCN SRV DIRN

code message CDE EFF

Circuit pack fail M SA REPT ALM CONTCOM MJ SA NA

Circuit pack mismatch M SA REPT ALM CONTEQPT MJ SA NA

Circuit pack missing M SA REPT ALM IMPROPRMVL MJ SA NA

Intercard fail M SA REPT ALM BUERR MJ NSA NA

OH Bus multidrop link fail m nsa REPT ALM BUERR MN NSA NA

Software error m nsa REPT ALM INTSFT MN NSA NA

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-111

External synchronization interface facility alarms

External synchronization interface (ESI) facility alarms indicate trouble with
the signals being carried by the ESI circuit pack. Table 4-90 lists SCCM and
AID values for ESI facility alarms. Table 4-91 correlates ESI facility alarms to
TL1 messages.

Table 4-90
SCCM and AID values for external synchronization interface (ESI) facility alarms

SCCM AID

T1 1-REF[1..6]
1-BITS[A,B]
1-TRG[1,2]-[1,2]

Table 4-91
External synchronization interface facility alarms

Network element alarm TL1 representation of the network element alarm

Alarm text Sev Serv TL1 message CONDTYPE NTFCN SRV DIRN
code CDE EFF

Degraded clock carrier m nsa REPT ALM SYNCCLK MN NSA AZ

Line AIS m nsa REPT ALM AIS MN NSA ZA

Loss of frame m nsa REPT ALM LOF MN NSA ZA

Loss of signal m nsa REPT ALM LOS MN NSA NA

Reference forced switch m nsa REPT ALM FRCDWKSWPR MN NSA ZA

request

Reference manual switch m nsa REPT ALM MANWKSWPR MN NSA ZA

request

Signal degrade m nsa REPT ALM SYNCCLK MN NSA AZ

Tx AIS m nsa REPT ALM SFI MN NSA AZ

Note: The TL1 parameter LOCN contains NEND for external synchronization interface (ESI) facility
alarms.

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-112 Surveillance interface

OC-192 facility alarms

OC-192 facility alarms indicate trouble with the signals being carried by the
OC-192 transmit/receive/demultiplexer circuit packs. Table 4-92 lists SCCM
and AID values for OC-192 facility alarms. Table 4-93 correlates OC-192
facility alarms to TL1 messages.

Table 4-92
SCCM and AID values for OC-192 facility alarms

Application SCCM AID

10G WT transport facility at an OPTera OC192 1-[D..S]

Long Haul 1600 Repeater

OC-192 XR transport facility at an OC192 1-D[E,W], 1-E[E,W],

OPTera Long Haul 1600 Repeater in a 1-F[E,W], 1-G[E,W],
regenerator capacity 1-H[E,W], 1-I[E,W],
1-J[E,W], 1-K[E,W]

OC-192 TR transport facility at an OC192 1-G

OPTera Long Haul 1600 Combiner. 1-L
1-Q

Table 4-93
OC-192 facility alarms

Network element alarm TL1 representation of the network element alarm

Alarm text Sev Serv TL1 messages CONDTYPE NTFCN SRV DIRN
code CDE EFF

Channel ID mismatch M SA REPT ALM OC192TERM MJ SA NA

Default K-bytes m nsa REPT ALM APSB MN NSA ZA

Extended WTR oscillation M nsa REPT ALM WTR MJ NSA ZA

control active

Far end protection line fail m nsa REPT ALM FEPRLF MN NSA ZA

FEC provisioning mismatch m nsa REPT ALM OC192TERM MN NSA ZA

Force switch request m nsa REPT ALM FRCDWKSWPR MN NSA ZA

Improper APS m nsa REPT ALM APSB MN NSA NA

Invalid sync status message m nsa REPT ALM SYNCSTATINV MN NSA ZA

Invalid K-bytes m nsa REPT ALM APSC MN NSA ZA

Invalid neighbor detected M nsa REPT ALM EXTERR MJ NSA ZA

—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-113

Table 4-93
OC-192 facility alarms (continued)

Network element alarm TL1 representation of the network element alarm

Alarm text Sev Serv TL1 messages CONDTYPE NTFCN SRV DIRN
code CDE EFF

Line AIS C SA REPT ALM AIS CR SA ZA

w nsa REPT EVT SC NSA

Line RFI C SA REPT ALM FERF CR SA ZA

m nsa MN NSA

Line/lockout request m nsa REPT ALM INHSWPR MN NSA ZA

Lock on oscillation control M nsa REPT ALM MA MJ NSA NA

active

Manual switch request m nsa REPT ALM MANWKSWPR MN NSA ZA

Path AIS m nsa REPT ALM AIS MN NSA ZA

Protection switch fail m nsa REPT ALM FAILTOSW MN NSA NA

Protection message m nsa REPT ALM MSGTHRTLACT MN NSA NA

throttling active

Section Rx loss of frame C SA REPT ALM LOF CR SA ZA

m nsa MN NSA

Section Rx loss of signal C SA REPT ALM LOS CR SA ZA

m nsa MN NSA

Section trace mismatch m nsa REPT ALM OC192TERM MN NSA ZA

Signal degrade m SA REPT ALM OC192TERM MN SA ZA

m nsa MN NSA

Signal fail C SA REPT ALM OC192TERM CR SA AZ

m nsa MN NSA

SONET LDCC link fail m nsa REPT ALM LOS MN NSA AZ

SONET SDCC link fail m nsa REPT ALM CONTCON MN NSA ZA

Traffic squelched m nsa REPT ALM AIS MN NSA ZA

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-114 Surveillance interface

OC-48 facility alarms

Table 4-94 lists SCCM and AID values for OC-48 facility alarms. Table 4-95
correlates OC-48 facility alarms to TL1 messages.

Table 4-94
SCCM and AID values for OC-48 facility alarms

SCCM AID

OC48 1-48G[4..19
1-48G[5,6,8,9]
1-48G[10,11,13,14]
1-48G[15,16,18,19]

Table 4-95
OC-48 facility alarms

Network element alarm TL1 representation of the network element alarm

Alarm text Sev Serv TL1 CONDTYPE NTFCN SRV DIRN

code message CDE EFF

APS mode mismatch m nsa REPT ALM APSB MN NSA ZA

Channel ID mismatch M SA REPT ALM OC48TERM MJ SA ZA

Extended WTR oscillation M nsa REPT ALM WTR MJ NSA ZA

control active

Far end protection line fail m nsa REPT ALM FEPRLF MN NSA NA

FEC provisioning mismatch m nsa REPT ALM OC48TERM MN NSA ZA

Force switch request m nsa REPT ALM FRCDWKSWPR MN NSA ZA

Improper APS m nsa REPT ALM APSB MN NSA NA

Invalid sync status m nsa REPT ALM SYNCSTATINV MN NSA ZA

message

Line AIS C SA REPT ALM AIS CR SA ZA

w nsa REPT EVT (see (see
Note1) Note2)

Line RFI C SA REPT ALM FERF CR SA AZ

m nsa MN NSA

Lock on oscillation control M nsa REPT ALM MA MJ NSA NA

active

Line/Lockout request m nsa REPT ALM INHSWPR MN NSA ZA

Manual switch request m nsa REPT ALM MANWKSWPR MN NSA ZA

—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-115

Table 4-95
OC-48 facility alarms (continued)

Network element alarm TL1 representation of the network element alarm

Alarm text Sev Serv TL1 CONDTYPE NTFCN SRV DIRN

code message CDE EFF

Payload fail m nsa REPT ALM OC48TERM MN NSA ZA

Protection message m nsa REPT ALM MSGTHRTLACT MN NSA NA

throttling active

Protection path fail m nsa REPT ALM APSB MN NSA ZA

Protection switch byte fail m nsa REPT ALM APSC MN NSA NA

Protection switch complete w nsa REPT EVT WKSWPR (see (see ZA

Note1) Note2)

Protection switch fail m nsa REPT ALM FAILTOSW MN NSA ZA

Section Rx loss of frame C SA REPT ALM LOF CR SA ZA

m nsa MN NSA

Section Rx loss of signal C SA REPT ALM LOS CR SA ZA

m nsa MN NSA

Section trace mismatch m nsa REPT ALM OC48TERM MN NSA ZA

Signal degrade m SA REPT ALM OC48TERM MN SA ZA

m nsa MN NSA

Signal fail C SA REPT ALM OC48TERM CR SA AZ

m nsa MN NSA

SONET LDCC link fail m nsa REPT ALM LOS MN NSA NA

SONET SDCC link fail m nsa REPT ALM CONTCOM MN NSA NA

Unstable sync status m nsa REPT ALM SYNCSTATINV MN NSA ZA

message

Note 1: The TL1 parameter NTFCNCDE is not used in REPT EVT messages. The CONDEFF
parameter is used instead of NTFCNCDE with a value of SC for warnings.
Note 2: The TL1 parameter SRVEFF is not used in REPT EVT messages.

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-116 Surveillance interface

Multiwavelength optical repeater (MOR Plus) facility alarms

MOR Plus facility alarms indicate trouble with the signals being carried by the
MOR Plus circuit packs. Table 4-96 lists the SCCM and AID values for MOR
Plus facility alarms in terminal, regenerator, and stand alone MOR
configurations. Table 4-97 correlates MOR Plus facility alarms to TL1
messages.

Note 1: The SCCM of “OS” applies to the following alarms:

Blue/Red loss of signal alarm
Blue/Red output optical return loss alarm
Low Blue/Red input for provisioned output alarm
Blue/Red input signal change alarm.
Note 2: SCCM of “OC192” applies to the Blue/Red band shutoff threshold
crossed alarm.
Note 3: The SCCM of “OSC” applies to the OSC loss of signal alarm.
Table 4-96
SCCM and AID values for MOR Plus facility alarms

SCCM Application AID

OS/OC192/OSC Repeater 1-MORG[0..3]

Combiner

Table 4-97
MOR Plus facility alarms
Network element alarm TL1 representation of the network element alarm

Alarm text Sev Serv TL1 CONDTYPE NTFCN SRV DIRN

code message CDE EFF

Blue/Red channel M SA REPT ALM MORTERM MJ SA ZA/AZ

propagation fail

Blue/Red channel M SA REPT ALM MORTERM MJ SA ZA/AZ

propagation mismatch

Blue/Red power M SA REPT ALM MORTERM MJ SA ZA

propagation fail

Blue/Red input signal m nsa REPT ALM INCFAD MN NSA ZA/AZ

change

Blue/Red LOS M SA REPT ALM LOS MJ SA AZ

Blue/Red output optical m nsa REPT ALM MORTERM MN NSA AZ

return loss

Blue/Red power M SA REPT ALM MORTERM MJ SA ZA

propagation fail
—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-117

Network element alarm TL1 representation of the network element alarm

Alarm text Sev Serv TL1 CONDTYPE NTFCN SRV DIRN

code message CDE EFF

Low Blue/Red input for m nsa REPT ALM MORTERM MN NSA AZ

provisioned output

OSC DCC link fail m nsa REPT ALM LOS MN NSA NA

OSC loss of frame m nsa REPT ALM LOS MN NSA ZA

OSC loss of signal m nsa REPT ALM LOS MN NSA ZA

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-118 Surveillance interface

Common equipment performance monitoring (PM) facility alarms

Common equipment PM facility alarms indicate the occurrence of reported
PM threshold crossing alerts. Table 4-98 lists SCCM and AID values for
common equipment PM facility alarms. Table 4-99 correlates common
equipment PM facility alarms to TL1 messages.

Table 4-98
SCCM and AID values for common equipment PM facility alarms

SCCM AID

OC192 1-[D..S]
1-D[E,W], 1-E[E,W],
1-F[E,W], 1-G[E,W],
1-H[E,W], 1-I[E,W],
1-J[E,W], 1-K[E,W]
1-G
1-L
1-Q

OC48 1-48G[4..19
1-48G[5,6,8,9]
1-48G[10,11,13,14]
1-48G[15,16,18,19]

Table 4-99
Common equipment PM facility alarms

Network element alarm TL1 representation of the network element alarm

Alarm Text Sev Serv TL1 CONDTYPE NTFCN SRV DIRN

code message CDE EFF

PM 1 minute line/section threshold m nsa REPT ALM T-GPMLS1MI MN NSA NA

N

PM 15 minute line/section threshold m nsa REPT ALM T-GPMLSM MN NSA NA

PM 15 minute path threshold m nsa REPT ALM T-GPMIPM MN NSA NA

PM day line/section threshold m nsa REPT ALM T-GPMLSD MN NSA NA

PM day path threshold m nsa REPT ALM T-GPMLSD MN NSA NA

PM physical TCA m nsa REPT ALM T-GPMPHYS MN NSA NA

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-119

RLM facility alarms

Remote Layer Management (RLM) facility alarms indicate a loss of signal on
the maintenance interface Ethernet port. Table 4-100 lists SCCM and AID
values for RLM facility alarms. Table 4-101 correlates RLM facility alarms to
TL1 messages.
‘

Table 4-100
SCCM and AID values for RLM facility alarms

OC-192 transport at a terminal COM

OC-192 transport at a regenerator or COM

dense regenerator

Table 4-101
RLM facility alarms

Network element alarm TL1 representation of the network element alarm

Alarm Text Sev Serv TL1 CONDTYPE NTFCN SRV DIRN

code message CDE EFF

MI ethernet loss of signal m nsa REPT ALM LOS MN NSA ZA

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-120 Surveillance interface

Common equipment environmental alarms

Common equipment environmental alarms indicate trouble with various
common environmental conditions affecting the network element. Table 4-102
lists SCCM and AID values for common equipment environmental alarms.
Table 4-103 correlates common equipment environmental alarms to TL1
messages.
‘

Table 4-102
SCCM and AID values for common equipment environmental alarms

SCCM AID

ENV 1
1-B[A,B]
1-BF[A,B]
1-F[1..3]

Table 4-103
Common equipment environmental alarms

Network element alarm TL1 representation of the network element alarm

Alarm Text Sev Serv TL1 CONDTYPE NTFCN SRV DIRN

code message CDE EFF

Breaker filter A fail m nsa REPT ALM BATTERY MN NSA NA

Breaker filter A fail m nsa REPT ALM BATTERY MN NSA NA

Breaker filter B fail m nsa REPT ALM BATTERY MN NSA NA

Breaker filter A missing m nsa REPT ALM BATTERY MN NSA NA

Breaker filter B missing m nsa REPT ALM BATTERY MN NSA NA

Breaker filter A trip m nsa REPT ALM BATTERY MN NSA NA

Breaker filter B trip m nsa REPT ALM BATTERY MN NSA NA

Fan 1 fail M SA REPT ALM CLFAN MJ SA NULL

m nsa MN NSA

Fan 2 fail M SA REPT ALM CLFAN MJ SA NULL

m nsa MN NSA

Fan 3 fail M SA REPT ALM CLFAN MJ SA NULL

m nsa MN NSA

Fan 1 missing M SA REPT ALM CLFAN MJ SA NA

m nsa MN NSA

Fan 2 missing M SA REPT ALM CLFAN MJ SA NA

m nsa MN NSA
—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-121

Table 4-103
Common equipment environmental alarms (continued)

Network element alarm TL1 representation of the network element alarm

Alarm Text Sev Serv TL1 CONDTYPE NTFCN SRV DIRN

code message CDE EFF

Fan 3 missing M SA REPT ALM CLFAN MJ SA NA

m nsa MN NSA

High shelf temperature m nsa REPT ALM HITEMP MN NSA NULL

Low shelf voltage M nsa REPT ALM PWR MJ NSA NA

SATT fail m nsa REPT ALM FUSE MN NSA NA

48V battery A CE supply fail m nsa REPT ALM BATTERY MN NSA NULL

48V battery B CE supply fail m nsa REPT ALM BATTERY MN NSA NULL

48V battery A CE supply low m nsa REPT ALM BATTERY MN NSA NA

48V battery B CE supply low m nsa REPT ALM BATTERY MN NSA NA

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-122 Surveillance interface

Parallel telemetry environmental alarms

The parallel telemetry environmental alarm indicates trouble with
environmental conditions affecting parallel telemetry external customer
inputs. Table 4-104 lists SCCM and AID values for parallel telemetry
environmental alarms. Table 4-105 correlates parallel telemetry environmental
alarms to TL1 messages.

Table 4-104
SCCM and AID values for parallel telemetry environmental alarms

SCCM AID

ENV 1-PTG1-S[1..32],
1-PTG2-S[1..32]

Table 4-105
Parallel telemetry environmental alarms

Network element alarm TL1 representation of the network element alarm

Alarm text Sev Serv TL1 messages CONDTYPE NTFCN SRV DIRN
code CDE EFF

Telemetry input (1 to 32) m nsa REPT ALM MISC MN NSA NULL

Telemetry output m nsa REPT ALM MISC MN NSA NULL

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-123

External synchronization equipment interface (ESI) alerts

External synchronization interface (ESI) alerts indicate event reports affecting
the ESI circuit pack. Table 4-106 lists SCCM and AID values for ESI alerts.
Table 4-107 correlates ESI alerts to TL1 messages.

Table 4-106
SCCM and AID values for ESI alerts

SCCM AID

EQPT 1-ESIG[1-S7,2-S8]
1-SW[A-S14,B-S15]

T1 1-REF[1..6]
1-BITSA
1-BITSB

Table 4-107
ESI alerts

Network element alarm TL1 representation of the network element alarm

Alarm text Sev Serv TL1 messages CONDTYPE COND SRV DIRN
code DEF EFF

Equipment protection switch — nsa REPT EVT WKSWPR TC NSA NA

complete

Equipment protection switch — nsa REPT EVT FAILTOSW TC NSA NA

fail

Reference switch complete — nsa REPT EVT WKSWPR TC NSA ZA

Reference switch fail — nsa REPT EVT FAILTOSW TC NSA ZA

Timing generation to normal — nsa REPT EVT NORMAL TC NSA NA

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-124 Surveillance interface

Message exchange alerts

Message exchange alerts indicate event reports affecting the message
exchange circuit pack. Table 4-108 lists SCCM and AID values for the
message exchange circuit pack. Table 4-109 correlates message exchange
alerts to TL1 messages.
Table 4-108
SCCM and AID values for message exchange alerts

SCCM AID

EQPT 1-MXG[1-S10, 2-S11]

Table 4-109
Message exchange alerts

Equipment protection — nsa REPT EVT WKSWPR TC NSA NA

switch complete

Equipment protection — nsa REPT EVT FEPRLF TC NSA NA

switch fail

External synchronization equipment interface (ESI)

ESI facility alerts indicate event reports affecting ESI facilities. Table 4-110
lists SCCM and AID values for ESI facility alerts. Table 4-111 correlates ESI
facility alerts to TL1 messages.

Table 4-110
SCCM and AID values for ESI facility alerts

SCCM AID

T1 1-REF[1..6]
1-BITSA
1-BITSB

Table 4-111
ESI facility alerts

Network element alarm TL1 representation of the network element alarm

Alarm text Sev Serv TL1 messages CONDTYPE COND SRV DIRN
code DEF EFF

Reference switch complete — nsa REPT EVT WKSWPR TC NSA ZA

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 Surveillance interface 4-125

Common equipment performance monitoring alerts

Common equipment performance monitoring (PM) alerts indicate common
equipment PM threshold crossing event reports. Table 4-112 lists SCCM and
AID values for common equipment PM alerts. Table 4-113 correlates common
equipment PM alerts to TL1 messages.
Table 4-112
SCCM and AID values for common equipment PM alerts

SCCM AID

OC48 1-48G[4..19
1-48G[5,6,8,9]
1-48G[10,11,13,14]
1-48G[15,16,18,19]

STS1 1-48G[1..8]-[1..48]
1-192G[D..S]-[1..192]

Table 4-113
Common equipment PM alerts

Network element alarm TL1 representation of the network element alarm

Alarm Text Sev Serv TL1 CONDTYPE COND SRV DIRN

code message DEF EFF

LBC Threshold — nsa REPT EVT T-LBCL TC NSA ZA

Line Rx CV threshold 1 — nsa REPT EVT T-CVL TC NSA NA

Line Rx CV threshold 2 — nsa REPT EVT T-CVL TC NSA NA

Line Rx ES threshold 1 — nsa REPT EVT T-ESL TC NSA ZA

Line Rx ES threshold 2 — nsa REPT EVT T-ESL TC NSA ZA

Line Rx FEC threshold 1 — nsa REPT EVT T-FECL TC NSA ZA

Line Rx FEC threshold 2 — nsa REPT EVT T-FECL TC NSA ZA

Line Rx SES threshold 1 — nsa REPT EVT T-SESL TC NSA ZA

Line Rx SES threshold 2 — nsa REPT EVT T-SESL TC NSA ZA

Line Rx UAS threshold 1 — nsa REPT EVT T-UASL TC NSA ZA

Line Rx UAS threshold 2 — nsa REPT EVT T-UASL TC NSA ZA

Section Rx CV threshold 1 — nsa REPT EVT T-CVS TC NSA ZA

Section Rx CV threshold 2 — nsa REPT EVT T-CVS TC NSA ZA

Section Rx ES threshold 1 — nsa REPT EVT T-ESS TC NSA ZA

—continued—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

4-126 Surveillance interface

Table 4-113
Common equipment PM alerts (continued)

Network element alarm TL1 representation of the network element alarm

Alarm Text Sev Serv TL1 CONDTYPE COND SRV DIRN

code message DEF EFF

Section Rx ES threshold 2 — nsa REPT EVT T-ESS TC NSA ZA

Section Rx SEFS threshold 1 — nsa REPT EVT T-SEFSS TC NSA ZA

Section Rx SEFS threshold 2 — nsa REPT EVT T-SEFSS TC NSA ZA

Section Rx SES threshold 1 — nsa REPT EVT T-SESS TC NSA ZA

Section Rx SES threshold 2 — nsa REPT EVT T-SESS TC NSA ZA

Path Rx CV threshold 1 — nsa REPT EVT T-CVP TC NSA ZA

Path Rx CV threshold 2 — nsa REPT EVT T-CVP TC NSA ZA

Path Rx ES threshold 1 — nsa REPT EVT T-ESP TC NSA ZA

Path Rx ES threshold 2 — nsa REPT EVT T-ESP TC NSA ZA

Path Rx SES threshold 1 — nsa REPT EVT T-SESP TC NSA ZA

Path Rx SES threshold 2 — nsa REPT EVT T-SESP TC NSA ZA

Path Rx UAS threshold 1 — nsa REPT EVT T-UASP TC NSA ZA

Path Rx UAS threshold 2 — nsa REPT EVT T-UASP TC NSA ZA

OPR threshold — nsa REPT EVT T-LPR TC NSA NA

OPT threshold — nsa REPT EVT T-LPT TC NSA AZ

MS Rx SES threshold 1 — nsa REPT EVT T-SESL TC NSA ZA

MS Rx SES threshold 2 — nsa REPT EVT T-SESL TC NSA ZA

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 5-1

TL1 commissioning 5-
The operations controller (OPC) supports Transaction Language 1 (TL1)
communications over an X.25 connection at the OPC X.25 port. The default
configuration of the OPC X.25 port is for X.25 communications. On the legacy
OPC, X.25 is configured on port B. The OPC also supports TL1
communications over Transmission Control Protocol/Internet Protocol
(TCP/IP) using an Ethernet connection on the OPC faceplate.

This chapter describes how to configure the OPC X.25 port for TL1
communications over X.25, how to configure TL1 over TCP/IP, and how to
access TL1 interfaces through the OPC. It also describes how to configure and
enable TL1 Interface Router Service.

Configuring and accessing TL1 interfaces

To make the TL1 interface over X.25 operational, you must:
• define and enable X.25 on the OPC X.25 port
• configure virtual circuit profile (VCP) addresses
• configure the TL1 Protocol identifier (PID)
• restart the TL1 Session Manager
The procedures in this chapter use the TL1 Configuration tool. Access the TL1
Configuration tool through the OPC UNIX shell. This TL1 Configuration tool
provides the capability to restart the TL1 Session Manager without rebooting
the OPC.

The TL1 Session Manager permits a maximum of four simultaneous TL1

sessions to be active. If four TL1 sessions are active, then a maximum of two
OPC user interface sessions can occur. The quantity of TL1 sessions to the
OPC does not have any affect on the number of virtual circuit profiles. You can
configure more than four virtual circuits, but only a maximum of four can be
active at any one time to establish TL1 sessions to the OPC. The system
permits one TL1 session for each virtual circuit profile. The TL1
Configuration tool allows a user to check the current quantity of active TL1
sessions on the OPC.

TL1 Interface Description 323-1801-190 Rel 3 July 2000

5-2 TL1 commissioning

To configure the X.25 as an X.25/TL1 interface, the OPC X.25 port must have
no connections. To configure the OPC X.25 port for X.25 use, establish a
terminal session through the OPC Ethernet port or through an rlogin session
from a network element.

Configuring the TL1 Interface Router Service

The TL1 Interface Router Service routes TL1 traffic from a remote Operations
System/Network Monitoring (OS/NM) system through a gateway OPC. The
gateway OPCs can route the TL1 traffic to a maximum of four OPCs or spans
of control. A transport protocol class 4 (TP4) connection routes TL1 messages
from the OS through a gateway OPC to a network element on a remote OPC’s
span of control.

Each connection can be one of the following Operations Support System

(OSS) types: NMA (surveillance), OPS (provisioning), or BTH (surveillance
and provisioning). The setting of the OS type for each X.121 address/IP
address provisioned on the Gateway or Remote OPCs determines the
connection.

The preferred combination of connections from the OSS to the gateway OPC
are as follows:
• If a single gateway OPC manages four spans of control (SOCs): then have
one OSS connection to the primary router service and one OSS connection
to the backup router service on the gateway OPC.
• If a single gateway OPC manages only one SOC: then the OSS can have
four connections to the primary router service and four connections to the
backup router service on the gateway OPC.

TL1 Interface Merge

The TL1 Interface Merge allows both the surveillance (NMA) and
provisioning (OPS) interfaces on the same X.121 address/IP address. This
allows an OSS to send and receive TL1 commands/messages to and from an
OPC. The OSS sends and receives the commands and messages over the same
X.121 connection via the X.25 link or the TCP/IP connection. To configure
X.121 address to the option “BTH” (both interfaces) for the TL1 Interface
Merge operation, see Procedure 5-2“Configuring virtual circuit profiles” in
this chapter.

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 TL1 commissioning 5-3

Chapter procedure list

Perform the procedures in Table 5-1 in the order shown to configure an OPC
for TL1 communications over X.25:
Table 5-1

Action Details

Completing an X.25 worksheet Procedure 5-1

Defining and enabling X.25 communications on the OPC X.25 port Procedure 5-2

Configuring virtual circuit profiles Procedure 5-3

Restarting the TL1 Session Manager Procedure 5-4

Perform the procedure in Table 5-2 to modify X.25 parameters on an existing

configuration:
Table 5-2

Action Details

Defining and enabling X.25 communications on the OPC X.25 port Procedure 5-2

Perform the procedure in Table 5-3 to query active TL1 sessions:

Table 5-3

Action Details

Querying active TL1 sessions Procedure 5-5

Perform the procedure in Table 5-4 to access TL1 interfaces through the OPC
UNIX shell:
Table 5-4

Action Details

Accessing and exiting TL1 interfaces through the UNIX shell tool Procedure 5-6

TL1 Interface Description 323-1801-190 Rel 3 July 2000

5-4 TL1 commissioning

Perform the procedure in Table 5-5 to configure and enable TL1 Interface
Router Service over X.25 or TCP/IP:
Table 5-5
Action Details

Configuring and enabling the TL1 Interface Router Service over Procedure 5-7
X.25 or TCP/IP

Perform the procedure in Table 5-6 to configure TL1 over TCP/IP

Table 5-6
Action Details

Configuring TL1 over TCP/IP Procedure 5-8

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 TL1 commissioning 5-5

Procedure 5-1
Completing an X.25 worksheet
Use this procedure to complete an X.25 worksheet. Make copies of the
worksheet from the sample worksheet on page 5-8 to work on. You need the
information in the worksheet to complete Procedure 5-2, “Defining and
enabling X.25 communications on the OPC X.25 port.”

Note: An identical worksheet and a similar procedure is in External

Interface Configuration Procedures, 323-1801-302. The similar procedure
is Completing an X.25 worksheet. Use this procedure to configure OPC
ports for X.3 PAD.

Before you start

• Obtain the listing of the X.25 parameters for your connection from your service provider. X.25 parameter
descriptions are listed at the end of this procedure
• Have a working copy of the X.25 worksheet on page 5-8.

Procedure tasks
• Fill out the X.25 worksheet with your requested values (step 1).
• Obtain the listing of the X.25 parameters for your connection from your service provider (step 7).
• Fill out the X.25 worksheet with the actual service values from your service provider (step 8).

Expected results
• A completed X.25 worksheet.
• If the expected results do not occur:
— Review steps 1 through 5 to be sure you have all your requested values.
— Contact your service provider for any actual service values you are missing.

—continued—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

5-6 TL1 commissioning

Procedure 5-1 (continued)

Completing an X.25 worksheet

Action
Step Action

1 Determine which CCITT X.25 recommendation you want to use for your
connection (that is, 1980 or 1984). Record this value in the “Requested value”
column of the X.25 worksheet for the Network name parameter.
2 Determine the speed of service you want for your receiver and transmitter.
Record these values in the “Requested value” column of the X.25 worksheet.
Record the default inbound throughput class (speed of the receiver) and the
default outbound throughput class (speed of the transmitter) parameters. The
throughput classes supported by the OPC are in the following table.

Throughput class Corresponding baud rate

11 (default) 19200

10 9600

9 4800

8 2400

7 1200

3 Determine the quantity and type of virtual circuits you require and record
these values in the “Requested value” column of the X.25 worksheet for the
following parameters: Maximum number of circuits allowed, Number of
inbound SVCs, Number of SVCs, and Number of outbound SVCs.
The OPC supports a maximum of 16 virtual circuits. The circuits include:
SVCs (two-way switched virtual circuits), IVCs (incoming virtual circuits), and
OVCs (outgoing virtual circuits). The OPC does not support PVCs
(permanent virtual circuits).
As a general guideline, TL1 requires one SVC or IVC for each TL1 session,
and X.3 PAD requires one SVC or IVC for each connection. See External
Interface Configuration Procedures, 323-1801-302 for more information on
X.3 PAD.
4 Determine which facilities you require (that is, flow control negotiation,
throughput class negotiation, fast select, and reverse charge acceptance).
See the X.25 parameter description, which begins on page 5-10, for an
explanation of these facilities. Record the values in the “Requested value”
column of the X.25 worksheet.
—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 TL1 commissioning 5-7

Procedure 5-1 (continued)

Completing an X.25 worksheet

Step Action

5 Determine if you require any specific values for the rest of the X.25
parameters (see the X.25 parameter description, which begins on page
5-10). Note that the OPC default values are not necessarily the same as your
service provider’s default values. Record any requested values in the
“Requested value” column of the X.25 worksheet for the appropriate
parameters.
6 Contact your service provider and request an X.25 connection. You must
provide the following information from step 1 to step 5 to the service provider:
• CCITT X.25 recommendation (1980 or 1984)
• speed of service (throughput class for receiver and transmitter)
• quantity and type of virtual circuits
• any required facilities
• any specific values for the rest of the X.25 parameters
7 Obtain the listing of the X.25 parameters for your connection from your
service provider.
8 Use the information from the X.25 parameter listing to complete the “Actual
service value” column in the X.25 worksheet for all parameters (see the
worksheet on page 5-8).
Note: Record all values provided by your service provider in the worksheet’s
“Actual service value” column. Even if you did not request a specific value for
some parameters, the OPC default might not be the same as your service
provider’s default. For the X.25 connection to function properly, use the
service provider’s value.
—continued—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

5-8 TL1 commissioning

Procedure 5-1 (continued)

Completing an X.25 worksheet

X.25 worksheet
The X.25 worksheet lists all relevant X.25 parameters, and provides space in
which you can record both your required values and the actual service value.
Shaded areas indicate that the column does not apply to that parameter.

Parameter OPC default value Requested Actual

value service value

Global parameters

X.121 Address none

X.121 Packet Address none

Device File Name /dev/x25_0

Programmatic Access Name scc0

Level 2 parameters

Level 2 window size 7 frames

Retransmission timer (T1) 3 000 msec

Idle timer (T3) 60 000 msec

Idle probe timer (T4) 0 msec

Number of retransmissions allowed (N2) 20

Frame size (N1) 149 octets

Level 3 parameters

Network name DTE_84

Flow control negotiation off

Throughput class negotiation off

Fast select disabled

Reverse charge acceptance disabled

PVC inbound packet size none

PVC outbound packet size none

PVC inbound window size none

—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 TL1 commissioning 5-9

Procedure 5-1 (continued)

Completing an X.25 worksheet

Parameter OPC default value Requested Actual

value service value

PVC outbound window size none

PVC inbound throughput class none

PVC outbound throughput class none

Default inbound packet size 128 octets

Default outbound packet size 128 octets

Default inbound window size 2 packets

Default outbound window size 2 packets

Default inbound throughput class 11 (19200 baud)

Default outbound throughput class 11 (19200 baud)

Negotiation limit for inbound packet size 128 octets

Negotiation limit for outbound packet size 128 octets

Negotiation limit for inbound window size 2 packets

Negotiation limit for outbound window size 2 packets

Negotiation limit for inbound throughput class 11 (19200 baud)

Negotiation limit for outbound throughput class 11 (19200 baud)

Maximum number of circuits allowed 0

Number of PVCs none

Number of inbound SVCs 0

Starting logical channel identifier (LCI) 1

Number of SVCs 0

Starting logical channel identifier (LCI) 1

Number of outbound SVCs 0

Starting logical channel identifier (LCI) 1

—continued—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

5-10 TL1 commissioning

Procedure 5-1 (continued)

Completing an X.25 worksheet

X.25 parameter description

The following sections describe the X.25 parameters listed in the X.25
worksheet. This section provides a brief description of each parameter. It also
provides the valid range, the default value, and if applicable the abbreviation
used in the X.25 initialization file. The default values are those used by the
OPC and might differ from those used by your service provider.

For the X.25 connection to function properly, you must use the values provided
by your service provider. Even if you do not request a specific value for some
parameters, the OPC default might not be the same as your service provider’s
default. Use the service provider’s default value.

Global parameters
This section describes the global parameters.
X.121 Address
Obtain the X.121 address from your service provider. The X.121 is the address
of your X.25 connection. There is no default value. The X.121 address can be
a maximum of 10 digits in length. This parameter has the abbreviation “x.121”
in the X.25 initialization file.
X.121 Packet Address
The X.121 packet address is the same as the X.121 address. Obtain the X.121
packet address from your service provider. There is no default value. The
X.121 packet address can be a maximum of 15 digits in length. This parameter
has the abbreviation “x.121_packetaddr” in the X.25 initialization file.
Device File Name
The device file name is the name of the device special file for X.25 on the OPC.
The default file name is /dev/x25_0. Use the default file name. This parameter
has the abbreviation “device” in the X.25 initialization file.
Programmatic Access Name
This is the name that application programs (for example, X.3 PAD) use to
identify the X.25 interface. The default name is scc0. Do not change the default
name. This parameter has the abbreviation “name” in the X.25 initialization
file.
—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 TL1 commissioning 5-11

Procedure 5-1 (continued)

Completing an X.25 worksheet

Level 2 parameters
The following sections describe the level 2 parameters.
Level 2 window size
The level 2 window size defines the number of frames the system can send
before receiving an acknowledgment. The valid range is 1 to 7 and the default
value is 7. This parameter has the abbreviation “l2window” in the X.25
initialization file.
Retransmission timer (T1)
The retransmission timer (T1 timer) specifies the amount of time to wait for
acknowledgment of a frame. The valid range is 1 000 to 12 000 msec and the
default value is 3 000 msec. This parameter has the abbreviation “t1” in the
X.25 initialization file.
Idle timer (T3)
The idle timer (T3 timer) specifies the amount of time the X.25 connection can
be idle before it disconnects. The value must be a multiple of 1 000 msec. If it
is not, the value rounds up. A value of 0 disables the timer. The connection will
never disconnect if the timer disables. The maximum value is 13 000 000
msec. The default value is 60 000 msec. The idle timer should be greater than
the product of the retransmission timer and the number of retransmissions
allowed (T1xN2). This parameter has the abbreviation “t3” in the X.25
initialization file.
Idle probe timer (T4)
After the time specified by the idle probe timer (T4 timer) has elapsed, the
system sends a message to check the integrity of the X.25 connection. The idle
probe timer must be less than or equal to the idle timer. The default value is 0
msec. When the default value is 0, the idle probe timer is off and the
verification message does not get sent. This parameter has the abbreviation
“t4” in the X.25 initialization file.

Note: If the T4 timer is in a disabled state, ensure that the data circuit is
providing a “keep alive signal”. Without the “keep alive signal”, the OPC
drops the connection after a specified time interval (typically 60 seconds).
—continued—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

5-12 TL1 commissioning

Procedure 5-1 (continued)

Completing an X.25 worksheet

Number of retransmissions allowed (N2)

This parameter defines the number of times data can be resent when there is no
acknowledgment message. If there is no acknowledgment message received
after the time defined by the retransmission timer, the system transmits the data
again. The cycle repeats by the number of retransmissions defined by this
parameter. The valid range is 0 to 255. The default value is 20. This parameter
has the abbreviation “n2” in the X.25 initialization file.
Frame size (N1)
The frame size is the number of octets in a frame. The default value is 149. This
parameter has the abbreviation “framesize” in the X.25 initialization file.

Level 3 parameters
The following sections describe the level 3 parameters.
Network name
This parameter specifies the version of the X.25 CCITT recommendation used
for your connection. The default version is DTE_84. Version DTE_80 is also
available. The recommended version is the default version. This parameter has
the abbreviation “networktype” in the X.25 initialization file.
Flow control negotiation
If flow control negotiation is on, you can negotiate packet size and window
size. If flow control negotiation is off you cannot negotiate packet size or
window size. The default is off. This parameter has the abbreviation
“flowcontrol” in the X.25 initialization file.
Throughput class negotiation
Depending on certain conditions, the service provider might not be able to
support your requested connection speed. If throughput class negotiation is on,
negotiation for different connection speeds can occur. If throughput class
negotiation is off, negotiation for different connection speeds cannot occur.
The default is off. This parameter has the abbreviation “thruputclass” in the
X.25 initialization file.
Fast select
If fast select is enabled, it is possible to send data with the call request packet.
If fast select is disabled, it is not possible to send data with the call request
packet. Disable is the default value. This parameter has the abbreviation
“fast_select_accept” in the X.25 initialization file.
—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 TL1 commissioning 5-13

Procedure 5-1 (continued)

Completing an X.25 worksheet

Reverse charge acceptance

If reverse charge acceptance is enabled, you accept all reverse-charge calls
made to you. If reverse charge acceptance is disabled, you do not accept
reverse-charge calls. Disable is the default value. This parameter has the
abbreviation “reverse_charge” in the X.25 initialization file.
PVC inbound packet size
The OPC does not support PVCs. This parameter has no effect, therefore you
do not need to define it. This parameter does not appear in the X.25
initialization file.
PVC outbound packet size
The OPC does not support PVCs. This parameter has no effect, therefore you
do not need to define it. This parameter does not appear in the X.25
initialization file.
PVC inbound window size
The OPC does not support PVCs. This parameter has no effect, therefore you
do not need to define it. This parameter does not appear in the X.25
initialization file.
PVC outbound window size
The OPC does not support PVCs. This parameter has no effect, therefore you
do not need to define it. This parameter does not appear in the X.25
initialization file.
PVC inbound throughput class
The OPC does not support PVCs. This parameter has no effect, therefore you
do not need to define it. This parameter does not appear in the X.25
initialization file.
PVC outbound throughput class
The OPC does not support PVCs. This parameter has no effect, therefore you
do not need to define it. This parameter does not appear in the X.25
initialization file.
Default inbound packet size
The default inbound packet size is the number of octets in each packet that you
can receive. The default value is 128. This parameter has the abbreviation
“def_inpacketsize” in the X.25 initialization file.
—continued—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

5-14 TL1 commissioning

Procedure 5-1 (continued)

Completing an X.25 worksheet

Default outbound packet size

The default outbound packet size is the number of octets per packet that you
transmit. The default is 128. This parameter has the abbreviation
“def_outpacketsize” in the X.25 initialization file.
Default inbound window size
The default inbound window size is the number of packets that you can receive
without sending an acknowledgment message to the sender before
retransmission of the data. The default is 2. This parameter has the
abbreviation “def_inwindow” in the X.25 initialization file.
Default outbound window size
The default outbound window size is the number of packets you can send
without receiving an acknowledgment before you retransmit the data. The
default is 2. This parameter has the abbreviation “def_outwindow” in the X.25
initialization file.
Default inbound throughput class
The default inbound throughput class is the speed of the receiver. The
throughput classes supported by the OPC are 7 (1200 baud), 8 (2400 baud), 9
(4800 baud), 10 (9600 baud), and 11 (19200 baud). The default is 11 (19200
baud). This parameter has the abbreviation “def_inthruputclass” in the X.25
initialization file.
Default outbound throughput class
The default outbound throughput class is the speed of the transmitter. The
throughput classes supported by the OPC are 7 (1200 baud), 8 (2400 baud), 9
(4800 baud), 10 (9600 baud) and 11 (19200 baud). The default is 11 (19200
baud). This parameter has the abbreviation “def_outthruputclass” in the X.25
initialization file.
Negotiation limit for inbound packet size
If flow control negotiation is off, this parameter has no effect and therefore you
do not need to define it. If flow control negotiation is on, this parameter defines
the maximum number of octets per packet that you can receive. You can
receive any packet that contains a number of octets that is less than or equal to
the value defined for this parameter. The negotiation is done during the call
request. The default value is 128. This parameter has the abbreviation
“neg_inpacketsize” in the X.25 initialization file and only appears if flow
control negotiation is on.
—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 TL1 commissioning 5-15

Procedure 5-1 (continued)

Completing an X.25 worksheet

Negotiation limit for outbound packet size

If flow control negotiation is off, this parameter has no effect and therefore you
do not need to define it. If flow control negotiation is on, this parameter defines
the maximum number of octets per packet that you can transmit. You can
transmit any packet that contains a number of octets that is less than or equal
to the value defined for this parameter). The negotiation is done during the call
request. The default value is 128. This parameter has the abbreviation
“neg_outpacketsize” in the X.25 initialization file and only appears if flow
control negotiation is on.
Negotiation limit for inbound window size
If flow control negotiation is off, this parameter has no effect and therefore you
do not need to define it. If flow control negotiation is on, this parameter defines
the maximum number of packets that you can receive without transmitting an
acknowledgment. The negotiation is done during the call request. The default
value is 2. This parameter has the abbreviation “neg_inwindow” in the X.25
initialization file and only appears if flow control negotiation is on.
Negotiation limit for outbound window size
If flow control negotiation is off, this parameter has no effect and therefore you
do not need to define it. If flow control negotiation is on, this parameter defines
the maximum number of packets that you can transmit without receiving an
acknowledgment. The negotiation is done during the call request. The default
value is 2. This parameter has the abbreviation “neg_outwindow” in the X.25
initialization file and only appears if flow control negotiation is on.
Negotiation limit for inbound throughput class
If throughput class negotiation is off, this parameter has no effect and therefore
you do not need to define it. If throughput class negotiation is on, this
parameter defines the maximum speed of the receiver. The negotiation is done
during the call request. The default is 11 (19200 baud). This parameter has the
abbreviation “neg_inthruputclass” in the X.25 initialization file and only
appears if throughput class negotiation is on.
Negotiation limit for outbound throughput class
If throughput class negotiation is off, this parameter has no effect and therefore
you do not need to define it. If throughput class negotiation is on, this
parameter defines the maximum speed of the transmitter. The negotiation is
done during the call request. The default is 11 (19200 baud). This parameter
has the abbreviation “neg_outthruputclass” in the X.25 initialization file and
only appears if throughput class negotiation is on.
—continued—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

5-16 TL1 commissioning

Procedure 5-1 (continued)

Completing an X.25 worksheet

Maximum number of circuits allowed

This parameter defines the maximum number of virtual circuits allowed. The
OPC supports a maximum of 16 virtual circuits. The maximum value includes
two-way SVCs, IVCs, and OVCs. The default is 0. This parameter has the
abbreviation “max_circuits” in the X.25 initialization file.
Number of PVCs
The OPC does not support PVCs. This parameter has no effect, therefore you
do not need to define it. This parameter does not appear in the X.25
initialization file.
Number of inbound SVCs
This parameter defines the maximum number of IVCs. The default is 0. This
parameter is a part of the starting LCI parameter in the X.25 initialization file.
(See the following description of the starting LCI parameter for more details.)

Note: The total quantity of IVCs, SVCs, and OVCs cannot exceed 16.
Number of SVCs
This parameter defines the maximum number of two-way SVCs. The default
is 0. This parameter is a part of the starting LCI parameter in the X.25
initialization file. (See the following description of the starting LCI parameter
for more details.)

Note: The total quantity of IVCs, SVCs, and OVCs cannot exceed 16.
Number of outbound SVCs
This parameter defines the maximum number of outbound SVCs. The default
is 0. This parameter is a part of the starting LCI parameter in the X.25
initialization file. (See the following description of the starting LCI parameter
for more details.)

Note: The total quantity of IVCs, SVCs, and OVCs cannot exceed 16.
Starting LCI
Use this parameter to assign LCIs to the virtual circuits. The valid range is 1 to
4095. The default is 1. You must define a unique LCI for each type of virtual
circuit that used. This parameter has the abbreviation “lci” in the X.25
initialization file and the defined information appears in tabular format. The
LCI number, and the type and number of virtual circuits are in the list.
—end—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 TL1 commissioning 5-17

Procedure 5-2
Defining and enabling X.25 communications on the
OPC X.25 port
Use this procedure to define the X.25 configuration parameters on the OPC
X.25 port. The Port configuration from the OPC described in this procedure
uses the TL1 configuration tool. This tool is an interactive program that
displays menus and prompts to guide you through the process of specifying
configuration parameters. This procedure tells you how to start the program
with the config_TL1 command in the UNIX shell. After you start the program,
it prompts you to supply the necessary parameter values. If the program
terminates abnormally, it might create a configuration file that does not support
X.25 communications. If this happens you must reexecute the following
procedure from the beginning. X.25 configuration parameters on the OPC
X.25 port can also be defined through the OPC UI Port configuration tool.

For parameters that require change, refer to Procedure 5-1, “Completing an

X.25 worksheet”. You must negotiate the values for these parameters with your
network provider. An X.25 interface worksheet is in the External Interface
Configuration Procedures, 323-1801-302. Use this worksheet to help you with
this negotiation.

Before you start

• Obtain a userID and password, at the root or admin class level, that accesses the TL1 Configuration tool.
• Complete the X.25 worksheet as shown in Procedure 5-1, “Completing an X.25 worksheet”.
• Be familiar with the command conventions described in OPC User Interface Description, 323-1801-196.

Procedure tasks
• Log in to the OPC (step 1).
• Configure an X.25 port (step 5).
• Change the X.25 parameters (step 16).
• Create the configuration file (step 74).
• Enable X.25 (step 75).

Expected results
• You will define X.25 parameters and enable X.25.
• If the expected results do not occur:
— Make sure that you have a userID and password at the root or admin class level.
— Make sure that you have thoroughly completed the X.25 worksheet.
— Review the command conventions described in OPC User Interface Description, 323-1801-196.

—continued—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

5-18 TL1 commissioning

Procedure 5-2 (continued)

Defining and enabling X.25 communications on the OPC X.25 port

Note 1: The TL1 Port configuration tool cannot be run simultaneously

with the Port configuration tool.
Note 2: To configure the X.25 as an X.25/TL1 interface the OPC X.25 port
must have no connections. To configure the OPC X.25 port for X.25 use
establish a terminal session through the OPC Ethernet port or through an
rlogin session from a network element.
Note 3: Use all values provided by your service provider as written in the
worksheet’s “Actual service value” column. Even if you do not require a
specific value for some parameters, the OPC default might not be the same
as your service provider’s default. For the X.25 connection to function
properly, use the service provider’s value.
Action
Step Action

Log in to the OPC

1 Log in to the OPC, use the root userID. If you do not know how to do this, see
User Interface Connection Procedures, 323-1801-301.
The “opc>” prompt appears. This is the UNIX shell.
2 Open the TL1 Configuration tool. To open this tool enter:
config_TL1 ↵
The TL1 Configuration Main Menu appears.
Note: Option 8 is not supported by OPTera Long Haul 1600.
***********************************
* TL1 Configuration Main Menu *
***********************************

1 Port Configuration
2 Virtual Circuit Profile Configuration
3 Restart TL1 Session Manager
4 Query Active TL1 Sessions
5 Configure OC-3 TL1 Router over X.25
6 TL1 Interface Router Service Configuration
7 Configure TL1 Over TCP/IP (Enhancements)
8 Configure TL1 AID for High Speed Optics
9 Exit

Enter the number for your selection:

—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 TL1 commissioning 5-19

Procedure 5-2 (continued)

Defining and enabling X.25 communications on the OPC X.25 port

Step Action

3 Select one of the following actions:

If you want to Then go to

configure an X.25 port step 5
exit the TL1 Configuration tool step 4

4 Exit the TL1 Configuration tool. To exit this tool enter:

9 ↵

The “opc>” prompt appears on the UNIX shell. This is the end of the
procedure.
Configure an X.25 port
5 Configure an X.25 port from the TL1 Configuration Main Menu, by entering:
1 ↵
The X.25 Configuration Main Menu appears.
************************************
* X.25 Configuration Main Menu *
************************************

1 Query Configuration
2 Configure X.25
3 Unconfigure a service
4 View config_port_log file
8 Return to Main menu
9 Exit

Enter the number for your selection:

6 Select one of the following actions:

If you want to Then go to

configure an X.25 port step 10
query OPC port configurations step 8
return to the TL1 Configuration Main Menu step 7
exit the TL1 Configuration tool step 4

7 Return to the TL1 Configuration Main Menu, by entering:

8 ↵
The TL1 Configuration Main Menu appears.
Go to step 3.
—continued—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

5-20 TL1 commissioning

Procedure 5-2 (continued)

Defining and enabling X.25 communications on the OPC X.25 port

Step Action

8 Query OPC port configurations from X.25 Configuration Main Menu, by

entering:
1 ↵
A list of current port configurations appears.
9 Note the port configurations, then return to the X.25 Configuration Main
Menu, by pressing the Return key.
The X.25 Configuration Main Menu appears.
Go to step 6.
10 Configure an X.25 port from the X.25 Configuration Main Menu, by entering:
2 ↵
The Configure X.25 menu appears.
Configure X.25:
1 View X.25 parameters
2 Enter X.25 parameters
3 Enable X.25
8 Return to Configure menu
9 Exit

Enter the number for your selection:

11 Select one of the following actions:

If you want to Then go to

view X.25 parameters step 13
change X.25 parameters step 16
return to the X.25 Configuration Main Menu step 12
exit the TL1 Configuration tool step 4

12 Return to the X.25 Configuration Main Menu, by entering:

8 ↵
The X.25 Configuration Main Menu appears.
Go to step 6.
—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 TL1 commissioning 5-21

Procedure 5-2 (continued)

Defining and enabling X.25 communications on the OPC X.25 port

Step Action

View X.25 parameters

13 View X.25 parameters from the Configure X.25 menu, by entering:
1↵
The X.25 parameters appear.
Note: To configure more parameters than fit on the screen, press the return
key to continue or type quit.
14 Compare the X.25 parameters values identified on your X.25 interface
worksheet with the values displayed on your screen, then return to the
configure X.25 menu. To return to this menu press the Return key.
The Configure X.25 menu appears.
15 Select one of the following actions:

If you want to Then go to

change X.25 parameters step 16
accept the current X.25 parameters, and enable X.25 step 75
return to the X.25 Configuration Main Menu step 12
exit the TL1 Configuration tool step 4

Change X.25 parameters

16 Change X.25 parameters from the Configure X.25 menu, by entering:
2 ↵
Messages and prompts similar to the ones below appear. If an X.25
configuration file already exists, the prompt asks you to confirm the creation
of a new one.
The X.25 configuration file (/etc/x25init_scc0) already
exists.
Do you want to create a new configuration file? (Yes/No):
17 Confirm the creation of a new configuration file, by entering:
y↵
—continued—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

5-22 TL1 commissioning

Procedure 5-2 (continued)

Defining and enabling X.25 communications on the OPC X.25 port

Step Action

18 Determine that you have the information required to properly configure the
X.25 parameters.
The following messages and prompts appear.
To properly configure X.25 you MUST know the following
information:
X.121 Address
Device File (/dev/x25_?)
X.25 Programmatic Access Name
Circuit Table Definition
Do you wish to begin configuring X.25 parameter values?
[y/n]:
Note: The circuit table definition is the quantity and type of virtual circuits
(IVCs, SVCs, and OVCs), and their associated starting logical channel
identifiers (LCIs).
19 Confirm the configuration of X.25 parameters, by entering:
y↵
The X.25 parameter menu appears.
1 Global parameters
2 Level 2 parameters
3 Level 3 parameters
4 Display all parameters
5 Exit configuration and create file
6 Abort configuration program; file will not be created

Enter selection:
20 Select one of the following actions:

If you want to Then go to

change global parameters step 21
change level 2 parameters step 29
change level 3 parameters step 39
exit the configuration program: file is created step 74
—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 TL1 commissioning 5-23

Procedure 5-2 (continued)

Defining and enabling X.25 communications on the OPC X.25 port

Step Action

21 Select Global parameters from the X.25 parameter menu, by entering:

1↵
The Global parameters appear in a list. Default values are in the square
brackets that follow the parameter name. If the square brackets are empty,
there is no default value. The Global parameter menu follows the Global
parameter listing.
Global Parameters

X.121 address [] X.121 packet address []

device file [/dev/x25_0] programmatic access name [scc0]

1 Modify global parameters

2 Previous menu

Enter selection:
22 Modify the Global Parameters, by entering:
1↵
Each of the Global parameters appears in turn. You have the opportunity to
enter a value, or to accept the default value. To accept the default value press
the Return key.
The following message appears prompting you to enter the X.121 address.
Enter the X.25 values below; type ‘quit’ to return to menu
23 Enter the X.121 address and press the Return key.
A message appears. The message asks if the X.121 packet address is the
same.
24 Confirm that the X.121 packet address is the same as the X.121 address, by
entering:
y↵
A message appears prompting you to enter the device file name.
25 Use the default device file name (/dev/x25_0), to do this press:
↵
A message appears prompting you to enter the programmatic access name.
—continued—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

5-24 TL1 commissioning

Procedure 5-2 (continued)

Defining and enabling X.25 communications on the OPC X.25 port

Step Action

26 Use the default programmatic access name (scc0), by pressing the Return
key.
The Global parameters appear in a list. The values you entered appear in the
square brackets that follow the parameter name. The Global parameter menu
follows the Global parameter listing.
27 Determine whether or not the Global parameters match the values in your
X.25 worksheet.

If the Global parameters Then go to

match the values in your X.25 worksheet step 28
do not match the values in your X.25 worksheet step 22

28 Return to the X.25 parameter menu, by entering:

2↵
The X.25 parameter menu appears.
Go to step 20.
29 Select the Level 2 parameter option from the X.25 parameter menu, by
entering:
2↵
The Level 2 parameters appear in a list. Default values are in the square
brackets that follow the parameter name. If the square brackets are empty,
there is no default value. The Level 2 parameter menu follows the Level 2
parameter listing.
Level 2 parameters
Level 2 window [7]
idle probe timer (T4) [0 ms]
retransmission timer (T1) [3000 ms]
idle timer (T3) [60000 ms]
retransmission (N2) [20]
framesize (N1) [149 octets]

1 Modify Level 2 parameters

2 Previous menu

Enter selection:
—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 TL1 commissioning 5-25

Procedure 5-2 (continued)

Defining and enabling X.25 communications on the OPC X.25 port

Step Action

30 Modify the Level 2 parameters, by entering:

1↵
The following message appears. The message asks you to enter the Level 2
window size.
Enter the Level 2 values below; type ‘quit’ to return to
menu
31 Enter the Level 2 window size and press the Return key.
The prompt asks you to enter the retransmission timer.
32 Enter the retransmission timer and press the Retrurn key.
The prompt asks you to enter the idle timer.
33 Enter the idle timer and press the Return key.
The prompt asks you to enter the idle probe timer.
34 Enter the idle probe timer and press the Return key.
The prompt asks you to enter the number of retransmissions allowed.
35 Enter the number of retransmissions allowed and press the Return key.
The prompt asks you to enter the frame size.
36 Enter the frame size and press the Return key.
The Level 2 parameters appear in a list. The values you entered appear in the
square brackets that follow the parameter name. The Level 2 parameter menu
follows the Level 2 parameter listing.
37 Determine whether or not the Level 2 parameters match the values in your
X.25 worksheet.

If the Level 2 parameters Then go to

match the values in your X.25 worksheet step 38
do not match the values in your X.25 worksheet step 30
—continued—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

5-26 TL1 commissioning

Procedure 5-2 (continued)

Defining and enabling X.25 communications on the OPC X.25 port

Step Action

38 Return to the X.25 parameter menu, by entering:

2↵
The X.25 parameter menu appears.
Go to step 20.
39 Select Level 3 parameters from the X.25 parameter menu, by entering:
3↵
The Level 3 parameters appear in a list. Default values are in the square
brackets that follow the parameter name.The Level 3 parameter menu follows
the Level 3 parameter listing.
Level 3 Parameters
Network Type… DTE_84 CCITT 1984
Flow control is off Throughput class is off
Fast select is disabled Reverse charging is disabled
Flow control and Throughput Class: IN OUT
PVC packet size [128] [128]
PVC window size [2] [2]
PVC throughput class [11] [11]
default packet size [128] [128]
default window size [2] [2]
default throughput class [11] [11]
negotiation packet size [128] [128]
negotiation window size [2] [2]
negotiation throughput class [11] [11]
CIRCUIT TABLE DEFINITION Total VCs[0] Max VCs allowed[0]
CIRCUIT TYPE STARTING LCI HOW MANY

1 Modify Level 3 parameters

2 Previous menu

Enter selection:
40 Modify the Level 3 parameters, by entering:
1↵
The following message appears. The message asks you to enter the network
name.
Enter the Level 3 values below; type ‘quit’ to return to
menu
—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 TL1 commissioning 5-27

Procedure 5-2 (continued)

Defining and enabling X.25 communications on the OPC X.25 port

Step Action

41 Enter the network name and press the Return key.

Note: The network name is case sensitive. Enter DTE_80 or DTE_84.
A message appears. The message asks if you want flow control negotiation
on.
42 Indicate whether you want flow control negotiation on or off, by entering:
y ↵ (to turn flow control negotiation on)
or
n ↵ (to turn flow control negotiation off)
A message appears. The message asks if you want throughput class
negotiation on.
43 Indicate whether you want throughput class negotiation on or off, by entering:
y ↵ (to turn throughput class negotiation on)
or
n ↵ (to turn throughput class negotiation off)
A message appears. The message asks if you want fast select enabled.
44 Indicate whether you want fast select enabled or disabled, by entering:
y ↵ (to enable fast select)
or
n ↵ (to disable fast select)
A message appears. The message asks if you want reverse charge
acceptance enabled.
45 Indicate whether you want reverse charge acceptance enabled or disabled,
by entering:
y ↵ (to enable reverse charge acceptance)
or
n ↵ (to disable reverse charge acceptance)
A message appears. The message asks you to enter the PVC inbound packet
size.
—continued—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

5-28 TL1 commissioning

Procedure 5-2 (continued)

Defining and enabling X.25 communications on the OPC X.25 port

Step Action

46 Press the Return key.

Note: The OPC does not support PVCs, so it ignores any value you enter for
this parameter.
A message appears. The massage asks you to enter the PVC outbound
packet size.
47 Press the Return key.
Note: The OPC does not support PVCs, so it ignores any value you enter for
this parameter.
A message appears. The massage asks you to enter the PVC inbound
window size.
48 Press the Return key.
Note: The OPC does not support PVCs, so it ignores any value you enter for
this parameter.
A message appears. The message asks you to enter the PVC outbound
window size.
49 Press the Return key.
Note: The OPC does not support PVCs, so it ignores any value you enter for
this parameter.
A message appears. The message asks you to enter the PVC inbound
throughput class.
50 Press the Return key.
Note: The OPC does not support PVCs, so it ignores any value you enter for
this parameter.
A message appears. The message asks you to enter the PVC outbound
throughput class.
51 Press the Return key.
Note: The OPC does not support PVCs, so it ignores any value you enter for
this parameter.
A message appears. The message asks you to enter the default inbound
packet size.
—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 TL1 commissioning 5-29

Procedure 5-2 (continued)

Defining and enabling X.25 communications on the OPC X.25 port

Step Action

52 Enter the default inbound packet size and press the Return key.
A message appears. The message asks you to enter the default outbound
packet size.
53 Enter the default outbound packet size and press the Return key.
A message appears. The message asks if you to enter the default inbound
window size.
54 Enter the default inbound window size and press the Return key.
A message appears. The message asks you to enter the default outbound
window size.
55 Enter the default outbound window size and press the Return key.
A message appears. The message asks you to enter the default inbound
throughput class.
56 Enter the default inbound throughput class and press the Return key.
A message appears. The message asks you to enter the default outbound
throughput class.
57 Enter the default outbound throughput class and press the Return key.
A message appears. The message asks you to enter the negotiation limit for
inbound packet size.
58 Enter the negotiation limit for inbound packet size and press the Return key.
Note: If flow control negotiation is off, the OPC ignores any value you enter
for this parameter.
A message appears. The message asks you to enter the negotiation limit for
outbound packet size.
59 Enter the negotiation limit for outbound packet size and press the Return key.
Note: If flow control negotiation is off, the OPC ignores any value you enter
for this parameter.
A message appears. The message asks you to enter the negotiation limit for
inbound window size.
—continued—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

5-30 TL1 commissioning

Procedure 5-2 (continued)

Defining and enabling X.25 communications on the OPC X.25 port

Step Action

60 Enter the negotiation limit for inbound window size and press the Return key.
Note: If flow control negotiation is off, the OPC ignores any value you enter
for this parameter.
A message appears. The message asks you to enter the negotiation limit for
outbound window size.
61 Enter the negotiation limit for outbound window size and press the Return
key.
Note: If flow control negotiation is off, the OPC ignores any value you enter
for this parameter.
A message appears. The message asks you to enter the negotiation limit for
inbound throughput class.
62 Enter the negotiation limit for inbound throughput class and press the Return
key.
Note: If throughput class negotiation is off, the OPC ignores any value you
enter for this parameter.
A message appears. The message asks you to enter the negotiation limit for
outbound throughput class.
63 Enter the negotiation limit for outbound throughput class and press the
Return key.
Note: If throughput class negotiation is off, the OPC ignores any value you
enter for this parameter.
A message appears. The message asks you to enter the maximum number
of circuits allowed.
64 Enter the maximum number of circuits allowed and press the Return key.
A message appears. The message asks you to enter the number of
permanent virtual circuits.
65 Do not enter any value.
Press the Return key.
A message appears. The message asks you to enter the quantity of inbound
switched virtual circuits.
—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 TL1 commissioning 5-31

Procedure 5-2 (continued)

Defining and enabling X.25 communications on the OPC X.25 port

Step Action

66 Enter the quantity of inbound switched virtual circuits (IVC) and press the
Return key.

If the quantity of IVCs entered is Then

0 The prompt asks you to enter the
quantity of switched virtual circuit.
Go to step 68.
greater than 0 The prompt asks you to enter the
starting logical channel identifier.
Go to step 67.

67 Enter the starting logical channel identifier for the inbound switched virtual
circuits and press the Return key.
A message appears. The message asks you to enter the quantity of switched
virtual circuits.
68 Enter the number of switched virtual circuits (SVC) and press the Return key.

If the quantity of SVCs entered is Then

0 The prompt asks you to enter the
quantity of outbound switched virtual
circuits.
Go to step 70.
greater than 0 The prompt asks you to enter the
starting logical channel identifier.
Go to step 69.

A message appears. The message asks you to enter the starting logical
channel identifier.
69 Enter the starting logical channel identifier for the two-way switched virtual
circuits and press the Return key.
A message appears. The message asks you to enter the quantity of outbound
switched virtual circuits.
—continued—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

5-32 TL1 commissioning

Procedure 5-2 (continued)

Defining and enabling X.25 communications on the OPC X.25 port

Step Action

70 Enter the number of outbound switched virtual circuits (OVC) and press the
Return key.

If the quantity of OVCs entered is Then

0 The Level 3 parameters appear in a
list. Values in square brackets that
follow the parameter name are the
values that you entered. The Level 3
parameter menu follows the Level 3
parameter listing.
Go to step 72.
greater than 0 The prompt asks you to enter the
starting logical channel identifier.
Go to step 71.

71 Enter the starting logical channel identifier for the outbound switched virtual
circuits and press the Return key.
The Level 3 parameters appear in a list. Values in square brackets that follow
the parameter name are the values that you entered. The Level 3 parameter
menu follows the Level 3 parameter listing.
72 Review the Level 3 parameters.

If the Level 3 parameters Then go to

match the values in the X.25 worksheet step 73
do not match the values in the X.25 worksheet step 40

73 Return to the X.25 parameter menu, by entering:

2↵
The X.25 parameter menu appears.
Create the configuration file
74 Create the configuration file from the X.25 parameter menu, by entering:
5↵
The configuration file is created, the program terminates, and the Configure
X.25 menu appears.
—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 TL1 commissioning 5-33

Procedure 5-2 (continued)

Defining and enabling X.25 communications on the OPC X.25 port

Step Action

Enable X.25
75 Enable X.25 from the Configure X.25 menu, by entering:
3↵
If one of the following messages appears for the Then go to
legacy OPC or partitioned OPC:
Port Number (B, 1, 2, 3): step
X.25 operation is being configured on step 77
port X25
Do you wish to continue? (Yes/No)

76 If your hardware configuration supports multiple OPC ports, a message

prompting you to select a port appears.
Port Number (B, 1, 2, 3):
Select OPC port B, 2 or 3 for OC-48 or port 1 for OC-12, by entering:
<port #>↵
where
<port #> is B, 2, 3, or 1

A confirmation message appears.

X.25 operation is being configured on port X25
Do you wish to continue? (Yes/No):
77 Confirm the configuration of X.25 on the OPC X25 port, by entering:
y↵
The following message appears:
X.25 configuration successful on port X25.
Insert the appropriate X.25 cable on port X25.
You have defined X.25 parameters and enabled X.25. The Configure X.25
menu appears after a short period.
Go to step 11.
—end—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

5-34 TL1 commissioning

Procedure 5-3
Configuring virtual circuit profiles
Use this procedure to configure virtual circuit profiles which must be defined
to support the TL1 protocol. Profiles can be added, removed, or listed.
Configuring virtual circuit profiles from the OPC as described in this
procedure utilizes the TL1 configuration tool. This procedure tells you how to
start the program by using the config_TL1 command in the UNIX shell.

Note: The Port configuration tool cannot be run simultaneously with the
TL1 configuration tool.

Before you start

• Obtain a userID and password that allows you to access the OPC at the root level.
• Determine the remote address of the virtual circuit profile you are adding or removing.
• Read the command conventions described in OPC User Interface Description, 323-1801-196.

Procedure tasks
• Configure a virtual circuit profile (step 5).
• List all virtual circuit profiles and protocol ids (step 10).
• Add a virtual circuit profile (step 13).
• Delete a virtual circuit profile (step 17).
• Define a protocol id (step 21).

Expected results
• A virtual circuit profile will be added or deleted.
• A protocol ID for TL1 requests will be defined.
• If the expected results do not occur:
— Verify that you have logged in to the OPC as root.
— Verify that you have the correct OSS address, OSS type, and protocol ID.

—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 TL1 commissioning 5-35

Procedure 5-3 (continued)

Configuring virtual circuit profiles

Action
Step Action

1 Log in to the OPC as root. If you do not know how to do this, see User
Interface Connection Procedures, 323-1801-301.
The “opc>” prompt appears. This is the UNIX shell.
2 Open the TL1 Configuration tool, by entering:
config_TL1 ↵
The TL1 Configuration Main Menu appears.
3 Select an action from the following table:

If you want to Then go to

configure a virtual circuit profile step 5
exit the TL1 Configuration tool step 4

4 Exit the TL1 Configuration tool, by entering:

9↵
The “opc>” prompt appears. This is the UNIX shell.
Configure a virtual circuit profile
5 Configure a virtual circuit profile from the TL1 Configuration Main Menu, by
entering:
2↵
The Virtual Circuit Profile Configuration menu appears.
6 The Virtual Circuit Profile Configuration menu provides access to all of the
virtual circuit profile management functions. Select a function from the
following table:

If you want to Then go to

list all virtual circuit profiles and Protocol IDs step 10
add a virtual circuit profile step 13
remove a virtual circuit profile step 17
define a Protocol ID for TL1 requests step 21
return to the TL1 Configuration Main Menu step 7
exit the TL1 Configuration tool step 9

7 Return to the TL1 Configuration Main Menu, by entering:

8↵
The TL1 Configuration Main Menu appears.
—continued—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

5-36 TL1 commissioning

Procedure 5-3 (continued)

Configuring virtual circuit profiles

Step Action

8 Go to step 3.
9 Exit the TL1 Configuration tool, by entering:
9↵
The “opc>” prompt appears on the UNIX shell. This is the end of the
procedure.
List all virtual circuit profiles and protocol ids
10 List virtual circuit profiles and Protocol IDs from the Virtual Circuit
Configuration menu, by entering:
3↵
A list, similar to the following, appears:
Listing virtual circuits ...

-------------------------------------------------------
Remote address received: 01413134 - OPS
Remote address received: 01412122 - NMA
Remote address received: 01412142 - BTH
Total of 3 virtual circuit profile(s) received.

configured
In-service Protocol ID: NULL
-------------------------------------------------------

Press RETURN when you are done.

11 Return to the Virtual Circuit Configuration menu, by entering:
↵
The Virtual Circuit Profile Configuration menu appears.
12 Go to step 6.
Add a virtual circuit profile
13 Add a virtual circuit profile from the Virtual Circuit Configuration menu, by
entering:
1↵
—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 TL1 commissioning 5-37

Procedure 5-3 (continued)

Configuring virtual circuit profiles

Step Action

14 Define the OSS address, by entering:

<oss address> ↵

where
<oss address> is a number of up to 16 digits
Note: The form of the address can be seen by
listing existing virtual circuit profiles.

The following prompt appears:

Enter OSS type [NMA, OPS, or BTH]:
15 Define the OSS type, by entering:
<oss type> ↵

where
<oss type> is
NMA (for a surveillance interface), or
OPS (for a provisioning interface)
BTH (for both surveillance and provisioning
interface)

A message similar to the following appears:

Adding VCP circuit: address 12345678, type nma.
Do you wish to continue? (Yes/No):
16 Confirm, by entering:
y↵
A message similar to the following appears:
Adding virtual circuit ...

-------------------------------------------------------
New virtual circuit profile created with remote address
12345678
-------------------------------------------------------
The Virtual Circuit Profile Configuration menu appears.
Go to step 6.
—continued—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

5-38 TL1 commissioning

Procedure 5-3 (continued)

Configuring virtual circuit profiles

Step Action

Delete a virtual circuit profile

17 Delete a virtual circuit profile from the Virtual Circuit Profile Configuration
menu, by entering:
2↵
The following prompt appears:
Enter OSS address:
18 Define the OSS address, by entering:
<oss address> ↵

where
<oss address> is the address of the virtual circuit to be deleted

A message similar to the following appears:

Deleting VCP circuit: address 12345678.
Do you wish to continue? (Yes/No):
19 Confirm, by entering:
y↵
A message similar to the following appears:
Deleting virtual circuit ...

-------------------------------------------------------
Virtual circuit profile with remote address 12345678 has
been deleted
-------------------------------------------------------
The Virtual Circuit Profile Configuration menu appears.
20 Go to step 6.
Define a protocol id
21 Define a Protocol ID for TL1 requests from the Virtual Circuit Profile
Configuration menu, by entering:
4↵
A message and prompt similar to the following appear:
Warning: If X.3 PAD is enabled, the Protocol ID must be
set to a value other than 01 or NULL.

The TL1 Session Manager must be restarted in

order for the Protocol ID to take effect.

Enter protocol ID:

—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 TL1 commissioning 5-39

Procedure 5-3 (continued)

Configuring virtual circuit profiles

Step Action

22 Define the protocol ID, by entering:

<protocol ID> ↵

where
<protocol ID> is a hexadecimal number from 1 to 16 digits
Note: Bellcore recommends that “CF” be used as
the protocol ID.

A message and prompt similar to the following appear:

Changing TL1 protocol ID to CF.
Do you wish to continue? (Yes/No):
23 Confirm, by entering:
y↵
A message similar to the following appears:
Modifying protocol identifier ...

-------------------------------------------------------
New protocol ID accepted,
-------------------------------------------------------
The Virtual Circuit Profile Configuration menu appears.
Note: Procedure 5-4 describes restarting the TL1 Session Manager.
Go to step 6.
—end—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

5-40 TL1 commissioning

Procedure 5-4
Restarting the TL1 Session Manager
Use this procedure to restart the TL1 Session Manager. This procedure ensures
that a changed Protocol ID takes effect. There is no need to reboot the OPC.

Note: Restarting the TL1 Session Manager terminates all current TL1
connections.

Before you start

• Obtain a userID and password that allows you to access the OPC at the root level.
• Read the command conventions described in OPC User Interface Description, 323-1801-196.

Procedure tasks
• Log in to the OPC as root (step 1).
• Open the TL1 Configuration tool (step 2).
• Restart the TL1 Session Manager (step 5).

Expected results
• The TL1 Session Manager will be successfully restarted.
• If the expected results do not occur:
— Ensure that you have a userID and password that allows you to access the OPC at the root level.
— Recall if these messages appeared onscreen: “Do you still wish to restart the TL1 Session
Manager? (Yes/No)”, “Restarting TL1 Session Manager”.

—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 TL1 commissioning 5-41

Procedure 5-4 (continued)

Restarting the TL1 Session Manager

Action
Step Action

1 Log in to the OPC as root. If you do not know how to do this, see User
Interface Connection Procedures, 323-1801-301.
The “opc>” prompt appears. This is the UNIX shell.
2 Open the TL1 Configuration tool, by entering:
config_TL1 ↵
The TL1 Configuration Main Menu appears.
3 Select your next step:

If you want to Then go to

Restart the TL1 Session Manager step 5
exit the TL1 Configuration tool step 4

4 Exit the TL1 Configuration tool, by entering:

9↵
The “opc>” prompt appears on the UNIX shell. This is the end of the
procedure.
5 Restart the TL1 Session Manager from the TL1 Configuration Main Menu, by
entering:
3↵
The following warning and prompt appear:
Warning: Restarting the TL1 Session Manager will terminate
all current TL1 connections.

Do you still wish to restart the TL1 Session Manager?

(Yes/No):
6 Confirm, by entering:
y↵
A message similar to the following appears:
Restarting TL1 Session Manager ...
The TL1 Session Manager is restarted, and the TL1 Configuration Main Menu
appears.
7 Go to step 3.
—end—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

5-42 TL1 commissioning

Procedure 5-5
Querying active TL1 sessions
Use this procedure to query the current session quantity. The TL1 Session
Manager permits up to four simultaneous TL1 sessions to be active.

Before you start

• Obtain a userID and password that allows you to access the OPC at the root level.
• Read the command conventions described in OPC User Interface Description, 323-1801-196.

Procedure tasks
• Log in to the OPC as root (step 1).
• Open the TL1 Configuration tool (step 2).
• Query the TL1 Session Manager (step 5).

Expected results
• A list of active TL1 sessions appears.
• If the expected results do not occur:
— Ensure that you have a userID and password that allows you to access the OPC at the root level.
— Ensure that no more than four simultaneous TL1 sessions are active.

—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 TL1 commissioning 5-43

Procedure 5-5 (continued)

Querying active TL1 sessions

Action
Step Action

1 Log in to the OPC as root. If you do not know how to do this, see User
Interface Connection Procedures, 323-1801-301.
The “opc>” prompt appears. This is the UNIX shell.
2 Open the TL1 Configuration tool, by entering:
config_TL1
The TL1 Configuration Main Menu appears.
3 Select your next step:

If you want to Then go to

query the TL1 Session Manager step 5
exit the TL1 Configuration tool step 4

4 Exit the TL1 Configuration tool, by entering:

9↵
The “opc>” prompt appears. This is the UNIX shell. This is the end of the
procedure.
5 Query active TL1 sessions from the TL1 Configuration Main Menu, by
entering:
4↵
A list of active TL1 sessions, similar to the following, appears:
TL1 Interface Managers X.121
---------------------- -----

Press RETURN when you are done.

6 Return to the TL1 Configuration Main Menu, by entering:

↵
The TL1 Configuration Main Menu appears.
7 Go to step 3.
—end—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

5-44 TL1 commissioning

Procedure 5-6
Accessing and exiting TL1 interfaces through the
UNIX shell tool
Use this procedure to access or exit the TL1 surveillance network monitoring
and analysis (NMA). TL1 messages are transferred between the terminal and
the OPC.

Before you start

• Obtain a userID and password that allows you to access the OPC UNIX shell tool directly.
• Read the command conventions described in OPC User Interface Description, 323-1801-196.
• Use a terminal connected to the OPC. The procedure to connect a terminal to an OPC is provided in
User Interface Connection Procedures, 323-1801-301. Do not access TL1 interfaces through the UNIX
shell tool in the User Session Manager.

Procedure tasks
• Access the TL1 interface (step 2).
• Exit the TL1 interface (step 4).

Expected results
• The TL1 Surveillance interface (NMA) is accessed or exited.
• If the expected results do not occur:
— Ensure that you have a userID and password that allows you to access the OPC at the root level.
— Ensure that you have properly typed the commands tl1shell nma and canc-user.

—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 TL1 commissioning 5-45

Procedure 5-6 (continued)

Accessing and exiting TL1 interfaces through the UNIX shell tool

Action
Step Action

1 Log in to the OPC as root. If you do not know how to do this, see User
Interface Connection Procedures, 323-1801-301.
The “opc>” prompt appears. This is the UNIX shell.
Access the TL1 interface
2 Access the TL1 Surveillance interface (NMA), by entering:
tl1shell nma ↵
The “TL1 Command” prompt appears.
3 You can now enter TL1 commands.

All commands must end with a semi-colon. You can spread one TL1
command over many lines, provided you end the command with a
semi-colon. You can also enter multiple commands on one line, providing the
commands are separated with a semi-colon.

For TL1 surveillance interface (NMA) commands, see Chapter 4,

“Surveillance interface”.
Exit the TL1 interface
4 At the “TL1 Command” prompt, enter:
canc-user; ↵
The “opc>” prompt appears. This is the UNIX shell.
5 Exit from the UNIX shell, by entering:
logout ↵
—end—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

5-46 TL1 commissioning

Procedure 5-7
Configuring and enabling the TL1 Interface Router
Service over X.25 or TCP/IP
Use this procedure to configure and enable the TL1 Interface Router Service
(TIRS) over X.25 or TCP/IP. TIRS routes TL1 messages to a maximum of four
spans of control interconnected via optical tributaries, Ethernet, or CNet.

The primary router service is used to route TL1 messages to remote primary
OPC’s span of control. The backup router service is used to route TL1
messages to a remote backup OPC’s span of control.

Before you start

• Obtain a userID and password that accesses the TL1 Configuration tool from the User Session Manager.
• X.25: Determine and provision the X.121 address of the OSS into the virtual circuit profile of both the
gateway OPC containing the TL1 Interface Router Service configuration, and into the remote OPCs. For
more detailed instructions, see Procedure 5-3, “Configuring virtual circuit profiles”, of this chapter.
• X.25: Configure the gateway OPC port B for X.25. For more detailed instructions, see Procedure 5-2,
“Defining and enabling X.25 communications on the OPC X.25 port”, of this chapter.
• X.25: Determine the X.121 address and protocol id (PID) used for the Operations Support System (OSS)
connected to the OPC.
• TCP/IP: Determine the RemoteOPCNames, TIDs, IP address of the OSS, OSS type, and port number
for primary router service over TCP/IP.
• Ensure the OC192 PID is not set to NULL. If it is go to Procedure 5-3 to change the PID value.

Procedure tasks
• Log in to the OPC (step 1).
• Choose to configure TIRS over X.25 or TCP/IP (step 3).
• TCP/IP: Configure and enable primary and backup router service (step 4).
• X.25: Configure and enable primary and backup router service (step 57).

Expected results
• The primary (and backup) TL1 Interface Router Service is configured and enabled over X.25 or TCP/IP.
— If the expected results do not occur:
— Ensure that you have a userID and password that allows you to access the OPC at the admin level.
— Verify that you have chosen the correct options from the TIRS Configuration Main Menu.
— Verify that you have entered the correct data for each step (such as the TID and RemoteOPCName).
— Contact your next level of support.

—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 TL1 commissioning 5-47

Procedure 5-7 (continued)

Configuring and enabling the TL1 Interface Router Service over X.25 or TCP/IP

Action
Step Action

1 Log in to the OPC using the admin userID and open the TL1 Configuration
tool from the User Session Manager. If you do not know how to do this, see
User Interface Connection Procedures, 323-1801-301.
2 Configure the TL1 Interface Router Service, by entering:
6↵
The following TL1 Interface Router Services Configuration menu appears.
********************************************************
* TL1 Interface Router Services Configuration Main Menu *
********************************************************
1 TL1 Interface Router Services Configuration
over X.25
2 TL1 Interface Router Services Configuration
over TCP/IP
8 Return to Main Menu
9 Exit

Enter the number for your selection:

3 Select your next step:

If you want to Then
configure TIRS over X.25 go to step 57
configure TIRS over TCP/IP go to step 4
establish or disable a TL1 session over the go to step 102
TL1 Interface Router Service (see Note)
return to main menu enter 8 ↵
exit the TL1 Configuration tool enter 9 ↵

Note: After you have configured TIRS over X.25 or TCP/IP, you must
establish a TL1 session over the TL1 Interface Router Service (step 102).
When you wish to disable your session, you must disable your session over
the TL1 Interface Router Service (step 102).
—continued—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

5-48 TL1 commissioning

Procedure 5-7 (continued)

Configuring and enabling the TL1 Interface Router Service over X.25 or TCP/IP

Step Action

Configure TIRS over TCP/IP

4 Configure TIRS over TCP/IP, by entering:
2↵
The following TL1 Interface Router Services over TCP/IP
menu appears.

*******************************************************
* TL1 Interface Router Services over TCP/IP Main Menu *
*******************************************************1
1 Primary Router Service Configuration
2 Backup Router Service Configuration
3 Add IP address for OSS Type
4 Delete IP address for OSS Type
5 List IP address for OSS Type
8 Return to Main Menu
9 Exit

Enter the number for your selection:

5 Select your next step:

If you want to Then
configure the primary router service go to step 7
configure the backup router service go to step 6
add IP address for OSS Type go to step 23
delete IP address for OSS Type go to step 27
list IP address for OSS Type go to step 30
return to the main menu enter 8 ↵ and
go to step 3
exit enter 9 ↵

6 Configure the backup router service, by entering:

2↵

Note: For backup router service, the computer screens and procedure steps
are very similar to the screens and steps for the primary router service. The
only difference is the word “backup” will appear instead of the word “primary”
for all screens and text.
—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 TL1 commissioning 5-49

Procedure 5-7 (continued)

Configuring and enabling the TL1 Interface Router Service over X.25 or TCP/IP

Step Action

7 Begin the TL1 primary router service configuration, by entering:

1↵
The following TL1 Interface Router Services over TCP/IP menu appears.
*****************************************************
* TL1 Primary Router Configuration over TCP/IP Menu *
*****************************************************
1 TL1 Primary Router Service Port Configuration
2 TL1 Primary Router Service Configuration
3 Enable TL1 Primary Router Service
4 Disable TL1 Primary Router Service
5 List the TL1 Primary Router Configuration
6 List the TL1 Primary Router Service Port
Configuration
7 Modify TL1 Primary Router Configuration
8 Return to Main Menu
9 Exit

Enter the number for your selection:

8 Select your next step:

If you want to Then

Configure TL1 Primary Router Service Port go to step 9
Configure TL1 Primary Router Service go to step 12
Enable TL1 Primary Router Service go to step 18
Disable TL1 Primary Router Service go to step 19
List the TL1 Primary Router Configuration go to step 20
List the TL1 Primary Router Service Port Configuration go to step 22
Modify TL1 Primary Router Configuration go to step 32
Return to Main Menu enter 8 ↵ and
go to step 5
Exit enter 9 ↵

9 Configure Primary Router Service port, by entering:

1↵
The following message appears.

Enter the port number for Primary Router Service over

TCPIP Operation:
—continued—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

5-50 TL1 commissioning

Procedure 5-7 (continued)

Configuring and enabling the TL1 Interface Router Service over X.25 or TCP/IP

Step Action

10 Enter the port number:

9007 ↵ (this is an example only; your port number may not be the same)
A message similar to the following appears.
Adding the Port Number 9007 for the TL1 Primary Router
Service

Do you wish to continue? (Yes/No):

11 To add the port number enter yes ↵. If you do not want to add the port number
enter no ↵.
Go to step 8.
12 Configure TL1 Primary Router Service, by entering:
2↵

The following message appears:

Enter the RemoteOPCName for TL1 Interface Primary Router
Service (END):
13 Enter the RemoteOPCName
Note 1: The format is OPCxxxxxP, where xxxxx is a 9-character
alphanumeric string, and P stands for primary OPC. Replace the P with B for
a backup OPC. An example of a RemoteOPCName is OPC92755P.
14 Continue to enter all the RemoteOPCNames, when you are finished enter:
end ↵.
The following message appears:
Enter the TID for TL1 Interface Primary Router
Service (END):Configuring and enabling the TL1 Interface
Router Service over X.25 or TCP/IP
15 Enter the TID for TL1 Interface Primary Router Service, by entering:
4801 ↵ (this is an example only; your TID will not be the same)
—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 TL1 commissioning 5-51

Procedure 5-7 (continued)

Configuring and enabling the TL1 Interface Router Service over X.25 or TCP/IP

Step Action

16 When you are finished entering all TIDs, enter end ↵

The following message appears (example only).
The TL1 Primary Router over TCP/IP Configuration you have
Configured:

The RemoteOPC : OPC48011P

The TID : OPC48011P
The TID : 4801
The TID : 4802
Do you wish to Update the Configuration? (Yes/No)

17 To update the configuration enter yes ↵. If you do not want to update the
configuration enter no ↵.
Go to step 8.
18 Enable TL1 Primary Router Service, by entering:
3↵
The following message appears.
TL1 Primary Router Process Enabled Successfully.
Go to step 8.
19 Disable TL1 Primary Router Service, by entering:
4↵
The following message appears.
TL1 Primary Router Process Disabled Successfully.
Go to step 8.
—continued—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

5-52 TL1 commissioning

Procedure 5-7 (continued)

Configuring and enabling the TL1 Interface Router Service over X.25 or TCP/IP

Step Action

20 List the TL1 Primary Router Configuration, by entering:

5↵
The following message appears (example only).
The Configuration
*****************

The RemoteOPC : OPC92755P

The TargetIDentifer : OPC92755P
The TargetIDentifer : ROMULUS
The TargetIDentifer : VULCAN

The RemoteOPC : OPC92599P

The TargetIDentifer : OPC92599P
The TargetIDentifer : TRALEE
The TargetIDentifer : 9259
The TargetIDentifer : WESTPORT

Press Return to continue

21 Press the Return key.

Go to step 8

22 List the TL1 Primary Router Service Port Configuration, by entering:

6↵
The following message appears (9001 is an example only).
TL1 Primary Router Service Configured on the Port Number
9001
Go to step 5.
—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 TL1 commissioning 5-53

Procedure 5-7 (continued)

Configuring and enabling the TL1 Interface Router Service over X.25 or TCP/IP

Step Action

23 Add IP address for OSS type, by entering:

3↵
The following message appears:
Enter IP address of the OSS (END):
An example of an IP address is 192.219.223.79.
The following message appears.
Enter OSS type [NMA or OPS or BTH] (END):
24 Enter OSS type by typing:
NMA ↵ or OPS ↵ or BTH ↵
25 Continue to enter IP addresses to be added, when you are finished enter:
end ↵
The following message appears:
The IP addresses added are

The IP Address : 192.219.223.79 - NMA (example only)

Do you wish to Update the Configuration? (Yes/No):

26 To update the configuration enter yes ↵ if you do not want to update the
configuration enter no ↵.
Go to step 5.
27 Delete IP address for OSS type, by entering:
4↵
The following message appears:
Enter IP address of the OSS (END):
An example of an IP address is 192.219.223.79.
28 Continue to enter the IP addresses to be deleted, when you are finished
enter:
end ↵.
The following message appears:
The IP addresses deleted are

The IP Address : 192.219.223.79 - NMA (example only)

Do you wish to Update the Configuration? (Yes/No):

29 To update the configuration enter yes ↵. If you do not want to update the
configuration enter no ↵.
Go to step 5.
—continued—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

5-54 TL1 commissioning

Procedure 5-7 (continued)

Configuring and enabling the TL1 Interface Router Service over X.25 or TCP/IP

Step Action

30 List IP address for OSS type, by entering:

5↵
The following message appears:
The IP Configuration
********************

The IP Address : 47.105.11.85 - NMA

The IP Address : 47.124.7.206 - BTH

Press Return to continue

Note: The IP addresses shown are examples only. Your addresses will be
different.
31 Press return:
↵
Go to step 5.
32 Modify TL1 Primary Router Configuration, by entering:
7↵

The following Modify Primary Router Configuration menu appears.

***************************************
* Modify Primary Router Configuration *
***************************************
1 Add SOC to Existing TL1 Primary Router Configuration
2 Add TID to existing TL1 Primary Router Configuration
3 Delete SOC from Existing TL1 Primary Router
Configuration
4 Delete TID from existing TL1 Primary Router
Configuration
5 List the TIDs under SOC
8 Return to Main Menu
9 Exit

Enter the number for your selection:

—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 TL1 commissioning 5-55

Procedure 5-7 (continued)

Configuring and enabling the TL1 Interface Router Service over X.25 or TCP/IP

Step Action

33 Select your next step:

If you want to Then

Add SOC to Existing TL1 Primary Router Configuration go to step 46
Add TID to existing TL1 Primary Router Configuration go to step 52
Delete SOC from Existing TL1 Primary Router Configuration go to step 34
Delete TID from Existing TL1 Primary Router Configuration go to step 38
List the TIDs under SOC go to step 42
Return to Main Menu enter 8 ↵ and
go to step 8
Exit enter 9 ↵

34 Delete SOC from existing TL1 Primary Router Configuration, by entering:

3↵
The following message appears:
Enter the RemoteOPCName for TL1 Interface Primary Router
Service(END):
35 Enter the RemoteOPCName, by entering:
OPC48011P ↵ (example only, your OPC name will be different)
The following message appears:
Enter the RemoteOPCName for TL1 Interface Primary Router
Service(END):
36 Continue to enter all the RemoteOPCNames, when you are finished enter:
end ↵
The following message appears:
The SOC’s deleted are

The Remote OPC : OPC48011P (example only)

The TIDs deleted : OPC48011P (example)

Do you wish to continue? (Yes/No):

37 Enter yes ↵ to continue, or no ↵ to end.
Go to step 33.
—continued—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

5-56 TL1 commissioning

Procedure 5-7 (continued)

Configuring and enabling the TL1 Interface Router Service over X.25 or TCP/IP

Step Action

38 Delete TID from existing TL1 Primary Router Configuration, by entering:

4↵
The following message appears:
Enter the TID to be removed from Primary Router
Service(END):
39 Enter the TID, by entering:
TIDNAME ↵ (example only, your TID will be different)
The following message appears:
Enter the TID to be removed from Primary Router
Service(END):
40 Continue to enter the TIDs to be deleted from the primary router. When you
are finished enter:
end ↵
The following message appears:
The Remote OPC : OPC48011P (example only)
The TIDs deleted : TIDNAME (example)

Do you wish to continue? (Yes/No):

41 Enter yes ↵ to continue, or no ↵ to end.
Go to step 33.
42 List the TIDs under SOC, by entering:
5↵
The following message appears:
Enter the RemoteOPCName for TL1 Interface Primary Router
Service(END):
43 Enter the RemoteOPCName for TL1 Interface Primary Router Service, by
entering:
OPC92755P ↵ (example only, your OPC name will be different)
The following message appears:
The RemoteOPC : OPC92755P

The TargetIDentifer : OPC92755P

The TargetIDentifer : A1
The TargetIDentifer : A2

Enter the RemoteOPCName for TL1 Interface Primary Router

Service(END):
44 Continue to enter the RemoteOPCNames, when you are finished enter:
end ↵
—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 TL1 commissioning 5-57

Procedure 5-7 (continued)

Configuring and enabling the TL1 Interface Router Service over X.25 or TCP/IP

Step Action

45 Go to step 33.
46 Add SOC to existing TL1 Primary Router Configuration, by entering:
1↵
The following message appears:
Enter the RemoteOPCName for TL1 Interface Primary Router
Service(END):
47 Enter the RemoteOPCName for TL1 Interface Primary Router Service, by
entering:
OPC92755P ↵ (example only, your OPC name will be different)
The following message appears:
Enter the TID for TL1 Interface Primary Router
Service (END):
48 Enter the TID, by entering:
TIDNAME1 ↵ (example only, your TID will be different)
The following message appears:
Enter the TID for TL1 Interface Primary Router
Service (END):
49 Continue to enter all the TIDs, when you are finished enter:
end ↵.
The following message appears:
Enter the RemoteOPCName for TL1 Interface Primary Router Service(END)
50 Continue to enter all the TIDs, when you are finished enter:
end ↵.
The following message appears:
THE SOCs added are

The RemoteOPC : OPC92755P

The TIDs added: TIDNAME1

Do you wish to continue? (Yes/No):

51 Enter yes ↵ to continue, or no ↵ to end.

If you entered YES, the following message appears:

Modifying the database ...

Go to step 33.
—continued—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

5-58 TL1 commissioning

Procedure 5-7 (continued)

Configuring and enabling the TL1 Interface Router Service over X.25 or TCP/IP

Step Action

52 Add TID to existing TL1 Primary Router Configuration, by entering:

2↵
The following message appears:
Enter the RemoteOPCName to which you want to add TID for
TL1 Interface Primary Router Service (END):
53 Enter the RemoteOPCName.
An example of an RemoteOPCName is OPC92755P
The following message appears:
Enter the TID for TL1 Interface Primary Router
Service (END):
54 Enter the TID, by entering:
TIDNAME1 ↵ (example only, your TID will be different)
The following message appears:
Enter the TID for TL1 Interface Primary Router
Service (END):
55 Continue to enter all the TIDs, when you are finished enter:
end ↵
The following message appears:
THE TIDs added are

The RemoteOPC : OPC92755P

The TIDs added: TIDNAME1

Do you wish to continue? (Yes/No):

—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 TL1 commissioning 5-59

Procedure 5-7 (continued)

Configuring and enabling the TL1 Interface Router Service over X.25 or TCP/IP

Step Action

56 Enter yes ↵ to continue, or no ↵ to end.

If you entered YES, the following message appears:
Modifying the database ...

Go to step 33.
Configure TIRS over X.25
57 Configure TIRS over X.25, by entering:
1↵
The following TL1 Interface Router Services over X.25 menu appears.
*****************************************************
* TL1 Interface Router Services over X.25 Main Menu *
*****************************************************
1 Primary Router Service Configuration
2 Backup Router Service Configuration
8 Return to Main Menu
9 Exit

Enter the number for your selection:

58 Select your next step:

If you want to Then

configure the primary router service go to step 60
configure the backup router service go to step 59
return to the main menu enter 8 ↵ and
go to step 3
exit enter 9 ↵

59 Configure the backup router service, by entering:

2↵
Go to step 60 and follow the procedure steps for configuring the primary
router service.
Note: For backup router service, the computer screens and procedure steps
are very similar to the screens and steps for the primary router service. The
only difference is the word “backup” will appear instead of the word “primary”
for all screens and text.
—continued—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

5-60 TL1 commissioning

Procedure 5-7 (continued)

Configuring and enabling the TL1 Interface Router Service over X.25 or TCP/IP

Step Action

60 Begin the TL1 primary router service configuration, by entering:

1↵
The following TL1 Interface Router Services over X.25 menu appears.
***************************************************
* TL1 Primary Router Configuration over X.25 Menu *
***************************************************
1 TL1 Primary Router Protocol Identifier
Configuration
2 TL1 Primary Router Service Configuration
3 Enable TL1 Primary Router Service
4 Disable TL1 Primary Router Service
5 List the TL1 Primary Router Configuration
6 List the TL1 Primary Router Protocol Identifier
Configuration
7 Modify TL1 Primary Router Configuration
8 Return to Main Menu
9 Exit

Enter the number for your selection:

61 Select your next step:

If you want to Then

Configure TL1 Primary Router Protocol Identifier go to step 62
Configure TL1 Primary Router Service go to step 65
Enable TL1 Primary Router Service go to step 72
Disable TL1 Primary Router Service go to step 73
List the TL1 Primary Router Configuration go to step 74
List the TL1 Primary Router Protocol Identifier go to step 76
Configuration
Modify TL1 Primary Router Configuration go to step 77
return to the main menu enter 8 ↵ and
go to step 3
Exit enter 9 ↵

Enter the number for your selection:

—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 TL1 commissioning 5-61

Procedure 5-7 (continued)

Configuring and enabling the TL1 Interface Router Service over X.25 or TCP/IP

Step Action

62 Configure Primary Router Protocol Identifier, by entering:

1↵
The following message appears.
Enter the number of bytes for X.25 protocol id of TL1
Primary Router Service:
63 Enter the number of bytes (maximum of 8) and press:
4 ↵ (this is an example only; your number of bytes may be different)
The following message appears.
Enter the X.25 protocol id for TL1 Primary Router:
64 Enter the X.25 protocol id and press:
00000007 ↵ (this is an example only; your X.25 protocol id may be different)
Note: The protocol id is in hexadecimal with the number of characters
entered always double the number of bytes (maximum of 16 characters). A
message indicating an error appears if the protocol ID of the current
OPTera Long Haul 1600 TL1 is NULL, If the protocol id has already been
used, or if the protocol id does not equal the number of bytes.
The following message appears.
The Protocol Id 00000007 configured successfully.
Go to step 61.
65 Configure TL1 Primary Router Service, by entering:
2↵
The following message appears.
Enter the RemoteOPCName for TL1 Interface Primary Router
Service (END):
66 Enter the RemoteOPCNames:
The following message appears:
Enter the TID for TL1 Interface Primary Router Service
(END):
Note: The format is OPCxxxxxP, where xxxxx is a 9-character alphanumeric
string, and P stands for primary OPC. Replace the P with B for a backup OPC.
An example of a RemoteOPCName is OPC92755P.
67 Enter the TIDs that correspond to span of control of the OPC above, and
press the Return key.
—continued—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

5-62 TL1 commissioning

Procedure 5-7 (continued)

Configuring and enabling the TL1 Interface Router Service over X.25 or TCP/IP

Step Action

68 Repeat step 67 until all the TIDs have been entered, then enter:
end ↵
The following message appears (example only).
Enter the RemoteOPCName for TL1 Interface Primary Router Service
(END):
69 Select an action from the following table:
If you would like to Then go to
enter another remote OPC name and the TIDs in its step 66
span of control
quit entering another remote OPC and its TIDs step 71

70 To quit entering another OPC, enter:

end ↵
A message similar to the following appears.
The TL1 Primary Router over X.25 Configuration you have
Configured:

The RemoteOPC : OPC48011P

The TID : OPC48011P
The TID : 4801

Do you wish to Update the Configuration? (Yes/No)

71 Update (or do not update) the configuration, by entering:
yes ↵ or no ↵
Go to step 61.
72 Enable TL1 Primary Router Service, by entering:
3↵
The following message appears.
TL1 Primary Router Service over X.25 Enabled
Successfully.
Go to step 61.
73 Disable TL1 Primary Router Service, by entering:
4↵
The following message appears.
TL1 Primary Router Service over X.25 Disabled
Successfully.
Go to step 61.
—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 TL1 commissioning 5-63

Procedure 5-7 (continued)

Configuring and enabling the TL1 Interface Router Service over X.25 or TCP/IP

Step Action

74 List the TL1 Primary Router Configuration, by entering:

5↵
The following message appears (example only).
The Configuration
*****************

The RemoteOPC : OPC92755P

The TargetIDentifer : OPC92755P
The TargetIDentifer : ABC
The TargetIDentifer : EFG

The RemoteOPC : OPC92599P

The TargetIDentifer : OPC92599P
The TargetIDentifer : TRALEE
The TargetIDentifer : 9259
The TargetIDentifer : WESTPORT

Press Return to continue

75 Press return the Return key.

Go to step 61.
76 List the TL1 Primary Router Protocol Identifier Configuration, by entering:
6↵
The following message appears (numbers are example only).
Number of bytes of X.25 protocol id : 4
Protocol Id : 00000007
Go to step 61.
—continued—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

5-64 TL1 commissioning

Procedure 5-7 (continued)

Configuring and enabling the TL1 Interface Router Service over X.25 or TCP/IP

Step Action

77 Modify TL1 Primary Router Configuration, by entering:

7↵

The following Modify Primary Router Configuration menu appears.

***************************************
* Modify Primary Router Configuration *
***************************************
1 Add SOC to Existing TL1 Primary Router Configuration
2 Add TID to Existing TL1 Primary Router Configuration
3 Delete SOC from Existing TL1 Primary Router
Configuration
4 Delete TID from existing TL1 Primary Router
Configuration
5 List the TIDs under SOC
8 Return to Main Menu
9 Exit

Enter the number for your selection:

78 Select your next step:

If you want to Then

Add SOC to Existing TL1 Primary Router Configuration go to step 90
Add TID to existing TL1 Primary Router Configuration go to step 96
Delete SOC from Existing TL1 Primary Router Configuration go to step 80
Delete TID from Existing TL1 Primary Router Configuration go to step 83
List the TIDs under SOC go to step 87
Return to Main Menu enter 8 ↵ and
go to step 61
Exit enter 9 ↵

79 Delete SOC from existing TL1 Primary Router

Configuration, by entering:
3↵
The following message appears:
Enter the RemoteOPCName for TL1 Interface Primary Router
Service(END)
—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 TL1 commissioning 5-65

Procedure 5-7 (continued)

Configuring and enabling the TL1 Interface Router Service over X.25 or TCP/IP

Step Action

80 Enter the RemoteOPCName, by entering:

OPC48011P ↵ (example only, your OPC name will be different)
The following message appears:
Enter the RemoteOPCName for TL1 Interface Primary Router
Service(END):
81 Continue to enter all the RemoteOPCNames, when you are finished enter:
end ↵
The following message appears:
The SOC’s deleted are

The Remote OPC : OPC48011P (example only)

The TIDs deleted : OPC48011P (example only)

Do you wish to continue? (Yes/No):

82 Enter yes ↵ to continue, or no ↵ to end.

If you entered YES, the following message appears:

Modifying the database ...

Go to step 78.
83 Delete TID from existing TL1 Primary Router Configuration, by entering:
4↵
The following message appears:
Enter the TID to be removed from Primary Router
Service(END):
84 Enter the TID, by entering:
TIDNAME ↵ (example only, your TID will be different)
The following message appears:
Enter the TID to be removed from Primary Router
Service(END):
—continued—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

5-66 TL1 commissioning

Procedure 5-7 (continued)

Configuring and enabling the TL1 Interface Router Service over X.25 or TCP/IP

Step Action

85 Continue to enter all the TIDs, when you are finished enter end ↵
The following message appears:
The RemoteOPC : OPC48011P (example only)

The TIDs deleted: TIDNAME (example only)

Do you wish to continue? (Yes/No):

86 Enter yes ↵ to continue, or no ↵ to end.
Go to step 78.
87 List the TIDs under SOC, by entering:
5↵
The following message appears:
Enter the RemoteOPCName for TL1 Interface Primary Router
Service(END):
88 Enter the RemoteOPCName for TL1 Interface Primary Router Service, by
entering:
OPC92755P ↵ (example only, your OPC name will be different)
The following message appears:
The RemoteOPC : OPC92755P

The TargetIDentifer : OPC92755P

The TargetIDentifer : A1
The TargetIDentifer : A2

Enter the RemoteOPCName for TL1 Interface Primary Router

Service(END):
89 Continue to enter all the RemoteOPCNames, when you are finished enter:
end ↵.
—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 TL1 commissioning 5-67

Procedure 5-7 (continued)

Configuring and enabling the TL1 Interface Router Service over X.25 or TCP/IP

Step Action

90 Add SOC to existing TL1 Primary Router Configuration, by entering:

1↵
The following message appears:
Enter the RemoteOPCName for TL1 Interface Primary Router
Service(END):
91 Enter the RemoteOPCName for TL1 Interface Primary Router Service, by
entering:
OPC92755P ↵ (example only, your OPC name will be different)
The following message appears:
Enter the TID for TL1 Interface Primary Router
Service (END):
92 Enter the TID, by entering:
TIDNAME1 ↵ (example only, your TID will be different)

The following message appears:

Enter the TID for TL1 Interface Primary Router
Service (END):
93 Continue to enter all the TIDs, when you are finished enter END ↵.
The following message appears:
Enter the RemoteOPCName for TL1 Interface Primary Router
Service(END):
94 Continue to enter all the RemoteOPCNames, when you are finished enter:
end ↵.
The following message appears:
THE SOCs added are

The RemoteOPC : OPC92755P

The TIDs added: TIDNAME1

Do you wish to continue? (Yes/No):

—continued—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

5-68 TL1 commissioning

Procedure 5-7 (continued)

Configuring and enabling the TL1 Interface Router Service over X.25 or TCP/IP

Step Action

95 Enter yes ↵ to continue, or no ↵ to end.

If you entered YES, the following message appears:

Modifying the database ...

Go to step 78.
96 Add TID to existing TL1 Primary Router Configuration, by entering:
1↵
The following message appears:
Enter the RemoteOPCName to which you want to add TID for
TL1 Interface Primary Router Service (END) :
97 Enter the RemoteOPCName, by entering:
OPC92755P ↵ (example only, your OPC name will be different)
98 Continue to enter all the RemoteOPCNames, when you are finished enter:
end ↵.
The following message appears:
Enter the TID for TL1 Interface Primary Router
Service (END):
99 Enter the TID, by entering:
TIDNAME1 ↵ (example only, your TID will be different)
The following message appears:
Enter the TID for TL1 Interface Primary Router
Service (END):
100 Continue to enter all the TIDs, when you are finished enter end ↵.
The following message appears:
THE TIDs added are

The RemoteOPC : OPC92755P

The TIDs added: TIDNAME1

Do you wish to continue? (Yes/No):

101 Enter yes ↵ to continue, or no ↵ to end.

If you entered YES, the following message appears:

Modifying the database ...
Go to step 78.
—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 TL1 commissioning 5-69

Procedure 5-7 (continued)

Configuring and enabling the TL1 Interface Router Service over X.25 or TCP/IP

Step Action

Enable or disable a TL1 session over the TL1 Interface Router Service
102 Select your next step:

If you would like to Then go to

enable a TL1 session over the TL1 Interface Router Service step 103
disable a TL1 session over the TL1 Interface Router Service step 108

Enable TL1 session

103 Ensure that a physical X.25/TCP/IP connection is present and configured
correctly between the operations system and OPC.
104 Ensure that the operations system X.121/TCP/IP addresses have been
configured on the Gateway and Remote OPCs and that the TL1 Interface
Router Service has been provisioned on the Gateway OPC.
105 Establish a TL1 session over the TL1 Interface Router Service. Enter the
following command from an operations system TL1 window:
act-user:<tid>:<uid>:<ctag>::<password>; ↵
Note: The act-user command has to be sent to a TID in each OPC SOC to
connect to each SOC.

where
<tid> is the target identifier. The tid must be specified and it
should be a valid identifier in the OPC’s span of control.
<uid> is the user id. The following conditions apply on which
type of user id can be used:
When TL1 SECURITY is DISABLED:
1.admin user
2.root user
When TL1 SECURITY is ENABLED:
1.root user
2.admin user
3.tl1usr user

<ctag> is the correlation tag.

<password> is the password for the corresponding user id.

TL1 Interface Description 323-1801-190 Rel 3 July 2000

5-70 TL1 commissioning

Procedure 5-7 (continued)

Configuring and enabling the TL1 Interface Router Service over X.25 or TCP/IP

Step Action

106 Send a TL1 command using a valid TID from the OPC’s SOC to verify that the
connection has been established. Enter:
rtrv-hdr:<tid>::<ctag>; ↵
where
<tid> is the target identifier. The tid must be specified and it should
be a valid identifier in the OPC’s span of control.
<ctag> is the correlation tag.

A message similar to the following appears.

rtrv-hdr:NE1::0100;

NE1 97-09-24 11:40:23

M 0100 COMPLD
;

107 Verify that a ‘COMPLD’ is returned from the RTRV-HDR response output
message.
Go to step 3.
Disable the TL1 session
108 Disable a TL1 session over the TL1 Interface Router Service. Enter in the
following command from an operations system TL1 window:
canc-user:<tid>::<ctag>; ↵
where
<tid> is the target identifier. The tid must be specified and it should
be a valid identifier in the OPC’s span of control.
<ctag> is the correlation tag.

A message appears in the operations system TL1 window stating that

“Remote session dropped”.
Go to step 3.
—end—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 TL1 commissioning 5-71

Procedure 5-8
Configuring TL1 over TCP/IP
Use this procedure for configuring TL1 over TCP/IP.

Before you start

• Obtain a userID and password that accesses the TL1 Configuration tool from the User Session Manager.

Procedure tasks
• Configure TL1 over TELNET/TCP/IP (step 5).
• Configure TL1 over TRUE TCP/IP (step 8).
• Unconfigure TL1 over TELNET/TCP/IP (step 16).
• Unconfigure TL1 over TRUE TCP/IP (step 19).
• Display TL1 TCP/IP port configurations (step 22).

Expected results
• TL1 will be configured over TELNET/TCP/IP or TRUE TCP/IP.
• If required, TL1 will be unconfigured over TELNET/TCP/IP or TRUE TCP/IP.
• TL1 TCP/IP configurations will be displayed.
• If the expected results do not occur:
— Ensure that you have a userID and password that allows you to access the TL1 Configuration tool
from the User Session Manager.
— Verify that you have chosen the correct options from the TL1 over TCP/IP Port Configuration Menu.
— Verify that you have entered the correct data for each step (port number, OSS name, IP address,
etc.).

—continued—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

5-72 TL1 commissioning

Procedure 5-8 (continued)

Configuring TL1 over TCP/IP

Action
Step Action

1 Log in to the OPC using the admin userID and open the TL1 Configuration
tool from the User Session Manager. If you do not know how to do this, see
User Interface Connection Procedures, 323-1801-301.
The TL1 Configuration Main Menu appears.
2 Configure TL1 over TCP/IP, by entering:
7↵
The following message appears.
This option will update the files
/etc/services,/etc/inetd.conf
and /usr/adm/inetd.sec. You can take a backup of the above
files
with extension .backup before proceeding further. Choose
Yes/No.

Do you wish to take the backup? (Yes/No):

3 Confirm the backup request, by entering:
y↵
The following TL1 Over TCP/IP Port Configuration menu appears.
TL1 Over TCP/IP Port Configuration Menu
****************************************
1 Configure TL1 Over TELNET/TCP/IP
2 Configure TL1 Over TRUE TCP/IP
3 Unconfigure TL1 Over TELNET/TCP/IP
4 Unconfigure TL1 Over TRUE TCP/IP
5 Display TL1 TCP/IP Port Configuration
8 Return to Main Menu
9 Exit

Enter the number for your selection:

—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 TL1 commissioning 5-73

Procedure 5-8 (continued)

Configuring TL1 over TCP/IP

Step Action

4 Select your next step:

If you are Then go to

configuring TL1 over TELNET/TCP/IP step 5
configuring TL1 over TRUE TCP/IP step 8
unconfiguring TL1 over TELNET/TCP/IP step 16
unconfiguring TL1 over TRUE TCP/IP step 19
displaying TL1 TCP/IP port configuration step 22
returning to the main menu step 23
exiting step 24

Configure TL1 over TELNET/TCP/IP

5 Configure TL1 over TELNET/TCP/IP, by entering:
1↵
The following message appears.
This option allows for configuring a port for Telnet
operations. Select a port number > 5000 && <= 65535.

Enter port number:

6 Enter the port number for your telnet operations and press:
↵
You are prompted to confirm your request.
7 Confirm your request, by entering:
y↵
Go to step 4.
Configure TL1 over TRUE TCP/IP
8 Configure TL1 over TRUE TCP/IP, by entering:
2↵
The following message appears.
This option allows for configuring a port for TL1 over
TRUE TCP/IP
operations. Select a port number > 5000 and <= 65535.

Enter port number:

—continued—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

5-74 TL1 commissioning

Procedure 5-8 (continued)

Configuring TL1 over TCP/IP

Step Action

9 Enter the port number for your TRUE TCP/IP operations and press:
↵
A message prompting you to enter the OSS for NMA or OPS appears.
Enter OSS type [NMA or OPS]:
10 Enter an OSS type (“NMA” or “OPS”) and press:
↵
A message appears asking whether you want to allow connections from all
OSS hosts.
11 Select your next step:

If you are Then

allowing connections from answer by entering: yes ↵. Go to step 14.
all OSS hosts
not allowing connections answer by entering: no ↵. You must then enter
from all OSS hosts a list of IP addresses from which the TL1 over
TRUE TCP/IP connection can be established.
Go to step 12.

12 Enter an IP address at each IP prompt and press:

↵
13 To end the input of the IP addresses from which TL1 over TRUE TCP/IP
connections can be established, press:
0↵
14 Enter “yes” to confirm the configuration or “no” to cancel the configuration and
press:
↵
15 Go to step 4.
Unconfigure TL1 over TELNET/TCP/IP
16 Unconfigure TL1 over TELNET/TCP/IP, by entering:
3↵
The following message appears.
This option allows for Unconfiguring a port for TL1 TCP/IP
operations. Select a port number > 5000 && <= 65535.

Enter port number:

—continued—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

 TL1 commissioning 5-75

Procedure 5-8 (continued)

Configuring TL1 over TCP/IP

Step Action

17 Enter the port number that you want to unconfigure and press:
↵
A confirmation asking you whether you want to continue appears.
18 Confirm the request, by entering:
y↵
The TL1 over TCP/IP Port Configuration menu appears.
Go to step 4.
Unconfigure TL1 over TRUE TCP/IP
19 Unconfigure TL1 over TRUE TCP/IP, by entering:
4↵
The following message appears.
This option allows for Unconfiguring a port for TL1 TCP/IP
operations. Select a port number > 5000 && <= 65535.

Enter port number:

20 Enter the port number that you want to unconfigure and press:
↵
A confirmation asking you whether you want to continue appears.
21 Confirm the request, by entering:
y↵
The TL1 Over TCP/IP Port Configuration menu appears.
Go to step 4.
Display TL1 TCP/IP port configurations
22 Display the TL1 TCP/IP port configurations, by entering:
5↵
After the display has been shown, the TL1 Over TCP/IP Port Configuration
menu appears.
Go to step 4.
Return to the main menu
23 Return to the Main Menu, by entering:
8↵
The TL1 Configuration Main Menu appears.
—continued—

TL1 Interface Description 323-1801-190 Rel 3 July 2000

5-76 TL1 commissioning

Procedure 5-8 (continued)

Configuring TL1 over TCP/IP

Step Action

Exit the tool

24 Exit the TL1 Configuration tool, by entering:
9↵
The TL1 Configuration tool is closed and the User Session Manager
reappears.
—end—

OPTera Long Haul 1600 323-1801-190 Rel 3 Standard July 2000

Nortel Networks

OPTera Long Haul 1600

Optical Line System
TL1 Interface Description
Copyright  2000 Nortel Networks, All Rights Reserved.

The information contained herein is the property of Nortel

Networks and is strictly confidential. Except as expressly
authorized in writing by Nortel Networks, the holder shall keep all
information contained herein confidential, shall disclose it only to
its employees with a need to know, and shall protect it, in whole
or in part, from disclosure and dissemination to third parties with
the same degree of care it uses to protect its own confidential
information, but with no less than reasonable care. Except as
expressly authorized in writing by Nortel Networks, the holder is
granted no rights to use the information contained herein.

Nortel Networks, the Nortel Networks logo, the Globemark, How

the World Shares Ideas, S/DMS TransportNode, OPTera,
Preside, and Unified Networks are trademarks are trademarks of
Nortel Networks.

VT100 is a trademark of Digital Equipment Corporation.

UNIX is a trademark of X/Open Company Ltd.

323-1801-190
Rel 3 Standard
July 2000
Printed in Canada and in the United Kingdom