tl1 reference guide - 323-1059-190.2.r16

NTN465GNNTN465GN 323-1059-190

Nortel

Optical Metro 3500TL1 Reference—Part 2 of 4

What’s inside...Commands ENT-aa to RST-zz

See Part 1 for commands A to ED-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

Commands ENT-aa to RST-zz 3-1ENT-ALM-PROFILE 3-9ENT-BLSRRING 3-11ENT-CHALLENGE-RESPONSE 3-12ENT-CRS-STS1 3-13ENT-CRS-STS12C 3-18ENT-CRS-STS24C 3-21ENT-CRS-STS3C 3-24ENT-CRS-STS48C 3-29ENT-CRS-VT1 3-31ENT-EC1 3-36ENT-EQPT 3-38ENT-ETH 3-43ENT-FAC 3-48ENT-FC 3-49ENT-FFP-OC12 3-51ENT-FFP-OC192 3-53ENT-FFP-OC3 3-55ENT-FFP-OC48 3-57ENT-GRE 3-59ENT-IPT 3-61ENT-IPTR 3-62ENT-LLSDCC 3-63ENT-OC12 3-65ENT-OC192 3-67ENT-OC3 3-70ENT-OC48 3-73ENT-RINGMAP 3-75ENT-ROLL-STS1 3-77ENT-ROLL-STS12C 3-81ENT-ROLL-STS24C 3-84ENT-ROLL-STS3C 3-87ENT-ROLL-STS48C 3-91ENT-ROLL-VT1 3-94ENT-SECU-ACCESS 3-98ENT-SECU-BADPID 3-99ENT-SECU-USER 3-100

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

iv Contents

ENT-T1 3-103ENT-T3 3-108EX-SW-OC12 3-110EX-SW-OC192 3-112EX-SW-OC3 3-114EX-SW-OC48 3-116INH-EX-OC12 3-118INH-EX-OC192 3-119INH-EX-OC3 3-120INH-EX-OC48 3-121INH-MSG-ALL 3-122INH-MSG-BROADCAST 3-123INH-UPGRD 3-124INIT-COLD 3-125INIT-OM-ETH 3-126INIT-OM-IF 3-127INIT-REG-ALL 3-129INIT-REG-EC1 3-133INIT-REG-ETH 3-137INIT-REG-FC 3-141INIT-REG-OC12 3-145INIT-REG-OC192 3-149INIT-REG-OC3 3-153INIT-REG-OC48 3-157INIT-REG-STS1 3-161INIT-REG-STS12C 3-165INIT-REG-STS24C 3-169INIT-REG-STS3C 3-173INIT-REG-STS48C 3-176INIT-REG-T1 3-180INIT-REG-T3 3-184INIT-REG-WAN 3-188INIT-UPGRD-EQPT 3-192INIT-WARM 3-193INVK-INSTALL 3-196INVK-RINGMAP 3-197INVK-UPGRD 3-198LOAD-FPGA 3-199LOAD-INSTALL 3-201LOAD-REPLACE 3-202LOAD-RINGMAP 3-203LOAD-TL1SCRPT-NE 3-204LOAD-UPGRD 3-207OPR-ACO-ALL 3-209OPR-BITSOUTSW 3-210OPR-EXT-CONT 3-211OPR-LAMP-TEST 3-214OPR-LPBK-EC1 3-216OPR-LPBK-ETH 3-218OPR-LPBK-FC 3-220OPR-LPBK-OC12 3-222

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

Contents v

OPR-LPBK-OC192 3-223OPR-LPBK-OC3 3-224OPR-LPBK-OC48 3-225OPR-LPBK-T1 3-226OPR-LPBK-T3 3-228OPR-PROTNSW-EQPT 3-230OPR-PROTNSW-OC12 3-233OPR-PROTNSW-OC192 3-235OPR-PROTNSW-OC3 3-237OPR-PROTNSW-OC48 3-239OPR-PROTNSW-STS1 3-241OPR-PROTNSW-STS12C 3-243OPR-PROTNSW-STS24C 3-245OPR-PROTNSW-STS3C 3-247OPR-PROTNSW-STS48C 3-249OPR-PROTNSW-VT1 3-251OPR-SYNCSW 3-253OPR-TARP-TEF 3-254OPR-TOD-SYNC 3-256REPTÂLM^COM 3-257REPTÂLMÊC1 3-260REPTÂLMÊNV 3-262REPTÂLMÊQPT 3-265REPTÂLM^FAC 3-269REPTÂLMÔC12 3-271REPTÂLMÔC192 3-274REPTÂLMÔC3 3-276REPTÂLMÔC48 3-278REPTÂLM^SECU 3-280REPTÂLM^STS1 3-282REPTÂLM^STS12C 3-286REPTÂLM^STS24C 3-288REPTÂLM^STS3C 3-290REPTÂLM^STS48C 3-293REPTÂLM^T1 3-295REPTÂLM^T3 3-297REPTÂLM^VT1 3-299REPT^CONFIG^CHG 3-302REPT^DBCHG 3-303REPTÊVT^COM 3-306REPTÊVTÊC1 3-309REPTÊVTÊQPT 3-311REPTÊVTÎNVENTORY 3-315REPTÊVT^LOG 3-319REPTÊVTÔC12 3-321REPTÊVTÔC192 3-324REPTÊVTÔC3 3-326REPTÊVTÔC48 3-329REPTÊVT^STS1 3-331REPTÊVT^STS12C 3-335REPTÊVT^STS24C 3-338


vi Contents

REPTÊVT^STS3C 3-341REPTÊVT^STS48C 3-345REPTÊVT^T1 3-348REPTÊVT^T3 3-351REPTÊVT^VT1 3-353REPTÊX^LINK 3-356REPTÎMSG 3-358REPT^SOC 3-359REPT-INITZN 3-361REPT-STAT 3-362RLS-EXT-CONT 3-363RLS-LPBK-EC1 3-365RLS-LPBK-ETH 3-366RLS-LPBK-FC 3-367RLS-LPBK-OC12 3-368RLS-LPBK-OC192 3-369RLS-LPBK-OC3 3-370RLS-LPBK-OC48 3-371RLS-LPBK-T1 3-372RLS-LPBK-T3 3-373RLS-PROTNSW-EQPT 3-374RLS-PROTNSW-OC12 3-376RLS-PROTNSW-OC192 3-377RLS-PROTNSW-OC3 3-379RLS-PROTNSW-OC48 3-380RLS-PROTNSW-STS1 3-382RLS-PROTNSW-STS12C 3-383RLS-PROTNSW-STS24C 3-384RLS-PROTNSW-STS3C 3-385RLS-PROTNSW-STS48C 3-386RLS-PROTNSW-VT1 3-387RMV-EC1 3-388RMV-EQPT 3-389RMV-ETH 3-393RMV-FC 3-394RMV-OC12 3-395RMV-OC192 3-396RMV-OC3 3-397RMV-OC48 3-398RMV-SOC 3-399RMV-T1 3-400RMV-T3 3-401RST-BANNER 3-402RST-EC1 3-403RST-EQPT 3-404RST-ETH 3-407RST-FC 3-408RST-OC12 3-409RST-OC192 3-410RST-OC3 3-411RST-OC48 3-412


Contents vii

RST-PROV 3-413RST-PROV-SP 3-417RST-T1 3-420RST-T3 3-421


viii Contents


ix323-1059-190

About this document 0

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

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

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

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 Networks Optical Metro 3500 Release 16.0.

Supported hardwareThis document supports the Optical Metro 3500 shelf.

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

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

AudienceThe following members of your company are the intended audience of this Nortel Networks 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 Networks, 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.nortelnetworks.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.nortelnetworks.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.nortelnetworks.com. Click on the Contact Us link.


3-1

Commands ENT-aa to RST-zz 3-

This chapter covers the TL1 commands from ENT-aa to RST-zz.

For more TL1 commands, see:

• Part 1 for commands A to ED-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

ENT-ALM-PROFILE 3-9

INH-MSG-ALL 3-122

INH-MSG-BROADCAST 3-123

OPR-ACO-ALL 3-209

OPR-EXT-CONT 3-211

RLS-EXT-CONT 3-363

Automatic report commands

REPTÂLM^COM 3-257

REPTÂLMÊC1 3-260

REPTÂLMÊNV 3-262

REPTÂLMÊQPT 3-265

REPTÂLM^FAC 3-269

REPTÂLMÔC12 3-271

REPTÂLMÔC192 3-274


3-2 Commands ENT-aa to RST-zz

REPTÂLMÔC3 3-276

REPTÂLMÔC48 3-278

REPTÂLM^SECU 3-280

REPTÂLM^STS1 3-282

REPTÂLM^STS12C 3-286




REPTÂLM^T1 3-295

REPTÂLM^T3 3-297

REPTÂLM^VT1 3-299

REPT^CONFIG^CHG 3-302

REPT^DBCHG 3-303

REPTÊVT^COM 3-306

REPTÊVTÊC1 3-309

REPTÊVTÊQPT 3-311

REPTÊVTÎNVENTORY 3-315

REPTÊVT^LOG 3-319

REPTÊVTÔC12 3-321

REPTÊVTÔC192 3-324

REPTÊVTÔC3 3-326

REPTÊVTÔC48 3-329

REPTÊVT^STS1 3-331

REPTÊVT^STS12C 3-335




REPTÊVT^T1 3-348

REPTÊVT^T3 3-351

Task/Command Page


Commands ENT-aa to RST-zz 3-3

REPTÊVT^VT1 3-353

REPTÊX^LINK 3-356

REPTÎMSG 3-358

REPT^SOC 3-359

BLSR commands

ENT-BLSRRING 3-11

ENT-RINGMAP 3-75

INVK-RINGMAP 3-197

LOAD-RINGMAP 3-203

Cross-connect commands

ENT-CRS-STS1 3-13

ENT-CRS-STS12C 3-18

ENT-CRS-STS24C 3-21

ENT-CRS-STS3C 3-24

ENT-CRS-STS48C 3-29

ENT-CRS-VT1 3-31

DS1 service module commands

OPR-LAMP-TEST 3-214

Equipment commands

ENT-EQPT 3-38

INIT-UPGRD-EQPT 3-192

RMV-EQPT 3-389

RST-EQPT 3-404

Facility commands

ENT-EC1 3-36

ENT-ETH 3-43

ENT-FC 3-49

ENT-FFP-OC12 3-51

ENT-FFP-OC192 3-53

Task/Command Page



ENT-FFP-OC3 3-55

ENT-FFP-OC48 3-57

ENT-OC12 3-65

ENT-OC192 3-67

ENT-OC3 3-70

ENT-OC48 3-73

ENT-T1 3-103

ENT-T3 3-108

RMV-EC1 3-388

RMV-ETH 3-393

RMV-FC 3-394

RMV-OC12 3-395

RMV-OC192 3-396

RMV-OC3 3-397

RMV-OC48 3-398

RMV-T1 3-400

RMV-T3 3-401

RST-EC1 3-403

RST-ETH 3-407

RST-FC 3-408

RST-OC12 3-409

RST-OC192 3-410

RST-OC3 3-411

RST-OC48 3-412

RST-T1 3-420

RST-T3 3-421

Facility test signal generation commands

OPR-LPBK-EC1 3-216

OPR-LPBK-ETH 3-218

Task/Command Page



OPR-LPBK-FC 3-220

OPR-LPBK-OC12 3-222

OPR-LPBK-OC192 3-223

OPR-LPBK-OC3 3-224

OPR-LPBK-OC48 3-225

OPR-LPBK-T1 3-226

OPR-LPBK-T3 3-228

RLS-LPBK-EC1 3-365

RLS-LPBK-ETH 3-366

RLS-LPBK-FC 3-367

RLS-LPBK-OC12 3-368

RLS-LPBK-OC192 3-369

RLS-LPBK-OC3 3-370

RLS-LPBK-OC48 3-371

RLS-LPBK-T1 3-372

RLS-LPBK-T3 3-373

Initialization commands

INIT-COLD 3-125

INIT-WARM 3-193

Inservice traffic rollover commands

ENT-ROLL-STS1 3-77

ENT-ROLL-STS12C 3-81


ENT-ROLL-STS3C 3-87


ENT-ROLL-VT1 3-94

Network processor commands

ENT-FAC 3-48

ENT-GRE 3-59

Task/Command Page



RMV-SOC 3-399

Packet Edge ring management commands

ENT-IPT 3-61

ENT-IPTR 3-62

Performance monitoring commands

INIT-OM-ETH 3-126

INIT-OM-IF 3-127

INIT-REG-ALL 3-129

INIT-REG-EC1 3-133

INIT-REG-ETH 3-137

INIT-REG-FC 3-141

INIT-REG-OC12 3-145

INIT-REG-OC192 3-149

INIT-REG-OC3 3-153

INIT-REG-OC48 3-157

INIT-REG-STS1 3-161

INIT-REG-STS12C 3-165




INIT-REG-T1 3-180

INIT-REG-T3 3-184

INIT-REG-WAN 3-188

Protection switching commands

EX-SW-OC12 3-110

EX-SW-OC192 3-112

EX-SW-OC3 3-114

EX-SW-OC48 3-116

INH-EX-OC12 3-119

Task/Command Page



INH-EX-OC192 3-116

INH-EX-OC3 3-120

INH-EX-OC48 3-121

OPR-PROTNSW-EQPT 3-230

OPR-PROTNSW-OC12 3-233




OPR-PROTNSW-STS1 3-243

OPR-PROTNSW-STS12C 3-245




OPR-PROTNSW-VT1 3-251

RLS-PROTNSW-EQPT 3-374

RLS-PROTNSW-OC12 3-376




RLS-PROTNSW-STS1 3-382

RLS-PROTNSW-STS12C 3-383




RLS-PROTNSW-VT1 3-387

SDCC commands

ENT-LLSDCC 3-63

Security and administration commands

ENT-CHALLENGE-RESPONSE 3-12

Task/Command Page



ENT-SECU-ACCESS 3-98

ENT-SECU-BADPID 3-99

ENT-SECU-USER 3-100

LOAD-TL1SCRPT-NE 3-204

OPR-TOD-SYNC 3-256

RST-BANNER 3-402

RST-PROV 3-413

RST-PROV-SP 3-417

Software load installation commands

INVK-INSTALL 3-196

LOAD-INSTALL 3-201

LOAD-UPGRD 3-207

Software upgrade commands

INH-UPGRD 3-124

INVK-UPGRD 3-198

LOAD-FPGA 3-199

LOAD-REPLACE 3-202

Synchronization commands

OPR-BITSOUTSW 3-210

OPR-SYNCSW 3-253

TARP commands

OPR-TARP-TEF 3-254

Test access commands

REPT-INITZN 3-361

REPT-STAT 3-362

Task/Command Page



ENT-ALM-PROFILEThe Enter Alarm Profile command allows the user to create a new alarm profile. The profile is given a name and the status of all alarms in the profile is initially set to enabled by default.

Security LevelLevel 3

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

Table 3-1Syntax definition

Field Purpose

TID Target identifier

CTAG Correlation tag

AIDTYPE Access identifier TYPE

PRFLNAME Alarm profile name assigned by user

Table 3-2Parameter description

Parameter Possible values Description

AIDTYPE VT1 VT1 facility

STS1 STS-1 facility

STS3C STS-3C facility




EQPT equipment

T1 T1 facility

T3 T3 facility

EC1 EC-1 facility

E1 E1 facility

OC3 OC-3 facility



Example input Create a new alarm profile for network element NEWYORK: ENT-ALM-PROFILE:NEWYORK::CTAG12::OC48,”ALARMSON”;

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

Table 3-2 (continued)Parameter description




ENT-BLSRRINGUse the Enter BLSR Ring command to create a new BLSR ring with the specified name. This command is supported on the network processor.

Security levelLevel 3

Input syntaxENT-BLSRRING:[TID]:AID:CTAG;

Example inputCreate a new BLSR ring with the name OTTAWA_RING:

ENT-BLSRRING:NPFGXOTT:OTTAWA_RING:CTAG;


Field Purpose

TID Target identifier.

AID Ring name


Table 3-4AID descriptions

AID type Command-specific values Purpose

Ring name An alphanumeric string between 1 and 20 characters. Special characters are not supported.

Identify the ring name

Table 3-5Parameter descriptions


AID An alphanumeric string between 1 and 20 characters. Special characters are not supported.

Ring name



ENT-CHALLENGE-RESPONSEUse the Enter Challenge Response command to enter the response to a retrieved challenge. If the response is correct, you are logged in to the network processor or shelf processor with the appropriate user privilege code (UPC) for this login session.


Input syntaxENT-CHALLENGE-RESPONSE:[TID]::CTAG::RESPONSE;

Example inputEnter the response to log in to network processor NEWYORK:ENT-CHALLENGE-RESPONSE:NEWYORK::CTAG23::1FR5DVB6;


Field Purpose



RESPONSE Response



RESPONSE Any valid response Response to the retrieved challenge. If the response includes lowercase characters, enclose the response in double quotes (“).



ENT-CRS-STS1The Enter Cross-connect STS-1 command is used to add an STS-1 connection between two STS-1 facilities.

Note: When a cross-connect command fails due to bandwidth fragmentation on the 8x100BT-P2P or MS DSM, the following message is issued: “Available backplane bandwidth is fragmented”. Use DEFRAG-EQPT to perform bandwidth defragmentation.


Input syntaxENT-CRS-STS1:[TID]:FromAID,ToAID:CTAG::[CCT]:[SWMATE=Domain][,CKTID=Domain][,FROMAEND=Domain][,FROMZEND=Domain][,TOAEND=Domain][,TOZEND=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 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”).

FROMAEND APS ID of FromAID originating node for BLSR systems.

FROMZEND APS ID of FromAID terminating node for BLSR systems.

TOAEND APS ID of ToAID originating node for BLSR systems.

TOZEND APS ID of ToAID terminating node for BLSR systems.




AID type Command-specific values

Purpose

STS-1 Facility AID

OC3-slot#-port#-sts# Identify the STS-1 facility on an OC-3 circuit pack whereslot# = 3 to 10, port# = 1 for OC-3port# = 1 to 4 for OC-3x4, sts# = 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, port# = 1 for OC-12port# = 1 to 4 for OC-12x4 STS, sts# = 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, 12, sts# = 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 9, port# = 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

Note: For shelves equipped with VTX-48 or VTX-48e circuit packs, the total bandwidth available for a Point-to-Point circuit pack is 12xSTS1 in each direction, that is, 12xSTS1 for ingress and 12xSTS1 for egress. However, the bandwidth is allocated bidirectionally, which means the same AID must be used for ingress and egress.

STS1 Facility AID on MS DSM

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

slot = 3 or 5, port = 1 to 6, Hline = OC3 or OC12, Hslot = 3 to 10, Hport = 1 to 4

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

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

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

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# 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

Note: For RPR connections where the Side 1 and Side 2 optics are both in odd slots, the slot number of the optical interface used for Side 1 must be greater than the slot number of the optical interface used for Side 2 (for example, you can use OC48-11 for Side 1 and OC12-5 for Side 2).

Table 3-9 (continued)AID descriptions


Purpose





CCT 1WAY Unidirectional connection

2WAY Bidirectional connection (default)

1WAYPR Unidirectional path ring connection

2WAYPR Bidirectional path ring connection

2WAYBR Bidirectional bridge ring connection

IPTRING SONET bandwith allocation for an RPR

SWMATE 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 12port# = 1 for OC-12port# = 1 to 4 for OC-12x4sts# = 1 to 12


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

CKTID 1 to 40 alphanumeric characters

Connection identifier. A string between 1 and 40 alphanumeric characters that identifies the cross-connect.

FROMAEND An integer between 0 and 15

APS ID of FromAID originating node for BLSR systems

FROMZEND An integer between 0 and 15

APS ID of FromAID terminating node for BLSR systems



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, add a bidirectional STS-1 passthrough cross-connection between the OC-3 interfaces in slot 9 port 1 sts 1 and slot 10 port 1 sts 1:

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

To provision bandwidth to an RPR:

ENT-CRS-STS1:OC3SP:OC3-9-1-1,IPTR-1:CTAG12::IPTRING;ENT-CRS-STS1:OC3SP:OC3-10-1-1,IPTR-1:CTAG12::IPTRING;

Note: The OCn optical circuit pack for either end must be on different slots of a different protection pair.

Example inputFor the OTTAWA network element, add a STS-1 cross-connection between the OC-48 interface in slot 11 sts 1 and the OC-12 interface in slot 9 sts 1 and define the entry point and the exit point for a BLSR system: ENT-CRS-STS1:OTTAWA:OC48-11-1,OC12-9-1-1:CTAG12::2WAY:FROMAEND=2,FROMZEND=3;

TOAEND An integer between 0 and 15

APS ID of ToAID originating node for BLSR systems

TOZEND An integer between 0 and 15

APS ID of ToAID terminating node for BLSR systems

Note: If the fromAid is a tributary, FROMAEND/FROMZEND parameters are not applicable. If toAid is a tributary, TOAEND/TOZEND parameters are not applicable.

Table 3-10 (continued)Parameter descriptions




ENT-CRS-STS12CThe Enter Cross-connect STS-12c command is used to add a STS-12c connection between two STS12c facilities.


Input syntaxENT-CRS-STS12C:[TID]:FromAID,ToAID:CTAG::[CCT]:[SWMATE=Domain][,CKTID=Domain][,FROMAEND=Domain][,FROMZEND=Domain][,TOAEND=Domain][,TOZEND=Domain];


Field Purpose






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










STS-12c Facility AID

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

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 10, port# = 1 or 2, sts# = 1

RPR AID














Example inputFor the NEWYORK network element, add a bidirectional STS-12c passthrough cross-connection between the OC-12 interfaces in slots 9 and 10:

ENT-CRS-STS12C:NEWYORK:OC12-9-1-1,OC12-10-1-1:CTAG12::2WAY;

To provision bandwidth to a RPR:

ENT-CRS-STS12C:OC12SP:OC12-9-1-1,IPTR-1:12::IPTRING;ENT-CRS-STS12C:OC12SP:OC12-10-1-1,IPTR-1:12::IPTRING;


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-48slot# = 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




















Field Purpose


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

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














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

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








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

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










Example inputFor the NEWYORK network element, add a bidirectional STS-24c passthrough cross-connection between the OC-48 STS interfaces in slots 9 and 10:

ENT-CRS-STS24C:NEWYORK:OC48-9-1-1,OC48-10-1-1:CTAG12::2WAY;











ENT-CRS-STS3CThe Enter Cross-connect STS-3c command is used to add an STS-3c connection between two STS3c facilities.

Note 1: When a cross-connect command fails due to bandwidth fragmentation on the 8x100BT-P2P or MS DSM, the following message is issued: “Available backplane bandwidth is fragmented”. Use DEFRAG-EQPT to perform bandwidth defragmentation.

Note 2: When a cross-connect command fails due to STS-3c WAN physical fragmentation on the MS DSM, the following message is issued: “Resource required to create STS3c connection are fragmented”. Use DEFRAG-EQPT to perform physical defragmentation.




Field Purpose


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

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



SWMATE Path protection switch mate. Path protection for the FromAID OC-n interface when CCT is protected (that is, when CCT is 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 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 12, port# = 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

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

Table 3-17 (continued)Syntax definition

Field Purpose



STS-3c Facility AID

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

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












Purpose




Example inputFor the NEWYORK network element, add a bidirectional STS-3c passthrough cross-connection between the OC-3 interfaces in slots 9 and 10: ENT-CRS-STS3C:NEWYORK:OC3-9-1-1,OC3-10-1-1:CTAG12::2WAY;

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
















To provision bandwidth to an RPR:

ENT-CRS-STS3C:OC3SP:OC3-9-1-1-1,IPTR-1:CTAG12::IPTRING;

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


Example inputFor the OTTAWA network element, add a STS-3c cross-connection between the OC-48 interface in slot 11 sts 4 and the OC-12 interface in slot 9 sts 1 and define a BLSR passthrough:

ENT-CRS-STS3C:OTTAWA:OC48-11-4,OC12-9-1-1:CTAG5::2WAY:FROMAEND=1,FROMZEND=4;







Field Purpose















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

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




Example inputFor the NEWYORK network element, add a bidirectional STS-48c passthrough cross-connection between the OC-48 STS interfaces in slots 9 and 10: ENT-CRS-STS48C:NEWYORK:OC48-9-1-1,OC48-10-1-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














ENT-CRS-VT1The Enter Cross-connect VT1.5 command is used to cross-connect one VT1.5 facility to another.

Note 1: When a cross-connect command fails due to bandwidth fragmentation on the 8x100BT-P2P or MS DSM, the following message is issued: “Available backplane bandwidth is fragmented”. The message may not appear when provisioning a bulk of VT1.5 cross-connects. The message always appears for single VT1.5 cross-connects. Use DEFRAG-EQPT to perform bandwidth defragmentation.

Note 2: When a cross-connect command fails due to DS1 physical fragmentation on the MS DSM, the following message is issued: “Resource required to create a DS1 group <grp> connection are fragmented”, where <grp> is the number of the DS1 group or groups. Use DEFRAG-EQPT to perform physical defragmentation.


Input syntaxENT-CRS-VT1:[TID]:FromAID,ToAID:CTAG::[CCT]:[SWMATE=Domain][,CKTID=Domain][,FROMAEND=Domain][,FROMZEND=Domain][,TOAEND=Domain][,TOZEND=Domain];


Field Purpose


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

ToAID To access identifier. The facility at the other end of the cross-connect. For unidirectional connections, 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

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

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

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

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

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

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 7vt# = 1 to 4


Field Purpose



Use the DFLT-# smart AID to cross-connect 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. 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 3-25 shows the DFLT-# smart AID value and the corresponding ports.

For network element NEWYORK, create 28 DS1, 2 way bidirectional connections from DSM STS1, group number 1, connecting to OC12 in slot 5, port 1 channel 1 through OC3 in slot 3 channel 1.

Example inputENT-CRS-VT1:NEWYORK:DS1-DFLT-1-%HLINK-OC3-3-1,OC12-5-1-1-ALL:189::2WAY:,CKTID="";

VT1.5 facility AID

OC12-slot#-port#-sts#-vtg#-vt#OC12-slot#-port#-sts#-vtg#-ALLOC12-slot#-port#-sts#-ALL

slot# = 3 to 12port# = 1, sts# = 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 7vt# = 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 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

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 2, vtg# = 1 to 7,vt# = 1 to 4 or sts#=3, vtg#=1 to 2, Hline = OC3 or OC12, Hslot# = 3 to 10, Hport# = 1 to 4

SMART AID DS1-DFLT-grp# grp# = 1 to 3





Table 3-25DFLT-# 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-3port# = 1 to 4 for OC-3x4sts# = 1 to 3vtg# = 1 to 7vt# = 1 to 4

OC12-slot#-port#-sts#-vtg#-vt#OC12-slot#-port#-sts#-vtg#-ALLOC12-slot#-port#-sts#-ALL

Identify the VT1.5 facility whereslot# = 3 to 12port# = 1sts# = 1 to 12vtg# = 1 to 7vt# = 1 to 4

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

Identify the VT1.5 facility whereslot# = 11, 12sts# = 1 to 48vtg# = 1 to 7vt# = 1 to 4

CKTID 1 to 40 alphanumeric characters Connection identifier. A string between 1 and 40 alphanumeric characters that identifies the cross-connect.




Example inputFor the NEWYORK network element, add a VT1.5 bidirectional cross-connect between the DS1 mapper in slot four and the path protected optical interfaces in slots 9 and 10:

ENT-CRS-VT1:NEWYORK:OC3-9-2-1-1-1,DS1-4-1:CTAG45::2WAYPR:SWMATE=OC3-10-2-1-1-1;

For the WASHINGTON network element, add 28 bidirectional VT1.5 cross-connects between the DFLT-1 VT1.5 facilities (DS1 ports 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 8 and 10: ENT-CRS-VT1:WASHINGTON:OC3-8-3-1-ALL,DS1-DFLT-1:CTAG89::2WAYPR:SWMATE=OC3-10-3-1-ALL;

Note: For a BLSR VT1.5 traffic, the cross-connects on the passthrough nodes should be at the STS-1 level.

FROMAEND An integer between 0 and 15 APS ID of FromAID originating node for BLSR systems

FROMZEND An integer between 0 and 15 APS ID of FromAID terminating node for BLSR systems

TOAEND An integer between 0 and 15 APS ID of ToAID originating node for BLSR systems

TOZEND An integer between 0 and 15 APS ID of ToAID terminating node for BLSR systems






ENT-EC1The Enter EC-1 command provisions and enters the attributes of an EC-1 facility in a network element.


Input syntaxENT-EC1:[TID]:AID:CTAG:::[LBO=Domain]:[PST],[SST];


Field Purpose


AID Access identifier. EC-1 facility to act on.


LBO Line buildout

PST Primary state

SST Secondary state



EC1 AID EC1-slot#-port#EC1-slot#-ALL

Identify the EC-1 facility whereslot# = 3, 5, 7, or 9 port # = 1 to 3 for EC-1x3port # = 1 to 12 for EC-1x12



Example inputSet the EC-1 facilities on all ports in slot 9 to a line buildout of 0 to 224 feet, a primary state of in-service, and a secondary state of auto in-service: ENT-EC1:SEATTLE:EC1-9-ALL:CTAG12:::LBO=1:IS,AINS;



LBO 1 0 to 224 ft to EC-1 cross-connect (default)

2 225 to 450 ft to EC-1 cross-connect

PST IS In service (default)

OOS-MA Out of service maintenance for provisioning memory administration

SST(see Note)

AINS Auto in-service

AINS-DEA Auto in-service deactivated

TS Test

TS-DEA Test Deactivated

Note: AINS is not supported on EC-1 facilities and equipment.



ENT-EQPTThe Enter Equipment command is used to enter the attributes of a given type of common equipment module or slot definition in a network element. This tells the network element that a specific circuit pack of a particular type is supposed to be in a particular slot.

If the system does a self test and finds a circuit pack in a slot that does not match the description provisioned, an alarm is raised.

On a shelf, if this command is used to add OC-3x4, OC-12, or OC-12x4 STS equipment, it also adds the corresponding section data communications channel (SDCC) link (layers 1, 2). The SDCC protection scheme is based on the OC-3x4, OC-12, or OC-12x4 STS equipment protection scheme (Simplex instead of 1+1 protected).

Security level Level 3

Input syntaxENT-EQPT:[TID]:AID:CTAG::::[PST];


Field Purpose


AID Access identifier. Equipment to act on.


PST Primary state



Purpose

DS1 AID DS1-slot# Identify the DS1 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 equipmentwhere slot# = 3 to 10



Purpose



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



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



PST IS In-service (default)

OOS-MA Out-Of-Service maintenance for provisioning Memory Administration

Note: Secondary state cannot be provisioned.



Purpose



Example inputProvision a DS1 circuit pack in slot 4:

ENT-EQPT:NEWYORK:DS1-4:CTAG12::::IS;

Provision a DS3 circuit pack in slot 6: ENT-EQPT:SEATTLE:DS3-6:CTAG23;



ENT-ETHUse the Enter Ethernet command to provision an Ethernet facility.

Note 1: The WAN facility of a circuit pack is created automatically when its corresponding ETH facility is created.

Note 2: 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]:[PST-Q];

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]:[PST-Q];

Input syntax for the 4x100FX-P2PED-ETH:[tid]:aid:ctag:::[,PASSCTRL=Domain][,PAUSETX=Domain][,MTU=Domain][,TXCON=Domain]:[PST-Q];

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]:[PST-Q];


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

PST-Q Primary state qualifier



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 inputProvision ETH port 1 of the 2x100BT-P2P circuit pack in slot 7 of network element OTTAWA as follows:

• Set the duplex mode to FULL

• Set the speed to 100 Mbit/s

• Discard pause frames

• Set the primary state in-service

ENT-ETH:OTTAWA:ETH-7-1:CTAG01:::ETHDPX=FULL,SPEED=100,PASSCTRL=DISABLE:IS;

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)

PST-Q IS (default) Set the state of the facility to in-service (IS) or out-of-service management (OOS-MA).

OOS-MA





