1677 sonet link operation and administration · 1677 sonet link operation and administration pn...

1677 SONET LinkOperation and Administration

PN 3EM13851AD 02R05.00, Issue 02, July 2006

Alcatel 2002-2006 - All Rights ReservedPrinted in U.S.A.

THIS PRODUCT COMPLIES WITH D.H.H.S. RADIATION PERFORMANCE STANDARDS 21CFR, 1040.10, FOR A CLASS 1 LASER PRODUCT.

DANGER

Invisible laser radiation is present when the optic connector is open. AVOID DIRECTEXPOSURE TO BEAM.

WARNING

This equipment has been tested and found to comply with the limits for a Class A digital device, pursuantto Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmfulinterference when the equipment is operated in a commercial environment. This equipment generates,uses, and can radiate radio frequency energy and, if not installed and used in accordance with theinstruction manual, may cause harmful interference to radio communications. Operation of this equipmentin a residential area is likely to cause harmful interference in which case users will be required to correct theinterference at their own expense.

NOTICE

This manual applies to 1677 SONET Link R05.00 software. Release notes describing revisions to thissoftware may impact operations described in this manual.

This transfer of commodities, technology, or software, if from the United States, is an export in accordancewith the U.S. Export Administration Regulations. Diversion contrary to U.S. law is prohibited. The export orre-export (further transfer) of such commodities, technology, software or products made from suchtechnology is prohibited without proper authorization(s) from the U.S. Department of Commerce or otherappropriate U.S. government agency(s).

All rights reserved. No part of this manual may be reproduced, translated, stored in a retrieval system, ortransmitted or distributed by any means, electronic or mechanical, by photocopying, recording, or otherwise,without the written permission of Alcatel. Preparing derivative works or providing instruction based on thematerial is prohibited unless agreed to in writing by Alcatel.

The product specification and/or performance levels contained in this document are for informationpurposes only and are subject to change without notice. They do not represent any obligation on the part ofAlcatel. Such obligations will only be committed to in a written sales agreement signed by Alcatel.

DOCUMENTATION

Product documentation is available on Alcatel’s Online Support Documentation and Software web site athttp://www.alcatel.com/osds.

To offer comments on this documentation, visit Alcatel’s Online Support Documentation and Software website at http://www.alcatel.com/osds and select Online Services Helpdesk or write to the following address.

AlcatelAttention: Doc Comment, MS OLXDV

3400 W. Plano Pkwy.Plano, Texas 75075 USA

3EM13851ADIssue 02, July 2006

Change History

1677 SONET Link Operation and Administration

ISSUE ISSUE DATE SECTION REASON01 May 2006 Entire manual New software release02 July 2006 Entire manual Add missing TL1 information


ALCATEL PRACTICEStandard

1677 SONET Link Operation and AdministrationTable of Contents

Introduction

1. OVERVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Writing Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Admonishments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Document Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

2. 1677 SONET Link Element Management Application (EMA) . . . . . . . . . . . . . . . . . 1-5Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5Alcatel Management Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5Node Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14

3. TL1DAT Only Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-61

4. COMMAND STRUCTURE AND SYNTAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-65Command Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-65Input Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-66Special Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-68Ranging and Grouping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-70

5. MODES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-71TL1DAT Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-71TL1 Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-74

6. SYSTEM MESSAGES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-77Response Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-77In-Progress Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-78Alarm Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-79

7. PRODUCT SUPPORT INFORMATION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-81Telephone Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-81Product Documentation and Training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-81Technical Assistance Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-83Repair and Return Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-84Spare Parts and Replacement Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . 1-84Service Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-85Installation and Maintenance Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-87

© Alcatel 2002-2006 - All Rights Reserved i


Index Task Lists (IXLs)

IXL-100 Index Task List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

IXL-101 User Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

IXL-102 Auxiliary Equipment Provisioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

IXL-103 Equipment Provisioning and Deprovisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

IXL-104 System Information Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

IXL-105 System Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11

IXL-106 DS3 (T3) Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13

IXL-107 DS1 (T1) Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15

IXL-108 OC-n Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17

IXL-109 STS-n Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19

IXL-110 VT1.5 Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21

IXL-111 Gigabit Ethernet Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23

IXL-112 Transmux Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25

IXL-113 EDFA (OFA) Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27

IXL-114 EVC Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29

IXL-115 EC1 Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31

Non-trouble Procedures (NTPs)

NTP-100 DS3 (T3) Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

NTP-101 DS1 (T1) Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

NTP-102 OC-n Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

NTP-103 STS-n Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9

NTP-104 VT1.5 Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11

NTP-105 Gigabit Ethernet Provisioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13

Table of Contentsii


NTP-106 DS3 (T3) Deprovisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15

NTP-107 DS1 (T1) Deprovisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17

NTP-108 OC-n Deprovisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21

NTP-109 STS-n Deprovisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23

NTP-110 VT1.5 Deprovisioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25

NTP-111 Gigabit Ethernet Deprovisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27

NTP-112 Transmux Provisioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29

NTP-113 Transmux Deprovisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31

NTP-114 Optical Fiber Amplifier Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33

NTP-115 Optical Fiber Amplifier Deprovisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35

NTP-116 EVC Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-37

NTP-117 EVC Deprovisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-39

NTP-118 EC1 Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-41

NTP-119 EC1 Deprovisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43

NTP-120 GIGE Circuit Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-45

NTP-121 GIGE Circuit Deprovisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-47

Detailed Level Procedures (DLPs)

DLP-100 Log Into System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

DLP-101 Log Out of System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

DLP-102 Change User Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7

DLP-103 Configure U.S. Robotics 56K Faxmodem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9

DLP-104 Retrieve System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15

DLP-105 Initialize System Processors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17

DLP-106 Set User and System Security Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21

Table of Contents iii


DLP-107 Set System Date and Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27

DLP-108 Administer System Timing/BITS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-29

DLP-109 Retrieve Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-35

DLP-110 Enter Trusted Host for Dynamic IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-37

DLP-111 Display Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-39

DLP-112 Provision Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-43

DLP-113 Deprovision Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-49

DLP-114 Provision EC1 Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-57

DLP-115 Provision DS3 (T3) Facility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-59

DLP-116 Provision OC-n Facility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-65

DLP-117 Provision STS-n Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-71

DLP-118 Provision VT1.5 Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-77

DLP-119 Administer OC-n Facility Protection Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-81

DLP-120 Deprovision DS3 (T3) Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-89

DLP-121 Deprovision OC-n Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-93

DLP-122 Deprovision STS-n Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-95

DLP-123 Deprovision VT1.5 Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-99

DLP-124 Administer DS3 Cross-Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-103

DLP-125 Administer STS-n Cross-Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-109

DLP-126 Administer VT1.5 Cross-Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-115

DLP-127 Set EC1 PM Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-121

DLP-128 Set DS1 PM Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-123

DLP-129 Set OFA PM Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-125

DLP-130 Administer T3 Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-127

Table of Contentsiv


DLP-131 Administer OC-n Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-135

DLP-132 Switch OC-n Line to Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-141

DLP-133 Schedule PM Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-147

DLP-134 Report DS3 PM Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-151

DLP-135 Report OC-n PM Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-155

DLP-136 Report STS-n PM Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-159

DLP-137 Report VT1.5 PM Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-163

DLP-138 Set DS3 PM Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-167

DLP-139 Set OC-n PM Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-169

DLP-140 Set STS-n PM Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-171

DLP-141 Set VT1.5 PM Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-173

DLP-142 Set DS3 PM Threshold Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-175

DLP-143 Set OC-n PM Threshold Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-177

DLP-144 Set STS-n PM Threshold Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-179

DLP-145 Set VT1.5 PM Threshold Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-181

DLP-146 Add New User to System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-183

DLP-147 Delete User from System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-185

DLP-148 Administer STS-n Test Access Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-187

DLP-149 Switch STS-n Path to Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-191

DLP-150 Clean Fiber-Optic Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-197

DLP-151 Administer OC-n UPSR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-207

DLP-152 Administer VT1.5 Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-215

DLP-153 Set Alarm Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-221

DLP-154 Provision Gigabit Ethernet Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-223

Table of Contents v


DLP-155 Deprovision Gigabit Ethernet Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-227

DLP-156 Administer OC-n BLSR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-229

DLP-157 Administer Dual Ring Interconnect (DRI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-247

DLP-158 Deprovision EC1 Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-263

DLP-159 Administer EC1 Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-265

DLP-160 Provision DS1 (T1) Facility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-271

DLP-161 Deprovision DS1 (T1) Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-275

DLP-162 Enable TL1 Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-279

DLP-163 Retrieve Remote Inventory (RI) Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-281

DLP-164 Administer Gigabit Ethernet Cross-Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-285

DLP-165 Set Gigabit Ethernet PM Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-295

DLP-166 Set Gigabit Ethernet PM Threshold Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-297

DLP-167 Report Gigabit Ethernet PM Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-299

DLP-168 Enable/Disable Automatic Generation of Squelch and Ring Maps . . . . . . . . . . . . . . 4-303

DLP-169 Restart Laser for OC-n Facility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-309

DLP-170 Set EC1 PM Threshold Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-311

DLP-171 Provision Ethernet Virtual Concatenation (EVC) Port . . . . . . . . . . . . . . . . . . . . . . . . 4-313

DLP-172 Deprovision Ethernet Virtual Concatenation (EVC) Port . . . . . . . . . . . . . . . . . . . . . . 4-317

DLP-173 Administer TL1 Gateway Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-319

DLP-174 Retrieve/ Change Site Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-321

DLP-175 Reprogram Equipment Flash Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-323

DLP-176 Retrieve Node IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-329

DLP-177 Administer DS1 Cross-Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-331

DLP-178 Report DS1 PM Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-337

Table of Contentsvi


DLP-179 Retrieve VSC and TMUX Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-341

DLP-180 Inhibit/Allow Protection Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-343

DLP-181 Provision Optical Fiber Amplifier (OFA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-347

DLP-182 Report EC1 PM Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-349

DLP-183 Deprovision Optical Fiber Amplifier (OFA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-353

DLP-184 Administer DS3 Test Access Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-355

DLP-185 Report OFA PM Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-359

DLP-186 Set OFA PM Threshold Levels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-363

DLP-187 Set DS1 PM Threshold Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-365

DLP-188 Perform FTP Backup of Provisioning Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-367

DLP-189 Perform FTP Restore of Provisioning Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-371

DLP-190 Retrieve Disk Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-375

DLP-191 Activate Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-379

DLP-192 Connect PC to the 1677 SONET Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-383

DLP-193 Change Facility Service State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-385

DLP-194 Perform Manual Protection Switch for Working Cards. . . . . . . . . . . . . . . . . . . . . . . . 4-389

DLP-195 Switch to Redundant Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-393

DLP-196 Set Default Thresholds for All Cross-Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . 4-395

DLP-197 Change Line Buildout (LBO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-397

DLP-198 Issue TL1 Commands Through a Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-401

DLP-199 Administer STS-n Facility Protection Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-403

DLP-200 Administer T1 Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-409

DLP-201 Configure PC as FTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-417

DLP-202 Add Node to UPSR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-423

Table of Contents vii


DLP-203 Delete Node from UPSR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-439

DLP-204 Add Node to Two-Fiber BLSR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-449

DLP-205 Delete Node from Two-Fiber BLSR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-469

DLP-206 Perform Database Backup to Flash Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-481

DLP-207 Perform Database Restore from Flash Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-491

DLP-208 Administer T1 Test Access Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-499

DLP-209 Administer VT1 Test Access Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-503

DLP-210 Configure EMA and TL1DAT on PC for NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-507

DLP-211 Modify DS1 (T1) Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-511

DLP-212 Modify DS3 (T3) Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-515

DLP-213 Modify EC1 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-519

DLP-214 Modify GIGE Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-521

DLP-215 Modify OC-n Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-523

DLP-216 Modify OFA Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-527

DLP-217 Modify STS-n Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-529

DLP-218 Modify VT1.5 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-533

DLP-219 Administer Far-End Alarm and Control (FEAC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-537

DLP-220 Retrieve TL1 Commands Available for User Level . . . . . . . . . . . . . . . . . . . . . . . . . . 4-541

DLP-221 Enable/Disable Database Change Autonomous Messages . . . . . . . . . . . . . . . . . . . 4-545

DLP-222 Connect 1677 SONET Link to FES301 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-547

DLP-223 Build DCC Network Links. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-557

DLP-224 Set Up UPSR Operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-559

DLP-225 Set Up BLSR Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-561

DLP-226 Provision ECC Within DS3 Protection Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-565

Table of Contentsviii


DLP-227 1677 SONET Link Emergency Shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-571

Software Reference Guide

1. INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

2. STATES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3State Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3Primary State Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3Secondary State Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

3. CODES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7Equipment Condition Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7Facility Condition Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9Common Condition Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14Transient Condition Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14Notification Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19Service Affect Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20Command Privilege Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20Response (Error) Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-38Command Parser Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-40

4. SECURITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-43Controlling System Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-43Controlling Access to System Resources. . . . . . . . . . . . . . . . . . . . . . . . . . 5-47Obtaining Security Audit Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-48

5. PERFORMANCE MONITORING. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-51Storage Registers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-52Register Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-52Validity Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-53Threshold Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-54Threshold Crossing Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-54Scheduling Daily PM Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-55Suppressing Scheduled PM Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-55Retrieving Selective PM Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-55Monitored Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-56

6. TEST ACCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-67Monitor Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-68Split Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-69Loop Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-72

7. IP CONFIGURATION OPTIONS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-75Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-75

Table of Contents ix


Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-76Advanced Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-87

Table of Contentsx


1677 SONET Link Operation and AdministrationList of FiguresFigure 2-1. Alcatel Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

Figure 2-2. Context Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

Figure 2-3. Property Window with Mutable Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8

Figure 2-4. Create New User Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9

Figure 2-5. Allow Event All Options Dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10

Figure 2-6. Misaligned State Informational Message Boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11

Figure 2-7. Warning Message Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11

Figure 2-8. Error Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12

Figure 2-9. Set NE Date and Time Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22

Figure 2-10. Details View of Equipment Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-23

Figure 2-11. Graphical View of Equipment Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-24

Figure 2-12. Facility Type Node with Facility Groups in Results Pane. . . . . . . . . . . . . . . . . . . . . . . 1-32

Figure 2-13. Create CrossConnection Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-52

Figure 2-14. Facility Browser Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-54

Figure 2-15. Manage CrossConnections Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-55

Figure 5-1. TL1DAT Enhanced Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-72

Figure 5-2. TL1DAT Basic Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-74

Figure 103-1. Modem Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10

Figure 103-2. US Robotics Modem Connection to System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14

Figure 112-1. Shelf Card Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-45

Figure 115-1. DS3 Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-61

Figure 115-2. STS-1 Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-61

List of Figures xi


Figure 116-1. OC-3 Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-65

Figure 116-2. OC-12 Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-66

Figure 116-3. OC-48 Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-67

Figure 116-4. OC-192 Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-68

Figure 117-1. STS-1 Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-73

Figure 118-1. VT1 Provisioning in an OC-n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-78

Figure 119-1. Example of OC-3 Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-82

Figure 130-1. DS3 Loopback Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-128

Figure 130-2. Equipment Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-128

Figure 130-3. Facility Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-129

Figure 130-4. FEND Line Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-129

Figure 130-5. ALLDS1LINE Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-130



Figure 150-1. Fiber-Optic Connector Inspection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-200

Figure 150-2. Fiber-Optic Connector Types, Illustrations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-201

Figure 150-3. Fiber-Optic Connector Types, Photographs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-202

Figure 150-4. Optical Removal and Cleaning Tool (PN 3EM07060AAAA) . . . . . . . . . . . . . . . . . . . 4-203


Figure 154-1. GIGE Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-224

Figure 157-1. One-Node Ring Interconnect Cross-Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-249

Figure 157-2. Two-Node Ring Interconnect Cross-Connections: UPSR-UPSR. . . . . . . . . . . . . . . . 4-250

Figure 157-3. Two-Node Ring Interconnect Cross-Connections: UPSR-BLSR and BLSR-UPSR. . 4-251

Figure 157-4. Two-Node Ring Interconnect Cross-Connections: BLSR-BLSR . . . . . . . . . . . . . . . . 4-252

List of Figuresxii


Figure 157-5. Four-Node Ring Interconnect Cross-Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-254




Figure 164-2. GIGE Video Broadcast Applications in BLSR and UPSR . . . . . . . . . . . . . . . . . . . . . 4-287

Figure 164-3. GIGE Cross-Connection Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-288



Figure 200-2. Line Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-410

Figure 200-3. Payload Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-411

Figure 200-4. DS1FEAC Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-411

Figure 202-1. Sample UPSR Configuration Before and After Node is Added . . . . . . . . . . . . . . . . . 4-424

Figure 202-2. Fiber Connections Before New Node is Added . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-429

Figure 202-3. Fiber Connections after New Node is Added . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-430


Figure 202-5. Fiber Connections After New Node is Added. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-437

Figure 203-1. Fiber Connections to be Removed from Node to be Deleted . . . . . . . . . . . . . . . . . . 4-442

Figure 203-2. Fiber Connections after Node is Deleted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-443

Figure 204-1. Sample BLSR Configuration Before and After Adding Node . . . . . . . . . . . . . . . . . . . 4-450


Figure 204-3. Fiber Connections after New Node is Added . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-454


Figure 204-5. Fiber Connections After New Node is Added. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-462

Figure 205-1. Fiber Connections to be Removed from Node to be Deleted . . . . . . . . . . . . . . . . . . 4-472

List of Figures xiii


Figure 205-2. Fiber Connections after Node is Deleted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-473

Figure 226-1. Shelf Card Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-566

Figure 227-1. A and B Power Sitch Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-571

Figure 6-1. MONE Test Access Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-68

Figure 6-2. MONF Test Access Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-69

Figure 6-3. MONEF Test Access Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-69

Figure 6-4. SPLTA Test Access Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-71

Figure 6-5. SPLTB Test Access Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-71

Figure 6-6. SPLTE Test Access Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-71

Figure 6-7. SPLTF Test Access Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-72

Figure 6-8. SPLTEF Test Access Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-72

Figure 6-9. LOOPE Test Access Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-73

Figure 6-10. LOOPF Test Access Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-74

Figure 7-1. Stand-Alone Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-76

Figure 7-2. Stand-Alone Node with Router. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-77

Figure 7-3. Multiple Co-Located Nodes without DCC Connectivity - Example 1 . . . . . . . . . . . . . . 5-79

Figure 7-4. Multiple Co-Located Nodes without DCC Connectivity - Example 2 . . . . . . . . . . . . . . 5-80

Figure 7-5. Multiple Nodes with DCC Connectivity - Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . 5-83

Figure 7-6. Multiple Nodes with DCC Connectivity - Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . 5-84

Figure 7-7. Passing Non-TL1 Management Traffic to Attached Ethernet Devices. . . . . . . . . . . . . 5-88

List of Figuresxiv


1677 SONET Link Operation and AdministrationList of TablesTable 2-A. Icons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13

Table 3-A. TL1DAT Only Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-61

Table 4-A. TL1 Special Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-69

Table 100-A. Index Task List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Table 101-A. Common User Administration Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Table 102-A. Auxiliary Equipment Provisioning Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

Table 103-A. Equipment Provisioning and Deprovisioning Functions . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

Table 104-A. System Information Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

Table 105-A. System Administration Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11

Table 106-A. DS3 (T3) Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13

Table 107-A. DS1 (T1) Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15

Table 108-A. OC-n Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17

Table 109-A. STS-n Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19

Table 110-A. VT1.5 Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21

Table 111-A. Gigabit Ethernet Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23

Table 112-A. Transmux Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25

Table 113-A. EDFA Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27

Table 114-A. EVC Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29

Table 115-A. EVC Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31

Table 103-A. Modem Settings and Configuration for Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13

Table 112-A. Card Type Parameter Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-44

Table 112-B. Valid Slot Locations for I/O Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-44

List of Tables xv


Table 112-C. Slot Definitions for ECC and DS3 Card Protection Groups . . . . . . . . . . . . . . . . . . . . . 4-44

Table 113-A. Procedures Required Before Deprovisioning Cards . . . . . . . . . . . . . . . . . . . . . . . . . . 4-49

Table 115-A. Valid T3 Provisioning Combinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-60

Table 115-B. STSMAP Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-60

Table 117-A. STSMAP Parameter Values for STS-1 Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . 4-72

Table 119-A. Valid OC-n Facility Protection Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-86

Table 130-A. Allowed Loopback Type for Specific T3 Configuration and Location . . . . . . . . . . . . . 4-127

Table 151-A. OC-n UPSR Nodes PROTECTED_ID and PROTECTING_ID Pairs . . . . . . . . . . . . . 4-207

Table 156-A. OC-n BLSR Nodes Protected and Protecting Pairs . . . . . . . . . . . . . . . . . . . . . . . . . 4-229

Table 157-A. One-Node Ring Interconnect Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-250

Table 157-B. Two-Node Ring Interconnect Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-253

Table 157-C. Four-Node Ring Interconnect Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-254

Table 163-A. RI Data Visible per Equipment Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-281

Table 164-A. GIGE Allowed Cross-Connections and Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . 4-289

Table 175-A. TMUX Working and Protection Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-323

Table 197-A. LBO Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-397

Table 199-A. Valid STS-n Facility Protection Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-404

Table 200-A. Allowed Loopback Type for Provisioned T1 Framing Format . . . . . . . . . . . . . . . . . . 4-409

Table 202-A. OC-n UPSR Nodes PROTECTED_ID and PROTECTING_ID Pairs . . . . . . . . . . . . . 4-423

Table 204-A. OC-n BLSR Nodes Protected and Protecting Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . 4-449

Table 210-A. PC Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-508

Table 212-A. Valid T3 Provisioning Combinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-515

Table 217-A. STSMAP Parameter Values for STS-1 Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . 4-530

Table 222-A. FES301 Module Software Revision and Software Release . . . . . . . . . . . . . . . . . . . . 4-548

List of Tablesxvi


Table 222-B. STS-1 to Mid Speed Slot Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-554

Table 226-A. Card Type Parameter Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-565

Table 226-B. Valid Slot Locations for DS3 and ECC I/O Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-565

Table 226-C. Slot Definitions for ECC and DS3 Card Protection Groups . . . . . . . . . . . . . . . . . . . . 4-566

Table 2-A. Primary State Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

Table 2-B. Secondary State Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

Table 3-A. 1677 SONET Link Equipment Condition Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7

Table 3-B. 1677 SONET Link Configuration Facility Condition Types. . . . . . . . . . . . . . . . . . . . . . . 5-9

Table 3-C. Transient Condition Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15

Table 3-D. Notification Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20

Table 3-E. Service Affect Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20

Table 3-F. Command Access Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21

Table 3-G. Response (Error) Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-39

Table 3-H. Command Parser Error Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-41

Table 5-A. Number of Registers for Each PM Parameter Monitored. . . . . . . . . . . . . . . . . . . . . . . 5-52

Table 5-B. DS3 PM Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-57

Table 5-C. OC-3 PM Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-58

Table 5-D. OC-12 PM Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-59

Table 5-E. OC-48 PM Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-60

Table 5-F. OC-192 PM Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-61

Table 5-G. STS-1 PM Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-62

Table 5-H. STS-3c PM Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-62

Table 5-I. STS-12c PM Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-63

Table 5-J. STS-48c PM Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-63

List of Tables xvii


Table 5-K. VT1.5 PM Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-64

Table 5-L. EDFA (OFA) PM Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-64

Table 5-M. GIGE PM Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-64

Table 5-N. EC1 PM Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-65

Table 5-O. T1 PM Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-66

Table 7-A. Allowed Combinations of Section DCC and Line DCC . . . . . . . . . . . . . . . . . . . . . . . . 5-75

List of Tablesxviii


Introduction

1. OVERVIEW

1.1 This user's guide provides step-by-step procedures to help users perform tasks. Each procedure contains important introductory information that is essential to understanding and completing the task properly. Procedures must be started at step 1, and steps must be performed in the order given. Failure to do so may cause unforeseen hazardous conditions.

Writing Conventions

1.2 Boldface characters indicate commands or parameters that must be entered or keys that must be pressed. Enter input parameters exactly as shown in the examples.

Admonishments

1.3 To avoid hazardous conditions, observe the following admonishments:

DANGER Possibility of personal injury.

CAUTION Possibility of service interruption.

WARNING Possibility of equipment damage.

Introduction 1-1


Related Documentation

1.4 For additional system information, refer to the following related documents:

• 1677 SONET Link Product Information (PN 3EM13848AD)

• 1677 SONET Link Installation Practices manual (PN 3EM13849AD)

• 1677 SONET Link Turn-Up manual (PN 3EM13850AB)

• 1677 SONET Link Maintenance and Trouble Clearing manual (PN 3EM13853AD)

• 1677 SONET Link Commands and Messages manual (PN 3EM13852AD)

• 1677 SONET Link Address and Location Guide (PN 3EM13854AB)

Document Types

1.5 The documentation contains all instructions needed to perform a task. This manual consists of the following types of documents:

• Task Index List (IXL)

• Nontrouble Procedure (NTP)

• Detailed Level Procedure (DLP)

Task Index List (IXL)

1.6 IXLs group procedures by function. Each IXL lists procedures alphabetically by name and refers the user to the appropriate procedure number.

Nontrouble Procedure (NTP)

1.7 NTPs list the major steps required to complete a task. This list may be all an experienced user requires. For an inexperienced user, each step refers to a DLP. The steps must be performed in the order listed.

Introduction1-2


Detailed Level Procedure (DLP)

1.8 DLPs contain detailed steps and supporting information required to complete a task. When a DLP is referenced from another part of the manual, perform the DLP, then return to the point where the DLP was referenced.

Introduction 1-3


Introduction1-4


2. 1677 SONET Link Element Management Application (EMA)

Introduction

2.1 The Alcatel Management Console (AMC) is part of the Element Management Application (EMA), which serves as the direct interface between the 1353 NM and the individual NEs of the network.

2.2 Refer to DLP-210 in this manual to perform the following:

• Install 1353 NM Craft software

• Install 1677 SONET Link Element Management Application (EMA) software

• Configure EMA for NE

• Install the I/O manual for TL1DAT

2.3 For help with the 1353 NM CT, refer to the 1353 NM CT Guide (PN 3EM16057AA).

Alcatel Management Console

2.4 The components of the AMC window follow (see figure 2-1):

• Caption Bar—shows the name of the NE for which the console has been launched

• Menu Bar—provides control options for the NE

• Tool Bar—provides go to Root, Go Backward, and Go Forward buttons

• Scope Pane—displays the Navigation Tree and node configurations

• Result Pane—displays the contents of the node selected in the Scope Pane in either details view or graphics view. In details view, data can be sorted by clicking on the desired column heading.

• Busy Indicator—shows the operational state of the NE. An orange triangle in the lower left corner of the window displays one of two operational states. A spinning orange triangle indicates that one or more actions are pending. A stationary orange triangle indicates that there are no pending actions.

Introduction 1-5


Context Menu

2.5 Right-clicking on an entity displays a context menu of available actions for the selected entity. If multiple entities are selected, only the actions valid for all selected entities are shown. Actions not available due to the state of the selected entity are shown in gray. Actions unavailable to a user due to security access privileges are not shown. See figure 2-2.

Figure 2-1. Alcatel Management Console

Introduction1-6


Property Windows

2.6 Entity properties are displayed and edited in property windows. Property windows typically use mutable tables, which contain editable or non-editable text fields, spinners, or combo boxes. The first cell of a mutable table typically contains the AID of the entity and its alarm status. A red triangle at the top, left corner of a cell indicates that a change has been made. The value of a cell can been changed back to its previous value by right-clicking on the cell and selecting Restore. If the value of the cell is changed back to its original value, the red triangle is removed. All red triangles in a table are removed when the Apply button at the bottom of the property window is clicked. A red plus sign at the top, right corner of a cell indicates that a conflict exists. The red plus sign is removed when the conflict is resolved. See figure 2-3.

Figure 2-2. Context Menu

Introduction 1-7


Wizards

2.7 A wizard is an interactive tool that simplifies certain command tasks that require a series of operations. See figure 2-4. Each wizard consists of the following pages:

1. Welcome page—describes the purpose of the wizard

2. Intermediate pages—enable selection of various options and parameter values. A selection made on an intermediate page determines the options available on the next page.

3. Summary page—displays changes made using the wizard for verification before the changes are submitted to the NE. The summary page has a Finish button instead of a Next Button.

2.8 Typically, Back, Next, Cancel, and Help buttons are available at the bottom of a wizard page. When the Go to Finish button appears, the remaining intermediate pages can be skipped if default values are desired for remaining optional parameters. The summary page has a Finish button instead of a Next

Figure 2-3. Property Window with Mutable Table

Introduction1-8


button. The Back and Next buttons are used to navigate through the pages. The Cancel button closes the wizard before the task is complete. The Go to Finish button goes to the summary page, and the Finish button executes the task. The Help button opens the I/O manual to the associated TL1 command.

2.9 If an error occurs and the wizard is relaunched, it opens with the values that were previously entered. This data is available only for the relaunched session. Data is not saved and is not available if a user logs out, then logs back into the NE.

Options Dialog

2.10 An options dialog provides task options to the user in the form of check boxes. The user can select an option and start the task. The options dialog also provides information about the task to be performed. See figure 2-5.

Figure 2-4. Create New User Wizard

Introduction 1-9


Message Box

2.11 Message boxes are used to provide information, obtain a user response, explain an error, or confirm a potentially dangerous choice. There are three types of message boxes: informational, warning, and critical. See figure 2-7.

2.12 An informational message box provides information about results of a command. The OK button at the bottom of the box is used to acknowledge the message.

If the NE becomes misaligned with the 1353 NM EMS (loss of communication with the NE either by loss of connectivity, stopping supervision, etc.), two informational message boxes appear (see figure 2-6) and the AMC window shuts down. If the state is misaligned, new NE information (alarms, equipment provisioned, facilities provisioned, etc.) is not transferred to the 1353 NM EMS. The server will try to connect with the NE and when it does, it re-discovers all NE information so that the AMC window is current (aligned) with the NE. The AMC window can then be launched again.

Figure 2-5. Allow Event All Options Dialog

Introduction1-10


2.13 A warning message box, which is also referred to as a confirmation message box, provides information about a condition that requires input. The option to back out of the action is provided.

Error Dialog Box

2.14 An error dialog box displays when a command fails. The error message consists of a description of the error and the reason for failure. Clicking the Details button shows the entire error response from the NE. If multiple errors occur, each error displays an individual error dialog box. See figure 2-8.

Figure 2-6. Misaligned State Informational Message Boxes

Figure 2-7. Warning Message Box

Introduction 1-11


Icons

2.15 Icons appear throughout the AMC window. Alarm status icons appear in the Scope and Result Panes to the left of the domain or entity (facility or equipment). Refer to table 2-A for descriptions of common icons.

Figure 2-8. Error Dialog Box

Introduction1-12


Table 2-A. IconsICON DESCRIPTION

Alarms Cleared

Critical Alarm

Major Alarm

Minor Alarm

Alarm Severity is Not Alarmed (NA).

Alarm Severity is Not Reported (NR).

Alarm Severity is Default value.

Misaligned. Appears to the left of NE node (in Scope Pane and Result Pane) if state becomes misaligned. Refer to section 2.12 for more information.

Entity is In Service (IS).

NE is Aligning up. Appears in Result Pane of Console Node (under MIB Alignment State) if NE is aligning up.

Entity is Out of Service (OOS).

Introduction 1-13


Node Navigation

2.16 The following first-, second-, and third-level nodes are available for the 1677 SONET Link EMA:

• Console—first-level node

• NE—second-level node

• Getting Started—third-level node

• Equipment—third-level node

• Facilities—third-level node

• Protection—third-level node

• CrossConnection—third-level node

• System—third-level node

Node Functions

1353 NM EMS Security

2.17 Access to EMA functions is restricted depending upon user privileges. If all commands and functions on a menu are not available to a user, the menu is completely removed for that user. If the user has access to some, but not all, of the commands and functions on a menu, the menu is still available, but the restricted commands and functions are removed from the menu.

Open

2.18 The Open menu option is available for nodes displayed in details view in the Result Pane. The Open menu option displays the selected node’s children. In the Scope Pane, clicking the key symbol to the left of the node displays the node’s children.

Open in New Window

2.19 The Open in New Window menu option is available in both the Scope Pane and the Result Pane. The Open in New Window menu option opens a new AMC window with the selected node in the Scope Pane and its children in the Result Pane.

Introduction1-14


Refresh

2.20 The Refresh menu option is used to verify that the data viewed by the operator for a selected node is the same as the data on the NE. Selecting Refresh does two things:

1. All attributes for the selected node are re-retrieved from the NE.

2. The children of the selected node are re-retrieved. Children no longer available on the NE are removed, and any new children are added. The attributes of the children may not be re-retrieved.

2.21 The Refresh menu option is not available for the Console node.

View Current Conditions

2.22 The View Current Conditions menu option is available for NE, Equipment, Facility, and Systems nodes if reporting of conditions is available for the node. A Conditions window displays when the View Current Conditions menu option is selected. The Conditions window contains a mutable table that shows the various conditions retrieved from the NE for the selected node. Close and Help buttons are available at the bottom of the Conditions window.

Console Node

2.23 The Console node is the root node. NE nodes are children of this node.

NE Node

2.24 The name of the NE node is the name of the NE. Getting Started, Equipment, Facilities, Protection, CrossConnection, and System nodes are children of an NE node. Clicking on the NE node in the Scope Pane displays its children and a brief description of each in detail mode in the Result Pane.

Introduction 1-15


2.25 The context menu for the NE node includes the following menu options:

• Perform Alarm Cutoff

• View Current Conditions

• File Transfer

• Event Control>Allow All

• Event Control>Inhibit All

• File Operations>Check Disk

• File Operations>Copy File

• File Operations>Delete File

• File Operations>Make Directory

• File Operations>Move File

• File Operations>View File Information

• IP Routes>Create

• IP Routes>Manage

• System Configuration Operations>Activate

• System Configuration Operations>Backup

• System Configuration Operations>Purge

• System Configuration Operations>Revert

• System Image Operations>Activate

• System Image Operations>Backup

• System Image Operations>Purge

• System Image Operations>Revert

• Synchronization>Manage BITS

• Synchronization>Operate Synchronization

• Synchronization>Set Timing Values

Introduction1-16


• Synchronization>View Timing Status

• Initialize NE

• Open in New Window

• Properties>General

• Properties>Date and Time

Perform Alarm Cutoff

2.26 The Perform Alarm Cutoff menu option launches a confirmation dialog box. The dialog box provides the options to complete the task or to back out of the action. Click Yes to cut off the office audible alarm indications without changing the local alarm indications.


2.27 This shows the current standing Conditions of the NE in a Mutable Table as the following:

File Transfer

2.28 The File Transfer menu option launches a dialog box. This dialog will allow the user to backup the NE database to a Remote File Server, Download a database from a Remote File Server, or download a software generic from a Remote File Server. Before launching this command, the destination machine must have an FTP server configured.

Columns TL1 ParametersName AIDAID Type ENTITYTYPENotification Code NTFCNCDECondition Type CONDTYPEService Effect SRVEFFDate Occurred OCRDATTime Occurred OCRTMDescription CONDDESCR

Introduction 1-17


Event Control>Allow All

2.29 The Event Control>Allow All menu option launches an option dialog to allow user to resume trasmitting all autonomous messages for the selected Notification Codes. The dialog box provides the options to complete the task or to back out of the action.

Event Control>Inhibit All

2.30 The Event Control>Inhibit All menu option launches an option dialog to allow user to inhibit all autonomous messages for the selected Notification Codes. The dialog box provides the options to complete the task or to back out of the action.

File Operations>Check Disk

2.31 The File Operations>Check Disk menu option launches a wizard that will step the operator through the valid parameter entry screens. This command will verify the integrity of the specified disk or the data on it.

File Operations>Copy File

2.32 The File Operations>Copy File menu option launches a wizard that will step the operator through the valid parameter entry screens. This command will copy a file to a different name or to a different disk.

File Operations>Delete File

2.33 The File Operations>Delete File menu option launches a wizard that will step the operator through the valid parameter entry screens. This command will remove a file or directory. If a directory is specified, all the files in that directory will also be deleted.

File Operations>Make Directory

2.34 The File Operations>Make Directory menu option launches a wizard that will step the operator through the valid parameter entry screens. This command will create a user directory on DISK-A or DISK-B.

File Operations>Move File

2.35 The File Operations>Move File menu option launches a wizard that will step the operator through the valid parameter entry screens. This command will move a file from one location to another.

Introduction1-18


File Operations>View File Information

2.36 The File Operations>View File Information menu option launches a wizard that will step the operator through the valid parameter entry screens. This command will display file information in a mutable table.

IP Routes>Create

2.37 The IP Routes>Create menu option launches a wizard that will step the operator through the valid parameter entry screens. This command will create a static IP route.

IP Routes>Manage

2.38 The IP Routes>Manage menu option launches a mutable table allowing the operator to view or delete entries from the IP Routing table.

System Configuration Operations>Activate

2.39 The System Configuration Operations>Activate menu option launches a wizard that will step the operator through the valid parameter entry screens. This command activates a new system configuration.

System Configuration Operations>Backup

2.40 The System Configuration Operations>Backup menu option launches a wizard that will step the operator through the valid parameter entry screens. This command will backup the system configuration.

System Configuration Operations>Purge

2.41 The System Configuration Operations>Purge menu option launches a wizard that will step the operator through the valid parameter entry screens. This command will delete unneeded system configuration files.

System Configuration Operations>Revert

2.42 The System Configuration Operations>Revert menu option launches a confirmation dialog box. This command will reload the configuration files saved in /LAST and then activate them.

Introduction 1-19


System Image Operations>Activate

2.43 The System Image Operations>Activate menu option launches a wizard that will step the operator through the valid parameter entry screens. This command will activate a new system image.

System Image Operations>Backup

2.44 The System Image Operations>Backup menu option launches a wizard that will step the operator through the valid parameter entry screens. This command will backup image files.

System Image Operations>Purge

2.45 The System Image Operations>Purge command launches a wizard that will step the operator through the valid parameter entry screens. This command will delete unneeded system image files.

System Image Operations>Revert

2.46 The System Image Operations>Revert menu option launches a confirmation dialog box. This command will reload the image files saved in /LAST and then activate them.

Synchronization>Manage BITS

2.47 The Synchronization>BITS menu option launches a mutable table that allows BITS values to be viewed or changed.

Synchronization>Operate Synchronization

2.48 The Synchronization>Operate Synchronization menu option launches an option dialog box. The dialog box allows the user to select the Primary, Secondary, or Internal reference.

Synchronization>Set Timing Values

2.49 The Synchronization>Set Timing Values menu option launches a mutable table. The table allows the user to modify the provisioning of the clock reference priorities.

Introduction1-20


Synchronization>View Timing Status

2.50 The Synchronization>View Timing Status menu option launches a mutable table. The table allows the user to view information on equipment providing NE synchronization.

Initialize NE

2.51 The Initialize NE menu option launches a confirmation dialog box. The dialog box provides the options to complete the task or to back out of the action.

Properties>General

2.52 The Properties>General menu option launches a mutable table that displays general system level configuration information such as system type, software release number and date, matrix size, and restart status.

Properties>Date and Time

2.53 The Properties>Date and Time menu option launches the Set NE Date and Time property sheet, which can be used to set the NE’s date and time. See figure 2-9.

Introduction 1-21


Getting Started Node

2.54 Clicking the Getting Started node displays the Getting Started page in the Result pane. The Getting Started page provides basic information about the application, about its organization, and how to begin using it. The following navigation icons are provided at the top of the Results Pane:

• Go back

• Reload

• Go home

• Search

• Print

• Help

Figure 2-9. Set NE Date and Time Window

Introduction1-22


Equipment Node

2.55 The Equipment node supports the details view and the graphics view. When the Equipment node is selected, the modules in the shelf display in the Result Pane. The details view provides the following for the modules in the shelf (see figure 2-10):

• Access Identifiers (AID)

• Assigned Type

• Equipped Type

• Primary State

• Secondary State

Figure 2-10. Details View of Equipment Node

Introduction 1-23


2.56 The graphical view shows a picture of the shelf and the modules/slots within the shelf. The individual shelf graphics do not depict the actual shelf. See figure 2-11.

2.57 The context menu for the Equipment node includes the following menu options:


• View DS3 Panels

• Open

• Open in new window

• Refresh

Figure 2-11. Graphical View of Equipment Node

Introduction1-24



2.58 The View Current Conditions menu option launches a mutable table displaying the current conditions of a selected equipment type.

View DS3 Panels

2.59 The View DS3 Panels menu option launches a mutable table that displays DS3 panel information. Information shown includes Primary State, Secondary State, Part Number, Serial Number, and hardware version.

Board Nodes

2.60 To view context menus for each board, right click on the appropriate board. The options shown in the context menus vary depending on the board and its availability.

2.61 The context menus for CCC boards include the following menu options:

• Initialize Board

• Reprogram


• Event Control>Allow

• Event Control>Inhibit

• Service State>Remove

• Service State>Restore

• Switch>Switch Duplex

• Refresh


• Properties>Remote Inventory

Introduction 1-25


2.62 The context menus for DISKs include the following menu options:

• Activate Disk

• Deactivate Disk

• Mount Disk

• UnMount Disk

• Format Disk




• Refresh


2.63 The context menus for IOC boards (OC-n) include the following menu options:

• Assign

• Unassign



• Go to Supported Facility





• Refresh



Introduction1-26


2.64 The context menus for DS3 boards include the following menu options:

• Assign

• Unassign



• Go to Supported Facility





• Switch>Switch to Protection

• Switch>Switch to Working

• Switch>Allow Switch to Protection

• Switch>Inhibit Switch to Protection

• Switch>Allow Switch to Working

• Switch>Inhibit Switch to Working

• Refresh



Introduction 1-27


2.65 The context menus for ECC boards include the following menu options:

• Assign

• Unassign



• Go to Supported Facility>T3 Facility

• Go to Supported Facility>EC1 Facility











• Refresh



Introduction1-28


2.66 The context menus for TMUX and VSC boards include the following menu options:

• Assign

• Unassign


• Reprogram (TMUX only)

• Retrieve Resource Usage












• Refresh



2.67 The context menus for PWR and PWR-FAN boards include the following menu options:


• Refresh


Introduction 1-29


2.68 The context menus for SWC and DCC boards include the following menu options:


• Reprogram




• Service State>Remove (SWC only)

• Service State>Restore (SWC only)

• Switch>Switch Duplex (SWC only)

• Refresh



2.69 The context menus for TC boards include the following menu options:






• Switch>Switch Duplex

• Refresh



Introduction1-30


Facilities Node

2.70 The Facilities node is the root node and contains all Facility Type nodes. When this folder is selected, all Facility Type nodes display in the Results Pane. Only the details view is available for the Facilities node and its children. An example of the Facilities node hierarchy using OC-48s follows:

1. Facilities node

2. Facility Type node—OC48

3. Facility Group node—OC48-14-A

4. Facility Instance node—OC48-14-A-1

2.71 The context menu for the Facilities node includes the following menu option:

• Open


Facility Type Node

2.72 Facility Type nodes contain all payload-carrying facilities of one type for an NE. The payload consists of facility instances. The facility type nodes for the 1677 SONET Link are T3, OC3, OC12, OC48, OC192, GIGE, OFA, and EC1.

2.73 Clicking the Facility Type node displays Facility Group nodes in the Results Pane. See figure 2-12.

Introduction 1-31


2.74 The context menu for a Facility Type node includes the following menu options:


• Open


Facility Group Node

2.75 Facility group nodes show the facility groups for each of the I/O boards provisioned for that facility type.

2.76 The context menu for the facility group nodes includes the following menu options:

• Open


• Refresh

Figure 2-12. Facility Type Node with Facility Groups in Results Pane

Introduction1-32


Facility Instance Node

2.77 A facility instance node is the individual provisioned facility of a specific type. It is located under the facility group node. For example, OC3-2-B-1 is a facility instance under the facility group OC3-2-B.

Introduction 1-33


2.78 The context menus for GIGE Facility instance nodes include the following menu options:

• Assign

• Unassign


• Go To>Supporting Board





• Performance Monitoring>Allow Reporting

• Performance Monitoring>Inhibit Reporting

• Performance Monitoring>Initialize 15-Minute Registers

• Performance Monitoring>Initialize 1-Day Registers

• Performance Monitoring>15-Minute Thresholds

• Performance Monitoring>1-Day Thresholds

• Performance Monitoring>PM Mode

• Performance Monitoring>Schedule

• Performance Monitoring>View 15-Minute Data

• Performance Monitoring>View 1-Day Data

• Open


• Refresh


• Properties>Alarm Severity

Introduction1-34


2.79 The context menus for EVC Facility instance nodes include the following menu options:

• Assign

• Unassign


• Go To>Create Cross Connection

• Go To>Cross Connected Facility

• Refresh


Introduction 1-35


2.80 The context menus for T3 (DS3) Facility instance nodes include the following menu options:

• Unassign



• Go To>Create Cross Connect




• Loopback>Operate

• Loopback>Release

• Loopback>View













• Open


Introduction1-36


• Refresh



Introduction 1-37


2.81 The context menus for EC1 Facility instance nodes include the following menu options:

• Unassign







• Loopback>View













• Open


• Refresh


Introduction1-38



2.82 The context menus for OFA Facility instance nodes include the following menu options:

• Unassign

















• Refresh



Introduction 1-39


2.83 The context menus for OC3, OC12, OC48, OC192 Facility instance nodes include the following menu options:

• Assign

• Unassign



• Go To>Supporting Protection Group

• Go To>Associated Facility





• Loopback>View



• View DCC Parameters>IPC Line

• View DCC Parameters>IPC Section

• View DCC Parameters>LPC Line

• View DCC Parameters>LPC Section

• View DCC Parameters>Lower Layers Line

• View DCC Parameters>Lower Layers Section

• View DCC Parameters>Upper Layers Line

• View DCC Parameters>Upper Layers Section

• Network Interface>Create

• Network Interface>Manage


Introduction1-40











• Open


• Refresh



Network Interface>Create

2.84 The Network Interface>Create menu option launches a wizard that guides the operator through the valid parameter entry screens. This wizard is used to create a network interface using the DCC channel on an optical port.

Network Interface>Manage

2.85 The Network Interface>View menu option launches a mutable table. This table is used to view and delete network interfaces using the DCC channel on an optical port.

Introduction 1-41


2.86 The context menus for payloadable STS1 Facility instance nodes include the following menu options:

• Assign

• Unassign





• Go To>Create Cross Connection
















• Open

• Open in New WIndow

Introduction1-42


• Refresh



Introduction 1-43


2.87 The context menus for non-payloadable STS1, STS3C, STS12C, and STS48C Facility instance nodes include the following menu options:

• Unassign





















• Refresh



Introduction1-44


2.88 The context menus for STS1-T3 Facility instance nodes include the following menu options:

• Assign

• Unassign







• Loopback>View













• Open

• Open in New Wndow

• Refresh

Introduction 1-45




Introduction1-46


2.89 The context menus for VT1, and T1 Facility instance nodes include the following menu options:

• Assign

• Unassign



• Go To>Associated Facility (OC-3 only)







• Loopback>View













Introduction 1-47


• Open (VT1 only)

• Open in new window (VT1 only)

• Refresh



Protection Node

2.90 The Protection Node is the root node and contains all other protection nodes underneath this node. It is used to create protection pairs and to operate/release a protection switch.

2.91 The context menu for the Protection node includes the following menu options:

• Open


• Refresh

2.92 When the Protection node folder is selected, the protection facility type nodes display in the Results Pane. The protection facility type nodes are the facility types that are currently provisioned and are valid for protection pairs: OC3, OC12, OC48, and OC192. Only the details view is available for the Protection node and its children.

Protection Facility Type Node

2.93 The context menu for the Protection Facility Type node includes the following menu options:

• Open


• Refresh

2.94 When a Protection Facility Type folder is selected, the facility protection ranges are displayed in the Results Pane.

Introduction1-48


Facility Protection Range Node

2.95 The context menu for the Facility Protection Range node includes the following menu options:

• Create Protection Pair

• Open


• Refresh

2.96 When a Facility Protection Range folder is selected, current protection pairs are displayed in the Results Pane.

Create Protection Pair

2.97 The Create Protection Pair menu option launches a wizard that guides the operator through the valid parameter entry screens.

Protection Pair Node

2.98 The context menu for protection pairs varies depending on the type of protection scheme (Linear, UPSR, or BLSR).

2.99 The context menu for a Linear Protection Pair Node (for OC3/OC12/OC48/OC192) includes the following menu options:

• Delete

• Operate Switch

• Release Switch

• Go To>East Facility (Protecting Facility)

• Go To>West Facility (Working Facility)

• View Protection Trace

• Refresh


Introduction 1-49


2.100 The context menu for a UPSR Protection Pair Node (for OC3/OC12/OC48/OC192) includes the following menu options:

• Delete



• Open


• Refresh


2.101 Selecting a UPSR protection group will display UPSR Protection instances in the Results Pane. The East and West facilities are displayed along with the protection type, status, and preferred facility. The context menu for UPSR protection instances includes the following menu options:

• Operate Switch

• Release Switch



• Refresh


Introduction1-50


2.102 The context menu for a BLSR Protection Pair Node (for OC48/OC192) includes the following menu options:


• Delete

• Operate Switch

• Release Switch

• Go To>East (Protecting Facility)

• Go To>West (Working Facility)

• RINGMAP

• SQLMAP/BLSR Channel Data

• Refresh


• Properties>BLSR Trace

CrossConnection Node

2.103 The CrossConnection node is the root node and is used to cross-connect traffic-bearing facilities with one another.

2.104 For the CrossConnection node, the result pane is not used for display purposes, but instead shows a graphic. There is no details view.

2.105 Right clicking the CrossConnection node and selecting a menu option launches secondary windows to view/manage and create cross-connections.

2.106 The context menu for the CrossConnection node includes the following menu options:

• Create CrossConnections

• Manage CrossConnections

• Open

• Open in New Window

Introduction 1-51


Create CrossConnections

2.107 Cross-connections are created through a dialog box. See figure 2-13.

2.108 The Mode Selector provides radio buttons for selecting either Filter mode or Text mode. These modes of operation can be toggled.

2.109 A Mutable Table is below the Mode Selector. Each row has 17 columns, one for each input parameter depending on facility type.

Figure 2-13. Create CrossConnection Dialog Box

Introduction1-52


2.110 The buttons at the bottom of the table follow:

• Import - imports a file of cross-connections to be created. Available only in Text Mode.

• Add - creates a new row

• Remove - deletes the selected row(s)

• Apply - sends the TL1 command to the NE to create the cross-connection specified. Enabled only if there are no partially entered rows.

• Close - closes the mutable table

• Help - opens a help page with the option of opening the I/O manual to the ENT-CRS-x TL1 commands (where x is the appropriate facility type: GIGE, STS1, STS12C, STS3C, STS48C, T1, T3, or VT1).

2.111 The CrossConnection Type cell is a combo box that contains all cross-connection types available for the specified facility type. Valid CrossConnection Type values follow:

• 2WAY (Two Way)

• 2WAYDC (Two Way Drop and Continue)

• SRIW (Secondary Ring Interconnected on Working)

• 1WAYDC (One Way Drop and Continue)

• THRU (Ring pass-through connection)

2.112 The value of a cell can been changed back to its previous value by right-clicking on the cell and selecting Restore.

2.113 In Text Mode, the source and destination facility AIDs can be entered. Only the AID format is checked for cross-connection compatibility. Compatibility checks are not performed on any other parameters. The NE assumes that all the information necessary to perform data entry is available.

2.114 When the cell loses focus after entering the source or destination facility, data validation is performed, and an error is displayed in an informational message box.

Introduction 1-53


2.115 Import from File is enabled when Text Mode is active. When the Import button is clicked, a file selection dialog is provided. The file to be imported must be in the following format:

• Each cross-connection must be on a separate line

• Each line must be composed of 17 fields, separated by commas. (Some fields may be empty depending on protection scheme; separating commas must still be included.)

2.116 The imported file is checked for correct input format.

2.117 Values for the different fields can be edited. Double clicking enables the cell editor. Rows can be added by clicking Add.

2.118 In Filter Mode, to display the Facility Browser, click the Add button then click in an empty cell of either the Facility Source or Facility Destination column. See figure 2-14 for the Facility Browser dialog box.

Figure 2-14. Facility Browser Dialog Box

Introduction1-54


2.119 In the Create CrossConnections dialog box, values in the cells can be selected in any order. All cells are enabled at all times, and values can be changed in any order. Once a facility is selected in the Facility Browser window, the OK button is enabled. When the OK button is clicked, the Facility Browser is closed, and the facility is entered in the CrossConnection dialog box. Only one facility can be entered at a time using the Facility browser.

Manage CrossConnections

2.120 Cross-connections are managed through a dialog box. See figure 2-15. There are two selection buttons at the top of the screen: Facilities and Retrieve. There are also two combo boxes: Facility Type and CrossConnection type.

Figure 2-15. Manage CrossConnections Dialog Box

Introduction 1-55


2.121 Clicking the Facilities button opens the Facility Browser dialog box. In the Facility Browser, multiple facilities can be selected at a time. Once a valid facility is selected, the OK button is enabled. The OK button is disabled when a Facilities node or Facility Type node is selected. When the OK button is clicked, the Facility Browser is closed, and the facility is entered in the CrossConnection dialog box.

2.122 The Facility Type pull down menu allows retrieval of existing cross-connects based on facility: STS1, STS3c, STS12c, STS48c, EVC, T1, VT1.5, T3, or ALL.

2.123 The CrossConnection type pull down menu allows retrieval of existing cross-connects based on connection type: 2WAY, 1WAYDC, 2WAYDC, SRIW, THRU, or ALL.

2.124 A mutable table is below the buttons. Clicking Retrieve displays the selected facilities’ cross-connections in the table.

2.125 Available buttons at the bottom of the Manage CrossConnection dialog box follow:

• Delete - removes the selected cross-connection

• Modify - edits the cross-connection. (Button is enabled after a change is made in a parameter cell of a cross-connection.)

• Close - closes the table

• Help - opens a help page with the option of opening the I/O manual to the following commands:

– DLT-CRS-x (where x is the facility type)

– ED-CRS-x

System Node

2.126 The System node supports only the details view. When the System node folder is selected the NE Security node displays in the Result Pane, along with the CHASSIS, DCC/DCN, DISK-A, DISK-B, FANTRAY, MOS, NE Security, and TC-SYNC instances.

2.127 The context menu for the System node is the same as that of the NE node.

Introduction1-56


CHASSIS, FANTRAY, and TC-SYNC Instances

2.128 The context menu for the CHASSIS, FANTRAY, MOS, and TC-SYNC instances includes the following menu options:


DCC/DCN Instance

2.129 The context menu for the DCC/DCN instance includes the following menu options:

• View Address Resolution Protocol>ARP Cache Parameters

• View Address Resolution Protocol>TARP Parameters

• View Address Resolution Protocol>TARP Cache

• View Address Resolution Protocol>TARP Loop Detection

• View DCC Parameters>Upper Layer Common

• View Manual Address

• View Network Service Access Point

DISK-A and DISK-B Instances

2.130 The context menu for the DISK-A and DISK-B instances includes the following options:



NE Security Node

2.131 The NE Security node supports only the details view. When the NE Security node folder is selected, the TL1 Commands node, Users node, and Security Log instance display in the Result Pane.

2.132 All objects in the NE Security domain do not emit DBCHG or REPT^EVT messages when their state changes due to other user actions for NE security reasons and cannot be updated autonomously. A refresh must be used to verify current status.

Introduction 1-57


2.133 The context menu for the NE Security node includes the following menu options:



• Properties>Warning Message

TL1 Commands Node

2.134 The TL1 Commands node supports only the details view. When the TL1 Commands node folder is selected, the commands’ output from the RTRV-PRVG-CMD TL1 command displays in the Result Pane.

2.135 The context menu for the TL1 Command node includes the following menu options:


• Refresh

TL1 Command Instances

2.136 TL1 command instances are the leaf nodes under the TL1 Command node. All TL1 commands are listed in the Result Pane along with their Command Access Privilege (CAP).

2.137 The context menu for TL1 Command instances includes the following menu options:

• Refresh


Users Node

2.138 The Users node supports only the details view. When the Users node folder is selected, user instances and the access and security privileges, state, and login status of each user display in the Result Pane.

Introduction1-58


2.139 The context menu for the Users node includes the following menu options:

• Create User

• Open in new Window

• Refresh


2.140 The Create User menu option launches a wizard. The wizard provides entry screens for the completion of this task.

User Instances

2.141 User instances represent user accounts created on the NE. Once a user is created, a context menu is available. The context menu for the user instances includes the following menu options:

• Activate

• Deactivate

• Logoff

• Delete

• Change Password

• Refresh


Security Log Instance

2.142 The context menu for the Security Log instance includes the following menu options:

• Allow

• Inhibit


Introduction 1-59


Introduction1-60


3. TL1DAT Only Commands

3.1 Refer to table 3-A for commands available only through the TL1 Direct Access Terminal (TL1DAT) application or Direct Mode at a terminal. Equivalent functions for these commands are not available through the 1677 SONET Link Element Management Application (EMA).

Table 3-A. TL1DAT Only CommandsCOMMAND CODE FUNCTIONALW-MSG-COM Allow Message CommonALW-PMREPT-ALL Allow all PM ReportsALW-PMREPT-COM Allow common PM reportsCANC-CID-SECU Cancel channel identifier securityCHG-ACCMD-STS1 Change STS1 Test Access ModeCHG-ACCMD-STS12C Change STS12C Test Access ModeCHG-ACCMD-STS3C Change STS3C Test Access ModeCHG-ACCMD-STS48C Change STS48C Test Access ModeCHG-ACCMD-T1 Change T1 Test Access ModeCHG-ACCMD-T3 Change T3 Test Access ModeCHG-ACCMD-VT1 Change VT1 Test Access ModeCONN-TACC-STS1 Connect to STS1 Test Access PortCONN-TACC-STS12C Connect to STS12C Test Access PortCONN-TACC-STS3C Connect to STS3C Test Access PortCONN-TACC-STS48C Connect to STS48C Test Access PortCONN-TACC-T1 Connect to T1 Test Access PortCONN-TACC-T3 Connect to T3 Test Access PortCONN-TACC-VT1 Connect to VT1 Test Access PortDISC-TACC Disconnect Test AccessDLT-ARPCACHE Delete Address Resolution Protocol CacheDLT-MAP Delete gateway map entryDLT-NE-DENIED Delete Network Element denied hostDLT-NE-TRUST Delete Network Element trusted hostDLT-TARPCACHE Delete Tarp CacheDLT-TARPLDB Delete Tarp Loop Detection BufferED-MAADDR Edit Manual Area AddressED-MAP Edit gateway map entryED-NE Edit Network Element

Introduction 1-61


ED-NE-SNTP Edit Network Element SNTP parametersED-NE-TL1 Edit Network Element TL1 parametersED-TARP Edit TL1 Address Resolution Protocol parametersENT-MAP Enter gateway map entryENT-NE-DENIED Enter Network Element denied hostENT-NE-TRUST Enter trusted hostFLTLOC-PATH Fault locate pathINH-MSG-COM Inhibit common messagesINH-PMREPT-COM Inhibit common PM reportsOPR-ALS-OC12 Operate OC12 in Automatic Laser ShutoffOPR-ALS-OC192 Operate OC192 in Automatic Laser ShutoffOPR-ALS-OC3 Operate OC3 in Automatic Laser ShutoffOPR-ALS-OC48 Operate OC48 in Automatic Laser ShutoffRTRV-ALM-COM Retrieve common alarmsRTRV-ALM-EC1 Retrieve EC1 alarmsRTRV-ALM-EQPT Retrieve equipment alarmsRTRV-ALM-GIGE Retrieve GIGE alarmsRTRV-ALM-OC12 Retrieve OC12 alarmsRTRV-ALM-OC192 Retrieve OC192 alarmsRTRV-ALM-OC3 Retrieve OC3 alarmsRTRV-ALM-OC48 Retrieve OC48 alarmsRTRV-ALM-OFA Retrieve OFA alarmsRTRV-ALM-STS1 Retrieve STS1 alarmsRTRV-ALM-STS12C Retrieve STS12C alarmsRTRV-ALM-STS3C Retrieve STS3C alarmsRTRV-ALM-STS48C Retrieve STS48C alarmsRTRV-ALM-T1 Retrieve T1 alarmsRTRV-ALM-T3 Retrieve T3 alarmsRTRV-ALM-VT1 Retrieve VT1 alarmsRTRV-AO Retrieve autonomous outputRTRV-ATTR-COM Retrieve common alarm attributesRTRV-ATTR-CRSDFLT Retrieve cross-connect defaultsRTRV-ATTR-LOG Retrieve log attributesRTRV-AUDIT-SECULOG Retrieve entries of the security logRTRV-COND-COM Retrieve common standing conditions

Table 3-A. TL1DAT Only Commands (cont.)COMMAND CODE FUNCTION

Introduction1-62


RTRV-CRS-ALL Retrieve all cross-connectionsRTRV-DB-LABEL Retrieve database labelRTRV-FFP-ALL Retrieve Fast Facility Protection group parametersRTRV-LOG Retrieve disk log fileRTRV-MAP Retrieve gateway mapRTRV-MOS Retrieve Modular Optical SystemRTRV-NE Retrieve Network ElementRTRV-NE-DENIED Retrieve Network Element denied hostsRTRV-NEID Retrieve Network Element identifierRTRV-NE-SNTP Retrieve Network Element SNTP parametersRTRV-NE-TL1 Retrieve Network Element TL1 parametersRTRV-NE-TRUST Retrieve trusted host tableRTRV-NETYPE Retrieve Network Element typeRTRV-OPTICAL Retrieve Optical propertiesRTRV-PM-ALL Retrieve all PM dataRTRV-PMSCHED-ALL Retrieve all PM report schedules


Introduction 1-63


RTRV-PTHTRC-STS1 Retrieve STS1 pathtraceRTRV-PTHTRC-STS12C Retrieve STS12C pathtraceRTRV-PTHTRC-STS3C Retrieve STS3C pathtraceRTRV-PTHTRC-STS48C Retrieve STS48C pathtraceRTRV-SECTRC-EC1 Retrieve EC1 section traceRTRV-SECTRC-OC12 Retrieve OC12 section traceRTRV-SECTRC-OC192 Retrieve OC192 section traceRTRV-SECTRC-OC3 Retrieve OC3 section traceRTRV-SECTRC-OC48 Retrieve OC48 section traceRTRV-TACC Retrieve Test Access connectionsRTRV-TH-ALL Retrieve all threshold settingsRTRV-USER-SESSION Retrieve current user sessionSCHED-PMREPT-ALL Schedule all PM reportsSET-ATTR-COM Set common alarm attributesSET-ATTR-CRSDFLT Set default cross-connection attributesSET-ATTR-LOG Set log attributesSET-SID Set Site IdentifierSTA-LOG Start logSTP-LOG Stop logTEST-LED Test LEDs


Introduction1-64


4. COMMAND STRUCTURE AND SYNTAX

4.1 Command syntax refers to rules that govern Transaction Language 1 (TL1) command element arrangement; that is, how elements are delimited or separated using special characters and punctuation.

4.2 For the system to understand a command entered in Direct mode, the precise command structure and syntax must be entered.

4.3 A complete TL1 command consists of the following elements:

• Command code: specifies an action the command performs and the object or nature of that action.

• Input parameters: directs a command to the appropriate processing environment or supplies the data required to execute the command. Parameters can be either required or optional depending on the command.

• Special characters and punctuation: identify command elements, separate each element, and end each command.

Command Code

4.4 The command code contains up to three elements: a verb and one or two verb modifiers. A hyphen separates each element of a command. Command codes are usually abbreviations of the meaning of the command.

An example of a command code is ENT-CRS-T3. In this example, the first element, ENT, is a verb that specifies the action Enter. Up to two modifiers can follow; these modifiers refer to data, such as a database in the system, an internal software subsystem, or a physical entity (such as an equipment or circuit type). In this case, the first modifier is CRS for cross-connection, which is the type of action. The second modifier is T3 for DS3, which is the object of the cross-connection.

4.5 ENT-CRS-T3 connects an incoming DS3 circuit to an outgoing DS3 or STS-1 circuit in the switching environment. The command code, however, does not specify which circuits to connect. Input parameters supply the additional information needed to execute the command.

Introduction 1-65


Input Parameters

4.6 Input parameters specify conditions under which a command executes. Parameters can be either required or optional. The form screen encloses optional parameters in brackets. Three examples of input parameters follow:

• The Access Identifier (AID) of a facility or equipment unit

• The state of a facility after provisioning

• The range of a command (if ranging is supported for that command)

4.7 When a command contains multiple parameters of the same type in a string, the string is a parameter block. Colons ( : ) separate parameter blocks. Within a block, commas ( , ) separate individual parameters.

Introduction1-66


4.8 The cross-connect system generally uses the following parameter types; however, the parameters in some commands do not conform to this model.

Verb-Modifier1-Modifier2:[a]:[b]:[c]:[d]:[e]:[f]:[g];

• a=TID – Target Identifier. The TID is an alphanumeric block of up to 20 characters, the first of which must be alphabetic. It identifies the processing location for a command. When a value is not entered, the system defaults to the uppercase Site Identifier (SID) value. When a value is entered, it must match the SID. If the entered value does not match the SID, the system denies the command.

• b=AID – Access Identifier. The AID identifies a facility port, removable equipment unit, or other object entity. Examples of parameters in this field are: From Location, To Location, and Control Port. Some commands have multiple AID fields (FROM,TO).

• c=CTAG – Correlation Tag. The CTAG is a 1 to 6 alphanumeric block that identifies a transaction. The CTAG correlates system output messages with the commands that caused the messages. The CTAG is optional; if a CTAG is not entered, the system automatically assigns one.

• d=General Block – The general block is not supported and must be empty.

• e=Common Block – The common block is almost always positionally defined, which means that parameters in the common block are defined by their position or sequence in the block. Brackets indicate optional parameter values. Absence of brackets indicates that the parameter value must be entered. If one or more parameter values is omitted from the end of the block, the preceding comma associated with the value may be omitted. However, if an optional parameter value is omitted with other positional parameter values following, all intervening placeholder commas must be provided to indicate that no value is being entered for that parameter. The system assumes the default or existing parameter value for omitted optional parameter values. Parameter value combinations are verified by the system whether the value is determined from a default value or explicitly entered in the command.

• f=Specific Block – Parameters in the keyword block are defined by a keyword parameter name. A value for a keyword parameter is specified by entering the parameter name followed by an equal sign (=) then the parameter value. Keyword parameters may be entered in any order within the keyword block, but keyword parameters must be separated by a comma. Only commas separating each keyword

Introduction 1-67


parameter are required in the keyword parameter block, but the keyword block may not begin or end with a comma. Brackets indicate optional parameters and their associated comma separators. Absence of brackets indicates that the parameter and any comma separator must be entered.

• g=State Block – The state parameter block is a positional block with parameters defined by their position or sequence in the block. The state block defines parameters that relate to the primary and/or secondary state of equipment. The state block is supported only by commands that include the state block in the input format of a command. When supported, up to two parameters are possible for the state block, the PST (primary state) parameter and the SST (secondary state) parameter. Brackets indicate optional parameter values. Absence of brackets indicates that the parameter value must be entered. If the SST parameter value is omitted from the end of the block, the trailing comma associated with it may be omitted. However, if an optional PST parameter value is omitted with an SST positional parameter value following, the intervening placeholder comma must be provided to indicate that no value is being entered for the PST parameter. The system assumes the default parameter value for omitted optional parameter values.

4.9 Keyword parameters require a parameter name assignment with each parameter value. Enter keyword parameters in any order within a block. Positional parameters must occur in the order specified by the TL1 command.

Special Characters

4.10 TL1 uses characters that have special meanings depending on where the characters appear or how they are used. Refer to table 4-A for the characters used with commands, parameters, and output messages.

Introduction1-68


4.11 When using the equal sign with positional parameters, the parameter must be entered in the correct position. If this is not done, the system rejects the command.

4.12 Brackets [ ] indicate an optional parameter. Brackets are used in system documentation to indicate optional parameters. Brackets are not entered as part of a TL1 command.

Table 4-A. TL1 Special CharactersSPECIALCHARACTER DESCRIPTION< > In syntax statements, enclosing less-than and greater-than signs indicate a value

substitution. The enclosing less-than and greater-than signs are not part of the actual input command. Generally, this notation is used only to provide additional clarity in the syntax descriptions for an input command.

{ } In syntax statements, paired braces enclose a set of values. Generally, enclosing braces are used in the notation for the non-parsable command echo line and in describing an output parameter's value set. The enclosing braces are not part of the actual input command or output message.

[ ] In syntax statements, paired brackets enclose an optional command argument; for example: [TID]. These enclosing brackets are not part of the actual input command or output message.

The following characters are entered in TL1 commands.- Hyphen. Separates elements of TL1 command codes. Also combines elements of a

compound parameter., Comma. Separates parameter values when multiple values exist.: Colon. Separates the command code segment from the parameters. Also separates

succeeding parameter blocks.; Semicolon. Terminates a command entry and starts execution.= Equal sign. Associates a parameter name with the assigned parameter. A parameter

must be entered in uppercase exactly as specified. A value of the parameter follows the equal sign.

& Ampersand. Groups parameter values in an input command (as list of parameter values is generated), and combines parameter values in an output message.

&& Double ampersand. Represents numeric ranging in the last argument value of a parameter (simple or compound) in an input command. It generates a sequential range of parameter values, beginning with the first term specified through the last term specified.

Introduction 1-69


Ranging and Grouping

4.13 The AID parameter of specific commands lets ranging and grouping generate a range of AID values, a list of AID values, or a combination of both. The string &&- (double ampersand and hyphen) specifies a range of AID values (&&-ranging), while &- (single ampersand and hyphen) specifies a list of AID values (&-grouping).

4.14 The &&-ranging supports numeric ranging on multiple arguments of a compound AID parameter (the information units in the AID). The range must fully define the first AID value (for example, STS1-4-A-2-1), while the range argument must end with the numeric argument of the last AID value in the range (with the preceding hyphen after the ampersands; for example, &&-3, &&-10, and so on). The expanded range of AIDs always includes the first and last AID values of the sequential series specified by the range. AID formats cannot be combined for different entity types (that is, a DS3 AID format and an OC-12 AID format) when specifying &&-ranging.

An example of STS-1 &&-ranging is: STS1-2-A-2-1&&-3. This is understood by the system as STS1-2-A-2-1, STS1-2-A-2-2, and STS1-2-A-2-3.

4.15 Ranged sequences increment by N, and the system default is N=1. To change the value of N, enter .++.N after the range. For example, STS1-6-AB-1-2&&-6.++.2 is understood by the system as STS1-6-AB-1-2, STS1-6-AB-1-4, and STS1-6-AB-1-6. The range ends at the highest value less than or equal to the end value; STS1-6-AB-1-2&&-7.++.2 is also understood as STS1-6-AB-1-2, STS1-6-AB-1-4, and STS1-6-AB-1-6.

4.16 When using &-grouping, a hyphen may be used after the ampersand. An example of DS3 &-grouping is: T3-2-A-1&-2&-3. This is understood by the system as T3-2-A-1, T3-2-A-2, and T3-2-A-3.

4.17 Ranging/Grouping capability is permitted on the last segment of an AID when that segment is numeric. Specific AID types have additional rules.

Introduction1-70


5. MODES

TL1DAT Modes

5.1 There are two modes of command entry in the TL1 Direct Access Terminal (TL1DAT) application:

• Enhanced

• Basic

5.2 To switch between Enhanced and Basic modes, select Preferences>Mode>Enhanced or Preferences>Mode>Basic from the main menu.

5.3 Basic mode is the only mode available if the user is connected to an NE that hasn’t been installed yet (assigned an I/O manual), or an NE that has to I/O manual installed in the correct HTML format.

Enhanced Mode

5.4 Enhanced Mode lets the user execute a command by selecting a command from the Command Tree Panel of the TL1DAT window. After selecting a command, the Command Parameter Panel displays the command and required and optional parameter fields. See figure 5-1.

5.5 Using Enhanced Mode, remembering a specific command code, parameters for each command, or special TL1 syntax characters is not necessary. Based on user-provided information in the Command Parameter Panel, the system automatically executes commands using the proper syntax.

5.6 The Command Parameter Panel displays the selected command code at the top center. Fields below the command code show command input parameters. The parameter field names appear in plain text and are not necessarily the exact TL1 parameter name or acronym.

Introduction 1-71


5.7 A list after a parameter field describes valid entries for that field. Not all parameter fields show lists of valid entries. For more information on a particular parameter, follow either of these options:

• Right click in the parameter field and select I/O manual from the pop up menu. The online I/O manual opens to the current command.

• Place cursor in parameter field and select Help>Parameter Help from the main menu. The parameter help window appears. Leave window open and place curcor i other parameter fields for information on those parameters.

5.8 For a complete list of parameter options and ranges, refer to the 1677 SONET Link Commands and Messages manual (PN 3EM13852AD) for this cross-connect system. For online I/O manual help, select Help>I/O Manual from the main menu.

Figure 5-1. TL1DAT Enhanced Mode

Introduction1-72


Basic Mode

5.9 In Basic Mode, enter complete TL1 commands on the TL1 Command line in the Command Composition Panel. This mode is recommended only for users who are familiar with TL1 commands, parameters, and syntax. See figure 5-2.

5.10 After executing a command, the screen output area displays a successful response message with the effects of execution or an unsuccessful response message with an error code.

5.11 To execute a command in Basic Mode, perform the following steps:

1. In the TL1 Command line, enter command code and at least all required parameters. Use precise syntax, and end command with a ; (semicolon). System will not execute a command that is entered with any mistakes.

2. Click Send in the TL1DAT window.

System processes command and displays successful response message if command executed properly.

Introduction 1-73


TL1 Modes

5.12 The direct mode is supported for TL1 command entry.

Direct Mode

5.13 In Direct mode, enter complete TL1 commands at the prompt. This mode is recommended only for users who are familiar with TL1 commands, parameters, and syntax.

Figure 5-2. TL1DAT Basic Mode

Introduction1-74


Executing a Command in Direct Mode

5.14 To execute a command in Direct mode, perform the following steps:

1. Enter command code and at least all required parameters. Use precise syntax. The system will not execute a command that is entered with any syntax mistakes.

2. Press ; (semicolon) or Return.

The system processes the command and displays a successful response message if the command executed properly. The next command may be entered at the next prompt.

Introduction 1-75


Introduction1-76


6. SYSTEM MESSAGES

6.1 When the system processes a command, it returns a specific type of message to indicate the status of the request. These message types include: successful and unsuccessful response messages, in-progress messages, and alarm messages.

Response Messages

6.2 When a command is entered, the system processes it and then returns either a successful response message if the command executed properly or an unsuccessful response message if the command failed. The system records all command transactions, successful and unsuccessful, in the system's Audit Log. For more information on the Audit Log, refer to the Software Reference Guide in the back of this manual.

6.3 Successful response messages have the following general content and format:

System Identifier (SID) Date (YY-MM-DD) Time (HH:MM:SS)M CTAG COMPLD Comments or Data (as appropriate) [/* command acknowledgment */];

For example:

ALCATEL-1677SL 2004-10-17 15:10:04M 32 COMPLD /* RTRV-HDR */;

Introduction 1-77


6.4 Unsuccessful response messages have the following general content and format:

System Identifier (SID) Date (YY-MM-DD) Time (HH:MM:SS)M CTAG DENY error code [/* command acknowledgment or error text */];

For example:

ALCATEL-1677SL 2004-10-17 15:10:04M 23 DENY IDNV

/* Data Not Valid */;

A single or partially successful response message contains an error code, which is a 4-character mnemonic that indicates the cause of the failure. For example, IISP means “Input, Invalid Syntax or Punctuation”; PICC means “Privilege, Illegal Command Code.” The information displayed in the successful or partially successful response message varies for different commands. Refer to the Software Reference Guide in the back of this manual for a list of error codes and definitions.

The following are a few common reasons why commands fail:

• User command privileges are invalid for the command entered.

• Command format, syntax, or parameter data is incorrect.

• Command is invalid.

• Equipment is in an invalid state for the command.

In-Progress Messages

6.5 If the system does not complete a command within 2 seconds, it automatically generates an in-progress message to acknowledge that the command is being processed. In-progress messages do not interrupt other output responses. The system generates additional in-progress messages until the command completes.

Introduction1-78


Alarm Messages

6.6 Alarm notifications are sent to active login sessions in standard TL1 format.

An example:

ALCATEL-1677SL 2004-10-17 15:10:04*C 17 REPT ALM EQPT "IOC-5-A:CR,IMPROPRMVL,SA,10-17,15-10-04:\"Improper Removal\"";

Introduction 1-79


Introduction1-80


7. PRODUCT SUPPORT INFORMATION

Telephone Support

Customer Service Telephone Support

7.1 For telephone support for the customer services mentioned in this Product Support Information, call 888-ALCATEC (888-252-2832) or 613-784-6100, 8:00 a.m. to 5:00 p.m., Central Time, Monday through Friday. Ask the operator for the appropriate service to be connected to a qualified representative or engineer.

7.2 After-hours emergency telephone support is also available by calling 888-ALCATEC (888-252-2832) or 613-784-6100. An emergency is defined as an out-of-service, traffic-affecting problem or a nonoperating alarm system on traffic-bearing systems.

Quality Hotline

7.3 A toll-free Quality Hotline (800-553-4056) is available to all customers to report quality issues related to products or services.

7.4 The Quality Hotline is answered 24 hours a day, 365 days a year, and is available throughout all 50 states and Canada.

7.5 To report quality issues, call 800-553-4056. An operator will take the information and have an Alcatel Quality Assurance Representative respond during normal business hours (8:00 a.m. to 5:00 p.m. Central Time, Monday through Friday). The regular customer service numbers should be used for normal customer service functions.

Product Documentation and Training

Product Documentation

7.6 Product documentation is available on both paper and CD-ROM. The documentation can also be accessed through Alcatel's Online Support Documentation and Software web site at http://www.alcatel.com/osds. Product documentation updates appear on Alcatel's Online Support Documentation and Software web site before they are available in any other format.

Introduction 1-81


7.7 At Alcatel's Online Support Documentation and Software web site, follow the on-screen instructions to register for access and obtain a login ID. In addition to accessing product documentation, the Alcatel Online Support Documentation and Software web site allows the user to view the following:

• Application notes

• Configuration notes

• Data collections

• Frequently Asked Questions (FAQs)

• General information books

• General Release Documents (GRDs)

• Installation documents

• Methods of Procedure (MOPs)

• Product Change Notifications (PCNs)

• Product Information Bulletins (PIBs)

• Product manual updates

• Software patch and software load documents

• Software Update Documents (SUDs)

• Technical bulletins

• Training documents

• Urgent Product Warnings (UPWs)

Training

7.8 Equipment training is available to all customers. Crafts and maintenance personnel who are trained by Alcatel's Training department can expect more effective assistance if they need to call the Technical Assistance Center. Regularly scheduled courses are available at the training facilities in Plano, Texas. If a customer cannot attend a standard course, the Training department can arrange a course for a specific requirement and conduct it at the customer's facility. For further information, call customer service telephone support and ask for a training coordinator or write to one of the following addresses:

Introduction1-82


7.9 The annual Product Training Catalog can be ordered by calling the training coordinator, or it can be viewed on-line at http://www7.alcatel.com/service/catalog.

Technical Assistance Center

7.10 The Technical Assistance Center staff is always ready to provide high-quality technical assistance. Customers can expect effective telephone assistance when their crafts and maintenance personnel have been trained by Alcatel's Training department and are equipped with adequate test equipment, spares, and documentation at the site.

7.11 For technical assistance, call customer service telephone support.

After-hours Emergency Telephone Support

7.12 Emergency support is available after-hours through dispatch operators. Call customer service telephone support and ask for the Lightwave, Microwave, Operations Support System (OSS), Digital Loop Carrier (LMS), or Digital Cross-Connect emergency duty engineer.

7.13 An emergency is defined as an out-of-service, traffic-affecting problem or a nonoperating alarm system on traffic-bearing systems.

7.14 Nonemergency is defined as installation turn-ups, application questions, traffic cutover, routine maintenance, or other non-service-affecting maintenance. All non-service-affecting, after-hours telephone services are billable to the customer.

7.15 Please provide the operator with the following information:

• Company name

• Caller name

• A telephone number where caller can be reached

• A brief description of the problem, including the product involved

IN USA: IN CANADA:Alcatel USA3400 W. Plano Pkwy.Plano, Texas 75075ATTN: Training M/S 1206-553

Alcatel CanadaNetwork Services DivisionP.O. Box 13600Ottawa, Ontario K2K 2E6

Introduction 1-83


After-hours Nonemergency Telephone Support

7.16 After-hours telephone support to address new installations, system expansions, system operations, system application, or other non-service-affecting issues is available by contacting Alcatel Customer Service at 1-888-252-2832 (1-888-ALCATEC) or 1-613-784-6100.

On-site Technical Support

7.17 On-site technical support is available when as issue cannot be resolved remotely. This determination is usually made by Alcatel TAC during the problem investigation process. These services may or may not be billable to a customer. This depends on several factors such as what type of Service Level Agreement a customer has with Alcatel, the age of the product, etc.

Repair and Return Services

7.18 As part of a comprehensive technical support program, Alcatel provides factory repair services for equipment. This service is available both during and after the warranty period through Alcatel's Return and Repair department.

Spare Parts and Replacement Modules

7.19 For spare parts, spare modules, module exchange, and in-warranty replacement on a routine or emergency basis, call customer service telephone support.

7.20 Provide the following information:

• Company name

• Caller name

• A telephone number where caller can be reached

• A brief description of the problem, including product line, part number, and quantity of parts needed

7.21 For emergency assistance after normal business hours, call customer service telephone support, ask the operator for Emergency Parts Assistance, and provide the operator with the required information. The operator will contact an appropriate individual to respond.

Introduction1-84


Return for Credit or Warranty Exchange Procedure

7.22 Returned equipment must have a Return Authorization (RA) number. Obtain an RA number either by calling customer service telephone support or by fax (972-519-4611).

7.23 No equipment should be returned without an RA number. The following information is required:

• Description and quantity of equipment to be returned

• Reason for return

• Order number the equipment was purchased against and approximate date of purchase

Service Center

7.24 The Service Center tests, repairs, and modifies all modules (both in and out of warranty). Modules received for repair or modification are returned promptly.

Introduction 1-85


Return for Repair Procedure

7.25 Refer to paragraph 7.22 for information on obtaining an RA number. Notification to the Service Center and issuance of an RA number by Alcatel personnel must be made prior to shipment of parts. The following information must be furnished with the request for return authorization:

• Purchase order number or requisition number

• Description and quantity of equipment to be returned

• Reason for return:

– Modification required

– Defective equipment to be repaired

• Warranty status (in or out of warranty) and warranty date stamped on unit

• Specific nature of problem

• Name and telephone number of person who identified problem

• Special instruction/information

Introduction1-86


Shipping Instructions for Repair, Credit, or Warranty Exchange

7.26 Return equipment or parts prepaid to the address provided when the RA number was issued. The RA number must be prominently marked on the shipping label, the packing list, and any correspondence regarding the order.

• Include company name, address, and name of person to contact in case of a question.

• Include specific reason for return. (This aids prompt processing.)

• Include the same requisition number or purchase order number that was furnished with request for return authorization.

• Include type number and part number of unit.

• State whether equipment is in or out of warranty.

• Furnish shipping address for return of unit, if applicable, or other pertinent details.

• Mail purchase order, if applicable, to address shown under Return for Repair Procedure, Attention: Service Center.

Installation and Maintenance Services

Engineering and Installation Service

7.27 Whether installation for specific equipment or a full turnkey network facility is needed, Installation Service can help. Alcatel has experience in central office, outside plant, and customer premises applications, and specializes in flexible scheduling and high-quality service. Qualified staff are in place nationwide, so an installation can be started and completed promptly.

Contract Maintenance Service

7.28 Field service from Alcatel offices nationwide is available if a maintenance contract is selected. Alcatel field service is well-suited for private networks of any size. For a fixed annual fee, Alcatel provides prompt response to service calls and provides scheduled preventive maintenance, including FCC-required measurements and record keeping.

Introduction 1-87


7.29 Factory-trained service technicians are qualified on similar systems before they are allowed to maintain customer equipment. They have direct access to additional technical support around the clock and to all necessary tools and test equipment.

Introduction1-88

IXL-1003EM13851ADIssue 02, July 2006

Index Task Lists (IXLs)

IXL-100Index Task ListRefer to table 100-A to select the type of procedure or information needed to perform tasks on the system.

Table 100-A. Index Task List TYPE OF PROCEDURE/INFORMATION REFERENCEAuxiliary Equipment Provisioning IXL-102DS1 (T1) Functions IXL-107DS3 (T3) Functions IXL-106EC1 Functions IXL-115EDFA (OFA) Functions IXL-113Equipment Provisioning and Deprovisioning IXL-103EVC Functions IXL-114Gigabit Ethernet Functions IXL-111OC-n Functions IXL-108STS-n Functions IXL-109System Administration IXL-105System Information Reports IXL-104Transmux Functions IXL-112User Administration IXL-101VT1.5 Functions IXL-110

Index Task List 2-1

IXL-100 3EM13851ADIssue 02, July 2006

Index Task List2-2


IXL-101User AdministrationRefer to table 101-A to identify a common user administration function and the corresponding procedure.

Table 101-A. Common User Administration FunctionsFUNCTION REFERENCEAdd New User to System DLP-146Change User Password DLP-102Delete User from System DLP-147Log Into System DLP-100Log Out of System DLP-101Retrieve TL1 Commands Available for User Level DLP-220Set User and System Security Parameters DLP-106Set Alarm Attributes DLP-153

User Administration 2-3


User Administration2-4


IXL-102Auxiliary Equipment ProvisioningRefer to table 102-A to identify an auxiliary equipment provisioning function and the corresponding procedure.

Table 102-A. Auxiliary Equipment Provisioning FunctionsFUNCTION REFERENCEConfigure U.S. Robotics 56K Faxmodem DLP-103

Auxiliary Equipment Provisioning 2-5


Auxiliary Equipment Provisioning2-6


IXL-103Equipment Provisioning and DeprovisioningRefer to table 103-A to identify an equipment provisioning or deprovisioning function and the corresponding procedure.

Table 103-A. Equipment Provisioning and Deprovisioning FunctionsFUNCTION REFERENCEDeprovision Equipment DLP-113Provision Equipment DLP-112

Equipment Provisioning and Deprovisioning 2-7


Equipment Provisioning and Deprovisioning2-8


IXL-104System Information ReportsRefer to table 104-A to identify a system information report and the corresponding procedure for retrieval of the report.

Table 104-A. System Information ReportsREPORT REFERENCEDisplay Alarms DLP-111Enable/Disable Database Change Autonomous Messages DLP-221Retrieve Log File DLP-109Retrieve System Configuration DLP-104Schedule PM Reports DLP-133

System Information Reports 2-9


System Information Reports2-10


IXL-105System AdministrationRefer to table 105-A to identify a system administration function and the corresponding procedure.

Table 105-A. System Administration FunctionsFUNCTION REFERENCEActivate Disk DLP-191Administer System Timing/BITS DLP-108Administer TL1 Gateway Map DLP-173Configure EMA and TL1DAT on PC for NE DLP-210Connect 1677 SONET Link to FES301 DLP-222Connect PC to the 1677 SONET Link DLP-192Enable TL1 Gateway DLP-162Enter Trusted Host for Dynamic IP Address DLP-110Initialize System Processors DLP-105Install FTP Software DLP-201Issue TL1 Commands Through a Gateway DLP-198Perform Database Backup to Flash Disk DLP-206Perform Database Restore from Flash Disk DLP-207Perform FTP Backup of Provisioning Database DLP-188Perform FTP Restore of Provisioning Database DLP-189Reprogram Equipment Flash Memory DLP-175Set System Date and Time DLP-107Retrieve/ Change Site Identifier DLP-174Retrieve Disk Information DLP-190Retrieve Node IP Addresses DLP-176Switch to Redundant Card DLP-195

System Administration 2-11


System Administration2-12


IXL-106DS3 (T3) FunctionsRefer to table 106-A to identify a DS3 function and the corresponding procedure.

Table 106-A. DS3 (T3) FunctionsFUNCTION REFERENCEAdminister DS3 Cross-Connection DLP-124Administer DS3 Loopback DLP-130Administer DS3 Test Access Connections DLP-184Administer Far-End Alarm and Control (FEAC) DLP-219Change Facility Service State DLP-193Change Line Buildout (LBO) DLP-197DS3 (T3) Deprovisioning NTP-106DS3 (T3) Provisioning NTP-100Modify DS3 (T3) Parameters DLP-212Report DS3 PM Data DLP-134Schedule PM Reports DLP-133Set Alarm Attributes DLP-153Set Default Thresholds for All Cross-Connects DLP-196Set DS3 PM Mode DLP-138Set DS3 PM Threshold Levels DLP-142Perform Manual Protection Switch for Working Cards DLP-194

DS3 (T3) Functions 2-13


DS3 (T3) Functions2-14


IXL-107DS1 (T1) FunctionsRefer to table 107-A to identify a DS1 function and the corresponding procedure.

Table 107-A. DS1 (T1) FunctionsFUNCTION REFERENCEAdminister DS1 Cross-Connection DLP-177Administer T1 Loopback DLP-200Administer T1 Test Access Connections DLP-208Change Facility Service State DLP-193DS1 (T1) Deprovisioning NTP-107DS1 (T1) Provisioning NTP-101Modify DS1 (T1) Parameters DLP-211Report DS1 PM Data DLP-178Schedule PM Reports DLP-133Set Alarm Attributes DLP-153Set Default Thresholds for All Cross-Connects DLP-196Set DS1 PM Mode DLP-128Set DS1 PM Threshold Levels DLP-187

DS1 (T1) Functions 2-15


DS1 (T1) Functions2-16


IXL-108OC-n FunctionsRefer to table 108-A to identify an OC-n function and the corresponding procedure.

Table 108-A. OC-n FunctionsFUNCTION REFERENCEAdd Node to Two-Fiber BLSR DLP-204Add Node to UPSR DLP-202Administer Dual Ring Interconnect (DRI) DLP-157Administer OC-n BLSR DLP-156Administer OC-n Facility Protection Group DLP-119Administer OC-n Loopback DLP-131Administer OC-n UPSR DLP-151Change Facility Service State DLP-193Delete Node from Two-Fiber BLSR DLP-205Delete Node from UPSR DLP-203Modify OC-n Parameters DLP-215OC-n Deprovisioning NTP-108OC-n Provisioning NTP-102Report OC-n PM Data DLP-135Restart Laser for OC-n Facility DLP-169Schedule PM Reports DLP-133Set Alarm Attributes DLP-153Set OC-n PM Mode DLP-139Set OC-n PM Threshold Levels DLP-143Switch OC-n Line to Protection DLP-132

OC-n Functions 2-17


OC-n Functions2-18


IXL-109STS-n FunctionsRefer to table 109-A to identify an STS-n function and the corresponding procedure.

Table 109-A. STS-n FunctionsFUNCTION REFERENCEAdminister STS-n Cross-Connection DLP-125Administer STS-1 Facility Protection Group DLP-199Administer STS-n Test Access Connection DLP-148Change Facility Service State DLP-193Modify STS-n Parameters DLP-217Report STS-n PM Data DLP-136Schedule PM Reports DLP-133Set Alarm Attributes DLP-153Set Default Thresholds for All Cross-Connects DLP-196Set STS-n PM Mode DLP-140Set STS-n PM Threshold Levels DLP-144STS-n Deprovisioning NTP-109STS-n Provisioning NTP-103Switch STS-n Path to Protection DLP-149

STS-n Functions 2-19


STS-n Functions2-20

IXL-110

VT1.5 Functions 2-21


IXL-110VT1.5 FunctionsRefer to table 110-A to identify a VT1.5 function and the corresponding procedure.

Table 110-A. VT1.5 FunctionsFUNCTION REFERENCEAdminister VT1.5 Cross-Connection DLP-126Administer VT1.5 Loopback DLP-152Administer VT1 Test Access Connections DLP-209Change Facility Service State DLP-193Modify VT1.5 Parameters DLP-218Report VT1.5 PM Data DLP-137Retrieve VSC and TMUX Usage DLP-179Schedule PM Reports DLP-133Set Alarm Attributes DLP-153Set Default Thresholds for All Cross-Connects DLP-196Set VT1.5 PM Mode DLP-141Set VT1.5 PM Threshold Levels DLP-145VT1.5 Deprovisioning NTP-110VT1.5 Provisioning NTP-104


IXL-111Gigabit Ethernet FunctionsRefer to table 111-A to identify a Gigabit Ethernet function and the corresponding procedure.

Table 111-A. Gigabit Ethernet FunctionsFUNCTION REFERENCEAdminister Gigabit Ethernet Cross-Connection DLP-164Change Facility Service State DLP-193Gigabit Ethernet Deprovisioning NTP-111Gigabit Ethernet Provisioning NTP-105Modify GIGE Parameters DLP-214Report Gigabit Ethernet PM Data DLP-167Schedule PM Reports DLP-133Set Alarm Attributes DLP-153Set Default Thresholds for All Cross-Connects DLP-196Set Gigabit Ethernet PM Mode DLP-165Set Gigabit Ethernet PM Threshold Levels DLP-166Provision Gigabit Ethernet Circuits NTP-120Deprovision Gigabit Ethernet Circuits NTP-121

Gigabit Ethernet Functions 2-23


Gigabit Ethernet Functions2-24


IXL-112Transmux FunctionsRefer to table 112-A to identify a Transmux function and the corresponding procedure.

Table 112-A. Transmux FunctionsFUNCTION REFERENCERetrieve VSC and TMUX Usage DLP-179Transmux Deprovisioning NTP-113Transmux Provisioning NTP-112

Transmux Functions 2-25


Transmux Functions2-26


IXL-113EDFA (OFA) FunctionsRefer to table 113-A to identify a EDFA (OFA) function and the corresponding procedure.

Table 113-A. EDFA FunctionsFUNCTION REFERENCEChange Facility Service State DLP-193Optical Fiber Amplifier Provisioning NTP-114Optical Fiber Amplifier Deprovisioning NTP-115Modify OFA Parameters DLP-216Report OFA PM Data DLP-185Schedule PM Reports DLP-133Set OFA PM Threshold Levels DLP-186Set Alarm Attributes DLP-153Set OFA PM Mode DLP-129

EDFA (OFA) Functions 2-27


EDFA (OFA) Functions2-28


IXL-114EVC FunctionsRefer to table 114-A to identify an EVC (Ethernet Virtual Concatenation) function and the corresponding procedure.

Table 114-A. EVC FunctionsFUNCTION REFERENCEEVC Deprovisioning NTP-117EVC Provisioning NTP-116

EVC Functions 2-29


EVC Functions2-30


IXL-115EC1 FunctionsRefer to table 115-A to identify an EC1 function and the corresponding procedure.

Table 115-A. EVC FunctionsFUNCTION REFERENCEAdminister EC1 Loopback DLP-159Change Facility Service State DLP-193EC1 Deprovisioning NTP-119EC1 Provisioning NTP-118Modify EC1 Parameters DLP-213Report EC1 PM Data DLP-182Schedule PM Reports DLP-133Set Alarm Attributes DLP-153Set EC1 PM Mode DLP-127Set EC1 PM Threshold Levels DLP-170

EC1 Functions 2-31


EC1 Functions2-32

NTP-1003EM13851ADIssue 02, July 2006

Non-trouble Procedures (NTPs)

NTP-100DS3 (T3) ProvisioningPURPOSE

This procedure provides instructions and sequence for DS3 provisioning.

STEP PROCEDURE

1 A DS3 port can stand alone or it can be embedded in an STS-1, which is embedded in an EC1 or OC-n.

Provision DS3 in one of the following provisioning schemes:

a. Stand-alone DS3.

– Refer to DLP-112 to provision DS3 card.

– Refer to DLP-115 to provision DS3 facility.

b. EC1 - STS-1 - DS3

– Refer to NTP-118 to provision EC1.

– Refer to NTP-103 to provision STS-1.


c. OC-n - STS-1 - DS3

– Refer to NTP-102 to provision OC-n.

– Refer to NTP-103 to provision STS-1.


2 STOP. This procedure is complete.

DS3 (T3) Provisioning 3-1

NTP-100 3EM13851ADIssue 02, July 2006

DS3 (T3) Provisioning3-2


NTP-101DS1 (T1) ProvisioningPURPOSE

This procedure provides instructions and sequence for DS1 provisioning.

GENERAL

A DS1 facility is embedded in

• a standalone DS3

• a DS3 embedded in an STS-1, which is embedded in an OC-n

• a VT1.5 embedded in an STS-1, which is embedded in an OC-n

• a DS3 embedded in an STS-1, which is embedded in an EC1

• a VT1.5 embedded in an STS-1, which is embedded in an EC1



STEP PROCEDURE

1 Depending on the provisioning scheme, provision T1 in one of the following sequences:

a. T3 – T1

– Refer to NTP-100 to provision DS3.

– Refer to DLP-160 to provision DS1.

b. OC-n – STS1 – T3 – T1


– Refer to DLP-117 to provision STS-1.

– Refer to DLP-115 to provision T3.


c. OC-n – STS1 – VT1 – T1



– Refer to DLP-118 to provision VT1.


d. EC1 – STS1 – T3 – T1





e. EC1 – STS1 – VT1 – T1



– Refer to DLP-118 to provision VT1.




NTP-102OC-n ProvisioningPURPOSE

This procedure provides instructions and sequence for OC-n provisioning.

STEP PROCEDURE

1 Provision OC-n card.

For details, refer to DLP-112.

2 Provision OC-n facility.


3 Provision OC-n facility protection group.



OC-n Provisioning 3-7


OC-n Provisioning3-8


NTP-103STS-n ProvisioningPURPOSE

This procedure provides instructions for STS-n provisioning.

GENERAL

An STS-1 port must be embedded in an EC1 or OC-n. An STS-3c, STS-12c, or STS-48c port must be embedded in an OC-n.

STEP PROCEDURE

1 Depending on the provisioning scheme, provision a STS-n in one of the following sequences:

a. OC-n – STS-n


– Refer to DLP-117 to provision STS-n.

b. EC1 – STS-1




STS-n Provisioning 3-9


STS-n Provisioning3-10


NTP-104VT1.5 ProvisioningPURPOSE

This procedure provides instructions and sequence for VT1.5 provisioning.

GENERAL

A VT1.5 facility must be embedded in an STS-1, which is embedded in an OC-n or EC1.

STEP PROCEDURE

1 Depending on the provisioning scheme, provision a VT1.5 in one of the following sequences:

a. OC-n – STS1 – VT1.5



– Refer to DLP-118 to provision VT1.5.

b. EC1 – STS1 – VT1



– Refer to DLP-118 to provision VT1.5.


VT1.5 Provisioning 3-11


VT1.5 Provisioning3-12


NTP-105Gigabit Ethernet ProvisioningPURPOSE

This procedure provides instructions and sequence for Gigabit Ethernet provisioning.

STEP PROCEDURE

1 Provision GIGE card.


2 Provision GIGE port.



Gigabit Ethernet Provisioning 3-13


Gigabit Ethernet Provisioning3-14


NTP-106DS3 (T3) DeprovisioningPURPOSE

This procedure provides instructions and sequence for DS3 deprovisioning.

STEP PROCEDURE

1 Depending on the provisioning scheme, deprovision DS3 in one of the following sequences:

a. Stand-alone DS3.

– Refer to DLP-120 to deprovision DS3.

– If required, refer to DLP-113 to deprovision DS3 card after all facilities in card are deprovisioned.

b. OC-n – STS-1 – DS3


– Refer to DLP-122 to deprovision STS-1.

– Refer to NTP-108 to deprovision OC-n.

c. EC1 – STS-1 – DS3



– Refer to NTP-119 to deprovision EC1.


DS3 (T3) Deprovisioning 3-15


DS3 (T3) Deprovisioning3-16


NTP-107DS1 (T1) DeprovisioningPURPOSE

This procedure provides instructions and sequence for DS1 deprovisioning.

GENERAL

A DS1 facility is embedded in

• a standalone DS3

• a DS3 embedded in an STS-1, which is embedded in an OC-n

• a VT1.5 embedded in an STS-1, which is embedded in an OC-n

• a DS3 embedded in an STS-1, which is embedded in an EC1

• a VT1.5 embedded in an STS-1, which is embedded in an EC1



STEP PROCEDURE

1 Depending on the provisioning scheme, deprovision T1 in one of the following sequences:

a. T3 – T1

– Refer to DLP-161 to deprovision T1.

– Refer to NTP-106 to deprovision T3.

b. OC-n – STS-1 – T3 – T1





c. OC-n – STS-1 – VT1 – T1


– Refer to DLP-123 to deprovision VT1.



d. EC1 – STS-1 – T3 – T1





e. EC1 – STS-1 – VT1 – T1


– Refer to DLP-123 to deprovision VT1.





NTP-108OC-n DeprovisioningPURPOSE

This procedure provides instructions and sequence for OC-n deprovisioning.

STEP PROCEDURE

1 Deprovision OC-n facility protection group.


2 Deprovision OC-n port.


3 If required, deprovision OC-n card after all facilities in card are deprovisioned.



OC-n Deprovisioning 3-21


OC-n Deprovisioning3-22


NTP-109STS-n DeprovisioningPURPOSE

This procedure provides instructions and sequence for STS-n deprovisioning.

GENERAL

An STS-1 port must be embedded in an EC1 or OC-n. An STS-3c, STS-12c, or STS-48c port must be embedded in an OC-n.

STEP PROCEDURE

1 Depending on the provisioning scheme, deprovision a STS-n in one of the following sequences:

a. OC-n – STS-n

– Refer to DLP-122 to deprovision STS-n.


b. EC1 – STS-1




STS-n Deprovisioning 3-23


STS-n Deprovisioning3-24


NTP-110VT1.5 DeprovisioningPURPOSE

This procedure provides instructions and sequence for VT1.5 deprovisioning.

GENERAL

A VT1.5 facility must be embedded in an STS-1, which is embedded in an OC-n or EC1.

STEP PROCEDURE

1 Depending on the provisioning scheme, deprovision a VT1.5 in one of the following sequences:

a. OC-n – STS1 – VT1.5

– Refer to DLP-123 to deprovision VT1.5.



b. EC1 – STS1 – VT1

– Refer to DLP-123 to deprovision VT1.5.




VT1.5 Deprovisioning 3-25


VT1.5 Deprovisioning3-26


NTP-111Gigabit Ethernet DeprovisioningPURPOSE

This procedure provides instructions and sequence for Gigabit Ethernet deprovisioning.

STEP PROCEDURE

1 Deprovision embedded Ethernet Virtual Concatenation (EVC) facilities.


2 Deprovision Gigabit Ethernet port.


3 If required, deprovision Gigabit Ethernet card after all facilities in card are deprovisioned.



Gigabit Ethernet Deprovisioning 3-27


Gigabit Ethernet Deprovisioning3-28


NTP-112Transmux ProvisioningPURPOSE

This procedure provides instructions and sequence for Transmux provisioning.

STEP PROCEDURE

1 Provision Transmux card.



Transmux Provisioning 3-29


Transmux Provisioning3-30


NTP-113Transmux DeprovisioningPURPOSE

This procedure provides instructions and sequence for Transmux deprovisioning.

STEP PROCEDURE

1 Deprovision Transmux card after all facilities in card are deprovisioned.



Transmux Deprovisioning 3-31


Transmux Deprovisioning3-32


NTP-114Optical Fiber Amplifier ProvisioningPURPOSE

This procedure provides instructions and sequence for OFA provisioning.

STEP PROCEDURE

1 Provision EDFA card.


2 Provision Optical Fiber Amplifier (OFA).



Optical Fiber Amplifier Provisioning 3-33


Optical Fiber Amplifier Provisioning3-34


NTP-115Optical Fiber Amplifier DeprovisioningPURPOSE

This procedure provides instructions and sequence for EDFA/OFA deprovisioning.

STEP PROCEDURE

1 Deprovision Optical Fiber Amplifier (OFA).


2 Deprovision EDFA card.



Optical Fiber Amplifier Deprovisioning 3-35


Optical Fiber Amplifier Deprovisioning3-36


NTP-116EVC ProvisioningPURPOSE

This procedure provides instructions and sequence for EVC (Ethernet Virtual Concatenation) provisioning.

STEP PROCEDURE

1 Provision GIGE card.




3 Provision embedded EVC facilities.



EVC Provisioning 3-37


EVC Provisioning3-38


NTP-117EVC DeprovisioningPURPOSE

This procedure provides instructions and sequence for EVC (Ethernet Virtual Concatenation) deprovisioning.

STEP PROCEDURE

1 Deprovision embedded EVC facilities.


2 Deprovision GIGE port.


3 If required, deprovision GIGE card after all facilities in card are deprovisioned.



EVC Deprovisioning 3-39


EVC Deprovisioning3-40


NTP-118EC1 ProvisioningPURPOSE

This procedure provides instructions and sequence for EC1 provisioning.

STEP PROCEDURE

1 Provision ECC module.


2 Provision EC1 facility.



EC1 Provisioning 3-41


EC1 Provisioning3-42


NTP-119EC1 DeprovisioningPURPOSE

This procedure provides instructions and sequence for EC1 deprovisioning.

STEP PROCEDURE

1 Deprovision EC1 facility.


2 If required, deprovision ECC after all facilities in card are deprovisioned.



EC1 Deprovisioning 3-43


EC1 Deprovisioning3-44


NTP-120GIGE Circuit ProvisioningPURPOSE

This procedure provides instructions and sequence for GIGE circuit provisioning.

STEP PROCEDURE



2 Provision EVC port.


3 Create GIGE cross-connections.



GIGE Circuit Provisioning 3-45


GIGE Circuit Provisioning3-46


NTP-121GIGE Circuit DeprovisioningPURPOSE

This procedure provides instructions and sequence for GIGE circuit deprovisioning.

STEP PROCEDURE

1 Delete GIGE cross-connections.


2 Deprovision EVC port.


3 Deprovision GIGE port.



GIGE Circuit Deprovisioning 3-47


GIGE Circuit Deprovisioning3-48

DLP-1003EM13851ADIssue 02, July 2006

Detailed Level Procedures (DLPs)

DLP-100Log Into SystemPURPOSE

This procedure provides the instructions to establish a session with the network element (NE) and to log in a specific user.

PREREQUISITE

The User Identification (UID) and current Password Identifier (PID) must be known before login can be accomplished.

GENERAL

ACT-USER is used to establish a session with the system and log in the specified user.

Access through telnet must be made from a trusted host. To access the system over telnet, port 3083 must be used.

For system security, the screen displays asterisks (******) in place of the characters entered for the password. In-progress response messages are not displayed.

A user cannot log in (using ACT-USER) on a terminal where another user is already logged in.

If a user's PID or UID has been deactivated or removed, only a System Administrator account user can enter a new user password or user account database entry.

For parameter descriptions of TL1 commands used in this procedure, refer to the 1677 SONET Link Commands and Messages manual (PN 3EM13852AD) or the 1677 SONET Link Address and Location Guide (PN 3EM13854AB). The Software Reference Guide in the back of this manual may also be used as reference.

STEP PROCEDURE

1 Select action.

To log in with 1677 SONET Link EMA, go to step 2.To log in with TL1, go to step 7.

Log in with 1677 SONET Link EMA

2 Right-click on appropriate NE in Network Element Synthesis (NES) window.

3 Select Start supervision from the menu options.

4 Enter login and password.

Log Into System 4-1

DLP-100 3EM13851ADIssue 02, July 2006

5 Click OK.

6 Go to step 10.

Log in with TL1

7 At login prompt, enter ACT-USER::UID:::PID;

where:UID=user identifierPID=password identifier

8 Did system return a successful response?

If yes, go to step 10.If no, go to step 9.

9 System returns error code when current logged-in user enters ACT-USER command. Refer to Software Reference Guide in this manual for complete list of error codes and definitions. For security purposes, system does not return error code when user who is not logged into system enters unsuccessful ACT-USER command.

Several unsuccessful attempts to log in can cause terminal lockout.

Check parameters for spelling and case-sensitive characters. Go to step 7 to retry system login.


Log Into System4-2


DLP-101Log Out of SystemPURPOSE

This procedure provides the instructions to terminate a session with the system and to log out a specific user.

GENERAL

A user can log only their own active User Identification (UID) out of the system. A System Administrator can log any other user out of the system.

The CANC-CID-SECU command is used to cancel (disconnect) a session that is running over a channel or port specified by its channel identifier (CID). These channels consist of the console, the debug port, and telnet connections. This command can terminate individual telnet sessions from a host, all sessions from a host, or all remote sessions. Only an administrator can use this command. The current session cannot be disconnected.


STEP PROCEDURE

1 Select action.

To log out with 1677 SONET Link EMA, go to step 2.To log out with TL1, go to step 11.

Log Out with 1677 SONET Link EMA

2 Select action.

To log out own UID, go to step 3.To log out other UID, go to step 5.

Log Out Own UID

3 Right-click on appropriate NE in the NES window and select Stop Supervision.

4 Go to step 19.

Log Out Other UID

5 Expand the System domain in the Scope Pane.

Log Out of System 4-3


6 Expand the NE Security domain.

7 Click on Users node to display all existing user profiles.

8 Right-click appropriate user profile and select Logoff from menu.

9 Click Yes.

10 Go to step 19.

Log Out with TL1

11 Select action.

To log out own UID, go to step 12.To log out other UID, go to step 14.To log out a user at a particular port, go to step 16.

Log Out Own User ID

12 Enter CANC-USER;

13 Go to step 19.

Log Out Other UID

14 Enter CANC-USER::UID;

where:UID=User ID to log out of system. Default is UID of person executing command.

15 Go to step 19.

Log Out User at Particular Port

16 Enter CANC-CID-SECU::CID;

where:CID=channel to be logged out. {IP Address, IP Address.Port, CONSOLE, DEBUG, REMOTE}


If yes, logout was successful. Go to step 19.If no, go to step 18.

Log Out of System4-4


18 Check parameters for correct port. Go to step 16 to retry.


Log Out of System 4-5


Log Out of System4-6


DLP-102Change User PasswordPURPOSE

This procedure provides the instructions to change a user's login Password Identifier (PID).

PREREQUISITE

The personal User Identification (UID) and current PID for the user must be known.

GENERAL

ED-PID is used to change a user’s own password, and the user must enter the current UID and PID. If a PID or UID has been deactivated or removed, only a System Administrator account user can enter a new PID or UID database entry.

ED-USER-SECU is used by a System Administrator to change the PID of any user.

The minimum number of characters in a password can be changed via ED-SECU and the PLEN parameter.


STEP PROCEDURE

1 Select action.

To change password with 1677 SONET Link EMA, go to step 2.To change password with TL1, go to step 11.

Change Password with 1677 SONET Link EMA

2 Expand the System domain in the Navigation Tree.


4 Click on Users to display all existing user profiles.

5 Right-click appropriate user profile.

6 Select Change Password from menu.

Change User Password 4-7


7 In Edit Password window, enter old password and new password into corresponding fields.

8 Re-enter new password to verify correct new password in set.

9 Click OK.

10 Go to step 18.

Change Password with TL1

11 Select action.

To change own password, go to step 12.To change password of another user, go to step 17.

Change Own Password

12 Enter ED-PID::[UID]:::OLDPID,NEWPID;

where:UID={3-32 valid UID characters}OLDPID={6-32 valid PID characters}NEWPID={6-32 valid PID characters}



14 Check error code message.

15 Consider error code message, and then go to step 12 for another attempt to change password.

16 Go to step 18.

Change Password of Another User

17 Enter ED-USER-SECU::UID:::,[PID],,[UAP];

where:UID=User ID {3-32 valid UID characters}PID=New password {6-32 valid PID characters}UAP=User privilege {CONF, NETADMIN, PROV, READ, SEC, TEST}


Change User Password4-8


DLP-103Configure U.S. Robotics 56K FaxmodemPURPOSE

This procedure provides the instructions to configure a U.S. Robotics® 56K Faxmodem for use with the 1677 SONET Link.

PREREQUISITES

This procedure requires the following equipment:

• PC laptop with a DB9 COM interface and terminal emulation software

• U.S. Robotics 56K Faxmodem V.92

• DB9 - DB25 straight-through cable (not null modem) (Used only to configure the US Robotics Modem from laptop)

• RJ11 - DB9 console cable with 9-25 pin null modem adapter (PN 101094-A)

• DB9 (Male) - DB9 (Female) Null Modem Adapter

• DB9 (Male) - DB25 (Male) straight-through adapter

The terminal used in this procedure must be configured to operate at 9600 bits per second (bps), 8 data bits, and no parity (9600-8N1).

Another modem (such as an internal modem in a laptop or tower PC) is needed to call the US Robotics Faxmodem once it is configured. The laptop is used to configure the US Robotics Faxmodem.


Refer to the 1677 SONET Link Installation Practices manual (PN 3EM13849AD) for ESD precaution procedures and installation information.

STEP PROCEDURE

1 Connect modem to power source.

2 Set up the laptop terminal emulation software to use the appropriate COM port for the 9-pin connector on the back of the laptop.

3 Verify terminal emulation software is running correctly.

Set up terminal emulation software as 9600-8N1 with no Flow Control.

Configure U.S. Robotics 56K Faxmodem 4-9


4 There is only one possible location for cable connection on modem.

Connect DB9 - DB25 straight-through cable between modem and laptop. Cable connects to modem at DB-25 female connector. Cable connects to DB9 COM port on laptop (typically COM1). See figure 103-1 for equipment setup.

Reset Modem to Factory Defaults

5 Set DIP switches 1, 3, 7, and 8 DOWN (ON) and all other DIP switches UP (OFF).

6 Turn modem on.

Change Default Values

7 At terminal, type the following command to wake up the modem:

atz

An OK message is returned.

8 Type the following command to disable data compression:

at&K0

9 Type the following command to set ceiling connect speed to 9600 bps:

at&N6

10 Type the following command to set floor connect speed to 9600 bps:

at&U6

Figure 103-1. Modem Configuration

677-0078-1060503

MODEM

LAPTOP

DB-9 Connector

DB-25 Connector

Configure U.S. Robotics 56K Faxmodem4-10


11 Type the following command to save these changes to the Y0 NVRAM (non-volatile RAM) location:

at&w0

12 Type the following command to save these changes to the Y1 NVRAM location:

at&w1

13 Turn the modem off.

14 Set DIP switch 7 UP (OFF). Do not change settings for other DIP switches.

15 Turn the modem on.

16 Type the following commands to view the modem settings:

atz

ati4

Example:

atz

ati4U.S. Robotics 56K FAX EXT Settings...

B0 E1 F1 M1 Q0 V1 X1 Y0 BAUD=9600 PARITY=N WORDLEN=8 DIAL=TONE ON HOOOK CID=0

&A1 &B0 &C1 &D0 &G0 &H0 &I0 &K0 (Please note bolded changed settings) &M4 &N6 &P1 &R1 &S0 &T5 &U6 &Y1

S00=001 S01=000 S02=043 S03=013 S04=010 S05=008 S06=004 S07=060 S08=002 S09=006 S10=014 S11=070 S12=050 S13=000 S15=000 S16=000 S18=010 S19=000 S21=010 S22=017 S23=019 S25=005 S27=000 S28=008 S29=020 S30=000 S31=128 S32=002 S33=000 S34=000 S35=000 S36=014 S38=000 S39=000 S40=001 S41=000 S42=000



17 Type the following command to view the NVRAM Y0 and Y1 settings:

ati5

Example:

ati5U.S. Robotics 56K FAX EXT NVRAM Settings...

Template Y0

DIAL=TONE B0 F1 M1 X1 BAUD=9600 PARITY=N WORDLEN=8

&A1 &B0 &G0 &H0 &I0 &K0 &M4 &N6 &P1 &R1 &S0 &T5 &U6 &Y1

S00=001 S02=043 S03=013 S04=010 S05=008 S06=004 S07=060 S08=002 S09=006 S10=014 S11=070 S12=050 S13=000 S15=000 S19=000 S21=010 S22=017 S23=019 S25=005 S27=000 S28=008 S29=020 S30=000 S31=128 S32=002 S33=000 S34=000 S35=000 S36=014 S38=000 S39=000 S40=001 S41=000 S42=000

Strike a key when ready...

Template Y1

DIAL=TONE B0 F1 M1 X1 BAUD=9600 PARITY=N WORDLEN=8

&A1 &B0 &G0 &H0 &I0 &K0 &M4 &N6 &P1 &R1 &S0 &T5 &U6 &Y1

S00=001 S02=043 S03=013 S04=010 S05=008 S06=004 S07=060 S08=002 S09=006 S10=014 S11=070 S12=050 S13=000 S15=000 S19=000 S21=010 S22=017 S23=019 S25=005 S27=000 S28=008 S29=020 S30=000 S31=128 S32=002 S33=000 S34=000 S35=000 S36=014 S38=000 S39=000 S40=001 S41=000 S42=000

Connect Modem to 1677 SONET Link Console

18 Turn modem off.

19 Set DIP switches 1 and 4 DOWN and set all other DIP switches UP. Refer to table 103-A for modem settings and configuration for operation.



20 Connect modem to the 1677 SONET Link using the black console cable (RJ11 - DB9) and a 9-25 pin null modem adapter. The null modem adapter is needed because the 1677 SONET Link is wired to connect to a DTE, not a DCE (modem). See figure 103-2.

Table 103-A. Modem Settings and Configuration for OperationDIP Switch Number and Position Function1 down (on) DTR Override2 up (off) Verbal Result Codes3 up (off) Suppress Result Codes4 down (on) No Echo, Offline Commands5 up (off) Modem answers on first ring6 up (off) Carrier Detect Override Disabled7 up (off) Load the Y0 configuration from user-defined

non-volatile memory (NVRAM)8 up (off) Disables command recognition (Dumb Mode)



21 Turn modem on.

22 Perform a test dial to the US Robotics Modem.

a. Connect laptop to a second analog phone line via an RJ-11 cable.

b. Use the terminal emulation software on the laptop to connect to the laptop modem. (For set up, use appropriate COM port and use 9600-8N1 with no Flow Control.)

c. Dial from the laptop to the US Robotics Modem.


Figure 103-2. US Robotics Modem Connection to System

STATUS

TIMING

EXT.

IN-USE

BITS

TIP

TIP

TIP

TIP

RING

RING

RING

RING

GND

GND

GND

GND

A

B

TIMING

IN

OUT

IN

OUT

DB-9

connector (F)US Robotics

Modem

Console cable

PN 101094-A

RJ-11

connector

Transmission

line

ETHERNET

CONSOLE

677-0179-1060603

Standard analog phone line

RJ-11 cable

Analog Phone

Line

DB-9 (M) DB-9 (F)

null modem

adapter

DB-9 (M) DB-25 (M)

adapter

DB-9 DB-25

null modem adapter



DLP-104Retrieve System ConfigurationPURPOSE

This procedure provides the instructions to retrieve general system level configuration information.

GENERAL

RTRV-PRMTR-NE command retrieves general system level configuration information that consists of the following parameters:

• System type

• Software release number

• Software release date

• Software release stream

• Release type

• Maximum matrix size

• Configuration size

• System restart status


STEP PROCEDURE

1 Select action.

To retrieve system configuration with 1677 SONET Link EMA, go to step 2.To retrieve system configuration with TL1, go to step 5.

Retrieve System Configuration with 1677 SONET Link EMA

2 Right click on the Network Element domain and select Properties>General. System configuration information appears in the System Information window.

Another way to view this same information is to right click on the System domain and select Properties>General.

Retrieve System Configuration 4-15


3 Click Close.

4 Go to step 7.

Retrieve System Configuration with TL1

5 Enter RTRV-PRMTR-NE;

6 Check output for system configuration.

The following example shows output for a 1677 SONET Link. The software release is R04.00.00 and the restart status is COMPLETE.

RTRV-PRMTR-NE;

ALCATEL-1677SL 04-11-01 13:24:28M 0 COMPLD ":1677SL,ADM&APS&DCS,R04.00.00,,,,::COMPLETE" /* RTRV-PRMTR-NE */;


Retrieve System Configuration4-16


DLP-105Initialize System ProcessorsPURPOSE

This procedure provides the instructions to reset processor-based cards provisioned and installed in the system.

PREREQUISITES

To reset an IOC, the user must have configure privilege; to reset any other card, the user must have Network Administrator privilege.

GENERAL

INIT-SYS is used to cold start (reset and reload with executable code) and warm start the processor-based cards: CCC, IOC, and SWC. All existing cross-connections remain intact during initialization. For the INIT-SYS command to execute on a specified module, the module must have a Primary State (PST) of OOS-MA or OOS-AUMA.

There are three levels of initialization, as defined by the PHASE parameter value:

• PHASE value 0: sufficient to reset an IOC.

• PHASE value 1: sufficient to reset a common card other than the active CCC.

• PHASE value 2: Required to reset the active CCC or the entire system.

If the command is applied to a specific module, it acts like a power-on reset and causes the module to undergo power-on initialization operations. If the command is applied to the entire NE, it acts like a power-on reset for all the modules equipped in the system.


STEP PROCEDURE

1 Select action.

To initialize system or cards with 1677 SONET Link EMA, go to step 2.To initialize system or cards with TL1, go to step 19.

Initialize System Processors 4-17


Initialize System or Cards with 1677 SONET Link EMA

2 Select action.

To initialize entire system, go to step 3.To initialize cards, go to step 6.

Initialize Entire System

3 Right-click on Network Element domain and select Initialize NE.

Another way to initialize the system is to right-click on the System domain and select Initialize NE.

4 Click Yes.

5 Go to step 25.

Initialize CCC, IOC, and SWC Cards

6 Select the Equipment domain in the Scope Pane.

7 Select the card to initialize and observe the Primary State in the Result Pane.

8 Is the Primary State IS, OOS-AU, OOS-MA, or OOS-AUMA?

If IS or OOS-AU, go to step 9.If OOS-MA or OOS-AUMA, go to step 11.

9 Right-click on appropriate card and select Service State>Remove.

10 Click Yes.

11 Right-click on appropriate card and select Initialize Board.

12 Click Yes.

13 When initialization is complete, right-click on card and select Service State>Restore.

14 Click Yes.

15 Go to step 25.

Initialize System Processors4-18


Initialize System or Cards with TL1

16 Select action.

To initialize entire system, go to step 17.To initialize cards, go to step 19.

Initialize Entire System

17 Enter INIT-SYS:::::2;

18 Go to step 25.

Initialize CCC, IOC, and SWC Cards

19 Enter RTRV-EQPT::AID;

where: AID=Access Identifier of card to initialize

20 Observe output.

21 Is the PST IS, OOS-AU, OOS-MA, or OOS-AUMA?

If IS or OOS-AU, go to step 22.If OOS-MA or OOS-AUMA, go to step 23.

22 Enter RMV-EQPT::AID;

where: AID=Access Identifier of card to initialize

23 Enter INIT-SYS::AID:::[PHASE];

where:AID=Access Identifier of card to initializePHASE={0, 1, or 2} (Default=0)

24 Enter RST-EQPT::AID;

where: AID=Access Identifier of card that was initialized


Initialize System Processors 4-19


Initialize System Processors4-20


DLP-106Set User and System Security ParametersPURPOSE

This procedure provides the instructions to retrieve and change security settings for the system or for a specific user.

GENERAL


STEP PROCEDURE

1 Select action.

To set user and system security parameters with 1677 SONET Link EMA, go to step 2.To set user and system security parameters with TL1, go to step 29.

Set User and System Security Parameters with 1677 SONET Link EMA

2 Select action.

To retrieve user security settings, go to step 3.To retrieve default system security attributes, go to step 8.To set default security attributes for the system, go to step 14.To change user security settings, go to step 21.

Retrieve User Security Settings



5 Right-click on the Users domain and select Refresh.

Another way to view this same information is to right-click on a particular User Instance domain and select Refresh.

6 Observe security settings.

7 Go to step 49.

Set User and System Security Parameters 4-21


Retrieve Default System Security Attributes



10 Right-click on the Users domain and select Properties>General.

11 Observe values in table.

12 Click Close to close table.

13 Go to step 49.

Set System Default Security Attributes



16 Right-click on the Users domain and select Properties>General.

17 Enter values for Failed Login, Lock Duration, and Idle Timeout in the table.

18 Click Apply.

19 Click Close.

20 Go to step 49.

Change User Security Settings



23 Click on Users node to display all existing user profiles.

24 Right-click appropriate user profile and select Properties>General.

25 Edit values for desired fields (Password, Access Privilege, or Security Privilege) in the table.

26 Click Apply.

27 Click Close.

Set User and System Security Parameters4-22


28 Go to step 49.

Set User and System Security Parameters with TL1

29 Select action.

To retrieve system security settings, go to step 30.To retrieve user security settings, go to step 33.To retrieve default system security attributes, go to step 36.To set default security attributes for the system, go to step 39.To change system security settings, go to step 41.To change user security settings, go to step 43.To suspend a user, go to step 45.To activate suspended user, go to step 47.To end this procedure, go to step 49.

Retrieve System Security Settings

30 Enter RTRV-SECU;

31 Examine output.

32 Go to step 29.

Retrieve User Security Settings

33 Enter RTRV-USER-SECU::[UID];

where:UID=User ID (Omit to retrieve information for all users.)

34 Examine output.

35 Go to step 29.

Retrieve Default System Security Attributes

36 Enter RTRV-DFLT-SECU;

37 Examine output.

38 Go to step 29.



Set System Default Security Attributes

39 Enter SET-ATTR-SECUDFLT:::::[MXINV=][,DURAL=][,TMOUT=];

where:MXINV=maximum number of failed login attempts (0-999) after which the port is locked. (The value 0 disables this option.)DURAL=number of seconds the port remains locked (1-999).TMOUT=number of minutes of idle time after which a session is closed (0-71582788). (The value 0 disables this option.)

40 Go to step 29.

Change System Security Settings

41 Enter ED-SECU:::::,:[PLEN=][,PAGE=][,PCHN=][,PCONV=][,MAXADMIN=][,SUSADMIN=][,SUSPEND=][,SPERIOD=][,DISUSER=][,GREET=];

where:PLEN=minimum password length {1-6} (Default = 6)PAGE=Password age. Maximum number of days a password can remain in effect. Value of 0 disables constraint. {0-999} (Default = 0)PCHN=Password change. Minimum number of minutes a password must remain in effect. Value of 0 disables constraint. {0-999} (Default = 0)PCONV=Password convention. {ANY, NUMERIC, SPECIAL} (Default = ANY)MAXADMIN=Maximum number of security administrators who can be logged in at one time. Value of 0 disables constraint. {0-999} (Default = 0)SUSADMIN=Indicates whether a security administrator can be suspended if no other security administrator account is available. {Y, N} (Default = N)SUSPEND=Number of consecutive failed logins after which that user account is suspended. Value of 0 disables the constraint. {0-999} (Default = 10)SPERIOD=Number of days to suspend a user accounts. {1-999} (Default = 1)DISUSER=Number of consecutive days after which an account will be disabled if the user has not logged on. Value of 0 disables the constraint. {0-999} (Default = 0)GREET=Message to be displayed when a TL1 connection is displayed. {0-255 characters} (Default = NOTICE: This is a private computer system. Unauthorized access may lead to prosecution.)

42 Go to step 29.



Change User Security Settings

43 Enter ED-USER-SECU::UID:::,[PID],,[UAP]:[PAGE=];

where:UID=User IdentifierPID=New PasswordUAP=User access privilege {CONF, NETADMIN, PROV, READ, SEC, TEST} (Default = Previously existing value)PAGE=Password aging interval, in days. Value of 0 disables password aging. {0-999}

44 Go to step 29.

Suspend a User

45 Enter INH-USER-SECU:::::UID:[REACTTIME=];

where:UID=User Identifier of account to be suspendedREACTTIME=Reactivation time in days. (Optional)

46 Go to step 29.

Activate Suspended User

47 Enter ALW-USER-SECU:::::UID;

where:UID=User ID to be activated

48 Go to step 29.




DLP-107Set System Date and TimePURPOSE

This procedure provides the instructions to retrieve and change the system date and time.

GENERAL

The RTRV-HDR command retrieves the system’s output response (site) header. The output response header consists of the site identifier (SID) and the current system date and local time.

The ED-DAT command sets the system date and time. Changing the system date or time could result in partial or incomplete PM data.


STEP PROCEDURE

1 Select action.

To retrieve system date and time with 1677 SONET Link EMA, go to step 2.To change system date and time with 1677 SONET Link EMA, go to step 6.To retrieve system date and time with TL1, go to step 16.To change system date and time with TL1, go to step 16.

Retrieve System Date and Time with 1677 SONET Link EMA

2 Right click on the Network Element domain and select Properties>Date and Time. The Set NE Date and Time window appears.

3 Observe date and time in Set NE Date and Time window.

4 Click Cancel to close Set NE Date and Time window.

5 Go to step 20.

Set System Date and Time 4-27


Change System Date and Time with 1677 SONET Link EMA

6 Right click on the Network Element domain and select Properties>Date and Time. The Set NE Date and Time window appears.

Another way to view this window is to right click on the System domain and select Properties>Date and Time.

7 In Set NE Date and Time window, click in Date field next to month value and use scroll buttons to change value.

8 Click in Date field next to day value and use scroll buttons to change value.

9 Click in Date field next to year value and use scroll buttons to change value.

10 Click in Time field next to hour and use scroll buttons to change value.

11 Click in Time field next to minute and use scroll buttons to change value.

12 Click in Time field next to second and use scroll buttons to change value.

13 Click in Time field next to AM or PM and use scroll buttons to toggle value.

14 Click OK to apply changes and close Set NE Date and Time window.

15 Go to step 20.

Retrieve System Date and Time with TL1

16 Enter RTRV-HDR;

17 Observe output. The response message shows the target identifier, date, and time.

18 Go to step 20.

Change System Date and Time with TL1

19 Enter ED-DAT:::::[DATE],[TIME];

where:DATE=New date value in the format YYYY-MM-DDTIME=New time value in the format HH-MM-SS

At least one of these values must be specified.


Set System Date and Time4-28


DLP-108Administer System Timing/BITSPURPOSE

This procedure provides the instructions to retrieve and edit BITS timing and to switch system clock synchronization from one reference to the other.

GENERAL

The 1677 SONET Link supports several timing inputs (external BITS and optical OC-n line timing). The following recommendations apply for system timing:

• It is recommended to have no more than four consecutive nodes daisy chained via line timing.

• It is recommended to have more than one timing source (BITS or other) per section of nodes.

The RTRV-BITS command retrieves the provisioning of one or more ports dedicated to BITS facilities for clock synchronization purposes.

The ED-BITS command modifies the provisioning of one or more ports dedicated to BITS facilities for clock synchronization purposes.

The RTRV-SYNCN command retrieves system timing information including the primary Timing Card (TC), current timing reference source, the assigned primary and secondary timing references, and the port associated with Line A and Line B optical timing.

The RTRV-SYNCN-SRC command retrieves the status of the External A, External B, Line A, and Line B timing sources.

The SET-SYNCN command sets the primary and secondary timing reference mode and the ports that will be used for the Line A and Line B reference sources. Line A and Line B cannot use the same I/O card as a timing source.

The OPR-SYNCSW command instructs the NE to switch to a different timing reference source.


Administer System Timing/BITS 4-29


STEP PROCEDURE

1 Select action.

To administer system timing with 1677 SONET Link EMA, go to step 2.To administer system timing with TL1, go to step 30.

Administer System Timing with 1677 SONET Link EMA

2 Select action.

To retrieve current BITS timing parameters, go to step 3.To edit BITS timing parameters, go to step 7.To retrieve current synchronization timing parameters, go to step 13.To set synchronization timing parameters, go to step 17.To view timing source status, go to step 23.To change the timing reference to a different source, go to step 27.

Retrieve Current BITS Timing Parameters

3 Right click on the Network Element domain and select Synchronization>BITS. The BITS information window appears.

Another way to view this window is to right click on the System domain and select Synchronization>BITS.

4 Observe BITS properties in the table.

5 Click Close.

6 Go to step 44.

Edit BITS Timing Parameters

7 Right click on the Network Element domain and select Synchronization>BITS. The BITS information window appears.

Another way to view this window is to right click on the System domain and select Synchronization>BITS.

8 Double click on the appropriate parameter value to edit and select new value from the drop-down list.

9 Repeat step 8 to modify other parameter values, if needed.

10 Click Apply.

Administer System Timing/BITS4-30


11 Click Close.

12 Go to step 44.

Retrieve Current Synchronization Timing Parameters

13 Right click on the Network Element domain and select Synchronization>Set Timing Values. The Synchronization Parameters window appears.

Another way to view this window is to right click on the System domain and select Synchronization>Set Timing Values.

14 Observe synchronization parameters in the table.

15 Click Close.

16 Go to step 44.

Set Synchronization Timing Parameters

17 Right click on the Network Element domain and select Synchronization>Set Timing Values. The Synchronization Parameters window appears.

Another way to view this window is to right click on the System domain and select Synchronization>Set Timing Values.

18 Double click on the appropriate parameter value to edit and select new value from the drop-down list.

19 Repeat step 18 to modify other parameter values, if needed.

20 Click Apply.

21 Click Close.

22 Go to step 44.

View Timing Source Status

23 Right click on the Network Element domain and select Synchronization>View Timing Status. The View Timing Status window appears.

Another way to view this window is to right click on the System domain and select Synchronization>View Timing Status.

24 Observe timing source status in the table.

25 Click Close.



26 Go to step 44.

Change Timing Reference to a Different Source

27 Right click on the Network Element domain and select Synchronization>Operate Synchronization. The Operate Synchronization Switch dialog window appears.

Another way to view this window is to right click on the System domain and select Synchronization>Operate Synchronization.

28 Click Yes.

29 Go to step 44.

Administer System Timing with TL1

30 Select action.

To retrieve current BITS timing parameters, go to step 31.To edit BITS timing parameters, go to step 33.To retrieve current synchronization timing parameters, go to step 35.To set synchronization timing parameters, go to step 38.To view timing source status, go to step 40.To change the timing reference to a different source, go to step 43.

Retrieve Current BITS Timing Parameters

31 Enter RTRV-BITS::[AID];

where:AID=Access identifier of an External Timing (IN) port on a TC. If the AID is omitted, the default is to retrieve all timing cards.

32 Go to step 44.

Edit BITS Timing Parameters

33 Enter ED-BITS::AID::::[FMT=][,LINECDE=][,LNLEN=];

where:AID=Timing Card port AIDFMT=T1 (DS1) signal format {D4 or ESF}LINECDE=Type of zero suppression {AMI or B8ZS}LNLEN=Length of the T1 (DS1) line in feet.

34 Go to step 44.



Retrieve Current Synchronization Timing Parameters

35 Enter RTRV-SYNCN;

36 Observe output.

37 Go to step 44.

Set Synchronization Timing Parameters

38 Enter SET-SYNCN::::::[PRIREF=][,SECREF=][,LINEA=][,LINEB=][,AUTOREFSW=];

Parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

39 Go to step 44.

View Timing Source Status

40 Enter RTRV-SYNCN-SRC;

41 Observe output.

42 Go to step 44.

Change Timing Reference to a Different Source

43 Enter OPR-SYNCNSW;




DLP-109Retrieve Log FilePURPOSE

This procedure provides the instructions to retrieve the entries of the audit log, debug log, system log, or security log.

GENERAL

The output format is the quoted name of the log followed by a number of commented lines that contain the text of the original log messages.


STEP PROCEDURE

1 Select action.

To view the audit log, go to step 2.To view the debug log, go to step 4.To view the system log, go to step 6.To view the security log, go to step 8.

View Audit Log

2 Enter RTRV-LOG:::::AUDIT:[START=][,STOP=][,NTFCNCDE=];

where:START=Start timestamp in the format YY-MM-DD-HH-MM-SSSTOP=End timestamp in the format YY-MM-DD-HH-MM-SSNTFCNCDE=Notification code of the messages to retrieve. Default is all codes. {CL, CR, MJ, MN, NA, NR, ALL}

For example, the values START=04-07-08-01-30-00 and STOP=04-07-08-22-45-00 retrieve audit log entries for July 8, 2004 beginning at 1:30 a.m. and ending at 10:45 p.m.

3 Go to step 10.

Retrieve Log File 4-35


View Debug Log

4 Enter RTRV-LOG:::::DEBUG:[START=][,STOP=][,NTFCNCDE=];



5 Go to step 10.

View System Log

6 Enter RTRV-LOG:::::SYSTEM:[START=][,STOP=][,NTFCNCDE=];



7 Go to step 10.

View Security Log

8 Enter RTRV-AUDIT-SECULOG:::::[START=][,STOP=][,NTFCNCDE=];


9 Go to step 10.


Retrieve Log File4-36


DLP-110Enter Trusted Host for Dynamic IP AddressPURPOSE

This procedure provides instructions to create a single entry in the trusted hosts table allowing any workstation access to the 1677 SONET Link.

GENERAL

Each 1677 SONET Link maintains a table of IP addresses of trusted hosts. A trusted host is allowed to connect to the TL1 agent on this NE. The 1677 SONET Link will deny access to any host whose IP address is not included in the trusted hosts list.

Each 1677 SONET Link also maintains a table of IP addresses of denied hosts. A denied host is not allowed to connect to TL1 agent on this node. An entry in the denied hosts list overrides any access granted through trusted hosts list.

A host is automatically added to the denied hosts list when it exceeds login failure threshold, and remains on the list for the specified suspension period (defined through ED-SECU). This procedure allows for manually adding a host to the denied hosts list, permanently suspending that host access until it is manually removed from the denied hosts list. The denied hosts list indicates whether the host is denied access until a specified date/time or permanently.

Depending on the configuration of the Dynamic Host Configuration Protocol (DHCP) server, this procedure may impact network security by allowing any workstation assigned addresses by the DHCP server to connect to the NE. For additional security, it is advisable to configure the DHCP server to issue a restricted range of addresses to hosts intended to control the 1677 SONET Link and then use the ENT-NE-TRUST command to enter the that restricted address range.


STEP PROCEDURE

1 Contact the IT department to determine the range of IP addresses available for issue by the DHCP server.

2 Enter RTRV-NE-TRUST;

3 Observe output.

Enter Trusted Host for Dynamic IP Address 4-37


4 Enter ENT-NE-TRUST:::::NETHOST,MASK;

where:NETHOST=IP address supplied by IT department (In the form x.y.z.0 if all addresses in range are to be used)MASK=Subnet mask supplied by IT department (In the form x.y.z.0 if all addresses in range are to be used)

For example: If all addresses in the range 192.168.1.1 to 192.168.3.254 are going to be used to manage the 1677 SONET Link, the commands would look like this:

ENT-NE-TRUST:::::192.168.1.0,255.255.255.0;ENT-NE-TRUST:::::192.168.2.0,255.255.255.0;ENT-NE-TRUST:::::192.168.3.0,255.255.255.0;

5 Repeat step 4 for all IP addresses in the DHCP address range.

6 To allow open access enter ENT-NE-TRUST:::::0.0.0.1,0.0.0.0;

7 Enter RTRV-NE-TRUST;

8 Observe output.


Enter Trusted Host for Dynamic IP Address4-38


DLP-111Display AlarmsPURPOSE

This procedure provides the instructions to view the status of current alarms.

GENERAL



Refer to the 1677 SONET Link Maintenance and Trouble Clearing manual (PN 3EM13853AD) for procedures to clear alarms.

Refer to the 1677 SONET Link Installation Practices manual (PN 3EM13849AD) for ESD precaution procedures.

STEP PROCEDURE

1 Select action.

To display alarms with 1677 SONET Link EMA, go to step 2.To display alarms with TL1, go to step 15.

Display Alarms with 1677 SONET Link EMA

2 Select action.

To retrieve all current NE alarms, go to step 3.To retrieve common alarms, go to step 5.To retrieve equipment alarms, go to step 8.To retrieve facility alarms, go to step 11.

Retrieve All NE Alarms

3 Click on the NE node and select Navigation>Show Alarms from the menu bar. The Alarm Surveillance window appears.

4 Go to step 24.

Display Alarms 4-39


Retrieve Common Alarms

5 Select the System node to display contents in the Result Pane.

6 Click on appropriate common entity (CHASSIS or TC-SYNC) and select Navigation>Show Alarms from the menu bar. The Alarm Surveillance window appears.

7 Go to step 24.

Retrieve Equipment Alarms

8 Select the Equipment domain in the Scope Pane.

9 Click on appropriate equipment and select Navigation>Show Alarms from the menu bar. The Alarm Surveillance window appears.

10 Go to step 24.

Retrieve Facility Alarms

11 Expand the Facilities domain in the Scope Pane.

12 Expand the appropriate domains and groups until appropriate facility is displayed.

13 Click on facility and select Navigation>Show Alarms from the menu bar. The Alarm Surveillance window appears.

14 Go to step 24.

Display Alarms with TL1

15 Select action.

To retrieve all current NE alarms, go to step 16.To retrieve common alarms, go to step 18.To retrieve equipment alarms, go to step 20.To retrieve facility alarms, go to step 22.

Retrieve All Current NE Alarms

16 Enter RTRV-ALM-ALL;

17 Go to step 24.

Display Alarms4-40


Retrieve Common Alarms

18 Enter RTRV-ALM-COM::[AID]:::[NTFCNCDE],[CONDTYPE],[SRVEFF],,,;

where:AID=ALL, CHASSIS, or TC-SYNCNTFCNCDE=Notification code of the alarms to be retrieved. Default is all codes. {CL, CR, MJ, MN, NA, NR, ALL}CONDTYPE=Condition type. Refer to the Commands and Messages manual (PN 3EM13852AD) for a list of all condition types.SRVEFF=Effect on service type. {NSA, SA}

19 Go to step 24.

Retrieve Equipment Alarms

20 Enter RTRV-ALM-EQPT::[AID];

where:AID=Equipment entity Access Identifier. (Omit to retrieve all equipment alarms.)

21 Go to step 24.

Retrieve Facility Alarms

22 Enter RTRV-ALM-x::AID;

where:x=Facility type (EC1, GIGE, OC3, OC12, OC48, OC192, OFA, STS1, STS3C, STS12C, STS48C, T1, T3, or VT1)AID=Facility Access Identifier

23 Go to step 24.


Display Alarms 4-41


Display Alarms4-42


DLP-112Provision EquipmentPURPOSE

This procedure provides the instructions to provision system cards.

GENERAL

ENT-EQPT assigns an equipment object entity at the AID physical location and provisions the specified equipment, regardless of whether the equipment is installed in the system.The following equipment can be provisioned into the system:

• DS3 card

• ECC

• EDFA card

• GIGE card

• OC3 card

• OC12 card

• OC48 card

• OC192 card

• TMUX card

• VSC

Common equipment entities (e.g. CCC, SSC, TC) are automatically created/provisioned with the system and can not be entered or deleted using commands.

Once equipment is provisioned, ED-EQPT can be used to alter parameters.

Provision Equipment 4-43


Refer to table 112-B for slot locations of I/O card. See figure 112-1 for I/O card location in shelf.

DS3 and ECC working modules can be mixed within the same protection group if the protection module is an ECC. An ECC/DS3 card protection group is defined when the corresponding protection slot is provisioned. Refer to table 112-C. The ECC module can operate in an unprotected mode. If the protection module is a DS3 module, all working modules in the protection group must be DS3. There is no restriction on the provisioning order.

Table 112-A. Card Type Parameter ValuesModule Card Type Parameter12-port DS3 module DS3-12P12-port DS3/EC1 module ECC-12PErbium-doped Fiber Amplifier module EDFA2-port Gigabit Ethernet module GIGE-2P12-port OC3 module OC3-12P4-port OC12 module OC12-4P1-port OC48 module OC48-1P1-port OC192 module OC192-1PTMUX module TMUXVSC module VTSC

Table 112-B. Valid Slot Locations for I/O CardsI/O Card Slot LocationsDS3, ECC {1-5,13-17}-{A,B}EDFA {1,3,5,12,14,16}-{A,B}GIGE {1-6,12-17}-{A,B}OC3, OC12, OC48 {1-6,12-17}-{A,B}OC192 {5,6,12,13}-{AB}TMUX, VSC {1-6,12-17}-{A,B}

Table 112-C. Slot Definitions for ECC and DS3 Card Protection GroupsProtection Slot Working Slot1A 2A, 3A, 4A, 5A1B 2B, 3B, 4B, 5B17A 16A, 15A, 14A, 13A17B 16B, 15B, 14B, 13B

Provision Equipment4-44






Figure 112-1. Shelf Card Locations

677-0247-1041305

IOC

1B 2B 3B 4B 5B 6B

SS

C7

SS

C8

CC

C9

CC

C10

TC

11B

12B

13B

14B

15B

16B

17B

17A

16A

15A

14A

13A

12A

TC

11A

6A5A4A3A2A1A

IOC

IOC

IOC

IOC

IOC

IOC

IOC

IOC

IOC

IOC

IOC

IOC

IOC

IOC

IOC

IOC

IOC

IOC

IOC

IOC

IOC

IOC

IOC



STEP PROCEDURE

1 Select action.

To provision equipment with 1677 SONET Link EMA, go to step 2.To provision equipment with TL1, go to step 13.

Provision Equipment with 1677 SONET Link EMA

2 Right-click the Equipment domain in the Navigation Tree.

3 Select Create Board. The Enter Equipment wizard appears.

4 Click Next to begin.

5 On the Card page of the wizard, select appropriate slot and board from the drop-down list of available boards.

6 Click Next.

7 On the Equipment Type page, select appropriate card type from the drop-down list. Refer to table 112-A.

8 Click Next.

9 Select appropriate parameter values on each remaining page in the wizard.

10 On the Finish page, verify chosen options.

11 Click Finish.

12 Go to step 27.

Provision Equipment with TL1

13 Select action.

To provision a DS3 card, go to step 14.To provision an ECC, go to step 16.To provision an EDFA card, go to step 18.To provision a GIGE card, go to step 20.To provision an OC-n card, go to step 22.To provision a TMUX card, go to step 24.To provision a VSC, go to step 26.



Provision DS3 Card

14 Enter ENT-EQPT::AID:::DS3-12P:[RVRTTIM=]:[PST];;

where:AID=IOC-{1-5, 13-17}-{A,B}Other parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

15 Go to step 27.

Provision ECC Card

16 Enter ENT-EQPT::AID:::ECC-12P:[RVRTTIM=]:[PST];


17 Go to step 27.

Provision EDFA Card

18 Enter ENT-EQPT::AID:::EDFA:[RVRTTIM=]:[PST];

where:AID=IOC-{1,3,5,12,14,16}-{A,B}Other parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

19 Go to step 27.

Provision Gigabit Ethernet Card

20 Enter ENT-EQPT::AID:::GIGE-2P:[RVRTTIM=]:[PST];


21 Go to step 27.



Provision OC-n Card

22 Enter ENT-EQPT::AID:::TYPE:[RVRTTIM=]:[PST];

where:AID={IOC-{1-6,12-17}-{A,B}} (for OC-3, OC-12, and OC-48 cards),{IOC-{5,6,12,13}-{AB}} (for OC-192 card)TYPE={OC3-12P, OC12-4P, OC48-1P, OC192-1P}Other parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

23 Go to step 27.

Provision Transmux Card

24 Enter ENT-EQPT::AID::TMUX:[RVRTTIM=]:[PST];


25 Go to step 27.

Provision VSC

26 Enter ENT-EQPT::AID::VTSC:[RVRTTIM=]:[PST];





DLP-113Deprovision EquipmentPURPOSE

This procedure provides the instructions to deprovision system cards.

PREREQUISITES

This procedure is service-affecting if any cross-connections are active on the card. All cross-connections must be deleted. Once cross-connections are deleted, ports associated with the card must be deprovisioned. Refer to table 113-A for appropriate procedures.

Supported entities (provisioned facilities and/or cards) must be deprovisioned before other cards can be deprovisioned.

Table 113-A. Procedures Required Before Deprovisioning CardsCARD PORT TYPE DELETE

CROSS-CONNECTIONSDEPROVISION PORTS

DS3, ECC, OC3, OC12, OC48, OC192 DS1 DLP-177 (DS1-DS1 or DS1-VT1)

DLP-161

DS3, ECC, OC3, OC12, OC48, OC192 DS3 DLP-124 (T3-T3 or T3-STS1)

DLP-120

ECC EC1 N/A DLP-158GIGE EVC DLP-164 DLP-172GIGE GIGE DLP-164 DLP-155OC3 OC-3 N/A DLP-121OC12 OC-12 N/A DLP-121OC48 OC-48 N/A DLP-121OC192 OC-192 N/A DLP-121EDFA OFA N/A DLP-183ECC, OC3, OC12, OC48, OC192 STS-1 DLP-125 DLP-122OC3, OC12, OC48, OC192 STS-3c DLP-125 DLP-122OC12, OC48, OC192 STS-12c DLP-125 DLP-122OC48, OC192 STS-48c DLP-125 DLP-122ECC, OC3, OC12, OC48, OC192 VT1 DLP-126 DLP-123

Deprovision Equipment 4-49


GENERAL

The DLT-EQPT command de-assigns and deprovisions the equipment entity specified by the Access Identifier (AID), even if equipment is not installed into the system. The following equipment can be deleted from the system:

• DS3 card

• ECC

• EDFA card

• GIGE card

• OC3 card

• OC12 card

• OC48 card

• OC192 card

• TMUX card

• VSC

I/O equipment can only be deleted if all supported facilities are deprovisioned first. This applies to DS3, ECC, EDFA, GIGE, OC3, OC12, OC48, and OC192 modules.

The protection module of a DS3, ECC, TMUX, or VSC equipment protection group can only be deleted if that module has a lock out in effect (due to INH-SWTOPROTN-EQPT command).

The TMUX or VSC module in a working slot can only be deleted if no facility is provisioned to use that module.

Upon successful completion of DLT-EQPT, all condition types associated with the specified equipment entity are cleared.

After the DLT-EQPT command has executed, the system removes all provisioning data associated with the specified equipment. The ENT-EQPT command needs to be executed in order to re-provision a deleted equipment entity.



Deprovision Equipment4-50





STEP PROCEDURE

1 Select action.

To deprovision cards with 1677 SONET Link EMA, go to step 2.To deprovision cards with TL1, go to step 33.

Deprovision Cards with 1677 SONET Link EMA

2 Select action.

To deprovision a DS3 card, go to step 3.To deprovision an ECC, go to step 3.To deprovision an EDFA card, go to step 14.To deprovision a GIGE card, go to step 14.To deprovision an OC-n card, go to step 14.To deprovision a TMUX card, go to step 22.To deprovision a VSC, go to step 22.

Deprovision DS3 and ECC Cards

3 Click the Equipment domain in the Scope Pane.

4 Is card to be deleted located in protection slot?


5 Right-click card to be deleted and select Switch>Inhibit Switch to Protection.

6 Click Yes.

7 Examine provisioning information on appropriate card.

8 Does facility have Primary State (and Secondary State) of IS, OOS-MA, OOS-AUMA, or OOS-MA,UAS??

If IS, go to step 9.If OOS-MA or OOS-AUMA, go to step 11.If OOS-MA,UAS, card is already deprovisioned. Go to step 55.




10 Click Yes.

11 Right-click on appropriate card and select Unassign.

12 Click Yes.

13 Go to step 55.

Deprovision EDFA, GIGE, and OC-n Cards






18 Click Yes.


20 Click Yes.

21 Go to step 55.

Deprovision TMUX and VSC Cards




24 Right-click card to be deleted and select Switch>Inhibit Switch to Protection.

25 Click Yes.







29 Click Yes.


31 Click Yes.

32 Go to step 55.

Deprovision Cards with TL1

33 Select action.

To deprovision a DS3 card, go to step 34.To deprovision an ECC, go to step 34.To deprovision an EDFA card, go to step 42.To deprovision a GIGE card, go to step 42.To deprovision an OC-n card, go to step 42.To deprovision a TMUX card, go to step 48.To deprovision a VSC, go to step 48.

Deprovision DS3 and ECC Cards



35 Enter INH-SWTOPROTN-EQPT::AID;

where:AID=Access Identifier of card to be deleted


where:AID=Access Identifier of specified equipment

37 Observe output.



38 Is PST (and SST) IS, OOS-MA, OOS-AUMA, or OOS-MA,UAS?




40 Enter DLT-EQPT::AID;


41 Go to step 55.

Deprovision EDFA, GIGE, and OC-n Cards



43 Observe output.







47 Go to step 55.



Deprovision TMUX and VSC Cards




where:AID=Access Identifier of card to be deleted


where:AID=Access Identifier specified equipment

51 Observe output.










DLP-114Provision EC1 FacilityPURPOSE

This procedure provides the instructions to provision an EC1 facility.

PREREQUISITES

An ECC module must be provisioned before EC1 facilities can be provisioned. Refer to DLP-112 to provision ECC modules.

GENERAL


STEP PROCEDURE

1 Select action.

To provision an EC1 facility with 1677 SONET Link EMA, go to step 2.To provision an EC1 facility with TL1, go to step 10.

Provision EC1 Facility with 1677 SONET Link EMA


3 Expand the EC1 domain.

4 Right-click on the appropriate EC1 group and select Create. The Provision EC1 wizard appears.




8 Click Finish.

9 Go to step 14.

Provision EC1 Facility 4-57


Provision EC1 Facility with TL1

10 Enter RTRV-EC1::AID;

where:AID=EC1 Access Identifier

11 Examine output for provisioning information on port. Ensure that port is in valid state for provisioning (OOS-MA,UAS).

12 Does port have PST and SST of OOS-MA,UAS?

If yes, go to step 13.If no, the ENT-EC1 command cannot be performed on the specified EC1 port. Go to step 14.

13 Enter ENT-EC1::AID::::[CKTID=][,TRC=][,LBO=]:[PST][,SST];

where:AID=EC1 Access IdentifierOther parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.


Provision EC1 Facility4-58


DLP-115Provision DS3 (T3) FacilityPURPOSE

This procedure provides the instructions to provision a DS3 facility. The DS3 facility can be associated with a DS3 port, or with an STS-1 facility of an optical port.

PREREQUISITES

When provisioning a DS3 facility for a DS3 card, the DS3 card must be provisioned first. Refer to DLP-112 to provision DS3 cards.

GENERAL

To provision a T3 test access port pair, the STSMAP of the T3 ports must be ASYNC and FMT must be UNFR. The provisioning parameters are applied to both AID and TADA.

To support T3 facilities on STS-1 facilities, the STS-1 STSMAP value must be set to:

• ASYNC&SUBPM

• ASYNC&VTFLOAT

• ASYNC&VTFLOAT&VTCRS

Once a DS3 facility is provisioned, ED-T3 can be used to alter parameters. RTRV-T3 can be used to view the parameters.

Creating an embedded DS3 facility within an STS-1 requires a Transmux resource. If the STS-1 does not have one reserved and is passing traffic, adding the Transmux will interrupt traffic.

Refer to table 115-A for valid provisioning combinations.

Provision DS3 (T3) Facility 4-59


Refer to table 115-B for description of STSMAP values.

Refer to figure 115-1 to aid in provisioning a stand-alone T3. Refer to figure 115-2 to aid in provisioning a T3 embedded in an STS-1.

Table 115-A. Valid T3 Provisioning CombinationsAID FMT STSMAP FEAC LBOStandalone T3 on ECC module

UNFR ASYNC N 1,2CBIT ASYNC, ASYNC&SUBPM,

VTFLOAT,VTFLOAT&VTCRSY,N 1,2

ASYNC ASYNC, ASYNC&SUBPM, VTFLOAT,VTFLOAT&VTCRS

N 1,2

Standalone T3 on DS3 card


VTFLOAT,VTFLOAT&VTCRSN 1,2


N 1,2

T3 embedded in STS1 CBIT,ASYNC ASYNC&SUBPM, VTFLOAT,VTFLOAT&VTCRS

N NA

Table 115-B. STSMAP ValuesSTSMAP DESCRIPTIONASYNC Indicates DS3 will be processed on module.ASYNC&SUBPM Pre-allocates TMUX resources for T3 and/or T1 PM. T3 and T1 facilities must

be created to establish signal formats. The DS3 port can be cross-connected to another STS-1 ASYNC port or another ASYNC DS3 port.

VTFLOAT Pre-allocates TMUX resources for T1/VT1 PM. However, VT signals can not be individually cross-connected. The DS3 port can only be cross-connected to VT mapped STS-1s.

VTFLOAT&VTCRS Pre-allocates TMUX and VSC module resources for VT to T1 cross-connections.

Provision DS3 (T3) Facility4-60


Figure 115-1. DS3 Provisioning

Figure 115-2. STS-1 Provisioning

DS3 Port ENT-T3

ENT-T1

677-0227-1031005

DS3 Module (DS3-12P) orDS3/EC1 Module (ECC-12P)

T1

ENT-EQPT

ENT-CRS-T1

Cross-connectto other T1sor to VT1s

STS-1

ALL ASYNCASYNC

&SUBPM1ASYNC&

VTFLOAT1

ASYNC

&VTFLOAT

&VTCRS2VTFLOAT

VTFLOAT

&SUBPM1VTFLOAT

&VTCRS3

VTFLOAT

&VTCRS

&SUBPM2

ENT-STS1

(STSMAP=)

ENT-T3

(STSMAP=)

ENT-VT1

(VTMAP=)

ENT-T1T1T1 T1T1T1 T1

T3 T3 T3

T1

T3

VT1 VT1VT1

1 TMUX card required

2 TMUX and VSC cards required

3 VSC card required

677-0385

033106




STEP PROCEDURE

1 Select action.

To provision DS3 facility with 1677 SONET Link EMA, go to step 2.To provision DS3 facility with TL1, go to step 35.

Provision DS3 Facility with 1677 SONET Link EMA


3 Select action.

If T3 is stand-alone, go to step 4.If T3 is embedded in an OC-n, go to step 11.If T3 is embedded in an EC1, go to step 23.

Provision Stand-Alone T3

4 Expand the T3 domain.

5 Right-click on appropriate T3 group and select Create. The Provision T3 wizard appears.




9 Click Finish.

10 Go to step 39.

Provision T3 Embedded in an OC-n

11 Expand the appropriate OC-n domain.

12 Expand the appropriate OC-n group.

13 Expand the appropriate OC-n facility.



14 Select the appropriate STS-1 facility (timeslot) to display available T3 facility.

15 Examine provisioning information on appropriate T3 facility.

16 Does facility have Primary State and Secondary State of OOS-MA,UAS or OOS-AUMA,UAS?

If yes, go to step 17.If no, the specified T3 facility cannot be provisioned. Go to step 39.

17 Right-click on appropriate T3 facility and select Assign. The Provision STS1 T3 Facility wizard appears.




21 Click Finish.

22 Go to step 39.

Provision T3 Embedded in an EC1


24 Expand the appropriate EC1 group.

25 Expand the appropriate EC1 facility.

26 Select the STS-1 facility (timeslot) to display available T3 facility.


28 Does facility have Primary State and Secondary State of OOS-MA,UAS or OOS-AUMA,UAS?


29 Right-click on appropriate T3 facility and select Assign. The Provision STS1 T3 Facility wizard appears.






33 Click Finish.

34 Go to step 39.

Provision DS3 Facility with TL1

35 Enter RTRV-T3::AID;

where:AID=T3 Access Identifier



If yes, go to step 38.If no, the ENT-T3 command cannot be performed on the specified T3 port. Go to step 39.

38 Enter ENT-T3::AID::::[CKTID=][,LBO=][,FMT=][,STSMAP=][,VTCARD=][,TMUX=][,TACC=][,TADB=][,FEAC=]:[PST],[SST];

where:AID= T3 Access IdentifierOther parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.




DLP-116Provision OC-n FacilityPURPOSE

This procedure provides the instructions to provision an OC-3, OC-12, OC-48, or OC-192 facility to receive and transmit data.

PREREQUISITES

An OC-n card must be provisioned before OC-n facilities can be provisioned. Refer to DLP-112 to provision OC-n cards.

GENERAL

Once an OC-n facility is provisioned, ED-OCn can be used to alter parameters. RTRV-OCn can be used to view the parameters.

Refer to figures 116-1 through 116-4 to aid in provisioning OC-n facilities.

Figure 116-1. OC-3 Provisioning

OC3 (Working Port)

ENT-OC3

(STSMAP=)

ENT-T3

(STSMAP=)

ENT-VT1

(VTMAP=)

ENT-T1

677-0231-1062303

OC3 Module (OC3-12P)

STS-3c STS-1

OC3(Protect Port)

ENT-EQPT

ENT-FFP-OC3

ENT-STSn

ENT-CRS-STSn

ALL

T3

VT1

T1 T1

* See STS-1 provisioning fordetailed information aboutSTSMAP parameter values.

* See notebelow.

Cross-connectto other STSns

Provision OC-n Facility 4-65



OC12 (Working Port)

ENT-OC12

(STSMAP=)

ENT-T3

(STSMAP=)

ENT-VT1

(VTMAP=)

ENT-T1

677-0229-1062303


STS-12c STS-3c STS-1

OC12(Protect Port)

ENT-EQPT

ENT-FFP-OC12

ENT-STSn

ENT-CRS-STSn

ALL

T3

VT1

T1 T1


* See notebelow.

Cross-connect toother STSns

Provision OC-n Facility4-66



OC48 (Working Port)

ENT-OC48

(STSMAP=)

ENT-T3

(STSMAP=)

ENT-VT1

(VTMAP=)

ENT-T1

677-0232-1062303


STS-48c STS-12c STS-3c STS-1

OC48(Protect Port)

ENT-EQPT

ENT-FFP-OC48

ENT-STSn

Cross-connect to other STSns

ENT-CRS-STSn

ALL

T3

VT1

T1 T1


* See notebelow.




STEP PROCEDURE

1 Select action.

To provision OC-n facility with 1677 SONET Link EMA, go to step 2.To provision OC-n facility with TL1, go to step 10.

Provision OC-n Facility with 1677 SONET Link EMA




OC192 (Working Port)

ENT-OC192

(STSMAP=)

ENT-T3

(STSMAP=)

ENT-VT1

(VTMAP=)

ENT-T1

677-0230-1080204


STS-48c STS-12c STS-3c STS-1

OC192(Protect Port)

ENT-EQPT

ENT-FFP-OC192

ENT-STSn

Cross-connect to other STSns

ENT-CRS-STSn

ALL

T3

VT1

T1 T1


* See notebelow.



4 Right-click on the appropriate OC-n group and select Create. The Provision OC-n wizard appears.




8 Click Finish.

9 Go to step 21.

Provision OC-n Facility with TL1

10 Enter RTRV-OCn::AID;

where:OCn=Type of optical facility (OC3, OC12, OC48, OC192).AID=OCn Access Identifier



If yes, go to step 13.If no, the ENT-OCn command cannot be performed on the specified OCn port. Go to step 21.

13 Select action.

To provision OC-3 facility, go to step 14.To provision OC-12 facility, go to step 16.To provision OC-48 facility, go to step 18.To provision OC-192 facility, go to step 20.

14 Enter ENT-OC3::AID::::[CKTID=][,SDTHRESH=][,SFTHRESH=][,TRC=][,ALSENB=]:[PST][,SST];

where:AID=OC-3 AIDOther parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

15 Go to step 21.



16 Enter ENT-OC12::AID::::[CKTID=][,SDTHRESH=][,SFTHRESH=][,TRC=][,ALSENB=]:[PST][,SST];


17 Go to step 21.

18 Enter ENT-OC48::AID::::[CKTID=][,SDTHRESH=][,SFTHRESH=][,TRC=][,ALSENB=][,OPRNOM=][,TXPWR=]:[PST][,SST];


19 Go to step 21.

20 Enter ENT-OC192::AID::::[CKTID=][,SDTHRESH=][,SFTHRESH=][,TRC=][,FECDW=][,FECSCRAMBLE=][,ALSENB=][,OPRNOM=][,TXPWR=]:[PST][,SST];





DLP-117Provision STS-n FacilityPURPOSE

This procedure provides the instructions to provision a port to receive and transmit STS-1 and STS concatenated signals.

PREREQUISITES

An STS-3c, STS-12c, or STS-48c signal must be embedded within an OC-n facility. The OC-n facility must be provisioned first. Refer to DLP-116 to provision an OC-n facility. An STS-1 signal must be embedded within an OC-n or EC1 facility. Refer to DLP-114 to provision an EC1 facility.

GENERAL

The ENT-STSn command is used to provision STS-1, STS-3c, STS-12c, and STS-48c facilities. RTRV-STSn can be used to view the parameters.

An STS-n can be provisioned on the following:

• EC1 facility (STS-1 only)

• an unprotected OCn facility

• working OCn facility of a UPSR protected FFP group

• working OCn facility of a LINEAR protected FFP group

• east/west OCn facility of a BLSR protected FFP group

When an STS-n is provisioned on the working OCn facility of a UPSR protected FFP group, an STS-n is automatically created on the protecting OCn facility of a UPSR protected FFP group.

The STSMAP parameter indicates the type of payload in the STS payload envelope. Refer to table 117-A. In addition, it includes two flags that allocate the necessary TMUX/VSC resources to support subrate performance monitoring and cross-connection functions. The following subrate flags are supported:

• SUBPM: This flag indicates that this facility will be supporting embedded T1, VT1, and/or T3 performance monitoring. TMUX resources will be allocated. The user must provision the T1, VT1, T3 facility for performance monitoring to be enabled.

• VTCRS: This flag indicates that this facility will be used to cross-connect an embedded VT1 with a T1 facility. VSC resources will be allocated. Note that VT level connections can only be made to STS1s using the same VSC module.

Provision STS-n Facility 4-71


To edit the VTCARD or TMUX parameters after an STS-1 has been provisioned, use the DLT-STS1 command to delete the STS-1 facility and then use the ENT-STS1 command to re-enter the facility with the new VTCARD and TMUX parameters.

See figure 117-1 for STS-1 provisioning information. See figures 116-1 through 116-4 in DLP-116 for STS-n provisioning information.

Table 117-A. STSMAP Parameter Values for STS-1 ProvisioningSTSMAP Possible Sub-entity TMUX/VSC ResourcesALL None NoneASYNC None NoneASYNC&SUBPM T3, T1 TMUXASYNC&VTFLOAT T3, T1 TMUXASYNC&VTFLOAT&VTCRS T3, T1 TMUX/VSCVTFLOAT None VSCVTFLOAT&SUBPM VT1, T1 TMUXVTFLOAT&VTCRS VT1 VSCVTFLOAT&VTCRS&SUBPM VT1, T1 VSC/TMUX

Provision STS-n Facility4-72



STEP PROCEDURE

1 Select action.

To provision STS-n facility with 1677 SONET Link EMA, go to step 2.To provision STS-n facility with TL1, go to step 21.

Provision STS-n Facility with 1677 SONET Link EMA

2 Select action.

To provision STS-n embedded in an OC-n, go to step 3.To provision STS-1 embedded in an EC1, go to step 8.

Figure 117-1. STS-1 Provisioning

STS-1

ALL ASYNCASYNC

&SUBPM1ASYNC&

VTFLOAT1

ASYNC

&VTFLOAT

&VTCRS2VTFLOAT

VTFLOAT

&SUBPM1VTFLOAT

&VTCRS3

VTFLOAT

&VTCRS

&SUBPM2

ENT-STS1

(STSMAP=)

ENT-T3

(STSMAP=)

ENT-VT1

(VTMAP=)

ENT-T1T1T1 T1T1T1 T1

T3 T3 T3

T1

T3

VT1 VT1VT1

1 TMUX card required

2 TMUX and VSC cards required

3 VSC card required

677-0385

033106



Provision STS-n Embedded in an OC-n




6 Select the appropriate OC-n port to display available timeslots.

7 Go to step 13.

Provision STS-1 Embedded in an EC1




11 Select the appropriate EC1 facility to display available STS-1 facilities.

12 Go to step 13.

Enter STS-n Provisioning Information Using Wizard

13 Examine provisioning information on appropriate timeslot.

14 Is timeslot empty (no information shown)?

If yes, go to step 15.If no, the specified timeslot cannot be provisioned. Go to step 31.

15 Right-click on the appropriate timeslot and select Assign. The Provision STSx wizard appears.




19 Click Finish.

20 Go to step 31.



Provision STS-n Facility with TL1

21 Select action.

To provision an STS-1 facility, go to step 22.To provision an STS-n facility, go to step 27.

Provision STS-1 Facility

22 Enter RTRV-STS1::AID;

where:AID=STS-1 Access Identifier



If yes, go to step 25.If no, the ENT-STS1 command cannot be performed on the specified STS1 port. Go to step 31.

25 Enter ENT-STS1::AID::::[CKTID=][,STSMAP=][,VTCARD=][,TMUX=][,TRC=][,EXPTRC=][,ENBTXPDIP=][,ENBTXRDIP=][,ENBTIMP=][,ENBPDIP=][,TACC=][,TADB=][,SDTH=][,SFTH=]:[PST],[SST];

where:AID=STS-1 Access IdentifierOther parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

26 Go to step 31.

Provision STS-n Facility

27 Enter RTRV-STSn::AID;

where:STSn=Signal type (STS3C, STS12C, or STS48C).AID=STSn Access Identifier





If yes, go to step 30.If no, the ENT-STSn command cannot be performed on the specified STSn port. Go to step 31.

30 Enter ENT-STSn::AID::::[CKTID=][,STSMAP=][,EXPTRC=][,ENBTIMP=][,TACC=][,TADB=][,SDTH=][,SFTH=]:[PST],[SST];

where:STSn=Signal type (STS3C, STS12C, or STS48C).AID=STSn Access IdentifierOther parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.




DLP-118Provision VT1.5 FacilityPURPOSE

This procedure provides the instructions to provision a facility to receive and transmit VT1.5.

PREREQUISITES

A VT1.5 must be embedded within a parent STS-1. The parent signal must be provisioned first. Refer to DLP-117 to provision an STS-1.

GENERAL

The ENT-VT1 command is used to provision VT1 facilities. Once a VT1.5 facility is provisioned, ED-VT1 can be used to alter parameters. RTRV-VT1 can be used to view the parameters. See figure 118-1 for provisioning information for a VT1 in an OC-n.

To provision a VT1.5 test access port pair, the STSMAP of the STS-1 in which the test access port pair is embedded must have been provisioned as VTFLOAT&VTCRS. If a test access port pair is provisioned on a OC-N port, the OC-N port must be unprotected.

To support VT1.5 facilities, the STS-1 STSMAP value must be set to:

• VTFLOAT&SUBPM&VTCRS

• VTFLOAT&VTCRS

• VTFLOAT&SUBPM

Provision VT1.5 Facility 4-77



STEP PROCEDURE

1 Select action.

To provision VT1.5 facility with 1677 SONET Link EMA, go to step 2.To provision VT1.5 facility with TL1, go to step 23.

Provision VT1 Facility with 1677 SONET Link EMA

2 Select action.

To provision VT1.5 embedded in an OC-n, go to step 3.To provision VT1.5 embedded in an EC1, go to step 9.

Figure 118-1. VT1 Provisioning in an OC-n

OCn (Working Port)

ENT-OCn

(STSMAP=)

ENT-VT1

(VTMAP=)

ENT-T1

677-0234-1062303

OCn Module

STS-1

OCn(Protect Port)

ENT-EQPT

ENT-FFP-OCn

ENT-STS1

ENT-CRS-VT1

T1


Cross-connectto other VT1s

VT1

* See note below.

ASYNCVT1ALL

Provision VT1.5 Facility4-78


Provision VT1 Embedded in an OC-n





7 Select the appropriate STS-1 facility to display available VT1 facilities.

8 Go to step .

Provision VT1 Embedded in an EC1





13 Select the appropriate STS-1 facility to display available VT1 facilities.

14 Go to step .

Enter VT1 Provisioning Information Using Wizard

15 Examine provisioning information on appropriate VT1 facility.

16 Does facility have Primary State and Secondary State of OOS-MA,UAS?

If yes, go to step 17.If no, the specified VT1 facility cannot be provisioned. Go to step 27.

17 Right-click on VT1 facility and select Assign. The Provision VT1 wizard appears.




21 Click Finish.

Provision VT1.5 Facility 4-79


22 Go to step 27.

Provision VT1 Facility with TL1

23 Enter RTRV-VT1::AID;

where:AID=VT1 Access Identifier



If yes, go to step 26.If no, the ENT-VT1 command cannot be performed on the specified VT1 port. Go to step 27.

26 Enter ENT-VT1::AID::::[CKTID=][,TACC=][,TADB=][,VTMAP=]:[PST],[SST];

where:AID=VT1 Access IdentifierOther parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.


Provision VT1.5 Facility4-80


DLP-119Administer OC-n Facility Protection GroupPURPOSE

This procedure provides the instructions to retrieve information on, provision, and deprovision OC-n facility protection groups.

PREREQUISITE

The working and protection OC-n facilities in facility protection groups must be provisioned. Refer to DLP-116. STS-n connections in a UPSR configuration must be deleted before the OC-n protection group can be deleted. Refer to DLP-125.

GENERAL

An OC-n facility protection group consists of a pair of adjacent OC-n facilities: one protect facility and one working facility.

After OC-n facility protection groups are provisioned, OC-n protect facility AIDs can be specified when executing RTRV-OCn and all OC-n Performance Monitoring (PM) commands.

After an OC-n facility protection group is provisioned, ED-FFP-OCn can be used to alter parameters.

OC-192 UPSR Drop and Continue is not supported in slots 6AB/12AB.

OC-192 BLSR is not supported in slots 6AB/12AB. Ring ports must be configured on an adjacent pair of cards (5AB/6AB or 12AB/13AB).

See figure 119-1 for an example of provisioning an OC-3 for FFP.

Administer OC-n Facility Protection Group 4-81



STEP PROCEDURE

1 Select action.

To administer OC-n facility protection group with 1677 SONET Link EMA, go to step 2.To administer OC-n facility protection group with TL1, go to step 21.

Administer OC-n Facility Protection Group with 1677 SONET Link EMA

2 Select action.

To retrieve OC-n facility protection group, go to step 3.To provision OC-n facility protection group, go to step 7.

Figure 119-1. Example of OC-3 Provisioning

OC3 (Working Port)

ENT-OC3

(STSMAP=)

ENT-T3

(STSMAP=)

ENT-VT1

(VTMAP=)

ENT-T1

677-0231-1062303


STS-3c STS-1

OC3(Protect Port)

ENT-EQPT

ENT-FFP-OC3

ENT-STSn

ENT-CRS-STSn

ALL

T3

VT1

T1 T1


* See notebelow.

Cross-connectto other STSns

Administer OC-n Facility Protection Group4-82


To deprovision OC-n facility protection group, go to step 15.To end the procedure, go to step 36.

Retrieve OC-n Facility Protection Group

3 Expand the Protection domain in the Scope Pane.


5 Right-click on the appropriate OC-n facility and select Refresh.

6 Go to step 2.

Provision OC-n Facility Protection Group



9 Right-click on the appropriate OC-n protection range and select Create Protection Pair. The Protection Provision wizard appears.




13 Click Finish.

14 Go to step 2.

Deprovision OC-n Facility Protection Group



17 Select the appropriate OC-n protection range to display current protection pairs.

18 Right-click on the appropriate OC-n protection pair and select Delete.

19 In the message window, click Delete.

20 Go to step 2.



Administer OC-n Facility Protection Group with TL1

21 Select action.

To retrieve OC-n facility protection group, go to step 22.To provision OC-n facility protection group, go to step 25.To deprovision OC-n facility protection group, go to step 34.To end the procedure, go to step 36.

Retrieve OC-n Facility Protection Group

22 Enter RTRV-FFP-OCn::[AID];

where:OCn=Optical facility type (OC3, OC12, OC48, or OC192).AID=OCn Access Identifier. Omit AID value to retrieve ALL OCn facilities.

23 Examine output. One line of output is returned for each OC-n specified, regardless of whether the OC-n is in a facility protection group. Output parameter ACTIVE= shows the active port of the pair only when it is LINEAR.

24 Go to step 21.


25 Select action.

To provision OC-3 facility protection group, go to step 26.To provision OC-12 facility protection group, go to step 28.To provision OC-48 facility protection group, go to step 30.To provision OC-192 facility protection group, go to step 32.

26 Enter ENT-FFP-OC3::PROTECTED_ID,PROTECTING_ID::::[APSTRC=][,PTYPE=][,PSDIRN=][,RVRTV=][,RVRTTIM=];

where:PROTECTED_ID=Working OC-3 in 1+1 FFP group or working (preferred) OC-3 in UPSR groupPROTECTING_ID=Protecting OC-3 in 1+1 FFP group or protecting (alternate) OC-3 in UPSR groupRefer to table 119-A for valid working and protect pairs. Ports must be configured on an adjacent pair of cards.Other parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

27 Go to step 21.



28 Enter ENT-FFP-OC12::PROTECTED_ID,PROTECTING_ID::::[APSTRC=][,PTYPE=][,PSDIRN=][,RVRTV=][,RVRTTIM=];

where:PROTECTED_ID=Working OC-12 in 1+1 FFP group or working (preferred) OC-12 in UPSR groupPROTECTING_ID=Protecting OC-12 in 1+1 FFP group or protecting (alternate) OC-12 in UPSR groupRefer to table 119-A for valid working and protect pairs. Ports must be configured on an adjacent pair of cards.Other parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

29 Go to step 21.

30 Enter ENT-FFP-OC48::PROTECTED_ID,PROTECTING_ID::::[PTYPE=][,PSDIRN=][APSTRC=][,RVRTV=][,RVRTTIM=][,NODEID=][,NODEDESCR=][,AUTOMAP=][,RINGID=];

where:PROTECTED_ID=Working OC-48 in 1+1 FFP group, working (preferred) OC-48 in UPSR group, or west OC-48 in BLSRPROTECTING_ID=Protecting OC-48 in 1+1 FFP group, protecting (alternate) OC-48 in UPSR group, or east OC-48 in BLSRRefer to table 119-A for valid working and protect pairs. Ports must be configured on an adjacent pair of cards.RINGID is required when PTYPE=BLSR2.Other parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

31 Go to step 21.

32 Enter ENT-FFP-OC192::PROTECTED_ID,PROTECTING_ID::::[PTYPE=][,PSDIRN=][APSTRC=][,RVRTV=][,RVRTTIM=][,NODEID=][,NODEDESCR=][,AUTOMAP=][,RINGID=];

where:PROTECTED_ID=Working OC-192 in 1+1 FFP group, working (preferred) OC-192 in UPSR group, or west OC-192 in BLSRPROTECTING_ID=Protecting OC-192 in 1+1 FFP group, protecting (alternate) OC-192 in UPSR group, or east OC-192 in BLSRRefer to table 119-A for valid working and protect pairs. Ports must be configured on an adjacent pair of cards.RINGID is required when PTYPE=BLSR2.Other parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.



33 Go to step 21.

Deprovision OC-n Facility Protection Group

34 Enter DLT-FFP-OCn::PROTECTED_ID,[PROTECTING_ID];

where:OCn=Optical facility type (OC3, OC12, OC48, or OC192).PROTECTED_ID=Working OC-n facility in the FFP groupPROTECTING_ID=Protecting OC-n facility in the FFP group

Table 119-A. Valid OC-n Facility Protection PairsWORKING OC-n AIDS PROTECT OC-n AIDSOC3-1-{A,B}-{1-12} (same port as protection) OC3-2-{A,B}-{1-12} (same port as working)

OC3-3-{A,B}-{1-12} (same port as protection) OC3-4-{A,B}-{1-12} (same port as working)











OC48-1-{A,B}-1 OC48-2-{A,B}-1OC48-3-{A,B}-1 OC48-4-{A,B}-1OC48-5-{A,B}-1 OC48-6-{A,B}-1OC48-12-{A,B}-1 OC48-13-{A,B}-1OC48-14-{A,B}-1 OC48-15-{A,B}-1OC48-16-{A,B}-1 OC48-17-{A,B}-1

OC192-5-AB-1 OC192-6-AB-1OC192-{5, 6, 12, 13}-AB-1 (UPSR) OC192-{5, 6, 12, 13}-AB-1 (UPSR)OC192-12-AB-1 OC192-13-AB-1



35 Go to step 21.




DLP-120Deprovision DS3 (T3) FacilityPURPOSE

This procedure provides the instructions to deprovision a DS3 facility.

PREREQUISITES

Before deprovisioning a DS3 facility, embedded T1 ports must be deprovisioned. Refer to DLP-161. If the T3 port is cross-connected, the cross-connect must be deleted before the T3 can be deprovisioned. To delete T3 cross-connections, refer to DLP-124.

GENERAL


STEP PROCEDURE

1 Select action.

To deprovision DS3 facility with 1677 SONET Link EMA, go to step 2.To deprovision DS3 facility with TL1, go to step 29.

Deprovision DS3 Facility with 1677 SONET Link EMA


3 Select action.

If T3 is stand-alone, go to step 4.If T3 is embedded in an OC-n, go to step 11.If T3 is embedded in an EC1, go to step 20.

Deprovision Stand-Alone T3


5 Select the appropriate T3 group.


Deprovision DS3 (T3) Facility 4-89


7 Does facility have Secondary State of LPBK, SDEE, TRM, TS, or UAS?

If yes, the specified T3 facility cannot be deleted. Go to step 33.If no, go to step 8.

8 Right-click the appropriate T3 facility and select Unassign.

9 Click Yes.

10 Go to step 33.

Deprovision T3 Embedded in OC-n



13 Expand appropriate OC-n facility.

14 Select the appropriate STS-1 facility to display T3 facilities.





18 Click Yes.

19 Go to step 33.

Deprovision T3 Embedded in EC1






Deprovision DS3 (T3) Facility4-90





27 Click Yes.

28 Go to step 33.

Deprovision DS3 Facility with TL1



30 Examine output for provisioning information on port. Ensure that port is in valid state for deprovisioning (IS).

31 Does facility have SST of LPBK, SDEE, TRM, TS, or UAS?

If yes, DLT-T3 command cannot be performed on the specified T3 facility. Go to step 33.If no, go to step 32.

32 Enter DLT-T3::AID;





DLP-121Deprovision OC-n FacilityPURPOSE

This procedure provides the instructions to deprovision an OC-3, OC-12, OC-48, or OC-192 facility.

PREREQUISITES

Before deprovisioning an OC-n facility, remove all cross-connects, rings, and facility protection pairs associated with the interface.

If the OC-n facility is part of a facility protection group, the group must be deprovisioned first. Refer to DLP-119.

If the OC-n facility contains embedded STS signals, they must be deprovisioned first. To deprovision embedded STS-n signals, refer to DLP-122.

GENERAL


STEP PROCEDURE

1 Select action.

To deprovision OC-n facility with 1677 SONET Link EMA, go to step 2.To deprovision OC-n facility with TL1, go to step 10.

Deprovision OC-n Facility with 1677 SONET Link EMA

2 Expand the Facilities domain in the Navigation Tree.


4 Select the appropriate OC-n group.

5 Examine provisioning information on appropriate OC-n facility.

6 Does facility have Secondary State of LPBK, SDEE, STBYH, TRM, UAS, or WRK?

If yes, the specified OC-n facility cannot be deleted. Go to step 15.If no, go to step 7.

Deprovision OC-n Facility 4-93


7 Right-click on the appropriate OC-n port and select Unassign.

8 Click Yes.

9 Go to step 15.

Deprovision OC-n Facility with TL1


where:OCn=Optical facility type (OC3, OC12, OC48, or OC192)AID=OC-n Access Identifier

11 Examine output for provisioning information on facility.

12 Does facility have SST of LPBK, SDEE, STBYH, TRM, UAS, or WRK?

If yes, DLT-OCn command cannot be performed on the specified OC-n facility. Go to step 15.If no, go to step 13.

13 Enter DLT-OCn::AID;

where:OCn=Optical facility type (OC3, OC12, OC48, or OC192)AID=OC-n Access Identifier

14 Enter DLT-OCn::AID;

where:OCn=Optical facility type (OC3, OC12, OC48, or OC192).AID=OC-n Access Identifier


Deprovision OC-n Facility4-94


DLP-122Deprovision STS-n FacilityPURPOSE

This procedure provides the instructions to deprovision an STS-1, STS-3c, STS-12c, or STS-48c facility.

GENERAL

The DLT-STS1 command is used to deprovision STS-1 facilities.

The DLT-STSn command is used to deprovision STS-3c, STS-12c, and STS-48c facilities.


STEP PROCEDURE

1 Select action.

To deprovision STS-n facility with 1677 SONET Link EMA, go to step 2.To deprovision STS-n facility with TL1, go to step 21.

Deprovision STS-n Facility with 1677 SONET Link EMA

2 Select action.

To deprovision STS-n embedded in an OC-n, go to step 3.To deprovision STS-1 embedded in an EC1, go to step 12.

Deprovision STS-n Embedded in an OC-n




6 Select the appropriate OC-n facility to display timeslots.

7 Examine provisioning information on appropriate facility.

Deprovision STS-n Facility 4-95


8 Does facility have Secondary State of SDEE, TRM, TS, or UAS?

If yes, the specified STS-n facility cannot be deleted. Go to step 31.If no, go to step 9.

9 Right-click on the appropriate STS-n facility and select Unassign.

10 Click Yes.

11 Go to step 31.

Deprovision STS-1 Embedded in an EC1




15 Select the appropriate OC-n facility to display STS-1 facility.

16 Examine provisioning information on STS-1 facility.

17 Does facility have Secondary State of SDEE, TRM, TS, or UAS?

If yes, the specified STS-n facility cannot be deleted. Go to step 31.If no, go to step 18.

18 Right-click on the appropriate STS-1 facility and select Unassign.

19 Click Yes.

20 Go to step 31.

Deprovision STS-n Facility with TL1

21 Select action.

To deprovision an STS-1 facility, go to step 22.To deprovision an STS-n facility, go to step 27.

Deprovision STS-1 Facility

22 Enter RTRV-STS1::AID;


Deprovision STS-n Facility4-96



24 Does facility have SST of SDEE, TRM, TS, or UAS?

If yes, DLT-STS1 command cannot be performed on the specified STS-1 facility. Go to step 31.If no, go to step 25.

25 Enter DLT-STS1::AID;


26 Go to step 31.

Deprovision STS-n Facility

27 Enter RTRV-STSn::AID;

where:STSn=Type of STS signal (STS3C, STS12C, STS48C, or STS192C)AID=STSn AID


29 Does facility have SST of SDEE, TRM, TS, or UAS?

If yes, DLT-STSn command cannot be performed on the specified STS-n facility. Go to step 31.If no, go to step 30.

30 Enter DLT-STSn::AID;

where:STSn=Type of STS signal (STS3C, STS12C, STS48C, or STS192C)AID=STSn Access Identifier


Deprovision STS-n Facility 4-97


Deprovision STS-n Facility4-98


DLP-123Deprovision VT1.5 FacilityPURPOSE

This procedure provides the instructions to deprovision a VT1.5 facility.

PREREQUISITES

If the VT1.5 port is cross-connected, the cross-connect must be deprovisioned first. To delete VT1.5 cross-connections, refer to DLP-126.

GENERAL


STEP PROCEDURE

1 Select action.

To deprovision VT1.5 facility with 1677 SONET Link EMA, go to step 2.To deprovision VT1.5 facility with TL1, go to step 21.

Deprovision VT1.5 Facility with 1677 SONET Link EMA

2 Select action.

To deprovision VT1.5 embedded in an OC-n, go to step 3.To deprovision VT1.5 embedded in an EC1, go to step 12.

Deprovision VT1 Embedded in an OC-n





7 Select the appropriate STS-1 facility to display VT1 facilities.

Deprovision VT1.5 Facility 4-99


8 Does facility have Secondary State of BUSY, LPBK, SDEE, TRM, TS, or UAS?

If yes, the specified VT1 facility cannot be deleted. Go to step 25.If no, go to step 9.

9 Right-click on the appropriate VT1 and select Unassign.

10 Click Yes.

11 Go to step 25.

Deprovision VT1 Embedded in an EC1






17 Does facility have Secondary State of BUSY, LPBK, SDEE, TRM, TS, or UAS?

If yes, the specified VT1 facility cannot be deleted. Go to step 25.If no, go to step 18.

18 Right-click on the appropriate VT1 and select Unassign.

19 Click Yes.

20 Go to step 25.

Deprovision VT1.5 Facility with TL1

21 Enter RTRV-VT1::[AID];


22 Examine output for provisioning information on facility. Ensure that facility is in valid state for deprovisioning (IS).

Deprovision VT1.5 Facility4-100


23 Does facility have SST of BUSY, LPBK, SDEE, TRM, TS, or UAS?

If yes, the DLT-VT1 command cannot be performed on the specified VT1 facility. Go to step 25.If no, go to step 24.

24 Enter DLT-VT1::AID;



Deprovision VT1.5 Facility 4-101


Deprovision VT1.5 Facility4-102


DLP-124Administer DS3 Cross-ConnectionPURPOSE

This procedure provides the instructions to retrieve information on, create, edit, and delete a cross-connection between two stand-alone DS3 ports, or between a stand-alone DS3 port and an STS-1 facility in an OC-n or EC1 facility.

PREREQUISITES

To establish a DS3 cross-connection, the required equipment and appropriate facilities must be provisioned. Refer to DLP-112 to provision equipment. Refer to DLP-115 to provision DS3 facilities. Refer to DLP-117 to provision STS-n facilities.

GENERAL

Two-way cross-connections can be established between two stand-alone DS3 facilities, and between a stand-alone DS3 facility and an STS-1 facility in an OC-n or EC1 facility.

If a connection is to be made between an STS-1 facility and a DS3 facility, the ENT-CRS-T3 command should be used with FROM=T3 facility AID and TO=STS-1 facility AID.


STEP PROCEDURE

1 Select action.

To administer DS3 cross-connection with 1677 SONET Link EMA, go to step 2.To administer DS3 cross-connection with TL1, go to step 41.

Administer DS3 Cross-Connection with 1677 SONET Link EMA

2 Select action.

To create DS3 cross-connection, go to step 3.To retrieve DS3 cross-connection, go to step 22.To modify DS3 cross-connection, go to step 22.To delete DS3 cross-connection, go to step 22.To end this procedure, go to step 52.

Administer DS3 Cross-Connection 4-103


Create DS3 Cross-Connection

3 Right-click the CrossConnection domain and select Create CrossConnections. The Create CrossConnections window appears.

4 In the Create CrossConnections window, click the Add button.

5 Click in the Source Facility box. The Facility Browser window appears.

6 Double-click on Facilities.

7 Double-click on facility types and groups until appropriate T3 facility is shown.

If connection being created is T3-STS1 connection, the T3 port must be in the Source Facility box.

8 Select T3 facility.

9 Click OK.

10 Click in the Destination Facility box. The Facility Browser window appears.


12 Double-click on facility types and groups until appropriate T3 or STS1 facility is shown.


13 Select T3 or STS1 facility.

14 Click OK.

15 Double-click in the CrossConnection Type box.

16 Select the cross connection type from the options in the drop-down list.

17 Enter information for other parameters as appropriate.

18 Click Apply. A message window appears with the results of the connection request.

19 Click Close to close the message window.

20 Click Close to close the Create CrossConnections window.

21 Go to step 2.

Administer DS3 Cross-Connection4-104


Retrieve, Modify, or Delete DS3 Cross-Connection

22 Right-click the CrossConnection domain and select Manage CrossConnections.

23 Under Facility Type, select T3 from the drop-down list.

24 Click Retrieve to retrieve cross connections.

25 Observe results in table.

26 Is a connection shown in the table to be modified?


27 Select appropriate connection from list.

28 Double-click in box under parameter to modify, enter a new value for the connection, and press the Enter key.

29 Repeat step 28 to modify other parameters as appropriate.

30 Click Modify. A message window appears with the results of the connection request.


32 Click Close to close the Manage CrossConnections window.

33 Go to step 2.

34 Is a connection shown in the table to be deleted?



36 Click Delete.

37 Click OK. A message window appears with the results of the connection request.



40 Go to step 2.



Administer DS3 Cross-Connection with TL1

41 Select action.

To retrieve DS3 cross-connection information, go to step 42.To create DS3 cross-connection, go to step 44.To modify DS3 cross-connection, go to step 46.To delete DS3 cross-connection, go to step 49.To end this procedure, go to step 52.

Retrieve DS3 Cross-Connection Information

42 Enter RTRV-CRS-T3::AID;


43 Go to step 41.


44 Enter ENT-CRS-T3::FROM,TO:::CCT:[CKTID=][,CKTADDR=][,CKTNBR=][,SWPDIP=][,SWUNEQP=][,PREFERRED=][,RVRTV=][,RVRTTIM=];

where:FROM=AID of source facility (T3). If connection being created is T3-STS1 connection, the T3 port must be specified in the FROM parameter.TO=AID of destination facility (T3 or STS-1)CCT=Cross-connec type. (2WAY, 2WAYDC, SRIW)Other parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

45 Go to step 41.

Modify DS3 Cross-Connection

46 CAUTION: Possibility of service interruption. Modifying an active cross-connection always affects service.



47 Enter ED-CRS-T3::FROM,TO:::,:[CKTID=][,CKTADDR=][,CKTNBR=][,SWPDIP=][,SWUNEQP=][,PREFERRED=][,RVRTV=][,RVRTTIM=];

where:FROM=AID of source facility (T3). If connection being modified is T3-STS1 connection, the T3 port must be specified in the FROM parameter.TO=AID of destination facility (T3 or STS-1)Other parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

48 Go to step 41.

Delete DS3 Cross-Connection

49 CAUTION: Possibility of service interruption. Deleting an active cross-connection always affects service.

50 Enter DLT-CRS-T3::FROM,TO;

where:FROM=AID of source facility (T3). If connection being deleted is T3-STS1 connection, the T3 port must be specified in the FROM parameter.TO=AID of destination facility (T3 or STS-1)Other parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

51 Go to step 41.




DLP-125Administer STS-n Cross-ConnectionPURPOSE

This procedure provides the instructions to retrieve information on, create, edit, and delete cross-connections between two STS-n facilities.

PREREQUISITES

To establish an STS-n cross-connection, the required equipment and appropriate OC-n or EC1 facilities must be provisioned. Refer to DLP-112 to provision equipment. Refer to DLP-116 to provision OC-n facilities. Refer to DLP-114 to provision EC1 facilities. Refer to DLP-117 to provision STS-n facilities. Refer to DLP-119 to provision an OC-n facility protection group, if an APS pair.

GENERAL

The system supports 2-way STS-n cross-connections between two STS-n facilities. This procedure is used to administer cross-connections between two STS-n facilities, and is valid only when both ends of cross-connection are STS-n facilities of the same type (that is, STS-1, STS-3c, STS-12c, or STS-48c). If any facility in the cross-connection is a DS3, refer to DLP-124.


STEP PROCEDURE

1 Select action.

To administer STS-n cross-connection with 1677 SONET Link EMA, go to step 2.To administer STS-n cross-connection with TL1, go to step 41.

Administer STS-n Cross-Connection with 1677 SONET Link EMA

2 Select action.

To create STS-n cross-connection, go to step 3.To retrieve STS-n cross-connection, go to step 22.To modify STS-n cross-connection, go to step 22.To delete STS-n cross-connection, go to step 22.To end this procedure, go to step 56.

Administer STS-n Cross-Connection 4-109


Create STS-n Cross-Connection





7 Double-click on facility types and groups until appropriate STS-n facility is shown.


8 Select STS-n facility.

9 Click OK.






14 Click OK.







21 Go to step 2.

Administer STS-n Cross-Connection4-110


Retrieve, Modify, or Delete STS-n Cross-Connection


23 Under Facility Type, select appropriate value (STS-n) from the drop-down list.











33 Go to step 2.




36 Click Delete.




40 Go to step 2.



Administer STS-n Cross-Connection with TL1

41 Select action.

To retrieve all cross-connection information, go to step 42.To retrieve cross-connection defaults, go to step 44.To retrieve STS-n cross-connection information, go to step 46.To create an STS-n cross-connection, go to step 48.To modify an STS-n cross-connection, go to step 50.To delete an STS-n cross-connection, go to step 53.To end this procedure, go to step 56.

Retrieve All Cross-Connection Information

42 Enter RTRV-CRS-ALL:::::[CCT];

where:CCT=Cross-connect type (2WAY, 2WAYDC, SRIW, THRU). If no value is entered, all cross-connect types are retrieved.

43 Go to step 41.

Retrieve Cross-Connection Defaults

44 Enter RTRV-ATTR-CRSDFLT;

45 Go to step 41.

Retrieve STS-n Cross-Connection Information

46 Enter RTRV-CRS-STSn::AID:::[CCT];

where:STSn=Signal type (STS1, STS3C, STS12C, or STS48C).AID=STSn Access IdentifierCCT=Cross-connect type (2WAY, 2WAYDC, SRIW, THRU)

47 Go to step 41.




48 Enter ENT-CRS-STSn::FROM,TO:::CCT[,CCT2]:[CKTID=][,CKTADDR=][,CKTNBR=][,SWPDIP=][,SWUNEQP=][,PREFERRED=][,RVRTV=][,RVRTTIM=][,SWPDIP2=][,SWUNEQP2=][,PREFERRED2=][,RVRTV2=][,RVRTTIM2=];

where:STSn=Signal type (STS1, STS3C, STS12C, or STS48C).FROM=AID of source facilityTO=AID of destination facilityCCT=Cross-connect type (2WAY, 2WAYDC, SRIW, THRU)Other parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

49 Go to step 41.

Modify STS-n Cross-Connection


51 Enter ED-CRS-STSn::FROM,TO::::[CKTID=][,CKTADDR=][,CKTNBR=][,SWPDIP=][,SWUNEQP=][,RVRTV=][,RVRTTIM=][,SWPDIP2=][,SWUNEQP2=][,RVRTV2=][,RVRTTIM2=];

where:STSn=Signal type (STS1, STS3C, STS12C, or STS48C).FROM=AID of source facilityTO=AID of destination facilityOther parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

52 Go to step 41.

Delete STS-n Cross-Connection


54 Enter DLT-CRS-STSn::FROM,TO;

where:STSn=Signal type (STS1, STS3C, STS12C, or STS48C).FROM=AID of source facilityTO=AID of destination facility



55 Go to step 41.




DLP-126Administer VT1.5 Cross-ConnectionPURPOSE

This procedure provides the instructions to retrieve information on, create, edit, and delete a 2-way cross-connection between two VT1.5 facilities.

PREREQUISITE

To establish a VT1.5 cross-connection, the required VT1.5 facilities must be provisioned first. Refer to DLP-118 to provision VT1.5 facilities.

GENERAL

The system supports a 2-way cross-connection between two VT1.5 facilities. This procedure is used to administer cross-connections between two VT1.5 facilities, and is valid only when both facilities are VT1.5.


STEP PROCEDURE

1 Select action.

To administer VT1.5 cross-connection with 1677 SONET Link EMA, go to step 2.To administer VT1.5 cross-connection with TL1, go to step 41.

Administer VT1.5 Cross-Connection with 1677 SONET Link EMA

2 Select action.

To create VT1.5 cross-connection, go to step 3.To retrieve VT1.5 cross-connection, go to step 22.To modify VT1.5 cross-connection, go to step 22.To delete VT1.5 cross-connection, go to step 22.To end this procedure, go to step 52.

Create VT1.5 Cross-Connection


Administer VT1.5 Cross-Connection 4-115





7 Double-click on facility types and groups until appropriate VT1 facility is shown.

8 Select VT1 facility.

9 Click OK.



12 Double-click on facility types and groups until appropriate VT1 facility is shown.

13 Select VT1 facility.

14 Click OK.







21 Go to step 2.

Retrieve, Modify, or Delete VT1.5 Cross-Connection


23 Under Facility Type, select VT1 from the drop-down list.



Administer VT1.5 Cross-Connection4-116










33 Go to step 2.




36 Click Delete.




40 Go to step 2.

Administer VT1.5 Cross-Connection with TL1

41 Select action.

To retrieve VT1.5 cross-connection information, go to step 42.To create VT1.5 cross-connection, go to step 44.To modify a VT1.5 cross-connection, go to step 46.To delete a VT1.5 cross-connection, go to step 49.To end this procedure, go to step 52.



Retrieve VT1.5 Cross-Connection Information

42 Enter RTRV-CRS-VT1::AID:::[CCT];

where:AID=VT1 Access IdentifierCCT=Cross-connect type (2WAY)

43 Go to step 41.

Create VT1.5 Cross-Connection

44 Enter ENT-CRS-VT1::FROM,TO:::2WAY:[CKTID=];

where:FROM=AID of source facilityTO=AID of destination facilityOther parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

45 Go to step 41.

Modify VT1.5 Cross-Connection


47 Enter ED-CRS-VT1::FROM,TO::::[CKTID=];

where:FROM=AID of source facilityTO=AID of destination facilityOther parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

48 Go to step 41.

Delete VT1.5 Cross-Connection




50 Enter DLT-CRS-VT1::FROM,TO;

where:FROM=AID of source facilityTO=AID of destination facility

51 Go to step 41.




DLP-127Set EC1 PM ModePURPOSE

This procedure provides the instructions to set or change Performance Monitoring (PM) mode for EC1 ports. The PM mode controls the data collection for specific types of PM data (path, line, segment, intermediate node).

GENERAL

PM commands operate only on provisioned ports.

PM commands are used to monitor signal overhead that is used to track system efficiency. By tracking efficiency, users can recognize gradual deterioration of system performance.


STEP PROCEDURE

1 Select action.

To set EC1 PM mode with 1677 SONET Link EMA, go to step 2.To set EC1 PM mode with TL1, go to step 11.

Set EC1 PM Mode with 1677 SONET Link EMA



4 Expand appropriate EC1 group.

5 Right-click appropriate EC1 facility and select Performance Monitoring>PM Mode. Current PM mode parameters are displayed in the table.

6 For Near End, double click in the box under ALL Mode Types and select value from drop-down list.

– ON enables Near End PM

– OFF disables Near End PM

Set EC1 PM Mode 4-121


7 For Far End, double click in the box under ALL Mode Types and select value from drop-down list.

– ON enables Far End PM

– OFF disables Far End PM

8 Click Apply.

9 Click Close.

10 Go to step 14.

Set EC1 PM Mode with TL1

11 Enter RTRV-PMMODE-EC1::AID:::[LOCN];

where:AID=EC1 Access IdentifierLOCN={ALL, FEND, NEND}

12 Examine output to determine current PM mode.

13 Enter SET-PMMODE-EC1::AID:::LOCN,ALL,[PMSTATE];

where:AID=EC1 Access IdentifierLOCN={ALL, FEND, NEND}PMSTATE={OFF, ON}


Set EC1 PM Mode4-122


DLP-128Set DS1 PM ModePURPOSE

This procedure provides the instructions to set or change Performance Monitoring (PM) mode for DS1 ports. The PM mode controls the data collection for specific types of PM data (path, line, segment, intermediate node).

GENERAL




STEP PROCEDURE

1 Select action.

To set DS1 PM mode with 1677 SONET Link EMA, go to step 2.To set DS1 PM mode with TL1, go to step 11.

Set DS1 PM Mode with 1677 SONET Link EMA


3 Expand appropriate facility domain.

4 Expand the facility groups and instances until appropriate DS1 facility is displayed.

5 Right-click appropriate DS1 facility and select Performance Monitoring>PM Mode. Current PM mode parameters are displayed in the table.




Set DS1 PM Mode 4-123





8 Click Apply.

9 Click Close.

10 Go to step 14.

Set DS1 PM Mode with TL1

11 Enter RTRV-PMMODE-T1::AID:::[LOCN];

where:AID=T1 Access IdentifierLOCN={ALL, FEND, NEND}


13 Enter SET-PMMODE-T1::AID:::LOCN,ALL,[PMSTATE];

where:AID=T1 Access IdentifierLOCN={ALL, FEND, NEND}PMSTATE={OFF, ON}


Set DS1 PM Mode4-124


DLP-129Set OFA PM ModePURPOSE

This procedure provides the instructions to set or change Performance Monitoring (PM) mode for OFA ports. The PM mode controls the data collection for specific types of PM data (path, line, segment, intermediate node).

GENERAL




STEP PROCEDURE

1 Select action.

To set OFA PM mode with 1677 SONET Link EMA, go to step 2.To set OFA PM mode with TL1, go to step 11.

Set OFA PM Mode with 1677 SONET Link EMA


3 Expand the OFA domain.

4 Expand appropriate OFA group.

5 Right-click appropriate OFA facility and select Performance Monitoring>PM Mode. Current PM mode parameters are displayed in the table.




Set OFA PM Mode 4-125





8 Click Apply.

9 Click Close.

10 Go to step 14.

Set OFA PM Mode with TL1

11 Enter RTRV-PMMODE-OFA::AID:::[LOCN];

where:AID=OFA Access IdentifierLOCN={ALL, NEND}


13 Enter SET-PMMODE-OFA::AID:::LOCN,ALL,[PMSTATE];

where:AID=OFA Access IdentifierLOCN={ALL, NEND}PMSTATE={OFF, ON}


Set OFA PM Mode4-126


DLP-130Administer T3 LoopbackPURPOSE

This procedure provides the instructions to administer DS3 (T3) loopbacks.

PREREQUISITES

The DS3 facility to place in loopback must have a Primary State (PST) of OOS-AUMA or OOS-MA.

GENERAL

Loopbacks are test features that can be set to loop a signal back at different points along the signal path. The system supports five types of T3 loopbacks. Refer to table 130-A for a list of supported loopback types and locations.

An Equipment loopback is a loopback of a signal received from the switch fabric. The signal is still forwarded to the network. See figure 130-2.

A Facility loopback is a loopback of a signal received from the network before the switch fabric. The Alarm Indication Signal (AIS) is forwarded to the switch fabric. See figure 130-3.

A Line loopback occurs in different places depending on value of location (LOCN). For a location of NEND, the DS3 line signal received from the network is looped back before the switch fabric. The signal is still forwarded to the switch fabric. See figure 130-1. For a location of FEND, the DS3 line signal is looped back by far-end equipment. The loopback request is sent through the Far End Alarm and Control (FEAC) channel. See figure 130-4.

An ALLDS1LINE loopback is a loopback of all embedded DS1 line signals by far-end equipment. The loopback request is sent through the FEAC channel. See figure 130-5.

Table 130-A. Allowed Loopback Type for Specific T3 Configuration and LocationStandalone T3 on ECC

Standalone T3 on DS3 Card T3 embedded in an STS1Using a TMUX1

[1] Whether the T3 uses a TMUX is determined by the STSMAP parameter of the T3. Refer to DLP-115.

Not using a TMUX1

LOCN NEND EQUIP, FACILITY LINE, EQUIP, FACILITY

LINE, EQUIP FACILITY

FEND LINE2, ALLDS1LINE2

[2] FEND LINE or FEND ALLDS1LINE is allowed only if the T3 has been provisioned with a framing format (FMT)of CBIT.

LINE2, ALLDS1LINE2

NA LINE2, ALLDS1LINE2

LIU NA LINE, EQUIP, DUAL

LINE, EQUIP, DUAL NA

Administer T3 Loopback 4-127


A Dual loopback is simultaneous LINE and EQUIP loopbacks at the LIU (for location of LIU only). See figure 130-1.

Figure 130-1. DS3 Loopback Diagram

Figure 130-2. Equipment Loopback

A B C D

STS-1 Signalto 1677 Fabric

STS-1 Signalfrom 1677 Fabric

IncomingDS3 Signal

OutgoingDS3 Signal

I/O Card

LIU DS3 Framer

A = LIU Line LoopbackB = LIU Equipment Loopback

C = Line LoopbackD = Equipment Loopback

DS3 LIU Loopback supports a dual that is both A and B.

677-0080-1100404

677-0245-1100404

I/O Module I/O ModuleMatrix

X

Administer T3 Loopback4-128


Figure 130-3. Facility Loopback

Figure 130-4. FEND Line Loopback

677-0244-1100404


X AIS

677-0292-1110804

1677 Far End NE

FEND Line loopback

request sent via

OPR-LPBK-T3

Line loopback

request received and

signal is looped back

CBIT formatted T3

(FEAC Channel)




STEP PROCEDURE

1 CAUTION: Possibility of service interruption. Performing loopbacks interrupts traffic.

2 Connect DS3 test equipment to selected DS3 interface on the 1677 SONET Link.

3 Set the DS3 test equipment for internal timing.

4 Review the DS3 Interface loopback diagram shown in figure 130-1.

5 Select action.

To administer DS3 loopback with 1677 SONET Link EMA, go to step 6.To administer DS3 loopback with TL1, go to step 44.

Administer DS3 Loopback with 1677 SONET Link EMA

6 Select action.

To retrieve current loopback status of DS3 facility, go to step 7.To establish loopback, go to step 14.To verify loopback status, go to step 29.To release loopback, go to step 36.To end this procedure, go to step 60.

Figure 130-5. ALLDS1LINE Loopback

677-0293-1110804

1677 Far End NE

ALLDS1LINE loopbackrequest sent viaOPR-LPBK-T3

Line loopbackrequest received andsignal is looped back

CBIT formatted T3(FEAC Channel)



Retrieve Loopback Information


8 Expand the appropriate facility domain (EC1, OC3, OC12, OC48, OC192, T3).

9 Expand the facility groups and instances until appropriate facility is displayed.

10 Right-click facility and select Loopback>View.

11 Observe results in table. No information appears if facility is not in loopback.

12 Click Close.

13 Go to step 6.

Establish Loopback




17 Right-click facility and select Refresh.

18 Observe facility Primary State (PST) in the Result Pane.

19 Select action.

If the PST for the facility is IS or OOS-AU, go to step 20.If the PST for the facility is OOS-AUMA or OOS-MA, go to step 23.

20 Right-click the facility and select Service State>Remove.

21 Click Yes.

22 Verify the Primary State is now OOS-MA or OOS-AUMA.

23 Right-click the T3 facility and select Loopback>Operate. The Operate Loopback T3 wizard appears.






27 Click Finish.

28 Go to step 6.

Verify Loopback Status






34 Click Close.

35 Go to step 6.

Release Loopback




39 Right-click on appropriate facility and select Loopback>Release.

40 Click Yes.

41 Right-click on the facility and select Service State>Restore.

42 Click Yes.

43 Go to step 6.

Administer DS3 Loopback with TL1

44 Select action.

To retrieve current loopback status of DS3 facility, go to step 45.To establish loopback, go to step 48. To verify loopback status, go to step 54.To release loopback, go to step 57.To end this procedure, go to step 60.




45 Enter RTRV-LPBK-T3::[AID];


46 Examine output. One line of information displays for each facility in loopback within specified range of AIDs. No information displays for facilities that are not in loopback.

47 Go to step 44.

Establish Loopback

48 Enter RTRV-T3::AID; to retrieve the current PST and SST of the T3 facility.


49 Observe output.

50 Select action.

If the PST for the T3 facility is IS or OOS-AU, go to step 51.If the PST for the T3 facility is OOS-AUMA or OOS-MA, go to step 52.

51 Before establishing a loopback, the facility must be placed out of service.

Enter RMV-T3::AID;


52 Enter OPR-LPBK-T3::AID:::[LOCN],,,LPBKTYPE;

where:AID=T3 Access IdentifierLOCN={FEND, LIU, NEND} Default=NEND.LPBKTYPE={ALLDS1LINE, DUAL, EQUIP, FACILITY, LINE}

53 Go to step 44.


54 Enter RTRV-LPBK-T3::[AID]; to verify the DS3 facility is in loopback.




55 Examine output. One line of information displays for each port in loopback within specified range of AIDs. No information displays for ports that are not in loopback.

56 Go to step 44.

Release Loopback

57 Enter RLS-LPBK-T3::AID:::[LOCN],,,[LPBKTYPE]; to release the DS3 loopback.

where:AID=T3 Access IdentifierLOCN={FEND, LIU, NEND} Default=NEND.LPBKTYPE={ALLDS1LINE, DUAL, EQUIP, FACILITY, LINE}

58 Enter RST-T3::AID; to place the facility back in service.


59 Go to step 44.




DLP-131Administer OC-n LoopbackPURPOSE

This procedure provides the instructions to administer OC-3, OC-12, OC-48, or OC-192 loopbacks.

PREREQUISITES

The OC-n facility to place in loopback must have a Primary State (PST) of OOS-AUMA or OOS-MA.

GENERAL

Loopbacks are test features that can be set to loop a signal back at different points along the signal path. The system supports two types of OC-n loopbacks.


An Equipment loopback is a loopback of a signal received from the switch fabric. The signal is still forwarded to the network. See figure 131-2.


677-0244-1100404


X AIS

Administer OC-n Loopback 4-135



STEP PROCEDURE

1 CAUTION: Possibility of service interruption. Performing loopbacks may interrupt service if a protection line or protecting path is not available.

2 Review the loopback diagrams in figures 131-1 and 131-2.

3 Select action.

To administer OC-n loopback with 1677 SONET Link EMA, go to step 4.To administer OC-n loopback with TL1, go to step 40.

Administer OC-n Loopback with 1677 SONET Link EMA

4 Select action.

To retrieve current loopback status of OC-n facility, go to step 5.To establish loopback, go to step 12.To verify loopback status, go to step 25.


677-0245-1100404


X

Administer OC-n Loopback4-136


To release loopback, go to step 32.To end this procedure, go to step 56.





8 Right-click appropriate facility and select Loopback>View.


10 Click Close.

11 Go to step 4.

Establish Loopback




15 Right-click appropriate OC-n facility and select Refresh.


17 Select action.


18 Right-click on the OC-n facility and select Service State>Remove.

19 Click Yes.


21 Right-click on the appropriate OC-n facility and select Loopback>Operate. The Operate OC-n Loopback dialog box appears.

22 Select the appropriate loopback type (Equipment or Facility).



23 Click Operate.

24 Go to step 4.





28 Right-click appropriate OC-n facility and select Loopback>View.


30 Click Close.

31 Go to step 4.

Release Loopback





36 Click Yes.


38 Click Yes.

39 Go to step 4.

Administer OC-n Loopback with TL1

40 Select action.

To retrieve current loopback status of OC-n facility, go to step 41.To establish OC-n loopback, go to step 44.To verify loopback status, go to step 50.To release loopback, go to step 53.To end this procedure, go to step 56.




41 Select RTRV-LPBK-OCn::[AID];

where:OCn=Optical facility type (OC3, OC12, OC48, or OC192).AID=OCn Access Identifier


43 Go to step 40.

Establish Loopback

44 Enter RTRV-OCn::AID; to retrieve current PST and SST of facility.


45 Observe output.

46 Select action.



Enter RMV-OCn::AID;


48 Enter OPR-LPBK-OCn::AID:::[LOCN],,,LPBKTYPE;

where:OCn=Optical facility type (OC3, OC12, OC48, or OC192).AID=OCn Access IdentifierLOCN=NENDLPBKTYPE={EQUIP, FACILITY}

49 Go to step 40.




50 Enter RTRV-LPBK-OCn::[AID]; to verify the OC-n facility is in loopback status.



52 Go to step 40.

Release Loopback

53 Enter RLS-LPBK-OCn::AID:::[LOCN],,,[LPBKTYPE];

where:OCn=Optical facility type (OC3, OC12, OC48, or OC192).AID=OCn Access IdentifierLOCN=NENDLPBKTYPE={EQUIP, FACILITY}

54 Enter RST-OCn::AID; to place the facility back in service.


55 Go to step 40.




DLP-132Switch OC-n Line to ProtectionPURPOSE

This procedure provides the instructions to initiate and release an OC-n line switch to protection.

This procedure is used for BLSR and APS 1+1 configurations.

PREREQUISITES

OC-n facilities must be provisioned. Refer to DLP-116.

OC-n facilities must be provisioned as a facility protection group (FFP). Refer to DLP-119.

GENERAL

When initiating a protection switch using OPR-PROTNSW-OCn, three options for the switch command (SWTCHCMD) parameter are available for OC-3 and OC-12 facilities: LOCKOUT, FRCD, and MAN.

• Lockout of Protection (LOCKOUT) keeps traffic on the working facility. If traffic is on the protect facility when the command is issued, traffic switches to the working facility and remains there until the lockout is released. For this switch command, the protect AID must be specified. A Lockout overrides a Forced Switch and a Manual Switch.

• Forced Switch (FRCD) forces traffic to either the working facility or the protect facility. Specifying a working AID forces the traffic to the protect facility, and specifying a protect AID forces traffic to the working facility in the case of Linear APS. A Forced Switch overrides a Manual Switch.

• Manual Switch (MAN) moves traffic to either the working facility or the protect facility. Specifying a working AID moves the traffic to the protect facility, and specifying a protect AID moves traffic to the working facility.

For BLSR, these switch commands switch the working channels to the protection channels (timeslots).

Switch OC-n Line to Protection 4-141


Additional switch commands are available for OC-48 and OC-192 facilities: EXER-R, FRCD-R, LOP-S, and MAN-R.

• Exercise Ring (EXER-R) is applicable to AIDs in a 2FBLSR protection group. This command exercises ring protection switching of the requested span without completing the actual bridge and switch.

• Forced Switch of working to Protection-Ring (FRCD-R) is applicable to AIDs in a 2FBLSR protection group. This command performs the ring switch from the working channels to the protection channels for the span between the node at which this command is initiated and the adjacent node. This switch occurs regardless of the state of the protection channels, unless the ring is satisfying a higher poriority request than the forced switch such as lockout of protection.

• Lockout of Protection-Span (LOP-S) is applicable to AIDs in a 2FBLSR protection group. This command prevents protection switching on the entire ring. If any working traffic is using the ring protection channels, this command causes working traffic to be switched back to the working channels regardless of the condition of the working channels.

• Manual Switch of Working to Protection-Ring (MAN-R) is applicable to AIDs in a 2FBLSR protection group. This command performs the ring switch from working channels to the protection channels for the span between the node at which this command is initiated and the adjacent node.


STEP PROCEDURE

1 Select action.

To switch OC-n line to protection with 1677 SONET Link EMA, go to step 2.To switch OC-n line to protection with TL1, go to step 31.

Switch OC-n Line to Protection with 1677 SONET Link EMA

2 Select action.

To retrieve information on OC-n facilities and FFP, go to step 3.To initiate OC-n switch to protection, go to step 14.To release OC-n switch to protection, go to step 23.To end this procedure, go to step 41.

Switch OC-n Line to Protection4-142


Retrieve Information on OC-n Facilities and FFP

3 Expand the Facilities domain.




7 Examine output in Result Pane. Note states and other pertinent information.

8 Expand the Protection domain.


10 Click on the appropriate OC-n group to display current protection pairs.

11 Right-click on the appropriate OC-n protection pair and select Refresh.

12 Examine output in Result Pane.

13 Go to step 2.

Perform OC-n Protection Switch




17 Right-click on the appropriate protection pair and select Operate Switch. The Operate Protection Switch wizard appears.




21 Click Finish.

22 Go to step 2.



Release OC-n Protection Switch




26 Right-click on the appropriate protection pair and select Release Switch.

27 Is protection pair Linear or BLSR?

If Linear, go to step 29.If BLSR go to step 28.

28 Select the direction of transmission in which the switch request is to be cleared (Both, East, West).

29 Click Release.

30 Go to step 2.

Switch OC-n Line to Protection with TL1

31 Select action.

To retrieve information on OC-n facilities and FFP, go to step 32.To initiate OC-n switch to protection, go to step 37.To release OC-n switch to protection, go to step 39.To end this procedure, go to step 41.

Retrieve Information on OC-n Facilities and FFP

32 Enter RTRV-OCn::[AID];


33 Examine output. Note states and other pertinent information.





35 Examine output. The output response displays FFP information about the specified AID. No information displays for ports that are not in an FFP group.

36 Go to step 31.

Perform OC-n Protection Switch

37 Enter OPR-PROTNSW-OCn::AID:::SWTCHCMD;

where:OCn=Optical facility type (OC3, OC12, OC48, or OC192).AID=OCn Access IdentifierSWTCHCMD={FRCD, LOCKOUT, MAN} for OC3 and OC12{EXER-R, FRCD, FRCD-R, LOCKOUT, LOP-S, MAN, MAN-R} for OC48 and OC192

38 Go to step 31.

Release OC-n Protection Switch

39 Enter RLS-PROTNSW-OCn::AID;


40 Go to step 31.




DLP-133Schedule PM ReportsPURPOSE

This procedure provides the instructions to schedule daily Performance Monitoring (PM) reports and control PM reporting for specific ports.

GENERAL

PM commands operate on provisioned ports/facilities only.



STEP PROCEDURE

1 Enter RTRV-PMSCHED-ALL;

2 Examine output to determine what reports have been scheduled, if any.

3 Select action.

To schedule PM report generation and printing for all ports, go to step 4.To schedule PM report generation for a specific port, go to step 6.To disable PM report generation for a specific port/facility, go to step 8.To enable PM report generation for a specific port, go to step 13.To end this procedure, go to step 20.

Schedule Daily PM Report for All Ports

4 Enter SCHED-PMREPT-ALL:::::[REPTINVL],[REPTSTATM],[NUMREPT],[MONTYPE],[MONLEV],,,[TMPER],[TMOFST];


5 Go to step 3.

Schedule PM Reports 4-147


Schedule Daily PM Report for a Specific Port/Facility

6 Enter SCHED-PMREPT-x::AID:::[REPTINVL],[REPTSTATM],[NUMREPT],[MONTYPE],[MONLEV],,,[TMPER],[TMOFST];

where:x=Facility type (EC1, GIGE, OC3, OC12, OC48, OC192, OFA, STS1, STS3C, STS12C, STS48C, T1, T3, or VT1).AID=Facility Access IdentifierOther parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

7 Go to step 3.

Disable PM Report

8 Select option.

To disable PM reports for all facilities, go to step 9.To disable PM reports for specific facilities, go to step 11.

9 Enter INH-PMREPT-COM;

10 Go to step 3.

11 Enter INH-PMREPT-x::AID;


12 Go to step 3.

Enable PM Report

13 Select option.

To enable PM reports for all facilities, go to step 9.To enable PM reports for all facilities, go to step 16.To enable PM reports for specific facilities, go to step 11.

14 Enter ALW-PMREPT-ALL;

15 Go to step 3.

16 Enter ALW-PMREPT-COM;

Schedule PM Reports4-148


17 Go to step 3.

18 Enter ALW-PMREPT-x::AID;


19 Go to step 3.


Schedule PM Reports 4-149


Schedule PM Reports4-150


DLP-134Report DS3 PM DataPURPOSE

This procedure provides the instructions to report Performance Monitoring (PM) data and initialize (reset) the collection register for DS3 ports.

GENERAL

PM commands operate on provisioned ports only.



STEP PROCEDURE

1 Select action.

To report DS3 PM data with 1677 SONET Link EMA, go to step 2.To report DS3 PM data with TL1, go to step 25.

Report DS3 PM Data with 1677 SONET Link EMA

2 Select action.

To retrieve PM data, go to step 3.To initialize PM data collection register, go to step 10.

Retrieve PM Data


4 Expand the appropriate facility domain (OC3, OC12, OC48, OC192, T3, EC1).


6 Right-click facility and select action.

For 15-Minute data, select Performance Monitoring>View 15-Minute Data.For 1-Day data, select Performance Monitoring>View 1-Day Data.

Report DS3 PM Data 4-151


7 Observe PM information in table.

8 Click Close.

9 Go to step 25.

Initialize PM Data Collection Register


11 Expand the appropriate facility domain (OC3, OC12, OC48, OC192, T3, EC1).



To initialize 15-Minute registers, select Performance Monitoring>Initialize 15-Minute Registers.To initialize 1-Day registers, select Performance Monitoring>Initialize 1-Day Registers.

The appropriate Initialize Register table appears.

14 Under the Monitored Value column, double-click in cell corresponding to Monitored Type value to be changed.

15 Enter new monitored value for the monitored type.

16 Repeat steps 14 and 15 to change Monitored Values for other Monitored Types.

17 Click Apply.

18 Click Close.

19 Go to step 25.

Report DS3 PM Data with TL1

20 Select action.


Report DS3 PM Data4-152


Retrieve PM Data

21 Enter RTRV-PM-T3::[AID]:::[MONTYPE],[MONLEV],,,[TMPER],[MONDAT],[MONTM];


22 Examine output for PM information.

23 Go to step 25.


24 Enter INIT-REG-T3::AID:::[MONTYPE],[MONVAL],[LOCN],,[TMPER];

where:AID=T3 Access IdentifierTMPER=15-MIN or 1-DAYOther parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.




DLP-135Report OC-n PM DataPURPOSE

This procedure provides the instructions to report Performance Monitoring (PM) data and initialize (reset) the collection register for OC-3, OC-12, OC-48, and OC-192 ports.

GENERAL




STEP PROCEDURE

1 Select action.

To report OC-n PM data with 1677 SONET Link EMA, go to step 2.To report OC-n PM data with TL1, go to step 20.

Report OC-n PM Data with 1677 SONET Link EMA

2 Select action.


Retrieve PM Data


4 Expand the appropriate facility domain (OC3, OC12, OC48, OC192).

5 Expand the appropriate facility group.



Report OC-n PM Data 4-155



8 Click Close.

9 Go to step 24.



11 Expand the appropriate facility domain (OC3, OC12, OC48, OC192).

12 Expand the appropriate facility group.







17 Click Apply.

18 Click Close.

19 Go to step 24.

Report OC-n PM Data with TL1

20 Select action.


Report OC-n PM Data4-156


21 Enter RTRV-PM-OCn::[AID]:::[MONTYPE],[MONLEV],,,[TMPER],[MONDAT],[MONTM];

where:OCn=Optical facility type (OC3, OC12, OC48, or OC192).Parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.


23 Enter INIT-REG-OCn::AID:::[MONTYPE],[MONVAL],[LOCN],,[TMPER];

where:OCn=Optical facility type (OC3, OC12, OC48, or OC192).AID=OCn Access IdentifierTMPER=15-MIN or 1-DAYOther parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.


Report OC-n PM Data 4-157


Report OC-n PM Data4-158


DLP-136Report STS-n PM DataPURPOSE

This procedure provides the instructions to report Performance Monitoring (PM) data and initialize (reset) the collection register for STS-1, STS-3c, STS-12c, and STS-48c ports.

GENERAL




STEP PROCEDURE

1 Select action.

To report STS-n PM data with 1677 SONET Link EMA, go to step 2.To report STS-n PM data with TL1, go to step 20.

Report STS-n PM Data with 1677 SONET Link EMA

2 Select action.


Retrieve PM Data


4 Expand the appropriate facility domain (EC1, OC3, OC12, OC48, OC192).




Report STS-n PM Data 4-159



8 Click Close.

9 Go to step 24.











17 Click Apply.

18 Click Close.

19 Go to step 24.

Report STS-n PM Data with TL1

20 Select action.


Report STS-n PM Data4-160


Retrieve PM Data

21 Enter RTRV-PM-STSn::[AID]:::[MONTYPE],[MONLEV],,,[TMPER],[MONDAT],[MONTM];

where:STSn=Signal type (STS1, STS3C, STS12C, or STS48C).Parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.



23 Enter INIT-REG-STSn::AID:::[MONTYPE],[MONVAL],[LOCN],,[TMPER];

where:STSn=Signal type (STS1, STS3C, STS12C, or STS48C).AID=STSn Access IdentifierTMPER=15-MIN or 1-DAYOther parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.


Report STS-n PM Data 4-161


Report STS-n PM Data4-162


DLP-137Report VT1.5 PM DataPURPOSE

This procedure provides the instructions to report Performance Monitoring (PM) data and initialize (reset) the collection register for VT1.5 ports.

GENERAL


PM commands are used to monitor defect conditions, and can be used to track system efficiency. By tracking efficiency, users can recognize gradual deterioration of system performance.


STEP PROCEDURE

1 Select action.

To report VT1.5 PM data with 1677 SONET Link EMA, go to step 2.To report VT1.5 PM data with TL1, go to step 20.

Report VT1.5 PM Data with 1677 SONET Link EMA

2 Select action.


Retrieve PM Data






Report VT1.5 PM Data 4-163



8 Click Close.

9 Go to step 25.











17 Click Apply.

18 Click Close.

19 Go to step 25.

Report VT1.5 PM Data with TL1

20 Select action.


Report VT1.5 PM Data4-164


Retrieve PM Data

21 Enter RTRV-PM-VT1::[AID]:::[MONTYPE],[MONLEV],,,[TMPER],[MONDAT],[MONTM];



23 Go to step 25.


24 Enter INIT-REG-VT1::AID:::[MONTYPE],[MONVAL],[LOCN],,[TMPER];

where:AID=VT1 Access IdentifierTMPER=15-MIN or 1-DAYOther parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.


Report VT1.5 PM Data 4-165


Report VT1.5 PM Data4-166


DLP-138Set DS3 PM ModePURPOSE

This procedure provides the instructions to set or change Performance Monitoring (PM) mode for DS3 ports. The PM mode controls the data collection for specific types of PM data (path, line, segment, intermediate node).

GENERAL




STEP PROCEDURE

1 Select action.

To set T3 PM mode with 1677 SONET Link EMA, go to step 2.To set T3 PM mode with TL1, go to step 11.

Set T3 PM Mode with 1677 SONET Link EMA




5 Right-click appropriate T3 facility and select Performance Monitoring>PM Mode. Current PM mode parameters are displayed in the table.




Set DS3 PM Mode 4-167





8 Click Apply.

9 Click Close.

10 Go to step 14.

Set T3 PM Mode with TL1

11 Enter RTRV-PMMODE-T3::AID:::[LOCN];

where:AID=T3 Access IdentifierLOCN={ALL, FEND, NEND}


13 Enter SET-PMMODE-T3::AID:::LOCN,ALL,[PMSTATE];

where:AID=T3 Access IdentifierLOCN={ALL, FEND, NEND}PMSTATE={OFF, ON}


Set DS3 PM Mode4-168


DLP-139Set OC-n PM ModePURPOSE

This procedure provides the instructions to set or change Performance Monitoring (PM) mode for OC-n ports. The PM mode controls the data collection for specific types of PM data (path, line, segment, intermediate node).

GENERAL




STEP PROCEDURE

1 Select action.

To set OC-n PM mode with 1677 SONET Link EMA, go to step 2.To set OC-n PM mode with TL1, go to step 11.

Set OC-n PM Mode with 1677 SONET Link EMA


3 Expand appropriate OC-n domain.

4 Expand appropriate facility group to display OC-n facilities.

5 Right-click appropriate OC-n facility and select Performance Monitoring>PM Mode. Current PM mode parameters are displayed in the table.




Set OC-n PM Mode 4-169





8 Click Apply.

9 Click Close.

10 Go to step 14.

Set OC-n PM Mode with TL1

11 Enter RTRV-PMMODE-OCn::AID:::[LOCN];

where:OCn=Optical facility type (OC3, OC12, OC48, or OC192).AID=OCn Access IdentifierLOCN={ALL, FEND, NEND}


13 Enter SET-PMMODE-OCn::AID:::LOCN,ALL,[PMSTATE];

where:OCn=Optical facility type (OC3, OC12, OC48, or OC192).AID=OCn Access IdentifierLOCN={ALL, FEND, NEND}PMSTATE={OFF, ON}


Set OC-n PM Mode4-170


DLP-140Set STS-n PM ModePURPOSE

This procedure provides the instructions to set or change Performance Monitoring (PM) mode for STS-n ports. The PM mode controls the data collection for specific types of PM data (path, line, segment, intermediate node).

GENERAL




STEP PROCEDURE

1 Select action.

To set STS-n PM mode with 1677 SONET Link EMA, go to step 2.To set STS-n PM mode with TL1, go to step 14.

Set STS-n PM Mode with 1677 SONET Link EMA




5 Right-click appropriate STS-n facility and select Performance Monitoring>PM Mode. Current PM mode parameters are displayed in the table.




Set STS-n PM Mode 4-171





8 Click Apply.

9 Click Close.

10 Go to step 14.

Set STS-n PM Mode with TL1

11 Enter RTRV-PMMODE-STSn::AID:::[LOCN];

where:STSn=Signal type (STS1, STS3C, STS12C, or STS48C).AID=STSn Access IdentifierLOCN={ALL, FEND, NEND}


13 Enter SET-PMMODE-STSn::AID:::LOCN,MODETYPE,[PMSTATE];

where:STSn=Signal type (STS1, STS3C, STS12C, or STS48C).AID=STSn Access IdentifierLOCN={ALL, FEND, NEND}MODETYPE={ALL, P}PMSTATE={OFF, ON}


Set STS-n PM Mode4-172


DLP-141Set VT1.5 PM ModePURPOSE

This procedure provides the instructions to set or change Performance Monitoring (PM) mode for VT1.5 ports. The PM mode controls the data collection for specific types of PM data (path, line, segment, intermediate node).

GENERAL




STEP PROCEDURE

1 Select action.

To set VT1.5 PM mode with 1677 SONET Link EMA, go to step 2.To set VT1.5 PM mode with TL1, go to step 11.

Set VT1.5 PM Mode with 1677 SONET Link EMA



4 Expand facility groups and instances until appropriate facility is displayed.

5 Right-click appropriate VT1.5 facility and select Performance Monitoring>PM Mode. Current PM mode parameters are displayed in the table.




Set VT1.5 PM Mode 4-173





8 Click Apply.

9 Click Close.

10 Go to step 14.

Set VT1.5 PM Mode with TL1

11 Enter RTRV-PMMODE-VT1::AID:::[LOCN];

where:AID=VT1 Access IdentifierLOCN={ALL, FEND, NEND}


13 Enter SET-PMMODE-VT1::AID:::LOCN,MODETYPE,[PMSTATE];

where:AID=VT1 Access IdentifierLOCN={ALL, FEND, NEND}MODETYPE={ALL, P}PMSTATE={OFF, ON}


Set VT1.5 PM Mode4-174


DLP-142Set DS3 PM Threshold LevelsPURPOSE

This procedure provides the instructions to set Performance Monitoring (PM) threshold levels for DS3 ports.

GENERAL



The SET-TH-T3 command is used to designate PM threshold levels for DS3 ports. For each type of error (parameter) being monitored, a threshold level with either a 15-minute or 24-hour period may be set. If the number of errors collected exceeds the threshold level within the time selected, the system generates a Threshold Crossing Alert (TCA).


STEP PROCEDURE

1 Select action.

To set DS3 PM threshold levels with 1677 SONET Link EMA, go to step 2.To set DS3 PM threshold levels with TL1, go to step 11.

Set DS3 PM Threshold Levels with 1677 SONET Link EMA




5 Right-click appropriate facility and select action.

To set 15-Minute thresholds, select Performance Monitoring>15-Minute Thresholds.

Set DS3 PM Threshold Levels 4-175


To set 1-Day thresholds, select Performance Monitoring>1-Day Thresholds.

The appropriate PM threshold table appears.

6 Double-click in the cell under the Threshold Level column corresponding to the monitored parameter type and location to be modified and enter new value.

7 Repeat step 6 for all monitored parameter types and locations to be modified.

8 Click Apply.

9 Click Close.

10 Go to step 14.

Set DS3 PM Threshold Levels with TL1

11 Enter RTRV-TH-T3::[AID]:::[MONTYPE],,[TMPER];


12 Examine output for threshold information.

13 Enter SET-TH-T3::AID:::MONTYPE,THLEV,,,[TMPER];

where:AID=T3 Access IdentifierMONTYPE=Monitored type. See Commands and Messages manual (PN 3EM13852AD) for possible values.THLEV={DFLT, (0-1048575)}TMPER={15-MIN, 1-DAY}


Set DS3 PM Threshold Levels4-176


DLP-143Set OC-n PM Threshold LevelsPURPOSE

This procedure provides the instructions to set Performance Monitoring (PM) threshold levels for OC-n ports.

GENERAL



The SET-TH-OCn command is used to designate PM threshold levels for OC-n ports. For each type of error (parameter) being monitored, a threshold level with either a 15-minute or 24-hour period may be set. If the number of errors collected exceeds the threshold level within the time selected, the system generates a Threshold Crossing Alert (TCA).


STEP PROCEDURE

1 Select action.

To set OCn PM threshold levels with 1677 SONET Link EMA, go to step 2.To set OCn PM threshold levels with TL1, go to step 11.

Set OCn PM Threshold Levels with 1677 SONET Link EMA






Set OC-n PM Threshold Levels 4-177






8 Click Apply.

9 Click Close.

10 Go to step 14.

Set OCn PM Threshold Levels with TL1

11 Enter RTRV-TH-OCn::[AID]:::[MONTYPE],,[TMPER];

where:OCn=Optical facility type (OC3, OC12, OC48, or OC192).Parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.


13 Enter SET-TH-OCn::AID:::MONTYPE,THLEV,,,[TMPER];

where:OCn=Optical facility type (OC3, OC12, OC48, or OC192).AID=OCn Access IdentifierMONTYPE=Monitored type. See Commands and Messages manual (PN 3EM13852AD) for possible values.THLEV={DFLT, (0-1048575)}TMPER={15-MIN, 1-DAY}


Set OC-n PM Threshold Levels4-178


DLP-144Set STS-n PM Threshold LevelsPURPOSE

This procedure provides the instructions to set Performance Monitoring (PM) threshold levels for STS-n ports.

GENERAL



The SET-TH-STSn command is used to designate PM threshold levels for STS-n ports. For each type of error (parameter) being monitored, a threshold level with either a 15-minute or 24-hour period may be set. If the number of errors collected exceeds the threshold level within the time selected, the system generates a Threshold Crossing Alert (TCA).


STEP PROCEDURE

1 Select action.

To set STSn PM threshold levels with 1677 SONET Link EMA, go to step 2.To set STSn PM threshold levels with TL1, go to step 11.

Set STSn PM Threshold Levels with 1677 SONET Link EMA






Set STS-n PM Threshold Levels 4-179






8 Click Apply.

9 Click Close.

10 Go to step 14.

Set STSn PM Threshold Levels with TL1

11 Enter RTRV-TH-STSn::[AID]:::[MONTYPE],,[TMPER];

where:STSn=Facility type (STS1, STS3C, STS12C, or STS48C).Parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.


13 Enter SET-TH-STSn::AID:::MONTYPE,THLEV,,,[TMPER];

where:STSn=Facility type (STS1, STS3C, STS12C, or STS48C).AID=STSn Access IdentifierMONTYPE=Monitored type. See Commands and Messages manual (PN 3EM13852AD) for possible values.THLEV={DFLT, (0-1048575)}TMPER={15-MIN, 1-DAY}


Set STS-n PM Threshold Levels4-180


DLP-145Set VT1.5 PM Threshold LevelsPURPOSE

This procedure provides the instructions to set Performance Monitoring (PM) threshold levels for VT1.5 ports.

GENERAL



The SET-TH-VT1 command is used to designate PM threshold levels for VT1.5 ports. For each type of error (parameter) being monitored, a threshold level with a 15-minute period may be set. If the number of errors collected exceeds the threshold level within the time selected, the system generates a Threshold Crossing Alert (TCA).


STEP PROCEDURE

1 Select action.

To set VT1 PM threshold levels with 1677 SONET Link EMA, go to step 2.To set VT1 PM threshold levels with TL1, go to step 11.

Set VT1 PM Threshold Levels with 1677 SONET Link EMA






Set VT1.5 PM Threshold Levels 4-181






8 Click Apply.

9 Click Close.

10 Go to step 14.

Set VT1 PM Threshold Levels with TL1

11 Enter RTRV-TH-VT1::[AID]:::[MONTYPE],,[TMPER];



13 Enter SET-TH-VT1::AID:::MONTYPE,THLEV,,,[TMPER];

where:AID=VT1 Access IdentifierMONTYPE=Monitored type. See Commands and Messages manual (PN 3EM13852AD) for possible values.THLEV={DFLT, (0-1048575)}TMPER={15-MIN, 1-DAY}


Set VT1.5 PM Threshold Levels4-182


DLP-146Add New User to SystemPURPOSE

This procedure provides the instructions to create a new user's profile in for a specified User Identification (UID).

GENERAL

Only a user with the security privilege can create a user profile entry. If ENT-USER-SECU executes successfully, the system accepts any association of the UID with a TCP/IP port number and server IP address. The 1677 SONET Link uses port 3083 for telnet port and port 3082 for raw port.


STEP PROCEDURE

1 Select action.

To add new user profile with 1677 SONET Link EMA, go to step 2.To add new user profile with TL1, go to step 10.

Add New User Profile with 1677 SONET Link EMA

2 Expand System domain.

3 Expand NE Security domain.

4 Right-click on Users domain and select Create User. The Create User wizard appears.



7 On Finish page, verify chosen options.

8 Click Finish.

9 Go to step 12.

Add New User to System 4-183


Add New User Profile with TL1

10 Enter ENT-USER-SECU::UID:::PID,,UAP:[PAGE=];

where:UID=User IDPID=Password IDUAP=User access privilege {CONF, NETADMIN, PROV, READ, SEC, TEST}

11 Enter RTRV-USER-SECU::[UID]; to verify the user profile information.

where:UID=User ID


Add New User to System4-184


DLP-147Delete User from SystemPURPOSE

This procedure provides the instructions to delete a user's profile for a specified User Identification (UID).

PREREQUISITE

The UID must be known before it can be deleted.

GENERAL

Only the system administrator can delete a user profile entry. If DLT-USER executes successfully, the system deletes any association of the UID with a TCP/IP port number and server IP address.


STEP PROCEDURE

1 Select action.

To delete user with 1677 SONET Link EMA, go to step 2.To delete user with TL1, go to step 8.

Delete User with 1677 SONET Link EMA

2 Expand System domain.

3 Expand NE Security domain.

4 Click on Users domain to display all existing user profiles.

5 Right-click on appropriate user profile and select Delete.

6 Click Yes.

7 Go to step 10.

Delete User from System 4-185


Delete User with TL1

8 Enter RTRV-USER-SECU::[UID]; to verify user profile information.

where:UID=User ID

9 Enter DLT-USER-SECU::UID;

where:UID=User ID


Delete User from System4-186


DLP-148Administer STS-n Test Access ConnectionsPURPOSE

This procedure provides the instructions to retrieve information on, connect, and disconnect Test Access (TACC) connections used to test STS-n ports (and T3 and EVC ports if STS-1 test access connection).

PREREQUISITES

A CONN-TACC-STSn command must be administered before a CHG-ACCMD-STSn command will be accepted.

Test access port pairs are not allowed on OC-192 interfaces.

If a test access port pair is provisioned on an OC-n facility, the OC-n facility must be unprotected.

The maximum number of T3/STS1/STS3C/STS12C/STS48C test access connections supported in a system is six.

T3/STS-level test access connections require the redundant SSC.

GENERAL

Test access connections route signals from the system-designated Test Access Port (TAP) to external test equipment. Various test modes configure various connections between equipment and ports.

When an STSn is defined as a test access port (TACC=Y), the two ports identified by AID and TADB in the ENT-STSn command are both provisioned as a Test Access Port Pair (TAPP). When using ED-STSn to change the provisioning of a TAPP, either of the AIDs for TAD A or TAD B can be specified as the AID in the command and the provisioning changes are applied to both the TAD A and TAD B ports. The STSMAP value of a TAPP port must be set to ALL and can not be changed.

CONN-TACC-STSn connects a test access port to a specified STSn port (or EVC or T3 port if CONN-TACC-STS1) in the specified test access mode. The available test access modes for a test access port connection are MONE, MONEF, MONF, SPLTA, SPLTB, SPLTE, SPLTEF, SPLTF, LOOPE, or LOOPF.

CHG-ACCMD-STSn modifies the test access mode of STSn test access connections.

RTRV-TACC retrieves the port AIDs for Test Access Port Pairs (TAPPs) within the specified range of AIDs, or within all AIDs if AID is left blank. If the TAPPs are connected for test access, the Equipment side port AID, any Facility side port AID, the test access mode, and the user session link association is also retrieved. Along with this information may be the user id of the user owning and/or controlling the TAPP. The command is executed regardless of the provisioning of the specified ports.

Administer STS-n Test Access Connections 4-187



STEP PROCEDURE

1 Enter RTRV-TACC::[AID]::::[TYPE=][,UID=];

where:AID=STSn access identifier of TAP (TAD A or TAD B), equipment-side port being tested, or facility-side port being tested.TYPE=Type of test access connection (STS1, STS3C, STS12C, or STS48C)UID=(ALL, MYSELF)

2 Examine output.

ACTIVE=Y test access connection is active. ACTIVE=N indicates test access connection is inactive.

3 Enter RTRV-STSn::[AID]; to verify status of possible TAPs.

where:STSn=Facility type (STS1, STS3C, STS12C, or STS48C)AID=STSn access identifier

4 Examine output.

TACC=Y indicates a TAP is established. SST=BUSY&TS indicates an established TAP is being used in a test access connection.

5 Select action.

To provision an STS-n port as a TAP, go to step 6.To modify provisioning of a TAP, go to step 8.To create a test access connection, go to step 13.To change test access mode of TACC connection, go to step 15.To disconnect TACC connection, go to step 17.To end procedure, go to step 19.

Administer STS-n Test Access Connections4-188


Provision an STS-n Port as a TAP

6 Enter ENT-STSn::AID::::,STSMAP=ALL,TACC=Y,TADB=:OOS; to provision TAPP.

where:STSn=Facility type (STS1, STS3C, STS12C, or STS48C)AID=STSn access identifier of TAD A port in TAPPTADB=STSn access identifier of TAD B port in TAPP (AID selected must be an available STSn port. It will be provisioned with same parameters as AID.)

7 Go to step 5.

Modify TAP

CAUTION: Possibility of service interruption. Do not edit a traffic-carrying port out of service. If a port is busy in a test aconnection (SST=BUSY&TS), use another test access port pair.

8 Select option.

To modify STS-1 TAP, go to step 9.To modify STS-3c, STS-12c, or STS-48c TAP, go to step 11.

9 Enter ED-STS1::AID::::[CKTID=][,STSMAP=][,TRC=][,EXPTRC=][,ENBTXPDIP=][,ENBTXRDIP=][,ENBTIMP=][,ENBPDIP=][,SDTH=][,SFTH=]:[PST][,SST];

where:AID=STS-1 access identifier (TAD A or TAD B)Other parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

10 Go to step 5.

11 Enter ED-STSn::AID::::[CKTID=][,STSMAP=][,EXPTRC=][,ENBTIMP=][,SDTH=][,SFTH=]:[PST],[SST];

where:STSn=Facility type (STS1, STS3C, STS12C, or STS48C)AID=STSn access identifier (either TAD A or TAD B)Other parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

12 Go to step 5.

Administer STS-n Test Access Connections 4-189


Create Test Access Connection

CAUTION: Possibility of service interruption. CONN-TACC-STSn executed with a mode of LOOPE, LOOPF, SPLTA, SPLTB, SPLTE, SPLTEF, or SPLTF affects service and interrupts traffic.

13 Enter CONN-TACC-STSn::AID:::TAP:MD:[AID1]:[LA];

where:STSn=Facility type (STS1, STS3C, STS12C, or STS48C)AID=Identifies the equipment-side STSn port to be tested (Can also include EVC or T3 port if CONN-TACC-STS1 is used.)TAP=STSn access identifier of TAD A (first port in test access port pair)MD=Test access modeOther parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

14 Go to step 5.

Change Test Access Mode

CAUTION: Possibility of service interruption. CHG-ACCMD-STSn executed with a mode of LOOPE, LOOPF, SPLTA, SPLTB, SPLTE, SPLTEF, or SPLTF affects service and interrupts traffic.

15 Enter CHG-ACCMD-STSn::AID:::MD;

where:STSn=Facility type (STS1, STS3C, STS12C, or STS48C)AID=STSn access identifier of TAD A (first port in test access port pair)MD=Test access mode

16 Go to step 5.

Disconnect TACC Connection

17 Enter DISC-TACC::AID;

where:AID=STSn access identifier of TAD A (first port in test access port pair)

18 Go to step 5.


Administer STS-n Test Access Connections4-190


DLP-149Switch STS-n Path to ProtectionPURPOSE

This procedure provides the instructions to initiate and release an STS-n path switch to protection.

This procedure is used for UPSR and DRI configurations.

PREREQUISITES

STS-n facilities must be provisioned. Refer to DLP-117 to provision STS-n.

STS-n facilities must be provisioned as a facility protection group. Refer to DLP-199.

OC-n facilities that support the STS-n must be provisioned for UPSR. Refer to DLP-151.

GENERAL

OPR-PROTNSW-STSn command initiates external switch requests for paths involved in 2WAYDC, 2WAY single node UPSR connection and 2WAYDC and 2WAY dual ring interconnection connections. The command requests the system to switch the path selector to the Preferred or Alternate path of the FFP. User switch requests initiated with this command remain active until they are released via the RLS-PROTNSW-STSn command or overridden by a higher priority protection switch request.

When initiating a protection switch using OPR-PROTNSW-STSn, five options for the switch command (SWTCHCMD) parameter are available: FRCDWKSWBK, FRCDWKSWPR, LOCKOUT, MANWKSWBK, and MANWKSWPR.

• Lockout of Protection (LOCKOUT) keeps traffic on the preferred path. If traffic is on the non-preferred path when the command is issued, traffic switches to the preferred path and remains there until the lockout is released. A Lockout overrides a Forced Switch and a Manual Switch.

• Forced Switch forces traffic from preferred path to non-preferred path (FRCDWKSWPR) or non-preferred path to preferred (FRCDWKSWBK). A Forced Switch overrides a Manual Switch.

• Manual Switch moves traffic from preferred path to non-preferred path (MANWKSWPR) or non-preferred path to preferred path (MANWKSWBK).


Switch STS-n Path to Protection 4-191


STEP PROCEDURE

1 Select action.

To switch STS-n path to protection with 1677 SONET Link EMA, go to step 2.To switch STS-n path to protection with TL1, go to step 36.

Switch STS-n Path to Protection with 1677 SONET Link EMA

2 Select action.

To retrieve information on STS-n facilities and FFP, go to step 3.To retrieve STS-n cross-connections, go to step 14.To perform STS-n switch to protection, go to step 19.To release STS-n switch to protection, go to step 29.To end this procedure, go to step 50.

Retrieve Information on STS-n Facilities and FFP




6 Select appropriate OC-n facility and select Refresh.

7 Observe appropriate STS-n facility in Result Pane and note states.



10 Expand the appropriate OC-n protection range.

11 Select appropriate OC-n protection pair to display current STS-n protection pairs in the Result Pane.

12 Observe FFP information for appropriate STS-n protection pair in Result Pane.

13 Go to step 2.

Retrieve STS-n Cross-Connections


Switch STS-n Path to Protection4-192





18 Go to step 2.

Perform STS-n Protection Switch





23 Right-click appropriate STS-n protection pair and select Operate Switch. The Operate Protection Switch wizard appears.




27 Click Finish.

28 Go to step 50.

Release STS-n Protection Switch





33 Right-click appropriate STS-n protection pair and select Release Switch.

34 Click Release.



35 Go to step 2.

Switch STS-n Path to Protection with TL1

36 Select action.

To retrieve information on STS-n facilities and FFP, go to step 37.To retrieve STS-n cross-connections, go to step 43.To perform STS-n switch to protection, go to step 46.To release STS-n switch to protection, go to step 48.To end this procedure, go to step 50.

Retrieve Information on STS-n Facilities and FFP

37 Enter RTRV-STSn::[AID]; from Command Tree Panel.

where:STSn=Facility type (STS1, STS3C, STS12C, or STS48C)AID=STSn access identifier

38 Examine output. Note states and other pertinent information.

39 Is facility an STS-1?


40 Enter RTRV-FFP-STS1::[AID];

where:AID=STS-1 access identifier

41 Examine output. One line of output is returned for each specified STS-1, regardless of whether the STS-1 is part of an FFP.

42 Go to step 36.

Retrieve STS-n Cross-Connections

43 Enter RTRV-CRS-STSn::AID:::[CCT];

where:STSn=Facility type (STS1, STS3C, STS12C, or STS48C)AID=STSn access identifierCCT=(2WAY, 2WAYDC, SRIW, THRU)

44 Examine output. Note active cross-connections.



45 Go to step 36.

Perform STS-n Protection Switch

46 Enter OPR-PROTNSW-STSn::AID:::SWTCHCMD;

where:STSn=Facility type (STS1, STS3C, STS12C, or STS48C)AID=STSn access identifierSWTCHCMD=Switching command (FRCDWKSWBK, FRCDWKSWPR, LOCKOUT, MANWKSWBK, MANWKSWPR)

47 Go to step 36.

Release STS-n Protection Switch

48 Enter RLS-PROTNSW-STSn::AID;

where:STSn=Facility type (STS1, STS3C, STS12C, or STS48C)AID=Protected STSn access identifier

49 Go to step 36.




DLP-150Clean Fiber-Optic ConnectorsPURPOSE

This procedure provides the recommended instructions to clean fiber-optic connectors found in Alcatel equipment.

PREREQUISITE

Anyone who performs this procedure must be familiar with cleaning fiber-optic connectors and with the specific system on which the procedure is to be performed.

This procedure must not be performed on traffic-carrying equipment. If a system is in service, traffic must be removed from equipment to be cleaned.

RECOMMENDED TOOLS

The following tools must be available for this procedure:

• Optical power meter with standard accessories

• Optical power meter adapter

– Spider, MPX-to-SC, 2-meter, single-mode, 8-fiber—AMP 492328-2

– Spider, MPX-to-SC, 2-meter, multimode, 8-fiber—AMP 97-A169-62-2

• Inspection microscope, 200X to 400X—Aerotech World Trade Ltd. AWT200 or AWT300

• Inspection microscope tip

– MPX tip—Aerotech World Trade Ltd. AWT-MPX

– MPX backplane tip—Aerotech World Trade Ltd. AWT-MPXAPC

• Lint-free wiper—Texwipe TX304, Alcatel PN 1553366020

• Anti-static lint-free swab—Texwipe TX757E, Alcatel PN 1552762010

• CLETOP1 fiber-optic cleaner

– Aerotech World Trade Ltd. PN 14100500 for all fiber-optic connectors

1. CLETOP is a registered trademark of NTT International.

Clean Fiber-Optic Connectors 4-197


• CLETOP swab

– Aerotech World Trade Ltd. PN 14100400 for all fiber-optic connectors except mini-SC and LC, Alcatel PN 1553366010

– Aerotech World Trade Ltd. PN 14100401 for mini-SC and LC fiber-optic connectors

• Optical removal and cleaning tool—Alcatel PN 3EM07060AAAA

• Penlight (pocket-style flashlight)

• Laser safety glasses

GENERAL

If the cleaning method described in this procedure does not produce acceptable results, connector may need to be replaced.

STEP PROCEDURE

1 DANGER: Possibility of personal injury. DO NOT LOOK INTO FIBER-OPTIC CONNECTOR. Laser infrared radiation is present when fiber-optic connector is open and optical interface is installed. Laser infrared radiation is not visible to naked eye or with laser safety glasses.

2 DANGER: Possibility of personal injury. Ensure no optical power is connected to fiber being tested. An optical power meter must be used to ensure all optical power has been removed.

3 WARNING: Possibility of equipment damage. Do not disassemble modules to clean fibers. Disassembling module could cause damage to optical splice and could void warranty.

4 WARNING: Possibility of equipment damage. To preserve integrity of fiber-optic connectors, observe the following precautions:

-Do not use cleaning swabs more than once.

-Do not use alcohol or any type of liquid to clean fiber-optic connectors.

-Do not use canned air to clean fiber-optic connectors. Canned air propellant leaves residue that clouds fiber-optic connectors.

-Do not touch polished optical surface of fiber-optic connector. Oil from skin can degrade performance of fiber-optic connector and attract dust particles.

Clean Fiber-Optic Connectors4-198


-Always use protective covers to protect disconnected fiber-optic connectors. When protective covers are not in use, store them in a clean container. Do not store protective covers in clothes pocket.

5 Use optical power meter to determine if light is coming out of fiber-optic connector.

6 Did optical power meter detect light coming out of fiber-optic connector?

If yes, find source and disconnect it, then go to step 7.If no, go to step 7.

7 Remove fiber-optic connector from receptacle, if necessary.

8 Use inspection microscope to inspect fiber-optic connector. See figure 150-1 for examples of clean and contaminated fibers. Note that MPX connector has multiple fibers. Use the following criteria to determine clean fiber:

a. Fiber core must have no contaminants or defects.

b. Fiber cladding must have no contaminants. Minor defects (pits and scratches) are acceptable.

c. Fiber ferrule may not have contaminants or defects that interfere with fiber-optic connector mating.

9 Is fiber-optic connector clean?


10 Select type of connector to clean. For illustrations and photographs of connector types, see figures 150-2 and 150-3, respectively.

If nonbackplane-mounted MPX fiber-optic connector, go to step 11.If backplane-mounted MPX fiber-optic connector, go to step 13.If FC, SC, mini-SC, LC, or ST/STII fiber-optic connector, go to step 21.

Nonbackplane-Mounted MPX Fiber-Optic Connector

11 Do not touch tip of TX757E swab.

Use TX757E swab to clean fiber-optic connector by swiping once between two metal alignment pins, then discard swab.

12 Go to step 30.



Backplane-Mounted MPX Fiber-Optic Connector

13 Do not touch tip of TX757E swab.

Insert swab handle into swab optical cleaning tool (extender). See figure 150-4.

Figure 150-1. Fiber-Optic Connector Inspection

FIBER CONTAMINATED WITH SOLID PARTICLES

PARTICLES

FIBER CONTAMINATED WITH OIL (FINGERPRINT)

CLEAN FIBER

OIL FILM AND PARTICLESON CLADDING AND INCORE AREA

FIBER

CLADDING CORE

129-1280-1040302

FERRULE(SHAPE CAN VARYBY CONNECTOR TYPE)



14 WARNING: Possibility of equipment damage. Use care to prevent damaging backplane-mounted fiber-optic connector pins when cleaning backplane-mounted fiber-optic connectors.

Figure 150-2. Fiber-Optic Connector Types, Illustrations

END VIEWS

MPX CONNECTOR

MALEFEMALE

SIDE VIEWSIDE VIEW

MINI SC FIBER CONNECTOR

LC FIBER CONNECTOR

ST CONNECTOR

SC CONNECTORFC CONNECTOR

129-1281-1031504



15 Use penlight to light backplane-mounted fiber-optic connector.

16 Is fiber-optic connector top mounted or bottom mounted?

If top mounted, go to step 17.If bottom mounted, go to step 18.

17 Clean fiber-optic connector by swiping fiber ferrule once from top to bottom, discard TX757E swab, then go to step 19.

18 Clean fiber-optic connector by swiping fiber ferrule once from bottom to top, discard TX757E swab, then go to step 19.

19 Insert TX757E swab into bulkhead (barrel) receptacle and rotate swab, sliding it in and out to clean inside of receptacle, then discard swab.

20 Go to step 30.

Figure 150-3. Fiber-Optic Connector Types, Photographs

SC CONNECTOR FC CONNECTOR

ST/STII CONNECTOR

MPX CONNECTORS

FEMALE MALE

160-2973-1

022802



FC, SC, Mini-SC, LC, or ST/STII Fiber-Optic Connector

21 Select desired method for cleaning FC, SC, mini-SC, LC, or ST/STII fiber-optic connector:

For CLETOP method, go to step 22.For wiper method, go to step 26.

22 Holding CLETOP fiber-optic cleaner with one hand, use metal lever to open metal slide and expose cleaning surface. Do not release lever.

Figure 150-4. Optical Removal and Cleaning Tool (PN 3EM07060AAAA)

160-2974-1041102



23 Place fiber ferrule firmly against CLETOP fiber-optic cleaner cleaning surface, rotate ferrule 90 degrees, then swipe ferrule along cleaning surface one time in one direction only.

24 Release metal lever.

25 Go to step 28.

26 Place TX304 wiper on hard, flat surface and hold with one hand.

27 Place fiber ferrule on TX304 wiper and gently rub in figure-8 pattern one time only.

28 Insert CLETOP swab into bulkhead (barrel) receptacle and rotate swab, sliding it in and out to clean inside of receptacle, then discard swab.

29 Go to step 30.

Inspect Connector

30 Use inspection microscope to inspect fiber-optic connector. See figure 150-1 for examples of clean and contaminated fibers. Note that MPX connector has multiple fibers. Use the following criteria to determine clean fiber:

a. Fiber core must have no contaminants or defects.

b. Fiber cladding must have no contaminants. Minor defects (pits and scratches) are acceptable.

c. Fiber ferrule may not have contaminants or defects that interfere with fiber-optic connector mating.



32 Clean and inspect fiber-optic connector up to five more times.


If yes, go to step 34.If no, contact next level of support.

34 Remove permanent plastic cap retainer, if applicable. Follow customer practices.



35 Are there more fiber-optic connectors to clean?





DLP-151Administer OC-n UPSRPURPOSE

This procedure provides the instructions to retrieve information on, provision, and deprovision a Unidirectional Path Switched Ring (UPSR) in which two fibers are used to transport traffic between nodes of a ring. Add/drop traffic at the 1677 SONET Link ring node is connected to other facilities through the 1677 SONET Link matrix.

PREREQUISITES

Two OC-3, OC-12, OC-48, or OC-192 facilities must be provisioned as a UPSR pair using the ENT-FFP-OCn command before path protection groups can be established.

GENERAL

ENT-FFP-OCn will execute if a pair of OC-n facilities in adjacent slots (that is, 1 and 2, 3 and 4, 5 and 6, 12 and 13, 14 and 15, or 16 and 17) of the 1677 SONET Link node have been previously provisioned, and are not currently operating as a 1+1 APS protection group. The pair of OC-n facilities must be on the same port of each slot (for example, OC3-1-A-1,OC3-2-A-1).

The valid AID values for OC-n facilities PROTECTED_ID and PROTECTING_ID using the ENT-FFP-OCn are listed in table 151-A.


The 1677 SONET Link node supports up to 144 UPSR rings (if only OC-3 facilities are used).

Table 151-A. OC-n UPSR Nodes PROTECTED_ID and PROTECTING_ID PairsOC-n UPSR PROTECTED_ID AND PROTECTING_ID PAIRS

PROTECTED_ID AID PROTECTING_ID AIDOC-3 OC3-{1,3,5,12,14,16}-{A,B}-{1-12} OC3-{2,4,6,13,15,17}-{A,B}-{1-12}OC-12 OC12-{1,3,5,12,14,16}-{A,B}-{1-4} OC12-{2,4,6,13,15,17}-{A,B}-{1-4}OC-48 OC48-{1,3,5,12,14,16}-{A,B}-1 OC48-{2,4,6,13,15,17}-{A,B}-1OC-192 OC192-{5,6,12}-AB-1 OC192-{6,12,13}-AB-1

Administer OC-n UPSR 4-207


Features of the UPSR are as follows:

• One to 144 OC-n UPSR rings within the same 1677 SONET Link node.

• OC-n UPSR protection groups may co-exist with other BLSR protection groups, other 1+1 protection groups, or other unprotected OC-n facilities in the same 1677 SONET Link node.

• Each OC-n UPSR node is provided with the following features:

– STS-n paths can be configured using the ENT-CRS-STSn command.

– STS-n paths can be cross-connected between two OC-ns of a UPSR pair as a pass-through connection.

– The working and protection paths of each 2WAY path are monitored. Defects which initiate path switching are: AIS-P, LOP-P, UNEQ-P, EBER-P, SDBER-P, and PDI-P.

– Path switching occurs within 50 msec after a defect is detected. Total switching time will not exceed 60 msecs.

– Nonrevertive and revertive switching are supported.

– External switch commands (OPR-PROTNSW-STSn) can be entered to manually control each path of the UPSR. Refer to DLP-149 for procedures to switch STS-n path from working to protection and protection to working.


STEP PROCEDURE

1 Select action.

To administer OC-n UPSR with 1677 SONET Link EMA, go to step 2.To administer OC-n UPSR with TL1, go to step 35.

Administer OC-n UPSR with 1677 SONET Link EMA

2 Select action.

To provision OC-n UPSR facilities, go to step 3.To deprovision OC-n UPSR facilities, go to step 26.

Administer OC-n UPSR4-208


Provision OC-n UPSR Facilities







9 Click Finish.

10 Repeat steps 5 through 9 to provision OC-n facility in protection slot.

11 Are additional OC-n facilities to be provisioned?

If yes, repeat steps 5 through 10 until all appropriate OC-3/OC-12 facilities have been provisioned.If no, go to step 12.





15 On the Protection Type page, select UPSR from the drop-down list.

16 Click Next.



19 Click Finish.



20 When an STS-n entity in the working slot is provisioned, the associated STS-n entity having the same port number is automatically provisioned in the protection slot with the same parameter values.

Provision all STS-n entities in OC-n working slot. Refer to NTP-103.

21 Select action.

If an STS-n pair is to be configured as a THRU connection, go to step 22.If an STS-n pair is to be configured as a 2WAY add/drop connection, go to step 24.

Configure a Pair of Path Entities as a Pass-Through Connection

22 A THRU connection is established by creating an STS-n cross-connection. The THRU connection occurs when there is an STS-n facility in the working slot and an STS-n in the protection slot, and both slots have the same port number in the AID field.

Establish the THRU connection. To administer cross-connections, refer to DLP-125 with parameter Cross Connect Type=THRU.

23 Select action.

If other pass-through connections are to be established, repeat step 22 for each connection.If no additional THRU connections are required, go to step 57.

Configure 2WAY Cross Connections

24 Create an STS-n connection between FROM and TO parameters. To administer cross-connections terminated add/drop connection to/from the ring, refer to DLP-125 with parameter Cross Connect Type=2WAY.

25 Are additional STS-n 2WAY cross connections to be established?

If yes, repeat step 24 for each STS-n to be established.If no, go to step 57.

Deprovision OC-n UPSR Facilities

26 Delete all pass-through connections by using the Manage CrossConnections option in the CrossConnection domain. Refer to DLP-125.

27 Delete all 2WAY connections by using the Manage CrossConnections option in the CrossConnection domain. Refer to DLP-125.



28 When an STS-n entity in the working slot is removed, the associated STS-n entity having the same port number is automatically removed in the protection slot. Delete all STS-n entities. Refer to NTP-109.

29 To deprovision UPSR node application, expand the Protection domain.



32 Right-click on the appropriate OC-n protection pair and select Delete.

33 In the message window, click Delete.

34 Go to step 57.

Administer OC-n UPSR with TL1

35 Select action.

To provision OC-n facilities for UPSR, go to step 36.To deprovision OC-n facilities in UPSR, go to step 53.

Provision OC-n UPSR Facilities

36 Select action.

To provision OC-3 or OC-12, go to step 37.To provision OC-48 or OC-192, go to step 40.

37 Enter ENT-OCn::AID::::[CKTID=][,SDTHRESH=][,SFTHRESH=][,TRC=][,ALSENB=]:[PST][,SST]; to provision OC-3 or OC-12 facility in working slot of OCn pair.

where:OCn=Optical facility type (OC3 or OC12).AID=OC-3 or OC-12 access identifierOther parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

38 Repeat step 37 to provision OC-3 or OC-12 facility in protection slot of OCn pair.

39 Are additional OC-3 or OC-12 facilities to be provisioned?

If yes, repeat steps 37 and 38 until all appropriate OC-3/OC-12 facilities have been provisioned.If no, go to step 43.



40 Enter ENT-OCn::AID::::[CKTID=][,SDTHRESH=][,SFTHRESH=][,TRC=][,ALSENB=][,OPRNOM=][,TXPWR=]:[PST][,SST]; to provision OC-48 or OC-192 facility in working slot of OCn pair.


41 Repeat step 40 to provision OC-48 or OC-192 facility in protection slot of OCn pair.

42 Are additional OC-48 or OC-192 facilities to be provisioned?

If yes, repeat steps 40 and 41 until all appropriate OC-48/OC-192 facilities have been provisioned.If no, go to step 43.

Provision UPSR

43 Select action.

To provision OC-3 or OC-12 UPSR, go to step 44.To provision OC-48 or Oc-192 UPSR, go to step 46.

44 Enter ENT-FFP-OCn::PROTECTED_ID,PROTECTING_ID::::[APSTRC=],PTYPE=UPSR[,PSDIRN=][,RVRTV=][,RVRTTIM=]; to provision UPSR node application.

where:OCn=Optical facility type (OC3 or OC12).PROTECTED_ID=Working OC-3/OC-12 in 1+1 FFP group or working (preferred) OC-3/OC-12 in UPSR groupPROTECTING_ID=Protecting OC-3/OC-12 in 1+1 FFP group or protecting (alternate) OC-3/OC-12 in UPSR groupRefer to table 151-A for valid working and protect pairs. Ports must be configured on an adjacent pair of cards.Other parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

45 Go to step 47.



46 Enter ENT-FFP-OCn::PROTECTED_ID,PROTECTING_ID::::PTYPE=UPSR[,PSDIRN=][,APSTRC=][,RVRTV=][,RVRTTIM=][,NODEID=][,NODEDESCR=][,AUTOMAP=][,RINGID=]; to provision UPSR node application.

where:OCn=Optical facility type (OC48 or OC192).PROTECTED_ID=Working OC-48/OC-192 in 1+1 FFP group or working (preferred) OC-48/OC-192 in UPSR groupPROTECTING_ID=Protecting OC-48/OC-192 in 1+1 FFP group or protecting (alternate) OC-48/OC-192 in UPSR groupRefer to table 151-A for valid working and protect pairs. Ports must be configured on an adjacent pair of cards.Other parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

47 When an STS-n entity in the working slot is provisioned, the associated STS-n entity having the same port number is automatically provisioned in the protection slot with the same parameter values.

Provision all STS-n entities in OC-n working slot. Refer to NTP-103.

48 Select action.

If an STS-n pair is to be configured as a THRU connection, go to step 49.If an STS-n pair is to be configured as a 2WAY add/drop connection, go to step 51.

Configure a Pair of Path Entities as a Pass-Through Connection

49 A THRU connection is established using ENT-CRS-STSn command. The THRU connection occurs when there is an STS-n facility in the working slot and an STS-n in the protection slot, and both slots have the same port number in the AID field.

Establish the THRU connection. To administer cross-connections, refer to DLP-125 with parameter CCT=THRU.

50 Select action.

If other pass-through connections are to be established, repeat step 49 for each connection.If no additional THRU connections are required, go to step 57.


51 Using ENT-CRS-STSn, cross-connect FROM and TO parameters. To administer cross-connections terminated add/drop connection to/from the ring, refer to DLP-125 with parameter CCT=2WAY.



52 Are additional STS-n 2WAY cross connections to be established?

If yes, repeat step 51 for each STS-n to be established.If no, go to step 57.

Deprovision OC-n UPSR Facilities

53 Delete all pass-through connections using DLT-CRS-STSn command. Refer to DLP-125.

54 Delete all 2WAY connections using DLT-CRS-STSn command. Refer to DLP-125.

55 When an STS-n entity in the working slot is removed, the associated STS-n entity having the same port number is automatically removed in the protection slot. Delete all STS-n entities using DLT-STSn command. Refer to NTP-109.

56 Enter DLT-FFP-OCn::PROTECTED_ID,[PROTECTING_ID]; to deprovision UPSR node application.

where:OCn=Optical facility type (OC3, OC12, OC48, or OC192).PROTECTED_ID=Working OCn in 1+1 FFP group or working (preferred) OCn in UPSR groupPROTECTING_ID=Protecting OCn in 1+1 FFP group or protecting (alternate) OCn in UPSR group




DLP-152Administer VT1.5 LoopbackPURPOSE

This procedure provides the instructions to administer VT1.5 loopbacks.

PREREQUISITES

The VT1 facility to place in loopback must have a Primary State (PST) of OOS-AUMA or OOS-MA.

GENERAL

Loopbacks are test features that can be set to loop a signal back at different points along the signal path. The system supports one type of VT1 loopback.


The OPR-LPBK-VT1 command is used to initiate a VT1.5 loopback.



677-0244-1100404


X AIS

Administer VT1.5 Loopback 4-215


STEP PROCEDURE


2 Review the facility loopback diagram in figure 152-1.

3 Select action.

To administer VT1.5 loopback with 1677 SONET Link EMA, go to step 4.To administer VT1.5 loopback with TL1, go to step 39.

Administer VT1.5 Loopback with 1677 SONET Link EMA

4 Select action.

To retrieve current loopback status of VT1.5 port, go to step 5.To establish loopback, go to step 12.To verify loopback status, go to step 24.To release loopback, go to step 31.To end this procedure, go to step 55.







10 Click Close.

11 Go to step 4.

Establish Loopback




Administer VT1.5 Loopback4-216




17 Select action.



19 Click Yes.


21 Right-click the appropriate facility and select Loopback>Operate.

22 Click Yes in the Operate VT1 Loopback window.

23 Go to step 4.







29 Click Close.

30 Go to step 4.

Release Loopback







35 Click Yes.

36 Right-click on the appropriate facility and select Service State>Restore.

37 Click Yes.

38 Go to step 55.

Administer VT1.5 Loopback with TL1

39 Select action.

To retrieve current loopback status of VT1.5 facility, go to step 40.To establish loopback, go to step 43. To verify loopback status, go to step 49.To release loopback, go to step 52.To end this procedure, go to step 55.


40 Enter RTRV-LPBK-VT1::[AID];



42 Go to step 39.

Establish Loopback

43 Enter RTRV-VT1::AID; to retrieve the current PST and SST of the VT1 facility.


44 Observe output.

45 Select action.

If the PST for the VT1 facility is IS or OOS-AU, go to step 46.If the PST for the VT1 facility is OOS-AUMA or OOS-MA, go to step 47.




Enter RMV-VT1::AID;


47 Enter OPR-LPBK-VT1::AID:::[LOCN],,,FACILITY;

where:AID=VT1 Access IdentifierLOCN=NEND

48 Go to step 39.


49 Enter RTRV-LPBK-VT1::[AID]; to verify the VT1 facility is in loopback.



51 Go to step 39.

Release Loopback

52 Enter RLS-LPBK-VT1::AID:::[LOCN],,,[LPBKTYPE]; to release the VT1.5 loopback.

where:AID=VT1 Access IdentifierLOCN=NENDLPBKTYPE=FACILITY

53 Enter RST-VT1::AID; to place the facility back in service.


54 Go to step 39.




DLP-153Set Alarm AttributesPURPOSE

This procedure provides the instructions to set alarm condition attributes for the system.

GENERAL

This procedure provides instructions to set alarm condition attributes for OC-n, EC1, STS-n, DS3, OFA, GIGE, DS1, VT1.5 and SYNC.

The RTRV-ATTR-x (x=EC1,OCn, STSn, T1, T3, VT1, OFA, GIGE, COM) command retrieves the provisioned condition type attributes (notification code and service effect) for the specified port.

The SET-ATTR-x (x=EC1,OCn, STSn, T1, T3, VT1, OFA, GIGE, COM) command sets the notification code for service affecting and non-service facility standing conditions for the specified port.


STEP PROCEDURE

1 Select action.

To set alarm attributes with 1677 SONET Link EMA, go to step 2.To set alarm attributes with TL1, go to step 15.

Set Alarm Attributes with 1677 SONET Link EMA


3 Expand the appropriate facility domain (OC3, OC48, T3, EC1).


5 Right-click the appropriate facility and select Properties>Alarm Severity. The Alarm Severity table appears.

6 Observe current settings for alarm attributes.

7 Double-click in the cell under the Service Affecting column corresponding to the Condition Type and Location to be modified.

Set Alarm Attributes 4-221


8 Select the new Notification Code (for this Condition Type) from the drop-down list.

9 Double-click in the cell under the Non-Service Affecting column corresponding to the Condition Type and Location to be modified.

10 Select the new Notification Code (for this Condition Type) from the drop-down list.

11 Repeat steps 7 through 10 for each Condition Type to be changed.

12 Click Apply.

13 Click Close.

14 Go to step 17.

Set Alarm Attributes with TL1

15 Enter RTRV-ATTR-x::[AID]; to retrieve current provisioned alarm attributes.

where:x=Facility type. (OC3, OC12, OC48, OC192, EC1, STS1, STS3C, STS12C, STS48C, T1, T3, VT1, OFA, GIGE or COM)AID=Facility Access Identifier (Leave blank to retrieve all facilities of a certain type.)

16 Enter SET-ATTR-x::[AID]:::NTFCNCDE,[CONDTYPE],,,,[SRVEFF];

where:x=Facility type. (OC3, OC12, OC48, OC192, EC1, STS1, STS3C, STS12C, STS48C, T1, T3, VT1, OFA, GIGE or COM)AID=Facility Access Identifier (Leave blank to set all facilities of a certain type.)NTFCNCDE=Notification Code of condition type. (CR, MJ, MN, NA, NR)Other parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.


Set Alarm Attributes4-222


DLP-154Provision Gigabit Ethernet PortPURPOSE

This procedure provides the instructions to provision a port to receive and transmit Gigabit Ethernet lines.

PREREQUISITES

A Gigabit Ethernet card must be provisioned before Gigabit Ethernet ports can be provisioned. Refer to DLP-112 to provision equipment.

GENERAL

The system supports 2-way cross-connections between an EVC facility on a Gigabit Ethernet port and an STS-1 facility on an OC-n facility. The system also supports 1-way drop and continue connections for GIGE virtual concatenated cross-connects through OC-48 and OC-192 BLSR and UPSR configurations supporting broadcast video applications.

The ENT-GIGE command is used to provision GIGE facilities. Once a Gigabit Ethernet port is provisioned, ED-GIGE can be used to alter parameters however, a GIGE entity cannot be edited from Simplex mode of operation to Duplex or vice-versa. It must be deleted using DLT-GIGE and then re-entered using ENT-GIGE with the change.

EVC and the MAP configuration in the Gigabit Ethernet facility are independent. The relation is only when cross-connects to all the EVC timeslots specified in the MAP option are configured for the traffic to pass. The user can create facilities on any timeslot (1-24), and any number of them. Each Gigabit Ethernet port can be provisioned with 24 different addressable EVC facilities. The ENT-EVC command is used to provision EVC facilities. RTRV-EVC can be used to view the parameters.

In order to take advantage of the full GIGE bandwidth available, the MAP= field must be filled in as follows: MAP=1&&24. Both ends of the Gigabit Ethernet circuit must have the same value in the map.

To provision an EVC port, refer to DLP-171. To create a GIGE cross-connection, refer to DLP-164. To deprovision a GIGE circuit, refer to NTP-121.

See figure 154-1 for GIGE provisioning information.

Provision Gigabit Ethernet Port 4-223



STEP PROCEDURE

1 Select action.

To provision GIGE port with 1677 SONET Link EMA, go to step 2.To provision GIGE port with TL1, go to step 10.

Provision GIGE Port with 1677 SONET Link EMA

2 Expand the Facilities domain in the Scope pane.

3 Expand the GIGE domain.

4 Right-click the appropriate GIGE group and select Create. The Provision GIGE wizard appears.




Figure 154-1. GIGE Provisioning

GIGE Port ENT-GIGE

ENT-EVC

677-0228-1062303

GIGE Module (GIGE-2P)

EVC

ENT-EQPT

ENT-CRS-GIGE

Cross-connectEVC to STS1

Provision Gigabit Ethernet Port4-224


8 Click Finish.

9 Go to step 14.

Provision GIGE Port with TL1

10 Enter RTRV-GIGE::AID;

where:AID=GIGE Access Identifier

11 Examine provisioning information on port. Ensure that port is in valid state for provisioning (OOS-MA,UAS).


If yes, go to step 13.If no, the ENT-GIGE command cannot be performed on the specified GIGE port. Go to step 14.

13 Enter ENT-GIGE::AID::::[CKTID=][,MAP=][,ECHECK=][,JUMBO=][,NEGOTN=][,IPG=][,MODE=][,DROP=]:[PST];

where:AID=GIGE Access IdentifierMAP=1-24 is map EVCs included in data path. Both ends of connection must have same MAP= value.NEGOTN= AUTO (default) for duplex connections, DISABLED required for simplex connections.MODE=DUPLEX for 2 way communication, SIMPLEX for broadcast applications.DROP= Y if traffic drops at NE, N if traffic inserts at NE.Other parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.


Provision Gigabit Ethernet Port 4-225


Provision Gigabit Ethernet Port4-226


DLP-155Deprovision Gigabit Ethernet PortPURPOSE

This procedure provides the instructions to deprovision a Gigabit Ethernet port.

PREREQUISITES

If the Gigabit Ethernet port contains embedded EVCs, they must be deprovisioned first. To deprovision embedded EVC facilities, refer to DLP-172.

GENERAL

Deprovisioning a Gigabit Ethernet port clears all condition types, current Performance Monitoring (PM) data, and registers associated with the port.


STEP PROCEDURE

1 Select action.

To deprovision GIGE port with 1677 SONET Link EMA, go to step 2.To deprovision GIGE port with TL1, go to step 10.

Deprovision GIGE Port with 1677 SONET Link EMA

2 Expand the Facilities domain in the Navigation Tree.


4 Select appropriate GIGE group.

5 Examine provisioning information on appropriate GIGE facility.

6 Does facility have Secondary State of DSBLD, SDEE, TRM, or UAS?

If yes, the specified GIGE facility cannot be deleted. Go to step 14.If no, go to step 7.

7 Right-click the appropriate GIGE group and select Unassign.

8 Click Yes.

Deprovision Gigabit Ethernet Port 4-227


9 Go to step 14.

Deprovision GIGE Port with TL1

10 Enter RTRV-GIGE::AID;


11 Examine output for provisioning information on port. Ensure that port is in valid state for deprovisioning (IS).

12 Does facility have SST of DSBLD, SDEE, TRM, or UAS?

If yes, DLT-GIGE command cannot be performed on the specified GIGE facility. Go to step 14.If no, go to step 13.

13 Enter DLT-GIGE::AID;



Deprovision Gigabit Ethernet Port4-228


DLP-156Administer OC-n BLSRPURPOSE

This procedure provides the instructions to retrieve information on, provision, and deprovision a Bidirectional Line Switched Ring (BLSR) in which two fiber facilities are used to transport traffic between nodes of a ring. The two BLSR facilities interface with an OC-n BLSR. Add/drop traffic at the 1677 SONET Link ring node is connected to other facilities through the 1677 SONET Link matrix.

It also provides instructions to modify a BLSR ring map, squelch map, or node ID.

PREREQUISITES

Two OC-48 or OC-192 facilities must be provisioned using the ENT-OCn command, before protection groups can be established.

To modify BLSR squelch maps and ring maps manually, the automap feature must be disabled. Refer to DLP-168.

GENERAL

ENT-FFP-OCn will execute if a pair of OC-n facilities in adjacent slots of the 1677 SONET Link node have been previously provisioned, and are not currently operating as a 1+1 APS protection group. The paired OC-n facilities must be on the same port of each slot; for example, OC48-1-A-1 andOC48-2-A-1.

The ring ports must be configured on an adjacent pair of cards. The west ring port is the left (lower-numbered) facility, and the east ring port is the right (higher-numbered) facility.

The valid AID values for OC-n facilities using the ENT-FFP-OCn are listed in table 156-A.


The 1677 SONET Link node supports as many as 12 BLSR rings (if only OC-48 facilities are used).

Table 156-A. OC-n BLSR Nodes Protected and Protecting PairsOC-n BLSR PROTECTING AND PROTECTED PAIRS

Protected AID Protecting AIDOC-48 OC48-{1,3,5,12,14,16}-{A,B}-1 OC48-{2,4,6,13,15,17}-{A,B}-1OC-192 OC192-{5,12}-AB-1 OC192-{6,13}-AB-1

Administer OC-n BLSR 4-229


Features of the BLSR are as follows:

• One to 12 OC-n BLSR rings within the same 1677 SONET Link node if using OC48 and two otherwise.

• OC-n BLSR rings may co-exist with other UPSR protection groups, other 1+1 protection groups, or other unprotected OC-n facilities in the same 1677 SONET Link node.

• Each OC-n BLSR node is provided with the following features:

– STS-n cross-connects can be configured to go over the BLSR ring using the ENT-CRS-STSn command.

– STS-n paths can be cross-connected between two OC-ns as a pass-through connection, 2WAY connection, or DRI connection, or to interconnect two BLSR rings using one node.

– BLSR Switch initiation criteria includes external initiated switching commands, and automatic initiated switching request.

– Automatic switching is initiated by the 1677 SONET Link node detecting either APS channel signaled commands including LP-S, FS-R, MS-R, EXER-R, and automatic initiated requests including SF-R, SD-R, RR-R, and WTR.

– External switch commands (OPR-PROTNSW-OCn) can be entered to manually initiate protection switching of BLSR. Refer to DLP-132 for procedures to switch OC-n line from working to protection and vice versa.

– Line switching occurs within 50 msec after a defect is detected.

– Nonrevertive and revertive switching are supported.

– BLSR Dual Ring Interconnection using Working capacity. Provisioning and deprovisioning of this feature is discussed in DLP-157.

When adding a new entry in the ring, a minor alarm “Improper K byte received” will occur on the nodes. After adding the new entry to all the nodes on the BLSR, the alarm will be cleared.

The ENT-FFP-OC48/192 command enables the BLSR operation.

Automap is an automatic provisioning feature where BLSR squelch and ring maps are learned. This feature is enabled using the ENT-FFP-OC48/192 command and setting AUTOMAP=Y. When this feature is enabled, the node identifier of the local node needs to be only specified. If this feature is not enabled, ring map must be entered via ED-RINGMAP command, and squelch information must be entered via the ED-SQLMAP command for the BLSR to function properly.

Until a valid ring map is created, the NE will transmit an APSCDFLTK alarm. While this alarm is present, no BLSR protection is available.

Administer OC-n BLSR4-230


A ring map contains the BLSR topology. It shows the order in which BLSR nodes appear in the ring. The ED-RINGMAP command is used to edit the BLSR ringmap. Automap provisioning must be disabled for this command to complete.

The BLSR node maintains a squelch map containing the entry and exit node IDs for every provisioned working STS path on the ring. The ED-SQLMAP command modifies an entry in the BLSR squelch map. Automap provisioning must be disabled for this command to complete.

The RINGID parameter of the ENT-FFP-OC48/OC192 command must be properly provisioned if automatic learning of squelch maps and ring maps is enabled. This parameter identifies a BLSR within a shelf and must be unique to the system and common across a BLSR. It has no significance when the automatic learning protocol is not enabled.

The NODEID parameter of the ENT-FFP-OC48/OC192 command is used to assign an identifier to each node on a ring. The NODEID is a number from zero to 15; therefore a maximum of 16 nodes on a 2-fiber BLSR are allowed. The node ID an be edited when both BLSR facilities are locked out or in the forced switch state. The local node ID can be changed when the auto map feature is enabled or disabled.


STEP PROCEDURE

1 Select action.

To administer OC-n BLSR with 1677 SONET Link EMA, go to step 2.To administer OC-n BLSR with TL1, go to step 123.

Administer OC-n BLSR with 1677 SONET Link EMA

2 Select action.

To provision OC-n BLSR node, go to step 3.To modify BLSR ring map, go to step 44.To modify BLSR squelch map, go to step 76.To modify BLSR node ID, go to step 86.To deprovision OC-n BLSR facilities, go to step 113.To end this procedure, go to step 171.

Provision OC-n BLSR Node





5 Provision working OC-n facility. Right-click on the appropriate OC-n group and select Create. The Provision OC-n wizard appears.




9 Click Finish.

10 Repeat steps 5 through 10 to provision the protection OC-n facility (East facility).

11 Will ring maps and squelch maps be manually entered or automatically learned?

If manually entered, go to step 29.If automatically learned, go to step 12.

Enable DCC



14 Right-click on appropriate OC-n facility protection range and select Network Interface>Create. The Create Network Interface wizard appears.


16 On the Name page, enter AID of Protected (west) OC-n.

17 Click Next.

18 Click Next to skip the Line Lower Layer Protocol page.

19 On the Line Upper Layer Protocol page, select action.

To enable DCC on line of OC-n, go to step 24.To enable DCC on section of OC-n, go to step 20.

20 Click Next.

21 Click Next to skip the Section Lower Layer Protocol page.

22 On the Section Upper Layer Protocol page, select CLNP from drop-down menu.

23 Go to step 25.



24 Select CLNP from drop-down menu.

25 Click Go to Finish.


27 Click Finish.

28 Repeat steps 14 through 27 for protecting (east) OC-48 or OC-192.

Enable BLSR Operation

29 To enable BLSR node application, expand the Protection domain in the Scope Pane.




33 On the Protection Type page, select PROT_TYPE_2FBLSR from the drop-down menu.

34 Click Next.



37 Click Finish.

38 Provision all STS-n entities in OC-n working slot. Refer to NTP-103.

39 Select action.

If an STS-n pair is to be configured as a THRU connection, go to step 40.If an STS-n pair is to be configured as a 2WAY connection, go to step 42.If an STS-n pair is to be configured as a DRI connection, refer to DLP-157.



Configure Pass-Through Connection

40 A THRU connection is established by creating an STSn cross-connection. The THRU connection occurs when there is an STS-n entity in the working slot and an STS-n in the protection slot, and both slots have the same port number and time slot number in the AID field.

Establish the THRU connection. To administer cross-connections, refer to DLP-125 with parameter Cross Connect Type=THRU.

41 Are additional STS-n cross connections to be established?

If yes, repeat step 40 for each connection.If no, go to step 2.


42 A 2WAY connection is established by creating a cross-connection.

Establish 2WAY connection.

To administer STS-n cross-connections, refer to DLP-125 with parameter Cross Connect Type=2WAY.To administer T3 cross-connections, refer to DLP-124 with parameter Cross Connect Type=2WAY.To administer T1 cross-connections, refer to DLP-177 with parameter Cross Connect Type=2WAY.To administer VT1 cross-connections, refer to DLP-126 with parameter Cross Connect Type=2WAY.



Modify BLSR Ring Map



46 Select appropriate OC-n protection range to display current protection pairs.

47 Right-click on appropriate protection pair and select Properties>General.

48 Scroll to the Automap parameter and note the value.



49 Does AUTOMAP parameter have value of Y or N?

If Y, ring maps are automatically learned and can not be changed manually. Go to step 2.If N, go to step 50.

50 Click Close.

51 Right-click on appropriate OC-n protection pair and select RINGMAP.

52 Observe information in table.

53 Click Close.


55 Right-click on appropriate OC-n protection pair and select Operate Switch. The Operate Protection Switch wizard appears.


57 On the Switching Side page, select East.

58 Click Next.

59 On the Switch Command Mode page, select Lockout of Protection-Span.

60 Click Next.


62 Click Finish.

63 Repeat steps 55 through 62 for the West switching side.


65 Double-click cell under Ring Map and select appropriate value from drop-down list.

Value of RINGMAP is the sequence of BLSR node IDs, starting with the node to its east, and continuing around the ring ending with the node to the west of the current node.

66 Click Apply.

67 Click Close.



68 Verify the new ring map. Right-click on appropriate OC-n protection pair and select RINGMAP.


70 Click Close.

71 Right-click on appropriate OC-n protection pair and select Release Switch.

72 Select East.

73 Click Release.

74 Repeat steps 71 through 73 for the West side.

75 Every node in the ring needs an entry for the BLSR Ring Map. Are there other nodes to perform this procedure on in the BLSR Ring?


Modify BLSR Squelch Map



78 Expand appropriate OC-n protection range to display current protection pairs.

79 Right-click on appropriate OC-n protection pair and select SQLMAP/BLSR Channel Data.


81 Double-click in cell under Source Node and select node ID value from drop-down list.

82 Double-click in cell under Destination Node and select node ID value from drop-down list.

83 Click Apply.

84 Click Close.

85 Go to step 2.



Modify BLSR Node ID




89 Right-click on appropriate OC-n protection pair and select Properties>General.

90 Observe information in table and note current Node ID.

91 Click Close.




95 Click Next.


97 Click Next.


99 Click Finish.



102 Double-click in cell under Node ID and select new value from the drop-down list.

103 Click Apply.

104 Click Close.


106 Select East.

107 Click Release.





110 Observe information in table and verify new Node ID.

111 Click Close.

112 Go to step 2.

Deprovision OC-n BLSR Facilities

113 Delete all pass-through connections. Refer to DLP-125.

114 Delete all 2WAY connections. Refer to DLP-125, DLP-124, DLP-177, and DLP-126.

115 Delete all DRI connections related to this OC-n BLSR. Refer to DLP-157.

116 Delete all STS-n entities. Refer to DLP-122.

117 To deprovision BLSR node application, expand the Protection domain.


119 Select appropriate OC-n group to display current protection pairs.

120 Right-click on appropriate OCn protection pair and select Delete.

121 Click Delete.

122 Go to step 2.

Administer OC-n BLSR with TL1

123 Select action.

To provision OC-n BLSR Node, go to step 124.To modify BLSR ring map, go to step 140.To modify BLSR squelch map, go to step 152.To modify BLSR node ID, go to step 157.To deprovision OC-n BLSR facilities, go to step 166.To end this procedure, go to step 171.



Provision OC-n BLSR Node

124 Enter ENT-OCn::AID::::[CKTID=][,SDTHRESH=][,SFTHRESH=][,TRC=][,ALSENB=][,OPRNOM=][,TXPWR=]:[PST][,SST]; to provision OC-48 or OC-192 facility in working slot of OCn pair (west facility).


125 Repeat step 124 to provision protection OC-n facility (East facility).

126 Will ring maps and squelch maps be manually entered or automatically learned?

If manually entered, go to step 133.If automatically learned, go to step 127.

Enable DCC

127 Select action.

To enable DCC on line of OCn, go to step 128.To enable DCC on section of OCn, go to step 131.

128 Enter ENT-NETIF::AID::::,LINEUL=CLNP;

where:AID=Protected (west) OC-48 or OC-192 access identifier

129 Repeat step 128 for protecting (east) OC-48 or OC-192.

130 Go to step 133.

131 Enter ENT-NETIF::AID::::,,,SECTIONUL=CLNP;

where:AID=Protected (west) OC-48 or OC-192 AID





133 Enter ENT-FFP-OCn::PROTECTED_ID,PROTECTING_ID::::PTYPE=BLSR2[,PSDIRN=][,APSTRC=][,RVRTV=][,RVRTTIM=],NODEID=[,NODEDESCR=],AUTOMAP=,RINGID=; to enable BLSR node operation.

where:OCn=Optical facility type (OC48 or OC192).PROTECTED_ID=Access identifier of west OCn in BLSRPROTECTING_ID=Access identifier of east OCn in BLSRNODEID=Local node identifier. Must be unique within a BLSR. {0-15}AUTOMAP=Automatic provisioning feature where squelch and ring maps are learned is enabled. {Y or N} Default=Y if PTYPE=BLSR2. If AUTOMAP=N, ring maps and squelch maps must be manually entered for the BLSR to operate correctly.RINGID=Ring identifier, identifies a BLSR within a shelf. Must be six alphanumeric characters.Refer to table 156-A for valid working and protect pairs. Ports must be configured on an adjacent pair of cards.Other parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

134 Provision all STS-n entities in OC-n working slot. Refer to NTP-103.

135 Select action.

If an STS-n pair is to be configured as a THRU connection, go to step 136.If an STS-n pair is to be configured as a 2WAY connection, go to step 138.If an STS-n pair is to be configured as a DRI connection, refer to DLP-157.

Configure Pass-Through Connection

136 A THRU connection is established by using the ENT-CRS-STSn The THRU connection occurs when there is an STS-n entity in the working slot and an STS-n in the protection slot, and both slots have the same port number and time slot number in the AID field.

Establish the THRU connection. To administer cross-connections, refer to DLP-125 with parameter CCT=THRU.






138 A 2WAY connection is established using the ENT-CRS-x command. (Where x is STS1, STS3C, STS12C, STS48C, T1, T3, VT1.)

Establish 2WAY connection.

To administer STS-n cross-connections, refer to DLP-125 with parameter CCT=2WAY.To administer T3 cross-connections, refer to DLP-124 with parameter CCT=2WAY.To administer T1 cross-connections, refer to DLP-177 with parameter CCT=2WAY.To administer VT1 cross-connections, refer to DLP-126 with parameter CCT=2WAY.

139 Are additional 2WAY cross connections to be established?


Modify BLSR Ring Map


where:OCn=Optical facility type (OC-48 or OC-192)AID=OC-48/OC-192 access identifier

141 Observe output. Note value of AUTOMAP parameter.



143 Enter RTRV-RINGMAP::[AID]; to retrieve the existing BLSR ring maps.

where:AID=OC48 or OC192 access identifier or ALL

Example Output:



ALCATEL-1677SL 04-05-30 19:26:57M 0 COMPLD "OC192-5-AB-1,OC192-6-AB-1::RINGID=DALLAS,NODEID=4,RINGMAP=1&2&3" "OC48-1-A-1,OC48-2-A-1::RINGID=MADRID,NODEID=6,RINGMAP=3&1&2" /* RTRV-RINGMAP */;

144 Observe output. Note values of RINGID, NODEID, and RINGMAP parameters.

145 Enter OPR-PROTNSW-OCn::AID:::LOP-S;

where:OCn=Optical facility (OC-48 or OC-192)AID=East OC-n facility access identifier


where:OCn=Optical facility (OC-48 or OC-192)AID=West OC-n facility access identifier

147 Enter ED-RINGMAP::AID::::RINGMAP=;

where:AID=OC-48 or OC-192 access identifier of BLSR nodeRINGMAP=Sequence of node IDs within a BLSR. (0-15) Ampersand (&) grouping is used to join each node ID value (up to 15 values). The first RINGMAP value defines the node ID of the adjacent BLSR node (east side). Subsequent RINGMAP values define the node ID of the BLSR node (in the eastward side). The last RINGMAP value defines the node ID of the adjacent BLSR node (west side).

148 Enter RTRV-RINGMAP::[AID]; to verify the new ring map.

where:AID=OC48 or OC192 access identifier or ALL







151 Every node in the ring needs an entry for the BLSR Ring Map. Are there other nodes to perform this procedure on in the BLSR Ring?


Modify BLSR Squelch Map

152 Enter RTRV-SQLMAP::AID; to retrieve current squelch map.

where:AID=STSn or OC-48/OC192 access identifier

153 Observe output. Note values for ENTRY and EXIT parameters. (A value of 255 means the node ID is unspecified.)

154 Enter ED-SQLMAP::AID::::ENTRY=,EXIT=;

where:AID=STSn or OC-48/OC192 access identifierENTRY=Node ID (0-15) of the source node in the BLSR.EXIT=Node ID (0-15) of the destination node in the BLSR.

155 Enter RTRV-SQLMAP::AID; to verify the new squelch map.

where:AID=STSn or OC-48/OC192 access identifier

156 Go to step 123.

Modify BLSR Node ID


where:OCn=Optical facility type (OC-48 or OC-192)AID=OC-48/OC-192 access identifier

158 Observe output and note current value of NODEID parameter.







161 Enter ED-FFP-OCn::PROTECTED_ID::::,NODEID=;

where:OCn=Optical facility type (OC-48 or OC-192)PROTECTED_ID=OC-48/OC-192 access identifierNODEID=New value of node identifier (0-15)





164 Enter RTRV-FFP-OCn::[AID]; to verify new node ID value.

where:OCn=Optical facility type (OC-48 or OC-192)AID=OC-48/OC192 access identifier

165 Go to step 123.

Deprovision OC-n BLSR Facilities

166 Delete all pass-through connections using DLT-CRS-STSn command. Refer toDLP-125.

167 Delete all 2WAY connections using DLT-CRS-rr command. Refer to DLP-125, DLP-124, DLP-177, and DLP-126.

168 Delete all DRI connections pertinent to this OC-n BLSR. Refer to DLP-157.

169 Delete all STS-n entities using DLT-STSn command. Refer to DLP-122.



170 Enter DLT-FFP-OCn::PROTECTED_ID,[PROTECTING_ID]; to deprovision BLSR node application.

where:OCn=Optical facility type (OC48 or OC192).PROTECTED_ID=Working (west) OCn in FFP groupPROTECTING_ID=Protecting (east) OCn in FFP group




DLP-157Administer Dual Ring Interconnect (DRI)PURPOSE

This procedure provides the instructions to retrieve information on, provision, and deprovision Dual Ring Interconnect (DRI) cross-connections in which one, two (nodes are connected to both rings), three (one node on both rings, and two nodes on each ring), or four (two nodes on each ring) 1677 SONET Link nodes are used to transport traffic between two rings. The interconnected rings may be BLSR to BLSR, BLSR to UPSR, or UPSR to UPSR.

PREREQUISITES

For each ring, two facilities must be provisioned as a ring using the ENT-FFP-OCn command, before Dual Ring Interconnect protection groups can be established. Depending on the ring type to which the 1677 SONET Link node is connected, the ring node may be provisioned as a BLSR node or a UPSR node. In the case of using one or two 1677 SONET Link nodes to transport traffic between two rings, two ring nodes must be provisioned on the 1677 SONET Link node, one for each ring. Refer to DLP-151 to provision the node as UPSR node, and refer to DLP-156 to provision the node as BLSR node.

GENERAL

The 1677 SONET Link node supports one-node DRI, two-node DRI, three-node DRI, and four-node DRI.

Features of the DRI include:

• DRI may be a simple or composite cross-connection, depending on DRI type.

• One- and two-node DRI contain composite cross-connections for each DRI, and four-node DRI contains one simple cross-connection for each DRI.

• Each cross-connection may be BLSR or UPSR in the case of simple cross-connection, or it may be BLSR/UPSR, BLSR/BLSR, or UPSR/UPSR in the case of composite cross-connection.

• DRI may co-exist with other BLSR protection groups, other UPSR protection groups, other 1+1 protection groups, or other unprotected OC-n facilities in the same 1677 SONET Link node.

• One-node DRI is only used to interconnect two rings. It is not a Drop and Continue type of cross-connection.

• Three-node DRI is a combination of two-node and four-node DRI.

Administer Dual Ring Interconnect (DRI) 4-247


Each DRI is provided with the following features:

• STS-1, STS-3c, STS12c, and STS48c paths can be configured as DRI protection groups by using ENT-CRS-STSn command.

• The combination of Drop and Continue and service selector functionality is supported for two-, three-, and four-node DRIs.

• The following features are specific to DRIs on the BLSR ring node side:

– Support drop and continue using working capacity.

– 1677 SONET Link node may be provisioned as the primary or secondary node for two-, three-, or four-node DRIs on the BLSR ring node side.

– Service selectors will select the interconnecting line as its default path unless it is provisioned otherwise.

– A hold off timer of 100 ms at the service selector is initiated at the detection of any failure. No switch will occur when the timer expires and the failure which triggers the timer is no longer present.

• The working and protection paths of each DRI path are monitored. Defects which initiate path switching are: AIS-P, LOP-P, UNEQ-P, EBER-P, SDBER-P, and PDI-P

• External switch commands (OPR-PROTNSW-STSn) can be entered to manually control each path of the DRI. Refer to DLP-149 for procedures to switch STS-n path from working to protection and vice versa.

• Nonrevertive and revertive switching of the service selector are supported.

In a Drop and Continue application, there are three types of signals:

• Ring interfaces are the continue part of the Drop and Continue connection and follow the protected rules above.

• Drop interfaces are the drop part of the Drop and Continue connection and can be protected or unprotected. They can even be drop interfaces from other Drop and Continue rings.

• Local access interfaces are the typical UPSR and are not supported at Drop and Continue nodes, only at other nodes on the Drop and Continue rings.

Administer Dual Ring Interconnect (DRI)4-248


Figure 157-1. One-Node Ring Interconnect Cross-Connections

677-0180-1081704

UPSR Ring 1

FROM

UPSR 2WAY to UPSR 2WAY

UPSR Ring 1

UPSR Ring 2 UPSR Ring 2TO

2WAY (CCT)

UPSR 2WAY to BLSR 2WAY

UPSR Ring 1 UPSR Ring 1

BLSR Ring 2

FROM

TO

2WAY (CCT)

BLSR Ring 1

FROM

BLSR 2WAY to BLSR 2WAY

BLSR Ring 2TO

2WAY (CCT)



Table 157-A. One-Node Ring Interconnect ParametersComposition of Cross-Connection

Restriction on Parameters

Ring 1 Ring 2 FROM TO CCT CCT2 SWPDIP SWPDIP2

PREFERRED

PREFERRED2

UPSR 2WAY

UPSR 2WAY

UPSR ring port

UPSR ring port

2WAY Not allowed

Allowed Allowed EAST or WEST

EAST or WEST

UPSR 2WAY

BLSR 2WAY

UPSR ring port

BLSR ring port

2WAY Not allowed

Allowed Not allowed

EAST or WEST

Not allowed

BLSR 2WAY

UPSR 2WAY

BLSR ring port

UPSR ring port

2WAY Not allowed

Not allowed

Allowed Not allowed

EAST or WEST

BLSR 2WAY

BLSR 2WAY

BLSR ring port

BLSR ring port

2WAY Not allowed

Not allowed

Not allowed

Not allowed

Not allowed

Figure 157-2. Two-Node Ring Interconnect Cross-Connections: UPSR-UPSR

677-0181-1081704

2WAYDC (CCT)

UPSR 2WAYDC to UPSR 2WAYDC

UPSR 1 UPSR 1

UPSR 2UPSR 2

FROM

TO



Figure 157-3. Two-Node Ring Interconnect Cross-Connections: UPSR-BLSR and BLSR-UPSR

677-0182-1081704

2WAYDC (CCT)

Working Channel

UPSR 2WAYDC to BLSR 2WAYDC

2WAYDC (CCT2)UPSR 1 UPSR 1

FROM

TO

BLSR 2 BLSR 2

UPSR 2WAYDC to BLSR SRIW

2WAYDC (CCT)SRIW (CCT2)UPSR 1 UPSR 1

FROM

BLSR 2 BLSR 2

TOWorking Channel

BLSR 2WAYDC to UPSR 2WAYDC

2WAYDC (CCT)2WAYDC (CCT2)

BLSR 1 BLSR 1

Working Channel

FROM

TO

UPSR 2 UPSR 2

BLSR SRIW to UPSR 2WAYDCSRIW (CCT)

2WAYDC (CCT2)BLSR 1 BLSR 1

Working Channel

FROMTO

UPSR 2 UPSR 2



Figure 157-4. Two-Node Ring Interconnect Cross-Connections: BLSR-BLSR

677-0183-1081704

BLSR 2WAYDC to BLSR SRIW

2WAYDC (CCT)SRIW (CCT2)

BLSR SRIW to BLSR 2WAYDC

SRIW (CCT)2WAYDC (CCT2)BLSR 1 BLSR 1

Working ChannelFROM

TO

Working Channel

BLSR 2BLSR 2

BLSR 1 BLSR 1

Working Channel

FROMTO

Working Channel

BLSR 2 BLSR 2

BLSR 2WAYDC to BLSR 2WAYDC2WAYDC (CCT)

2WAYDC (CCT2)BLSR 1 BLSR 1

Working ChannelFROM

TO

BLSR 2BLSR 2

Working Channel

BLSR SRIW to BLSR SRIWSRIW (CCT)SRIW (CCT2)

BLSR 1 BLSR 1

Working Channel

Working Channel

BLSR 2

FROM

TOBLSR 2



Table 157-B. Two-Node Ring Interconnect ParametersComposition of Cross-Connection


Ring 1 Ring 2 FROM TO CCT CCT2 SWPDIP SWPDIP2

PREFERRED

PREFERRED2

UPSR 2WAYDC

UPSR 2WAYDC

UPSR ring port

UPSR ring port

2WAYDC

Not allowed


EAST or WEST

UPSR 2WAYDC

BLSR 2WAYDC

UPSR ring port

BLSR ring port

2WAYDC

2WAYDC


ACCESS or Ring

UPSR 2WAYDC

BLSR SRIW

UPSR ring port

BLSR ring port

2WAYDC

SRIW Allowed Not allowed

EAST or WEST

Not allowed

BLSR 2WAYDC

UPSR 2WAYDC

BLSR ring port

UPSR ring port

2WAYDC

2WAYDC

Allowed Allowed ACCESS or Ring

EAST or WEST

BLSR SRIW

UPSR 2WAYDC

BLSR ring port

UPSR ring port

SRIW 2WAYDC

Not allowed

Allowed Not allowed

EAST or WEST

BLSR 2WAYDC

BLSR 2WAYDC

BLSR ring port

BLSR ring port

2WAYDC

2WAYDC

Allowed Allowed ACCESS or Ring

ACCESS or Ring

BLSR 2WAYDC

BLSR SRIW

BLSR ring port

BLSR ring port

2WAYDC

SRIW Allowed Not allowed

ACCESS or Ring

Not allowed

BLSR SRIW

BLSR 2WAYDC

BLSR ring port

BLSR ring port

SRIW 2WAYDC

Not allowed

Allowed Not allowed

ACCESS or Ring

BLSR SRIW

BLSR SRIW

BLSR ring port

BLSR ring port

SRIW SRIW Not allowed

Not allowed

Not allowed

Not allowed




Figure 157-5. Four-Node Ring Interconnect Cross-Connections

Table 157-C. Four-Node Ring Interconnect ParametersComposition of Cross-Connection


FROM1

[1] If provisioning the primary node on the BLSR ring, the FROM/TO port should be the port of source of the con-tinue traffic for ring. Otherwise, it should be the port accessed on the ring.

TO1 CCT CCT2 PREFERRED PREFERRED2

UPSR 2WAYDC Unprotected or 1+1 APS port

UPSR ring port

2WAYDC

Not allowed

EAST or WEST

Not allowed

BLSR 2WAYDC Unprotected or 1+1 APS port

BLSR ring port

2WAYDC

Not allowed

ACCESS or RING

Not allowed

BLSR SRIW Unprotected or 1+1 APS port

BLSR ring port

SRIW Not allowed

Not allowed Not allowed

677-0184-1081704

Primary Node

FROM

TO

Working Channel

UPSR UPSR

2WAYDC (CCT)

FROM

UPSR 2WAYDC

TO

BLSR 2WAYDC

2WAYDC (CCT)

BLSR BLSR

TO

FROM

BLSR SRIWSecondary Node

SRIW (CCT)

BLSR BLSR

Working Channel



STEP PROCEDURE

1 Select action.

To administer Dual Ring Interconnect with 1677 SONET Link EMA, go to step 2.To administer Dual Ring Interconnect with TL1, go to step 52.

Administer Dual Ring Interconnect with 1677 SONET Link EMA

2 Select action.

To provision DRI one-node UPSR/UPSR cross-connection, go to step 3.To provision DRI one-node UPSR/BLSR cross-connection, go to step 6.To provision DRI one-node BLSR/BLSR cross-connection, go to step 9.To provision DRI two-node UPSR/UPSR cross-connection, go to step 12.To provision DRI two-node UPSR/BLSR cross-connection, go to step 15.To provision DRI two-node BLSR/BLSR cross-connection, go to step 18.To provision DRI four-node cross-connection, go to step 21.To deprovision DRI facilities, go to step 42.

Provision DRI One-Node Facilities – UPSR to UPSR

3 Review the UPSR to UPSR one-node DRI diagram shown in figure 157-1.


Use table 157-A as a guide when entering values into the cross connection table.

5 Go to step 24.

Provision DRI One-Node Facilities – UPSR to BLSR

6 Review the UPSR to BLSR one-node DRI diagram shown in figure 157-1.



8 Go to step 24.

Provision DRI One-Node Facilities – BLSR to BLSR One-Node DRI

9 Review the BLSR to BLSR one-node DRI diagram shown in figure 157-1.





11 Go to step 24.

Provision DRI Two-Node Facilities – UPSR to UPSR

12 Review the UPSR to UPSR two-node DRI diagram shown in figure 157-2.


Use table 157-B as a guide when entering values into the cross connection table.

14 Go to step 24.

Provision DRI Two-Node Facilities – UPSR to BLSR

15 Review the UPSR to BLSR two-node DRI diagram shown in figure 157-3.



17 Go to step 24.

Provision DRI Two-Node Facilities – BLSR to BLSR

18 Review the BLSR to BLSR two-node DRI diagrams shown in figure 157-4.



20 Go to step 24.

Provision DRI Four-Node Facilities

21 Review the four-node DRI diagrams shown in figure 157-5.


Use table 157-C as a guide when entering values into the cross connection table.



23 Go to step 24.

Enter cross-connection Information




27 Double-click on facility types and groups until appropriate STSn facility is shown.

28 Select STSn facility.

29 Click OK.



32 Double-click on facility types and groups until appropriate STSn facility is shown.

33 Select STSn facility.

34 Click OK.







41 Go to step 76.

Deprovision DRI Facilities







46 Select appropriate connection to delete.

47 Click Delete.




51 Go to step 76.

Administer Dual Ring Interconnect with TL1

52 Select action.

To provision DRI one-node UPSR/UPSR facilities, go to step 53.To provision DRI one-node UPSR/BLSR facilities, go to step 56.To provision DRI one-node BLSR/BLSR facilities, go to step 59.To provision DRI two-node UPSR/UPSR facilities, go to step 62.To provision DRI two-node UPSR/BLSR facilities, go to step 65.To provision DRI two-node BLSR/BLSR facilities, go to step 68.To provision DRI four-node facilities, go to step 71.To deprovision DRI facilities, go to step 74.

Provision DRI One-Node Cross-Connection – UPSR to UPSR

53 Review the UPSR to UPSR one-node DRI diagram shown in figure 157-1.

54 Enter ENT-CRS-STSn::FROM,TO:::2WAY[,CCT2]:[CKTID=][,CKTADDR=][,CKTNBR=][,SWPDIP=][,SWUNEQP=][,PREFERRED=][,RVRTV=][,RVRTTIM=][,SWPDIP2=][,SWUNEQP2=][,PREFERRED2=][,RVRTV2=][,RVRTTIM2=];

where:STSn=Signal type (STS1, STS3C, STS12C, or STS48C).Refer to table 157-A for parameter values. See figure 157-1 for an example diagram.

FROM=AID of source facility (either port of the UPSR ring pair for one ring)TO=AID of destination facility (either port of the UPSR ring pair for the other ring)Other parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

55 Go to step 76.



Provision DRI One-Node Cross-Connection – UPSR to BLSR

56 Review the UPSR to BLSR one-node DRI diagram shown in figure 157-1.



FROM=AID of source facility (either port of the UPSR ring pair for the UPSR ring)TO=AID of destination facility (BLSR ring port that is accessed)Other parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

58 Go to step 76.

Provision DRI One-Node Cross-Connection – BLSR to BLSR One-Node DRI

59 Review the BLSR to BLSR one-node DRI diagram shown in figure 157-1.



FROM=Ring port that is being cross-connected on one BLSR ringTO=Ring port that is being cross-connected on the other BLSR ringOther parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

61 Go to step 76.

Provision DRI Two-Node Cross-Connection – UPSR to UPSR

62 Review the UPSR to UPSR two-node DRI diagram shown in figure 157-2.



63 Enter ENT-CRS-STSn::FROM,TO:::2WAYDC[,CCT2]:[CKTID=][,CKTADDR=][,CKTNBR=][,SWPDIP=][,SWUNEQP=][,PREFERRED=][,RVRTV=][,RVRTTIM=][,SWPDIP2=][,SWUNEQP2=][,PREFERRED2=][,RVRTV2=][,RVRTTIM2=];

where:STSn=Signal type (STS1, STS3C, STS12C, or STS48C).Refer to table 157-B for parameter values. See figure 157-2 for an example diagram.

FROM=Port of source of the continue traffic for one UPSR ring.TO=Port where the dropped traffic is sent on the other UPSR ring.Other parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

64 Go to step 76.

Provision DRI Two-Node Cross-Connection – UPSR to BLSR

65 Review the UPSR to BLSR two-node DRI diagram shown in figure 157-3.



FROM=Port of source of the continue traffic for the UPSR ring.TO=Either the port of source of the continue traffic for the BLSR ring or the ring port accessed on the BLSR ring. See figure 157-3. Refer to table 157-B.

Other parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

67 Go to step 76.

Provision DRI Two-Node Cross-Connection – BLSR to BLSR

68 Review the BLSR to BLSR two-node DRI diagrams shown in figure 157-4.





FROM: If provisioning the primary node on the BLSR ring, it should be the port of source of the continue traffic for ring. Otherwise, it should be the port accessed on the ring.TO: If provisioning the primary node on the BLSR ring, it should be the port of source of the continue traffic for ring. Otherwise, it should be the port accessed on the ring.CCT:

CCT=2WAYDC if node is the primary node for this DRI on BLSR ring 1.CCT=SRIW if node is the secondary node for this DRI on the BLSR ring.CCT2=2WAYDC if node is the primary node for this DRI on BLSR ring 2.CCT=SRIW if node is the secondary node for this DRI on the BLSR ring.


70 Go to step 76.

Provision DRI Four-Node Cross-Connection

71 Review the four-node DRI diagrams shown in figure 157-5.


where:STSn=Signal type (STS1, STS3C, STS12C, or STS48C).Refer to table 157-C for parameter values. See figure 157-5 for an example diagram.

FROM=If provisioning the primary node on the BLSR ring, it should be the port of source of the continue traffic for ring. Otherwise, it should be the port accessed on the ring.TO=If provisioning the primary node on the BLSR ring, it should be the port of source of the continue traffic for ring. Otherwise, it should be the port accessed on the ring.Other parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

73 Go to step 76.



Deprovision DRI Facilities


where:STSn=Signal type (STS1, STS3C, STS12C, or STS48C).FROM=Source identifierTO=Destination identifier

75 If required, delete STS-n path entities within OC-n working slot. Refer to DLP-122.




DLP-158Deprovision EC1 FacilityPURPOSE

This procedure provides the instructions to deprovision an EC1 facility.

PREREQUISITES

Before deprovisioning an EC1 facility, embedded STS-1 ports must be deprovisioned. Refer to DLP-122.

GENERAL


STEP PROCEDURE

1 Select action.

To deprovision an EC1 facility with 1677 SONET Link EMA, go to step 2.To deprovision an EC1 facility with TL1, go to step 10.

Deprovision an EC1 Facility with 1677 SONET Link EMA



4 Select the appropriate EC1 group.

5 Examine provisioning information on appropriate EC1 facility.

6 Does facility have Secondary State of LPBK, SDEE, TRM, or UAS?

If yes, the specified EC1 facility cannot be deleted. Go to step 14.If no, go to step 7.

7 Right-click on the appropriate EC1 port and select Unassign.

8 Click Yes.

Deprovision EC1 Facility 4-263


9 Go to step 14.

Deprovision an EC1 Facility with TL1




12 Does facility have SST of LPBK, SDEE, TRM, or UAS?

If yes, DLT-EC1 command cannot be performed on the specified EC1 facility. Go to step 14.If no, go to step 13.

13 Enter DLT-EC1::AID;



Deprovision EC1 Facility4-264


DLP-159Administer EC1 LoopbackPURPOSE

This procedure provides the instructions to administer EC1 loopbacks.

PREREQUISITES

The EC1 facility to place in loopback must have a Primary State (PST) of OOS-AUMA or OOS-MA.

GENERAL

Loopbacks are test features that can be set to loop a signal back at different points along the signal path. The system supports two types of EC1 loopbacks: Facility and Equipment.

Facility loopback is the loopback of a signal received from the network before the switch fabric. The AIS signal is forwarded to the switch fabric. See figure 159-1.

Equipment loopback is the loopback of a signal received from the switch fabric. The signal is still forwarded to the network. See figure .


677-0244-1100404


X AIS

Administer EC1 Loopback 4-265



STEP PROCEDURE


2 Select action.

To administer EC1 loopbacks with 1677 SONET Link EMA, go to step 3.To administer EC1 loopbacks with TL1, go to step 39.

Administer EC1 Loopbacks with 1677 SONET Link EMA

3 Select action.

To retrieve current loopback status of EC1 facility, go to step 4.To establish loopback, go to step 11.To verify loopback status, go to step 24.To release loopback, go to step 31.To end this procedure, go to step 55.


677-0245-1100404


X

Administer EC1 Loopback4-266






7 Right-click appropriate facility and select Loopback>View.


9 Click Close.

10 Go to step 3.

Establish Loopback




14 Right-click appropriate EC1 facility and select Refresh.


16 Select action.


17 Right-click on the EC1 facility and select Service State>Remove.

18 Click Yes.


20 Right-click on the appropriate EC1 facility and select Loopback>Operate. The Operate EC1 Loopback dialog box appears.

21 Select the appropriate loopback type (Equipment or Facility).

22 Click Operate.

23 Go to step 3.







27 Right-click appropriate EC1 facility and select Loopback>View.


29 Click Close.

30 Go to step 3.

Release Loopback





35 Click Yes.


37 Click Yes.

38 Go to step 3.

Administer EC1 Loopbacks with TL1

39 Select action.

To retrieve current loopback status of EC1 facility, go to step 40.To establish loopback, go to step 43. To verify loopback status, go to step 49.To release loopback, go to step 52.To end this procedure, go to step 55.




40 Enter RTRV-LPBK-EC1::[AID];



42 Go to step 39.

Establish Loopback

43 Enter RTRV-EC1::AID; to retrieve the current PST and SST of the EC1 facility.


44 Observe output.

45 Select action.

If the PST for the EC1 facility is IS or OOS-AU, go to step 46.If the PST for the EC1 facility is OOS-AUMA or OOS-MA, go to step 47.


Enter RMV-EC1::AID;


47 Enter OPR-LPBK-EC1::AID:::[LOCN],,,LPBKTYPE;

where:AID=EC1 Access IdentifierLOCN={NEND} Default=NEND.LPBKTYPE={EQUIP, FACILITY}

48 Go to step 39.


49 Enter RTRV-LPBK-EC1::[AID]; to verify the EC1 facility is in loopback.





51 Go to step 39.

Release Loopback

52 Enter RLS-LPBK-EC1::AID:::[LOCN],,,[LPBKTYPE]; to release the EC1 loopback.

where:AID=EC1 Access IdentifierLOCN={NEND} Default=NEND.LPBKTYPE={EQUIP, FACILITY}

53 Enter RST-EC1::AID; to place the facility back in service.


54 Go to step 39.




DLP-160Provision DS1 (T1) FacilityPURPOSE

This procedure provides the instructions to provision a T1 facility.

PREREQUISITES

A DS1 must be embedded within a parent DS3 or VT1.5. The parent signal must be provisioned first. Refer to DLP-115 to provision a T3 facility or DLP-118 to provision a VT1.5 facility.

GENERAL

The ENT-T1 command is used to provision T1 facilities. RTRV-T1 can be used to view the parameters.

To support T1 facilities within STS-1s, the STS-1 STSMAP value must be set to one of the following options:

• ASYNC&VTFLOAT

• ASYNC&VTFLOAT&VTCRS

• ASYNC&SUBPM

• VTFLOAT&SUBPM

• VTFLOAT&VTCRS&SUBPM

To support T1 facilities within electrical T3s, the T3 STSMAP value must be set to one of the following options:

• ASYNC&SUBPM

• VTFLOAT&VTCRS

• VTFLOAT




STEP PROCEDURE

1 Select action.

To provision DS1 facility with 1677 SONET Link EMA, go to step 2.To provision DS1 facility with TL1DAT, go to step 25.

Provision DS1 Facility with 1677 SONET Link EMA


3 Select action.

If T1 is embedded in a T3 or VT1 in an STS-1, go to step 4.If T1 is embedded in stand-alone T3, go to step 14.

Provision T1 Embedded in T3 or VT1 in an STS-1

4 Expand the appropriate facility domain (OC3, OC12, OC48, OC192, EC1).

5 Expand the appropriate facility groups and instances until appropriate facility is displayed.

6 Examine provisioning information on T1 facility.



8 Right-click on T1 facility and select Assign. The Provision STS1 T1 wizard appears.

9 Click Next to continue.



12 Click Finish.

13 Go to step 29.

Provision T1 Embedded in Stand-Alone T3


15 Expand the appropriate T3 group.



16 Select the appropriate T3 facility to display available T1 ports.




19 Right-click on T1 facility and select Assign. The Provision T1 wizard appears.




23 Click Finish.

24 Go to step 29.

Provision DS1 Facility with TL1

25 Enter RTRV-T1::[AID];




If yes, go to step 28.If no, the ENT-T1 command cannot be performed on the specified T1 port. Go to step 29.

28 Enter ENT-T1::AID::::[CKTID=][,FMT=][,TACC=][,TADB=]:[PST],[SST];

where:AID=T1 Access IdentifierOther parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.




DLP-161Deprovision DS1 (T1) FacilityPURPOSE

This procedure provides the instructions to deprovision a DS1 facility.

PREREQUISITES

If the T1 port is cross-connected, the cross-connect must be deprovisioned first. To deprovision T1 cross-connects, refer to DLP-177.

GENERAL

RTRV-T1 is used to retrieve provisioning information on the selected T1 facility. The DLT-T1 command is used to deprovision the T1 facility.


STEP PROCEDURE

1 Select action.

To deprovision DS1 port with 1677 SONET Link EMA, go to step 2.To deprovision DS1 port with TL1, go to step 19.

Deprovision DS1 Port with 1677 SONET Link EMA


3 Select action.

If T1 is embedded in a T3 or VT1 in an STS-1, go to step 4.If T1 is embedded in stand-alone T3, go to step 11.

Deprovision T1 Embedded in T3 or VT1 in an STS-1

4 Expand the appropriate facility domain.





7 Does facility have Secondary State of BUSY, LPBK, TS, or UAS?

If yes, specified T1 facility cannot be deleted. Go to step 23.If no, go to step 8.

8 Right-click on appropriate T1 facility and select Unassign.

9 Click Yes.

10 Go to step 23.

Deprovision T1 Embedded in Stand-Alone T3



13 Select the appropriate T3 facility to display T1 facilities.


15 Does facility have Secondary State of BUSY, LPBK, TS, or UAS?

If yes, specified T1 facility cannot be deleted. Go to step 23.If no, go to step 16.

16 Right-click on appropriate T1 facility and select Unassign.

17 Click Yes.

18 Go to step 23.

Deprovision DS1 Port with TL1




21 Does facility have SST of BUSY, LPBK, TS, or UAS?

If yes, the DLT-T1 command cannot be performed on the specified T1 facility. Go to step 23.If no, go to step 22.



22 Enter DLT-T1::AID;





DLP-162Enable TL1 GatewayPURPOSE

This procedure provides the instructions to enable a TL1 gateway.

PREREQUISITE

Each node in a ring must have a unique TID/SID.

The node that is designated as the gateway must be able to reach all subtended nodes. To forward incoming commands to the appropriate NE, the gateway uses a mapping table. Each entry in this table associates a target identifier (TID) with an IP address and port number. Use the commands ENT-MAP, ED-MAP, DLT-MAP, and RTRV-MAP to create, edit, delete, and retrieve maps. Refer to DLP-173 to administer TL1 Gateway maps. If DCC is enabled, the maps are automatically discovered.

GENERAL

A TL1 IP gateway simplifies the management of a ring. With a TL1 gateway, a ring of network elements can be administered by creating a single TCP session with the assigned gateway NE, which directs incoming TL1 commands to the appropriate NE using the target identifier (TID) supplied with the command. (The optional TID field, if omitted, defaults to the gateway NE.)

The gateway NE uses DCC to forward TL1 commands within the ring and to return messages to the originating management system. If DCC is not enabled, provision is provided to use ethernet to forward TL1 commands.

Nodes serviced by a gateway are called subtended nodes. The gateway is sometimes referred to as the subtending node.

Within a ring, each node must have a unique TL1 system identifier (SID), which enables the gateway NE to forward commands to the appropriate target.


STEP PROCEDURE

1 Log in to the node that will become the gateway.

Enable TL1 Gateway 4-279


2 Enter ED-NE-TL1::::::[RAWPORT=][,TELPORT=][,CONMDE=][,PRMPT=][,CONDITVL=],GWENB=Y;



Enable TL1 Gateway4-280


DLP-163Retrieve Remote Inventory (RI) InformationPURPOSE

This procedure provides the instructions to retrieve Remote Inventory (RI) information for the specified equipment entity.

GENERAL

The following information is provided for each replaceable equipment entity in the NE:

• Software load revision information

• Software part number

• Firmware load revision information

• Part number, item change status, or manufacturing revision

• Part serial number

• Part mnemonic

• Manufacturer

• Factory

• Date of manufacture

• CLEI code

Table 163-A. RI Data Visible per Equipment TypeModule CARDTYPE CLEI PARTNBR SERIAL HWVER FWVER SWVERCCC X X X X X X XSSC X X X X X X XTC X X X X XDS3 X X X X XECC X X X X X XEDFA X X X X XGIGE X X X X XOC-n X X X X XTMUX X X X X X XVSC X X X X XDS3/EC1P X X X X

Retrieve Remote Inventory (RI) Information 4-281


The DISK does not support any Remote Inventory information except recognition of the card type. The FANTRAY supports remote inventory, but it is not displayed in TL1. The ECC and TMUX-301 support the COMPANY, FACTORY, and FDATE visible fields.

The Modular Optical System (MOS) supports the following retrievable RI information: REVISION, PARTNUM, CLEI, FREVISION, FPARTNUM, STREV, STLEN, CKSUM. RI information for MOS can only be retrieved with TL1.

The RTRV-EQPT is used to retrieve Remote Inventory information for the specified equipment entity. The RTRV-MOS command is used to retrieve Remote Inventory information for the MOS.


STEP PROCEDURE

1 Select action.

To retrieve remote inventory information with 1677 SONET Link EMA, go to step 2.To retrieve remote inventory information with TL1, go to step 7.

Retrieve Remote Inventory Information with 1677 SONET Link EMA

2 Expand the Equipment domain in the Scope Pane.

3 Right-click on the appropriate card and select Properties>Remote Inventory. The Remote Inventory table appears.


5 Click Close.

6 Go to step 13.

Retrieve Remote Inventory Information with TL1

7 Select action.

To retrieve RI information for MOS, go to step 8.To retrieve RI information for other equipment, go to step 11.

Retrieve Remote Inventory (RI) Information4-282


Retrieve RI Information for MOS

8 Enter RTRV-MOS::[AID]:::[CMDMDE];

where:AID=MOS or ALLCMDMDE=Command mode (FRCD, NORM)

9 Examine output.

10 Go to step 13.

Retrieve RI Information for Equipment

11 Enter RTRV-EQPT::[AID];

where:AID=Equipment Access Identifier

12 Examine output.


Retrieve Remote Inventory (RI) Information 4-283


Retrieve Remote Inventory (RI) Information4-284


DLP-164Administer Gigabit Ethernet Cross-ConnectionPURPOSE

This procedure provides the instructions to retrieve information on, create, edit, and delete a cross-connection between two Gigabit Ethernet ports.

PREREQUISITES

To establish a Gigabit Ethernet cross-connection, the required equipment and appropriate ports must be provisioned. Refer to DLP-112 to provision equipment. Refer to DLP-154 to provision Gigabit Ethernet ports.

To provision simplex GIGE video broadcast an OC-48 or OC-192 BLSR or UPSR must first be provisioned. Refer to DLP-156 to provision BLSR or DLP-151 to provision UPSR.

To deprovision a GIGE circuit, refer to NTP-121.

GENERAL

The system supports 2-way cross-connections between an EVC facility on a Gigabit Ethernet port and an STS-1 facility on an OC-n facility. See to figure 164-1.


GIGE Port ENT-GIGE

ENT-EVC

677-0228-1062303


EVC

ENT-EQPT

ENT-CRS-GIGE


Administer Gigabit Ethernet Cross-Connection 4-285


An established cross-connection cannot be edited. To change any parameter of an existing cross-connection, the cross-connection must first be deleted (using DLT-CRS-GIGE), and then a new cross-connection must be created with different parameter settings (using ENT-CRS-GIGE).

GigE Broadcast Applications

The system also supports drop and continue connections for GigE virtual concatenated cross-connects through OC-48 and OC-192 in UPSR and BLSR configurations allowing a broadcast video application. The node at which the video source feeds the ring is designated the head end. Other nodes on the ring at which the video signal is dropped are designated as tail ends.

BLSR configurations require 2WAY cross-connections at the head end node and the final tail end node. 1WAYDC, drop and continue, cross-connections are used at the tail end nodes. Figure 164-2 demonstrates provisioning on the BLSR nodes.

UPSR configurations require a 2WAY cross-connection at the head end and 1WAYDC cross-connections at the tail ends. Figure 164-2 demonstrates provisioning on the UPSR nodes.

DROP=N is provisioned on the head end node to suppress transmit defects. DROP=Y is provisioned on all tail end node to suppress receive defects. The DROP parameter is valid only if MODE=SIMPLEX.

Administer Gigabit Ethernet Cross-Connection4-286


Figure 164-2. GIGE Video Broadcast Applications in BLSR and UPSR

GIGE VIDEO SOURCE

GIGE PORT GIGE PORT

GIG

E P

OR

TG

IGE

PO

RT

GIGE PORT

IDLE

677-0386

032406

GIGE VIDEO SOURCE

GIGE PORT GIGE PORT

GIG

E P

OR

TG

IGE

PO

RT

GIGE PORT

IDLE

SIMPLEX GIGE

VIDEO BROADCAST

ON OC-48/OC-192 BLSR

SIMPLEX GIGE

VIDEO BROADCAST

ON OC-48/OC-192 UPSR

HEAD NODE

MODE=SIMPLEX

DROP=N

CCT = 2WAY

HEAD NODE

MODE=SIMPLEX

DROP=N

CCT = 2WAY

FINAL TAIL NODE

MODE=SIMPLEX

DROP=Y

CCT = 2WAY

TAIL 3 NODE

MODE=SIMPLEX

DROP=Y

CCT = 1WAYDC

TAIL 3 NODE

MODE=SIMPLEX

DROP=Y

CCT = 1WAYDC

TAIL 4 NODE

MODE=SIMPLEX

DROP=Y

CCT = 1WAYDC

TAIL 2 NODE

MODE=SIMPLEX

DROP=Y

CCT = 1WAYDC

TAIL 2 NODE

MODE=SIMPLEX

DROP=Y

CCT = 1WAYDC

TAIL 1 NODE

MODE=SIMPLEX

DROP=Y

CCT = 1WAYDC

TAIL 1 NODE

MODE=SIMPLEX

DROP=Y

CCT = 1WAYDC

BLSR

UPSR



Cross-connects to all the EVC timeslots specified in the MAP configuration of the GIGE facility should be provisioned for the traffic to pass.

The cross-connection type (CCT) parameter indicates the type of the cross-connection. See figure 164-3 for cross-connection types. Only certain cross-connections and associated parameter combinations are allowed for this command. Refer to table 164-A for allowed cross-connections and the restrictions on parameters.

Figure 164-3. GIGE Cross-Connection Types

FROMTO

2WAY (CCT)

FROM

TO

2WAY (CCT)

FROM

TO

TRIBUTARY

1WAY (CCT)

RING RING

FROM* FROM*

TO

TRIBUTARY

1WAY (CCT)

RING RING

*EITHER SIDE MAY BE SPECIFIED AS FROM

SPECIFIED SIDE IS PREFERRED SIDE

FROM

TO

UPSR1 UPSR1

2WAY (CCT)

TRIBUTARY

ACCESS TO ACCESS UPSR ACCESS TO RING BLSR ACCESS TO RING

UPSR DROPAND CONTINUE BLSR DROPAND CONTINUE

677-0384

033106




STEP PROCEDURE

1 Select action.

To administer GIGE cross-connection with 1677 SONET Link EMA, go to step 2.To administer GIGE cross-connection with TL1, go to step 41.

Administer GIGE Cross-Connection with 1677 SONET Link EMA

2 Select action.

To create GIGE cross-connection, go to step 3.To retrieve GIGE cross-connection, go to step 22.

Table 164-A. GIGE Allowed Cross-Connections and Restrictions Cross-Connection Category

Cross-Connection Description

Restriction on ParametersFROM TO CCT Ring

Switching Parameter (SWPDIP etc.)

Allowed PREFERRED value

Access to access

Access to access

Unprotected EVC

Unprotected STS1

2WAY Not allowed Not allowed

Access-to-ring (Duplex GigE)

Access toUPSR

Unprotected EVC

UPSR ring port STS1

2WAY Allowed EAST or WEST

Access toBLSR

Unprotected EVC

BLSR ring port STS1


Access-to-ring (Simplex GigE)

Access toUPSR

Unprotected EVC

UPSR ring port STS1

2WAY Not allowed EAST or WEST

Access toBLSR

Unprotected EVC

BLSR ring port STS1


Drop-and-continue (Simplex GigE)

UPSR ring1-way drop-and-continue

UPSR ring port STS1

Unprotected EVC

1WAYDC Allowed EAST or WEST

BLSR ring 1-way drop-and-continue

BLSR ring port STS1

Unprotected EVC

1WAYDC Not allowed Not allowed



To modify GIGE cross-connection, go to step 22.To delete GIGE cross-connection, go to step 22.To end this procedure, go to step 52.

Create GIGE Cross-Connection





7 Double-click on facility types and groups until appropriate EVC facility is shown.

8 Select EVC facility.

9 Click OK.



12 Double-click on facility types and groups until appropriate STS-1 facility is shown.

13 Select STS-1 facility.

14 Click OK.







21 Go to step 2.



Retrieve, Modify, or Delete GIGE Cross-Connection


23 Under Facility Type, select GIGE from the drop-down list.











33 Go to step 2.




36 Click Delete.




40 Go to step 2.



Administer GIGE Cross-Connection with TL1

41 Select action.

To retrieve GIGE cross-connection information, go to step 42.To create a GIGE cross-connection, go to step 44.To modify a GIGE cross-connection, go to step 46.To delete a GIGE cross-connection, go to step 49.To end this procedure, go to step 52.

Retrieve Gigabit Ethernet Cross-Connection Information

42 Enter RTRV-CRS-GIGE::AID:::[CCT];

where:AID=EVC or STS1 Access IdentifierCCT=Cross-connect type (2WAY or 1WAYDC)

43 Go to step 41.

Create Gigabit Ethernet Cross-Connection

44 Enter ENT-CRS-GIGE::FROM,TO:::CCT:[CKTID=][,CKTADDR=][,CKTNBR=][,SWPDIP=][,SWUNEQP=][,PREFERRED=][,RVRTV=][,RVRTTIM=];

where:FROM=Access Identifier of source facility (EVC AID associated with the GIGE)TO=Access Identifier of destination facility (STS-1 AID to transport the GIGE facility)CCT=2WAY or 1WAYDCOther parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

45 Go to step 41.

Modify Gigabit Ethernet Cross-Connection




47 Enter ED-CRS-GIGE::FROM,TO:::,:[CKTID=][,CKTADDR=][,CKTNBR=][,SWPDIP=][,SWUNEQP=][,PREFERRED=][,RVRTV=][,RVRTTIM=];

where:FROM=Access Identifier of source facility (EVC AID associated with the GIGE)TO=Access Identifier of destination facility (STS-1 AID to transport the GIGE facility)Other parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

48 Go to step 41.

Delete Gigabit Ethernet Cross-Connection


50 Enter DLT-CRS-GIGE::FROM,TO;

where:FROM=Access Identifier of source facility (EVC AID associated with the GIGE)TO=Access Identifier of destination facility (STS-1 AID to transport the GIGE facility)

51 Go to step 41.




DLP-165Set Gigabit Ethernet PM ModePURPOSE

This procedure provides the instructions to set or change Performance Monitoring (PM) mode for Gigabit Ethernet ports. The PM mode controls the data collection for specific types of PM data (path, line, segment, intermediate node).

GENERAL




STEP PROCEDURE

1 Select action.

To set GIGE PM mode with 1677 SONET Link EMA, go to step 2.To set GIGE PM mode with TL1, go to step 11.

Set GIGE PM Mode with 1677 SONET Link EMA


3 Expand GIGE domain.


5 Right-click appropriate GIGE facility and select Performance Monitoring>PM Mode. Current PM mode parameters are displayed in the table.




Set Gigabit Ethernet PM Mode 4-295





8 Click Apply.

9 Click Close.

10 Go to step 14.

Set GIGE PM Mode with TL1

11 Enter RTRV-PMMODE-GIGE::AID:::[LOCN];

where:AID=GIGE Access IdentifierLOCN={ALL, NEND}


13 Enter SET-PMMODE-GIGE::AID:::LOCN,MODETYPE,[PMSTATE];

where:AID=GIGE Access IdentifierLOCN={ALL, NEND}MODETYPE={ALL, P}PMSTATE={OFF, ON}


Set Gigabit Ethernet PM Mode4-296


DLP-166Set Gigabit Ethernet PM Threshold LevelsPURPOSE

This procedure provides the instructions to set Performance Monitoring (PM) threshold levels for Gigabit Ethernet ports.

GENERAL



The SET-TH-GIGE command is used to designate PM threshold levels for Gigabit Ethernet ports. For each type of error (parameter) being monitored, a threshold level with either a 15-minute or 24-hour period may be set. If the number of errors collected exceeds the threshold level within the time selected, the system generates a Threshold Crossing Alert (TCA).


STEP PROCEDURE

1 Select action.

To set GIGE PM threshold levels with 1677 SONET Link EMA, go to step 2.To set GIGE PM threshold levels with TL1, go to step 11.

Set GIGE PM Threshold Levels with 1677 SONET Link EMA



4 Expand appropriate GIGE group.

5 Right-click appropriate GIGE facility and select action.


Set Gigabit Ethernet PM Threshold Levels 4-297






8 Click Apply.

9 Click Close.

10 Go to step 14.

Set GIGE PM Threshold Levels with TL1

11 Enter RTRV-TH-GIGE::[AID]:::[MONTYPE],,[TMPER];

where:Parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.


13 Enter SET-TH-GIGE::AID:::MONTYPE,THLEV,,,[TMPER];

where:AID=GIGE Access IdentifierMONTYPE=Monitored type. See Commands and Messages manual (PN 3EM13852AD) for possible values.THLEV={DFLT, (0-4294967295)}TMPER={15-MIN, 1-DAY}


Set Gigabit Ethernet PM Threshold Levels4-298


DLP-167Report Gigabit Ethernet PM DataPURPOSE

This procedure provides the instructions to report Performance Monitoring (PM) data and initialize (reset) the collection register for Gigabit Ethernet ports.

GENERAL




STEP PROCEDURE

1 Select action.

To report GIGE PM data with 1677 SONET Link EMA, go to step 2.To report GIGE PM data with TL1, go to step 20.

Report GIGE PM Data with 1677 SONET Link EMA

2 Select action.


Retrieve PM Data



5 Expand the appropriate GIGE group to display GIGE facilities.



Report Gigabit Ethernet PM Data 4-299



8 Click Close.

9 Go to step 25.




12 Expand the appropriate GIGE group to display GIGE facilities.







17 Click Apply.

18 Click Close.

19 Go to step 25.

Report GIGE PM Data with TL1

20 Select action.


Report Gigabit Ethernet PM Data4-300


Retrieve PM Data

21 Enter RTRV-PM-GIGE::[AID]:::[MONTYPE],[MONLEV],,,[TMPER],[MONDAT],[MONTM];



23 Go to step 25.


24 Enter INIT-REG-GIGE::AID:::[MONTYPE],[MONVAL],[LOCN],,[TMPER];

where:AID=GIGE Access IdentifierTMPER=15-MIN or 1-DAYOther parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.


Report Gigabit Ethernet PM Data 4-301


Report Gigabit Ethernet PM Data4-302


DLP-168Enable/Disable Automatic Generation of Squelch and Ring MapsPURPOSE

This procedure provides the instructions to enable or disable the automatic generation of squelch and ring maps on a per BLSR basis.

GENERAL

A ring map is a map (sequence) of node IDs within the ring.

The BLSR node maintains a squelch map containing the entry and exit node IDs for every provisioned working STS path on the ring (added, dropped, and through).

The ENT-FFP-OC48/OC192 command associates a working OC48/OC192 facility with a protecting OC48/OC192 facility. Upon completion of the command, the Fast Facility Protection (FFP) group is created and the two facilities function as protected facilities.

Automap is an automatic provisioning feature where BLSR squelch and ring maps are learned. This feature is enabled using the ENT-FFP-OC48/192 command and setting AUTOMAP=Y. When this feature is enabled, the node identifier of the local node needs to be only specified. If this feature is not enabled, ring map must be entered via ED-RINGMAP command, and squelch information must be entered via the ED-SQLMAP command for the BLSR to function properly.

Until a valid ring map is created, the NE will transmit an APSCDFLTK alarm. While this alarm is present, no BLSR protection is available.

The RINGID parameter of the ENT-FFP-OC48/OC192 command must be properly provisioned if automatic learning of squelch maps and ring maps is enabled. This parameter identifies a BLSR within a shelf and must be unique to the system and common across a BLSR. It has no significance when the automatic learning protocol is not enabled.


STEP PROCEDURE

1 Select action.

To enable/disable automatic map generation with 1677 SONET Link EMA, go to step 2.To enable/disable automatic map generation with TL1, go to step 31.

Enable/Disable Automatic Generation of Squelch and Ring Maps 4-303


Enable/Disable Automatic Map Generation with 1677 SONET Link EMA

2 Select action.

To enable automatic map generation, go to step 3.To disable automatic map generation, go to step 17.

Enable Automatic Map Generation


4 Expand the appropriate OC-n domain (OC48 or OC192).


6 Observe protection pairs in Result Pane.

7 Is BLSR protection pair provisioned?


8 Right-click on appropriate BLSR protection pair and select Properties>General.

9 Scroll to the Automap parameter, double-click in the box, and select Y from the drop-down list.

10 Go to step 45.




When the Auto Map page is displayed, select Yes from the drop-down menu.


15 Click Finish.

16 Go to step 45.

Disable Automatic Map Generation


Enable/Disable Automatic Generation of Squelch and Ring Maps4-304




20 Observe protection pairs in Result Pane.

21 Is BLSR already provisioned?



23 Scroll to the Automap parameter, double-click in the box, and select N from the drop-down list.

24 Go to step 45.




When the Auto Map page is displayed, select No from the drop-down menu.


29 Click Finish.

30 Go to step 45.

Enable/Disable Automatic Map Generation with TL1

31 Select action.

To enable automatic map generation, go to step 32.To disable automatic map generation, go to step 39.

Enable Automatic Map Generation


where:OCn=Optical facility type (OC48 or OC192)AID=OC48 or OC192 Access Identifier



33 Observe output.

34 Is BLSR protection pair provisioned?


35 Enter ED-FFP-OCn::PROTECTED_ID,[PROTECTING_ID]::::,AUTOMAP=Y;

where:OCn=Optical facility type (OC48 or OC192)PROTECTED_ID=West OC-48/192 in BLSRPROTECTING_ID=East OC-48/192 in BLSR

36 Go to step 45.

37 Enter ENT-FFP-OCn::PROTECTED_ID,PROTECTING_ID::::PTYPE=BLSR2[,PSDIRN=][APSTRC=][,RVRTV=][,RVRTTIM=],NODEID=[,NODEDESCR=],AUTOMAP=Y,RINGID=;

where:OCn=Optical facility type (OC48 or OC192)PROTECTED_ID=West OC-48/192 in BLSRPROTECTING_ID=East OC-48/192 in BLSRNODEID=Node identifier of the BLSR node {0-15}RINGID=Ring identifier, identifies a BLSR within a shelf. Must be unique to the system. {6 alphanumeric characters}Other parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

38 Go to step 45.

Disable Automatic Map Generation


where:OCn=Optical facility type (OC48 or OC192)AID=OC48 or OC192 Access Identifier

40 Observe output.

41 Is BLSR already provisioned?




42 Enter ED-FFP-OCn::PROTECTED_ID,[PROTECTING_ID]::::,AUTOMAP=N;

where:OCn=Optical facility type (OC48 or OC192)PROTECTED_ID=West OC-48/192 in BLSRPROTECTING_ID=East OC-48/192 in BLSR

43 Go to step 45.

44 Enter ENT-FFP-OCn::PROTECTED_ID,PROTECTING_ID::::PTYPE=BLSR2[,PSDIRN=][APSTRC=][,RVRTV=][,RVRTTIM=],NODEID=[,NODEDESCR=],AUTOMAP=N,RINGID=;

where:OCn=Optical facility type (OC48 or OC192)PROTECTED_ID=West OC-48/192 in BLSRPROTECTING_ID=East OC-48/192 in BLSRNODEID=Node identifier of the BLSR node {0-15}RINGID=Ring identifier, identifies a BLSR within a shelf. Must be unique to the system. {6 alphanumeric characters}Other parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.




DLP-169Restart Laser for OC-n FacilityPURPOSE

This procedure provides the instructions to restart the laser for an OC-n facility disabled by the Automatic Laser Shutoff (ALS) system.

GENERAL

This procedure allows the laser to be pulsed under manual control. The pulse allows the far end to detect that a broken fiber has been repaired. When the far end turns its laser on, the current end can keep the laser on.

RESTART mode briefly enables the laser to attempt to restart in both directions. TEST mode enables the laser for a longer period for testing purposes.

If the laser is not currently disabled by the ALS system, this procedure completes successfully, but has no effect.


STEP PROCEDURE

1 Enter OPR-ALS-OCn::AID:::[MODE];

where:OCn=Optical facility type (OC3, OC12, OC48, or OC192)AID=OCn Access IdentifierMODE=(RESTART, TEST)


Restart Laser for OC-n Facility 4-309


Restart Laser for OC-n Facility4-310


DLP-170Set EC1 PM Threshold LevelsPURPOSE

This procedure provides the instructions to set Performance Monitoring (PM) threshold levels for EC1 ports.

GENERAL



The SET-TH-EC1 command is used to designate PM threshold levels for EC1 ports. For each type of error (parameter) being monitored, a threshold level with either a 15-minute or 24-hour period may be set. If the number of errors collected exceeds the threshold level within the time selected, the system generates a Threshold Crossing Alert (TCA).


STEP PROCEDURE

1 Select action.

To set EC1 PM threshold levels with 1677 SONET Link EMA, go to step 2.To set EC1 PM threshold levels with TL1, go to step 11.

Set EC1 PM Threshold Levels with 1677 SONET Link EMA




5 Right-click appropriate EC1 facility and select action.


Set EC1 PM Threshold Levels 4-311






8 Click Apply.

9 Click Close.

10 Go to step 14.

Set EC1 PM Threshold Levels with TL1

11 Enter RTRV-TH-EC1::[AID]:::[MONTYPE],,[TMPER];



13 Enter SET-TH-EC1::AID:::MONTYPE,THLEV,,,[TMPER];

where:AID=EC1 Access IdentifierMONTYPE=Monitored type. See Commands and Messages manual (PN 3EM13852AD) for possible values.THLEV={DFLT, (0-1048575)}TMPER={15-MIN, 1-DAY}


Set EC1 PM Threshold Levels4-312


DLP-171Provision Ethernet Virtual Concatenation (EVC) PortPURPOSE

This procedure provides the instructions to provision an Ethernet Virtual Concatenation (EVC) port within a Gigabit Ethernet port. An EVC carries Ethernet bandwidth equivalent of an STS-1 facility.

PREREQUISITES

A Gigabit Ethernet port must be provisioned before EVC facilities can be provisioned. Refer to DLP-154 to provision Gigabit Ethernet port. To create a GIGE cross-connection, refer to DLP-164. To deprovision a GIGE circuit, refer to NTP-121.

GENERAL

EVC and the MAP configuration in the Gigabit Ethernet facility are independent. The relation is only when cross-connects to all the EVC timeslots specified in the MAP option are configured for the traffic to pass. The user can create facilities on any timeslot (1-24), and any number of them. Each Gigabit Ethernet port can be provisioned with 24 different addressable EVC facilities. Refer to figure 171-1.

The ENT-EVC command is used to provision EVC facilities. RTRV-EVC can be used to view the parameters.



GIGE Port ENT-GIGE

ENT-EVC

677-0228-1062303


EVC

ENT-EQPT

ENT-CRS-GIGE


Provision Ethernet Virtual Concatenation (EVC) Port 4-313


STEP PROCEDURE

1 Select action.

To provision EVC port with 1677 SONET Link EMA, go to step 2.To provision EVC port with TL1, go to step 11.

Provision EVC Port with 1677 SONET Link EMA



4 Expand the appropriate GIGE group.

5 Click the appropriate GIGE facility to display the available EVC facilities.


7 Does facility have Primary State and Secondary State of OOS-MA, UAS?

If yes, go to step 8.If no, the specified EVC facility cannot be provisioned. Go to step 15.

8 Right-click the appropriate EVC port and select Assign. A message window appears.

9 Click Yes.

10 Go to step 15.

Provision EVC Port with TL1

11 Enter RTRV-EVC::[AID];

where:AID=EVC Access Identifier



If yes, go to step 14.If no, the ENT-EVC command cannot be performed on the specified EVC port. Go to step 15.

Provision Ethernet Virtual Concatenation (EVC) Port4-314


14 Enter ENT-EVC::AID;



Provision Ethernet Virtual Concatenation (EVC) Port 4-315


Provision Ethernet Virtual Concatenation (EVC) Port4-316


DLP-172Deprovision Ethernet Virtual Concatenation (EVC) PortPURPOSE

This procedure provides the instructions to deprovision an Ethernet Virtual Concatenation (EVC) port.

PREREQUISITES

If the EVC port is cross-connected, the cross-connect must be deprovisioned first. To deprovision EVC cross-connects, refer to DLP-164.

GENERAL

RTRV-EVC is used to retrieve provisioning information on the selected EVC facility. The DLT-EVC command is used to deprovision the T1 facility.


STEP PROCEDURE

1 Select action.

To deprovision EVC port with 1677 SONET Link EMA, go to step 2.To deprovision EVC port with TL1, go to step 11.

Deprovision EVC Port with 1677 SONET Link EMA



4 Expand the appropriate GIGE group.

5 Click the appropriate GIGE facility to display the EVC facilities.


7 Does facility have Secondary State of DSBLD or UAS?

If yes, the specified EVC facility cannot be deleted. Go to step 15.If no, go to step 8.

Deprovision Ethernet Virtual Concatenation (EVC) Port 4-317


8 Right-click the appropriate EVC port and select Unassign. A message window appears.

9 Click Yes.

10 Go to step 15.

Deprovision EVC Port with TL1

11 Enter RTRV-EVC::[AID];



13 Does facility have SST of DSBLD or UAS?

If yes, the DLT-EVC command cannot be performed on the specified EVC facility. Go to step 15.If no, go to step 14.

14 Enter DLT-EVC::AID;



Deprovision Ethernet Virtual Concatenation (EVC) Port4-318


DLP-173Administer TL1 Gateway MapPURPOSE

This procedure provides the instructions to administer the mapping used by a TL1 gateway.

PREREQUISITE

Each node in a ring must have a unique TID/SID. Refer to DLP-174.

GENERAL

A TL1 IP gateway simplifies the management of a network. With a TL1 gateway, a group of DCC-interconnected of network elements can be administered by creating a single TCP session with the assigned gateway NE, which directs incoming TL1 commands to the appropriate NE using the target identifier (TID) supplied with the command. (The optional TID field, if omitted, defaults to the gateway NE.)

The gateway NE uses DCC to forward TL1 commands and to return messages to the originating management system.

Nodes serviced by a gateway are called subtended nodes. The gateway is sometimes referred to as the subtending node.

The node that is designated as the gateway must be able to reach all subtended nodes. To forward incoming commands to the appropriate NE, the gateway uses a mapping table. Each entry in this table associates a target identifier (TID) with an IP address and port number.

Once the TL1 gateway mapping is defined, refer to DLP-162 to enable the gateway.

The TL1 gateway mapping table associates TIDs with IP address/port pairs. The RTRV-MAP command retrieves the static mappings that are configured using the ENT-MAP and ED-MAP commands, and also the dynamic mappings established by the OSPF software on the 1677 SONET Link.


STEP PROCEDURE

1 Select action.

To retrieve gateway mapping table entries, go to step 2.To create a gateway mapping table entry, go to step 4.To change a gateway mapping table entry, go to step 6.

Administer TL1 Gateway Map 4-319


To delete a gateway mapping table entry, go to step 8.To end this procedure, go to step 10.

Retrieve TL1 Gateway Mapping Entries

2 Enter RTRV-MAP::[NETID];

where:NETID=TID of the remote node. Default=TID of current node.

3 Go to step 1.

Create TL1 Gateway Mapping Entry

4 Enter ENT-MAP::NETID:::IPADDR,[PORT];

where:NETID=TID of the NE where the mapping table residesIPADDR=IP address to be added to the mapping tablePORT=Associated IP port of the TL1 raw-mode server on the remote NE to be added to the mapping table. Default=3082.

5 Go to step 1.

Change TL1 Gateway Mapping Entry

6 Enter ED-MAP::NETID:::[IPADDR],[PORT];

where:NETID=TID of the NE to be added to the mapping tableIPADDR=IP address of the remote NE in the mapping table entryPORT=Associated IP port of the TL1 raw-mode server on the remote NE to be added to the mapping table. Default=3082.

7 Go to step 1.

Delete TL1 Gateway Mapping Entry

8 Enter DLT-MAP::NETID;

where:NETID=TID of the NE to be deleted from the mapping table

9 Go to step 1.


Administer TL1 Gateway Map4-320


DLP-174Retrieve/ Change Site IdentifierPURPOSE

Follow this procedure to retrieve or change the unique identifier for the NE.

GENERAL

The site identifier appears in command response messages, and is used as the target identifier when addressing an NE through a TL1 gateway.

For the 1677 SONET Link, the default site identifier is ALCATEL-1677SL.

If the RTRV-HDR command is issued with the PC parameter not specified, the output response header contains the network element's target identifier, date, and time.

If the RTRV-HDR command is issued with the PC parameter specified, the output response contains the network element's target identifier, model, notification code, and software load.


STEP PROCEDURE

1 Select action.

To retrieve current site identifier, go to step 2.To change site identifier, go to step 5.To end this procedure, go to step 7.

Retrieve Site Identifier

2 Enter RTRV-HDR::::::[PC];

where:PC=PC (Privilege command).

3 Examine output to determine current site identifier, which appears on the first line.

4 Go to step 1.

Retrieve/ Change Site Identifier 4-321


Change Site Identifier

5 Enter SET-SID:::::SID;

where:SID=Site identifier

6 Go to step 1.


Retrieve/ Change Site Identifier4-322


DLP-175Reprogram Equipment Flash MemoryPURPOSE

This procedure provides instructions to reprogram flash memory on a Common Control Card (CCC), the DCC or SWC on an STS switch card (SSC), or TMUX card. The source files are located on CCC flash disks (A and B).

GENERAL

The processor boards supporting this command are:

• CCC (boot ROM)

• SWC (boot ROM)

• DCC (boot ROM)

• TMUX (FPGA)


STEP PROCEDURE

1 Select action.

To reprogram equipment flash memory with 1677 SONET Link EMA, go to step 2.To reprogram equipment flash memory with TL1, go to step 29.

Reprogram Equipment Flash Memory with 1677 SONET Link EMA

2 Click Equipment domain to display current cards in system.

Table 175-A. TMUX Working and Protection ModulesWorking TMUX Slots Protection TMUX SlotsIOC-{2,4,6,13,15,17}-{A,B} IOC-{1,3,5,12,14,16}-{A,B}

Reprogram Equipment Flash Memory 4-323


3 Examine primary state and secondary state in Result Pane. Is Primary State IS, OOS-MA, OOS-AUMA, or OOS-MA,UAS?

If IS, go to step 4.If OOS-MA or OOS-AUMA, go to step 14.If OOS-MA,UAS, card is deprovisioned and cannot be reprogrammed. Go to step 45.


5 Click Yes.

6 Is card to be reprogrammed a TMUX card?


7 Is TMUX card to be reprogrammed the working or protection card? Refer to table 175-A.

If working card, go to step 8.If protection card, go to step 11.

8 Right-click on appropriate working TMUX card and select Switch>Inhibit Switch to Working.

9 Click Yes.

10 Go to step 13.

11 Right-click on appropriate protection TMUX card and select Switch>Inhibit Switch to Protection.

12 Click Yes.

13 CAUTION: Possibility of service interruption. If board to be reprogrammed is not protected, this operation may be service affecting.

14 Right-click on appropriate card (CCC, DCC, SWC, or TMUX) and select Reprogram. The Reprogram Equipment wizard appears.


16 On the Name of the .ROM file page, enter the name of the file (including path) to be programmed into EEPROM(s).

17 Click Next.

Reprogram Equipment Flash Memory4-324



19 Click Finish.

20 Wait for command to complete.

21 Is reprogrammed card a TMUX card?


22 Is reprogrammed TMUX card the working or protection card? Refer to table 175-A.


23 Right-click on appropriate working TMUX card and select Switch>Allow Switch to Working.

24 Click Yes.

25 Go to step 45.

26 Right-click on appropriate protection TMUX card and select Switch>Allow Switch to Protection.

27 Click Yes.

28 Go to step 45.

Reprogram Equipment Flash Memory with TL1

29 Enter RTRV-EQPT::[AID];

where: AID=Equipment Access Identifier of card to reprogram

30 Examine output. Is PST IS, OOS-MA, OOS-AUMA, or OOS-MA,UAS?

If IS, go to step 31.If OOS-MA or OOS-AUMA, go to step 37.If OOS-MA,UAS, card is deprovisioned and cannot be reprogrammed. Go to step 45.


where: AID=Equipment Access Identifier of card to reprogram



32 Is card to be reprogrammed a TMUX card?


33 Is TMUX card to be reprogrammed the working or protection card? Refer to table 175-A.


34 Enter INH-SWTOWKG-EQPT::AID;

where: AID=Access Identifier of working TMUX card to reprogram

35 Go to step 37.


where: AID=Access Identifier of protection TMUX card to reprogram

37 CAUTION: Possibility of service interruption. If board to be reprogrammed is not protected, this operation may be service affecting.

38 Enter RPGM-EQPT::AID::::CARDTYPE=[,DIRECTORY=];

where:AID=Equipment Access Identifier of card to reprogramCARDTYPE=Module type of board that needs to be upgraded with a new firmware. (CCC, SSC-DCC, SSC-SWC, TMUX)DIRECTORY=Directory name from which the file is to be copied, enclosed in quotation marks.

39 Wait for command to complete.

40 Is reprogrammed card a TMUX card?


41 Is reprogrammed TMUX card the working or protection card? Refer to table 175-A.


42 Enter ALW-SWTOWKG-EQPT::AID;

where: AID=Access Identifier of working TMUX card



43 Go to step 45.

44 Enter ALW-SWTOPROTN-EQPT::AID;

where: AID=Access Identifier of protection TMUX card




DLP-176Retrieve Node IP AddressesPURPOSE

This procedure provides instructions to retrieve the IP addresses for a node.

GENERAL

There is no GUI function to retieve the NE IP address. It must be retrieved using TL1.


STEP PROCEDURE

1 Enter the TL1 command RTRV-NE;

2 Examine output. The IPADDR parameter identifies the IP address of the node.


Retrieve Node IP Addresses 4-329


Retrieve Node IP Addresses4-330


DLP-177Administer DS1 Cross-ConnectionPURPOSE

This procedure provides the instructions to retrieve information on, create, modify, and delete a 2-way cross-connection between two DS1 facilities, or between a DS1 facility and a VT1 facility.

PREREQUISITE

To establish a DS1 cross-connection, the required facilities must be provisioned. Refer to DLP-160 to provision DS1 facilities. Refer to DLP-118 to provision VT1 facilities.

GENERAL

The system supports a 2-way cross-connection between two DS1 facilities or between a DS1 facility and a VT1 facility. This procedure is used to administer cross-connections between two DS1 facilities or between a DS1 facility and a VT1 facility.

If the connection is between a DS1 facility and a VT1 facility, the DS1 facility must be specified in the FROM parameter.


STEP PROCEDURE

1 Select action.

To administer DS1 cross-connection with 1677 SONET Link EMA, go to step 2.To administer DS1 cross-connection with TL1, go to step 39.

Administer DS1 Cross-Connection with 1677 SONET Link EMA

2 Select action.

To create DS1 cross-connection, go to step 3.To retrieve DS1 cross-connection, go to step 21.To modify DS1 cross-connection, go to step 21.To delete DS1 cross-connection, go to step 21.To end this procedure, go to step 50.



Create T1 Cross-Connection





7 Double-click on facility types and groups until appropriate T1 facility is shown.

8 Select T1 facility.

9 Click OK.



12 Double-click on facility types and groups until appropriate T1 or VT1 facility is shown.

13 Select T1 or VT1 facility.

14 Click OK.






20 Go to step 2.

Retrieve, Modify, or Delete T1 Cross-Connection


22 Under Facility Type, select T1 from the drop-down list.








27 Double-click in box under Circuit Name, enter a new Circuit ID for the connection, and press the Enter key.




31 Go to step 2.




34 Click Delete.




38 Go to step 2.

Administer DS1 Cross-Connection with TL1

39 Select action.

To retrieve DS1 cross-connection information, go to step 40.To create DS1 cross-connection, go to step 42.To modify DS1 cross-connection, go to step 44.To delete DS1 cross-connection, go to step 47.To end this procedure, go to step 50.



Retrieve DS1 Cross-Connection Information

40 Enter RTRV-CRS-T1::AID:::[CCT];

where:AID=T1 Access IdentifierCCT=Cross-connect type (2WAY)

41 Go to step 39.


42 Enter ENT-CRS-T1::FROM,TO:::2WAY:[CKTID=];

where:FROM=Access Identifier of source facilityTO=Access Identifier of destination facilityOther parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

43 Go to step 39.

Modify DS1 Cross-Connection


45 Enter ED-CRS-T1::FROM,TO::::[CKTID=];

where:FROM=Access Identifier of source facilityTO=Access Identifier of destination facilityOther parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

46 Go to step 39.

Delete DS1 Cross-Connection




48 Enter DLT-CRS-T1::FROM,TO;

where:FROM=Access Identifier of source facilityTO=Access Identifier of destination facility

49 Go to step 39.




DLP-178Report DS1 PM DataPURPOSE

This procedure provides the instructions to report Performance Monitoring (PM) data and initialize (reset) the collection register for DS1 facilities.

GENERAL




STEP PROCEDURE

1 Select action.

To report DS1 PM data with 1677 SONET Link EMA, go to step 2.To report DS1 PM data with TL1, go to step 20.

Report DS1 PM Data with 1677 SONET Link EMA

2 Select action.


Retrieve PM Data









8 Click Close.

9 Go to step 25.











17 Click Apply.

18 Click Close.

19 Go to step 25.

Report DS1 PM Data with TL1

20 Select action.




Retrieve PM Data

21 Enter RTRV-PM-T1::[AID]:::[MONTYPE],[MONLEV],,,[TMPER],[MONDAT],[MONTM];



23 Go to step 25.


24 Enter INIT-REG-T1::AID:::[MONTYPE],[MONVAL],[LOCN],,[TMPER];

where:AID=T1 Access IdentifierTMPER=15-MIN or 1-DAYOther parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.




DLP-179Retrieve VSC and TMUX UsagePURPOSE

This procedure provides instructions to retrieve information about the facilities that are using resources from a VSC or TMUX card and to get a summary of remaining capacity.

GENERAL


STEP PROCEDURE

1 Select action.

To retrieve resource usage with 1677 SONET Link EMA, go to step 2.To retrieve resource usage with TL1, go to step 8.

Retrieve Resource Usage with 1677 SONET Link EMA

2 Expand the Equipment domain in the Scope Pane.

3 Right-click on the appropriate card (TMUX or VSC) and select Retrieve Resource Usage.

4 Click Retrieve.

5 Observe information in window.

6 Click Cancel.

7 Go to step 10.

Retrieve Resource Usage with TL1

8 Enter RTRV-USAGE-EQPT::[AID]:::[TYPE][,SUMMARY];

where:AID=VSC or TMUX Access Identifier or ALLTYPE=Resource module type (All, TMUX, VTSC)SUMMARY=Retrieve summary information. (Y or N).

Retrieve VSC and TMUX Usage 4-341


9 Examine output.


Retrieve VSC and TMUX Usage4-342


DLP-180Inhibit/Allow Protection SwitchingPURPOSE

This procedure provides instructions to control protection switching for DS3, ECC, TMUX, and VSC modules in the event of excessive automatic switching.

GENERAL

Protection switching reduces possible service-effect by switching traffic to an alternate copy.

This procedure describes how to inhibit and allow both automatic and manual protection switching for DS3, ECC, TMUX, and VSC modules. Traffic on a working module can be prevented from switching to a protection module, and traffic on a protection module can be prevented from switching to a working module.

The INH-SWTOPROTN-EQPT command is used to perform "Lockout a Working" operation for the specified working module and to perform "Lockout of Protection" operation for the specified protection module. It applies to working and protection DS3 and ECC modules and to protection TMUX and VSC modules.

Executing an INH-SWTOPROTN-EQPT command sets a SST of PSI (Protection Switch Inhibited) for the specified equipment entity and sets an INHSWPR (Inhibit Switch to Protection) condition type for the specified equipment entity.

The INH-SWTOWKG-EQPT command performs "Lock onto Protection" operation for the specified working module. The working module will be switched to the protection module if not switched already. It applies to working DS3, ECC, TMUX, and VSC modules.

Executing an INH-SWTOWKG-EQPT command sets a SST of PRI (Protection Release Inhibited) for the specified equipment entity and sets an INHSWWKG (Inhibit Switch to Working) condition type for the specified equipment entity.

The ALW-SWTOPROTN-EQPT command clears "Lockout a Working" operation (initiated by INH-SWTOPROTN-EQPT command) that is in effect for the specified working module. It also clears "Lockout of Protection" operation (initiated by INH-SWTOPROTN-EQPT command) that is in effect for the specified protection module. If a working module is specified, that module can switch to the associated protection module. If a protection module is specified, that module can provide protection to the associated working modules. This command applies to working and protection DS3 and ECC modules and it applies to protection TMUX and VSC modules.

Executing an ALW-SWTOPROTN-EQPT command clears the SST of PSI for the specified equipment entity and clears the INHSWPR condition type for the specified equipment entity.

The ALW-SWTOWKG-EQPT command clears "Lock onto Protection" operation (initiated by INH-SWTOWKG-EQPT command) that is in effect for the specified working module. The specified working module is returned to automatic switching mode. This command applies to working DS3, ECC, TMUX, and VSC modules.

Inhibit/Allow Protection Switching 4-343


Executing an ALW-SWTOWKG-EQPT command clears the SST of PRI for the specified equipment entity and clears the INHSWWKG condition type for the specified equipment entity.


STEP PROCEDURE

1 CAUTION: Possibility of service interruption. Equipment failure during an inhibit-switch-to-protection condition causes traffic loss.

2 Select action.

To inhibit/allow protection switching with 1677 SONET Link EMA, go to step 3.To inhibit/allow protection switching with TL1, go to step 20.

Inhibit/Allow Protection Switching with 1677 SONET Link EMA

3 Select action.

To inhibit working card switch to protection, go to step 4.To inhibit protection card switch to working, go to step 8.To allow working card switch to protection, go to step 12.To allow protection card switch to working, go to step 16.

Inhibit Working Card Switch to Protection


5 Right-click on appropriate card (working DS3 or ECC or protection DS3, ECC, TMUX, or VSC) and select Switch>Inhibit Switch to Protection. The Inhibit Switch to Protection dialog box appears.

6 Click Yes.

7 Go to step 28.

Inhibit Protection Card Switch to Working


9 Right-click on appropriate working card (DS3, ECC, TMUX, or VSC) and select Switch>Inhibit Switch to Working. The Inhibit Switch to Working dialog box appears.

Inhibit/Allow Protection Switching4-344


10 Click Yes.

11 Go to step 28.

Allow Working Card Switch to Protection


13 Right-click on appropriate card (working DS3 or ECC or protection DS3, ECC, TMUX, or VSC) and select Switch>Allow Switch to Protection. The Allow Switch to Protection dialog box appears.

14 Click Yes.

15 Go to step 28.

Allow Protection Card Switch to Working


17 Right-click on appropriate working card (DS3, ECC, TMUX, or VSC) and select Switch>Allow Switch to Working. The Allow Switch to Working dialog box appears.

18 Click Yes.

19 Go to step 28.

Inhibit/Allow Protection Switching with TL1

20 Select action.

To inhibit working card switch to protection, go to step 21.To inhibit protection card switch to working, go to step 23.To allow working card switch to protection, go to step 25.To allow protection card switch to working, go to step 27.

Inhibit Working Card Switch to Protection


where:AID=Access Identifier of working card (DS3 or ECC) or protection card (DS3, ECC, TMUX, or VSC)

22 Go to step 28.

Inhibit/Allow Protection Switching 4-345


Inhibit Protection Card Switch to Working

23 Enter INH-SWTOWKG-EQPT::AID;

where:AID=Access Identifier of working card (DS3, ECC, TMUX, or VSC)

24 Go to step 28.

Allow Working Card Switch to Protection

25 Enter ALW-SWTOPROTN-EQPT::AID;

where:AID=Access Identifier of working card (DS3 or ECC) or protection card (DS3, ECC, TMUX, or VSC)

26 Go to step 28.

Allow Protection Card Switch to Working

27 Enter ALW-SWTOWKG-EQPT::AID;

where:AID=Access Identifier of working card (DS3, ECC, TMUX, or VSC)


Inhibit/Allow Protection Switching4-346


DLP-181Provision Optical Fiber Amplifier (OFA)PURPOSE

This procedure provides the instructions to provision an Optical Fiber Amplifier (OFA).

PREREQUISITES

When provisioning an OFA on an EDFA card, the EDFA card must be provisioned first. Refer to DLP-112 to provision EDFA cards.

GENERAL


STEP PROCEDURE

1 Select action.

To provision OFA with 1677 SONET Link EMA, go to step 2.To provision OFA with TL1, go to step 10.

Provision OFA with 1677 SONET Link EMA



4 Right-click appropriate OFA group and select Create. The Provision OFA wizard appears.




8 Click Finish.

9 Go to step 14.

Provision Optical Fiber Amplifier (OFA) 4-347


Provision OFA with 1677 SONET Link EMA

10 Enter RTRV-OFA::[AID];

where:AID=OFA Access Identifier



If yes, go to step 13.If no, the ENT-OFA command cannot be performed on the specified OFA port. Go to step 14.

13 Enter ENT-OFA::AID::::[OPRNOM=][,OPTNOM=]:[PST];

where:AID=OFA Access IdentifierOPRNOM=Nominal received power levelOPTNOM=Nominal transmitted power levelOther parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.


Provision Optical Fiber Amplifier (OFA)4-348


DLP-182Report EC1 PM DataPURPOSE

This procedure provides the instructions to report Performance Monitoring (PM) data and initialize (reset) the collection register for EC1 ports.

GENERAL




STEP PROCEDURE

1 Select action.

To report EC1 PM data with 1677 SONET Link EMA, go to step 2.To report EC1 PM data with TL1, go to step 20.

Report EC1 PM Data with 1677 SONET Link EMA

2 Select action.


Retrieve PM Data



5 Expand the appropriate EC1 group to display EC1 facilities.



Report EC1 PM Data 4-349



8 Click Close.

9 Go to step 25.




12 Expand the appropriate EC1 group to display EC1 facilities.







17 Click Apply.

18 Click Close.

19 Go to step 25.

Report EC1 PM Data with TL1

20 Select action.


Report EC1 PM Data4-350


Retrieve PM Data

21 Enter RTRV-PM-EC1::[AID]:::[MONTYPE],[MONLEV],,,[TMPER],[MONDAT],[MONTM];



23 Go to step 25.


24 Enter INIT-REG-EC1::AID:::[MONTYPE],[MONVAL],[LOCN],,[TMPER];

where:AID=EC1 Access IdentifierTMPER=15-MIN or 1-DAYOther parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.


Report EC1 PM Data 4-351


Report EC1 PM Data4-352


DLP-183Deprovision Optical Fiber Amplifier (OFA)PURPOSE

This procedure provides the instructions to deprovision an Optical Fiber Amplifier (OFA).

GENERAL


STEP PROCEDURE

1 Select action.

To deprovision OFA with 1677 SONET Link EMA, go to step 2.To deprovision OFA with TL1, go to step 8.

Deprovision OFA with 1677 SONET Link EMA




5 Right-click on appropriate OFA and select Unassign.

6 Click Yes.

7 Go to step 12.

Deprovision OFA with 1677 SONET Link EMA




Deprovision Optical Fiber Amplifier (OFA) 4-353


10 Does facility have SST of DSBLD or UAS?

If yes, the DLT-OFA command cannot be performed on the specified OFA facility. Go to step 12.If no, go to step 11.

11 Enter DLT-OFA::AID;



Deprovision Optical Fiber Amplifier (OFA)4-354


DLP-184Administer DS3 Test Access ConnectionsPURPOSE

This procedure provides the instructions to retrieve information on, connect, and disconnect Test Access (TACC) connections used to test STS-n and DS3 ports.

PREREQUISITES

A CONN-TACC-T3 command must be administered before a CHG-ACCMD-T3 command will be accepted.


If a test access port pair is provisioned on an OC-n facility, the OC-n facility must be unprotected.

The maximum number of T3/STS1/STS3C/STS12C/STS48C test access connections supported in a system is six.

T3/STS-level test access connections require the redundant SSC.

GENERAL


When a T3 port is defined as a test access port (TACC=Y), the two ports identified by AID and TADB in the ENT-T3 command are both provisioned as a Test Access Port Pair (TAPP). When using ED-T3 to change the provisioning of a TAPP, either of the AIDs for TAD A or TAD B can be specified as the AID in the command and the provisioning changes are applied to both the TAD A and TAD B ports. The STSMAP value of a TAPP port must be set to ASYNC and the FMT value must be UNFR and can not be changed.

CONN-TACC-T3 connects a test access port to a specified T3 or STS-1 port in the specified test access mode. The available test access modes for a test access port connection are MONE, MONEF, MONF, SPLTA, SPLTB, SPLTE, SPLTEF, SPLTF, LOOPE, or LOOPF.

CHG-ACCMD-T3 modifies the test access mode of T3 test access connections.


Administer DS3 Test Access Connections 4-355



STEP PROCEDURE


where:AID=DS3 Access Identifier of TAP (TAD A or TAD B), equipment-side port being tested, or facility-side port being tested.TYPE=Type of test access connection (T3)UID=(ALL, MYSELF)

2 Examine output.


3 Enter RTRV-T3::[AID]; to verify status of possible TAPs.


4 Examine output.


5 Select action.

To provision a T3 port as a TAP, go to step 6.To modify provisioning of a TAP, go to step 8.To create a test access connection, go to step 10.To change test access mode of TACC connection, go to step 12.To disconnect TACC connection, go to step 14.To end this procedure, go to step 16.

Administer DS3 Test Access Connections4-356


Provision a T3 Port as a TAP

6 Enter ENT-T3::AID::::,FMT=UNFR,STSMAP=ASYNC,TACC=Y,TADB=; to provision TAPP.

where:AID=T3 access identifier of TAD A port in TAPPTADB=T3 access identifier of TAD B port in TAPP (AID selected must be an available T3 port. It will be provisioned with same parameters as AID.)

7 Go to step 5.

Modify TAP


8 Enter ED-T3::AID::::[CKTID=][,LBO=][,FMT=][,FEAC=]:[PST],[SST];

where:AID=T3 Access Identifier (TAD A or TAD B)Other parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

9 Go to step 5.

Create TACC Connection

CAUTION: Possibility of service interruption. CONN-TACC-T3 executed with a mode of LOOPE, LOOPF, SPLTA, SPLTB, SPLTE, SPLTEF, or SPLTF affects service and interrupts traffic.

10 Enter CONN-TACC-T3::AID:::TAP:MD:[AID1]:[LA];

where:AID=Identifies the equipment-side T3/STS-1 port to be testedTAP=T3 Access Identifier of TAD A (first port in test access port pair)MD=Test access modeOther parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

11 Go to step 5.

Change Test Access Mode of TACC Connection

CAUTION: Possibility of service interruption. CHG-ACCMD-T3 executed with a mode of LOOPE, LOOPF, SPLTA, SPLTB, SPLTE, SPLTEF, or SPLTF affects service and interrupts traffic.

Administer DS3 Test Access Connections 4-357


12 Enter CHG-ACCMD-T3::AID:::MD;

where:AID=T3 Access Identifier of TAD A (first port in test access port pair)MD=Test access mode

13 Go to step 5.



where:AID=T3 Access Identifier of TAD A (first port in test access port pair)

15 Go to step 5.


Administer DS3 Test Access Connections4-358


DLP-185Report OFA PM DataPURPOSE

This procedure provides the instructions to report Performance Monitoring (PM) data and initialize (reset) the collection register for OFA ports.

GENERAL




STEP PROCEDURE

1 Select action.

To report OFA PM data with 1677 SONET Link EMA, go to step 2.To report OFA PM data with TL1, go to step 20.

Report OFA PM Data with 1677 SONET Link EMA

2 Select action.


Retrieve PM Data



5 Expand appropriate OFA group to display OFA facilities.



Report OFA PM Data 4-359



8 Click Close.

9 Go to step 25.




12 Expand appropriate OFA group to display OFA facilities.







17 Click Apply.

18 Click Close.

19 Go to step 25.

Report OFA PM Data with TL1

20 Select action.


Report OFA PM Data4-360


Retrieve PM Data

21 Enter RTRV-PM-OFA::[AID]:::[MONTYPE],[MONLEV],,,[TMPER],[MONDAT],[MONTM];



23 Go to step 25.


24 Enter INIT-REG-OFA::AID:::[MONTYPE],[MONVAL],[LOCN],,[TMPER];

where:AID=OFA Access IdentifierTMPER=15-MIN or 1-DAYOther parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.


Report OFA PM Data 4-361


Report OFA PM Data4-362


DLP-186Set OFA PM Threshold LevelsPURPOSE

This procedure provides the instructions to set Performance Monitoring (PM) threshold levels for Gigabit Ethernet ports.

GENERAL



The SET-TH-OFA command is used to designate PM threshold levels for OFA ports. For each type of error (parameter) being monitored, a threshold level with either a 15-minute or 24-hour period may be set. If the number of errors collected exceeds the threshold level within the time selected, the system generates a Threshold Crossing Alert (TCA).


STEP PROCEDURE

1 Select action.

To set OFA PM threshold levels with 1677 SONET Link EMA, go to step 2.To set OFA PM threshold levels with TL1, go to step 11.

Set OFA PM Threshold Levels with 1677 SONET Link EMA




5 Right-click appropriate OFA facility and select action.


Set OFA PM Threshold Levels 4-363






8 Click Apply.

9 Click Close.

10 Go to step 14.

Set OFA PM Threshold Levels with TL1

11 Enter RTRV-TH-OFA::[AID]:::[MONTYPE],,[TMPER];



13 Enter SET-TH-OFA::AID:::MONTYPE,THLEV,,,[TMPER];

where:AID=OFA Access IdentifierMONTYPE=Monitored type. See Commands and Messages manual (PN 3EM13852AD) for possible values.THLEV={DFLT, (0-255)}TMPER={15-MIN, 1-DAY}


Set OFA PM Threshold Levels4-364


DLP-187Set DS1 PM Threshold LevelsPURPOSE

This procedure provides the instructions to set Performance Monitoring (PM) threshold levels for DS1 ports.

GENERAL



The SET-TH-T1 command is used to designate PM threshold levels for DS1 ports. For each type of error (parameter) being monitored, a threshold level with either a 15-minute or 24-hour period may be set. If the number of errors collected exceeds the threshold level within the time selected, the system generates a Threshold Crossing Alert (TCA).


STEP PROCEDURE

1 Select action.

To set T1 PM threshold levels with 1677 SONET Link EMA, go to step 2.To set T1 PM threshold levels with TL1, go to step 11.

Set T1 PM Threshold Levels with 1677 SONET Link EMA






Set DS1 PM Threshold Levels 4-365






8 Click Apply.

9 Click Close.

10 Go to step 14.

Set T1 PM Threshold Levels with TL1

11 Enter RTRV-TH-T1::[AID]:::[MONTYPE],,[TMPER];



13 Enter SET-TH-T1::AID:::MONTYPE,THLEV,,,[TMPER];

where:AID=T1 Access IdentifierMONTYPE=Monitored type. See Commands and Messages manual (PN 3EM13852AD) for possible values.THLEV={DFLT, (0-1048575)}TMPER={15-MIN, 1-DAY}


Set DS1 PM Threshold Levels4-366


DLP-188Perform FTP Backup of Provisioning DatabasePURPOSE

This procedure provides the instructions to perform an FTP backup of provisioning data from the 1677 SONET Link to a remote FTP server.

PREREQUISITES

To perform this procedure the NE being backed up must have IP-based access and the user must be logged in to that node.

GENERAL

The COPY-RFILE command is used to move database or software generic files from and to different locations: disk storage on the NE or a Remote File Server (RFS).

The OPR-DISK command is used to activate, back up, or purge system image or configuration files.


STEP PROCEDURE

1 Select action.

To perform FTP backup of provisioning database with 1677 SONET Link EMA, go to step 2.To perform FTP backup of provisioning database with TL1, go to step 15.

Perform FTP Backup of Provisioning Database with 1677 SONET Link EMA

2 Back up the provisioning database. Right-click on the Network Element domain or the System domain and select System Configuration Operations>Backup. The Backup System Configuration wizard appears.


4 On the Backup Directory page, specify the directory to backup the system configuration files to. This directory should be a path relative to the /cfg directory.

5 Click Next.

Perform FTP Backup of Provisioning Database 4-367



7 Click Finish.

8 Copy the saved provisioning database to the FTP server. Right-click on the Network Element domain or the System domain and select File Transfer. The File Transfer window appears.

9 Select Backup the NE active database to a Remote File Server from the Operation drop-down list.

10 Verify the FTP Host, FTP Port, and FTP User are correct.

11 Enter the FTP Password.

12 Enter the Remote File Path.

13 Click Transfer.

14 Go to step 19.

Perform FTP Backup of Provisioning Database with TL1

15 Enter OPR-DISK::::::TYPE=CFG,ACTION=BACKUP[,SRC=][,LEVEL=]; to back up the provisioning database.

where:SRC=Directory within A:/CFG to hold the backup copy of the provisioning database.Other parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

16 Wait for the completion message.

17 Enter COPY-RFILE::AID:::RFBU,SRCURL,DESTURL,[OVERWRITE]; to copy the saved provisioning database to the FTP server.

where:AID=Access Identifier of local disk (DISK-{A, B})SRCURL=Source file or directory in A:/cfg (if AID=DISK-A) or in B:/user (if AID=DISK-B)DESTURL=URL of Remote File Server (RFS)Other parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

Perform FTP Backup of Provisioning Database4-368


18 Wait for the completion messages.


Perform FTP Backup of Provisioning Database 4-369


Perform FTP Backup of Provisioning Database4-370


DLP-189Perform FTP Restore of Provisioning DatabasePURPOSE

This procedure provides instructions to restore backed up provisioning data (configuration files) from a remote FTP server to a 1677 SONET Link.

PREREQUISITES

To perform this procedure the NE being restored must have IP-based access and the user must be logged in to that node.

GENERAL

The COPY-RFILE command is used to move database or software generic files from and to different locations: disk storage on the NE or a Remote File Server (RFS).



STEP PROCEDURE

1 Select action.

To perform FTP restore of provisioning database with 1677 SONET Link EMA, go to step 2.To perform FTP restore of provisioning database with TL1, go to step 18.

Perform FTP Restore of Provisioning Database with 1677 SONET Link EMA

2 Restore the saved provisioning database from the FTP server. Right-click on the Network Element domain or the System domain and select File Transfer. The File Transfer window appears.

3 Select Download a database from a Remote File Server to the NE from the Operation drop-down list.

4 Verify the FTP Host, FTP Port, and FTP User are correct.

5 Enter the FTP Password.

Perform FTP Restore of Provisioning Database 4-371


6 Enter the Remote File Path.

7 Click Transfer.

8 Activate the newly restored provisioning database. Right-click on the Network Element domain or the System domain and select System Configuration Operations>Activate. The Activate System Configuration wizard appears.


10 On the Configuration Directory page, specify the directory containing the configuration files to activate. This directory should be a path relative to the /cfg directory.

11 Click Next.


13 Click Finish.

14 Reset the node. Right-click on the Network Element domain or the System domain and select Initialize NE.

15 Click Yes.

16 Verify the node properly resets by logging in after the node completes the rebooting process.

17 Go to step 24.

Perform FTP Restore of Provisioning Database with TL1

18 Enter COPY-RFILE::DISK-A:::CONFIGDL,SRCURL,DESTURL,[OVERWRITE]; to restore the saved provisioning database from the FTP server.

where:SRCURL=URL of Remote File Server (RFS)DESTURL=Destination file or directory in A:/cfg or A:/binOther parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.


Perform FTP Restore of Provisioning Database4-372


20 Enter OPR-DISK::::::TYPE=CFG,ACTION=ACTIVATE[,SRC=][,LEVEL=]; to activate the newly restored provisioning database.

where:SRC=Directory in A:/cfg or A:/bin that holds the backup files to be restored.Other parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.


22 Enter INIT-SYS:::::2; to reset the node.



Perform FTP Restore of Provisioning Database 4-373


Perform FTP Restore of Provisioning Database4-374


DLP-190Retrieve Disk InformationPURPOSE

This procedure provides instructions to retrieve general information about logical and physical flash disks installed in common control cards (such as the disk status, total size in bytes, and current free space in byte), or to retrieve a listing of files and directories on a disk.

To activate or deactivate a disk, refer to DLP-191.

GENERAL

Ther RTRV-DISK command retrieves the data and state parameters associated with DISK equipment entities.

The RTRV-RFILE command retrieves the listing for a remote file or directory, including its size, and the date and time it was last modified.


STEP PROCEDURE

1 Select action.

To retrieve disk information with 1677 SONET Link EMA, go to step 2.To retrieve disk information with TL1, go to step 16.

Retrieve Disk Information with 1677 SONET Link EMA

2 Select action.

To retrieve general information about flash disks, go to step 3.To retrieve a listing of files on a flash disk, go to step 9.

Retrieve General Disk Information


4 Right-click on appropriate disk and select Properties>General.


6 Click Close.

Retrieve Disk Information 4-375


7 Repeat steps 4 through 6 to retrieve information on other disks.

8 Go to step 20.

Retrieve File Listing

9 Right-click on the Network Element domain or the System domain and select File Operations>View File Information. The File Information wizard appears.




13 Click Finish. The RTRV-RFILE window appears with file information.

14 Click Close when done viewing information.

15 Go to step 20.

Retrieve Disk Information with TL1

16 Select action.

To retrieve general information about flash disks, go to step 17.To retrieve a listing of files on a flash disk, go to step 19.

Retrieve General Disk Information

17 Enter RTRV-DISK::[AID];

where:AID=Disk Access Identifier (Default=all disks)

18 Go to step 20.

Retrieve Disk Information4-376


Retrieve File Listing

19 Enter RTRV-RFILE::AID::::[LOCN=””][,LEVEL=][,STORUSG=];

where:AID=Disk AIDLOCN=File or directory, enclosed in quotation marks.Other parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.


Retrieve Disk Information 4-377


Retrieve Disk Information4-378


DLP-191Activate DiskPURPOSE

This procedure provides instructions to activate or deactivate a flash disk in a common control card (CCC). For a redundant pair (Disks A9 and A10 or Disks B9 and B10), either disk can be designated as the primary or secondary in the pair.

GENERAL

When activating Disk A9 or A10 as primary, the user can either import configuration files from the newly activated disk, or export the current configuration files from the NE to the disk.

To retrieve current flash disk information, refer to DLP-190.


STEP PROCEDURE

1 Select action.

To activate disk with 1677 SONET Link EMA, go to step 2.To activate disk with TL1, go to step 14.

Activate Disk with 1677 SONET Link EMA

2 Select action.

To activate a disk, go to step 3.To deactivate a disk, go to step 10.

Activate Disk


4 Right-click on appropriate disk and select Activate Disk. The Activate Disk wizard appears.




Activate Disk 4-379


8 Click Finish.

9 Go to step 20.

Deactivate Disk


11 Right-click on appropriate disk and select Deactivate Disk.

12 Click Yes.

13 Go to step 20.

Activate Disk with TL1

14 Select action.

To activate a disk as primary, go to step 15.To activate a disk as secondary, go to step 17.To deactivate a disk, go to step 19.

Activate Disk as Primary

15 Enter ACT-DISK::AID::::MODE=PRI,ACTION=ACTIVATE[,BEHAVIOR=];

where:AID=Disk Access Identifier (DISK-{A9, A10, B9, B10})BEHAVIOR=Disk function. (IMPORT, EXPORT) Required when activating disk A9 or A10 as primary. IMPORT=Import system configuration files from the activated disk. EXPORT=Export current system configuration files to the activated disk.

16 Go to step 20.

Activate Disk as Secondary

17 Enter ACT-DISK::AID::::MODE=SEC,ACTION=ACTIVATE;

where:AID=Disk Access Identifier (DISK-{A9, A10, B9, B10})

18 Go to step 20.

Activate Disk4-380


Deactivate Disk

19 Enter ACT-DISK::AID::::,ACTION=DEACTIVATE;

where:AID=Disk Access Identifier (DISK-{A9, A10, B9, B10})


Activate Disk 4-381


Activate Disk4-382


DLP-192Connect PC to the 1677 SONET LinkPURPOSE

This procedure provides instructions to connect a console cable to the NE to allow access to the node.

Refer to DLP-210 to perform the following:





GENERAL


STEP PROCEDURE

1 Open a terminal emulator (like hyperterminal).

2 Choose one of the serial communications port on the PC. Typically COM1.

3 Configure the COM port as follows:

Baud rate = 9600Data bits = 8Stop Bits = 1Parity = None

4 Plug the DB-9 connector of the console cable into the COM port of the PC.

5 Plug the RJ-11 connector of the console cable into Console port of the Timing card, in either slot 11/A or 11/B.

Connect PC to the 1677 SONET Link 4-383


6 Enter ACT-USER::UID:::PID; to log into the node.

where:UID=User identifierPID=Password identifier


Connect PC to the 1677 SONET Link4-384


DLP-193Change Facility Service StatePURPOSE

This procedure provides instructions to retrieve or change the service state for a facility.

GENERAL

In this procedure, enter parameter values only for indicated fields. Leave remaining fields blank for system defaults.


STEP PROCEDURE

1 Select action.

To change facility service state with 1677 SONET Link EMA, go to step 2.To change facility service state with TL1, go to step 16.

Change Facility Service State with 1677 SONET Link EMA


3 Expand the appropriate facility domain.



6 Observe facility Primary State (PST) and Secondary State (SST) in the Result Pane.

7 Select action.

To remove facility from service, go to step 8.To restore facility to service, go to step 12.

Remove Facility

8 Right-click on the appropriate facility and select Service State>Remove.

9 Click Yes.

Change Facility Service State 4-385


10 Verify Primary State is now OOS-MA.

11 Go to step 22.

Restore Facility

12 Right-click on the appropriate facility and select Service State>Restore.

13 Click Yes.

14 Verify Primary State is now IS.

15 Go to step 22.

Change Facility Service State with TL1

16 Enter RTRV-x::[AID];

where:x=Facility type (EC1, OC3, OC12, OC48, OC192, STS1, STS3C, STS12C, STS48C, GIGE, OFA, T1, T3, VT1)AID=Facility Access Identifier (Default=all facilities of that type.)

17 Examine output for primary state and secondary state values.

18 Select action.

To remove facility from service, go to step 19.To restore facility to service, go to step 21.

Remove Facility

19 Enter RMV-x::AID;

where: x=Facility type (EC1, OC3, OC12, OC48, OC192, STS1, STS3C, STS12C, STS48C, GIGE, OFA, T1, T3, VT1)AID=Access Identifier of port to be removed

20 Go to step 22.

Change Facility Service State4-386


Restore Facility

21 Enter RST-x::AID;

where: x=Facility type (EC1, OC3, OC12, OC48, OC192, STS1, STS3C, STS12C, STS48C, GIGE, OFA, T1, T3, VT1)AID=Access Identifier of port to be restored


Change Facility Service State 4-387


Change Facility Service State4-388


DLP-194Perform Manual Protection Switch for Working CardsPURPOSE

This procedure provides instructions to manually switch a DS3, ECC, TMUX, or VSC working card to its associated protection card.

PREREQUISITES

The SW-TOPROTN-EQPT command is executed regardless of the state of the specified (main) card but the protection card must have a state of IS,STBYH.

The system does not allow manual protection switching if a card was previously inhibited using INH-SWTOPROTN-EQPT or INH-SWTOWKG-EQPT. Refer to DLP-180 to allow protection switching for a card. Protection switching clears a PSI (Protection Switch Inhibited) secondary state and INHSWPR condition.

GENERAL

Protection switching reduces possible service-effect by switching traffic to an alternate copy. When a manual protection switch is performed, traffic will not return to the original card until it is manually switched back.

This procedure describes how to manually switch traffic from a working card to a protection card or from a protection card to a working card.


STEP PROCEDURE

1 Select action.

Perform manual protection switch with 1677 SONET Link EMA, go to step 2.Perform manual protection switch with TL1, go to step 13.

Perform Manual Protection Switch with 1677 SONET Link EMA

2 Select action.

To switch card to protection, go to step 3.To switch card to working, go to step 8.

Perform Manual Protection Switch for Working Cards 4-389


Switch Card to Protection


4 Right-click on appropriate card and select Switch>Switch to Protection. The Switch to Protection Equipment dialog appears.

5 Select the command mode by clicking box next to appropriate option (Normal or Forced).

6 Click Switch.

7 Go to step 17.

Switch Card to Working


9 Right-click on appropriate card and select Switch>Switch to Working. The Switch to Working Equipment dialog appears.

10 Select the command mode by clicking box next to appropriate option (Normal or Forced).

11 Click Switch.

12 Go to step 17.

Perform Manual Protection Switch with TL1

13 Select action.

To switch card to protection, go to step 14.To switch card to working, go to step 16.

Switch Card to Protection

14 Enter SW-TOPROTN-EQPT::AID:::[MODE],[PROTID],[DIRN];

where:AID=Access Identifier of working card to switch to protectionOther parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

15 Go to step 17.

Perform Manual Protection Switch for Working Cards4-390


Switch Card to Working

16 Enter SW-TOWKG-EQPT::AID:::[MODE],[DIRN];

where:AID=Access Identifier of working card to switch back to workingOther parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.


Perform Manual Protection Switch for Working Cards 4-391


Perform Manual Protection Switch for Working Cards4-392


DLP-195Switch to Redundant CardPURPOSE

This procedure describes how to switch from the active card to the standby or backup card. The following cards can have a redundant card: CCC, SSC, and TC.

PREREQUISITES

Both copies of redundant cards must be provisioned and in service (IS).

GENERAL

For redundant (duplex) equipment (CCC, SSC, and TC), this procedure describes how to manually switch traffic from one copy to another. The active copy becomes standby and the standby copy becomes active.

The SW-DX-EQPT command performs a copy switch for the specified duplex equipment. When the command is issued on an SWC, the primary SWC will reset (similar to an INIT-SYS). This will cause Test Access connections with Link Association to be dropped temporarily. When the command is issued on a CCC, the primary CCC will reset. This will cause all users logged into TL1 ports (3083) to be dropped, as well as Test Access connections with Link Association.


STEP PROCEDURE

1 Select action.

To perform copy switch to redundant card with 1677 SONET Link EMA, go to step 2.To perform copy switch to redundant card with TL1, go to step 6.

Perform Copy Switch to Redundant Card with 1677 SONET Link EMA


3 Right-click on appropriate card and select Switch>Switch Duplex. The Switch Duplex Equipment dialog box appears.

When issued for CCC or SSC, the primary CCC or SSC module will reset, similar to an INIT-SYS.

Switch to Redundant Card 4-393


4 Click Yes.

5 Go to step 7.

Perform Copy Switch to Redundant Card with TL1

6 Enter SW-DX-EQPT::AID;

where:AID=Access Identifier of either copy module

When issued for CCC or SSC, the primary CCC or SSC module will reset, similar to an INIT-SYS.


Switch to Redundant Card4-394


DLP-196Set Default Thresholds for All Cross-ConnectionsPURPOSE

This procedure provides instructions to set the configurable network element-wide defaults for switching parameters associated with cross-connections.

GENERAL

The SET-ATTR-CRSDFLT command sets the default values for the following parameters:

• RVRTV=Revertive. Specifies whether to automatically revert to working.

• RVRTTIM=Revert Time. Revert delay time in minutes.

• SWUNEQP=Default value for this NE for enabling/disabling switch paths upon UNEQ-P condition.

• SWPDIP=Default value for this NE for enabling/disabling switch paths upon PDI-P condition.


STEP PROCEDURE

1 Enter SET-ATTR-CRSDFLT::::::[RVRTV=][,RVRTTIM=][,SWUNEQP=][,SWPDIP=];



Set Default Thresholds for All Cross-Connections 4-395


Set Default Thresholds for All Cross-Connections4-396


DLP-197Change Line Buildout (LBO)PURPOSE

This procedure provides instructions to determine the provisioned value of the Electrical Line Buildout (LBO) parameter for T3 and EC1 facilities and how to change that value.

GENERAL

The Default value for the LBO is the previously existing value. The 1677 SONET Link assumes that 734-type cable is used. If 735A-type cable is used the LBO value will need to be adjusted according to the information in Table 197-A.


STEP PROCEDURE

1 Select action.

To change LBO with 1677 SONET Link EMA, go to step 2.To change LBO with TL1, go to step 12.

Change Line Build Out with 1677 SONET Link EMA

2 Expand Facilities domain in the Navigation Tree.

3 Expand appropriate domain (T3 or EC1).

Table 197-A. LBO ValueConnecting the 1677 SONET Link to:

Length in feet from 1677 SONET Link to Connected Equipment for DS3 Out Cable

LBO Required?

1677 SONET Link Setting

735A-Type Cable 734-Type CableDSXCross-Connect Equipment

0 – 125 0 - 255 Yes Set feet to a number >=225

>125 - 250 >255 - 450 No Set feet to a number < 225

Other Terminating Equipment directly connected to1677 SONET Link

0 - 125 0 - 255 Yes Set feet to a number >=225

>125 - 500 >225 - 900 No Set feet to a number < 225

Change Line Buildout (LBO) 4-397


4 Expand appropriate group.

5 Right-click on appropriate facility and select Properties>General.

6 Examine information in table and note value of Line Build Out parameter.

7 Refer to table 197-A to determine appropriate LBO value. Does provisioned LBO value need to be changed?


8 Double-click in Line Build Out box and enter a new value, if appropriate.

9 Click Apply.

10 Click Close.

11 Go to step 22.

Change Line Build Out with TL1

12 Select action.

To change LBO for T3, go to step 13.To change LBO for EC1, go to step 18.

Change T3 LBO


where:AID=T3 Access Identifier (Default=all T3 facilities)

14 Examine output and note value of Line Build Out parameter.

15 Refer to Table 197-A to determine appropriate LBO value. Does provisioned LBO value need to be changed?


16 Enter ED-T3::AID::::,LBO=;

where:AID=T3 Access IdentifierLBO=Line build out length in feet. (1=0-225 ft, 2=225-450ft)

Change Line Buildout (LBO)4-398


17 Go to step 22.

Change EC1 LBO



19 Examine output and note value of Line Build Out parameter.

20 Refer to Table 197-A to determine appropriate LBO value. Does provisioned LBO value need to be changed?


21 Enter ED-EC1::AID::::,LBO=;

where:AID=EC1 Access IdentifierLBO=Line build out length in feet. (1=0-225 ft, 2=225-450ft)


Change Line Buildout (LBO) 4-399


Change Line Buildout (LBO)4-400


DLP-198Issue TL1 Commands Through a GatewayPURPOSE

This procedure provides instructions to communicate with a network element (NE) through a TL1 gateway.

PREREQUISITES

Before communicating with the target NE, the user must log in to the node that serves as the TL1 gateway. Refer to DLP-100.

GENERAL


STEP PROCEDURE

1 After logging in to the TL1 gateway node, log in to the target NE. Enter ACT-USER:TID:UID:::PID;

where:TID=Target identifier of the target NE accessed through the gatewayUID=User ID for the target NEPID=Password ID for the target NE

2 In subsequent TL1 commands directed to the target NE, include the target identifier (TID) value for the target NE.


Issue TL1 Commands Through a Gateway 4-401


Issue TL1 Commands Through a Gateway4-402


DLP-199Administer STS-n Facility Protection GroupPURPOSE

This procedure provides the instructions to retrieve information on, provision, and deprovision STS-n facility protection groups.

PREREQUISITE

The working STS-n ports in facility protection groups must be provisioned. Refer to DLP-117.

OC-n facilities that support the STS-n must be provisioned for UPSR. Refer to DLP-151.

GENERAL

An STS-n facility protection group consists of a pair of adjacent STS-n ports: one protect port and one working port.

After STS-n facility protection groups are provisioned, STS-n protect port AIDs can be specified when executing RTRV-STSn and all STS-n Performance Monitoring (PM) commands.

After an STS-1 facility protection group is provisioned, ED-FFP-STS1 can be used to alter parameters.

Administer STS-n Facility Protection Group 4-403


Table 199-A. Valid STS-n Facility Protection PairsWORKING STS-n AIDS PROTECT STS-n AIDS STS1-1-{A,B}-{1-12}-{1-48}(same port and timeslot as protection)

STS1-2-{A,B}-{1-12}-{1-48}( same port and timeslot as working)

STS1-3-{A,B}-{1-12}-{1-48}(same port and timeslot as protection)

STS1-4-{A,B}-{1-12}-{1-48} (same port and timeslot as working)

STS1-5-{A,B, AB}-{1-12}-{1-192} (same port and timeslot as protection)

STS1-6-{A,B, AB}-{1-12}-{1-192} (same port and timeslot as working)

STS1-6-{AB}-{1}-{1-192} (same port and timeslot as protection)

STS1-12-{AB}-{1}-{1-192} (same port and timeslot as protection)

STS1-12-{A,B, AB}-{1-12}-{1-192} (same port and timeslot as protection)

STS1-13-{A,B,AB}-{1-12}-{1-192} (same port and timeslot as working)

STS1-14-{A,B}-{1-12}-{1-48} (same port and timeslot as protection)


STS1-16-{A,B}-{1-12}-{1-48} (same port and timeslot as protection)


STS3C-1-{A,B}-{1-12}-{1,4,7,10,13,16,19,22,25,28,31,34,37,40,43,46,49,52,55,58,61,64, 67,70,73,76,79,82,85,88,91,94,97,100,103,106,109,112,115,118,121,124,127,130,133,136,139,142, 145,148,151,154,157,160,163,166,169,172,175,178,181,184,187,190} (same port and timeslot as protection)

STS3C-2-{A,B}-{1-12}-{1,4,7,10,13,16,19,22,25,28,31,34,37,40,43,46,49,52,55,58,61,64, 67,70,73,76,79,82,85,88,91,94,97,100,103,106,109,112,115,118,121,124,127,130,133,136,139,142, 145,148,151,154,157,160,163,166,169,172,175,178,181,184,187,190} (same port and timeslot as working)





Administer STS-n Facility Protection Group4-404








STS12C-1-{A,B}-{1-4}-{1,13,25,37,49,61,73,85,97,109,121,133,145,157,169,181} (same port and timeslot as protection)

STS12C-2-{A,B}-{1-4}-{1,13,25,37,49,61,73,85,97,109,121,133,145,157,169,181} (same port and timeslot as working)





Table 199-A. Valid STS-n Facility Protection Pairs (cont.)WORKING STS-n AIDS PROTECT STS-n AIDS




STEP PROCEDURE

1 Select action.

To administer STS-n facility protection group with 1677 SONET Link EMA, go to step 2.To administer STS-n facility protection group with TL1, go to step 7.







STS48C-1-{A,B}-1-{1,49,97,145} (same timeslot as protection)

STS48C-2-{A,B}-1-{1,49,97,145} (same timeslot as working)











Table 199-A. Valid STS-n Facility Protection Pairs (cont.)WORKING STS-n AIDS PROTECT STS-n AIDS



Administer STS-n Facility Protection Group with 1677 SONET Link EMA

2 Select action.

To provision STS-n facility protection group, go to step 3.To deprovision STS-n facility protection group, go to step 5.To end this procedure, go to step 16.

Provision STS-n Facility Protection Group

3 To create STS-n protection group, create a cross-connection between the appropriate STS-n ports. Refer to DLP-125.

For BLSR:

– If a BLSR node serves as a drop port for the STS-n path in the ring, CCT=2WAY.

– If connecting two rings via a drop using Drop and Continue modules at the primary node, CCT=2WAYDC. For the secondary node, CCT=SRIW.

– If a BLSR node serves as a pass-through for the STS-n path in the ring, CCT=THRU.

For UPSR:

– If STS-n paths are between two OC-n ports of a UPSR, CCT=THRU.

4 Go to step 2.

Deprovision STS-n Facility Protection Group

5 To delete STS-n protection group, delete the cross-connection between the appropriate STS-n ports. Refer to DLP-125.

6 Go to step 2.

Administer STS-n Facility Protection Group with TL1

7 Select action.

To retrieve STS-1 facility protection group, go to step 8.To provision STS-n facility protection group, go to step 11.To deprovision STS-n facility protection group, go to step 13.To end this procedure, go to step 16.

Retrieve STS-1 Facility Protection Group

8 Enter RTRV-FFP-STS1::[AID];



9 Examine output. One line of output is returned for each STS-1 specified that is in an FFP group. Output parameter ACTIVE= shows the active port of the pair.

10 Go to step 7.

Provision STS-n Facility Protection Group


where:STSn=Signal type (STS1, STS3C, STS12C, or STS48C).FROM=Access Identifier of source facilityTO=Access Identifier of destination facilityCCT=Cross-connect type (2WAY, 2WAYDC, SRIW, THRU)Other parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

12 Go to step 7.

Deprovision STS-n Facility Protection Group



where:STSn=Signal type (STS1, STS3C, STS12C, or STS48C).FROM=Access Identifier of source facilityTO=Access Identifier of destination facility

15 Go to step 7.




DLP-200Administer T1 LoopbackPURPOSE

This procedure provides the instructions to administer DS1 (T1) loopbacks.

PREREQUISITES

The T1 facility to place in loopback must have a Primary State (PST) of OOS-AUMA or OOS-MA.

GENERAL

Loopbacks are test features that can be set to loop a signal back at different points along the signal path. The system supports four types of T1 loopbacks. Refer to table 200-A for a list of supported loopback types and locations.


A Line loopback is a complete loopback of a DS1 line signal by far-end equipment. The loopback request is sent through in-band control codes for SF and the Facility Data Link (FDL) for ESF. See figure 200-2.

A Payload loopback is a loopback of DS1 payload by far-end equipment with newly-generated framing bits. The loopback request is sent through the DS1 ESF FDL. See figure 200-3.

A DS1FEAC loopback is a complete loopback of a DS1 line signal by far-end equipment. The loopback request is sent through the Far End Alarm and Control (FEAC) channel of the DS3 in which the DS1 is embedded. See figure 200-4.

Table 200-A. Allowed Loopback Type for Provisioned T1 Framing FormatT1 Framing Format (FMT)ESF SF UNFR

LOCN NEND FACILITY FACILITY FACILITYFEND LINE, PAYLOAD,

DS1FEAC1

[1] DS1FEAC is allowed only if the T3 in which the T1 is embedded has been provisioned with a framing format(FMT) of CBIT.

LINE, DS1FEAC1 DS1FEAC1




Figure 200-2. Line Loopback

677-0244-1100404


X AIS

677-0289-1110504

1677 Far End NE

Line loopbackrequest sent viaOPR-LPBK-T1

Line loopbackrequest received andsignal is looped back

SF and ESFformatted T1




STEP PROCEDURE


2 Review the T1 loopback diagrams.

Figure 200-3. Payload Loopback

Figure 200-4. DS1FEAC Loopback

677-0290-1110504

1677 Far End NE

Payload loopback

request sent via

OPR-LPBK-T1

Payload loopback

request received and

signal is looped back

ESF formatted T1

677-0291-1110504

1677 Far End NE

DS1FEAC loopbackrequest sent viaOPR-LPBK-T1

Payload loopbackrequest received andsignal is looped back

T1 embedded inCBIT formatted T3



3 Select action.

To administer T1 loopback with 1677 SONET Link EMA, go to step 4.To administer T1 loopback with TL1, go to step 42.

Administer T1 Loopback with 1677 SONET Link EMA

4 Select action.

To retrieve current loopback status of T1 facility, go to step 5.To establish loopback, go to step 12.To verify loopback status, go to step 27.To release loopback, go to step 34.To end this procedure, go to step 58.







10 Click Close.

11 Go to step 4.

Establish Loopback






17 Select action.





19 Click Yes.


21 Right-click the T1 facility and select Loopback>Operate. The Operate Loopback T1 wizard appears.




25 Click Finish.

26 Go to step 4.







32 Click Close.

33 Go to step 4.

Release Loopback





38 Click Yes.




40 Click Yes.

41 Go to step 4.

Administer T1 Loopback with TL1

42 Select action.

To retrieve current loopback status of T1 facility, go to step 43.To establish loopback, go to step 46.To verify loopback status, go to step 52.To release loopback, go to step 55.To end this procedure, go to step 58.


43 Select RTRV-LPBK-T1::[AID];

where:AID=T1 access identifier


45 Go to step 42.

Establish Loopback

46 Enter RTRV-T1::AID; to retrieve the current PST and SST of the T1 facility.


47 Observe output.

48 Select action.

If the PST for the T1 facility is IS or OOS-AU, go to step 49.If the PST for the T1 facility is OOS-AUMA or OOS-MA, go to step 50.


Enter RMV-T1::AID;




50 Enter OPR-LPBK-T1::AID:::[LOCN],,,LPBKTYPE;

where:AID=T1 Access IdentifierLOCN={FEND, NEND}LPBKTYPE={DS1FEAC, FACILITY, LINE, PAYLOAD}

51 Go to step 42.


52 Enter RTRV-LPBK-T1::[AID]; to verify the T1 facility is in loopback status.



54 Go to step 42.

Release Loopback

55 Enter RLS-LPBK-T1::AID:::[LOCN],,,[LPBKTYPE]; to release the T1 loopback.

where:AID=T1 Access IdentifierLOCN={FEND, NEND}LPBKTYPE={DS1FEAC, FACILITY, LINE, PAYLOAD}

56 Enter RST-T1::AID; to place the facility back in service.


57 Go to step 42.




DLP-201Configure PC as FTP ServerPURPOSE

This procedure provides instructions to configure a Windows1 2000 or XP PC as an FTP server.

PREREQUISITES

User must have Local administrator privileges to perform these procedures.

GENERAL

Once a PC is configured as an FTP server, NE software can be downloaded to the 1677 SONET Link and remote NE database backups and restores can be performed.

STEP PROCEDURE

1 Is there currently a Windows1 FTP server set up on the local machine?

If yes, go to step 2.If unsure, go to step 3.If no, go to step 18.

2 Is the Local Path information known?


Check if Windows1 FTP Server is Installed

3 Open the Control Panel. Select Start>Settings>Control Panel.

4 Double-click the Administrative Tools icon.

5 Double-click the Computer Management icon.

6 In the Computer Management window, expand the Services and Applications node.

7 Is Internet Information Services listed?

If yes, go to step 8.If no, there is currently no FTP server installed. Close the Computer Management window and go to step 18.

1. Windows is a registered trademark of Microsoft Corporation.

Configure PC as FTP Server 4-417


8 Select Internet Information Services.

9 Is an FTP site listed in the details window?


10 FTP server is set up on local machine. Is current FTP site to be configured with the Alcatel default configuration?


11 Right-click the FTP site and select Properties.

12 Select the Home Directory tab.

13 Write down the value entered for the Local Path for future use.

14 Verify the Read and Write boxes are checked.

15 Click OK.

16 Close the Computer Management window.

17 Go to step 43.

Install Microsoft Windows FTP Server Software


19 Double-click Add/Remove Programs.

20 On the left sife of the Add/Remove Programs window, select Add/Remove Windows Components.

21 In the Components window, highlight Internet Information Services (IIS) and click the Details... button.

22 Select the File Transfer Protocol (FTP) Server/Service checkbox.

23 Click OK.

24 In the Windows Components window, click Next to initiate the installation.

25 As the installation continues, the user may be asked to provide Windows1 media. Either insert the disk or browse to location of files.

Configure PC as FTP Server4-418


26 In the completion window, click Finish.

27 Close the Add/Remove Programs window.

Configure FTP Site


29 Double-click on the Administrative Tools icon.

30 Double-click on the Computer Management icon.

31 In the Computer Management window, expand the Services and Applications node.

32 Select the Internet Information Services node.

33 Right-click Default FTP Site in the details window and select Properties.

34 Select the Security Accounts tab.

35 Uncheck the Allow Anonymous Connections box.

36 If prompted, click Yes in the confirmation window.

37 Select the Home Directory tab.

38 Under the FTP Site Directory pane, set the Local Path to where the NE database backups and NE generic software is to be stored.

The Alcatel preferred path is: C:\ALCATEL

Note: If selecting a different directory, note the location for future use.

39 Verify that the Read and Write check boxes are selected.

40 Click OK.

41 Close the Computer Management window.

42 Close the Administrative Tools window.

Configure FTP User Account


1. Windows is a registered trademark of Microsoft Corporation.



44 Double-click Users and Passwords. (For Windows XP, double-click User Accounts.)

45 In the Users and Passwords/User Accounts window, select the Advanced tab.

46 Under Advanced User Management, click the Advanced button.

47 Right-click the Users node and select New User...

48 Enter the name gemftp for the User name.

49 Enter and confirm password.

Note: Record this password for future reference and protect it to prevent unauthorized use.

50 Uncheck the User must change password at next login box.

51 Check the User cannot change password and Password never expires boxes.

52 Click Create.

53 Click Close.

54 Close the Local Users and Groups window.

55 In the Users and Passwords/User Accounts window, click OK.

56 Is PC running Windows XP Service Pack 2?


Create Exception for FTP Port


58 Double-click the Windows Firewall icon.

59 Click the Exceptions tab.

60 Click the Add Port... button.

61 In the name field, enter FTP.

62 In the Port number field, enter 21.

63 Click OK.



64 Click OK to close the Windows Firewall box.




DLP-202Add Node to UPSRPURPOSE

This procedure provides instructions to add a new node to an existing and In-Service two-fiber ring network.

The new node will be connected between two operational nodes called the West node and the East node. The West node is defined as the node connecting to the west link of the new node’s ring link. The East node is defined as the node connecting to the east link of the new node’s ring link.

For all 1677 SONET Link nodes, the West port corresponds to the lower slot numbered (left, protected) card in a FFP pair. The East port corresponds to the higher slot numbered (right, protecting) card in a FFP pair.

To delete a node from a UPSR, refer to DLP-203.

PREREQUISITES

There should not be any facility or node failures prior to performing this procedure.

GENERAL

Alarms will occur during this procedure but will be cleared by the end of the procedure.

The valid AID values for OC-n facilities PROTECTED_ID and PROTECTING_ID using the ENT-FFP-OCn are listed in table 202-A.


Table 202-A. OC-n UPSR Nodes PROTECTED_ID and PROTECTING_ID PairsOC-n UPSR PROTECTED_ID AND PROTECTING_ID PAIRS

PROTECTED_ID AID PROTECTING_ID AIDOC-3 OC3-{1,3,5,12,14,16}-{A,B}-{1-12} OC3-{2,4,6,13,15,17}-{A,B}-{1-12}OC-12 OC12-{1,3,5,12,14,16}-{A,B}-{1-4} OC12-{2,4,6,13,15,17}-{A,B}-{1-4}OC-48 OC48-{1,3,5,12,14,16}-{A,B}-1 OC48-{2,4,6,13,15,17}-{A,B}-1OC-192 OC192-{5,12}-AB-1 OC192-{6,13}-AB-1

Add Node to UPSR 4-423



STEP PROCEDURE

1 Select action.

To add node to UPSR with 1677 SONET Link EMA, go to step 2.To add node to UPSR with TL1, go to step 100.

Add Node to UPSR with 1677 SONET Link EMA

PROVISION NEW NODE

2 Right-click the Equipment domain in the Scope Pane.



Figure 202-1. Sample UPSR Configuration Before and After Node is Added

677-0236-1081004

Pre-existing Ring

A

B

C

Ring with Added Node

New Node

A

B

C

D

Add Node to UPSR4-424




7 Click Finish.

Provision OC-n Facility







14 Click Finish.

15 Repeat steps 8 through 14 to provision OC-n facility in protection slot.






20 On the Protection Type page, select UPSR from the drop-down list.

21 Click Next.



24 Click Finish.















35 Click Finish.









42 Click OK.








47 Click OK.


49 Select THRU from the options in the drop-down list.





Switch West Node Circuits Away From New Node

The West node’s circuits that will be disconnected in order to connect to the new node need to be switched away from the new node.



56 Expand the appropriate OC-n protection range to display current protection pairs.

57 Select the appropriate OC-n protection pair. A list of STS-n protection pairs is displayed in the Result Pane.

58 Select the appropriate STS-n protection pair and observe the value of the Preferred Facility in the Result Pane.

59 Right-click on the appropriate STS-n protection pair and select Operate Switch. The Operate Protection Switch wizard appears.




61 On the Switching Side page, select the switching side (Working or Protecting).

62 Click Next.

63 Refer to the value of the Preferred Facility parameter from step 58. On the Switch Command Mode page, select one of the following options:

If Preferred Facility is East, select Manual switch from Preferred.If Preferred Facility is West, select Manual switch from Alternate.

64 Click Next.


66 CAUTION: Possibility of service interruption. This step may cause traffic hits on circuits that pass through the West and East nodes.

Click Finish.

67 Repeat steps 54 through 66 for all STS-n circuits that need to be switched away from the new node.

Switch East Node Circuits Away From New Node

The East node’s circuits that will be disconnected in order to connect to the new node need to be switched away from the new node.




71 Select the appropriate OC-n protection pair. A list of STS-n protection pairs is displayed in the Result Pane.


73 Right-click on the appropriate STS-n protection pair and select Operate Switch. The Operate Protection Switch wizard appears.



76 Click Next.




If Preferred Facility is East, select Manual switch from Alternate.If Preferred Facility is West, select Manual switch from Preferred.

78 Click Next.



Click Finish.


Remove Fibers from West and East Nodes

82 On the West node, remove the receive fiber that is currently connected to the East node. To do this, disconnect the fiber connected to the east module Rx connector. (The east module is the higher numbered module of the pair.) See figure 202-2.

83 On the East node, remove the receive fiber that is currently connected to the West node. To do this, disconnect the fiber connected to the west module Rx connector. (The west module is the lower numbered module of the pair.) See figure 202-2.

Figure 202-2. Fiber Connections Before New Node is Added

677-0239-1111703

A

B

C

WestCard

EastCard

East Card

West Card

West Card

East Card

EastNode

WestNode



Connect New Node to West and East Nodes

84 Use fibers to connect the New node to the West and East nodes. See figure 202-3.

a. Using a fiber-optic cable, connect one end of the cable to the east card Rx connector (on the New node) and connect the other end of the cable to the west card Tx connector (on the East node).

b. Using a fiber-optic cable, connect one end of the cable to the west card Rx connector (on the East node) and the other end of the cable to the east card Tx connector (on the New node).

c. Using a fiber-optic cable, connect one end of the cable to the east card Rx connector (on the West node) and the other end of the cable to the west card Tx connector (on the New node).

d. Using a fiber-optic cable, connect one end of the cable to the west card Rx connector (on the New node) and the other end of the cable to the east card Tx connector (on the West node).

Release Protection Switch on West Node



Figure 202-3. Fiber Connections after New Node is Added

New Node 677-0237-1111703

A

B

C

D

WestNode

EastNode

EastCard

WestCard

WestCard

EastCard

East Card

West Card

West Card

East Card




88 Select the appropriate OC-n protection pair. A list of STS-n protection pairs is displayed in the results pane.

89 Right-click on the appropriate STS-n protection pair and select Release Switch. The Release Switch dialog box appears.


Click Release to release protection switch.

91 Repeat steps 85 through 90 for other connections on West node.

Release Protection Switch on East Node




95 Select the appropriate OC-n protection pair. A list of STS-n protection pairs is displayed in the results pane.

96 Right-click on the appropriate STS-n protection pair and select Release Switch. The Release Switch dialog box appears.



98 Repeat steps 92 through 97 for other connections on East node.

99 Go to step 135.

Add Node to UPSR with TL1

Provision New Node

100 Enter ENT-EQPT::AID:::TYPE;

where:AID=Access Identifier of OC3, OC12, OC48, or OC192 moduleTYPE={OC3-12P, OC12-4P, OC48-1P, OC192-1P}




where:OCn=Optical facility type (OC3, OC12, OC48, OC192).AID=OCn Access Identifier




104 Select action.

To provision OC-3 or OC-12 facility and FFP, go to step 105.To provision OC-48 or OC-192 facility and FFP, go to step 109.

105 Enter ENT-OCn::AID::::[CKTID=][,SDTHRESH=][,SFTHRESH=][,TRC=][,ALSENB=]:[PST][,SST];

where:OCn=Optical facility type (OC3 or OC12).AID=OC-3 or OC-12 Access IdentifierOther parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

106 Repeat step 105 for OC-3 or OC-12 facility in protection slot.

107 Enter ENT-FFP-OCn::PROTECTED_ID,PROTECTING_ID::::[APSTRC=],PTYPE=UPSR[,PSDIRN=][,RVRTV=][,RVRTTIM=];

where:OCn=Optical facility type OC3 or OC12).PROTECTED_ID=Working (preferred) OC-3/OC-12 in UPSR groupPROTECTING_ID=Protecting (alternate) OC-3/OC-12 in UPSR groupRefer to table 202-A for valid working and protect pairs. Ports must be configured on an adjacent pair of cards.Other parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

108 Go to step 112.



109 Enter ENT-OCn::AID::::[CKTID=][,SDTHRESH=][,SFTHRESH=][,TRC=][,ALSENB=][,OPRNOM=][,TXPWR=]:[PST][,SST];


110 Repeat step 109 for OC-48 or OC-192 facility in protection slot.

111 Enter ENT-FFP-OCn::PROTECTED_ID,PROTECTING_ID::::PTYPE=UPSR[,PSDIRN=][APSTRC=][,RVRTV=][,RVRTTIM=][,NODEID=][,NODEDESCR=][,AUTOMAP=][,RINGID=];

where:OCn=Optical facility type (OC48 or OC192).PROTECTED_ID=Working (preferred) OC-48/OC-192 in UPSR groupPROTECTING_ID=Protecting (alternate) OC-48/OC-192 in UPSR groupRefer to table 202-A for valid working and protect pairs. Ports must be configured on an adjacent pair of cards.Other parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

112 Enter RTRV-STSn::[AID];

where:STSn=Signal type (STS1, STS3C, STS12C, or STS48C).AID=STSn Access Identifier




115 Select action.

To provision STS-1, go to step 116.To provision STS-3c, STS-12c, or STS-48c, go to step 118.





117 Go to step 119.



119 Enter ENT-CRS-STSn::FROM,TO:::THRU[,CCT2]:[CKTID=[,CKTADDR=][,CKTNBR=][,SWPDIP=][,SWUNEQP=][,PREFERRED=][,RVRTV=][,RVRTTIM=][,SWPDIP2=][,SWUNEQP2=][,PREFERRED2=][,RVRTV2=][,RVRTTIM2=]; to configure the THRU cross-connections.

where:STSn=Signal type (STS1, STS3C, STS12C, or STS48C).FROM=Access Identifier of source facilityTO=Access Identifier of destination facilityCCT=Cross-connect type (THRU)Other parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

Switch West Node Circuits Away From New Node

The West node’s circuits that will be disconnected in order to connect to the new node need to be switched away from the new node.

120 Enter RTRV-CRS-STSn::AID;

where:STSn=Signal type (STS1, STS3C, STS12C, or STS48C)AID=STSn Access Identifier

121 Observe output. Note value of preferred direction from parameter PREFERRED=.




Enter OPR-PROTNSW-STSn::AID:::SWTCHCMD;

where:STSn=Signal type (STS1, STS3C, STS12C, or STS48C).AID=STSn Access IdentifierSWTCHCMD=Switching command to be performed. Refer to value of Preferred parameter from step 121 and select one of the following options:

If PREFERRED=EAST, use MANWKSWPR for the value of SWTCHCMD.If PREFERRED=WEST, use MANWKSWBK for the value of SWTCHCMD.


Switch East Node Circuits Away From New Node

The East node’s circuits that will be disconnected in order to connect to the new node need to be switched away from the new node.







If PREFERRED=EAST, use MANWKSWBK for the value of SWTCHCMD.If PREFERRED=WEST, use MANWKSWPR for the value of SWTCHCMD.





128 On the West node, remove receive fiber that is currently connected to the East node. To do this, disconnect the fiber connected to the east module Rx connector. (The east module is the higher numbered module of the pair.) See figure 202-4.

129 On the East node, remove receive fiber that is currently connected to the West node. To do this, disconnect the fiber connected to the west module Rx connector. (The west module is the lower numbered module of the pair.) See figure 202-4.


677-0239-1111703

A

B

C

WestCard

EastCard

East Card

West Card

West Card

East Card

EastNode

WestNode





a. Using a fiber-optic cable, connect one end of the cable to the east card Rx connector (on the New node) and connect the other end of the cable to the west card Tx connector (on the East node).




Figure 202-5. Fiber Connections After New Node is Added

New Node 677-0237-1111703

A

B

C

D

WestNode

EastNode

EastCard

WestCard

WestCard

EastCard

East Card

West Card

West Card

East Card





Enter RLS-PROTNSW-STSn::AID;

where:STSn=Facility type (STS1, STS3C, STS12C, or STS48C)AID=Protected STSn Access Identifier

132 Repeat step 131 for other connections on West node.





134 Repeat step 133 for other connections on East node.




DLP-203Delete Node from UPSRPURPOSE

This procedure provides instructions to delete a node from an existing and In-Service two-fiber ring network.

The node to be deleted is connected between two operational nodes called the West node and the East node. The West node is defined as the node connected to the west link of the node to be deleted. The East node is defined as the node connected to the east link of the node to be deleted.


PREREQUISITES


There must not be circuits terminated at the node to be deleted. If there are, they must be removed prior to performing this procedure.

GENERAL


This procedure does not provide instructions to delete a node that is a Gateway NE (GNE).


STEP PROCEDURE

1 Select action.

To delete node from UPSR with 1677 SONET Link EMA, go to step 2.To delete node from UPSR with TL1, go to step 53.

Delete Node from UPSR with 1677 SONET Link EMA

Retrieve all THRU Connections



Delete Node from UPSR 4-439



5 Examine results. Note all connections with cross-connect type of THRU that pass through the node to be deleted.

6 Repeat steps 2 through 5 for other STS-n facility types.

Switch West Node Circuits Away From Node to be Deleted

Circuits on the West node that are outbound to the node to be deleted need to be switched away from the node to be deleted.






12 Right-click appropriate STS-n protection pair and select Operate Switch. The Operate Protection Switch wizard appears.



15 Click Next.


If Preferred Facility is East, select Manual switch from Preferred.If Preferred Facility is West, select Manual switch from Alternate.

17 Click Next.



Click Finish.

Delete Node from UPSR4-440


20 Repeat steps 7 through 19 for all STS-n connections (from step 5) on the West node.

Switch East Node Circuits Away From Node to be Deleted

Circuits on the East node that are outbound to the node to be deleted need to be switched away from the node to be deleted.






26 Right-click STS-n protection pair and select Operate Switch. The Operate Protection Switch wizard appears.



29 Click Next.


If Preferred Facility is East, select Manual switch from Alternate.If Preferred Facility is West, select Manual switch from Preferred.

31 Click Next.



Click Finish.

34 Repeat steps 21 through 33 for all STS-n connections (from step 5) on the East node.



Remove Fibers from Node to be Deleted

35 On the West node, remove fibers that are currently connected to the node to be deleted. See figure 203-1.

a. Disconnect the fiber between the east module Rx connector (on the West node) and the west module Tx connector (on the node to be deleted). (The east module is the higher numbered module of the pair.)

b. Disconnect the fiber between the west module Rx connector (on the node to be deleted) and the east module Tx connector (on the West node). (The west module is the lower numbered module of the pair.)

36 On the East node, remove fibers that are currently connected to the node to be deleted. See figure 203-1.

a. Disconnect the fiber between the east module Rx connector (on the node to be deleted) and the west module Tx connector (on the East node). (The east module is the higher numbered module of the pair.)

b. Disconnect the fiber between the west module Rx connector (on the East node) and the east module Tx connector (on the node to be deleted). (The west module is the lower numbered module of the pair.)

Figure 203-1. Fiber Connections to be Removed from Node to be Deleted

Node to bedeleted

677-0238-1111703

A

B

C

D

WestNode

EastNode

EastCard

WestCard

WestCard

EastCard

East Card

West Card

West Card

East Card



Connect West and East Nodes

37 Use fibers to connect the West node to the East node. See figure 203-2.

a. Using a fiber-optic cable, connect one end of the cable to the east module Rx connector (on the West node) and connect the other end of the cable to the west module Tx connector (on the East node).

b. Using a fiber-optic cable, connect one end of the cable to the west module Rx connector (on the East node) and connect the other end of the cable to the east module Tx connector (on the West node).






42 Right-click appropriate STS-n protection pair and select Release Switch. The Release Switch dialog box appears.

Figure 203-2. Fiber Connections after Node is Deleted

677-0239-1111703

A

B

C

WestCard

EastCard

East Card

West Card

West Card

East Card

EastNode

WestNode





44 Repeat steps 38 through 43 for other connections on West node.






49 Right-click appropriate STS-n protection pair and select Release Switch. The Release Switch dialog box appears.



51 Repeat steps 45 through 50 for other connections on East node.

52 Go to step 70.

Delete Node from UPSR with TL1

Retrieve all THRU Connections

53 Enter RTRV-CRS-ALL:::::THRU;

54 Examine output. Note all connections with cross-connect type of THRU that pass through the node to be deleted.

Switch West Node Circuits Away From Node to be Deleted

Circuits on the West node that connect to the node to be deleted need to be switched away from the node to be deleted.









If PREFERRED=EAST, use MANWKSWPR for the value of SWTCHCMD.If PREFERRED=WEST, use MANWKSWBK for the value of SWTCHCMD.

58 Repeat steps 55 through 57 for all STS-n connections (from step 53) on the West node.

Switch East Node Circuits Away From Node to be Deleted

Circuits on the East node that connect to the node to be deleted need to be switched away from the node to be deleted.









If PREFERRED=EAST, use MANWKSWBK for the value of SWTCHCMD.If PREFERRED=WEST, use MANWKSWPR for the value of SWTCHCMD.

62 Repeat steps 59 through 61 for all STS-n connections (from step 53) on the East node.



a. Disconnect the fiber between the west card Tx connector (on the node to be deleted) and the east card Rx connector (on the West node). (The east card is the higher numbered card of the pair.)

b. Disconnect the fiber between the east card Tx connector (on the West node) and the west card Rx connector (on the node to be deleted). (The west card is the lower numbered card of the pair.)


a. Disconnect the fiber between the west card Tx connector (on the East node) and the east card Rx connector (on the node to be deleted). (The east card is the higher numbered card of the pair.)

b. Disconnect the fiber between the east card Tx connector (on the node to be deleted) and the west card Rx connector (on the East node). (The west card is the lower numbered card of the pair.)





a. Using a fiber-optic cable, connect one end of the cable to the east card Rx connector (on the West node) and connect the other end of the cable to the west card Tx connector (on the East node).

b. Using a fiber-optic cable, connect one end of the cable to the west card Rx connector (on the East node) and connect the other end of the cable to the east card Tx connector (on the West node).





67 Repeat step 66 for other connections on West node.





69 Repeat step 68 for other connections on East node.




DLP-204Add Node to Two-Fiber BLSRPURPOSE

This procedure provides instructions to add a new node to an existing and In-Service two-fiber ring network.

The new node will be connected between two operational nodes called the West node and the East node. The West node is defined as the node connecting to the west link of the new node’s ring link. The East node is defined as the node connecting to the east link of the new node’s ring link.


To delete a node from a two-fiber BLSR, refer to DLP-205.

PREREQUISITES


GENERAL


The Node ID of the new node (the first number of the ring map) must be unique within the ring map. An incorrectly provisioned ring map will result in a service outage under certain failure conditions.

The valid AID values for OC-n facilities using the ENT-FFP-OCn are listed in table 204-A.


Table 204-A. OC-n BLSR Nodes Protected and Protecting PairsOC-n BLSR PROTECTING AND PROTECTED PAIRS

Protected AID Protecting AIDOC-48 OC48-{1,3,5,12,14,16}-{A,B}-1 OC48-{2,4,6,13,15,17}-{A,B}-1OC-192 OC192-{5,12}-AB-1 OC192-{6,13}-AB-1

Add Node to Two-Fiber BLSR 4-449



STEP PROCEDURE

1 Select action.

To add node to two-fiber BLSR with 1677 SONET Link EMA, go to step 2.To add node to two-fiber BLSR with TL1, go to step 141.

Add Node to Two-Fiber BLSR with 1677 SONET Link EMA

Disable Automap on Nodes A, B, and C




Figure 204-1. Sample BLSR Configuration Before and After Adding Node

New Node

Pre-existing Ring Ring with Added Node

677-0235-1081104

Node ID=3

Node ID=2

Node ID=1

A

B

C

Node ID=3

Node ID=2

Node ID=1

Node ID=4

A

B

C

D

Add Node to Two-Fiber BLSR4-450


5 Scroll to the Automap parameter, double-click in the box, and select N from the drop-down list.

6 Click Apply.

7 Click Close.

8 Repeat steps 2 through 7 for Node B.

9 Repeat steps 2 through 7 for Node C.

Switch West Node Link to Protection

The West node’s link that will be disconnected in order to connect to the new node needs to be switched to protection.







16 Click Next.

17 On the Switch Command Mode page, select Forced switch of working to Protection-Ring.

18 Click Next.


20 CAUTION: Possibility of service interruption. This step may cause traffic hits on circuits that pass through the West and East nodes. A forced-ring line switch preempts any extra traffic on the ring.

Click Finish.

Switch East Node Link to Protection

The East node’s link that will be disconnected in order to connect to the new node needs to be switched to protection.








26 On the Switching Side page, select West.

27 Click Next.


29 Click Next.



Click Finish.


32 On the West node, remove receive fiber that is currently connected to the East node. To do this, disconnect the fiber connected to the east module Rx connector. (The east module is the higher numbered module of the pair.) See figure 204-2.

33 On the East node, remove receive fiber that is currently connected to the West node. To do this, disconnect the fiber connected to the west module Rx connector. (The west module is the lower numbered module of the pair.) See figure 204-2.





There will be a transient node ID conflict condition when the ring is reconnected.

a. Using a fiber-optic cable, connect one end of the cable to the east module Rx connector (on the New node) and the other end of the cable to the west module Tx connector (on the East node).

b. Using a fiber-optic cable, connect one end of the cable to the west module Rx connector (on the East node) and the other end of the cable to the east module Tx connector (on the New node).

c. Using a fiber-optic cable, connect one end of the cable to the east module Rx connector (on the West node) and the other end of the cable to the west module Tx connector (on the New node).

d. Using a fiber-optic cable, connect one end of the cable to the west module Rx connector (on the New node) and the other end of the cable to the east module Tx connector (on the West node).


677-0239-1111703

A

B

C

WestCard

EastCard

East Card

West Card

West Card

East Card

EastNode

WestNode



Provision New Node



37 Provision working OC-n facility. Right-click on the appropriate OC-n group and select Create. The Provision OC-n wizard appears.




41 Click Finish.

42 Repeat steps 37 through 41 to provision the protection OC-n facility (East facility).

Enable DCC



Figure 204-3. Fiber Connections after New Node is Added

New Node 677-0237-1111703

A

B

C

D

WestNode

EastNode

EastCard

WestCard

WestCard

EastCard

East Card

West Card

West Card

East Card



45 Right-click on appropriate OC-n facility protection range and select Network Interface>Create. The Create Network Interface wizard appears.


47 On the Name page, enter AID of Protected (west) OC-n.

48 Click Next.

49 Click Next to skip the Line Lower Layer Protocol page.

50 On the Line Upper Layer Protocol page, select action.

To enable DCC on line of OC-n, go to step 55.To enable DCC on section of OC-n, go to step 51.

51 Click Next.

52 Click Next to skip the Section Lower Layer Protocol page.

53 On the Section Upper Layer Protocol page, select CLNP from drop-down menu.

54 Go to step 56.

55 Select CLNP from drop-down menu.

56 Click Go to Finish.


58 Click Finish.

59 Repeat steps 45 through 58 for protecting (east) OC-48 or OC-192.


60 To enable BLSR node application, expand the Protection domain in the Scope Pane.




64 On the Protection Type page, select PROT_TYPE_2FBLSR from the drop-down menu.



65 Click Next.


On the Automap page, select No.


68 Click Finish.













79 Click Finish.











86 Click OK.






91 Click OK.


93 Select THRU from the options in the drop-down list.





Update Ring Map on New Node in Ring



100 Select appropriate OC-n protection range to display current protection pairs.






103 Click Apply.

104 Click Close.

Update Squelch Map






110 Double-click in cell under Source Node and select node ID value from drop-down list.

111 Double-click in cell under Destination Node and select node ID value from drop-down list.

112 Click Apply.

113 Click Close.

Update Ring Maps on Other Nodes in Ring




116 Click Apply.

117 Click Close.



118 Repeat steps 114 through 117 to update Ring Maps as needed on other nodes in the ring.






123 Select East.


Click Release.






129 Select West.


Click Release.

Enable Automap on Nodes A, B, C, and D




134 Scroll to the Automap parameter, double-click in the box, and select Y from the drop-down list.



135 Click Apply.

136 Click Close.

137 Repeat steps 131 through 136 for Node B.

138 Repeat steps 131 through 136 for Node C.

139 Repeat steps 131 through 136 for Node D.

140 Go to step 184.

Add Node to Two-Fiber BLSR with TL1

Disable Automap on Nodes A, B, and C

141 Enter ED-FFP-OCn::PROTECTED_ID,[PROTECTING_ID]::::,AUTOMAP=N;

where:OCn=Optical facility type (OC48 or OC192)PROTECTED_ID=West OC-48/192 in BLSR for Node A. Refer to 204-1.PROTECTING_ID=East OC-48/192 in BLSR for Node A. Refer to 204-1.

142 Repeat step 141 for Node B.

143 Repeat step 141 for Node C.


The West node’s link that will be disconnected in order to connect to the new node needs to be switched to protection.


Enter OPR-PROTNSW-OCn::AID:::FRCD-R;

where:OCn=Optical facility type (OC48 or OC192).AID=OCn Access Identifier on East card

A forced-ring line switch preempts any extra traffic on the ring.







where:OCn=Optical facility type (OC48 or OC192).AID=OCn Access Identifier on West card



146 On the West node, remove receive fiber that is currently connected to the East node. To do this, disconnect the fiber connected to the east card Rx connector. (The east card is the higher numbered card of the pair.) See figure 204-4.

147 On the East node, remove receive fiber that is currently connected to the West node. To do this, disconnect the fiber connected to the west card Rx connector. (The west card is the lower numbered card of the pair.) See figure 204-4.


677-0239-1111703

A

B

C

WestCard

EastCard

East Card

West Card

West Card

East Card

EastNode

WestNode






a. Using a fiber-optic cable, connect one end of the cable to the east card Rx connector (on the New node) and the other end of the cable to the west card Tx connector (on the East node).




Figure 204-5. Fiber Connections After New Node is Added

New Node 677-0237-1111703

A

B

C

D

WestNode

EastNode

EastCard

WestCard

WestCard

EastCard

East Card

West Card

West Card

East Card



Provision New Node


where:OCn=Optical facility type (OC48, OC192).AID=OCn Access Identifier




152 Enter ENT-OCn::AID::::[CKTID=][,SDTHRESH=][,SFTHRESH=][,TRC=][,ALSENB=][,OPRNOM=][,TXPWR=]:[PST][,SST]; to provision working OCn facility.


153 Repeat step 152 for OC-n facility in protection slot.

Enable DCC

154 Select action.

To enable DCC on line of OCn, go to step 155.To enable DCC on section of OCn, go to step 158.

155 Enter ENT-NETIF::AID::::,LINEUL=CLNP;

where:AID=Protected (west) OC-48 or OC-192 Access Identifier


157 Go to step 160.

158 Enter ENT-NETIF::AID::::,,,SECTIONUL=CLNP;

where: AID=Protected (west) OC-48 or OC-192 Access Identifier





160 Enter ENT-FFP-OCn::PROTECTED_ID,PROTECTING_ID::::PTYPE=BLSR2[,PSDIRN=][APSTRC=][,RVRTV=][,RVRTTIM=],NODEID=[,NODEDESCR=],AUTOMAP=N,RINGID=;

where:OCn=Optical facility type (OC48 or OC192).PROTECTED_ID=West OC-48/OC-192 in BLSRPROTECTING_ID=East OC-48/OC-192 in BLSRNODEID=Local node identifier. Must be unique within a BLSR. {0-15}AUTOMAP=Automatic provisioning feature where squelch and ring maps are learned is enabled. {Y or N} Default=Y if PTYPE=BLSR2. If AUTOMAP=N, ring maps and squelch maps must be manually entered for the BLSR to operate correctly.RINGID=Ring identifier, identifies a BLSR within a shelf.Refer to table 204-A for valid working and protect pairs. Ports must be configured on an adjacent pair of cards.Other parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.



where:STSn=Signal type (STS1, STS3C, STS12C, or STS48C).AID=STSn Access Identifier




164 Select action.

To provision STS-1, go to step 165.To provision STS-3c, STS-12c, or STS-48c, go to step 167.





166 Go to step 168.




168 Enter ENT-CRS-STSn::FROM,TO:::THRU[,CCT2]:[CKTID=[,CKTADDR=][,CKTNBR=][,SWPDIP=][,SWUNEQP=][,PREFERRED=][,RVRTV=][,RVRTTIM=][,SWPDIP2=][,SWUNEQP2=][,PREFERRED2=][,RVRTV2=][,RVRTTIM2=]; to configure the THRU cross-connections.

where:STSn=Signal type (STS1, STS3C, STS12C, or STS48C).FROM=Access Identifier of source facilityTO=Access Identifier of destination facilityCCT=Cross-connect type (THRU)Other parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

Update Ring Map on New Node in Ring


where: AID=OCn Access Identifier or ALL

Example Output:





where:AID=OCn Access IdentifierRINGMAP=Sequence of node IDs within a BLSR. (0-15) The first RINGMAP value defines the node ID of the adjacent BLSR node (east side). Subsequent RINGMAP values define the node ID of the BLSR node (in the eastward side). The last RINGMAP value defines the node ID of the adjacent BLSR node (west side).


where: AID=OCn access identifier or ALL

Update Squelch Map

172 Enter RTRV-SQLMAP::AID; to retrieve current squelch map.

where: AID=STSn or OC-48/OC192 Access Identifier on new node in the ring

173 Enter ED-SQLMAP::AID::::ENTRY=,EXIT=;

where:AID=STSn or OC-48/OC192 Access IdentifierENTRY=Node ID (0-15) of the source node in the BLSR.EXIT=Node ID (0-15) of the destination node in the BLSR.

174 Enter RTRV-SQLMAP::AID; to verify the new squelch map.

where: AID=STSn or OC-48/OC192 Access Identifier

Update Ring Maps on Other Nodes in Ring


where: AID=OC48 or OC192 Access Identifier or ALL




where:AID=OC-48 or OC-192 Access Identifier of BLSR nodeRINGMAP=Sequence of node IDs within a BLSR. (0-15) Ampersand (&) grouping is used to join each node ID value (up to 15 values). The first RINGMAP value defines the node ID of the adjacent BLSR node (east side). Subsequent RINGMAP values define the node ID of the BLSR node (in the eastward side). The last RINGMAP value defines the node ID of the adjacent BLSR node (west side).


where: AID=OC48 or OC192 Access Identifier or ALL



Enter RLS-PROTNSW-OCn::AID;

where:OCn=Optical facility type (OC48 or OC192).AID=OCn Access Identifier on West node




where:OCn=Optical facility type (OC48 or OC192).AID=OCn Access Identifier on East node

Enable Automap on Nodes A, B, C, and D

180 Enter ED-FFP-OCn::PROTECTED_ID,[PROTECTING_ID]::::,AUTOMAP=Y;

where:OCn=Optical facility type (OC48 or OC192)PROTECTED_ID=West OC-48/192 in BLSR for Node A. Refer to 204-1.PROTECTING_ID=East OC-48/192 in BLSR for Node A. Refer to 204-1.

181 Repeat step 180 for Node B.

182 Repeat step 180 for Node C.



183 Repeat step 180 for Node D.




DLP-205Delete Node from Two-Fiber BLSRPURPOSE

This procedure provides instructions to delete a node from an existing and In-Service two-fiber ring network.

The node to be deleted is connected between two operational nodes called the West node and the East node. The West node is defined as the node connected to the west link of the node to be deleted. The East node is defined as the node connected to the east link of the node to be deleted.


PREREQUISITES


Circuits must not originate or terminate at the node to be deleted. If there are circuits that originate or terminate at the node to be deleted, they must be removed prior to performing this procedure.

GENERAL


This procedure does not provide instructions to delete a node that is a Gateway NE (GNE).


STEP PROCEDURE

1 Select action.

To delete node from two-fiber BLSR with 1677 SONET Link EMA, go to step 2.To delete node from two-fiber BLSR with TL1, go to step 73.

Delete Node from Two-Fiber BLSR with 1677 SONET Link EMA

Eliminate Traffic Originating or Terminating at Node to be Deleted


Delete Node from Two-Fiber BLSR 4-469






7 Is the node to be deleted specified in the Source or Destination parameters?


8 Delete all pass-through cross-connections that have the node to be deleted as their ENTRY or EXIT. Refer to DLP-125 to delete STS-n connections.

9 Update squelch map. Refer to DLP-156.


The West node’s link that will be disconnected in order to remove the node needs to be switched to protection.







16 Click Next.


18 Click Next.


Delete Node from Two-Fiber BLSR4-470



Click Finish.








26 On the Switching Side page, select West.

27 Click Next.


29 Click Next.



Click Finish.





a. Disconnect the fiber between the east module Rx connector (on the West node) and the west module Tx connector (on the node to be deleted). (The east module is the higher numbered module of the pair.)

b. Disconnect the fiber between the west module Rx connector (on the node to be deleted) and the east module Tx connector (on the West node). (The west module is the lower numbered module of the pair.)


a. Disconnect the fiber between the east module Rx connector (on the node to be deleted) and the west module Tx connector (on the East node). (The east module is the higher numbered module of the pair.)

b. Disconnect the fiber between the west module Rx connector (on the East node) and the east module Tx connector (on the node to be deleted). (The west module is the lower numbered module of the pair.)

Figure 205-1. Fiber Connections to be Removed from Node to be Deleted

Node to bedeleted

677-0238-1111703

A

B

C

D

WestNode

EastNode

EastCard

WestCard

WestCard

EastCard

East Card

West Card

West Card

East Card






a. Using a fiber-optic cable, connect one end of the cable to the east module Rx connector (on the West node) and connect the other end of the cable to the west module Tx connector (on the East node).

b. Using a fiber-optic cable, connect one end of the cable to the west module Rx connector (on the East node) and connect the other end of the cable to the east module Tx connector (on the West node).






39 Select East.

Figure 205-2. Fiber Connections after Node is Deleted

677-0239-1111703

A

B

C

WestCard

EastCard

East Card

West Card

West Card

East Card

EastNode

WestNode




Click Release.






45 Select West.


Click Release.

Update Ring Map on Remaining Nodes in Ring




50 Right-click on appropriate protection pair and select Properties>General.

51 Scroll to the Automap parameter and note the value.



53 Click Close.






57 Click Next.


59 Click Next.


61 Click Finish.





65 Click Apply.

66 Click Close.


68 Select East.

69 Click Release.


71 Repeat steps 54 through 70 to update ring map on other remaining nodes on the ring.

72 Go to step 96.

Delete Node from Two-Fiber BLSR with TL1

Eliminate Traffic Originating or Terminating at Node to be Deleted

73 Enter RTRV-SQLMAP::AID;

where:AID=OC-n Access Identifier



74 Observe output and note ENTRY and EXIT parameter values.

75 Is the node to be deleted specified in the ENTRY or EXIT parameters?


76 Delete all pass-through cross-connections that have the node to be deleted as their ENTRY or EXIT. Refer to DLP-125 to delete STS-n connections.

77 Update squelch map. Refer to DLP-156.


The West node’s link that will be disconnected in order to remove the node needs to be switched to protection.



where:OCn=Optical facility type (OC48 or OC192)AID=OCn Access Identifier on East card



The East node’s link that will be disconnected in order to remove the node needs to be switched to protection.



where:OCn=Optical facility type (OC48 or OC192)AID=OCn Access Identifier on West card






a. Disconnect the fiber between the east card Rx connector (on the West node) and the west card Tx connector (on the node to be deleted). (The east card is the higher numbered card of the pair.)

b. Disconnect the fiber between the west card Rx connector (on the node to be deleted) and the east card Tx connector (on the West node). (The west card is the lower numbered card of the pair.)


a. Disconnect the fiber between the east card Rx connector (on the node to be deleted) and the west card Tx connector (on the East node). (The east card is the higher numbered card of the pair.)

b. Disconnect the fiber between the west card Rx connector (on the East node) and the east card Tx connector (on the node to be deleted). (The west card is the lower numbered card of the pair.)




a. Using a fiber-optic cable, connect one end of the cable to the east card Rx connector (on the West node) and connect the other end of the cable to the west card Tx connector (on the East node).

b. Using a fiber-optic cable, connect one end of the cable to the west card Rx connector (on the East node) and connect the other end of the cable to the east card Tx connector (on the West node).




where:OCn=Optical facility type (OC48 or OC192)AID=OCn Access Identifier on West node






where:OCn=Optical facility type (OC48 or OC192)AID=OCn Access Identifier on East node

Update Ring Map on Remaining Nodes in Ring


where:OCn=Optical facility type (OC48 or OC192).AID=OC-48 or OC-192 access identifier

86 Observe output. Note value of AUTOMAP parameter.




where:AID=OCn Access Identifier or ALL

Example Output:



where:OCn=Optical facility (OC-48 or OC-192)AID=East OC-n facility Access Identifier




where:OCn=Optical facility (OC-48 or OC-192)AID=West OC-n facility Access Identifier


where:AID=OC-48 or OC-192 access identifier of BLSR nodeRINGMAP=Sequence of node IDs within a BLSR. (0-15) Ampersand (&) grouping is used to join each node ID value (up to 15 values). The first RINGMAP value defines the node ID of the adjacent BLSR node (east side). Subsequent RINGMAP values define the node ID of the BLSR node (in the eastward side). The last RINGMAP value defines the node ID of the adjacent BLSR node (west side).


where:AID=OC48 or OC192 Access Identifier or ALL


where:OCn=Optical facility (OC-48 or OC-192)AID=West OC-n facility Access Identifier


where:OCn=Optical facility (OC-48 or OC-192)AID=East OC-n facility Access Identifier

95 Repeat steps 88 through 94 to update ring map on other remaining nodes on the ring.




DLP-206Perform Database Backup to Flash DiskPURPOSE

This procedure provides the instructions to perform a backup of provisioning data to flash disk drives A or B. However, the preferred method for database backups is to backup to a remote FTP server to prevent overloading DISK-A. Refer to DLP-188.

GENERAL

To backup files to Redundant Disk System (RDS) drive B, the files are first backed up to drive A and then copied to drive B.

The ACT-DISK command activates or deactivates a flash disk on a Common Control Card (CCC). When activating Disk A9 or A10 as primary, configuration files can be imported from the newly activated disk, or the current configuration files can be exported from the NE to the disk.

The RTRV-DISK command retrieves the data and state parameters associated with the DISK equipment entities.


The MK-DIR command is used to create a directory within the /USER directory on a CCC flash disk.

The CPY-MEM command is used to copy a file from one CCC flash disk to another. Files can be copied into the /USER directory or its subdirectories only.


STEP PROCEDURE

1 Select action.

To perform database backup to flash disk with 1677 SONET Link EMA, go to step 2.To perform database backup to flash disk with TL1, go to step 75.

Perform Database Backup to Flash Disk with 1677 SONET Link EMA

Verify Disk Availability

2 Click on System domain to display contents.

Perform Database Backup to Flash Disk 4-481


3 Right-click on one of the disks (DISK-A or DISK-B) and select Properties>General. Note the free space.

4 Click Close.

5 Repeat steps 3 and 4 to retrieve information on the other disk.


7 Right-click on appropriate disk and select Properties>General. Note the free space.

8 Click Close.

9 Repeat steps 7 and 8 to retrieve information on the three other disks.

10 Is free disk space greater than 20 MB?


11 Right-click on the Network Element domain or the System domain and select System Configuration Operations>Purge. The Purge System Configuration wizard appears.


13 On the Configuration Directory page, specify the directory containing the configuration files to delete. This directory should be a path relative to the /cfg directory.

14 Click Next.


16 Click Finish.

17 Go to step 2.

Verify RDS Drives are Synchronized

18 Click Equipment domain to display current cards in system in the Result Pane.

19 Note the current Primary State and Secondary State of the four RDS drives (DISK-A9, DISK-A10, DISK-B9, DISK-B10)

20 Do the members of RDS drive A (A9 and A10) show one with PST,SST of IS,WRK and one with PST,SST of IS,STBYH?


Perform Database Backup to Flash Disk4-482


21 Activate RDS member(s), as required. One member should be IS,WRK and one should be IS,STBYH. Click Equipment domain to display current cards in system.

22 Right-click on appropriate disk (A9 or A10) and select Activate Disk. The Activate Disk wizard appears.


24 On the Disk Mode page, select the value for disk mode (Primary or Secondary).

25 Click Next.

26 Was Disk Mode selected Primary or Secondary?

If Primary, go to step 27.If Secondary, go to step 29.

27 On the Behavior page, select a value for the disk behavior from the drop-down menu (Import or Export).

28 Click Next.


30 Click Finish.

31 Wait a few minutes. Even though the command has completed, the disk synchronization is still in progress. This may take awhile.

32 Repeat steps 21 through 31 to activate other RDS member, if necessary.


34 Note the current Primary State and Secondary State of DISK-A9 and DISK-A10.

35 Does output show one RDS member with PST,SST of IS,WRK and the other RDS member with PST,SST of IS,STBYH?

If yes, go to step 36.If no, wait a minute and repeat steps 33 through 34.

36 Click System domain to display contents.

37 Right-click on DISK-A and select Properties>General. Note the current Primary State.



38 Does output show DISK-A with PST,SST of OOS-AUMA,SWDL or IS?

If OOS-AUMA,SWDL, synchronization is still in progress. Wait a few minutes and repeat steps 36 through 38.If IS, go to step 39.

39 Do the members of RDS drive B (B9 and B10) show one with PST,SST of IS,WRK and one with PST,SST of IS,STBYH?



41 Right-click on appropriate disk (B9 or B10) and select Activate Disk. The Activate Disk wizard appears.



44 Click Next.


46 Click Finish.




50 Note the current Primary State and Secondary State of DISK-B9 and DISK-B10.




53 Right-click on DISK-B and select Properties>General. Note the current Primary State.



54 Does output show DISK-B with PST,SST of OOS-AUMA,SWDL or IS?


Perform Database Backup

55 Right-click on the Network Element domain or the System domain and select System Configuration Operations>Backup. The Backup System Configuration wizard appears.


57 On the Backup Directory page, specify the directory to backup the system configuration files to. This directory should be a path relative to the /cfg directory.

58 Click Next.


60 Click Finish. Database backup to RDS drive A is complete.

61 Perform database backup to RDS drive B?


62 Right-click on the Network Element domain or the System domain and select File Operations>Make Directory. The Create Directory wizard appears.


64 On the Disk Selection page, select DISK-B as the disk on which to create the directory.

65 Click Next.

66 On the Path page, enter the pathname of the directory to hold the backup copy of the provisioning database. This directory is within the /user directory.


68 Click Finish.

69 Right-click on the Network Element domain or the System domain and select File Operations>Copy File. The Copy File wizard appears.






73 Click Finish.

74 Go to step 103.

Perform Database Backup to Flash Disk with TL1

Verify Disk Availability

75 Enter RTRV-DISK;

76 Observe output and note free disk space of each drive.

77 Is free disk space greater than 20 MB?


78 Enter OPR-DISK::::::TYPE=CFG,ACTION=PURGE,SRC=; to delete files.

where:SRC=directory within A:/CFG containing the configuration files to delete.

79 Go to step 75.


80 Enter RTRV-DISK;

81 Observe output.





83 Activate RDS member(s), as required. One member should be IS,WRK and one should be IS,STBYH.

Enter ACT-DISK::AID:::MODE=,ACTION=ACTIVATE,BEHAVIOR=;

where:AID=DISK-{A9, A10}MODE=PRI or SECBEHAVIOR=IMPORT or EXPORT (only if MODE=PRI)

84 Wait for the completion message. Even though the command has completed, the disk synchronization is still in progress. This may take awhile.


86 Enter RTRV-DISK;

87 Observe output.








Enter ACT-DISK::AID::::MODE=,ACTION=ACTIVATE;

where:AID=DISK-{B9, B10}MODE=PRI or SEC





94 Enter RTRV-DISK;

95 Observe output.





Perform Database Backup

98 Enter OPR-DISK:::::TYPE=CFG,ACTION=BACKUP,SRC=;

where:SRC=directory within A:/CFG to hold the backup copy of the provisioning database.

99 Wait for the completion message. Database backup to RDS drive A is complete.

100 Perform database backup to RDS drive B?


101 Enter MK-DIR::DISK-B:::PATH;

where:PATH=directory within B:/USER directory structure to hold the backup copy of the provisioning database, enclosed in quotation marks.



102 Enter CPY-MEM:::::FROMPATH,FDISK,DESTPATH,DDISK;

where:FROMPATH=pathname of the source file, enclosed in quotation marks.FDISK=DISK-ADESTPATH=pathname of the destination file, enclosed in quotation marks.DDISK=DISK-B

For example, the following command copies from the directory A:/cfg/bck0001/ to the directory B:/USER/bck0001:

CPY-MEM:::::”/cfg/bck0001/*”,DISK-A,”/user/bck0001/*”,DISK-B;




DLP-207Perform Database Restore from Flash DiskPURPOSE

This procedure provides the instructions to perform a restore of provisioning data from flash disk drive A.

GENERAL

The activation process copies the software files or configuration files from their backup locations to the A:/bin or A:/cfg directories, respectively.

GENERAL

To backup files to Redundant Disk System (RDS) drive B, the files are first backed up to drive A and then copied to drive B.


STEP PROCEDURE

1 Select action.

To perform database restore from flash disk with 1677 SONET Link EMA, go to step 2.To perform database restore from flash disk with TL1, go to step 52.

Perform Database Restore From Flash Disk with 1677 SONET Link EMA

2 From the menu bar of the AMC window, select Navigation>Show Alarms to report alarms.

3 Right-click on the Network Element domain or the System domain and select View Current Conditions.

4 Are there any disk or common module failures in the system?

If yes, refer to the Maintenance and Trouble Clearing manual (PN 3EM13853AD) for procedures to clear necessary alarms/conditions.If no, go to step 5.

Perform Database Restore from Flash Disk 4-491



5 Click Equipment domain to display current cards in system in the Result Pane.

6 Note the current Primary State and Secondary State of the four RDS drives (DISK-A9, DISK-A10, DISK-B9, DISK-B10)




9 Right-click on appropriate disk (A9 or A10) and select Activate Disk. The Activate Disk wizard appears.



12 Click Next.

13 Was Disk Mode selected Primary or Seconday?

If Primary, go to step 14.If Secondary, go to step 16.

14 On the Behavior page, select a value for the disk behavior from the drop-down menu (Import or Export).

15 Click Next.

16 On the finish page, verify chosen options.

17 Click Finish.




21 Note the current Primary State and Secondary State of DISK-A9 and DISK-A10.

Perform Database Restore from Flash Disk4-492





24 Right-click on DISK-A and select Properties>General. Note the current Primary State.



26 Do the members of RDS drive B (B9 and B10) showone with PST,SST of IS,WRK and one with PST,SST of IS,STBYH?



28 Right-click on appropriate disk (B9 or B10) and select Activate Disk. The Activate Disk wizard appears.



31 Click Next.

32 On the finish page, verify chosen options.

33 Click Finish.




37 Note the current Primary State and Secondary State of DISK-B9 and DISK-B10.






40 Right-click on DISK-B and select Properties>General. Note the current Primary State.



Restore Database

42 Restore the saved provisioning database from drive A. Right-click on the Network Element domain or the System domain and select System Configuration Operations>Activate. The Activate System Configuration wizard appears.


44 On the Configuration Directory page, specify the directory from which to restore the system configuration files. This directory should be a path relative to the /cfg directory.

45 Click Next.


47 Click Finish. Database restore from RDS drive A is complete.

48 Reset the node. Right-click on the Network Element domain or the System domain and select Initialize NE.

49 Click Yes.


51 Go to step 79.

Perform Database Restore From Flash Disk with TL1

52 Enter RTRV-ALM-ALL;

53 Observe output.



54 Enter RTRV-COND-ALL;

55 Observe output.

56 Are there any disk or common module failures in the system?

If yes, refer to the Maintenance and Trouble Clearing manual (PN 3EM13853AD) for procedures to clear necessary alarms/conditions.If no, go to step 57.


57 Enter RTRV-DISK;

58 Observe output.




Enter ACT-DISK::AID:::MODE=,ACTION=ACTIVATE,BEHAVIOR=;

where:AID=DISK-{A9, A10}MODE=PRI or SECBEHAVIOR=IMPORT or EXPORT (only if MODE=PRI)



63 Enter RTRV-DISK;

64 Observe output.










Enter ACT-DISK::AID:::MODE=,ACTION=ACTIVATE;

where:AID=DISK-{B9, B10}MODE=PRI or SEC



71 Enter RTRV-DISK;

72 Observe output.







Restore Database

75 Enter OPR-DISK:::::TYPE=CFG,ACTION=ACTIVATE,SRC=;

where:SRC=restore directory within A:/CFG that holds the backup files of the provisioning database.


77 Reset the node. Enter INIT-SYS:::::2;





DLP-208Administer T1 Test Access ConnectionsPURPOSE

This procedure provides the instructions to retrieve information on, connect, and disconnect Test Access (TACC) connections used to test T1 ports.

PREREQUISITES

A CONN-TACC-T1 command must be administered before a CHG-ACCMD-T1 command will be accepted.

The two ports of a test access port pair must reside in the same DS3. To provision a T1 test access port pair, the T3 in which the test access port pair is embedded must have been provisioned with STSMAP=VTFLOAT&VTCRS and FMT=CBIT or ASYNC.

A T1 test access port pair can only be provisioned in a stand-alone T3.

The maximum number of T1/VT1 test access port pairs supported in a system is 42.

GENERAL


The cross-connection to be tested may be a T1/T1, T1/VT1, or VT1/VT1 connection. The T1 or VT1 ports involved in the test access connection (test access port pair and equipment/facility port) must have been provisioned to use the same VT switch fabric.

When a T1 port is defined as a test access port (TACC=Y), the two ports identified by AID and TADB in the ENT-T1 command are both provisioned as a Test Access Port Pair (TAPP). When using ED-T1 to change the provisioning of a TAPP, either of the AIDs for TAD A or TAD B can be specified as the AID in the command and the provisioning changes are applied to both the TAD A and TAD B ports.

CONN-TACC-T1 connects a test access port to a specified T1 or VT1 port in the specified test access mode. The available test access modes for a test access port connection are MONE, MONEF, MONF, SPLTA, SPLTB, SPLTE, SPLTEF, SPLTF, LOOPE, or LOOPF.

CHG-ACCMD-T1 modifies the test access mode of T1 test access connections.


Administer T1 Test Access Connections 4-499



STEP PROCEDURE


where:AID=T1 or VT1 Access Identifier of TAP (TAD A or TAD B), equipment-side port being tested, or facility-side port being tested.TYPE=Type of test access connection (VT1)UID=(ALL, MYSELF)

2 Examine output.


3 Enter RTRV-T1::[AID]; to verify status of possible TAPs.


4 Examine output.


5 Select action.

To provision a T1 port as a TAP, go to step 6.To modify provisioning of a TAP, go to step 8.To create a test access connection, go to step 10.To change test access mode of TACC connection, go to step 12.To disconnect TACC connection, go to step 14.To end this procedure, go to step 16.

Administer T1 Test Access Connections4-500


Provision a T1 Port as a TAP

6 Enter ENT-T1::AID::::,TACC=Y,TADB=; to provision TAPP.

where:AID=T1 Access Identifier of TAD A port in TAPPTADB=T1 Access Identifier of TAD B port in TAPP (AID selected must be an available T1 port in the same T3. It will be provisioned with same parameters as AID.)

7 Go to step 5.

Modify TAP


8 Enter ED-T1::AID::::[CKTID=][,FMT=]:[PST],[SST];

where:AID=T1 Access Identifier (TAD A or TAD B)Other parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

9 Go to step 5.


CAUTION: Possibility of service interruption. CONN-TACC-T1 executed with a mode of LOOPE, LOOPF, SPLTA, SPLTB, SPLTE, SPLTEF, or SPLTF affects service and interrupts traffic.

10 Enter CONN-TACC-T1::AID:::TAP:MD:[AID1]:[LA];

where:AID=Identifies the equipment-side T1/VT1 port to be testedTAP=T1 Access Identifier of TAD A (first port in test access port pair)MD=Test access modeOther parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

11 Go to step 5.


CAUTION: Possibility of service interruption. CHG-ACCMD-T1 executed with a mode of LOOPE, LOOPF, SPLTA, SPLTB, SPLTE, SPLTEF, or SPLTF affects service and interrupts traffic.

Administer T1 Test Access Connections 4-501


12 Enter CHG-ACCMD-T1::AID:::MD;

where:AID=T1 Access Identifier of TAD A (first port in test access port pair)MD=Test access mode

13 Go to step 5.



where:AID=T1 Access Identifier of TAD A (first port in test access port pair)

15 Go to step 5.


Administer T1 Test Access Connections4-502


DLP-209Administer VT1 Test Access ConnectionsPURPOSE

This procedure provides the instructions to retrieve information on, connect, and disconnect Test Access (TACC) connections used to test T1 and VT1 ports.

PREREQUISITES

A CONN-TACC-VT1 command must be administered before a CHG-ACCMD-VT1 command will be accepted.

The two ports of a test access port pair must reside in the same STS-1. To provision a VT1.5 test access port pair, the STSMAP of the STS-1 in which the test access port pair is embedded must have been provisioned as VTFLOAT&VTCRS.


A VT1 test access port pair may be provisioned on a protected or an unprotected OC-n facility.

The maximum number of T1/VT1 test access port pairs supported in a system is 42.

GENERAL


The cross-connection to be tested may be a T1 to T1, T1 to VT1, or VT1 to VT1 connection. The T1 or VT1 ports involved in the test access connection (test access port pair and equipment/facility port) must have been provisioned to use the same VT switch fabric.

When a VT1 port is defined as a test access port (TACC=Y), the two ports identified by AID and TADB in the ENT-VT1 command are both provisioned as a Test Access Port Pair (TAPP). When using ED-VT1 to change the provisioning of a TAPP, either of the AIDs for TAD A or TAD B can be specified as the AID in the command and the provisioning changes are applied to both the TAD A and TAD B ports.

CONN-TACC-VT1 connects a test access port to a specified T1 or VT1 port in the specified test access mode. The available test access modes for a test access port connection are MONE, MONEF, MONF, SPLTA, SPLTB, SPLTE, SPLTEF, SPLTF, LOOPE, or LOOPF.

CHG-ACCMD-VT1 modifies the test access mode of VT1 test access connections.

Administer VT1 Test Access Connections 4-503




STEP PROCEDURE


where:AID=T1 or VT1 access identifier of TAP (TAD A or TAD B), equipment-side port being tested, or facility-side port being tested.TYPE=Type of test access connection (VT1)UID=(ALL, MYSELF)

2 Examine output.


3 Enter RTRV-VT1::[AID]; to verify status of possible TAPs.


4 Examine output.


5 Select action.

To provision a VT1 port as a TAP, go to step 6.To modify provisioning of a TAP, go to step 8.To create a test access connection, go to step 10.To change test access mode of TACC connection, go to step 12.To disconnect TACC connection, go to step 14.To end this procedure, go to step 16.

Administer VT1 Test Access Connections4-504


Provision a VT1 Port as a TAP

6 Enter ENT-VT1::AID::::,TACC=Y,TADB=; to provision TAPP.

where:AID=VT1 Access Identifier of TAD A port in TAPPTADB=VT1 Access Identifier of TAD B port in TAPP (AID selected must be an available VT1 port in the same STS1. It will be provisioned with same parameters as AID.)

7 Go to step 5.

Modify TAP


8 Enter ED-VT1::AID::::[CKTID=][,VTMAP=]:[PST],[SST];

where:AID=VT1 Access Identifier (TAD A or TAD B)Other parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

9 Go to step 5.


CAUTION: Possibility of service interruption. CONN-TACC-VT1 executed with a mode of LOOPE, LOOPF, SPLTA, SPLTB, SPLTE, SPLTEF, or SPLTF affects service and interrupts traffic.

10 Enter CONN-TACC-VT1::AID:::TAP:MD:[AID1]:[LA];

where:AID=Identifies the equipment-side T1/VT1 port to be testedTAP=VT1 Access Identifier of TAD A (first port in test access port pair)MD=Test access modeOther parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

11 Go to step 5.


CAUTION: Possibility of service interruption. CHG-ACCMD-VT1 executed with a mode of LOOPE, LOOPF, SPLTA, SPLTB, SPLTE, SPLTEF, or SPLTF affects service and interrupts traffic.

Administer VT1 Test Access Connections 4-505


12 Enter CHG-ACCMD-VT1::AID:::MD;

where:AID=VT1 Access Identifier of TAD A (first port in test access port pair)MD=Test access mode

13 Go to step 5.



where:AID=VT1 Access Identifier of TAD A (first port in test access port pair)

15 Go to step 5.


Administer VT1 Test Access Connections4-506


DLP-210Configure EMA and TL1DAT on PC for NEPURPOSE

This procedure provides the instructions to perform the following:





PREREQUISITES

The Personal Computer (PC) must meet hardware/software requirements (refer to table 210-A).

The user must have local administrative privileges on the PC.

The Microsoft®1 Loopback Adapter supplied with Windows®2 2000 must be installed.

A Windows® 2000 setup CD must be available for configuring the FTP Server.

GENERAL

The applications and log files software require approximately 500 MB of disk space.

For assistance with difficulties encountered during software installation, contact the Alcatel Customer Technical Assistance Center (CTAC). Refer to Introduction.

For parameter descriptions of TL1 commands used in this procedure, refer to the 1677 SONET Link Commands and Messages manual (PN 3EM13855ADAA) or the 1677 SONET Link Address and Location Guide (PN 3EM13854AB). The Software Reference Guide in the back of this manual may also be used as reference.

1. Microsoft is a registered trademark of Microsoft Corporation.2. Windows is a registered trademark of Microsoft Corporation.

Configure EMA and TL1DAT on PC for NE 4-507


STEP PROCEDURE

1 Use 1353 NM 1677 R05.00.00 EMA R01.00.00 software distribution kit (PN 3EM14320ABAA) to install 1677 SONET Link EMA software.

Configure EMA for NE

2 Verify that PC is properly set up to communicate with customer network (gateway, mask, and IP addresses are compatible), and PC is physically connected to customer LAN. Contact customer LAN administrator for assistance, if necessary.

3 On PC desktop, double-click 1677 NER05.00.00 icon to start 1677 SONET Link EMA.

4 In NES window menu bar, select NE Directory>Create TL/1 NE.

Table 210-A. PC RequirementsREQUIREMENTS RECOMMENDEDProcessor 1.5 GHz Intel®1 Pentium®2 4 processor or equivalent

[1] Intel is a registered trademark of Intel Corporation.[2] Pentium is a registered trademark of Intel Corporation.

RAM 512 MB minimum; 1GB recommendedGraphics Resolution supporting 64K colors with 16 MB RAM on

video card set to 1280x1024 pixelsMonitor 17” for desktops, 14” for laptopsFree hard disk space 10 GBLAN Card IEEE 802.3 LAN card (TCP/IP via 10baseT Ethernet)Serial Line Standard RS232-CMouse Two-button pointing device, such as a mouse or trackballCD-ROM Drive RequiredOperation System Microsoft® Windows 2000 (service pack 4) or

Microsoft® Windows XP Pro (Service Pack 1 or 2)HTML Browser Netscape®3 Communicator 4.79 or higher or

Microsoft® Internet Explorer 6

[3] Netscape is a registered trademark of Netscape Communications Corporation.

Configure EMA and TL1DAT on PC for NE4-508


5 In NE Settings dialog box, enter the required information in the text boxes:

a. TCP/IP Address: IP address of NE

b. TCP/IP Port: 3082

c. Type & Release: 1677 R05_00_00

d. User Label: User-assigned name of NE

e. Location: Physical or geographical location of NE

6 Click OK.

7 Select Maps>Save.

Install I/O Manual for TL1DAT

8 In NES window menu bar, select Application>ALCATEL TL1DAT.

9 In TL1 NE Connection Information dialog box, enter user UID in User Identifier (UID) field.

10 Enter user PID in Password Identifier (PID) field.

11 Enter system TID in Target Identifier (TID) field.

12 Select TCP/IP Connection.

13 Enter system hostname or IP address in Hostname or IP address field.

14 Enter 3082 in Port field.

15 Click OK. LogIn Status Window appears until login successfully completes, then TL1 Direct Access Terminal Application window opens.

16 In main menu, select File>Install NE...

17 In TL1DAT Administration dialog box, click Add Current.

18 Navigate to C:\ALCATEL\EMA1677R05.00.00\io-man\ subdirectory.

19 In file list select CM subdirectory.

20 Click Select.

Configure EMA and TL1DAT on PC for NE 4-509


21 In message box, click OK. Alcatel TL1DAT Enhanced Mode Window displays


Configure EMA and TL1DAT on PC for NE4-510


DLP-211Modify DS1 (T1) ParametersPURPOSE

This procedure provides the instructions to modify T1 provisioned parameter values.

GENERAL

The ED-T1 command is used to modify parameter values previously provisioned using the ENT-T1 command. RTRV-T1 can be used to view the parameters.


STEP PROCEDURE

1 Select action.

To modify DS1 parameters with 1677 SONET Link EMA, go to step 2.To modify DS1 parameters with TL1, go to step 40.

Modify DS1 Parameters with 1677 SONET Link EMA


3 Select action.

If T1 is embedded in an electrical T3, go to step 4.If T1 is embedded in an OC-n/STS-1/T3, go to step 8.If T1 is embedded in an OC-n/STS-1/VT1, go to step 14.If T1 is embedded in an EC1/STS-1/T3, go to step 20.If T1 is embedded in an EC1/STS-1/VT1, go to step 26.

Modify T1 Embedded in an Electrical T3



6 Select the appropriate T3 to display T1 facilities.

7 Go to step 32.

Modify DS1 (T1) Parameters 4-511


Modify T1 Embedded in an OC-n/STS-1/T3



10 Expand the appropriate OC-n facility to display STS-1 facilities.

11 Expand the appropriate STS-1 facility to display the T3 facility.

12 Select the T3 facility to display T1 facilities.

13 Go to step 32.

Modify T1 Embedded in an OC-n/STS-1/VT1

14 Expand the OC-n domain.


16 Expand the appropriate OC-n facility to display STS-1 facilities.

17 Expand the appropriate STS-1 facility to display VT1 facilities.

18 Select appropriate VT1 facility to display the T1 facility.

19 Go to step 32.

Modify T1 Embedded in an EC1/STS-1/T3



22 Expand the appropriate EC1 facility to display the STS-1 facility.

23 Expand the STS-1 facility to display the T3 facility.

24 Select the T3 facility to display T1 facilities.

25 Go to step 32.

Modify T1 Embedded in an EC1/STS-1/VT1



Modify DS1 (T1) Parameters4-512


28 Expand the appropriate EC1 facility to display the STS-1 facility.

29 Expand the STS-1 facility to display VT1 facilities.

30 Select VT1 facility to display the T1 facility.

31 Go to step 32.

Modify T1 Provisioning

32 Right-click on T1 facility and select Properties>General. A mutable table appears containing current parameter values.

33 Double click in cell of parameter value to modify.

34 Select new value from drop-down list or type new value into cell, as appropriate.

35 Repeat steps 33 and 34 to modify additional parameter values.

36 CAUTION: Possibility of service interruption. Editing port parameters of a traffic bearing port can adversely affect service.

37 Click Apply.

38 Click Close.

39 Go to step 44.

Modify DS1 Parameters with TL1



41 Examine output for current provisioning information on port.




43 Enter ED-T1::AID::::[CKTID=][,FMT=]:[PST],[SST];





DLP-212Modify DS3 (T3) ParametersPURPOSE

This procedure provides the instructions to modify T3 provisioned parameter values.

GENERAL

The ED-T3 command is used to modify parameter values previously provisioned using the ENT-T3 command. RTRV-T3 can be used to view the parameters.

Refer to table 212-A for valid provisioning combinations.


STEP PROCEDURE

1 Select action.

To modify DS3 parameters with 1677 SONET Link EMA, go to step 2.To modify DS3 parameters with TL1, go to step 25.

Modify DS3 Parameters with 1677 SONET Link EMA


Table 212-A. Valid T3 Provisioning CombinationsAID FMT STSMAP FEAC LBOStandalone T3 on ECC module


VTFLOAT,VTFLOAT&VTCRSY,N 1,2


N 1,2

Standalone T3 on DS3 card


VTFLOAT,VTFLOAT&VTCRSN 1,2


N 1,2

T3 embedded in STS1 CBIT,ASYNC ASYNC&SUBPM, VTFLOAT,VTFLOAT&VTCRS

N NA



3 Select action.

If T3 is electrical T3, go to step 4.If T3 is embedded in an OC-n, go to step 7.If T3 is embedded in an EC1, go to step 12.

Modify Electrical T3


5 Select the appropriate T3 group to display T3 facilities.

6 Go to step 17.

Modify T3 Embedded in an OC-n





11 Go to step 17.

Modify T3 Embedded in an EC1





16 Go to step 17.

Modify T3 Provisioning








22 Click Apply.

23 Click Close.

24 Go to step 29.

Modify DS3 Parameters with TL1





28 Enter ED-T3::AID::::[CKTID=][,LBO=][,FMT=][,FEAC=]:[PST],[SST];





DLP-213Modify EC1 ParametersPURPOSE

This procedure provides the instructions to modify EC1 provisioned parameter values.

GENERAL

The ED-EC1 command is used to modify parameter values previously provisioned using the ENT-EC1 command. RTRV-EC1 can be used to view the parameters.


STEP PROCEDURE

1 Select action.

To modify EC1 parameters with 1677 SONET Link EMA, go to step 2.To modify EC1 parameters with TL1, go to step 13.

Modify EC1 Parameters with 1677 SONET Link EMA



4 Select the appropriate EC1 group.

5 Right-click on the appropriate EC1 and select Properties>General. A mutable table appears containing current parameter values.



8 Repeat steps 6 and 7 to modify additional parameter values as needed.


10 Click Apply.

Modify EC1 Parameters 4-519


11 Click Close.

12 Go to step 17.

Modify EC1 Parameters





16 Enter ED-EC1::AID::::[CKTID=][,TRC=][,LBO=]:[PST],[SST];

where:AID=EC1 Access IdentifierOther parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.


Modify EC1 Parameters4-520


DLP-214Modify GIGE ParametersPURPOSE

This procedure provides the instructions to modify GIGE provisioned parameter values.

GENERAL

The ED-GIGE command is used to modify parameter values previously provisioned using the ENT-GIGE command however, a GIGE object entity cannot be edited from Simplex mode of operation to Duplex or vice-versa. It must be deleted using DLT-GIGE and then re-entered using ENT-GIGE with the change. RTRV-GIGE can be used to view the parameters.

For parameter descriptions of TL1 commands used in this procedure, refer to the 1677 SONET Link Commands and Messages manual (PN 3AL12345AA) or the 1677 SONET Link Address and Location Guide (PN 3EM13854AB). The Software Reference Guide in the back of this manual may also be used as reference.

STEP PROCEDURE

1 Select action.

To modify GIGE parameters with 1677 SONET Link EMA, go to step 2.To modify GIGE parameters with TL1, go to step 13.

Modify GIGE Parameters with 1677 SONET Link EMA



4 Select the appropriate GIGE group.

5 Right-click on the appropriate GIGE and select Properties>General. A mutable table appears containing current parameter values.



8 Repeat steps 6 and 7 to modify additional parameter values as needed.


Modify GIGE Parameters 4-521


10 Click Apply.

11 Click Close.

12 Go to step 17.

Modify GIGE Parameters with TL1

13 Enter RTRV-GIGE::[AID];




16 Enter ED-GIGE::AID::::[CKTID=][,MAP=][,ECHECK=][,JUMBO=][,NEGOTN=][,IPG=]:[PST];

where:AID=GIGE Access IdentifierOther parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.


Modify GIGE Parameters4-522


DLP-215Modify OC-n ParametersPURPOSE

This procedure provides the instructions to modify OC-n provisioned parameter values.

GENERAL

The ED-OCn command is used to modify parameter values previously provisioned using the ENT-OCn command (where OCn=OC3, OC12, OC48, or OC192). RTRV-OCn can be used to view the parameters.

For parameter descriptions of TL1 commands used in this procedure, refer to the 1677 SONET Link Commands and Messages manual (PN 3AL12345AA) or the 1677 SONET Link Address and Location Guide (PN 3EM13854AB). The Software Reference Guide in the back of this manual may also be used as reference.

STEP PROCEDURE

1 Select action.

To modify OC-n parameters with 1677 SONET Link EMA, go to step 2.To modify OC-n parameters with TL1, go to step 13.

Modify OC-n Parameters with 1677 SONET Link EMA



4 Select the appropriate OC-n group.

5 Right-click on the appropriate OC-n facility and select Properties>General. A mutable table appears containing current parameter values.





10 Click Apply.

Modify OC-n Parameters 4-523


11 Click Close.

12 Go to step 24.

Modify OC-n Parameters with TL1


where:OCn=OC3, OC12, OC48, OC192AID=OC-n Access Identifier



16 Select action.

To edit OC-3 facility, go to step 17.To edit OC-12 facility, go to step 19.To edit OC-48 facility, go to step 21.To edit OC-192 facility, go to step 23.

17 Enter ED-OC3::AID::::[CKTID=][,SDTHRESH=][,SFTHRESH=][,TRC=][,ALSENB=]:[PST][,SST];

where:AID=OC-3 Access IdentifierOther parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

18 Go to step 24.

19 Enter ED-OC12::AID::::[CKTID=][,SDTHRESH=][,SFTHRESH=][,TRC=][,ALSENB=]:[PST][,SST];


20 Go to step 24.

Modify OC-n Parameters4-524


21 Enter ED-OC48::AID::::[CKTID=][,SDTHRESH=][,SFTHRESH=][,TRC=][,ALSENB=][,OPRNOM=][,TXPWR=]:[PST][,SST];


22 Go to step 24.

23 Enter ED-OC192::AID::::[CKTID=][,SDTHRESH=][,SFTHRESH=][,TRC=][,FECDW=][,FECSCRAMBLE=][,ALSENB=][,OPRNOM=][,TXPWR=]:[PST][,SST];



Modify OC-n Parameters 4-525


Modify OC-n Parameters4-526


DLP-216Modify OFA ParametersPURPOSE

This procedure provides the instructions to modify OFA provisioned parameter values.

GENERAL

The ED-OFA command is used to modify parameter values previously provisioned using the ENT-OFA command. RTRV-OFA can be used to view the parameters.


STEP PROCEDURE

1 Select action.

To modify OFA parameters with 1677 SONET Link EMA, go to step 2.To modify OFA parameters with TL1, go to step 13.

Modify OFA Parameters with 1677 SONET Link EMA



4 Select the appropriate OFA group.

5 Right-click on the appropriate OFA facility and select Properties>General. A mutable table appears containing current parameter values.





10 Click Apply.

Modify OFA Parameters 4-527


11 Click Close.

12 Go to step 17.

Modify OFA Parameters with TL1





16 Enter ED-OFA::AID::::[OPRNOM=][,OPTNOM=]:[PST];

where:AID=OFA Access IdentifierOther parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.


Modify OFA Parameters4-528


DLP-217Modify STS-n ParametersPURPOSE

This procedure provides the instructions to modify STS-n provisioned parameter values.

GENERAL

The ED-STSn command is used to modify parameter values previously provisioned using the ENT-STSn command. RTRV-STSn can be used to view the parameters.

The STSMAP parameter indicates the type of payload in the STS payload envelope. Refer to table 217-A. In addition, it includes two flags that allocate the necessary TMUX/VSC resources to support subrate performance monitoring and cross-connection functions. The following subrate flags are supported:

• SUBPM: This flag indicates that this facility will be supporting embedded T1, VT1, and/or T3 performance monitoring. TMUX resources will be allocated. The user must provision the T1, VT1, T3 facility for performance monitoring to be enabled.

• VTCRS: This flag indicates that this facility will be used to cross-connect an embedded VT1 with a T1 facility. VSC resources will be allocated. Note that VT level connections can only be made to STS1s using the same VSC module.

The STSMAP value can not be changed or set to a value that uses TMUX/VSC resources with the ED-STS1 command. To change the VTCARD or TMUX parameters after an STS-1 has been provisioned, use the DLT-STS1 command to delete the STS-1 facility and then use the ENT-STS1 command to re-enter the facility with the new VTCARD and TMUX parameters. The STSMAP value can be changed under the following circumstances:

• If the port is not connected and current STSMAP is set to {ALL, ASYNC, VTFLOAT, HDLC, GFP, 10GIGE, IP-PPP, ATM}, the STSMAP value can be changed to any value within this set.

• If the port is T3 connected, the STSMAP value can be changed to {ALL, ASYNC}.

• If the port is STS1 connected, the STSMAP value can be changed to {ALL, ASYNC, VTFLOAT, HDLC, GFP, IP-PPP, ATM}.

• If the port is GIGE connected, the STSMAP value can be changed to {ALL, GFP}.

Modify STS-n Parameters 4-529



STEP PROCEDURE

1 Select action.

To modify STS-n parameters with 1677 SONET Link EMA, go to step 2.To modify STS-n parameters with TL1, go to step 20.

Modify STS-n Parameters with 1677 SONET Link EMA


3 Select action.

If STS-1 is embedded in an OC-n, go to step 4.If STS-1 is embedded in an EC1, go to step 8.

Modify STS-n Embedded in an OC-n


Table 217-A. STSMAP Parameter Values for STS-1 ProvisioningSTSMAP Possible Sub-entity TMUX/VSC ResourcesALL None NoneASYNC None NoneASYNC&SUBPM T3, T1 TMUXASYNC&VTFLOAT T3, T1 TMUXASYNC&VTFLOAT&VTCRS T3, T1 TMUX/VSCATMGFP10GIGEHDLCIP-PPPVTFLOAT None VSCVTFLOAT&SUBPM VT1, T1 TMUXVTFLOAT&VTCRS VT1 VSCVTFLOAT&VTCRS&SUBPM VT1, T1 VSC/TMUX

Modify STS-n Parameters4-530



6 Select the appropriate OC-n port to display STS-1 facilities.

7 Go to step 12.

Modify STS-n Embedded in an EC1



10 Select the appropriate EC1 facility to display STS-1 facilities.

11 Go to step 12.

Modify STS-n Provisioning

12 Right-click on the appropriate STS-1 facility and select Properties>General. A mutable table appears containing current parameter values.





17 Click Apply.

18 Click Close.

19 Go to step 27.

Modify STS-n Parameters with TL1


where:AID=STSn Access Identifier



Modify STS-n Parameters 4-531


23 Select action.

To edit STS-1 facility, go to step 24.To edit STS-n facility, go to step 26.

24 Enter ED-STS1::AID::::[CKTID=][,STSMAP=][,TRC=][,EXPTRC=][,ENBTXPDIP=][,ENBTXRDIP=][,ENBTIMP=][,ENBPDIP=][,SDTH=][,SFTH=]:[PST],[SST];


25 Go to step 27.

26 Enter ED-STSn::AID::::[CKTID=][,STSMAP=][,EXPTRC=][,ENBTIMP=][,SDTH=][,SFTH=]:[PST],[SST];

where:STSn=Signal type (STS3C, STS12C, or STS48C)AID=STSn Access IdentifierOther parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.


Modify STS-n Parameters4-532


DLP-218Modify VT1.5 ParametersPURPOSE

This procedure provides the instructions to modify VT1.5 provisioned parameter values.

GENERAL

The ED-VT1 command is used to modify parameter values previously provisioned using the ENT-VT1 command. RTRV-VT1 can be used to view the parameters.


STEP PROCEDURE

1 Select action.

To modify VT1.5 parameters with 1677 SONET Link EMA, go to step 2.To modify VT1.5 parameters with TL1, go to step 23.

Modify VT1.5 Parameters with 1677 SONET Link EMA

2 Select action.

To modify VT1.5 embedded in an OC-n, go to step 3.To modify VT1.5 embedded in an EC1, go to step 9.

Modify VT1.5 Embedded in OC-n






8 Go to step 15.

Modify VT1.5 Parameters 4-533


Modify VT1.5 Embedded in EC1





13 Selectn the appropriate STS-1 facility to display VT1 facilities.

14 Go to step 15.

Modify VT1 Provisioning

15 Right-click on VT1 facility and select Properties>General. A mutable table appears containing current parameter values.





20 Click Apply.

21 Click Close.

22 Go to step 27.

Modify VT1.5 Parameters with TL1

23 Enter RTRV-VT1::[AID];

where:AID=VT1.5 Access Identifier



Modify VT1.5 Parameters4-534


26 Enter ED-VT1::AID::::[CKTID=][,VTMAP=]:[PST],[SST];

where:AID=VT1.5 Access IdentifierOther parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.


Modify VT1.5 Parameters 4-535


Modify VT1.5 Parameters4-536


DLP-219Administer Far-End Alarm and Control (FEAC)PURPOSE

This procedure provides the instructions to create and modify a DS3 facility to support a Far-End Alarm and Control (FEAC) channel.

PREREQUISITES

The card supporting the DS3 facility must be provisioned before any DS3 facilities can be provisioned. Refer to DLP-112 to provision equipment.

This procedure is used to provision a DS3 facility to support a FEAC channel. Refer to DLP-115 for the procedure to provision other parameters of a DS3 facility.

This procedure is used to modify a DS3 port to enable or disable FEAC channel support. Refer to DLP-212 for the procedure to modify other parameters of a DS3 port.

GENERAL

The system provides a FEAC signaling channel for C-bit parity applications. This channel is used as a communications channel between the far end DS3 terminal and the near end DS3 terminal. It is used to send alarm and status information and loopback commands to activate and deactivate DS3 and DS1 loopbacks at the distant terminal.

Enabling and disabling the FEAC channel is performed on a per DS3 basis. The ENT-T3 and ED-T3 commands are used to enable/disable the FEAC channel. FEAC is supported on standalone T3s only.

The ENT-T3 command is used to provision T3 facilities. The ED-T3 command is used to modify parameter values previously provisioned using the ENT-T3 command. RTRV-T3 can be used to view the parameters.


STEP PROCEDURE

1 Select action.

To administer FEAC with 1677 SONET Link EMA, go to step 2.To administer FEAC with TL1, go to step 27.

Administer Far-End Alarm and Control (FEAC) 4-537


Administer FEAC with 1677 SONET Link EMA

2 Select action.

To provision a DS3 port to support a FEAC channel, go to step 3.To modify a DS3 port to enable/disable a FEAC channel, go to step 16.

Provision DS3 Port to Support FEAC Channel



5 Right-click appropriate T3 group and select Create. The Provision T3 Facility wizard appears.


7 Select appropriate parameter values on first few pages in the wizard until Framing Format page appears.

8 On the Framing Format page, select C-bit parity.

9 Click Next.

10 On the Far-End Alarm & Control page, select Enable from the drop-down list.

11 Click Next.



14 Click Finish.

15 Go to step 40.

Modify a DS3 Port to Enable/Disable FEAC Channel



18 Select the appropriate T3 group to display T3 facilities.


Administer Far-End Alarm and Control (FEAC)4-538


20 Double click in cell labeled Enable Responses to FEAC.

21 Is FEAC to be enabled or disabled?

If enabled, select Enable from drop-down list. Go to step 22.If disabled, select Disable from drop-down list. Go to step 24.

22 Double click in cell labeled Framing Format.

23 Select C-bit parity from drop-down list.

24 Click Apply.

25 Click Close.

26 Go to step 40.

Administer FEAC with TL1

27 Select action.

To provision a DS3 facility to support a FEAC channel, go to step 28.To modify a DS3 facility to enable a FEAC channel, go to step 33.To modify a DS3 facility to disable a FEAC channel, go to step 37.

Provision DS3 Facility to Support FEAC Channel



29 Examine output for provisioning information on facility. Ensure that facility is in valid state for provisioning (OOS-MA,UAS).

30 Does facility have PST and SST of OOS-MA,UAS?

If yes, go to step 31.If no, the ENT-T3 command cannot be performed on the specified T3 facility. Go to step 40.

Administer Far-End Alarm and Control (FEAC) 4-539


31 Enter ENT-T3::AID::::[CKTID=][,LBO=],FMT=CBIT[,STSMAP=][,VTCARD=][,TMUX=][,TACC=][,TADB=],FEAC=Y:[PST],[SST];


32 Go to step 40.

Modify a DS3 Facility to Enable FEAC Channel



34 Examine output for current provisioning information on facility.

35 Enter ED-T3::AID::::,FMT=CBIT,FEAC=Y;


36 Go to step 40.

Modify a DS3 Facility to Disable FEAC Channel



38 Examine output for current provisioning information on facility.

39 Enter ED-T3::AID::::,FEAC=N;



Administer Far-End Alarm and Control (FEAC)4-540


DLP-220Retrieve TL1 Commands Available for User LevelPURPOSE

This procedure provides the instructions to retrieve TL1 commands a user with a specified User Access Privilege (UAP) can execute, the Command Access Privilege (CAP) security level for the specified command or all commands, or all the commands that a user can execute.

GENERAL

The RTRV-PRVG-CMD is used to retrieve the CAP security level for a certain command or the commands that a user with a certain UAP can execute.


STEP PROCEDURE

1 Select action.

To retrieve commands available for user level with 1677 SONET Link EMA, go to step 2.To retrieve commands available for user level with TL1, go to step 18.

Retrieve Commands Available for User Level with 1677 SONET Link EMA

2 Select action.

To retrieve CAP security level for specific command, go to step 3.To retrieve commands available for UAP, go to step 8.To retrieve all commands a user can execute, go to step 13.

Retrieve CAP Security Level for Specific Command



5 Right-click on the TL1 Commands domain and select Refresh.

6 Find specific command in Result Pane and observe value for Command Access Privilege.

7 Go to step 29.

Retrieve TL1 Commands Available for User Level 4-541


Retrieve Commands Available for UAP




11 Click the Command Access Privilege box to sort CAPs.

12 Go to step 29.

Retrieve All Commands a User Can Execute




16 Observe commands in Result Pane.

17 Go to step 29.

Retrieve Commands Available for User Level with TL1

18 Select action.

To retrieve CAP security level for specific command, go to step 19.To retrieve commands available for UAP, go to step 23.To retrieve all commands a user can execute, go to step 26.

Retrieve CAP Security Level for Specific Command

19 Enter RTRV-PRVG-CMD:::::[CMD];

20 where:CMD=TL1 command code

21 Examine output.

22 Go to step 29.

Retrieve TL1 Commands Available for User Level4-542


Retrieve Commands Available for UAP

23 Enter RTRV-PRVG-CMD:::::[,CAP];

where:CAP=Command Access Privilege (READ, TEST, PROV, CONF, NETADMIN, SEC)

24 Examine output.

25 Go to step 29.

Retrieve All Commands a User Can Execute

26 Enter RTRV-PRVG-CMD;

27 Examine output. Output lists all commands (and associated CAPs) a user can execute.

28 Go to step 18.


Retrieve TL1 Commands Available for User Level 4-543


Retrieve TL1 Commands Available for User Level4-544


DLP-221Enable/Disable Database Change Autonomous MessagesPURPOSE

This procedure provides the instructions to enable/disable the REPT^DBCHG autonomous messages.

GENERAL

The REPT^DBCHG autonomous message immediately reports any database change that occurs as a result of a command to change equipment provisioning or configuration. Actions that trigger this message include RMV-, RST-, ENT-, ED-, and DLT- commands, as well as plug and unplug events.

The INH-DBCHGMSG-ALL command is used to disable REPT^DBCHG autonomous message reporting. The ALW-DBCHGMSG-ALL command is used to enable REPT^DBCHG autonomous message reporting.


STEP PROCEDURE

1 Select action.

To enable REPT^DBCHG messages, go to step 2.To disable REPT^DBCHG messages, go to step 4.

Enable REPT^DBCHG Messages

2 Enter ALW-DBCHGMSG-ALL;

3 Go to step 5.

Disable REPT^DBCHG Messages

4 Enter INH-DBCHGMSG-ALL;


Enable/Disable Database Change Autonomous Messages 4-545


Enable/Disable Database Change Autonomous Messages4-546


DLP-222Connect 1677 SONET Link to FES301PURPOSE

This procedure provides instructions to connect a FES301 to the 1677 SONET Link.

PREREQUISITE

The 1677 SONET Link and the FES301 systems should be installed and turned up before performing this procedure. Refer to the 1677 SONET Link Installation Practices manual (PN 3EM13849AD) and Turn-Up manual (PN 3EM13850AB). Also refer to the FES301 Installation and Turn-Up manual (PN 3EM15188AA).

GENERAL

This procedure is performed using TL1 command entry on the 1677 SONET Link and the menu screens on the FES301.

This procedure does not provide a method to make a direct communications connection between the 1677 SONET Link and the FES301. The two NEs are managed separately, with communications through the 1353 NM. Communications with the 1353 NM should be set up after the connection between the 1677 SONET Link and the FES301 is made. For information on configuring the EMA and TL1DAT on a PC for the 1677 SONET Link, refer to DLP-210. For information on configuring TL1DAT on a PC for the FES301, refer to the Installation Guide for FES301 R03.01 CLEM R01.00.01 (PN 3EM17918AAABRJZZA).

Refer to the 1677 SONET Link Commands and Messages manual (PN 3EM13852AD) for more information on the TL1 commands used in this procedure.

STEP PROCEDURE

DETERMINE FES301 SOFTWARE RELEASE

Determine SCM Software Revision (FES301)

1 From Main Menu, select option 1 (System Controller) and press Return.

2 Select option 1 (Configuration) and press Return.

3 Note the Unit Name (module).

4 Note the module part number.

5 Note the module CLEI code.

6 Note the module Software Revision. (It is listed as the seventh item on the page.)

Connect 1677 SONET Link to FES301 4-547


7 Is SCM unit name, part number, CLEI code, and Software Revision listed in table 222-A?


8 Press Esc until the Main Menu is displayed.

Determine OMM3IR Software Revision (FES301)

9 From Main Menu, select option 2 (HS1) and press Return.





14 Note the module Software Revision. (It is listed as the sixth item on the page.)

15 Is OMM3IR unit name, part number, CLEI code, and Software Revision listed in table 222-A?



17 From Main Menu, select option 3 (HS2) and press Return.



Table 222-A. FES301 Module Software Revision and Software Release

UNIT NAME (MODULE) PART NUMBER CLEI CODE

MODULE SOFTWARE REVISION

SOFTWARE RELEASE

SCM 3EM15001AB WMUCASRBAA C10 R03.01.03OMM3IR 3EM15004AB WMOMA0UHAA C02.10 R03.01.03DS1VM 3EM15018AB WMUIAARCAA B02.04 R03.01.03DS1VME 3EM18712AA WMOTB19EAA A002 R03.01.03

Connect 1677 SONET Link to FES3014-548


20 Is OMM3IR unit name, part number, CLEI code, and Software Revision listed in table 222-A?



Determine DS1VM/DS1VME Software Revision (FES301)

22 From Main Menu, select option 4 (MS Modules) and press Return.

23 Select option 3 (MS3) and press Return.






29 Is DS1VM/DS1VME unit name, part number, CLEI code, and Software Revision listed in table 222-A?



31 Repeat steps 22 through 30 for all DS1VM/DS1VME modules.

ROUTE FIBER-OPTIC CABLES BETWEEN 1677 SONET LINK AND FES301

32 Using a fiber-optic cable, connect one end of cable to Rx connector on appropriate working OC-3 module on 1677 SONET Link, and connect other end of cable to Tx connector on HS1 module on FES301.

33 Using a fiber-optic cable, connect one end of cable to Rx connector on HS1 module on FES301, and connect other end of cable to Tx connector on appropriate working OC-3 module on 1677 SONET Link.

34 Using a fiber-optic cable, connect one end of cable to Rx connector on appropriate protect OC-3 module on 1677 SONET Link, and connect other end of cable to Tx connector on HS2 module on FES301.



35 Using a fiber-optic cable, connect one end of cable to Rx connector on HS2 module on FES301, and connect other end of cable to Tx connector on appropriate protect OC-3 module on 1677 SONET Link.

Provision 1677 SONET Link

36 Enter ENT-EQPT::AID:::OC3-12P; to provision working OC-3 module.

where: AID=OC-3 module AID

37 Repeat step 36 to provision protect OC-3 module, then go to step 38.

38 Enter ENT-OC3::AID; to provision working OC-3 line facility.

where: AID=OC-3 facility AID

39 Repeat step 38 to provision protect OC-3 line facility, then go to step 40.

40 Enter ENT-NETIF::AID::::SECTIONLL=LAPD,SECTIONUL=CLNP; to enter section DCC for working OC-3 line facility.


41 Enter ED-LLSDCC::AID::::L2SIDE=NETWORK; to provision working DCC to be network interface.


42 Repeat step 40 to enter section DCC for protect OC-3 line facility, then go to step .43.

43 Repeat step 41 to provision protect DCC to be network interface, then go to step 44.

44 Enter ENT-FFP-OC3::PROTECTED_ID,PROTECTING_ID::::PTYPE=LINEAR; to provision OC-3 1+1 protection group.

where:PROTECTED_ID=working OC-3 in 1+1 FFP groupPROTECTING_ID=protecting OC-3 in 1+1 FFP group

45 Enter ED-NE-TL1::::::GWENB=Y; to enable 1677 SONET Link TL1 gateway.



46 Enter path facilities. Refer to the following Non-trouble Procedures:

– NTP-100: DS3 (T3) provisioning

– NTP-101: DS1 (T1) provisioning

– NTP-103: STS-n provisioning

– NTP-104: VT1.5 provisioning

47 Enter cross-connections. Refer to DLP-177 for T1 cross-connections. Refer to DLP-126 for VT1 cross-connections.

PROVISION FES301

48 From Main Menu, select option 2 (HS1 - OMM3) and press Return to start to provision working OC-3 equipment.

49 Select option 2 (Provisioning) and press Return.

50 Select option 1 (Service States) and press Return.

51 Select option 3 (Equipment) and press Return.

52 Select option 1 (IS) and press Return to provision OMM3 In Service.

53 Press Esc key three times to return to Main Menu.

54 From Main Menu, select option 3 (HS2 - OMM3) and press Return to start to provision protect OC-3 equipment.

55 Repeat steps 49 through 52 to provision protect OMM3 In Service.


Provision OC-3 Line Facilities

57 From Main Menu, select option 2 (HS1 - OMM3) and press Return.


59 Select option 1 (Service States) and press Return.

60 Select option 4 (Facility) and press Return.

61 Select option 1 (IS) and press Return to provision OC-3 facility In Service.





64 Repeat steps 58 through 61 to provision protect OC-3 facility In Service.


Provision Clock Source



68 Select option 5 (Clocks) and press Return.

69 Select option 1 (Clock Source) and press Return.

70 Select option 1 (Receive Fiber) and press Return.


Provision Target Identifier (TID)

72 Select option 1 (System Controller) and press Return.


74 Select option 5 (TL1) and press Return.

75 Select option 2 (Target ID [TID]) and press Return.

76 Enter a valid Target ID and press Return.


Provision Mid Speed Modules


79 From list, select module in slot MS3 and press Return.


81 Select option 1 (Equipment Primary State) and press Return.

82 Select option 1 (IS) and press Return to provision equipment In Service.




84 Repeat steps 78 through 83 to provision remaining working and protect modules in slots MS4, MS7, MS8, MS9, and MS10.

Provision T1 Facilities


86 Select option 3 (first DS1VM/DS1VME module in slot MS3) and press Return.


88 Is DS1VM or DS1VME equipped in MS slot?

If DS1VM, go to step 89.If DS1VME, go to step 91.

89 Select option 3 (Facility Provisioning) and press Return.

90 Go to step 92.

91 Select option 4 (Facility Provisioning) and press Return.

92 Select option 1 (Facility Primary State) and press Return.

93 Select option 30 and press Return to provision multiple T1 facilities.

94 Enter 1-28 and press Return. When working facilities are entered, associated protect facilities are automatically provisioned if protect module is provisioned.

95 Select option 1 (IS) and press Return to provision facilities In Service.

96 Press Esc key until Main Menu is shown.

97 Repeat steps 85 through 96 to provision remaining T1 facilities on remaining modules in slots MS7 and MS9.

Provision VT Mapping


99 Select option 3 (First DS1 Card) and press Return.


101 Select option 8 (Mapping) and press Return.

102 Select option 2 (M13) and press Return.




104 Repeat steps 98 through 103 for all Mid Speed modules.

Provision Cross-Connections

105 From Main Menu, select option 2 (HS 1) and press Return to select working OMM3.


107 Select option 2 (STS-1 Mapping) and press Return.

108 From list, select STS-1 that must be cross-connected and press Return.

109 From list, select slot of Mid Speed module to which STS-1 will be cross-connected, then press Return. Refer to table 222-B.

110 Select port and press Return.

111 Select Y and press Return at prompt to copy cross-connection provisioning information to protect module.


113 Repeat steps 105 through 112 for all time slots.

TEST FES301

114 Refer to the FES301 Installation and Turn-Up manual (PN 3EM15188AA), Appendix F, to test the FES301.

VERIFY FIBER-OPTIC CABLE ROUTING BETWEEN 1677 SONET LINK AND FES301

115 At FES301 OMM3 module, disconnect fiber-optic cable from TX port.

116 Is LOS declared on 1677 SONET Link LC2 10x port corresponding to disconnected OMM3 TX port?


Table 222-B. STS-1 to Mid Speed Slot MappingSTS-1 Mid Speed Slot1 MS32 MS73 MS9



117 Check fiber-optic cable routing between OMM3 and LC2 10x to verify that fiber-optic cable is connected to correct modules.

118 Go to step 115 to restest fiber-optic cable routing.

119 Repeat steps 115 and 116 for each fiber routed between each OMM3s in FES301 and LC2 10xs in 1677 SONET Link.

DAISY CHAIN MULTIPLE FES301s

120 Is more than one FES301 connected to 1677 SONET Link?


121 Refer to FES301 R03.01.03 Intersystem Communication Guide (PN 3EM18665ABAARJZZA) to establish a communication daisy chain between all FES301s connected to 1677 SONET Link.

122 From FES301 Main Menu, select option 6 (Auxiliary Shelf Access) and press Return.

123 Verify that all expansion shelves are shown in menu. An “e” is listed in the Chassis Location column for each expansion shelf.

124 Are all expansion shelves shown in menu?


125 Refer to FES301 R03.01.03 Intersystem Communication Guide (PN 3EM18665ABAARJZZA) to verify that communication daisy chain was set up correctly.

126 Go to step 122.

ADD FES301 TO 1353 NM

127 Add each FES301 element to the 1353 NM. Refer to the 1353 NM User Guide (PN 3EM17256AB).

DEFINE OC-3 LINK BETWEEN 1677 SONET LINK AND FES301

128 Use the 1677 SONET Link EMA to define an OC-3 link between the 1677 SONET Link and an FES301. Refer to the 1353 NM User Guide (PN 3EM17256AB).

129 Go to step 131.



130 Contact next level of technical support for assistance.




DLP-223Build DCC Network LinksPURPOSE

This procedure is used to link multiple NEs after all NEs in the ring are powered, tested, and configured.

GENERAL

For information on TL1 command syntax, refer to the 1677 SONET Link Commands and Messages manual (PN 3EM13852AD).

STEP PROCEDURE

1 Enter ENT-OCn::AID; to provision OC facility.

where:OCn=OC3, OC12, OC48, or OC192AID=OCn facility AID

2 Enter ENT-NETIF::AID:::LINELL=LAPD,LINEUL=CLNP; to create network interface.

where: AID=OCn facility AID

3 Enter RTRV-LLLDCC::AID; to retrieve lower layer DCC.

where: AID=OCn facility AID

4 Examine output for L2SIDE value. Current value must be opposite value set on far-end node. Values for L2SIDE are USER or NETWORK.

ALCATEL-1677SL 2005-04-30 15:27:34M 0 COMPLD "OC48-1-A-1:L2IF=7,L2INFO=512,MAXCALLS=0,L2NOA=200,L2RCALLTMR=10 L2REX=2,L2SIDE=NETWORK,L2WAIT=20";

5 Enter ED-LLLDCC::AID:::L2SIDE=USER;

Changing L2SIDE with a new value disables DCC and restores it with a new value. Provisioning working ID in a 1+1 APS environment automatically copies parameters to protect ID.

Build DCC Network Links 4-557


6 Create a telnet session to remote node.

In hyper terminal screen, enter telnet <IP_address> 3083.

7 Press Enter.

8 Enter ACT-USER::UID:::PID;

where:UID=User IdentifierPID=Personal Identifier (password). Both values are case-sensitive. The password echoes as asterisks.

9 Enter ENT-NETIF:::LINELL=LAPD,LINEUL=CLNP; to create network notification on remote node.

10 Enter ED-LLLDCC::AID::::L2SIDE=NETWORK;

Changing L2SIDE with a new value disables DCC and restores it with a new value. Provisioning working ID in a 1+1 APS environment automatically copies parameters to protect ID.

11 Enter ED-NE-TL1::::::GWENB=Y; to enable node as a gateway.


Build DCC Network Links4-558


DLP-224Set Up UPSR OperationsPURPOSE

This procedure is used to set up the node for Unidirectional Path Switched Rings (UPSR) operations. This procedure must be performed before UPSR cross-connections can be provisioned.

PREREQUISITES

The following conditions must be met before starting this procedure:

• The 1677 SONET Link is equipped and in service.

• The user is logged into the network element (node).

GENERAL

A UPSR is a method of protecting STS paths in a SONET ring configuration. The STS paths are broadcast in both directions around the ring. The received side of the cross-connection chooses the signal from the better of the two STS paths.

Data is transmitted simultaneously along the protected and protecting lines of the ring. The traffic for each line is transmitted in the clockwise and counterclockwise directions and is received by both facilities of each UPSR node. A path selector is provisioned in each two-way protection group and selects the best signal. If a fiber cut occurs, the received signals at the protection and protected lines of the node are interrupted. This interruption causes the path selectors at each node to select the alternate facility to automatically restore traffic.

STEP PROCEDURE

1 Enter ENT-EQPT::AID:::TYPE; to provision working OC-n module.

where:AID=IOCn module AIDTYPE=OC3-12P, OC12-4P, OC48-1P, or OC192-1P

2 Enter ENT-EQPT::AID:::TYPE; to provision protect OC-n module.

where:AID=IOCn module AIDTYPE=OC3-12P, OC12-4P, OC48-1P, or OC192-1P

3 Connect fiber-optic cable from West port of node 1 to East port of node 2.

4 Connect fiber-optic cable from East port of node 1 to West port of node 2.

Set Up UPSR Operations 4-559


Create UPSR

5 Create a UPSR for OC-3, OC-12, OC-48, or OC-192 interfaces.

Enter ENT-FFP-OCn::PROTECTED_ID,PROTECTING_ID::::PTYPE=UPSR; to create UPSR pair on two OC-n facilities.

where:OCn=OC3, OC12, OC48, or OC192PROTECTED_ID=working OC-n in 1+1 FFP groupPROTECTING_ID=protecting OC-n in 1+1 FFP group

6 Enter ENT-STS1::AID::::STSMAP=ALL:IS; to create STS facilities.

where: AID=STS-1 facility AID on PROTECTED_ID OC-n

7 Enter ENT-CRS-STS1::FROM,TO:::2WAY; to create cross-connections within ring.

where:FROM=STS-1 facility AID (drop)TO=STS-1 facility AID (ring)

8 Repeat steps 5 through 7 for other node in ring, then go to step 9.


Set Up UPSR Operations4-560


DLP-225Set Up BLSR OperationsPURPOSE

This procedure is used to set up node for two-fiber Bidirectional Line Switched Rings (BLSR) operations. This procedure must be performed before BLSR cross-connects can be provisioned.

PREREQUISITES

DCC network links must be created. Refer to DLP-223.

The following conditions must be met before starting this procedure:

• The 1677 SONET Link is equipped and in service.

• The user is logged into a network element (node).

• The facility must be an OC-48 or an OC-192 optical facility.

• BLSR must have no more than 16 NEs in a ring.

GENERAL

A two-fiber BLSR is a method of protecting STS paths in a SONET ring configuration. For example, for OC-48 BLSR, bandwidth is divided into two sets of STS paths. STS-1 through STS-24 are working channels, and STS-25 through STS-48 are protection channels. BLSR uses SONET line level performance to make ring-switch decisions, where Unidirectional Path Switched Rings (UPSR) method uses path level performance.

For information on TL1 command syntax, refer to the 1677 SONET Link Commands and Messages manual (PN 3EM13852AD).

STEP PROCEDURE

1 Enter ENT-EQPT::AID:::TYPE; to provision working OC-n module.

where:AID=IOCn module AIDTYPE=OC48-1P or OC192-1P

2 Enter ENT-EQPT::AID:::TYPE; to provision protect OC-n module.

where:AID=IOCn module AIDTYPE=OC48-1P or OC192-1P

Set Up BLSR Operations 4-561


3 Enter ENT-OCn::AID; for each OC-n facility on working and protect modules.

where:OCn=OC48 or OC192AID=OCn facility AID

4 Connect fiber-optic cable from West port of node 1 to East port of node 2.

5 Connect fiber-optic cable from East port of node 1 to West port of node 2.

Create BLSR

6 Create a BLSR ring for OC-48 or OC-192 interfaces.

7 Enter ENT-FFP-OCn::PROTECTED_ID,PROTECTING_ID::::PTYPE=BLSR2,NODEID=0-15,RINGID=ringid_value;

where:OCn=OC48 or OC192PROTECTED_ID=working OCn in 1+1 FFP groupPROTECTING_ID=protecting OCn in 1+1 FFP groupNODEID=0-15 (default=0) each node on BLSR must have unique NODEID numberringid_value=ring identifier for BLSR ring

8 Enter ENT-STS1::AID::::STSMAP=ALL:IS; to create STS facilities.

where: AID=STS-1 facility AID

9 Enter ENT-CRS-STS1::FROM,TO:::2WAY; to create cross-connects to appropriate NEs within ring.

where:FROM=STS-1 facility AIDTO=STS-1 facility AID

10 Enter RTRV-BLSR-TRC::WEST,[EAST]:::DIRN=BOTH,CAPTURE=Y,NOL=5; to retrieve BLSR trace data and status of the ring.

where:WEST=OC-n facility (example: OCn-{1,3,5,12,14,16}-{A,B}-1)EAST=OC-n facility (example: OCn-{2,4,6,13,15,17}-{A,B}-1)n=48 or 192

Set Up BLSR Operations4-562


11 Enter RTRV-COND-BLSR::WEST,[EAST]; to retrieve current ring status.

where:WEST=OC-n facility (example: OCn-{1,3,5,12,14,16}-{A,B}-1)EAST=OC-n facility (example: OCn-{2,4,6,13,15,17}-{A,B}-1)n=48 or 192

12 Are there more nodes to create?



Set Up BLSR Operations 4-563


Set Up BLSR Operations4-564


DLP-226Provision ECC Within DS3 Protection GroupPURPOSE

This procedure provides the instructions to provision an ECC module within an existing DS3 protect group. This process requires the protect group to be changed to ECC.

GENERAL

ENT-EQPT assigns an equipment object entity at the AID physical location and provisions the specified equipment, regardless of whether the equipment is installed in the system.The following equipment will be provisioned into the system using this procedure:

• DS3 card

• ECC


Once equipment is provisioned, ED-EQPT can be used to alter parameters.

Refer to table 226-B for slot locations of DS3 and ECC I/O cards. See figure 226-1 for all I/O card locations in shelf.

DS3 and ECC working modules can be mixed within the same protection group if the protection module is an ECC. An ECC/DS3 card protection group is defined when the corresponding protection slot is provisioned. Refer to table 226-C. The ECC module can operate in an unprotected mode. If the protection module is a DS3 module, all working modules in the protection group must be DS3. There is no restriction on the provisioning order.

Table 226-A. Card Type Parameter ValuesModule Card Type Parameter12-port DS3 module DS3-12P12-port DS3/EC1 module ECC-12P

Table 226-B. Valid Slot Locations for DS3 and ECC I/O CardsI/O Card Slot LocationsDS3, ECC {1-5,13-17}-{A,B}

Provision ECC Within DS3 Protection Group 4-565


Table 226-C. Slot Definitions for ECC and DS3 Card Protection GroupsProtection Slot Working Slot1A 2A, 3A, 4A, 5A1B 2B, 3B, 4B, 5B17A 16A, 15A, 14A, 13A17B 16B, 15B, 14B, 13B

Figure 226-1. Shelf Card Locations

677-0247-1041305

IOC

1B 2B 3B 4B 5B 6B

SS

C7

SS

C8

CC

C9

CC

C10

TC

11B

12B

13B

14B

15B

16B

17B

17A

16A

15A

14A

13A

12A

TC

11A

6A5A4A3A2A1A

IOC

IOC

IOC

IOC

IOC

IOC

IOC

IOC

IOC

IOC

IOC

IOC

IOC

IOC

IOC

IOC

IOC

IOC

IOC

IOC

IOC

IOC

IOC

Provision ECC Within DS3 Protection Group4-566






STEP PROCEDURE

Change Protection Group

1 DANGER: Possibility of personal injury. Cards can be installed or removed with rack power on. Hazardous electrical potentials are present; use extreme care when installing or removing cards with power on.

2 WARNING: Possibility of equipment damage. This equipment contains static-sensitive devices. Refer to Maintenance and Trouble Clearing Introduction for special handling instructions.

3 CAUTION: Possibility of service interruption. This procedure should be performed during a maintenance window.

4 Enter RTRV-EQPT::AID; for protect DS3 card being replaced.

where: AID=Equipment Access Identifier of protect DS3 card to be replaced. (DS3 protection slots are 1A, 1B, 17A, or 17B.)

5 Observe output.

6 Is state of protect module IS, WRK?


7 Enter INH-SWTOPROTN-EQPT::AID; for DS3 card to be replaced.

where: AID=Access Identifier of the DS3 card to be replaced



8 Did the output return COMPLD or DENY?

If COMPLD, to to step 9.If DENY, go to step 20.

9 Enter RMV-EQPT::AID; for DS3 card being replaced.

where: AID=Equipment Access Identifier of the DS3 card to be replaced.

10 Did output return COMPLD or DENY?

If COMPLD, go to step 11.If DENY, go to step 20.

11 Enter DLT-EQPT::AID; for DS3 card being replaced.

where: AID=Equipment Access Identifier of the DS3 card to be replaced.



13 Remove DS3 card. Refer to Maintenance and Trouble Clearing manual (PN 3EM13853AD).

14 Insert ECC module. Refer to Maintenance and Trouble Clearing manual (PN 3EM13853AD).

15 Enter ENT-EQPT::AID:::ECC-12P; for replacement ECC module.

where: AID=Equipment Access Identifier of the ECC module just inserted.



17 Enter RTRV-EQPT::AID; to verify state of ECC module.

where: AID=Equipment Access Identifier of the ECC module just inserted.



18 Is state of ECC module IS, STBYH?

If yes, configuration of protection slot is complete. Go to step 21 to configure working slots.If no, go to step 19.

It is normal for the LED on an ECC or DS3 card to not be lit if the card is in a protect slot and the status is standby.

19 Replacement ECC module should be in standby state within 3 minutes. Repeat step 17. If card is not in “IS, STBYH” state after 5 minutes, go to step 20.

20 Contact next level of technical support for assistance.

21 Select action.

To provision modules in working slots with 1677 SONET Link EMA, go to step 22.To provision modules in working slots with TL1, go to step 33.

Provision Working Slots with 1677 SONET Link EMA

22 Right-click the Equipment domain in the Navigation Tree.



25 On the Card page of the wizard, select appropriate slot and board from the drop-down list of available boards.

26 Click Next.

27 On the Equipment Type page, select appropriate card type from the drop-down list. Refer to table 226-A.

28 Click Next.



31 Click Finish.

32 Go to step 37.



Provision Working Slots with TL1

33 Select action.

To provision a DS3 card, go to step 34.To provision an ECC, go to step 36.

Provision DS3 Card

34 Enter ENT-EQPT::AID:::DS3-12P:[RVRTTIM=]:[PST];;

where: AID=IOC-{1-5, 13-17}-{A,B}Other parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.

35 Go to step 37.

Provision ECC Module

36 Enter ENT-EQPT::AID:::ECC-12P:[RVRTTIM=]:[PST];

where: AID=IOC-{1-5, 13-17}-{A,B}Other parameters are optional. If a value is not entered for these parameters, the system will use the default value. Refer to Commands and Messages manual (PN 3EM13852AD) for details on parameter values.




DLP-2271677 SONET Link Emergency ShutdownPURPOSE

This procedure provides the instructions for emergency shutdown.

STEP PROCEDURE

1 DANGER: Possibility of personal injury. Cards can be installed or removed with rack power on. Hazardous electrical potentials are present; use extreme care when installing or removing cards with power on.

2 WARNING: Possibility of equipment damage. This equipment contains static-sensitive devices. Refer to Maintenance and Trouble Clearing Introduction for special handling instructions.

3 CAUTION: Possibility of service interruption. This procedure will definitely result in service interruption.

4 If time and conditions allow, perform an FTP backup of provisioning data. Refer to DLP-188.

5 If time and conditions allow, document any standing alarms and state of equipment/disks. Refer to DLP-104, 111, and 190.

6 Remove power from the shelf bysetting the A and B power switches to the off (O) position. See figure 227-1. Power switches are located on the front of a 15RU shelf and the rear of an 18RU shelf.


Figure 227-1. A and B Power Sitch Location

A POWER SWITCH B POWER SWITCH

677-0335-1

032205

RTN RTNPOWER A

RTN RTNPOWER B

-48 VDC -48 VDC-48 VDC -48 VDC

1677 SONET Link Emergency Shutdown 4-571


1677 SONET Link Emergency Shutdown4-572


Software Reference Guide

1. INTRODUCTION

1.1 This Software Reference Guide provides supplementary information to be used with the User's Guide for the 1677 SONET Link.

• Section 2 (States) defines primary and secondary states for equipment and facilities.

• Section 3 (Codes) lists all codes including condition types, errors, and equipment- and facility-level default conditions.

• Section 4 (Security) explains system security, which prevents unauthorized access to system commands and determines each user's access level.

• Section 5 (Performance Monitoring) lists PM parameters supported in the system, parameter maximum values and threshold levels, and factory defaults for each parameter.

• Section 6 (Test Access) describes test access and shows example test access setups.

Software Reference Guide 5-1


Software Reference Guide5-2


2. STATES

2.1 This section defines the Primary States (PSTs) and Secondary States (SSTs) used in the 1677 SONET Link.

State Names

2.2 The system uses entity states to indicate the availability of an entity in providing its functions. (The term entity represents the resource or service generally identified by the Access Identifier [AID] parameter.) If an entity is not available, the entity states indicate the cause of the unavailability and what action can be taken to make the entity available. An entity's state is described by two parameters, the PST (primary state) and the SST (secondary state).

Primary State Values

2.3 The PST indicates the current overall service condition of an entity. Refer to table 2-A for the PST values used in the system.

2.4 If an entity is out of service (OOS), the PST indicates whether the out-of-service condition is due to an external management command (from an OS or user interface) or is caused by the system because of an internal event, or both.

Table 2-A. Primary State ValuesSTATE NAME DEFINITIONIS In Service - The entity is capable and allowed to provide its provisioned

functions.OOS-AU Out Of Service-Autonomous - The entity cannot provide its provisioned

functions due to the occurrence of an unsolicited autonomous event.OOS-AUMA Out Of Service-Autonomous and Management - The entity cannot provide its

provisioned functions because it is intentionally suspended by an external management command (from an OS or user interface) from performing its provisioned functions.

OOS-MA Out Of Service-Management - The entity is intentionally suspended by external management command (from an OS or user interface) from performing its provisioned functions; however, it may still be operationally capable of performing its provisioned functions.



2.5 When provisioning an entity and specifying a PST value in a command, the PST name is shortened to IS (in service) or OOS, but the full PST name (for example, OOS-AUMA) is used when provided in output response messages.

Secondary State Values

2.6 The SST provides additional information pertaining to the PST. Multiple SST values may apply to an entity at a particular instant. If more than one SST value applies to an entity, the SST values are grouped with an ampersand (&) in the output response message (for example, FAF&SGEO).

Refer to table 2-B for SST values used in the system.

Table 2-B. Secondary State ValuesSTATE NAME DEFINITIONAINS Automatic In-Service - The entity can transition to IS state if it is operationally

capable.AINS-DEA Automatic In-Service DeactivatedBUSY Busy - The entity is has been cross-connected and has no spare operating

capacity.DSBLD Disabled - The facility is prohibited from carrying traffic. (The required

supporting equipment is not provisioned.)FAF Facility Failure - The associated facility entity has failed.FLT Fault - The entity is OOS due to at least one hardware fault.IDLE Idle - Entity is available for providing service but currently no user is using it.LPBK Loopback - The entity is in a loopback operation.MEA Mismatch of Equipment and Attributes - The entity is installed with incorrect

equipment or card, or the correct equipment is installed, but it has improper attributes assigned.

MT MaintenancePMI Performance Monitoring Inhibited - The Performance Monitoring (PM)

function has been temporarily suspended for the entity.PRI Protection Release Inhibited - The protection entity is inhibited from automatic

release from protection.PSI Protection Switching Inhibited - The working entity is inhibited from

automatically switching to protection.SDEA Subordinate Entity AbsentSDEE Supported Entity Exists - The entity is currently supporting other entities.SGEO Supporting Entity Outage - The associated supporting entity has failed or is

out of service due to management action.



STBYH Standby, Hot - The entity is backing up another entity and it is synchronized with the backed up entity. A hot standby entity can assume the role of the backed up entity with no need for initialization.

STBYS Standby Switched - This value indicates that the standby entity has taken over for the backed-up entity.

SWDL Software download in progress.TRM Terminated - The facility entity has been given termination parameters, i.e. the

entity has been connected and its path has been terminated (as a result of the connection) or the parent entity has been terminated as a result of its subentities being connected. Note that TRM is set for STS1 entities that are cross-connected to T3, or that have had at least one embedded VT1.5 or T1 cross-connected. TRM is also set on GigE facilities that have had all of their required Ethernet Virtual Concatenation entities cross-connected.

TS Test - Test access activity is currently being performed on or by the entity.UAS Unassigned - The entity has not been assigned with necessary provisioning

data.UEQ Unequipped - The equipment entity is not equipped with necessary hardware,

or software entity is not loaded with necessary data or code. WRK Working - The redundant entity is currently providing service.

Table 2-B. Secondary State Values (cont.)STATE NAME DEFINITION



3. CODES

Equipment Condition Types

3.1 Refer to table 3-A for equipment condition types used in the system. The DESCRIPTION column identifies the relationship between equipment and condition type. The EQUIPMENT column lists applicable equipment for each condition.

Table 3-A. 1677 SONET Link Equipment Condition TypesCONDITIONTYPE DESCRIPTION EQUIPMENTBKUPMEMP Backup Memory-Primary Failure. Redundant disk is

not available. Applies to logical disk.DISK

BKUPMEMS Backup Memory-Secondary Failure. Physical disk is not available. Applies to physical disk.

DISK

BKUPMEMSYNCH Disk synchronization is in progress. Applies to logical disk.

DISK

CFG-RESET Creation of initial facility set is in progress as part of SSC bootup process.

SSC

CFGFLT Configuration database download failure for the processor module.

CCC, SSC

CLFAN Failure of one or more fans in the fan tray. FANTRAYCONTBUS-7 Unable to select a valid message bus A arbiter. CHASSISCONTBUS-8 Unable to select a valid message bus B arbiter. CHASSISCONTBUS-MOS-1 Hardware error is detected when attempting to

enumerate MOS devices after MOS discovery.MOS

CONTBUS-MOS-2 After MOS discovery, MOS devices are seen by only one of the two CCCs.

MOS

CONTR Control processor module failure. CCC, SSCCONTR-TACC Test access is inhibited due to control processor

module failure.SSC

CTRLREAD Fan controller read operation failure. FANTRAYCTRLWRITE Fan controller write operation failure. FANTRAYDISK90 Disk is 90% full. Applies to physical disk. DISKFPGAIP FPGA upgrade is in progress. Applies to TMUX

module.IOC

FPSWUNLCK Front panel switch is unlocked. CCC, SSC, TC



FRCDWKSWPR Forced switch to protection is in effect for a working module. Applies to DS3, ECC, TMUX, and VSC modules.

IOC

FWMISM Incompatible firmware. Applies to TMUX module. IOCHLDOVRSYNC System timing is in holdover synchronization mode. TC-SYNCHWFAIL Hardware error is detected associated with a module.

Applies to DS3, ECC, EDFA, GIGE, OC3, OC12, OC48, OC192, TMUX, and VSC modules.

IOC

IMPROPRMVL Improper removal of module CCC, SSC, IOC, DISK, TC

INHMSG-PM PM reports are inhibited for all entities. CHASSISINHSWPR Declared against a protection module when that

module is inhibited from providing protection. Applies to DS3, ECC, TMUX, and VSC modules.

IOC

INHSWWKG Working module is inhibited from switching back from protection (traffic is locked onto protection module). Applies to DS3, ECC, TMUX, and VSC modules.

IOC

INIT System initialization is in progress. CHASSISINT Unrecognized fan controller. FANTRAYINT-1 No valid oscillator could be selected. CHASSISINT-19 Module ID ROM (remote inventory data) is improperly

programmed. Applies to Ds3, ECC, EDFA, GIGE, OC3, OC12, OC48, OC192, TMUX,and VSC modules.

IOC

INT-2 No valid system clock could be selected. CHASSISMANWKSWPR Manual switch to protection is in effect for a working

module. Applies to DS3, ECC, TMUX, and VSC modules.

IOC

PRCDRERR Procedure error. Module not consistent with hardware slot/software assignment. Applies to DS3, ECC, GIGE, OC3, OC12, OC48, OC192, TMUX, and VSC I/O modules as well as the TC.

IOC, TC

PWR Battery A/B -48V DC error is detected. Applies to ECC module, fan power supply, or chassis power supply.

IOC, POWER

SNTP Failed to synchronize time from the server at the specified interval.

CHASSIS

SYNCINT System timing is in internal mode. TC-SYNCSYNCOOS No valid timing reference is available or no TC module

is available.TC-SYNC

SYNCPRI Primary timing reference is not available. TC-SYNC

Table 3-A. 1677 SONET Link Equipment Condition Types (cont.)CONDITIONTYPE DESCRIPTION EQUIPMENT



Facility Condition Types

3.2 Refer to table 3-B for facility condition types used in the system. The DESCRIPTION column identifies the relationship between facility and condition type. The FACILITY TYPE column lists applicable facility types for each condition.

SYNCSEC Secondary timing reference is not available and/or no backup TC module is available.

TC-SYNC

SYSDBG The system is operating in debug mode. CHASSISSYSREADY System is ready to accept TL1 messages. CHASSISTEMP Temperature sensor has detected marginally high or

very high temperature.CHASSIS

USTHRESHOLD Resource module usage has reached 80%. Applies to TMUX and VSC modules.

IOC

WKSWPR Automatic switch to protection is in effect for a working module. Applies toDS3, ECC, TMUX, and VSC modules.

IOC

WTR Wait to restore state is in effect for a working module. Applies to DS3, ECC, TMUX, and VSC modules.

IOC

Table 3-B. 1677 SONET Link Configuration Facility Condition TypesCONDITION TYPE DESCRIPTION FACILITY TYPEACTLPBK The associated entity has a loopback activated at

near end.EC1, OC12, OC192, OC3, OC48, T1, T3, VT1

AIC DS3 Application Identification Channel (AIC) detected. Applies to standalone DS3 on ECC module.

T3

AIS Alarm Indication Signal detected. T1, T3AIS-L Alarm Indication Signal - Line detected. OC12, OC192, OC3, OC48,

EC1AIS-P Alarm Indication Signal - Path detected. STS1, STS12C, STS3C,

STS48CAIS-V Alarm Indication Signal - Path detected. VT1APSB Protection byte failure has been detected. This

failure is applicable to 1+1 bidirectional FFP provisioned facilities. Applies to the protection OCn facility.

OC12, OC192, OC3, OC48

Table 3-A. 1677 SONET Link Equipment Condition Types (cont.)CONDITIONTYPE DESCRIPTION EQUIPMENT



APSCDFLTK Default K byte received. OC192, OC48APSCIMP Improper K byte received (2F-BLSR). OC192, OC48APSCINCON Inconsistent K byte received. OC192, OC48APSCM APS channel match failure has been detected. This

failure is applicable to 1+1 bidirectional FFP provisioned facilities. Applies to the protection OCn facility.

OC12, OC192, OC3, OC48

APSCNMIS Node identifier mismatch in K bytes (2F-BLSR). OC192, OC48APSMM APS mode mismatch failure has been detected.

This failure is applicable to 1+1 bidirectional FFP provisioned facilities. Applies to the protection OCn facility.

OC12, OC192, OC3, OC48

BLSRCOMMERR BLSR communication error. This condition is set when there is a communications break in an existing automap session or an automap packets cannot be exchanged due to controller initialization, inactivity timer, ring identifier mismatch, DCC not enabled between the local and remote nodes, DCC provisioned for IP between the local and remote nodes. Applies to both working and protection OCn facilities.

OC192, OC48

BLSRPROV BLSR misprovisioning alarm. The local and remote nodes are provisioned for CLNP DCC communications and the local node is provisioned for automap generation. However, the remote node is not provisioned for automap generation. Applies to both working and protection OCn facilities.

OC192, OC48

DUPNODEID Duplicate Node ID. A duplicate node ID has been detected. This condition can be detected on a BLSR ring when automap generation is enabled. Applies to both working and protection OCn facilities.

OC192, OC48

EOC Embedded Operations Channel failure on Section DCC. No adjacencies formed.

OC12, OC192, OC3, OC48

EOCL Embedded Operations Channel failure on Line DCC. No adjacencies formed.

OC12, OC192, OC3, OC48

FEACAIS DS3 AIS failure at remote terminal (reported via DS3 FEAC channel).

T3

FEACDS1EFAILNSA

DS1 equipment failure at remote terminal (reported via DS3 FEAC channel).

T3

Table 3-B. 1677 SONET Link Configuration Facility Condition Types (cont.)CONDITION TYPE DESCRIPTION FACILITY TYPE



FEACDS1EFAILSA DS1 equipment failure at remote terminal (reported via DS3 FEAC channel).

T3

FEACDS1LOS Single DS1 LOS failure at remote terminal (reported via DS3 FEAC channel).

T3

FEACDS1MLOS Multiple DS1 LOS failures at remote terminal (reported via DS3 FEAC channel).

T3

FEACEFAILCOM Common equipment failure at remote terminal (reported via DS3 FEAC channel).

T3

FEACEFAILNSA DS3 equipment failure at remote terminal (reported via DS3 FEAC channel).

T3

FEACEFAILSA DS3 equipment failure at remote terminal (reported via DS3 FEAC channel).

T3

FEACISD DS3 ISD at remote terminal (reported via DS3 FEAC channel).

T3

FEACLOF DS3 LOF failure remote terminal (reported via DS3 FEAC channel).

T3

FEACLOS DS3 LOS failure remote terminal (reported via DS3 FEAC channel).

T3

FEPRLF Far ENd protection failure has been detected. This failure is applicable to 1+1 bidirectional FFP provisioned facilities. applies to the protection OCn facility.

OC12, OC192, OC3, OC48

FRCDWKSWBK Forced switch from protection to working. This is a standing condition for 1+1 FFP provisioned facilities. Applies to the protection OCn facility.

OC12, OC192, OC3, OC48

FRCDWKSWPR Forced switch from working to protection. This is a standing condition for 1+1 FFP provisioned facilities. Applies to the working OCn facility.

OC12, OC192, OC3, OC48

INHMSG-PM PM reports inhibited. EC1, GIGE, OC12, OC192, OC3, OC48, OFA, STS1, STS12C, STS3C, STS48C, T1, T3, VT1

IPCPLCONFAIL IPCP Line DCC connection failure. OC12, OC192, OC3, OC48IPCPLDCF IPCP Line DCC connection failure. Alarm raised

after MAXTERM count exhausted or reception of Code reject.

OC12, OC192, OC3, OC48

IPCPSCONFAIL IPCP Section DCC connection failure. OC12, OC192, OC3, OC48IPCPSDCF IPCP Section DCC connection failure. Alarm raised

after MAXTERM count exhausted or reception of Code reject.

OC12, OC192, OC3, OC48




ISD DS3 Idle signal detected. T3L2LCONFAIL Layer 2 Line DCC connection failure: Line DCC

cannot communicate with far-end Line DCC due to data link connection problems. This alarm is detectable when L2SIDE=USER.

OC12, OC192, OC3, OC48

L2SCONFAIL Layer 2 Section DCC connection failure: Section DCC cannot communicate with far-end Section DCC due to data link connection problems. This alarm is detectable when L2SIDE=USER.

OC12, OC192, OC3, OC48

LCPLCONFAIL LCP Line DCC connection failure. Alarm raised after MAXCONFIG count exhausted.

OC12, OC192, OC3, OC48

LCPLDF LCP Line DCC failure. Alarm raised after MAXTERM count exhausted or ECHOREPCOUNT exhausted or reception of Code reject.

OC12, OC192, OC3, OC48

LCPSCONFAIL LCP Section DCC connection failure. Alarm raised after MAXCONFIG count exhausted.

OC12, OC192, OC3, OC48

LCPSDF LCP Section DCC failure. Alarm raised after MAXTERM count exhausted or ECHOREPCOUNT exhausted or reception of Code reject.

OC12, OC192, OC3, OC48

LOCC Loss of Client Character synchronization. GIGELOCKOUTOFPR APS lockout of protection. This is a standing

condition for 1+1 FFP provisioned facilities. Applies to the protection OCn facility.

OC12, OC192, OC3, OC48

LOCS Loss of Client Signal event. GIGELOF Loss of Frame EC1, OC3, OC12, OC48,

OC192, T1, T3, VT1LOFFEAC DS3 LOF failure at remote terminal (reported via

DS3 FEAC channel). Applies to T3 residing on ECC module.

T3

LOL Gigabit Ethernet Loss of Link GIGELOP-P Loss of Pointer detected. STS1, STS3C, STS12C,

STS48CLOP-V Loss of Pointer-Path detected. VT1LOS Loss of Signal. (Loss of Pointer if GIGE) EC1, GIGE, OC3, OC12,

OC48, OC192, OFA, T3MANWKSWBK Manual switch from protection to working. This is a

standing condition for 1+1 FFP provisioned facilities. Applies to the protection OCn facility.

OC12, OC192, OC3, OC48




MANWKSWPR Manual switch from working to protection. This is a standing condition for 1+1 FFP provisioned facilities. Applies to the working OCn facility.

OC12, OC192, OC3, OC48

OALCASETEMP Optical case temperature. OFA

OALKEYLOCK EDFA Key Lock. OFAOALLBC Excessive laser bias current level detected. OC192, OC48, OFAOALLOPOW Optical loss of power. OFAOALPWR Excessive laser power detected. OC192, OC48, OFAOALRXLOCK Laser receiver lock error detected. OFAOALTEMP Excessive laser temperature detected. OC192, OC48, OFAOALTXLOCK Laser transmitter lock error detected. OFAOOL-RXD Gigabit Ethernet out of lock - receive data. GIGEOOL-RXR Gigabit Ethernet out of lock - receive reference. GIGEOOL-TXR Gigabit Ethernet out of lock - transmit reference. GIGEOOS GIGE is out of sync. GIGEPLM-P Payload Label Mismatch - Path detected. STS1, STS3C, STS12C,

STS48CPLM-V Payload Label Mismatch - VT Path. VT1RAI Remote Alarm Indication detected. T3, T1RFI-L Remote Failure Indication (RFI-L) detected. (RDI-L

for EC1.)EC1, OC3, OC12, OC48, OC192

RFI-P Remote Failure Indication - Path detected. STS1, STS3C, STS12C, STS48C

RFI-V Remote Failure Indication detected. VT1RINGMAPPROV Ring Map misprovisioning. If automap is enabled,

this alarm is based on the ability to communicate around the entire ring in both directions. If automapis disabled, this alarm is based on the valuesin the manual ring map. Applies to both working and protection OCn facilities.

OC192, OC48

RMOPTIC Gigabit Ethernet removable optics unplugged. GIGERNG-SQUELCH Traffic on ring squelched. OC192, OC48SD Signal Degrade - Path (SF) detected. (For STSn)

Signal Degrade threshold exceeded on line (SD). (For OCn)

STS1, STS3C, STS12C, STS48C, OC3, OC12, OC48, OC192

SF Signal Fail - Path (SF) detected. (For STSn)Signal fail threshold exceeded on line (SF). (For OCn)

STS1, STS3C, STS12C, STS48C, OC3, OC12, OC48, OC192




Common Condition Types

3.3 The system has no common (no specific entity) condition types.

Transient Condition Types

3.4 Refer to table 3-C for transient condition type codes used in the system.

TH-LBCN-HT Laser Bias Current (Normalized) - Upper threshold crossed.

OC192, OC48, OFA

TH-LSRTEMP-HT Laser Temperature - Uper threshold crossed. OC192, OC48, OFATH-OPRN-HT Optical Power Received (Normalized) - Upper

threshold crossed.OC192, OC48, OFA

TH-OPRN-LT Optical Power Received (Normalized) - Lower threshold crossed.

OC192, OC48, OFA

TH-OPTN-HT Optical Power Transmitted (Normalized) - Upper threshold crossed.

OFA

TH-OPTN-LT Optical Power Transmitted (Normalized) - Lower threshold crossed.

OFA

TIM-P Trace Identifier Mismatch - Path detected. STS1, STS3C, STS12C, STS48C

UNEQ-P Unequipped - Path detected. STS1, STS3C, STS12C, STS48C

UNEQ-V Unequipped detected. VT1WKSWBK APS automatic switch from protection to working.

This condition is a standing condition for 1+1 FFP provisioned facilities. Applies to the protection OCn facility.

OC3, OC12, OC48, OC192

WKSWPR APS automatic switch from working to protection. This condition is a standing condition for 1+1 FFP provisioned facilities. Applies to the working OCn facility.

OC3, OC12, OC48, OC192

WTR Wait to Restore state. Applies to the working OCn facility.

OC3, OC12, OC48, OC192

XMTLPBK The associated entity has an active loopback request to the far end.

T1, T3




Table 3-C. Transient Condition TypesCONDITION TYPE CONDITION DESCRIPTION AIDAUTORESET Automatic system reset. CHASSISBKUPMEMSYNCHFAIL

Disk synchronization operation failure. Applies to logical disk.

DISK

CFGFLT Configuration database download failure for the system.

CHASSIS

CONTBUS-MOS-3 Mismatch in number of MOS devices discovered by each CCC.

MOS

EXER-MULT Multiple EXER-R commands detected. OC48, OC192EXER-RING-DONE Exercise ring complete. OC48, OC192EXT-CMD-PREEMPT

Command preempted by ring operation. OC48, OC192

EXTCMD-DEFAULT Command was rejected; adjacent node is in capable of signaling.

OC48, OC192

EXTCMD-DUP Command was rejected; duplicated command. OC48, OC192EXTCMD-EQUAL-PRI

Command was rejected; equal priority to the existing command.

OC48, OC192

EXTCMD-LOWER-PRI

Command was rejected; lower priority than existing one.

OC48, OC192

EXTCMD-LWR-RING

Command was rejected; lower priority than ring existing ring condition.

OC48, OC192

FAILTOSW-RING Fail to switch. OC48, OC192FPGAUPFAIL FPGA upgrade has failed. Applies to TMUX. IOCFRCDWKSWBK Forced switch from protection to working. Applies to

UPSR facilities.STS1, STS3C, STS12C, STS48C

FRCDWKSWPR Forced switch from working to protection. Applies to BLSR facilities (OCn) and UPSR facilities (STSn).

OC48, OC192, STS1, STS3C, STS12C, STS48C

FRD Intrusion is suspected. CHASSISINIT-2 Module is reset. CCC, SSCINTERR An internal error has been detected for the module.

Applies to DS3, ECC, EDFA, GIGE, OC3, OC12, OC48, and OC192 modules.

IOC

LDCCDLFL Line DCC data link connection failure: After establishing a connection, Line DCC communication failed, and the problem persists for L2REX times L2WAIT times.

OC3, OC12, OC48, OC192

LDCCFRMR Line DCC Frame Reject: FRMR PDU was received over Line DCC.

OC3, OC12, OC48, OC192

LOCKOUTOFPR Lockout of protection. Applies to UPSR facilities. STS1, STS3C, STS12C, STS48C



MANRESET Manual system reset. CHASSISMANWKSWBK Manual switch from protection to working. Applies

to UPSR facilities.STS1, STS3C, STS12C, STS48C

MANWKSWPR Manual switch from working to protection. Applies to BLSR facilities (OCn) and UPSR facilities (STSn).


SDCCDLFL Section DCC data link connection failure: After establishing a connection, Section DCC communication failed, and the problem persists for L2REX times L2WAIT times.

OC3, OC12, OC48, OC192

SDCCFRMR Section DCC Frame Reject: FRMR PDU was received over Section DCC.

OC3, OC12, OC48, OC192

SRFLT-CIRRUS Internal subsystem failure. Error while accessing the Cirrus PC Card controller.

TC

SRFLT-DISK0 Internal subsystem failure. Error while accessing lower disk control registers.

TC

SRFLT-DISK1 Internal subsystem failure. Error while accessing upper disk control registers.

TC

SRFLT-ISAIO Internal subsystem failure. Error while accessing ISA bus for an I/O operation.

TC

SRFLT-ISAMEM Internal subsystem failure. Error while accessing ISA bus for a memory operation.

TC

SRFLT-SRREG Internal subsystem failure. Error while accessing a System Resource Bus status register.

TC

SRFLT-T1FR1 Internal subsystem failure. Error while accessing a DS1 Framer 1 register.

TC

SRFLT-T1FR2 Internal subsystem failure. Error while accessing a DS1 Framer 2 register.

TC

SWTMGREF Timing reference is switched. TCSYNCSTATCHNG Timing reference quality level has changed. TCSYSBOOT Startup configuration database download has

completed.CHASSIS

T-AISS-P TCA - AIS seconds - T1 path or DS3 path T1, T3T-CSS-PFE TCA - CSS seconds - T1 Path Far End T1T-CV-LFE TCA - Code Violations, Line Far End EC1, OC3, OC12, OC48,

OC192T-CV-PFE TCA - Code Violations, Path Far End T1, STS1, STS3C, STS12C,

STS48CT-CV-V TCA - Code Violations, VT Path VT1

Table 3-C. Transient Condition Types (cont.)CONDITION TYPE CONDITION DESCRIPTION AID



T-CV-VFE TCA - Code Violations, VT Path Far End VT1T-CVCP-P TCA - Code Violations, CP parity, DS3 Path T3T-CVCP-PFE TCA - Code Violations, CP parity, DS3 Path Far

EndT3

T-CVL TCA - Code Violations, Line EC1, OC3, OC12, OC48, OC192, T3

T-CVP TCA - Code Violations, Path T1, STS1, STS3C, STS12C, STS48C

T-CVP-P TCA - Code Violations, DS3 Path T3T-CVS TCA - Code Violations, Section EC1, OC3, OC12, OC48,

OC192T-ES-LFE TCA - Errored Seconds, Line Far End EC1, OC3, OC12, OC48,

OC192, T1T-ES-PFE TCA - Errored Seconds, Path Far End T1, STS1, STS3C, STS12C,

STS48CT-ES-V TCA - Errored Seconds, VT Path VT1T-ES-VFE TCA - Errored Seconds, VT Path Far End VT1T-ESA-L TCA - Errored Seconds Type A, DS3 Line T3T-ESA-P TCA - Errored Seconds Type A, T1 Path T1T-ESA-PFE TCA - Errored Seconds Type A, T1 Path Far End T1T-ESACP-P TCA - Errored Seconds CP Parity Type A, DS3

PathT3

T-ESACP-PFE TCA - Errored Seconds CP Parity Type A, DS3 Path Far End

T3

T-ESAP-P TCA - Errored Seconds Type A, DS3 Path T3T-ESB-L TCA - Errored Seconds Type B, DS3 Line T3T-ESB-P TCA - Errored Seconds Type B, T1 Path T1T-ESB-PFE TCA - Errored Seconds Type B, T1 Path Far End T1T-ESBCP-P TCA - Errored Seconds CP Parity Type B, DS3

PathT3

T-ESBCP-PFE TCA - Errored Seconds CP Parity Type B, DS3 Path Far End

T3

T-ESBP-P TCA - Errored Seconds Type B, DS3 Path T3T-ESCP-P TCA - Errored Seconds CP Parity, DS3 Path T3T-ESCP-PFE TCA - Errored Seconds CP Parity, DS3 Path Far

EndT3

T-ESL TCA - Errored Seconds, Line EC1, OC3, OC12, OC48, OC192, T3




T-ESP TCA - Errored Seconds, Path T1, STS1, STS3C, STS12C, STS48C

T-ESP-P TCA - Errored Seconds, DS3 Path T3T-ESS TCA - Errored Seconds, Section EC1, OC3, OC12, OC48,

OC192T-ETH-FCS TCA - Ethernet Frame Checksum error GIGET-ETH-FLME TCA - Frames lost due to MAC error GIGET-ETH-FRAG TCA - Fragmentation GIGET-ETH-JABB TCA - Jabber GIGET-ETH-LENERR TCA - GIGE Length error GIGET-ETH-SYMERR TCA - Symbol Error GIGET-ETH-SYSERR TCA - System Error GIGET-LOSS-L TCA - LOS seconds, DS3 Line T3T-SAS-P TCA - SEF/AIS Seconds, Path T1, T3T-SASCP-PFE TCA - SEF/AIS Seconds CP Parity, DS3 Path Far

EndT3

T-SEFS-PFE TCA - Severely Errored Frame Seconds, T1 Path Far End

T1

T-SEFS-S TCA - Severely Errored Frame Seconds, Section EC1, OC3, OC12, OC48, OC192

T-SES-LFE TCA - Severely Errored Seconds, Line Far End EC1, OC3, OC12, OC48, OC192

T-SES-PFE TCA - Severely Errored Seconds, Path Far End T1, STS1, STS3C, STS12C, STS48C

T-SES-V TCA - Severely Errored Seconds, VT Path VT1T-SES-VFE TCA - Severely Errored Seconds, VT Path Far End VT1T-SESCP-P TCA - Severely Errored Seconds CP Parity, DS3

PathT3

T-SESCP-PFE TCA - Severely Errored Seconds CP Parity, DS3 Path Far End

T3

T-SESL TCA - Severely Errored Seconds, Line EC1, OC3, OC12, OC48, OC192, T3

T-SESP TCA - Severely Errored Seconds, Path T1, STS1, STS3C, STS12C, STS48C

T-SESP-P TCA - Severely Errored Seconds, DS3 Path T3T-SESS TCA - Severely Errored Seconds, Section EC1, OC3, OC12, OC48,

OC192




Notification Codes

3.5 Refer to table 3-D for notification codes reported by the system. Codes are listed in order of significance.

T-UAS-LFE TCA - Unavailable Seconds, Line Far End EC1, OC3, OC12, OC48, OC192

T-UAS-PFE TCA - Unavailable Seconds, Path Far End T1, STS1, STS3C, STS12C, STS48C

T-UAS-V TCA - Unavailable Seconds, VT Path VT1T-UAS-VFE TCA - Unavailable Seconds, VT Path Far End VT1T-UASCP-P TCA - Unavailable Seconds CP Parity, DS3 Path T3T-UASCP-PFE TCA - Unavailable Seconds CP Parity, DS3 Path

Far EndT3

T- UASL TCA - Unavailable Seconds, Line EC1, OC3, OC12, OC48, OC192

T-UASP TCA - Unavailable Seconds, Path T1, STS1, STS3C, STS12C, STS48C

T-UASP-P TCA - Unavailable Seconds, Path, DS3 Path T3WKSRPR Cross connect path switch to protection alarm. STS1, STS3C, STS12C,

STS48CWKSWBK Automatic working switch back. Applicable to

UPSR facilities.STS1, STS3C, STS12C, STS48C

WKSWBK-RING A ring switch back to working has completed. OC48, OC192WKSWPR Automatic switch from Working to Protection.

Applicable to BLSR (OC48, OC192) and UPSR (STSn) facilities.


WKSWPR-RING-FE Aworking switch to protect has occurred due to a far-end SF.

OC48, OC192




Service Affect Codes

3.6 Refer to table 3-E for service affect codes that indicate whether a condition is service-affecting or non-service-affecting.

Command Privilege Defaults

3.7 Refer to table 3-F for TL1 commands and their associated minimum default User Access Privileges (UAPs).

Table 3-D. Notification CodesNOTIFICATION CODE DEFINITIONCR Critical - reported through REPTÂLMMJ Major - reported through REPTÂLMMN Minor - reported through REPTÂLMNA Not alarmed - reported through REPTÊVT. User can set other activities

to be NA via the SET-ATTR command.NR Not reported. Used only in provisioning requests. Conditions with this

notification code are not considered alarms and are not reported using REPTÊVT; however, they are available through the REPT^COND and RTRV-COND messages.

Table 3-E. Service Affect CodesSERVICE AFFECT DEFINITIONSA Service-affecting, immediate action requiredNSA Non-service-affecting, action required



Table 3-F. Command Access PrivilegesCOMMAND CODE UAP SEC UAPACT-DISK NETADMINACT-USER READ ALW-LOG-SECU READ XALW-MSG-ALL READALW-DBCHGMSG-ALL READALW-MSG-COM READALW-MSG-EC1 READALW-MSG-EQPT READALW-MSG-GIGE READALW-MSG-OC12 READALW-MSG-OC192 READALW-MSG-OC3 READALW-MSG-OC48 READALW-MSG-OFA READALW-MSG-STS1 READALW-MSG-STS12C READALW-MSG-STS3C READALW-MSG-STS48C READALW-MSG-T1 READALW-MSG-T3 READALW-MSG-VT1 READALW-PMREPT-ALL TESTALW-PMREPT-COM TESTALW-PMREPT-EC1 TESTALW-PMREPT-GIGE TESTALW-PMREPT-OC12 TESTALW-PMREPT-OC192 TESTALW-PMREPT-OC3 TESTALW-PMREPT-OC48 TESTALW-PMREPT-OFA TESTALW-PMREPT-STS1 TESTALW-PMREPT-STS12C TESTALW-PMREPT-STS3C TESTALW-PMREPT-STS48C TESTALW-PMREPT-T1 TEST



ALW-PMREPT-T3 TESTALW-PMREPT-VT1 TESTALW-SWTOPROTN-EQPT CONFALW-SWTOWKG-EQPT CONFALW-USER-SECU READ XCANC-CID-SECU READ XCANC-USER READ1

CHG-ACCMD-STS1 TESTCHG-ACCMD-STS12C TESTCHG-ACCMD-STS3C TESTCHG-ACCMD-STS48C TESTCHG-ACCMD-T1 TESTCHG-ACCMD-T3 TESTCHG-ACCMD-VT1 TESTCHK-DISK NETADMINCONN-TACC-STS1 CONFCONN-TACC-STS3C CONFCONN-TACC-STS12C CONFCONN-TACC-STS48C CONFCONN-TACC-T1 CONFCONN-TACC-T3 CONFCONN-TACC-VT1 CONFCOPY-RFILE NETADMINCPY-MEM NETADMINDISC-TACC CONFDLT-ARPCACHE CONFDLT-CRS-GIGE CONFDLT-CRS-STS1 CONFDLT-CRS-STS12C CONFDLT-CRS-STS3C CONFDLT-CRS-STS48C CONFDLT-CRS-T1 CONFDLT-CRS-T3 CONFDLT-CRS-VT1 CONFDLT-EC1 CONF

Table 3-F. Command Access Privileges (cont.)COMMAND CODE UAP SEC UAP



DLT-EQPT NETADMINDLT-EVC CONFDLT-FFP-OC12 CONFDLT-FFP-OC192 CONFDLT-FFP-OC3 CONFDLT-FFP-OC48 CONFDLT-GIGE CONFDLT-MAP NETADMINDLT-NE-DENIED NETADMINDLT-NE-IPRT NETADMINDLT-NE-TRUST READ XDLT-NETIF CONFDLT-OC12 CONFDLT-OC192 CONFDLT-OC3 CONFDLT-OC48 CONFDLT-OFA CONFDLT-RFILE NETADMINDLT-STS1 CONFDLT-STS12C CONFDLT-STS3C CONFDLT-STS48C CONFDLT-T1 CONFDLT-T3 CONFDLT-TARPCACHE CONFDLT-TARPLDB CONFDLT-USER-SECU READ XDLT-VT1 CONFED-BITS NETADMINED-CRS-GIGE CONFED-CRS-STS1 CONFED-CRS-STS12C CONFED-CRS-STS3C CONFED-CRS-STS48C CONFED-CRS-T1 CONF




ED-CRS-T3 CONFED-CRS-VT1 CONFED-DAT NETADMINED-EC1 CONFED-EQPT NETADMINED-FFP-OC12 CONFED-FFP-OC192 CONFED-FFP-OC3 CONFED-FFP-OC48 CONFED-FFP-STS1 CONFED-GIGE CONFED-LCPLDCC CONFED-LCPSDCC CONFED-LLLDCC PROVED-LLSDCC PROVED-MAADDR CONFED-MAP NETADMINED-NE NETADMINED-NE-SNTP NETADMINED-NE-TL1 NETADMINED-OC12 CONFED-OC192 CONFED-OC3 CONFED-OC48 CONFED-OFA CONFED-PID READ ED-RINGMAP CONFED-SECU READ XED-SQLMAP CONFED-STS1 CONFED-STS12C CONFED-STS3C CONFED-STS48C CONFED-T1 CONFED-T3 CONF




ED-TARP CONFED-ULCOMPMR CONFED-ULLDCC PROVED-ULSDCC PROVED-USER-SECU READ XED-VT1 CONFENT-CRS-GIGE CONFENT-CRS-STS1 CONFENT-CRS-STS12C CONFENT-CRS-STS3C CONFENT-CRS-STS48C CONFENT-CRS-T1 CONFENT-CRS-T3 CONFENT-CRS-VT1 CONFENT-EC1 PROVENT-EQPT NETADMINENT-EVC PROVENT-FFP-OC12 PROVENT-FFP-OC192 PROVENT-FFP-OC3 PROVENT-FFP-OC48 PROVENT-GIGE PROVENT-MAP NETADMINENT-NE-DENIED NETADMINENT-NE-IPRT NETADMINENT-NE-TRUST READ XENT-NETIF PROVENT-OC12 PROVENT-OC192 PROVENT-OC3 PROVENT-OC48 PROVENT-OFA PROVENT-STS1 PROVENT-STS12C PROVENT-STS3C PROV




ENT-STS48C PROVENT-T1 PROVENT-T3 PROVENT-USER-SECU READ XENT-VT1 PROVEX-SW-OC48 TESTEX-SW-OC192 TESTFMT-DISK NETADMININH-LOG-SECU READ XINH-MSG-ALL READINH-DBCHGMSG-ALL READINH-MSG-COM READINH-MSG-EC1 READINH-MSG-EQPT READINH-MSG-EVC READINH-MSG-GIGE READINH-MSG-OC12 READINH-MSG-OC192 READINH-MSG-OC3 READINH-MSG-OC48 READINH-MSG-OFA READINH-MSG-STS1 READINH-MSG-STS12C READINH-MSG-STS3C READINH-MSG-STS48C READINH-MSG-T1 READINH-MSG-T3 READINH-MSG-VT1 READINH-PMREPT-COM TESTINH-PMREPT-EC1 TESTINH-PMREPT-GIGE TESTINH-PMREPT-OC12 TESTINH-PMREPT-OC192 TESTINH-PMREPT-OC3 TESTINH-PMREPT-OC48 TEST




INH-PMREPT-OFA TESTINH-PMREPT-STS1 TESTINH-PMREPT-STS12C TESTINH-PMREPT-STS3C TESTINH-PMREPT-STS48C TESTINH-PMREPT-T1 TESTINH-PMREPT-T3 TESTINH-PMREPT-VT1 TESTINH-SWTOPROTN-EQPT CONFINH-SWTOWKG-EQPT CONFINH-USER-SECU READ XINIT-REG-EC1 PROVINIT-REG-GIGE PROVINIT-REG-OC12 PROVINIT-REG-OC192 PROVINIT-REG-OC3 PROVINIT-REG-OC48 PROVINIT-REG-OFA PROVINIT-REG-STS1 PROVINIT-REG-STS12C PROVINIT-REG-STS3C PROVINIT-REG-STS48C PROVINIT-REG-T1 PROVINIT-REG-T3 PROVINIT-REG-VT1 PROVINIT-SYS CONFMK-DIR NETADMINMV-MEM NETADMINOPR-ACO-COM TESTOPR-ALS-OC12 PROVOPR-ALS-OC192 PROVOPR-ALS-OC3 PROVOPR-ALS-OC48 PROVOPR-DISK NETADMINOPR-LPBK-EC1 PROV




OPR-LPBK-OC12 PROVOPR-LPBK-OC192 PROVOPR-LPBK-OC3 PROVOPR-LPBK-OC48 PROVOPR-LPBK-T1 PROVOPR-LPBK-T3 PROVOPR-LPBK-VT1 PROVOPR-PROTNSW-OC12 CONFOPR-PROTNSW-OC192 CONFOPR-PROTNSW-OC3 CONFOPR-PROTNSW-OC48 CONFOPR-PROTNSW-STS1 CONFOPR-PROTNSW-STS12C CONFOPR-PROTNSW-STS3C CONFOPR-PROTNSW-STS48C CONFOPR-SYNCNSW NETADMINREPT-INITZN CONFREPT-STAT READRLS-LPBK-EC1 PROVRLS-LPBK-OC12 PROVRLS-LPBK-OC3 PROVRLS-LPBK-OC48 PROVRLS-LPBK-OC192 PROVRLS-LPBK-T1 PROVRLS-LPBK-T3 PROVRLS-LPBK-VT1 PROVRLS-PROTNSW-OC12 CONFRLS-PROTNSW-OC192 CONFRLS-PROTNSW-OC3 CONFRLS-PROTNSW-OC48 CONFRLS-PROTNSW-STS1 CONFRLS-PROTNSW-STS12C CONFRLS-PROTNSW-STS3C CONFRLS-PROTNSW-STS48C CONFRMV-EQPT NETADMIN




RMV-EC1 PROVRMV-GIGE PROVRMV-OC3 PROVRMV-OC12 PROVRMV-OC48 PROVRMV-OC192 PROVRMV-STS1 PROVRMV-STS3C PROVRMV-STS12C PROVRMV-STS48C PROVRMV-OFA PROVRMV-T1 PROVRMV-T3 PROVRMV-VT1 PROVRPGM-EQPT NETADMINRST-EQPT NETADMINRST-EC1 PROVRST-GIGE PROVRST-OC3 PROVRST-OC12 PROVRST-OC48 PROVRST-OC192 PROVRST-STS1 PROVRST-STS3C PROVRST-STS12C PROVRST-STS48C PROVRST-OFA PROVRST-T1 PROVRST-T3 PROVRST-VT1 PROVRTRV-ALM-ALL READRTRV-ALM-COM READRTRV-ALM-EC1 READRTRV-ALM-EQPT READRTRV-ALM-GIGE READ




RTRV-ALM-OC12 READRTRV-ALM-OC192 READRTRV-ALM-OC3 READRTRV-ALM-OC48 READRTRV-ALM-OFA READRTRV-ALM-STS1 READRTRV-ALM-STS12C READRTRV-ALM-STS3C READRTRV-ALM-STS48C READRTRV-ALM-T1 READRTRV-ALM-T3 READRTRV-ALM-VT1 READRTRV-AO READRTRV-ARPCACHE READRTRV-ATTR-CRSDFLT READRTRV-ATTR-BLSR READRTRV-ATTR-EC1 READRTRV-ATTR-EQPT READRTRV-ATTR-GIGE READRTRV-ATTR-LOG NETADMINRTRV-ATTR-OC12 READRTRV-ATTR-OC192 READRTRV-ATTR-OC3 READRTRV-ATTR-OC48 READRTRV-ATTR-OFA READRTRV-ATTR-SECULOG READ XRTRV-ATTR-STS1 READRTRV-ATTR-STS12C READRTRV-ATTR-STS3C READRTRV-ATTR-STS48C READRTRV-ATTR-T1 READRTRV-ATTR-T3 READRTRV-ATTR-VT1 READRTRV-AUDIT-SECULOG READ XRTRV-BITS READ




RTRV-BLSR-TRC READRTRV-CHAN-BLSR READRTRV-COND-ALL READRTRV-COND-BLSR READRTRV-COND-COM READRTRV-COND-EC1 READRTRV-COND-EQPT READRTRV-COND-GIGE READRTRV-COND-OC12 READRTRV-COND-OC192 READRTRV-COND-OC3 READRTRV-COND-OC48 READRTRV-COND-OFA READRTRV-COND-STS1 READRTRV-COND-STS12C READRTRV-COND-STS3C READRTRV-COND-STS48C READRTRV-COND-T1 READRTRV-COND-T3 READRTRV-COND-VT1 READRTRV-CRS READRTRV-CRS-ALL READRTRV-CRS-GIGE READRTRV-CRS-STS1 READRTRV-CRS-STS12C READRTRV-CRS-STS3C READRTRV-CRS-STS48C READRTRV-CRS-T1 READRTRV-CRS-T3 READRTRV-CRS-VT1 READRTRV-DFLT-SECU READ XRTRV-DISK READRTRV-EC1 READRTRV-EQPT READRTRV-EVC READ




RTRV-FFP-ALL READRTRV-FFP-OC12 READRTRV-FFP-OC192 READRTRV-FFP-OC3 READRTRV-FFP-OC48 READRTRV-FFP-STS1 READRTRV-FFP-TRC READRTRV-GIGE READRTRV-HDR READ1

RTRV-IPCPLDCC READRTRV-IPCPSDCC READRTRV-LCPLDCC READRTRV-LCPSDCC READRTRV-LLLDCC READRTRV-LLSDCC READRTRV-LOG NETADMINRTRV-LPBK-EC1 READRTRV-LPBK-OC3 READRTRV-LPBK-OC12 READRTRV-LPBK-OC48 READRTRV-LPBK-OC192 READRTRV-LPBK-T1 READRTRV-LPBK-T3 READRTRV-LPBK-VT1 READRTRV-MAADDR READRTRV-MAP READRTRV-MOS READRTRV-NE READRTRV-NE-DENIED READRTRV-NE-IPRT READRTRV-NE-SNTP READRTRV-NE-TL1 READRTRV-NE-TRUST READRTRV-NEID READRTRV-NETIF READ




RTRV-NETYPE READRTRV-NSAP READ1

RTRV-OC12 READRTRV-OC192 READRTRV-OC3 READRTRV-OC48 READRTRV-OFA READRTRV-OPTICAL READRTRV-PM-ALL READRTRV-PM-EC1 READRTRV-PM-EVC READRTRV-PM-GIGE READRTRV-PM-OC12 READRTRV-PM-OC192 READRTRV-PM-OC3 READRTRV-PM-OC48 READRTRV-PM-OFA READRTRV-PM-STS1 READRTRV-PM-STS12C READRTRV-PM-STS3C READRTRV-PM-STS48C READRTRV-PM-T1 READRTRV-PM-T3 READRTRV-PM-VT1 READRTRV-PMATTR-ALL READRTRV-PMMODE-EC1 READRTRV-PMMODE-EVC READRTRV-PMMODE-GIGE READRTRV-PMMODE-OC12 READRTRV-PMMODE-OC192 READRTRV-PMMODE-OC3 READRTRV-PMMODE-OC48 READRTRV-PMMODE-OFA READRTRV-PMMODE-STS1 READRTRV-PMMODE-STS12C READ




RTRV-PMMODE-STS3C READRTRV-PMMODE-STS48C READRTRV-PMMODE-T1 READRTRV-PMMODE-T3 READRTRV-PMMODE-VT1 READRTRV-PMSCHED-ALL READRTRV-PMSCHED-EC1 READRTRV-PMSCHED-EVC READRTRV-PMSCHED-GIGE READRTRV-PMSCHED-OC12 READRTRV-PMSCHED-OC192 READRTRV-PMSCHED-OC3 READRTRV-PMSCHED-OC48 READRTRV-PMSCHED-OFA READRTRV-PMSCHED-STS1 READRTRV-PMSCHED-STS12C READRTRV-PMSCHED-STS3C READRTRV-PMSCHED-STS48C READRTRV-PMSCHED-T1 READRTRV-PMSCHED-T3 READRTRV-PMSCHED-VT1 READRTRV-PRMTR-NE READRTRV-PRVG-CMD READ RTRV-PTHTRC-STS1 READRTRV-PTHTRC-STS12C READRTRV-PTHTRC-STS3C READRTRV-PTHTRC-STS48C READRTRV-RFILE READRTRV-RINGMAP READRTRV-SECTRC-EC1 READRTRV-SECTRC-OC12 READRTRV-SECTRC-OC192 READRTRV-SECTRC-OC3 READRTRV-SECTRC-OC48 READRTRV-SECU READ




RTRV-SQLMAP READRTRV-STATUS READ XRTRV-STS1 READRTRV-STS12C READRTRV-STS3C READRTRV-STS48C READRTRV-SYNCN READRTRV-SYNCN-SRC READRTRV-T1 READRTRV-T3 READRTRV-TACC READRTRV-TARP READRTRV-TARPCACHE READRTRV-TARPLDB READRTRV-TH-ALL READRTRV-TH-EC1 READRTRV-TH-EVC READRTRV-TH-GIGE READRTRV-TH-OC12 READRTRV-TH-OC192 READRTRV-TH-OC3 READRTRV-TH-OC48 READRTRV-TH-OFA READRTRV-TH-STS1 READRTRV-TH-STS12C READRTRV-TH-STS3C READRTRV-TH-STS48C READRTRV-TH-T1 READRTRV-TH-T3 READRTRV-TH-VT1 READRTRV-ULCOMPMR READRTRV-ULLDCC READRTRV-ULSDCC READRTRV-USAGE-EQPT READRTRV-USER-SECU READ




RTRV-USER-SESSION READ XRTRV-VT1 READSCHED-PMREPT-ALL TESTSCHED-PMREPT-EC1 TESTSCHED-PMREPT-GIGE TESTSCHED-PMREPT-OC12 TESTSCHED-PMREPT-OC192 TESTSCHED-PMREPT-OC3 TESTSCHED-PMREPT-OC48 TESTSCHED-PMREPT-OFA TESTSCHED-PMREPT-STS1 TESTSCHED-PMREPT-STS12C TESTSCHED-PMREPT-STS3C TESTSCHED-PMREPT-STS48C TESTSCHED-PMREPT-T1 TESTSCHED-PMREPT-T3 TESTSCHED-PMREPT-VT1 TESTSET-ATTR-BLSR PROVSET-ATTR-CRSDFLT PROVSET-ATTR-EC1 PROVSET-ATTR-GIGE PROVSET-ATTR-LOG NETADMINSET-ATTR-OC12 PROVSET-ATTR-OC192 PROVSET-ATTR-OC3 PROVSET-ATTR-OC48 PROVSET-ATTR-OFA PROVSET-ATTR-SECUDFLT READ XSET-ATTR-SECULOG READ XSET-ATTR-STS1 PROVSET-ATTR-STS12C PROVSET-ATTR-STS3C PROVSET-ATTR-STS48C PROVSET-ATTR-T1 PROVSET-ATTR-T3 PROV




SET-ATTR-VT1 PROVSET-PMATTR-ALL NETADMINSET-PMMODE-EC1 PROVSET-PMMODE-GIGE PROVSET-PMMODE-OC12 PROVSET-PMMODE-OC192 PROVSET-PMMODE-OC3 PROVSET-PMMODE-OC48 PROVSET-PMMODE-OFA PROVSET-PMMODE-STS1 PROVSET-PMMODE-STS12C PROVSET-PMMODE-STS3C PROVSET-PMMODE-STS48C PROVSET-PMMODE-T1 PROVSET-PMMODE-T3 PROVSET-PMMODE-VT1 PROVSET-SID NETADMINSET-SYNCN NETADMINSET-TH-EC1 PROV




Response (Error) Codes

3.8 Refer to table 3-G for a list of response (error) codes used in unsuccessful response messages by the system.

SET-TH-GIGE PROVSET-TH-OC12 PROVSET-TH-OC192 PROVSET-TH-OC3 PROVSET-TH-OC48 PROVSET-TH-OFA PROVSET-TH-STS1 PROVSET-TH-STS12C PROVSET-TH-STS3C PROVSET-TH-STS48C PROVSET-TH-T1 PROVSET-TH-T3 PROVSET-TH-VT1 PROVSTA-LOG NETADMINSTP-LOG NETADMINSW-DX-EQPT CONFSW-TOPROTN-EQPT CONFSW-TOWKG-EQPT CONFTEST-LED TESTCANC READ X

[1] TL1 command will complete regardless of the user’s UAP and without requiring the user to be logged in.




Table 3-G. Response (Error) Codes

CODEERROR CATEGORY DEFINITION

ENEQ EQUIPAGE Not EquippedENFE EQUIPAGE Feature Not ProvidedIBEX INPUT Block ExtraICNV INPUT Command Not ValidIDMS INPUT Data MissingIDNC INPUT Data Not ConsistentIDNV INPUT Data Not ValidIDRG INPUT Data Range ErrorIEAE INPUT Entity Already ExistsIENE INPUT Entity Does Not ExistIIAC INPUT Invalid Access Identifier (AID)IICT INPUT Invalid Correlation TagIIFM INPUT Invalid Data FormatIISP INPUT Invalid Syntax or PunctuationIITA INPUT Invalid Target IdentifierIPEX INPUT Parameter ExtraIPMS INPUT Parameter MissingIPNC INPUT Parameter Not ConsistentIPNV INPUT Parameter Not ValidITSN INPUT Invalid/Inactive Test Session NumberPICC PRIVILEGE Invalid Command CodePIUI PRIVILEGE Illegal User IdentityPLNA PRIVILEGE Login Not ActiveRTBY RESOURCE Requested Tap BusyRTEN RESOURCE Requested Tab Does Not ExistSAAL STATUS Already Allowed



Command Parser Error Codes

3.9 Refer to table 3-H for a list of response (error) codes used in unsuccessful response message by the system’s Command Parser when a command cannot successfully parsed.

SADC STATUS Already DisconnectedSAIN STATUS Already InhibitedSAIS STATUS Already In ServiceSAOP STATUS Already OperatedSAOS STATUS Already Out of ServiceSARB STATUS All Resources BusySARL STATUS Already ReleasedSCAT STATUS Circuit is Already Connected to Another TapSCSN STATUS Invalid Command SequenceSDBE STATUS Internal Database ErrorSDNC STATUS Data Not ConsistentSNCC STATUS Not Cross-connectedSNOS STATUS Not currently Out of ServiceSNVS STATUS Not in Valid StateSROF STATUS Requested Operation FailedSRQN STATUS Invalid RequestSRSD STATUS Remote Session DroppedSSRD STATUS Switch Request DeniedSSRE STATUS System Resources ExceededSTTI STATUS Tap Idle

Table 3-G. Response (Error) Codes (cont.)




Table 3-H. Command Parser Error Codes


IBEX INPUT Block ExtraICNV INPUT Command Not ValidIDNV INPUT Data Not ValidIDRG INPUT Data Range ErrorIIAC INPUT Invalid Access Identifier (AID)IICT INPUT Invalid Correlation TagIISP INPUT Invalid Syntax or PunctuationIITA INPUT Invalid Target IdentifierIPEX INPUT Parameter ExtraIPMS INPUT Parameter MissingIPNV INPUT Parameter Not ValidPICC PRIVILEGE Invalid Command CodeSARB STATUS All Resources BusySDBE STATUS Internal Database ErrorSROF STATUS Requested Operation FailedSSRE STATUS System Resources Exceeded



4. SECURITY

4.1 TL1 commands are used to control the 1677 SONET Link and to optimize its operation and maintenance. Unauthorized use of these commands can degrade or completely destroy the functionality of the system. Security is concerned with two major sources of inappropriate use of system commands:

• Intruders who may maliciously take control of the system with the intent of damaging or disabling the system

• Authorized users who use commands with which they are either unfamiliar or that are outside their scope of responsibility

4.2 System security, when properly set up, effectively prevents unauthorized users from accessing system commands, responses, and messages. This includes both preventing intruders from accessing the system and restricting authorized users from using TL1 commands that are outside their scope of responsibility.

4.3 The security scheme is based on setting up security values to restrict access to the system and its resources. This section describes how the system administrator uses security measures to proactively establish and maintain local security policies and practices.

4.4 All new systems are shipped with default security values. Before customizing the security scheme by altering default values, the system administrator should read this section completely. Major topics include the following:

• Controlling system access

• Controlling access to system resources

• Obtaining security audit information

Controlling System Access

4.5 The 1677 SONET Link can be accessed locally via the console interface or remotely via either telnet or raw interfaces. System access requires every user to correctly enter the ACT-USER command using a valid UID and its corresponding PID within a preset number of attempts.

4.6 To prevent an unauthorized bystander from viewing a user's PID, the TL1 command echoes (as the user types) a series of asterisks (******) in place of the PID as it is typed.



4.7 Remote access to the 1677 SONET Link does not employ an encrypted data path on the external link between the user and the CID port on the system. It is possible that the ACT-USER command, including the UID and PID, may be discovered during a legitimate, authorized attempt to log into the system.

4.8 When a login is attempted, the system verifies that the command was entered using the correct syntax and that the UID/PID combination matches encrypted records set up in the internal security database. If the UID and PID are acceptable, the user can access the system. A provisionable warning message displays with the date and time of the last successful session. The warning message is created and edited using the SET-ATTR-SECULOG command. An example of a typical message is:

Warning: This system is restricted to authorized users for business purposes. Unauthorized access is a violation of the law. This service is being monitored for administrative and security reasons. By proceeding, you consent to this monitoring.

4.9 If the UID and PID are not acceptable, the system denies access. The response to a denied login intentionally provides no additional information to the user. This prevents an intruder from discovering the ACT-USER command syntax, then repeatedly attempting login until a valid UID and corresponding PID is discovered.

Entering New Users

4.10 The system security administrator sets up and controls the security database. The ENT-USER command is used to establish a security record for each person or network entity (such as an operations support system) that is allowed to access the system.



4.11 A UID, a PID, and a User Access Level (UAL) are required for every user. Users must not share a UID/PID. (The UAL is described in detail later in this section.)

The UID must be unique within the system and must be at least three characters and no more than 32 characters.

The PID is not required to be unique in the system. This means that two or more users can have the same password at the same time. The system can be configured to require differing degrees of PID complexity. The default configuration is to not require a non-alphabetic or special character in the PID. However, the system security administrator may set options to require a PID to contain at least one numeric character or at least one numeric and special character in addition to the normal alphabetic characters.

The minimum PID length is six characters by default but the system security operator may set a larger minimum length. The maximum PID length is 32 characters.

4.12 The user-security database is limited to 300 users. New systems are shipped with a pre-existing user: administrator. Thus, a new system can accommodate 299 new UIDs.

User Aging

4.13 The system uses UID aging to prevent inactive users from logging into the system after a period of disuse. This feature is enabled by setting the DISUSER parameter of the ED-SECU command to a nonzero number. This system-wide parameter applies to all users. This number specifies the number of days in which there is no login for a user. If DISUSER is set to 180 days, a UID is disabled after about 6 months of inactivity. If DISUSER is set to 0, UID aging is not used within the system and UIDs are never disabled because of inactivity.

Password Aging

4.14 The system uses PID aging to require users to change their passwords periodically. This feature is enabled by setting the Password Aging Interval (PAGE) parameter of the ED-SECU command to a nonzero number. This system-wide parameter applies to all users. This number specifies the number of days that a user's PID is aged before the system prompts the user to change to a new password. The user must use the ED-PID command to enter a new PID before the session in which the user receives this prompt is terminated.



4.15 The system tracks the number of minutes since the PID was last changed. The system operator may enforce a minimum time. The PCHN parameter of the ED-SECU command specifies the number of minutes.

4.16 If a user's PID is deactivated by DISUSER, the user's account can only be reactivated by the system security administrator.

User Control of Password

4.17 Authorized users can change their own passwords, using the ED-PID command, at any time before the passwords expire. To change the password, the user must be logged into the system using the current UID and PID. To change the PID, the user must know the UID and the old PID. This prevents an unauthorized person from inappropriately changing the currently logged-in user's password.

The command syntax is:

ED-PID:[TID]:[UID]:[CTAG]::OLDPID,NEWPID;

4.18 To prevent PID discovery through trial and error, PIDs must meet the requirements described in section 4.11.

Setting Lockout for Unsuccessful Login Attempts

4.19 To deter repeated attempts to breach login security, the system restricts the number of unsuccessful logins from a particular interface and a particular UID/PID. When an unsuccessful login attempt is detected, the system increments a counter for both the interface and, if the UID is valid,f or the UID. When the MXINV unsuccessful login limit is reached, the remote interface is disconnected and the originating IP address is added to the denied hosts table for DURAL seconds. Any subsequent attempts to originate a connection fromthat IP address are automatically rejected.

4.20 The MXINV and DURAL parameters are specified in the SET-ATTR-SECUDFLT command. The default value and range for MXINV are three attempts, with a minimum of 0 and a maximum of 999. Setting the MXINV parameter to 0 disables this functionality. The default value and range for DURAL are five seconds with a minimum of one second and a maximum of 999 seconds. The current value for MXINV and DURAL can be obtained with the RTRV-DFLT-SECU command. If the unsuccessful login attempts are originating locally, the system withholds the login prompt for DURAL seconds. Any successful login automatically resets the counters.



4.21 To deter repeated attempts to breach login security for a particular user, the system will automatically disable a UID/PID for SPERIOD days after SUSPEND number of consecutive login failures. The SUSPEND and SPERIOD parameters are specified int he ED-SECU command. The default value and range for SUSPEND are 10 attempts with a minimum of 0 and a maximum of 999. Setting the SUSPEND parameter to 0 disables this functionality. The default value and range for SPERIOD are one day with a minimum of one day and a maximum of 999 days. The RTRV-SECU command can be used to retrieve the current values for SUSPEND and SPERIOD.

4.22 When a UID/PID is suspended, the system continues to issue the login prompts.

Automatic Logout

4.23 The system automatically logs out inactive users after a specified period of inactivity. Inactivity is defined as no user input. The TMOUT parameter of the SET-ATTR-SECUDFLT command specifies whether the user is to be automatically logged out when the inactivity interval (period which triggers log out) expires (20 minutes is the default; 0 indicates disabled).

Controlling Access to System Resources

4.24 An important part of system security involves restricting the commands that users are allowed to execute, the output responses they are allowed to view, and the system messages they are allowed to receive.

4.25 The following paragraphs describe system command security, the considerations for assigning privileges and categories, and the tasks required to accomplish resource control.

System Control of Command Use

4.26 The Permission filter compares User Access Levels (UALs) assigned to commands with UALs assigned to users. If a user enters a restricted command, the comparison fails and the command is denied. This control is established through the UAP parameter of the ENT-USER-SECU and ED-USER-SECU commands.



Privilege and Category Assignments

4.27 Command usage is controlled in two ways:

• By assigning access privileges for each command. These assignments restrict the command to certain individuals.

• By assigning access privileges for each user. These assignments establish individual authorization levels.

4.28 The following criteria are used to determine the security mix for a typical system:

• Determine command system-wide impact.

• Decide which commands users are allowed to issue.

4.29 The security mix allows a wide degree of control over command use. If the workforce is relatively small and experienced with job assignments broadly defined, only a few functional categories and privilege levels may need to be defined. However, if individual work assignments are specialized, and workforce personnel have varying degrees of experience and qualifications, a more highly structured system of command categories and privilege levels may be needed.

4.30 The system administrator UID defaults allow access to commands needed to establish user-security database records and change parameters affecting system security. In the absence of a system security administrator account, commands that directly affect system security cannot be executed.

Establishing User Privileges and Functional Categories

4.31 To set or edit individual user command privileges, the UAP parameter of the ENT-USER-SECU and ED-USER-SECU commands is used. Values for this parameter should correlate with the structure established for assigning command privilege requirements.

Obtaining Security Audit Information

4.32 The system maintains two security related logs. The two logs are the security and audit logs. Access to the security log is restricted to UIDs with security administrator privileges.



4.33 The security log records security related events such as:

• Successful logins

• Login failures

• Changes to trusted and denied host tables

• Changes to the system clock

• Creation/deletion of UIDs

4.34 The audit log records all commands entered into the system. Along with the command entered, the audit log also records for each command the following information:

• The UID of the user entering the command

• The date and time the command was entered

4.35 Sensitive security related information such as the PID entered in the ACT-USER, ED-USER-SECU, and ED-PID commands is not recorded directly in the audit log. Instead, the audit log substitutes the field contents with a predetermined number of asterisk characters. This prevents the discovery of the user’s PID by reviewing the contents of the audit log.

4.36 The Audit Secure Log is read-only. It cannot be edited, deleted, or backed up and restored. This prevents anyone, including the security administrator, from tampering with the data in the log. The RTRV-AUDIT-SECULOG command can be used to retrieve information from the log.



5. PERFORMANCE MONITORING

5.1 The system uses internal equipment monitoring to detect faults and card failures, and to issue appropriate alarms, alerting users of troubles. Equipment monitoring does not, however, detect deteriorating conditions that could lead to service-affecting failures. Performance Monitoring (PM) provides this important function. PM continuously monitors selected parameters of incoming traffic, detects errors, counts the detected errors, and reports daily error accumulations and at 15-minute intervals. PM also compares the error counts with user-defined thresholds and issues a REPT^EVT (report event) message when any error count crosses its defined threshold.

5.2 The system performs PM on the following facility types:

• DS3

• OC-3

• OC-12

• OC-48

• OC-192

• STS-1

• STS-3c

• STS-12c

• STS-48c

• T1

• VT1.5

• EC1

• EDFA (OFA)

• GIGE

5.3 The system monitors and reports several performance parameters that let the user distinguish between a system internal failure and an incoming facility failure. Refer to the Monitored Parameters subsection in this section for lists and definitions of the parameters monitored for each facility type.



5.4 SET-TH-rr commands (where rr is the facility type: OC3, OC12, OC48, OC192, STS1, STS3C, STS12C, STS48C, OC192, T3, T1, VT1, EC1, OFA, or GIGE) are used to define performance parameter thresholds for each circuit. The user can select the parameter type and threshold level, and initialize the error count register on a daily or 15-minute basis. These user-defined thresholds are stored in the circuit-provisioning database. RTRV-TH-rr commands cause the defined parameter thresholds to display on the Video Display Terminal (VDT).

Storage Registers

5.5 Refer to table 5-A for a list of the types and numbers of storage registers provided for each PM parameter monitored.

Register Initialization

5.6 Current registers for 15-minute and 1-day counts accumulate error and event counts. When the count in any of these registers reaches a maximum value, the register remains full until either it is reset or the value is transferred to the Previous register. Current registers initialize in the following circumstances:

• Automatically every 15 minutes or 1 day (24 hours) (register value set to 0)

• Automatically upon initialization of subsystem where Current registers reside (register value set to 0)

• Manually using the INIT-REG-rr command at any time (register value set to any integer from 0 to 900 for registers that count in seconds, 0 to 65535 for all other registers)

5.7 The INIT-REG-rr commands let the user reset selected error count registers to a desired value (default=0). The register's value then increments from that value as new errors are counted. When the end of the time period for the register (1-DAY or 15-MIN) is reached, its count is automatically initialized to 0.

Table 5-A. Number of Registers for Each PM Parameter MonitoredNUMBER OF REGISTERS PER MONITORED PARAMETER

REGISTER TYPE 15-MINUTE 1-DAYCurrent 1 1Previous 1 1Recent 31 0



Validity Flags

5.8 Each register marks accumulation data with an associated validity (VLDTY) flag. The system sets the VLDTY flag to one of the following values:

• ADJ - Adjusted, data has been manually adjusted or initialized

• NA - Not available, data not available during entire accumulation period

• OFF - Data accumulation turned off for the entire time period

• LONG - Data accumulated over longer time than the indicated time period

• PRTL - Partial, Data accumulated over some portion of the time period

• COMPL - Complete, data accumulated during the entire accumulation period

5.9 The ADJ validity flag is set if the PM data was adjusted or initialized using an INIT-REG-rr command.

5.10 The NA validity flag is set if monitoring of the corresponding parameter is prevented for the entire accumulation period due to equipment failure or equipment initialization.

5.11 The OFF validity flag is set if PM collection is disabled for the entire collection period.

5.12 The LONG validity flag is set if the time of day is changed and it results in the current data collection period to be longer than the normal accumulation period by 10 seconds or more.



5.13 The PRTL validity flag is set on facilities if the PM data is collected only for part of the accumulation period due to:

• Failure of the I/O modules.

• Failover (lasting more than 10 seconds) of SSC module.

• Presence of a higher level defect or failure.

• Initialization of the I/O module starts during the accumulation period.

• Initialization of the I/O module or the active SSC completes during the accumulation period.

• PM collection is disabled for part of the accumulation period and some data is available.

• The Time of Day is changed and it results in the current data collection to be shorter than the normal accumulation period by 10 seconds or more.

5.14 The COMPL validity flag is set under all other conditions. It indicates that data was accumulated over the entire period.

5.15 The order of priority of the validity flags is ADJ, PRTL, and LONG in descending order. Only ADJ, PRTL, and LONG have hierarchy and each of these is mutually exclusive to OFF, NA, COMPL flags.

Threshold Registers

5.16 Two threshold registers are provided for each parameter monitored; a 15-minute threshold register and a 1-day threshold register. Threshold registers are supported for all facility PM parameters.

5.17 Use the SET-TH-rr command to set threshold register values and use RTRV-TH-rr to retrieve them. Minimum threshold register size is equal to the corresponding storage register size.

Threshold Crossing Alerts

5.18 A threshold value is crossed when a current value register reaches or exceeds the set value in the corresponding threshold register. When a threshold crossing is recognized, Threshold Crossing Alerts (TCAs) are generated using REPT^EVT messages.



5.19 During an accumulation period, only one TCA is sent for each threshold setting on a Current register, unless the Current register is reset. In that case, the reset Current register must again reach or exceed its value before another TCA is sent.

5.20 A threshold is not crossed (and no TCA is generated) if a register value that has reached a threshold value is reduced to less than the threshold value when unavailability is declared.

5.21 Setting a threshold register value to zero inhibits the corresponding TCA from being generated or reported. This effectively disables that TCA for that entity.

Scheduling Daily PM Report

5.22 The SCHED-PMREPT command is used to enable automatic printing of the daily PM report; however, use of this command does not enable the report itself. Scheduled reports include all DS3, DS1, OC-3, OC-12, OC-48, OC-192, STS-1, STS-3c, STS-12c, STS-48c, VT1.5, EC1, OFA, and GIGE PM data. The daily PM registers record system PM data from midnight to midnight. If the PMREPT is enabled, the daily PM report automatically prints at the time specified in the REPTSTATM parameter (the default is next reporting time). To schedule printing at a time other than midnight, enter the desired hour and minute in the REPTSTATM field. The start and end times of the surveillance period, however, cannot be changed.

5.23 The RTRV-PMSCHED-ALL command displays the current PM mode status and the designated time of the daily PM report defined by the SCHED-PMREPT-ALL command.

Suppressing Scheduled PM Reporting

5.24 The INH-PMREPT command can be used to suppress printing of the daily PM report. The stats remain in storage for 32 15-MIN intervals, then rolled over into the 1-DAY stats. It can then be retrieved using the RTRV-PM-rr command. When printing of the daily PM report is suppressed, a message appears on the VDT at midnight to indicate the report will not print.

Retrieving Selective PM Data

5.25 The RTRV-PM-rr commands are used to retrieve PM data on selected ports. These commands are used to let the user receive PM reports on specified ports immediately.



5.26 RTRV-PM-rr can be used to automatically execute and display 15-minute and daily reports as follows:

• Immediately or at a designated date and time

• At a single port, range of ports, or all ports

5.27 The user can also request up to one of the preceding 24-hour PM report or up to 32 of the preceding 15-minute reports.

Monitored Parameters

Parameters monitored by the system (MONTYPEs) vary according to facility.

• For a list of DS3 PM parameters, refer to table 5-B.

• For a list of OC-3 PM parameters, refer to table 5-C.

• For a list of OC-12 PM parameters, refer to table 5-D.

• For a list of OC-48 PM parameters, refer to table 5-E.

• For a list of OC-192 PM parameters, refer to table 5-F.

• For a list of STS-1 PM parameters, refer to table 5-G.

• For a list of STS-3c PM parameters, refer to table 5-H.

• For a list of STS-12c PM parameters, refer to table 5-I.

• For a list of STS-48c PM parameters, refer to table 5-J.

• For a list of VT1.5 PM parameters, refer to table 5-K.

• For a list of EDFA PM parameters, refer to table 5-L.

• For a list of GIGE parameters, refer to table 5-M.

• For a list of EC1 PM parameters, refer to table 5-N.

• For a list of T1 PM parameters, refer to table 5-O.

For each facility type and MONTYPE there are default and maximum threshold levels. Refer to the 1677 SONET Link Commands and Messages manual (PN 3EM13852AD).



Table 5-B. DS3 PM ParametersMONTYPE PARAMETER DEFINITIONNear-End Line PM Parameters for DS3CV-L Coding ViolationsES-L Errored Second Count ESA-L Errored Seconds Type AESB-L Errored Seconds Type BLOSS-L Loss of Signal Seconds SES-L Severely Errored Seconds Near-End Path PM Parameters for DS3 or DS3 in SONET PathAISS-P AIS Second CountCVP-P Coding ViolationsESP-P Errored SecondsESAP-P Errored Seconds Type AESBP-P Errored Seconds Type BFC-P Failure CountsSAS-P SEF/AIS SecondsSESP-P Severely Errored SecondsUASP-P Unavailable SecondsNear-End CP-Bit Path PM Parameters for DS3CVCP-P Coding ViolationsESCP-P Errored SecondsESACP-P Errored Seconds Type AESBCP-P Errored Seconds Type BSESCP-P Severely Errored SecondsUASCP-P Unavailable SecondsFar-End CP-Bit Path PM Parameters for DS3CVCP-PFE Coding ViolationsESACP-PFE Errored Seconds Type AESBCP-PFE Errored Seconds Type BESCP-PFE Errored SecondsFCCP-PFE Failure CountsSASCP-PFE SEF/AIS SecondsSESCP-PFE Severely Errored SecondsUASCP-PFE Unavailable Seconds



Table 5-C. OC-3 PM ParametersMONTYPE PARAMETER DEFINITIONNear-End Section PM Parameters for OC-3CVS Coding ViolationsESS Error Second CountSEFS-S Severely Errored Frame Seconds SESS Severely Errored SecondsNear-End Line PM Parameters for OC-3CVL Coding Violations ESL Errored Seconds FC-L Failure CountPSC-L Protection Switching CountSESL Severely Errored Seconds UASL Unavailable Seconds Far-End Line PM Parameters for OC-3CV-LFE Coding ViolationsES-LFE Errored SecondsFC-LFE Failure CountSES-LFE Severely Errored Seconds UAS-LFE Unavailable Seconds



Table 5-D. OC-12 PM ParametersMONTYPE PARAMETER DEFINITIONNear-End Section PM Parameters for OC-12CVS Coding ViolationsESS Error Second CountSEFS-S Severely Errored Frame Seconds SESS Severely Errored SecondsNear-End Line PM Parameters for OC-12CVL Coding Violations ESL Errored Seconds FC-L Failure CountPSC-L Protection Switching CountSESL Severely Errored Seconds UASL Unavailable Seconds Far-End Line PM Parameters for OC-12CV-LFE Coding Violations ES-LFE Errored Seconds FC-LFE Failure CountSES-LFE Severely Errored Seconds UAS-LFE Unavailable Seconds



Table 5-E. OC-48 PM ParametersMONTYPE PARAMETER DEFINITIONNear-End Section PM Parameters for OC-48CVS Coding ViolationsESS Error Second CountSEFS-S Severely Errored Frame Seconds SESS Severely Errored SecondsNear-End Line PM Parameters for OC-48CVL Coding Violations ESL Errored Seconds FC-L Failure CountsPSC-L Protection Switching CountPSCP-L Protection Switching Count on BLSR Protection CapacityPSCW-L Protection Switching Count on BLSR Working CapacitySESL Severely Errored Seconds UASL Unavailable Seconds Far-End Line PM Parameters for OC-48CV-LFE Coding Violations ES-LFE Errored Seconds FC-LFE Failure CountsSES-LFE Severely Errored Seconds UAS-LFE Unavailable Seconds Optical PM Parameters for OC-48 (supported for OC-48 Drop and Continue cards or OC-48 cards that support OPM (Optical Power Monitor))LBCN Laser Bias Current NormalizedLSRTEMP Laser TemperatureOPRN Optical Power Receive NormalizedOPTN Optical Power Transmit Normalized



Table 5-F. OC-192 PM ParametersMONTYPE PARAMETER DEFINITIONNear-End Section PM Parameters for OC-192CVS Coding ViolationsESS Error Second CountSEFS-S Severely Errored Frame Seconds SESS Severely Errored SecondsNear-End Line PM Parameters for OC-192CVL Coding Violations ESL Errored Seconds FC-L Failure CountsPSC-L Protection Switching CountPSCP-L Protection Switching Count on BLSR Protection CapacityPSCW-L Protection Switching Count on BLSR Working CapacitySESL Severely Errored Seconds UASL Unavailable Seconds Far-End Line PM Parameters for OC-192CV-LFE Coding Violations ES-LFE Errored Seconds FC-LFE Failure CountsSES-LFE Severely Errored Seconds UAS-LFE Unavailable Seconds Optical PM Parameters for OC-192 (supported for OC-192 Drop and Continue cards or OC-192 cards that support OPM (Optical Power Monitor))LBCN Laser Bias Current NormalizedLSRTEMP Laser TemperatureOPRN Optical Power Receive NormalizedOPTN Optical Power Transmit Normalized



Table 5-G. STS-1 PM ParametersMONTYPE PARAMETER DEFINITIONNear-End Path PM Parameters for STS1CV-P Coding ViolationsES-P Errored SecondsFC-P Failure CountSES-P Severely Errored SecondsUAS-P Unavailable SecondsFar-End Path PM Parameters for STS1CV-PFE Coding ViolationsES-PFE Errored SecondsFC-PFE Failure CountSES-PFE Severely Errored SecondsUAS-PFE Unavailable Seconds

Table 5-H. STS-3c PM ParametersMONTYPE PARAMETER DEFINITIONNear-End Path PM Parameters for STS-3cCV-P Coding Violations ES-P Errored Seconds FC-P Failure CountSES-P Severely Errored Seconds UAS-P Unavailable Seconds Far-End Path PM Parameters for STS-3cCV-PFE Coding Violations ES-PFE Errored Seconds FC-PFE Failure CountSES-PFE Severely Errored Seconds UAS-PFE Unavailable Seconds



Table 5-I. STS-12c PM ParametersMONTYPE PARAMETER DEFINITIONNear-End Path PM Parameters for STS-12cCV-P Coding Violations ES-P Errored Seconds FC-P Failure CountSES-P Severely Errored Seconds UAS-P Unavailable SecondsFar-End Path PM Parameters for STS-12cCV-PFE Coding ViolationsES-PFE Errored SecondsFC-PFE Failure CountSES-PFE Severely Errored SecondsUAS-PFE Unavailable Seconds

Table 5-J. STS-48c PM ParametersMONTYPE PARAMETER DEFINITIONNear-End Path PM Parameters for STS-48cCV-P Coding ViolationsES-P Errored SecondsFC-P Failure CountSES-P Severely Errored SecondsUAS-P Unavailable SecondsFar-End Path PM Parameters for STS-48cCV-PFE Coding ViolationsES-PFE Errored SecondsFC-PFE Failure CountSES-PFE Severely Errored SecondsUAS-PFE Unavailable Seconds



Table 5-K. VT1.5 PM ParametersMONTYPE PARAMETER DEFINITIONNear-End Path PM Parameters for VT1.5CV-V Coding ViolationsES-V Errored SecondsFC-V Failure CountsSES-V Severely Errored SecondsUAS-V Unavailable SecondsFar-End Path PM Parameters for VT1.5CV-VFE Coding ViolationsES-VFE Errored SecondsFC-VFE Failure CountsSES-VFE Severely Errored SecondsUAS-VFE Unavailable Seconds

Table 5-L. EDFA (OFA) PM ParametersMONTYPE PARAMETER DEFINITIONOptical PM ParametersLBCN Laser Bias Current NormalizedLSRTEMP Laser TemperatureOPRN Optical Power Receive NormalizedOPTN Optical Power Transmit Normalized

Table 5-M. GIGE PM ParametersMONTYPE PARAMETER DEFINITIONETH-FCS Ethernet Frame Checksum Errors ReceivedETH-FLME Ethernet Frames Lost Due to MAC Error (Receive)ETH-FRAG Ethernet Fragments ReceivedETH-JABB Ethernet Jabbers ReceivedETH-LENERR Ethernet Length ErrorsETH-PAUSETX Ethernet Pause Frame Transmit CountETH-SYMERR Ethernet Receive Symbol ErrorsETH-SYSERR Ethernet Transmit System Errors



Table 5-N. EC1 PM ParametersMONTYPE PARAMETER DEFINITIONNear-End Section PM Parameters for EC1CVS Coding ViolationsESS Errored SecondsSEFS-S Severely Errored Frame SecondsSESS Severely Errored SecondsNear-End Line PM Parameters for EC1CVL Coding ViolationsESL Errored SecondsFC-L Failure CountSESL Severely Errored SecondsUASL Unavailable SecondsFar-End Line PM Parameters for EC1CV-LFE Coding ViolationsES-LFE Errored SecondsFC-LFE Failure CountSES-LFE Severely Errored SecondsUAS-LFE Unavailable Seconds



Table 5-O. T1 PM ParametersMONTYPE PARAMETER DEFINITIONNear-End Path PM Parameters for T1AISS-P AIS SecondsCV-P Coding ViolationsESA-P Errored Seconds Type AESB-P Errored Seconds Type BESP Errored Seconds FC-P Failure CountsSAS-P SEF/AIS SecondsSES-P Severely Errored SecondsUAS-P Unavailable SecondsFar-End Path PM Parameters for T1CSS-PFE Controlled Slip SecondsCV-PFE Coding ViolationsES-PFE Errored SecondsESA-PFE Errored Seconds Type AESB-PFE Errored Seconds Type BFC-PFE Failure CountsSEFS-PFE Severely Errored Frame SecondsSES-PFE Severely Errored SecondsUAS-PFE Unavailable SecondsFar-End Line PM Parameters for T1ES-LFE Errored Seconds



6. TEST ACCESS

6.1 Test access allows for the monitoring, injection, and isolation of signals to isolate facility and/or equipment faults. The user can assign any DS3, DS1, VT1, STS-1, STS-3c, STS-12c, or STS-48c port to function as a test access Facility Access Digroup (FAD) to monitor incoming or outgoing DS3, DS1, VT1, STS-1, STS-3c, STS-12c, or STS-48c signals. Two signals are assigned as FAD A and FAD B to form a Test Access Port Pair (TAPP). Restrictions are as follows:

When a port is defined as a test access port (TACC=Y), the two ports identified by AID and TADB are both provisioned as a Test Access Port Pair (TAPP). A TAPP does not have to be a sequential pair of ports. When using ENT-rr (where ‘rr’ is T3, T1, VT1, STS1, STS3C, STS12C, or STS48C) to provision a TAPP, TADB must be specified. The provisioning parameters are applied to both AID and TADB. If the TADB port is already provisioned, the command is denied.

• The two ports of a T1 test access port pair must reside in the same T3.

• The two ports of a VT1 test access port pair must be within the same STS-1.

6.2 The Test Access Path (TAP) can be manipulated locally or remotely through software control. The system acts as a Digital Test Access Unit (DTAU) to a Generic Test System (GTS). The GTS uses a Remote Test Unit (RTU) to interface through the TAP to the system's TAPP. The system supports monitor, split, and loop test access connections.

6.3 The ENT-rr or ED-rr command is used to assign any two ports as a TAPP (FAD A and FAD B) by manually provisioning the FAD A parameters. The CONN-TACC-rr command is then used to establish a test access connection to probe the cross-connection established between two other ports or another standalone port utilizing the TAPP ports for the test access path. The Equipment side (AID) and Facility side (AID1) ports of the cross-connection are defined in the CONN-TACC-rr TL1 command.

6.4 The CONN-TACC-rr command is used to set the test mode to monitor, split, or loop. The CHG-ACCMD-rr command is used to change the test access mode to a different mode at a later time. The RTRV-TACC command is used to retrieve information on configured test access ports.



Monitor Connections

6.5 Monitor connections establish a bridged connection with a DS3, DS1, VT1, STS-1, STS-3c, STS-12c, or STS-48c circuit, but normal signal transmission continues with the test access connection transparent to the signal. The incoming signal passes through the designated port and the assigned TAP simultaneously, and the unused direction of the test port automatically terminates.

6.6 Monitor connections are not service affecting.

6.7 Monitor connections can be provisioned when the test access connection is established using CONN-TACC-rr, or it can be changed using CHG-ACCMD-rr. There are three monitor test modes (MD):

1. MONE (monitor equipment side): Connects the equipment-side transmission path (A-side path) to FAD A or TAD A. See figure 6-1.

2. MONF (monitor facility side): Connects the facility-side transmission path (B-side path) to FAD A or TAD A. See figure 6-2.

3. MONEF (monitor equipment and facility sides): Connects the equipment-side path (A-side path) to FAD A or TAD A and the facility-side path (B-side path) to FAD B or TAD B. See figure 6-3.

Figure 6-1. MONE Test Access Connection

FACILITY SIDE

PORT

E

EQUIPMENT SIDE

PORT

F

TEST ACCESS PORT

A SIDE

B SIDE

FAD A FAD B

ORTAD A

ORTAD B

677-0093-1032003



Split Connections

6.8 Split connections separate the connection between a specified test port and the targeted port. Split connections are service affecting.

Figure 6-2. MONF Test Access Connection

Figure 6-3. MONEF Test Access Connection

FACILITY SIDE

PORT

E

EQUIPMENT SIDE

PORT

F

TEST ACCESS PORT

A SIDE

B SIDE

FAD A FAD BORTAD A

ORTAD B

677-0094-1032003

FACILITY SIDE

PORT

E

EQUIPMENT SIDE

PORT

F

TEST ACCESS PORT

A SIDE

B SIDE

677-0095-1

032003

FAD A FAD BOR

TAD A

OR

TAD B



6.9 Split connections can be established or changed using CONN-TACC-rr or CHG-ACCMD-rr. There are five split test modes (MD) listed below:

1. SPLTA (split A side): Splits the equipment-side transmission path (A-side path) and routes it into and out of FAD A or TAD A. See figure 6-4.

2. SPLTB (split B side): Splits the facility-side transmission path (B-side path) and routes it into and out of a FAD A or TAD A. See figure 6-5.

3. SPLTE (split equipment side): Provides a full-duplex connection between FAD A or TAD A and the equipment-side port. If the facility-side port is connected to the equipment-side port, the A-side and B-side paths are split, and a keep-alive signal is inserted into the outgoing facility-side signal, and the incoming facility-side signal is terminated. See figure 6-6.

4. SPLTF (split facility side): Provides a full-duplex connection between FAD A or TAD A and the facility-side port. The A-side and B-side paths of the facility-side port are split, and a keep-alive signal is inserted into the outgoing equipment-side signal, and the incoming equipment-side signal is terminated. See figure 6-7.

5. SPLTEF (split equipment and facility sides): Provides a full-duplex connection between the equipment-side port and FAD A or TAD A and a full-duplex connection between the facility-side port and FAD B or TAD B. See figure 6-8.

6.10 The following Keep Alive Signals are supported for SPLTE and SPLTF connections:

– AIS-V for VT1 ports

– Unframed Quasi-Random Signal (QRS) for DS1 ports

– AIS-P for STS1 ports

– Idle signal for T3 ports



Figure 6-4. SPLTA Test Access Connection

Figure 6-5. SPLTB Test Access Connection

Figure 6-6. SPLTE Test Access Connection

FACILITY SIDE

PORTE

EQUIPMENT SIDE

PORTF

TEST ACCESS PORT

A SIDE

B SIDE

677-0096-1031005

FAD A FAD BOR

TAD AOR

TAD B

FACILITY SIDE

PORT

E

EQUIPMENT SIDE

PORT

F

TEST ACCESS PORT

A SIDE

B SIDE

677-0097-1032003

FAD A FAD BOR

TAD AORTAD B

FACILITY SIDE

PORT

E

EQUIPMENT SIDE

PORT

F

TEST ACCESS PORT

A SIDE

B SIDE

677-0098-1032003

*KAS= KEEP ALIVE SIGNAL

KAS*

FAD A FAD B

ORTAD A

ORTAD B



Loop Connections

6.11 Loop connections route the incoming signal back to its output and monitors the looped signal with FAD A or TAD A. Loop connections are service affecting.

Figure 6-7. SPLTF Test Access Connection

Figure 6-8. SPLTEF Test Access Connection

FACILITY SIDE

PORT

F

EQUIPMENT SIDE

PORT

E

TEST ACCESS PORT

A SIDE

B SIDE

677-0099-1

*KAS

032003*KAS= KEEP ALIVE SIGNAL

FAD A FAD B

ORTAD A

ORTAD B

FACILITY SIDE

PORT

E

EQUIPMENT SIDE

PORT

F

TEST ACCESS PORT

A SIDE

B SIDE

677-0100-1032003

FAD A FAD BOR

TAD AOR

TAD B



6.12 Loop connections can be established or changed using CONN-TACC-rr or CHG-ACCMD-rr. There are two loop test modes (MD):

1. LOOPE (loop equipment-side): Loops the equipment-side incoming signal to its output and monitors the looped signal with FAD A or TAD A. If the facility-side port is connected to the equipment-side port, the A-side and B-side paths are split, and a keep-alive signal is inserted into the outgoing facility-side signal, and the incoming facility-side signal is terminated. See figure 6-9.

2. LOOPF (loop facility-side): Loops the facility-side incoming signal to its output and monitors the looped signal with FAD A or TAD A. The A-side and B-side paths of the facility-side port are split, and a keep-alive signal is inserted into the outgoing equipment-side signal, and the incoming equipment-side signal is terminated. See figure 6-10.

6.13 The following Keep Alive Signals are supported for LOOPE and LOOPF connections:

– AIS-V for VT1 ports

– Unframed Quasi-Random Signal (QRS) for DS1 ports

– AIS-P for STS1 ports

– Idle signal for T3 ports

Figure 6-9. LOOPE Test Access Connection

FACILITY SIDE

PORT

E

EQUIPMENT SIDE

PORT

F

TEST ACCESS PORT

A SIDE

B SIDEB SIDE

A SIDE

KAS*

677-0101-1

032003


FAD A FAD BOR

TAD A

OR

TAD B



Figure 6-10. LOOPF Test Access Connection

FACILITY SIDE

PORT

E

EQUIPMENT SIDE

PORT

F

TEST ACCESS PORT

A SIDE

B SIDE

*KAS

677-0102-1032003


FAD A FAD B

ORTAD A

ORTAD B



7. IP CONFIGURATION OPTIONS

Introduction

7.1 The 1677 SONET Link incorporates an IP stack allowing communications over the Ethernet interface as well as the SONET Section and Line DCCs. Communications over both these paths can be used independently or together. If the DCC functionality is not being employed, there is no need to assign an internal IP address. The default internal IP address of 172.16.254.254 should be retained. This document provides information that allows users to choose a configuration best suited to their needs and implement it. The interaction with the TL1 Gateway functionality is also discussed.

7.2 The 1677 SONET Link's IP stack allows the user to provision static routes and employs OSPF to propagate routing information over the DCC links. The OSPF protocol is also employed to distribute TL1 Gateway information from remote nodes to the TL1 Gateway node.

7.3 The DCC links can also be provisioned to carry OSI management traffic along with IP traffic. Both Section and Line DCCs on a link may not be simultaneously configured for IP use only or for OSI use only. Table 7-A summarizes the allowable combinations.

Table 7-A. Allowed Combinations of Section DCC and Line DCCSECTION DCC LINE DCC ALLOWED CONFIGURATIONUnused Unused YesIP IP NoIP Unused YesUnused IP YesIP OSI YesOSI IP YesOSI OSI NoOSI Unused YesUnused OSI Yes



Configurations

7.4 The IP stack allows the 1677 SONET Link to function as a limited-capability router. OSPF functionality is available on the DCC interfaces. There are no routing protocols (OSPF, RIP1, RIP2, etc.) available on the Ethernet interface. All of the following examples assume the EMS is connected to the TL1 gateway node via Ethernet. Each of the various configurations options are discussed below.

Stand-Alone Node

7.5 Figure 7-1 and figure 7-2 show examples of the stand-alone node configuration. This is the simplest configuration and comes in two variations. For the first variation, the node is locally monitored by a system on the same logical subnet. For the second variation, the monitoring system is located on a different logical subnet. The commands to configure each are described below.

Figure 7-1. Stand-Alone Node

677-0357-1101005

Ethernet (172.16.1.0)

1677SL Node 1172.16.1.101 (Ethernet)

EMS172.16.1.10



Figure 7-2. Stand-Alone Node with Router

677-0358-1101005

1677SL Node 1172.16.1.101 (Ethernet)

EMS172.16.2.10

Ethernet (172.16.1.0)

Ethernet (172.16.2.0)

Router

172.16.2.1

172.16.1.1



Stand-Alone Node with Monitoring System on Same IP Subnet

7.6 The stand-alone node with monitoring system on same IP subnet configuration requires provisioning the Ethernet interface with an IP address and subnet mask and entering the IP address of the monitoring system into the trusted host table. These commands must be entered through the local console (Timing Card serial) port. The required TL1 commands to configure this configuration follow:

ED-NE:::100::ETHIPADDR=172.16.1.101,ETHIPMASK=255.255.255.0;ENT-NE-TRUST:::110::172.16.1.10,255.255.255.255;

Additional monitoring/control systems can be allowed to access the node by entering additional TL1 ENT-NE-TRUST commands. To allow any IP address in the 172.16.1.0 subnet to access the node, use the following TL1 command in place of the above command:

ENT-NE-TRUST:::110::172.16.1.0,255.255.255.0;

Stand-Alone Node With Monitoring System on Different IP Subnet

7.7 As with the stand-alone node with monitoring system on same IP subnet configuration, for the stand-alone node with monitoring system on different IP subnet configuration, the Ethernet interface must be provisioned with an IP address and subnet mask, and the monitoring system's IP address must be entered into the trusted host table. Additionally, appropriate IP routing information must be entered into the node1. The following TL1 commands are used to configure the node:

ED-NE:::100::ETHIPADDR=172.16.1.101,ETHIPMASK=255.255.255.0;ENT-NE-IPRT::105:::172.16.2.0,255.255.255.0,172.16.1.1,1;ENT-NE-TRUST:::110::172.16.2.10,255.255.255.255;


ENT-NE-TRUST:::110::172.16.2.0,255.255.255.0;

1. The monitoring system is assumed to be a *nix based system with appropriate default or static routes entered such that it can send IP traffic on the correct interface to the appropriate next hop router. Additionally, the routers in the path between the monitoring system and the node are presumed to be running appropriate routing protocols such as RIP, RIP2, or OSPF.



Multiple Co-Located Nodes without DCC Connectivity

7.8 Figure 7-3 and figure 7-4 show examples of the multiple co-located nodes without DCC connectivity configuration. This configuration also comes in two variations. For the first variation, the nodes are locally monitored by a system on the same logical subnet. For the second variation, the monitoring system is located on a different logical subnet. The commands to configure each node are described below. The process repeats the command described in the stand-alone node section on each node with appropriate changes for the IP address assigned to each node.

Figure 7-3. Multiple Co-Located Nodes without DCC Connectivity - Example 1

677-0359-1101005

EMS172.16.1.10

1677 Node 1

172.16.1.101 (Ethernet)

1677 Node 2

172.16.1.102 (Ethernet)1677 Node 3

172.16.1.103 (Ethernet)



Figure 7-4. Multiple Co-Located Nodes without DCC Connectivity - Example 2

677-0360-1101005

1677 Node 1

172.16.1.101 (Ethernet)

EMS172.16.2.10

Ethernet (172.16.1.0)

Ethernet (172.16.2.0)

Router

172.16.2.1

172.16.1.1

1677 Node 21677 Node 3

172.16.1.102 (Ethernet) 172.16.1.103 (Ethernet)



Multiple Co-Located Nodes with Monitoring System on Same IP Subnet

7.9 The multiple co-located nodes with monitoring system on same IP subnet configuration requires provisioning the Ethernet interface with an IP address and subnet mask and entering the IP address of the monitoring system into the trusted host table. These commands must be entered through the local console (Timing Card serial) port. The required TL1 commands for each host to configure this configuration follow:

NODE 1ED-NE:::100::ETHIPADDR=172.16.1.101,ETHIPMASK=255.255.255.0;ENT-NE-TRUST:::110::172.16.1.10,255.255.255.255;



As with the single-node configuration, additional monitoring/control systems can be allowed to access the nodes by entering additional TL1 ENT-NE-TRUST commands. To allow any IP address in the 172.16.1.0 subnet to access the nodes, use the following TL1 command in place of the above command:

ENT-NE-TRUST:::110::172.16.1.0,255.255.255.0;



Multiple Co-Located Nodes with Monitoring System on Different IP Subnet

7.10 As with the configuration described in the preceding section, for the multiple co-located nodes with monitoring system on different IP subnet configuration the Ethernet interface must be provisioned with an IP address and subnet mask and the monitoring system's IP address must be entered into the trusted host table. Additionally, appropriate IP routing information must be entered into the node. The following TL1 commands are used to configure the node:

NODE 1ED-NE:::100::ETHIPADDR=172.16.1.101,ETHIPMASK=255.255.255.0;ENT-NE-IPRT::105:::172.16.2.0,255.255.255.0,172.16.1.1,1;ENT-NE-TRUST:::110::172.16.2.10,255.255.255.255;




ENT-NE-TRUST:::110::172.16.2.0,255.255.255.0;

Multiple Nodes with DCC Connectivity

7.11 Figure 7-5 and figure 7-6 show examples of the multiple nodes with DCC connectivity configuration. This configuration also comes in two variations. For the first variation, the nodes are locally monitored by a system on the same logical subnet. For the second variation, the monitoring system is located on a different logical subnet. Since the DCCs are active in this configuration, each node has two IP addresses assigned: Ethernet and Internal (i.e. DCC). These addresses should be in different subnets. In these examples, Node 1 functions as the IP routing gateway. The commands to configure each node are described below1.

1. The monitoring station in this configuration needs to have a static route for the internal subnet configured to use Node 1's Ethernet address as the next hop.



Figure 7-5. Multiple Nodes with DCC Connectivity - Example 1

677-0361-1101005

1677 Node 1

Ethernet (172.16.1.0)

172.16.1.101 (Ethernet)

EMS172.16.1.10

1677 Node 2 1677 Node 3

172.16.100.102 (DCC) 172.16.100.103 (DCC)

172.16.100.101 (DCC)



Multiple Nodes with DCC Connectivity and Monitoring System on Same IP Subnet

7.12 The multiple nodes with DCC connectivity and monitoring system on same IP subnet configuration requires the provisioning of the internal IP address and subnet mask on all nodes. The Ethernet IP address and subnet mask for the IP gateway also must be provisioned. The remote (non-gateway) nodes need a route back to the monitoring station via the internal IP address

Figure 7-6. Multiple Nodes with DCC Connectivity - Example 2

677-0362-1101105

1677 Node 1

172.16.1.101 (Ethernet)

1677 Node 2 1677 Node 3

172.16.100.102 (DCC) 172.16.100.103 (DCC)

172.16.100.101 (DCC)

EMS172.16.2.10

Ethernet (172.16.1.0)

Ethernet (172.16.2.0)

Router

172.16.2.1

172.16.1.1



on Node 1. The IP address of the monitoring system must also be entered into the trusted host table of each node. These commands must be entered through the local console (Timing Card serial) port. The required TL1 commands for each host to configure this configuration follow:

NODE 1ED-NE:::100::IPADDR=172.16.100.101,IPMASK=255.255.255.255,SWITCHNAME=Node1";ED-NE:::105::ETHIPADDR=172.16.1.101,ETHIPMASK=255.255.255.0;ENT-NE-TRUST:::110::172.16.1.10,255.255.255.255;

NODE 2

ED-NE:::100::IPADDR=172.16.100.102,IPMASK=255.255.255.255,SWITCHNAME="Node2";ENT-NE-IPRT::106:::172.16.1.10,255.255.255.255,172.16.100.101,1;ENT-NE-TRUST:::110::172.16.1.10,255.255.255.255;

NODE 3

ED-NE:::100::IPADDR=172.16.100.103,IPMASK=255.255.255.255,SWITCHNAME="Node3";ENT-NE-IPRT::106:::172.16.1.10,255.255.255.255,172.16.100.101,1;ENT-NE-TRUST:::110::172.16.1.10,255.255.255.255;

ALL NodesENT-NETIF::OC48-1-A-1:1000:::LINELL=PPP,LINEUL=IP;ENT-NETIF::OC48-2-A-1:1001:::LINELL=PPP,LINEUL=IP;

Multiple Nodes with DCC Connectivity and Monitoring System on Different IP Subnet

7.13 The multiple nodes with DCC connectivity and monitoring system on different IP subnet configuration requires the provisioning of the internal IP address and subnet mask on all nodes. The Ethernet IP address and subnet mask for the IP gateway node also must be provisioned. The remote nodes will not have their Ethernet interfaces provisioned. The gateway node also requires provisioning of a static route back to the monitoring station. The static route information is propagated over the DCC interfaces to the remote nodes via



OSPF. The IP address of the monitoring system must also be entered into the trusted host table of each node. These commands must be entered through the local console (Timing Card serial) port. The required TL1 commands for each host to configure this configuration follow:

NODE 1ED-NE:::100::IPADDR=172.16.100.101,IPMASK=255.255.255.255,SWITCHNAME="Node1";ED-NE:::105::ETHIPADDR=172.16.1.101,ETHIPMASK=255.255.255.0;ENT-NE-IPRT::106:::172.16.2.10,255.255.255.255,172.16.1.1,1;ENT-NE-TRUST:::110::172.16.2.10,255.255.255.255;

NODE 2ED-NE:::100::IPADDR=172.16.100.102,IPMASK=255.255.255.255,SWITCHNAME="Node2";ENT-NE-TRUST:::110::172.16.2.10,255.255.255.255;

NODE 3ED-NE:::100::IPADDR=172.16.100.103,IPMASK=255.255.255.255,SWITCHNAME="Node3";ENT-NE-TRUST:::110::172.16.2.10,255.255.255.255;


TL1 Gateway Use With Multiple Nodes and DCC Connectivity

7.14 The previous configurations all assumed the management station was communicating directly with the node. However, the 1677 SONET Link supports the concept of TL1 Gateways. A TL1 Gateway operates by relaying commands from the management station to a remote node. Network operators may provision more than one TL1 Gateway in the network. The TL1 Gateway appears to the remote node as the originating point of the TL1 session. Therefore, the TL1 Gateway's internal IP address must appear in the remote node's trusted host table. The use of a TL1 Gateway requires each node have a unique System ID (SID). OSPF propagates the remote node's SID, IP address, and TCP port information to the TL1 Gateway, which maintains a table mapping the SID to the remote node's internal IP address and TCP port.

NODE 1ED-NE:::100::IPADDR=172.16.100.101,IPMASK=255.255.255.255,SWITCHNAME="Node1";ED-NE:::105::ETHIPADDR=172.16.1.101,ETHIPMASK=255.255.255.0;



ENT-NE-IPRT::106:::172.16.2.10,255.255.255.255,172.16.1.1,1;ENT-NE-TRUST:::110::172.16.2.10,255.255.255.255;SET-SID:::120::"Node1";ED-NE-TL1::130:::PRMPT="node1> ",GWENB=Y;

NODE 2ED-NE:::100::IPADDR=172.16.100.102,IPMASK=255.255.255.255,SWITCHNAME="Node2";ENT-NE-TRUST:::110::172.16.100.101,255.255.255.255;SET-SID:::120::"Node2";

NODE 3ED-NE:::100::IPADDR=172.16.100.103,IPMASK=255.255.255.255,SWITCHNAME="Node3";ENT-NE-TRUST:::110::172.16.100.101,255.255.255.255;SET-SID:::120::"Node3";


Advanced Configurations

The previous configurations cover the vast majority of the expected configurations. However, the IP routing capability within the 1677 SONET Link allows for usage beyond the traditional ones.

Passing Non-TL1 Management Traffic to Attached Ethernet Devices

The 1677 SONET Link DCC links can also carry non-1677 SONET Link management traffic to remote equipment connected to the Ethernet interface. Figure 7 shows an example of such a configuration. This configuration is also using the TL1 Gateway functionality described in the previous example. The available DCC bandwidth is sufficient to configure, monitor, and diagnose equipment attached to the Ethernet interface.1 For instance, the control port for an IP router may be attached to the Ethernet interface of a remote 1677 SONET Link. The provisioning of proper IP routes in the 1677 SONET Link network allows management traffic to enter the Ethernet interface of an IP gateway node, pass over the DCC links, and exit the Ethernet interface where the router is located. Provisioning a configuration of this type

1. There may be more than one Ethernet attached device connected to the Ethernet port if an Ethernet switch, hub, or router is directly connected to the 1677 SONET Link interface to distribute the Ethernet data.



requires static routes at the gateway node and the remote node. Additionally, static routes may be required in intermediate routers. The attached equipment may require static (or default) routes. The commands to provision this configuration follow:

NODE 1ED-NE:::100::IPADDR=172.16.100.101,IPMASK=255.255.255.255,SWITCHNAME="Node1";ED-NE:::105::ETHIPADDR=172.16.1.101,ETHIPMASK=255.255.255.0;ENT-NE-IPRT::106:::172.16.2.0,255.255.255.0,172.16.1.1,1;ENT-NE-IPRT::107:::172.16.3.0,255.255.255.240,172.16.100.102

Figure 7-7. Passing Non-TL1 Management Traffic to Attached Ethernet Devices

677-0363-1101105

1677 Node 1

172.16.1.101 (Ethernet)

1677 Node 2 1677 Node 3

172.16.100.102 (DCC)

172.16.100.103 (DCC)

172.16.100.101 (DCC)

EMS172.16.2.10

Ethernet (172.16.1.0)

Ethernet (172.16.2.0)

Router

172.16.2.1

172.16.1.1

Alt. EMS172.16.2.11

Ethernet (172.16.3.0/28)

Ethernet (172.16.3.16/24)

172.16.3.17/28 (Ethernet)172.16.3.1/28 (Ethernet)

Router

Ethernet (172.16.4.0/24)

172.1.6.4.1/24

172.16.3.18/28



ENT-NE-IPRT::108:::172.16.3.16,255.255.255.240,172.16.100.103ENT-NE-TRUST:::110::172.16.2.10,255.255.255.255;SET-SID:::120::"Node1";ED-NE-TL1::130:::PRMPT="node1> ",GWENB=Y;

NODE 2ED-NE:::100::IPADDR=172.16.100.102,IPMASK=255.255.255.255,SWITCHNAME="Node2";ED-NE:::105::ETHIPADDR=172.16.3.1,ETHIPMASK=255.255.255.240;ENT-NE-TRUST:::110::172.16.100.101,255.255.255.255;SET-SID:::120::"Node2";

NODE 3ED-NE:::100::IPADDR=172.16.100.103,IPMASK=255.255.255.255,SWITCHNAME="Node3";ED-NE:::105::ETHIPADDR=172.16.3.17,ETHIPMASK=255.255.255.240;ENT-NE-IPRT::106:::172.16.4.0,255.255.255.0,172.16.3.18ENT-NE-TRUST:::110::172.16.100.101,255.255.255.255;SET-SID:::120::"Node3";

