tl1 reference guide - 323-1059-190.1.r16

NTN465GNNTN465GN 323-1059-190

Nortel

Optical Metro 3500TL1 Reference—Part 1 of 4

What’s inside...Introducing TL1Commands A to ED-zz

See Part 2 for commands ENT-aa to RST-zz

See Part 3 for commands RTRV-aa to RTRV-RINGMAP

See Part 4 for commands RTRV-ROLL-aa to Z

Standard Release 16.0 Issue 1 December 2008

This document is protected by copyright laws and international treaties. All information, copyrights and any other intellectual property rights contained in this document are the property of Nortel Networks. Except as expressly authorized in writing by Nortel Networks, the holder is granted no rights to use the information contained herein and this document shall not be published, copied, produced or reproduced, modified, translated, compiled, distributed, displayed or transmitted, in whole or part, in any form or media.

This information is provided “as is”, and Nortel Networks does not make or provide any warranty of any kind, expressed or implied, including any implied warranties of merchantability, non-infringement of third party intellectual property rights, and fitness for a particular purpose.

Nortel, the Nortel logo, and the Globemark are trademarks of Nortel Networks.

Printed in Canada

Copyright 2000-2008 Nortel Networks, All Rights Reserved

iii

Contents 0

About this document ix

Introducing TL1 1-1TL1 command interface 1-3

TL1 prompt 1-3User authentication 1-3User identifier 1-3Password identifier 1-3Security access level 1-4Target identifier and source identifier 1-5Multiple sessions 1-5

TL1 message notation 1-6Access identifier 1-6Correlation tag 1-6Command structure 1-6Parameter value grouping 1-7Mandatory punctuation 1-7TL1 command acknowledgment 1-7

TL1 message overview 1-7TL1 message types 1-7TL1 command response header 1-8

Editing features 1-10TL1 script file 1-10Online syntax help 1-11

Commands A to ED-zz 2-1ACT-USER 2-8ADD-SOC 2-10ALW-EX-OC12 2-11ALW-EX-OC192 2-13ALW-EX-OC3 2-14ALW-EX-OC48 2-16ALW-MSG-ALL 2-17ALW-MSG-BROADCAST 2-18ALW-SECU-CID 2-19ALW-SECU-USER 2-20ALW-UPGRD 2-21AUD-BLSR 2-22

TL1 Reference—Part 1 of 4 323-1059-190 Standard Rel 16.0 Iss 1 Dec 2008

iv Contents

CANC-INSTALL 2-24CANC-PROV 2-25CANC-PROV-SOC 2-26CANC-PROV-SP 2-27CANC-RINGMAP 2-28CANC-TL1SCRPT-NE 2-29CANC-UPGRD 2-30CANC-USER 2-32CHG-ACCMD-STS1 2-33CHG-ACCMD-STS12C 2-36CHG-ACCMD-STS24C 2-38CHG-ACCMD-STS3C 2-40CHG-ACCMD-STS48c 2-42CHG-ACCMD-T1 2-44CHG-ACCMD-T3 2-46CHG-ACCMD-VT1 2-48CHK-INSTALL 2-50CHK-PROV 2-51CHK-PROV-SOC 2-53CHK-PROV-SP 2-56CHK-RINGMAP 2-59CHK-UPGRD 2-60CLR-ALM-SECU 2-62CLR-LAN-STATS 2-63CMMT-INSTALL 2-64CMMT-PROV 2-65CMMT-PROV-SP 2-66CMMT-RINGMAP 2-67CMMT-ROLL-STS1 2-68CMMT-ROLL-STS12C 2-73CMMT-ROLL-STS24C 2-76CMMT-ROLL-STS3C 2-79CMMT-ROLL-STS48C 2-81CMMT-ROLL-VT1 2-83CMMT-TL1SCRPT-NE 2-86CMMT-UPGRD 2-87CONN-TACC-STS1 2-88CONN-TACC-STS12C 2-92CONN-TACC-STS24C 2-94CONN-TACC-STS3C 2-96CONN-TACC-STS48C 2-98CONN-TACC-T1 2-100CONN-TACC-T3 2-102CONN-TACC-VT1 2-105CONN-TSTSIG-T1 2-108CONN-TSTSIG-T3 2-111DEFRAG-EQPT 2-114DISC-TACC 2-116DISC-TSTSIG-T1 2-118DISC-TSTSIG-T3 2-119DLT-ALM-PROFILE 2-120

Optical Metro 3500 323-1059-190 Standard Rel 16.0 Iss 1 Dec 2008

Contents v

DLT-BANNER 2-122DLT-BLSRRING 2-123DLT-CRS-STS1 2-124DLT-CRS-STS12C 2-128DLT-CRS-STS24C 2-131DLT-CRS-STS3C 2-133DLT-CRS-STS48C 2-136DLT-CRS-VT1 2-138DLT-EC1 2-142DLT-EQPT 2-143DLT-ETH 2-147DLT-FAC 2-149DLT-FC 2-150DLT-FFP-OC12 2-151DLT-FFP-OC192 2-152DLT-FFP-OC3 2-154DLT-FFP-OC48 2-155DLT-GRE 2-157DLT-IPT 2-158DLT-IPTR 2-159DLT-LLSDCC 2-160DLT-OC12 2-161DLT-OC192 2-162DLT-OC3 2-163DLT-OC48 2-164DLT-PROV 2-165DLT-PVC 2-167DLT-RINGMAP 2-168DLT-ROLL-STS1 2-169DLT-ROLL-STS12C 2-174DLT-ROLL-STS24C 2-177DLT-ROLL-STS3C 2-180DLT-ROLL-STS48C 2-183DLT-ROLL-VT1 2-185DLT-SECU-ACCESS 2-189DLT-SECU-BADPID 2-190DLT-SECU-USER 2-191DLT-T1 2-192DLT-T3 2-193DLT-UPGRD 2-194ED-ALM-PROFILE 2-195ED-BLSRRING 2-197ED-COMM 2-198ED-CRS-STS1 2-199ED-CRS-STS12C 2-205ED-CRS-STS24C 2-209ED-CRS-STS3C 2-212ED-CRS-STS48C 2-216ED-CRS-VT1 2-219ED-DAT 2-224ED-DFLT-AINS 2-225


vi Contents

ED-EC1 2-226ED-ETH 2-227ED-FC 2-232ED-FFP-OC12 2-234ED-FFP-OC192 2-236ED-FFP-OC3 2-238ED-FFP-OC48 2-240ED-IP 2-242ED-LLSDCC 2-243ED-LLX25 2-246ED-NETYPE 2-247ED-OC12 2-248ED-OC192 2-251ED-OC3 2-254ED-OC48 2-258ED-PMCONFIG-EC1 2-261ED-PMCONFIG-ETH 2-263ED-PMCONFIG-FC 2-265ED-PMCONFIG-OC12 2-267ED-PMCONFIG-OC192 2-269ED-PMCONFIG-OC3 2-271ED-PMCONFIG-OC48 2-273ED-PMCONFIG-STS1 2-275ED-PMCONFIG-STS12C 2-278ED-PMCONFIG-STS24C 2-281ED-PMCONFIG-STS3C 2-283ED-PMCONFIG-STS48C 2-286ED-PMCONFIG-WAN 2-288ED-PTX25 2-291ED-ROLL-STS1 2-293ED-ROLL-STS12C 2-297ED-ROLL-STS24C 2-300ED-ROLL-STS3C 2-303ED-ROLL-STS48C 2-307ED-ROLL-VT1 2-310ED-SECU-PID 2-314ED-SECU-USER 2-316ED-SITE-DSM 2-319ED-STS1 2-320ED-STS12C 2-323ED-STS24C 2-325ED-STS3C 2-327ED-SYS 2-329ED-T1 2-331ED-T3 2-336ED-TARP-CONFIG 2-338ED-TARP-TBL 2-341ED-TOD-MODE 2-343ED-ULSDCC (network element) 2-345ED-ULSDCC (network processor) 2-347ED-ULX25 2-349


Contents vii

ED-VC 2-352ED-WAN 2-354


viii Contents


ix323-1059-190

About this document 0

You are reading Part 1 of the TL1 Reference for Nortel Optical Metro 3500 Release 16.0.

Part 1 covers the TL1 commands from A to ED-zz. Part 1 also provides an introduction to the TL1 interface.

Part 2 covers the TL1 commands from ENT-aa to RST-zz.

Part 3 covers the TL1 commands from RTRV-aa to RTRV-RINGMAP.

Part 4 covers the TL1 commands from RTRV-ROLL-aa to Z. Part 4 also covers error codes and messages.

Supported softwareThis document supports the software release for Nortel Optical Metro 3500 Release 16.0

Supported hardwareThis document supports the Optical Metro 3500 shelf.

ATTENTIONEach part of the TL1 Reference has its own table of contents, which contains topics found in that part only. Part 2 continues sequential chapter numbering from Part 1. Part 3 continues sequential chapter numbering from Part 2. Part 4 continues sequential chapter numbering from Part 3.


x About this document

Hardware naming conventionsThe following naming conventions are used throughout this document to identify the Optical Metro hardware:

• the extended shelf processor (SPx) is referred to as the shelf processor

• the extended network processor (NPx) is referred to as the network processor

• starting with Release 13.0, optical interface circuit packs include both SONET and SDH terminology on their faceplates labels (OC-n/STM-n). However, only SONET terminology is used in references to optical interface circuit packs in this NTP. For example, this document refers to OC-12x4 STS circuit packs, but the faceplate label for this circuit pack is OC-12x4/STM-4x4 STS

AudienceThe following members of your company are the intended audience of this Nortel technical publication (NTP):

• planners

• provisioners

• network administrators

• transmission standards engineers

StandardsThe Telecommunications Industry Association (TIA) and the Electronics Industries Alliance (EIA) accepted RS-232 as a standard in 1997 and renumbered this standard as TIA/EIA-232. In this document, RS-232 is used to reflect current labels on the hardware and in the software for the Optical Metro 3500.


About this document xi

Optical Metro 3500 NTP libraryEX1879p

Planning and Ordering Guide(NTRN10AU)

ProvisioningSynchronization(323-1059-310)

Performance Monitoring

(323-1059-510)

Network Surveillance

(323-1059-520)

Alarm and Trouble Clearing(323-1059-543)

About theOptical Metro 3500

NTP Library(323-1059-090)

Operations,Administration

and Provisioning

MaintenanceTL1 ReferenceGuides andShelf Setup

Installation (323-1059-201)

Commissioning(323-1059-210)

System Testing (323-1059-222)

BandwidthManagement

(323-1059-320)

ProvisioningEquipment and

Facilities(323-1059-350)

ProtectionSwitching

(323-1059-311)

Security andAdministration

(323-1059-302)

SystemReconfiguration(323-1059-224)

Supportingdocumentation for the OpticalMetro 3500Library

Optical Packet Edge System Planning

Guide(NTRN10YS)

Optical Packet Edge System Network Applications and

Management(NTRN11YS)

Optical Packet Edge System User Guide

(NTN465YS)

Change ApplicationProcedures

(CAPs)

DataCommunicationsNetwork Planning

Guide(NTR710AM)

Network Interworking

Guide(NTCA68CA)

Site ManagerPlanning and

Installation Guide,Rel 10.0

(NTNM35KA)

TL1 Reference (323-1059-190)

Optical Metro3000 series

DWDM ApplicationGuide

(NTRN12AA)


xii About this document

Technical support and informationFor technical support and information from Nortel, refer to the following table.

Technical Assistance Service

For service-affecting problems:For 24-hour emergency recovery or software upgrade support, that is, for:

• restoration of service for equipment that has been carrying traffic and is out of service

• issues that prevent traffic protection switching

• issues that prevent completion of software upgrades

North America: 1-800-4NORTEL (1-800-466-7835)

International: 001-919-992-8300

For non-service-affecting problems:For 24-hour support on issues requiring immediate support or for 14-hour support (8 a.m. to 10 p.m. EST) on upgrade notification and non-urgent issues.

North America:1-800-4NORTEL (1-800-466-7835)

Note: You require an express routing code (ERC). To determine the ERC, see our corporate Web site at www.nortel.com. Click on the Express Routing Codes link.

International: Varies according to country. For a list of telephone numbers, see our corporate Web site at www.nortel.com. Click on the Contact Us link.

Global software upgrade support: North America:1-800-4NORTEL (1-800-466-7835)

International: Varies according to country. For a list of telephone numbers, see our corporate Web site at www.nortel.com. Click on the Contact Us link.


1-1323-1059-190

Introducing TL1 1-

This chapter provides an introduction to the Transaction Language 1 (TL1) used on the network element and the network processor.

TL1 is a common language protocol for messages exchanged between network elements and network processors in an Optical Metro 3500 Multiservice Platform series network. TL1 is the primary user interface to the network element and network processor, and is used to operate, administer, maintain, and provision the network.

The TL1 implementation on the network element and network processor allows the user to perform the following functions:

• commissioning

• testing

• provisioning

• alarm and network surveillance

• performance monitoring

• protection switching

• network security and administration

• inventory retrieval

Standards compliance The TL1 interface complies with the Bellcore standard TR-TSY-439, Operations Technology Generic Requirements (OTGR):

• Section 12.3, TR-TSY-833, Issue 3: Network Maintenance - Network Element and Transport Surveillance Messages

• Section 12.2, TR-NWT-199, Issue 2: Operations Application Messages and Memory Administration Messages, Specifications of Memory Administration at the OS/NE Interface

• Section 12.5, TR-NWT-835, Issue 2: Operations Application Messages - Network Element (NE) Security Parameter Administration Messages


1-2 Introducing TL1

TL1 user interface on the network elementThe TL1 interface is a text-based, single command line user interface.

On the shelf, the TL1 user interface is obtained by connecting a VT100 or other ANSI, standard terminal to a DB-9, RS-232, DTE, craft access port, or to the DB-25, RS-232, DCE, craft access port on the shelf processor circuit pack.

All network elements in the system can be accessed from any other network element in the system.

TL1 user interface on the network processorThe TL1 interface on the network processor allows the retrieval of all TL1 alarms and events from the network elements in the network processor span of control. The TL1 interface also allows provisioning of network processor facilities, X.25 parameters, an IP address and up to three manual area addresses.

The network processor requires one of the following connections:

• backplane connection from the co-located shelf processor to the network processor through OSI/Ethernet (10base T). You can access the network processor using a VT100 compatible terminal connected to any network element in the system. You do not have to log in to the local network element to log in to the network processor

• Site Manager to network processor through TCP/IP over Ethernet (10base T)

• Optical Network Manager Applications Platform or Optical Network Manager Multiservice Managed Object Agent to network processor through TCP/IP over Ethernet (10base T)

• an operations support system (OSS) to network processor through the X.25 port

• a straight Ethernet connection through the central office LAN (COLAN)


Introducing TL1 1-3

TL1 command interface TL1 prompt

The TL1 prompt is indicated by a less than sign (<) on the left side of the screen. The prompt appears in response to the semi-colon (;) from the terminal keyboard. TL1 commands are executed from the TL1 prompt.

Note: TL1 uses a semi-colon (;), not a carriage return, as a line terminator. The semi-colon is shown at the end of all TL1 commands in this guide.

User authenticationYou can log in to a network processor or network element using remote authentication, challenge-response authentication, or local authentication. The methods available depend on the state of centralized security administration (CSA) and on the provisioned alternate method, as follows:

• If CSA is enabled, you can log in using remote authentication or challenge-response authentication.

• If CSA is disabled or is enabled but unavailable, you can log in using local authentication or challenge-response authentication if local authentication is provisioned as the alternate method. If challenge-response is provisioned as the alternate method, only challenge-response is available (local accounts are disabled). By default, challenge-response authentication is the alternate method when CSA is enabled and local authentication is the alternate method when CSA is disabled.

To log in using remote or local authentication, you must have a valid user identifier (UID) and password identifier (PID).

To log in using challenge-response authentication, enter the UID to partially log in to the network processor or network element. Then, use the RTRV-CHALLENGE and ENTER-CHALLENGE-RESPONSE commands to complete the login. See RTRV-CHALLENGE on page 4-69 and ENT-CHALLENGE-RESPONSE on page 3-12.

For more information on authentication modes, refer to the Planning and Ordering Guide (NTRN10AU) and to the TL1 commands used to set CSA attributes, UIDs, and PIDs.

User identifier The UID is a unique non-confidential name to identify each authorized system user. UIDs are between 1 and 10 alphanumeric characters. It is essential to have a UID to activate a user login session.

Password identifier The PID is a confidential code to qualify the authorized system user to access the account specified by a UID. It is essential to use the PID for local or remote authentication or to change the current PID.


1-4 Introducing TL1

PIDs must meet the following:

• The PID must be between 8 and 10 characters.

• The PID can include alphabetical characters, numbers, and the following symbols:

! “ # $ % ` ( ) * + - . / < = > @ [ ] ^ _ ' { | } ~

• The PID must contain at least one alphanumeric character and one non-alphanumeric character (such as one of the above symbols or a number).

• The PID cannot contain any of the following characters: semicolon (;), colon (:), ampersand (&), comma (,), spaces (deleted as entered), control characters, and question mark (?).

• The PID cannot contain the associated user identifier (UID).

• You cannot use any of your previous five passwords or any words that are in the list of unusable passwords. The list of unusable passwords is set with the ENT-SECU-BADPID command and can be retrieved with the RTRV-SECU-BADPID command.

• A double quote (“) entered in the PID must be preceded by a backslash (\). The backslash is considered as a character in the length of the password.

• Carriage returns (<Enter>) are ignored.

Security access level When logging in to a network element or a network processor, an account name and password are used. Each account is created by the user of a master account. During account creation a security access level is assigned from 1 through 5 on the network element or the network processor. This number is called the user privilege code (UPC). The UPC security levels offer access to a range of task execution capabilities as follows:

• Surveillance - level 5, allows surveillance of all network elements in the network processor span of control. A user account with a level 5 UPC is valid only under the following circumstances:

— a login to the network processor from Optical Network Manager Applications Platform or Optical Network Manager Multiservice Managed Object Agent

— a login to the network processor if the network processor is the gateway to the network

Note 1: A user account with a level 5 UPC can only be used to log into a network processor using a local connection.

Note 2: Starting with Release 12, up to three Level 5 users can log into and have access to the same network processor at the same time if the UIDs are different. Each of these Level 5 users can access and manage all 16 network elements within the span of control of this network processor.


Introducing TL1 1-5

Note 3: Autonomous messages will not be displayed to the level 5 user, who logs in from the TL1 interface, until you issue the ALW-MSG-ALL command.

• Administration - level 4, allows complete access to all commands and processes, except for automatic surveillance of all network elements in the network processor span of control; level 4 can be assigned to more than one account so that several users have full privilege access to a network element

• Provisioning - level 3, allows access to provisioning, testing, editing, and retrieving commands

• Control - level 2, permits access to operate, release, and retrieve commands but not provisioning

• Retrieve - level 1, allows retrieve and report related commands to be executed; because of its limitations, level 1 is suitable as a login ID for a monitoring process

To execute TL1 commands, you must log in using an account with the sufficient UPC level.

Target identifier and source identifier Every TL1 command includes a target identifier (TID) as part of the syntax. The TID is a non-confidential code to identify the network element or network processor being addressed. It is the name of the network element or network processor.

If a TID is not entered in the TL1 command, the local TID is substituted. You must enter a TID to send the command to a remote network element or remote network processor. TIDs must be between 1 and 20 alphanumeric characters and are assigned using the SET-SID command. The first character must be a letter. The remaining characters can be any combination of letters, numbers, or dashes (-). Enclose the TID in double quotes (“) to include any combination of lower case or special characters. The string, enclosed by the double quotes, cannot include the following characters: backslash (\), space, and double quotes (“).

Note: Source identifier (SID) is the term used to identify the TID in a received message or response.

Some TL1 commands accept a TID value of ALL. When you enter the value of ALL, the command is forwarded to each SP or network processor to which you are logged into, through the access port to which the command was sent.

Multiple sessionsYou can use the ACT-USER command to log in to 20 network elements at a time. For more information on multiple sessions, see ACT-USER on page 2-8.


1-6 Introducing TL1

TL1 message notationThe following notation is used to define the syntax of the TL1 messages.

Access identifierAn access identifier (AID) appears in most command argument strings. The AID identifies the equipment or facilities to be accessed by the command.

Correlation tag The TL1 interface requires a sequential command identifier to be used with every command input. The identifier is called a correlation tag (CTAG). If a CTAG is not entered as part of the command, the command will be rejected.

The CTAG is returned with all response messages including confirmation, failed and syntax error messages, and retrieved reports. A CTAG is not returned with a scheduled report.

Note: An automatically generated message has an automatic tag (ATAG) instead of a CTAG. The ATAG is a unique numeric string generated by the system.

The CTAG correlates the command to the result of the command. The format of the CTAG is alphanumeric and can be up to six characters in length. The CTAG can be used to reflect its purpose, for example, JOB28, TAG33.

Command structureTL1 commands use a rigid structure. A command always begins with a verb, followed by a hyphen and a modifier. A second hyphen and a secondary modifier may follow. The TID and AID follow, then the CTAG and any additional parameters used by the command:

VERB-MODIFIER:TID:AID:CTAG::parameter-list;

Symbol Meaning

<cr> ASCII carriage return

<lf> ASCII line feed

^ ASCII space

<ctrl> ASCII control key

+ Symbol used in response block syntax

; Semicolon command or message terminator, used instead of Return to execute commands


Introducing TL1 1-7

Command elements are separated by punctuation marks, fields by colons (:) and subfields by commas(,). The order of AID, CTAG, and additional parameters can vary from one command group to another.

Parameter value groupingTL1 allows the values of some parameters to be grouped. This technique saves time because you enter a single command with multiple values for a particular parameter rather than multiple commands in which the parameter has a single value. The general format for parameter value grouping is<Parameter value 1> &<Parameter value 2> up to a maximum of 33 parameter values in a command. For example:

VERB-MODIFIER:tid:aid:ctag::<Parameter value 1>&<Parameter value 2> ...&<Parameter value 33>;

Note: The command length cannot exceed 234 characters.

Mandatory punctuationTL1 commands use colons and commas as command element separators and a semicolon to terminate the command line. TL1 also uses ampersands (&) as group item separators where command grouping is supported.

All punctuation shown in the command descriptions must be used or the command will fail to execute.

TL1 command acknowledgmentWhenever a TL1 command is entered, the system responds with the letters IP for in progress and the CTAG entered. Until the command either completes successfully or fails, the TL1 prompt does not return. Since no other command can be executed until the prompt returns, the same CTAG can be used in every subsequent command.

TL1 message overviewThis section describes the TL1 message types, the common elements present in all TL1 messages, and the responses to TL1 non-autonomous requests. TL1 autonomous messages are also referred to as automatic output (see the RTRV-AO command).

TL1 message types There are two types of TL1 messages: autonomous and non-autonomous. Each consists of a header and a message block.

Autonomous messages are generated by a network element as a result of activity on the network element (such as alarms, non-alarmed events, protection switch activity, and performance monitoring threshold alerts). These messages are generated automatically. Alarms, events and PM threshold


1-8 Introducing TL1

crossing alerts are broadcast to all user sessions active on the SID. Up to 10 user sessions can be active at one time. No information request is required to receive autonomous messages.

Non-autonomous messages are the network element response to a TL1 command.

TL1 command response header A response is identified by a two-line header that indicates the origin of the message, time and date, and whether the command successfully executed. The second line always begins with the letter M to indicate it is a response message.

Normal response syntax <cr> <lf> <lf>^^^<sid>^<date>^<time> <cr> <lf>M^^<ctag>^COMPLD <cr> <lf> (;|>)

Response block All retrieve commands return a response block <rspblk> in the third line as follows:

<cr> <lf> <lf>^^^<sid>^<date>^<time> <cr> <lf>M^^<ctag>^COMPLD <cr> <lf> <rspblk>(;|>)

The response block contains command-specific details retrieved. The maximum size of the response block is 32 lines. Any response longer than 32 lines is divided into multiple responses.

The RTRV-PM commands (except RTRV-PM-ABORT) support a continuation message mechanism. If no PM data is available within 2 minutes, a continuation message is sent to the TL1 session. The continuation message indicates that additional time is required for reporting PM data. The termination character in the last line of the response indicates whether or not complete data has been reported. The continuation message is sent at regular intervals (1 minute and 40 second intervals), until PM data is available.

Table 1-1 describes the termination characters for the RTRV-PM response.


Introducing TL1 1-9

Error responsesIf a TL1 command is unsuccessful, a DENY response with a TL1 error is returned. The response includes an error code. The error codes are reported along with a description of the situation under which the problem occurred. The error response follows the syntax:

<cr> <lf> <lf> ^^^<sid>^<date>^<time> <cr> <lf> M^^<ctag>^DENY <cr> <lf> ^^^<errcde> <cr> <lf> ^^^/*error text*/ <cr> <lf> ;

Refer to Chapter 6, “Error codes and messages”.

Autonomous messages format The network element reports all alarms and events autonomously to all sessions logged in through the TL1 interface. The alarm reports are generated by events or faults in facilities or equipment, environmental faults, or performance monitored threshold crossings.

Autonomous reports display a header similar to that of command response headers. The second line begins with either the letter A indicating that it reports an autonomous event, or an alarm code indicating the severity of the alarm. The second element of the second line is always a numeric autonomous tag followed by a report label:

<cr> <lf> <lf>^^^<sid>^<date>^<time> <cr> <lf>A|<almcde>^^|^<atag>^REPT^MODIFIER^MODIFIER <cr> <lf><rspblk> ;

Table 1-1Termination characters supported in the RTRV-PM response message

Termination character

Description

semi-colon (;) Indicates the termination of the response. All PM data has been reported and the process is complete.

greater than (>) If the current response does not include PM data (in a response block), then the termination character indicates that the current response is a continuation message. PM data will be reported in subsequent response messages.

If the current response includes PM data, the termination character indicates that this response contains partial data. Additional PM data will be reported in subsequent response messages.


1-10 Introducing TL1

The report label (REPT^MODIFIER^MODIFIER) indicates if a facility, common (COM), environmental (ENV), equipment (EQPT) or shelf (FAC, CONFIG, EX) alarm or event has been generated.

The response block (rspblk) is the response to either a command, scheduled report, or fault. It contains several elements to identify the specific nature of the problem. The names and significance of each is specific to the type of report.

Editing featuresThe Optical Metro 3500 Multiservice Platform supports the following editing features:

• <ctrl>+a, recalls the last command line to the current line

• <ctrl>+u, deletes the current command line

• backspace

• arrow keys are not supported

• if the TID is left blank, the TL1 command interpreter fills in the empty space with the default TID

TL1 script fileStarting with Release 11, users can create a script file that contains a series of TL1 commands to be exectued on a target shelf processor or network processor. This script file allows users to execute several, frequently used TL1 commands once. This approach is more efficient than having a user enter each command one at a time.

Users must create this script file at a remote location (such as a Unix workstation) with a text editor tool. This file must be in ASCII format and must have the filename “tl1scrpt.scr”. In order to have several TL1 script files, you must store each script file in a separate directory.

Each command in this script file must contain the precise parameters required to successfully execute the command. Each command must also be listed on a new line, separated by carriage returns. There is no limit to the number of TL1 commands that can be included in this script file. The following is an example of syntax contained in a TL1 script file:

ent-fac:ottawa:ilan1:234;ent-fac:ottawa:ilan2:235;clr-alm-secu:ottawa::j345;

TL1 allows users to load a TL1 script file to the network processor and then commit the TL1 script file to the target shelf processor or network processor. By committing the TL1 script file, the user is executing the commands in the TL1 script file to the target shelf processor or network processor.


Introducing TL1 1-11

Note 1: Only commands that complete an action (such as making connections) can be included in the TL1 script file. Retrieve commands cannot be included in this script file.

Note 2: Do not include the ACT-USER command in the TL1 script file. When this script file is committed, the network processor automatically logs in to the target shelf processor.

Note 3: It is not recommended to include commands in the TL1 script file that require password identification.

For information on how to load the TL1 script file, refer to LOAD-TL1SCRPT-NE on page 3-204. For information on how to commit the TL1 script file to a target shelf processor or network processor, refer to CMMT-TL1SCRPT-NE on page 2-86. For information on how to cancel the lodaing or committing of the TL1 script file, refer to CANC-TL1SCRPT-NE on page 2-29.

Online syntax helpThe TL1 interface has a built-in help system. When typing TL1 commands you can enter an incomplete command terminated with a question mark (?) at the point where syntax help is needed. The interface responds with syntax choices for that command element. The rule applies throughout the command, from first letter onward. For example entering A?; displays a list of all commands beginning with A.

When you log in to a network element, the following message appears indicating some of the online help functions:

Version 16.0: Welcome to NORTEL's Optical Metro 3500 MSP.

/** Starting Interactive TL1 Command Mode.* Type ? for help while constructing TL1 commands.* Type .? for specific parameter/keyword help.*/

For example, entering

< RST?

returns the following list:

/** Applicable Command(s):** RST-BANNER* RST-EC1* RST-EQPT* RST-ETH



* RST-FC* RST-OC12* RST-OC192* RST-OC3* RST-OC48 * RST-PROV* RST-T1* RST-T3*/

The help function can be called at any point in the syntax and the response is always context sensitive. For example, entering

< RST-OC?

returns the following:

/** Applicable Command(s):** RST-OC12* RST-OC192* RST-OC3* RST-OC48 */

To get the whole command syntax structure enter

< RST-OC12?

and the following results:

/** RST-OC12 (Switch OC-12 Facility In Service)

************************************************************** ** Command Syntax:** RST-OC12:[tid]:aid:ctag;** Minimum required UPC: 3* TID = "ALL" supported? NO** Parameters:** AID - OC-12 Line Facility To Act Upon*/



Entering a question mark in a specific field such as the TID

< RST-OC12:?

results in a field-specific response as follows:

/** RST-OC12 (Switch OC-12 Facility In Service)************************************************************** ** Command Syntax:** RST-OC12:[tid]:aid:ctag;** TID (Target Identifier)* Optional* -------------------------------------------------------------- * <String> System Identifier (SID) of targeted NE* ex. BUILDING6A, BAYVIEW_CAMPUS, "Harrisburg West"*/

The following example illustrates that a question mark can be entered in any field, such as the AID below

< RST-OC12::?

and the response is always context specific:

/** RST-OC12 (Switch OC-12 Facility In Service)************************************************************** ** Command Syntax:** RST-OC12:[tid]:aid:ctag;** AID Details:** AID (OC-12 Line Facility To Act Upon)* Mandatory* --------------------------------------------------------------* OC12-Slot Slot = 3..12 */

The TL1 online help function prompts you to enter correct length and content values for all fields in every command and gives examples. The interface specifies if a field should be left null.



Entering a question mark in a field with multiple components returns an explanation of all the components. For example, entering

< ENT-SECU-USER::ADMIN:CTAG123::?

results in the following:

/** ENT-SECU-USER (Provision New User Account) * Command Syntax:* ENT-SECU-USER:[TID]:newuid:ctag::newpid,newpid,upc:

TMOUTA=Domain [,TMOUT=Domain] [,PAGESTAT=Domain][,PAGE=Domain] [,ACCRSTAT=Domain] [,ACCR=Domain][, PCND=Domain] [,MINW=Domain] [,USERTYPE=Domain];

** Parameter Details:** NEWPID (New Password Identifier)* Mandatory -------------------------------------------------------------* <String> 8-10 password characters* * NEWPID (New Password Identifier)* Mandatory-------------------------------------------------------------* <String> Re-entered NEWPID for confirmation

* Hit any key to continue* UPC (User Privilege Code)* Mandatory-------------------------------------------------------------* 1 Retrieve Privileges* 2 Control Privileges* 3 Provisioning Privileges* 4 Administration Privileges* 5 Span of Control Surveillance*/



However entering period+question mark (.?) as follows:

< ENT-SECU-USER::ADMIN:CTAG123::.?

results in the following:

/** ENT-SECU-USER (Provision New User Account) * Command Syntax:* ENT-SECU-USER:[TID]:newuid:ctag::newpid,newpid,upc:

TMOUTA=Domain [,TMOUT=Domain] [,PAGESTAT=Domain][,PAGE=Domain] [,ACCRSTAT=Domain] [,ACCR=Domain][, PCND=Domain] [,MINW=Domain] [,USERTYPE=Domain];

** Parameter Details:** NEWPID (New Password Identifier)* Mandatory -------------------------------------------------------------* <String> 8-10 password characters*/

The response detail is limited to only the first comma delimited parameter (PID) being treated by online help. Any comma delimited parameter can be isolated by the online help system by using period+question mark (.?).

Help can be used in the middle of a command parameter as well, to list all commands of a certain type. For example, entering

< ED-S?

returns the following:

/** Applicable Command(s):** ED-SECU-PID* ED-SECU-USER* ED-SITE-DSM* ED-STS1* ED-STS12C* ED-STS24C* ED-STS3C* ED-SYS*/


2-1

Commands A to ED-zz 2-

This chapter covers the TL1 commands from A to ED-zz.

For more TL1 commands, see:

• Part 2 for commands ENT-aa to RST-zz

• Part 3 for commands RTRV-aa to RTRV-RINGMAP

• Part 4 for commands RTRV-ROLL-aa to Z

The following table provides an overview of the TL1 commands in this chapter by task. These tasks are listed in alphabetical order.

Task/Command Page

Alarms, events, and external controls commands

ALW-MSG-ALL 2-17

ALW-MSG-BROADCAST 2-18

DLT-ALM-PROFILE 2-120

ED-ALM-PROFILE 2-195

ED-COMM 2-198

BLSR commands

AUD-BLSR 2-22

CANC-RINGMAP 2-28

CHK-RINGMAP 2-59

CMMT-RINGMAP 2-67

DLT-BLSRRING 2-123

DLT-RINGMAP 2-168

ED-BLSRRING 2-197


2-2 Commands A to ED-zz

Cross-connect commands

DLT-CRS-STS1 2-124

DLT-CRS-STS12C 2-128


DLT-CRS-STS3C 2-133


DLT-CRS-VT1 2-138

ED-CRS-STS1 2-199

ED-CRS-STS12C 2-205

ED-CRS-STS24C 2-209

ED-CRS-STS3C 2-212

ED-CRS-STS48C 2-216

ED-CRS-VT1 2-219

DS1 service module commands

ED-SITE-DSM 2-319

Equipment commands

DEFRAG-EQPT 2-114

DLT-EQPT 2-143

Facility commands

DLT-EC1 2-142

DLT-ETH 2-147

DLT-FC 2-150

DLT-FFP-OC12 2-151

DLT-FFP-OC192 2-152

DLT-FFP-OC3 2-154

DLT-FFP-OC48 2-155

DLT-OC12 2-161

DLT-OC192 2-162

DLT-OC3 2-163

Task/Command Page


Commands A to ED-zz 2-3

DLT-OC48 2-164

DLT-T1 2-192

DLT-T3 2-193

ED-DFLT-AINS 2-225

ED-EC1 2-226

ED-ETH 2-227

ED-FC 2-232

ED-FFP-OC12 2-234

ED-FFP-OC192 2-236

ED-FFP-OC3 2-238

ED-FFP-OC48 2-240

ED-OC12 2-248

ED-OC192 2-251

ED-OC3 2-254

ED-OC48 2-258

ED-T1 2-331

ED-T3 2-336

ED-WAN 2-354

Facility test signal generation commands

CONN-TSTSIG-T1 2-108

CONN-TSTSIG-T3 2-111

DISC-TSTSIG-T1 2-118

DISC-TSTSIG-T3 2-119

Inservice traffic rollover commands

CMMT-ROLL-STS1 2-68

CMMT-ROLL-STS12C 2-73




Task/Command Page



CMMT-ROLL-VT1 2-83

DLT-ROLL-STS1 2-169

DLT-ROLL-STS12C 2-174




DLT-ROLL-VT1 2-185

ED-ROLL-STS1 2-293

ED-ROLL-STS12C 2-297


ED-ROLL-STS3C 2-303


ED-ROLL-VT1 2-310

Network processor commands

ADD-SOC 2-10

CLR-LAN-STATS 2-63

DLT-FAC 2-149

DLT-GRE 2-157

DLT-PVC 2-167

ED-IP 2-242

ED-LLX25 2-246

ED-PTX25 2-291

ED-ULX25 2-349

ED-VC 2-352

Packet Edge ring management commands

DLT-IPT 2-158

DLT-IPTR 2-159

Path and section trace commands

ED-STS1 2-320

Task/Command Page



ED-STS12C 2-323

ED-STS24C 2-325

ED-STS3C 2-327

Performance monitoring commands

ED-PMCONFIG-EC1 2-261

ED-PMCONFIG-ETH 2-263

ED-PMCONFIG-FC 2-265

ED-PMCONFIG-OC12 2-267




ED-PMCONFIG-STS1 2-275

ED-PMCONFIG-STS12C 2-278




ED-PMCONFIG-WAN 2-288

Protection switching commands

ALW-EX-OC12 2-11

ALW-EX-OC192 2-13

ALW-EX-OC3 2-14

ALW-EX-OC48 2-16

SDCC commands

DLT-LLSDCC 2-160

ED-LLSDCC 2-243

ED-ULSDCC (network element) 2-345

ED-ULSDCC (network processor) 2-347

Security and administration commands

ACT-USER 2-8

Task/Command Page



ALW-SECU-CID 2-19

ALW-SECU-USER 2-20

CANC-PROV 2-25

CANC-PROV-SOC 2-26

CANC-PROV-SP 2-27

CANC-TL1SCRPT-NE 2-29

CANC-USER 2-32

CHK-PROV 2-51

CHK-PROV-SOC 2-53

CHK-PROV-SP 2-56

CLR-ALM-SECU 2-62

CMMT-PROV 2-65

CMMT-PROV-SP 2-66

CMMT-TL1SCRPT-NE 2-86

DLT-BANNER 2-122

DLT-PROV 2-165

DLT-SECU-ACCESS 2-189

DLT-SECU-BADPID 2-190

DLT-SECU-USER 2-191

ED-DAT 2-224

ED-SECU-PID 2-314

ED-SECU-USER 2-316

ED-TOD-MODE 2-343

Software load installation commands

CANC-INSTALL 2-24

CHK-INSTALL 2-50

CMMT-INSTALL 2-64

Software upgrade commands

ALW-UPGRD 2-21

Task/Command Page



CANC-UPGRD 2-30

CHK-UPGRD 2-60

CMMT-UPGRD 2-87

DLT-UPGRD 2-194

System commands

ED-NETYPE 2-247

ED-SYS 2-329

TARP commands

ED-TARP-CONFIG 2-338

ED-TARP-TBL 2-341

Test access commands

CHG-ACCMD-STS1 2-33

CHG-ACCMD-STS12C 2-36



CHG-ACCMD-STS48c 2-42

CHG-ACCMD-T1 2-44

CHG-ACCMD-T3 2-46

CHG-ACCMD-VT1 2-48

CONN-TACC-STS1 2-88

CONN-TACC-STS12C 2-92




CONN-TACC-T1 2-100

CONN-TACC-T3 2-102

CONN-TACC-VT1 2-105

DISC-TACC 2-116

Task/Command Page



ACT-USERUse the Activate User command to log in to a network processor or network element. You can log in using remote authentication, challenge-response authentication, or local authentication. To log in using remote or local authentication, you must have a valid user identifier (UID) and password identifier (PID).

To log in using challenge-response authentication, enter the UID to partially log in to the network processor or network element. Then, use the RTRV-CHALLENGE and ENTER-CHALLENGE-RESPONSE commands to complete the login. See RTRV-CHALLENGE on page 4-69 and ENT-CHALLENGE-RESPONSE on page 3-12.

Up to 100 unique accounts can be created for one network element but only 10 TL1 user sessions using these accounts can be active at one time on one network element. Up to 100 accounts can be created for the network processor as well, but only 34 TL1 user sessions can be active at one time on one network processor.

To log out, see the CANC-USER command on page 2-32.

You can use ACT-USER to log in to a maximum of 20 network elements at one time. To maintain multiple logins all network elements must be interconnected. Once you have activated sessions to a number of network elements, most TL1 commands can be addressed to all the network elements simultaneously.

Note: A maximum of two users can log in locally to the same network element.

Once you are connected to a network processor, you can log in to a maximum of 20 network processors or network elements, if the nodes are interconnected. Only one account with level 5 UPC can be active at a time on the network element.

Starting with Release 12, up to three Level 5 users can log into and have access to the same network processor at the same time if the UIDs are different. Each of these Level 5 users can access and manage all 16 network elements within the span of control of this network processor.

If your password has expired when you log in to a network element with a UPC level of 3 or lower, you only have access to the ED-SECU-PID command. If your password accreditation time has expired when you try to log in to the network element, this command returns a DENY response. Note that, if you log in to a network element with a UPC level of 4 or 5, you are given a warning a specified number of days before your password expires. Password expiry and



accreditation times are set using the SET-ATTR-SECUDFLT command and retrieved with the RTRV-SECU-DFLT command. See SET-ATTR-SECUDFLT on page 5-196 and RTRV-SECU-DFLT on page 5-40.

Security level Level 1

Input syntaxACT-USER:[TID]:UID:CTAG::[PID]:[DOMAIN=Domain];

Example input Log in to network element NEWYORK using the account ADMIN: ACT-USER:NEWYORK:ADMIN:IL123::SESAME;

Note: The password does not appear on screen.

Table 2-1Syntax definition

Field Purpose

TID Target identifier

UID User identifier

CTAG Correlation tag

PID Password identifier

DOMAIN Authentication mode

Table 2-2Parameter definition

Parameter Possible values Definition

DOMAIN REMOTE Use remote, challenge-response, or local authentication to log in to the network processor or network element.

If centralized security administration (CSA) is enabled, you can use remote authentication or challenge-response authentication.

If CSA is disabled or is enabled but unavailable, you can use local authentication or challenge-response authentication if local authentication is provisioned as the alternate method. If challenge-response is provisioned as the alternate method, only challenge-response is available (local accounts are disabled).

See SET-ATTR-CSA on page 5-189 to set the CSA state and SET-REMAUTH-ALTERNATE on page 5-211 to set the alternate method.

CHALLENGE

LOCAL



ADD-SOCThe Add Span of Control command is used to add a network element to the NP span of control (SOC). A maximum of 16 network elements can be added to an NP span of control.

Security levelLevel 4

Input syntaxADD-SOC:[TID]:SID:CTAG::UID,PID;

Example inputAdd network element NEWYORK to the span of control of OC3NP:ADD-SOC:OC3NP:NEWYORK:CTAG13::SURVEIL,SURVEIL;


Field Purpose

TID Target identifier.

SID System identifier.

CTAG Correlation tag.

UID User identifier of the network element to add to the NP span of control.

PID Password identifier of the network element to add to the NP span of control.

Note 1: If centralized security administration (CSA) is enabled on both the NP and the network element, the command uses only the user identifier. The SOC application will only log in successfully if the NP and network element have the same shared secret. See SET-ATTR-CSA on page 5-189 to provision the CSA state and SET-CHALLENGE-SECRET on page 5-203 to set the shared secret. If CSA is disabled on either the NP or network element, the command uses the user identifier and password identifier.

Note 2: The password does not appear on screen.



ALW-EX-OC12 The Allow Exerciser OC-12 command is used to activate the exerciser to test the different protection mechanisms associated with OC-12 line switching in a linear 1+1 protected system.

The high-speed exerciser is a routine that tests the integrity of the protection switching bytes (K-bytes) communication between an OC-12 pair configured in a linear 1+1 protected system. The exerciser can run automatically on a predetermined schedule, or it can be initiated manually. The exerciser runs on a pair of OC-12 or OC-12x4 STS circuit packs or on all OC-12/OC-12x4 STS circuit packs in the shelf that are in-service. The pair must be in 1+1 protection for the exerciser to work.

Note: If the circuit packs are in a 1+1 linear configuration, there must not be an active protection switch.

The exerciser is the lowest priority user command and does not run if a higher priority feature or command is in effect.


Input syntaxALW-EX-OC12:[TID]:AID:CTAG;


Field Purpose


AID Access identifier




Example input Allow the exerciser for network element SEATTLE to run:ALW-EX-OC12:SEATTLE:OC12-9-1:CTAG13;

Table 2-5AID descriptions

AID type Command-specific values Purpose

OC-12 AID OC12-slot#-port#OC12-ALL

Identify the OC-12 facility where slot# = 3, 5, 7, 9, or 11port# = 1 for OC-12port# = 1 to 4 for OC-12x4 STS

MS DSM AID OC12-slot-1-%HLINK-OC12-Hslot-Hport

Identify a single MS DSM termination module, where slot# = 1 or 2, hslot# = 3 to 10, hport# = 1 to 4



ALW-EX-OC192 The Allow Exerciser OC-192 command is used to activate the exerciser to test the different protection mechanisms associated with OC-192 line switching in a linear 1+1 or bidirectional line-switched ring (BLSR) protected system.

The high-speed exerciser is a routine that tests the integrity of the protection switching bytes (K-bytes) communication between an OC-192 pair configured in a linear 1+1 protected system. The exerciser can run automatically on a predetermined schedule, or it can be initiated manually. The exerciser runs on a pair of in-service OC-192 circuit packs. The pair must be in 1+1 or BLSR protection for the exerciser to work.

Note 1: If the OC-192 circuit packs are in a BLSR configuration, they must also have a valid BLSR configuration and no active protection switch.

Note 2: If the OC-192 circuit packs are in a 1+1 linear configuration, there must not be an active protection switch.




Example input Allow the exerciser for network element SEATTLE to run:

ALW-EX-OC192:SEATTLE:OC192-11:CTAG13;


Field Purpose






OC-192 AID OC192-slot#OC192-ALL

Identifies the OC-192 facilityslot# = 11



ALW-EX-OC3 The Allow Exerciser command is used to activate the exerciser to test the different protection mechanisms associated with OC-3 line switching in a linear 1+1 protected system.

The high-speed exerciser is a routine that tests the integrity of the protection switching bytes (K-bytes) communication between an OC-3 pair configured in a linear 1+1 protected system. The exerciser can run automatically on a predetermined schedule or can be initiated manually. The exerciser runs on a pair of OC-3x4 circuit packs or on all OC-3x4 circuit packs in the shelf that are in-service. The pair must be in 1+1 protection for the exerciser to work.

Note: If the OC-3x4 circuit packs are in a 1+1 linear configuration, there must not be an active protection switch.





Field Purpose






Example input Allow the exerciser to run in slot 10 on all ports for network element OSAKA:ALW-EX-OC3:OSAKA:OC3-10-ALL:CTAG13;



OC3 AID OC3-slot#-port#OC3-slot#-ALLOC3-ALL

Identify the OC-3 where slot# = 3, 5, 7, and 9port# = 1 for OC-3, 1 to 4 for OC-3x4

DSM AID OC3-slot#-1-%HLINK-OC3- hslot#-hport#

slot# = 1 or 2, hslot# = 3 to 10hport# = 1 to 4



ALW-EX-OC48 The Allow Exerciser OC-48 command is used to activate the exerciser to test the different protection mechanisms associated with OC-48 line switching in a linear 1+1 or bidirectional line-switched ring (BLSR) protected system.

The high-speed exerciser is a routine that tests the integrity of the protection switching bytes (K-bytes) communication between an OC-48 pair configured in a linear 1+1 protected system. The exerciser can run automatically on a predetermined schedule or can be initiated manually. The exerciser runs on a pair of OC-48 or OC-48 STS circuit packs or on all OC-48/OC-48 STS circuit packs in the shelf that are in-service. The pair must be in 1+1 or BLSR protection for the exerciser to work.

Note 1: If the circuit packs are in a BLSR configuration, they must also have a valid BLSR configuration and no active protection switch.

Note 2: If the circuit packs are in a 1+1 linear configuration, there must not be an active protection switch.




Example input Allow the exerciser for network element SEATTLE to run:

ALW-EX-OC48:SEATTLE:OC48-11:CTAG13;

Table 2-10Sysntax definition

Field Purpose






OC-48 AID OC48-slot#OC48-ALL

Identifies the OC-48 facilityslot# = 11 for OC-48slot# = 3, 5, 7, 9, 11 for OC-48 STS



ALW-MSG-ALLThe Allow Messages All command instructs the network element to resume previously inhibited REPTÂLM, REPTÂLMÊNV, REPTÊVT and REPTÊX autonomous messages. These messages are inhibited through the use of the INH-MSG-ALL command.

When a TL1 session begins, REPTÂLM, REPTÂLMÊNV, and REPTÊVT messages are allowed by default.

To inhibit messages see INH-MSG-ALL.

Note: The Allow Messages All command does not resume previously inhibited REPTÊVT^LOG and REPTÊVTÎNVENTORY autonomous messages. To resume these inhibited autonomous messages, use the ALW-MSG-BROADCAST command.


Input syntaxALW-MSG-ALL:[TID]:[ALL]:CTAG;

Note: ALL is a valid target identifier (TID).

Example input Restart all autonomous message from network element BOSTON3: ALW-MSG-ALL:BOSTON3:ALL:CTAG12;


Field Purpose


ALL All data




ALW-MSG-BROADCASTThe Allow Messages Broadcast command instructs the network element or network processor to resume previously inhibited REPT^DBCHG, REPTÊVT^LOG and REPTÊVTÎNVENTORY autonomous messages. These messages are inhibited through the use of the INH-MSG-BROADCAST command.

When a TL1 session begins, REPT^DBCHG, REPTÊVT^LOG and REPTÊVTÎNVENTORY messages are inhibited by default.

To inhibit messages see INH-MSG-BROADCAST.


Input syntaxALW-MSG-BROADCAST:[TID]::CTAG;


Example input Turn the autonomous display of REPT^DBCHG, REPTÊVT^LOG and REPTÊVTÎNVENTORY events to on for network element BOSTON:

ALW-MSG-BROADCAST:BOSTON::CTAG12;


Field Purpose





ALW-SECU-CIDThe Allow Security Channel Identifier command is used to unlock all channels on the specified network processor that are in a locked out state. Channels are locked out when the maximum number of invalid login attempts is exceeded.


Input syntaxALW-SECU-CID:TID:[AID]:CTAG;


Example input Unlock all channels on network processor NEWYORK:

ALW-SECU-CID:NEWYORK:ALL:IL123;


Field Purpose


AID Access identifier. This command only supports an AID of ALL.




ALW-SECU-USERThe Allow Security User command is used to enable a disabled user account on the network element or network processor. This command is necessary, for example, if password accreditation was turned on using the SET-ATTR-SECUDFLT command and the user failed to changed their password before the specified accreditation time.

After an account is enabled, the user is given a warning a specified number of days before their password expires. The warning time is set with the SET-ATTR-SECUDFLT command.


Input syntaxALW-SECU-USER:[TID]::CTAG::UID;


Example inputTo enable the account of user EMILY on network element OTTAWA:

ALW-SECU-USER:OTTAWA::CTAG98::EMILY;


Field Purpose



UID User identifier. Grouping is allowed.



ALW-UPGRDThe Allow Upgrade command is entered on a network element, with parameters specifying the slot for which you want to allow the upgrade.


Input syntax for SPALW-UPGRD:[TID]:AID:CTAG;

Example input Allow slot 3 on network element Ottawa to be upgraded:

ALW-UPGRD:OTTAWA:3:CTAG24;


Field Purpose


AID Slot number of the card to allow the upgrade




AUD-BLSRUse the Audit BLSR command to run a configuration and connection audit on one or more network elements in the span of control of the network processor and to set the configuration audit period.

Note 1: By default, when you change the audit period, the first audit runs according to the occurrence of the last audit. For example, if you change the audit period to 20 hours and the last audit was 12 hours ago, the next audit would occur 8 hours after you change the audit period. You can specify that the audit run immediately after you change the audit period, rather than according to the last audit.

Note 2: When running this command, you must wait 10 seconds before performing this command again, otherwise you will get the message Status Not in Valid State (SNVS).


Input syntaxAUD-BLSR:[TID]:[AID]:CTAG::[SID]:[AUDPERIOD=Domain][,RUNAUD=Domain];


Field Purpose


AID Ring name


SID Network element name

AUDPERIOD Audit period

RUNAUD Run audit option



Ring name An alphanumeric string between 1 and 20 characters

Identify the ring name



Example inputAudit the BLSR configuration immediately for network element OTTAWA and set the connection audit period to 15 minutes:AUD-BLSR:NPFGXOTT:RING1:CTAG::OTTAWA:AUDPERIOD=15,RUNAUD=Y;

Table 2-19Parameter descriptions

Parameter Possible values Description

SID An alphanumeric string between 1 and 20 characters or ALL

Network element name. To run the audit on all network elements, set this parameter to ALL.

AUDPERIOD 15 to 10080, in increments of 15 Connection audit period in minutes (default is 720). To turn off audits, set this parameter to 0.

RUNAUD Y Run the connection audit immediately after entering this command

N Run the connection audit on schedule after entering this command (default)



CANC-INSTALLThe Cancel Install command backs out of the installation of software to a shelf processor. The command removes all load files and provisioning data from the release being installed on the shelf processor, and restores provisioning data and load files to the shelf processor from a specified node.

The CANC-INSTALL command can be run after the LOAD-INSTALL or INVK-INSTALL commands. When you run the command after the INVK-INSTALL command, a restart of the shelf processor occurs. After the restart, the status of the installation (retrieved using RTRV-INSTALL-STATE) changes to “CANCEL, PASSED”. You must run the CANC-INSTALL command again to completely cancel the installation. The status of the installation then changes to “CANCEL”. After the first CANC-INSTALL command, the system raises a “Load Mismatch’ alarm to indicate that the software loads on the shelf processor and network element do not match. The alarm clears after the second CANC-INSTALL command.


Input syntaxCANC-INSTALL:[TID]::CTAG::RNAME;

Example inputCancel the installation of the software on network element OTTAWA: CANC-INSTALL:OTTAWA::CTAG45::MONTREAL;


Field Purpose

TID Target identifier of the network element that contains the shelf processor


RNAME Remote node name where target release files reside

Table 2-21Parameter description


RNAME PC Locally attached PC

string of 1 to 40 alphanumeric characters

Target identifier of the local/remote network element, network processor, or operation controller that contains the load files and provisioning data to restore to the shelf processor



CANC-PROVThe Cancel Provisioning command is used to cancel a SAV-PROV or RST-PROV command in progress on the network element or network processor. In addition it

• cleans-up any backup files left in an invalid state by the SAV-PROV, or RST-PROV

• disconnects any file transfer connections left behind by the SAV-PROV or RST-PROV

• clears any in progress alarms raised by the SAV-PROV, or RST-PROV

• cancels the failure state that may exist


Input syntaxCANC-PROV:[TID]::CTAG;

Example input Cancel a SAV-PROV command executed on shelf processor OTTAWA:CANC-PROV:OTTAWA::CTAG99;

Table 2-22Syntax definitions

Field Purpose





CANC-PROV-SOCThe Cancel Provisioning Span of Control (CANC-PROV-SOC) command is used to cancel a SAV-PROV-SOC or CHK-PROV-SOC command in progress on the network processor. In addition it cleans-up any backup files left in an invalid state by the SAV-PROV-SOC command.


Input syntaxCANC-PROV-SOC:[TID]::CTAG;

Example input Cancel a SAV-PROV-SOC command executed on network processor OTTAWA:

CANC-PROV-SOC:OTTAWA::CTAG99;


Field Purpose





CANC-PROV-SPThe Cancel Provisioning command is used to cancel a SAV-PROV-SP or RST-PROV-SP command in progress on the shelf processor.

In addition, this command

• cleans-up any backup files left in an invalid state by the SAV-PROV-SP or RST-PROV-SP command

• disconnects any file transfer connections left behind by the SAV-PROV-SP or RST-PROV-SP command

• clears any in progress alarms raised by the SAV-PROV-SP or RST-PROV-SP command

• clears any exclusion locks left by the SAV-PROV-SP or RST-PROV-SP command


Input syntaxCANC-PROV-SP:[TID]::CTAG:::[TRGTID=Domain];

Example input Cancel a SAV-PROV-SP command executed on shelf processor OTTAWA:CANC-PROV-SP:OTTAWA::CTAG99;


Field Purpose



TRGTID Target ID



CANC-RINGMAPUse the Cancel Ring Map command to cancel the previous provisioning change and apply the original ring map. This command is supported on the network processor.


Input syntaxCANC-RINGMAP:[TID]:AID:CTAG;

Example inputCancel the previous ring map provisioning for NPFGXOTT:CANC-RINGMAP:NPFGXOTT:RING1:CTAG12;


Field Purpose


AID Ring name








CANC-TL1SCRPT-NEThe Cancel TL1 Script Network Element command is used to cancel the download of the TL1 script file to the network processor.

In addition, this command

• clears alarms related to the LOAD-TL1-SCRPT-NE command

• deletes the TL1 script file from the NP

• clears any exclusion locks left by the LOAD-TL1-SCRPT-NE command

Note: The CANC-TL1SCRPT-NE command cannot be used to cancel a CMMT-TL1SCRPT-NE command.


Input syntaxCANC-TL1SCRPT-NE:[TID]::CTAG;

Example input Cancel the download of the TL1 script file to the network processor OTTAWA:CANC-TL1SCRPT-NE:OTTAWA::CTAG99;


Field Purpose





CANC-UPGRDThe Cancel Upgrade command allows you to back out of the upgrade, if a commit upgrade command has not been issued.


Input syntax for shelf processorCANC-UPGRD:[TID]:[AID]:CTAG::RNAME;

Input syntax for network processorCANC-UPGRD:[TID]::CTAG;


Field Purpose


AID Slot number of the card you were upgrading (to be used for slot upgrade only).

Note: If the AID parameter is used, the RNAME parameter is not required.


RNAME Remote node name (applies to the shelf processor only)


Parameter Description

RNAME The RNAME parameter applies to the shelf processor only. The name of the node from which the old loads are retrieved. The node can be of different types:

OC3NE: RNAME = the remote TID (7-20 characters)OC3NP: RNAME = the remote TID (7-20 characters)OPC: RNAME = the name of the remote OPC

To obtain old loads from the PC using the RS-232 port:

PC: RNAME = "PC"

Note: OC3NE is valid only for network element upgrade.



Example input Cancel the upgrade of node Ottawa, using network processor Montreal:

CANC-UPGRD:OTTAWA::CTAG24::MONTREAL;

Cancel the upgrade of network processor Toronto:CANC-UPGRD:TORONTO::CTAG12;

Cancel the upgrade of slot 3 of node Ottawa:CANC-UPGRD:OTTAWA:3:CTAG26;



CANC-USERThe Cancel User command is used to log out of an active session with the network element or network processor.

Regardless of privilege, no account can be logged out by a CANC-USER command from a different user account. However an INIT-WARM and INIT-COLD command will log out all currently active sessions.

Note: The UID must be used to log out any account. If a user remains logged in to an account on the local network element and another user wants to log the user out but does not know the UID of the first user, the only way to log out the account is to disconnect the appropriate cable (RS-232, LAN, or X.25) from the craft access port, or turn off the power to the VT100 terminal.


Input syntaxCANC-USER:[TID]:UID:CTAG;


Example inputLog out SYSOP from the network element WASHINGTON: CANC-USER:WASHINGTON:SYSOP:TN777;


Field Purpose


UID User identifier




CHG-ACCMD-STS1The Change Access Mode command is used to transition from a monitor test access session to a split test access session on a STS-1 facility.

All connections should be monitored before splitting the connection. After successful completion of the CONN-TACC-STS1 command, the test access session is in the monitor state and can be split with the CHG-ACCMD-STS1 command.

Once the test access session is in the split state, it can be either disconnected with DISC-TACC command or set back to the monitor state using the CHG-ACCMD-STS1 command.

Note: For a listing of supported mode transitions, see Table 2-31. For a listing of supported cross-connect types for split test access sessions, see Table 2-32.

Table 2-31Supported mode transitions

From/To MONE MONF MONEF SPLTE SPLTF SPLTEF SPLTA

MONE Yes No Yes Yes No Yes

MONF Yes No Yes Yes No Yes

MONEF No No No No Yes No

SPLTE Yes Yes No No No No

SPLTF Yes Yes No No No No

SPLTEF No No Yes No No No

SPLTA Yes Yes No No No No

Table 2-32Supported test access cross-connect types (split mode)

Cross-connect type/Mode SPLTE SPLTF SPLTEF SPLTA

1WAY (Unidirectional) No No No Yes

2WAY(Bidirectional) Yes Yes Yes Yes

1WAYPR (Unidirectional Path Ring) No No No No

2WAYPR (Bidirectional Path Ring) Yes No No No

2WAYBR (Bidirectional Bridge Ring) Yes No No No

FFP (Facility Protection Group) Yes No No No




Input syntaxCHG-ACCMD-STS1:[TID]:TAPAID:CTAG::MODE;


Field Purpose



TAPAID Test access port access identifier. STS-1 to act on.

MODE Mode of test access session


TAPAID type

Possible values Description

STS-1 Facility AID

EC1-slot#-port# slot# = 3 to 10port# = 1 to 3 for EC-1x3port# = 1 to 12 for EC-1x12 or DS3/EC-1x12

DS3-slot#-port# slot# = 3, 5, 7 or 9port# = 1 to 3 for DS3x3port# = 1 to 12 for DS3x12, DS3x12e, or DS3/EC-1x12

OC3-slot#-port#-sts# slot# = 3 to 10port# = 1 for OC-3port# = 1 to 4 for OC-3x4sts# = 1 to 3

OC12-slot#-port#-sts# slot# = 3 to 10port# = 1 for OC-12port# = 1 to 4 for OC-12x4 STSsts# = 1 to 12

OC48-slot#-sts# slot# = 3 to 10sts# = 1 to 48

MS DSM STS-1 Facility AID

DS3-slot#-port#-%HLINK-Hline-hslot#-hport#

slot# = 3, 5, 7 or 9port# = 1 to 6Hline = OC3 or OC12hslot# = 3 to 10hport# = 1 to 4



Example inputTransition from the monitor test access mode to the split test access mode on the receive path at the “from end” or originating point of the path on an STS-1 facility.CHG-ACCMD-STS1:NEWYORK:DS3-5-3:CAKE23::SPLTE;



MODE MONE Monitor receive path at “from” end.

MONF Monitor receive path at “to” end.

MONEF Monitor receive path at both “from” and “to” ends.

SPLTE Split path at “from” end.

SPLTF Split path at “to” end.

SPLTEF Split path at both “from” and “to” ends.

SPLTA Split forward path



CHG-ACCMD-STS12CThe Change Access Mode command is used to transition from a monitor test access session to a split test access session on a STS-12c facility.

All connections should be monitored before splitting the connection. After successful completion of the CONN-TACC-STS12C command, the test access session is in the monitor state and can be split with the CHG-ACCMD-STS12C command.

Once the test access session is in the split state, it can be either disconnected with DISC-TACC command or set back to the monitor state using the CHG-ACCMD-STS12C command.

Note: For a listing of supported mode transitions, see Table 2-31 on page 2-33. For a listing of supported cross-connect types for split test access sessions, see Table 2-32 on page 2-33.


Input syntaxCHG-ACCMD-STS12C:[TID]:TAPAID:CTAG::MODE;


Field Purpose



TAPAID Test access port access identifier. STS-12c to act on.



TAPAID type


STS-12c Facility AID

OC12-slot#-port#-sts# slot# = 3 to 10port# = 1 for OC-12port# = 1 to 4 for OC-12x4 STSsts# = 1

OC48-slot#-port#-sts# slot# = 3 to 10port# = 1 to 4sts# = 1,13, 25, 37



Example inputTransition from the monitor test access mode to the split test access mode on the receive path at the “from end” or originating point of the path on an STS-12c facility.CHG-ACCMD-STS12C:NEWYORK:OC12-3-1-1:CAKE23::SPLTE;



















Field Purpose






TAPAID type



OC48-slot#-sts# slot# = 3 to 10sts# = 1, 25



Example inputTransition from the monitor test access mode to the split test access mode on the receive path at the “from end” or originating point of the path on an STS-24c facility.CHG-ACCMD-STS24C:NEWYORK:OC48-5-1:CAKE23::SPLTE;



















Field Purpose







Example inputTransition from the monitor test access mode to the split test access mode on the receive path at the “from end” or originating point of the path on an STS-3c facility.CHG-ACCMD-STS3C:NEWYORK:OC3-5-3-1:CAKE23::SPLTE;


TAPAID type


STS-3c Facility AID

OC3-slot#-port#-sts# slot# = 3 to 10port# = 1 for OC-3port# = 1 to 4 for OC-3x4sts# = 1

OC12-slot#-port#-sts# slot# = 3 to 10port# = 1 for OC-12port# = 1 to 4 for OC-12x4 STSsts# = 1,4,7,10

OC48-slot#-sts# slot# = 3 to 10sts# = 1,4,7, ... 46












CHG-ACCMD-STS48cThe Change Access Mode command is used to transition from a monitor test access session to a split test access session on a STS-48c facility.

All connections should be monitored before splitting the connection. After successful completion of the CONN-TACC-STS48C command, the test access session is in the monitor state and can be split with the CHG-ACCMD-STS48c command.

Once the test access session is in the split state, it can be either disconnected with DISC-TACC command or set back to the monitor state using the CHG-ACCMD-STS48c command.





Field Purpose






TAPAID type



OC48-slot#-sts# slot# = 3 to 10sts# = 1



Example inputTransition from the monitor test access mode to the split test access mode on the receive path at the “from end” or originating point of the path on an STS-48c facility.CHG-ACCMD-STS48C:NEWYORK:OC48-3-1:CAKE23::SPLTE;












CHG-ACCMD-T1The Change Access Mode command is used to transition from a monitor test access session to a split test access session on a DS1 facility.

All connections should be monitored before splitting the connection. After successful completion of the CONN-TACC-T1 command, the test access session is in the monitor state and can be split with the CHG-ACCMD-T1 command.

Once the test access session is in the split state, it can be either disconnected with DISC-TACC command or set back to the monitor state using the CHG-ACCMD-T1 command.



Input syntaxCHG-ACCMD-T1:[TID]:TAPAID:CTAG::MODE;


Field Purpose



TAPAID Test access port access identifier. DS1 to act on.



TAPAID type Possible values Description

DS1 AID DS1-slot#-port# slot# =4 to 10, port# =1 to 12

DS3V AID DS1-slot#-port#-t1# slot# = 3 to 10, port# = 1 to 12t1# = 1 to 28

DSM AID DS1-1-port#-%HLINK-HLINE-hslot#-hport#

port# = 1 to 84, hslot# = 3 to 10hport# = 1 to 4HLINE = OC3 or OC12



Example inputTransition from the split test access mode to the monitor test access mode on the receive path at the “to end” or end point of the path on a DS-1 facility.CHG-ACCMD-T1:NEWYORK:DS1-10-3:CAKE23::MONF;

VT1.5 facility AID

EC1-slot#-port#-vtg#-vt# slot# = 3, 5, 7, 9port# = 1 to 3 for EC-1x3port# = 1 to 12 for EC-1x12 or DS3/EC-1x12vtg# = 1 to 7, vt# = 1 to 4

OC3 AID OC3-slot#-port#-sts#-vtg#-vt#

slot# = 3 to 10port# = 1 for OC-3port# = 1 to 4 for OC-3x4sts#= 1 to 3vtg# = 1 to 7, vt# = 1 to 4

OC12 AID OC12-slot#-port#-sts#-vtg#-vt#

slot# = 3 to 10port# = 1sts#= 1 to 12vtg# = 1 to 7, vt# = 1 to 4










Table 2-49 (continued)AID descriptions




CHG-ACCMD-T3The Change Access Mode command is used to transition from a monitor test access session to a split test access session on a DS-3 facility.

All connections should be monitored before splitting the connection. After successful completion of the CONN-TACC-T3 command, the test access session is in the monitor state and can be split with the CHG-ACCMD-T3 command.

Once the test access session is in the split state, it can be either disconnected with DISC-TACC command or set back to the monitor state using the CHG-ACCMD-T3 command.



Input syntaxCHG-ACCMD-T3:[TID]:TAPAID:CTAG::MODE;


Field Purpose







Example inputTransition from the split test access mode to the monitor test access mode on the receive path at the “to end” or end point of the path on a DS-3 facility.CHG-ACCMD-T3:NEWYORK:DS3-9-3:CAKE23::MONF;

Table 2-52AID description

TAPAID type


T3 Facility AID

EC1-slot#-port# slot# = 3 to 10, port# = 1 to 3 for EC-1x3port# = 1 to 12 for EC-1x12 or DS3/EC-1x12

DS3-slot#-port# slot# = 3,5,7,9, port# = 1 to 3 for DS3x3port# = 1 to 12 for DS3x12, DS3x12e, or DS3/EC-1x12

DS3-slot#-port#-%HLINK-Hline-Hslot#-Hport#

slot# = 3 or 5; port# = 1 to 6Hline = OC3 or OC12Hslot# = 3 to10Hport# = 1 to 4


OC12-slot#-port#-sts# slot# = 3 to 10port# = 1 sts# = 1 to 12










SPLTA Split forward path.



CHG-ACCMD-VT1The Change Access Mode command is used to transition from a monitor test access session to a split test access session on a VT1.5 facility.

All connections should be monitored before splitting the connection. After successful completion of the CONN-TACC-VT1 command, the test access session is in the monitor state and can be split with the CHG-ACCMD-VT1 command.

Once the test access session is in the split state, it can be either disconnected with DISC-TACC command or set back to the monitor state using the CHG-ACCMD-VT1 command.



Input syntaxCHG-ACCMD-VT1:[TID]:TAPAID:CTAG::MODE;


Field Purpose



TAPAID Test access port access identifier. VT1.5 to act on.




Example inputTransition from the split test access mode to the monitor test access mode on the receive path at the “to end” or end point of the path.CHG-ACCMD-VT1:NEWYORK:DS1-10-3:CAKE23::MONF;



VT1.5 facility AID

DS1-slot#-port# slot# =4 to 10, port# =1 to 12

DS1-slot#-port#-t1# slot# = 3 to 10, port# = 1 to 12t1# = 1 to 28

DS1-1-port#-%HLINK-Hline-hslot#-hport#

port# = 1 to 84, hslot# = 3 to 10hport# = 1 to 4

EC1-slot#-port#-vtg#-vt# slot# = 3 to 10port# = 1 to 3 for EC-1x3port# = 1 to 12 for EC-1x12 or DS3/EC-1x12vtg# = 1 to 7, vt# = 1 to 4

OC3-slot#-port#-sts#-vtg#-vt#



slot# = 3 to 10port# = 1sts#= 1 to 12vtg# = 1 to 7, vt# = 1 to 4


Parameter Possible values description










CHK-INSTALLThe Check Installation command verifies that the installation of a new software release to the shelf processor is possible and that a specified node can provide the necessary load.

For the check to be successful:

• The software loads on the shelf processor and on the network element that contains the shelf processor must be different

• The software loads on the specified node and on the network element that contains the shelf processor must be the same

• The software load on the network element that contains the shelf processor must not be indeterminate (the circuit packs on the network element must all have the same software release)


Input syntaxCHK-INSTALL:[TID]::CTAG::RNAME;

Example inputCheck the installation of the new software on network element OTTAWA: CHK-INSTALL:OTTAWA::CTAG45::MONTREAL;


Field Purpose



RNAME Target identifier of the node (local/remote network element, network processor, or operation controller) that contains the load files and provisioning data to install on the shelf processor



RNAME PC Locally attached PC

string of 1 to 40 alphanumeric characters

Remote node name where target release files reside.



CHK-PROVThe Check Provisioning command is used to do pre-checks on the shelf processor or network processor for which the provisioning data is to be saved or restored. These checks include whether

• the given destination is reachable (if the DESTTYPE and DESTADDR options are included). If the file transfer connection cannot be made or if the destination is involved in a duplicate SID, the check fails.

Note: the system is in one of the following preventative states- upgrade in progress- load mismatch- inservice rollover in progress (shelf processor only)- disk is full (network processor only)- duplicate source identifier (SID)- database save and restore in progress- database save and restore has failedIf the system is in a preventative state the check fails.

• any alarms are raised on the shelf processor or network processor (if the CHKALM option is omitted or given the value Y). If any alarms are raised on the shelf processor or network processor the check fails.

The CHK-PROV command, although optional, should always be sent before sending a SAV-PROV or a RST-PROV to a shelf processor or network processor.

Note: Only one save and restore command can occur at a time, with the exception of CANC-PROV.


Input syntaxCHK-PROV:[TID]::CTAG:::[DESTTYPE=Domain][,DESTADDR=Domain][,CHKALM=Domain];


Field Purpose





Example inputCheck network processor MONTREAL prior to saving its provisioning data to a UNIX workstation:CHK-PROV:MONTREAL::CTAG98:::DESTTYPE=IP,DESTADDR=47.124.9.88,CHKALM=Y;

orCHK-PROV:MONTREAL::CTAG98:::DESTTYPE=TID,DESTADDR=OPCOTTAWA,CHKALM=Y;

DESTTYPE Source of the Restore — TID, IP, or locally attached PC

DESTADDR Destination address

Address of the Destination type (TID or IP) which is the destination of the Save or source of the Restore.

For a DESTTYPE of PC, omit DESTADDR.

CHKALM Check active alarms



DESTTYPE TID Target Identifier

IP Internet Protocol

PC Locally attached PC

DESTADDR TID address Name of the network element, network processor, or OPC

IP address A network element or network processor identifier in the format x.x.x.x (where x = a number from 1-255)

CHKALM Y (default) A CHK-PROV is not allowed if there is an alarm present on the network processor or shelf processor card receiving the command

N A CHK-PROV is allowed whether or not there is an alarm present on the network processor or shelf processor card receiving the command. If the CHK-PROV command is sent with the CHKALM=N and some preventative states exist, the command will fail.

Table 2-59 (continued)Syntax definition

Field Purpose



CHK-PROV-SOCThe Check Provisioning Span of Control (CHK-PROV-SOC) command is used to do pre-checks on the network processor to ensure that it can save the provisioning data from all of the shelf processors in its span of control (SOC) to a given destination. These checks include whether

• the given destination is reachable (if the DESTTYPE and DESTADDR options are included). The given destination can be a remote location with a TID or IP address. If the file transfer connection cannot be made or if the destination is involved in a duplicate SID, the check fails.

• the system is in one of the following preventative states- upgrade in progress- load mismatch- inservice rollover in progress (shelf processor only)- disk is full (network processor only)- duplicate source identifier (SID)- database save and restore in progress- database save and restore has failedIf the system is in a preventative state the check fails.

• any alarms are raised on the shelf processor or network processor (if the CHKALM option is omitted or given the value Y). If any alarms are raised on the shelf processor or network processor the check fails.

The CHK-PROV-SOC command, although optional, should always be sent before sending a SAV-PROV-SOC to a shelf processor or network processor.

Note 1: Only one save and restore command can occur at a time, with the exception of CANC-PROV.

Note 2: If the given destination is a remote location, the CHK-PROV-SOC command cannot check if there is sufficient disk space at the remote location to download the provisioning data.


Input syntaxCHK-PROV-SOC:[TID]::CTAG::[“USERID”][,”PASSWRD”]:[DESTTYPE=Domain],[DESTADDR=Domain][,DIR=”Domain”][,CHKALM=Domain];




Field Purpose



USERID User ID (see Note)

PASSWRD User’s password (see Note)

DESTTYPE Destination type (TID or IP)

DESTADDR Destination address. Address of the Destination type (TID or IP) which is the destination of the Save or source of the Restore.

DIR Directory in which the backed-up provisioning data is stored (see Note)

CHKALM Check alarm status

Note: Do not specify a user ID, password or directory if the remote location is an Operations Controller.


Parameter Possible values

Description



DESTADDR TID address

Name of remote location

IP address

A remote location identifier in the format x.x.x.x (where x = a number from 1-255)

CHKALM Y (default)

A CHK-PROV-SOC is not allowed if there is an alarm present on the network processor or shelf processor card receiving the command

N A CHK-PROV-SOC is allowed whether or not there is an alarm present on the network processor or shelf processor card receiving the command. If the CHK-PROV-SOC command is sent with the CHKALM=N and some preventative states exist, the command will fail.



Example inputCheck network processor MONTREAL prior to saving its provisioning data to a remote UNIX workstation:CHK-PROV-SOC:MONTREAL::CTAG98::”jim”,”password”:DESTTYPE=IP,DESTADDR=47.202.198.105,DIR=”/home/saverest”,CHKALM=Y;

Check network processor MONTREAL prior to saving its provisioning data to to the Operations Controller of network element TORONTO:CHK-PROV-SOC:MONTREAL::CTAG98:::DESTTYPE=TID,DESTADDR=TORONTO,CHKALM=Y;



CHK-PROV-SPThe Check Provisioning Shelf Processor command is used to determine whether there are preventative states on the shelf processor for which the provisioning data is to be saved (with the SAV-PROV-SP command) or restored (with RST-PROV-SP command). These preventative states include

• upgrade in progress

• in-service rollover on the SP

• reconfiguration or BLSR configuration in progress

• provisioning of data in progress

• FPGA download in progress

• transmit data recovery failed

• SP version mismatch

• loads mismatch

• database corruption

• load install

• disk full

• shelf ID mismatch

• duplicate SID on the SP or NP

• database save and restore in progress

• exclusion lock on the save and restore directory

• remote destination is not reachable with the given user name and password from the NP if the destination information is provided

If the system is in one of these preventative states, the check fails.

The CHK-PROV-SP command, although optional, should always be sent before sending a SAV-PROV-SP command to a shelf processor.

Note: If the given destination is a remote location, the CHK-PROV-SP command cannot check if there is sufficient disk space at the remote location to download the provisioning data.


Input syntaxCHK-PROV-SP:[TID]::CTAG::[“USERID”][,”PASSWRD”]:TRGTID=DomainDESTTYPE=Domain,DESTADDR=Domain[,DIR=Domain][,CHKALM=Domain];




Field Purpose



USERID User ID (see Note)

PASSWRD User’s password (see Note)

TRGTID Targeted TID (the SP for which the NP is required to acted upon)

DESTTYPE Destination type (TID or IP)

DESTADDR Destination address

Address of the Destination type (TID or IP) which is the destination of the Save or source of the Restore.

DIR Directory in which the backed-up provisioning data is stored (see Note)

CHKALM Check alarm status

Note: Do not specify a user ID, password or directory if the remote location is an Operations Controller.



Description



DESTADDR TID address Name of remote location

IP address A remote location identifier in the format x.x.x.x (where x = a number from 1-255)

CHKALM Y (default) A CHK-PROV-SP is not allowed if there is an alarm present on the shelf processor card receiving the command

N A CHK-PROV-SP is allowed whether or not there is an alarm present on the shelf processor card receiving the command. If the CHK-PROV-SP command is sent with the CHKALM=N and some preventative states exist, the command will fail.



Example inputCheck shelf processor MONTREAL prior to saving its provisioning data to a remote Unix workstation:CHK-PROV-SP:MONTREAL::CTAG98::”jim”,”password”:TRGTID=MONTREALNP ,DESTTYPE=IP,DESTADDR=47.202.198.105,DIR=”/home/saverest”,CHKALM=Y;

or

Check shelf processor MONTREAL prior to saving its provisioning data to the Operations Controller of network element TORONTO:CHK-PROV-SP:MONTREAL::CTAG98:::TRGTID=MONTREALNPDESTTYPE=TID,DESTADDR=TORONTO,CHKALM=Y;



CHK-RINGMAPUse the Check Ring Map command to verify map information for a BLSR ring. This command is supported on the network processor and shelf processor.


Input syntaxCHK-RINGMAP:[TID]:AID:CTAG;

Example inputVerify the ring map information for the BLSR RING1:CHK-RINGMAP:NPFGXOTT:RING1:CTAG;


Field Purpose


AID Ring name








CHK-UPGRDThe Check Upgrade command is entered with parameters specifying the new release number and where to get the files containing the new loads (PC, OPC, another network element).

When CHK-UPGRD is issued from the network element user interface, the shelf processor checks if the specified location is reachable and does a pre-upgrade check to see if the network element can be upgraded. When CHK-UPGRD is issued from the network processor user interface, the network processor checks if the specified location is reachable and does a pre-upgrade check to see if the network processor can be upgraded. When CHK-UPGRD is issued from the network element user interface and it specifies a slot number, the shelf processor does a pre-upgrade check to see if the slot can be upgraded.


Input syntax for NPCHK-UPGRD:[TID]::CTAG::RNAME,RELNO;

Input syntax for SPCHK-UPGRD:[TID]:[AID]:CTAG::RNAME,RELNO;


Field Purpose





Example input Check that network element Ottawa can be upgraded from network element TORONTO:CHK-UPGRD:OTTAWA::CTAG24::TORONTO,NTNA6021;

Check that OC3NP can be upgraded from another network processor:CHK-UPGRD:OC3NP::CTAG25::OC3NP2,NTNA6021;

Check that slot 3 of network element Ottawa can be upgraded:CHK-UPGRD:OTTAWA:3:CTAG26;

AID Slot number of the card to upgrade (to be used for slot upgrade only).

Note: If the AID parameter is used, the RELNO and RNAME parameters are not required.

RNAME The name of the node from which the new loads are retrieved.

The node can be of the following types:

OC3NE: RNAME = the remote TID (7-20 characters)OC3NP: RNAME = the remote TID (7-20 characters)OPC: RNAME = the name of the remote OPC

For upgrade from a PC using the RS-232 port:

PC: RNAME = "PC"

For upgrade from the local file system:

file system: RNAME = the local TID (7-20 characters)

Note: OC3NE is valid only for network element upgrade.

RELNO An ASCII string identifying the release number to upgrade to


Field Purpose



CLR-ALM-SECUThe Clear Alarm Security command is used to clear all security alarms on the specified network element or network processor.


Input syntaxCLR-ALM-SECU:[TID]::CTAG;


Example inputClear all security alarms on network element OTTAWA:CLR-ALM-SECU:OTTAWA::CTAG93;


Field Purpose





CLR-LAN-STATSThe Clear ILAN Statistics command is used to clear

• ILAN1 or COLAN error statistics on the specified network processor

• ILAN error statistics on the specified network element


Input syntaxCLR-LAN-STATS:[TID]:AID:CTAG;


Example inputClear all ILAN error statistics on network element OTTAWA:

CLR-ILAN-STATS:OTTAWA:ILAN:CTAG93;


Field Purpose

TID Target identifier of the network element or network processor

AID Type of error statistic to clear.

For a network processor, possible values are ILAN1 or COLAN.

For a network element, the only possible value is ILAN.




CMMT-INSTALLThe Commit Installation command causes the new software load on the shelf processor to become permanent. The command removes any files and provisioning data from the previous load.


Input syntaxCMMT-INSTALL:[TID]::CTAG;

Example inputCommit the installation of the software on network element OTTAWA: CMMT-INSTALL:OTTAWA::CTAG45;


Field Purpose





CMMT-PROVThe Commit Provisioning (CMMT-PROV) command is used to commit the files which have been restored to a shelf processor or network processor by the RST-PROV command.

The CMMT-PROV command checks to see if there are any outstanding reasons not to commit the data at this time. If there are no reasons, it will commit the data and cause a special reset. It will also clear the Database Restore in Progress alarm.


Input syntaxCMMT-PROV:[TID]::CTAG;

Example inputCommit provisioning data that has been restored to shelf processor OTTAWA:CMMT-PROV:OTTAWA::CTAG93;


Field Purpose





CMMT-PROV-SPThe Commit Provisioning SP command is used to commit the files which have been restored from a remote location with a TID or IP address to a shelf processor by the RST-PROV-SP command. The CMMT-PROV-SP command checks to see if there are any outstanding reasons not to commit the data at this time. If there are no reasons, this command will commit the data.

This command is completed on the designated shelf processor after an autonomous save and restore restart is performed. This restart consists of a warm restart of the shelf processor and the tributary circuit packs.


Input syntaxCMMT-PROV-SP:[TID]::CTAG:::[TRGTID=Domain];

Example inputCommit provisioning data that has been restored to shelf processor MONTREAL:CMMT-PROV-SP:MONTREAL::CTAG93;


Field Purpose





CMMT-RINGMAPUse the Commit Ring Map command to copy the temporary ring map to the permanent ring map. This command is supported on the network processor.


Input syntaxCMMT-RINGMAP:[TID]:AID:CTAG;

Example inputCommit the ring map provisioning for NPFGXOTT:CMMT-RINGMAP:NPFGXOTT:RING1:CTAG;


Field Purpose


AID Ring name








CMMT-ROLL-STS1 The Commit Rollover STS-1 command is used to delete the original STS-1 path.


Input syntaxCMMT-ROLL-STS1:[TID]:fromAID,toAID:CTAG::CCT:RFROM=Domain,RTO=Domain[,CMMTSWMATE=Domain];


Field Purpose

TID Target identifier, the network element to which the command is directed

fromAID One of the original cross-connection endpoints

toAID Second of the original cross-connection endpoints

CTAG Correlation tag, an alphanumeric identifier to correlate the command and response messages

CCT Connection type to be rolled

RFROM The fromAID or toAID to be rolled (see Note)

RTO AID RFROM is to be rolled to (see Note)

CMMTSWMATE Deletes the original switch mate in a 1WAYPR, 2WAYPR, or 2WAYBR circuit

Note: When rolling a switch mate, RFROM=OLDSWMATE, RTO=NEWSWMATE.




AID type Command-specific values

Purpose

STS1facility AID

DS3-slot#-port# Identify the STS-1 facility on a DS3 circuit pack whereslot# = 3, 5, 7, 9port# = 1 to 3 for DS3x3port# = 1 to 12 for DS3x12, DS3x12e, or DS3/EC-1x12

OC3-slot#-port#-sts# Identify the STS-1 facility on an OC-3 circuit pack whereslot# = 3 to 10port# = 1 for OC-3port# = 1 to 4 for OC-3x4sts# = 1 to 3

OC12-slot#-port#-sts# Identify the STS-1 facility on an OC-12 or OC-12x4 STS circuit pack whereslot# = 3 to 12 for OC-12slot# = 3 to 10 for OC-12x4 STSport# = 1 for OC-12port# = 1 to 4 for OC-12x4 STSsts# = 1 to 12

OC48-slot#-sts# Identify the STS-1 facility on an OC-48 or OC-48 STS circuit pack whereslot# = 11 or 12 for OC-48slot # = 3 to 12 for OC-48 STSsts# = 1 to 48



STS1facility AID

OC192-slot#-sts# Identify the STS-1 facility on an OC-192 circuit pack whereslot# = 11 or 12sts# = 1 to 192

EC1-slot#-port# Identify the STS-1 facility on an EC-1 circuit pack whereslot# = 3, 5, 7, 9port# = 1 to 3 for EC-1x3port# = 1 to 12 for EC-1x12 or DS3/EC-1x12

WAN-slot#-port#-sts# Identify the STS-1 facility on the WAN port where slot# = 3 to 10port# = 1 or 2 for 2xGigE/FC-P2P, 2xGigE/FC-P2P-C, 2xGigE-P2P, or 2x100BT-P2Pport# = 1 to 4 for 4x100FX-P2Pport# = 1 to 8 for 8x100BT-P2Psts# = 1 for 2x100BT-P2Psts# = 1 to 3 for 4x100FX-P2Por 8x100BT-P2Psts# = 1 to 21 for 2xGigE/FC-P2P, 2xGigE/FC-P2P-C, or 2xGigE-P2P

Note: The WAN AID only applies to the fromAID and toAID fields. The WAN AID does not apply to the RFROM and RTO fields.

STS1 facility AID on DSM

OC3-1-1-sts-%HLINK-OC3-Hslot#-Hport#

Identify the STS-1 facility on an OC-3 circuit pack whereHslot# = 3 to 10Hport# = 1 to 4



Purpose



Example inputRollover an STS1 working connection on the OC-3x4 circuit pack in a 2WAYPR circuit between a DS3 service and the OC-3x4 circuit pack.

Bridge the original OC-3 working connection:ENT-ROLL-STS1:OTTAWA:OC3-9-2-1,DS3-3-1:A::2WAYPR:RFROM=OC3-9-2-1,RTO=OC3-9-3-1,VALID=Y;

STS1 facility AID on MS DSM

DS3-slot-port-%HLINK-Hline-Hslot-Hport

slot = 3 or 5port = 1 to 6Hline = OC3 or OC12Hslot = 3 to 10Hport = 1 to 4

WAN-slot-port-sts-%HLINK-Hline-Hslot-Hport

slot = 3 to 6; port = 1 to 8; sts = 1 to 3Hline = OC3 or OC12Hslot = 3 to 10Hport = 1 to 4

STSMDS1-grp-%HLINK-Hline-Hslot-Hport

grp = 1 to 3 where grp 1 =DS1s 1 to 28, grp 2 = DS1s 29 to 56, grp 3 = DS1s 57 to 84 Hline = OC3 or OC12Hslot = 3 to 10Hport = 1 to 4



CCT 1WAY Unidirectional connection

2WAY Bidirectional connection

1WAYPR 1WAY path ring, fromAID must be optical


2WAYBR 2WAY bridge ring, fromAID must be optical

CMMTSWMATE Y Bridge will be performed regardless of the condition of the switched-to path.

N (default) Bridge will be denied if conditions on the node are inappropriate.



Purpose



Switch to the bridge connection:

ED-ROLL-STS1:OTTAWA:OC3-9-2-1,DS3-3-1:B::2WAYPR:RFROM=OC3-9-2-1,RTO=OC3-9-3-1,VALID=Y:SWITCHED;

Remove the original working connection:

CMMT-ROLL-STS1:OTTAWA:OC3-9-2-1,DS3-3-1:C::2WAYPR:RFROM=OC3-9-2-1,RTO=OC3-9-3-1;



CMMT-ROLL-STS12C The Commit Rollover STS-12c command is used to delete the original STS-12c path.


Input syntaxCMMT-ROLL-STS12C:[TID]:fromAID,toAID:CTAG::CCT:RFROM=DOMAIN,RTO=DOMAIN[,CMMTSWMATE=Domain];


Field Purpose









Note: When rolling a switch mate, RFROM=OLDSWMATE, RTO=NEWSWMATE





STS12Cfacility AID

OC12-slot#-port#-sts# Identify the STS-12c facility on an OC-12 or OC-12x4 STS circuit pack whereslot# = 3 to 12 for OC-12slot# = 3 to 10 for OC-12x4 STSport# = 1 for OC-12port# = 1 to 4 for OC-12x4 STSsts# = 1

OC48-slot#-sts# Identify the STS-12c facility on an OC-48 or OC-48 STS circuit pack whereslot# = 11 or 12 for OC-48slot# = 3 to 12 for OC-48 STSsts# = 1, 13, 25, 37

OC192-slot#-sts# Identify the STS-12c facility on an OC-192 circuit pack whereslot# = 11, 12sts# = 1, 13, 25, 37, ... 181

WAN-slot#-port#-sts# Identify the STS-12c facility on the WAN port of the 2xGigE/FC-P2P, 2xGigE-P2P, or 2xGigE/FC-P2P-C where slot# = 3 to 10port# = 1 or 2sts# = 1

Note: The WAN AID only applies to the fromAID and toAID fields. The WAN AID does not apply to RFROM and RTO.



Example inputRollover an STS-12c working connection on the OC-12 circuit pack in a 2WAYPR circuit between an OC-12 service and the OC-12 circuit pack.

Bridge the original OC-12 working connection:ENT-ROLL-STS12C:OTTAWA:OC12-9-1-1,OC12-8-1-1:CTAG3::2WAYPR:RFROM=OC12-9-1-1,RTO=OC12-7-1-1,VALID=Y;


ED-ROLL-STS12C:OTTAWA:OC12-9-1,OC12-8-1:CTAG3::2WAYPR:RFROM=OC12-9-1-1,RTO=OC12-7-1-1,VALID=Y:SWITCHED;


CMMT-ROLL-STS12C:OTTAWA:OC12-9-1-1,OC12-8-1-1:CTAG3::2WAYPR:RFROM=OC12-9-1-1,RTO=OC12-7-1-1;
















Field Purpose














STS24Cfacility AID

OC48-slot#-sts# Identify the STS-24c facility on an OC-48 or OC-48 STS circuit pack whereslot# = 11, 12 for OC-48slot# = 3 to 12 for OC-48 STSsts# = 1, 25

OC192-slot#-sts# Identify the STS-24c facility on an OC-192 circuit pack whereslot# = 11, 12sts# = 1, 25, 49, ... 169

WAN-slot#-port#-sts# Identify the STS-24c facility on the WAN port of the 2xGigE/FC-P2P, 2xGigE-P2P, or 2xGigE/FC-P2P-C whereslot# = 3 to 10port# = 1 or 2sts# = 1













Example inputRollover an STS-24c working connection on the OC-48 STS circuit pack in a 2WAYPR circuit between an OC-48 STS circuit pack and another OC-48 STS circuit pack.

Bridge the original OC-48 working connection:

ENT-ROLL-STS24C:OTTAWA:OC48-9-1,OC48-8-1:CTAG3::2WAYPR:RFROM=OC48-9-1,RTO=OC48-7-1,VALID=Y;


ED-ROLL-STS24C:OTTAWA:OC48-9-1,OC48-8-1:CTAG3::2WAYPR:RFROM=OC48-9-1,RTO=OC48-7-1,VALID=Y:SWITCHED;


CMMT-ROLL-STS24C:OTTAWA:OC48-9-1,OC48-8-1:CTAG3::2WAYPR:RFROM=OC48-9-1,RTO=OC48-7-1;





Input syntaxCMMT-ROLL-STS3C:[TID]:fromAID,toAID:CTAG::CCT:RFROM=Domain,RTO=Domain[,CMMTSWMATE=Domain];


Field Purpose












Example inputRollover an STS-3c working connection on the OC-3x4 circuit pack in a 2WAYPR circuit between an OC-3 service and the OC-3x4 circuit pack.

Bridge the original OC-3 working connection:ENT-ROLL-STS3C:OTTAWA:OC3-9-1-1,OC3-8-1-1:D::2WAYPR:RFROM=OC3-9-1-1,RTO=OC3-7-1-1,VALID=Y;


ED-ROLL-STS3C:OTTAWA:OC3-9-1-1,OC3-8-1-1:B::2WAYPR:RFROM=OC3-9-1-1,RTO=OC3-7-1-1,VALID=Y:SWITCHED;


CMMT-ROLL-STS3C:OTTAWA:OC3-9-1-1,OC3-8-1-1:C::2WAYPR:RFROM=OC3-9-1-1,RTO=OC3-7-1-1;
















Field Purpose












STS48Cfacility AID

OC48-slot#-sts# slot# = 11, 12 for OC-48slot# = 3 to 12 on OC-48 STSsts# = 1

OC192-slot#-sts# slot# = 11, 12sts# = 1, 49, 97... 145




Bridge the original OC-48 working connection:ENT-ROLL-STS48C:OTTAWA:OC48-9-1,OC48-8-1:CTAG3::2WAYPR:RFROM=OC48-9-1,RTO=OC48-7-1,VALID=Y;

Switch to the bridge connection:ED-ROLL-STS48C:OTTAWA:OC48-9-1,OC48-8-1:CTAG3::2WAYPR:RFROM=OC48-9-1,RTO=OC48-7-1,VALID=Y:SWITCHED;

Remove the original working connection:CMMT-ROLL-STS48C:OTTAWA:OC48-9-1,OC48-8-1:CTAG3::2WAYPR:RFROM=OC48-9-1,RTO=OC48-7-1;












CMMT-ROLL-VT1 The Commit Rollover VT1 command is used to delete the original VT1.5 path.


Input syntaxCMMT-ROLL-VT1:[TID]:fromAID,toAID:CTAG::CCT:RFROM=Domain,RTO=Domain[,CMMTSWMATE=Domain];


Field Purpose












VT1.5facility AID

DS1-slot#-port#DS1-DFLT-grp

slot# = 4 to 10port# = 1 to 12grp = 1 to 3

DS1-slot#-port#-t1#DS1-slot#-port#-ALL

slot# = 3, 5, 7, 9port# = 1 to 12t1# = 1 to 28


DS1 service moduleport# = 1 to 84hslot# = 3 to 10hport# = 1 to 4



VT1.5facility AID

DS1-DFLT-grp#-%HLINK-Hline-hslot#-hport#

DS1 service modulegrp# = 1 to 3hslot# = 3 to 10hport# = 1 to 4

OC3-slot#-port#-sts#-vtg#-vt#OC3-slot#-port#-sts#-ALL

slot# = 3 to 10port# = 1 for OC-3port# = 1 to 4 for OC-3x4sts# = 1 to 3vtg# = 1 to 7vt# = 1 to 4


slot# = 3 to 12port# = 1sts# = 1 to 12vtg# = 1 to 7vt# = 1 to 4

OC48-slot#-sts#-vtg#-vt#OC48-slot#-sts#-ALL

slot# = 11, 12sts# = 1 to 48vtg# = 1 to 7vt# = 1 to 4

EC1-slot#-port#-vtg#-vt#EC1-slot#-port#-ALL

slot# = 3, 5, 7, 9port# = 1 to 3 for EC-1x3port# = 1 to 12 for EC-1x12 or DS3/EC-1x12vtg# = 1 to 7vt# = 1 to 4

WAN-slot#-port#-sts#-vtg#-vt#WAN-slot#-port#-sts#-vtg#-ALLWAN-slot#-port#-sts#-ALL

slot# = 3 to 10port# = 1 to 4 for 4x100FX-P2Pport# = 1 to 8 for 8x100BT-P2Psts# = 1 to 3vtg# = 1 to 7 for sts# = 1 or 2vtg# = 1 or 2 for sts# = 3vt# = 1 to 4





Example inputRollover a VT1.5 working connection on the OC-3x4 circuit pack in a 2WAYPR circuit between a DS1 service and the OC-3x4 circuit pack.

Bridge the original OC-3 connection:ENT-ROLL-VT1:OTTAWA:OC3-9-2-1-7-1,DS1-4-4:A::2WAYPR:RFROM=OC3-9-2-1-7-1,RTO=OC3-9-3-1-7-1,VALID=Y;


ED-ROLL-VT1:OTTAWA:OC3-9-2-1-7-1,DS1-4-4:B::2WAYPR:RFROM=OC3-9-2-1-7-1,RTO=OC3-9-3-1-7-1,VALID=Y:SWITCHED;

Remove the original connection:

CMMT-ROLL-VT1:OTTAWA:OC3-9-2-1-7-1,DS1-4-4:C::2WAYPR:RFROM=OC3-9-2-1-7-1,RTO=OC3-9-3-1-7-1;












CMMT-TL1SCRPT-NEThe Commit TL1 Script Network Element command is used to apply the TL1 commands contained in the TL1 script file (stored on the NP) to a designated network element.

This command is not successful if one of the following occurs:

• any command in the TL1 script file does not complete successfully

• a timeout period elapses before an event or alarm is generated, indicating that the save command is completed

If this command is not successful, a TL1 Script file Load Failed alarm becomes active. To clear this alarm (and cancel this operation), you must run the CANC-TL1SCRPT-NE command.


Input syntaxCMMT-TL1SCRPT-NE:[TID]::CTAG;

Example inputCommit the TL1 commands in the TL1 script file to network element OTTAWA:CMMT-TL1SCRPT-NE:OTTAWA::CTAG93;


Field Purpose





CMMT-UPGRDThe Commit Upgrade command causes the new loads on the shelf processor, the card, or the network processor to become the permanent load. You cannot cancel the upgrade once the commit upgrade command has been executed.


Input syntax for NPCMMT-UPGRD:[TID]::CTAG;

Input syntax for SPCMMT-UPGRD:[TID]:[AID]:CTAG;

Example input Commit the upgrade load on network element OTTAWA:CMMT-UPGRD:OTTAWA::CTAG24;

Commit the upgrade load on OC3NP:

CMMT-UPGRD:OC3NP::CTAG25;

Commit the upgrade load on slot 3 of network element OTTAWA:

CMMT-UPGRD:OTTAWA:3:CTAG26;


Field Purpose


AID Slot number of the card to upgrade (to be used for slot upgrade only).




CONN-TACC-STS1The Connect Test Access Cross-Connect command is used to provision a test access session for a STS-1 facility.

Note: For a listing of supported cross-connect types for monitor test access sessions, see Table 2-94.


Input syntaxCONN-TACC-STS1:[TID]:FromAID:CTAG::TAPAID:MODE[::LASSO];

Table 2-94Supported test access cross-connect types (monitor mode)

Cross-connect type MONE (FromAid)

MONF (ToAid)

MONEF(FromAid & ToAid)

1WAY (Unidirectional) Yes No No

2WAY (Bidirectional) Yes Yes Yes

1WAYPR (Unidirectional Path Ring) Yes No No

2WAYPR (Bidirectional Path Ring) Yes No No

2WAYBR (Bidirectional Bridge Ring) Yes No No

FFP (Facility Protection Group) Yes No No


Field Purpose


FromAID From access identifier. The facility at one end of the cross-connect. The FromAID specifies the signal source.


TAPAID Test access port access identifier. STS-1 to act on.


LASSO Link association




AID type Possible values Description

FromAID DS3-slot#-port# slot# = 3, 5, 7, or 9port# = 1 to 3 for DS3x3port# = 1 to 12 for DS3x12, DS3x12e, or DS3/EC-1x12

DS3-slot#-port#-%HLINK-Hline-Hslot-Hport

slot# = 3, 5, 7, or 9port# = 1 to 6Hline = OC3 or OC12Hslot = 3 to 10Hport = 1 to 4

EC1-slot#-port# slot# = 3, 5, 7, 9port# = 1 to 3 for EC-1x3port# = 1 to 12 for EC-1x12 or DS3/EC-1x12


OC12-slot#-port#-sts# slot# = 3 to 12 for OC-12slot# = 3 to 10 for OC-12x4 STSport# = 1 for OC-12port# = 1 to 4 for OC-12x4 STSsts# = 1 to 12


OC192-slot#-sts# slot# = 11 or 12sts# = 1 to 192



TAPAID EC1-slot#-port# slot# = 3, 5, 7, 9port# = 1 to 3 for EC-1x3port# = 1 to 12 for EC-1x12 or DS3/EC-1x12

DS3-slot#-port# slot# = 3, 5, 7, or 9port# = 1 to 3 for DS3x3port# = 1 to 12 for DS3x12, DS3x12e, or DS3/EC-1x12


OC12-slot#-port#-sts# slot# = 3 to 10port# = 1 for OC-12port# = 1 to 4 for OC-12x4 STSsts# = 1 to 12




MODE MONE Monitor receive path at “from” end. Creates a single facility access digroup (FAD) test access session.

MONF Monitor receive path at “to” end. Creates a single facility access digroup (FAD) test access session.

MONEF Monitor receive path at both “from” and “to” ends. Creates a dual facility access digroup (FAD) test access session.





Example inputProvision a monitor test access session on the receive path at the “from end” or originating point of the path on a STS-1 facility. In this example the test access connection will be dropped if a loss of association occurs.

CONN-TACC-STS1:MYTOWN:OC3-3-1-1:MYTAG::DS3-3-1:MONE::Y;

LASSO Y Y for yes

Drops the test access connections when the link is dropped.

N (default) N for no

Test access connections are maintained when the link is dropped.

Note: The LASSO parameter only applies when using a Hekimian test set for the test access session. If you are not using a Hekimian test set, the test access session is always maintained when the link is dropped, even if the LASSO parameter is enabled.





CONN-TACC-STS12CThe Connect Test Access Cross-Connect command is used to provision a test access session for a STS-12c facility.

Note: For a listing of supported cross-connect types for monitor test access sessions, see Table 2-94 on page 2-88.


Input syntaxCONN-TACC-STS12C:[TID]:FromAID:CTAG::TAPAID:MODE[::LASSO];


Field Purpose









FromAID OC12-slot#-port#-sts# slot# = 3 to 12port# = 1 for OC-12, 1 to 4 for OC-12x4 STSsts# = 1

OC48-slot#-sts# slot# = 3 to 12sts# = 1,13, 25, 37

OC192-slot#-sts# slot# = 11 or 12sts# = 1,13, 25, ... 181

TAPAID OC12-slot#-port#-sts# slot# = 3 to 10port# = 1 for OC-12, 1 to 4 for OC-12x4 STSsts# = 1

OC48-slot#-sts# slot# = 3 to 10sts# = 1,13, 25, 37



Example inputProvision a monitor test access session on the receive path at the “from end” or originating point of the path on a STS-12c facility. In this example the test access connection will be dropped if a loss of association occurs.

CONN-TACC-STS12C:MYTOWN:OC12-3-1-1:MYTAG::OC12-3-1-1:MONE::Y;






LASSO Y Y for yes












Field Purpose









FromAID OC48-slot#-sts# slot# = 3 to 12sts# = 1, 25

OC192-slot#-sts# slot# = 11 or 12sts# = 1, 25, 49, ...169

TAPAID OC48-slot#-sts# slot# = 3 to 10sts# = 1, 25




CONN-TACC-STS24C:MYTOWN:OC48-3-1:MYTAG::OC48-3-1:MONE::Y;






LASSO Y Y for yes












Field Purpose









FromAID OC3-slot#-port#-sts# slot# = 3 to 10port# = 1 for OC-3port# = 1 to 4 for OC-3x4sts# = 1

OC12-slot#-port#-sts# slot# = 3 to 12 for OC-12slot# = 3 to 10 for OC-12x4 STSport# = 1 for OC-12port# = 1 to 4 for OC-12x4 STSsts# = 1 to 12


OC192-slot#-sts# slot# = 11 or 12sts# = 1,4,7, ... 190




CONN-TACC-STS1:MYTOWN:OC3-3-1-1:MYTAG::OC3-3-1-1:MONE::Y;

TAPAID OC3-slot#-port#-sts# slot# = 3 to 10port# = 1 for OC-3port# = 1 to 4 for OC-3x4sts# = 1

OC12-slot#-port#-sts# slot# = 3 to 10port# = 1 for OC-12port# = 1 to 4 for OC-12x4sts# = 1,4,7,10







LASSO Y Y for yes














Field Purpose









FromAID OC48-slot#-sts# slot# = 3 to 12sts# = 1

OC192-slot#-sts# slot# = 11 or 12sts# = 1, 49, 97, 145

TAPAID OC48-slot#-sts# slot# = 3 to 10sts# = 1




CONN-TACC-STS48C:MYTOWN:OC48-3-1:MYTAG::OC48-3-1:MONE::Y;






LASSO Y Y for yes







CONN-TACC-T1The Connect Test Access Cross-Connect command is used to provision a test access session for a DS1 facility on a DS1, DS3/VT, or DSM circuit pack.



Input syntaxCONN-TACC-T1:[TID]:FromAID:CTAG::TAPAID:MODE[::LASSO];


Field Purpose









FromAID DS1-slot#-port# slot# = 4 to 10, port# =1 to 12



port# = 1 to 84, hslot# = 3 to 10hport# = 1 to 4Hline= OC3 or Oc12



Example inputProvision a monitor test access session on the receive path at the “from end” or originating point of the path on a DS1 facility. In this example the test access connection is maintained if a loss of association occurs.

CONN-TACC-T1:MYTOWN:DS1-4-1:MYTAG::DS1-5-1:MONE::N;

TAPAID DS1-slot#-port# slot# = 4 to 10, port# =1 to 12

EC1-slot#-port#-vtg#-vt# slot# = 3, 5, 7, 9port# = 1 to 3 for EC-1x3port# = 1 to 12 for EC-1x12 or DS3/EC-1x12vtg# = 1 to 7, vt# = 1 to 4


slot# = 3 to 10port# = 1 for OC-3port# = 1 to 4 for OC-3x4 sts#= 1 to 3, vtg# = 1 to 7, vt# = 1 to 4


slot# = 3 to 10port# = 1 sts#= 1 to 12, vtg# = 1 to 7, vt# = 1 to 4



Description




LASSO Y Y for yes. Drops the test access connections when the link is dropped.

N (default) N for no. Test access connections are maintained when the link is dropped.






CONN-TACC-T3The Connect Test Access Cross-Connect command is used to provision a test access session for a DS3 facility.



Input syntaxCONN-TACC-T3:[TID]:FromAID:CTAG::TAPAID:MODE[::LASSO];


Field Purpose









FromAID DS3-slot#-port# slot# = 3, 5, 7, 9port # = 1 to 3 for EC-1x3port # = 1 to 12 for EC-1x12 or DS3/EC-1x12

MS DSM DS3 Facility AID


slot = 3 or 5; port = 1 to 6Hline = OC3 or OC12Hslot = 3 to10Hport = 1 to 4



TAPAID EC1-slot#-port# slot# = 3 to 10 port # = 1 to 3 for EC-1x3port # = 1 to 12 for EC-1x12 or DS3/EC-1x12

DS3-slot#-port# slot# = 3, 5, 7, 9port # = 1 to 3 for EC-1x3port # = 1 to 12 for EC-1x12 or DS3/EC-1x12




OC12-slot#-port#-sts# slot# = 3 to 10port# = 1 sts# = 1 to 12







Table 2-114 (continued)AID description




Example inputProvision a monitor test access session on the receive path at the “from end” or originating point of the path on a DS3 facility. In this example the test access connection is maintained if a loss of association occurs.

CONN-TACC-T3:MYTOWN:DS3-9-3:MYTAG::DS3-9-12:MONE::N;

LASSO Y Y for yes





Table 2-115 (continued)Parameter descriptions




CONN-TACC-VT1The Connect Test Access Cross-Connect command is used to provision a test access session for a VT1.5 facility on a DS1, DS3/VT, DSM, OC-n, or EC-1xn circuit pack.



Input syntaxCONN-TACC-VT1:[TID]:FromAID:CTAG::TAPAID:MODE[::LASSO];


Field Purpose




TAPAID Test access port access identifier. VT1.5 to act on.





FromAID DS1-slot#-port# slot# = 4 to 10, port# =1 to 12

EC1-slot#-port#-vtg#-vt# slot# = 3, 5, 7, 9port # = 1 to 3 for EC-1x3port # = 1 to 12 for EC-1x12 or DS3/EC-1x12vtg# = 1 to 7, vt# = 1 to 4

OC3-slot#-port#-sts#-vtg#-vt# slot# = 3 to 10, port# = 1 for OC-3port# = 1 to 4 for OC-3x4sts# = 1 to 3, vtg# = 1 to 7vt# = 1 to 4

OC12-slot#-port#-sts#-vtg#-vt# slot# = 3 to 12, port# = 1 sts# = 1 to 12, vtg# = 1 to 7vt# = 1 to 4






TAPAID DS1-slot#-port# slot# = 4 to 10, port# =1 to 12


DS1-1-port#-%HLINK-OC3-hslot#-hport#

port# = 1 to 84, hslot# = 3 to 10hport# = 1 to 4



EC1-slot#-port#-vtg#-vt# slot# = 3, 5, 7, 9port # = 1 to 3 for EC-1x3port # = 1 to 12 for EC-1x12 or DS3/EC-1x12vtg# = 1 to 7, vt# = 1 to 4




slot# = 3 to 10port# = 1 sts#= 1 to 12vtg# = 1 to 7, vt# = 1 to 4










Example inputProvision a VT1.5 monitor test access session on the receive path at the “from end” or originating point of the path. In this example the test access connection is dropped if a loss of association occurs.

CONN-TACC-VT1:MYTOWN:OC3-7-1-1-1-1:MYTAG::DS1-4-1:MONE::Y;

LASSO Y Y for yes









CONN-TSTSIG-T1The Connect Test Signal T1 command instructs the network element to connect a test signal to the DS1 facility or monitor a connected signal. To retrieve error count on the monitored signal, use the RTRV-T1 command. Internal test equipment connected with the CONN-TSTSIG-T1 remains connected until it is released using the DISC-TSTSIG-T1 command (see page 2-118).

Before internal test equipment can be connected to a DS1 facility, the facility must be put in an out-of-service state (RMV-T1 command).

In order to clear the error count on the internal signal monitor, disconnect the internal test equipment by using the DISC-TSTSIG-T1 command.


Input syntax CONN-TSTSIG-T1:[TID]:AID:CTAG::[SRC],[DIRN],[TSIG],[ERR];


Field Purpose


AID Access identifier. The facility to act on.


SRC, DIRN, TSIG, ERR See the Parameter descriptions table for details



DS1 DS1-slot#-port# Identify the DS1 facility where slot# = 4 to 10, port# = 1 to 12

DS1 DSM DS1-1-port#-%HLINK-OC3-Hslot#-Hport#

Identify the DS1 facility where port#=1 to 84, Hslot# = 3 to 10, Hport# = 1 to 4

MS DSM DS1 facility

DS1-1-port#-%HLINK-Hline-Hslot#-Hport#

Identify the DS1 facility on the MS DSM where port# = 1 to 84Hline = OC3 or OC12Hslot# = 3 to 10, Hport# = 1 to 4





Description

SRC SRC

MON

Connect the internal signal generator to the facility (default)

Connect the internal signal monitor to the facility

DIRN IN

OUT

Default. Internal signal generator outputs a test signal in the direction of the optics. Internal signal monitor monitors the signal from the copper (DS1) side of the facility.

Internal signal generator outputs a test signal to the copper (DS1) side of the facility. Internal signal monitor monitors the signal from the direction of the optics.

TSIG

PR2017

PR2003

PR1514

PR2318

FIX

QRSS

<number>

The test signal to be sent for or monitored (see notes):

a pseudo-random pattern: x20 + x17 + 1 (default)

a pseudo-random pattern: x20 + x3 + 1



the fixed Daly pattern

a pseudo-random pattern, x20 + x17 + 1, with zero suppression

a fixed pattern made by endlessly repeating the binary version of the number specified by the user. For DS1 facilities on the MS DSM, the supported range is between 0 and 512. For all other DS1 facilities, the supported range is between 0 and 16,777,215

ERR 0 to 1023 The number of errors to be inserted in one second (default is 0). Valid only if the SRC parameter is set to SRC.

Note 1: The PR2003 pattern is not the pattern usually referred to as PR2003 in North American DS1 test sets. It is a rare variant that has been included for completeness. To generate a PR2003 pattern compatible with a North American test set, the PR2017 pattern should be used without zero suppression enabled.

Note 2: DS1 facilities on the MS DSM do not support the PR2003 and FIX pattern.

Note 3: DS1 facilities on the DSM do not support the QRSS pattern. QRSS is only supported by DS1 facilities on the MS DSM.

Note 4: Test set patterns 2e15-1, 2e20-1, and 2e23-1 correspond to a repeating fixed pattern on the Optical Metro 3000. Test set pattern PRBS corresponds to one of the PR2017, PR1514, PR2003, or PR2318 patterns on the Optical Metro 3000. Test set pattern 3:24 does not have an equivalent Optical Metro 3000 pattern.

Note 5: Monitoring of a DS1 facility on the MS DSM will not work properly if the frame format of the facility is set to superframe with TR08 extensions (SF-TR08).



Example inputAt the SEATTLE network element, attach an internal DS1 signal generator to DS1 facility 7 on the slot 4 DS1 mapper. Send the test signal with a pattern of x20 + x17 + 1 and with 10 errors onto the DS1 copper:

CONN-TSTSIG-T1:SEATTLE:DS1-4-7:CTAG12::SRC,OUT,,10;

Monitor the returned pattern:

CONN-TSTSIG-T1:SEATTLE:DS1-4-7:CTAG12::MON,IN,,10;



CONN-TSTSIG-T3The Connect Test Signal T3 command instructs the network element to connect a test signal to the DS3 facility or monitor a connected signal. To retrieve error count on the monitored signal, use the RTRV-T3 command. Internal test equipment connected with the CONN-TSTSIG -T3 remains connected until it is released using the DISC-TSTSIG-T1 command (see page 2-118).

Before internal test equipment can be connected to a DS3 facility, the facility must be put in an out-of-service state (RMV-T3 command).

In order to clear the error count on the internal signal monitor, disconnect the internal test equipment by using the DISC-TSTSIG -T3 command.

For the Multiservice Distributed Service Module (MS DSM), DS3 cross-connects must be present to connect a test signal to a DS3 facility. In addition, you must disconnect the DS3 test signal before you can delete DS3 cross-connects.


Input syntax CONN-TSTSIG-T3:[TID]:AID:CTAG::[SRC],[DIRN],[TSIG];


Field Purpose




SRC, DIRN, TSIG See the Parameter descriptions table for details



MS DSM DS3-slot#-port#-%HLINK-Hline-Hslot#-Hport#

Identify the DS3 facility on theMS DSM whereslot# = 3 or 5; port# = 1 to 6Hline = OC3 or OC12Hslot# = 3 to10, Hport# = 1 to 4





SRC SRC

MON

Connect the internal signal generator to the facility (default)

Connect the internal signal monitor to the facility

DIRN IN

OUT

Default. Internal signal generator outputs a test signal in the direction of the optics. Internal signal monitor monitors the signal from the copper (DS3) side of the facility.

Internal signal generator outputs a test signal to the copper (DS3) side of the facility. Internal signal monitor monitors the signal from the direction of the optics.

TSIG

PR15UFRNER

PR15FRNER

PR15UFRER

PR15FRER

ALL1S

IDLE

PR20UFR

PR23UFR

QRSSUFR

The test signal to be sent for or monitored:

a pseudo-random pattern, 2E+15-1, unframed, unerrored (default)

a pseudo-random pattern, 2E+15-1, framed, unerrored

a pseudo-random pattern, 2E+15-1, unframed, errored

a pseudo-random pattern, 2E+15-1, framed errored

All 1's pattern (only available in SRC mode)

DS3 framed idle (repeating 1100 pattern)

a pseudo-random pattern, 2E+20-1, unframed, unerrored

a pseudo-random pattern, 2E+23-1, unframed, unerrored

a pseudo-random pattern, x20 + x17 + 1, with zero-suppression, unframed

Note: DS3 facilities on the MS DSM support unframed patterns only.



Example inputAt the SEATTLE network element, attach an internal DS3 signal generator to DS3 facility 5-2 of the MS DSM connected to OC12-3-1 host port. Send the test signal with a pattern of x20 + x17 + 1: CONN-TSTSIG-T3:SEATTLE:DS3-5-2-%HLINK-OC12-3-1:CTAG12::SRC,OUT,QRSSUFR;

Monitor the returned pattern:

CONN-TSTSIG-T3:SEATTLE:DS3-5-2-%HLINK-OC12-3-1:CTAG12::MON,IN,QRSSUFR;



DEFRAG-EQPTThe Defragment Equipment command achieves internal bandwidth or physical defragmentation. Bandwidth defragmentation is achieved by sequentially deleting then reprovisioning cross-connects, rearranging the internal backplane bandwidth. Physical defragmentation is achieved by re-ordering the spread of bandwidth or component allocations to make room for new cross-connects.


Input syntaxDEFRAG-EQPT:[TID]:AID:CTAG::[MODE][,FOR_DS1_GROUP];


Field Purpose


AID Access identifier. Equipment to act on.


MODE Defragmentation mode. Omit this parameter to achieve bandwidth defragmentation.

FOR_DS1_GROUP Group number for DS1 physical defragmentations



100FOST 100FOST-slot# Identify the 8x100BT-P2P whereslot# = 3 to 10

MS DSM AID AGGOC3-1-%HLINK-OC3-hslot#-hport#

Identify the MS DSM aggregate circuit pack whereslot# = 1 or 2 HLINE=OC3 or OC12hslot# = 3 to 10, hport# = 1 to 4

AGGOC3OC12-1-%HLINK-HLINE-hslot#-hport#





MODE CONSOLIDATE Re-order the spread of VT1.5 and STS-1 bandwidth allocations to make room for new WAN, VT1.5, STS-1 or STS-3c cross-connects.

FREE_DS1_RSRC Re-order component allocation for DS3 cross-connects to make room for DS1 cross-connects. Use the FOR_DS1_GROUP parameter to select the DS1 group or groups.

FREE_STS3c_WAN_RSRC Re-order component allocation for STS-1 cross-connects to make room for STS-3c cross-connects.

FOR_DS1_GROUP 1 to 3 Select the DS1 group(s), for DS1 physical defragmentations:1 = ports 1 to 282 = ports 29 to 563 = ports 57 to 84

Grouping is allowed.



DISC-TACCThe Disconnect Test Access Cross-Connect command is used to remove individual test access sessions.


Input syntaxDISC-TACC:[TID]:TAPAID:CTAG;


Field Purpose


TAPAID Test access port access identifier.




Example inputDisconnect the path from a test access session.

DISC-TACC:MYTOWN:DS1-4-1:MYTAG;



TAPAID DS1-slot#-port# slot# =4 to 10, port# =1 to 12

DS1-slot#-port#-t1# slot# = 3, 5, 7, 9, port# = 1 to 12t1# = 1 to 28

DS1-1-port#-%HLINK-HLINE-hslot#-hport#

port# = 1 to 84, hslot# = 3 to 10hport# = 1 to 4; Hline= OC3 or OC12

DS3-slot#-port# slot# = 3, 5, 7, or 9port# = 1 to 3 for DS3x3port# = 1 to 12 for DS3x12, DS3x12e, or DS3/EC-1x12


slot = 3 or 5; port = 1 to 6Hline = OC3 or OC12Hslot = 3 to10, Hport = 1 to 4

EC1-slot#-port#-vtg#-vt# slot# = 3, 5, 7, 9port# = 1 to 3 for EC-1x3port# = 1 to 12 for EC-1x12 or DS3/EC-1x12, vtg# = 1 to 7, vt# = 1 to 4

EC1-slot#-port# slot# = 3, 5, 7, 9port# = 1 to 3 for EC-1x3port# = 1 to 12 for EC-1x12 or DS3/EC-1x12



slot# = 3 to 10port# = 1 for OC-3, 1 to 4 for OC-3x4sts#= 1 to 3, vtg# = 1 to 7, vt# = 1 to 4

OC12-slot#-port#-sts# slot# = 3 to 10port# = 1 for OC-12, 1 to 4 for OC-12x4sts# = 1 to 12


slot# = 3 to 10port# = 1 sts#= 1 to 12, vtg# = 1 to 7, vt# = 1 to 4

OC48-slot#-sts# slot# = 3 to 10, sts# = 1 to 48



DISC-TSTSIG-T1The Disconnect Test Signal T1 command instructs the network element to disconnect the DS1 test signal from the facility or stop monitoring a connected DS1 signal. All internal test equipment connected to a facility is disconnected.


Input syntaxDISC-TSTSIG-T1:[TID]:AID:CTAG;

Example inputRemove all internal test equipment on DS1 facility 7 on the DS1 in slot 4:

DISC-TSTSIG-T1:SEATTLE:DS1-4-7:CTAG12;


Field Purpose






DS1 DS1-slot#-port# Identify the DS1 facility whereslot# =4 to 10port# =1 to 12

DS1 DSM DS1-1-port#-%HLINK-OC3-Hslot#-Hport#

Identify the DS1 facility where port#=1 to 84, Hslot# = 3 to 10, Hport# = 1 to 4

MS DSM DS1 facility

DS1-1-port-%HLINK-Hline-Hslot-Hport

port = 1 to 84Hline = OC3 or OC12Hslot = 3 to 10Hport = 1 to 4



DISC-TSTSIG-T3The Disconnect Test Signal T3 command instructs the network element to disconnect the DS3 test signal from the facility or stop monitoring a connected DS3 signal. All internal test equipment connected to a facility is disconnected.


Input syntaxDISC-TSTSIG-T1:[TID]:AID:CTAG;

Example inputRemove all internal test equipment on DS3 facility 5-2 of the MS DSM connected to OC12-3-1 host port: DISC-TSTSIG-T3:SEATTLE:DS3-5-2-%HLINK-OC12-3-1:CTAG12;


Field Purpose








Identify the DS3 facility whereslot = 3 or 5; port = 1 to 6Hline = OC3 or OC12Hslot = 3 to10Hport = 1 to 4



DLT-ALM-PROFILEThe Delete Alarm Profile command allows the user to delete an alarm profile.

Security LevelLevel 3

Input syntaxDLT-ALM-PROFILE:[TID]::CTAG::AIDTYPE,”PRFLNAME”;


Field Purpose



AIDTYPE Access identifier TYPE

PRFLNAME Alarm profile name assigned by user



AIDTYPE VT1 VT1 facility

STS1 STS-1 facility

STS3C STS-3C facility




EQPT equipment

E1 E1 facility

T1 T1 facility

T3 T3 facility

EC1 EC-1 facility

OC3 OC-3 facility

OC12 OC-12 facility



Example input Delete the alarm profile for network element OTTAWA:

DLT-ALM-PROFILE:OTTAWA::CTAG12::OC3,”ALARMSON”;

AIDTYPE OC48 OC-48 facility

OC192 OC-192 facility

FAC conditions attributed to ILAN facilities

COM conditions attributed to shelf or SP

DSM DS1 or DS3 service module facility

SECU Security related

ETH Ethernet facility

WAN WAN facility

FC Fibre Channel

PRFLNAME ASCII string Alarm profile name assigned by user

Alarm profile name-can be up to 20 characters long and must be enclosed within quotation marks (quotation marks and backslash to be excluded from name).





DLT-BANNERThe Delete Banner command is used to delete the current login banner warning text and restore the default login banner warning text for a network element or NP. The login banner warning text is displayed when you log in to a TL1 session on a network element or NP.


Input syntaxDLT-BANNER:[TID]::CTAG;

Example inputDelete the login banner warning text for network element OTTAWA:

DLT-BANNER:OTTAWA::CTAG93;


Field Purpose





DLT-BLSRRINGUse the Delete BLSR Ring command to delete a BLSR ring and its associated map. This command is supported on the network processor.


Input syntaxDLT-BLSRRING:[TID]:AID:CTAG:::[DELETE=DOMAIN];

Example inputDelete the BLSR ring and its ring map for NPFGXOTT:DLT-BLSRRING:NPFGXOTT:RING1:CTAG:::DELETE=Y;


Field Purpose


AID Ring name


DELETE Delete status







DELETE Y Delete ring and all nodes on ring

N (default) Only delete ring with no nodes



DLT-CRS-STS1The Delete Cross-connect STS1 command is used to delete an STS-1 cross-connect between two STS-1 facilities.

Note 1: Bandwidth assigned to a Resilient Packet Ring (RPR) cannot be removed until all Packet Edge circuit packs have been detached from the RPR.

Note 2: For DS3 facilities on the MS DSM, you cannot delete DS3 cross-connects if a test signal is connected to the facility. You must first disconnect the test signal.


Input syntaxDLT-CRS-STS1:[TID]:FromAID,ToAID:CTAG::[CCT]:[SWMATE=Domain];


Field Purpose


FromAID From access identifier. The facility at one end of the cross-connect. If the connection is unidirectional, the FromAID specifies the signal source.

ToAID To access identifier. The facility at the other end of the cross-connect. If the connection is unidirectional, the ToAID specifies the signal destination.


CCT Cross-connection type

SWMATE Path protection Switch Mate. Path protection for the FromAID OC-3, OC-3x4, OC-12, OC-12x4, OC-48, OC-48 STS, or OC-192 interface only when the CCT is protected. That is, when the CCT is one of 1WAYPR, 2WAYPR, or 2WAYBR.




AID type Command-specificvalues

Purpose

STS-1 Facility AID


OC12-slot#-port#-sts# Identify the STS-1 facility on an OC-12 or OC-12x4 STS circuit pack whereslot# = 3 to 12port# = 1 for OC-12port# = 1 to 4 for OC-12x4 STSsts# = 1 to 12

OC48-slot#-sts# Identify the STS-1 facility on an OC-48 or OC-48 STS circuit pack whereslot# = 11, 12 for OC-48slot# = 3 to 12 for OC-48 STSsts# = 1 to 48

OC192-slot#-sts# Identify the STS-1 facility on an OC-192 circuit pack whereslot# = 11, 12sts# = 1 to 192

EC1-slot#-port# Identify the STS-1 facility on an EC-1 circuit pack whereslot# = 3, 5, 7, 9port # = 1 to 3 for EC-1x3port # = 1 to 12 for EC-1x12 or DS3/EC-1x12

DS3-slot#-port# Identify the STS-1 facility on a DS3 circuit pack whereslot# = 3, 5, 7, or 9port# = 1 to 3 for DS3x3port# = 1 to 12 for DS3x12, DS3x12e, or DS3/EC-1x12



STS-1 Facility AID

WAN-slot#-port#-sts# Identify the STS-1 facility on the WAN port whereslot# = 3 to 10port# = 1 or 2 for 2xGigE/FC-P2P, 2xGigE/FC-P2P-C, 2xGigE-P2P, or 2x100BT-P2Pport# = 1 to 4 for 4x100FX-P2Pport# = 1 to 8 for 8x100BT-P2Psts# = 1 for 2x100BT-P2Psts# = 1 to 3 for 4x100FX-P2Por 8x100BT-P2Psts# = 1 to 21 for 2xGigE/FC-P2P, 2xGigE/FC-P2P-C, or 2xGigE-P2P

STS1 facility AID on MS DSM






grp = 1 to 3grp 1 =DS1s 1 to 28grp 2 = DS1s 29 to 56grp 3 = DS1s 57 to 84 Hline = OC3 or OC12Hslot = 3 to 10Hport = 1 to 4

RPR AID

IPTR-index# Identify the RPR where index# = 1 to 8

IPTR-index#-port#-sts# Identify the RPR, for RPRs that have virtual concatenation enabled, where index# = 1 to 8port# = 1 or 2sts# = 1 to 24


AID type Command-specificvalues

Purpose



AID, CCT, and SWMATE usage Figure 4-1 on page 4-122 shows valid combinations of AID, CCT, and SWMATE along with the resulting facility connections.

Example inputFor the NEWYORK network element, delete the bidirectional STS-1 passthrough cross-connection between the OC-3x4 in slot 9 port 1 sts 1 and slot 10 port 1 sts 1:

DLT-CRS-STS1:NEWYORK:OC3-9-1-1,OC3-10-1-1:CTAG12::2WAY;

For the SEATTLE network element, delete the bidirectional STS-1 cross-connection between the DS3x3 circuit pack in slot 9 port 1 and the path protected OC-3x4 interfaces in slot 9 port 1 sts 1 and slot 10 port 1 sts 1:

DLT-CRS-STS1:SEATTLE:OC3-9-1-1,DS3-9-1:CTAG12::2WAYPR:SWMATE=OC3-10-1-1;



CCT 1WAY

2WAY

1WAYPR

2WAYPR

2WAYBR

IPTRING

Unidirectional connection

Bidirectional connection (default)

Unidirectional path ring connection

Bidirectional path ring connection

Bidirectional bridge ring connection

SONET bandwith allocation for RPR

SWMATE OC3-slot#-port#-sts# Identify the STS-1 facility on an OC-3 circuit pack whereslot# = 3 to 10port# = 1 for OC-3, 1 to 4 for OC-3x4sts# = 1 to 3

OC12-slot#-port#-sts# Identify the STS-1 facility on an OC-12 circuit pack whereslot# = 3 to 12port# = 1 for OC-12, 1 to 4 for OC-12x4sts# = 1 to 12

OC48-slot#-sts# Identify the STS-1 facility whereslot# = 11, 12 for OC-48slot# = 3 to 12 for OC-48 STSsts# = 1 to 48

OC192-slot#-sts# Identify the STS-1 facility whereslot# = 11, 12, sts# = 1 to 192



DLT-CRS-STS12CThe Delete Cross-connect STS-12c command is used to delete an STS-12c cross-connect between two STS-12c facilities.

Note: Bandwidth assigned to a Resilient Packet Ring (RPR) cannot be removed until all Packet Edge circuit packs have been detached from the RPR.


Input syntaxDLT-CRS-STS12C:[TID]:FromAID,ToAID:CTAG::[CCT]:[SWMATE=Domain];


Field Purpose


FromAID From access identifier. The STS-12c facility at one end of the cross-connect. If the connection is unidirectional, the FromAID specifies the signal source.

ToAID To access identifier. The STS-12c facility at the other end of the cross-connect. If the connection is unidirectional, the ToAID specifies the signal destination.



SWMATE The path protection for the FromAID when the CCT is protected. That is, when the CCT is one of 1WAYPR or 2WAYPR.






OC12-slot#-port#-sts# Identify the STS-12c facility on an OC-12 or OC-12x4 STS circuit pack whereslot# = 3 to 12port# = 1 for OC-12port# = 1 to 4 for OC-12x4 STSsts# = 1

OC48-slot#-sts# Identify the STS-12c facility on an OC-48 circuit pack whereslot# = 11 or 12 for OC-48slot# = 3 to 12 for OC-48 STSsts# = 1, 13, 25, 37



RPR AID




CCT 1WAY

2WAY

1WAYPR

2WAYPR

2WAYBR

IPTRING









Example inputFor network element NEWYORK, delete the bidirectional STS-12c pass-through cross-connect between OC-48, slot 11, sts 1 and OC-48, slot 12, sts 25: DLT-CRS-STS12C:NEWYORK:OC48-11-1,OC48-12-25:CTAG12::2WAY;

SWMATE OC12-slot#-port#-sts# Identify the STS-12c facility whereslot# = 3 to 12port# = 1 for OC-12, 1 to 4 for OC-12x4sts# = 1

OC48-slot#-sts# Identify the STS-12c facility whereslot# = 11 or 12 for OC-48slot# = 3 to 12 for OC-48 STSsts# = 1, 13, 25, 37

OC192-slot#-sts# Identify the STS-12c facility whereslot# = 11, 12sts# = 1, 13, 25, 37, ... 181









Field Purpose









Example inputFor the NEWYORK network element, delete the bidirectional STS-24c passthrough cross-connection between the OC-48 STS in slot 11 sts 1 and slot 12 sts 25: DLT-CRS-STS24C:NEWYORK:OC48-11-1,OC48-12-25:CTAG12::2WAY;




OC48-slot#-sts# Identify the STS-24c facility on an OC-48 circuit pack whereslot# = 3 to 12sts# = 1, 25

OC192-slot#-sts# Identify the STS-24c facility on an OC-192 circuit pack whereslot# = 11, 12sts# = 1, 25, ... 169





2WAY Bidirectional connection (default)

1WAYPR Unidirectional path ring connection

2WAYPR Bidirectional path ring connection

2WAYBR Bidirectional bridge ring connection

SWMATE OC48-slot#-sts# Identify the STS-24c facility whereslot# = 3 to 12sts# = 1, 25

OC192-slot#-sts# Identify the STS-24c facility whereslot# = 11, 12sts# = 1, 25, ... 169




Note: Bandwidth assigned to a Resilient Packet Ring (RPR) cannot be removed until all Packet Edge circuit packs have been detached from the RPR.




Field Purpose






SWMATE Path protection Switch Mate. Path protection for the FromAID OC-3, OC-3x4, OC-12, OC-12x4, OC-48, OC-48 STS, or OC-192 interface only when the CCT is protected. That is, when the CCT is one of 1WAYPR, 2WAYPR, or 2WAYBR.





Purpose

STS-3c Facility AID

OC3-slot#-port#-sts# Identify the STS-3c facility on an OC-3 circuit pack whereslot# = 3 to 10port# = 1 for OC-3port# = 1 to 4 for OC-3x4sts# =1

OC12-slot#-port#-sts# Identify the STS-3c facility on an OC-12 or OC-12x4 STS circuit pack where slot# = 3 to 12port# = 1 for OC-12port# = 1 to 4 for OC-12x4 STSsts# = 1, 4, 7, or 10

OC48-slot#-sts# Identify the STS-3c facility on an OC-48 or OC-48 STS circuit pack whereslot# = 11, 12 for OC-48slot# = 3 to 12 for OC-48 STSsts# = 1, 4, 7, 10, ...to 46

OC192-slot#-sts# Identify the STS-3c facility on an OC-192 circuit pack whereslot# = 11, 12sts# = 1, 4, 7, 10, ...to 190

WAN-slot#-port#-sts# Identify the STS-3c facility on the WAN port whereslot# = 3 to 10port# = 1 or 2 for 2xGigE/FC-P2P, 2xGigE/FC-P2P-C, 2xGigE-P2P, or 2x100BT-P2Pport# = 1 to 4 for 4x100FX-P2Pport# = 1 to 8 for 8x100BT-P2Psts# = 1 for 2x100BT-P2P, 4x100FX-P2P, or 8x100BT-P2Psts# = 1, 4, 7, ... 19 for 2xGigE/FC-P2P, 2xGigE/FC-P2P-C, or 2xGigE-P2P


Identify the STS-3c facility on the WAN port whereslot = 3 to 6; port = 1 to 8sts = 1; Hline = OC3 or OC12Hslot = 3 to 10Hport = 1 to 4

RPR AID





Example inputFor the NEWYORK network element, delete the bidirectional STS-3c passthrough cross-connection between the OC-3x4 in slots 9 and 10:

DLT-CRS-STS3C:NEWYORK:OC3-9-1-1,OC3-10-1-1:CTAG12::2WAY;

Deprovision the bandwidth from an RPRDLT-CRS-STS3C:OC3SP:OC3-9-1-1,IPTR-1:CTAG12::IPTRING;

DLT-CRS-STS3C:OC3SP:OC3-10-1-1,IPTR-1:CTAG12::IPTRING;



CCT 1WAY

2WAY

1WAYPR

2WAYPR

2WAYBR

IPTRING







SWMATE OC3-slot#-port#-sts# Identify the STS-3c facility whereslot# = 3 to 10port# = 1 for OC-3port# = 1 to 4 for OC-3x4sts# = 1

OC12-slot#-port#-sts# Identify the STS-3c facility whereslot# = 3 to 12port# = 1 for OC-12port# = 1 to 4 for OC-12x4 STSsts# = 1, 4, 7 or 10

OC48-slot#-sts# Identify the STS-3c facility whereslot# = 11, 12 for OC-48slot# = 3 to 12 for OC-48 STSsts# = 1, 4, 7, 10, ...to 46

OC192-slot#-sts# Identify the STS-3c facility whereslot# = 11, 12sts# = 1, 4, 7, 10, ...to 190







Field Purpose









STS-48c Facility AID OC48-slot#-sts# slot# = 3 to 12sts# = 1

OC192-slot#-sts# slot# = 11, 12sts# = 1, 49, ... 145



Example inputFor the NEWYORK network element, delete the bidirectional STS-48c passthrough cross-connection between the OC-48 STS in slot 11 sts 1 and slot 12 sts 1: DLT-CRS-STS48C:NEWYORK:OC48-11-1,OC48-12-1:CTAG12::2WAY;








SWMATE OC48-slot#-sts# Identify the STS-48c facility whereslot# = 3 to 12sts# = 1

OC192-slot#-sts# Identify the STS-48c facility whereslot# = 11, 12sts# = 1, 49 ... 145



DLT-CRS-VT1The Delete Cross-connect VT1.5 command is used to delete a VT1.5 cross-connect from between two VT1.5 facilities.


Input syntaxDLT-CRS-VT1:[TID]:FromAID,ToAID:CTAG::[CCT]:[SWMATE=Domain];


Field Purpose


FromAID From access identifier. The VT1.5 path facility at one end of the cross-connect. If the connection is unidirectional, the FromAID specifies the signal source.

ToAID To access identifier. The VT1.5 path facility at the other end of the cross-connect. If the connection is unidirectional, the ToAID specifies the signal destination.



SWMATE Path protection Switch Mate. Path protection for the FromAID OC-3, OC-3x4, OC-12 or OC-48 interface only when the CCT is protected. That is, when the CCT is one of 1WAYPR, 2WAYPR, or 2WAYBR.



VT1.5 facility AID

DS1-slot#-port# slot# = 4 to 10port# = 1 to 12


slot# = 3, 5, 7, 9port# = 1 to 12t1# = 1 to 28


DS1 service module port# = 1 to 84hslot# = 3 to 10hport# = 1 to 4



DS1-DFLT-grp#-%HLINK-OC3-hslot#-hport#

DS1 service module grp# = 1 to 3hslot# = 3 to 10hport# = 1 to 4

OC3-slot#-sts#-port#-vtg#-vt#OC3-slot#-port#-sts#-vtg#-ALLOC3-slot#-port#-sts#-ALL

slot# = 3 to 10port# = 1 for OC-3port# = 1 to 4 for OC-3x4sts# = 1 to 3vtg# = 1 to 7, vt# = 1 to 4

OC12-slot#-port#-sts#-vtg#-vt#OC12-slot#-port#-sts#-vtg#-ALLOC12-slot#-port#-sts#-ALL

slot# = 3 to 12port# = 1sts# = 1 to 12vtg# = 1 to 7, vt# = 1 to 4

OC48-slot#-sts#-vtg#-vt#OC48-slot#-sts#-vtg#-ALLOC48-slot#-sts#-ALL

slot# = 11, 12sts# = 1 to 48vtg# = 1 to 7, vt# = 1 to 4

EC1-slot#-port#-vtg#-vt#EC1-slot#-port#-vtg#-ALLEC1-slot#-port#-ALL

slot# = 3, 5, 7, 9port # = 1 to 3 for EC-1x3port # = 1 to 12 for EC-1x12 or DS3/EC-1x12vtg# = 1 to 7, vt# = 1 to 4



MS DSM WAN facility

WAN-slot#-port#-sts#-vtg#-vt#-%HLINK-Hline-Hslot#-Hport#

WAN-slot#-port#-sts#-vtg#-ALL-%HLINK-Hline-Hslot#-Hport#

WAN-slot#-port#-sts#-ALL-%HLINK-Hline-Hslot#-Hport#

slot# = 3 to 10port# = 1 to 8 sts# = 1 to 3vtg# = 1 to 7 for sts# = 1 or 2vtg# = 1 or 2 for sts# = 3vt# = 1 to 4

SMART AID DS1-DFLT-grp# grp# = 1 to 3





Use the DFLT-# smart AID to delete one of three sets of 28 DS1s cross-connected to VT1.5s within an STS-1. For each possible DFLT-# value, a specific set of 28 ports is cross-connected to an STS-1. For example, the DFLT-2 set of DS1 ports can be mapped to STS1-3. This causes DS1 ports 29 through 56 to be cross-connected to STS1-3. Table 2-157 shows the DFLT-# smart AID value and the corresponding ports.

Table 2-157DFLT-# smart AID values

DFLT-# Ports Equivalent facilities

1 1 to 28 DS1-4-1 — DS1-6-4

2 29 to 56 DS1-6-5 — DS1-8-8

3 57 to 84 DS1-8-9 — DS1-10-12








SWMATE OC3-slot#-port#-sts#-vtg#-vtOC3-slot#-port#-sts#-vtg#-ALLOC3-slot#-port#-sts#-ALL

Identify the VT1.5 facility whereslot# = 3 to 10port# = 1 for OC-3, 1 to 4 for OC-3x4sts# = 1 to 3, vtg# = 1 to 7vt# = 1 to 4


Identify the VT1.5 facility whereslot# = 3 to 12port# = 1sts# = 1 to 12, vtg# = 1 to 7vt# = 1 to 4


Identify the VT1.5 facility whereslot# = 11, 12sts# = 1 to 48, vtg# = 1 to 7vt# = 1 to 4




Example inputFor the NEWYORK network element, delete a VT1.5 bidirectional cross-connect between the DS1 mapper in slot 4 and the path protected optical interfaces in slots 8 and 9:

DLT-CRS-VT1:NEWYORK:OC3-8-2-1-1-2,DS1-4-1:CTAG45::2WAYPR:SWMATE=OC3-9-2-1-1-3;

For the WASHINGTON network element, delete 28 bidirectional VT1.5 cross-connects between the DFLT-1 VT1.5 facilities (DS1 ports 1 to 12 on the slot 4 DS1 mapper, DS1 ports 1 to 12 on the slot 5 DS1 mapper and DS1 ports 1 to 4 on the slot 6 DS1 mapper), from the path protected optical interfaces in slots 9 and 11: DLT-CRS-VT1:WASHINGTON:OC3-9-3-1-ALL,DS1-DFLT-1:CTAG89::2WAYPR:SWMATE=OC3-11-3-1-ALL;



DLT-EC1The Delete EC-1 command is used to eliminate the EC-1 facility from the EC-1 circuit pack; the EC-1 facility provisioning information is deleted and all other information (errors, monitoring points) is ignored. Before you delete an EC-1 facility, you must delete all connections on the facility, delete any SDCC links on the EC-1, ensure the facility is not used as a timing reference, and put the facility OOS.


Input syntaxDLT-EC1:[TID]:AID:CTAG;

Example inputDelete the EC-1 facility in slot 7 port 2:

DLT-EC1:SEATTLE:EC1-7-2:CTAG04;


Field Purpose


AID Access identifier. EC-1 facility to act on.




EC1 AID EC1-slot#-port#EC1-slot-ALL

Identify the EC-1 slot where slot# = 3, 5, 7, 9port # = 1 to 3 for EC-1x3port # = 1 to 12 for EC-1x12



DLT-EQPTThe Delete Equipment command is used to delete the provisioning information for the specified equipment.

When you delete OC-3x4, OC-12 or OC-12x4 STS equipment, the section data communications channel (SDCC) link is also affected (layers 1, 2).

Note 1: Equipment cannot be deleted if any facilities are provisioned on the equipment except the OC-3/OC-12 facilities for aggregate circuit packs of the MS DSM. The working aggregate equipment can only be deleted once the following has been completed:

— The on-board OCN facility has been taken out-of-service

— All DS1, DS3, and 10/100 BaseT facilities have been deleted

— The on-board PSM equipment has been deleted

— The aggregate equipment has been taken Out Of Service

— Protection aggregate equipment and all expansion PSM equipment are not provisioned/deleted

Note 2: The protection aggregate equipment can only be deleted once the following has been completed:

— The OCN facility has been taken out-of-service

— The on-board PSM equipment has been deleted

— The aggregate equipment has been taken out-of-service

Note 3: The OC-3 facility of the DS1 service module must be taken out of service. The facility cannot be deleted.


Input syntaxDLT-EQPT:[TID]:AID:CTAG;


Field Purpose


AID Access identifier. Equipment to act on.






Purpose

DS1 AID DS1-slot# Identify the DS1 equipment where slot# = 3 to 10

DS3 AID DS3-slot# Identify the DS3 equipment where slot# = 3 to 10

DS3VT AID DS3V-slot# Identify the DS3VTx12 equipment where slot# = 3 to 10

DS3/EC1 AID

DS3EC1-slot# Identify the DS3/EC1x12 equipment whereslot# = 3 to 10

OC-3 AID OC3-slot# Identify the OC-3 equipment where slot# = 3 to 10

OC-12 AID OC12-slot# Identify the OC-12 or OC-12x4 STS equipment whereslot# = 3 to 12 for OC-12slot# = 3 to 10 for OC-12x4 STS

OC-48 AID OC48-slot# Identify the OC-48 equipment whereslot# = 11, 12 for OC-48slot# = 3 to 12 for OC-48 STS

OC-48 DWDM SFP AID

POC48-slot#-port# Identify the OC-48 DWDM SFP module whereslot# = 3 to 12, port# = 1

OC-192 AID OC192-slot# Identify the OC-192 equipment whereslot# = 11, 12

EC1 AID EC1-slot# Identify the EC-1 equipment whereslot# = 3 to 10

ILAN AID ILAN Identify the ILAN equipment

PSC AID PSC Identify the protection switch controller

PSX AID PSX Identify the protection switch extender

Note: The PSX can only be deleted if DS1-6-5 and higher do not exist.

NP AID NP Identify the network processor

IPT100 AID IPT100-slot# Identify the 4x100BT equipment whereslot# = 3 to 10

GE AID GE-slot#-port# Identify the 2xGigE 2.5G SFP module where slot# = 3, 5, 7, 9 port#=1, 2



1GE AID 1GE-slot# Identify the 2xGigE equipment whereslot# = 3, 5, 7, 9 for double slot cards and slot#=3 to 10 for single slot 2xGigE.

100FX AID 100FX-slot# Identify the 4x100FX equipment whereslot# = 3 to 10

100BTFOS AID

100BTFOS-slot# Identify the 2x100BT-P2P circuit packwhere slot# = 3 to 10

1GFOS AID 1GFOS-slot# Identify the 2xGigE/FC-P2P, 2xGigE/FC-P2P-C or 2xGigE-P2P equipmentwhere slot# = 3 to 10

100FOSO AID

100FOSO-slot# Identify the 4x100FX-P2P equipment where slot# = 3 to 10

100FOST AID

100FOST-slot# Identify the 8x100BT-P2P equipment where slot# = 3 to 10

1GE25G AID 1GE25G-slot# Identify the 2xGigE 2.5G equipmentwhere slot# = 3, 5, 7, 9

GEFC AID GEFC-slot#-port# Identify the 2xGigE/FC-P2P, 2xGigE/FC-P2P-C or 2xGigE-P2P SFP module, whereslot# = 3 to 10port# = 1, 2

DS1TM AID DS1TM-slot#-%HLINK-OC3-hslot#-hport#

Identify the DSM DS1 termination module, whereslot# = 1 or 2, hslot# = 3 to 10, hport# = 1 to 4



Purpose



Example inputDelete the DS1 circuit pack in slot 4:

DLT-EQPT:NEWYORK:DS1-4:CTAG23;

MS DSM AID AGGOC3-slot#-%HLINK- HLINE- hslot#-hport#

Identify the MS DSM Aggregate equipment, whereHLINE= OC3slot# = 1 or 2, hslot# = 3 to 10, hport# = 1 to 4

AGGOC3OC12- slot#-%HLINK- HLINE- hslot#-hport#

Identify the MS DSM Aggregate equipment, whereHLINE= OC3 or OC12slot# = 1 or 2, hslot# = 3 to 10, hport# = 1 to 4

PECN-slot#-%HLINK-HLINE-hslot#-hport#

Identify the MS DSM DS3 Expansion equipment, whereHLINE=OC3 or OC12slot# = 3 to 6, hslot# = 3 to 10, hport# = 1 to 4

PFOST-slot#-%HLINK-HLINE-hslot#-hport#

Identify the MS DSM 10/100BaseT Expansion equipment, whereHLINE=OC3 or OC12slot# = 3 to 6, hslot# = 3 to 10, hport# = 1 to 4

POC3-slot#-port#-%HLINK-HLINE-hslot#-hport#

Identify the MS DSM OC-3 SFP, whereHLINE=OC3slot# = 1 or 2, port#=1, hslot# = 3 to 10, hport# = 1 to 4

POC3OC12-slot#-port#-%HLINK-HLINE-hslot#-hport#

Identify the MS DSM OC-3/12 SFP, whereHLINE=OC3 or OC12slot# = 1 or 2, port# = 1, hslot# = 3 to 10, hport# = 1 to 4



Purpose



DLT-ETHUse the Delete Ethernet command to deprovision an Ethernet facility of a 2x100BT-P2P, 8x100BT-P2P, 2xGigE/FC-P2P, 2xGigE/FC-P2P-C, 4x100FX-P2P or 2xGigE-P2P.

The command deletes facility provisioning information. Other information (errors, monitoring points) is ignored.

Before you delete an Ethernet facility, you must delete all connections on the WAN port associated with the Ethernet facility and put the Ethernet facility out-of-service (OOS). To delete connections, see:

• DLT-CRS-STS1 on page 2-124

• DLT-CRS-STS3C on page 2-133



To put an Ethernet facility OOS, see RMV-ETH on page 3-393.


Input syntaxDLT-ETH:[TID]:AID:CTAG;


Field Purpose


AID Access identifier. The Ethernet facility to deprovision.




Example inputDeprovision ETH port 1 of the 2x100BT-P2P circuit pack in slot 7 of network element OTTAWA: DLT-ETH:OTTAWA:ETH-7-1:CTAG01;



ETH AID ETH-slot#-port#ETH-slot#-ALL

Identify the Ethernet facility where slot# = 3 to 10port# = 1 to 8 for 8x100BT-P2Pport# = 1 to 4 for 4x100FX-P2Pport# = 1 to 2 for all the other supported cards

MS DSM Ethernet Facility

ETH-slot-port-%HLINK-Hline-Hslot-Hport

slot = 3 to 6; port = 1 to 8Hline = OC3 or OC12Hslot = 3 to10Hport = 1 to 4



DLT-FACThe Delete Facility command is used to delete an NP facility. NP facilities include ILANSP, ILANNP, ILAN1, ILAN2, COLAN, and X25. ILANSP and ILANNP are autoprovisioned and cannot be manually deprovisioned.

Note: You cannot delete a COLAN facility if any of the GRE facilities are active.


Input syntaxDLT-FAC:[TID]:AID:CTAG;

Example inputDelete the ILAN-2 facility on OC3NP:DLT-FAC:OC3NP:ILAN2:CTAG24;


Field Purpose


AID Access identifier. The NP facility to act on.




AID ILAN1ILAN2COLANX25ALL

Intershelf LAN-1Intershelf LAN-2Central office LANX.25All facility entities

Note: An AID of ALL is supported but command execution will stop if the operation fails for one facility. In this case, delete each facility individually.



DLT-FCUse the Delete Fibre Channel command to deprovision a Fibre Channel facility (FC port) on the GE/FC SFP of a 2xGigE/FC-P2P or 2xGigE/FC-P2P-C circuit pack.

The command deletes facility provisioning information. Other information (errors, monitoring points) is ignored.

Before you delete a Fibre Channel facility, you must delete all connections on the WAN port associated with the Fibre Channel facility and put the Fibre Channel facility out-of-service (OOS). To delete connections, see:

• DLT-CRS-STS1 on page 2-124




To put a Fibre Channel facility OOS, see RMV-FC on page 3-394.


Input syntaxDLT-FC:[TID]:AID:CTAG;

Example inputDeprovision FC port 1 of the GE/FC SFP of a 2xGigE/FC-P2P or 2xGigE/FC-P2P-C circuit pack in slot 7 of network element OTTAWA: DLT-FC:OTTAWA:FC-7-1:CTAG01;


Field Purpose


AID Access identifier. The Fibre Channel facility to deprovision.




FC FC-slot#-port#FC-slot#-ALL

Identify the Fibre Channel facility where slot# = 3 to 10port# = 1 or 2



DLT-FFP-OC12The Delete FFP OC-12 command is used to delete 1+1 protection for an OC-12 linear facility. Of the pair, the protection facility is in the even slot. The protection OC-12 facility must be OOS-MA (out of service maintenance for memory administration) before the FFP can be deleted. The OC-12 and OC-12x4 STS run in simplex mode once you delete the FFP. Connections on the protection OC-12 are deleted when you delete the FFP. Deleting protection also affects how the section data communication channel (SDCC) operates.

Note 1: Ensure that facilities on the protection circuit pack are out of service.

Note 2: You cannot execute this command if there is an active test access session on this facility.


Input syntaxDLT-FFP-OC12:[TID]:workingOC12AID,protectionOC12AID:CTAG;

Example inputDelete 1+1 protection for the OC-12 facility in slot 7 port 1 and slot 8 port 1: DLT-FFP-OC12:SEATTLE:OC12-7-1,OC12-8-1:CTAG13;


Field Purpose


AID Access identifier. OC-12 facility to act on.




Purpose

working OC-12 AID

OC12-slot#-port# Identify the slot number of the working facilityslot# = 3, 5, 7, 9, or 11 for OC-12slot# = 3, 5, 7, or 9 for OC-12x4 STSport# = 1 for OC-12, 1 to 4 for OC-12x4 STS

protection OC-12 AID

OC12-slot#-port# Identify the slot number of the protection facilityslot# = 4, 6, 8, 10, or 12 for OC-12slot# = 4, 6, 8, or 10 for OC-12x4 STSport# = 1 for OC-12, 1 to 4 for OC-12x4 STS



DLT-FFP-OC192The Delete FFP OC-192 command is used to delete the specified protection scheme for an OC-192 facility. The OC-192 protection facility is in the even slot. The OC-192 protection facility must be OOS-MA (out of service maintenance for memory administration) before the FFP can be deleted. The OC-192 equipment runs in simplex mode once you delete the FFP. Connections on the protection OC-192 are deleted when you delete the FFP. Deleting protection also affects how the section data communication channel (SDCC) operates.

Note: You cannot execute this command if there is an active test access session on this facility.


Input syntaxDLT-FFP-OC192:[TID]:workingOC192AID,protectionOC192AID:CTAG:::[PS=Domain];


Field Purpose


workingOC192AID Working side access identifier. OC-192 facility to act on.

protectionOC192AID Protection side access identifier. OC-192 facility to act on.


PS Protection scheme to delete



Purpose

working OC-192 AID

OC192-slot# Identifies the slot number of the working OC-192 where slot# = 11

protection OC-192 AID (see Note)

OC192-slot# Identifies the slot number of the protection OC-192 where slot# = 12

Note: Ensure that facilities on the protection circuit pack are out of service.



Example inputDelete 1+1 protection for the OC-192 facility in slot 11and slot 12: DLT-FFP-OC192:SEATTLE:OC192-11,OC192-12:CTAG13;



PS 1PLUS1 Delete the 1+1 linear protection scheme (default)

BLSR_2FR Delete the 2-Fiber BLSR protection scheme



DLT-FFP-OC3The Delete FFP OC-3 command is used to delete 1+1 protection for an OC-3 linear facility. Of the pair, the protection facility is in the even slot. The protection OC-3 facility must be OOS-MA (out of service maintenance for memory administration) before the FFP can be deleted. The OC-3 and OC-3x4 equipment runs in simplex mode once you delete the FFP. Connections on the protection OC-3 are deleted when you delete the FFP. Deleting protection also affects how the section data communication channel (SDCC) operates.

Note 1: Ensure that facilities on the protection circuit pack are out of service.



Input syntaxDLT-FFP-OC3:[TID]:workingOC3AID,protectionOC3AID:CTAG;

Example inputDelete 1+1 protection for the OC-3 facility in slot 9 port 1 and slot 10 port 1: DLT-FFP-OC3:SEATTLE:OC3-9-1,OC3-10-1:CTAG13;


Field Purpose






Purpose

working OC3 AID

OC3-slot#-port# Identify the slot number of the working OC-3 where slot# = 3, 5, 7, 9port# = 1 for OC-3port# = 1 to 4 for OC-3x4

protection OC3 AID

OC3-slot#-port# Identify the slot number of the protection OC-3 where slot# = 4, 6, 8, 10port# = 1 for OC-3port# = 1 to 4 for OC-3x4



DLT-FFP-OC48The Delete FFP OC-48 command is used to delete the specified protection scheme for an OC-48 facility. The OC-48 protection facility is in the even slot. The OC-48 protection facility must be OOS-MA (out of service maintenance for memory administration) before the FFP can be deleted. The OC-48 or OC-48 STS equipment runs in simplex mode once you delete the FFP. Connections on the protection OC-48 are deleted when you delete the FFP. Deleting protection also affects how the section data communication channel (SDCC) operates.

Note: You cannot execute this command if there is an active test access session on this facility.


Input syntaxDLT-FFP-OC48:[TID]:workingOC48AID,protectionOC48AID:CTAG:::[PS=Domain];


Field Purpose





PS Protection scheme to delete



Example inputDelete 1+1 protection for the OC-48 facility in slot 11and slot 12: DLT-FFP-OC48:SEATTLE:OC48-11,OC48-12:CTAG13;



Purpose

working OC-48 AID OC48-slot# Identifies the slot number of the working OC-48 or OC-48 STSslot# = 11 for OC-48slot# = 3, 5, 7, 9, or 11 for OC-48 STS


(see Note)

OC48-slot# Identifies the slot number of the protection OC-48 or OC-48 STSslot# = 12 for OC-48slot# = 4, 6, 8, 10, or 12 for OC-48 STS

Note: Ensure that facilities on the protection circuit pack are out of service.



PS 1PLUS1 Delete the 1+1 linear protection scheme (default)

BLSR_2FR Delete the 2-Fiber BLSR protection scheme



DLT-GREThe Delete GRE command is used to delete a specific GRE tunnel.

This command is supported on the network processor only.

Note: If GRE is provisioned on a Release 14.1 (or higher) network processor running on a Release 11.12 or Release 11.5 Optical Metro 3300/3400 shelf, you will need to re-perform system lineup and testing (SLAT) of the Optical Metro 3300/3400 shelf if

— GRE is deleted on the Release 14.1 (or higher) network processor and

— the Release 14.1 (or higher) network processor is replaced with a Release 11.12 or Release 11.5 network processor


Input syntaxDLT-GRE:[TID]:[AID]:CTAG;

Example inputDelete the GRE tunnel on OC3NP:

DLT-GRE:OC3NP::CTAG24;


Field Purpose


AID 0 - 26 (0 to the maximum GRE ID of 26)


Note: Deleting GRE-0 causes the COLAN to transition from OOS-GRE to IS.



DLT-IPTUse the Delete IPT command to detach a Packet Edge circuit pack from a Resilient Packet Ring (RPR).

Note: You must detach a Packet Edge circuit pack from an RPR before you can deprovision the circuit pack.


Input syntaxDLT-IPT:[TID]:IPTAID,IPTRAID:CTAG;

Example inputDetach a 4x100BT circuit pack from an RPR:DLT-IPT:OC3SP:IPT100-7,IPTR-1:123;


Field Purpose


IPTAID Circuit pack to act upon


IPTRAID RPR to act upon


AID Possible values Description

IPTAID IPT100-slot# Detach a 4x100BT circuit pack where slot# = 3 to 10

100FX-slot# Detach a 4x100FX circuit pack where slot# = 3 to 10

1GE-slot# Detach a 2xGigE circuit pack whereslot# = 3, 5, 7, 9 for double slot circuit packs and slot#= 3 to 10 for single slot 2xGigE circuit pack.

1GE25G-slot# Detach a 2xGigE 2.5G circuit pack whereslot# = 3, 5, 7, 9

IPTR AID IPTR-Index# RPR entity to act upon whereIndex# = 1 to 8



DLT-IPTRUse the Delete IPTR command to deprovision a Resilient Packet Ring (RPR).

Before you delete an RPR, you must

• delete SONET bandwidth assigned to the RPR

• detach all Packet Edge circuit packs from the RPR

Note: Refer to the DLT-CRS-STS1/STS3C/STS12C commands.


Input syntaxDLT-IPTR:[TID]:AID:CTAG;

Example inputDeprovision an RPR:

DLT-IPTR:OC3SP:IPTR-3:123;


Field Purpose





AID Possible values Description

IPTR AID IPTR-Index# RPR entity to act upon whereIndex# = 1 to 8



DLT-LLSDCCThe Delete Lower Layer SDCC command is used to delete a section data communications channel (SDCC) link (layers 1 and 2) on the specified AID.

Note: You cannot delete the SDCC link on OCn facilities related to the DSM.


Input syntaxDLT-LLSDCC:[TID]:AID:CTAG;

Example inputDelete the lower layer SDCC link for the OC-3x4 circuit pack in slot 7, port 1:DLT-LLSDCC:NEWYORK:OC3-7-1:CTAG34;


Field Purpose


AID Access identifier. The equipment to act on.




OC-3 AID

OC3-slot#-port# Identify the OC-3 whereslot# = 3 to 10port# = 1 for OC-3, 1 to 4 for OC-3x4

OC-12 AID

OC12-slot#-port# Identify the OC-12 whereslot# = 3 to 12 for OC-12slot# = 3 to 10 for OC-12x4 STSport# = 1 for OC-12port# = 1 to 4 for OC-12x4 STS

OC-48 AID

OC48-slot# Identify the OC-48 whereslot# = 11 or 12 for OC-48slot# = 3 to 12 for OC-48 STS

OC-192 AID

OC192-slot# Identify the OC-192 whereslot# = 11 or 12

EC-1 AID EC1-slot#-port# Identify the EC-1 whereslot# = 3, 5, 7, 9, port# = 1 to 3

Note: SDCC is not supported on EC-1x12 circuit packs



DLT-OC12The Delete OC-12 command is used to eliminate the OC-12 facility from the OC-12 or OC-12x4 STS circuit pack. The OC-12 facility provisioning information is deleted and all other information (errors, monitoring points) is ignored. Before you delete an OC-12 facility, you must

• delete all connections on the facility

• delete any SDCC links on the OC-12

• ensure the facility is not used as a timing reference

• put the facility OOS

• delete the FFP


Input syntaxDLT-OC12:[TID]:AID:CTAG;

Example inputDelete the OC-12 facility in slot 7 port 1: DLT-OC12:SEATTLE:OC12-7-1:CTAG04;


Field Purpose






OC-12 AID OC12-slot#-port# Identify the OC-12 facility where slot# = 3 to 12 for OC-12slot# = 3 to 10 for OC-12x4 STSport# = 1 for OC-12port# = 1 to 4 for OC-12x4 STS



DLT-OC192The Delete OC-192 command is used to eliminate the OC-192 facility from the OC-192 circuit pack. The OC-192 facility provisioning information is deleted and all other information (errors, monitoring points) is ignored. Before you delete an OC-192 facility, you must




• delete the FFP




Example inputDelete the OC-192 facility in slot 11: DLT-OC192:SEATTLE:OC19211:CTAG04;


Field Purpose






OC-192 AID OC192-slot# Identifies the OC-192 facilityslot# = 11, 12



DLT-OC3The Delete OC-3 command is used to eliminate the OC-3 facility from the OC-3 or OC-3x4 circuit pack; the OC-3 facility provisioning information is deleted and all other information (errors, monitoring points) is ignored. Before you delete an OC-3 facility, you must delete all connections on the facility, delete any SDCC links on the OC-3, ensure the facility is not used as a timing reference, delete the FFP and put the facility OOS.

The following cannot be deleted on the Host OC-3 prov-link, and DSM circuit packs OC3 line facility:

• SDCC links on the OC-3

• FFP



Example inputDelete the OC-3 facility in slot 10 port 1:

DLT-OC3:SEATTLE:OC3-10-1:CTAG04;


Field Purpose






OC3 AID OC3-slot#-port#OC3-slot#-ALL

Identify the OC-3 slot where slot# = 3 to 10port# = 1 for OC-3port# = 1 to 4 for OC-3x4



DLT-OC48The Delete OC-48 command is used to eliminate the OC-48 facility from the OC-48 or OC-48 STS circuit pack. The OC-48 facility provisioning information is deleted and all other information (errors, monitoring points) is ignored. Before you delete an OC-48 facility, you must




• delete the FFP




Example inputDelete the OC-48 facility in slot 11: DLT-OC48:SEATTLE:OC48-11:CTAG04;


Field Purpose






OC-48 AID OC48-slot# Identifies the OC-48 facilityslot# = 11, 12 for OC-48slot# = 3 to 12 for OC-48 STS



DLT-PROVThe Delete Provisioning (DLT-PROV) command is used to delete shelf processor backups that reside on the network processor.

For each shelf processor backup directory that is deleted from the network processor, a TL1 message stating that the backup has been deleted is displayed.


Input syntaxDLT-PROV:[TID]::CTAG::[DLTALL]:[DLTBKUP=Domain];


Field Purpose



DLTALL Deletes all shelf processor backups on a network processor

DLTBKUP Specifies the TID of a shelf processor whose backup is to be deleted from a network processor



DLTALL DLT_ALL_BACKUPS Delete all shelf processor backups on the network processor

DLTBKUP TID of shelf processor Name of the shelf processor whose backup is to be deleted from the network processor



Example inputDelete the provisioning data on network processor MONTREAL that was backed-up from shelf processor OTTAWA:DLT-PROV:MONTREAL::CTAG:::DLTBKUP=OTTAWA;

The response displayed is as follows:

MONTREAL 98-07-30 04:03:35M A COMPLD

Deleting SP Backups from NP

Backup for OTTAWA deleted

Response block syntaxThe response display is as follows:<SID><DATE><TIME>Deleting SP Backups from NP

Backup for <TID> deleted

If no SP backups are deleted, the response display is as follows:

<SID><DATE><TIME>Deleting SP Backups from NP

No Backups deleted

Table 2-196Response parameter descriptions

Parameter Description

SID Source identifier of the network processor storing the shelf processor data

DATE, TIME Date and time of shelf processor deletion

TID Target identifier of each shelf processor deleted



DLT-PVCThe Delete Permanent Virtual Circuit (PVC) command deletes an X.25 PVC. Deleting a PVC restores the circuit to a switched virtual circuit (SVC) with default values from ULX25.


Input syntaxDLT-PVC:[TID]:AID:CTAG;

Example inputDelete PVC #11 and then retrieve VC #11: DLT-PVC:OC3NP:11:CTAG45; RTRV-VC:OC3NP:11:CTAG45;

VC #11 is now an SVC with default values retrieved from the ULX25 database.


Field Purpose


AID Access identifier. The PVC to delete.




AID 0 to 15 Identify the X.25 virtual circuit to act upon



DLT-RINGMAPUse the Delete Ring Map command to delete map information for a node in a BLSR ring. This command is supported on the network processor.


Input syntaxDLT-RINGMAP:[TID]:AID:CTAG::[SID][,APSID];

Example inputDelete the ring map information for the node SPFGXOTT in the ring RING1:

DLT-RINGMAP:NPFGXOTT:RING1:CTAG::SPFGXOTT,1;


Field Purpose


AID Ring name


SID Node name

APSID APS ID of the node







SID An alphanumeric string between 1 and 20 characters

Node name

APSID An integer between 0 and 15 APS ID of the node



DLT-ROLL-STS1 The Delete Rollover STS-1 command is used to delete a connection previously established by the ENT-ROLL-STS1 command. The Delete Rollover STS-1 command will return the connection to its original idle state.


Input syntaxDLT-ROLL-STS1:[TID]:fromAID,toAID:CTAG::CCT:RFROM=Domain,RTO=Domain[,VALID=Domain][,DLTSWMATE=Domain];


Field Purpose






RFROM The fromAID or toAID to be rolled

RTO AID RFROM is to be rolled to

VALID Command execution will be denied if the conditions on the node are inappropriate

DLTSWMATE The switch mate reverts to the original switch mate in a 1WAYPR, 2WAYPR, or 2WAYBR circuit





Purpose

STS1facility AID


OC3-slot#-port#-sts# Identify the STS-1 facility on an OC-3 circuit pack whereslot# = 3 to 10 for OC-12slot# = 3 to 10 for OC-12x4 STSport# = 1 for OC-3port# = 1 to 4 for OC-3x4sts# = 1 to 3

OC12-slot#-port#-sts# Identify the STS-1 facility on an OC-12 or OC-12x4 STS circuit pack whereslot# = 3 to 12port# = 1 for OC-12port# = 1 to 4 for OC-12x4 STSsts# = 1 to 12




STS1facility AID







Purpose



STS1 dacility AID on MS DSM



OC3-1-1-STS-%HLINK-OC3-Hslot#-Hport#

Identify the STS-1 facility on an OC-3 circuit pack wherests = 1 to 3Hslot# = 3 to 10Hport# = 1 to 4




grp = 1 to 3grp 1 =DS1s 1 to 28grp 2 = DS1s 29 to 56grp 3 = DS1s 57 to 84 Hline = OC3 or OC12Hslot = 3 to 10Hport = 1 to 4










Purpose



Example inputRollover an STS-1 connection on the OC-3x4 circuit pack in a 2WAYPR circuit between a DS3 service and the OC-3x4 circuit pack.

Bridge the original OC-3 connection:ENT-ROLL-STS1:OTTAWA:OC3-9-2-1,DS3-3-1:CTAG1::2WAYPR:RFROM=OC3-9-2-1,RTO=OC3-9-3-1,VALID=Y,SWMATE=OC3-10-2-1;

Backout of the bridged connection:

DLT-ROLL-STS1:OTTAWA:OC3-9-2-1,DS3-3-1:CTAG1::2WAYPR:RFROM=OC3-9-2-1,RTO=OC3-9-3-1,VALID=Y;

VALID Y Bridge will be performed regardless of the condition of the switched-to path

N (default) Bridge will be denied if conditions on the node are inappropriate

DLTSWMATE Y The switch mate reverts to the original switch mate in a 1WAYPR, 2WAYPR, or 2WAYBR circuit

N (default) The switch mate is not affected





DLT-ROLL-STS12C The Delete Rollover STS-12c command is used to delete a connection previously established by the ENT-ROLL-STS12c command. The Delete Rollover STS-12c command will return the connection to its original idle state.


Input syntaxDLT-ROLL-STS12C:[TID]:fromAID,toAID:CTAG::CCT:RFROM=Domain,RTO=Domain[,VALID=Domain][,DLTSWMATE=Domain];


Field Purpose



toAID The second of the original cross-connection endpoints






DLTSWMATE Delete switch mate. The switch mate reverts to the original switch mate in a 1WAYPR, 2WAYPR, or 2WAYBR circuit





STS12Cfacility AID

OC-12-slot#-port#-sts# Identify the STS-12c facility on an OC-12 or OC-12x4 STS circuit pack whereslot# = 3 to 12port# = 1 for OC-12port# = 1 to 4 for OC-12x4 STSsts# = 1







Description








Example inputRollover an STS-12c connection on the OC-12 circuit pack in a 2WAYPR circuit between an OC-12 service and the OC-12 circuit pack.

Bridge the original OC-12 connection:ENT-ROLL-STS12C:OTTAWA:OC12-9-1-1,OC12-8-1-1:CTAG1::2WAYPR:RFROM=OC12-9-1-1,RTO=OC12-7-1-1:VALID=Y;

Backout of the bridge connection:

DLT-ROLL-STS12C:OTTAWA:OC12-9-1-1,OC12-8-1-1:CTAG1::2WAYPR:RFROM=OC12-9-1-1,RTO=OC12-7-1-1,VALID=Y;




N (default) The Switch Mate is not affected



Description







Field Purpose














STS24Cfacility AID

OC-48-slot#-sts# Identify the STS-24c facility on an OC-48 circuit pack whereslot# = 3 to 12sts# = 1, 25

















Example inputRollover an STS-24c connection on the OC-48 STS circuit pack in a 2WAYPR circuit between an OC-48 STS circuit pack and another OC-48 STS circuit pack.

Bridge the original OC-48 connection:

ENT-ROLL-STS24C:OTTAWA:OC48-9-1,OC48-8-1:CTAG1::2WAYPR:RFROM=OC48-9-1,RTO=OC48-7-1:VALID=Y;


DLT-ROLL-STS24C:OTTAWA:OC48-9-1,OC48-8-1:CTAG1::2WAYPR:RFROM=OC48-9-1,RTO=OC48-7-1,VALID=Y;



DLT-ROLL-STS3C The Delete Rollover STS-3c command is used to delete a connection previously established by the ENT-ROLL-STS3C command. The Delete Rollover STS-3c command will return the connection to its original idle state.




Field Purpose









DLTSWMATE The switch mate reverts to the original switch mate in a 1WAYPR, 2WAYPR, or 2WAYBR circuit





Purpose

STS3Cfacility AID

OC3-slot#-port#-sts# Identify the STS-3c facility on an OC-3 circuit pack whereslot# = 3 to 10port# = 1 for OC-3port# = 1 to 4 for OC-3x4sts# = 1

OC12-slot#-port#-sts# Identify the STS-3c facility on an OC-12 or OC-12x4 STS circuit pack whereslot# = 3 to 12 for OC-12slot# = 3 to 10 for OC-12x4 STSport# = 1 for OC-12port# = 1 to 4 for OC-12x4 STSsts# = 1, 4, 7, or 10

OC48-slot#-sts# Identify the STS-3c facility on an OC-48 or OC-48 STS circuit pack whereslot# =11, 12 for OC-48slot# = 3 to 12 for OC-48 STSsts# = 1, 4, 7, 10, ..., 46

OC192-slot#-sts# Identify the STS-3c facility on an OC-192 circuit pack whereslot# =11, 12sts# = 1, 4, 7, 10, ..., 190





Example inputRollover an STS-3c connection on the OC-3x4 circuit pack in a 2WAYPR circuit between an OC-3 service and the OC-3x4 circuit pack.

Bridge the original OC-3 connection:ENT-ROLL-STS3C:OTTAWA:OC3-9-1-1,OC3-8-1-1:CTAG1::2WAYPR:RFROM=OC3-9-1-1,RTO=OC3-7-1-1:VALID=Y;

Backout of the bridge connection:DLT-ROLL-STS3C:OTTAWA:OC3-9-1-1,OC3-8-1-1:CTAG1::2WAYPR:RFROM=OC3-9-1-1,RTO=OC3-7-1-1,VALID=Y;

STS3Cfacility AID





Description












Purpose







Field Purpose












STS48Cfacility AID

OC-48-slot#-sts# slot# = 11, 12 for OC-48slot# = 3 to 12 for OC-48 STSsts# = 1

OC192-slot#-sts# slot# =11, 12sts# = 1, 49, 97, ... 145



Example inputRollover an STS-48c connection on the OC-48 STS circuit pack in a 2WAYPR circuit between an OC-48 STS circuit pack and another OC-48 STS circuit pack.

Bridge the original OC-48 connection:ENT-ROLL-STS48C:OTTAWA:OC48-9-1,OC48-8-1:CTAG1::2WAYPR:RFROM=OC48-9-1,RTO=OC48-7-1:VALID=Y;


DLT-ROLL-STS48C:OTTAWA:OC48-9-1,OC48-8-1:CTAG1::2WAYPR:RFROM=OC48-9-1,RTO=OC48-7-1,VALID=Y;














DLT-ROLL-VT1 The Delete Rollover VT1 command is used to delete a connection previously established by the ENT-ROLL-VT1 command. The Delete Rollover VT1 command will return the connection to its original idle state.


Input syntaxDLT-ROLL-VT1:[TID]:fromAID,toAID:CTAG::CCT:RFROM=Domain,RTO=Domain[,VALID=Domain][,DLTSWMATE=Domain];


Field Purpose









DLTSWMATE If included in the command, the switch mate reverts to the original switch mate in a 1WAYPR, 2WAYPR, or 2WAYBR circuit






VT1.5facility AID


slot# = 4 to 10port# = 1 to 12grp = 1 to 3


slot# = 3, 5, 7, 9port# = 1 to 12t1# = 1 to 28


DS1 service moduleport# = 1 to 84hslot# = 3 to 10hport# = 1 to 4


DS1 service module grp# = 1 to 3hslot# = 3 to 10hport# = 1 to 4







VT1.5facility AID








Parameter Possible value Description








DLTSWMATE Y The switch mate reverts to the original switch mate in a 1WAYPR, 2WAYPR, or 2WAYBR

N (default) The switch mate is not affected





Example inputReverse the rollover of a VT1.5 connection on the OC-3x4 circuit pack in a 2WAYPR circuit between a DS1 service and the OC-3x4 circuit pack.

Bridge the original OC-3 connection:

ENT-ROLL-VT1:OTTAWA:OC3-9-2-1-7-1,DS1-4-4:A::2WAYPR:RFROM=OC3-9-2-1-7-1,RTO=OC3-9-3-1-7-1,VALID=Y;

Backout of the bridged connection:

DLT-ROLL-VT1:OTTAWA:OC3-9-2-1-7-1,DS1-4-4:B::2WAYPR:RFROM=OC3-9-2-1-7-1,RTO=OC3-9-3-1-7-1,VALID=Y;



DLT-SECU-ACCESSThe Delete Security Access command is used to delete network elements from the allow or deny access control list of a specified network element or network processor.


Input syntaxDLT-SECU-ACCESS:[TID]::CTAG::SID,[ACCESS];

Example inputDelete network element OTTAWA from the allow list of network element MONTREAL:DLT-SECU-ACCESS:MONTREAL::CTAG1::OTTAWA,ALLOW;


Field Purpose



SID Source identifier of the network element to delete. Grouping is allowed.

ACCESS Delete network elements from the allow list or from the deny list



ACCESS ALLOW Delete network elements from the allow list

DENY (default) Delete network elements from the deny list



DLT-SECU-BADPIDThe Delete Security Bad Password command is used to remove previously entered words from the list of unusable passwords on the specified network element or network processor.


Input syntaxDLT-SECU-BADPID:[TID]::CTAG::BADPID;


Example inputRemove the word EXPRESS951 from the list of unusable passwords for all network elements in the span of control where you are logged in:

DLT-SECU-BADPID:ALL::CTAG12::EXPRESS951;


Field Purpose



BADPID Word to remove. Grouping is allowed.



BADPID A string between eight and ten alphanumeric characters.

Word to remove from the list of unusable passwords.

ALL Remove all previously entered words from the list of unusable passwords



DLT-SECU-USERThe Delete Security User command is used to delete a user account on the network element or the network processor.

To change the UPC, see ED-SECU-USER.

Users with ADMIN privilege cannot delete their own UID. This ensures that at least one UID with ADMIN privilege always exists. If a user attempts to delete their UID, the error response /*Privilege, Illegal User Identity*/ is displayed.


Input syntaxDLT-SECU-USER:[TID]:UID:CTAG;


Example inputDelete the user account USER03 from network element NEWYORK:

DLT-SECU-USER:NEWYORK:USER03:CTAG12;


Field Purpose


UID User identifier




DLT-T1The Delete T1 command is used to eliminate a DS1 facility from a DS1 circuit pack; the DS1facility provisioning information is deleted and all other information (errors, monitoring points) is ignored. Before you delete a facility, you must delete all connections on the facility, ensure the facility is not used as a timing reference, and put the facility OOS.


Input syntaxDLT-T1:[TID]:AID:CTAG;

Example inputDelete the DS1 facility on the DS1 circuit pack in slot 4 port 7: DLT-T1:NEWYORK:DS1-4-7:CTAG123;


Field Purpose


AID Access identifier. DS1 facilities to act on.




DS1 AID DS1-slot#-port#DS1-slot#-ALL

Identify the DS1s where slot# = 4 to 10, port# =1 to 12

DS3V AID DS1-slot#-port#-t1#DS1-slot#-port#-ALL

Identify the DS1s where slot# = 3, 5, 7, 9port# = 1 to 12t1# = 1 to 28

DSM AID DS1-1-port#-%HLINK-OC3-hslot#-hport#

DS1 service module whereport# = 1 to 84hslot# = 3 to 10hport# = 1 to 4

DS1-1-ALL-%HLINK-OC3-hslot#-hport#

All DS1 ports on the DS1 service module wherehslot# = 3 to 10hport# = 1 to 4



DLT-T3The Delete T3 command is used to eliminate a DS3 facility from a circuit pack; the DS3 facility provisioning information is deleted and all other information (errors, monitoring points) is ignored. Before you delete a facility, you must delete all connections on the facility, and put the facility OOS.


Input syntaxDLT-T3:[TID]:AID:CTAG;

Example inputDelete the T3 facility on the DS3 circuit pack in slot 9 port 1 at the OTTAWA network element:

DLT-T3:OTTAWA:DS3-9-1:CTAG13;


Field Purpose


AID Access identifier. DS3s to act on.



AID type

Command-specific values

Purpose

T3 AID DS3-slot#-port#DS3-slot#-ALL

Identify the T3 facilitiesslot# = 3, 5, 7, or 9port# = 1 to 3 for DS3x3port# = 1 to 12 for DS3x12, DS3x12e, or DS3VTx12

MS DSM T3 Facility AID





DLT-UPGRD The Delete Upgrade command is used to delete a release of a software load stored on the network processor.


Input syntaxDLT-UPGRD:[TID]::CTAG::RELNO;

Example input Delete the software release REL0310D.TT on network processor OTTAWA:

DLT-UPGRD:OTTAWA::CTAG24::REL0310D.TT;


Field Purpose



RELNO ASCII string identifying the release number to delete



ED-ALM-PROFILEThe Edit Alarm Profile command allows the user to set the status of any alarms that are applicable to the specified profile.

Security LevelLevel 3

Input syntaxED-ALM-PROFILE:[TID]::CTAG::AIDTYPE,”PRFLNAME”:ALMID=Domain [,ALRMSTAT=Domain];


Field Purpose



AIDTYPE Access identifier TYPE

PRFLNAME Alarm profile name assigned by user

ALMID Alarm identifier

ALRMSTAT Alarm status



AIDTYPE VT1 VT1 facility

STS1 STS-1 facility





EQPT equipment

T1 T1 facility

T3 T3 facility

EC1 EC-1 facility



Example input Set the alarm status for network element OTTAWA: ED-ALM-PROFILE:OTTAWA::CTAG12::OC3,”ALARMSON”:ALMID=12;

AIDTYPE E1 E1 facility

OC3 OC-3 facility

OC12 OC-12 facility

OC48 OC-48 facility

OC192 OC-192 facility

FAC conditions attributed to ILAN facilities

COM conditions attributed to shelf or SP

DSM DS service module facility

SECU Security related

ETH Ethernet facility

WAN WAN facility

FC Fibre Channel facility

PRFLNAME ASCII string Alarm profile name-can be up to 20 characters long and must be enclosed within quotation marks (quotation marks and backslash to be excluded from name)

ALMID a positive integer Identifier of alarm point

ALRMSTAT ENABLED Enable selected alarms (default)

DISABLED Disable selected alarms

Table 2-231 (continued)Parameter description




ED-BLSRRINGUse the Edit BLSR Ring command to change the name of a BLSR ring. This command is supported on the network processor.


Input syntaxED-BLSRRING:[TID]:AID:CTAG::NEW_RINGNAME;

Example inputChange the name of the BLSR ring to OTTAWARING:ED-BLSRRING:NPFGXOTT:RING1:CTAG::OTTAWARING;


Field Purpose


AID Current ring name


NEW_RINGNAME New ring name







AID An alphanumeric string between 1 and 20 characters

Current ring name

NEW_RINGNAME An alphanumeric string between 1 and 20 characters. Special characters are not supported.

New ring name



ED-COMMUse this command to edit the parameters of the RS232 communication port.

Security level1

Input syntaxED-COMM:[tid]:aid:ctag::COMMTYPE:[STATUS=Domain];

Response block syntaxED-COMM::%HLINK-AID:CTAG:: RS232;


Field Purpose




COMMTYPE Communication type

STATUS Enable or disable the RS-232 communication port.


Parameter Description Possible values

COMMTYPE Select to display RS232 communication port information.

RS232

AID Single DSM MSP shelf or MS DSM Hline = OC3 or OC12Hslot = 3 to 10Hport = 1 to 4



ED-CRS-STS1 The Edit Cross-connect STS-1 command is used to edit the cross-connect type (CCT) of an existing STS-1 cross-connect.

See Figure 4-1 on page 4-122 for descriptions of cross-connect types.


Input syntaxED-CRS-STS1:[TID]:FromAID,ToAID:CTAG::[CCT]:[SWMATE=Domain][,CKTID=Domain];


Field Purpose


FromAID From access identifier. The STS-1 facility at one end of the cross-connect. If the connection is unidirectional, the FromAID specifies the signal source.

ToAID To access identifier. The STS-1 facility at the other end of the cross-connect. If the connection is unidirectional, the ToAID specifies the signal destination.



SWMATE Path protection Switch Mate. Path protection for the FromAID OC-3, OC-3x4, OC-12, OC-12x4 STS, OC-48, OC-48 STS, or OC-192 interface only when the CCT is protected. That is, when the CCT is one of 1WAYPR, 2WAYPR, or 2WAYBR.

CKTID Connection identifier. A string between 1 and 40 alphanumeric characters that identifies the cross-connect. Enclose the string in double quotes (for example, “Toronto-Ottawa”).





Purpose

STS-1 Facility AID

OC3-slot#-port#-sts# Identify the STS-1 facility on an OC-3 circuit pack whereslot# = 3 to 10port# = 1 for OC-3, 1 to 4 for OC-3x4sts# = 1 to 3

OC12-slot#-port#-sts# Identify the STS-1 facility on an OC-12 or OC-12x4 STS circuit pack whereslot# = 3 to 12port# = 1 for OC-12, 1 to 4 for OC-12x4 STSsts# = 1 to 12

OC48-slot#-sts# Identify the STS-1 facility on an OC-48 circuit pack whereslot# = 11, 12 for OC-48slot# = 3 to 12 for OC-48 STSsts# = 1 to 48





STS-1 Facility AID

DS3-slot#-port# Identify the STS-1 facility on a DS3 circuit pack whereslot# = 3, 5, 7, or 9port# = 1 to 3 for DS3x3port# = 1 to 12 for DS3x12, DS3x12e, or DS3/EC-1x12




Purpose



STS1 Facility AID on MS DSM


slot = 3 or 5

port = 1 to 6

Hline = OC3 or OC12

Hslot = 3 to 10

Hport = 1 to 4


slot = 3 to 6; port = 1 to 8; sts = 1 to 3

Hline = OC3 or OC12

Hslot = 3 to 10

Hport = 1 to 4


grp = 1 to 3

grp 1 =DS1s 1 to 28

grp 2 = DS1s 29 to 56

grp 3 = DS1s 57 to 84

Hline = OC3 or OC12

Hslot = 3 to 10

Hport = 1 to 4

RPR AID


IPTR-index#-port#-sts# Identify the RPR, for RPRs that have virtual concatenation enabled, where index# = 1 to 8port# = 1 or 2sts# = 1 to 24








IPTRING SONET bandwith allocation for RPR



Purpose



Example 1TaskFor the NEWYORK network element, edit (convert) an existing STS-1 1WAY cross-connect to a 2WAY cross-connect. The existing cross-connect has the following characteristics:

• FromAID = slot 7 DS3 mapper

• ToAID = slot 10 OC-3 interface, port 1, STS1 = 3

SolutionThe ED-CRS-STS1 command requires two 1WAY cross-connects to be in place before a 1WAY to 2WAY edit. Consequently, a second 1WAY cross-connect must be entered with the following command before the ED-CRS-STS1 command can be issued:ENT-CRS-STS1:NEWYORK:OC3-10-1-3,DS3-7-1:CTAG12::1WAY;

SWMATE OC3-slot#-port#-sts# Identify the STS-1 facility on an OC-3 circuit pack whereslot# = 3 to 10port# = 1 for OC-3, 1 to 4 for OC-3x4sts# = 1 to 3

OC12-slot#-port#-sts# Identify the STS-1 facility on an OC-12 or OC-12x4 STS circuit pack whereslot# = 3 to 12port# = 1 for OC-12, 1 to 4 for OC-12x4 STSsts# = 1 to 12

OC48-slot#-sts# Identify the STS-1 facility on an OC-48 or OC-48 STS circuit pack whereslot# = 11 or 12 for OC-48slot# = 3 to 12 for OC-48 STSsts# = 1 to 48


CKTID 1 to 40 alphanumeric characters

Connection identifier. A string between 1 and 40 alphanumeric characters that identifies the cross-connect.





Now that the complementary 1WAY cross-connect exists, the two cross-connects can be converted into a single 2WAY cross-connect with the following command:ED-CRS-STS1:NEWYORK:OC3-10-1-3,DS3-7-1:CTAG12::2WAY;

Example 2TaskFor the SEATTLE network element, edit an existing STS-1 2WAY cross-connect to a 2WAYPR cross-connect. The existing cross-connect has the following characteristics:

• FromAID = slot 9 port 2 OC-3 interface, STS1 = 1

• ToAID = slot 5 port 1 DS3 mapper

The switchmate for the resulting 2WAYPR cross-connect is to be STS1 #1 on the slot 10 port 2 optical interface.

SolutionThe following command will edit the existing cross-connect as required:

ED-CRS-STS1:SEATTLE:OC3-9-2-1,DS3-5-1:CTAG12::2WAYPR:SWMATE=OC3-10-2-1;



ED-CRS-STS12C The Edit Cross-connect STS-12c command is used to edit the cross-connect type (CCT) of an existing STS-12c cross-connect.



Input syntaxED-CRS-STS12C:[TID]:FromAID,ToAID:CTAG::[CCT]:[SWMATE=Domain][,CKTID=Domain];


Field Purpose






SWMATE Switchmate identifies the path protection for the FromAID when the CCT is path protected. That is, when the CCT is one of 1WAYPR or 2WAYPR.






Purpose






Resilient Packet Ring (RPR)

IPTR-index# Index# = 1 to 8











Example 1TaskFor the NEWYORK network element, edit (convert) an existing STS-12c 1WAY cross-connect to a 2WAY cross-connect. The existing cross-connect has the following characteristics:

• FromAID = slot 7 OC-12 interface

• ToAID = slot 10 OC-12 interface

SolutionThe ED-CRS-STS12C command requires two 1WAY cross-connects to be in place before a 1WAY to 2WAY edit. Consequently, a second 1WAY cross-connect must be entered with the following command before the ED-CRS-STS12C command can be issued:

ENT-CRS-STS12C:NEWYORK:OC12-10-1-1,OC12-7-1-1:CTAG12::1WAY;

Now that the complementary 1WAY cross-connect exists, the two cross-connects can be converted into an single 2WAY cross-connect with the following command:ED-CRS-STS12C:NEWYORK:OC12-10-1-1,OC12-7-1-1:CTAG12::2WAY;

SWMATE OC12-slot#-port#-sts# Identify the STS-12c facility whereslot# = 3 to 12port# = 1 for OC-12, 1 to 4 for OC-12x4 STSsts# = 1

OC48-slot#-sts# Identify the STS-12c facility whereslot# = 11, 12 for OC-48, 3 to 12 for OC-48 STSsts# = 1, 13, 25, 37

OC192-slot#-sts# Identify the STS-12c facility whereslot# = 11, 12, sts# = 1, 13, 25, 37, ... 181







Example 2TaskFor the SEATTLE network element, edit an existing STS-12c 2WAY cross-connect to a 2WAYPR cross-connect. The existing cross-connect has the following characteristics:



The switchmate for the resulting 2WAYPR cross-connect is to be the slot 10 optical interface.

SolutionThe following command will edit the existing cross-connect as required: ED-CRS-STS12C:SEATTLE:OC12-9-1-1,OC12-5-1-1:CTAG12::2WAYPR:SWMATE=OC12-10-1-1;








Field Purpose























SWMATE OC48-slot#-sts# Identify the STS-24c facility whereslot# = 3 to 12sts# = 1, 25







• FromAID = slot 7 OC-48 STS interface

• ToAID = slot 10 OC-48 STS interface

SolutionThe ED-CRS-STS24C command requires two 1WAY cross-connects to be in place before a 1WAY to 2WAY edit. Consequently, a second 1WAY cross-connect must be entered with the following command before the ED-CRS-STS24C command can be issued:

ENT-CRS-STS24C:NEWYORK:OC48-10-1-1,OC48-7-1-1:CTAG12::1WAY;

Now that the complementary 1WAY cross-connect exists, the two cross-connects can be converted into a single 2WAY cross-connect with the following command:

ED-CRS-STS24C:NEWYORK:OC48-10-1-1,OC48-7-1-1:CTAG12::2WAY;













Field Purpose











Purpose

STS-3c Facility AID

OC3-slot#-port#-sts# Identify the STS-3c facility on an OC-3 circuit pack whereslot# = 3 to 10, port# = 1 for OC-3port# = 1 to 4 for OC-3x4, sts# =1

OC12-slot#-port#-sts# Identify the STS-3c facility on an OC-12 or OC-12x4 STS circuit pack where slot# = 3 to 12port# = 1 for OC-12port# = 1 to 4 for OC-12x4 STSsts# = 1, 4, 7, or 10

OC48-slot#-sts# Identify the STS-3c facility on an OC-48 or OC-48 STS circuit pack whereslot# = 11, 12 for OC-48slot# = 3 to 12 for OC-48 STSsts# = 1, 4, 7, 10, ...to 46

OC192-slot#-sts# Identify the STS-3c facility on an OC-192 circuit pack whereslot# = 11, 12, sts# = 1, 4, 7, 10, ...to 190



Identify the STS-3c facility on the WAN port of the MS DSM whereslot = 3 to 6; port = 1 to 8sts = 1; Hline = OC3 or OC12Hslot = 3 to 10, Hport = 1 to 4

RPR AID


IPTR-index#-port#-sts# Identify the RPR, for RPRs that have virtual concatenation enabled, where index# = 1 to 8, port# = 1 or 2, sts# = 1 to 8




• FromAID = slot 7 OC-3 interface, port 1, STS-1 = 1

• ToAID = slot 10 OC-3 interface, port 3, STS-1 = 1









SWMATE OC3-slot#-port#-sts# Identify the STS-3c facility whereslot# = 3 to 10port# = 1 for OC-3port# = 1 to 4 for OC-3x4sts# =1

OC12-slot#-port#-sts# Identify the STS-3c facility whereslot# = 3 to 12port# = 1 for OC-12port# = 1 to 4 for OC-12x4 STSsts# = 1, 4, 7, or 10

OC48-slot#-sts# Identify the STS-3c facility whereslot# = 11, 12 for OC-48slot# = 3 to 12 for OC-48 STSsts# = 1, 4, 7, 10, ...to 46

OC192-slot#-sts# Identify the STS-3c facility whereslot# = 11, 12sts# = 1, 4, 7, 10, ...to 190





SolutionThe ED-CRS-STS3C command requires two 1WAY cross-connects to be in place before a 1WAY to 2WAY edit. Consequently, a second 1WAY cross-connect must be entered with the following command before the ED-CRS-STS3C command can be issued:ENT-CRS-STS3C:NEWYORK:OC3-10-3-1,OC3-7-1-1:CTAG12::1WAY;

Now that the complementary 1WAY cross-connect exists, the two cross-connects can be converted into a single 2WAY cross-connect with the following command:ED-CRS-STS3C:NEWYORK:OC3-10-3-1,OC3-7-1-1:CTAG12::2WAY;






ED-CRS-STS3C:SEATTLE:OC3-9-1-1,OC3-5-1-1:CTAG12::2WAYPR:SWMATE=OC3-10-1-1;








Field Purpose










STS-48c Facility AID OC48-slot#-sts# slot# = 3 to 12sts# = 1

OC192-slot#-sts# slot# = 11, 12sts# = 1, 49, ... 145






SolutionThe ED-CRS-STS48C command requires two 1WAY cross-connects to be in place before a 1WAY to 2WAY edit. Consequently, a second 1WAY cross-connect must be entered with the following command before the ED-CRS-STS48C command can be issued:ENT-CRS-STS48C:NEWYORK:OC48-10-1-1,OC48-7-1-1:CTAG12::1WAY;

Now that the complementary 1WAY cross-connect exists, the two cross-connects can be converted into an single 2WAY cross-connect with the following command:ED-CRS-STS48C:NEWYORK:OC48-10-1-1,OC48-7-1-1:CTAG12::2WAY;








SWMATE OC48-slot#-sts# Identify the STS-48c facility whereslot# = 3 to 12sts# = 1






ED-CRS-VT1 The Edit Cross-connect VT1.5command is used to edit the cross-connect type (CCT) of an existing VT1.5 cross-connect.



Input syntaxED-CRS-VT1:[TID]:FromAID,ToAID:CTAG::[CCT]:[SWMATE=Domain][,CKTID=Domain];


Field Purpose






SWMATE Path protection Switch Mate. Path protection for the FromAID OC-3, OC-3x4, OC-12 or OC-48 interface only when the CCT is protected. That is, when the CCT is one of 1WAYPR, 2WAYPR, or 2WAYBR.






VT1.5 facility AID

DS1-slot#-port# slot# = 4 to 10port# = 1 to 12


slot# = 3, 5, 7, 9port# = 1 to 12t1# = 1 to 28


port# = 1 to 84hslot# = 3 to 10hport# = 1 to 4

DS1-1-DFLT-grp#-%HLINK-OC3-hslot#-hport#

grp# = 1 to 3hslot# = 3 to 10hport# = 1 to 4

DS1-1-port#-%HLINK-Hline-Hslot#-Hport#

MS DSMport# = 1 to 84, Hline = OC3 or OC12, Hslot# = 3 to 10, Hport# = 1 to 4

DS1-DFLT-grp#-%HLINK-Hline-Hslot#-Hport#

MS DSMgrp# = 1 to 3, Hline = OC3 or OC12, Hslot# = 3 to 10, Hport# = 1 to 4









Use the DFLT-# smart AID to edit the CCT for one of three sets of 28 DS1s to VT1.5s within an STS-1. For each possible DFLT-# value, a specific set of 28 ports is cross-connected to an STS-1. Table 2-254 shows the DFLT-# smart AID value and the corresponding ports.

VT1.5 facility AID

EC1-slot#-port#-vtg#-vt#EC1-slot#-port#-vtg#-ALLEC1-slot#-port#-ALL

slot# = 3, 5, 7, 9port # = 1 to 3 for EC-1x3port # = 1 to 12 for EC-1x12 or DS3/EC-1x12vtg# = 1 to 7vt# = 1 to 4



WAN-slot#-port#-sts#-vtg#-vt#-%HLINK-Hline#-Hslot#-Hport#

WAN-slot#-port#-sts#-ALL-%HLINK-Hline#-Hslot#-Hport#

slot# = 3 to 6, port# = 1 to 8, sts# = 1 to 3, vtg# = 1 to 7,vt# = 1 to 4, Hline = OC3 or OC12, Hslot# = 3 to 10, Hport# = 1 to 4

MS DSM WAN facilities

WAN-slot#-port#-sts#-vtg#-vt#-%HLINK-Hline#-Hslot#-Hport#

WAN-slot#-port#-sts#-vtg#-ALL-%HLINK-Hline#-Hslot#-Hport#

WAN-slot#-port#-sts#-ALL-%HLINK-Hline#-Hslot#-Hport#

slot# = 3 to 10port# = 1 to 8 sts# = 1 to 3vtg# = 1 to 7 for sts# = 1 or 2vtg# = 1 or 2 for sts# = 3vt# = 1 to 4

SMART AID

DS1-DFLT-grp# grp# = 1 to 3

Table 2-254DFLT-# smart AID values

DFLT-# Ports Equivalent facilities

1 1 to 28 DS1-4-1 — DS1-6-4

2 29 to 56 DS1-6-5 — DS1-8-8

3 57 to 84 DS1-8-9 — DS1-10-12





Example 1TaskFor the NEWYORK network element, edit (convert) an existing VT1.5 1WAY cross-connect to a 2WAY cross-connect. The existing cross-connect has the following characteristics:

• FromAID = slot 7 DS1 mapper, port 2

• ToAID = slot 9 OC-3 interface, port 3, STS1 = 3, VTG = 1, VT =1

SolutionThe ED-CRS-VT1 command requires two 1WAY cross-connects to be in place before a 1WAY to 2WAY edit. Consequently, a second 1WAY cross-connect must be entered with the following command before the ED-CRS-VT1 command can be issued:

ENT-CRS-VT1:NEWYORK:OC3-9-3-3-1-1,DS1-7-2:CTAG12::1WAY;








SWMATE OC3-slot#-port#-sts#-vtg#-vtOC3-slot#-port#-sts#-vtg#-ALLOC3-slot#-port#-sts#-ALL






CKTID 1 to 40 alphanumeric characters Connection identifier. A string between 1 and 40 alphanumeric characters that identifies the cross-connect.



Now that the complementary 1WAY cross-connect exists, the two cross-connects can be converted into a single 2WAY cross-connect with the following command:ED-CRS-VT1:NEWYORK:OC3-9-3-3-1-1,DS1-7-2:CTAG12::2WAY;

Example 2TaskFor the SEATTLE network element, edit an existing VT1 2WAY cross-connect to a 2WAYPR cross-connect. The existing cross-connect has the following characteristics:

• FromAID = slot 9 OC-3 interface, port 2, STS1 = 3, VTG = 3, VT = 1

• ToAID = slot 5 DS1 mapper, port 12

The required switchmate for the resulting 2WAYPR cross-connect is the slot 10 optical interface.


ED-CRS-VT1:SEATTLE:OC3-9-2-3-3-1,DS1-5-12:CTAG12::2WAYPR:SWMATE=OC3-10-2-3-3-1;



ED-DATThe Edit Date command instructs the network element or network processor to change its system date and time clock to the value specified.

The date and time are set up on the network element as part of commissioning, and on the network processor when the network processor is initially provisioned. The date and time must be reset after a system power-up.

Note: The date and time on the network processor synchronizes to that of the selected shelf processor.


Input syntaxED-DAT:[TID]::CTAG::[date],[time];


Example inputSet the date and time on the network element to April 15, 1995, 9:30 a.m.: ED-DAT:NEWYORK::CTAG12::95-04-15,09-30-00;


Field Purpose



DATE Current date. A null value for DATE leaves the date unchanged.

TIME Current time. A null value for TIME leaves the time unchanged.


Parameter Format Description

DATE YY-MM-DD YY is the last two digits of the year ranging from 00 to 99, MM is the month of the year ranging from 01 to 12, and DD is the day of the month ranging from 01 to 31.

TIME HH-MM-SS HH is the hour ranging from 00 to 23, MM is the minute ranging from 00 to 59, and SS is the second ranging from 00 to 59.



ED-DFLT-AINS Use the Edit default auto-in-service command to modify the default DS1 or DS3 auto-in-service (AINS) start-up time for a shelf.

When the secondary state of a DS1 or DS3 facility is set to auto-in-service (using the ED-T1/T3 or ENT-T1/T3 commands), and the start-up time parameter (HH-MM) is not entered, HH-MM assumes the default start-up time.


Input syntaxED-DFLT-AINS:[TID]::CTAG::[AINS-TIME];

Example inputFor the SEATTLE network element, set the default AINS start-up time to 7 hours and 30 minutes: ED-DFLT-AINS:SEATTLE::CTAG04::07-30;


Field Purpose



AINS-TIME Auto-in-service start-up time



AINS-TIME HH-MM

00-01 to 96-00

Default = 04-00 (4 hours)

Amount of time that an error-free signal must be present on the DS1 or DS3 line in order for the auto-in-service state to clear. If an error-free signal is present for less than this period of time, the DS1 or DS3 facility remains in an auto-in-service state.

HH= 00-96 hours MM=00-59 minutes



ED-EC1The Edit EC-1 command is used to edit the line buildout and auto in-service parameters of an EC-1 facility.


Input syntaxED-EC1:[TID]:AID:CTAG:::[LBO=Domain]:,[SST];

Example inputAt the EC-1 facility in slot 5 port 3 of network element SEATTLE, edit the line buildout to 300 feet: ED-EC1:SEATTLE:EC1-5-3:CTAG04:::LBO=2;


Field Purpose


AID Access identifier. EC-1 facility to act on.


LBO Line buildout

SST Secondary state



ED-ETHUse the Edit Ethernet command to edit the parameters of an Ethernet facility.

Note: When auto-negotiation is disabled on the Optical Metro 3500, the customer data equipment must also have auto-negotiation disabled.


Input syntax for the 2x100BT-P2PED-ETH:[tid]:aid:ctag:::[,ETHDPX=Domain][,SPEED=Domain][,PASSCTRL=Domain];

Input syntax for the 8x100BT-P2P and 8x100BT MS DSMED-ETH:[tid]:aid:ctag:::[AN=Domain][,SPEED=Domain][,PASSCTRL=Domain][,FLOWCTRL=Domain][,PAUSETX=Domain][,MTU=Domain][,TXCON=Domain][,PAUSETXOVERRIDE=Domain];

Input syntax for the 4x100FX-P2PED-ETH:[tid]:aid:ctag:::[,PASSCTRL=Domain][,PAUSETX=Domain][,MTU=Domain][,TXCON=Domain];

Input syntax for the 2xGigE/FC-P2P, 2xGigE/FC-P2P-C, and 2xGigE-P2PED-ETH:[tid]:aid:ctag:::[AN=Domain][,PASSCTRL=Domain][,FLOWCTRL=Domain][,PAUSETX=Domain][,MTU=Domain][,TXCON=Domain][,PAUSETXOVERRIDE=Domain];


Field Purpose


AID Access identifier. The Ethernet facility to edit.


AN Auto negotiation

ETHDPX Duplex setting

SPEED Speed

PASSCTRL Control frames setting

FLOWCTRL Advertised flow control capabilities

PAUSETX Pause frame transmission



MTU Maximum transfer unit

TXCON Transmit conditioning

PAUSETXOVERRIDE Pause frame transmission override



ETH AID ETH-slot#-port#ETH-slot#-ALL

Identify the Ethernet facility where slot# = 3 to 10port# = 1 to 8 for 8x100BT-P2Pport# = 1 to 4 for 4x100FX-P2Pport# = 1 or 2 for all other circuit packs

MS DSM Ethernet Facility

ETH-slot#-port#-%HLINK-Hline-Hslot#-Hport#

Identify the MS DSM Ethernet facility whereslot# = 3 to 6port# = 1 to 8Hline = OC3 or OC12Hslot# = 3 to10Hport# = 1 to 4



AN ENABLE (default) Enable or disable auto-negotiation. When auto-negotiation is disabled, the customer data equipment must also have auto-negotiation disabled.

DISABLE

ETHDPX HALF Set the duplex mode to Half, Full, or Both. Make sure the device connected to the ETH port has the same duplex setting.FULL (default)

BOTH

SPEED 10 (default) Set the speed of the port to 10, 100, or 10/100 Mbit/s. For the 2x100BT-P2P card, since auto-negotiation is not supported, the 10/100 setting is equivalent to 100. Make sure the device connected to the port has the same speed.

100

10/100


Field Purpose



PASSCTRL ENABLE Discard pause frames received on the port (disable) or allow pause frames to transparently pass through (enable).

Note that this attribute applies to pass control frames of type 0x8808 only (PAUSE is the only defined control frame). Other pass control frames (for example, type 0x8809) are not affected by this attribute, and will always be transparently passed through.

Note: If pause frame transmission (PAUSETX) is enabled, the PASSCTRL attribute should be disabled to avoid flow control problems between the ETH port and subtending equipment.

DISABLE (default)

FLOWCTRL ASYM (default) Set the flow control capability used by auto negotiation to ASYM, SYM or NONE. Auto negotiation sets the actual flow control between two devices. Note that if auto negotiation is disabled, this attribute is ignored.

SYM

NONE

PAUSETX ENABLE (default) Enable or disable transmission of pause frames. If auto negotiation is enabled, this parameter only applies if PAUSETXOVERRIDE is also enabled.

DISABLE

MTU 1594 Set the maximum frame size (in bytes) that this port can transmit. This size includes all the overhead bytes such as MAC addresses, length and CRCs. 1594 is not supported by GE/FC SFP.

1600 (default)

9600





TXCON ENABLE (default) Enable or disable shut down of the transmit signal of the Ethernet port upon detection of certain Ethernet or WAN port defects. You can only edit this parameter if the ETH facility is out-of-service (OOS-MA).

If enabled, the transmit signal of the port shuts down when any of the following occur: there are client signal failures received from the far-end; there is a link down condition on the corresponding WAN port; the corresponding WAN port receives client signal failures; or there are no cross-connects on the corresponding WAN port.

In addition:

• client signal failures received from the far-end cause ingress frames at the ETH port to be discarded and egress frames on the WAN ports to be discarded

• link down conditions on the ETH port trigger transmission of client signal failures to the WAN port

• client signal failures from the WAN port trigger a “Far End Client Rx Signal Failure” alarm

If disabled, the transmit signal of the port does not shut down if any of the conditions listed above occur. In addition, an ETH link down condition does not trigger transmission of client signal failures to the WAN port and client signal failures from the WAN port do not trigger a “Far End Client Rx Signal Failure” alarm.

Note 1: If TXCON is disabled, the GFP CSF client management frame transmission will also be disabled with local client failures. If this occurs, incoming WAN traffic will cause LAN OMs to increment. However, frames will be silently discarded whether auto-negotiation is enabled or disabled.

Note 2: If TXCON is disabled, the Gigabit Ethernet laser will remain off even when no cross-connects are assigned against the WAN port.

DISABLE





Example inputChange the duplex mode on ETH port 1 of the 2x100BT-P2P circuit pack in slot 7 of network element OTTAWA to HALF (do not change other settings):ED-ETH:OTTAWA:ETH-7-1:CTAG01:::ETHDPX=HALF;

PAUSETXOVRRIDE

ENABLE If auto-negotiation is enabled and PAUSETXOVRRIDE = ENABLE:Pause frames are generated by the port and sent in the egress direction when PAUSETX = Enable, and not generated when PAUSETX = Disable, regardless of the outcome of the auto-negotiation process.

If auto-negotiation is enabled and PAUSETXOVRRIDE = DISABLE:The port abides with the negotiated pause transmission setting.

When auto-negotiation is disabled, the PAUSETXOVRRIDE setting is ignored.

DISABLE (default)

REMOTELPBK

ALLOW Set to ALLOWED or BLOCKED for remote loopback requests. You can edit this parameter even if the port is In-Service (IS).

Note 1: If you set the parameter LPBKTYPE to REMOTE with the command OPR-LPBK-ETH, the near-end node will send a loopback request every 500ms. A node with REMOTELPBK set to ALLOWED that receives a loopback request will apply a terminal loopback. This will cause the "Remotely Activated Loopback Active" alarm to be raised.

Note 2: Failure to receive a loopback request for 3 seconds will deactivate any remotely activated loopback and clear the corresponding alarm. This will cause the “Remote Loopback Requested” alarm to be raised and will clear the “Remote Loopback Active” alarm (if previously raised).

Note 3: If you set the LPBKTYPE parameter to REMOTE when the far-end node does not support the remote loopback feature, or has REMOTELPBK set to BLOCKED, a “Remote loopback Requested” alarm will be raised. You can clear this alarm by setting REMOTELPBK to ALLOWED at the far-end node (if supported). If this occurs, the “Remote Loopback Active” alarm will be raised.

BLOCKED (default)





ED-FCUse the Edit Fibre Channel command to edit the parameters of a Fibre Channel facility (FC port) on the GE/FC SFP of a 2xGigE/FC-P2P or 2xGigE/FC-P2P-C circuit pack.


Input syntaxED-FC:<tid>:<aid>:<ctag>:::[,SUBRATE=Domain][,EXTREACH=Domain][,SERVICE=Domain][,BBCOVERRIDE=Domain][,COMPRESSION=Domain];


Field Purpose


AID Access identifier. The Fibre Channel facility to provision.


SUBRATE Determines whether or not service is carried over sub-rate bandwidth

EXTREACH Extended reach mode of operation

SERVICE Type of service

BBCOVERRIDE Buffer-to-buffer credit (BBC) override value

COMPRESSION Allows compression. Applies only to the 2xGigE/FC-P2P-C.



FC AID FC-slot#-port#FC-slot#-ALL

Identify the Fibre Channel facility where slot# = 3 to 10port# = 1 or 2



Example inputChange the service mode on FC port 1 of the GE/FC SFP of a 2xGigE/FC-P2P circuit pack in slot 7 of network element OTTAWA to FICON:

ED-FC:OTTAWA:FC-7-1:CTAG01:::SERVICE=FICON;



SUBRATE ENABLE Enable or disable the ability of the service to be carried over sub-rate bandwidth. Must be of the same value as EXTREACH.

DISABLE (default)

EXTREACH ENABLE Enable or disable the extended reach mode of operation. Must be of the same value as SUBRATE.DISABLE (default)

SERVICE FC100 (default) Set the service mode to FC100 or FICON.

FICON

BBCOVERRIDE 0 (default)248163264128256

Set the buffer-to-buffer credit (BBC) override to 0 (no override), 1, 2, 4, 8, 16, 32, 64, 128 or 256. Note that if EXTREACH is disabled, this attribute and the selected value are ignored.

COMPRESSION ENABLE Enable or disable the compression mode of operation. Applicable only for the 2xGigE/FC-P2P-C.DISABLE (default)



ED-FFP-OC12The Edit FFP OC-12 command is used to edit the attributes of the OC-12 1+1 line protection group.

Note 1: Ensure facilities on the protection circuit pack are out of service.



Input syntaxED-FFP-OC12:[TID]:workingOC12AID,protectionOC12AID:CTAG:::[PSDIRN=Domain];


Field Purpose




PSDIRN Direction of protection group for OC-12 lines: UNI (unidirectional) or BI (bidirectional). Default is UNI.



working OC-12 AID

OC12-slot#-port# Identify the slot number of the working OC-12 facilityslot# = 3, 5, 7, 9, or 11 for OC-12slot# = 3, 5, 7, or 9 for OC-12x4 STSport# = 1 for OC-12port# = 1 to 4 for OC-12x4 STS


OC12-slot#-port# Identify the slot number of the protection OC-12 facilityslot# = 4, 6, 8, 10, or 12 for OC-12slot# = 4, 6, 8, or 10 for OC-12x4 STSport# = 1 for OC-12port# = 1 to 4 for OC-12x4 STS



Example inputEdit 1+1 protection for the OC-12 facility in slot 7 port 1 and slot 8 port 1 to be bidirectional: ED-FFP-OC12:SEATTLE:OC12-7-1,OC12-8-1:CTAG13:::PSDIRN=BI;



PSDIRN UNI Unidirectional (default)

BI Bidirectional



ED-FFP-OC192The Edit FFP OC-192 command is used to edit the attributes of the OC-192 line protection group.




Input syntaxED-FFP-OC192:[TID]:workingOC192AID,protectionOC192AID:CTAG:::[PSDIRN=Domain][,WR=Domain];


Field Purpose





PSDIRN Protection switch direction for 1+1 linear systems

WR Wait-to-restore period for BLSR systems



Purpose

working OC-192 AID OC192-slot# Identify the slot number of the working OC-192 whereslot# = 11


OC192-slot# Identify the slot number of the protection OC-192 whereslot# = 12



Example inputEdit 1+1 protection for the OC-192 facility in slots 11and 12 to be bidirectional: ED-FFP-OC192:SEATTLE:OC192-11,OC192-12:CTAG13:::PSDIRN=BI;



PSDIRN UNI

BI

Unidirectional switch for 1+1 linear systems (default)Bidirectional switch for 1+1 linear systems

WR n-MIN INFINITE

Wait-to-restore period for BLSR systems (in minutes, or infinite for no time limit). n = an integer between 1 and 12. Default is 5-MIN.



ED-FFP-OC3The Edit FFP OC-3 command is used to edit the attributes of the OC-3 1+1 line protection group.




Input syntaxED-FFP-OC3:[TID]:workingOC3AID,protectionOC3AID:CTAG:::[PSDIRN=Domain];


Field Purpose




PSDIRN Direction of protection group for OC-3 lines: UNI (unidirectional) or BI (bidirectional). Default is UNI.



Purpose

working OC3 AID

OC3-slot#-port# Identify the slot number of the working OC-3 slot# = 3, 5, 7, 9port# = 1 for OC-3, 1 to 4 for OC-3x4

protection OC3 AID

OC3-slot#-port# Identify the slot number of the protection OC-3 slot# = 4, 6, 8, 10port# = 1 for OC-3, 1 to 4 for OC-3x4



Example inputEdit 1+1 protection for the OC-3 facility in slot 5 port 1 and slot 6 port 1 to be bidirectional:

ED-FFP-OC3:SEATTLE:OC3-5-1,OC3-6-1:CTAG13:::PSDIRN=BI;



PSDIRN UNI

BI

Unidirectional (default)

Bidirectional



ED-FFP-OC48The Edit FFP OC-48 command is used to edit the attributes of the OC-48 line protection group.




Input syntaxED-FFP-OC48:[TID]:workingOC48AID,protectionOC48AID:CTAG:::[PSDIRN=Domain][,WR=Domain];


Field Purpose





PSDIRN Protection switch direction for 1+1 linear systems

WR Wait-to-restore period for BLSR systems



Purpose

working OC-48 AID OC48-slot# Identify the slot number of the working OC-48 facility whereslot# = 11 for OC-48slot# = 3, 5, 7, 9, or 11 for OC-48 STS

protection OC-48 AID OC48-slot# Identify the slot number of the protection OC-48 facility whereslot# = 12 for OC-48slot# = 4, 6, 8, 10, or 12 for OC-48 STS



Example inputEdit 1+1 protection for the OC-48 facility in slots 11and 12 to be bidirectional: ED-FFP-OC48:SEATTLE:OC48-11,OC48-12:CTAG13:::PSDIRN=BI;



PSDIRN UNI

BI

Unidirectional switch for 1+1 linear systems (default)Bidirectional switch for 1+1 linear systems

WR n-MIN INFINITE

Wait-to-restore period for BLSR systems (in minutes, or infinite for no time limit). n = an integer between 1 and 12. Default is 5-MIN.



ED-IPThe Edit IP command is used to edit the IP address and associated parameters assigned to the COLAN on the NP.


Input syntax ED-IP:[TID]::CTAG::[IPADDR]:[NETMASK=Domain][,GATEWAY=Domain][,BCASTADDR=Domain];

Example inputChange the COLAN IP address and default gateway:

ED-IP:OC3IP::CTAG45::47.215.37.65; ED-IP:OC3IP::CTAG45::47.215.37.65:GATEWAY=47.215.0.1;


Field Purpose



IPADDR The unique IP address to assign the COLAN on the NP. The IP address must be in standard dot notation (n.n.n.n) where 0 ≤ n ≤ 255, for example, 47.215.37.65

NETMASK COLAN network mask

GATEWAY COLAN default gateway

BCASTADDR COLAN broadcast address


Parameter Valid value Description

NETMASK Class A: 255.n.n.nClass B: 255.255.n.nClass C: 255.255.255.nClass D: 255.255.255.nClass E: 255.255.255.n

COLAN network mask. Value 0.0.0.0 means that the network mark is assigned automatically by the NP, based on the network class of the IP address. (default) 0.0.0.0

GATEWAY 0.0.0.0 (default)n.n.n.n

COLAN default gateway. Router for packets with unknown destination. Value 0.0.0.0 deletes the currently provisioned gateway.

BCASTADDR 0.0.0.0 (default)n.n.n.n

COLAN broadcast address. Value 0.0.0.0 means the broadcast address is assigned automatically by the NP based on the IP address.



ED-LLSDCCThe Edit Lower Layer SDCC command is used to modify editable layer 2 parameters of the section data communications channel (SDCC) link. When the SDCC link is provisioned, default values are set for these parameters.

Execute the edit command at the far end first since all edit commands cause the link to drop and be reestablished.

You can edit up to nine parameters in one command. The order of the parameters is unimportant. Separate each parameter with a comma.

Note: You cannot edit the SDCC link on OCn facilities related to the DSM.


Input syntaxED-LLSDCC:[TID]:AID:CTAG:::[L2INFO=Domain][,L2REX=Domain][,L2WAIT=Domain][,L2NOA=Domain][,L2IF=Domain][,L2TEI=Domain][,L2SAPI=Domain][,L2TS=Domain][,L2SIDE=Domain];


Field Purpose


AID Access identifier. The equipment to act on.


L2INFO Layer 2 frame size

L2REX Layer 2 retransmission count

L2WAIT Layer 2 waiting acknowledgement timer

L2NOA Layer 2 no activity timer

L2IF Layer 2 outstanding I frame count

L2TEI Layer 2 terminal endpoint identifier

L2SAPI Layer 2 service access point identifier

L2TS Layer 2 transfer type

L2SIDE Layer 2 user side / network side roles





OC-3 AID OC3-slot#-port# Identify the OC-3 whereslot# = 3 to 10port# = 1 for OC-3port# = 1 to 4 for OC-3x4

OC-12 AID

OC12-slot#-port# Identify the OC-12 whereslot# = 3 to 12 for OC-12slot# = 3 to 10 for OC-12x4 STSport# = 1 for OC-12port# = 1 to 4 for OC-12x4 STS

OC-48 AID

OC48-slot# Identify the OC-48 whereslot# = 11 or 12 for OC-48slot# = 3 to 12 for OC-48 STS

OC-192 AID

OC192-slot# Identify the OC-192 whereslot# = 11 or 12

EC-1 AID EC1-slot#-port# Identify the EC-1 whereslot# = 3, 5, 7, 9, port# = 1 to 3

Note: SDCC is not supported on EC-1x12 circuit packs



L2INFO 512 to 1492 The frame size in bytes (default is 1304 bytes)

L2REX 2 to 16 The retransmission count (default is 3)

Although there is no requirement to make this value the same at both ends, it is advisable to do so to improve performance.

L2WAIT 2 to 200 The waiting acknowledgment timer, in tenths of a second (default is 2)


L2NOA 4 to 120 The no activity timer, in seconds (default is 10)




Example inputChange the retransmission count from the default value:ED-LLSDCC:WASHINGTON:OC3-11-1:CTAG23:::L2REX=5;

Change the no activity timer to 100 seconds, the frame size to 1492 bytes and the terminal endpoint identifier to 25:ED-LLSDCC:WASHINGTON:OC3-11-1:CTAG23:::L2NOA=100,L2INFO=1492,L2TEI=25;

L2IF 1 to 127 The outstanding I-frame count (default is 7)


L2TEI 0 to 127 The terminal endpoint identifier (default is 0)

Make the change at both ends as a new value gives the channel a new address.

Make the change at the far end first, because when the first change is made, the channel state becomes down, and association with the far end is lost.

L2SAPI 0 to 63 The Service Access Point Identifier (default is 62)

Make the change at both ends as a new value gives the channel a new address. Make the change at the far end first, because when the first change is made, the channel state becomes down, and association with the far end is lost.

L2TS AITS

UITS

The transfer type. The default is AITS (acknowledged information transfer service).

UITS (unacknowledged information transfer service) is not supported in this release.

L2SIDE USER

NETWORK

AUTO

The role of the local node, network or user. The default value is Auto. The local node attempts to establish a connection with the far end by toggling its role between network and user in a random pattern.

Setting this parameter to auto simplifies the setup of the link since the nodes decide which node is user and which is network. It does not matter which node has which role, as long as the two connecting nodes have opposite roles.





ED-LLX25The Edit Lower Level X.25 command is used to edit the common parameters for all virtual circuits (VC) on the X.25 LAPB level.


Input syntax ED-LLX25:[TID]::CTAG:::[T1=Domain][,T3=Domain][,N1=Domain][,N2=Domain][,K=Domain][,MODULUS=Domain];

Example inputModify the T3 and the N2 parameters: ED-LLX25:OC3NP::CTAG45:::T3=20000,N2=20;


Field Purpose



T1 Acknowledgment timer

T3 Link inactivity timer

N1 Maximum length of I frame

N2 Maximum number of retransmissions

K Window size for transmitter

MODULUS Sequence number range



T1 500 to 10000 ms(default 500)

Acknowledgment timer (500 ms increment)

T3 10000 to 300000 ms(default 30000)

Link inactivity timer (500 ms increment)

N1 1080 to 16440 bits(default 1080)

Maximum length of an I frame in bits (increments of 8)

N2 1 to 30 (default 30) Maximum number of retransmissions

K 1 to 7 or 1 to 127 (default 7)

Window size for the transmitter based on LLX25 MODULUS value

MODULUS 8 or 128 (default 8) Sequence number range



ED-NETYPEUse the Edit Network Element Type command to update the network element to support add/drop multiplexer capabilities for ring configurations. See RTRV-NETYPE (SP host) for more details.


Input syntaxED-NETYPE:[TID]::CTAG:::NETYPE=Domain;

Example inputSet add/drop multiplexer capabilities for the network element NEWYORK:ED-NETYPE:NEWYORK::CTAG42:::NETYPE=ADM;


Field Purpose



NETYPE Type of network element supported



NETYPE TERMINAL Not supported

ADM Used when a shelf processor is replaced with a extended shelf processor. The network element can be set to add/drop multiplexer (ADM) functionality for ring configurations.



ED-OC12The Edit OC12 command is used to set the signal degrade threshold (SDTH) for OC-12 facilities. The signal degrade threshold determines the bit error rate (BER) in a received OC-12 signal at which an autonomous protection switch occurs.

• an autonomous linear protection switch occurs between two 1+1 linear protected OC-12 facilities. (OC-12 facilities are provisioned for 1+1 linear protection with the ENT-FFP-OC12 command. See page 3-51 for more information on the ENT-FFP-OC12 command.)

• an autonomous protection switch occurs between two path-protected (switchmate) OC-12 facilities. (Path protection occurs either at the STS-3c, STS-1, or VT1.5 levels. To provision path protection, see the ED-CRS-xx or ENT-CRS-xx commands).

• Provisioning the SDTH parameter on an optical interface provisions the SDTH for the line and for all signals (STS-3c, STS-1, VT1.5) on that line.

The Edit OC-12 command is also used to edit section trace parameters and SS Bits parameters. By default, the value of SS Bits is SONET but it can also be set to SDH.


Input syntaxED-OC12:[TID]:AID:CTAG:::[SDTH=Domain][,STFORMAT=Domain][,STRC=Domain][,EXPSTRC=Domain][,STFMODE=Domain][,SSBITMDE=Domain]:,[SST];


Field Purpose


AID Access identifier. Identifies an OC-12 facility.


SDTH Signal degrade threshold, bit error level at which a linear autonomous protection switch takes place. See Parameter descriptions table for details.

STFORMAT Section trace format. See Parameter descriptions table for details.

STRC Outgoing section trace message. See Parameter descriptions table for details.



EXPSTRC Expected section trace message. See Parameter descriptions table for details.

STFMODE Section trace fail mode. See Parameter descriptions table for details.

SSBITMDE SS bits mode. See Parameter descriptions table for details.

SST Secondary state. See Parameter descriptions table for details.



OC-12 Facility AID

OC12-slot#-port# Identify the OC-12 facility whereslot# = 3 to 12 for OC-12slot# = 3 to 10 for OC-12x4 STSport# = 1 for OC-12port# = 1 to 4 for OC-12x4 STS

MS DSM AID OC12-slot-1-%HLINK-OC12-Hslot-Hport




SDTH 5 to 9 Translates to 10-5 to 10-9 (default is 6)

STFORMAT NUM Section trace message is 1 byte long (default)

STRING Section trace message is up to 15 bytes long

STRC 0 to 255 if STFORMAT is NUM (default is 1)

ASCII string up to 15 characters

if STFORMAT is STRING (default is null character string). See Note 1.

EXPSTRC 0 to 255 if STFORMAT is NUM (default is 1)




Field Purpose



Example inputAt the NEWYORK network element, set the SDTH for the OC-12 facility in slot 7 port 1 to 10-7 errors per second and the STFMODE to LINEFAIL and the SSBITMDE to SONET:ED-OC12:NEWYORK:OC12-7-1:CTAG23:::SDTH=7,STFMODE=LINEFAIL,SSBITMDE=SONET;

STFMODE OFF Alarms off, no traffic protection (default)

ALMONLY Alarms on, no traffic protection

LINEFAIL Alarms on, with traffic protection. See Notes 2 and 3.

SSBITMDE SONET SS bits operate in SONET mode (default)

SDH SS bits operate in SDH mode

SST AINS Auto in-service

AINS-DEA Auto in-service deactivated

TS Test. See Note 4.

TS-DEA Test Deactivated

Note 1: The Possible values of the section trace messages depend on the STFORMAT value. If STFORMAT is NUM, the Possible values are 0 to 255. If STFORMAT is STRING, the Possible values are any printable alphanumeric ASCII string up to 15 characters (except comma, colon, semi-colon, equal sign, or question mark) or a NULL character string (for example, STRC=, or EXPSTRC=,). Enclose the ASCII string in double quotes (“) to maintain case sensitivity. The string must begin and end with the double quotes. You cannot use double quotes, or any special character, as part of the ASCII string.

Note 2: If STFMODE is currently set to LINEFAIL, you cannot modify the values of STFORMAT, STRC, or EXPSTRC, unless you also change STFMODE to OFF or ALMONLY in the same command.

Note 3: STFMODE can only be changed to LINEFAIL if the values of STFORMAT, STRC, and EXPSTRC are not being changed in the same command.

Note 4: Test access secondary state is supported in slots 3 to 10 only.





ED-OC192The Edit OC-192 command is used to set the signal degrade threshold (SDTH) for OC-192 facilities. The signal degrade threshold determines the bit error rate (BER) in a received OC-192 signal at which an autonomous protection switch occurs. An autonomous linear protection switch occurs between two 1+1 linear protected OC-192 facilities. (OC-192 facilities are provisioned for 1+1 linear protection with the ENT-FFP-OC192 command. See page 3-53 for more information on the ENT-FFP-OC192 command.) The Edit OC-192 command is also used to edit section trace parameters and SS Bits parameters. By default, the value of SS Bits is SONET but it can also be set to SDH.




Field Purpose






STRC Outgoing section trace value. See Parameter descriptions table for details.

EXPSTRC Expected incoming section trace value. See Parameter descriptions table for details.


SSBITMDE SS bit mode for optical signal. See Parameter descriptions table for details.






OC-192 Facility AID

OC192-slot# Identify the OC-192 facility where slot# = 11,12




STFORMAT NUM Integer 1 byte long (default)


STRC 0 to 255 If STFORMAT is NUM (default is 1)


If STFORMAT is STRING (default is null character string). See Note 1.

EXPSTRC 0 to 255 If STFORMAT is NUM (default is 1)


If STFORMAT is STRING (default is null character string). See Note 1.




SSBITMDE SONET Optical signal transmitted is SONET format (default)

SDH Optical signal transmitted is SDH format



Example inputAt the NEWYORK network element, set the SDTH for the OC-192 facility in slot 11 to 10-7 errors per second and the STFMODE to LINEFAIL and the SSBITMDE to SONET:

ED-OC192:NEWYORK:OC192-11:CTAG23:::SDTH=7,STFMODE=LINEFAIL,SSBITMDE=SONET;

SST TS Test. See Note 4.





Note 4: Test access secondary state is supported in slots 3 through 10 only.





ED-OC3The Edit OC-3 command is used to set the signal degrade threshold (SDTH) for OC-3 facilities. The signal degrade threshold determines the bit error rate (BER) in a received OC-3 signal at which an autonomous protection switch occurs.

• an autonomous linear protection switch occurs between two 1+1 linear protected OC-3 facilities. (OC-3 facilities are provisioned for 1+1 linear protection with the ENT-FFP-OC3 command. See page 3-55 for more information on the ENT-FFP-OC3 command.)

• an autonomous protection switch occurs between two path-protected (switchmate) OC-3 facilities. (Path protection occurs either at the STS-3c, STS-1, or VT1.5 levels. To provision path protection, see the ED-CRS-xx or ENT-CRS-xx commands.

• Provisioning the SDTH parameter on an optical interface provisions the SDTH for the line and for all signals (STS-3c, STS-1, VT1.5) on that line.

The Edit OC-3 command is also used to edit the section trace parameters. The user can edit the outgoing section trace message, the expected section trace message, the section trace format, and the section trace failure mode.

The Edit OC-3 command is also used to edit SS Bits parameters. By default, the value of SS Bits is SONET but it can also be set to SDH.

The following cannot be edited on the Host OCn prov-link, and the DSM circuit packs OCn line facility:

• remote node type (REMOTE=OM3X00)

• SS Bit Operation Mode (SSBITMDE=SONET)


Input syntaxED-OC3:[TID]:AID:CTAG:::[SDTH=Domain][,STFORMAT=Domain][,STRC=Domain][,EXPSTRC=Domain][,STFMODE=Domain][,SSBITMDE=Domain][,REMOTE=Domain]:[SST];


Field Purpose








STRC Outgoing section trace message. See Parameter descriptions table for details.

EXPSTRC Expected section trace message. See Parameter descriptions table for details.


SSBITMDE SS bits mode

REMOTE Type of node at remote end (for section trace purposes). See Parameter descriptions table for details.




OC-3 Facility AID

OC3-slot#-port#OC3-slot#-ALL

Identify the OC-3 facility where slot# = 3 to 10 port# = 1 for OC-3port# = 1 to 4 for OC-3x4

DSM or MS DSM OCn Facility AID

OC3-slot#-1-%HLINK-OC3-hslot#-hport#

Identify the DSM or MS DSM OCn facility where slot# = 1 or 2hslot# = 3 to 10hport# = 1 to 4




STFORMAT NUM Section trace message is 1 byte long (default)



Field Purpose












SSBITMDE SONET SS bits operate in SONET mode (default)

SDH SS bits operate in SDH mode

REMOTE EXPRESS Optical Metro node (default)

OC48 OC-48 node

SST AINS Auto in-service

AINS-DEA Auto in-service deactivated

TS Test




Note 3: STFMODE can be only be changed to LINEFAIL if the values of STFORMAT, STRC, and EXPSTRC are not being changed in the same command.





Example inputAt the NEWYORK network element, set the SDTH for OC-3 facility in slot 7 port 1 to 10-7 errors per second, set STFMODE to LINEFAIL, and set SSBITMDE to SONET:

ED-OC3:NEWYORK:OC3-7-1:CTAG23:::SDTH=7,STFMODE=LINEFAIL,SSBITMDE=SONET;

At the OTTAWA network element, edit the section trace information for OC-3 facility in slot 1 hslot 3 hport 1:

ED-OC3:OTTAWA:OC3-1-1-%HLINK-OC3-3-1:ctag12:::STFORMAT=STRING,STRC=DSMTM1;



ED-OC48The Edit OC-48 command is used to set the signal degrade threshold (SDTH) for OC-48 facilities. The signal degrade threshold determines the bit error rate (BER) in a received OC-48 signal at which an autonomous protection switch occurs. An autonomous linear protection switch occurs between two 1+1 linear protected OC-48 facilities. (OC-48 facilities are provisioned for 1+1 linear protection with the ENT-FFP-OC48 command. See page 3-57 for more information on the ENT-FFP-OC48 command.) The Edit OC-48 command is also used to edit section trace parameters and SS Bits parameters. By default, the value of SS Bits is SONET but it can also be set to SDH.




Field Purpose






STRC Outgoing section trace value. See Parameter descriptions table for details.

EXPSTRC Expected incoming section trace value. See Parameter descriptions table for details.


SSBITMDE SS bit mode for optical signal. See Parameter descriptions table for details.






OC-48 Facility AID OC48-slot# Identify the OC-48 facility where slot# = 11,12 for OC-48slot# = 3 to 12 for OC-48 STS




STFORMAT NUM Integer 1 byte long (default)











SSBITMDE SONET Optical signal transmitted is SONET format (default)

SDH Optical signal transmitted is SDH format



Example inputAt the NEWYORK network element, set the SDTH for the OC-48 facility in slot 11 to 10-7 errors per second and the STFMODE to LINEFAIL and the SSBITMDE to SONET:

ED-OC48:NEWYORK:OC48-11:CTAG23:::SDTH=7,STFMODE=LINEFAIL,SSBITMDE=SONET;

SST TS Test. See Note 4.





Note 4: Test access secondary state is supported in slots 3 through 10 only.





ED-PMCONFIG-EC1The Edit Performance Monitoring Configuration EC-1 command instructs the network element to set the PM threshold crossing report type and/or to reset the receive physical PM thresholding baseline value for the EC-1 facility.

You can set the report type to one of the following options:

• threshold crossing alert (TCA)

• TCA summary alarm

• both TCA and TCA summary alarm

• no reporting

To set the report type to both TCA and TCA summary alarm, use the ampersand (&) as a separator for grouping values in the THMODE parameter.


Input syntaxED-PMCONFIG-EC1:[TID]:AID:CTAG::[LOCN],[DIRN],[TMPER]:[THMODE=DOMAIN],[RXPHYBASE=DOMAIN];


Field Purpose


AID Access identifier. The facility to which the command applies


LOCN The location where the monitored parameter originates, and refers to the entity identified by the AID

DIRN The direction which the monitored parameter applies, and is relative to the entity identified by the AID

TMPER The accumulation time period for the PM information

THMODE The PM threshold crossing report type of the entity identified by the AID

RXPHYBASE Used to reset the baseline value for receive physical PM thresholding



Example inputFor EC-1 facilities (all applicable directions and locations) on network element BOSTON, set TCA summary alarm reporting for 15-minute threshold crossings.ED-PMCONFIG-EC1:BOSTON:ALL:CTAG12::,,15-MIN:THMODE=ALARM,;



EC1 EC1-slot#-port#EC1-slot#-ALLEC1-ALL

Identify the EC-1 facilities, whereslot# = 3, 5, 7, 9port # = 1 to 3 for EC-1x3port # = 1 to 12 for EC-1x12 or DS3/EC-1x12

ALL All EC-1 facilities



LOCN nullNENDFENDALL

Default: All applicable locationsNear endFar endAll applicable locations

DIRN nullTRMTRCVALL

Default: All applicable directionsTransmit direction onlyReceive direction onlyAll applicable directions

TMPER null15-MIN1-DAY1-UNT

ALL

Grouping allowed

Default: equivalent to 15-MIN15-minute interval1-day intervalUntimed interval

All intervals

THMODE TCAALARMNONE

Grouping allowed

Default: TCA reportingTCA summary alarm reportingNo reporting

RXPHYBASE RESETNULL

The baseline takes the current receive physical value from the hardware



ED-PMCONFIG-ETHThe Edit Performance Monitoring Configuration Ethernet command instructs the network element to set the PM threshold crossing report type and/or to reset the receive physical PM thresholding baseline value for an Ethernet facility.





• no reporting



Input syntaxED-PMCONFIG-ETH:[TID]:AID:CTAG::[LOCN],[DIRN],[TMPER]:[THMODE=DOMAIN],[RXPHYBASE=DOMAIN];


Field Purpose











Example inputFor Ethernet facility 1 in slot 10 of network element BOSTON, set TCA summary alarm reporting for 15-minute threshold crossings.ED-PMCONFIG-ETH:BOSTON:ETH-10-1:CTAG12::,,15-MIN:THMODE=ALARM,;



ETH ETH-slot#-port#ETH-slot#-ALLETH-ALL

Identify the Ethernet facilities, whereslot# = 3 to 10port# = 1 to 2 for 2xGigE/FC-P2P, 2xGigE/FC-P2P-C or 2xGigE-P2Pport# = 1 to 8 for 8x100BT-P2Pport# = 1 to 4 for 4x100FX-P2P

MS DSM ETH

ETH-slot-port-%HLINK-Hline-Hslot-Hport

slot = 3 to 6; port = 1 to 8, Hline = OC3 or OC12, Hslot = 3 to10, Hport = 1 to 4





Note: FEND is not applicable for MS DSM ETH facility

DIRN nullTRMTRCVALL


TMPER null15-MIN1-DAY1-UNTALLGrouping allowed

Default: equivalent to 15-MIN15-minute interval1-day intervalUntimed intervalAll intervals

THMODE TCAALARMNONEGrouping allowed


RXPHYBASE RESETNULL




ED-PMCONFIG-FCThe Edit Performance Monitoring Configuration Fibre Channel command instructs the network element to set the PM threshold crossing report type and/or to reset the receive physical PM thresholding baseline value for a Fibre Channel facility.





• no reporting



Input syntaxED-PMCONFIG-FC:[TID]:AID:CTAG::[LOCN],[DIRN],[TMPER]:[THMODE=DOMAIN],[RXPHYBASE=DOMAIN];


Field Purpose











Example inputFor Fibre Channel facility 1 in slot 10 of network element BOSTON, set TCA summary alarm reporting for 15-minute threshold crossings.

ED-PMCONFIG-FC:BOSTON:ETH-10-1:CTAG12::,,15-MIN:THMODE=ALARM,;



Purpose

FC FC-slot#-port#FC-slot#-ALLFC-ALL

Identify the Fibre Channel facilities, whereslot# = 3 to 10port# = 1 or 2





DIRN nullTRMTRCVALL



ALL

Grouping allowed


All intervals

THMODE TCAALARMNONE

Grouping allowed


RXPHYBASE RESETNULL




ED-PMCONFIG-OC12The Edit Performance Monitoring Configuration OC-12 command instructs the network element to set the PM threshold crossing report type and/or to reset the receive physical PM thresholding baseline value for the OC-12 facility.





• no reporting



Input syntaxED-PMCONFIG-OC12:[TID]:AID:CTAG::[LOCN],[DIRN],[TMPER]:[THMODE=DOMAIN],[RXPHYBASE=DOMAIN];


Field Purpose








RXPHYBASE Reset the baseline value for receive physical PM thresholding



Example inputFor OC-12 facilities (all applicable directions and locations) on network element BOSTON, set TCA summary alarm reporting for 15-minute threshold crossings.ED-PMCONFIG-OC12:BOSTON:ALL:CTAG12::,,15-MIN:THMODE=ALARM,;



Purpose

OC12 OC12-slot#-port#OC12-slot#-ALLOC12-ALLALL

Identify the OC-12 facilities where slot# = 3 to 12 for OC-12, 3 to 10 for OC-12x4 STSport# =1 for OC-12, 1 to 4 for OC-12x4 STS

MS DSM AID

OC12-slot-1-%HLINK-OC12-Hslot-Hport






DIRN nullTRMTRCVALL



ALL

Grouping allowed


All intervals

THMODE TCAALARMNONE

Grouping allowed


RXPHYBASE RESETNULL




ED-PMCONFIG-OC192The Edit Performance Monitoring Configuration OC-192 command instructs the network element to set the PM threshold crossing report type and/or to reset the optical power received (OPR) physical PM threshold baseline value for the OC-192 facility.





• no reporting



Input syntaxED-PMCONFIG-OC192[TID]:AID:CTAG::[LOCN],[DIRN],[TMPER]:[THMODE=DOMAIN],[RXPHYBASE=DOMAIN];


Field Purpose











Example inputFor OC-192 facilities on network element BOSTON, reset physical PM, optical power received (OPR) to the current value.ED-PMCONFIG-OC192:BOSTON:ALL:CTAG12::,,1-UNT,,RXPHYBASE=RESET;



OC192 OC192-slot#OC192-ALLALL

Identify the OC-192 facilities, whereslot# = 11 or 12





DIRN nullTRMTRCVALL


TMPER null15-MIN1-DAY1-UNTALLGrouping is allowed

Default 15-min bins (for OPR Normal only)15-Minute bins (for OPR Normal only)1-Day bins (for OPR Normal only)Untimed bins (for OPR only)All intervals

THMODE TCAALARMNONE

Grouping is allowed

Default TCAs onlySummary alarms onlyDisable both TCAs and summary alarms

RXPHYBASE RESETNULL

Reset the Receive Physical Baseline value



ED-PMCONFIG-OC3The Edit Performance Monitoring Configuration OC-3 command instructs the network element to set the PM threshold crossing report type and/or to reset the receive physical PM thresholding baseline value for the OC-3 facility.





• no reporting



Input syntaxED-PMCONFIG-OC3:[TID]:AID:CTAG::[LOCN],[DIRN],[TMPER]:[THMODE=DOMAIN],[RXPHYBASE=DOMAIN];


Field Purpose











Example inputFor OC-3 facilities (all applicable directions and locations) on network element BOSTON, set TCA summary alarm reporting for 15-minute threshold crossings.

ED-PMCONFIG-OC3:BOSTON:ALL:CTAG12::,,15-MIN:THMODE=ALARM,;



OC3 OC3-slot#-port#OC3-slot#-ALLOC3-ALL

Identify the OC-3 facilities, where slot# = 3 to 10port# = 1 for OC-3port# = 1 to 4 for OC-3x4

ALL All OC-3 facilities

MS DSM AID

OC3-slot-1-%HLINK-OC3-Hslot-Hport

Identify the OC-3 facilities, whereslot# = 1, 2hslot# = 3 to 10hport# = 1 to 4





DIRN nullTRMTRCVALL



ALL

Grouping allowed


All intervals

THMODE TCAALARMNONE

Grouping allowed


RXPHYBASE RESETNULL




ED-PMCONFIG-OC48The Edit Performance Monitoring Configuration OC-48 command instructs the network element to set the PM threshold crossing report type and/or to reset the optical power received (OPR) physical PM threshold baseline value for the OC-48 ER facility.





• no reporting



Input syntaxED-PMCONFIG-OC48:[TID]:AID:CTAG::[LOCN],[DIRN],[TMPER]:[THMODE=DOMAIN],,[RXPHYBASE=DOMAIN];


Field Purpose











Example inputFor OC-48 facilities on network element BOSTON, reset physical PM, optical power received (OPR) to the current value.

ED-PMCONFIG-OC48:BOSTON:ALL:CTAG12::,,1-UNT,,RXPHYBASE=RESET;



Purpose

OC48 OC48-slot#OC48-ALLALL

Identify the OC-48 facilities, whereslot# = 3 to 12 for OC-48 STS, 11 or 12 for OC-48





DIRN nullTRMTRCVALL



ALL

Grouping allowed


All intervals

THMODE TCAALARMNONE

Grouping allowed


RXPHYBASE RESETNULL




ED-PMCONFIG-STS1The Edit Performance Monitoring Configuration STS-1 command instructs the network element to set the PM threshold crossing report type and/or to reset the receive physical PM thresholding baseline value for the STS-1 facility.





• no reporting



Input syntaxED-PMCONFIG-STS1:[TID]:AID:CTAG::[LOCN],[DIRN],[TMPER]:[THMODE=DOMAIN],[RXPHYBASE=DOMAIN];


Field Purpose












AID type


Purpose

STS1 AID

OC3-slot#-port#-sts#OC3-slot#-port#-ALLOC3-slot#-ALLOC3-ALL

Identify the STS-1 facilities on the OC-3 or OC-3x4 interfaces whereslot# = 3 to 10port# = 1 for OC-3, 1 to 4 for OC-3x4sts# = 1 to 3

OC3-slot#-sts#-%HLINK-OC3-hslot#-hport#

Identify the STS-1 facilities on the DSM interfaces whereslot# = 1 or 2sts# = 1 to 3hslot# = 1 to 10hport# = 1 to 4

OC3-slot#-ALL-%HLINK-OC3-hslot#-hport#

Identify all STS-1 facilities on the DSM interfaces whereslot# = 1 or 2hslot# = 3 to 10hport# = 1 to 4

OC12-slot#-port#-sts#OC12-slot#-port#-ALLOC12-slot#-ALLOC12-ALL

Identify the STS-1 facilities on OC-12 or OC-12x4 STS interfaces where slot# = 3 to 12 for OC-12slot# = 3 to 10 for OC-12x4 STSport# =1 for OC-12port# = 1 to 4 for OC-12x4 STSsts# = 1 to 12

OC12-slot#-sts#-%HLINK-OC12-hslot#-hport#

OC12-slot#-ALL-%HLINK-OC12-hslot#-hport#

Identify the STS-1 facilities on the DSM interfaces whereslot# = 1 or 2sts# = 1 to 12hslot# = 3 to 10hport# = 1 to 4

OC192-slot#-sts#OC192-slot#-ALLOC192-ALL

Identify the STS-1 facilities on OC-192 interfaces whereslot# = 11 or 12port= 1 to 192

EC1-slot#-port#EC1-slot#-ALLEC1-ALL

Identify the STS-1 facilities on the EC-1x3, EC-1x12, or DS3/EC-1x12 interfaces whereslot# = 3, 5, 7, 9port # = 1 to 3 for EC-1x3port # = 1 to 12 for EC-1x12 or DS3/EC-1x12

ALL All applicable STS-1 path facilities



Example inputFor the STS-1 #2 facility (all applicable directions and locations) for the OC-3 circuit pack in slot 9 on network element BOSTON, set TCA summary alarm reporting for 15-minute threshold crossings.

ED-PMCONFIG-STS1:BOSTON:OC3-9-1-2:CTAG12::,,15-MIN:THMODE=ALARM,;





DIRN nullTRMTRCVALL



ALL

Grouping allowed


All intervals

THMODE TCAALARMNONE

Grouping allowed


RXPHYBASE RESETNULL




ED-PMCONFIG-STS12CThe Edit Performance Monitoring Configuration STS-12c command instructs the network element to set the PM threshold crossing report type and/or to reset the receive physical PM thresholding baseline value for the STS-12c facility.





• no reporting



Input syntaxED-PMCONFIG-STS12C:[TID]:AID:CTAG::[LOCN],[DIRN],[TMPER]:[THMODE=DOMAIN],[RXPHYBASE=DOMAIN];


Field Purpose













Purpose

STS-12c OC12-slot#-port#-sts#OC12-slot#-port#-ALLOC12-slot#-ALLOC12-ALL

Identify the STS-12c facilities, whereslot# = 3 to 12 for OC-12slot# = 3 to 10 for OC-12x4 STSport# = 1 for OC-12port# = 1 to 4 for OC-12x4 STSsts# = 1


Identify the STS-12c facilities, whereslot# = 3 to 12 for OC-48 STSslot# = 11 or 12 for OC-48sts# = 1, 13, 25, 37


slot# = 11 to 12sts# = 1, 13, ..., 181

ALL All applicable STS-12c path facilities





DIRN nullTRMTRCVALL




Example inputFor the STS-12c #1 facility (all applicable directions and locations) for the OC-12 circuit pack in slot 9 on network element BOSTON, set TCA summary alarm reporting for 15-minute threshold crossings.

ED-PMCONFIG-STS12C:BOSTON:OC12-9-1:CTAG12::,,15-MIN:THMODE=ALARM,;


ALL

Grouping allowed


All intervals

THMODE TCAALARMNONE

Grouping allowed


RXPHYBASE RESETNULL






ED-PMCONFIG-STS24CThe Edit Performance Monitoring Configuration STS-24c command instructs the network element to set the PM threshold crossing report type and/or to reset the optical power received (OPR) physical PM threshold baseline value for the STS24c facility.





• no reporting



Input syntaxED-PMCONFIG-STS24C:[TID]:AID:CTAG::[LOCN],[DIRN],[TMPER]:[THMODE=Domain],[RXPHYBASE=DOMAIN];


Field Purpose











Example inputFor STS24c facilities on network element BOSTON, reset physical PM, optical power received (OPR) to the current value.ED-PMCONFIG-STS24C:BOSTON:ALL:CTAG12::,,1-UNT,



STS-24c OC192-slot#-sts#OC192-slot#-ALLOC192-ALL

Identify the STS-24c facility whereslot# = 11 or 12 sts# =1, 25, 49, ..., 169All slots with OC-192 circuit packs


Identify the STS-24c facility whereslot# = 3 to 12, sts# =1, 25All slots with OC-48 STS circuit packs





DIRN nullTRMTRCVALL


TMPER null15-min1-day1null15-MIN1-DAY1-UNTAll

Grouping is allowed

Default 15-min bins (for OPR Normal only)15-Minute bins (for OPR Normal only)1-Day bins (for OPR Normal only)Untimed bins (for OPR only)

All intervals Default: equivalent to 15-MIN15-minute interval1-day intervalAll intervals

THMODE TCAALARMNONEGrouping allowed


RXPHYBASE RESETNULL




ED-PMCONFIG-STS3CThe Edit Performance Monitoring Configuration STS-3c command instructs the network element to set the PM threshold crossing report type and/or to reset the receive physical PM thresholding baseline value for the STS-3c facility.





• no reporting



Input syntaxED-PMCONFIG-STS3C:[TID]:AID:CTAG::[LOCN],[DIRN],[TMPER]:[THMODE=DOMAIN],[RXPHYBASE=DOMAIN];


Field Purpose













Purpose

STS-3c AID OC3-slot#-port#-sts#OC3-slot#-port#-ALLOC3-slot#-ALLOC3-ALL

Identify the STS-3c facilityslot# = 3 to 10port# = 1 to 4sts# =1

OC3-slot-1-sts-%HLINK-OC3-Hslot-Hport

OC3-slot-1-ALL-%HLINK-OC3-Hslot-Hport

Identify the STS-3c facility on an OC-3 circuit pack whereslot# = 1,2sts# = 1Hslot# = 3 to 10Hport# = 1 to 4

OC12-slot#-port#-sts#OC12-slot#-port#-ALLOC12-slot#-ALLOC-12-ALL

Identify the STS-3c facilityslot# = 3 to 12 for OC-12slot# = 3 to 10 for OC-12x4 STSport# =1 for OC-12port# = 1 to 4 for OC-12x4 STSsts# = 1, 4, 7, 10

OC12-slot-1-sts-%HLINK-OC12-Hslot-Hport

OC12-slot-1-ALL-%HLINK-OC12-Hslot-Hport

Identify the STS-3c facility on an OC-3 circuit pack whereslot# = 1,2sts# = 1, 4, 7, 10Hslot# = 3 to 10Hport# = 1 to 4


Identify the STS-3c facilityslot# = 3 to 12 for OC-48 STSslot# = 11 or 12 for OC-48sts# = 1, 4, 7, .., 46


slot# = 11 or 12sts# = 1, 4, 7, ..., 190

ALL All applicable STS-3c path facilities



Example inputFor the STS-3c #1 facility (all applicable directions and locations) for the OC-3 circuit pack in slot 9 on network element BOSTON, set TCA summary alarm reporting for 15-minute threshold crossings.

ED-PMCONFIG-STS3C:BOSTON:OC3-9-1-1:CTAG12::,,15-MIN:THMODE=ALARM,;





DIRN nullTRMTRCVALL



ALL

Grouping allowed


All intervals

THMODE TCAALARMNONE

Grouping allowed


RXPHYBASE RESETNULL




ED-PMCONFIG-STS48CThe Edit Performance Monitoring Configuration STS48c command instructs the network element to set the PM threshold crossing report type and/or to reset the optical power received (OPR) physical PM threshold baseline value for the STS48c facility.





• no reporting



Input syntaxED-PMCONFIG-STS48C[TID]:AID:CTAG::[LOCN],[DIRN],[TMPER]:[THMODE=Domain],[RXPHYBASE=DOMAIN];


Field Purpose











Example inputFor STS48c facilities on network element BOSTON, reset physical PM, optical power received (OPR) to the current value.ED-PMCONFIG-STS48c:BOSTON:ALL:CTAG12::,,1-UNT,



STS-48c OC192-slot#-sts#OC192-slot#-ALLOC192-ALL

Identify the STS-48c facility whereslot# = 11 or 12 sts# =1, 49, 97, 145All slots with OC-192 circuit packs


Identify the STS-48c facility whereslot# = 3 to 12, sts# =1All slots with OC-48 STS circuit packs





DIRN nullTRMTRCVALL


TMPER null15-min1-day1null15-MIN1-DAY-UNTAll

Grouping is allowed

Default 15-min bins (for OPR Normal only)15-Minute bins (for OPR Normal only)1-Day bins (for OPR Normal only)Untimed bins (for OPR only)

All intervals Default: equivalent to 15-MIN15-minute interval1-day intervalAll intervals

THMODE TCAALARMNONE

Grouping allowed


RXPHYBASE RESETNULL




ED-PMCONFIG-WANThe Edit Performance Monitoring Configuration WAN command instructs the network element to set the PM threshold crossing report type and/or to reset the receive physical PM thresholding baseline value for a WAN facility.





• no reporting



Input syntaxED-PMCONFIG-WAN:[TID]:AID:CTAG::[MONTYPE],[LOCN],[DIRN],[TMPER]:[THMODE=DOMAIN],[RXPHYBASE=DOMAIN];


Field Purpose













WAN WAN-slot#-port#WAN-slot#-ALLWAN-ALL

Identify the WAN facilities, whereslot# = 3 to 10port# = 1 to 2 for 2xGigE/FC-P2P, 2xGigE/FC-P2P-C or 2xGigE-P2Pport# = 1 to 8 for 8x100BT-P2Pport# = 1 to 4 for 4x100FX-P2P

MS DSM WAN AID

WAN-slot-port-%HLINK-Hline-Hslot-HportWAN-slot-ALL-%HLINK-Hline-Hslot-Hport

Identify the WAN port where slot = 3 to 6, port = 1 to 8, HLINE = OC3 or OC12, Hslot# = 3 to 10, Hport# = 1 to 4



MONTYPE nullLDSLSDSLUASALLGrouping allowed

Default: equivalent to ALLLCAS degraded secondsLCAS severely degraded secondsLCAS unavailable secondsAll applicable MONTYPEsLDS, LSDS, LUAS are applicable only for 4x100FX and 8x100BT-P2P circuit packs.



Note: FEND is not applicable for MS DSM WAN

DIRN nullTRMTRCVALL




Example inputFor WAN facility 1 in slot 10 of network element BOSTON, set TCA summary alarm reporting for 15-minute threshold crossings.ED-PMCONFIG-WAN:BOSTON:WAN-10-1:CTAG12::,,15-MIN:THMODE=ALARM,;

TMPER null15-MIN1-DAY1-UNTALL

Grouping allowed

Default: equivalent to 15-MIN15-minute interval1-day intervalUntimed intervalAll intervals

THMODE TCAALARMNONE

Grouping allowed


RXPHYBASE RESETNULL






ED-PTX25The Edit X.25 Physical Port Configuration command is used to modify the physical port configuration of X.25.


Input syntax ED-PTX25:[TID]::CTAG:::[RXCLKSRC=Domain][,TXCLKSRC=Domain][,CTS_PIN=Domain][,DCD_PIN=Domain][,DSR_PIN=Domain][,DTR_PIN=Domain][,RTS_PIN=Domain][,DSR=Domain][,DTR=Domain][,RTS=Domain];


Field Purpose



RXCLKSRC Receive clock source

TXCLKSRC Transmit clock source

CTS_PIN CTS pin configuration

DCD_PIN DCD pin configuration

DSR_PIN DSR pin configuration

DTR_PIN DTR pin configuration

RTS_PIN RTS pin configuration

DSR DSR pin initial value

DTR DTR pin initial value

RTS RTS pin initial value



RXCLKSRC RXEXT, TXEXT (default RXEXT) Source of receive clock

TXCLKSRC RXEXT, TXEXT (default TXEXT) Source of transmit clock

CTS_PIN ENABLEDDISABLED

(default ENABLED) CTS pin configuration



Example inputModify the X.25 port configuration of OC3NP: ED-PTX25:OC3NP::CTAG45:::RXCLKSRC=RXEXT,TXCLKSRC=RXEXT;

DCD_PIN ENABLED DISABLED

(default DISABLED) DCD pin configuration

DSR_PIN ENABLEDDISABLED

(default DISABLED) DSR pin configuration

DTR_PIN ENABLEDDISABLED

(default ENABLED) DTR pin configuration

RTS_PIN ENABLEDDISABLED

(default ENABLED) RTS pin configuration

DSR ON, OFF (default ON) DSR pin initial value when DSR_PIN is enabled

DTR ON, OFF (default ON) DTR pin initial value when DTR_PIN is enabled

RTS ON, OFF, AUTO (default ON) RTS pin initial value when RTS_PIN is enabled (see Note)

Note: When the range is set to AUTO, the RTS value is under hardware control.





ED-ROLL-STS1 The Edit Rollover STS1 command is used to switch traffic from an existing connection to another connection previously established by an ENT-ROLL-STS1 command.


Input syntaxED-ROLL-STS1:[TID]:fromAID,toAID:CTAG::CCT:RFROM=Domain,RTO=Domain[,VALID=Domain][,EDSWMATE=Domain]:SST;


Field Purpose









EDSWMATE Used to switch the switch mate in a 1WAYPR, 2WAYPR, or 2WAYBR circuit

SST Secondary state






Purpose

STS1facility AID



OC12-slot#-port#-sts# Identify the STS-1 facility on an OC-12 or OC-12x4 STS circuit pack whereslot# = 3 to 12 for OC-12slot# = 3 to 10 for OC-12x4 STSport# = 1 for OC-12port# = 1 to 4 for OC-12x4 STSsts# = 1 to 12




STS1facility AID





STS1 Facility AID on MS DSM






grp = 1 to 3 where grp 1 = DS1s 1 to 28, grp 2 = DS1s 29 to 56, grp 3 = DS1s 57 to 84 Hline = OC3 or OC12Hslot = 3 to 10Hport = 1 to 4



Purpose



Example inputRollover an STS1 working connection on the OC-3x4 circuit pack in a 2WAYPR circuit between a DS3 service and the OC-3x4 circuit pack.

Bridge the original OC-3 connection:ENT-ROLL-STS1:OTTAWA:OC3-11-2-1,DS3-3-1:A::2WAYPR:RFROM=OC3-11-2-1,RTO=OC3-11-3-1,VALID=Y;

Switch to the bridge connection:ED-ROLL-STS1:OTTAWA:OC3-11-2-1,DS3-3-1:B::2WAYPR:RFROM=OC3-11-2-1,RTO=OC3-11-3-1,VALID=Y:SWITCHED;

Remove the original working connection:CMMT-ROLL-STS1:OTTAWA:OC3-11-2-1,DS3-4-1:C::2WAYPR:RFROM=OC3-11-2-1,RTO=OC3-11-3-1;








VALID Y Bridge will be performed regardless of the condition of the switched-to path.


EDSWMATE Y Bridge will be performed regardless of the condition of the switched-to path.


SST SWITCHED (default)

when switching from bridged to switched, SST=SWITCHED

BRIDGED when backing out from switched to bridged, SST=BRIDGED



ED-ROLL-STS12C The Edit Rollover STS-12c command is used to switch traffic from an existing connection to another connection previously established by an ENT-ROLL-STS12c command.


Input syntaxED-ROLL-STS12C:[TID]:fromAID,toAID:CTAG::CCT:RFROM=domain,RTO=domain[,VALID=Domain][,EDSWMATE=Domain]:SST;


Field Purpose










SST Secondary state






STS12Cfacility AID

















Example inputRollover an STS-12c working connection on the OC-12 circuit pack in a 2WAYPR circuit between an OC-12 service and the OC-12 circuit pack.

Bridge the original OC-12 working connectionENT-ROLL-STS12C:OTTAWA:OC12-9-1-1,OC12-8-1-1:CTAG12::2WAYPR:RFROM=OC12-9-1-1,RTO=OC12-8-1-1,VALID=Y;

Switch to the bridge connection

ED-ROLL-STS12C:OTTAWA:OC12-9-1-1,OC12-8-1-1:CTAG12::2WAYPR:RFROM=OC12-9-1-1,RTO=OC12-8-1-1,VALID=Y:SWITCHED;

Remove the original working connection






BRIDGED when backing -out from switched to bridged, SST=BRIDGED







Input syntaxED-ROLL-STS24C:[TID]:fromAID,toAID:CTAG::CCT:RFROM=Domain,RTO=Domain[,VALID=Domain][,EDSWMATE=Domain]:SST;


Field Purpose










SST Secondary state






STS24Cfacility AID

















Bridge the original OC-48 working connectionENT-ROLL-STS24C:OTTAWA:OC48-9-1-1,OC48-8-1-1:CTAG12::2WAYPR:RFROM=OC48-9-1-1,RTO=OC48-8-1-1,VALID=Y;

Switch to the bridge connectionED-ROLL-STS24C:OTTAWA:OC48-9-1-1,OC48-8-1-1:CTAG12::2WAYPR:RFROM=OC48-9-1-1,RTO=OC48-8-1-1,VALID=Y:SWITCHED;

Remove the original working connectionCMMT-ROLL-STS24C:OTTAWA:OC48-9-1-1,OC48-8-1-1:CTAG12::2WAYPR:RFROM=OC48-9-1-1,RTO=OC48-7-1-1;










ED-ROLL-STS3C The Edit Rollover STS-3c command is used to switch traffic from an existing connection to another connection previously established by an ENT-ROLL-STS3C command.




Field Purpose










SST Secondary state






Purpose

STS3Cfacility AID

OC3-slot#-port#-sts# Identify the STS-3c facility on an OC-3 circuit pack whereslot# = 3 to 10port# = 1 for OC-3port# = 1 to 4 for OC-3x4sts# = 1

OC12-slot#-port#-sts# Identify the STS-3c facility on an OC-12 or OC-12x4 STS circuit pack whereslot# = 3 to 12 for OC-12slot# = 3 to 10 for OC-12x4 STSport# = 1 for OC-12port# = 1 to 4 for OC-12x4 STSsts# = 1, 4, 7, or 10

OC48-slot#-sts# Identify the STS-3c facility on an OC-48 or OC-48 STS circuit pack whereslot# =11, 12 for OC-48slot# = 3 to 12 for OC-48 STSsts# = 1, 4, 7, 10, ..., 46

OC192-slot#-sts# Identify the STS-3c facility on an OC-192 circuit pack whereslot# =11, 12sts# = 1, 4, 7, 10, ..., 190





STS3Cfacility AID



















Purpose



Example inputRollover an STS-3c working connection on the OC-3x4 circuit pack in a 2WAYPR circuit between an OC-3 service and the OC-3x4 circuit pack.

Bridge the original OC-3 working connection

ENT-ROLL-STS3C:OTTAWA:OC3-9-1-1,OC3-8-1-1:D::2WAYPR:RFROM=OC3-9-1-1,RTO=OC3-8-1-1,VALID=Y;


ED-ROLL-STS3C:OTTAWA:OC3-9-1-1,OC3-8-1-1:B::2WAYPR:RFROM=OC3-9-1-1,RTO=OC3-8-1-1,VALID=Y:SWITCHED;

Remove the original working connectionCMMT-ROLL-STS3C:OTTAWA:OC3-9-1-1,OC3-8-1-1:C::2WAYPR:RFROM=OC3-9-1-1,RTO=OC3-7-1-1;







Field Purpose










SST Secondary state






STS24Cfacility AID

OC48-slot#-sts# slot# = 11, 12 for OC-48slot# = 3 to 12 for OC-48 STSsts# = 1

OC192-slot#-sts# slot# =11, 12sts# = 1, 49, 97, ... 145


















Bridge the original OC-48 working connection

ENT-ROLL-STS48C:OTTAWA:OC48-9-1-1,OC48-8-1-1:CTAG12::2WAYPR:RFROM=OC48-9-1-1,RTO=OC48-8-1-1,VALID=Y;


ED-ROLL-STS48C:OTTAWA:OC48-9-1-1,OC48-8-1-1:CTAG12::2WAYPR:RFROM=OC48-9-1-1,RTO=OC48-8-1-1,VALID=Y:SWITCHED;

Remove the original working connection




ED-ROLL-VT1 The Edit Rollover VT1 command is used to switch traffic from an existing connection to another connection previously established by an ENT-ROLL-VT1 command.


Input syntaxED-ROLL-VT1:[TID]:fromAID,toAID:CTAG::CCT:RFROM=Domain,RTO=Domain[,VALID=Domain][,EDSWMATE=Domain]:SST;


Field Purpose









EDSWMATE Used to switch the switch mate in a 1WAYPR, 2WAYPR, or 2WAYBR

SST Secondary state






VT1.5facility AID


slot# = 4 to 10port# = 1 to 12, grp = 1 to 3


slot# = 3, 5, 7, 9port# = 1 to 12t1# = 1 to 28


DS1 service module port# = 1 to 84hslot# = 3 to 10hport# = 1 to 4


grp# = 1 to 3hslot# = 3 to 10hport# = 1 to 4







VT1.5facility AID




















Example inputRollover a VT1.5 working connection on the OC-3x4 circuit pack in a 2WAYPR circuit between a DS1 service and the OC-3x4 circuit pack.

Bridge the original working OC-3 connection:ENT-ROLL-VT1:OTTAWA:OC3-10-2-1-7-1,DS1-4-4:A::2WAYPR:RFROM=OC3-10-2-1-7-1,RTO=OC3-10-3-1-7-1,VALID=Y;


ED-ROLL-VT1:OTTAWA:OC3-10-2-1-7-1,DS1-4-4:B::2WAYPR:RFROM=OC3-10-2-1-7-1,RTO=OC3-10-3-1-7-1,VALID=Y:SWITCHED;


CMMT-ROLL-VT1:OTTAWA:OC3-10-2-1-7-1,DS1-4-4:C::2WAYPR:RFROM=OC3-10-2-1-7-1,RTO=OC3-10-3-1-7-1;




When switching from bridged to switched, SST=SWITCHED

BRIDGED When backing -out from switched to bridged, SST=BRIDGED





ED-SECU-PIDThe Edit Security Password Identifier command is used by users to edit their own account’s password on the network element or the network processor. This command cannot be used to edit the password of another user.

Password identifiers (PIDs) must meet the following guidelines:

• The PID must be between 8 and 10 characters.

• The PID can include alphabetical characters, numbers, and the following symbols:

! “ # $ % ` ( ) * + - . / < = > @ [ ] ^ _ ' { | } ~

• The PID must contain at least one alphanumeric character and one non-alphanumeric character (such as one of the above symbols or a number).

• The PID cannot contain any of the following characters: semicolon (;), colon (:), ampersand (&), comma (,), spaces (deleted as entered), control characters, and question mark (?).

• The PID cannot contain the associated user identifier (UID).

• You cannot use any of your previous five passwords or any words that are in the list of unusable passwords. The list of unusable passwords is set with the ENT-SECU-BADPID command and can be retrieved with the RTRV-SECU-BADPID command.

• A double quote (“) entered in the PID must be preceded by a backslash (\). The backslash is considered as a character in the length of the password.

• Carriage returns (<Enter>) are ignored.


Input syntaxED-SECU-PID:[TID]:UID:CTAG::OldPID,NewPID,NewPID;

Note 1: ALL is a valid target identifier (TID).

Note 2: Passwords do not appear on screen.

Note 3: Passwords must be entered twice for confirmation.


Field Purpose


UID User identifier



Example inputChange the password for user FORD on the network element NEWYORK from PREFECT to PENGUINE: ED-SECU-PID:NEWYORK:FORD:CTAG12::PREFECT,PENGUINE,PENGUINE;


OldPID Old user password identifier

NewPID New user password identifier




ED-SECU-USERThe Edit Security User command is used to edit the security parameters associated with a user account on the network element or the network processor. Enter only the data parameters you want to change. The remaining attributes are not altered.

The user identifier (UID) can be 1 to 10 alphanumeric characters. Parameter grouping of UIDs is not possible.

Users with ADMIN privilege (level 4) cannot change their own UPC to a level below 4. This is to ensure that at least one UID with ADMIN privilege always exists. The last account in the network element with level 4 privilege cannot be deleted.


Input syntaxED-SECU-USER:[TID]:UID:CTAG::[NEWUID][,NEWPID][,NEWPID][,UPC]:[TMOUTA=Domain][,TMOUT=Domain][,PAGESTAT=Domain][,PAGE=Domain][,ACCRSTAT=Domain][,ACCR=Domain][,MINW=Domain][,PCND=Domain][,USERTYPE=Domain];

Note 1: ALL is a valid target identifier (TID).

Note 2: Passwords do not appear on screen.

Note 3: Passwords must be entered twice for confirmation.


Field Purpose


UID User identifier


NewUID New user identifier

NewPID New user password identifier

UPC User privilege code

TMOUTA Automatic timeout flag. The user is automatically logged off from the network element if no valid TL1 command is sent within the specified TMOUT interval.

TMOUT Timeout interval in minutes. A decimal number from 1 to 99. The default is 30 minutes.



PAGESTAT Password aging status

PAGE Password aging time

ACCRSTAT Password accreditation status

ACCR Password accreditation time

PCND Early warning time

MINW Minimum waiting time

USERTYPE User account type



TMOUTA Y Timeout enabled. If TMOUTA is enabled and the TMOUT interval is not specified, the default is 30 minutes.

N Timeout disabled. The user will never be automatically logged off. TMOUT is irrelevant (set to 0 minutes).

TMOUT 1 to 99 Timeout interval in minutes (default is 30).

PAGESTAT OFF (default) Turn off password aging.

ON Turn on password aging.

PAGE 0 to 999 Password aging time in days (default is 45).

ACCRSTAT OFF (default) Turn off password accreditation.

ON Turn on password accreditation.

ACCR 0 to 30 Password accreditation time in days. The amount of time a user has to change a password that was assigned to the user account. The default is 0, which means that a password must be changed the day it is assigned to the user account.

PCND 0 to 14 Early warning time in days (default is 14). The number of days before a password expires that the user is given a warning when logging into the network element.


Field Purpose



Example input Change UID of ADMIN on network element NEWYORK to ADMIN2:

ED-SECU-USER:NEWYORK:ADMIN:CTAG12::ADMIN2;

Change UID and PID of UID ADMIN on network element NEWYORK to ADMIN2 and NTADMIN2 respectively:

ED-SECU-USER:NEWYORK:ADMIN:CTAG12::ADMIN2,NTADMIN2,NTADMIN2:TMOUTA=N;

Change UID and PID of UID ADMIN on network element NEWYORK to ADMIN2 and NTADMIN2 respectively, with a UPC level change from 4 to 3, a timeout interval of 60 minutes, an aging time of 60 days, an accreditation period of 20 days, and an early warning time of 7 days:ED-SECU-USER:NEWYORK:ADMIN:CTAG12::ADMIN2,NTADMIN2,NTADMIN2,3:TMOUTA=Y,TMOUT=60,PAGESTAT=ON,PAGE=60,ACCRSTAT=ON,ACCR=20,PCND=7;

MINW 0 to 999 The minimum number of days that a user must wait before changing a password (default is 0).

Note: This parameter applies even when password aging or password accreditation is turned off. However, this parameter does not apply when the password has been assigned and password accreditation is turned on.

USERTYPE 0

1

Local

Network

Note: You can create a temporary account by setting PAGESTAT=ON,ACCTSTAT=OFF, PAGE=X, and MINW=X+1.





ED-SITE-DSMUse the Edit Site-DSM command to assign a site address to the DS1 Service Module (DSM) or the Multiservice DSM (MS DSM). The site address is an attribute used to identify the DSM and is only supported for circuit packs in slot 1 of the DSM.

Note 1: Each DSM must have a site address. The DSM will not be operational until you assign a site address.

Note 2: The DSM site will not be visible at the RTRV-RTG-TBL command.


Input syntaxED-SITE-DSM:[TID]:AID:CTAG::SITE;

Example input Assign a site address to the DS1 service module of network element BOSTON:

ED-SITE-DSM:BOSTON:CTAG12::”XYZ”;


Field Purpose


AID The DSM entity to act upon


SITE Site address. 1 to 40 characters enclosed within quotations.


AID Possible values Purpose

AID DSM or MS DSM

DSM-%HLINK-HLINE-hslot#-hport#

Identify the DSM whereHLINE=OC3 or OC12hslot# = 3 to 10hport# = 1 to 4

The site address must be unique in the network element. Use the working OC-3 or OC-3x4 if protected.



ED-STS1The Edit STS-1 command is used to edit the expected incoming or outgoing path trace values, or both path trace values.


Input syntaxED-STS1:[TID]:AID:CTAG::[MON]:[EXPTRC=Domain],[TRC=Domain];


Field Purpose


AID Access identifier. The STS-1 facility to act on.


MONF Path trace monitoring

EXPTRC Expected incoming path trace message

TRC Outgoing path trace message



Purpose

DS3-slot#-port# Identify the STS-1 path facility on the DS3 slot# = 3 to 10port# =1 to 3 for DS3x3port# = 1 to 12 for DS3x12, DS3x12e, or DS3/EC-1x12

For MS DSM:


Identify the STS-1 path facility on the DS3 slot# = 3, 5, 7, or 9port# =1 to 6Hline = OC3 or OC12Hslot# = 3 to 10; Hport# = 1 to 4

OC3-slot#-port#-sts# Identify the STS-1 path facility on the OC-3slot# = 3 to 10, port# = 1 for OC-3,port# = 1 to 4 for OC-3x4, sts# = 1 to 3



OC12-slot#-port#-sts# Identify the STS-1 path facility on the OC-12 or OC-12x4 STSslot# = 3 to 12 for OC-12slot# = 3 to 10 for OC-12x4 STSport# = 1 for OC-12port# = 1 to 4 for OC-12x4 STSsts# = 1 to 12

OC48-slot#-sts# Identify the STS-1 path facility on the OC-48 or OC-48 STSslot# = 11 or 12 for OC-48slot# = 3 to 12 for OC-48 STSsts# = 1 to 48

OC192-slot#-sts# Identify the STS-1 path facility on the OC-192slot# = 11 or 12sts# = 1 to 192

WAN-slot#-port#-sts# Identify the STS-1 path facility on the WAN port slot# = 3 to 10port# = 1 or 2 for 2xGigE/FC-P2P, 2xGigE/FC-P2P-C, 2xGigE-P2P, or 2x100BT-P2Pport# = 1 to 4 for 4x100FX-P2Pport# = 1 to 8 for 8x100BT-P2Psts# = 1 for 2x100BT-P2Psts# = 1 to 3 for 4x100FX-P2Por 8x100BT-P2Psts# = 1 to 21 for 2xGigE/FC-P2P, 2xGigE/FC-P2P-C, or 2xGigE-P2P


Identify the STS-1 path facility on the MS DSM WAN port slot = 3 to 6; port = 1 to 8 ; sts = 1 to 3Hline = OC3 or OC12Hslot# = 3 to 10; Hport# = 1 to 6



Purpose



ExampleEdit the path trace value:ED-STS1:NEWYORK:OC3-10-1-1:CTAG13::ON:EXPTRC=NEWYORKOC3-10-1-1,TRC=TXPATHDS3-5;



MON ON

OFF (default)

Enables path trace monitoring

Disables path trace monitoring

EXPTRC(See Note)

<ASCII string> Any ASCII string of up to 62 characters

TRC(See Note)

<ASCII string> Any ASCII string of up to 62 characters

Note 1: Enclose the ASCII string in double quotes (“) to maintain case sensitivity. The string must begin and end with the double quotes. You cannot use double quotes as part of the ASCII string.

Note 2: For a DS3/EC-1x12 port, EXPTRC must be greater than one character for the STS Rx Path Trace Mismatch alarm to raise when the TRC value from the far-end is different from the EXPTRC value.



ED-STS12CUse the Edit STS-12c command to edit the expected incoming and/or outgoing path trace values for an STS-12c path.


Input syntaxED-STS12C:[TID]:AID:CTAG::[MON]:[EXPTRC=Domain][,TRC=Domain];


Field Purpose




MON Path trace monitoring





Purpose

WAN AID WAN-slot#-port#-sts# Identify the STS-12c path on the WAN port of the 2xGigE/FC-P2P, 2xGigE/FC-P2P-C, or 2xGigE-P2P where slot# = 3 to 10, port# = 1 or 2, sts# = 1



ExampleEdit the path trace value for WAN port 2 of the 2xGigE/FC-P2P circuit pack in slot 9 of network element OTTAWA:

ED-STS12C:OTTAWA:WAN-9-2-1:CTAG13::ON:EXPTRC=MONTREALWAN-10-1-1,TRC=TXPATH;



MON ON Enable or disable path trace monitoring

OFF (default)

EXPTRC A string up to 62 characters

The expected incoming path trace message

TRC A string up to 62 characters

The outgoing path trace message

Note: Enclose the incoming and outgoing path trace message in double quotes (“) to maintain case sensitivity. You cannot use double quotes in the string.







Field Purpose









Purpose

WAN AID WAN-slot#-port#-sts# Identify the STS-24c path on the WAN port of the 2xGigE/FC-P2P, 2xGigE/FC-P2P-C, or 2xGigE-P2P where slot# = 3 to 10, port# = 1 or 2, sts# = 1



ExampleEdit the path trace value for WAN port 2 of the 2xGigE/FC-P2P circuit pack in slot 9 of network element OTTAWA:





OFF (default)












Field Purpose









Purpose

WAN AID WAN-slot#-port#-sts# Identify the STS-3c path facility on the WAN port slot# = 3 to 10port# = 1 or 2 for 2xGigE/FC-P2P, 2xGigE/FC-P2P-C, 2xGigE-P2P, or 2x100BT-P2Pport# = 1 to 4 for 4x100FX-P2Pport# = 1 to 8 for 8x100BT-P2Psts# = 1 for 2x100BT-P2P, 4x100FX-P2P, or 8x100BT-P2Psts# = 1, 4, 7, ... 19 for 2xGigE/FC-P2P, 2xGigE/FC-P2P-C, or 2xGigE-P2P





ExampleEdit the path trace value for WAN port 2 of the 2x100BT-P2P circuit pack in slot 9 of network element OTTAWA:





OFF (default)








ED-SYSUse the Edit System command to set the following:

• The path signal degrade threshold value for all VT and STS paths within the network element.

• The time out value for test access sessions.

• The point-to-point auto-provisioning mode for 2xGigE circuit packs.

• The state of flexible slot provisioning.

• The auto-concatenation mode.

• The misconnection mode for DSM/MS DSM shelves.

You can also use this command to switch from SONET mode to a Superset (SONET and J-SDH) mode.

Note: You cannot set the 2xGigE configuration mode if there are any slots on the shelf provisioned for 2xGigE equipment. Refer to DLT-EQPT on page 2-143 to deprovision 2xGigE equipment.


Input syntaxED-SYS:[tid]::ctag:::[PATHSDTH=Domain][,JSDHOAM=Domain][,TS_TIMEOUT=Domain][,OPEGEMODE=Domain][,FLEX=Domain][,AC=Domain][,MISC_COND=Domain];


Field Purpose



PATHSDTH Path signal degrade threshold value

JSDHOAM Japan SDH mode

TS_TIMEOUT Test access timeout value

OPEGEMODE 2xGigE point-to-point auto-provisioning mode

FLEX Flexible slot provisioning state

AC Auto-concatenation mode

MISC_COND Misconnection mode for DSM/MS DSM shelves



Example inputAt the NEWYORK network element, set the PATHSDTH to 1x10-5:

ED-SYS:NEWYORK:OC48-11::CTAG23:::PATHSDTH=5;



PATHSDTH 5 to 9 Path signal degrade threshold. Range is 1x10-5 - 1x10-9.

JSDHOAM ON Switch to SONET and J-SDH mode.

OFF (default) Do not switch to SONET and J-SDH mode.

TS_TIMEOUT 0 to 900, default is 300

Time out value in seconds for test access sessions.

OPEGEMODE RPR (default) Do not auto-provision 2xGigE circuit packs for point-to-point mode.

PTPT Auto-provision a 2xGigE circuit pack for point-to-point mode when the 2xGigE equipment is provisioned on the shelf. Refer to the Planning and Ordering Guide (NTRN10AU) for information about this mode.

FLEX ON Enable flexible slot provisioning for the shelf.

OFF (default) Disable flexible slot provisioning for the shelf.

AC ON Enable or disable auto-concatenation for all cross-connects on the network element.

Note 1: The following alarms prevent auto-concatenation from being enabled on OC-3, OC-12, OC-48 and OC-192 facilities: LOS, STM, SD, LOF, EBER, RFI, and AIS.

Note 2: The following alarms prevent auto-concatenation from being enabled on STS-3c, STS-12c, STS-24c and STS-48c facilities: SD, Rollover in Progress, AIS, SLM, UEQ, RFI, and EBER.

OFF (default)

MISC_COND ON (default) In case of a misconnection between the DSM/MS DSM and the Host optical facility, block traffic through the DSM/MS DSM aggregate circuit pack.

OFF In case of a misconnection between the DSM/MS DSM and the Host optical facility, do not block traffic through the DSM/MS DSM aggregate circuit pack.



ED-T1The Edit T1 command is used to edit DS1 facility signal, facility service, and auto-in-service parameters.

If parameter and state changes are requested in the same edit command, the state change is processed first, followed by parameter updates.

Note: To change primary state use the RMV-T1 and RST-T1 commands.


Input syntaxED-T1:[TID]:AID:CTAG:::[EQLZ=Domain][,FENDNTE=Domain][,FLMDE=Domain][,FMT=Domain][,LINECDE=Domain][,MAP=Domain][,OMODE=Domain]][,NIU=Domain]::[,SST][,AINS-TIME];


Field Purpose




EQLZ=DomainFENDNTE=DomainFLMDE=DomainFMT=DomainLINECDE=DomainMAP=DomainOMODE=DomainNIU=DOMAIN

Facility signal attribute parameters. See the Parameter descriptions table on page 2-332.

SST Secondary state

AINS-TIME DS1 auto-in-service time





DS1 AID DS1-slot#-port#DS1-slot#-ALL

Identify the DS1s where slot# =4 to 10, port# =1 to 28

DS1 AID DS1-slot#-port#-t1#DS1-slot#-port#-ALL

Identify the DS1s where slot# = 3, 5, 7, 9port# = 1 to 12t1# = 1 to 28

DSM AID DS1-1-port#-%HLINK-<HLINE>-hslot#-hport#

Identify the DS1 port on DSM or MS DSM whereHLINE=OC3 or OC12port# = 1 to 84hslot# = 3 to 10hport# = 1 to 4

DS1-1-ALL-%HLINK-HLINE-hslot#-hport#

All DS1 ports on the DSM or MS DSM whereHLINE=OC3 or OC12hslot# = 3 to 10hport# = 1 to 4



Description

EQLZ Cable connecting DS1 to DS1 cross-connect. If the cables for the incoming and outgoing streams are different, add “TX” or “RX” to the domain, for example “1RX” or “2TX”.

1, 2 and 3 set the values for both TX and RX cables.

11TX1RX

Default: short: 0 to 220 ft both directions 0 to 220 ft transmit0 to 220 ft receive

22TX2RX

medium: 220 to 430 ft both directions 220 to 430 ft transmit220 to 430 ft receive

33TX3RX

long: 430 to 655 ft both directions 430 to 655 ft transmit430 to 655 ft receive

FENDNTE ANSI

NOTANSI

Default: Far end NTE supports ANSI standards

ANSI standards are not supported



NIU N

Y

DS1 facility does not support NIU feature (default).

DS1 facility does support NIU feature.

FLMDE

BOTH

INC

OC

N

Fault locate mode: Faults in the frame format will be checked for. Use N if DS1 data is unframed.

Default: both incoming and outgoing data streams will have the frame format, as specified by FMT, checked.

Only check incoming data. (Outgoing can be unframed.)

Only check outgoing data.

Do not check the frame format. (The DS1 facility can be unframed or used as a clear channel facility.)

FMT SF

ESF

SF-TR08

Default: Superframe format

Extended Superframe format

Superframe with TR08 extensions

LINECDE Line code. If the incoming and outgoing streams are different, add “TX” or “RX” to the domain, for example “AMITX”, “B8ZSRX”.

Note: For the MS DSM, legacy coding parameters AMITX, AMIRX, B8ZSTX, B8ZSRX are supported when used in the same group. For example AMITX can be used only with AMIRX and not B8ZSRX. Provisioning of AMITX and AMIRX will be retrieved as AMI. The same is true for B8ZS coding group. AMIZCSTX parameter is not supported on MS DSM.

AMI

AMITXAMIRX

Default: Alternate mark inversion (“bipolar”) both directionsAMI transmit AMI receive

AMIZCSTX AMIZCS Transmit. If there are 8 zeros in a byte, the least significant will be changed to a one.

B8ZS B8ZSTXB8ZSRX

Bipolar with 8-zero substitution, both directions B8ZS Transmit B8ZS Receive



Description



MAP

VTASYN

VTBYTE

VTBIT

SIGNLIN

SIGNLOUT

The form of mapping for DS1 payloads into VT1.5s.

Note: You must enter each MAP parameter in a separate command.

Default:VT1.5 bit asynchronous mapping

VT1.5 byte synchronous mapping

VT1.5 bit synchronous mapping

Note: If using VTBYTE mapping, one or both of these mappings can also be specified:

Robbed bit signaling bits are transported.

Out slot (S1 to S4) signaling bits are transported.

Note 1: DS1 facilities on the DSM and MS DSM do not support SIGNLIN and SIGNLOUT.

Note 2: Only VTBYTE and VTASYN mappings are supported by T1 facilities on MS DSM.

OMODE

NORM

IDLE

AZC

Output mode:

Default: The outgoing stream is a regular DS1

The outgoing stream is set to an idle code: repeating 1100

The outgoing stream will have any AIS code changed to all-zeros.



Description



Example inputAlter the provisioning for the DS1 facility on the DS1 circuit pack in slot 4 port 7; change the TX EQLZ value and set the FMT to ESF: ED-T1:NEWYORK:DS1-4-7:CTAG123:::EQLZ=2TX,FMT=ESF;

Change all the DS1 facilities on the DS1 circuit pack in slot 6 to use B8ZS: ED-T1:SEATTLE:DS1-6-ALL:CTAG123:::LINECDE=B8ZS;

Change all the DS1 facilities on the DS1 circuit pack in slot 6 to set the MAP to VTBYTE: ED-T1:SEATTLE:DS1-6-ALL:CTAG123:::MAP=VTBYTE;

Edit the frame format and line code of all DS1 ports on the DS1 service module in hport 7 hport 3 for network element OTTAWA: ED-T1:OTTAWA:DS1-1-ALL-%HLINK-OC3-7-3:CTAG12:::FMT=ESF,LINECDE=AMI;

SST (secondary state)

AINS

AINS-DEA

TS

TS-DEA

auto-in-service

auto-in-service deactivated

test

test deactivated

AINS-TIME(hour-minute)

HH-MM00-01 to 96-00


Amount of time that an error-free signal must be present on the DS1 line in order for the auto-in-service state to clear. If an error-free signal is present for less than this period of time, the DS1 facility remains in an auto-in-service state.


Note 1: The default secondary state for a DS1 facility is NULL. That is, when a DS1 facility autoprovisions, the secondary state is not auto-in-service. This state is reported as a blank in the TL1 response to a RTRV-T1 command. The purpose of the AINS-DEA parameter is to deactivate the AINS secondary state.

When the AINS-DEA parameter is entered, it is not maintained as a secondary state and is not reported by the RTRV-T1 command.

The secondary state remains NULL until it is changed with either the ENT-T1 or ED-T1 command.

Note 2: The default secondary state for DS1 facilities on a provisioned DSM circuit pack is auto-in-service.



Description



ED-T3The Edit T3 command is used to edit the service parameters (attributes) of a DS3 facility, such as the line buildout and auto in-service.

Note: To change primary state use the RMV-T3 and commands.


Input syntaxED-T3:[TID]:AID:CTAG:::[LBO=Domain][,FMT=Domain]][,NIU=Domain]:[,SST][,AINS-TIME];


Field Purpose




LBO Line buildout

FMT Frame format

SST Secondary state

AINS-TIME DS1 auto-in-service time

NIU Network Interface Unit


AID type


Purpose

T3 AID DS3-slot#-port#DS3-slot#-ALL

Identify the DS3s slot# =3, 5, 7, or 9port# = 1 to 3 for DS3x3port# = 1 to 12 for DS3x12, DS3x12e, or DS3VTx12

MS DSM T3 Facility AID





Example inputChange the FMT of the DS3 facility on the DS3 circuit pack in slot 5 port 1 to UNFR: ED-T3:NEWYORK:DS3-5-1:CTAG23:::FMT=UNFR;



FMT ASYNC M13, multiplex framed (default)

UNFR Unframed clear channel

CBIT C-bit parity

LBO 1 0 to 224 ft to DS3 cross-connect (default)

2 225 to 450 ft to DS3 cross-connect

NIU N DS3 facility does not support NIU feature (default).

Y DS3 facility does support NIU feature. DS3 cross-connects must be present to activate the feature.

SST (secondary state)

AINS

AINS-DEA

TS

TS-DEA

auto-in-service

auto-in-service deactivated

test

test deactivated

AINS-TIME(hour-minute)

HH-MM00-01 to 96-00


Amount of time that an error-free signal must be present on the DS3 line in order for the auto-in-service state to clear. If an error-free signal is present for less than this period of time, the DS3 facility remains in an auto-in-service state.




ED-TARP-CONFIGThe Edit TARP Configuration command is used to configure the (TARP) processor parameters as required.

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


Input syntaxED-TARP-CONFIG:[TID]::CTAG::OPERATION:[TMODE=Domain][,NSEL=Domain][,LIFE=Domain][,PTYPE=Domain][,SEQ=Domain][,THROTTLE=Domain][,T1=Domain][,T3=Domain][,LDBFLUSH=Domain][,TDCFLUSH=Domain][,LDBELIFE=Domain];



Field Purpose



OPERATION Configuration operation. See Parameter descriptions.

TMODE TARP mode

NSEL Network selector

LIFE PDU lifetime

PTYPE Protocol address type

SEQ PDU sequence number

THROTTLE Throttle and period

T1 TARP type 1 request period

T3 Address resolution request waiting period

LDBFLUSH Loop detection buffer flush

TDCFLUSH TARP data cache flush

LDBELIFE Loop detection buffer entry life





OPERATION SETRESETRESETALL

SET: Set parameters specified in configuration operation. Supply at least one keyword-defined parameter.RESET: Reset parameters specified in configuration operation to default values by specifying only the keyword.RESETALL: Reset all parameters to default values.

TMODE PROPAGATIONORIGINATIONBOTHNONE

TARP modeDefault: Both propagation and origination

NSEL String of 2 hexadecimal digitsnull

Network selector Default: AF for CLNP type of address

LIFE 0 to 65535

null

PDU lifetime. A integer value from 0 to 65535 (hops)Default: 100 hops

PTYPE String of 2 hexadecimal digitsnull

Protocol address typeDefault: FE for CLNP

SEQ 0 to 65535

null

PDU sequence number. A integer value from 0 to 65535 ( number of hops)Default: 100 hops

THROTTLE Trottle = 0 .. 32767Period = 1 .. 32767

null

Throttle and period. A decimal number grouping.Throttle (integer) is the maximum number of PDUs processed within the time of interval period (second)

Throttle default: 300 Period default: 2 An example is: THROTTLE=300&2

T1 0 to 3600

null

TARP type 1 request waiting periodA integer value from 0 to 3600 secondsDefault: 15 seconds



Example inputReset the TMODE and T1 parameter to the default on network element NEWYORK:

ED-TARP-CONFIG:NEWYORK::CTAG123::RESET:TMODE=,T1=;

T3 0 to 3600

null

Address resolution request response waiting periodA integer value from 0 to 3600 secondsDefault: 40 seconds

LDBFLUSH 0 to 1440

null

Loop detection buffer flushA integer value from 0 to 1440 minutesDefault: 5 minutes

TDCFLUSH 0 to 1440

null

TARP data cache flushA integer value from 0 to 1440 minutesDefault: 1440 minutes

LDBELIFE 1 to 10

null

Loop detection buffer entry lifeA integer value from 1 to 10 minutesDefault: 5 minutes





ED-TARP-TBLThe Edit TARP Tables command is used to edit the disabled adjacency table (DAT), disabled circuit/port table (DCT), loop detection buffer (LDB), manual adjacency table (MAT), and TARP data cache (TDC).


Input syntaxED-TARP-TBL:[TID]::CTAG::TABLE,OPERATION:[LDBENTRY=Domain][,TDCENTRY=Domain][,MATENTRY=Domain][,DATENTRY=Domain][,DCTENTRY=Domain];


Field Purpose



TABLE TARP Table

CDAT - Disabled adjacency tableDCT - Disabled circuit/port tableLDB - Loop detection buffer MAT - Manual adjacency tableTDC - TARP data cache

OPERATION TARP Operation

ADD - Adds a new entry operationDEL - Deletes an entry operationFLUSH - Flushes the table

LDBENTRY Loop detection buffer entry

TDCENTRY TARP Data cache entry

MATENTRY Manual adjacency table entry

DATENTRY Disabled adjacency table entry

DCTENTRY Disabled circuit/port table entry



Example inputDelete all entries from LDB table:

ED-TARP-TBL:OTTAWA::CTAG12::LDB,FLUSH;



LDBENTRY

12 digit hexadecimal string

0-65535

Loop detection buffer entry System ID and SEQ

System ID

SEQ (sequence number)

TDCENTRY

string of up to 20 characters

hexadecimal number up to 40 digits

TARP data cache entry TID and NSAP

TID

NSAP a number including a maximum of 40 hexadecimal digits

MATENTRY



Manual adjacency table entry NSAP or System ID

NSAP is a number including a maximum of 40 hexadecimal digits

System ID is a 12 hexadecimal digit number

DATENTRY



Disabled adjacency table entry NSAP or System ID

NSAP is a number including a maximum of 40 hexadecimal digits

SystemID is a 12 hexadecimal digit number

DCTENTRY LAN0, DCC-3, DCC-4, DCC-5, DCC-6, DCC-7, DCC-8, DCC-9, DCC-10, DCC-11, DCC-12

Disabled circuit/port table entry

Note: Add or delete the parameter(s) from the specified TABLE. Either parameter is mandatory if the OPERATION is either ADD or DEL. If OPERATION is FLUSH, the parameter(s) is ignored and all entries on the specified TABLE are deleted.



ED-TOD-MODEThe Edit Time of Day Mode command is used to activate or deactivate the time of day (TOD) feature. This command is also used to configure the polling time and set the threshold values for the TOD feature.

Threshold values are checked against the NP time in the event of the SP and against the external NTP server with respect to the NP.

The polling times will vary between the minimum and maximum polling intervals.


Input syntax (for NP)ED-TOD-MODE:[TID]::CTAG:::SYNC=domain[,MINPOLL=Domain] [,MAXPOLL=Domain][,THRESHOLD=Domain];

Input syntax (for SP)ED-TOD-MODE:[TID]::CTAG:::SYNC=domain [,THRESHOLD=Domain];


Field Purpose



SYNC TOD synchronization switch (on, off)

MINPOLL Minimum polling interval

MAXPOLL Maximum polling interval

THRESHOLD Threshold offset value



SYNC Active Turns TOD synchronization on

Inactive (default) Turns TOD synchronization off



Example input Set TOD parameters on a NP.

ED-TOD-MODE:NPFGX505::78:::SYNC=ACTIVE,MINPOLL=15,MAXPOLL=16, THRESHOLD=8;

Set TOD parameters on a SP.ED-TOD-MODE:SPFGX505::79:::SYNC=ACTIVE,THRESHOLD=4;

MINPOLL 2N where N is 1, 2, 3 ...16Default is 2

Minimum polling interval in seconds based on 2N.

MAXPOLL 2N where N is 1, 2, 3 ...16Default is 9

Maximum polling interval in seconds based on 2N.

THRESHOLD 1 to 1800 in increments of 1 for NPDefault is 6002 to 8 in increments of 1 for SPDefault is 5

Time of day offset threshold in seconds





ED-ULSDCC (network element)The Edit ULSDCC command is used to change manual area addresses of the section data communications channel (SDCC) link. When the SDCC link is provisioned, MANAREA0 has a default setting of 49000.

You must have at least one manual area address provisioned. If you want to delete the address in MANAREA0 and it is the only address provisioned, you must first provision an address in MANAREA1 or MANAREA2, then delete the address in MANAREA0.

To change a manual area address, you must delete the address that is provisioned, then add the new address. For example, to change MANAREA1, enter the command to edit MANAREA1 and leave a blank for the domain. This clears the address in MANAREA1. Then enter the command to edit MANAREA1 again, and enter the new address for the domain.


Input syntaxED-ULSDCC:[TID]::CTAG:::[MANAREA0=Domain][,MANAREA1=Domain][,MANAREA2=Domain];



Field Purpose



MANAREA0 Layer 3 area address 0





Example inputEdit the address in MANAREA1, by clearing the address that is already provisioned, then entering a new address:ED-ULSDCC:SEATTLE::CTAG34:::MANAREA1=;

ED-ULSDCC:SEATTLE::CTAG34:::MANAREA1=39830f80000000000000000000;

Delete area address 2ED-ULSDCC:SEATTLE::CTAG34:::MANAREA2=;



MANAREA0 3 to 13 octets, each octet of the form PQ, where P and Q are ASCII-encoded hex values

Area address 0 (default)

MANAREA1 Area address 1

MANAREA2 Area address 2

Note 1: The MANAREA address must follow a standard format for data communications protocol.

Note 2: Use null to delete the existing area address.



ED-ULSDCC (network processor)The Edit Upper Layer SDCC command is used to edit the network layer address of the OSI stack on the NP. Three manual area addresses can be provisioned. The manual area address identifies the network to which the NP belongs. When the NP is provisioned, MANAREA0 has a default setting of 490000.

You must have at least one manual area address provisioned. If you want to delete the address in MANAREA0 and it is the only address provisioned, you must first provision an address in MANAREA1 or MANAREA2, then delete the address in MANAREA0.

To change a manual area address, you must ensure that at least two area addresses are provisioned. You must delete the address you want to change, then add the new address. For example, to change MANAREA1, enter the command to edit MANAREA1 and leave a blank for the domain. This clears the address in MANAREA1. Then enter the command to edit MANAREA1 again, and enter the new address for the domain.


Input syntax ED-ULSDCC:[TID]::CTAG:::[MANAREA0=Domain][,MANAREA1=Domain][,MANAREA2=Domain];



Example inputEdit the address in MANAREA1, by clearing the address that is already provisioned, then entering a new address:ED-ULSDCC:OC3NP::CTAG34:::MANAREA1=;

ED-ULSDCC:OC3NP::CTAG34:::MANAREA1=39840f80000000000000000000;

Delete area address 0:ED-ULSDCC:OC3NP::CTAG34:::MANAREA0=;


Field Purpose








MANAREA0 3 to 13 octets, each octet of the form PQ, where P and Q are ASCII-encoded hex values

Network layer area address 0 (default)

MANAREA1 Network layer area address 1

MANAREA2 Network layer area address 2



ED-ULX25The Edit Upper Level X.25 command is used to edit the common parameters for all switched virtual circuits (SVCs) on the X.25 network level.

Note 1: To edit the parameters for a permanent virtual circuit (PVC), use the ED-VC command (page 2-352).

Note 2: Changes to any of the following ULX25 parameters cause all current SVC calls to be lost and all PVC calls to be restarted: TXSIZE, RXSIZE, WNDW, MODULUS, T20, N20, T21, T22, T23, N22, N23, or DBIT.

Note 3: Changes to any of the following ULX25 parameters only affect new calls: NUI, NEGFLOWCTRL, NEGTXSIZE, NEGRXSIZE, NEGTXWNDW, NEGRXWNDW, NEGTRPTCLS, NEGTXTRPT, or NEGRXTRPT.


Input syntax ED-ULX25:[TID]::CTAG:::[TXSIZE=Domain][,RXSIZE=Domain][,WNDW=Domain][,MODULUS=Domain][,T20=Domain][,N20=Domain][,T21=Domain][,T22=Domain][,T23=Domain][,N22=Domain][,N23=Domain][,DBIT=Domain][,NUI=Domain][,NEGFLOWCTRL=Domain][,NEGTXSIZE=Domain][,NEGRXSIZE=Domain][,NEGTXWNDW=Domain][,NEGRXWNDW=Domain][,NEGTRPTCLS=Domain][,NEGTXTRPT=Domain][,NEGRXTRPT=Domain];


Field Purpose



TXSIZE Maximum Transmitting Packet Size

RXSIZE Maximum Receiving Packet Size

WNDW Packet Window Size

MODULUS Sequence Number Range

T20 DTE Restart Time-out

N20 Number of T20 Retries

T21 DTE Call Request Time-out

T22 DTE Reset Time-out



T23 Declare Time-out



DBIT Delivery Confirmation Option

NUI Network User ID

NEGFLOWCTRL Negotiate Flow Control

NEGTXSIZE NFC Transmit Packet Size

NEGRXSIZE NFC Receive Packet Size

NEGTXWNDW NCF Transmit Packet Window Size

NEGRXWNDW NCF Receive Packet Window Size

NEGTRPTCLS Negotiate Throughput Class

NEGTXTRPT Throughput Class of Transmitter

NEGRXTRPT Throughput Class of Receiver



TXSIZE 16 to 4096 (default 128) Maximum transmitting packet size

RXSIZE 16 to 4096 (default 128) Maximum receiving packet size

WNDW 1 to 7 or 1 to 127

(default 2) Packet window size based on ULX25 MODULUS value

MODULUS 8 or 128 (default 8) Sequence number range

T20 5 to 500 sec (default 180 sec) Data terminating equipment (DTE) restart time-out (5 sec increment)

N20 1 to 255 (default 1) Number of T20 retries

T21 5 to 500 sec (default 200 sec) DTE call request time-out (5 sec increment)

T22 5 to 500 sec (default 180 sec) DTE reset time-out (5 sec increment)


Field Purpose



Example inputModify the TXSIZE and the RXSIZE parameters: ED-ULX25:OC3NP::CTAG45:::TXSIZE=256,RXSIZE=256;

T23 5 to 500 sec (default 180 sec) Declare time-out (5 sec increment)



DBIT Y N

(default YES) Delivery confirmation option

NUI Maximum 20 ASCII characters

(default null string) Network user identification for SVC only. (see Note 4)

NEGFLOWCTL ONOFF

(default OFF) Negotiate flow control (NFC)

NEGTXSIZE 16 to 4096 (default 128) NFC: Tx packet size(see Note 1)

NEGRXSIZE 16 to 4096 (default 128) NFC: Rx packet size(see Note 1)

NEGTXWNDW 1 to 7 or 1 to 127

(default 2) NFC: Tx window size based on ULX25 MODULUS value (see Note 1)

NEGRXWNDW 1 to 7 or 1 to 127

(default 2) NFC: Rx window size based on LIX25 MODULUS value (see Note 1)

NEGTRPTCLS ONOFF

(default OFF) Negotiate throughput class

NEGTXTRPT 7 to 11 (default 10) Throughput class: speed of transmitter (see Note 2)

NEGRXTRPT 7 to 11 (default 10) Throughput class: speed of receiver (see Note 2)

Note 1: The default value applies only when NEGFLOWCTRL is ON.

Note 2: The default value applies only when NEGTRPTCLS is ON.

Note 3: Any edited parameter values are also applied only when NEGFLOWCTRL or NEGTRPTCLS is on.

Note 4: Some ASCII characters are not supported for NUI. The semi-colon (;), question mark (?), backslash (\), space ( ), double quotes ( “), and comma (,) are not supported.





ED-VCThe Edit Virtual Circuit (VC) command modifies the parameter values of the specified permanent virtual circuit (PVC). This command cannot be used to modify a switched virtual circuit (SVC). To modify SVCs, use the ED-ULX25 command (page 2-349).

You can use ED-VC to change an SVC to a PVC, or to change a PVC to an SVC. To change an SVC to a PVC, you must specify the values of LCGN and LCN. Default values of TXSIZE and RXSIZE are available from ULX25 (see Table 2-397). To change a PVC to an SVC, the PVC is deleted and the circuit is restored as an SVC with default parameter values from the ULX25 (see Table 2-397).


Input syntaxED-VC:[TID]:AID:CTAG::TYPE:[DBIT=Domain][,WNDW=Domain][,T21=Domain][,T22=Domain][,T23=Domain][,N22=Domain][,N23=Domain][,LCN=Domain][,LCGN=Domain][,TXSIZE=Domain][,RXSIZE=Domain];


Field Purpose


AID Access identifier. The VC number to act on. Possible values are 0 to 15. Null is not a valid value.


TYPE The virtual circuit (VC) type, SVC or PVC

DBIT Delivery Confirmation Option

WNDW Packet Window Size

T21 DTE Call Request Time-out

T22 DTE Reset Time-out

T23 Declare Time-out



LCN Logical Channel Number (required for PVC)



Example inputChange SVC #10 to PVC: ED-VC:OC3NP:10:CTAG45::PVC:LCGN=0,LCN=5,WNDW=5;

This command reconfigures VC #10 to be a PVC with LCGN and LCN set to 0 and 5 respectively, and WNDW set to 5.

Change PVC #10 back to SVC: ED-VC:OC3NP:10:CTAG45::SVC:;

This command deletes PVC #10 and restores VC #10 as an SVC with WNDW reset to default value 2.

LCGN Logical Channel Group Number (required for PVC)

TXSIZE Maximum Transmitting Packet Size

RXSIZE Maximum Receiving Packet Size



DBIT YN

(default YES) Delivery confirmation option

WNDW 1 to 7 or 1 to 127

(default 2) Packet window size based on ULX25 MODULUS value

T21 5 to 500 sec (default 200 sec) DTE call request time-out

T22 5 to 500 sec (default 180 sec) DTE reset time-out

T23 5 to 500 sec (default 180 sec) Declare time-out



LCN 0 to 255 Logical channel number (see Note)

LCGN 0 to 7 Logical channel group number (see Note)

TXSIZE 16 to 4096 (default 128) Maximum transmitting packet size

RXSIZE 16 to 4096 (default 128) Maximum receiving packet size

Note: Values for LCGN and LCN must be provided when switching an SVC to a PVC.


Field Purpose



ED-WANUse the Edit WAN command to edit the parameters of a WAN port of a 2x100BT-P2P or 8x100BT-P2P circuit pack. You can also use this command to edit the WAN on the GE/FC SFP of a 2xGigE/FC-P2P, 2xGigE/FC-P2P-C, 2xGigE-P2P or a 4x100FX P2P circuit pack.

Note: To edit the parameters of a WAN port, the corresponding ETH or FC port must be in an out-of-service (OOS) state. See RMV-ETH on page 3-393 to put a ETH port to an OOS state. See RMV-FC on page 3-394 to put an FC port to an OOS state.


Input syntax ED-WAN:[tid]:aid:ctag:::[MAGICNUM=Domain][,FCS=Domain][,LCM=Domain][,MAPPING=Domain][,VCAT=Domain][,LCAS=Domain][,LANFCS=Domain][,GFPRTDELAY=Domain][,GFPRFI=Domain];


Field Purpose


AID Access identifier. The WAN port to edit.


MAGICNUM Magic number (for 2x100BT-P2P only)

FCS Frame check sum. Does not apply for the WAN port that is associated with a fibre channel port.

LCM Link connectivity monitor (for 2x100BT-P2P only)

VCAT Virtual concatenation (not applicable for 2x100BT-P2P)

GFPRFI Generic Framing Procedure Remote Failure Indication. Enable or disable control of the GFP RFI client management frame (CMF) transmission on the WAN facility (not applicable for 2x100BT-P2P)

GFPRTDELAY Enable or disable the ping used by a CMF to calculate RTDELAY (not applicable for 2x100BT-P2P)

LCAS Link Capacity Adjustment Scheme, (only for the 8x100BT-P2P and 4x100FX-P2P circuit packs). This parameter defaults to DISABLE, and can only be ENABLED when the VCAT parameter is ENABLED.





WAN AID WAN-slot#-port#WAN-slot#-ALL

Identify the WAN port where slot# = 3 to 10port# = 1 to 8 for 8x100BT-P2Pport# = 1 to 4 for 4x100FX-P2Pport# = 1 to 2 for all the other supported cards

MS DSM WAN AID

WAN-slot-port-%HLINK-Hline-Hslot-Hport

Identify the WAN port where slot = 3 to 6port = 1 to 8HLINE = OC3 or OC12Hslot# = 3 to 10Hport# = 1 to 4 depending on the circuit pack



MAGICNUM ENABLE Enable or disable the use of a magic number. The magic number is used during PPP negotiation on the 2x100BT-P2P WAN facility only. When enabled, the magic number field is four octets and helps in detecting looped back links. A random string is sent across the link and if the same value is returned, then the circuit pack determines that the link is looped back and the negotiation fails. If this occurs, a "Link Down" alarm is raised against the WAN port.

When disabled, the magic number is always transmitted as zero and is always ignored on reception.

DISABLE (default)

FCS 0 Set the frame check size (in bits) of the WAN port. Possible values for the 2x100BT-P2P WAN facility are 16 or 32. Possible values for the 2xGigE/FC-P2P, 2xGigE/FC-P2P-C or 2xGigE-P2P WAN facility are 0 or 32.

Note that the port at the other end of the connection must have the same frame check size as this port.

This parameter is only available for the GE/FC SFP WAN facility if the WAN facility was created in association with the ETH port.

16

32



LCM ENABLE Whether link connectivity monitoring is enabled or disabled at the WAN port. This attribute is only supported on the 2x100BT-P2P WAN facility.

Note that if you enable link connectivity monitoring, the “Link Down” alarm is raised against the WAN port during a software load or FPGA upgrade or when the port at the other end of the connection does not support link connectivity monitoring. The recommended configuration is to have link connectivity monitoring disabled at both ends of the connection.

Note that when link connectivity monitoring is enabled, an echo request is sent every second. If more than five echo requests are transmitted without receiving an echo response, the PPP operational OSI state becomes disabled and PPP attempts to re-establish the link connection through LCP configuration request packets.

DISABLE (default)

VCAT ENABLE Enable or disable virtual concatenation for the GE/FC SFP WAN facility. This attribute is disabled by default. Note that you can only edit this attribute if there are no cross-connections present on the specified facility.

DISABLE (default)

GFPRFI ENABLE (default for ETH)

Enable or disable to control the GFP RFI CMF transmission. You can only edit this parameter if the WAN facility is OOS-MA. If enabled, GFPRFI causes GFP RFI CMF transmission if the WAN link goes down.

DISABLE (default and only value for FC)





Example inputEnable the use of a magic number, set the FCS to 16 bits, and disable link connectivity monitoring on WAN port 2 of the 2x100BT-P2P circuit pack in slot 9 of network element OTTAWA:

ED-WAN:OTTAWA:WAN-9-2:CTAG01:::MAGICNUM=ENABLE,FCS=16,LCM=DISABLE;

GFPRTDELAY ENABLE (default) Enable or disable the ping used by a CMF to calculate RTDELAY and the “Distance Exceeded Alarm”. If this parameter is set to DISABLE, the RTDELAY will always be UNKNOWN and the “Distance Exceeded Alarm” will not be raised. This parameter can only be edited when the WAN facility is OOS-MA.

DISABLE

LCAS ENABLE (default) LCAS is a signalling protocol for VCAT that allows hitless VCGM addition to or deletion from a group. It also allows automated degradation of the total bandwidth capacity of a VCG when one or more of its VCGMs is faulty. Can only be edited if virtual concatenation is enabled.

DISABLE




Copyright 2000-2008 Nortel Networks, All Rights Reserved

This document is protected by copyright laws and international treaties. All information, copyrights and any other intellectual property rights contained in this document are the property of Nortel Networks. Except as expressly authorized in writing by Nortel Networks, the holder is granted no rights to use the information contained herein and this document shall not be published, copied, produced or reproduced, modified, translated, compiled, distributed, displayed or transmitted, in whole or part, in any form or media.

Nortel

Optical Metro 3500TL1 Reference—Part 1 of 4

323-1059-190Standard Release 16.0 Issue 1December 2008Printed in Canada

This information is provided “as is”, and Nortel Networks does not make or provide any warranty of any kind, expressed or implied, including any implied warranties of merchantability, non-infringement of third party intellectual property rights, and fitness for a particular purpose.

Nortel, the Nortel logo, and the Globemark are trademarks of Nortel Networks.

tl1 reference guide - 323-1059-190.1.r16

Documents