ENT-FACThe Enter Facility command is used to provision an NP facility. NP facilities include ILANSP, ILANNP, ILAN1, ILAN2, COLAN, and X25. ILANSP and ILANNP cannot be manually provisioned.


Input syntaxENT-FAC:[TID]:AID:CTAG;

Example inputProvision the ILAN-2 facility:

ENT-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, enter each facility individually.



ENT-FCUse the Enter Fibre Channel command to provision a Fibre Channel facility (FC port) of a 2xGigE/FC-P2P or 2xGigE/FC-P2P-C circuit pack.

Note: The WAN facility on the GE/FC SFP of a 2xGigE/FC-P2P or 2xGigE/FC-P2P-C circuit pack is created automatically when its corresponding FC facility is created.


Input syntaxENT-FC:<tid>:<aid>:<ctag>:::[,SUBRATE=Domain][,EXTREACH=Domain][,SERVICE=Domain][,BBCOVERRIDE=Domain][,COMPRESSION=Domain][PST-Q=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 to the 2xGigE/FC-P2P-C only.

PST-Q Primary state qualifier



FC AID FC-slot#-port#FC-slot#-ALL

Identify the Fibre Channel facility where slot# = 3 to 10port# = 1 or 2



Example inputProvision FC port 1 of the 2xGigE/FC-P2P circuit pack in slot 7 of network element OTTAWA as follows:

• the subrate is disabled

• the extended reach is disabled

• the service mode is set to FC100

• the BBC override is set to 0

ENT-FC:OTTAWA:ETH-7-1:CTAG01:::SUBRATE=DISABLE,EXTREACH=DISABLE;SERVICE=FC100,BBCOVERRIDE=0;



SUBRATE ENABLE Enable or disable the ability of the service to be carried over sub-rate bandwidth.

DISABLE (default)

EXTREACH ENABLE Enable or disable the extended reach mode of operation.

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.

PST-Q IS (default) Set the state of the facility to in-service (IS) or out-of-service management (OOS-MA).OOS-MA

COMPRESSION ENABLE Enable or disable the compression mode of operation. Applicable only for the 2xGigE/FC-P2P-C.DISABLE (default)



ENT-FFP-OC12The Enter FFP OC-12 command is used to set up 1+1 linear protection for OC-12 interfaces. The command also affects the operation of the SDCC in different ways depending on the current number of SDCC links configured on the pair of OC-12 interfaces targeted by this command. If two SDCC links are provisioned before 1+1 protection is set up, make sure the SDCC layer 2 parameters are the same for both links. If the parameters are not the same, the ENT-FFP-OC12 command will not complete.

Note 1: If the craftperson attempts to modify optical protection through an FFP command, the command will be denied if the shelf has an active test access session.

Note 2: You cannot execute this command if there is an active test access session on this facility.


Input syntaxENT-FFP-OC12:[TID]:workingOC12AID,protectionOC12AID:CTAG:::[PSDIRN=Domain];


Field Purpose


AID Access identifier. OC-12 to act on.


PSDIRN Direction of protection group for OC-12 lines.



Example inputProvision unidirectional 1+1 protection for the pair of OC-12 circuit packs in slot 9 port 1 and slot 10 port 1:ENT-FFP-OC12:NEWYORK:OC12-9-1,OC12-10-1:CTAG12:::PSDIRN=UNI;



Purpose

working OC12 AID

OC12-slot#-port# Identify the slot number of the working OC-12 facility where slot# = 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

protection OC12 AID

OC12-slot#-port# Identify the slot number of the protection OC-12 facility where slot# = 4, 6, 8, 10, or 12 for OC-12slot# = 4, 6, 8, or 10 for OC-12x4 STSport# = 1 for OC-12slot# = 1 to 4 for OC-12x4 STS



PSDIRN UNI

BI

Unidirectional (default)

Bidirectional



ENT-FFP-OC192The Enter FFP OC-192 command is used to set up protection for OC-192 interfaces. The command also affects the operation of the SDCC in different ways depending on the current number of SDCC links configured on the pair of OC-192 interfaces targeted by this command. If two SDCC links are provisioned before 1+1 protection is set up, make sure the SDCC layer 2 parameters are the same for both links. If the parameters are not the same, the ENT-FFP-OC192 command will not complete.

Note 1: Ensure that facilities on the protection circuit pack are out of service.



Input syntaxENT-FFP-OC192:[TID]:workingOC192AID,protectionOC192AID:CTAG:::[PSDIRN=Domain][,PS=Domain][,WR=Domain];


Field Purpose


workingOC192AID Working side access identifier. OC-192 to act on

protectionOC192AID Protection side access identifier


PSDIRN Protection switch direction for 1+1 linear systems

PS Protection scheme

WR Wait-to-restore period for BLSR systems



Purpose

workingOC192 AID OC192-slot# Identifies the slot number of the working OC-192 where slot# = 11

protectionOC192 AID

OC192-slot# Identifies the slot number of the protection OC-192 where slot# = 12



Example inputProvision unidirectional 1+1 protection for the pair of OC-192 circuit packs in slots 11 and 12:

ENT-FFP-OC192:NEWYORK:OC192-11,OC192-12:CTAG12:::PSDIRN=UNI;

Example inputEnter a BLSR protection for the pair of OC-192 circuit packs in slots 11 and 12 and set a wait to restore value of 1 minute:

ENT-FFP-OC192:NEWYORK:OC19211,OC192-12:CTAG12:::PS=BLSR_2FR,WR=1-MIN;



PSDIRN UNI

BI


Bidirectional

PS 1PLUS1 1+1 protection (default)

BLSR_2FR 2-Fiber BLSR protection

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.



ENT-FFP-OC3The Enter FFP OC-3 command is used to set up 1+1 linear protection for OC-3 interfaces. The command also affects the operation of the SDCC in different ways depending on the current number of SDCC links configured on the pair of OC-3 interfaces targeted by this command. If two SDCC links are provisioned before 1+1 protection is set up, make sure the SDCC layer 2 parameters are the same for both links. If the parameters are not the same, the ENT-FFP-OC3 command will not complete.

Note 1: If the craftsperson attempts to modify optical protection through an FFP command, the command will be denied if the shelf has an active test access session.



Input syntaxENT-FFP-OC3:[TID]:workingOC3AID,protectionOC3AID:CTAG:::[PSDIRN=Domain];


Field Purpose




PSDIRN Direction of protection group for OC-3 lines.



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 whereslot# = 4, 6, 8, 10port# = 1 for OC-3port# = 1 to 4 for OC-3x4



Example inputProvision unidirectional 1+1 protection for the pair of OC-3 circuit packs in slot 9 port 1 and slot 10 port 1:

ENT-FFP-OC3:NEWYORK:OC3-9-1,OC3-10-1:CTAG12:::PSDIRN=UNI;



PSDIRN UNI

BI


Bidirectional



ENT-FFP-OC48The Enter FFP OC-48 command is used to set up protection for OC-48 interfaces. The command also affects the operation of the SDCC in different ways depending on the current number of SDCC links configured on the pair of OC-48 interfaces targeted by this command. If two SDCC links are provisioned before 1+1 protection is set up, make sure the SDCC layer 2 parameters are the same for both links. If the parameters are not the same, the ENT-FFP-OC48 command will not complete.

Note 1: Ensure that facilities on the protection circuit pack are out of service.



Input syntaxENT-FFP-OC48:[TID]:workingOC48AID,protectionOC48AID:CTAG:::[PSDIRN=Domain][,PS=Domain][,WR=Domain];


Field Purpose


workingOC48AID Working side access identifier. OC-48 to act on

protectionOC48AID Protection side access identifier


PSDIRN Protection switch direction for 1+1 linear systems

PS Protection scheme

WR Wait-to-restore period for BLSR systems



Example inputProvision unidirectional 1+1 protection for the pair of OC-48 circuit packs in slots 11 and 12:ENT-FFP-OC48:NEWYORK:OC48-11,OC48-12:CTAG12:::PSDIRN=UNI;

Enter a BLSR protection for the pair of OC-48 circuit packs in slots 11 and 12 and set a wait to restore value of 1 minute:ENT-FFP-OC48:NEWYORK:OC48-11,OC48-12:CTAG12:::PS=BLSR_2FR,WR=1-MIN;



Purpose

workingOC48 AID OC48-slot# Identifies the slot number of the working OC-48 facility where slot# = 11 for OC-48slot# = 3, 5, 7, 9, or 11 for OC-48 STS

protectionOC48 AID OC48-slot# Identifies the slot number of the protection OC-48 facility where slot# = 12 for OC-48slot# = 4, 6, 8, 10, or 12 for OC-48 STS



PSDIRN UNI

BI


Bidirectional

PS 1PLUS1 1+1 protection (default)

BLSR_2FR 2-Fiber BLSR protection

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.



ENT-GREThe Enter GRE command is used to create a GRE tunnel.

This command is supported on the network processor only.

The command can be used to create multiple GRE tunnels with unique IP and NSAP addresses. The maximum number of GRE tunnels supported is 26.

GRE-0 is reserved for a connection to a head-end system (where the NPx is not the head-end). When GRE-0 is active, the COLAN is OOS-GRE and the GRE-0 acquires the COLAN’s ED-IP settings, namely: IPADDR, NETMASK, and GATEWAY. When using GRE-0, the ED-IP parameters must be set as if the NPx were directly connected to the head-end LAN.


Input syntaxENT-GRE:[TID]:AID:CTAG::[IPADDR]:[Netmask=<netmask>]:DEST=<nsap>;


Field Purpose


AID GRE-0 to GRE-26


IPADDR n.n.n.n (the IP address of the network element at the far-end of the GRE tunnel)

Note: For GRE-0 an IP of 0.0.0.0 must be entered.



Example inputCreate the GRE tunnel:ENT-GRE:OC3NP:GRE-7:CTAG24::10.1.1.207:NETMASK=255.255.255.252:DEST=490000000075D0082E00;

Netmask The netmask along with the IPADDR determines the range and number of IP addresses which are forwarded to the tunnel.

255.255.255.192 - 64 IP addresses255.255.255.224 - 32 IP addresses255.255.255.240 - 16 IP addresses255.255.255.248 - 8IP addresses255.255.255.252 - 4 IP addresses255.255.255.254 - 2 IP addresses255.255.255.255 - (Default) 1 IP address

Note 1: For GRE-0, the default netmask (255.255.255.255) must be entered.

Note 2: The sum of IP addresses for GRE-1 to GRE-26 must be less than or equal to 64.

DEST OSI NSAP address of the destination NE (includes an NSEL of “00”)

DEST must be a hexadecimal number with a maximum of 40 digits.

Note 1: GRE tunnels can only be created if the COLAN is IS or OOS-GRE, and if valid IP settings have been entered through the ED-IP command.

Note 2: The IP/Netmask range for each tunnel must be unique and non-overlapping.

Note 3: Multiple GRE tunnels can have the same DEST nsap.

Note 4: When the NPx is a head-end, the NPx will proxy ARPs for all IP addresses within active GRE tunnels (GRE-1 to GRE-26).

Note 5: When the NPx is a head-end, the user must not define a GRE tunnel for an IP address which is resident on the head-end NPx COLAN.


Field Purpose



ENT-IPTUse the Enter IPT command to attach a Packet Edge circuit pack to a Resilient Packet Ring (RPR).

Note 1: A Packet Edge circuit pack cannot be attached to an RPR until SONET bandwidth on both ends of the ring have been assigned.

Note 2: A Packet Edge circuit pack can be attached to only one RPR.

Note 3: 4x100BT, 4x100FX, and 2xGigE circuit packs can only be attached to RPRs with virtual concatenation (VCAT) disabled. 2xGigE 2.5G circuit packs can only be attached to RPRs with VCAT enabled. VCAT is disabled by default. See ENT-IPTR to set the VCAT mode.


Input syntaxENT-IPT:[TID]:IPTAID,IPTRAID:CTAG;

Example inputAttach a 4x100BT circuit pack to an RPR:ENT-IPT:OC3SP:IPT100-7,IPTR-2: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 the double slot circuit packs slot# = 3 to 10 for the single slot circuit packs

1GE25G-slot# Detach a 2xGigE 2.5G circuit pack where slot# = 3, 5, 7, 9

IPTR AID IPTR-Index# RPR entity to act upon where Index# = 1 to 8



ENT-IPTRUse the Enter IPTR command to create a Resilient Packet Ring (RPR).


Input syntaxENT-IPTR:[TID]:AID:CTAG:::[VCAT];

Example inputCreate a Resilient Packet Ring for network element MONTREAL:

ENT-IPTR:MONTREAL:IPTR-2:123;


Field Purpose


AID Access identifier


VCAT Virtual concatenation status



IPTR AID IPTR-Index# RPR entity to create where Index# = 1 to 8



VCAT ENABLE Enable or disable virtual concatenation on the RPR.

DISABLE (default)



ENT-LLSDCCThe Enter Lower Layer SDCC command is used to add a section data communications channel (SDCC) link (layers 1 and 2) to the indicated AID (equipment slot). The request is validated based on SDCCs already configured on the pair of slots (the number of SDCCs and the current SDCC protection scheme) and the circuit pack now provisioned in that slot or pair of slots.

Upon SDCC provisioning, parameters are the default values. To change the provisioning defaults, see ED-LLSDCC on page 2-243.

Note: The SDCC link on the DS1 DSM OC-3 facility has the provisioning default parameter, L2SIDE=USER.


Input syntaxENT-LLSDCC:[TID]:AID:CTAG;


Field Purpose


AID Access identifier. The equipment to retrieve SDCC information from.



AID type

Command-specific values

Purpose

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-12, 3 to 10 for OC-12x4 STSport# = 1 for OC-12, 1 to 4 for OC-12x4 STS

OC-48 AID

OC48-slot# Identify the OC-48 whereslot# = 11 or 12 for OC-48, 3 to 12 for OC-48 STS



Example inputAdd a lower layer SDCC link on the OC-3x4 circuit pack in slot 7, port 1:

ENT-LLSDCC:NEWYORK:OC3-7-1:CTAG13;

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


AID type


Purpose



ENT-OC12The Enter OC-12 command provisions and enters the attributes of an OC-12 facility in a network element.


Input syntaxENT-OC12:[TID]:AID:CTAG:::[SDTH=Domain][,STFORMAT=Domain][,STRC=Domain][,EXPSTRC=Domain][,STFMODE=Domain][,SSBITMDE=Domain]:[PST],[SST];


Field Purpose




SDTH Signal degrade threshold. 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.

PST Primary state. See Parameter descriptions table for details.

SST Secondary state. See Parameter descriptions table for details.



Purpose

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

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



Example inputSet the primary state of the OC-12 facility in slot 7 port 1 to in-service, with a section trace format value of STRING, an outgoing section trace value of Abc123, and SSBITMDE set to SONET:

ENT-OC12:SEATTLE:OC12-7-1:CTAG12:::STFORMAT=STRING,STRC=”Abc123”,SSBITMDE=SONET:IS;



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)



STFMODE OFF Alarms off, no traffic protection (default)

ALMONLY Alarms on, no traffic protection

SSBITMDE SONET SS bits operate in SONET mode (default)

SDH SS bits operate in SDH mode

PST(see Note 2)

IS In service (default)


SST AINS Auto in-service


TS Test. See Note 2.


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: Test access secondary state is supported in slots 3 through 10 only.







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.





Purpose

OC192 AID OC192-slot# Identify the OC-192 facility where slot# = 11, 12




Parameter Possible values

Description


STFORMAT NUM An integer 1 byte long (default)

STRING An ASCII string up to 15 bytes long









LINEFAIL Alarms on, traffic protection

SSBITMDE SONET Optical signal transmitted is SONET format (default)

SDH Optical signal transmitted is SDH format

PST(see Note 2)


OOS-MA Out of service - memory administration



Example inputSet the primary state of the OC-192 facility in slot 11 to an in-service state with a section trace format value of STRING and an outgoing section trace value of Abc123 and the SSBITMDE to SONET:

ENT-OC192:SEATTLE:OC192-11:CTAG12:::STFORMAT=STRING,STRC=”Abc123”,SSBITMDE=SONET:IS;









Description




Note: This command is not supported for Host prov-link OC-3 facility, and DSM TM OC-3 line facility.


Input syntaxENT-OC3:[TID]:AID:CTAG:::[SDTH=Domain][,STFORMAT=Domain][,STRC=Domain][,EXPSTRC=Domain][,STFMODE=Domain][,SSBITMDE=Domain][,REMOTE=Domain]:[PST],[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.







Purpose

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

Identify the OC-3 where slot# = 3 to 10port# = 1 for OC-3port# = 1 to 4 for OC-3x4




STFORMAT NUM Section trace message is 1 byte long (default)

STRING Section trace message is up to 15 bytes long



If STFORMAT is STRING (default is null character string). See Note.



If STFORMAT is STRING (default is null character string). See Note.





REMOTE EXPRESS Optical Metro node (default)

OC48 OC-48 node

PST(see Note 2)





Example inputSet the primary state of the OC-3 facility in slot 10 port 1 to an in-service state with a section trace format value of STRING and an outgoing section trace value of Abc123 and the SSBITMDE to SONET:

ENT-OC3:SEATTLE:OC3-10-1:CTAG12:::STFORMAT=STRING,STRC=”Abc123”,SSBITMDE=SONET:IS;



TS Test


Note: 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.









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.





Purpose

OC48 AID OC48-slot# Identify the OC-48 facility where slot# = 11, 12 for OC-48slot# = 3 to 12 for OC-48 STS



Example inputSet the primary state of the OC-48 facility in slot 11 to an in-service state with a section trace format value of STRING and an outgoing section trace value of Abc123 and the SSBITMDE to SONET:

ENT-OC48:SEATTLE:OC48-11:CTAG12:::STFORMAT=STRING,STRC=”Abc123”,SSBITMDE=SONET:IS;



Description


STFORMAT NUM An integer 1 byte long (default)

STRING An ASCII string up to 15 bytes long









LINEFAIL Alarms on, traffic protection



PST(see Note 2)


OOS-MA Out of service - memory administration









ENT-RINGMAPUse the Enter Ring Map command to enter map information for a managed or unmanaged node in a BLSR ring. This command is supported on the network processor.


Input syntaxENT-RINGMAP:[TID]:AID:CTAG::SID,APSID,WEST-AID,EAST-AID,WEST-APSID,EAST-APSID;


Field Purpose


AID Ring name


SID Node name

APSID APS ID of the node

WEST West optics slot number

EAST East optics slot number

WEST-APSID APS ID of the west adjacent node

EAST-APSID APS ID of the east adjacent node



Ring name Alphanumeric string between 1 and 20 characters.

Identify ring name



Example inputEnter the ring map information for NPFGXOTT:

ENT-RINGMAP:NPFGXOTT:OTTAWA_RING:CTAG::SPFGXOTT,1,OC48-11,OC48-12,2,3;



SID An alphanumeric string between 1 and 20 characters

Node name

APSID An integer between 0 and 15 APS ID of the node

WEST OCn-slot#where n is 48 or 192where slot# = 11 or 12

Slot number of the node’s west optics

EAST OCn-slot#where n is 48 or 192where slot# = 11 or 12

Slot number of the node’s east optics

WEST-APSID An integer between 0 and 15 APS ID of the west adjacent node

EAST-APSID An integer between 0 and 15 APS ID of the east adjacent node



ENT-ROLL-STS1The Enter Rollover STS-1 command is used to define a new connection to which to rollover an existing termination point in an STS-1 path.

If you try to execute an inservice rollover command on a 1WAYPR multicast cross-connect, you get the message “Status, data not consistent”. To rollover a 1WAYPR multicast cross-connect, you must

• convert each 1WAYPR multicast cross-connect to a 1WAY cross-connect with the ED-CRS command

• rollover the endpoint of each 1WAY cross-connect

• convert each 1WAY cross-connect back to a 1WAYPR cross-connect with the ED-CRS command

Note: Rollovers must be performed one connection at a time. Bulk rollovers are not supported.


Input syntaxENT-ROLL-STS1:[TID]:fromAID,toAID:CTAG::CCT:RFROM=Domain,RTO=Domain[,VALID=Domain][,SWMATE=AID];


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)

VALID Command execution will be denied if the conditions on the node are inappropriate

SWMATE Used to bridge the switch mate in a 1WAYPR, 2WAYPR, or 2WAYBR circuit

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





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

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

Identify the DSM or MS DSM facility on a DS3 circuit pack whereslot# = 3, 5port# = 1 to 6Hline = OC3 or OC12hslot# = 3 to 10hport# = 1 to 4

OC3-slot#-port#-sts# Identify the STS-1 facility on an OC-3 circuit pack whereslot# = 3 to 10 port# = 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




STS1facility AID

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


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




2WAY Bidirectional connection

1WAYPR 1WAY path ring, fromAID must be optical


2WAYBR 2WAY bridge ring, fromAID must be optical

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.



Purpose



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

Bridge the original working OC-3 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;

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-,RTO=OC3-9-3-1;

Bridge the original switch mate OC-3 connection:

ENT-ROLL-STS1:OTTAWA:OC3-9-2-1,DS3-3-1:E::2WAYPR:RFROM=OC3-9-2-1,RTO=OC3-9-2-1,VALID=Y,SWMATE=OC3-10-2-1;

Switch to the bridge connection:ED-ROLL-STS1:OTTAWA:OC3-9-2-1,DS3-3-1:F::2WAYPR:RFROM=OC3-9-2-1,RTO=OC3-9-2-1,VALID=Y,EDSWMATE=Y:SWITCHED;

Remove the original switch mate OC-3 connection:CMMT-ROLL-STS1:OTTAWA:OC3-9-2-1,DS3-3-1:G::2WAYPR:RFROM=OC3-9-2-1,RTO=OC3-9-2-1,CMMTSWMATE=Y;



ENT-ROLL-STS12C The Enter Rollover STS12C command is used to define a new connection to which to rollover an existing termination point in a STS-12c path.






Input syntaxENT-ROLL-STS12C:[TID]:fromAID,toAID:CTAG::CCT:RFROM=Domain,RTO=Domain[,VALID=Domain][,SWMATE=AID];


Field Purpose















STS12Cfacility AID

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

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/FC-P2P-C or the 2xGigE-P2P where slot# = 3 to 10, port# = 1 or 2, sts# = 1

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












Example inputRollover an STS12C connection and its switch mate on the OC-12 circuit pack in a 2WAYPR circuit between an OC-12 service and the OC-12 circuit pack.

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


ED-ROLL-STS12C:OTTAWA:OC12-9-1-1,OC12-8-1-1:B::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:C::2WAYPR:RFROM=OC12-9-1-1,RTO=OC12-7-1-1;


ENT-ROLL-STS12C:OTTAWA:OC12-9-1-1,OC12-10-1-1:D::2WAYPR:RFROM=OC12-9-1-1,RTO=OC12-7-1-1,VALID=Y,SWMATE=OC12-6-1-1;

Switch to the bridge connection:ED-ROLL-STS12C:OTTAWA:OC12-9-1-1,OC12-8-1-1:E::2WAYPR:RFROM=OC12-9-1-1,RTO=OC12-9-1-1,VALID=Y,EDSWMATE=Y:SWITCHED;

Remove the original switch mate connection:CMMT-ROLL-STS12C:OTTAWA:OC12-9-1-1,OC12-8-1-1:F::2WAYPR:RFROM=OC12-9-1-1,RTO=OC12-9-1-1,CMMTSWMATE=Y;











Field Purpose















STS24Cfacility AID

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

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

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












Example inputRollover an STS24C connection and its switch mate 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.


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




ENT-ROLL-STS24C:OTTAWA:OC48-9-1-1,OC48-10-1-1:D::2WAYPR:RFROM=OC48-9-1-1,RTO=OC48-7-1-1,VALID=Y,SWMATE=OC48-6-1;


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












Field Purpose















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-3, 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-12, 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-48, 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





MS DSM WAN AID

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

Identify the STS-3c facility on the WAN port whereslot# = 3 to 6port# = 1 to 8sts# = 1Hline# = OC3 or OC12hslot# = 3 to 10hport# = 1 to 4













Purpose



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



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;




ENT-ROLL-STS3C:OTTAWA:OC3-9-1-1,OC3-10-1-1:D::2WAYPR:RFROM=OC3-9-1-1,RTO=OC3-7-1-1,VALID=Y,SWMATE=OC3-6-1-1;

Switch to the bridge connection:ED-ROLL-STS3C:OTTAWA:OC3-9-1-1,OC3-8-1-1:E::2WAYPR:RFROM=OC3-9-1-1,RTO=OC3-9-1-1,VALID=Y,EDSWMATE=Y:SWITCHED;












Field Purpose















STS48Cfacility 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












Example inputRollover an STS48C connection and its switch mate 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.


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




ENT-ROLL-STS48C:OTTAWA:OC48-9-1-1,OC48-10-1-1:D::2WAYPR:RFROM=OC48-9-1-1,RTO=OC48-7-1-1,VALID=Y,SWMATE=OC48-6-1;


ED-ROLL-STS48C:OTTAWA:OC48-9-1-1,OC48-8-1-1:E::2WAYPR:RFROM=OC48-9-1-1,RTO=OC48-9-1-1,VALID=Y,EDSWMATE=Y:SWITCHED;




ENT-ROLL-VT1 The Enter Rollover VT1 command is used to define a new connection to which to rollover an existing termination point in a VT1.5 path.





Note: Rollovers must be performed one connection at a time. Bulk rollovers are not supported.


Input syntaxENT-ROLL-VT1:[TID]:fromAID,toAID:CTAG::CCT:RFROM=Domain,RTO=Domain[,VALID=Domain][,SWMATE=AID];


Field Purpose




CTAG Correlation tag, a user created alphanumeric identifier to correlate the command and response messages











VT1.5facility AID

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

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


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

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

DS1 service module facility whereport# = 1 to 84hslot# = 3 to 10hport# = 1 to 4

DS1-1-DFLT-grp#-%HLINK-OC3-hslot#-hport#

DS1 service module facility wheregrp# = 1 to 3hslot# = 3 to 10hport# = 1 to 4

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

MS DSM facility whereport# = 1 to 84Hline = OC3 or OC12hslot# = 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



VT1.5facility AID

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 and its switch mate 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-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;


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;

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

Switch to the bridge connection:ED-ROLL-VT1:OTTAWA:OC3-9-2-1-7-1,DS1-4-4:F::2WAYPR:RFROM=OC3-9-2-1-7-1,RTO=OC3-9-2-1-7-1,VALID=Y,EDSWMATE=Y:SWITCHED;

Remove the original switch mate OC-3 connection:CMMT-ROLL-VT1:OTTAWA:OC3-9-2-1-7-1,DS1-4-4:G::2WAYPR:RFROM=OC3-9-2-1-7-1,RTO=OC3-9-2-1-7-1,CMMTSWMATE=Y;



ENT-SECU-ACCESSThe Enter Security Access command is used to add network elements to the allow or deny access control list of the specified network element or network processor.


Input syntaxENT-SECU-ACCESS:[TID]::CTAG::SID,[ACCESS];

Example inputAdd network element OTTAWA to the allow list of network element MONTREAL:ENT-SECU-ACCESS:MONTREAL::CTAG1::OTTAWA,ALLOW;


Field Purpose



SID Source identifier of the network element to add. Grouping is allowed.

ACCESS Add network elements to the allow list or to the deny list



ACCESS ALLOW Add network elements to the allow list

DENY (default) Add network elements to the deny list



ENT-SECU-BADPIDThe Enter Security Bad Password command is used to add words to a list of unusable passwords on the network element or network processor. You can add up to 50 words to the list. If you try to add more than 50, an error code is returned. Duplicate words are not added.

Words to add to a list of unusable passwords might be locally used names and acronyms.


Input syntaxENT-SECU-BADPID:[TID]::CTAG::BADPID[&BADPID2]..[&BADPID3];

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

Note 2: The length of the command, including the syntax, cannot exceed 234 characters. If you require more characters to enter all the unusable passwords, issue the command again.

Example inputAdd the words NORTEL951 and EXPRESS951 to the list of unusable passwords on network element OTTAWA:ENT-SECU-BADPID:OTTAWA::CTAG98::NORTEL951&EXPRESS951;


Field Purpose



BADPID Word to add to the list of unusable passwords. A string between eight and ten alphanumeric characters.

Grouping is allowed.



ENT-SECU-USERThe Enter Security User command is used to create a new user account on a network element or network processor and enter the security parameters associated with the account. The network element or network processor is specified by the TID.

Note: Password identifiers (PIDs) must meet the guidelines listed under ED-SECU-PID on page 2-314.

A maximum of 100 UIDs can be added to the password file. If you try to create UID 101, the error message /*Status, List Exceeds Maximum*/ is displayed.


Input syntaxENT-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];

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


NEWUID User identifier


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

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 inputCreate an account on network element Seattle, with user name CAM, password VWXYZ123, security privilege level 3, and timeout disabled: ENT-SECU-USER:SEATTLE:CAM:CTAG12::VWXYZ123,VWXYZ123,3:TMOUTA=N;

Create an account on network element Seattle, with user name CAM, password VWXYZ123, security privilege level 3, timeout set to 60 minutes, an aging time of 30 days, an accreditation period of 20 days, and an early warning time of 7 days: ENT-SECU-USER:SEATTLE:CAM:CTAG12::VWXYZ123,VWXYZ123,3:TMOUTA=Y,TMOUT=60,PAGESTAT=ON,PAGE=30,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.





ENT-T1The Enter T1 command is used to enter the attributes of a DS1 facility in a network element.

To modify DS1 facilities once they have been created, use the ED-T1 command.


Input syntaxENT-T1:[TID]:AID:CTAG:::[EQLZ=Domain][,FENDNTE=Domain][,FLMDE=Domain][,FMT=Domain][,LINECDE=Domain][,MAP=Domain][,OMODE=Domain]][,NIU=Domain]:[PST],[SST],[AINS-TIME];


Field Purpose


AID Access identifier. DS1s to act on.


EQLZ=DomainFENDNTE=DomainFLMDE=DomainFMT=DomainLINECDE=DomainMAP=DomainOMODE=DomainNIU=Domain

Facility signal attribute parameters. See the Parameter descriptions table on page 3-104.

PST Primary state

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

DS3 AID DS3-slot#-port#-t1#DS3-slot#-port#-ALL

Identify the DS3s 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



EQLZ Cable connecting T1 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-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 transmit 220 to 430 ft receive

33TX3RX

long: 430 to 655 ft both directions 430 to 655 ft transmit 430 to 655 ft receive

FENDNTE ANSI

NOTANSI

Default: Far end NTE supports ANSI standards

ANSI standards are not supported



FLMDE

BOTH

INC

OC

N

Fault locate mode: Faults in the frame format that 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.

AMIAMITXAMIRX

Default: Alternate mark inversion (“bipolar”) both directionsAMI transmit AMI receive

AMIZCS

AMIZCSTX

AMI with zero code suppression, both directions If there are 8 zeros in a byte, the least significant will be changed to a one.AMIZCS transmit

Note: Zero code suppression is not supported in the receive direction.

B8ZS B8ZSTXB8ZSRX

Bipolar with 8-zero substitution, both directions B8ZS Transmit B8ZS Receive





MAP

VTASYN

VTBYTE

VTBIT

SIGNLIN

SIGNLOUT

The form of mapping for DS1 payloads into VT1.5s.

Default:VT1.5 bit asynchronous mapping

VT1.5 byte synchronous mapping

VT1.5 bit synchronous mapping

Note: Only VTBYTE and VTASYN mappings are supported by T1 facilities on MS DSM.

If using VTBYTE mapping, one or both of these mappings can also be specified:

Robbed bit signaling bits are transported.

Out slot (S1-S4) signaling bits are transported.

Note 1: You must enter each MAP parameter in a separate command.

Note 2: DS1 facilities on the DSM and MS DSM do not support SIGNLIN and SIGNLOUT.

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.

NIU N

Y

DS1 facility does not support NIU feature (default).

DS1 facility does support NIU feature.

PST (primary state)

IS

OOS-MA

In service (default)

Out of service maintenance



TS Test

TS-DEA Test Deactivate





Example input Provision the DS1 facility on the DS1 circuit pack in slot 4 port 7 and set its TX EQLZ value:

ENT-T1:NEWYORK:DS1-4-7:CTAG23:::EQLZ=2TX;

Provision all the DS1 facilities on the DS1 circuit pack in slot 6 and set their LINECDE values to use B8ZS:

ENT-T1:NEWYORK:DS1-6-ALL:CTAG23:::LINECDE=B8ZS;

Provision the DS1 facility on the DS1 circuit pack in slot 4 port 7, overruling the defaults for EQLZ (it is a long cable, not a short one) and FMT (the framing is extended superframe):

ENT-T1:NEWYORK:DS1-4-7:CTAG23:::EQLZ=3,FMT=ESF;

Provision all the DS1 facilities on the DS1 circuit pack in slot 6 and set their MAP values to use VTBYTE:

ENT-T1:SEATTLE:DS1-6-ALL:CTAG23:::MAP=VTBYTE;



ENT-T3The Enter T3 command is used to enter the attributes of a DS3 facility in a network element.

To modify DS3 facilities once they have been created, use the ED-T3 command.


Input syntaxENT-T3:[TID]:AID:CTAG:::[LBO=Domain][,NIU=Domain[,FMT=Domain]:[PST],[SST],[AINS-TIME];


Field Purpose




LBO Line buildout

NIU Network interface unit

FMT Frame format

PST Primary state

SST Secondary state

AINS-TIME DS1 auto-in-service time



T3 AID DS3-slot#-port#DS3-slot#-ALL

Identify the DS3s whereslot# =3, 5, 7, or 9port# = 1 to 3 for DS3x3port# = 1 to 12 for DS3x12, DS3x12e, or DS3VTx12

MS DSM DS3 Facility AID

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

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

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



Example input Provision a DS3 facility on the DS3 circuit pack in slot 5 port 1 with a line buildout of 225 ft and the frame format to unframed: ENT-T3:NEWYORK:DS3-5-1:CTAG23:::LBO=2,FMT=UNFR;



FMT ASYNC M13, multiplex framed (default)

UNFR Unframed clear channel

CBIT C-bit parity

NIU N

Y

DS3 facility does not support NIU feature (default)

DS3 facility does support NIU feature. DS3 cross-connects must be present to activate the feature.

LBO 1 (default) 0 to 224 ft to DS3 cross-connect

2 225 to 450 ft to DS3 cross-connect

PST IS In service (default)




TS Test

TS-DEA Test deactivated

AINS-TIME 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. Default = 04-00 (4 hours)

HH= 00-96 MM=00-59



EX-SW-OC12The Exercise Switch OC-12 command is used to run the exerciser to test the different protection mechanisms associated with OC-12 line switching.

The high-speed exerciser is a routine that tests the integrity of the protection switching bytes (K-bytes) communication between an OC-12 or OC-12x4 STS 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 an in-service state. 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 syntaxEX-SW-OC12:[TID]:AID:CTAG;


Field Purpose






OC-12 AID OC12-slot#-port# 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 the MS DSM OC-12 facility where slot# = 1 or 2Hslot# = 3 to 10Hport# = 1 to 4



Example inputRun the exerciser on network element OTTAWA and report results of all exercises:EX-SW-OC12:OTTAWA:OC12-9-1:CTAG23;

Response block syntax[AID]:<RSLT>

Possible values for <RSLT> are:

FAIL the exercise has determined unit failurePASS the exercise found no problem in the unit




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 or BLSR 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.



Input syntax422EX-SW-OC192:[TID]:AID:CTAG;


Field Purpose






OC-192 AID OC192-slot# Identify the OC-192 facility where slot# = 11



Example inputRun the exerciser on network element OTTAWA and report results of all exercises:EX-SW-OC192:OTTAWA:OC192-11:CTAG23;







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 it 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 an in-service state. 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






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

DS1 service module or MS DSM OC-3 Facility AID

OC3-slot-1-%HLINK-OC3-hslot-hport

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



Example inputRun the exerciser on network element OTTAWA and report results of all exercises:EX-SW-OC3:OTTAWA:OC3-10-2:CTAG23;







The high-speed exerciser is a routine that tests the integrity of the protection switching bytes (K-bytes) communication between an OC-48 or OC-48 STS pair configured in a linear 1+1 or BLSR 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-48 or OC-48 STS circuit packs or on all OC-48/OC-48 STS circuit packs in the shelf that are in an in-service state. 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.





Field Purpose






OC-48 AID OC48-slot# Identify the OC-48 facility where slot# = 11 for OC-48slot# = 3, 5, 7, 9, 11 for OC-48 STS



Example inputRun the exerciser on network element OTTAWA and report results of all exercises:EX-SW-OC48:OTTAWA:OC48-11:CTAG23;






INH-EX-OC12The Inhibit Exercise OC-12 command is used to prevent the exerciser from running to test the different protection mechanisms associated with OC-12 line switching.


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

Example inputPrevent the exerciser from running on network element SEATTLE:INH-EX-OC12:SEATTLE:OC12-ALL:CTAG23;


Field Purpose






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

Identify the OC-12 facility whereslot# = 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






Example inputPrevent the exerciser from running on network element SEATTLE:INH-EX-OC192:SEATTLE:OC192-11:CTAG23;


Field Purpose






OC-192 AID OC192-slot#OC192-ALL

Identify the OC-192 facility whereslot# = 11



INH-EX-OC3The INH-EX-OC3 command is used to prevent the exerciser from running to test the different protection mechanisms associated with OC-3 line switching.



Example inputPrevent the exerciser from running on network element SEATTLE:INH-EX-OC3:SEATTLE:OC3-ALL:CTAG23;


Field Purpose






OC-3 AID OC3-slot#- port#OC3-ALL

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

DS1 service module OC-3 Facility AID or MS DSM OC-3 Facility AID








Example inputPrevent the exerciser from running on network element SEATTLE:INH-EX-OC48:SEATTLE:OC48-11:CTAG23;


Field Purpose






OC-48 AID OC48-slot#OC48-ALL

Identify the OC-48 facility whereslot# = 11 for OC-48slot# = 3, 5, 7, 9, 11 for OC-48 STS



INH-MSG-ALLThe Inhibit Messages All command is used to stop all REPTÂLM, REPTÂLMÊNV, REPTÊVT and REPTÊX autonomous messages. It is meant to be used during maintenance to keep the terminal screen uncluttered.

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

To resume messages see ALW-MSG-ALL.

Note: The Inhibit Messages All command does not inhibit REPTÊVT^LOG and REPTÊVTÎNVENTORY autonomous messages. To inhibit these autonomous messages, use the INH-MSG-BROADCAST command.


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

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

Example inputTurn off all messages from the network element NEWYORK: INH-MSG-ALL:NEWYORK:ALL:CTAG12;


Field Purpose


ALL All data




INH-MSG-BROADCASTThe Inhibit Messages Broadcast command instructs the network element or network processor to inhibit REPT^DBCHG, REPTÊVT^LOG and REPTÊVTÎNVENTORY autonomous messages.

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

To resume messages see ALW-MSG-BROADCAST.


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


Example input Turn the autonomous display of REPTÊVT^LOG and REPTÊVTÎNVENTORY events to off for network element BOSTON: INH-MSG-BROADCAST:BOSTON::CTAG12;


Field Purpose





INH-UPGRDThe Inhibit Upgrade command is entered on a network element, with parameters specifying the slot for which you want to inhibit the upgrade.


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

Example input Inhibit slot 3 on network element Ottawa from being upgraded:

INH-UPGRD:OTTAWA:3:CTAG24;


Field Purpose


AID Slot number of the card to inhibit the upgrade




INIT-COLDThe Initialize Cold command instructs a network element to initialize its circuit packs. A cold initialization is equivalent to a power-up and can affect traffic. You can use the network processor as the target identifier to initialize the network processor.

The date and time must be reset on the network element and network processor after a system restart.


Input syntaxINIT-COLD:[TID]:AID:CTAG;

Example inputPerform a cold initialization of OC-3x4 in slot 10 only on network element WASHINGTON: INIT-COLD:WASHINGTON:OC3-10:CTAG13;

Reset the 4x100BT circuit pack in slot 7:INIT-COLD:OC3SP:IPT100-7:123;


Field Purpose


Note: You must use the network processor as the target identifier to initialize the NP.

AID Access identifier. The circuit pack to initialize. See Table 3-179.




INIT-OM-ETHUse the Initialize Operational Measurements Ethernet command to clear Ethernet operational measurements for an Ethernet facility of a 2x100BT-P2P, 8x100BT-P2P, 4x100FX-P2P, 8x100BT MS DSM, 2xGigE/FC-P2P, 2xGigE/FC-P2P-C, or 2xGigE-P2P circuit pack.

Note: Clearing Ethernet operational measurements for an Ethernet facility also clears the interface operational measurements for the facility.


Input syntaxINIT-OM-ETH:[TID]:AID:CTAG;

Example inputClear Ethernet operational measurements for the Ethernet facility in port 1 of the 2x100BT-P2P circuit pack in slot 7 of network element OTTAWA:

INIT-OM-ETH:OTTAWA:ETH-7-1:CTAG01;


Field Purpose


AID Access identifier. The facility to clear.



ETH AID ETH-slot#-port#ETH-slot#-ALLETH-ALL

Identify the Ethernet facility where slot# = 3 to 10port# = 1 or 2 for 2x100BT-P2P, 2xGigE/FC-P2P, 2xGigE/FC-P2P-C or 2xGigE-P2Pport# = 1 to 4 for 4x100FX-P2Pport# = 1 to 8 for 8x100BT-P2P


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

Identify the Ethernet facility on the MS DSM whereslot# = 3 to 6; port# = 1 to 8Hline = OC3 or OC12Hslot = 3 to10Hport = 1 to 4



INIT-OM-IFUse the Initialize Operational Measurements Interface command to clear

• Interface operational measurements for an Ethernet or WAN facility on a 2x100BT-P2P, 8x100BT-P2P, 4x100FX-P2P, 8x100BT MS DSM, 2xGigE/FC-P2P, 2xGigE/FC-P2P-C, or 2xGigE-P2P circuit pack.

• Interface operational measurements for a Fibre Channel facility on a 2xGigE/FC-P2P or 2xGigE/FC-P2P-C circuit pack.

Note: Clearing interface operational measurements for an Ethernet port also clears the Ethernet operational measurements for the port.


Input syntaxINIT-OM-IF:[TID]:AID:CTAG;


Field Purpose


AID Access identifier. The facility to clear.



Example inputClear interface operational measurements for WAN facility 2 of the 2x100BT-P2P circuit pack in slot 9 of network element OTTAWA:INIT-OM-IF:OTTAWA:WAN-9-2:CTAG01;



ETH AID ETH-slot#-port#ETH-slot#-ALLETH-ALL

Identify the Ethernet facility where slot# = 3 to 10port# = 1 or 2 for 2x100BT-P2P, 2xGigE/FC-P2P, 2xGigE/FC-P2P-C or 2xGigE-P2Pport# = 1 to 4 for 4x100FX-P2Pport# = 1 to 8 for 8x100BT-P2P


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

Identify the Ethernet facility on the MS DSM whereslot# = 3 to 6; port# = 1 to 8Hline = OC3 or OC12Hslot = 3 to10Hport = 1 to 4

MS DSM WAN AID

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

Identify the WAN port on the MS DSM where slot# = 3 to 6; port# = 1 to 8Hline = OC3 or OC12Hslot = 3 to10Hport = 1 to 4

FC AID FC-slot#-port#FC-slot#-ALLFC-ALL

Identify the FC facility where slot# = 3 to 10port# = 1 or 2

WAN AID WAN-slot#-port#WAN-slot#-ALLWAN-ALL

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



INIT-REG-ALLThe Initialize Registers All command instructs a network element to clear the performance monitoring data registers for all facilities.

To initialize registers for individual facilities use the INIT-REG-<FACTYPE> commands.

The AID for this command is always ALL.

PM data is kept in separate monitored parameter registers or bins for each passed interval.You can specify either the starting time of the periods of interest using <MONDAT>, <MONTM>, or both, or you can directly specify the interval by using <INDEX>. If you specify <MONDAT>, <MONTM>, or both, you cannot specify <INDEX>.

Current intervals are indicated by INDEX=0, and older periods have higher numbers. If you specify <INDEX>, you cannot specify <MONDAT> or <MONTM>.

Note: The accumulation intervals that are stored are as follows: the current 15-minute and 32 previous 15-minute intervals, the current day and previous day, and an untimed interval.

If all optional parameters are left blank, all of the PM registers for all facilities and parameters for the current 15-minute accumulation period will be cleared at once.

Several parameters can be grouped. To group parameters, use the ampersand (&) as the separator. To use a range of parameters, use two ampersands (&&) between the parameters. For example, to use a range of INDEX intervals from 5 to 12, enter 5&&12 as the INDEX parameter.


Input syntax INIT-REG-ALL:[TID]:AID:CTAG::[MONTYPE],[MONVAL],[LOCN],[DIRN],[TMPER],[MONDAT],[MONTM],[INDEX];




Field Purpose


AID Access identifier. The facility to which the command applies.


MONTYPE The type of monitored parameter for which a value is requested

MONVAL The value the registers should be initialized to

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

MONDAT The date of the beginning of the requested PM period

MONTM The beginning time of day of the requested PM period

INDEX The interval numbers to be accessed



Purpose

ALL ALL All facilities: EC-1, ETH, FC, OC-3, OC-12, OC-48, OC-192, STS-1, STS-3c, STS-12c, STS-24c, STS-48c, WAN, DS1, DS3



MONTYPE nullALL

Default: equivalent to ALLAll applicable MONTYPEs

MONVAL null0

Default: equivalent to 0Reset registers to zero

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-UNTALL

Grouping allowed

Default: equivalent to 15-MIN15-minute interval1-day intervalUntimed intervalAll intervals

MONDAT nullALLMONTH-DAY

Grouping allowed

Default: Current dateAll dates availableMONTH= 1 to 12, DAY= 1 to 31

MONDAT and MONTM can be used as a pair.

Note 1: If INDEX is used, MONDAT and MONTM cannot be used.

Note 2: If TMPER = 1-UNT, MONDAT is not applicable.

MONTM nullALLHOUR-MINUTE

Grouping allowed

Default: Current 15-MINAll available timesHOUR= 00 to 23, MINUTE= 00, 15, 30, 45



Note 2: If TMPER=1-UNT or TMPER=1-DAY, MONTM is not applicable.

INDEX null01-32ALL

Grouping and ranges allowed

Default: equivalent to 0Current intervalPrevious intervals (see Note)All available intervals

If MONDAT and MONTM are used, INDEX cannot be used.

Note: For TMPER=15-MIN, INDEX=1 is the most recently completed 15-minute interval, INDEX=2 is the interval before that. For TMPER=1-DAY, INDEX=1 is the most recently completed day interval (yesterday).





Example input Initialize all 15-minute and 1-day registers on the network element, specifying MONDAT and MONTM: INIT-REG-ALL:NEWYORK:ALL:CTAG23::,,,,15-MIN&1-DAY,ALL,ALL;

Initialize all registers on the network element, specifying all intervals:

INIT-REG-ALL:SEATTLE:ALL:CTAG23::,,,,ALL,,,ALL;



INIT-REG-EC1The Initialize Register EC-1 command instructs a network element to initialize performance monitoring data for an EC-1 facility.

PM data is kept in separate monitored parameter registers or bins for each passed interval. You can specify either the starting time of the periods of interest using <MONDAT>, <MONTM>, or both, or you can directly specify the interval by using <INDEX>. If you specify <MONDAT>, <MONTM>, or both, you cannot specify <INDEX>.



If all optional parameters are left blank, all of the current 15-min PM registers for all parameters for the corresponding facility will be cleared at once.



Input syntaxINIT-REG-EC1:[TID]:AID:CTAG::[MONTYPE],[MONVAL],[LOCN],[DIRN],[TMPER],[MONDAT],[MONTM],[INDEX];




Field Purpose














EC1 EC1-slot#-port#EC1-slot#-ALLEC1-ALLALL

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





MONTYPE nullCVSESSSESSSEFSSCVLESLSESLUASLFCL ALL

Grouping allowed

Default: equivalent to ALLCoding Violations - SectionErrored Seconds - Section Severely Errored Seconds - SectionSeverely Errored Frame Seconds - Section Coding Violations - LineErrored Seconds - LineSeverely Errored Seconds - LineUnavailable Second - Line Failure Count - Line All applicable MONTYPEs

MONVAL null0




DIRN nullTRMTRCVALL


TMPER null15-MIN1-DAY1-UNT

ALL

Grouping allowed

Default: equivalent to 15-MIN15-minute interval1-day intervalUntimed interval

All intervals


Grouping allowed







Example inputInitialize the PM data for near-end receive line coding violations for EC-1slot 3 port 6, for all intervals, all MONDAT and MONTM (that is, all current and historical information):INIT-REG-EC1:SEATTLE:EC1-3-6:CTAG12::CVL,,NEND,RCV, ALL,ALL,ALL;

Initialize the PM data for all monitored parameters for EC-1 slot 3 port 6, for all intervals, specifying all intervals:INIT-REG-EC1:NEWYORK:EC1-3-6:CTAG12::,,,,ALL,,,ALL;

Initialize all current 15-minute registers for all EC-1 facilities:INIT-REG-EC1:WASHINGTON:ALL:CTAG12;


Grouping allowed





INDEX null01 to 32ALL



If MONDAT or MONTM is used, INDEX cannot be used.






INIT-REG-ETHThe Initialize Register Ethernet command instructs a network element to initialize performance monitoring data for an Ethernet facility.







Input syntaxINIT-REG-ETH:[TID]:AID:CTAG::[MONTYPE],[MONVAL],[LOCN],[DIRN],[TMPER],[MONDAT],[MONTM],[INDEX];




Field Purpose














ETH ETH-slot#-port#ETH-slot#-ALLETH-ALL

Identify Ethernet facilities, whereslot# = 3 to 10port# = 1 to 2 for 2xGigE/FC-P2P, 2xGigE/FC-P2P-C or 2xGigE-P2Pport# = 1 to 4 for 4x100FX-P2Pport # = 1 to 8 for 8x100BT-P2P



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





MONTYPE nullES SES UAS INFRAMES INFRAMESERROUTFRAMESOUTFRAMEDISCINFRAMESDISCFRTOOLONGSFRTOOSHORTSINMACCONTROLFRALL Grouping allowed

Default: equivalent to ALLErrored SecondsSeverely Errored Seconds Unavailable SecondsIn Frames In Frames ErroredOut FramesOut Frames DiscardedIn Frames DiscardedOversized Ethernet framesUndersized Ethernet framesMAC Control framesAll applicable MONTYPEs

MONVAL null0




DIRN nullTRMTRCVALL



ALL

Grouping allowed


All intervals


Grouping allowed







Example inputInitialize the PM data for near-end receive errored seconds for the Ethernet facility in slot 3 port 6, for all intervals, all MONDAT and MONTM (that is, all current and historical information):INIT-REG-ETH:SEATTLE:ETH-3-6:CTAG12::ES,,NEND,RCV, ALL,ALL,ALL;

Initialize the PM data for all monitored parameters for the Ethernet facility in slot 3 port 6, for all intervals, specifying all intervals:INIT-REG-ETH:NEWYORK:ETH-3-6:CTAG12::,,,,ALL,,,ALL;

Initialize all current 15-minute registers for all Ethernet facilities:INIT-REG-ETH:WASHINGTON:ALL:CTAG12;


Grouping allowed














INIT-REG-FCThe Initialize Register Fibre Channel command instructs a network element to initialize performance monitoring data for a Fibre Channel facility.







Input syntaxINIT-REG-FC:[TID]:AID:CTAG::[MONTYPE],[MONVAL],[LOCN],[DIRN],[TMPER],[MONDAT],[MONTM],[INDEX];




Field Purpose














FC FC-slot#-port#FC-slot#-ALLFC-ALL

Identify Fibre Channel facilities, whereslot# = 3 to 10port# = 1 or 2





MONTYPE nullES SES UAS INFRAMES OUTFRAMESOUTFRAMEDISCINFRAMESDISCCMPCMPMXALL Grouping allowed

Default: equivalent to ALLErrored SecondsSeverely Errored Seconds Unavailable SecondsIn Frames Out FramesOut Frames DiscardedIn Frames DiscardedCompression EfficiencyMaximum Compression efficiencyAll applicable MONTYPEs

MONVAL null0




DIRN nullTRMTRCVALL



ALL

Grouping allowed


All intervals


Grouping allowed







Example inputInitialize the PM data for near-end receive errored seconds for the Fibre Channel facility in slot 3 port 1, for all intervals, all MONDAT and MONTM (that is, all current and historical information):INIT-REG-FC:SEATTLE:FC-3-1:CTAG12::ES,,NEND,RCV,ALL,ALL,ALL;

Initialize the PM data for all monitored parameters for the Fibre Channel facility in slot 3 port 1, for all intervals, specifying all intervals:INIT-REG-FC:NEWYORK:FC-3-1:CTAG12::,,,,ALL,,,ALL;

Initialize all current 15-minute registers for all Fibre Channel facilities:INIT-REG-FC:WASHINGTON:ALL:CTAG12;


Grouping allowed














INIT-REG-OC12The Initialize Register OC-12 command instructs a network element to initialize performance monitoring data for an OC-12 facility.

Performance Monitoring (PM) data is kept in separate monitored parameter registers or bins for each passed interval. You can specify either the starting time of the periods of interest using <MONDAT>, <MONTM>, or both, or you can directly specify the interval by using <INDEX>. If you specify <MONDAT>, <MONTM>, or both, you cannot specify <INDEX>.






Input syntaxINIT-REG-OC12:[TID]:AID:CTAG::[MONTYPE],[MONVAL],[LOCN],[DIRN],[TMPER],[MONDAT],[MONTM],[INDEX];




Field Purpose












Table 3-142AID parameters


OC12 AID type OC12-slot#-port#OC12-slot#-ALLOC12-ALLALL

Identify the OC-12 facilities whereslot# = 3 to12 for OC-12slot# = 3 to10 for OC-12x4 STSport# =1 for OC-12port# =1 to 4 for OC-12x4 STS


Identify the MS DSM OC-12 facility where slot = 1 or 2Hport = 1 to 4Hslot = 3 to 10





MONTYPE nullCVSESSSESSSEFSSCVLESLSESLUASLFCL PSCWPSCPPSDALL

Grouping allowed

Default: equivalent to ALLCoding Violations - SectionErrored Seconds - Section Severely Errored Seconds - SectionSeverely Errored Frame Seconds - Section Coding Violations - LineErrored Seconds - LineSeverely Errored Seconds - LineUnavailable Second - Line Failure Count - Line Protection switch count - Working lineProtection switch count - Protection lineProtection switch durationAll applicable MONTYPEs

MONVAL null0




DIRN nullTRMTRCVALL



ALL

Grouping allowed


All intervals


Grouping allowed







Example inputInitialize the PM data for near-end receive line coding violations for OC-12 slot 10, for all intervals, all MONDAT and MONTM (that is, all current and historical information):INIT-REG-OC12:SEATTLE:OC12-10:CTAG12::CVL,,NEND,RCV, ALL,ALL,ALL;

Initialize the PM data for all monitored parameters for OC-12 slot 10, for all intervals, specifying all intervals:INIT-REG-OC12:NEWYORK:OC12-10:CTAG12::,,,,ALL,,,ALL;

Initialize all current 15-minute registers for all OC-12 facilities:INIT-REG-OC12:WASHINGTON:ALL:CTAG12;


Grouping allowed















Field Purpose









MONDAT The date of beginning the requested PM period

MONTM The time of beginning the requested PM period

INDEX The interval numbers to be retrieved



OC-192 AID OC192-slot#OC192-ALLALL

Identifies the OC-192 slotslot# =11, 12





MONTYPE nullCVSESSSESSSEFSSCVLESLSESLUASLFCLPSCWPSCPPSDOPRALL

Grouping allowed

Default: equivalent to ALLCoding Violations - SectionErrored Seconds - Section Severely Errored Seconds - SectionSeverely Errored Frame Seconds - Section Coding Violations - LineErrored Seconds - LineSeverely Errored Seconds - LineUnavailable Seconds - Line Failure Count - LineProtection switch count - Working lineProtection switch count - Protection lineProtection switch durationOptical Power Receive

Optical Power Receive, normalizedAll monitored type

MONVAL null0




DIRN nullTRMTRCVALL



ALL

Grouping allowed


All intervals


Grouping allowed










Grouping allowed





INDEX null01-32ALL










Field Purpose














OC3 AID OC3-slot#-port#OC3-slot#-ALLOC3-ALLALL


MS DSM or DSM OC3 Facility AID

OC3-slot#-1-%HLINK-OC3-hslot#-hport# slot# = 1 or 2hslot# = 3 to 10hport# = 1 to 4





MONTYPE nullCVSESSSESSSEFSSCVLESLSESLUASLFCL PSCWPSCPPSDALL

Grouping allowed

Default: equivalent to ALLCoding Violations - SectionErrored Seconds - Section Severely Errored Seconds - SectionSeverely Errored Frame Seconds - Section Coding Violations - LineErrored Seconds - LineSeverely Errored Seconds - LineUnavailable Second - Line Failure Count - Line Protection switch count - Working lineProtection switch count - Protection lineProtection switch durationAll applicable MONTYPEs

MONVAL null0




DIRN nullTRMTRCVALL



ALL

Grouping allowed


All intervals


Grouping allowed







Example inputInitialize the PM data for near-end receive line coding violations for OC-3x4 slot 10 port 2, for all intervals, all MONDAT and MONTM (that is, all current and historical information):INIT-REG-OC3:SEATTLE:OC3-10-2:CTAG12::CVL,,NEND,RCV, ALL,ALL,ALL;

Initialize the PM data for all monitored parameters for OC-3x4 slot 10 port 2, for all intervals, specifying all intervals:INIT-REG-OC3:NEWYORK:OC3-10-2:CTAG12::,,,,ALL,,,ALL;

Initialize all current 15-minute registers for all OC-3 facilities:INIT-REG-OC3:WASHINGTON:ALL:CTAG12;


Grouping allowed















Field Purpose









MONDAT The date of beginning the requested PM period

MONTM The time of beginning the requested PM period

INDEX The interval numbers to be retrieved



OC-48 AID OC48-slot#OC48-ALLALL

Identifies the OC-48 slotslot# = 3 to 12 for OC-48 STS, 11 or 12 for OC-48





MONTYPE nullCVSESSSESSSEFSSCVLESLSESLUASLFCLPSCWPSCPPSDOPRALL

Grouping allowed

Default: equivalent to ALLCoding Violations - SectionErrored Seconds - Section Severely Errored Seconds - SectionSeverely Errored Frame Seconds - Section Coding Violations - LineErrored Seconds - LineSeverely Errored Seconds - LineUnavailable Seconds - Line Failure Count - LineProtection switch count - Working lineProtection switch count - Protection lineProtection switch durationOptical Power ReceiveAll applicable MONTYPEs

MONVAL null0




DIRN nullTRMTRCVALL



ALL

Grouping allowed


All intervals


Grouping allowed










Grouping allowed





INDEX null01-32ALL









INIT-REG-STS1The Initialize Register STS-1 command instructs a network element to initialize performance monitoring data for the STS-1 facility.







Input syntaxINIT-REG-STS1:[TID]:AID:CTAG::[MONTYPE],[MONVAL],[LOCN],[DIRN],[TMPER],[MONDAT],[MONTM],[INDEX];




Field Purpose














MONTYPE nullCVP ESP SESP ALSPUASP FCPALLGrouping allowed

Default: equivalent to ALLCoding Violations - PathErrored Seconds - PathSeverely Errored Seconds - PathAIS/LOP Seconds - PathUnavailable Seconds - PathFailure Count - PathAll applicable MONTYPEs

MONVAL null0






DIRN nullTRMTRCVALL



ALL

Grouping allowed


All intervals


Grouping allowed






Grouping allowed














Example inputInitialize the PM data at NEWYORK on OC-3x4 in slot 3 port 1 sts 2, for path errored seconds (ESP) for the current 15-minute bin: INIT-REG-STS1:NEWYORK:OC3-3-1-2:CTAG12::ESP;

Initialize the PM data at SEATTLE on all facilities for path failure count (FCP), at the near-end receive direction only for the current 1-day bin: INIT-REG-STS1:SEATTLE:ALL:CTAG12::FCP,,NEND,RCV,1-DAY;



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-1-sts#-%HLINK-OC3-hslot#-hport#

Identify the STS-1 facilities on the DSM interfaces whereslot# = 1 or 2, sts# = 1 to 3hslot# = 3 to 10, hport# = 1 to 4

OC3-slot-1-ALL-%HLINK-OC3-hslot#-hport#

Identify all STS-1 facilities on the DSM interfaces whereslot# = 1 or 2, hslot# = 3 to 10hport# = 1 to 4

OC12-slot-1-sts#-%HLINK-OC12-hslot#-hport#

Identify the STS-1 facilities on the DSM interfaces whereslot# = 1 or 2, sts# = 1 to 3hslot# = 3 to 10, hport# = 1 to 4

OC12-slot-1-ALL-%HLINK-OC12-hslot#-hport#

Identify all STS-1 facilities on the DSM interfaces whereslot# = 1 or 2, hslot# = 3 to 10hport# = 1 to 4

OC192-slot#-sts#OC192-slot#-ALLOC192-ALL

Identify the STS-1 facilities on the OC-192 interfacesslot# = 11 or 12, sts# = 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



INIT-REG-STS12CThe Initialize Register STS-12c command instructs a network element to initialize performance monitoring data for the STS-12c facility.







Input syntaxINIT-REG-STS12C:[TID]:AID:CTAG::[MONTYPE],[MONVAL],[LOCN],[DIRN],[TMPER],[MONDAT],[MONTM],[INDEX];




Field Purpose


AID Access identifier. The STS-12c path facility to which the command applies.












STS-12c OC12-slot#-port#-sts#OC12-slot#-port#-ALLOC12-slot#-ALLOC12-ALL

Identify the STS-12c facilities, whereslot# = 3 to12 for OC-12slot# = 3 to10 for OC-12x4 STSport# =1 for OC-12port# = 1 to 4 for OC-12x4 STSsts# = 1

OC12-slot#-sts#-%HLINK-OC12-hslot#-hport#

Identify the STS-12c facilities on the DSM interfaces whereslot# = 1 or 2, sts# = 1 to 3hslot# = 1 to 10, hport# = 1 to 4

OC12-slot-#-ALL-%HLINK-OC12-hslot#-hport#

Identify all STS-12c facilities on the DSM interfaces whereslot# = 1 or 2, hslot# = 1 to 10hport# = 1 to 4

ALL All applicable STS-12c path facilities







MONVAL null0




DIRN nullTRMTRCVALL



ALL

Grouping allowed


All intervals


Grouping allowed







Example inputInitialize the PM data at NEWYORK on OC-12 in slot 3 sts 1, for path errored seconds (ESP) for the current 15-minute bin: INIT-REG-STS3C:NEWYORK:OC12-3-1:CTAG12::ESP;

Initialize the PM data at WASHINGTON on all OC-12 slots for STS-12c path severely errored seconds (SESP), specifying MONDAT and MONTM for 15-minute bins: INIT-REG-STS3C:WASHINGTON:OC12-ALL:CTAG12:SESP,,,,,12-25,09-00;

Initialize the PM data at SEATTLE on all OC-12 and OC-48 facilities for STS-12c path failure count (FCP), at the near-end receive direction only for the current 1-day bin:

INIT-REG-STS12C:SEATTLE:ALL:CTAG12::FCP,,NEND,RCV,1-DAY;


Grouping allowed















Field Purpose














STS-24c AID OC192-slot#-sts#OC192-slot#-ALLOC192-ALL

Identify the STS-24c facility whereslot# = 11, 12sts# =1, 25All slots with OC-192 cards


Identify the STS-24c facility whereslot# = 3 to 12sts# = 1, 25All slots with OC-48 STS cards

ALL All applicable STS-24c facilities







MONVAL null0




DIRN nullTRMTRCVALL



ALL

Grouping allowed


All intervals


Grouping allowed









Initialize the PM data at SEATTLE on all OC-48 facilities for STS-24c path failure count (FCP), at the near-end receive direction only for the current 1-day bin:



Grouping allowed















Field Purpose














Example inputInitialize the PM data at NEWYORK on OC-3x4 in slot 3 port 2 sts 1, for path errored seconds (ESP) for the current 15-minute bin: INIT-REG-STS3C:NEWYORK:OC3-3-2-1:CTAG12::ESP;

Initialize the PM data at WASHINGTON on all OC-3x4 slots for STS-3c path severely errored seconds (SESP), specifying MONDAT and MONTM for 15-minute bins:

INIT-REG-STS3C:WASHINGTON:OC3-ALL:CTAG12:SESP,,,,,12-25,09-00;

Initialize the PM data at SEATTLE on all facilities for STS-3c path failure count (FCP), at the near-end receive direction only for the current 1-day bin:


Table 3-163AID Description


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

OC12-slot#-port#-sts#OC12-slot#-port#-ALLOC12-slot#-ALLOC-12-ALL

Identify the STS-3c facilityslot# = 3 to12 for OC-12slot# = 3 to10 for OC-12x4 STSport# =1 for OC-12port# = 1 to 4 for OC-12x4 STSsts# = 1, 4, 7, 10


Identify the STS-3c facilityslot# = 3 to 12 for OC-48 STSslot# = 11 or 12 for OC-48sts# = 1, 4, 7, .., 46


Identify the STS-3c facilityslot# =11 to 12sts# = 1, 4, 7, ..., 190

ALL All applicable STS-3c path facilities

DSMSTS-3c AID

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

OC3-slot-1-ALL-%HLINK-OC3-Hslot#-Hport#

Identify the STS-3c facility whereslot# = 1, 2sts# = 1, hslot# = 3 to 10, hport# = 1 to 4

OC12-slot-1-sts-%HLINK-OC12-Hslot#-Hport#

OC12-slot-1-ALL-%HLINK-OC12-Hslot#-Hport#

Identify the STS-3c facility whereslot# = 1, 2sts# = 1, 4, 7, 10hslot# = 3 to 10, hport# = 1 to 4




Field Purpose














STS-48c AID OC192-slot#-sts#OC192-slot#-ALL

OC192-ALL

Identify the STS-48c facility whereslot# = 11, 12sts# =1, 49, 97, 145

All slots with OC-192 cards

OC48-slot#-sts#OC48-slot#-ALL

OC48-ALL

Identify the STS-48c facility whereslot# = 3 to 12, sts# =1All slots with OC-48 STS cards

ALL All applicable STS-48c facilities







MONVAL null0




DIRN nullTRMTRCVALL



ALL

Grouping allowed


All intervals


Grouping allowed









Initialize the PM data at SEATTLE on all OC-48 facilities for STS-48c path failure count (FCP), at the near-end receive direction only for the current 1-day bin:



Grouping allowed














INIT-REG-T1The Initialize Registers T1 command instructs a network element to initialize performance monitoring data for the DS1 facility.







Input syntaxINIT-REG-T1:[TID]:AID:CTAG::[MONTYPE],[MONVAL],[LOCN],[DIRN],[TMPER],[MONDAT],[MONTM],[INDEX];




Field Purpose














T1 AID DS1-slot#-port#DS1-slot#-ALLDS1-ALL

Identify the DS1s whereslot# = 4 to 10port# = 1 to 12


Identify DS1s on DS3VTx12 equipment whereslot# = 3, 5, 7, 9port# = 1 to 12t1# = 1 to 28

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

DSM port# = 1 to 84HLINE= OC3 or OC12hslot# = 3 to 10, hport# = 1 to 4


All DS1 ports on DSMHLINE= OC3 or OC12hslot# = 3 to 10hport# = 1 to 4

ALL All DS1 facilities





MONTYPE null

CVLESLSESLCVPESPSESPSEFSPSASPCSSPUASPFCP ALL

Grouping allowed

Default: equivalent to ALL

Coding Violations - LineErrored Seconds - LineSeverely Errored Seconds- LineCoding Violations - PathErrored Seconds - PathSeverely Errored Seconds - PathSeverely Errored Frame Seconds - PathSEF / AIS Seconds - PathControlled slip seconds - PathUnavailable Seconds - PathFailure Count - Path All applicable MONTYPEs

MONVAL null0




DIRN nullTRMTRCVALL



ALL

Grouping allowed


All intervals


Grouping allowed







Example inputInitialize the PM data for near-end receive line coding violations for DS1 slot 4 port 7, for all intervals, specifying ALL MONDAT and ALL MONTM (that is, all current and historical bins): INIT-REG-T1:NEWYORK:DS1-4-7:CTAG12::CVL,,NEND,RCV,ALL,ALL,ALL;

Initialize the PM data for all monitored parameters for DS1 slot 4 port 7, for all intervals, specifying all time periods: INIT-REG-T1:SEATTLE:DS1-4-7:CTAG12::,,,,15-MIN&1-DAY&1-UNT,,,ALL;

Initialize all current 15-minute registers for all DS1 facilities: INIT-REG-T1:WASHINGTON:ALL:CTAG12;


Grouping allowed














INIT-REG-T3The Initialize Registers T3 command instructs a network element to initialize performance monitoring data for the DS3 facility.







Input syntaxINIT-REG-T3:[TID]:AID:CTAG::[MONTYPE],[MONVAL],[LOCN],[DIRN], [TMPER],[MONDAT],[MONTM],[INDEX];




Field Purpose


AID Access identifier. The facility to which the command applies












T3 AID DS3-slot#-port# slot#=3 to 10port#=1 to 4

DS3-slot#-ALL slot#=3 to 10All DS3 ports

DS3-ALL All DS3 ports

MS DSM T3 AID


port# = 1 to 6HLINE=OC3 or OC12hslot# = 3 to 10hport# = 1 to 4


All DS3 ports on MS DSM

HLINE=OC3 or OC12hslot# = 3 to 10hport# = 1 to 4





MONTYPE null

CVLESLSESLCVPESPSESPSASPUASPFCP ALL

Grouping allowed

Default: equivalent to ALL

Coding Violations - LineErrored Seconds - LineSeverely Errored Seconds- LineCoding Violations - PathErrored Seconds - PathSeverely Errored Seconds - PathSEF / AIS Seconds - PathUnavailable Seconds - PathFailure Count - Path All applicable MONTYPEs

MONVAL null0




DIRN nullTRMTRCVALL



ALL

Grouping allowed


All intervals


Grouping allowed







Example inputInitialize the PM data at NEWYORK on DS3 in slot 3 port 2 for path coding violations (CVP) for the current 15-minute bin: INIT-REG-T3:NEWYORK:DS3-3-2:CTAG12::CVP;

Initialize the PM data at WASHINGTON on all DS3 slots for path unavailable seconds (UASP), specifying MONDAT and MONTM: INIT-REG-T3:WASHINGTON:DS3-ALL:CTAG12::UASP,,,,,12-25,09-00;

Initialize the PM data at SEATTLE on all DS3 facilities for path severely errored seconds (SESP), at the near-end receive direction only for the current 1-day bin: INIT-REG-T3:SEATTLE:ALL:CTAG12::SESP,,NEND,RCV,1-DAY;


Grouping allowed














INIT-REG-WANThe Initialize Register WAN command instructs a network element to initialize performance monitoring data for a WAN facility.







Input syntaxINIT-REG-WAN:[TID]:AID:CTAG::[MONTYPE],[MONVAL],[LOCN],[DIRN],[TMPER],[MONDAT],[MONTM],[INDEX];




Field Purpose














WAN WAN-slot#-port#WAN-slot#-ALLWAN-ALL

Identify WAN facilities, whereslot# = 3 to 10port# = 1 to 2 for 2xGigE/FC-P2P, 2xGigE/FC-P2P-C, 2xGigE-P2Pport# = 1 to 4 for 4x100FX-P2Pport# = 1 to 8 for 8x100BT-P2P

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.





MONTYPE nullES SES UAS INFRAMES INFRAMESERR OUTFRAMESLDSLSDSLUASUTLUTLMXALLGrouping allowed

Default: equivalent to ALLErrored SecondsSeverely Errored Seconds Unavailable SecondsIn Frames In Frames ErroredOut FramesLCAS degraded secondsLCAS severely degraded secondsLCAS unavailable secondsLink utilizationMaximum link UtilizationAll applicable MONTYPEsLDS, LSDS, LUAS are applicable only for 4x100FX and 8x100BT-P2P circuit packs.

MONVAL null0




DIRN nullTRMTRCVALL



ALL

Grouping allowed


All intervals


Grouping allowed







Example inputInitialize the PM data for near-end receive errored seconds for the WAN facility in slot 3 port 6, for all intervals, all MONDAT and MONTM (that is, all current and historical information):INIT-REG-WAN:SEATTLE:WAN-3-6:CTAG12::ES,,NEND,RCV, ALL,ALL,ALL;

Initialize the PM data for all monitored parameters for the WAN facility in slot 3 port 6, for all intervals, specifying all intervals:INIT-REG-WAN:NEWYORK:WAN-3-6:CTAG12::,,,,ALL,,,ALL;

Initialize all current 15-minute registers for all WAN facilities:INIT-REG-WAN:WASHINGTON:ALL:CTAG12;


Grouping allowed














INIT-UPGRD-EQPTThe Initiate Upgrade - Equipment command is used to initiate an automatic line rate upgrade which converts all the provisioning data of an

• OC-3 to that of an OC-12




Input syntax INIT-UPGRD-EQPT:[TID]:AID:CTAG;

Example inputInitiate an automatic line rate upgrade for network element NEWYORK:

INIT-UPGRD-EQPT:NEWYORK:OC12-7:CTAG12;


Field Purpose






OC-12 AID OC12-slot# Identify the OC-12 equipment whereslot# = 3 to 12

OC-48 AID OC48-slot# Identify the OC-48 equipment whereslot# = 11, 12

OC-48 STS AID

OC48-slot# Identify the OC-48 equipment whereslot# = 3 to 12

OC-192 AID OC192-slot# Identify the OC-192 equipment where slot# = 11, 12



INIT-WARMThe Initialize Warm command instructs a network element to initialize its circuit packs. A warm initialization does not affect traffic.

The date and time must be reset after a system restart.

Note: If the INIT-WARM command is issued against the OC-3x4 circuit pack, an SDCC link failure alarm will be briefly raised and then cleared.


Input syntaxINIT-WARM:[TID]:AID:CTAG;


Field Purpose



AID Access identifier. The circuit pack to initialize.




Purpose

Equipment DS1-slot# Identify the DS1 where slot# =3 to 10

DS3-slot# Identify the DS3 where slot# =3 to 10

DS3V-slot# Identify the DS3VTx12 where slot# =3 to 10

DS3EC1-slot# Identify the DS3/EC-1x12 where slot# = 3 to 10

OC3-slot# Identify the OC-3 or OC-3x4 where slot# =3 to 10



Equipment OC12-slot# Identify the OC-12 or OC-12x4 STS whereslot# = 3 to 12 for OC-12, 3 to 10 for OC-12x4 STS

OC48-slot# Identify the OC-48 or OC-48 STS whereslot# = 11 or 12 for OC-48, 3 to 12 for OC-48 STS

OC192-slot# Identify the OC-192 where slot# = 11 or 12

EC1-slot# Identify the EC-1 where slot# = 3 to 10

CLX-slot# Identify the VTX48, VTX40/10 or STX-192 where slot# =13 or 14

ILAN Identify the ILAN

IPT100-slot# Identify the 4x100BT where slot# = 3 to 10

100FOSO-slot# Identify the 4x100FX-P2P where slot# = 3 to 10

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

1GE-slot# Identify the 2xGigE where slot# = 3, 5, 7, 9 for the double slot circuit packs and slot# =3 to 10 for the single slot 2xGigE circuit packs.

100FX-slot# Identify the 4x100FX where slot# = 3 to 10

100BTFOS-slot# Identify the 2x100BT-P2P where slot# = 3 to 10

1GFOS-slot# Identify the 2xGigE/FC-P2P, 2xGigE/FC-P2P-C or 2xGigE-P2P where slot# = 3 to 10

1GE25G-slot# Identify the 2xGigE 2.5G circuit packwhere slot# = 3, 5, 7, 9

PSC Protection switch controller

SP Shelf processor

NP Network processor




Purpose



Example inputPerform a warm initialization of OC-3x4 in slot 10 only on network WASHINGTON:INIT-WARM:WASHINGTON:OC3-10:CTAG12;

Restart the 4x100BT circuit pack in slot 8:INIT-WARM:OC3SP:IPT100-8:CTAG12;

Equipment DS1TM-slot#-%HLINK-oc3-hslot#-hport#

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

AGGOC3-slot-%HLINK-OC3-Hslot-Hport#


AGGOC3OC12-slot-%HLINK-OC12-Hslot-Hport#


PECN-slot#-%HLINK-Hline-Hslot#-Hport#

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

PFOST-slot#-%HLINK-Hline-Hslot#-Hport#

Identify the pluggable equipment where slot# = 1 or 2, hslot# = 3 to 10, hport# = 1 to 4, HLINE = OC3 or OC12



Purpose



INVK-INSTALLThe Invoke Installation command initiates the installation of software to the shelf processor.


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

Example inputInitiate the installation of the software to the shelf processor on network element OTTAWA: INVK-INSTALL:OTTAWA::CTAG45;


Field Purpose

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




INVK-RINGMAPUse the Invoke Ring Map command to apply the ring map. This command is supported on the network processor.


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

Example inputApply the ring map for NPFGXOTT:

INVK-RINGMAP:NPFGXOTT:OTTAWA_RING:CTAG;


Field Purpose


AID Ring name




Ring name An alphanumeric string between 1 and 20 characters




AID An alphanumeric string between 1 and 20 characters

Ring name



INVK-UPGRDWhen issued from the network element user interface, the Invoke Upgrade command causes the new shelf processor and transport loads to be executed. The new transport load runs on each transport card. When issued from the network processor user interface, the Invoke Upgrade command causes the new network processor load to be executed.


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

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

Example input Invoke the upgrade on network element NEWYORK:INVK-UPGRD:NEWYORK::CTAG24;

Invoke the upgrade on OC3NP:INVK-UPGRD:OC3NP::CTAG25;

Invoke the upgrade of slot 3 on network element NEWYORK:INVK-UPGRD:NEWYORK:3:CTAG26;


Field Purpose


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




LOAD-FPGAUse the Load Field Programmable Gate Array command to upgrade the FPGA load of a Packet Edge, 2x100BT-P2P, 2xGigE/FC-P2P, 2xGigE/FC-P2P-C or 2xGigE-P2P circuit pack.

Note: After the upgrade, you must cold restart the circuit pack for the new FPGA load to be used. See the description of the INIT-COLD command on page 3-125 for information about performing a cold restart.


Input syntaxLOAD-FPGA:[TID]:AID:CTAG::RNAME;


Field Purpose




RNAME Remote node name where FPGA load file resides. 1 to 40 alphanumeric characters.



IPT100 IPT100-slot# Upgrade the FPGA load of the 4x100BT where slot# = 3 to 10

1GE 1GE-slot# Upgrade the FPGA load of the 2xGigE where slot# = 3, 5, 7, 9 for double slot circuit pack and slot#= 3 to 10 for single slot 2xGigE circuit packs.

100FX 100FX-slot# Upgrade the FPGA load of the 4x100FX where slot# = 3 to 10

100BTFOS 100BTFOS-slot# Upgrade the FPGA load of the 2x100BT-P2P where slot# = 3 to 10

1GFOS 1GFOS-slot# Upgrade the FPGA load of the 2xGigE/FC-P2P, 2xGigE/FC-P2P-C or 2xGigE-P2P where slot# = 3 to 10



Example inputUpgrade the FPGA load of the 4x100BT in slot 5 of network element NEWYORK:LOAD-FPGA:NEWYORK:IPT100-5:CTAG 12::MASTERNODE58;

1GE25G AID

1GE25G-slot# Upgrade the FPGA load of the 2xGigE 2.5G circuit pack where slot# = 3, 5, 7, 9

MS DSM AID

AGGOC3-slot-%HLINK-OC3-Hslot#-Hport#


AGGOC3OC12-slot-%HLINK-HLINE-Hslot#-Hport#


PFOST-slot-%HLINK-Hline-Hslot#-Hport#

Identify the pluggable equipment where slot# = 1 or 2, hslot# = 3 to 10, hport# = 1 to 4, HLINE = OC3 or OC12





LOAD-INSTALLThe Load Installation command downloads the software load to install on the shelf processor from a specified node to the program store bank of the shelf processor. The system uses a different store bank from the one currently running.


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

Example inputDownload the software load from the network element MONTREAL to the shelf processor of network element OTTAWA:

LOAD-INSTALL:OTTAWA::CTAG45::MONTREAL;


Field Purpose

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


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.



LOAD-REPLACEThe Load Replace command installs the specified software load into the file system, without upgrading to it. This makes the load available for upgrades by the local network processor or other connected network elements or network processors. This command is only available on the network processor.


Input syntaxLOAD-REPLACE:[TID]::CTAG::[RNAME],[RELNO]:[ALRMS=Domain][,INHIBIT=Domain];

Example input Install load REL0400A.DM from OPC MONTREAL onto network processor OTTAWANP and proceed only if there are no alarms:LOAD-REPLACE:OTTAWANP::CTAG1::MONTREAL,REL0400A.DM:ALRMS=Y;


Field Purpose



RNAME Name of the node or OPC where the load files reside

RELNO Release number to install on network processor. See Parameter descriptions table for details.

ALRMS=Domain Check alarms. See Parameter descriptions table for details.

INHIBIT=Domain Check inhibit


Parameter Description

RNAME The name of the node from which the new loads are retrieved. The node can be of different types:OC3NP: RNAME = the remote TID (7-20 characters)OPC: RNAME = the name of the remote OPC

RELNO ASCII string identifying the release number to upgrade to

ALRMS If Y, proceed only if there are no alarms If N, proceed regardless of the alarm status

INHIBIT If Y, proceed only if no slots have been inhibitedIf N, proceed regardless of inhibit status



LOAD-RINGMAPUse the Load Ring Map command to load map information to all managed shelf processors.

By default, the ring map is loaded from the local network processor. You can also load the ring map from a remote network processor.


Input syntaxLOAD-RINGMAP:[TID]:AID:CTAG::[REMOTE-NAME][,DIRECTORY];

Example inputLoad the ring map information to all nodes in the ring OTTAWA_RING:LOAD-RINGMAP:NPFGXOTT:OTTAWA_RING:CTAG;


Field Purpose


AID Ring name


REMOTE-NAME Remote shelf processor or network processor

DIRECTORY Path that contains the ring map



Ring name An alphanumeric string between 1 and 20 characters




REMOTE-NAME An alphanumeric string between 1 and 20 characters

Target identifier of the remote network processor

DIRECTORY An alphanumeric string between 1 and 96 characters

Path on the remote shelf processor or network processor that contains the ring map



LOAD-TL1SCRPT-NEThe Load TL1 Script Network Element command is used to download a TL1 script file from a remote destination with a TID or IP address, and then temporarily store it on the NP.

While this command is running, a TL1 Script file Load in Progress alarm becomes active. This alarm remains active until you run the CMMT-TL1SCRPT-NE command (to commit the TL1 commands in this file to the target network element), or the CANC-TL1SCRPT-NE command (to cancel this operation).

This command is not successful if one of the following occurs

• there is an unsuccessful download of the TL1 script file from the remote location

• the file validation fails

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 syntaxLOAD-TL1SCRPT-NE:[TID]::CTAG::[userid],[passwd]:TRGTID=Domain,DESTTYPE=Domain,DESTADDR=Domain][,DIR=Domain][,CHKALM=Domain][,CHKTID=Domain];


Field Purpose



userid User login ID

passwd User password

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

DESTTYPE Source of the TL1 script file — TID or IP

DESTADDR Address of the DESTTYPE (TID or IP) which is the source of the TL1 script file



DIR Directory in which the TL1 script file is stored.

CHKALM Check alarm status

CHKTID Check TID

Specifies whether the operation does or does not compare the TID from which the TL1 script file was saved with the TID of the network processor to which the TL1 script file is being stored.



DESTTYPE TID A remote Restore will be executed using ALFTAM or FTAM protocol to transfer files from the TID given in the DESTADDR parameter to a shelf processor or network processor.

IP A remote Restore will be enacted using FTP to transfer files from the IP address given in theDESTADDR parameter to the network processor.

DESTADDR TID address Name of the remote location with the TL1 script file consisting of an identifier of 7 to 20 alphanumeric characters. The first character is alphabetic.

IP address The address of the remote location with the TL1 script file consisting of an identifier in the format x.x.x.x (where x=a number 0-255).

DIR Directory name A string of characters that specifies the unique directory name in which the TL1 script file is located.

When storing the TL1 script file on the network processor, the name of the directory in which the TL1 script file is located must be specified in the command or the command fails. (That is, there is no default directory name.) The directory name is a string of 1 to 60 characters.


Field Purpose



Example inputLoad the TL1 script file from a remote Unix station to network processor OTTAWA:

LOAD-TL1SCRPT-NE::CTAG96:::TRGTID=OTTAWA,DESTTYPE=IP,DESTADDR=47.100.3.54,DIR=”/home/sam/saverest”,CHKALM=Y,CHKTID=N;

CHKTID Y (default) Perform TID check

N Do not check the TID

To store the TL1 script file of a network processor to a network processor with a different TID, set CHKTID to N.

CHKALM Y (default) The LOAD-TL1SCRPT-NE command is not allowed if there is an alarm present on the network processor.

N The LOAD-TL1SCRPT-NE command is allowed if there is an alarm present on the network processor receiving the command except if it is in one of the following states: upgrade in progress; load mismatch; IS rollover in progress; duplicate SID; database save and restore in progress.





LOAD-UPGRDWhen issued from the network element user interface, the Load Upgrade command causes the new shelf processor and transport loads to be downloaded into the shelf processor file system. The new transport load is transferred from the shelf processor to each transport card in the network element. When issued from the network processor user interface, the Load Upgrade command causes the new shelf processor, transport, and network processor loads to be downloaded into the network processor file system. When issued from the network element user interface on a specific slot, the Load Upgrade command causes the transport loads to be downloaded into the specified card.


Input syntax for NPLOAD-UPGRD:[TID]::CTAG::RNAME,RELNO:[ALRMS=Domain];

Input syntax for SPLOAD-UPGRD:[TID]:[AID]:CTAG::[RNAME],[RELNO]:[ALRMS=Domain][,INHIBIT=Domain];


Field Purpose



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. The ALRMS parameter is also not required and the functionality will default to N (ignore any alarms).

RNAME Name of the node from which the new loads are retrieved. See Parameter descriptions table for details.

RELNO Release number to upgrade to. See Parameter descriptions table for details.

ALRMS Check alarms. See Parameter descriptions table for details.

INHIBIT Check inhibit. This parameter allows the upgrade to continue even though slots have been inhibited on the shelf. See Parameter descriptions table for details.



Example input Download the new software from network element OTTAWA to network element NEWYORK regardless of the alarm status:LOAD-UPGRD:NEWYORK::CTAG24::OTTAWA,NTNA6021:ALRMS=N;

Download the new software from OC3NP2 to OC3NP:LOAD-UPGRD:OC3NP::CTAG25::OC3NP2,NTNA6021;

Download the new software to slot 3 of network element NEWYORK:LOAD-UPGRD:NEWYORK:3:CTAG26;



RNAME The name of the node from which the new 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

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 ASCII string identifying the release number to upgrade to

ALRMS If Y, proceed only if there are no alarms

If N, proceed regardless of the alarm status

INHIBIT If Y (default), procced only if no slots have been inhibited

If N, proceed regardless of inhibit status



OPR-ACO-ALLThe Operate Audible Alarm Cutoff All command instructs a network element to cut off the office audible alarm indications without changing the other alarm indications.

The result of the OPR-ACO-ALL command is identical to manually pressing the ACO button on the network element circuit pack.

There is no complementary release command for ACO.


Input syntaxOPR-ACO-ALL:[TID]:[AID]:CTAG;


Example inputStop the audible alarm in network element NEWYORK:

OPR-ACO-ALL:NEWYORK::CTAG12;

Stop audible alarms in ALL network elements:

OPR-ACO-ALL:ALL::CTAG12;


Field Purpose





AID TYPE Command-specific values Purpose

AID ALL-%HLINK-HLINE-hslot#-hport#

Turn off DS1 service module or the MS DSM office audible alarms

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

ALL Turn off all office audible alarms



OPR-BITSOUTSWThe Operate BITS Out Switch command is used to perform manual synchronization switching between the primary and secondary timing references at a BITS output. The switch completes only if the quality of the two references is the same. The network element always chooses the best quality timing reference for its synchronization reference.

Use the RTRV-BITS-OUT command to retrieve the current timing reference settings. Use the SET-BITS-OUT command to assign the primary and secondary timing references.

User synchronization switches initiated using this command remain active until another BITS Out switch is activated or they are overridden by a synchronization reference failure.


Input syntaxOPR-BITSOUTSW:[TID]:AID:CTAG;

Example inputSwitch BITSOUT-A from the currently active timing source to the other timing source:

OPR-BITSOUTSW:NEWYORK:BITSOUT-A:CTAG23;


Field Purpose


AID Access identifier. BITS output ot act on.




BITS output BITSOUT-<bits> Identify the BITSOUT to switch where bits= A or B



OPR-EXT-CONTThe Operate External Controls command is used to turn on one or more of the four external control relays. The network element is equipped with four relays that can be configured for normally closed or normally open operation.

The contact number parameter is mandatory and grouping is allowed. The control TYPE parameter is not required, but can be used to parse the command.

For example, if the command is intended to turn on lights on relay 3, but relay 3 is actually connected to sprinklers, then including the value LIGHT in the CONTTYPE field would cause the command to fail (and prevent sprinklers from being accidentally turned on).

To turn off external control relays see the RLS-EXT-CONT command.


Input syntaxOPR-EXT-CONT:[TID]:AID:CTAG::[CONTTYPE];

CAUTIONBe careful not to turn on external controls that activate a potential danger such as sprinklers or miscellaneous controls connected to possibly hazardous systems or equipment.


Field Purpose


AID Access identifier. A group of values is acceptable.


CONTTYPE Optional parameter, the TYPE of control for which the control state is being set





CONTACT NO. 1 to 4 Identify the contact number

ALL ALL Activate all external relays. Not allowed when CONTTYPE is null.

Grouping #&#&#, #= 1 to 4 Identify multiple contacts

DSM number-%HLINK-HLINE-hslot#-hport#

DS1 service module or the MS DSM office audible alarmsnumber = 1 to 4, hslot# = 3 to 10hport# =1 to 4, HLINE = OC3 or OC12

ALL-%HLINK-HLINE-hslot#-hport#

All DS1 service module or MS DSM office audible alarmshslot# = 3 to 10, hport# = 1 to 4, HLINE = OC3 or OC12



CONTTYPE null Optional parameter (ALL). Not allowed when AID is ALL

AIRCOND Air conditioning

ENGINE Engine

FAN Fan

GEN Generator

HEAT Heat

LIGHT Light

MISC Miscellaneous

SPKLR Sprinkler



Example inputTurn on the air conditioner on relay 1 at network element WASHINGTON:

OPR-EXT-CONT:WASHINGTON:1:CTAG12::AIRCOND;

Turn on the heat on all external controls at network element NEWYORK: OPR-EXT-CONT:NEWYORK:ALL:CTAG12::HEAT;

Turn on relays 2 and 3 to activate the generator at network element SEATTLE: OPR-EXT-CONT:SEATTLE:2&3:CTAG12::GEN;



OPR-LAMP-TESTThe Operate Lamp Test command performs a lamp test on

• a specific DSM DS1x84 termination module on the DSM

• a specific aggregate circuit pack on the MS DSM

• all network element slots and associated DSMs/MS DSMs

For a DSM DS1x84 termination module or MS DSM aggregate circuit pack, the lamp test helps identify module locations and host link misconnections. The lamp test is directed to the host OCn port and sent to the DSM or MS DSM that is fiber connected to this OCn port.

Note 1: The DS1x84 termination module or MS DSM aggregate circuit pack must have a direct OAM link to the Host OCn port.

Note 2: A lamp test against the active aggregate circuit pack turns on the entire shelf except the standby aggregate circuit pack. A lamp test against the standby aggregate circuit pack turns on the aggregate circuit pack only.


Input syntaxOPR-LAMP-TEST:[TID]:AID:CTAG;


Field Purpose




Table 3-206AID description

AID type Command specific values

Purpose

DSM or MS DSM AID

%HLINK-HLINE-hslot#-hport#

Identify the DS1x84 TM or aggregate circuit pack where HLINE = OC3 or OC12, hslot# = 3 to 10, hport# = 1 to 4

ALL Perform a lamp test on all network element slots and attached DSMs or MS DSMs.



Example inputPerform a lamp test on network element BOSTON and all attached DSMs/MS DSMs:

OPR-LAMP-TEST:BOSTON:ALL:CTAG12;

Response block syntax<SID><DATE><TIME><CTAG> CMPLD



OPR-LPBK-EC1 The Operate Loopback EC-1 facility command instructs the equipment to set the specified EC-1 facility into loopback mode. Two types of loopbacks are provided: terminal and facility.

The facility must be put in an out-of-service state before a loopback will be permitted (see the RMV-EC1 command).

To release the facility loopback, use the RLS-LPBK-EC1 command.


Input syntaxOPR-LPBK-EC1:TID:AID:CTAG::,,,[LPBKTYPE];


Field Purpose


AID Access identifier. The facility to act on.


LPBKTYPE Loopback type



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



LPBKTYPE FACILITY (default) A signal received on the copper side of the facility is looped back towards the copper.

TERMINAL A signal received on the optical side of the facility is looped back towards the optics.



Example inputAt the SEATTLE network element, for the port 11 facility on the slot 5 EC-1 mapper, loopback the incoming signal from the optics back on to the optics:

OPR-LPBK-EC1:SEATTLE:EC1-5-11:CTAG::,,,TERMINAL;

At the SEATTLE network element, for the port 11 facility on the slot 5 EC-1 mapper, loopback the incoming signal from the copper back on to the copper:

OPR-LPBK-EC1:SEATTLE:EC1-5-11:CTAG::,,,FACILITY;



OPR-LPBK-ETH The Operate Loopback Ethernet command operates a facility or terminal loopback on an Ethernet facility (LAN port) of a 2x100BT-P2P, 8x100BT-P2P, 4x100FX-P2P, 2xGigE/FC-P2P, 2xGigE/FC-P2P-C or 2xGigE-P2P circuit pack.

The facility must be in an out-of-service management (OOS-MA) state before you can operate a loopback. See RMV-ETH on page 3-393 for information about putting an Ethernet facility in an OOS-MA state. See RLS-LPBK-ETH on page 3-366 for information about releasing a loopback.


Input syntaxOPR-LPBK-ETH:[TID]:AID:CTAG::,,,[LPBKTYPE];


Field Purpose


AID Access identifier. The Ethernet facility to put in loopback mode.





ETH ETH-slot#-port# Identify the Ethernet facility where slot# = 3 to 10port# = 1 or 2



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



Example inputOperate a facility loopback on LAN port 1 of the 2x100BT-P2P circuit pack in slot 7 of network element OTTAWA: OPR-LPBK-ETH:OTTAWA:ETH-7-1:CTAG::,,,FACILITY;



LPBKTYPE FACILITY (default) The Ethernet signal received on the LAN port is sent back out.

TERMINAL The SONET signal received on the corresponding WAN port is sent back out.

Note 1: To operate a terminal loopback, the LAN port must be in full duplex mode. See ED-ETH on page 2-227 to change the duplex mode of a LAN port.

Note 2: During a terminal loopback, the LAN port sends a link pulse, even though the port is out-of-service. Also, the INFRAMES, INOCTETS, OUTFRAMES, and OUTOCTETS measurements of the LAN port increment, in relation to the number of packets received by the WAN port.

Note 3: The 8x100BT-P2P on the MS DSM does not support facility loopbacks.



OPR-LPBK-FCThe Operate Loopback Fibre Channel command operates a facility or terminal loopback on a Fibre Channel facility (LAN port) of a 2xGigE/FC-P2P, 2xGigE/FC-P2P-C circuit pack. The facility must be in an out-of-service management (OOS-MA) state before you can operate a loopback. See RMV-FC on page 3-394 for information about putting a Fibre Channel facility in an OOS-MA state. See RLS-LPBK-FC on page 3-367 for information about releasing a loopback. Following the activation of the loopback, the FC generic OMs should be cleared (INIT-OM-IF) prior to running traffic. This is to guaranty there are no left over counts.


Input syntaxOPR-LPBK-FC:[TID]:AID:CTAG::,,,[LPBKTYPE];


Field Purpose


AID Access identifier. The Fibre Channel facility to put in loopback mode.





FC FC-slot#-port# Identify the Fibre Channel facility where slot# = 3 to 10port# = 1 or 2



Example inputOperate a facility loopback on LAN port 1 of the 2xGigE/FC-P2P circuit pack in slot 7 of network element OTTAWA:

OPR-LPBK-FC:OTTAWA:FC-7-1:CTAG::,,,FACILITY;



LPBKTYPE FACILITY (default) The Fibre Channel signal received on the LAN port is sent back out.

TERMINAL The SONET signal received on the corresponding WAN port is sent back out.

Note 1: To operate a terminal loopback, the LAN port must be in full duplex mode. See ED-ETH on page 2-227 to change the duplex mode of a LAN port.

Note 2: During a terminal loopback, the LAN port sends a link pulse, even though the port is out-of-service. Also, the INFRAMES, INOCTETS, OUTFRAMES, and OUTOCTETS measurements of the LAN port increment, in relation to the number of packets received by the WAN port.

Note 3: You can only operate a remote loopback if the port is In-Service. If a port is set to operate a remote loopback, this port will be blocked from going Out-of-Service.



OPR-LPBK-OC12 The Operate Loopback OC12 facility command instructs the equipment to set the specified OC12 facility into loopback mode. To release the facility loopback, use the RLS-LPBK-OC12 command. Loopback modes supported include terminal and facility. The facility must be put in an out-of-service state before a loopback is permitted (see the RMV-OC12 command).


Input syntaxOPR-LPBK-OC12:[TID]:AID:CTAG::,,,[LPBKTYPE];

Example inputAt the SEATTLE network element, loopback the signal leaving the OC-12 circuit pack to the associated incoming receiver:

OPR-LPBK-OC12:SEATTLE:OC12-11:CTAG23::,,,TERMINAL;


Field Purpose






AID type Command-specific values Details

OC-12 OC12-slot#-port# slot# = 3 to 12port# = 1 for OC-12, 1 to 4 for OC-12x4 STS



LPBKTYPE FACILITY (default)

The incoming signal into the OC-12 or OC-12x4 STS circuit pack is connected to the associated return transmitter.

TERMINAL The signal leaving the OC-12 or OC-12x4 STS circuit pack is connected to the associated incoming receiver.









Field Purpose







OC-192 OC192-slot# slot # = 11 or 12




The incoming signal into the OC-192 circuit pack is connected to the associated return transmitter.

TERMINAL The signal leaving the OC-192 circuit pack is connected to the associated incoming receiver.






Example inputAt the SEATTLE network element, loopback the incoming signal to the associated return transmitter on the specified OC-3 circuit pack:

OPR-LPBK-OC3:SEATTLE:OC3-3-1:CTAG23::,,,FACILITY;


Field Purpose







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



LPBKTYPE FACILITY (default) The incoming signal into the OC-3 circuit pack is connected to the associated return transmitter.

TERMINAL The signal leaving the OC-3 circuit pack is connected to the associated incoming receiver.









Field Purpose







OC-48 OC48-slot# slot# = 11 or 12 for OC-48slot# = 3 to 12 for OC-48 STS




The incoming signal into the OC-48 or OC-48 STS circuit pack is connected to the associated return transmitter.

TERMINAL The signal leaving the OC-48 or OC-48 STS circuit pack is connected to the associated incoming receiver.



OPR-LPBK-T1The Operate Loopback T1 facility command instructs the equipment to set the specified DS1 facility into loopback mode. Two types of loopback are provided: terminal and facility.

The facility must be put in an out-of-service state before a loopback is permitted (RMV-T1 command).

To release the facility loopback, use the RLS-LPBK-T1 command.

Note: DS3VTx12 circuit packs do not support DS1 facility loopbacks.


Input syntaxOPR-LPBK-T1:[TID]:AID:CTAG::,,,[LPBKTYPE];


Field Purpose




LPBKTYPE Loopback. See the Parameter descriptions table for details.



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

DS3V DS1-slot#-port#-t1# Identify DS1s on DS3VTx12 equipment whereslot# = 3, 5, 7, 9port# = 1 to 12t1# = 1 to 28

MS DSM DS1 facility

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

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



Example inputAt the SEATTLE network element, for the port 11 facility on the slot 5 DS1 mapper, loopback the incoming signal from the optics back on to the optics:

OPR-LPBK-T1:SEATTLE:DS1-5-11:CTAG::,,,TERMINAL;

At the SEATTLE network element, for the port 11 facility on the slot 5 DS1 mapper, loopback the incoming signal from the copper back on to the copper:

OPR-LPBK-T1:SEATTLE:DS1-5-11:CTAG::,,,FACILITY;




A signal received on the copper side of the facility is looped back towards the copper (default). The signal will only pass through the DS1-n mapper on the shelf that has the loopback.

Note: DS3VTx12 circuit packs do not support DS1 facility loopbacks.

TERMINAL A signal received on the optical side of the facility is looped back towards the optics. The signal will pass through the following cards on the shelf that has the loopback:OC-n => VTX => DSn-n => VTX => OC-n

2WAy Both directions are looped back (DSn line to DSn line and Network to network)



OPR-LPBK-T3The Operate Loopback T3 facility command instructs the equipment to set the specified DS3 facility into loopback mode. Two types of loopback are provided: terminal and facility.

The facility must be put in an out-of-service state before a loopback is permitted (RMV-T3 command).

To release the facility loopback, use the RLS-LPBK-T3 command.


Input syntaxOPR-LPBK-T3:[TID]:AID:CTAG::,,,[LPBKTYPE];


Field Purpose




LPBKTYPE Loopback type. See the Parameter descriptions table for details.



DS3 DS3-slot#-port# Identify the DS3 where slot# =3, 5, 7, or 9port# = 1 to 3 for DS3x3port# = 1 to 12 for DS3x12, DS3x12e, or DS3VTx12

DSM or MS DSM DS3 Facility AID


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



Example inputAt the NEWYORK network element, for the port 3 facility on the slot 5 DS3 mapper, loopback the incoming signal from the optics back on to the optics:

OPR-LPBK-T3:NEWYORK:DS3-5-3:CTAG::,,,TERMINAL;

At the NEWYORK network element, for the port 3 facility on the slot 5 DS3 mapper, loopback the incoming signal from the copper back on to the copper:

OPR-LPBK-T3:NEWYORK:DS3-5-3:CTAG::,,,FACILITY;



LPBKTYPE FACILITY (default) A signal received on the copper side of the facility is looped back towards the copper.

Note: The signal will only pass through the DS1-n mapper on the shelf that has the loopback.

TERMINAL A signal received on the optical side of the facility is looped back towards the optics.

Note: The signal will pass through the following cards on the shelf that has the loopback:

OC-n => VTX => DSn-n => VTX => OC-n

2WAy Both directions are looped back (DSn line to DSn line and Network to network)



OPR-PROTNSW-EQPTThe Operate Protection Switch Equipment command instructs the network element to initiate an equipment protection switch request for a DS1, a DS3, an EC1 or a DS3/EC1 circuit pack.

User switch requests initiated with this command remain active until they are released using the RLS-PROTNSW-EQPT command or overridden by a higher priority switch request.


Input syntaxOPR-PROTNSW-EQPT:[TID]:AID:CTAG::[SC];


Field Purpose




SC Switch command. See the Parameter descriptions table for details. Default is manual.



DS1 AID DS1-slot# Identify the DS1 whereslot# = 3 to 10


DS3V AID DS3V-slot# Identify the DS3VTx12 whereslot# = 3 to 10

DSM AID DS1TM-slot#-%HLINK-HLINE-hslot#-hport#

Identify the DS1 service module whereslot# = 1 or 2hslot# = 3 to 10hport# = 1 to 4



MS-DSM AID AGGOC3-slot-%HLINK-OC3-Hslot-Hport#


AGGOC3OC12-slot-%HLINK-HLINE-Hslot-Hport#


PECN-slot-%HLINK-Hline-Hslot-Hport


EC1 AID EC1-slot# Identify the EC-1 whereslot# = 3 to 10





Example input Manually switch the DS1 in slot 5 to protection mode: OPR-PROTNSW-EQPT:NEWYORK:DS1-5:CTAG23::MAN;


Parameter Possible values AID Description

SC MAN (default) DS1#4 to 10

DS3 #3 to 10

If the AID identifies a working circuit pack, then service will be transferred from it to the protection circuit pack if and only if the latter is neither failed nor servicing a higher or equal priority request.

DS1#3 Not applicable.

FRCD DS1#4 to 10

DS3 #3 to 10

If the AID identifies a working circuit pack, then service will be transferred from it to the protection circuit pack if and only if the latter is not servicing a higher or equal priority request.

If the AID identifies a working circuit pack that has already been switched to protection, no switch occurs; however, the priority of the existing switch will be raised to “forced”.

DS1#3 Not applicable.

LOCKOUT DS1#3 If the AID identifies the protection circuit pack (DS1-3) then the command will prevent any working circuit pack from switching to the protection circuit pack. If a working circuit pack is already on protection, it will be switched back.

DS1#4 to 10 If the AID identifies a working circuit pack, then the command will prevent the working circuit pack from switching to protection. If the working circuit pack is on protection, it will be switched back.



OPR-PROTNSW-OC12The Operate Protection Switch OC-12 command instructs the network element to initiate a protection switch request for an OC-12 or OC-12x4 STS circuit pack. You can initiate a protection switch request only for network elements in a linear system.

User switch requests initiated with this command remain active until they are released using the RLS-PROTNSW-OC12 command or overridden by a higher priority switch request.


Input syntaxOPR-PROTNSW-OC12:[TID]:AID:CTAG::[SC];


Field Purpose




SC Switch Command. See the Parameter descriptions table for details.



OC-12 AID OC12-slot#-port# Identify the OC-12slot# = 3 to 12port# = 1 for OC-12port# = 1 to 4 for OC-12x4 STS



Example input Manually switch the OC-12 in slot 9 to protection mode: OPR-PROTNSW-OC12:NEWYORK:OC12-9-1:CTAG23::MAN;

Lockout the OC-12 protection circuit pack in slot 10: OPR-PROTNSW-OC12:NEWYORK:OC12-10-1:CTAG23::LOCKOUT;



SC MAN (default) If the AID identifies a working circuit pack, then service will be transferred from it to the protection circuit pack if and only if the latter is neither failed nor servicing a higher or equal priority request.

FRCD If the AID identifies a working circuit pack, then service will be transferred from it to the protection circuit pack if and only if the latter is not servicing a higher or equal priority request.


LOCKOUT (only available on the Protection circuit pack)

If the AID identifies the protection circuit pack then the command will prevent any working circuit pack from switching to the protection circuit pack. If a working circuit pack is already on protection, it will be switched back.



OPR-PROTNSW-OC192The Operate Protection Switch OC-192 command instructs the network element to initiate a protection switch request for an OC-192 circuit pack. You can initiate a protection switch request only for network elements in a linear system.





Field Purpose




SC Switch command



OC-192 AID OC192-slot# Identify the OC-192 where slot# = 11, 12



Example input Manually switch the OC-192 in slot 11 to protection mode: OPR-PROTNSW-OC192:NEWYORK:OC192-11:CTAG23::MAN;

Lockout the OC-192 protection circuit pack in slot 12:

OPR-PROTNSW-OC192:NEWYORK:OC192-12:CTAG23::LOCKOUT;



SC MAN (default)




LOCKOUT (valid only for the protection circuit pack in a 1+1 linear system)


LOCKOUT_PROT(valid only for BLSR systems)

Prevents the use of the span of the ring for any protection activity and prevents switches anywhere around the ring.

LOCKOUT_WRKG(valid only for BLSR systems)

Prevents the working channels over the addressed span from accessing protection channels for a switch by disabling the node’s capability to request a ring protection switch.



OPR-PROTNSW-OC3The Operate Protection Switch OC-3 command instructs the network element to initiate a protection switch request for an OC-3 or an OC-3x4 circuit pack. You can initiate a protection switch request only for network elements in a linear system.





Field Purpose




SC Switch Command. See the Parameter descriptions table for details. Default is manual.



OC-3 AID OC3-slot# -port# Identify the OC-3 where slot# = 3 to 10port# = 1 for OC-3port# = 1 to 4 for OC-3x4



Example input Manually switch the OC-3x4 in slot 9 to protection mode: OPR-PROTNSW-OC3:NEWYORK:OC3-9-1:CTAG23::MAN;

Lock out the OC-3x4 protection circuit pack in slot 10: OPR-PROTNSW-OC3:NEWYORK:OC3-10-1:CTAG23::LOCKOUT;



SC MAN (default) If the AID identifies a working circuit pack, then service will be transferred from it to the protection circuit pack if and only if the latter is neither failed nor servicing a higher or equal priority request.



LOCKOUT (only available on the Protection circuit pack




OPR-PROTNSW-OC48The Operate Protection Switch OC-48 command instructs the network element to initiate a protection switch request for an OC-48 or OC-48 STS circuit pack. You can initiate a protection switch request only for network elements in a linear system.





Field Purpose




SC Switch command



OC-48 AID OC48-slot# Identify the OC-48 where slot# = 11, 12 for OC-48slot# = 3 to 12 for OC-48 STS



Example input Manually switch the OC-48 in slot 11 to protection mode: OPR-PROTNSW-OC48:NEWYORK:OC48-11:CTAG23::MAN;

Lockout the OC-48 protection circuit pack in slot 12:

OPR-PROTNSW-OC48:NEWYORK:OC48-12:CTAG23::LOCKOUT;



SC MAN (default)




LOCKOUT (valid only for the protection circuit pack in a 1+1 linear system)


LOCKOUT_PROT(valid only for BLSR systems)

Prevents the use of the span of the ring for any protection activity and prevents switches anywhere around the ring.

LOCKOUT_WRKG(valid only for BLSR systems)

Prevents the working channels over the addressed span from accessing protection channels for a switch by disabling the node’s capability to request a ring protection switch.



OPR-PROTNSW-STS1The Operate Protection Switch STS-1 command instructs the network element to initiate an STS-1 path protection switch request for an OC-12 or OC-12x4 STS circuit pack.

Two levels of priority are supported: manual and forced. Lockout is not supported because STS-1 circuits are non-revertive.

User switch requests initiated with this command remain active until they are released using the RLS-PROTNSW-STS1 command or overridden by a higher priority switch request.


Input syntaxOPR-PROTNSW-STS1:[TID]:AID:CTAG::[SC];


Field Purpose







Example input Manually switch the STS-1 of the OC-3 in slot 9 port 2 sts 1 to protection mode:

OPR-PROTNSW-STS1:NEWYORK:OC3-9-2-1:CTAG23::MAN;



STS-1 facility AID

OC3-slot#-port#-sts# Identify the STS-1 path on the OC-3slot# = 3 to 10port# = 1 to 4sts# = 1 to 3

OC12-slot#-port#-sts# Identify the STS-1 path on the OC-12 or OC-12x4 STSslot# = 3 to 12port# = 1 for OC-12port# = 1 to 4 for OC-12x4 STSsts# = 1 to 12

OC48-slot#-sts# Identify the STS-1 path on the OC-48 or OC-48 STSslot# = 11, 12 for OC-48slot# = 3 to 12 for OC-48 STSsts# = 1 to 48

OC192-slot#-sts# Identify the STS-1 path on the OC-192 slot# = 11, 12sts# = 1 to 192

Note: ALL is not a valid AID option.



Description

SC MAN (default)






OPR-PROTNSW-STS12CThe Operate Protection Switch STS-12c command instructs the network element to initiate an STS-12c path protection switch request.

Two levels of priority are supported: manual and forced. Lockout is not supported.

User switch requests initiated with this command remain active until they are released using the RLS-PROTNSW-STS12C command or overridden by a higher priority switch request.


Input syntaxOPR-PROTNSW-STS12C:[TID]:AID:CTAG::[SC];


Field Purpose







STS-12c facility AID

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

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

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




Example input Manually switch the STS-12c signal of the OC-12 in slot 9 sts 1 to protection mode: OPR-PROTNSW-STS12C:NEWYORK:OC12-9-1:CTAG23::MAN;



Description

SC MAN (default)

If the AID identifies a working path, then service will be transferred from it to the protection path if and only if the latter is neither failed nor servicing a higher or equal priority request.

FRCD If the AID identifies a working path, then service will be transferred from it to the protection path if and only if the latter is not servicing a higher or equal priority request.










Field Purpose








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

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







Description

SC MAN (default)






OPR-PROTNSW-STS3CThe Operate Protection Switch STS-3c command instructs the network element to initiate an STS-3c path protection switch request for an OC-3 path.






Field Purpose







Example input Manually switch the STS-3c signal of the OC-3 in slot 9 port 1 sts 1 to protection mode:

OPR-PROTNSW-STS3C:NEWYORK:OC3-9-1-1:CTAG23::MAN;



STS-3c facility AID

OC3-slot#-port#-sts# Identify the STS-3c path on the OC-3 slot# = 3 to 10port# = 1 to 4sts# = 1

OC12-slot#-port#-sts# Identify the STS-3c path on the OC-12 or OC-12x4 STSslot# = 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 path on the OC-48 slot# = 11, 12 for OC-48slot# = 3 to 12 for OC-48 STSsts# = 1, 4, 7, 10, ...46

OC192-slot#-sts# Identify the STS-3c path on the OC-192 slot# = 11, 12sts# = 1, 4, 7, 10, ...190




Description

SC MAN (default)












Field Purpose








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







Description

SC MAN (default) If the AID identifies a working path, then service will be transferred from it to the protection path if and only if the latter is neither failed nor servicing a higher or equal priority request.





OPR-PROTNSW-VT1The Operate Protection Switch VT1 command instructs the network element to initiate a VT1.5 path protection switch request.

Two levels of priority are supported: manual and forced. Lockout is not supported because VT1.5 circuits are non-revertive.

Manual and forced switch requests initiated using this command remain active until they are released using the RLS-PROTNSW-VT1 command or overridden by a higher priority switch request.


Input syntaxOPR-PROTNSW-VT1:[TID]:AID:CTAG::[SC];


Field Purpose







Example inputRequest forced protection switching for VT1 #1, VTG#1, STS1#1, port 2 in slot 10: OPR-PROTNSW-VT1:SEATTLE:OC3-10-2-1-1-1:CTAG45::FRCD;



VT1.5 facility AID


Identify the VT1.5 path on the OC-3 where slot# = 3 to 10port# = 1 to 4sts# = 1 to 3vtg# = 1 to 7vt# = 1 to 4


Identify the VT1.5 path on the OC-12 slot# = 3 to 12port# = 1sts# = 1 to 12vtg# = 1 to 7vt# = 1 to 4


Identify the VT1.5 path on the OC-48 slot# = 11, 12 sts# = 1 to 48vtg# = 1 to 7vt# = 1 to 4



SC MAN (default) Manual VT1.5 path protection switch. Service is transferred from the VT1.5 path identified, to the alternate path only if the path selector is not satisfying a higher or equal priority request.

FRCD Forced VT1.5 path protection switch. Service is transferred from the VT1.5 path identified, to the alternate path only if the path selector is not satisfying a higher or equal priority request.



OPR-SYNCSW The Operate Synchronization Switch command instructs the network element to switch synchronization timing reference signals from primary to secondary, or vice versa. The switch completes only if the quality of the two references are the same. The network element always chooses the best quality timing reference for its synchronization reference. Use the RTRV-TMREFIN command to retrieve timing references.

Use the SET-SYNCSTIN command to set the synchronization status of the incoming synchronization signal.

User synchronization switches initiated using this command remain active until another synchronization switch is activated or they are overridden by a synchronization reference failure.

Primary and secondary timing references are assigned using the SET-TMREFIN command.


Input syntaxOPR-SYNCSW:[TID]::CTAG;

Example inputSwitch synchronization from the currently active timing source to the other timing source: OPR-SYNCSW:NEWYORK::CTAG23;


Field Purpose





OPR-TARP-TEFThe Operate TARP TEF (TARP Echo Function) command is used to support TEF for troubleshooting. It is similar to the ping function in the IP network.


Input syntaxOPR-TARP-TEF:[TID]::CTAG::ADDRTYPE,ADDRESS:[ITERATION=Domain][,RATE=Domain][,TIMEOUT=Domain];

Table 3-268Syntax definitions

Field Purpose



ADDRTYPE Remote address type can be TL1 System Identifier Type Address (TID) or Network Service Access Point Address Type (NSAP)

ADDRESS ADDRESS is the value of ADDRTYPE.If ADDRTYPE is TID, ADDRESS is a string with a maximum of 20 characters. (the SID name)If ADDTYPE is NSAP, ADDRESS is a hexadecimal number with a maximum of 40 digits. (the NSAP number)

ITERATION Number TARP Type 5 messages to be transmitted

RATE Rate of sent requests

TIMEOUT Maximum echo waiting period



Input examplePerform a TARP-TEF:

OPR-TARP-TEF:OTTAWA::CTAG12::TID,NEWYORK;

Example outputTEF:SEQ=1,TID=NEWYORK,NSAP=490000000075D0082E00,TIME=70TEF:SENT 1, RECEIVED 1,MTNTM/AVETM/MAXTM=70/70/70, SUCCESS=100%



ITERATION Integer from 1 to 65535

null

Iterations of number TARP Type 5messages to be transmitted

Default: 1

RATE Integer from 1000 to 180000

null

Rate of sent requestsA decimal number that ranges from 1000 to 180000 msecWait for a response before sending each request (in milliseconds)

Default: 1000

TIMEOUT Integer from 1000 to 180000

null

The maximum time to wait for a response to each echo request (in milliseconds)A decimal number that ranges from 1000 to 180000 msec

Default: 1500

Table 3-270Response parameter descriptions

Parameter Possible value Description

TEF A string with a maximum of 20 characters

TARP echo function indicator

SEQ A decimal number Sequence number

TID A string with a maximum of 20 characters

Target identifier

NSAP A number with a maximum of 40 hexadecimal digits

NSAP

TIME A decimal number Response time in milliseconds



OPR-TOD-SYNCThe Operate Time of Day Synchronization command can be used to force the the SP to request the time from the current NP time of day (TOD) server.

The Operate Time of Day Synchronization command can also be used on the NP to force a the NP to attempt to reference it’s internal clock to one of its provisioned external time servers.


Input syntax OPR-TOD-SYNC:TID::CTAG;

Example inputOperate a time of day synchronization on the New York network element, NP.

OPR-TOD-SYNC:NEWYORK::CTAG12;


Field Purpose





REPT^ALM^COMReport Alarm Com is generated by a network element or network processor to report alarms that affect the network processor or the shelf as a whole. In general, an alarmed event causes a standing condition and has immediate or potential impact on the operation or performance of the entity. Some form of maintenance effort is required to restore normal operation or performance of the entity after the event has occurred.

Message formatAll parameters in this message are either positional or name-defined.

<cr> <lf> <lf>^^^<sid>^<date>^<time> <cr> <lf><almcde>^<atag>^REPT^ALM^COM <cr> <lf><rspblk> + ;

The message must contain at least one occurrence of <rspblk>. Its format is: ^^^"<aid>:<ntfcncde>,<condtype>,<srveff>,<ocrdat>,<ocrtm>, <locn>,<dirn>:<conddescr>" <cr> <lf>;


Field Purpose

<sid> The network element or NPx source identifier

<date> In the format yy-mm-dd

<time> In the format hh:mm:ss

<almcde> Possible alarm code values in decreasing order of severity: *C (Critical alarm) ** (Major alarm) *^ (Minor alarm) A^ (Automatic message)

<atag> Automatic tag, the numerical identification of the message

<rspblk> Response block. See the following tables for details.





Shelf SHELF Identify the network element

SPx SP Identify the shelf processor

NPx NP Identify the network processor

Fan FAN-slot# Identify the fan unit whereslot# = 1 to 3

BITS signal BITS-ABITS-B

Identify the BITS A or B input or output

Timing reference DS1-slot#-port# Identify the timing reference whereslot# = 4 to 10, port# = 1 to 12

EC1-slot#-port# Identify the timing reference whereslot# = 3, 5, 7, 9, port# = 1 to 12

OC3-slot#-port# Identify the timing reference whereslot# = 3 to 10, port# = 1 to 4


OC48-slot# Identify the timing reference whereslot# = 3 to 12

OC192-slot# Identify the timing reference whereslot# = 11 or 12

TBOS display display-shelf Identify the remote network element wheredisplay = 1 to 16shelf = user-defined shelf name

Power cards PWR-APWR-B

Identify the power cards


Parameter Values Applicable AIDs Description

<ntfcncde> CRMJMNCL

all Critical alarmMajor alarmMinor alarmCleared alarm



Example messageAt 9 pm on March 17, 2002, the timing reference was lost for the BITS out A signal:

<cr> <lf> <lf> OC3NE01 02-03-17 21:00:00 <cr> <lf>* 123 REPT ALM COM <cr> <lf>

"BITS-A,COM:MN,SYNCPRI,NSA,03-17,21-00-00,NEND,NA:\"Loss of BITSout-A Pri. Timing Ref.\"";<cr> <lf>

<condtype> INC BITS signal Incoming failure condition

SWTOINT Shelf Switch to internal synchronization

BPV BITS signal BITS In A or B bipolar violations >10-3

AIS BITS signal BITS In A or B receive AIS

LOF BITS signal BITS In A or B loss of frame

LOS BITS signal BITS In A or B loss of signal

FA Shelf Power failure

null SPx, NPx Software upgrade

SWFTDWN SPx, NPx Software download

SYNCPRI BITS signal timing ref Primary synchronization reference failure

SYNCSEC BITS signal timing ref Secondary synchronization reference failure

INT all Internal software failure

<srveff> SA or NSA all Service affecting or non-service affecting

<ocrdat> mm-dd all The date when the alarm occurred

<ocrtm> hh-mm-ss all The time when the alarm occurred

<locn> NEND all Failure at the near end of the system

FEND null Failure at the far end of the system

null SPx, NPx No failure in the system

<dirn> NA all Not applicable

RCV BITs signal null Receive failure

null SPx, NPx No failure in the system

<conddescr> Character string all The detailed text description of the trouble





REPTÂLMÊC1Report Alarm EC-1 is generated by a network element to report the occurrence of EC-1 alarmed events. In general, an alarmed event causes a standing condition and has immediate or potential impact on the operation or performance of the entity. Some form of maintenance effort is required to restore normal operation or performance of the entity after the event has occurred.


<cr> <lf> <lf>^^^<sid>^<date>^<time> <cr> <lf><almcde>^<atag>^REPTÂLMÊC1 <cr> <lf><rspblk> + ;

The message must contain at least one occurrence of <rspblk>. Its format is:

^^^"<aid>:<ntfcncde>,<condtype>,<srveff>,<ocrdat>,<ocrtm>, <locn>,<dirn>:<conddescr>" <cr> <lf>


Field Purpose

<sid> The network element source identifier








EC-1 facility AID EC1-slot#-port# Identify EC-1 facility whereslot# = 3, 5, 7, or 9port# = 1 to 12



Example messages At 9 pm on October 17, 2001, the following alarm report was generated for the EC-1x12 in slot 7, port 1:

<cr> <lf> <lf> OC3NE01 01-10-17 21:00:00 <cr> <lf>* 123 REPT ALM EC1 <cr> <lf>

"EC1-7-1:MN,INT,SA,10-17,21-00-00,NEND,RCV:\"EC1 Loopback Active\"";<cr> <lf>


Parameter Values Description

<ntfcncde> CRMJMNCL

Critical alarmMajor alarmMinor alarmCleared alarm

<condtype> LOS

LOF

INT

INC

AIS

null

Loss of signal

Loss of frame

Internal hardware fault/failure

Incoming failure condition

Alarm indication signal detected

Not applicable

<srveff> SA NSA

Service affecting Non service affecting

<ocrdat> mm-dd The date when the alarm occurred

<ocrtm> hh-mm-ss The time when the alarm occurred

<locn> NEND Near end

<dirn> NA RCV

Not applicable Receive direction only

<conddescr> character string The detailed text description of the trouble



REPTÂLMÊNVReport Alarm Environment is generated by a network element to report the occurrence of an environmental alarm.


<cr> <lf> <lf>^^^<sid>^<date>^<time> <cr> <lf><almcde>^<atag>^REPTÂLMÊNV <cr> <lf><rspblk> + ;

The message must contain at least one occurrence of <rspblk>. Its format is: ^^^"<aid>:<ntfcncde>,<almtype>,<ocrdat>,<ocrtm>,<almmsg><cr> <lf>;


Field Purpose








AID type Purpose

1 to 16 Identify the contact




Parameter Values Applicable AIDs

Description

<ntfcncde> CRMJMNCL

all Critical alarmMajor alarmMinor alarmCleared alarm

<almtype> AIRCOMPR all Air compressor failure

AIRCOND all Air conditioning failure

AIRDRYR all Air dryer failure

BATDSCHRG all Battery discharging

BATTERY all Battery failure

CLFAN all Cooling fan failure

ENGINE all Engine failure

ENGOPRG all Engine operating

EXPLGS all Explosive gas

FIRDETR all Fire detector failure

FIRE all Fire

FLOOD all Flood

FUSE all Fuse failure

GEN all Generator failure

HIAIR all High airflow

HIHUM all High humidity

HITEMP all High temperature

HIWTR all High water

INTRUDER all Intrusion



Example message<cr> <lf> <lf> OC3NE01 01-10-17 21:00:00 <cr> <lf>* 123 REPT ALM ENV <cr> <lf>

"1:MN,FLOOD,10-17,21-00-00,\"Flood\"";<cr> <lf>

<almtype> LWBATVG all Low battery voltage

LWFUEL all Low fuel

LWHUM all Low humidity

LWPRES all Low cable pressure

LWTEMP all Low temperature

LWWTR all Low water

MISC all Miscellaneous

OPENDR all Open door

PUMP all Pump failure

POWER all Commercial power failure

PWR-48 all -48 V power supply failure

RECT all Rectifier failure

RECTHI all Rectifier high voltage

RECTLO all Rectifier low voltage

SMOKE all Smoke

TOXICGAS all Toxic gas

VENTN all Ventilation system failure



<almmsg> character string all The detailed text description of the trouble


Parameter Values Applicable AIDs

Description



REPTÂLMÊQPTReport Alarm Equipment is generated by a network element to report the occurrence of alarmed equipment related events. In general, an alarmed event causes a standing condition and has immediate or potential impact on the operation or performance of the entity. Some form of maintenance effort is required to restore normal operation or performance of the entity after the event has occurred.


<cr> <lf> <lf>^^^<sid>^<date>^<time> <cr> <lf><almcde>^<atag>^REPTÂLMÊQPT <cr> <lf><rspblk> + ;




Field Purpose











2xGigE eqpt 1GE-slot# Identify 2xGigE equipment where slot# = 3, 5, 7, 9

2xGigE 2.5G eqpt

1GE25G-slot# Identify 2xGigE 2.5G equipment where slot# = 3, 5, 7, 9

4x100BT eqpt IPT100-slot# Identify 4x100BT equipment where slot# = 3 to 10

4x100FX eqpt 100FX-slot# Identify 4x100FX equipment where slot# = 3 to 10

100BTFOS AID 100BTFOS-slot# Identify 2x100BT-P2P equipment where slot# = 3 to 10

100FOST AID 100FOST-slot# Identify 8x100BT-P2P equipment where slot# = 3 to 10

100FOSO AID 100FOSO-slot# Identify 4x100FX-P2P equipment where slot# = 3 to 10

1GFOS AID 1GFOS-slot# Identify 2xGigE/FC-P2P, 2xGigE-P2P, or 2xGigE/FC-P2P-C equipment where slot# = 3 to 10

DS1 eqpt DS1-slot# Identify DS1 equipment where slot# = 3 to 10

DSM eqpt DSnTM-slot#-%HLINK-OC3-hslot#-hport#

Identify the DS1 or DS3 equipment on the DSM where slot# = 1, 2, hslot# = 3 to 10, hport# = 1 to 4

DS3 eqpt DS3-slot# Identify DS3x3, DS3x12, or DS3x12e equipmentwhere slot# = 3 to 10

DS3VT AID DS3V-slot# Identify DS3VTx12 equipment where slot# = 3 to 10

EC1 eqpt EC1-slot# Identify EC-1 equipment where slot# = 3 to 10

DS3/EC-1 eqpt DS3EC1-slot# Identify DS3/EC-1x12 equipment where slot# = 3 to 10

ILAN eqpt ILAN Identify ILAN equipment

OC3 eqpt OC3-slot# Identify OC-3 or OC-3x4 equipment where slot# = 3 to 10

OC12 eqpt OC12-slot# Identify OC-12 or OC-12x4 STS equipment where slot# = 3 to 12

OC48 eqpt OC48-slot# Identify OC-48 equipment where slot# = 3 to 12

OC192 ept OC192-slot# Identify OC-192 equipment where slot# = 11 or 12

PSC eqpt PSC Identify the protection switch controller

PSX eqpt PSX Identify the protection switch extender

SPx eqpt SP Identify the shelf processor

CLX eqpt CLX-slot# Identify the VTX48, VTX40/10, or STX-192 where slot# =13 or 14





<ntfcncde> CR, MJ, MN, or CL all Critical, Major, Minor or Cleared alarm

<condtype> EQPT all Critical alarm caused by equipment failure

INT all Internal hardware fault/failure

INC OC12-slot# Incoming failure condition whereslot# = 3 to 12

IPT100-slot# Incoming failure condition where slot# = 3 to 10

100FX-slot# Incoming failure condition where slot# = 3 to 10

1GE-slot# Incoming failure condition whereslot# = 3, 5, 7, 9

1GE25G-slot# Incoming failure condition whereslot# = 3, 5, 7, 9

<srveff> SANSA

all Service affectingNot service affecting





RCV OC12-slot# Incoming failure condition where slot# = 3 to 12

IPT100-slot# Incoming failure condition where slot# = 3 to 10

100FX-slot# Incoming failure condition where slot# = 3 to 10

1GE-slot# Incoming failure condition where slot# = 3, 5, 7, 9

1GE25G-slot# Incoming failure condition whereslot# = 3, 5, 7, 9

NEND DS3-slot# Near end direction only where slot# = 3 to 10

<conddescr> Character string all The detailed text description of the trouble



Example messageAt 9 p.m. on October 17, 2001, an automatic diagnostic ran and passed on the DS1 in slot 5:

<cr> <lf> <lf> OC3NE01 01-10-17 21:00:00 <cr> <lf>* 123 REPT ALM EQPT <cr> <lf>

"DS1-5:CR,INT,NSA,10-17,21-00-00,NEND,NA:\"Circuit Pack Failed\"";<cr> <lf>



REPT^ALM^FACReport Alarm Facility is generated by a network processor to report the occurrence of alarmed facility related events. In general, an alarmed event causes a standing condition and has immediate or potential impact on the operation or performance of the entity. Some form of maintenance effort is required to restore normal operation or performance of the entity after the event has occurred.


<cr> <lf> <lf>^^^<sid>^<date>^<time> <cr> <lf><almcde>^<atag>^REPT^ALM^FAC <cr> <lf><rspblk> + ;




Field Purpose









Example messageAt 9 p.m. on October 17, 2001, the NP ILAN1:

<cr> <lf> <lf> NPOC3NE01 01-10-17 21:00:00 <cr> <lf>* 123 REPT ALM FAC<cr> <lf>

"ILAN1:MN,INT,NSA,10-17,21-00-00,NEND,NA:\"Facility Failure\"";<cr> <lf>



NPx facility AID ILAN1ILAN2COLANILANSPILANNPX25

Identify the NPx facility



<ntfcncde> CRMJMNCL


<condtype> INT Internal software fault/failure

<srveff> NSA Non service affecting




<dirn> NA Not applicable

<conddescr> character string

The detailed text description of the trouble



REPTÂLMÔC12Report Alarm OC-12 is generated by a network element to report the occurrence of OC-12 alarmed events. In general, an alarmed event causes a standing condition and has immediate or potential impact on the operation or performance of the entity. Some form of maintenance effort is required to restore normal operation or performance of the entity after the event.


<cr> <lf> <lf>^^^<sid>^<date>^<time> <cr> <lf><almcde>^<atag>^REPTÂLMÔC12 <cr> <lf><rspblk> + ;




Field Purpose











Purpose

OC-12 facility AID

OC12-slot#-port# Identify the OC-12 or OC-12x4 STS whereslot# = 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 OC12 facility AID

OC12-slot-1-%HLINK-OC12-hslot#-hport#

Identify the OC-12 whereslot# = 1, 2hslot# = 3 to 10, hport# = 1 to 4



<ntfcncde> CRMJMNCL


<condtype> LOS Loss of signal

LOF Loss of frame

INT Internal hardware fault/failure

INC Incoming failure condition

AIS Alarm indication signal detected

APSC Automatic protection switch channel condition

APSMM Automatic protection switch mode mismatch condition

<srveff> SA Service affecting

NSA Non service affecting




<dirn> NA RCV






Example message<cr> <lf> <lf> OC12NE01 01-10-17 21:00:00 <cr> <lf>*C 123 REPT ALM OC12 <cr> <lf>

"OC12-10-1:C,INC,SA,10-17,21-00-00,NEND,RCV:\"OC12 Signal Degrade\"" ;<cr> <lf>



REPT^ALM^OC192Report Alarm OC-192 is generated by a network element to report the occurrence of OC-192 alarmed events. In general, an alarmed event causes a standing condition and has immediate or potential impact on the operation or performance of the entity. Some form of maintenance effort is required to restore normal operation or performance of the entity after the event has occurred.





Table 3-290Syntax defintion

Field Purpose









OC-192 facility AID





"OC192-11:C,INC,SA,10-17,21-00-00,NEND,RCV:\"OC192 Signal Degrade\"" ;<cr> <lf>



<ntfcncde> CRMJMNCL



LOF Loss of frame






SWEX Switch exerciser failure condition

RSWS Traffic squelched condition





<locn> NEND FEND

Near end Far end

<dirn> NA RCVTRMT

Not applicable Receive direction only Transmit direction only





REPT^ALM^OC3Report Alarm OC-3 is generated by a network element to report the occurrence of OC-3 alarmed events. In general, an alarmed event causes a standing condition and has immediate or potential impact on the operation or performance of the entity. Some form of maintenance effort is required to restore normal operation or performance of the entity after the event.






Field Purpose










"OC3-10-1:C,INC,SA,10-17,21-00-00,NEND,RCV:\"OC3 Signal Degrade\"" ;<cr> <lf>



OC-3 facility AID

OC3-slot#-port# Identify the OC-3 facility whereslot# = 3 to 10, port# = 1 to 4

OC3-slot#-port#-%HLINK-OC3-hslot#-hport#

Identify the OC-3 facility on the DSM interface whereslot# = 1 or 2, port# = 1 to 84, hslot# = 3 to 10, hport# = 1 to 4



<ntfcncde> CR, MJ, MNCL

Critical, Major, Minor, or Cleared Alarm

<condtype> LOS

LOF

INT

INC

AIS

APSC

APSMM

Loss of signal

Loss of frame




Automatic protection switch channel condition

Automatic protection switch mode mismatch condition

<srveff> SA

NSA

Service affecting

Non service affecting




<dirn> NA RCV





REPT^ALM^OC48Report Alarm OC-48 is generated by a network element to report the occurrence of OC-48 alarmed events. In general, an alarmed event causes a standing condition and has immediate or potential impact on the operation or performance of the entity. Some form of maintenance effort is required to restore normal operation or performance of the entity after the event has occurred.






Field Purpose









OC-48 facility AID

OC48-slot# Identify the OC-48 whereslot# = 3 to 12




"OC48-11:C,INC,SA,10-17,21-00-00,NEND,RCV:\"OC48 Signal Degrade\"" ;<cr> <lf>



<ntfcncde> CRMJMNCL



LOF Loss of frame






SWEX Switch exerciser failure condition

RSWS Traffic squelched condition





<locn> NEND FEND

Near end Far end

<dirn> NA RCVTRMT






REPT^ALM^SECUReport Alarm Security is generated when the shelf processor or network processor detects a security alarm, for example, an incoming network access violation or intrusion attempt. The message is generated to users with a UPC level of 4 or higher.

Security alarms have an impact of major, non-service affecting. Security alarms can be manually cleared by accounts with an UPC level of 4 or higher. Intrusion attempt alarms are also automatically cleared when the lockout expires.


<cr> <lf> <lf>^^^<sid>^<date>^<time> <cr> <lf>^<atag>^REPT^ALM^SECU <cr> <lf><rspblk> + ;




Field Purpose








Purpose

SPx SP Identify the shelf processor




Example messages <cr> <lf> <lf> OC3NE01 01-10-17 21:00:00 <cr> <lf>123 REPT ALM SECU <cr> <lf>

"SP:MJ,INT,NSA,10-17,21-00-00,NEND,NA:\"Intrusion Attempt\"" ;<cr> <lf>



<ntfcncde> MJCL

Major alarmCleared alarm

<condtype> INT Internal

<srveff> NSA Non-service affecting






The detailed text description of the alarm



REPT^ALM^STS1Report Alarm STS-1 is generated by a network element to report the occurrence of STS-1 alarmed events. In general, an alarmed event causes a standing condition and has immediate or potential impact on the operation or performance of the entity. Some form of maintenance effort is required to restore normal operation or performance of the entity after the event has occurred.


<cr> <lf> <lf>^^^<sid>^<date>^<time> <cr> <lf><almcde>^<atag>^REPT^ALM^STS1<cr> <lf><rspblk> + ;




Field Purpose











STS path AID

OC3-slot#-port#-sts# Identify the STS-1 whereslot# = 3 to 10port# = 1 to 4sts# = 1 to 3

OC12-slot#-port#-sts# Identify the STS-1 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

OC12-slot#-1-sts#-%HLINK-hslot#-hport#

Identify the STS-1 whereslot# = 1, 2sts# = 1 to 12hslot# = 3 to 10hport# = 1 to 4

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

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

EC1-slot#-port# Identify STS-1 whereslot# = 3, 5, 7, 9port# = 1 to 12



OC3-slot#-1-sts#-%HLINK-OC3-hslot#-hport#



MS DSM STS path AID

WAN-slot-port-sts-%HLINK-Hline-hslot#-hport#

Identify the STS-1 facility on the WAN port whereslot# = 3 to 6port# = 1 to 8sts# = 1Hline = OC3 or OC12hslot# = 3 to 10hport# = 1 to 4



<ntfcncde> CRMJMNCL


<condtype> SLMF Signal label mismatch failure



<srveff> SA

NSA

Service affecting






Example message<cr> <lf> <lf> OC3NE01 01-10-17 21:00:00 <cr> <lf>*C 123 REPT ALM STS1 <cr> <lf>

"OC3-9-1-1:CR,AIS,SA,10-17,21-00-00,NEND,RCV:\"STS Rx AIS\"" ; <cr> <lf>




<dirn> RCV Receive direction only






REPT^ALM^STS12CReport Alarm STS-12c is generated by a network element to report the occurrence of STS-12c alarmed events. In general, an alarmed event causes a standing condition and has immediate or potential impact on the operation or performance of the entity. Some form of maintenance effort is required to restore normal operation or performance of the entity after the event has occurred.


<cr> <lf> <lf>^^^<sid>^<date>^<time> <cr> <lf><almcde>^<atag>^REPT^ALM^STS12C <cr> <lf><rspblk> + ;




Field Purpose




<almcde> Possible alarm code values in decreasing order of severity:** (Major alarm) *^ (Minor alarm) A^ (Automatic message)





Example message<cr> <lf> <lf> OC12NE01 01-10-17 21:00:00 <cr> <lf>*C 123 REPT ALM STS12C <cr> <lf>

"OC12-9-1-1:CR,AIS,SA,10-17,21-00-00,NEND,RCV:\"STS12C Rx AIS\"" ;<cr> <lf>



OC-12 OC12-slot#-port#-sts#OC12-slot#-port#-ALLOC12-ALL

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

OC-48 OC48-slot#-sts#OC48-slot#-ALLOC48-ALL

slot# = 11 or 12 for OC-48slot# = 3 to 12 for OC-48 STSsts# = 1, 13, 25, 37


slot# = 11, 12sts# = 1, 13, 25, 37, ... 181

WAN WAN-slot#-port#-sts# slot# = 3 to 10, port# = 1 or 2, sts# = 1



<ntfcncde> MJMNCL

Major alarmMinor alarmCleared alarm

<condtype> PAYUEQ Payload unequipped

PAYERR Payload error

<srveff> SA

NSA

Service affecting















Field Purpose














slot# = 3 to 12 sts# = 1, 25


slot# = 11, 12sts# = 1, 25, ..., 169

WAN WAN-slot#-port#-sts# slot# = 3 to 10, port# = 1 or 2, sts# = 1



<ntfcncde> CRMJMNCL




<srveff> SA

NSA

Service affecting















Field Purpose











Purpose

STS-3c facility AID

OC3-slot#-port#-sts# Identify the STS-3c where slot# = 3 to 10, port# = 1 to 4, sts# = 1

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

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

OC192-slot#-sts# Identify the STS-3c whereslot# = 11 or 12, sts# = 1, 4, 7, ..., 190




<ntfcncde> CR, MJ, MN, or CL Critical, major, minor, or cleared alarm

<condtype> SLMF

AIS

INC

PAYUEQ

PAYERR

Signal label mismatch failure



Payload unequipped

Payload error

<srveff> SA or NSA Service affecting or non-service affecting











Field Purpose










"OC48-9-1:CR,AIS,SA,10-17,21-00-00,NEND,RCV:\"STS48C Rx AIS\"" ;<cr> <lf>




slot# = 3 to 12sts# = 1


slot# = 11, 12sts# = 1, 49, ..., 145



<ntfcncde> CRMJMNCL




<srveff> SA

NSA

Service affecting









REPT^ALM^T1Report Alarm T1 is generated by a network element to report the occurrence of DS1 alarmed events. In general, an alarmed event causes a standing condition and has immediate or potential impact on the operation or performance of the entity. Some form of maintenance effort is required to restore normal operation or performance of the entity after the event.


<cr> <lf> <lf>^^^<sid>^<date>^<time> <cr> <lf><almcde>^<atag>^REPT^ALM^T1 <cr> <lf><rspblk> + ;




Field Purpose









Example message<cr> <lf> <lf> OC3NE01 01-10-17 21:00:00 <cr> <lf>* 123 REPT ALM T1 <cr> <lf>

"DS1-5-12:MJ,INT,SA,10-17,21-00-00,NEND,RCV:\"DS1 Loopback Active\"" ;<cr> <lf>



DS1 facility AID

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

DS3VT facility AID

DS1-slot#-port#-t1# Identify the DS1 facility on DS3VTx12 equipment where slot# = 3, 5, 7, 9, port# = 1 to 12, t1# = 1 to 28


Identify the DS1s on the DSM whereHLINE=OC3 or OC12port# = 1 to 84, hslot# = 3 to 10, hport# = 1 to 4



<ntfcncde> CRMJMNCL


<condtype> LOS LOF INT INC AIS

Loss of signal Loss of frame Internal hardware fault/failure Incoming failure condition Alarm indication signal

<srveff> SA NSA

Service affecting Non service affecting




<dirn> NA RCVTRMT





REPT^ALM^T3Report Alarm T3 is generated by a network element to report the occurrence of DS3 alarmed events. In general, an alarmed event causes a standing condition and has immediate or potential impact on the operation or performance of the entity. Some form of maintenance effort is required to restore normal operation or performance of the entity after the event has occurred.


<cr> <lf> <lf>^^^<sid>^<date>^<time> <cr> <lf><almcde>^<atag>^REPT^ALM^T3 <cr> <lf><rspblk> + ;




Field Purpose









Example message<cr> <lf> <lf> OC3NE01 01-10-17 21:00:00 <cr> <lf>* 123 REPT ALM T3 <cr> <lf

"DS3-5-3:MN,INT,SA,10-17,21-00-00,NEND,RCV:\"DS3 Loopback Active\"" ;<cr> <lf>



DS3 facility AID DS3-slot#-port# Identify the DS3 facility where slot# = 3, 5, 7, or 9, port# = 1 to 12

MS DSM DS3 facility AID

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

Identify the DS3 facility where slot# = 3, 5, port# = 1 to 6Hline = OC3 or OC12hslot# = 3 to 10, hport# = 1 to 4



<ntfcncde> CRMJMNCL


<condtype> LOS

LOF

INT

INC

AIS

Loss of signal

Loss of frame



Alarm indication signal

<srveff> SA

NSA

Service affecting





<dirn> NA RCVTRMT





REPT^ALM^VT1Report Alarm VT1 is generated by a network element to report the occurrence of VT1.5 alarmed events. In general, an alarmed event causes a standing condition and has immediate or potential impact on the operation or performance of the entity. Some form of maintenance effort is required to restore normal operation or performance of the entity after the event has occurred.


<cr> <lf> <lf>^^^<sid>^<date>^<time> <cr> <lf><almcde>^<atag>^REPT^ALM^VT1 <cr> <lf><rspblk> + ;




Field Purpose











VT1.5 facility AID

EC1-slot#-port#-vtg#-vt# Identify the VT1.5 path where slot# = 3, 5, 7, 9port# = 1 to 12vtg# = 1 to 7vt# = 1 to 4

OC3-slot#-port#-sts#-vtg#-vt# Identify the VT1.5 path where slot# = 3 to 10port# = 1 to 4sts# = 1 to 3vtg# = 1 to 7vt# = 1 to 4

OC3-slot#-1-sts#-vtg#-vt#-%HLINK-OC3-hslot#-hport#

Identify the VT1.5 path where slot# = 1, 2sts# = 1 to 3vtg# = 1 to 7vt# = 1 to 4hslot# = 3 to 10hport# = 1 to 4

OC12-slot#-port#-sts#-vtg#-vt# Identify the VT1.5 path where slot# = 3 to 12port# = 1sts# = 1 to 12vtg# = 1 to 7vt# = 1 to 4



OC48-slot#-sts#-vtg#-vt# Identify the VT1.5 path whereslot# = 11, 12 sts# = 1 to 48vtg# = 1 to 7vt# = 1 to 4

DS1-slot#-port#-t1# Identify the VT1.5 path on DS3VTx12 equipment whereslot# =3, 5, 7, 9port# = 1 to 12t1# = 1 to 28



Example message<cr> <lf> <lf> OC3NE01 01-10-17 21:00:00 <cr> <lf>*C 123 REPT ALM VT1 <cr> <lf>

"OC3-10-1-2-2-1:CR,AIS,SA,10-17,21-00-00,NEND,RCV:\"VT Rx AIS\""; <cr> <lf>

Table 3-325Paramter descriptions


<ntfcncde> CRMJMNCL


<condtype> SLMF Signal label match failure



<srveff> SA

NSA

Service affecting










REPT^CONFIG^CHGReport Configuration Change is generated when the functionality detects that there may be a change in the configured network administered by the network processor. Typically this is due to expansion and reconfiguration of an existing network. An example of this might be the upgrading of a point-to-point linear network to a linear ADM chain or the addition of nodes to a ring.


<cr> <lf> <lf>^^^<sid>^<date>^<time> <cr> <lf><almcde>^<atag>^REPT^CONFIG^CHG <cr> <lf>;


Field Purpose




<almcde> A^ (Automatic message)




REPT^DBCHGReport Database Change is generated by the network element to which a name change (TID) or account change (UID) was made. It is also generated by BLSR configuration, cross-connect, FFP and SOC commands.


<cr> <lf> <lf>^^^<sid>^<date>^<time> <cr> <lf>A^^<atag>^REPT^DBCHG <cr> <lf><rspblk> + ;

The message must contain at least one occurrence of <rspblk>. The format for an NE name change is:

^^^"<msgtype>:<netid>,<oldtid>,<newtid>" <cr> <lf>

The format for an NE account change is:

^^^"<msgtype>:<netid>,<olduid>,<newuid>" <cr> <lf>

Note: Since an atag of 0000000 is always used for this type of report, they are not logged into the automatic output (AO) buffer.

The format for all other commands that cause a configuration change (level 1 to level 4) commands is:

^^^”<DBCHGSEQ=seqnum>:<DATE>,<TIME>:<userid=domain>,<priority=domain>:<commandcode>:<aid1><,aid2>:<ctag>:<position1><,position2>:<keyword1=domain><,keyword2=domain]>:<pst>,<sst>”<cr> <lf>

Note 1: When issued for a SID change, REPT DBCHG is sent only to the TL1 session that originated the change.

Note 2: When issued for a UID change, REPT DBCHG is sent to all active TL1 sessions to the shelf processor or network processor that issued the change. The affected TL1 sessions are those that have a UPC equal or greater to the UPC of the UID that was changed.




Field Purpose




<atag> Automatic tag, the numerical identification of the message. Since an atag of 0000000 is always used for this type of report, they are not logged into the automatic output (AO) buffer

<rspblk> Response block. See the following table for details.



<msgtype> NNCSAC

NE name changeSystem account change

<netid> Target identifier

<oldtid> Old target identifier

<newtid> New target identifier

<olduid> Old user identifier

<newuid> New user identifier

<DBCHGSEQ=seqnum>

REPT- DBCHG sequence number

<uid=domain> User name that executed the command

<command code> The provisioning command issued (for example, ENT-CRS-STS1)

<aid1><,aid2> Optional and specific to the provisioning command.

<ctag> Correlation tag

<position1><,position2

All position defined parameters specified in the command

<keyword1=domain><,keyword2=domain>

All keyword defined parameters that were specified in the command

<pst> Primary state from the command

<sst> Secondary state from the command



Example messageAt 9 p.m. on October 17, 2001, the name of NE01TID was changed to OC3NE01. This message will be returned:

<cr> <lf> <lf>NE01TID 01-10-17 21:00:00 <cr> <lf>

A 000000 REPT DBCHG <cr> <lf>"NNC:NE01TID,NE01TID,OC3NE01" <cr> <lf>

At 10 p.m. on January 18, 2002, the user identifier EXPRESS01 on network element BOSTON was changed to EXPRESS02. This message will be returned:

<cr> <lf> <lf>BOSTON 02-01-18 22:00:00 <cr> <lf>

A 000000 REPT DBCHG <cr> <lf>"SAC:BOSTON,EXPRESS01,EXPRESS02" <cr> <lf>



REPT^EVT^COMReport Event Com is generated by a network element or network processor to report alarms that affect the network processor or the shelf as a whole. In general, an event causes a standing condition and has immediate or potential impact on the operation or performance of the entity. Some form of maintenance effort is required to restore normal operation or performance of the entity after the event has occurred.


<cr> <lf> <lf>^^^<sid>^<date>^<time> <cr> <lf>A^^<atag>^REPT^EVT^COM <cr> <lf><rspblk> +

The message must contain at least one occurrence of <rspblk>. Its format is: ^^^"<aid>:<condtype>,<condeff>,<ocrdat>,<ocrtm>,<locn>,<dirn>:<conddescr>" <cr> <lf>


Field Purpose








SPx SP Identify the network element


Shelf SHELF Identify the shelf

BITS signal BITS-ABITS-B

Identify the BITS-A or BITS-B input or output



Timing reference

DS1-slot#-port# Identify the timing reference whereslot# = 4 to 10, port# = 1 to 12

EC1-slot#-port# Identify the timing reference whereslot# = 3, 5, 7, 9, port# = 1 to 12


OC12-slot#-port# Identify the timing reference 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

OC48-slot# Identify the timing reference whereslot# = 11 or 12 for OC-48slot# = 3 to 12 for OC-48 STS

OC192-slot# Identify the timing reference whereslot# = 11 or 12

TBOS display

display-shelf Identify the remote network element wheredisplay = 1 to 16shelf = user-defined shelf name



<condtype> INC BITS signal Incoming failure condition

FEMCOD TBOS display Far end SID change

HLDOVRSYNC Shelf Switch to holdover synchronization

FRNGSYNC Shelf Switch to freerun synchronization

SYNCREFSW BITS signalSynchronization reference

Synchronization reference switch

SWFTDWN SPx or NPx Software download

INT SPx or NPx Internal software failure





Example messageAt 9 p.m. on March 17, 2001, during a software upgrade on network element NEWYORK, the following event is reported:

<cr> <lf> <lf>NEWYORK 01-10-17 21:00:00 <cr> <lf>

A 123 REPT EVT COM <cr> <lf>"SP:SWFTDWN,TC,10-17,21-00-00:"

Invoke upgrade passedSlot(s) 05 06 09 10 11 12 13 14 15 passed"";<cr> <lf>

<condeff> SCTCCL

all Standing condition raisedTransient conditionStanding condition cleared

<ocrdat> mm-dd all The date when the event occurred

<ocrtm> hh-mm-ss all The time when the event occurred

<conddescr> character string all The detailed text description of the trouble

<locn> NENDFEND

allTBOS display

Failure at the near end of the systemFailure at the far end of the system


RCV BITS signalTBOS display

Receive failure





REPTÊVTÊC1Report Event EC-1 is generated by a network element to report the occurrence of non-alarmed EC-1 related events. The event being reported can be a change of status or the occurrence of an irregularity, which by itself is not severe enough to warrant an alarm notification.


<cr> <lf> <lf>^^^<sid>^<date>^<time> <cr> <lf>A^^<atag>^REPTÊVTÊC1 <cr> <lf><rspblk> + ;


^^^"<aid>:<condtype>,<condeff>,<ocrdat>,<ocrtm>,<locn>,<dirn>,<monval>,<thlev>,<tmper>:<conddescr>" <cr> <lf>


Field Purpose








EC1 facility AID EC1-slot#-port# Identify EC-1 facility whereslot# = 3, 5, 7, 9port# = 1 to 12



Example messageAt 00:29:23 on 1 January 2002 a transient threshold-crossing of Severely Errored Seconds - Section of 1, where the threshold level is 1, is recorded for the EC-1 circuit pack in slot 7, port 1 of FMX70.

<cr> <lf> <lf>FMX70 02-01-01 00:29:23^MA 000012 REPT EVT EC1^M "EC1-7-1:T-SESS,TC,01-01,00-29-23,NEND,RCV,1,1,15-MIN:\"T-SESS\"<cr> <lf>



<condtype> T-MONTYPE Threshold-crossing monitored threshold type

<condeff> TC Transient condition

<ocrdat> mm-dd Date when the event occurred

<ocrtm> hh-mm-ss Time when the event occurred

<locn> NENDFEND

Near endFar-end

<dirn> TRMTRCV

Transmit (away from the node)Receive (onto the node)

<monval> 1 and up Measured value of a monitored parameter

<thlev> 1 and up Threshold level for the monitored parameter

<tmper> 15-MIN1-DAY1-UNT

The accumulation time period: 15 minute, 1 day, or untimed.

<conddescr> text message Condition description

Table 3-335Montype parameter descriptions


<montype> CVSESSSESSSEFSSCVLESLSESLUASL

Coding Violations - SectionErrored Seconds - SectionSeverely Errored Seconds - SectionSeverely Errored Frame Seconds - SectionCoding Violations - LineErrored Seconds - LineSeverely Errored Seconds- LineUnavailable Seconds - Line



REPTÊVTÊQPTReport Event Equipment is generated by a network element to report the occurrence of non-alarmed equipment related events. The event being reported can be a change of status or the occurrence of an irregularity, which by itself is not severe enough to warrant an alarm notification.


<cr> <lf> <lf>^^^<sid>^<date>^<time> <cr> <lf>A^^<atag>^REPTÊVTÊQPT <cr> <lf><rspblk> + ;


^^^"<aid>:<condtype>,<condeff>,<ocrdat>,<ocrtm>,<locn>,<dirn>:<conddescr>"<cr> <lf>


Field Purpose








Purpose

2xGigE eqpt 1GE-slot# Identify 2xGigE equipment whereslot# = 3, 5, 7, 9 for double slot circuit pack and slot#= 3 to 10 for single slot 2xGigE circuit packs.

2xGigE 2.5G eqpt


4x100BT eqpt IPT100-slot# Identify 4x100BT equipment whereslot# = 3 to 10

4x100FX eqpt 100FX-slot# Identify 4x100FX equipment whereslot# = 3 to 10



2x100BT-P2P eqpt

100BTFOS-slot# Identify 2x100BT-P2P equipment where slot# = 3 to 10




DS1 eqpt DS1-slot# Identify DS1 equipment whereslot# = 3 to 10

DS1TM-slot#-%HLINK-OC3-hslot#-hport#

Identify the DS1 equipment on the DSM where slot# = 1, 2, hslot# = 3 to 10, hport# = 1 to 4



Identify the DS3 equipment on the MS DSM where slot# = 1, 2, hslot# = 3 to 10, hport# = 1 to 4

DS3 eqpt DS3-slot# Identify the DS3x3, DS3x12, or DS3x12e equipment where slot# = 3 to 10

DS3VT eqpt DS3V-slot#DS3V-ALL

Identify the DS3VTx12 equipment where slot# =3 to 10

EC1 eqpt EC1-slot# Identify the EC-1x3 or EC-1x12 equipment where slot# = 3 to 10



MS DSM eqpt AGGOC3OC12-slot#-%HLINK-HLINE-hslot#-hport#

AGGOC3-slot#-%HLINK-HLINE-hslot#-hport#

Identify aggregate equipment whereslot# = 1, 2, HLINE = OC3 or OC12,hslot# = 3 to 10, hport# = 1 to 4



Purpose



NPx eqpt NP Identify the network processor

OC3 eqpt OC3-slot# Identify the OC-3 or OC-3x4 equipment where slot# = 3 to 10

OC12 eqpt OC12-slot# Identify the OC-12 or OC-12x4 STS equipment where slot# = 3 to 12 for OC-12slot# = 3 to 10 for OC-12x4

OC48 eqpt OC48-slot# Identify the OC-48 or OC-48 STS equipment where slot# = 11 or 12 for OC-48slot# = 3 to 12 for OC-48 STS

OC192 ept OC192-slot# Identify the OC-192 equipment whereslot# = 11 or 12





CLX eqpt CLX-slot# Identify the VTX48, VTX40/10, or STX-192 equipment where slot# = 13 or 14



Purpose



Example messageAt 9 p.m. on March 21, 2002, the DS1 in slot 4 switches to protection. This message will be returned.

<cr> <lf> <lf>OC3NE01 02-03-21 21:00:00 <cr> <lf>

A 123 REPT EVT EQPT <cr> <lf>DS1-4:INT,SC,03-21,21-00-00,NEND,NA:\"Auto Switch Complete"\;



<condtype> INC IPT100-slot# Switch to protection inhibited where slot# = 3 to 12

100FX-slot# Switch to protection inhibited where slot# = 3 to 10

1GE-slot# Switch to protection inhibited where slot# = 3, 5, 7, 9

FWGADWNLD IPT100-slot# FPGA download whereslot# = 3 to 10

100FX-slot# FPGA download whereslot# = 3 to 10

1GE-slot# FPGA download whereslot# = 3, 5, 7, 9

1GE25G-slot# FPGA download whereslot# = 3, 5, 7, 9

INT all Internal software failure

<condeff> TC SCCL

all Transient condition Standing condition raisedStanding condition cleared

<ocrdat> mm-dd all The date when the event occurred

<ocrtm> hh-mm-ss all The time when the event occurred



<conddescr> character string all The detailed text description of the trouble



REPTÊVTÎNVENTORYReport Event Inventory is generated by a network element to report the occurrence of inventory events. The event being reported is for the insertion or removal of circuit packs from the shelf.

Message formatAll parameters in this message are either positional or name-defined.<cr> <lf> <lf>^^^<sid>^<date>^<time> <cr> <lf>A^^<atag>^REPTÊVTÎNVENTORY <cr> <lf><rspblk> +;

The message must contain at least one occurrence of <rspblk>. Its format is:^^^"<ACTION=descriptor>:<aid>:<CTYPE=domain>,<SER=domain>,<PEC=domain>" <cr> <lf>


Field Purpose








<Descriptor> INSERTREMOVE

The action that was performed

<aid> see AID description table

Circuit pack and slot number

<ctype=domain> circuit pack type

<serial=domain> circuit pack serial number

<pec=domain> circuit pack product engineering code (PEC)





Purpose

2xGigE eqpt 1GE-slot# Identify 2xGigE equipment whereslot# = 3, 5, 7, 9 for double slot circuit pack and slot#= 3 to 10 for single slot 2xGigE circuit packs.

2xGigE 2.5G eqpt


4x100BT eqpt IPT100-slot# Identify the 4x100BT circuit pack where slot# = 3 to 10

4x100FX eqpt 100FX-slot# Identify 4x100FX equipment whereslot# = 3 to 10

2x100BT-P2P eqpt

100BTFOS-slot# Identify the 2x100BT-P2P circuit pack where slot# = 3 to 10





DS1TM-slot#-%HLINK-HLINE-hslot#-hport#

Identify the DS1 equipment on the DSM whereHLINE= OC3 or OC12, slot# = 1, 2, hslot# = 3 to 10, hport# = 1 to 4


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

AGGOC3-slot#-%HLINK-HLINE-hslot#-hport#

Identify the DS1 equipment on the MS DSM where HLINE= OC3 or OC12, slot# = 1, 2, hslot# = 3 to 10, hport# = 1 to 4

DS3 eqpt DS3-slot# Identify the DS3x3, DS3x12, or DS3x12e equipment where slot# = 3 to 10



DS3VT eqpt DS3V-slot# Identify the DS3VTx12 equipment whereslot# =3 to 10

EC1 eqpt EC1-slot# Identify the EC-1 equipmentwhere slot# = 3 to 10



NPx eqpt NP Identify the network processor

OC3 eqpt OC3-slot# Identify the OC-3 or OC-3x4 equipment where slot# = 3 to 10

OC12 eqpt OC12-slot# Identify the OC-12 or OC-12x4 STS equipment where slot# = 3 to 12 for OC-12slot# = 3 to 10 for OC-12x4 STS

OC48 eqpt OC48-slot# Identify the OC-48 or OC-48 STS equipment where slot# = 11 or 12 for OC-48slot# = 3 to 12 for OC-48 STS

OC192 ept OC192-slot# Identify the OC-192 equipment whereslot# = 11 or 12

PECN PECN-slot-%HLINK-Hline-hslot-hport

Identify the expansion equipment whereslot = 3 to 6Hline = OC3 or OC12hslot = 3 to 10hport = 1 to 4

PFOST PFOST-slot-%HLINK-Hline-hslot-hport

Identify the expansion equipment whereslot = 3 to 6Hline = OC3 or OC12hslot = 3 to 10hport = 1 to 4

POC POC3-slot-subslot-%HLINK-OC3-hslot-hport

POC12-slot-subslot-%HLINK-OC12-hslot-hport

Identify the expansion equipment whereslot = 1, 2subslot = 1Hline = OC3 or OC12hslot = 3 to 10hport = 1 to 4




Purpose



Example messageAt 10:15 p.m. on October 15, 2002, an OC-12 circuit pack was inserted in slot 4. This message will be returned.

<cr> <lf> <lf>OC3NE01 02-10-15 22:15:00 <cr> <lf>

A 123 REPT EVT EQPT <cr> <lf>“ACTION=INSERT:OC12-4:CTYPE=OC12,SERIAL=NNTM01GZ34R76,PEC=NTN404AA”;




CLX eqpt CLX-slot# Identify the VTX48, VTX40/10, or STX-192 equipment where slot# = 13 or 14



Purpose



REPT^EVT^LOGReport Event Log is generated by a network element to report the occurrence of log events. The event being reported is for activities that have occurred on the system.

Message formatAll parameters in this message are either positional or name-defined.<cr> <lf> <lf>^^^<sid>^<date>^<time> <cr> <lf>A^^<atag>^REPT^EVT^LOG <cr> <lf><rspblk> ;

The message must contain at least one occurrence of <rspblk>. Its format is:^^^"<timestamp>:<uid=domain>:<priority=domain>,<status=domain>:<commandcode>:<aid>:<ctag>:<positionparms>:<keywordparms=domain>:<pst>,<sst>:<failure string>" <cr> <lf>


Field Purpose








<timestamp> Date and time command was executed

<uid=domain> User name that executed the command

<priority=domain> The priority of the message

<status=domain> The status of the command (for example: completed, failed, or IDNV)

<commandcode> Name of the command that was executed

<aid> The AID that received the command

<ctag> Correlation tag

<positionparms> All position defined parameters specified in the command



Example messageAt 10:15 p.m. on October 15, 2002, the following failure message was returned for an input command:

ENT-EQPT:FGXSPX107:EC1-11:D;IP D

FGXSPX107 02-10-17 17:00:00M D DENY

IIAC/*Input, Invalid ACcess identifier*/

Due to this failure, this log event will be returned.

<cr> <lf> <lf>FGXSPX107 02-10-17 17:00:00 <cr> <lf>

A 005551 REPT EVT LOG <cr> <lf>“02-10-17,17-00-00:UID=ADMIN,PRIORITY=GEN_TL1_CMD,STATUS=IIAC:ENT-EQPT:EC1-11:CTAG99:::”;

<keywordparms> All keyword defined parameters specified in the command

<pst> Primary state from the command

<sst> Secondary state from the command





REPTÊVTÔC12Report Event OC-12 is generated by a network element to report the occurrence of non-alarmed OC-12 related events. The event being reported can be a change of status or the occurrence of an irregularity, which by itself is not severe enough to warrant an alarm notification.


<cr> <lf> <lf>^^^<sid>^<date>^<time> <cr> <lf>A^^<atag>^REPTÊVTÔC12 <cr> <lf><rspblk> + ;

The message must contain at least one occurrence of <rspblk>. Its format is in one of the two following formats:

^^^"<aid>:<condtype>,<condeff>,<ocrdat>,<ocrtm>,<locn>,<dirn>:<conddescr>" <cr> <lf>

or

^^^"<aid>:<condtype>,<condeff>,<ocrdat>,<ocrtm>,<locn>,<dirn>,<monval>,<thlev>,<tmper>:<conddescr>"<cr> <lf>


Field Purpose





<rspblk> Response block. See the following AID and Parameter description tables for details.




AID type

Command-specific values Purpose

OC-12 facility AID

OC12-slot#-port# Identify the OC-12 or OC-12x4 STS 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 OC-12 Facility AID

OC12-slot#-1-%HLINK-OC12-hslot-hport

Identify the OC-12 whereslot = 1, 2hslot = 3 to 10hport = 1 to 4



<condtype> T-MONTYPE PSINT

Threshold-crossing monitored threshold type Protection switch exerciserInternal hardware or software failure

<condeff> TC SCCL

Transient conditionStanding condition raisedStanding condition cleared



<locn> NENDFEND

Near endFar end

<dirn> RCVTRMTNA

Receive (onto the node) Transmit (away from the node)Not applicable



<tmper> 15-MIN1-DAY1-UNT





Example messageAt 9 a.m. on October 17, 2001, the OC-12 in slot 10 records coding violations. This message will be returned:

<cr> <lf> <lf>^NE1^01-10-17^9-00 <cr> <lf>A^^123^REPT^EVT^OC12 <cr> <lf>^^^"OC12-10:T-CVS,TC,10-17,9-0-0,NEND,RCV,10,10,15-MIN:\"T-CVS\"<cr> <lf>












or



Field Purpose







AID type Command-specific Values Purpose

OC-192 facility AID










<condeff> TC SCCL




<locn> NENDFEND

Near endFar end

<dirn> RCVTRMTNA




<tmper> 15-MIN, 1-DAY, or1-UNT



Table 3-351Montype paramter descriptions











or



Field Purpose










OC-3 facility AID

OC3-slot#-port# Identify the OC-3 or OC-3x4 where slot# = 3 to 10, port# = 1 to 4

OC3-slot#-%HLINK-HLINE-hslot#-hport#

Identify the OC-3 equipment on the DSM or MS DSM where slot# = 1, 2, hslot# = 3 to 10, hport# = 1 to 4





<condeff> TC SCCL




<locn> NENDFEND

Near endFar end

<dirn> RCVTRMTNA




<tmper>15-MIN1-DAY1-UNT

The accumulation time period15 minute1 dayuntimed









or



Field Purpose








OC-48 facility AID

OC48-slot# Identify the OC-48 or OC-48 STS whereslot# = 3 to 12 for OC-48 STSslot# = 11 or 12 for OC-48









<condeff> TC SCCL




<locn> NEND or FEND Near end or far end

<dirn> RCV, TRMT, or NA

Receive (onto the node), Transmit (away from the node), or Not applicable



<tmper> 15-MIN, 1-DAY, or1-UNT

The accumulation time period: 15 minute, 1 day, or untimed








REPT^EVT^STS1Report Event STS1 is generated by a network element to report the occurrence of non-alarmed STS-1 related events. The event being reported can be a change of status or the occurrence of an irregularity, which by itself is not severe enough to warrant an alarm notification.


<cr> <lf> <lf>^^^<sid>^<date>^<time> <cr> <lf>A^^<atag>^REPT^EVT^STS1 <cr> <lf><rspblk> + ;



or



Field Purpose










STS path AID

OC3-slot#-port#-sts# Identify the STS-1 whereslot# = 3 to 10port# = 1 to 4sts# = 1 to 3

OC12-slot#-port#-sts# Identify the STS-1 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



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

OC-192-slot#-sts# Identify the STS-1 whereslot# = 11 or 12sts# = 1 to 192



EC1-slot#-port# Identify STS-1 whereslot# = 3, 5, 7, 9port# = 1 to 12






<condtype> T-MONTYPE INT

Threshold-crossing monitored threshold type Internal hardware or software failure

<condeff> TC SCCL

Transient condition Standing condition raisedStanding condition cleared



<locn> NENDFEND

Near endFar end

<dirn> RCVTRMTNA







Example messageAt 9 a.m. on October 17, 2001, the OC-3 in slot 10, port 1, sts 3 records coding violations. This message will be returned:

<cr> <lf> <lf>^NE1^01-10-17^9-00 <cr> <lf>A^^123^REPT^EVT^STS1 <cr> <lf>^^^"OC3-10-1-3:T-CVP,TC,10-17,9-0-0,NEND,RCV,10,10,15-MIN:\"T-CVP\"<cr> <lf>







<montype> CVP ESP SESP ALSPUASP

Coding Violations - PathErrored Seconds - PathSeverely Errored Seconds - PathAIS/LOP Seconds - PathUnavailable Seconds - Path





REPT^EVT^STS12CReport Event STS-12c is generated by a network element to report the occurrence of non-alarmed STS-12c related events. The event being reported can be a change of status or the occurrence of an irregularity, which by itself is not severe enough to warrant an alarm notification.


<cr> <lf> <lf>^^^<sid>^<date>^<time> <cr> <lf>A^^<atag>^REPT^EVT^STS12C <cr> <lf><rspblk> + ;



or



Field Purpose










OC-12 OC12-slot#-port#-sts#OC12-slot#-port#-ALLOC12-ALL

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


slot# = 11 or 12 for OC-48slot# = 3 to 12 for OC-48 STSsts# = 1, 13, 25, 37


slot# = 11, 12sts# = 1, 13, 25, 37, ... 181

WAN WAN-slot#-port#-sts# slot# = 3 to 10port# = 1 or 2sts# = 1



<condtype> T-MONTYPEINTPAYCHG

Threshold-crossing monitored threshold type Internal hardware or software failurePayload change

<condeff> TC SCCL




<locn> NENDFEND

Near endFar end

<dirn> RCVTRMTNA





Example messageAt 9 a.m. on October 17, 2001, the OC-12 in slot 3 port 1 sts 1records coding violations. This message will be returned:

<cr> <lf> <lf>^NE1^01-10-17^9-00 <cr> <lf>A^^123^REPT^EVT^STS12C <cr> <lf>^^^"OC12-3-1-1:T-CVP,TC,10-17,9-0-0,NEND,RCV,10,10,15-MIN:\"T-CVP\"<cr> <lf>









Table 3-366 (continued)Response parameter descriptions









or



Field Purpose











slot# = 3 to 12sts# = 1, 25


slot# = 11, 12sts# = 1, 25, ..., 169

WAN WAN-slot#-port#-sts# slot# = 3 to 10port# = 1 or 2sts# = 1





<condeff> TC SCCL




<locn> NENDFEND

Near endFar end

<dirn> RCVTRMTNA









Example messageAt 9 a.m. on October 17, 2001, the OC-48 in slot 3 sts 1records coding violations. This message will be returned:

<cr> <lf> <lf>^NE1^01-10-17^9-00 <cr> <lf>A^^123^REPT^EVT^STS24C <cr> <lf>^^^"OC48-3-1:T-CVP,TC,10-17,9-0-0,NEND,RCV,10,10,15-MIN:\"T-CVP\"<cr> <lf>

Table 3-371Montype paramter descriptions











or



Field Purpose










STS-3c facility AID

OC3-slot#-port#-sts# Identify the STS-3c where slot# = 3 to 10port# = 1 to 4sts# = 1

OC12-slot#-port#-sts# Identify the STS-3c 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 whereslot# = 11 or 12 for OC-48slot# = 3 to 12 for OC-48 STSsts# = 1, 4, 7, ..., 46

OC192-slot#-sts# Identify the STS-3c whereslot# = 11 or 12sts# = 1, 4, 7, ..., 190


STS3C MS DSM WAN facility AID

WAN-slot-port-sts-%HLINK-Hline-hslot-hport

Identify the STS-3c facility on the WAN port whereslot# = 3 to 6port = 1 to 8sts = 1Hline = OC3 or OC12hslot = 3 to 10hport = 1 to 4







<condeff> TC SCCL




<locn> NENDFEND

Near endFar end

<dirn> RCVTRMTNA













Example messageAt 9 a.m. on October 17, 2001, the OC-3 in slot 10 port 1 sts 1records coding violations. This message will be returned:

<cr> <lf> <lf>^NE1^01-10-17^9-00 <cr> <lf>A^^123^REPT^EVT^STS3C <cr> <lf>^^^"OC3-10-1-1:T-CVP,TC,10-17,9-0-0,NEND,RCV,10,10,15-MIN:\"T-CVP\"<cr> <lf>








or


\


Field Purpose











slot# = 3 to 12sts# = 1


slot# = 11, 12sts# = 1, 49, ..., 145





<condeff> TC SCCL




<locn> NENDFEND

Near endFar end

<dirn> RCVTRMTNA









Example messageAt 9 a.m. on October 17, 2001, the OC-48 in slot 3 sts 1records coding violations. This message will be returned:

<cr> <lf> <lf>^NE1^01-10-17^9-00 <cr> <lf>A^^123^REPT^EVT^STS48C <cr> <lf>^^^"OC48-3-1:T-CVP,TC,10-17,9-0-0,NEND,RCV,10,10,15-MIN:\"T-CVP\"<cr> <lf>







REPT^EVT^T1Report Event T1 is generated by a network element to report the occurrence of non-alarmed DS1 related events. The event being reported can be a change of status or the occurrence of an irregularity, which by itself is not severe enough to warrant an alarm notification.


<cr> <lf> <lf>^^^<sid>^<date>^<time> <cr> <lf>A^^<atag>^REPT^EVT^T1 <cr> <lf><rspblk> + ;



or



Field Purpose


<date> in the format yy-mm-dd

<time> in the format hh:mm:ss

<atag> automatic tag, the numerical identification of the message






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

DS3VT facility AID

DS1-slot#-port#-t1# Identify the DS1 facility on DS3VTx12 equipment whereslot# =3, 5, 7, 9port# = 1 to 12t1# = 1 to 28


Identify the DS1 facility on the DSM where

HLINE=OC3 or OC12port# = 1 to 84hslot# = 3 to 10hport# = 1 to 4

Table 3-382Reponse parameter descriptions


<condtype> T-MONTYPE INCINT

Threshold-crossing monitored threshold typeIncoming failureSoftware failure

<condeff> TC SCCL




<locn> NENDFEND

Near endFar end

<dirn> RCVTRMTNA





Example messageAt 9 p.m. on October 17, 2001, the DS1 in slot 4, port 2 records unavailable seconds. This message will be returned:

<cr> <lf> <lf> OC3NE01 01-10-17 21:00:00 <cr> <lf> A 123 REPT EVT T1<cr> <lf>

"DS1-4-2:T-UASP,TC,10-17:21:00:00,NEND,TRMT,15,10,15-MIN:\"T-UASP\"<cr> <lf>

At 9 p.m. on October 17, 2001, the DS1 in slot 4, port 10 reports a problem with the DS1 test pattern. This message will be returned:


"DS1-4-10:INT,SC,10-17:21:00:00,NEND,NA:\"DS1 Test SignalActive-OutofSync\"" <cr> <lf>







montype CVL ESL SESLCVP ESP SEFSP SESP SASPUASP CSSP

Coding Violations - LineErrored Seconds - LineSeverely Errored Seconds - LineCoding Violations - PathErrored Seconds - PathSeverely Errored Frame Seconds - PathSeverely Errored Seconds - PathSEF / AIS Seconds - PathUnavailable Seconds - PathControlled Slip Seconds - Path

Table 3-382Reponse parameter descriptions




REPT^EVT^T3Report Event T3 is generated by a network element to report the occurrence of non-alarmed DS3 related events. The event being reported can be a change of status or the occurrence of an irregularity, which by itself is not severe enough to warrant an alarm notification.


<cr> <lf> <lf>^^^<sid>^<date>^<time> <cr> <lf>A^^<atag>^REPT^EVT^T3 <cr> <lf><rspblk> + ;




Field Purpose








DS3 AID DS3-slot#-port# Identify the DS3 where slot# = 3, 5, 7, or 9port# = 1 to 12

MS DSM DS3 facility

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

Identify the DS3 where slot# = 3, 5port# = 1 to 6Hline = OC3 or OC12hslot = 3 to 10hport = 1 to 4



Example messageAt 9 p.m. on October 17, 2001, the DS3x12 in slot 3, port 3 records coding violations. This message will be returned:


"DS3-3-3:T-CVL,TC,10-17,21:00:00,NEND,RCV,3,3,15-MIN:\"T-CVL\"<cr> <lf>



<condtype> T-MONTYPE Threshold-crossing monitored threshold type

<condeff> TC Transient condition



<locn> NENDFEND

Near endFar end

<dirn> RCVTRMT

Receive (onto the node) Transmit (away from the node)

monval 1 and up Measured value of a monitored parameter

thlev 1 and up Threshold level for the monitored parameter

tmper15-MIN1-DAY1-UNT





montype CVL ESL SESLCVP ESP SESP SASPUASP

Coding Violations - LineErrored Seconds - LineSeverely Errored Seconds - LineCoding Violations - PathErrored Seconds - PathSeverely Errored Seconds - PathSEF / AIS Seconds - PathUnavailable Seconds - Path



REPT^EVT^VT1Report Event VT1 is generated by a network element to report the occurrence of non-alarmed VT1.5 related events. The event being reported can be a change of status or the occurrence of an irregularity, which by itself is not severe enough to warrant an alarm notification.


<cr> <lf> <lf>^^^<sid>^<date>^<time> <cr> <lf>A^^<atag>^REPT^EVT^VT1 <cr> <lf><rspblk> + ;




Field Purpose










VT1.5 facility AID

EC1-slot#-port#-vtg#-vt# Identify the VT1.5 path where slot# = 3, 5, 7, 9port# = 1 to 12vtg# = 1 to 7vt# = 1 to 4

OC3-slot#-port#-sts#-vtg#-vt# Identify the VT1.5 path where slot# = 3 to 10port# = 1 to 4sts# = 1 to 3vtg# = 1 to 7vt# = 1 to 4



OC12-slot#-port#-sts#-vtg#-vt# Identify the VT1.5 path where slot# = 3 to 12port# = 1sts# = 1 to 12vtg# = 1 to 7vt# = 1 to 4


Identify the VT1.5 path where slot# = 1, 2sts# = 1 to 12vtg# = 1 to 7vt# = 1 to 4hslot# = 3 to 10hport# = 1

OC48-slot#-sts#-vtg#-vt# Identify the VT1.5 path whereslot# = 11, 12 sts# = 1 to 48vtg# = 1 to 7vt# = 1 to 4

DS1-slot#-port#-t1# Identify the VT1.5 path on DS3VTx12 equipment whereslot# =3, 5, 7, 9port# = 1 to 12t1# = 1 to 28



Example messageAt 9 p.m. on October 17, 2001, the OC-3 in slot 3, STS-3 records an internal hardware fault/failure. This message will be returned:

<cr> <lf> <lf> OC3NE01 01-10-17 21:00:00 <cr> <lf> A 123 REPT EVT VT1 <cr> <lf>

"OC48-11-3-1-1:INT,SC,10-17,21:00:00,NEND,NA:\Auto VT1.5Path Switch Complete"" <cr> <lf>



<condtype> INT Internal hardware fault/failure

<condeff> SCCL

Standing condition raisedStanding condition cleared







REPT^EX^LINKReport exercise link is generated by the NPx to exercise connections (links) made to the NPx and to detect any half open connections. If the link is half open, the attempt to transmit this message will fail and result in the NPx closing the link and cleaning up the associated resources.

Note: A TCP connection is half open when one end has closed or aborted the connection without the knowledge of the other end. This can happen at any time one of the two hosts crashes. As long as there is no attempt to transfer data across a half-open connection, the end that is still up will not detect that the other end has crashed.

The report exercise link message is only sent where there is no timeout set on the TL1 session (TIMEOUTA=N) or where no TL1 session has been activated (no ACT-USER has been completed).

The frequency of the REPT EX LINK is determined by the level of the user and whether there is an active TL1 session. The frequency is either every 30 seconds, or every 30 minutes.

Message format<cr> <lf> <lf>^^^<sid>^<date>^<time> <cr> <lf>A^^<atag>^REPT^EX^LINK <cr> <lf>;


Table 3-391Use and frequency of the REPT EX LINK message

Account UPC level Level 5 Level 4, 3, 2, 1 Unknown (no ACT-USER)

Session TIMEOUTA Y default

N Ydefault

N n/a

Is REPT EX LINK sent?

N Y N Y Y

REPT EX LINK time interval

n/a 30 sec n/a 30 min 30 min



Example messageAt 2 a.m. on November 17, 2001, the following message was generated by EXPRESS45NP:

<cr> <lf> <lf>EXPRESS45NP 01-11-17 02:00:00 <cr> <lf>

A 000 REPT EX LINK <cr> <lf>;


Field Purpose




<atag> Automatic tag, the numerical identification of the message. The atag for REPT EX LINK is 000.



REPT^IMSGReport Instant Message is generated by a network element to report the occurrence of a new text message.


<cr> <lf> <lf>^^^<sid>^<date>^<time> <cr> <lf>A^^<atag>^REPT^IMSG <cr> <lf>^^^"<date>,<time>:UID=<uid>:\"<msg>\"" <cr> <lf>;


Example messageAt 1:17 p.m. on October 17, 2003, user identifier ADMIN sent the following message "I am restarting this NE. Please re-connect in 5 minutes". The following will be returned:

<cr> <lf> <lf>NPGX0504 03-10-17 13:17:00 <cr> <lf>

A 000000 REPT IMSG <cr> <lf>"03-10-17,13-17-00:UID=ADMIN:18:\"I am restarting this NE.

Please re-connect in 5 minutes.\"" <cr> <lf>;


Field Purpose





<uid> User identifier

<msg> Message



REPT^SOCThe Report Span of Control is generated by the NPx to a level 5 user if there is a change in the span of control of the NPx, such as an NE is removed from or added to the span of control, or the connection status from an NPx to an NE in the span of control is changed.


<cr> <lf> <lf>^^^<sid>^<date>^<time> <cr> <lf>A^^<atag>^REPT^SOC <cr> <lf>^^^"<msgtype>:<netid>,<status>,<swversion>" <cr> <lf>;



Field Purpose





<msgtype><netid><status><swversion>

See the following table for details.



<msgtype> EADERMCSR

NE addedNE removedConnection status report

<netid> Target identifier



Example messageAt 9 p.m. on October 17, 2001, the connection status from NP OC3NP01 to network element OC3NE02 was changed from down to up. This message will be returned:

<cr> <lf> <lf>OC3NP01 01-10-17 21:00:00 <cr> <lf>

A 000000 REPT SOC <cr> <lf>"CSR:OC3NE02,UP,REL0902X.DU" <cr> <lf>

<status> UPDOWNXPID

Connection is upConnection is downIncorrect password

<swversion> Software version

Note: For the Connection status report notification, the software version is provided only if the connection status changes from DOWN to UP, or from XPID to UP.

Table 3-395 (continued)Response parameter descriptions




REPT-INITZNThe Report Initialization command is used to release all test access sessions on the network element. This command removes all test access connections and restores previous connections.


Input syntaxREPT-INITZN:[TID]::CTAG;

Example inputRelease all test access sessions on network element NewYork.REPT-INITZN:NEWYORK::MYTAG;


Field Purpose





REPT-STATThe Report State command is used to check that the association (communication) between the network element and test equipment is alive. An acknowledgement will be sent within 60 seconds.


Input syntaxREPT-STAT:[TID]::CTAG;

Example inputCheck link association between the test equipment and network element NewYork.

REPT-STAT:NEWYORK::MYTAG;


Field Purpose





RLS-EXT-CONTThe Release External Control command is used to switch any of the four electrical relays, for controlling external devices, from operative mode to idle mode.

The external control relays can be configured for either normally closed or normally open mode and are connected to external devices through wire-wrap pins.

External control relays are normally inoperative and are switched into operative mode by the OPR-EXT-CONT command.

Note: Though the CONTTYPE value is optional it should be used to prevent errors. If an incorrect value to relay pair is entered then the command will be denied by the network element.


Input syntaxRLS-EXT-CONT:[TID]:AID:CTAG::[CONTTYPE];


Field Purpose


AID Access identifier. A group of values is acceptable.


CONTTYPE Optional parameter, the TYPE of control for which the control state is being set



Example inputSwitch external control 1, for air conditioning off at network element NEWYORK: RLS-EXT-CONT:NEWYORK:1:CTAG34::AIRCOND;

Switch off engine and fan on relays 2 and 3 respectively at network element WASHINGTON: RLS-EXT-CONT:WASHINGTON:2&3:CTAG45::ENGINE&FAN;



CONTACT NO. 1 to 4 Identify the contact number

ALL ALL Release relays 1 to 4. ALL not allowed if CONTTYPE is null.

Grouping #&#&#, #=1 to 4 Multiple contacts for example 1,2

DSM number-%HLINK-OC3-hslot#-hport#

DS1 service module office audible alarmsnumber = 1 to 4, hslot# = 3 to 10hport# = 1 to 4

ALL-%HLINK-HLINE-hslot#-hport#

All DS1 service module or MS-DSM office audible alarms

HLINE=OC3 or OC12hslot# = 3 to 10, hport# = 1 to 4



CONTTYPE null Optional parameter (ALL)

Not allowed when AID is ALL

AIRCOND air conditioning

ENGINE engine

FAN fan

GEN generator

HEAT heat

LIGHT light

MISC miscellaneous

SPKLR sprinkler



RLS-LPBK-EC1 The Release Loopback EC-1 command instructs the equipment to release an EC-1 facility loopback.


Input syntaxRLS-LPBK-EC1:[TID]:AID:CTAG;

Example input At the NEWYORK network element, release the EC-1 facility loopbackin slot 4 port 7 :

RLS-LPBK-EC1:NEWYORK:DS1-4-7:CTAG23;


Field Purpose






RLS-LPBK-ETHThe Release Loopback Ethernet command releases a loopback on an Ethernet facility (LAN port) of a 2x100BT-P2P, 8x100BT-P2P, 4x100FX-P2P, 2xGigE/FC-P2P, 2xGigE/FC-P2P-C or 2xGigE-P2P circuit pack.


Input syntaxRLS-LPBK-ETH:TID:AID:CTAG;

Example inputRelease the loopback on LAN port 1 of the 2x100BT-P2P circuit pack in slot 7 of network element OTTAWA:

RLS-LPBK-ETH:OTTAWA:ETH-7-1:CTAG23;


Field Purpose


AID Access identifier. The Ethernet facility to release from loopback mode.




ETH ETH-slot#-port# Identify the Ethernet facility where slot# = 3 to 10port# = 1 or 2


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



RLS-LPBK-FCThe Release Loopback Fibre Channel command releases a loopback on an Fibre Channel facility (LAN port) of a 2xGigE/FC-P2P or 2xGigE/FC-P2P-C circuit pack.


Input syntaxRLS-LPBK-FC:TID:AID:CTAG;

Example input2xGigE/FC-P2P circuit pack in slot 7 of network element OTTAWA: RLS-LPBK-FC:OTTAWA:FC-7-1:CTAG23;


Field Purpose


AID Access identifier. The Fibre Channel facility to release from loopback mode.




FC FC-slot#-port# Identify the Fibre Channel facility where slot# = 3 to 10port# = 1 or 2



RLS-LPBK-OC12 The Release Loopback OC12 command instructs the equipment to release an OC-12 facility loopback.


Input syntaxRLS-LPBK-OC12:[TID]:AID:CTAG;

Example inputAt the SEATTLE network element, release the loopback on the specified OC-12 facility: RLS-LPBK-OC12:SEATTLE:OC12-11-1:CTAG23;


Field Purpose






Details

OC-12 OC12-slot#-port# slot # = 3 to 12port # = 1 for OC-12port # = 1 to 4 for OC-12x4 STS




Note 1: After the loopback has been released, a cold restart of the OC-192 circuit pack is automatically performed.

Note 2: After the loopback has been released, you should clear any performance measurements that were collected while the OC-192 was in the loopback state. See INIT-REG-OC192 on page 3-149.



Example inputAt the SEATTLE network element, release the loopback on the specified OC-192 facility:

RLS-LPBK-OC192:SEATTLE:OC192-12:CTAG23;


Field Purpose






OC-192 OC192-slot# slot # = 11 or 12






Example inputAt the SEATTLE network element, release the loopback on the specified OC-3 facility: RLS-LPBK-OC3:SEATTLE:OC3-3-1:CTAG23RLS-LPBK-OC12


Field Purpose






Details

OC-3 OC3-slot# -port# slot # = 3 to 10port # = 1 to 4 for OC-3x4 or port# = 1 for OC-3






Example inputAt the SEATTLE network element, release the loopback on the specified OC-48 facility: RLS-LPBK-OC48:SEATTLE:OC48-12:CTAG23;


Field Purpose






Details

OC-48 OC48-slot# slot # = 11 or 12 for OC-48slot # = 3 to 12 for OC-48 STS



RLS-LPBK-T1The Release Loopback T1 command instructs the equipment to release a DS1 facility loopback.


Input syntaxRLS-LPBK-T1:[TID]:AID:CTAG;

Example input At the NEWYORK network element, release the DS1 facility loopback in slot 4 port 7:

RLS-LPBK-T1:NEWYORK:DS1-4-7:CTAG23;


Field Purpose






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

DS3V DS1-slot#-port#-t1# Identify DS1s on DS3VTx12 equipment whereslot# = 3, 5, 7, 9port# = 1 to 12t1# = 1 to 28

DSM or MS DSM


Identify the T1 facility on theDS1 service module or the MS-DSM whereHLINE=OC3 or OC12port# = 1 to 84hslot# = 3 to 10hport# = 1 to 4



RLS-LPBK-T3The Release Loopback T3 command instructs the equipment to release a DS3 facility loopback.


Input syntaxRLS-LPBK-T3:[TID]:AID:CTAG;

Example input At the SEATTLE network element, release the DS3 facility loopback in slot 7 port 1: RLS-LPBK-T3:SEATTLE:DS3-7-1:CTAG45;


Field Purpose






DS3 DS3-slot#-port# Identify the DS3 whereslot# = 3, 5, 7, or 9 port# = 1 to 3 for DS3x3port# = 1 to 12 for DS3x12, DS3x12e, or DS3VTx12

DSM or MS DSM DS3 Facility AID


slot = 3,5; port = 1 to 6

Hline = OC3 or OC12

Hslot = 3 to10

Hport = 1 to 4



RLS-PROTNSW-EQPTThe Release Protection Switch Equipment command instructs the network element to release any equipment protection switch requests that were initiated by the OPR-PROTNSW-EQPT command and are active on the entity specified. This command clears lockouts, forced switches and manual switches of DS1 circuit packs, and forced switches of DS3x3, DS3x12, DS3x12e, EC1x12, DS3/EC1x12, or DS3VTx12 circuit packs.


Input syntaxRLS-PROTNSW-EQPT:[TID]:AID:CTAG;


Field Purpose








DS3V AID DS3V-slot# Identify the DS3VTx12 whereslot# = 3 to 10

DS1 service module AID

DS1TM-slot#-%HLINK-HLINE-hslot#-hport#

Identify the DSM DS1x84 termination module, whereslot# = 1 or 2hslot# = 3 to 10hport# = 1 to 4



Example inputRelease any protection requests on the DS1 in slot 5:

RLS-PROTNSW-EQPT:SEATTLE:DS1-5:CTAG23;

MS-DSM AID AGGOC3-slot-%HLINK-OC3-Hslot-Hport#


AGGOC3OC12-slot-%HLINK-HLINE-Hslot-Hport#

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

EC1 AID EC1-slot# Identify the EC-1 whereslot# = 3 to 10

PECN MS DSM AID

PECN-slot-%HLINK-Hline-Hslot-Hport

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





RLS-PROTNSW-OC12The Release Protection Switch OC-12 command instructs the network element to release an OC-12 protection switch request. This command clears lockouts and forced switches on OC-12 or OC-12x4 STS circuit packs.


Input syntaxRLS-PROTNSW-OC12:[TID]:AID:CTAG;

Example inputPlace the OC-12 circuit pack in slot 10 back into normal mode: RLS-PROTNSW-OC12:SEATTLE:OC12-10-1:CTAG12;


Field Purpose






OC-12 AID OC12-slot#-port# Identify the OC-12 facilityslot# = 3 to 12port# = 1 for OC-12port# = 1 to 4 for OC-12x4 STS



RLS-PROTNSW-OC192The Release Protection Switch OC-192 command instructs the network element to release an OC-192 protection switch request. This command clears lockouts and forced switches on OC-192 circuit packs.


Input syntaxRLS-PROTNSW-OC192:[TID]:AID:CTAG::[SC];


Field Purpose




SC Switch command



OC-192 AID OC192-slot# Identifies the OC-192 facilityslot# = 11, 12



Example inputPlace the OC-192 circuit pack in slot 12 back into normal mode:

RLS-PROTNSW-OC192:SEATTLE:OC192-12:CTAG12;



SC MAN Release a manual switch in a BLSR system.

FRCD Release a forced switch in a 1+1 linear or BLSR system (default).

LOCKOUT Release a lockout on the protection circuit pack in a 1+1 linear system.

LOCKOUT_PROT Release the protection lockout in a BLSR system.(valid only for BLSR systems)

LOCKOUT_WRKG Release the working lockout in a BLSR system.(valid only for BLSR systems)

WTR End the wait-to-restore period and release the associated automatic switch for a BLSR system.(valid only for BLSR systems)



RLS-PROTNSW-OC3The Release Protection Switch OC-3 command instructs the network element to release an OC-3 protection switch request. This command clears lockouts and forced switches of OC-3 or OC-3x4 circuit packs.


Input syntaxRLS-PROTNSW-OC3:[TID]:AID:CTAG;

Example inputPlace the OC-3x4 circuit pack in slot 10 back into normal mode: RLS-PROTNSW-OC3:SEATTLE:OC3-10:CTAG12;


Field Purpose






OC-3 AID OC3-slot#-port# Identify the OC-3 where slot# = 3 to 10port# = 1 for OC-3port# = 1 to 4 for OC-3x4



RLS-PROTNSW-OC48The Release Protection Switch OC-48 command instructs the network element to release an OC-48 protection switch request. This command clears lockouts and forced switches on OC-48 and OC-48 STS circuit packs.


Input syntaxRLS-PROTNSW-OC48:[TID]:AID:CTAG::[SC];


Field Purpose




SC Switch command



OC-48 AID OC48-slot# Identifies the OC-48 facilityslot# = 11, 12 for OC-48slot# = 3 to 12 for OC-48 STS



Example inputPlace the OC-48 circuit pack in slot 12 back into normal mode:

RLS-PROTNSW-OC48:SEATTLE:OC48-12:CTAG12;



SC MAN Release a manual switch in a BLSR system.

FRCD Release a forced switch in a 1+1 linear or BLSR system (default).

LOCKOUT Release a lockout on the protection circuit pack in a 1+1 linear system.

LOCKOUT_PROT Release the protection lockout in a BLSR system.(valid only for BLSR systems)

LOCKOUT_WRKG Release the working lockout in a BLSR system.(valid only for BLSR systems)

WTR End the wait-to-restore period and release the associated automatic switch for a BLSR system.(valid only for BLSR systems)



RLS-PROTNSW-STS1The Release Protection Switch STS-1 command instructs the network element to release an STS-1 path protection switch request.


Input syntaxRLS-PROTNSW-STS1:[TID]:AID:CTAG;

Example inputPlace the STS-1 signal on OC-3x4 circuit pack in slot 10 port 1 sts1 back into normal mode: RLS-PROTNSW-STS1:SEATTLE:OC3-10-1-1:CTAG12;


Field Purpose






STS-1 facility AID

OC3-slot#-port#-sts#OC3-slot#-port#-ALL

Identify the STS-1 path on the OC-3 slot# = 3 to 10, port# = 1 to 4sts# = 1 to 3

OC12-slot#-port#-sts#OC12-slot#-port#-ALLOC12-ALL

Identify the STS-1 path on the OC-12 or OC-12x4 STSslot# = 3 to 12port# = 1 for OC-12port# = 1 to 4 for OC-12x4 STS sts# = 1 to 12

OC48-slot#-sts#OC48-slot#-ALLOC-48-ALL

Identify the STS-1 path on the OC-48 or OC-48 STSslot# = 11, 12 for OC-48slot# = 3 to 12 for OC-48 STSsts# = 1 to 48

OC192-slot#-sts#OC192-slot#-ALLOC-192-ALL

Identify the STS-1 path on the OC-192 slot# = 11, 12sts# = 1 to 192



RLS-PROTNSW-STS12C The Release Protection Switch STS-12c command instructs the network element to release an STS-12c path protection switch request.


Input syntaxRLS-PROTNSW-STS12C:[TID]:AID:CTAG;

Example inputPlace the STS-12c signal on OC-12 circuit pack in slot 10 sts 1 back into normal mode:

RLS-PROTNSW-STS12C:SEATTLE:OC12-10-1:CTAG12;


Field Purpose



CTAG Correlation tags



Purpose



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


slot# = 11, 12 for OC-48slot# = 3 to 12 for OC-48 STSsts# = 1, 13, 25, 37


slot# = 11, 12sts# = 1, 13, 25, 37, ... 181






Example inputPlace the STS-24c signal on OC-48 circuit pack in slot 10 sts 1 back into normal mode: RLS-PROTNSW-STS24C:SEATTLE:OC48-10-1:CTAG12;


Field Purpose






Purpose



slot# = 11, 12 for OC-48slot# = 3 to 12 for OC-48 STSsts# = 1, 25


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






Example inputPlace the STS-3c signal on OC-3x4 circuit pack in slot 10 port 1 sts 1 back into normal mode: RLS-PROTNSW-STS3C:SEATTLE:OC3-10-1-1:CTAG12;


Field Purpose






STS-3c facility AID

OC3-slot#-port#-sts#OC3-slot-port-#-ALLOC3-slot-ALL

Identify the STS-3c path on the OC-3slot# = 3 to 10, port# = 1 to 4sts# = 1


Identify the STS-3c path on the OC-12 or OC-12x4 STSslot# = 3 to 12 port# = 1 for OC-12port# = 1 to 4 for OC-12x4 STSsts# = 1, 4, 7 or 10


Identify the STS-3c path on the OC-48 or OC-48 STS slot# = 11, 12 for OC-48slot# = 3 to 12 for OC-48 STSsts# = 1, 4, 7, 10, ...to 46


Identify the STS-3c path on the OC-192 slot# = 11, 12sts# = 1, 4, 7, 10, ...to 190






Example inputPlace the STS-48c signal on OC-48 circuit pack in slot 10 sts 1 back into normal mode: RLS-PROTNSW-STS48C:SEATTLE:OC48-10-1:CTAG12;


Field Purpose






Purpose



slot# = 11, 12 for OC-48slot# = 3 to 12 for OC-48 STSsts# = 1, 25


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



RLS-PROTNSW-VT1The Release Protection Switch VT1 command instructs the network element to release a VT1.5 path protection switch request.


Input syntaxRLS-PROTNSW-VT1:[TID]:AID:CTAG;

Example inputPlace the VT1.5 signal on OC-3x4 circuit pack in slot 10, port 1, STS1#1, VTG#1, VT# 2 back into normal mode:

RLS-PROTNSW-VT1:SEATTLE:OC3-10-1-1-1-2:CTAG12;


Field Purpose






VT1.5 facility AID


Identify the VT1.5 path on the OC-3 slot# = 3 to 10port# = 1 to 4sts# = 1 to 3vtg# = 1 to 7vt# = 1 to 4


Identify the VT1.5 path on the OC-12 slot# = 3 to 12port# = 1sts# = 1 to 12vtg# = 1 to 7vt# = 1 to 4


Identify the VT1.5 path on the OC-48 slot# = 11, 12 sts# = 1 to 48vtg# = 1 to 7vt# = 1 to 4



RMV-EC1The Remove EC-1 command instructs a network element to change the state of the EC-1 facility from in service to out-of-service maintenance for memory administration. Once the EC-1 is removed from service, service-affecting tests or physical replacement of defective equipment can be initiated.


Input syntaxRMV-EC1:[TID]:AID:CTAG;

Example inputRemove the EC1 facility on the EC1 circuit pack in slot 7 port 1: RMV-EC1:NEWYORK:EC1-7-1:CTAG56;


Field Purpose


AID Access identifier. EC-1 to act on.




EC-1 EC1-slot#-port#EC1-slot#-ALL

Identify the EC-1 facility slot# = 3, 5, 7, 9 port # = 1 to 3 for EC-1x3port # = 1 to 12 for EC-1x12



RMV-EQPT The Remove Equipment command removes the specified type of common equipment module from service and puts it in an out-of-service maintenance for memory administration state (OOS-MA). Any facilities on the equipment must also be OOS for this to be permitted.


Input syntax RMV-EQPT:[TID]:AID:CTAG;


Field Purpose






Purpose




DS3/EC1 AID

DS3EC1-slot# Identify the DS3/EC1x12 equipment whereslot# = 3 to 10






OC-48 DWDM SFP AID










GE AID GE-slot#-port# Identify the 2xGigE 2.5G SFP module where slot# = 3, 5, 7, 9 port#=1, 2



100BTFOS AID

100BTFOS-slot# Identify the 2x100BT-P2P equipmentwhere 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



Purpose



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 input Put the DS1 circuit pack in slot 4 out of service: RMV-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


Identify the MS DSM DS3 Expansion equipment, whereHLINE=OC3 or OC12slot# = 3 to 6, hslot# = 3 to 10, hport# = 1 to 4


Identify the MS DSM 10/100BaseT Expansion equipment, whereHLINE=OC3 or OC12slot# = 3 to 6, hslot# = 3 to 10, hport# = 1 to 4


Identify the MS DSM OC-3 SFP, whereHLINE=OC3slot# = 1 or 2, port#=1, hslot# = 3 to 10, hport# = 1 to 4


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

CLX AID CLX-slot# Identify the VTX48, VTX40/10, or STX-192 equipment, whereslot# = 13 or 14



Purpose



RMV-ETHThe Remove Ethernet command changes an Ethernet facility (ETH port) of a 2x100BT-P2P, 8x100BT-P2P, 2xGigE/FC-P2P , 2xGigE/FC-P2P-C, 2xGigE-P2P or 4x100FX P2P circuit pack from an in-service (IS) state to an out-of-service management (OOS-MA) state.


Input syntax RMV-ETH:[TID]:AID:CTAG;

Example input Change ETH port 1 of the 2x100BT-P2P circuit pack in slot 7 of network element OTTAWA to an OOS-MA state:

RMV-ETH:OTTAWA:ETH-7-1:CTAG77;


Field Purpose


AID Access identifier. The Ethernet facility to change.





Identify the Ethernet facility where slot# = 3 to 10port# = 1 or 2



slot = 3 to 6; port = 1 to 8

Hline = OC3 or OC12

Hslot = 3 to10

Hport = 1 to 4



RMV-FCThe Remove Fibre Channel command changes a Fibre Channel facility (FC port) of a 2xGigE/FC-P2P or a 2xGigE/FC-P2P-C circuit pack from an in-service (IS) state to an out-of-service management (OOS-MA) state.


Input syntax RMV-FC:[TID]:AID:CTAG;

Example input Change FC port 1 of the 2xGigE/FC-P2P circuit pack in slot 7 of network element OTTAWA to an OOS-MA state: RMV-FC:OTTAWA:FC-7-1:CTAG77;


Field Purpose


AID Access identifier. The Fibre Channel facility to change.




FC FC-slot#-port#FC-slot#-ALL




RMV-OC12The Remove OC-12 command instructs a network element to change the state of the OC-12 facility from in service to out-of-service maintenance for memory administration. Once the OC-12 facility is removed from service, service-affecting tests or physical replacement of defective equipment can be initiated.


Input syntaxRMV-OC12:[TID]:AID:CTAG;

Example inputRemove the OC-12 facility on the OC-12 circuit pack in slot 7 port 1:

RMV-OC12:NEWYORK:OC12-7:CTAG56;


Field Purpose






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

Identify the OC-12 facility where slot# = 3 to 12 for OC-12slot# = 3 to 10 for OC-12x4 STS port# = 1 for OC-12port# = 1 to 4 for OC-12x4 STS





RMV-OC192The Remove OC-192 command instructs a network element to change the state of the OC-192 facility from in service to out-of-service maintenance for memory administration. After the OC-192 facility is removed from service, service-affecting tests or replacement of defective equipment can be initiated.



Example inputRemove the OC-192 facility on the OC-192 circuit pack in slot 11: RMV-OC192:NEWYORK:OC192-11:CTAG56;


Field Purpose









RMV-OC3The Remove OC-3 command instructs a network element to change the state of the OC-3 facility from in service to out-of-service maintenance for memory administration. Once the OC-3 is removed from service, service-affecting tests or physical replacement of defective equipment can be initiated.



Example inputRemove the OC-3 facility on the OC-3x4 circuit pack in slot 10 port 1:

RMV-OC3:NEWYORK:OC3-10-1:CTAG56;


Field Purpose






OC-3 AID OC3-slot#-port#OC3-slot#-ALL


DSM or MS DSM OC-3 Facility AID

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




RMV-OC48The Remove OC-48 command instructs a network element to change the state of the OC-48 facility from in service to out-of-service maintenance for memory administration. After the OC-48 facility is removed from service, service-affecting tests or replacement of defective equipment can be initiated.



Example inputRemove the OC-48 facility on the OC-48 circuit pack in slot 11: RMV-OC48:NEWYORK:OC48-11:CTAG56;


Field Purpose









RMV-SOCThe Remove Span of Control command is used to remove a network element from the NP span of control.


Input syntaxRMV-SOC:[TID]:SID:CTAG;

Example inputRemove network element NEWYORK from the span of control of OC3NP:

RMV-SOC:OC3NP:NEWYORK:CTAG13;


Field Purpose


SID System identifier. 1 to 20 alphanumeric characters or a text string enclosed within quotations.




RMV-T1The Remove T1 command instructs a network element to change the state of the DS1 from in-service to out-of-service maintenance for memory administration. Once the DS1 is removed from service, service-affecting tests or physical replacement of defective equipment can be initiated.


Input syntaxRMV-T1:[TID]:AID:CTAG;

Example inputRemove the DS1 facility on the DS1 circuit pack in slot 4 port 1: RMV-T1:NEWYORK:DS1-4-1:CTAG45;

Remove all the DS1 facilities on the DS1 circuit pack in slot 6: RMV-T1:CHARLESTON:DS1-6-ALL:CTAG78;


Field Purpose






DS1 AID DS1-slot#-port# DS1-slot#-ALL

Identify the DS1s where slot# =4 to 10, port# =1 to 12




DS1 service module port# = 1 to 84HLINE = OC3 or OC12hslot# = 3 to 10, hport# = 1 to 4


All DS1 ports on the DS1 service modulehslot# = 3 to 10hport# = 1 to 4



RMV-T3The Remove T3 command instructs a network element to change the state of the DS3 from in-service to out-of-service maintenance for memory administration. Once the DS3 is removed from service, service-affecting tests or physical replacement of defective equipment can be initiated.


Input syntaxRMV-T3:[TID]:AID:CTAG;

Example inputRemove the DS3 facility on the DS3 circuit pack in slot 5 port 1:

RMV-T3:TOMBSTONE:DS3-5-1:CTAG45;


Field Purpose





AID type


Purpose

T3 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 DS3 Facility AID


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



RST-BANNERThe Reset Banner command is used to replace the current login banner warning text with the login banner text saved to a backup file on 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.

If there is no login banner warning text saved to a backup file and you execute this command, the login banner warning text does not change.


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

Example inputReplace the login banner warning text for network element OTTAWA with the login banner text saved to a backup file on this network element:RST-BANNER:OTTAWA::CTAG93;


Field Purpose





RST-EC1The Restore EC-1 command instructs the network element to bring an EC-1 facility back into service from an out-of-service maintenance for memory administration state.


Input syntax RST-EC1:[TID]:AID:CTAG;

Example input Restore the EC-1 facility on the EC-1 circuit pack in slot 5 port 1: RST-EC1:NEWYORK:EC1-5-1:CTAG77;


Field Purpose


AID Access identifier. EC-1 facility to act on.




EC-1 AID EC1-slot#-port#EC1-slot#-ALL

Identify the EC-1 facility slot# = 3, 5, 7, 9 port # = 1 to 3 for EC-1x3port # = 1 to 12 for EC-1x12



RST-EQPTThe Restore Equipment command brings a given type of common equipment module back into service from an out-of-service maintenance for memory administration state.


Input syntaxRST-EQPT:[TID]:AID:CTAG;


Field Purpose






Purpose




DS3/EC1 AID DS3EC1-slot# Identify the DS3/EC1x12 equipment whereslot# = 3 to 10






OC-48 DWDM SFP AID










GE AID GE-slot#-port# Identify the 2xGigE 2.5G SFP module where slot# = 3, 5, 7, 9 port#=1, 2



100BTFOS AID 100BTFOS-slot# Identify the 2x100BT-P2P equipmentwhere 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



Purpose



Example inputPut the DS1 circuit pack in slot 4 back in to service for network element NEWYORK:

RST-EQPT:NEWYORK:DS1-4:CTAG34;

GEFC AID GEFC-slot#-port# Identify the 2xGigE/FC-P2P, 2xGigE/FC-P2P-C or 2xGigE-P2P SFP module, whereslot# = 3 to 10, port# = 1, 2

DS1TM AID DS1TM-slot#-%HLINK-OC3-hslot#-hport#

Identify the DSM DS1 termination module, where slot# = 1 or 2, hslot# = 3 to 10, hport# = 1 to 4

MS DSM AID AGGOC3-slot#-%HLINK-HLINE- hslot#-hport#

Identify MS DSM Aggregate equipment whereHLINE= OC3, slot# = 1 or 2, hslot# = 3 to 10, hport# = 1 to 4

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

Identify MS DSM Aggregate equipment whereHLINE= OC3 or OC12slot# = 1 or 2, hslot# = 3 to 10, hport# = 1 to 4


Identify MS DSM DS3 Expansion equipment, whereHLINE=OC3 or OC12slot# = 3 to 6, hslot# = 3 to 10, hport# = 1 to 4


Identify the MS DSM 10/100BaseT Expansion equipment, whereHLINE=OC3 or OC12, slot# = 3 to 6, hslot# = 3 to 10, hport# = 1 to 4


Identify the MS DSM OC-3 SFP, whereHLINE=OC3, slot# = 1 or 2, port#=1, hslot# = 3 to 10, hport# = 1 to 4


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

CLX AID CLX-slot# Identify the VTX48, VTX40/10, or STX-192 equipment , where slot# = 13 or 14



Purpose



RST-ETHThe Restore Ethernet command changes an Ethernet facility (ETH port) of a 2x100BT-P2P, 8x100BT-P2P, 2xGigE/FC-P2P, 2xGigE/FC-P2P-C, 2xGigE-P2P or 4x100FX P2P circuit pack from an out-of-service management (OOS-MA) state to an in-service (IS) state.


Input syntax RST-ETH:[TID]:AID:CTAG;

Example input Change ETH port 1 of the 2x100BT-P2P circuit pack in slot 7 of network element OTTAWA to an IS state: RST-ETH:OTTAWA:ETH-7-1:CTAG77;


Field Purpose


AID Access identifier. The Ethernet facility to change.





Identify the Ethernet facility where slot# = 3 to 10port# = 1 to 4 for 4x100FX-P2Pport# = 1 to 8 for 8x100BT-P2P

port# = 1 or 2



slot = 3 to 6; port = 1 to 8

Hline = OC3 or OC12

Hslot = 3 to10

Hport = 1 to 4



RST-FCThe Restore Fibre Channel command changes a Fibre Channel facility (FC port) of a 2xGigE/FC-P2P or a 2xGigE/FC-P2P-C circuit pack from an out-of-service management (OOS-MA) state to an in-service (IS) state.


Input syntax RST-FC:[TID]:AID:CTAG;

Example input Change FC port 1 of the 2xGigE/FC-P2P circuit pack in slot 7 of network element OTTAWA to an IS state: RST-FC:OTTAWA:FC-7-1:CTAG77;


Field Purpose


AID Access identifier. The Fibre Channel facility to change.




FC AID FC-slot#-port#FC-slot#-ALL




RST-OC12The Restore OC-12 command instructs the network element to bring an OC-12 facility back into service from an out-of-service maintenance for memory administration state.


Input syntax RST-OC12:[TID]:AID:CTAG;

Example input Restore the OC-12 facility on the OC-12 circuit pack in slot 11 port 1: RST-OC12:NEWYORK:OC12-11-1:CTAG77;


Field Purpose






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

Identify the OC-12s 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

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







Example input Restore the OC-192 facility on the OC-192 circuit pack in slot 11: RST-OC192:NEWYORK:OC192-11:CTAG77;


Field Purpose












Example input Restore the OC-3 facility on the OC-3x4 circuit pack in slot 9 port 1: RST-OC3:NEWYORK:OC3-9-1:CTAG77;


Field Purpose


AID Access identifier. OC-3s to act on.




OC-3 AID OC-3-slot#-port#OC-3-slot#-ALL


DSM or MS DSM OC-3 Facility AID








Example input Restore the OC-48 facility on the OC-48 circuit pack in slot 11: RST-OC48:NEWYORK:OC48-11:CTAG77;


Field Purpose









RST-PROVThe Restore Provisioning command is used to restore

• provisioning data (including that backed-up from circuit packs) to a shelf processor from a locally attached PC. This function can only be executed by a user through Site Manager.

• provisioning data (including that backed-up from circuit packs) to a shelf processor from a network processor

• provisioning data (including that backed-up from a shelf processor) to a network processor from a UNIX workstation or an Operations Controller (OPC)

The RST-PROV command

• does some basic checks on the integrity of the restored data

• compares the software release listed in the backup data with the current software release running on the network element (NE). If they are not the same, the restoration fails.

• if CHKTID=Y or CHKTID is omitted, the RST-PROV command compares the TID of the network element to which provisioning data is being restored with the stored TID. If they are not the same, the restoration fails.

The RST-PROV command is supported on the network element and network processor.

Note: The RST-PROV command is not allowed if there is an alarm present on the network processor or shelf processor circuit pack receiving the command when it is in one of the following states: upgrade in progress; load mismatch; IS rollover in progress; duplicate SID; database save and restore in progress.


Input syntaxRST-PROV:[TID]::CTAG::[USERID],[PASSWD]:DESTTYPE=Domain[,DESTADDR=Domain][,DIR=Domain][,CHKTID=Domain][,CHKALM=Domain];




Field Purpose



USERID User login name

PASSWD User login password

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

DESTADDR Address of the DESTTYPE (TID or IP) which is the source of the Restore

For a DESTTYPE of PC, omit DESTADDR

DIR Directory in which the backed-up provisioning data is stored.

CHKTID Check TID

Specifies whether the operation does or does not compare the TID from which the backup was saved with the TID of the shelf processor or network processor to which the backup is being restored.




UID 1 to 10 alphanumeric characters

A unique, non-confidential identifier used to identify each authorized system user.

PASSWD 8 to 10 alphanumeric characters

A confidential code name used to activate a user login session.



PC A local restore will be executed between a shelf processor and a locally attached PC.



DESTADDR TID address Name of the Restore source (a network element or network processor) consisting of an identifier of 7 to 20 alphanumeric characters. The first character is alphabetic.

DESTADDR(continued)

IP address The address of the Restore source (a networkelement or network processor) consisting of an identifier in the format x.x.x.x (where x=a number 0-255).

DIR Directory name A string of characters that specifies the unique directory name in which the backup is stored.

If a directory name parameter is not specified in the command, when restoring provisioning data from a network processor to a shelf processor that is in its span of control, the shelf processor uses its TID to derive a default directory name.

Note: The shelf processors only derive a default directory name if they are in the span of control of the destination network processor.

When restoring network processor provisioning data from an external repository, the name of the directory in which the data is stored must be specified in the command or the command fails. (That is, there is no default directory name.) The directory name is a string of 1 to 60 characters.


N Do not check the TID (Note)

CHKALM Y (default) The RST-PROV is not allowed if there is an alarm present on the network processor or shelf processor circuit pack.

N The RST-PROV is allowed if there is an alarm present on the network processor or shelf processor card receiving the command except if it is in one of the following states: upgrade in progress; load mismatch; IS rollover in progress; duplicate SID; database save and restore in progress.

Note: To restore the provisioning data of a shelf processor to a shelf processor with a different TID or the provisioning data of a network processor to a network processor with a different TID, set CHKTID to N.





Example inputRestore provisioning data stored on network processor MONTREAL to its original shelf processor in OTTAWA:

RST-PROV:OTTAWA::CTAG96:::DESTTYPE=TID,DESTADDR=MONTREAL,DIR=”/saverest/NE01”,CHKTID=N;

Restore provisioning data stored on a UNIX workstation to its original network processor MONTREAL:

RST-PROV:MONTREAL::CTAG96::”abc123”,”Sam4test”:DESTTYPE=IP,DESTADDR=47.100.3.54,DIR=”/home/sam/saverest”,CHKTID=N;

Restore provisioning data stored on directory /xyz/ from the OPC TORONTO to its original network processor OTTAWA:

RST-PROV:OTTAWA::CTAG96::”userid”,Passwd01”:DESTTYPE=TID,DESTADDR=TORONTO,DIR=”/xyz”,CHKTID=N;

Restore provisioning data stored on directory /xyz/ from the OC-192 OPC of network element BOSTON to its original network processor NEWYORK:

RST-PROV:NEWYORK::CTAG96::”userid”,Passwd01”:DESTTYPE=IP,DESTADDR=47.100.3.54,DIR=”/xyz”,CHKTID=N;



RST-PROV-SPThe Restore Provisioning SP command is used to restore provisioning data from a remote location with a TID or IP address to a designated SP within an NP span of control.

The RST-PROV-SP command

• does some basic checks on the integrity of the restored data

• compares the software release listed in the backup data with the current software release running on the network element (NE). If they are not the same, the restoration fails.

If CHKTID=Y or CHKTID is omitted, the RST-PROV-SP command compares the TID of the network element to which provisioning data is being restored with the stored TID. If they are not the same, the restoration fails.


Input syntaxRST-PROV:[TID]::CTAG::[USERID],[PASSWD]:TRGTID=Domain,DESTTYPE=Domain,DESTADDR=Domain[,DIR=Domain][,CHKTID=Domain][,CHKALM=Domain];


Field Purpose



USERID User login name

PASSWD User login password

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

DESTTYPE Source of the Restore — TID or IP

DESTADDR Address of the DESTTYPE (TID or IP) which is the source of the Restore



DIR Directory in which the backed-up provisioning data is stored.

CHKTID Check TID

Specifies whether the operation does or does not compare the TID from which the backup was saved with the TID of the shelf processor to which the backup is being restored.




USER ID 1 to 10 alphanumeric characters

A unique, non-confidential identifier used to identify each authorized system user.

PASSWD 8 to 10 alphanumeric characters

A confidential code name used to activate a user login session.



DESTADDR TID address Name of the Restore source (a remote location) consisting of an identifier of 7 to 20 alphanumeric characters. The first character is alphabetic.

IP address The address of the Restore source (a remote location) consisting of an identifier in the format x.x.x.x (where x=a number 0-255).

DIR Directory name A string of characters that specifies the unique directory name in which the backup is stored.

When restoring shelf processor provisioning data from a remote location, the name of the directory in which the data is stored must be specified in the command or the command fails. (That is, there is no default directory name.) The directory name is a string of 1 to 60 characters.


Field Purpose



Example inputRestore provisioning data stored on a remote location to its original shelf processor MONTREAL:

RST-PROV-SP:MONTREAL::CTAG96::”abc123”,”Sam4test”:TRGTID=MONTREALNP,DESTTYPE=IP,DESTADDR=47.100.3.54,DIR=”/home/sam/saverest”,CHKTID=N,CHKALM=Y;


N Do not check the TID

To restore the provisioning data of a shelf processor to a shelf processor with a different TID, set CHKTID to N.

CHKALM Y (default) The RST-PROV-SP is not allowed if there is an alarm present on the shelf processor circuit pack.

N The RST-PROV-SP is allowed if there is an alarm present on the shelf processor circuit pack receiving the command except if it is in one of the following states: upgrade in progress; load mismatch; IS rollover in progress; duplicate SID; database save and restore in progress.





RST-T1The Restore T1 command instructs a network element to bring a DS1 line facility back into service from an out-of-service maintenance for memory administration state.


Input syntaxRST-T1:[TID]:AID:CTAG;

Example inputRestore DS1 facility # 7 on the DS1 circuit pack in slot 4:

RST-T1:NEWYORK:DS1-4-7:BM001;

Restore all the DS1 facilities on the DS1 circuit pack in slot 6:

RST-T1:SEATTLE:DS1-6-ALL:CK002;


Field Purpose






DS1 AID DS1-slot#-port#DS1-slot#-ALL

Identify the DS1s where

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




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


All DS1 ports on the DS1 service modulehslot# = 3 to 10hport# = 1 to 4



RST-T3The Restore T3 command instructs a network element to bring a DS3 line facility back into service from an out-of-service maintenance for memory administration state.


Input syntax RST-T3:[TID]:AID:CTAG;

Example inputRestore the DS3 facility on the DS3 circuit pack in slot 5 port 1: RST-T3:NEWYORK:DS3-5-1:CTAG01;


Field Purpose





AID type


Purpose

T3 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


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


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 2 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.2.r16

Documents